2011/9/28 Werner LEMBERG <w...@gnu.org>: > >>> In fact, the accidentals shouldn't overshoot the height of a normal text: >>> not higher than 'f' and not lower than 'g'. >> >> Yes, approximately. > > I think the question is rather where to position the glyph's baseline.
Yes, baseline is most important. >>> It would be interesting to see trailing accidentals if combined with >>> digits from a figured bass. Maybe we should have a third, different >>> looking set of accidentals? >> >> Maybe, but i'd prefer to avoid this if possible for the sake of >> simplicity. > > Mhmm, we are using Metafont! Given the many different noteheads, > controlled by a bunch of meta-variables, I don't see a reason to not > do the same for accidentals, if necessary. Admittedly, this isn't an > urgent issue, but it was you who has started this thread :-) ok, you got me here :) >> There are two different ways we would like to align accidentals [...] >> >> The first method (for use with text) should be implemented by moving >> the baseline of the glyphs, i think. > > Yes. > >> For the second method, i see two possibilities: >> - use bounding box (adjusted a bit), i.e. the bottom of bounding box >> becomes baseline (i hope its possible?); see attachment 2, > > No. As soon as other characters are involved, the first method should > be used. I'm not sure i understand - are you saying that we should always align accidentals like in attached 'blah.png'? I.e. chordnames with accidentals should look like 'chords 2.png'? >> - vertically center the accidental on parent grob. > > No. There is a similar problem in TeX, namely to align a complex > inline mathematical formula along the text line around it. The only > solution which really works is to align the baselines. Centering > glyphs gives horrible results; for example, just look at the way how > Wikipedia displays formulae (if converted to little inline gif images) > if you select a different text size for the text. I don't like this solution either. cheers, Janek
<<attachment: chords 2.png>>
<<attachment: blah.png>>
_______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
