|
From: | Martin Tarenskeen |
Subject: | Re: lilypond pdf error/warning messages from Evince |
Date: | Fri, 16 Dec 2011 09:12:24 +0100 (CET) |
User-agent: | Alpine 2.02 (LFD 1266 2009-07-14) |
On Thu, 15 Dec 2011, Francisco Vila wrote:
2011/12/15 Francisco Vila <address@hidden>:Entity: line 5: parser error : Input is not proper UTF-8, indicate encoding ! Bytes: 0xFF 0xFF 0xFF 0xFF <rdf:Description rdf:about='52da2502-5ec5-11ec-0000-73b663e6b6f????????????uuid:52 ^ Entity: line 5: parser error : xmlParseCharRef: invalid xmlChar value 16 ??????uuid:52da2502-5ec5-11ec-0000-73b663e6b6f2011-12-15T00:10:12+01:00kOAll the errors come from metadata sections in your PDF and yes, they are put there by GhostScript. So, no LilyPond bug here.
I have found that if use Lilypond to create a .ps file, and then manually convert this to pdf using the scripts provided by the ghostscript package:
- if I use ps2pdf, ps2pdf14, or ps2pdfwr I will get all these error messages - if I use ps2pdf12 or ps2pdf13 I will not get any error messages
-- MT
[Prev in Thread] | Current Thread | [Next in Thread] |