Re: Ghostscript fails with special characters in filename

[Reinhold Kainhofer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Donnerstag, 20. August 2009 10:48:09 schrieb Reinhold Kainhofer:
> Yes, I think that's the case here. It seems that gs is well able to handle
> 16- bit unicode characters, but it needs the correct file name.
>
> A little more playing around shows this: Calling "lilypond --png ĉacâ.ly"
> prints an error message:
>    Error: /undefinedfilename in (\304\\x89ac\303\242.ps)
> As you can see, the high-byte character is written as \x89ac, however, the
> backslash is escaped, which of course makes it an invalid UTF-8 character
> considering the \304 before...
[...]
> So, basically, lilypond messes up the proper UTF-8 encoding of the external
> utility calls.

Hmm, it seems that it is actually guile's fault:
guile> (simple-format #f "~asdfasdf" "ĉâ")
"�\x89âsdfasdf"
guile> (simple-format #f "~a b âĉ" "ĉâ")
"�\x89â b â�\x89"
guile> "âĉ"
"â�\x89"

To me this seems like guile is not able to properly handle wide UTF-8 
characters properly and messes up the wide characters.

Cheers,
Reinhold

- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, address@hidden, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFKjRZ0TqjEwhXvPN0RAuHSAJ4z32tPuwfQpf8Q1d4tcLUodKw4VQCgnDHB
ZvDLuRb4vrkdnxvhOHhx6vY=
=nTcp
-----END PGP SIGNATURE-----