Werner LEMBERG wrote Tuesday, September 01, 2009 6:44 AM
Hmm. I currently can't imagine a situation where a value 0 is
needed, so I vote to remove the setting of
#'outside-staff-priority for MultiMeasureRestText -- however,
I'm
not sure whether this has any influence to issue #495 (this
Reinhold Kainhofer reinh...@kainhofer.com a écrit :
is it okay to change note-name-lily-string (and octave-lily-string) to
define-public instead, so e.g. debugging statements can print out the human-
readable pitch name?
I guess nobody will object.
LGTM. But a regtest is missing ;-)
http://codereview.appspot.com/110122
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
I can't really judge the internals of the patch. But at least I don't
see any obvious problem.
On the other hand, I would really like this to be included, as that
issue has bitten me quite a few times while preparing ~50 small excerpts
of Dvorak's Cello concerto for a thesis...
2008/12/17 Valentin Villenave v.villen...@gmail.com:
Hi everyone,
Several months ago I posted a (hackish) workaround for #442:
http://lists.gnu.org/archive/html/lilypond-user/2008-12/msg00456.html
%%%
\layout {
\context { \RemoveEmptyStaffContext }
\context {
\name PseudoVoice
It seems sensible to have a distinct, lower, value, but something
like 40 would place it below everything else while retaining some
future flexibility.
OK. Shall I commit this or will you do that?
Werner
___
lilypond-devel mailing list
Hello everyone,
Attached is a patch to extend the NR documentation on Turkish classical
music as defined in the file makam.ly.
This patch adds a section on 'Non-Western note names and accidentals' to
the Pitches section of NR, using makam as an example. It also adds a
section on Turkish
