RE: Reverting to the 2.13.46 font

[James Lowe]

Jon,

________________________________________
From: address@hidden address@hidden on behalf of Xavier Scheuer address@hidden
Sent: 20 June 2011 17:04
To: Jon Toohill
Cc: lilypond-user
Subject: Re: Reverting to the 2.13.46 font

On 20 June 2011 17:47, Jon Toohill <address@hidden> wrote:
>
> Whoops, I wrote that backwards. The older font (the one I want) is on
> the right, whereas the newer font that I'm seeing in 2.14 is on the
> left. Sorry for the confusion.
>
> And, in retrospect, I'm not seeing the problem on Linux. In that case,
> it's just my configuration on the Mac. I'll see what I can do to fix
> it.

OK, that makes more sense (of course!).

Could it be the issue of Mac OS X (not due to LilyPond then!) when
upgrading to OS X 10.6.7?  This Mac OS X issue has been reported there
for instance:
http://lists.gnu.org/archive/html/lilypond-user/2011-04/msg00619.html
Did you recall making such upgrade between 2.13.46 and 2.14?

--------------------------

Apple 'broke' some aspects of Font handling, but this was fixed in the last 
signficant Update that came out circa April of this year. If you are unsure, 
open your system properties, click on Software Update and then click on the 
'Installed Software' button at the top.

There is an explicit 'Snow Leopard Font Update' mentioned (dated 27/04/2011) - 
assuming you use Snow Leopard. I cannot recall (if you don't) if this was a 
10.6.x specific issue.

That's not to say this is your problem*

So assuming it isn't just this update then you could simply use a tool like 
'Onyx' (freely downloadable) to delete the font cache, then you can reboot and 
the OS will rebuild it and LilyPond will use the 'correct' font - whatever it 
is called.

James

* The symptom reported that this update fixed actually caused LP to generate 
PDFs without any noteheads (just the stems). So it may not be anything similar 
or related to your issue.