On 8 Aug 2009, at 15:41, Valentin Villenave wrote:
Er, I got lost in the discussion. Could you sum up your report
(possibly with a picture)?
The default rule is really that one should have a minimum number of
time signatures if the repeat construct is expanded*). An alternative
way to put
>> Er, I got lost in the discussion. Could you sum up your report
>> (possibly with a picture)?
>
> Meter changes should occur before an opening repeat sign. If there
> is a closing one immediately adjacently, opening and closing one are
> placed apart, and the meter change in between.
I've sent
[I'm sitting in a train, walking over notation.pdf -- I currently
can't look up the bug database. In case this problem is already
reported please ignore this mail.]
The attached image is taken from notation.pdf, subsection `Multiple
notes to one syllable'; the bug IMHO is that the extender line
On Sat, Aug 08, 2009 at 03:45:25PM +0200, Valentin Villenave wrote:
> 2009/8/4 Harmath Dénes :
> > No. It otherwise works perfectly on an Intel Mac. It only fails always with
> > the mentioned characters. (Strangely, similar special characters, like ű or
> > ê, work).
>
> Could you run lilypond --
Valentin Villenave writes:
> 2009/8/8 Werner LEMBERG :
>> Yes. By default, a meter change should be positioned before the
>> repetition sign.
>>
>> This should be added to the bug tracker...
>
> Er, I got lost in the discussion. Could you sum up your report
> (possibly with a picture)?
Meter ch
2009/8/4 Harmath Dénes :
> No. It otherwise works perfectly on an Intel Mac. It only fails always with
> the mentioned characters. (Strangely, similar special characters, like ű or
> ê, work).
Could you run lilypond --verbose on your file? That still looks a lot
like #811; perhaps I'll Fwd it to t
2009/8/8 Werner LEMBERG :
> Yes. By default, a meter change should be positioned before the
> repetition sign.
>
> This should be added to the bug tracker...
Er, I got lost in the discussion. Could you sum up your report
(possibly with a picture)?
Regards,
Valentin
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Low Engraving-nitpick
New issue 827 by v.villenave: Tuplet brackets should be continued after a
line break
http://code.google.com/p/lilypond/issues/detail?id=827
As shown below (LSR #406), the tuplet bracket is not reprinted aft
2009/8/5 Werner LEMBERG :
> (see section 1.2.1), shows IMHO a problem: The tuplet bracket isn't
> continued after the line break to `finish' the tuplet. Looks like a
> bug...
Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=827
Regards,
Valentin
_
2009/7/31 gnomino :
> I think this would be a useful modification of the \fermataMarkup command.
Thanks, applied:
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=f924264773699f778097efc9b5869f530179466a
Regards,
Valentin
___
bug-lilypond
2009/8/8 Werner LEMBERG :
> I suggest to replace this with
> \mark \markup { \char ##x2193 }
OK, done.
Regards,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
The snippet
aligning-marks-with-various-notation-objects.ly
uses U+2193, the `arrow-down' character. Unfortunately, this is not
available as a real glyph in PDF output due to limitations of the
glyph repertoire of the CM fonts used by texinfo. In the PDF, you now
see
\mark ""
instead of
Status: Accepted
Owner: v.villenave
CC: lemzwerg
Labels: Type-Defect Priority-Medium
New issue 826 by v.villenave: Wrong bounding box for \longa glyph
http://code.google.com/p/lilypond/issues/detail?id=826
As demonstrated by the attached skyline, the longa's stem is currently not
taken into acco
2009/8/7 Werner LEMBERG :
>
> This is not a clue, this is clearly a bug.
Not just "a" bug: now the famous #826 bug! :-)
http://code.google.com/p/lilypond/issues/detail?id=826
Regards,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://
14 matches
Mail list logo
