I don't really see the problem. What you already have proposed is to
use property settings to change between the different styles. To save
some typing, it will then be easy to add macros such as
\arrowQuarterToneAccidentals (please make up something shorter)
and \...whatever, to easily change betw
Hi,
we use additional simple up/down arrows placed left to normal
accidentals, giving a concise way to specify the complete eighth tone
scale. The glyphs are actually included in the font. This would make
even more changing of alteration syntax necessary, though.
I don't mind to be able to combin
I needed to fabricate a MIME for LilyPond sources, and
hit upon text/x-lilypond; any opinions?
(text/x-lilypond as opposed to application/x-lilypond,
by the way, so that the browser falls back on plain text and
not binary.)
--
Peter Danenberg
Hi,
On Sun, 28 Jan 2007, Rune Zedeler wrote:
> Trying to get a copy of jneemans branch to try out the new page breaking and
> score stretching stuff.
>
> I clone the repository with
>
> $ git clone git://git.sv.gnu.org/lilypond.git
>
> Then I create .git/remotes/jneem containing
>
> URL: git+
I agree %100 with the addition of accidentals with arrows. However, I also
think that both, the standard 1/4 and 3/4 tone signs Lilypond already has
and the new ones should both be accessible, and, ideally, within the same
"notehead-style". Otherwise combining them in a single score would require
Orm Finnendahl schrieb:
> thanks for pointing that out. That's exactly along the lines I was
> thinking. Is anybody capable of doing the scheme/lilypond code? I
> don't know Metafont yet but I think I could handle that part and throw
> in the glyphs (they are currently PS Type1).
Well, I'd be de
Hi all,
thanks for pointing that out. That's exactly along the lines I was
thinking. Is anybody capable of doing the scheme/lilypond code? I
don't know Metafont yet but I think I could handle that part and throw
in the glyphs (they are currently PS Type1).
--
Orm
Am 28. Januar 2007, 05:19 Uhr
