Re: Lilypond 2.19.43 font issue

[Hans Åberg]

> On 12 Jun 2016, at 18:38, Andrew Bernard <address@hidden> wrote:
> 
> Hi Hans,
> 
> 
> On 13 June 2016 at 02:11, Hans Åberg  wrote:
> 
>> The solution: the UTF-8 locale has not been set as it wishes [1]. OS X 
>> 10.11.6 has no leading language “en”, only
>>  LC_CTYPE=UTF-8
>> 
>> It suffices with any single one of:
>>  export LC_CTYPE=en.UTF-8
>>  export LC_CTYPE=en_US.UTF-8
>>  export LC_ALL=en_US.UTF-8
>> 
> 
> 
> I don't have 10.11.6 but 10.11.5. If you do:
> 
> $ locale -a | grep UTF-8
> 
> there is no standalone UTF-8 locale without a language prefix.

I dropped Apple a note.

> If there is in 10.11.6 I would be quite surprised. This sounds like a
> beta defect in OS X to me. But are you sure you have your regional
> settings set up correctly?

Yes, I checked ‘env’ without .profile.

I could add that, either in .profile, or the script that invokes lilypond, but 
then I will not see the issue anymore.