[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lSR=197
From: |
David Wright |
Subject: |
Re: lSR=197 |
Date: |
Sat, 17 Dec 2016 15:47:28 -0600 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Sat 17 Dec 2016 at 16:31:33 (+0000), MING TSANG wrote:
> sorry I hit the wrong key before I complete the email.Here is the other email
> message intended to send.I attached a small snippet contains UTF-8 in file
> name if compile fine with pdf file name contains the UTF-8.However the log
> file cannot display UTF-8 file name (see red text below).Starting
> lilypond-windows.exe 2.19.52 [testing-utf-8_file-name_中文.ly]...Processing
> `C:/Users/user/Google
> Drive/CHOIR_2016/testing-utf-8_file-name_����.ly'Parsing...Interpreting
> music...Preprocessing graphical objects...Finding the ideal number of
> pages...Fitting music on 1 page...Drawing systems...Layout output to
> `./tmp-lilypond-WyLwQu'...Converting to
> `testing-utf-8_file-name_����.pdf'...Deleting
> `./tmp-lilypond-WyLwQu'...Success: compilation successfully
> completedCompleted successfully in 1.5".
>
> filename_名字.ly is the LSR 197 refer to previous email (which is included in
> this emai) below:
>
>
> This is to followup previous "LSR - file information [0.24759]" on Nov 26,
> 2016.Is there a work-a-round solution?
Perhaps reread
http://lists.gnu.org/archive/html/lilypond-user/2016-11/msg00707.html
and
http://lists.gnu.org/archive/html/lilypond-user/2015-11/msg00331.html
Whether you can hack the scheme/guile to make it read UTF8, I don't
know. In any case, it might be a waste of time in view of the
intention, I believe, to migrate to a newer version in the long term.
Cheers,
David.
Re: lSR=197, MING TSANG, 2016/12/17
- Re: lSR=197, Phil Holmes, 2016/12/17
- Re: lSR=197,
David Wright <=