Le 25/09/2021 à 14:44, David Kastrup a écrit :
Aaron Hill <lilyp...@hillvisions.com> writes:
Still, be pedantic and miss the forest for the trees, my point was
that \x is a good option if \* was going to be problematic.
Sure, but the problem with \× is exactly that × is not part of ASCII and
thus does not uniformly work on extended ASCII encodings (of which the
non-8-bit UTF-8 encoding that LilyPond uses for representing code points
in the Latin-1 specific subrange of Unicode is only one).
You did realize that Aaron talked about the good option being \x and not \×?
