From: Hans Hagen <pragma@wxs.nl>
Subject: Re: How to use and not embed the PdfBase14 fonts?
Date: Mon, 31 Jan 2005 16:06:37 +0100 [thread overview]
Message-ID: <41FE497D.9060505@wxs.nl> (raw)
In-Reply-To: <41FE46E2.7050003@gmx.de>
Stefan Wachter wrote:
> I want to generate PDF documents that use the standard PDF fonts
> (Helvetica, Times-Roman, and Courier) and not to embed these fonts. With
> my former installation (TexLive-2003 and a ConText distribution of last
> autumn) this was possible by using the following lines in the praeambel:
>
> \usetypescript[adobekb][texnansi]
> \usetypescript[postscript][texnansi]
> \setupbodyfont[postscript,ss,13pt]
>
> (In addition, I had to configure pdfTeX by "updmap --setoption
> pdftexDownloadBase14 false").
>
> After I upgraded to TexLive-2004 this does no longer work!
>
> I found that the typescript "adobekb" was replaced by "type-akb". Yet,
> the encoding "texnansi" seems no longer to be available (Metafont
> complains that it can not find: texnansi-utmr8a). Changing the encoding
> to "ec" that still is available yields:
texnansi tfm files are not distributed (actually, what gets distributed is some
mix of encodings) so you need to generate them using texfont
> \usetypescript[type-akb][ec]
> \usetypescript[postscript][ec]
> \setupbodyfont[postscript,ss,13pt]
>
> Yet, using these lines in the praeambel results in a document that uses
> the NimbusSanL-Regu font, that clearly has to be embedded.
you can make a private map file, say myfonts.map, and load that one with
\loadmapfile[myfonts.map]
lines with as first char an '=' will replace other map entries, so that way you
can overrule defaults
> Does anyone know how the standard PDF fonts can be used while not being
> embedded?
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2005-01-31 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 14:55 Stefan Wachter
2005-01-31 15:06 ` Hans Hagen [this message]
2005-01-31 18:29 ` Hartmut Henkel
2005-02-01 11:35 ` Stefan Wachter
2005-02-02 14:34 ` Stefan Wachter
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=41FE497D.9060505@wxs.nl \
--to=pragma@wxs.nl \
--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).