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
Am Mittwoch, 28. September 2011, 16:05:51 schrieb Janek Warchoł:
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'?
Basically, yes. The image just shows that the
I'm not sure i understand - are you saying that we should always
align accidentals like in attached 'blah.png'?
Yes, but in this image, the baseline for the sharp is far too high
(this is, the accidental is positioned too low) and both accidentals
are slightly too big.
Werner
Reinhold, Werner,
2011/9/28 Reinhold Kainhofer reinh...@kainhofer.com:
Am Mittwoch, 28. September 2011, 16:05:51 schrieb Janek Warchoł:
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
2011/9/27 Bertrand Bordage bordage.bertr...@gmail.com:
This looks great!
Thanks!
What still needs to be changed in my opinion:
* lower the sharp and the natural so that it fits in the text.
* decrease the size of all accidentals in markups.
I also think they are too big. The question is,
* decrease the size of all accidentals in markups.
I also think they are too big. The question is, how should we
achieve that? Is there something like
musical-glyphs-font-size-when-used-in-markups?
Good question. AFAIK, there isn't such a predefined scaling value
which might be a good
should i change the baseline of the new shorter versions of the
glyphs? It should make easier adding them to other notation
elements. See attached.
Your idea is good. However, I suggest to move down both the sharp and
natural sign a bit so that its horizontally oriented elements are
nearer
For figured bass, the situation is different: Here we use
LilyPond's digit font, which is completely under our control, and
having accidentals fitting those digits better is a good thing.
I will prepare shorter versions of accidentals.
Thanks!
Would you help me with writing code that
On Sep 21, 2011, at 10:05 AM, Werner LEMBERG wrote:
For figured bass, the situation is different: Here we use
LilyPond's digit font, which is completely under our control, and
having accidentals fitting those digits better is a good thing.
I will prepare shorter versions of accidentals.
2011/9/13 Werner LEMBERG w...@gnu.org:
I think the solution is to create a shorter variaton of accidental
glyphs; an example in the attachment. How do you like this idea?
Do you think all accidentals should have shorter versions, or would
it be overkill to create for example a shorter
Hi,
I've noticed that accidental glyphs don't mix well with text: their
baseline is incorrect, and their size doesn't match the letters. Look
at the chordnames resulting from input below: the accidentals are too
big. If they were of correct height, they would become too thin and
generally too
I think the solution is to create a shorter variaton of accidental
glyphs; an example in the attachment. How do you like this idea?
Do you think all accidentals should have shorter versions, or would
it be overkill to create for example a shorter version of 3-stemmed
sharp or arrowed flat?
12 matches
Mail list logo
