Comment #9 on issue 2985 by [email protected]: lilypond: Umlauts and other
special characters incorrectly exported to PDF meta data
http://code.google.com/p/lilypond/issues/detail?id=2985
Regarding comment #7: no need to be "sorry for the noise". It turns out
after some further analysis that indeed LilyPond produces invalidly encoded
PDF Metadata. It also turns out that we can't really do anything about
that since the Metadata is produced by Ghostscript via pdf2ps, and so the
fault lies with Ghostscript ultimately. I attach a basic PostScript file
exhibiting the same problem after running it through ps2pdf.
In case nobody on the Evince list picks this up, does anybody want to
report this to Ghostscript developers?
Attachments:
sss.ps 76 bytes
sss.pdf 2.4 KB
