>> In searching about the problem people suggest that the text
>> encoding should be utf-16be and include the BOM
Yep.
> It's actually simpler than using utf-16be. All that is needed is to
> use escape sequences instead of the accented characters. E.g. I
> would need to use "\362" instead of "ò".
That's another encoding, PDFDocEncoding (documented in the PDF
reference).
> Unfortunately, I haven't found a scheme/guile method to create those
> escape sequences from a utf8 string (I don't even know exactly which
> escape sequences these are! At least they are none of the usual
> utf8 representations).
I suggest to consequently use UTF-16BE (including surrogate support)
which can be easily converted from and to UTF-8.
Werner
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
