>> A. LilyPond actually _does_ support the Latin1 character set, as Latin1 >> and Unicode coincide on the first 256 codepoints. > > I don't quite see that. If I put an e-acute (a byte of decimal value > #233) in a LilyPond file, it is skipped -- it does not appear in the PDF > output. I have to put in the unicode equivalent, which is the two bytes > #195 #169 (where 169 = 233 - 64) in order for LilyPond to give me an > e-acute.
Yes, that is called Encoding. >> B. LilyPond does not support Latin1 encoding. This is because Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
