Re: Renaming `ly:wide-char->utf-8`

[Jean Abou Samra]

> Le 10/02/2022 13:37, David Kastrup <dak@gnu.org> a écrit :
> 
> 
> Jean Abou Samra <jean@abou-samra.fr> 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 too broad a term IMHO, and
> >>>> the function doesn't do any character set conversions.
> >>> We are more or less close to transitioning to Guile 2 exclusively
> >>> which is going to obviate it anyway.
> >> Obviate what? Will the name of this function change automatically?
> >
> >
> > No :-) But we will be able to spell (ly:wide-char->utf-8 1234) as
> > either (integer->char 1234)
> Wrong since a char is not a string.
> 
> > 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).
> Again, a char is not a string. ly:wide-char->utf-8 generates a string.


Oh, true. These should all be (string (integer->char ...)).
For convert-ly, (compose string integer->char) should be a
very reasonable replacement.