Re: [Lilypond-auto] Issue 2985 in lilypond: lilypond: Umlauts and other special characters incorrectly exported to PDF meta data

[lilypond]

Comment #6 on issue 2985 by address@hidden: lilypond:  
Umlauts and other special characters incorrectly exported to PDF meta data
http://code.google.com/p/lilypond/issues/detail?id=2985

copy of the email I sent to evince list:

Dear evince developpers,

The attached pdf triggers an error while opened with evince 3.4.0
(poppler/cairo 0.18.4) on fedora 17:
Entity: line 10: parser error : Input is not proper UTF-8, indicate  
encoding !
Bytes: 0xE4 0x3C 0x2F 0x72
='x-default'>Untitled</rdf:li></rdf:Alt></dc:title><dc:creator><rdf:Seq><rdf:li>

       ^

The pdf was created with lilypond 2.16.0 (music typesetting tool) on
fedora 17. According to the developpers of lilypond, the "ä" character
that triggers the error is well encoded and the error should not be
reported by evince:
00004830  74 3e 3c 2f 64 63 3a 74  69 74 6c 65 3e 3c 64 63  | 
t></dc:title><dc|
00004840  3a 63 72 65 61 74 6f 72  3e 3c 72 64 66 3a 53 65   
|:creator><rdf:Se|
00004850  71 3e 3c 72 64 66 3a 6c  69 3e e4 3c 2f 72 64 66  | 
q><rdf:li>.</rdf|

On this last line, we can see that the code of the "ä" is e4 which is
the right unicode code.
Other readers like xpdf, okular and pdfinfo do not report any error.
Here is the issue link at lilypond:
http://code.google.com/p/lilypond/issues/detail?id=2985

Regards,

Frédéric

Attachments:
        unicode.ly  56 bytes
        unicode.pdf  19.1 KB