From: William Adams <will.adams@frycomm.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: embed fonts
Date: Fri, 16 Oct 2009 14:59:32 -0400 [thread overview]
Message-ID: <BD106727-4F18-4FD4-BFC1-B27083B44EFE@frycomm.com> (raw)
In-Reply-To: <4AD88F6A.4010400@wxs.nl>
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
___________________________________________________________________________________
next prev parent reply other threads:[~2009-10-16 18:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 12:00 Thomas A. Schmitz
2009-10-16 12:09 ` Hans Hagen
2009-10-16 13:32 ` Thomas A. Schmitz
2009-10-17 10:46 ` Andreas Schneider
2009-10-17 13:26 ` Hans Hagen
2009-10-17 22:48 ` Martin Schröder
2009-10-19 16:10 ` luigi scarso
2009-10-19 17:53 ` Peter Rolf
2009-10-17 22:41 ` Martin Schröder
2009-10-16 12:16 ` luigi scarso
2009-10-16 13:34 ` Thomas A. Schmitz
2009-10-16 15:15 ` luigi scarso
2009-10-16 15:21 ` Hans Hagen
2009-10-16 15:51 ` luigi scarso
2009-10-16 16:28 ` Arthur Reutenauer
2009-10-16 17:10 ` luigi scarso
2009-10-16 17:17 ` Arthur Reutenauer
2009-10-16 17:24 ` luigi scarso
2009-10-16 18:59 ` William Adams [this message]
2009-10-17 8:22 ` R. Bastian
2009-10-17 8:32 ` Taco Hoekwater
2009-10-17 9:05 ` R. Bastian
2009-10-17 10:17 ` Peter Rolf
2009-10-18 8:38 ` R. Bastian
2009-10-18 8:40 ` Taco Hoekwater
2009-10-18 9:05 ` R. Bastian
2009-10-18 8:44 ` luigi scarso
2009-10-18 11:16 ` Hans Hagen
2009-10-18 12:15 ` R. Bastian
2009-10-18 15:06 ` R. Bastian
2009-10-18 15:40 ` Peter Rolf
2009-10-18 17:56 ` Barry Schwartz
2009-10-18 21:33 ` Hans Hagen
2009-10-18 20:06 ` luigi scarso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BD106727-4F18-4FD4-BFC1-B27083B44EFE@frycomm.com \
--to=will.adams@frycomm.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).