Re: Issue 2173 in lilypond: Deal with file names not encoded in UTF-8

[lilypond]

Comment #4 on issue 2173 by address@hidden: Deal with file names not encoded  
in UTF-8
http://code.google.com/p/lilypond/issues/detail?id=2173

That just means that Windows supports byte streams.  Pango is not a Windows  
component.

UTF-8 support would mean supporting UTF-8 on the command line, in console  
input and output, and, regarding this issue, in filenames.  The _names_ of  
the files are the problem, not the contents.  How to interpret the contents  
is up to the application, and LilyPond uses Pango for typesetting them.

The question is whether the error messages on the console look sensibly,  
and whether file names are input and output as UTF-8 in a readable (and  
identical) manner on both console as well as log files.