Since there is so much work going into the documentation, I thought it
would be useful to add such a type to the tracker.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
ht
Nicolas Sceaux schrieb:
Le 7 févr. 08 à 02:49, Han-Wen Nienhuys a écrit :
Since the incipit is a completely
different piece of notation (eg. whose spacing and beat counting
should not influence the main music), this should be implemented
similiar to the hack with a \score inside the instrume
Le 7 févr. 08 à 02:49, Han-Wen Nienhuys a écrit :
Since the incipit is a completely
different piece of notation (eg. whose spacing and beat counting
should not influence the main music), this should be implemented
similiar to the hack with a \score inside the instrument name.
I think the best
On 07/02/2008, Han-Wen Nienhuys wrote:
> 2008/2/7, Mats Bengtsson :
> > Keeping the description at a cookbook level, as you propose, is one
> > alternative.
Probably the worst one. :-) But a good conversation starter, I hope.
> > Another alternative is to describe more clearly what the different
2008/2/7, Mats Bengtsson <[EMAIL PROTECTED]>:
> Keeping the description at a cookbook level, as you propose, is one
> alternative.
> Another alternative is to describe more clearly what the different
> parameters
> actually mean.
So, the e-mail message that Risto cites is a bit on the obtuse side
Risto Vääräniemi wrote:
Should the Section 1.8.2 Text markup - Font selection have a text
describing how the make-pango-font-tree parameters should be used.
Something like:
If the set-global-staff-size is used for changing the global staff
size, the \myStaffSize should be set to the same
Dear All,
In 2006 Eyolf made a extensive study about the combined effect of the
set-global-staff-size and the Pango font definitions in
make-pango-font-tree [1]. It seems that this manual section has not
been yet updated. I was struggling with the same thing yesterday and
because I've got no inter
