Re: \displayMusic and UTF-8

[David Kastrup]

Malte Meyn <address@hidden> writes:

> Hi list,
>
> attached you find a file that tries to \displayMusic a string
> containing the apostrophe ’ (U+2019). Everything fine with this file
> says my hexeditor. But not with lilypond’s output which you find in
> the attached file displayMusic_utf8_output.txt.
>
> The apostrophe from the source (displayMusic_utf8.ly):
> E2 80 99 = U+2019
> The ‘apostrophe’ from the output:
> E2 5C 78 38 30 99 = garbage, 5C is not a valid UTF-8 continuation byte.
>
> The substring 5C 78 38 30 is ASCII/UTF-8 for \x80 so it’s not
> completely random ;)
>
> Malte
>
> \version "2.19.40"
>
> \void \displayMusic \tempo "l€™istesso tempo"
>
>
> (make-music
>   'TempoChangeEvent
>   'metronome-count
>   #f
>   'tempo-unit
>   #f
>   'text
>   "l\x80™istesso tempo")

That's a Guile-1 artifact which has no idea of UTF-8.  You'll find that
if you read that exact byte sequence back into Guile-1.8 (for example,
by putting a $ in front of the make-music expression and using an editor
which will not balk at preserving the bytes surrounding \x80), it will
work perfectly fine.

-- 
David Kastrup