On Mon, 21 Nov 2016 10:49:07 +0100
David Kastrup <d...@gnu.org> wrote:
> Thomas Morley <thomasmorle...@gmail.com> writes:
>
> > 2016-11-20 23:23 GMT+01:00 Antonio Ospite <a...@ao2.it>:
> >> On Sun, 20 Nov 2016 22:07:39 +0100
> >> Antonio Ospite <a...@ao2.it> wrote:
> >>
> >>> On Sun, 20 Nov 2016 01:12:59 +0100
> >>> Thomas Morley <thomasmorle...@gmail.com> wrote:
> >>>
> >> [...]
> >>> > Well, this example gives a gs-error again:
> >>> >
> >>> > \header { title = "ちりぬるを)" } \markup \null
> >>> >
> >>>
> >>> The problem here is that, when writing to the postscript file, the
> >>> escaping is (mistakenly) done before the encoding, so the escaped "\)"
> >>> gets represented in UTF-16 as "^@\^@)" which makes the ')' not really
> >>> escaped anymore and ghostscript fails.
> >>>
> >>> I'll try to come up with a better solution for this problem.
> >>>
> >>
> >> I think I got it this time. David?
>
> In general I think you are better off reverting to "bytevectors" for
> most of our purposes since they don't result in unnecessary conversions.
> But they really require at least Guile 2.0.12 in order to not have some
> showstopper bugs interfering.
>
Thanks, at the end I settled on this change:
https://ao2.it/tmp/lilypond-guile2/patches_2016-11-22/0010-Fix-the-encoding-of-the-PDF-metadata-when-using-guil.patch
and now ly:encode-string-for-pdf works with guile-2.0, and I didn't
need to complicate scm/framework-ps.scm even further.
Ciao,
Antonio
--
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
