I think this is because these are texts that are attached to multimeasure
rests. The multi measure rest is the Y parent of the text. IIRC, the texts
are implemented as spanners, so their X parent would be the left bound of
the text spanner.
On Tue, Apr 2, 2013 at 10:55 PM, Janek Warchoł
LGTM. I learned something, thanks :)
Janek
https://codereview.appspot.com/8340044/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Like Phil and his wife, I prefer the current version.
This patch makes the octavation symbol too coarse
and heavy. I suspect the old scores which used
punches to engrave the octavation symbol were
not able to reliably reproduce small light italic
characters and had no option but to use a heavy
Reviewers: janek,
Message:
Regarding the description: Acknowledgers should usually just register a
grob (or write grob data) with any actual reading of grob data occurring
at the end of the timestep instead.
Strictly speaking, this principle has been violated already by allowing
subproperty
On Thu, Apr 4, 2013 at 12:30 PM, d...@gnu.org wrote:
Regarding the description: Acknowledgers should usually just register a
grob (or write grob data) with any actual reading of grob data occurring
at the end of the timestep instead.
Strictly speaking, this principle has been violated
It's probably worth noting that by far most uses of octavated clefs are
for the purpose of correctness (similar to transposition in xxx): the
player/singer would not actually execute the piece differently if the
octavation was omitted from the clef.
I can think of one exception: modern-clef
Reviewers: Trevor Daniels, dak,
Message:
Hi,
i suggest to move this discussion to tracker issue. Rietveld is good
for discussing details of the code changes, but it's the tracker issue
that we expect to be kept around longer (and also images can be attached
there).
best,
Janek
Description:
On 2013/04/03 08:31:26, dak wrote:
Perhaps double-check that the % end verbatim occurs only where
expected
in master,
Done.
and then close as fixed, possibly with the version number
where the fix traveled in via makelsr.
Done.
https://codereview.appspot.com/7834043/
Hi Han-Wen,
On Thu, Apr 4, 2013 at 10:48 AM, Han-Wen Nienhuys hanw...@gmail.com wrote:
I think this is because these are texts that are attached to multimeasure
rests. The multi measure rest is the Y parent of the text. IIRC, the texts
are implemented as spanners,
so their X parent would be
hi David,
On Tue, Jan 8, 2013 at 5:10 PM, David Kastrup d...@gnu.org wrote:
Ok, since last year's meeting was sort of a smash hit
URL:http://news.lilynet.net/?The-LilyPond-Report-28 in spite of the
rather late organization of it, I'm trying to start earlier this year.
The proposed date
Hi,
2013/3/14 Joe Neeman joenee...@gmail.com:
On Wed, Mar 13, 2013 at 4:33 PM, Janek Warchoł janek.lilyp...@gmail.com
wrote:
[discussion about aligning grobs on other grobs]
Is there any place with such information? I don't recall seeing
anything like that. It would be useful.
Grep for
https://codereview.appspot.com/8384043/diff/1/Documentation/notation/vocal.itely
File Documentation/notation/vocal.itely (right):
https://codereview.appspot.com/8384043/diff/1/Documentation/notation/vocal.itely#newcode1632
Documentation/notation/vocal.itely:1632: cadence, or a measure or two.
This expresses pretty much what already appears
under Temporary polyphonic passages in Section 1.5.2
of the NR, although using rather more words. It
should not be repeated here. By all means replace
it with a reference to the appropriate part of 1.5.2.
The reason is as usual - the NR is
13 matches
Mail list logo
