On Sat 17 Dec 2016 at 18:38:59 (+0100), Simon Albrecht wrote: > 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.
I have no problem with UTF-8 per se, but only with the more exotic characters, outline arrows, scissors, five-pointed star and suchlike (on Debian). I would imagine Chinese characters would fall in that category. Cheers, David.
pdfFi7G8aoZk9.pdf
Description: Adobe PDF document
_______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
