Re: lSR=197

[Simon Albrecht]

On 17.12.2016 17:41, MING TSANG wrote:
> Window 10 has no problem use UTF-8  .ly file. after compile through 
> Frecobaldi .pdf and .mid files are created.
> It seems that internal working of lilypond and its associated programs 
> not handling it. I was wondering there is a work-around?

Well, you were the one reporting that there _is_ a problem with UTF-8 
file names on Windows. See 
<https://sourceforge.net/p/testlilyissues/issues/2173/>.
The deal is very simple: If somebody comes along who needs UTF-8 file 
names on Windows, and has the time and skills to look for the problem 
and craft a fix for LilyPond so it can handle them, then the problem 
will be fixed.
However, the majority of LilyPond users and a greater majority of 
LilyPond developers do not use Windows, and while it would be nice to be 
able to use UTF-8 file names, it’s no dealbreaker if you can’t. 
Additionally, the guile-v2 transition is involved, so it’s certainly 
wise to not wait for a fix and instead adopt using ASCII-only file names 
for LilyPond work.

Best, Simon