Werner LEMBERG escreveu:
>>> Isn't this the same what I propose?
>> I thought you were proposing to scrap B altogether.
>
> Well, I have proposed this
>
> ^ ^
> | B| header
> | v
>A|
> |
> v
>
>
> which
> > Isn't this the same what I propose?
>
> I thought you were proposing to scrap B altogether.
Well, I have proposed this
^ ^
| B| header
| v
A|
|
v
which can be directly transformed into your proposal.
Werner LEMBERG escreveu:
>> The effective distance would be the lowest of both.
>
> Isn't this the same what I propose?
I thought you were proposing to scrap B altogether.
>
>
>
> ^ header^ ^ no header
>
> >>> Regarding head-separation I wonder whether the current approach
> >>> of lilypond to handle headers and footers is the right one.
> >>> Wouldn't it be better to define a zone of a given height within
> >>> the header (or footer) is rendered, instead of defining a
> >>> distance from the heade
Werner LEMBERG escreveu:
>>> Regarding head-separation I wonder whether the current approach of
>>> lilypond to handle headers and footers is the right one. Wouldn't
>>> it be better to define a zone of a given height within the header
>>> (or footer) is rendered, instead of defining a distance fr
> > Han-Wen, shall I apply this to the git repository?
>
> yes, looks good.
Done.
> > Regarding head-separation I wonder whether the current approach of
> > lilypond to handle headers and footers is the right one. Wouldn't
> > it be better to define a zone of a given height within the header
>
Werner LEMBERG escreveu:
>> ;; not tested
>> (define (first-line-position line layout)
>> "Position of the first line on page"
>> (max (+ (if (ly:prob-property? line 'is-title)
>> 0.0 ; do not use page-top-space when the 1st line is a title
>> (ly:output-def-lookup l
> > Independently of this, I think it is another error that
> > `head-separation' and `page-top-space' are applied on the first page
> > if a title is present.
>
> You'd rather have to modify the function that computes the first system
> position on page: `first-line-position' in the file
> scm/la
> You'd rather have to modify the function that computes the first
> system position on page: `first-line-position' in the file
> scm/layout-page-layout.scm
Thanks, I came to the same conclusion (but without doing any
programming).
> (define (first-line-position line layout)
> "Position of the
Werner LEMBERG <[EMAIL PROTECTED]> writes:
> Independently of this, I think it is another error that
> `head-separation' and `page-top-space' are applied on the first page
> if a title is present.
>
> To circumvent this I would like to say
>
> page-top-space =
> #(if (not-first-page)
>
I wrote:
To circumvent this I would like to say
page-top-space =
#(if (not-first-page)
(* 12 mm)
0)
within the \header block, however, it doesn't work.
I mean the \page block, of course.
> If you look in ly/titling-init.ly, you will find lines like
> \on-th
If you look in ly/titling-init.ly, you will find lines like
\on-the-fly #not-first-page \fromproperty #'header:instrument
I'm not sure that it helps directly, but you can probably check the
definition of #not-first-page.
/Mats
Werner LEMBERG wrote:
Currently, the title block of a score is st
Currently, the title block of a score is still handled as a separate
system instead of being attached to the topmost stave. I consider
this as a severe design error; for example, it makes
`ragged-bottom=##f' produce very ugly results in case the systems are
vertically large.
Well, we have to liv
13 matches
Mail list logo
