On Oct 16, 2009, at 11:21 AM, Hans Hagen wrote:
it's no problem to provide that feature in mkiv, but i need some
real string arguments as well as to be sure that i'll never be
bothered by side effects of fonts not being in a pdf file
The argument to be able to fully include the font is that that's a
requirement for many archiving standards.
It also allows for easier, cleaner assembly of a single document file
from multiple files (all sub-files have compleat fonts, the merged
file can then discard the dupes and if desired, sub-set at that point
and there's only one sub-setted version of each font, 'stead of
multiples as there would be if the fonts were sub-setted in the source
files).
It also makes it possible to trouble-shoot for instances where font
sub-setting may be causing difficulties (make a version w/ the font
fully embedded / not sub-setted and see if that works instead).
The only negatives I've experienced to fully embedding fonts are:
- bloats filesize (not an issue w/ today's equipment and 'net
connections)
- some font licenses don't allow it (so set it up so that this is
determined when the font is installed an such can be dis-allowed where
not supported by the fonts' license)
William
--
William Adams
senior graphic designer
Fry Communications
Sphinx of black quartz, judge my vow.
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
