Matthias Neeracher wrote:
AFAIK, a .dfont is an archive of several TTFs, and should be possible
to extract the right TTF font from the .dfont directly.
Actually, we're not just dealing with dfonts here. Verdana, for
instance, is a tradtional MacOS font, as far as I can tell. Also, I
think that some font files may have the pfa font already embedded, so
going through the ttf version may entail a loss of quality.
Verdana actually confuses me greatly. It's part of Microsoft Web fonts
program. I just can't work out where they store the TTF/PFA files for
these fonts.
It would not be impossible to embed the fondu code in lilypond, but that
would definitely be more work, and at this stage in the release cycle,
it's probably not a great idea to add a considerably amount of code for
a marginal feature that is mostly needed on one platform.
Perhaps, but I see invoking ff or fondu externally as a potential
support problem. If we ship early, but have to deal with a lot of
questions from confused users, that will waste our time.
That should not be a surprise. The chinese/japanese fonts are shipped
as OTF and TTF, which are already correctly embedded by Lily. No need
for fontforge there.
Well no, at least on 10.4, lilypond tries to typeset that file by
pulling in the AppleMyunjo and Hei dfonts (fontconfig seems to take a
certain perverse pleasure in defaulting to fonts that lilypond has
difficulty embedding). Are you successful typesetting the file on 10.3 ?
I have successfully typeset typography-demo.ly, which uses japanese.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
