Re: Ghostscript fails with special characters in filename

[Patrick McCarty]

On 2009-08-20, Reinhold Kainhofer wrote:
> 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.

I've been following the Guile mailing lists recently, and it sounds
like UTF-8 handling will be improved in the next stable release.

In the meantime, does this patch work?


Thanks,
Patrick

0001-Fix-832.patch
Description: Text document