> On 26 Sep 2021, at 10:16, Jean Abou Samra <j...@abou-samra.fr> wrote:
>
> Le 26/09/2021 à 09:57, Hans Åberg a écrit :
>>> On 26 Sep 2021, at 06:49, Werner LEMBERG <w...@gnu.org> wrote:
>>>
>>> You might provide a MR, maybe it gets accepted. I still doubt that it
>>> would be a good idea.
>> There is a conflict in some contexts between {SYMBOL} and {COMMAND}, so may
>> not work. To get a regular COMMAND syntax, they should start with something
>> that SYMBOL does not.
>>
>> Otherwise you might replace the function YYText_utf8 with proper UTF-8
>> patterns, a variation of:
>>
>> /* UTF-8 character with valid Unicode code point. */
>> utf8char
>> [\x09\x0A\x0D\x20-\x7E]|[\xC2-\xDF][\x80-\xBF]|\xE0[\xA0-\xBF][\x80-\xBF]|[\xE1-\xEC\xEE\xEF]([\x80-\xBF]{2})|\xED[\x80-\x9F][\x80-\xBF]|\xF0[\x\90-\xBF]([\x80-\xBF]{2})|[\xF1-\xF3]([\x80-\xBF]{3})|\xF4[\x80-\x8F]([\x80-\xBF]{2})
>
> I concur with Werner.I don't think special characters like ×
> are easier to type than a backslash, and they are an annoyance if
> you don't have keyboard shortcuts at hand (like on a computer that
> is not your primary work device). They require more effort
> for beginners and memory of keyboard input methods for everyone.
> Plus, it's not clear how to make them work in lyrics mode and
> markup given that something like \lyricmode { ×8 } is already
> valid syntax and has legitimate uses.
I use text substitutions, which I have found to be fastest both to create and
use. For example, I have set ".x" to translate to "×".
