Re: Issue 1718 in lilypond: Slur collides with cross-staff stems

2011-06-29 Thread lilypond 


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 = #0.8
  c8( c c c)
}

The workaround, commented lines above, also works for the cross-staff  
example at the start of this bug report.


Attachments:
maybe1718.png  7.7 KB


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Issue 1723 in lilypond: beam drawn over less than its full span, some OS only

2011-06-29 Thread lilypond 

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 fails to extend to the right


\relative c' { r4 r8[ g' a r] r g[ | a] r }

Failures reported on Ubuntu 11 and MacOS X (see thread) various versions  
including 2.12.
On WinXP, versions 2.14-2.15.3 give expected output on WinXP, so I have no  
image showing failure to post.


Workaround, reported in the thread, is to set the Beam 'stemlet-length to a  
value greater than 0.


Users of affected systems, please add a picture, and reduce the example to  
something really tiny if you can.



___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals

2011-06-29 Thread lilypond 


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  
behavior was seen.


I mentioned in an earlier comment that I would wait until around 1 July to  
push, so I was waiting.



___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals

2011-06-29 Thread lilypond 


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?



___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1693 in lilypond: Attaches bound info to beam for better normalized-endpoint calculations

2011-06-29 Thread lilypond 


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


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1712 in lilypond: Braces redesigned

2011-06-29 Thread lilypond 


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-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Issue 1722 in lilypond: Lyrics hyphen's visibility after line break should be controllable

2011-06-29 Thread lilypond 

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/lilypond-user/2011-06/msg00449.html

%---8<
Dear LilyPonders,

by default LilyPond hides the hyphen after a line break.
Is it possible to make it always visible?

There is a regtest file to check this behavior: lyric-hyphen-break.ly.
I'm using it as a test file.

Hyphens are spanners, right?
In the doc I found this hint:

"The visibility of spanners which end on the first note following a line
break is controlled by the after-line-breaking callback
ly:spanner::kill-zero-spanned-time.

For objects such as glissandos and hairpins, the default behaviour is to
hide the spanner after a break; disabling the callback will allow the
left-broken span to be shown. "

Source:
http://lilypond.org/doc/v2.14/Documentation/snippets/expressive-marks#controlling-spanner-visibility-after-a-line-break

I played with \override LyricHyphen #'after-line-breaking (see file
attached), but nothing changed in the output.

Actually, I'm not directly interested in this issue.  I'm just trying to
help Luca (reviewer of Italian documentation), who asked a couple of
times about this and never got a reply:
https://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00330.html
https://lists.gnu.org/archive/html/lilypond-user/2011-04/msg00470.html

Thanks in advance for your help,
Federico
%---8<


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1128 in lilypond: Text pedal mark not closed at music end

2011-06-29 Thread lilypond 

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


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: [translations] Doc: @snippets links are broken when translated

