Dana Emery wrote Sunday, December 06, 2009 9:37 PM
Let the choice of font display a glyph in the proper shape.
Provide the
user with a way to display arbitrary glyphs and ligatures for each
encoded
'stop'. This will be useful for bass stops (/a /b /c... //a
//b //c,
///a) and essential for german tab should we go there.
It would be wrong to presume the encoding of the font. The need
for
glyphs beyond what is used in prose makes necessary special fonts
whose
encoding has no standard.
afm-like information in external files keyed by name to their
relevant
font would be my suggestion for that.
I prefer to leave the whole question of fonts until
later, primarily because I know little about them
at present. As Carl suggested, if we permit markups
then any available font can be used (although even
that is not necessary, as simply overriding the font
for TabNoteHead works with just characters entered
anyway, as my initial lash-up using Fronimo fonts
showed.) But markup will permit PostScript or even
images to be substituted, so there is an advantage
in flexibility to be gained by permitting it.
Although if i not j is a general rule
I have generally seen i used in preference to j, but I have seen
both in
the same document albeit this was german tab (same semantic).
Note that
that edition had large pages and lots of staves, it must have been
a
challenge to find enough sorts to set the amount of type on each
page,
several sizes and flavors of each sort were also used
interchangeably
(both tall and short s for example).
You will be able to use either or both.
Trevor
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel