Robin Bannister wrote Wednesday, March 25, 2009 12:46 PM
Where NR 3.3.3 is talking about \char it says
The following example shows UTF-8 coded characters being used
which got me typing in a UTF-8 byte pair after the ##x.
But, of course, it is more like UTF-32.
In fact, referring to UTF-32 would make it easier
to google for these high code points.
No, the manual is correct. LilyPond uses UTF-8.
UTF-8 is a variable-length encoding for Unicode in
which the common characters are encoded in 8 bits
and the less common in 16, 24 or 32 bits.
UTF-32 is an encoding which uses exactly 32 bits for
every code point.
However, I agree the description of \char in the
manual could be clearer. It needs to indicate the
hex string is a variable length dependent on the
character being encoded. I'll fix it.
Trevor
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
