Issue 247: lyrics attached to Devnull are left-aligned instead of center-aligned
http://code.google.com/p/lilypond/issues/detail?id=247
Comment #5 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you ar
Issue 247: lyrics attached to Devnull are left-aligned instead of center-aligned
http://code.google.com/p/lilypond/issues/detail?id=247
Comment #6 by gpermus:
Mats wrote:
I don't agree that this bug report should just be ignored.
It should certainly be possible to specify the alignment of
lyrics
Issue 247: lyrics attached to Devnull are left-aligned instead of
center-aligned
http://code.google.com/p/lilypond/issues/detail?id=247
Comment #7 by v.villenave:
Perhaps this problem should be handled when taking care of Issue 707
(another
Enhancement request).
--
You received this messa
Updates:
Owner: ---
Labels: -Type-Enhancement -Priority-Low Type-Ugly
Comment #8 on issue 247 by pkx1...@gmail.com: lyrics attached to Devnull
are left-aligned instead of center-aligned
http://code.google.com/p/lilypond/issues/detail?id=247
With 2.15.11 using the above snippet
I don't agree that this bug report should just be ignored.
It should certainly be possible to specify the alignment of
lyrics syllables even if the duration of each syllable is specified
explicitly (i.e. not using \lyricsto) or equivalently
if the durations are copied from a DevNull context.
Wh
That's why I haven't closed 248. 247/248 are dupes, so we only need one
of them.
Cheers,
- Graham
Mats Bengtsson wrote:
I don't agree that this bug report should just be ignored.
It should certainly be possible to specify the alignment of
lyrics syllables even if the duration of each syllable
Graham Percival wrote:
That's why I haven't closed 248. 247/248 are dupes, so we only need
one of them.
Since I saw "Status: invalid" on 248, I assumed that it didn't
count as a feature request. Also, 248 is focussed on a very
specific aspect, the interpretation of ties in DevNull contexts,
w
Mats Bengtsson wrote:
Graham Percival wrote:
That's why I haven't closed 248. 247/248 are dupes, so we only need
one of them.
Since I saw "Status: invalid" on 248, I assumed that it didn't
count as a feature request. Also, 248 is focussed on a very
specific aspect, the interpretation of tie