[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Musings on the font-encoding property

From: David Kastrup
Subject: Re: Musings on the font-encoding property
Date: Wed, 29 Mar 2023 17:05:42 +0200
User-agent: Gnus/5.13 (Gnus v5.13)

Werner LEMBERG <> writes:

>>>  AFAICS, the only limitation is that an ordinary text font with a
>>> family name 'music' cannot be used.
>> No :-) unlike what its name suggests, the `font-family` property is
>> a family symbol, not a font string (yes, it's another misnamed thing
>> in font handling). The `font-family` values recognized by default
>> are `'roman`, `'sans` and `'typewriter`. Nothing prevents you from
>> doing
> Ah.  Well, this makes the issue even more straightforward.
>> The practical impact of the change is mostly a syntax modification
>> that is not easy to convert-ly (the removal of `\text`, which should
>> be replaced with `\roman`, `\sans` or `\typewriter` depending on the
>> case).
> We could make `\text` a no-op (it's rather seldom used, I reckon) and
> `convert-ly` emit a warning.

A default conversion of \text to \roman would likely match more than 90%
of the current uses.

David Kastrup

reply via email to

[Prev in Thread] Current Thread [Next in Thread]