I'm reading the manual from cover to cover (sad person that I am), and
have found the following things so far ... (dead tree version ...)
Page 101, section 5.11.1, in the only real paragraph in the section -
"You should use \addlyrics unless you need to fancy things," - we seem
to have a missin
[EMAIL PROTECTED] writes:
>
> > > . The CFF part of bigcheese20.otf is extracted and put into a PS
> > > resource which is loaded with the -h option of dvips. If that
> > > doesn't work, lilypond-book simply emits
> > > \special{header=bigcheese.cff} at the beginning of the document.
>
> I
Graham Percival <[EMAIL PROTECTED]> writes:
> At the beginning of your violin part, do
> \tag #'(violin score)
>
> In your printing section, use
> \keepWithTag #'violin
> or
> \keepWithTag #'score
> depending on what you want.
Speaking of \keepWithTag, I usually use a custom version of it,
that l
On 5-Jan-05, at 5:14 PM, Erlend Aasland wrote:
Here's some trivial documentation patches:
Thanks; applied to CVS.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On 27-Dec-04, at 10:17 AM, Giancarlo Niccolai wrote:
The tag is a rater nice feature; however, it's syntax is quite
complex. Would
it be possible to simplify it and make it more typing friendly?
It's certainly _possible_, but I'm not certain how much friendlier it
could
be. Do you have any sugge
Hello,
In order to make tabs easier to read, I suggest that lilypond should
use a bold font when printing tabs. Tabs are a lot more readable when
printed in bold text.
Please apply.
Regards,
Erlend Aasland
tab-bold.patch
Description: Binary data
__
Well, replying to myself:
Previous patch was buggy when fret = 0. Sorry 'bout that. This patch
is now fully tested and 100% correct.
Regards,
Erlend Aasland
On Thu, 6 Jan 2005 02:59:45 +0100, Erlend Aasland <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> A problem arises when you try to write tab
