-Wen Nienhuys <[EMAIL PROTECTED]>
To: Trevor Baô a <[EMAIL PROTECTED]>
CC: Paul Scott <[EMAIL PROTECTED]>, lilypond-user@gnu.org,
[EMAIL PROTECTED], Karl Berry <[EMAIL PROTECTED]>
Subject: Re: navigating web documentation
Trevor Baô a schreef:
> (I second this, es
The `Non-guitar tablatures' node in the lilypond 1.6.0 manual says:
First you can change the number of strings, by setting the number of
lines in the *note (lilypond-internals)TabStaff:: . You can change the
strings tuning. A string tuning is given as a Scheme list with one
in
The above example shows you how to set the TabStaff to four strings,
tuned as you asked.
Thank you very much for this. However, I can't get it to work :(.
For starters, I told you the wrong notation for the tuning. Mandolin
tuning, like violin, is GDAE from the G below middle C (top sp
Thanks for all the help -- if anyone is interested in the bass line of
Bach's bourree in e minor transposed for mandolin, let me know :).
I do have two more questions, one minor, one major, so to speak:
1) is it really true that bar numbers cannot printed on every bar (so
says node `Bar numbe
Try setting #'break-visibility in BarNumber.
Forgive me, but to what?
I tried:
\property Score.BarNumber \override #'break-visibility = #
but (not surprisingly), this just gets `Unbound variable: http://mail.gnu.org/mailman/listinfo/lilypond-user
Here's another simple (I hope) question to which I don't see the answer
in the manual ... How to tell lilypond to generate a blank sheet of
music paper? (With tablature on the bottom, rather than two regular
staves, if that makes a difference.)
Thanks,
karl
Is it possible to force typesetting an accidental above the staff,
instead of on the notes? On an accidental-by-accidental basis rather
than for a whole piece.
This is common in pre-baroque pieces when most accidentals were left out
of the score because every performer knew what to do; modern ed
These are not really bugs, all up for interpretation, so I thought I'd
write here ...
I wanted to give a url about simple Lilypond input to the prototypical
naive user (my mom, who is a musician but not a programmer).
I start at http://lilypond.org/website/manuals.html. It says:
Text input: Li
>> than teaching absolute entry only to ditch it a few pages later.
I wasn't thinking of a few pages. More like a couple more examples
which do nothing more with pitches than the first one days (so not
digging a deeper non-\relative hole), but rather show a few other
completely basic things,
opens the door to dead links.
That door is open no matter what, it seems to me. It's not just people
clicking around your web site under your control that are affected.
Another Texinfo manual might have an xref to one of your nodes. That
will become a dead link.
The best way I know to close
Patches are always welcomed, but I do not know if anyone is
interested in hacking on the current php code to add such a feature.
Right, I'm not exactly "interested", but if that single feature makes
the difference between lilypond moving to savannah or , I'd
at least try to look at it. Of
assume that the Savane installation on Savannah will eventuall move to
FusionForge).
There are no such plans at present.
I would be glad if we could use Savannah
Ok, I'll look into the image-displaying feature. Unless by some miracle
"someone" else gets there first :).
while g
> In lilypond 1.6.6 (and earlier), it seems that rests are not output in
> tablature. It would be nice to do this;
Please do not add that. DaveA
Dare I ask why not? Why is it bad to output rests?
In any case, it could be an option, so that the rests could be output or
not, dependi
13 matches
Mail list logo
