discuss: Publishing process
Subject:
Re: Publishing process
From:
"Bas v.d. Wiel" ####@####.####
Date:
9 Mar 2005 22:25:47 -0000
Message-Id: <422F77D0.5080702@extranet.kompas-media.nl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Martin Wheeler wrote:
|
| Have you any pointers to the most trouble-free fonts to use in the
| first place, to reduce the post-design re-editing to a minimum?
|
| Apart from the current needs of the LDP, I produce a lot of PDFs
| for training manuals -- which always give me grief in the
| processing -- this could be a godsend.
|
| Cheers,
In short: use only ubiquitous fonts, like *shudder* the MS Core Fonts
or some other font that you know comes by default on your target
platform. Even then, fonts are slightly different from platform to
platform. Kerning is handled differently across platforms, hyphenation
is hell. The only real solution is font embedding, which has all kinds
of legal complexities. You have to license the fonts that you use in
your document, but the guy who prints your book also has to license
those fonts just to reproduce your document. In short, it's still hell.
Processing documents constitutes the entire livelihood of a great many
small businesses, that should mean a lot. In the case of the flowchart
that's now circulating on this list it's simple enough to maintain a
proper postscript version. As long as one maintainer keeps the file on
his own machine and does the conversion himself, things will remain
managable. I'd be happy to do this once the dust has settled on the
structure.
Bas
- --
Interesse in een digitale handtekening voor uw e-mail? Neem contact op!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFCL3fQjsOWd4ShSbERAsE3AJ9q3PvYNigAybXpTUDJApLj2AOoQQCeKFKs
26kcXjA16sYcHhywnIQ3Hgc=
=sSkD
-----END PGP SIGNATURE-----
