>> 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?


    Werner

Reply via email to