Ok, I've added it here.
http://code.google.com/p/lilypond/issues/detail?id=526
Han-Wen can decide which case is the bug.
Cheers,
- Graham
Rune Zedeler wrote:
Graham Percival skrev:
Actually, I'd consider this a new feature, not a regression -- if you
add an engraver multiple times, I'd expect
Graham Percival skrev:
Actually, I'd consider this a new feature, not a regression -- if you
add an engraver multiple times, I'd expect lilypond to draw the feature
multiple times.
Okay.
In this case somebody should go through engraver-init.ly to ensure that
no engravers are added twice anywh
Actually, I'd consider this a new feature, not a regression -- if you
add an engraver multiple times, I'd expect lilypond to draw the feature
multiple times. Doesn't Voice contain an Ottava_spanner_engraver by
default?
Han-Wen?
Cheers,
- Graham
Rune Zedeler wrote:
\version "2.10.25"
\pape
2007/12/6, Graham Percival <[EMAIL PROTECTED]>:
> Could we have a .36 release as soon as
> http://code.google.com/p/lilypond/issues/detail?id=516
> is fixed? This is becoming annoying for LSR <-> doc work.
I'll run a release this weekend.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://
Rune Zedeler skrev:
Can somebody on latest devel reproduce?
Sorry for noise.
I have reported the bug.
-Rune
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Kieren MacMillan skrev:
\version "2.11.33"
\paper{ ragged-right=##t }
drumStuff = \relative
{
\override TextSpanner #'dash-fraction = #1
\override TextSpanner #'bound-details #'left #'text = \markup {
\musicglyph #"scripts.open" \hspace #0.2 } c'4 c c c |
c\startTextSpan c c c
John Mandereau wrote:
Le jeudi 06 décembre 2007 à 14:57 +0100, Valentin Villenave a écrit :
2007/12/6, Graham Percival <[EMAIL PROTECTED]>:
AFAIK, most of the @commonprop aren't translated anyway, so this isn't
really a regression.
??? I don't understand. In the former User Manual, we used to
John Mandereau wrote:
Le mardi 04 décembre 2007 à 00:13 -0800, Graham Percival a écrit :
"since the snippet already has texinfo code, why not have them
automatically inserted directly into the compiled manuals" -- I'd love
to have this. That way everybody would be happy. @commonprop stuff
wo
Valentin Villenave wrote:
As for automatic snippets integration thanks to tags: it would be just
great; however we might think twice about it. For example, there's
currently only one "Pitches" tag, which gathers all snippets closely
(or not) related to the whole NR Chapter #1. As a result, we can
Could we have a .36 release as soon as
http://code.google.com/p/lilypond/issues/detail?id=516
is fixed? This is becoming annoying for LSR <-> doc work.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.o
John Mandereau schrieb:
I've committed a dirty change to make outdated titles appear in the POs.
I hope this is temporary (I expect to change it back when GDP is done).
I've also run po-update in Documentation. With this new hack, you
shouldn't translate all entries, translate only entries in
Trevor Daniels schrieb:
As I said yesterday, I've already added this to the learning manual.
Maybe it needs to go somewhere in the Notation Reference too?
Sorry, thanks for adding to the LM, I meant this additional sentence to
go to the NR, chapter 5.2.1,
which is about spacing and page
2007/12/6, John Mandereau <[EMAIL PROTECTED]>:
> Yes, we did. If we go this way moving many stuff to LSR (which I fully
> agree), we *must* i18n LSR. I volunteer to help with this during my
> Christmas vacation, if Sebastiano accepts to make this big change to
> LSR. I guess this is not trivial
Le lundi 03 décembre 2007 à 21:45 +0200, Till Rettig a écrit :
> Hi John,
> here comes the translation of the de.po for the documentation. Its not
> yet complete but it wouldn't anyways, because there are these entries
> marked with "ToDo".
> There is an issue: In the German docs (and also in t
Le mardi 04 décembre 2007 à 00:13 -0800, Graham Percival a écrit :
> "since the snippet already has texinfo code, why not have them
> automatically inserted directly into the compiled manuals" -- I'd love
> to have this. That way everybody would be happy. @commonprop stuff
> would be maintain
Le jeudi 06 décembre 2007 à 14:57 +0100, Valentin Villenave a écrit :
> 2007/12/6, Graham Percival <[EMAIL PROTECTED]>:
> > AFAIK, most of the @commonprop aren't translated anyway, so this isn't
> > really a regression.
>
> ??? I don't understand. In the former User Manual, we used to
> translate
Han-Wen Nienhuys wrote:
In the absence of notes/rests, lilypond tries to make guesses as to
how large a given column is, by using the column extents as a
fallback. If you then put very large texts into these columns, the
result will be strangely spaced.
If you "all notes equally spaced", eve
2007/12/6, Graham Percival <[EMAIL PROTECTED]>:
> No, I thought of this before you got involved at all.
All I wanted to demonstrate is that you're not as web2.0-reluctant as
you often claim... Plus, you're usually the one who stops me everytime
I go "let's use the LSR to do this all!"
> AFAIK, m
2007/12/6, Reinhold Kainhofer <[EMAIL PROTECTED]>:
> To me it looks very much like a bug. After all, all notes should be equally
> spaced, but that spacing is lost where the skip has a markup attached. There
> is no reason why a markup text below/above should actually have any influence
> on the n
El Thu, 06 de Dec de 2007, a las 09:43:26AM +0100, Reinhold Kainhofer dijo:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am Thursday, 6. December 2007 schrieb Graham Percival:
> > I'm not certain if this is a bug -- I mean, there's nothing obviously
> > wrong here. Still, it's in here:
>
Please see the bug tracker for previous discussion about this.
Cheers,
- Graham
claudio wrote:
Will be made a new version of
Lilypond fornew MacOSX Leopard?
thanks claudio
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.o
Will be made a new version of
Lilypond fornew MacOSX Leopard?
thanks claudio
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Thursday, 6. December 2007 schrieb Graham Percival:
> I'm not certain if this is a bug -- I mean, there's nothing obviously
> wrong here. Still, it's in here:
>
> http://code.google.com/p/lilypond/issues/detail?id=522
To me it looks very much like
23 matches
Mail list logo
