Issue 694 in lilypond: Enhancement: arrowed heads for microtone accidentals

[codesite-noreply]

Comment #4 on issue 694 by joseph.wakeling: Enhancement: arrowed heads for  
microtone accidentals
http://code.google.com/p/lilypond/issues/detail?id=694

I initiated some discussion of the arrow microtonal notation on the  
lilypond-user
mailing list in April 2009 -- at the time no one mentioned Maximilian's  
patches or
the discussion on the -devel list.

What motivated me was an aspect of arrow quarter-tone notation that isn't  
actually
addressed either by Maximilian's patches or the existing arrow notation in  
2.12: the
extended enharmonic equivalence that arises where, for  
example, 'c-quarter-sharp' can
be notated as either c-natural-with-arrow-up or c-sharp-with-arrow-down.
http://lists.gnu.org/archive/html/lilypond-user/2009-04/msg00139.html

The rough solution I came up with at the time follows a form similar to  
Maximilian's
patches:
http://lists.gnu.org/archive/html/lilypond-user/2009-04/msg00649.html

... but it runs into some key difficulties, notably transposition.  I  
suspect
Maximilian's patches, as they are, will also face these difficulties.

For an example of such a transposition issue, imagine taking E-sharp-up and
transposing it to Bb: you get F-double-sharp-up, which is not only  
ridiculous but
also has no associated glyph.

I wonder if it would be possible to combine Maximilian's approach with mine  
and
resolve both these issues of transposition and enharmonically-equivalent  
arrow notations?

I'm asking in particular because it seems that my approach is of interest  
to people
-- I've recently exchanged a series of emails with a freelance typesetter  
working for
C. F. Peters for whom my solution, with its complete set of arrow  
accidentals, proved
vital.  We have attempted to solve the transposition problem with tags --  
different
notes for the concert and transposed parts -- but it's an ugly, finnicky  
way to
address an issue that needs a more elegant resolution.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings