Werner LEMBERG <[email protected]> writes: > Sorry for the late reply. > >>> > Why not add global text replacements substituting the accidental >>> > markups in place of the Unicode characters? Personally I prefer >>> > to type and read within my code the Unicode accidentals but I'd >>> > always want the output to use Emmentaler. >>> >>> Sure! This sounds like a nice contribution to the LSR, in case you >>> have some time :-) >> >> Here's what I have in my stylesheet: >> >> \paper { >> #(add-text-replacements! >> `(("♭" . ,(markup #:fontsize -1 #:text-flat)) >> ("♮" . ,(markup #:fontsize -1 #:text-natural)) >> ("♯" . ,(markup #:fontsize -1 #:text-sharp)) >> )) >> } >> >> The fontsize adjustment might be out of date. I saw there was some >> discussion around the design of the text accidentals and I haven't >> checked how this looks on the most recent development release. >> >> What do you think about adding this to the default text >> replacements? > > Rather not IMHO. This is something only experts should activate. > While it is rather innocuous in this particular case it might be > extremely frustrating for beginners to find out why LilyPond does > this. But maybe it's only me who thinks that.
I would be extremely annoyed by that replacement since I use the text accidentals as super/subscripts and explicitly so because they run well with letters rather than noteheads. For example, a footnote block to one technical document of mine runs Maximum number of reeds sounding with “*” slider engaged: 8 reeds: D, E♭, E, F, F♯, G, A♭. 10 reeds: A, B♭, B, C, D♭. 18 reeds: e7, f°. 20 reeds: b♭, b♭7, b, bm, b°, c, cm, d♭, d♭m, d, dm, d7, d°, e♭, e♭m, e♭7, e♭°, e, em, e°, fm, f7, f♯7, f♯°, g, gm, g7, g°, a♭, a♭m, a♭7, a♭°. 22 reeds: a, am, a7, a°, b♭m, b♭°, b7, c7, c°, d♭7, d♭°, f, f♯, f♯m. and I was just able to copy&paste it from the document. -- David Kastrup
