bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Font scaling seems to be broken


From: Cameron Horsburgh
Subject: Re: Font scaling seems to be broken
Date: Sat, 15 Sep 2007 09:07:29 +1000
User-agent: Mutt/1.5.16 (2007-06-11)

On Fri, Sep 14, 2007 at 11:29:07AM -0700, Graham Percival wrote:
> http://code.google.com/p/lilypond/issues/detail?id=367
>
> Sorry,
> - Graham
>

Hmm. I saw this bug, but the title threw me off. There seem to be a few 
different issues. Looking at it more closely shows that it is the same thing. 

I would suggest that the reference to the \layout{ #(layout-set-staff-size 20) 
construct be deleted from the manual (11.2.1). If it has always been broken, we 
don't want to advertise it too much.

I think I may have noticed one or two other problems that may or may not be 
related. I'll mention one here, and test the others properly tonight.

There seems to be a problem with the #(set-global-staff-size 7) method. In this 
snippet the multi-measure rest doesn't scale correctly:

%%%%%%%%%%
\version "2.11.32"
#(set-global-staff-size 7)
\relative c''{
  \set Score.skipBars = ##t
  \override MultiMeasureRest #'expand-limit = 1
  a1 | R1*2|
}
\paper{
  ragged-right = ##t
}
%%%%%%%%%% 



> Cameron Horsburgh wrote:
>> Hi folks,
>> This could just be me, but I seem to be having a little trouble with
>> font scaling. Consider this score (it's not quite minimal because I
>> wanted to include a few grobs) : %%%%%%%%%%%%%%%%%%
>> \version "2.11.32"
>> \relative c''{
>>     \key aes \major
>>   aes2 c4 d|   \time 6/8
>>   \clef bass
>>   aes,8 bes c des?4 c8
>> }
>> \layout{
>> %  #(layout-set-staff-size 15)
>> %  #(layout-set-staff-size 26)
>> }
>> \paper{
>>   ragged-right = ##t
>> }
>> %%%%%%%%%%%%%%%%%%
>> This compiles and renders appropriately (I've attached PNGs of the
>> output.) However, if I uncomment the first line in the \layout block
>> the noteheads, time signature and other things seem to be too
>> small. If I uncomment the second they're too large. The same thing happens 
>> if I try the #(set-global-staff-size ??)
>> construct instead. Is this a bug or are my eyes getting old? 

--
=============================================
Cameron Horsburgh

=============================================

Attachment: multi.png
Description: PNG image


reply via email to

[Prev in Thread] Current Thread [Next in Thread]