Re: Likely bug in 2.16.1: Changing docu ment fonts messes lots of things up…

[Arle Lommel]

Hi Trevor,

I see you answered before I posted that I'd found the cause, and I think the 
discovery of the cause shows that your answer is really to a different problem. 
There is a real problem with font handling here and taking the approach in the 
documentation sections you point to to fix it would be fundamentally a kludge, 
one that would have to be changed every time there is a change in global staff 
size and one that would require manual correction to any local overrides.

Thank you for trying to point me to the proper location in the manuals, but I 
think I've discovered a genuine bug…

Best,

Arle


On 2012 Dec 14, at 10:18 , "Trevor Daniels" <address@hidden> wrote:

> 
> Arle Lommel Friday, December 14, 2012 8:31 AM
> 
>> I have followed instructions on how to change document fonts, as outlined at 
>> http://lilypond.org/doc/v2.16/Documentation/notation/fonts
>> 
>> But I find when I change the fonts that there are some undesirable side 
>> effects in *other* areas: Basically everything but the staff, note stems, > 
>> and beams gets bigger, meaning more is crammed in the same space. Chords 
>> start to look like smears, note heads stick slightly past the stems, > and 
>> time signatures and clefs stick outside the staff.
>> 
>> If this is not a bug (even though it sure looks like one), perhaps the 
>> documentation could be updated with an explanation on how to adjust for > 
>> these sorts of problems.
> 
> You must have missed this section in the docs:
> 
> http://www.lilypond.org/doc/v2.17/Documentation/learning/appearance-of-objects
> 
> Have a look in particular at
> 
> http://www.lilypond.org/doc/v2.17/Documentation/learning/size-of-objects
> 
> and 
> 
> http://www.lilypond.org/doc/v2.17/Documentation/learning/length-and-thickness-of-objects
> 
> Trevor