>> > In procedure open-file: No such file or directory:
>> > "/System/Library/Fonts/??? W4.ttc" [...]
>> >
>> > SO it looks to me like there's a problem with not getting UTF characters
>> > into the proper file name in the Scheme procedure. Any ideas for what to
>> > do next?
>>
>> What
On Sun, Jan 21, 2024 at 11:05 PM Werner LEMBERG wrote:
> > In procedure open-file: No such file or directory:
> > "/System/Library/Fonts/??? W4.ttc"
> >
> > I checked out the /System/Library/Fonts directory, and found these fonts
> > listed:
> >
> > ヒラギノ角ゴシック W3.ttc
> >
> > ヒラギノ角ゴシック
On Sun, Jan 21, 2024 at 12:33 AM Werner LEMBERG wrote:
>
> >> You have to check the log files in `lybook-db` to find the problematic
> >> `.ly` file(s). Does `make test` succeed? You should actually try that
> >> before running `make doc`...
> >>
> >
> > Interesting -- the CG has make doc show
On Mon, Jan 22, 2024 at 3:58 PM Jean Abou Samra wrote:
> Le lundi 22 janvier 2024 à 21:10 +, Werner LEMBERG a écrit :
> > > >
> > OK, thanks. This means that there is apparently a macOS-specific
> > problem with either Guile or LilyPond. For testing purposes I renamed
> > one of my local
Le lundi 22 janvier 2024 à 16:38 -0700, Carl Sorensen a écrit :
> > Looks like no error:
> >
> > carl@Carls-MBP-2 lilypond % build/out/bin/lilypond
> > input/regression/pdf-copy-paste.ly
> > GNU LilyPond 2.25.13 (running Guile 3.0)
> > Processing `input/regression/pdf-copy-paste.ly'
> >
Ah, but, wait.
$ touch àéù.txt
$ guile3.0
scheme@(guile-user)> (open-file "àéù.txt" "r")
$1 = #
~/tmp $ LC_ALL=C guile3.0
scheme@(guile-user)> (open-file "àéù.txt" "r")
ice-9/boot-9.scm:1685:16: In procedure raise-exception:
In procedure open-file: No such file or directory: "??.txt"
On Mon, Jan 22, 2024 at 5:58 PM Jean Abou Samra wrote:
> Le lundi 22 janvier 2024 à 16:38 -0700, Carl Sorensen a écrit :
> > > Looks like no error:
> > >
> > > carl@Carls-MBP-2 lilypond % build/out/bin/lilypond input/regression/
> pdf-copy-paste.ly
> > > GNU LilyPond 2.25.13 (running Guile 3.0)
Le lundi 22 janvier 2024 à 21:10 +, Werner LEMBERG a écrit :
> > >
> OK, thanks. This means that there is apparently a macOS-specific
> problem with either Guile or LilyPond. For testing purposes I renamed
> one of my local fonts to something containing Katakana, and my
> self-compiled
> Can someone remind me why the build system sets the C locale
> in the first place?
Answering my own question: I guess it is because we can't assume the
system has an en_US.UTF-8 locale or a C.UTF-8 locale?
Maybe we ought to set only LC_MESSAGES to C? It should prevent overriding
the system
Le mardi 23 janvier 2024 à 01:58 +0100, Jean Abou Samra a écrit :
> The latter is basically that this regtest (pdf-copy-paste.ly)
> has Japanese text, specifying the Noto Serif JP font, but since
> you apparently don't have that font installed, Fontconfig falls
> back to some system font, and
Le lundi 22 janvier 2024 à 18:00 -0700, Carl Sorensen a écrit :
> So I ran the file in this log message:
>
>
> carl@carls-mbp-2 build % out/bin/lilypond out/share/lilypond/current/ly/
> init.ly
>
> GNU LilyPond 2.25.13 (running Guile 3.0)
>
> Processing `out/share/lilypond/current/ly/init.ly'
On Mon, Jan 22, 2024 at 4:37 PM Carl Sorensen
wrote:
>
>
> On Sun, Jan 21, 2024 at 12:33 AM Werner LEMBERG wrote:
>
>>
>> >> You have to check the log files in `lybook-db` to find the problematic
>> >> `.ly` file(s). Does `make test` succeed? You should actually try that
>> >> before running
Here is the current countdown report.
The next countdown will begin on 2024-01-24
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!2236 Improve docstring of the `\postscript` markup command - Werner Lemberg
>> Can someone remind me why the build system sets the C locale in the
>> first place?
>
> Answering my own question: I guess it is because we can't assume the
> system has an en_US.UTF-8 locale or a C.UTF-8 locale?
Exactly. Some time ago (see
14 matches
Mail list logo