2011-06-29 Thread Dmytro O. Redchuk 
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:45
> To: Jean-Charles Malahieude
> Cc: Translations list at lilynet; Lilypond Bugreports
> Subject: Re: [translations] Doc: @snippets links are broken when translated
> 
> 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 link at the bottom of
> http://lilypond.org/doc/v2.15/Documentation/notation/expressive-marks-as-curves.fr.html
> doesn't use @rlsrnamed
> 
> Is this policy advertised in the CG? I couldn't find it. (I could
> provide a patch but for now it's safer to open a tracker page if it's
> deemed worth one.)
> 
> 
> 
> I struggled to find a coherent documentation policy/instruction for this 
> (although I don't deal with translations).
> 
> I don't think having a tracker open is a bad thing, and I'm happy to help 
> pushing or editing the CG for whomever wants it.
Thank you, all, added as 1721:
http://code.google.com/p/lilypond/issues/detail?id=1721

-- 
  Dmytro O. Redchuk
  Bug Squad

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Issue 1721 in lilypond: Doc: @snippets links are broken when translated

2011-06-29 Thread lilypond 

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-06/msg00587.html

%---8<
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
http://lilypond.org/doc/v2.15/Documentation/snippets/ausdrucksbezeichnungen
which doesn't exist (node names are not supposed to be translated in URLs).

However, this isn't the case in other sections: for example at the bottom of
http://lilypond.org/doc/v2.15/Documentation/notation/piano.fr.html
It points to the right address:
http://lilypond.org/doc/v2.15/Documentation/snippets/keyboards

Cheers,
Valentin.
%---8<

See the thread for some discussion.


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Issue 1720 in lilypond: Incorrect tuplet bracket direction calculation when tuplets contain rests.

2011-06-29 Thread lilypond 

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,,, c''' }
  \times 2/3 { r c c  }
  \times 2/3 { r c r }
  \times 2/3 { r r r }
  \times 2/3 { r c e }
  \times 2/3 { c r e }
  \times 2/3 { r c g }
  \times 2/3 { c r g }
}

\version "2.14.1"

Patch posted at

http://codereview.appspot.com/4668045/

Attachments:
example.png  16.9 KB


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

RE: [translations] Doc: @snippets links are broken when translated

2011-06-29 Thread James Lowe 
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 lilynet; Lilypond Bugreports
Subject: Re: [translations] Doc: @snippets links are broken when translated

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 link at the bottom of
http://lilypond.org/doc/v2.15/Documentation/notation/expressive-marks-as-curves.fr.html
doesn't use @rlsrnamed

Is this policy advertised in the CG? I couldn't find it. (I could
provide a patch but for now it's safer to open a tracker page if it's
deemed worth one.)



I struggled to find a coherent documentation policy/instruction for this 
(although I don't deal with translations).

I don't think having a tracker open is a bad thing, and I'm happy to help 
pushing or editing the CG for whomever wants it.

James
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: [translations] Doc: @snippets links are broken when translated

2011-06-29 Thread Valentin Villenave 
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 link at the bottom of
http://lilypond.org/doc/v2.15/Documentation/notation/expressive-marks-as-curves.fr.html
doesn't use @rlsrnamed

Is this policy advertised in the CG? I couldn't find it. (I could
provide a patch but for now it's safer to open a tracker page if it's
deemed worth one.)

Cheers,
Valentin.

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: [translations] Doc: @snippets links are broken when translated

2011-06-29 Thread Jean-Charles Malahieude 

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
http://lilypond.org/doc/v2.15/Documentation/snippets/ausdrucksbezeichnungen
which doesn't exist (node names are not supposed to be translated in URLs).

However, this isn't the case in other sections: for example at the bottom of
http://lilypond.org/doc/v2.15/Documentation/notation/piano.fr.html
It points to the right address:
http://lilypond.org/doc/v2.15/Documentation/snippets/keyboards



Just because I use
@rlsrnamed{Keyboards, Claviers}

to have it labeled in French even if the target wont be translated.
I often adopt the same behaviour with @rglosnamed instead of @rglos.

Cheers,
Jean-Charles

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Issue 1719 in lilypond: list of places to send release announcements

2011-06-29 Thread lilypond 

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 this problem, but I can't find it now)

http://lilypond.org/doc/v2.15/Documentation/contributor/major-release-checklist

Until we have a new list, I'm not going to make announcements anywhere  
other than lilypond.org and info-lilyp...@gnu.org


If you want to work on this issue:
- where should we send announcements?  I want links to the exact place;  
i.e. don't say "let's announce it at lwn.net", say "dump the announcement  
to lwn.net/projects/announce-release.php"  (fake url)


- if there's any kind of login or signing up to a mailing list before  
posting is allowed, put that in a separate list.  We might make a separate  
lilypond-announce email account for such things (unfortunately IIRC gmail  
officially bans sharing an email account, so it would have to be somewhere  
else)


- usenet, mailing lists, websites, social stuff like  
twitter/facebook/google plus?

  maybe see issue 940 as well.


ETA: 10 hours.
(PS. I'm serious about the priority; this issue is definitely not high  
priority)




___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1216 in lilypond: DynamicTextSpanners should end like hairpins

2011-06-29 Thread lilypond 


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 mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1214 in lilypond: Cue notes to music that creates a sub-voice does not work

2011-06-29 Thread lilypond 


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 returned as the  
first element of the list -- and the first element of the list is used for  
quoting...


I don't think it's easy to determine which voice to quote in this case. We  
only have the list of all contexts created by the expression, so maybe we  
can somehow extract the first Voice rather than implicitly assuming the the  
last created context will be the voice that should be quoted.



___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

DynamicText inside Dynamics context not correctly aligned

2011-06-29 Thread Xavier Scheuer 
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 the tracker either.

Does someone recall this discussion?  I'm actually looking for a
workaround.  \override DynamicText #'X-offset = #0  gives better results
than the default output but now they appear more like left-aligned and
 \override DynamicText #'self-alignment-X = #CENTER  does not change
anything in this case.

Any help would be appreciated.
Thanks in advance!

Cheers,
Xavier

-- 
Xavier Scheuer 

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

DynamicTextSpanner collides with DynamicText

2011-06-29 Thread Xavier Scheuer 
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 not know what would
be the proper way to do that).  At least in the case where there is
a collision, LilyPond should emit a warning!
This issue might be related to issue #1089 .

%% DynamicTextSpanner collides with DynamicText if the notes are close
%% to each other.
%%

\relative c' {
  c4..\p c16\cresc c4..\f c16\cresc
  c1\ff
}

Cheers,
Xavier

-- 
Xavier Scheuer 

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

DynamicTextSpanner inside Dynamics context are shifted due to pedal

2011-06-29 Thread Xavier Scheuer 
%% 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 with the bar line.
%%
%% This is really an issue for every piano score (using the Dynamics
%% context, i.e. centered dynamics and pedal on a horizontal line).
%%

\version "2.15.2"

\score {
  <<
\new PianoStaff <<
  \new Staff = "up" {
\clef treble
\repeat unfold 48 c'4
  }
  \new Dynamics = "dynamics" {
\repeat unfold 2 {
  s1\cresc s1\f s1\dim s1\p
}
  }
  \new Staff = "down" {
\clef bass
\repeat unfold 48 c4
  }
  \new Dynamics= "pedal" {
\repeat unfold 4 {
  % comment the pedal and the DynamicTextSpanner are well
  % aligned in the Dynamics context above!
  s1\sustainOn s1\sustainOff
}
  }
>>
  >>
}


Cheers,
Xavier

-- 
Xavier Scheuer 

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: [translations] Doc: @snippets links are broken when translated

2011-06-29 Thread Francisco Vila 
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 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
>
http://lilypond.org/doc/v2.15/Documentation/snippets/ausdrucksbezeichnungen
> which doesn't exist (node names are not supposed to be translated in
URLs).
>
> However, this isn't the case in other sections: for example at the bottom
of
> http://lilypond.org/doc/v2.15/Documentation/notation/piano.fr.html
> It points to the right address:
> http://lilypond.org/doc/v2.15/Documentation/snippets/keyboards
>
> Cheers,
> Valentin.
>
>
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond