Hi,
The patch I send in my previous post to lilypond-devel still contained
some bugs. Here is an updated version (which I hope will work fine!).
The bugs I mentioned in my previous post still apply.
Kristof.
Changelog:
2005-07-07 Kristof Bastiaensen <[EMAIL PROTECTED]>
* ly/declarat
I have posted a news on fr.audiofanzine.com after having translated it
in French.
Just in case, I enclose it.
Jean-Charles
Title: LilyPond version 2.6 maintenant disponible en téléchargement
LilyPond - La notation musicale pour tous
LilyPond, c'est un logiciel libre et gratuit pour cr
On Thursday 07 July 2005 12.14, Mats Bengtsson wrote:
> Erik Sandberg wrote:
> > Another way could be to tag the trick-worty snippets in the LSR somehow.
>
> In contrast to non-trick-worthy? For example, I find most of the
> examples in the current Regression Test very useful as Tips and Tricks
> a
> I finished the scheme part of the part-combiner. Attached is the patch.
Great, thanks. Do you have an example of what cases/bugs have been
fixed? Do the regression tests still work?
> There are still bugs in the C part which I cannot solve:
It would be nice to create small snippets for the
Hi,
I finished the scheme part of the part-combiner. Attached is the patch.
There are still bugs in the C part which I cannot solve:
- When there are two voices unisilence, one of them a multimeasure rest,
and the other a smaller rest, than sometimes the multimeasure rest
swallows the other, wit
Of course you are right that the manual should be updated.
The problem is the old '\musicglyph #"scripts-stopped"' doesn't work
anymore
The glyph name has changed to scripts.stopped, which I hope that
convert-ly will update automatically. This is also what it says in
the manual.
> and '\column'
Graham Percival wrote:
Index: lilypond/Documentation/user/changing-defaults.itely
diff -u lilypond/Documentation/user/changing-defaults.itely:1.130
lilypond/Documentation/user/changing-defaults.itely:1.131
--- lilypond/Documentation/user/changing-defaults.itely:1.130 Tue May 24
19:09:20 200
It's certainly possible to let lilypond-book automatically detect the
text height of the LaTeX document and set the vsize correspondingly.
However, it's not so much use since
1. It's only relevant when you explicitly have a \book{..} in
your .ly code (which it turn is mainly useful to be able t
Erik Sandberg wrote:
Another way could be to tag the trick-worty snippets in the LSR somehow.
In contrast to non-trick-worthy? For example, I find most of the
examples in the current Regression Test very useful as Tips and Tricks
as well.
/Mats
__
On Thursday 07 July 2005 07.33, Graham Percival wrote:
> On 5-Jul-05, at 10:23 AM, Sebastiano Vigna wrote:
> > I don't know why it's not easy to search--be more specific.
>
> I find the searching easy. If you want more powerful searches, then
> you can
> download the snippets and use grep. :)
Wo
10 matches
Mail list logo
