Am 03.05.2014 18:37, schrieb tisimst:
Once "font.scm" is replaced with the updated one, the following should work
in place of the usual way of changing entire document fonts
<http://lilypond.org/doc/v2.18/Documentation/notation/fonts#entire-document-fonts>
So, you are actually saying:
- with a little modification in the Scheme files
- and .otf fonts that match the LilyPond mapping
such as Gonville, your modification, or
any modification one could do with a custom
LilyPond build
- LilyPond could switch fonts?
Does that imply that one could create with reasonable effort a script
that can take a (suitably licensed) font with a different mapping (e.g.
SMuFL) and make that font thus usable with LilyPond, at least as far as
the glyph coverage is compatible?
That would be GREAT!
Urs
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
