I'm not top posting
When I use the \clef bass_8, the lay-out of it is not nice. The 8 is place to
low. It doesn't hit the clef. Compare it for instance with the clef for guitar
(\clef G_8).
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http
rosea wrote:
It doesn't hit the clef.
where should it hit - inside the stafflines? the bass-clef does not reach
the lower part of the stave, so where would you put the 8 (or 15)?
--
View this message in context:
http://www.nabble.com/%5Cclef-%22bass_8%22%2C-lay-out-issue
On 3/5/09 6:07 AM, \r rosea.grammost...@gmail.com wrote:
I'm not top posting
When I use the \clef bass_8, the lay-out of it is not nice. The 8 is place
to
low. It doesn't hit the clef. Compare it for instance with the clef for guitar
(\clef G_8).
Can you show us a scanned example
(Graham, or someone else, we should really try to make sure that
all commands and reserved words available in LilyPond are listed
in the Index. \layout is one of those missing. Doing such an exercise
would also help identifying what information is missing from the manual
today.)
Part of an
Aaron Mehl wrote:
Ok here is where I am confused. There is a structure
for files which makes a file valid.
Then there is a grammar which must also be followed
for the lanuguage of lilypond.
I get the feeling after reading the docs that the
structure of lilypond is loose.
What I mean is
Ok here is where I am confused. There is a structure
for files which makes a file valid.
Then there is a grammar which must also be followed
for the lanuguage of lilypond.
I get the feeling after reading the docs that the
structure of lilypond is loose.
What I mean is that it appear (if I am
--- Mats Bengtsson [EMAIL PROTECTED] wrote:
For me it's the opposite. I find it much harder to
see
the structure if you only have a long \score{...}
where
I have to scroll several pages from beginning to
end.
Well if I take docbook as an example a book can have
multiple sections no
