Thanks to Joe and John, we can simplify the .itely files. Here's
the new policy: (from writing-texinfo.txt)
* Most LilyPond input should be produced with:
@lilypond[verbatim,quote,relative=2]
or
@lilypond[verbatim,quote,relative=1]
If you want to use \layout{} or define variables, u
Valentin Villenave wrote
Actually, you're not the only one who isn't running Linux. MSysGit
could help you:
http://code.google.com/p/msysgit/
You probably don't need msysGit - this is the full Git development package
for Windows including the source code and the full development environment.
2008/5/20 Valentin Villenave <[EMAIL PROTECTED]>:
> 2008/5/20 padovani <[EMAIL PROTECTED]>:
>> Does anyone know a trick to slash the circled-tip option of Hairpins? The
>> circle seems to be a flageolet... maybe with some postscript... ??
>
> Unfortunately it's hardcoded in hairpin.cc, so it's a lo
2008/5/20 padovani <[EMAIL PROTECTED]>:
> Does anyone know a trick to slash the circled-tip option of Hairpins? The
> circle seems to be a flageolet... maybe with some postscript... ??
Unfortunately it's hardcoded in hairpin.cc, so it's a lot trickier. I
don't know what to say... besides "good luc
Does anyone know a trick to slash the circled-tip option of Hairpins?
The circle seems to be a flageolet... maybe with some postscript... ??
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Dienstag, 20. Mai 2008 schrieb David Fletcher:
> When I ran musicxml2ly on a music XML file containing breves e.g.
>
> 16
> 1
> breve
>
> it crashed in ly_expression with
> ValueError: negative shift count
>
> I fixed t
2008/5/20 David Fletcher <[EMAIL PROTECTED]>:
> "If you want to contribute fixes of any kind, use the following procedure
> Check out the latest sources via GIT at git.sv.gnu.org
>git clone git://git.sv.gnu.org/lilypond.git"
> I don't use Unix/Linux and the only git I know is me (an old one -
When I ran musicxml2ly on a music XML file containing breves e.g.
16
1
breve
it crashed in ly_expression with
ValueError: negative shift count
I fixed this by changing musicexp.py in the python folder, replacing line
152: str = '%d%s' % (1 << self.dura
2008/5/20 Jan Nieuwenhuizen <[EMAIL PROTECTED]>:
> What about a news item on rss feed?
News about the News? I like the idea :-)
If so, we should also send a mail on lilypond-info.
Cheers,
Valentin
___
lilypond-devel mailing list
lilypond-devel@gnu.o
2008/5/20 Trevor Daniels <[EMAIL PROTECTED]>:
> @code{^}, @code{_} or @code{-}, can usually be omitted, in which
> case @code{-} is assumed. But a direction indicator is
> @strong{always} required before
>
> @itemize
> @item @code{\tweak} commands and
> @item @code{\markup} commands.
> @end itemiz
John Mandereau writes:
> I had forgot to update them with @[EMAIL PROTECTED] This is fixed in Git
> now.
What about a news item on rss feed?
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
___
2008/5/20 Joe Neeman :
> On Mon, May 19, 2008 at 9:09 PM, Risto Vääräniemi wrote:
>> I tried to create the special case for 16th notes only. 8th notes and
>> notes from 32th forward (until 64th note) would use a common placement
>> rule. This is because the 16th note flags hang "lower" than the
>>
Am Dienstag, 20. Mai 2008 schrieb Trevor Daniels:
> I'm drafting a section for the Notation Reference which says:
>
> When adding articulations to notes the direction indicator,
> @code{^}, @code{_} or @code{-}, can usually be omitted, in which
> case @code{-} is assumed. But a direction indicator
I trust that you've seen the previous discussion about this?
http://lists.gnu.org/archive/html/lilypond-user/2008-02/msg00688.html
I can't see anything in that discussion that you didn't cover below,
but I figured the link wouldn't hurt.
Cheers,
- Graham
On Tue, 20 May 2008 11:06:01 +0100
"Trev
I'm drafting a section for the Notation Reference which says:
When adding articulations to notes the direction indicator,
@code{^}, @code{_} or @code{-}, can usually be omitted, in which
case @code{-} is assumed. But a direction indicator is
@strong{always} required before
@itemize
@item @code{
I found a useful solving on the http://lsr.dsi.unimi.it/LSR/Snippet?id=346
(Bach-Praeludium), by a basic simplification anybody can make patterns in
polyphony at any places, too. But something has come up.
Here's the point by explaining the noting of Rachmaninoff's Prelude in G
minor
I want to
16 matches
Mail list logo
