Hi Simon,David & Phil: It seems that UTF-8_filename.ly is not working on LSR-197.I am using the following snippet to hard-code the file information (ie UTF-8_filename.ly) and put it in header-copyright. Though, it only displays on first page. I was hopping LSR-197 will provide file information so that I will force it to display on all pages.I am looking forward to wait for Guile-V2 in lilypond. Hope will compile under Guile v2.Thank you all for helping.Immanuel,Ming%%%%%\version "2.19.52" \language "english" folderD = "c:/"folder = "choir_2016/"fileN = "testing-utf-8_file-name_中文"
\header { title = "生根建造" subtitle = "rooting construction" subsubtitle =
\markup{\concat{\folderD \folder \fileN}} copyright =
\markup{\concat{\folderD \folder \fileN}}}\score { {c' d' e' f' g' a' b' r4}
\layout {}}
%%%%%
From: MING TSANG <[email protected]>
To: "[email protected]" <[email protected]>; Simon Albrecht
<[email protected]>
Sent: Saturday, December 17, 2016 6:45 PM
Subject: Re: lSR=197
David,Thank you for showing that LSR-197 compiles fine with utf-8 characters on
Debian. I think under window 10, this should be the same.Lilypond has no
problem reading and display (output) utf-8 characters. On window 10 llilypond
produces utf-8.pdf utf-8.mid; utf-8 _header (title, subtitle, poet, composer,
arranger etc) and utf-8 lyrics. It is only LSR-197 not accepting utf-8
characters on file-utf-8.ly file name.As mention in this subject LSR-197 on the
list that guile-v2 transition is involved. I can wait till then.In the
meantime, I will keep using UTS-8-filename just refrain using LSR-197 to
generate filename. I am working away using hard-code variables for display as
drive#/utf-8_folder/utf-8_sub-folder/utf-8_filename.ly on pdf file footer.Thank
you all for helping.Immanuel,Ming
From: David Wright <[email protected]>
To: Simon Albrecht <[email protected]>
Cc: MING TSANG <[email protected]>; Lilypond-usermailinglist
<[email protected]>
Sent: Saturday, December 17, 2016 5:10 PM
Subject: Re: lSR=197
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.
testing-utf-8_file-name_中文.pdf
Description: Adobe PDF document
_______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
