From: Matt Gushee <mgushee@havenrock.com>
Subject: Re: Fourier Expert Fonts
Date: Tue, 08 Feb 2005 21:55:15 -0700 [thread overview]
Message-ID: <420997B3.6050109@havenrock.com> (raw)
In-Reply-To: <ba4316d305020817444760f71d@mail.gmail.com>
Randall Skelton wrote:
> Thanks Matt... after reading a few more sites, I was led back to trying:
Well, I probably can't help much (I haven't been working w/ fonts much
recently, either), but here are a couple of thoughts.
> texfont --fontroot=$HOME/Library/texmf --vendor=adobe
> --collection=utopia --makepath --install
>
> This creates a tree in ~/Library/texmf/fonts/*/adobe/utopia where * is
> either afm, tfm, type1, or vf. I also get
> $HOME/Library/texmf/map/pdftex/context/texnansi-adobe-utopia.map which
> I've added to my pdftex.cfg and run texhash.
That's only useful if you are planning to use TeXnANSI encoding. You
might try adding --encoding=ec to your texfont invocation. Then I think
you will get an ec-adobe-utopia.map file.
> Unfortunately, I still
> get CM fonts for the caps and there are no old-style figures?
You mean small caps, I presume? My first guess would be that they're not
properly referenced in the typescript. As for old-style figures, are you
sure Utopia is supposed to have them? If so, do you know which font
contains them?
> Comparing type-enc.tex and the suggestions on Bill McClain's site, the
> typescript definitions are somewhat different and I'm wondering if
> this isn't the source of my problems:
>
> \definefontsynonym [Fourier-Regular] [futr8t] [encoding=ec]
> vs.
> \definefontsynonym [Fourier-Regular] [texnansi-futr8t ]
> [encoding=texnansi]
My experience leads me to think that in general you should reference
fonts with some encoding prefix. That prefixed name has to correspond to
a name defined in a map file in your TeX tree; e.g., if your
texnansi-adobe-utopia.map file defines a name something like
'texnansi-raw-futr8t.map', then in your typescript, 'texnansi-futr8t'
should work. Then again, I suspect 'futr8t' might be the wrong name to
use. Do you have TFM files named 'futr8t.tfm', and so on? Or are they
named 'utopia'? In the latter case, I think the map file should say,
e.g., 'texnansi-raw-utopia', and you should say 'texnansi-utopia' in the
typescript.
If you want to use EC encoding, then I guess you would change every
instance of 'texnansi' above to 'ec'. By the way, is there a particular
reason you don't want to use TeXnANSI?
--
Matt Gushee
Englewood, CO, USA
next prev parent reply other threads:[~2005-02-09 4:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 22:35 Randall Skelton
2005-02-09 0:44 ` Matt Gushee
2005-02-09 1:44 ` Randall Skelton
2005-02-09 4:55 ` Matt Gushee [this message]
2005-02-09 20:37 ` Randall Skelton
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=420997B3.6050109@havenrock.com \
--to=mgushee@havenrock.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).