Am Sonntag, dem 13.02.2022 um 22:37 +0100 schrieb Thomas Morley: > Am So., 13. Feb. 2022 um 16:02 Uhr schrieb Jonas Hahnfeld via LilyPond > user discussion <lilypond-user@gnu.org>: > > > > Am Samstag, dem 12.02.2022 um 20:43 +0800 schrieb Jinsong Zhao: > > > On 2022/2/12 18:48, Jonas Hahnfeld wrote: > > > > Am Mittwoch, dem 09.02.2022 um 20:39 +0100 schrieb Jonas Hahnfeld via > > > > LilyPond user discussion: > > > > > Am Mittwoch, dem 09.02.2022 um 12:07 +0800 schrieb Jinsong Zhao: > > > > > > Hello developers, > > > > > > > > > > > > Thanks a lot for the transition towards Guile 2.2. I've switched to > > > > > > 2.23.6/guile 2.2 on Windows 10. > > > > > > > > > > > > The only issue I have currently encountered is when the filename is > > > > > > in > > > > > > Chines, for example "中文.ly", then lilypond could not generate PDF > > > > > > file. It could generate corrected "中文.midi", and also could generate > > > > > > correct ps and svg file, but the filenames are unreadable > > > > > > characters. > > > > > > > > > > I can confirm it's not working with the version using Guile 2.2 - > > > > > however I remember that I tested this in the past and made it work, > > > > > after fixing something in the LilyPond code. I'll have to dig up > > > > > details and figure out what broke / changed... > > > > > > > > Yep, I remembered correctly that there was a general issue with special > > > > character filenames: https://gitlab.com/lilypond/lilypond/-/issues/6089 > > > > The problem was fixed quite some time ago in > > > > https://gitlab.com/lilypond/lilypond/-/merge_requests/612 and this > > > > works, ie LilyPond produces the correct filenames and correctly encoded > > > > contents. What doesn't work is Ghostscript converting the generated > > > > Postscript to PDF, which I suspect is a packaging / cross-compilation > > > > error on our side since it works with the official Windows binaries > > > > from ghostscript.com and the older version of Ghostscript from GUB... > > > > > > > > Tracked in https://gitlab.com/lilypond/lilypond/-/issues/6282, I'll > > > > have to investigate how to solve this. > > > > > > Thanks a lot for your efforts on this issue. > > > > > > In my case, LilyPond 2.23.6/guile 2.2 does not produce the correct > > > filenames but correctly encoded contents. The only correct filename > > > produced by LilyPond is the MIDI file. However, LilyPond 2.23.6/guile > > > 1.8 produced all correct filenames. > > > > > > The following is the output in CMD terminal. You will find that > > > filenames of ps and svg are not correct. However the content are correct. > > > > Okay, interesting. So there actually may be multiple problems on > > Windows, again working fine on Linux... > > Not for me, being on Ubuntu 20.04 > > Compiling > \markup \override #'(font-name . "思源黑体 HW Bold") "中文" > returns: > ERROR: In procedure ly:text-interface::interpret-markup: > Invalid read access of chars of wide string: "思源黑体 HW Bold 3.8662109375" > > For both setups (see my recent mail on devel), i.e. self-compiled > 2.23.6 and the GitLab-archive
Yes, that's a different problem (not related to filenames), reported in a different email thread. I also reproduced this on Linux yesterday, but didn't reply yet since I don't know what is at fault here (I presume some string conversion in our font handling).
signature.asc
Description: This is a digitally signed message part
