On Feb 6, 2022, at 22:23, Colin Campbell wrote:
>
> For my guidance, I'd be grateful if the community would correct or amplify
> the following recap of the patch handling process.
>
Colin, I think you summed it up well and I agree with Lukas' additions.
Thanks,
—
Dan
> Le 10/02/2022 13:37, David Kastrup a écrit :
>
>
> Jean Abou Samra writes:
>
> > Le 10/02/2022 à 08:26, Werner LEMBERG a écrit :
> > >>> Given that LilyPond uses Unicode exclusively I wonder whether we
> > >>> should rename
> > >>>
> ly:wide-char->utf-8
>
> to
>
> ly
Jean Abou Samra writes:
> Le 10/02/2022 à 08:26, Werner LEMBERG a écrit :
Given that LilyPond uses Unicode exclusively I wonder whether we
should rename
ly:wide-char->utf-8
to
ly:unicode->utf-8
or something similar. 'Wide character' is to
> Le 10/02/2022 08:59, Werner LEMBERG a écrit :
>
>
> > [...] we will be able to spell (ly:wide-char->utf-8 1234) as either
> > (integer->char 1234) or (for literals which is the majority of
> > cases) #\x4d2 (where 4d2 is the hex representation for the number
> > that has the decimal representa
* Jonas Hahnfeld, hah...@hahnjo.de [09/02/22 21:28]:
> Am Samstag, dem 29.01.2022 um 17:18 +0100 schrieb Walter Garcia-Fontes:
> > I'm following the official procedure to ask for commit access and
> > join the developer team.
> >
> > I am a contributor to the translations. I have contributed all t
> [...] we will be able to spell (ly:wide-char->utf-8 1234) as either
> (integer->char 1234) or (for literals which is the majority of
> cases) #\x4d2 (where 4d2 is the hex representation for the number
> that has the decimal representation 1234).
In other words, the function will become obsolet
Le 10/02/2022 à 08:16, Werner LEMBERG a écrit :
Given that LilyPond uses Unicode exclusively I wonder whether we
should rename
ly:wide-char->utf-8
to
ly:unicode->utf-8
or something similar. 'Wide character' is too broad a term IMHO, and
the function doesn't do any character set convers
