Comment #1 on issue 1718 by k-ohara5...@oco.net: Slur collides with
cross-staff stems
http://code.google.com/p/lilypond/issues/detail?id=1718
This issue could be the same effect as this crossing of a slur over stems :
{ %\once\override Slur #'height-limit = #8
%\once\override Slur #'ratio
Status: Accepted
Owner:
Labels: Type-Defect Priority-High
New issue 1723 by k-ohara5...@oco.net: beam drawn over less than its full
span, some OS only
http://code.google.com/p/lilypond/issues/detail?id=1723
The first beam is intended to extend over rests,
but two users report that it fa
Comment #10 on issue 1701 by k-ohara5...@oco.net: default accidental style
prints too many 'extra' naturals
http://code.google.com/p/lilypond/issues/detail?id=1701
No such plans. It has already been through a countdown,
with no opposition, only a successful search for examples where the old
Comment #9 on issue 1701 by colinpkc...@gmail.com: default accidental style
prints too many 'extra' naturals
http://code.google.com/p/lilypond/issues/detail?id=1701
I'd like to put this on a countdown, Keith. Do you plan any further work,
aqlong the lines of Graham's comment?
__
Comment #5 on issue 1693 by colinpkc...@gmail.com: Attaches bound info to
beam for better normalized-endpoint calculations
http://code.google.com/p/lilypond/issues/detail?id=1693
This has had the 48-hour countdown, so please push and close it.
Thanks,
Colin
Comment #1 on issue 1712 by colinpkc...@gmail.com: Braces redesigned
http://code.google.com/p/lilypond/issues/detail?id=1712
This has had the 48-hour countdown, and should be pushed and closed, please.
cheers,
Colin
___
bug-lilypond mailing list
bug
Status: Accepted
Owner:
Labels: Type-Enhancement Priority-Low
New issue 1722 by brownian.box: Lyrics hyphen's visibility after line break
should be controllable
http://code.google.com/p/lilypond/issues/detail?id=1722
Discussed by Federico Bruni in -user,
http://lists.gnu.org/archive/html
Updates:
Labels: Bounty
Comment #2 on issue 1128 by brownian.box: Text pedal mark not closed at
music end
http://code.google.com/p/lilypond/issues/detail?id=1128
Kieren MacMillan offered C$25 bounty on a fix.
http://lists.gnu.org/archive/html/lilypond-user/2011-06/msg00630.html
On Wed 29 Jun 2011, 23:46 James Lowe wrote:
> Hello,
>
> From: bug-lilypond-bounces+james.lowe=datacore@gnu.org
> [bug-lilypond-bounces+james.lowe=datacore@gnu.org] on behalf of Valentin
> Villenave [valen...@villenave.net]
> Sent: 29 June 2011 23:
Status: Accepted
Owner:
Labels: Type-Documentation Priority-Medium
New issue 1721 by brownian.box: Doc: @snippets links are broken when
translated
http://code.google.com/p/lilypond/issues/detail?id=1721
Reported by Valentin Villenave,
http://lists.gnu.org/archive/html/bug-lilypond/2011-0
Status: New
Owner: mts...@gmail.com
Labels: Type-Collision
New issue 1720 by pkx1...@gmail.com: Incorrect tuplet bracket direction
calculation when tuplets contain rests.
http://code.google.com/p/lilypond/issues/detail?id=1720
\context Voice \relative c'' {
\time 2/4
\times 2/3 { r c,,,
Hello,
From: bug-lilypond-bounces+james.lowe=datacore@gnu.org
[bug-lilypond-bounces+james.lowe=datacore@gnu.org] on behalf of Valentin
Villenave [valen...@villenave.net]
Sent: 29 June 2011 23:45
To: Jean-Charles Malahieude
Cc: Translations list at
On Wed, Jun 29, 2011 at 7:42 PM, Jean-Charles Malahieude
wrote:
> Just because I use
> @rlsrnamed{Keyboards, Claviers}
> to have it labeled in French even if the target wont be translated.
Clever. Then we'd probably need to harmonize this policy through the
docs, since even in French the last lin
Le 28/06/2011 19:05, Valentin Villenave disait :
Greetings everybody,
some translated doc pages have broken @snippet links; for example if
you follow the link at the bottom of
http://lilypond.org/doc/v2.15/Documentation/notation/expressive-marks-as-curves.de.html
you'll see that it points to
htt
Status: Accepted
Owner:
Labels: Type-Other Priority-Medium Frog
New issue 1719 by percival.music.ca: list of places to send release
announcements
http://code.google.com/p/lilypond/issues/detail?id=1719
The old list under "unsorted policies" is out of date. (I wrote a nice
email about
Comment #5 on issue 1216 by reinhold...@gmail.com: DynamicTextSpanners
should end like hairpins
http://code.google.com/p/lilypond/issues/detail?id=1216
This issue is the same as bug #1398 (which has a much simpler test case).
___
bug-lilypond mail
Comment #6 on issue 1214 by reinhold...@gmail.com: Cue notes to music that
creates a sub-voice does not work
http://code.google.com/p/lilypond/issues/detail?id=1214
The problem here is that recording-group-emulate returns the list of
contexts in reverse order, so the last created voice is r
Hello,
I remember a discussion reporting that dynamics ( DynamicText ) inside
a Dynamics context (i.e. attached to spacer rests) are not correctly
aligned (they appear like right-aligned instead of centered).
Unfortunately I can't find this discussion again and I cannot find an
issue about it on
I'm surprised this issue seems not yet reported (at least I did not find
it on the tracker).
The example below is "extreme". I used 16th notes in order to show
clearly the issue. It happens in "real-life" scores with more logical
rhythm also.
Ideally LilyPond should avoid the collision (I do no
%% DynamicTextSpanner inside a Dynamics context are shifted to the left
%% if there is a Pedal inside another Dynamics context.
%% That leads to really poor output of the DynamicTextSpanner, which
%% are shifted left (compared to when they are well aligned without the
%% pedal) and so colliding wit
Thank you Valentin, I will try to do something about that on Sat or Sun, not
before. Sorry, stupid micro Android keyboard here.
El 28/06/2011 19:05, "Valentin Villenave" escribió:
> Greetings everybody,
>
> some translated doc pages have broken @snippet links; for example if
> you follow the link
21 matches
Mail list logo
