On 11.06.2010, at 23:14, Xavier Scheuer wrote:
2010/6/11 James Bailey :
It seems that titles aren't centered on non-a4 size paper.
Additionally, it appears that this is a regression that broke
between 2.13.11 and 2.13.12.
Hi!
Yes, several people reported a bug when using \center-column for
Comment #8 on issue 1029 by x.scheuer: \thumb should behave like other
fingerings
http://code.google.com/p/lilypond/issues/detail?id=1029
Great!
Thanks Frédéric, thanks everybody.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu
2010/6/11 Xavier Scheuer :
> A workaround that has been given is to use
> \markup \left-align \center-column
> but that doesn't seem to work here since your title is too long
> (same if you use simply your title between quotes)...
Forget the second part, it works!
(I should have had a better loo
2010/6/11 James Bailey :
> It seems that titles aren't centered on non-a4 size paper.
> Additionally, it appears that this is a regression that broke
> between 2.13.11 and 2.13.12.
Hi!
Yes, several people reported a bug when using \center-column for
\header fields (or in combination with \fill-l
It seems that titles aren't centered on non-a4 size paper.
Additionally, it appears that this is a regression that broke between
2.13.11 and 2.13.12.
Consider the following input file:
\version "2.12.3"
\paper { #(set-paper-size "11x17") }
\header { title = \markup \center-column { "How Razor
Comment #19 on issue 617 by v.villenave: X-offset works in a specific way
for RehearsalMarks
http://code.google.com/p/lilypond/issues/detail?id=617
What do people who override X-offset usually want to achieve? Can it be
done in another way?
___
Comment #3 on issue 897 by percival.music.ca: key signatures should be
inherited by all Voices (no matter their accidental style)
http://code.google.com/p/lilypond/issues/detail?id=897
"frog" doesn't mean "obvious". It just means "we believe it to be within
the reach of a serious, interest
Comment #2 on issue 878 by frederic...@m4x.org: Bowing indications need
higher priority than fingerings
http://code.google.com/p/lilypond/issues/detail?id=878
issue fixed, patch attached
Attachments:
0001-fixed-issue-878-bowing-indications-have-now-higher-p.patch 1009
bytes
_
Comment #2 on issue 897 by frederic...@m4x.org: key signatures should be
inherited by all Voices (no matter their accidental style)
http://code.google.com/p/lilypond/issues/detail?id=897
Why is this a frog's task? Is it something obvious?
___
bug-
Comment #18 on issue 617 by pkx1...@hotmail.com: X-offset works in a
specific way for RehearsalMarks
http://code.google.com/p/lilypond/issues/detail?id=617
OK here is the patch for review.
Attachments:
0001-Doc-Issue-617-NR-x-offsets.patch 3.3 KB
__
On Fri, Jun 11, 2010 at 3:27 PM, Xavier Scheuer wrote:
> Could you implement the possibility:
> \override RestCollision #'positioning-done = #merge-rests-on-positioning
> described in http://lsr.dsi.unimi.it/LSR/Item?id=336
> _directly_ into LilyPond?
Patches will be reviewed.
Cheers,
- Graham
Comment #17 on issue 617 by percival.music.ca: X-offset works in a specific
way for RehearsalMarks
http://code.google.com/p/lilypond/issues/detail?id=617
Sure, I have nothing against a @seealso. In general, whenever you think a
@seealso might be useful, just add it; don't bother asking.
2010/6/11 -Eluze :
> in the snippet below, stems of quoted notes are connected:
>
> \version "2.13.23"
> bass = \context Voice = "bass" \relative c''' { g4 g g g g4 g g g }
> sop = \context Voice = "sop" \relative c' { b4 b b b b4 b b b }
> first = \context Voice = "1" \relative c'
Hi!
Could you implement the possibility:
\override RestCollision #'positioning-done = #merge-rests-on-positioning
described in http://lsr.dsi.unimi.it/LSR/Item?id=336
_directly_ into LilyPond?
So we would not have to define merge-rests-on-positioning ourselves,
each time we want to use this fu
Comment #17 on issue 995 by pkx1...@hotmail.com: tuplets at the begin of a
piece cannot begin with a \tempo indication
http://code.google.com/p/lilypond/issues/detail?id=995
Thank you. I just wanted to be clear that the issue was ony one of 'text
formatting' and not something that was 'tec
2010/6/8 Neil Puttock :
> Oops, I'd forgotten how this should be used; it doesn't return a
> useful value (since it uses ly:grob-translate-axis! to perform the
> shift), so should only be used with 'after-line-breaking.
> Unfortunately, 'after-line-breaking is now spoken for, so you'll have
> to o
LGTM,
Carl
On 6/11/10 6:12 AM, "Graham Percival" wrote:
> Hi Bug Squad and others,
>
> I've updated CG 7 Issues with draft 3:
> http://kainhofer.com/~lilypond/Documentation/contributor/issues.html
>
> Note that this URL goes to kainhofer; the official online docs
> won't be updated until 2.
Comment #16 on issue 617 by pkx1...@hotmail.com: X-offset works in a
specific way for RehearsalMarks
http://code.google.com/p/lilypond/issues/detail?id=617
Would an @seealso be appropriate where the original @knownissue was but
pointing to the 'NR 5.5.1 Aligning objects' section?
___
Updates:
Status: Fixed
Labels: fixed_2_13_24
Comment #3 on issue 1109 by percival.music.ca: makelsr.py should strip
right-hand whitespace
http://code.google.com/p/lilypond/issues/detail?id=1109
Thanks, looks good, and produces good results.
__
Comment #15 on issue 617 by percival.music.ca: X-offset works in a specific
way for RehearsalMarks
http://code.google.com/p/lilypond/issues/detail?id=617
Given the confusion surrounding it, this issue is definitely not invalid --
there's a real gap in the documentation.
I'm happy with a p
Updates:
Status: Fixed
Labels: fixed_2_13_24
Comment #16 on issue 995 by percival.music.ca: tuplets at the begin of a
piece cannot begin with a \tempo indication
http://code.google.com/p/lilypond/issues/detail?id=995
*sigh* I was wondering what would happen here.
After comm
Updates:
Status: Verified
Mergedinto: -1104
Comment #2 on issue 1108 by brownian.box: [PATCH]Add independent control of
thickness and offset for underline markup (issue1347041)
http://code.google.com/p/lilypond/issues/detail?id=1108
(No comment was entered for this change.)
Comment #15 on issue 995 by brownian.box: tuplets at the begin of a piece
cannot begin with a \tempo indication
http://code.google.com/p/lilypond/issues/detail?id=995
Why what?-)
Why unreadable? Well, yes, this can be an arguable thing.
Anyway, take a look, please:
-8<
Comment #2 on issue 1109 by frederic...@m4x.org: makelsr.py should strip
right-hand whitespace
http://code.google.com/p/lilypond/issues/detail?id=1109
From a fresh clone, I found that the right script is:
./scripts/auxiliar/makelsr.py
patch attached.
Attachments:
0001-fixed-issue-11
Comment #14 on issue 617 by pkx1...@hotmail.com: X-offset works in a
specific way for RehearsalMarks
http://code.google.com/p/lilypond/issues/detail?id=617
Which is kind of what Graham alluded to April 01 2010
So is this whole issue 'invalid' as Neil P suggested May 04 2008.
One solution, i
Hi Bug Squad and others,
I've updated CG 7 Issues with draft 3:
http://kainhofer.com/~lilypond/Documentation/contributor/issues.html
Note that this URL goes to kainhofer; the official online docs
won't be updated until 2.13.24, and it's too early for that.
Cheers,
- Graham
_
Comment #14 on issue 995 by pkx1...@hotmail.com: tuplets at the begin of a
piece cannot begin with a \tempo indication
http://code.google.com/p/lilypond/issues/detail?id=995
Can you be more specific and say why?
james
___
bug-lilypond mailing li
Comment #1 on issue 1109 by frederic...@m4x.org: makelsr.py should strip
right-hand whitespace
http://code.google.com/p/lilypond/issues/detail?id=1109
Looked in the source tree where is makelsr.py. Found many identical files:
./scripts/auxiliar/makelsr.py
./input/regression/out-test/share/lil
Comment #13 on issue 617 by mats.ben...@s3.kth.se: X-offset works in a
specific way for RehearsalMarks
http://code.google.com/p/lilypond/issues/detail?id=617
Note also that the RehearsalMark is just one of many layout objects where
overriding X-offset causes the same problem. Other common e
29 matches
Mail list logo
