From: Stefan Wachter <stefan.wachter@gmx.de>
Subject: Re: How to switch between fonts?
Date: Fri, 18 Mar 2005 16:16:06 +0100 [thread overview]
Message-ID: <423AF0B6.1070002@gmx.de> (raw)
In-Reply-To: <423AE1E7.3060903@wxs.nl>
[-- Attachment #1: Type: text/plain, Size: 1461 bytes --]
> hard to test without those tfm files (i don't want to clobber my system
> by generating them; also, i never use the p* variants)
I created the vf and tfm files with the attached script. Maybe you can
setup a local directory? Creating these fonts simply needs the following
calls (the files are generated in the current directory!):
fonts.sh <path-to-afm-dir> adobe helvetic ec
fonts.sh <path-to-afm-dir> adobe times ec
fonts.sh <path-to-afm-dir> adobe courier ec
fonts.sh <path-to-afm-dir> adobe helvetic texnansi texnansi
fonts.sh <path-to-afm-dir> adobe times texnansi texnansi
fonts.sh <path-to-afm-dir> adobe courier texnansi texnansi
The first three calls generate virtual fonts that are base on raw fonts
with default encoding and the last three calls generate virtual fonts
that are based on texnansi reencoded raw fonts.
(After studying texfont I think that generating fonts based on the
default encoding of raw fonts is not possible with texfont.)
I think the generate vf and tfm files are correct because they can be
used without problems as long as no family switching occurs.
Is there a specific reason why the p* variants should not be used? I
hoped that they are very similar to what is present in the different
Acrobat Reader versions.
>
> looking at your map file:
>
> there are no pfb files mentioned ... why?
I want to use the built in fonts because the size of the PDF documents
must be as small as possible.
--Stefan
[-- Attachment #2: font.sh --]
[-- Type: application/x-sh, Size: 1151 bytes --]
[-- Attachment #3: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
prev parent reply other threads:[~2005-03-18 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 8:33 Stefan Wachter
2005-03-17 20:58 ` Hans Hagen
2005-03-18 13:41 ` Stefan Wachter
2005-03-18 14:12 ` Hans Hagen
2005-03-18 15:16 ` Stefan Wachter [this message]
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=423AF0B6.1070002@gmx.de \
--to=stefan.wachter@gmx.de \
--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).