On 2009-10-29, Harmath Dénes wrote:
> On 2009.10.29., at 22:12, Patrick McCarty wrote:
> >It *should* have an effect. But if I'm thinking about this correctly,
> >there will still be an off-by-one error in the character/column
> >counts, because my commit only affects the value of the character
>
Comment #1 on issue 732 by v.villenave: Alignment problems when vertically
stacking horizontally centered stencils.
http://code.google.com/p/lilypond/issues/detail?id=732
Issue 882 has been merged into this issue.
--
You received this message because you are listed in the owner
or CC fields
Updates:
Status: Duplicate
Mergedinto: 732
Comment #2 on issue 882 by v.villenave: Markup columns collisions
http://code.google.com/p/lilypond/issues/detail?id=882
Indeed. I did find 732, but it's described in a more complex way and I
didn't make
the connection.
--
You receiv
Updates:
Status: Duplicate
Mergedinto: 850
Comment #2 on issue 876 by v.villenave: Spacing bug: text exceeding page
footer
http://code.google.com/p/lilypond/issues/detail?id=876
Indeed. Sorry for the noise.
--
You received this message because you are listed in the owner
or C
Comment #3 on issue 850 by v.villenave: Vertical spacing: text lines
exceeding page bottom
http://code.google.com/p/lilypond/issues/detail?id=850
Issue 876 has been merged into this issue.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because
On Thu, Oct 29, 2009 at 11:08 PM, Neil Puttock wrote:
> This bug looks like #807, which has a patch pending.
Indeed. But what about #882 then?
Cheers,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/b
Valentin Villenave wrote Thursday, October 29, 2009 10:32 AM
On Sat, Oct 3, 2009 at 12:41 AM, luis jure
wrote:
Hi Luis, sorry for the delay,
% this shows the default beaming and how it should be beamed
r16 c8. c8 c r16 c8. c8[ c] |
I'm not sure what to do. The first half of the measur
2009/10/29 David Kastrup :
> Bug 882 may or may not be related, and may or may not be a bug, but this
> discrepancy in the context of brackets _is_ a bug.
This bug looks like #807, which has a patch pending.
Regards,
Neil
___
bug-lilypond mailing lis
Comment #1 on issue 882 by n.puttock: Markup columns collisions
http://code.google.com/p/lilypond/issues/detail?id=882
Duplicate of #732.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue not
2009/10/29 Valentin Villenave :
> 2009/10/29 Harmath Dénes :
>> No, the two are very different.
>> In http://code.google.com/p/lilypond/issues/detail?id=887, the _filename_
>> part of the URIs is wrong because of non-ASCII _filenames_.
>> In this bug (http://article.gmane.org/gmane.comp.gnu.lilypon
Le 29 oct. 09 à 10:32, Valentin Villenave a écrit :
On Sun, Sep 13, 2009 at 6:30 PM, Nicolas Sceaux > wrote:
%%% in the first page, text spread on the page footer (and beyond)
%%% before breaking to the next one.
Hi Nicolas,
it took me a while, but it's finally been added as
http://code.googl
--- On Thu, 10/29/09, Valentin Villenave wrote:
> From: Valentin Villenave
> Subject: Re: SystemStartBrace doesn't stretch vertically
> To: "Jonathan Wilkes"
> Cc: bug-lilypond@gnu.org
> Date: Thursday, October 29, 2009, 1:07 PM
> On Thu, Oct 29, 2009 at 11:16 AM,
> Valentin Villenave
>
> wr
Valentin Villenave wrote:
While waiting for acknowledgement,
I have come across several online examples of this.
Yes, I suspect these issues have the same underlying cause (though I
opened multiple issues since I'm not sure what that cause might be).
Well, that was my point
Comment #2 on issue 889 by Carl.D.Sorensen: SystemStartBrace's variable
vertical extent should not affect their weight
http://code.google.com/p/lilypond/issues/detail?id=889
Perhaps this could be resolved by changing the way the brace scales with
size in the font sources.
--
You received
Valentin Villenave writes:
> On Sun, Oct 18, 2009 at 2:34 PM, David Kastrup wrote:
>> % \bracket appears to correctly bracket an entire construct, but
>> % calculate its overall dimension just from its last part
>
> Thanks, but the actual bug doesn't even need to involve brackets:
> http://code.
On Thu, Oct 29, 2009 at 11:16 AM, Valentin Villenave
wrote:
> I'm not sure it's the appropriate engraving tradition
> (vertically-stretched braces could look quite awful IMHO). Could you
> find some example in a printed score, and send us the scan?
Oops, I just found your Debussy link. Never mind
Comment #1 on issue 889 by v.villenave: SystemStartBrace's variable
vertical extent should not affect their weight
http://code.google.com/p/lilypond/issues/detail?id=889
I'm not sure if this is a good idea, but it could be interesting to have an
alternative font for braces rather than blindly
2009/10/29 Harmath Dénes :
> No, the two are very different.
> In http://code.google.com/p/lilypond/issues/detail?id=887, the _filename_
> part of the URIs is wrong because of non-ASCII _filenames_.
> In this bug (http://article.gmane.org/gmane.comp.gnu.lilypond.bugs/16097),
> the _column position_
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium Engraving-nitpick
New issue 889 by v.villenave: SystemStartBrace's variable vertical extent
should not affect their weight
http://code.google.com/p/lilypond/issues/detail?id=889
New report from Jonathan Wilkes:
In the fo
Status: Accepted
Owner: v.villenave
Labels: Type-Enhancement Priority-Medium
New issue 888 by v.villenave: Enhancement: ly:stencil-scale
http://code.google.com/p/lilypond/issues/detail?id=888
New request from Robin:
We currently have two basic transformations: ly:stencil-translate and
ly:stenci
2009/10/27 Patrick McCarty :
> Valentin, can you add this to the tracker? The subject of this thread
> is okay for an issue summary.
Does http://code.google.com/p/lilypond/issues/detail?id=887 cover it?
I haven't mentioned the weird position oddity.
Cheers,
Valentin
___
On Wed, Oct 28, 2009 at 12:25 PM, Robin Bannister wrote:
> I feel that these two should be complemented by a third
> transformation along the lines of the postscript operator: x y scale.
Nice idea! Added as http://code.google.com/p/lilypond/issues/detail?id=888
Cheers,
Valentin
___
Comment #1 on issue 887 by harmathdenes: PDF point-and-click URI links with
special chars wrongly encoded depending on the OS
http://code.google.com/p/lilypond/issues/detail?id=887
As it can be seen, the difference between the encoding of directory and
file names
refers only to the OS X beh
2009/10/29 Harmath Dénes :
> I hope this clarifies the problem and helps to debug the source of it.
Well, all I know is that it allows me to add it to the tracker:
http://code.google.com/p/lilypond/issues/detail?id=887
I also have added the generated link on GNU/Linux.
Thanks,
Valentin
___
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium OpSys-Linux OpSys-OSX
New issue 887 by v.villenave: PDF point-and-click URI links with special
chars wrongly encoded depending on the OS
http://code.google.com/p/lilypond/issues/detail?id=887
New report from Dénes:
http:/
On Fri, Oct 23, 2009 at 12:31 PM, Jean-Alexis Montignies
wrote:
> %% the space between the two notes should not be so wide
> %% the problem is reproducible with 2.12 versions
Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=886
As you can see, this only affects high notes.
Re
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium
New issue 886 by v.villenave: ChordNames horizontal extent may affect note
spacing
http://code.google.com/p/lilypond/issues/detail?id=886
From Jean-Alexis Montignies:
In the following example (reproduced with both 2.12 a
On Tue, Oct 6, 2009 at 5:20 PM, Laura Conrad wrote:
> The attached lilypond file, which I would expect to produce baroque
> noteheads (i.e., square notes for the breves) produces whole notes
> with bars around them for breves.
Greetings Laura (sorry for the delay),
Hm. I can't understand exactly
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Low
New issue 885 by v.villenave: Uninstallation issues
http://code.google.com/p/lilypond/issues/detail?id=885
I'm opening this issue to gather all problems we may encounter when
uninstalling LilyPond.
For instance, Patrick has re
On Mon, Oct 5, 2009 at 10:42 PM, Patrick McCarty wrote:
> The `uninstall-lilypond' script in the GNU/Linux installers leaves the
> following dangling symlinks in ~/bin :
Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=885
Cheers,
Valentin
___
Status: Accepted
Owner: v.villenave
CC: nicolas.sceaux, joeneeman
Labels: Type-Defect Priority-Medium
New issue 884 by v.villenave: pageBreak resets page-count property
http://code.google.com/p/lilypond/issues/detail?id=884
From Chris Snyder:
"According to LNR 4.1.2, the page-count setting set
On Wed, Oct 21, 2009 at 6:45 PM, Francisco Vila wrote:
> 4 c'16 c c c % collision
Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=883
I'm not sure it's a bug, though, since the noBreaks and the line-width
are a bit extreme.
Regards,
Valenitn
_
Status: Accepted
Owner: v.villenave
Labels: Type-Collision Priority-Regression
New issue 883 by v.villenave: stems may collide with noteheads in
tightly-spaced music
http://code.google.com/p/lilypond/issues/detail?id=883
In the following example, some notes collide with the chord's stem while
Status: Accepted
Owner: v.villenave
Labels: Type-Collision Priority-Regression
New issue 881 by v.villenave: Arpeggios may collide with laissezVibrer ties
http://code.google.com/p/lilypond/issues/detail?id=881
% From Robin:
% As shown in the attached example, the collision is only reproduced
%
On Sat, Oct 17, 2009 at 3:05 PM, Robin Bannister wrote:
> \laissezVibrer \arpeggio \mark "always"
Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=881
Cheers,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lis
On Wed, Oct 21, 2009 at 2:53 PM, Robin Bannister wrote:
> While waiting for acknowledgement,
> I have come across several online examples of this.
Yes, I suspect these issues have the same underlying cause (though I
opened multiple issues since I'm not sure what that cause might be).
Regards,
Va
On Sun, Oct 18, 2009 at 2:34 PM, David Kastrup wrote:
> % \bracket appears to correctly bracket an entire construct, but
> % calculate its overall dimension just from its last part
Thanks, but the actual bug doesn't even need to involve brackets:
http://code.google.com/p/lilypond/issues/detail?id
Status: Accepted
Owner: v.villenave
Labels: Type-Collision Priority-Regression
New issue 882 by v.villenave: Markup columns collisions
http://code.google.com/p/lilypond/issues/detail?id=882
In the following example, only the very last part (a column followed with a
regular word) doesn't produce
On Sat, Oct 3, 2009 at 12:41 AM, luis jure wrote:
>
>> I'm not top posting.
Hi Luis, sorry for the delay,
> % this shows the default beaming and how it should be beamed
> r16 c8. c8 c r16 c8. c8[ c] |
I'm not sure what to do. The first half of the measure does look ugly
indeed (see attached),
2009/10/1 Harmath Dénes :
> I found out that they are actually encoded in the system's default encoding
> (Cp1250 on Windows, UTF-8 on Unixes) and then escaped with backslash-codes. So
> maybe this is the expected behaviour?
Greetings,
I'm digging through unaddressed reports and I'm not sure what
On Tue, Sep 29, 2009 at 11:19 PM, Robin Bannister wrote:
Greetings,
> When the connectArpeggios mode includes an arpeggio on a single note,
> the resultant span arpeggio may collide with a previous note.
Added (with much delay) as
http://code.google.com/p/lilypond/issues/detail?id=880
Cheers,
Status: Accepted
Owner: v.villenave
Labels: Type-Collision Priority-Medium
New issue 880 by v.villenave: Arpeggios collide with notes when
connectArpeggios is set
http://code.google.com/p/lilypond/issues/detail?id=880
% From Robin Bannister:
% When the connectArpeggios mode includes an arpeg
On Tue, Sep 29, 2009 at 3:35 AM, Jonathan Wilkes wrote:
Greetings Jonathan,
> The brace for a PianoStaff should be stretched vertically for larger staves,
> not simply resized as it currently seems to do.
I'm not sure it's the appropriate engraving tradition
(vertically-stretched braces could l
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium
New issue 879 by v.villenave: RemoveEmptyStaffContext doesn't need to
disable auto-knee-gap
http://code.google.com/p/lilypond/issues/detail?id=879
As of version 2.13.6, RemoveEmptyStaff still unsets auto-knee-gap, which
s
On Wed, Sep 23, 2009 at 9:54 PM, Neil Puttock wrote:
> There's a message in the deleted bug snippet harakiri-autoknee.ly
> which suggests there used to be a problem:
>
> Autoknee-ing triggers hara-kiri too early.
OK, since I can't decide whether to remove it or not, I've just added
it to the trac
Comment #1 on issue 876 by paconet.org: Spacing bug: text exceeding page
footer
http://code.google.com/p/lilypond/issues/detail?id=876
This is a dupe of #850 and was fixed by Joe b51279cfe1a
--
You received this message because you are listed in the owner
or CC fields of this issue, or becau
On Tue, Sep 8, 2009 at 12:26 PM, Valentin Villenave
wrote:
>> thanks, but did this work? I don't see any bug-lilypond ...
>
> Thanks for noticing :-)
And now added as http://code.google.com/p/lilypond/issues/detail?id=878
Since this is easy to fix, it could be a nice task for a Frog.
BTW, I di
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium Engraving-nitpick
New issue 878 by v.villenave: Bowing indications need higher priority than
fingerings
http://code.google.com/p/lilypond/issues/detail?id=878
Please read the discussion on
http://lists.gnu.org/archive/htm
> Under this premise, I think it makes sense to inherit the key signature.
> Now if we have _within_ a voice << { xxx } \\ { yyy } >>, what does this
> mean? Since the purpose of "voice" accidental style is to write stuff
> that several different people read, this corresponds to splitting a
> teno
On Fri, Sep 18, 2009 at 3:21 PM, Reinhold Kainhofer
wrote:
> This looks very weird for a mid-line \clef "soprano^8", since the (smaller)
> clef on the lowest staff line will not even touch the middle staff line, but
> the
> "8" is printed above the top staff line...
Hi Peter, Mats and Reinhold,
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium Engraving-nitpick
New issue 877 by v.villenave: Ottava clefs may not look good
http://code.google.com/p/lilypond/issues/detail?id=877
% Clef-ottavas may be printed too far from the clef: in the "F^8"
% example below, one can
Frédéric Bron writes:
>> Since the \key command still works at the Staff level (both
>> technically in LilyPond and musically, since there's no notation
>> available to specify separate key signatures for separate voices
>> within a stave), I clearly see it as a bug if the Staff key isn't
>> seen
On Sun, Sep 13, 2009 at 7:38 PM, Neil Puttock wrote:
> No, I'm sure you're right here, which means there's a problem with
> disabling the after-line-breaking callback, especially in the case of
> tall Score objects.
Greetings,
I'm not sure how to write a bug report for this: I can't understand
t
On Sun, Sep 13, 2009 at 6:30 PM, Nicolas Sceaux wrote:
> %%% in the first page, text spread on the page footer (and beyond)
> %%% before breaking to the next one.
Hi Nicolas,
it took me a while, but it's finally been added as
http://code.google.com/p/lilypond/issues/detail?id=876
Sorry for the
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium
New issue 876 by v.villenave: Spacing bug: text exceeding page footer
http://code.google.com/p/lilypond/issues/detail?id=876
From Nicolas Sceaux:
%%% in the first page, text spreads on the page footer (and beyond)
%%% befor
On Fri, Aug 28, 2009 at 11:41 PM, Trevor Daniels wrote:
Greetings Trevor and Neil, sorry for bumping this so late:
> The default value for 'full-measure-spacing-width appears to
> be just the default value for the distance property of a Spring
> object, which is 1, so setting 'full-measure-extra
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Low Script
New issue 875 by v.villenave: Generated lilypond-words files are not
complete
http://code.google.com/p/lilypond/issues/detail?id=875
It seems that automatically-generated word files do not include many words
used in L
> Since the \key command still works at the Staff level (both technically in
> LilyPond and musically, since there's no notation available to specify
> separate key signatures for separate voices within a stave), I clearly see
> it as a bug if the Staff key isn't seen by each Voice.
What if, at th
58 matches
Mail list logo
