David Kastrup <d...@gnu.org> writes: > Jan Nieuwenhuizen <jann...@gnu.org> writes: > >> Frédéric Bron writes: >> >>> It is due to a bug in ghostscript. I submitted a bug report 29th of >>> Nov (2012) and it is now corrected. But it will take time until the >>> new version of ghostscript comes to everybody's distribution. >> >> Do you have a patch to go with this? We could put the patch into GUB >> right away. > > LilyPond degrades its encoding ASCII->Latin1->UTF16LE for PDF metadata. > Old versions of GhostScript can't deal with UTF16LE. Recent versions > balk at Latin1. We could likely temporarily improve user experience by > skipping the Latin1 phase. It's a bit of a gamble.
Well, I've put the gamble on. Patch up at <URL:http://code.google.com/p/lilypond/issues/detail?id=2985>. I guess we'll have less of a chore dealing with user protests when using that. I don't think checking for this problem with autoconf would be a good idea, either: Ghostscript is just too likely to be upgraded independently of LilyPond. -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
