Re: Issue 1502 in lilypond: Document information in PDF headers requires escapes for accented characters
Updates: Labels: -fixed_2-14_0 fixed_2_14_0 Comment #11 on issue 1502 by carl.d.s...@gmail.com: Document information in PDF headers requires escapes for accented characters http://code.google.com/p/lilypond/issues/detail?id=1502 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1502 in lilypond: Document information in PDF headers requires escapes for accented characters
Updates: Labels: fixed_2-14_0 Comment #10 on issue 1502 by carl.d.s...@gmail.com: Document information in PDF headers requires escapes for accented characters http://code.google.com/p/lilypond/issues/detail?id=1502 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1502 in lilypond: Document information in PDF headers requires escapes for accented characters
Updates: Status: Verified Comment #9 on issue 1502 by philehol...@googlemail.com: Document information in PDF headers requires escapes for accented characters http://code.google.com/p/lilypond/issues/detail?id=1502 Thanks for this, Keith. Took me a while to research the fact that the problem was only with the properties, not the output itself. But I'm pleased to say that both display properly on Windows on 2.15.2 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1502 in lilypond: Document information in PDF headers requires escapes for accented characters
Comment #8 on issue 1502 by k-ohara5...@oco.net: Document information in PDF headers requires escapes for accented characters http://code.google.com/p/lilypond/issues/detail?id=1502 Sounds like cut-and-paste did not result in a proper UTF8-encoded .ly file for Phil. I get a good PDF file on Windows XP so I will attach: 1) my Lilypond input file -) skip the PostScript because it embeds a font and gets big 2) the PDF I say the PDF is good because: Adobe Reader shows everything perfectly in the information fields. Sumatra's popup box uses a font that shows a box instead of the e-ogonek, but everything else is good. PDF-XChange spells out all the non-ascii characters as octal escape sequences. Attachments: WinXP.ly 202 bytes WinXP.pdf 19.7 KB WinXP.png 4.4 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1502 in lilypond: Document information in PDF headers requires escapes for accented characters
Updates: Summary: Document information in PDF headers requires escapes for accented characters Comment #7 on issue 1502 by philehol...@googlemail.com: Document information in PDF headers requires escapes for accented characters http://code.google.com/p/lilypond/issues/detail?id=1502 If I run this in Windows, I get Non Lo Far Pi Johann Baptist Strau And the errors below. How should this fix work? (lilypond-windows.exe:5596): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+, file C:/Program Files (x86)/LilyPondV2.15.2/usr/share/lilypond/current/fonts/otf/CenturySchL-Bold.otf continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+, file C:/Program Files (x86)/LilyPondV2.15.2/usr/share/lilypond/current/fonts/otf/CenturySchL-Bold.otf continuing, cross fingers (lilypond-windows.exe:5596): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+, file C:/Program Files (x86)/LilyPondV2.15.2/usr/share/lilypond/current/fonts/otf/CenturySchL-Roma.otf continuing, cross fingers Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... Layout output to `1502.ps'... warning: Conversion of string `Johann Baptist Strauß' to UTF-16be failed: Partial character sequence at end of input warning: Conversion of string `Non Lo Farò Più' to UTF-16be failed: Invalid byte sequence in conversion input warning: Conversion of string `Johann Baptist Strauß' to UTF-16be failed: Partial character sequence at end of input Converting to `./1502.pdf'... `(gs -q -dNOSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile=./1502.pdf -c.setpdfwrite -f1502.ps)' failed (1) error: failed files: "D:\\Music\\LilyPondDev\\BugSquad\\1502.ly" ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1502 in lilypond: DOcument information in PDF headers requires escapes for accented characters
Updates: Status: Fixed Comment #6 on issue 1502 by colinpkc...@gmail.com: DOcument information in PDF headers requires escapes for accented characters http://code.google.com/p/lilypond/issues/detail?id=1502 Unverified in 2.13.61 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1502 in lilypond: DOcument information in PDF headers requires escapes for accented characters
Updates: Status: Verified Comment #5 on issue 1502 by colinpkc...@gmail.com: DOcument information in PDF headers requires escapes for accented characters http://code.google.com/p/lilypond/issues/detail?id=1502 Verified 2.15.0 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1502 in lilypond: DOcument information in PDF headers requires escapes for accented characters
Updates: Status: Fixed Labels: -Patch-review fixed_2_15_0 Comment #4 on issue 1502 by percival.music.ca: DOcument information in PDF headers requires escapes for accented characters http://code.google.com/p/lilypond/issues/detail?id=1502 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1502 in lilypond: DOcument information in PDF headers requires escapes for accented characters
Updates: Status: Started Comment #3 on issue 1502 by reinhold...@gmail.com: DOcument information in PDF headers requires escapes for accented characters http://code.google.com/p/lilypond/issues/detail?id=1502 Pushed to master with commit dffe04e8e1a7c0b94fdfc30e44fe141dfbe7cbec ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1502 in lilypond: DOcument information in PDF headers requires escapes for accented characters
Updates: Labels: -Patch-new Patch-review Comment #2 on issue 1502 by colinpkc...@gmail.com: DOcument information in PDF headers requires escapes for accented characters http://code.google.com/p/lilypond/issues/detail?id=1502 Compiles and clean regtest on 2.13.60 ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1502 in lilypond: DOcument information in PDF headers requires escapes for accented characters
Updates: Labels: Patch-new Comment #1 on issue 1502 by reinhold...@gmail.com: DOcument information in PDF headers requires escapes for accented characters http://code.google.com/p/lilypond/issues/detail?id=1502 Patch is up for review: http://codereview.appspot.com/4398046/ ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1502 in lilypond: DOcument information in PDF headers requires escapes for accented characters
Status: Accepted
Owner:
Labels: Type-Defect Priority-High
New issue 1502 by colinpkc...@gmail.com: DOcument information in PDF
headers requires escapes for accented characters
http://code.google.com/p/lilypond/issues/detail?id=1502
An example:
\version "2.13.48"
\header
{
title = "Non Lo Farò Più"
composer = "Johann Baptist Strauß"
}
When viewing the pdf the title shows as "Non Lo Farò Più". I've only
tested this with Evince and Okular. In searching about the problem
people suggest that the text encoding should be utf-16be and include
the BOM
Thanks for spotting that bug (Bug squad, can you please open a bug report
for
this!).
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 "ò".
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).
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
