Updates:
Status: Started
Owner: carl.d.s...@gmail.com
Comment #1 on issue 2408 by carl.d.s...@gmail.com: Inconsistent automatic
beaming when using multiple tuplets next to each other
http://code.google.com/p/lilypond/issues/detail?id=2408
Have a patch just about ready to go.
2012/3/16 Xavier Scheuer :
> On 16 March 2012 17:44, Francisco Vila wrote:
>>
>> Thank you. I have tried the \hideNotes trick but does not work because
>> a beam is only printed it the initial note is not hidden.
>
> The code I would have used (maybe a bit tricky).
Thank you! You have been credit
Updates:
Labels: -Fixed_2_13_34 Fixed_2_15_34
Comment #10 on issue 2399 by julien.r...@gmail.com: website links to 2.13
docs for 'help us' points to a non-existent page
http://code.google.com/p/lilypond/issues/detail?id=2399
hehe thanks I hard-coded that one in my head
_
Comment #9 on issue 2399 by ma...@gregoriana.sk: website links to 2.13 docs
for 'help us' points to a non-existent page
http://code.google.com/p/lilypond/issues/detail?id=2399
Typo? Fixed_2_13_34
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Comment #10 on issue 2230 by julien.r...@gmail.com: add svg regtests
http://code.google.com/p/lilypond/issues/detail?id=2230
The problem I have is that one small change in coordinates leads to a
full-line diff. Changes to ID could easily get lost. So I need to either
filter or weight the dif
Comment #2 on issue 1004 by julien.r...@gmail.com: more thought needed for
website integration
http://code.google.com/p/lilypond/issues/detail?id=1004
Website integration is not perfect, but we no longer have hard-coded
version strings in lilypond-texi2html.init after the fix to issue 2399
Updates:
Status: Fixed
Owner: julien.r...@gmail.com
Labels: Fixed_2_13_34
Comment #8 on issue 2399 by julien.r...@gmail.com: website links to 2.13
docs for 'help us' points to a non-existent page
http://code.google.com/p/lilypond/issues/detail?id=2399
pushed to staging
Comment #7 on issue 2399 by julien.r...@gmail.com: website links to 2.13
docs for 'help us' points to a non-existent page
http://code.google.com/p/lilypond/issues/detail?id=2399
Issue 2079 has been merged into this issue.
___
bug-lilypond mailing
Updates:
Status: Duplicate
Mergedinto: 2399
Comment #3 on issue 2079 by julien.r...@gmail.com: website links to 2.13
http://code.google.com/p/lilypond/issues/detail?id=2079
that suggestion is issue 2212
___
bug-lilypond mailing list
b
Comment #6 on issue 2399 by gra...@percival-music.ca: website links to 2.13
docs for 'help us' points to a non-existent page
http://code.google.com/p/lilypond/issues/detail?id=2399
substitution is fine. Please push directly to staging.
___
bug-li
Comment #9 on issue 2230 by m...@apollinemike.com: add svg regtests
http://code.google.com/p/lilypond/issues/detail?id=2230
I vote for only textual comparison.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/
Comment #5 on issue 2399 by pkx1...@gmail.com: website links to 2.13 docs
for 'help us' points to a non-existent page
http://code.google.com/p/lilypond/issues/detail?id=2399
Julien,
There was talk in one of the current items open to use 'dev' and 'stable'
instead of explicit numbers and li
Comment #8 on issue 2230 by julien.r...@gmail.com: add svg regtests
http://code.google.com/p/lilypond/issues/detail?id=2230
What exactly is needed from svg regtests? Do we want only textual
comparison of the generated svg files or also png output comparison?
Comment #4 on issue 2399 by julien.r...@gmail.com: website links to 2.13
docs for 'help us' points to a non-existent page
http://code.google.com/p/lilypond/issues/detail?id=2399
lilypond-texi2html.init line 1427:
# TODO: very yucky, but will be fixed in issue 1004
if ($web_manual) {
On 16 March 2012 17:44, Francisco Vila wrote:
>
> Thank you. I have tried the \hideNotes trick but does not work because
> a beam is only printed it the initial note is not hidden.
The code I would have used (maybe a bit tricky).
Snippet
\version "2.15.30"
\new Staff {
\time 2/4
<<
2012/3/16 Xavier Scheuer :
> On 16 March 2012 17:30, Francisco Vila wrote:
>>
>> This is not an upright slur from the lowest note, this is a 'downside' slur
>
> Right, I did not consider this case.
> Nice request, then.
>
>> See attached again. How do you do that?
>
> Right now I would use two voi
On 16 March 2012 17:30, Francisco Vila wrote:
>
> This is not an upright slur from the lowest note, this is a 'downside' slur
Right, I did not consider this case.
Nice request, then.
> See attached again. How do you do that?
Right now I would use two voices. ;-P
But with your "be able to start
2012/3/16 Xavier Scheuer :
> For a slur to start from the lowest note
> _(
This is not an upright slur from the lowest note, this is a 'downside' slur
> What would you expect —as graphical output— for a slur starting on
> a note *in the middle of a chord*? I cannot represent how it would
> look
On 16 March 2012 16:51, Francisco Vila wrote:
>
> Also, I had put my hopes in this variant:
>
> (snip)
>
> %END
>
> But not.
Might be considered as an issue.
But IMHO issue #1316 is by far more confusing for lambda users:
I mean, I replied to dozens of e-mail from users on the French (but
not onl
On Fri, Mar 16, 2012 at 04:47:01PM +0100, Francisco Vila wrote:
> 2012/3/16 Francisco Vila :
> > 2012/3/16 Xavier Scheuer :
> >
> >> Simply moving the "Slur_engraver" from Voice level to Staff level does
> >> what you want, IIUC.
> >
> > Thank you! That's what I needed. I'm going to try the other e
On 16 March 2012 16:47, Francisco Vila wrote:
>
> Well I'd change the title to "be able to start a slur from a specific
> note of a chord". This gives a warning and does not printa a slur. For
> cases like this, maybe still the named slurs have any sense.
>
> \version "2.15.30"
> \new Staff {
> \
2012/3/16 Francisco Vila :
> Well I'd change the title to "be able to start a slur from a specific
> note of a chord". This gives a warning and does not printa a slur. For
> cases like this, maybe still the named slurs have any sense.
>
> \version "2.15.30"
> \new Staff {
> \new Voice \relative f
2012/3/16 Francisco Vila :
> 2012/3/16 Xavier Scheuer :
>
>> Simply moving the "Slur_engraver" from Voice level to Staff level does
>> what you want, IIUC.
>
> Thank you! That's what I needed. I'm going to try the other example.
> If that's so easily doable, please ignore my request.
Well I'd chan
2012/3/16 Xavier Scheuer :
> Simply moving the "Slur_engraver" from Voice level to Staff level does
> what you want, IIUC.
Thank you! That's what I needed. I'm going to try the other example.
If that's so easily doable, please ignore my request.
--
Francisco Vila. Badajoz (Spain)
www.paconet.or
On 16 March 2012 13:51, Francisco Vila wrote:
>
> I attach two. Op25-n3 is more obvious. Its code (w/o slur) would be
> something like
>
> \version "2.15.30"
> \new Staff \relative f {
> <<
>\new Voice { \voiceOne d''16 c8. g16 f8. }
>\new Voice { \voiceTwo f8[ f'] c,[ c'] }
> >>
> }
>
>
2012/3/16 Colin Hall :
>
> On Fri, Mar 16, 2012 at 11:06:50AM +0100, Francisco Vila wrote:
>> Hello,
>> I am typesetting some Chopin music. Music from this period uses slurs
>> between different voices all the time. I'd like to file an enhancement
>> request for this, if possible. Thanks.
>
> Thank
On Fri, Mar 16, 2012 at 11:06:50AM +0100, Francisco Vila wrote:
> Hello,
> I am typesetting some Chopin music. Music from this period uses slurs
> between different voices all the time. I'd like to file an enhancement
> request for this, if possible. Thanks.
Thanks for the suggestion. I think it
Hello,
I am typesetting some Chopin music. Music from this period uses slurs
between different voices all the time. I'd like to file an enhancement
request for this, if possible. Thanks.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
_
Updates:
Labels: -Type-Documentation Type-Critical
Comment #3 on issue 2399 by gra...@percival-music.ca: website links to 2.13
docs for 'help us' points to a non-existent page
http://code.google.com/p/lilypond/issues/detail?id=2399
I match your bet, and raise the stakes by pointing ou
Comment #2 on issue 2399 by d...@gnu.org: website links to 2.13 docs
for 'help us' points to a non-existent page
http://code.google.com/p/lilypond/issues/detail?id=2399
Critical is 'release blocking' (documentation which is what this is) not
release-blocking.
Star wars fans will rejoice
Comment #6 on issue 2400 by d...@gnu.org: Dots no longer aligned between
voices
http://code.google.com/p/lilypond/issues/detail?id=2400
lilyp...@googlecode.com writes:
Comment #3 on issue 2400 by k-ohara5...@oco.net: Dots no longer
aligned between voices
http://code.google.com/p/lilypond/is
Hello,
On 13 March 2012 22:39, Trevor Daniels wrote:
>
> Eluze, you wrote Tuesday, March 13, 2012 10:22 PM
>
>
>> why is the Time_signature_engraver not called Time_engraver - or what
>> rules
>> are used in constructing names?
>
>
> I don't know. These names were first devised almost 10 years
Updates:
Summary: website links to 2.13 docs for 'help us' points to a non-existent
page
Labels: -Type-Critical Type-Documentation
Comment #1 on issue 2399 by pkx1...@gmail.com: website links to 2.13 docs
for 'help us' points to a non-existent page
http://code.google.com/p/lilypond
Updates:
Status: Fixed
Labels: -Patch-push Fixed_2_15_34
Comment #11 on issue 2388 by pkx1...@gmail.com: Doc: using \voiceXXX for
direction and placement
http://code.google.com/p/lilypond/issues/detail?id=2388
committer James Lowe
Fri, 16 Mar 2012 07:22:07 + (07
Status: Accepted
Owner:
Labels: Type-Documentation
New issue 2410 by pkx1...@gmail.com: Doc: Translation NR 5.1.4 - Typo for
engraver in Fr/Ja/Es and De docs
http://code.google.com/p/lilypond/issues/detail?id=2410
http://lilypond.org/doc/v2.14/Documentation/notation/modifying-context-plu
Updates:
Summary: use of Key_signature_engraver in 2.15.33 is incorrect should be
key_engraver
Status: Fixed
Owner: pkx1...@gmail.com
Labels: fixed_2_15_34
Comment #1 on issue 2394 by pkx1...@gmail.com: use of
Key_signature_engraver in 2.15.33 is incorrect should be
36 matches
Mail list logo
