On Wed, 2022-05-25 at 13:24 -0600, David F. wrote:
>
> > On May 25, 2022, at 11:21 AM, Jonas Hahnfeld wrote:
> >
> > On Sat, 2022-05-21 at 15:20 -0600, David F. wrote:
> > > System: Intel-based macOS
> > >
> > > I make extensive use of UTF-8 characters in the filenames of my Lilypond
> > > fil
On Sat 21 May 2022 at 23:36:26 (-0600), David F. wrote:
> > On May 21, 2022, at 5:01 PM, Jean Abou Samra wrote:
> > Le 21/05/2022 à 23:20, David F. a écrit :
> >> System: Intel-based macOS
> >>
> >> I make extensive use of UTF-8 characters in the filenames of my Lilypond
> >> files. This works
> On May 25, 2022, at 11:21 AM, Jonas Hahnfeld wrote:
>
> On Sat, 2022-05-21 at 15:20 -0600, David F. wrote:
>> System: Intel-based macOS
>>
>> I make extensive use of UTF-8 characters in the filenames of my Lilypond
>> files. This works in Lilypond up through version 2.22. But Lilypond 2.
Am 25.05.22 um 19:21 schrieb Jonas Hahnfeld via LilyPond user discussion:
On Sat, 2022-05-21 at 15:20 -0600, David F. wrote:
System: Intel-based macOS
I make extensive use of UTF-8 characters in the filenames of my Lilypond files.
This works in Lilypond up through version 2.22. But Lilypond
On Sat, 2022-05-21 at 15:20 -0600, David F. wrote:
> System: Intel-based macOS
>
> I make extensive use of UTF-8 characters in the filenames of my Lilypond
> files. This works in Lilypond up through version 2.22. But Lilypond 2.23
> cannot handle UTF-8 characters in filenames.
>
> Filename: t
On Tue 24 May 2022 at 20:59:18 (-0700), Curt McDowell wrote:
> I get that same error if running under Docker, if LANG is set to
> en_US.UTF-8, but where en_US.UTF-8 does not exist in the output of
> "locale -a".
>
>./out/bin/lilypond scheme-sandbox /(Lilypond 2.23.0, Guile 2.2.7,
>Ubuntu 2
I get that same error if running under Docker, if LANG is set to
en_US.UTF-8, but where en_US.UTF-8 does not exist in the output of
"locale -a".
./out/bin/lilypond scheme-sandbox /(Lilypond 2.23.0, Guile 2.2.7,
Ubuntu 20.04)/
(open-input-file "tést.ly")
In procedure open-file: No su
Thomas Morley writes:
> Am So., 22. Mai 2022 um 07:36 Uhr schrieb David F. :
>>
>>
>>
>> > On May 21, 2022, at 5:01 PM, Jean Abou Samra wrote:
>> >
>> > Le 21/05/2022 à 23:20, David F. a écrit :
>> >> System: Intel-based macOS
>> >>
>> >> I make extensive use of UTF-8 characters in the filenames
Am So., 22. Mai 2022 um 07:36 Uhr schrieb David F. :
>
>
>
> > On May 21, 2022, at 5:01 PM, Jean Abou Samra wrote:
> >
> > Le 21/05/2022 à 23:20, David F. a écrit :
> >> System: Intel-based macOS
> >>
> >> I make extensive use of UTF-8 characters in the filenames of my Lilypond
> >> files. This
> On May 21, 2022, at 5:01 PM, Jean Abou Samra wrote:
>
> Le 21/05/2022 à 23:20, David F. a écrit :
>> System: Intel-based macOS
>>
>> I make extensive use of UTF-8 characters in the filenames of my Lilypond
>> files. This works in Lilypond up through version 2.22. But Lilypond 2.23
>> ca
Le 21/05/2022 à 23:20, David F. a écrit :
System: Intel-based macOS
I make extensive use of UTF-8 characters in the filenames of my Lilypond files.
This works in Lilypond up through version 2.22. But Lilypond 2.23 cannot
handle UTF-8 characters in filenames.
Filename: tést.ly
\version
System: Intel-based macOS
I make extensive use of UTF-8 characters in the filenames of my Lilypond files.
This works in Lilypond up through version 2.22. But Lilypond 2.23 cannot
handle UTF-8 characters in filenames.
Filename: tést.ly
\version "2.22"
{ c' }
Under v2.22, this file
12 matches
Mail list logo
