Font question: New Baskerville for Y&Y
Christina Thiele
cthiele at ccs.carleton.ca
Wed Nov 12 21:49:12 CET 2003
David Ireland writes:
>
> Dear Norbert, Robin and Christina,
>
> Thanks for your responses.
>
> There is a lot of information in the Technical Addendum, but this all seems
> to assume you are using ATM. I'm working on an XP machine and Y&Y and
> apparently that means I shouldn't work with it.
>From what we've seen on this list, ATM is not needed or even wanted
(i.e., turn it off) for INSTALLING fonts. ATM did the rasterising for
Win95/98/NT; rasterising is now automatic in Win2000/XP.
But ATM is not simply a program for installing fonts -- it `manages'
them. Keep 'em out of individual program's hair, as it were. So having
ATM activated again _after_ the fonts have been installed for Y&Y use
is just fine. Again, this is based on comments people have been
posting here for the past while.
So that's ATM.
In the opening pages of the T. Add., the various font file formats
that the OS need for display and printing purposes are explained, as
well as what formats TeX needs.
So the first thing is to get this sorted out and clear -- in a
nutshell, this is as explained on p.5:
PFB and PFM files are required for viewing in DVIWindo, and both
are required for printing from DVIWindo using a Windows Postscript
driver. DVIPSONE [the Y&YTeX driver], on the other hand, requires
only the PFB files.
So now you know: you need PFB and PFM files.
As for TeX itself, it needs data that resides in TFM files -- which
are generated from AFM files. Section 6.7 `Flags and arguments for
AFMtoTFM' has added info -- and I'll bet that if you look in the utils
folder, you'll find the pertinent .txt files with the exact details.
So you need AFM files in order to generate TFM files.
And ALL of these files needs to be in the same encoding. The usual
recommendation in the documentation is texnansi.
> >...
>
> >you derive a set of y&y .tfm files from the .afm files;
> >you get_those_ from the adobe site if you didn't have
> >them in the first place.
>
> They files they provided were
> NBBI____.pfb
> NBB____.pfb
> NBR____.pfb
> NBI____.pfb
> NBBI____ (no file extension shown, but Windows lists as 'Type 1 font file)
> NBB____
> NBR____
> NBI____
>
> Are these last four the .afm files? Can I just rename them as .afm files?
> The rest of the files I have came from
> ftp://sunsite.doc.ic.ac.uk/packages/tex/uk-tex/fonts/psfonts/adobe/baskervi/
> . Maybe I'm missing something obvious?
First, I'd never rename a file on a Windows platform! Next, I'd
suggest waiting another day to see what surfaces.
I can contribute the following. I just went through the process of
getting a Times SC font, purchased from Adobe, to work with Y&YTeX.
I documented my every move -- I can't recall what I do from week to
week, so I need this kind of verbosity hanging around ... occasionally
it even helps others ;-)
I'll append to the end of this message. Note that all references to
ATM are because I'm on an NT machine and so need to install fonts via
it. For you, on XP, you just install via the Control Panel, as per
usual instructions. Just keep in mind that all you're installing are
the .pfb files. The .pfm files are automatically generated.
> >The necessary conversion utilities are all in c:\yandy\utils
>
> I took a look in the folder but am not sure which utilities I need.
>
> I'm surprised this is apparently so difficult and find it hard to believe
> that I'm the first person to come across this.
It's not difficult. But the documentation assumes a familiarity with
not only the different font formats but an awareness of what needs to
be done. I mean, we know that if we're using new macros, we'd better
define them, or load them via \usepackage. Anyone who uses LaTeX knows
that, right?! Well ... the documentation on getting `outside' fonts
into production form is making about as big an assumption as that!
> Anyway, thanks in advance for your help. When a solution is found I'll
> write an idiots' guide for future reference.
Be kinder to yourself -- it will be a `cookbook' ;-))
> Regards
>
> David
>
>
> -----Original Message-----
> From: Techsupport-owner at yandy.com [mailto:Techsupport-owner at yandy.com]On
> Behalf Of Christina Thiele
> Sent: 12 November 2003 23:10
> To: Techsupport at yandy.com
> Subject: Re: Font question: New Baskerville for Y&Y
> ...
=================
Adding Monotype Times SC/OSF to my Y&YTeX installation
------------------------------------------------------
Working Environment:
-------------------
Laptop with NT4, Y&YTeX 2.2(.8), ATM Lite
Procedures:
----------
1. After checking the Monotype website for various Times smallcaps
fonts, I called 1-800-424-8973 and acquired Times SC/OSF. The
material came later that day, via e-mail, including a .doc
instruction file and a .zip file. Payment via credit card.
2. Printed up the .doc file:
NOTE: the screen shot for ATM (last page) is incorrect, showing a
\pfm subfolder, whereas in reality, you see a \Fonts subfolder. Not
only is the name wrong -- but you don't get pfm files separately --
ATM generates them and installs them in the correct location
automatically. So a bit of a visual red herring. I've mentioned it
to them ... but who knows if they'll actually change anything.
3. Using WinZip, I unzipped the .zip file, which then created that
\Fonts subfolder. In my case, I got 4 files (Tibio, Tibsc, Tiio,
Tirsc) in .inf, .pfb, and .afm formats. The Y&YTeX Technical
Addendum describes these and other font file formats on pp.4-5:
PFB and [ATM-generated] PFM files are required for viewing in
DVIWindo, and both are required for printing from DVIPSONE
using a Windows Postscript driver. DVIPSONE, on the other
hand, requires only the PFB files. (p.5)
4. Then I had to stop -- you have to have administrative privileges in
order to install the fonts. Now, most people probably don't set up
their laptops to have individual log-ins and accounts ... but we
do. So I had to puzzle over why things weren't working until I
finally figured this one out and logged in as administrator. Just a
reminder, to those who have hyper-security set-ups ;-) Now back to
installation ...
5. Launch ATM and navigate (via the right-hand window) to the folder
with the new font files.
6. Highlight all the red-a files. Make sure the box `Add without
copying files' is NOT checked off. Click on `Add' and watch them
all get installed. The `Settings' tab in ATM indicates where the
.pfb and .pfm files are being stored.
7. Installation is now complete for the machine. Now to get the .tfm
files that TeX needs.
8. In DVIWindo, go to Fonts > Write TFM, which pops up a `Font'
dialogue box. Even though I'm installing 4 fonts, the `Write All
TFMs...' is not a good choice, as it locates all kinds of other
fonts -- apparently wanting to really go after every single font on
my machine. I got out of that one, and opted for doing `Write TFM'
four times.
9. The dialogue box has 3 panels: Font, Font Style, Size. Highlight
the entry in the `Font' panel, then highlight one of the 4 styles
(regular, italic, bold, bold-italic), ensure that your encoding
(I'm just sticking with default `texnansi') is properly selected,
and click on `OK'. I also just left the `FileName (default)' box as
was (checked off).
10. A new dialogue box, `TIRSC___', pops up, with a white `X' in a red
circle, accompanied by that lovely MS blamming sound ;-). The box
contains all kinds of delightful information about the font just
worked on: Face Name, Font Name, AFM file location, TFM file
location, and the encoding. Hit `OK' and it's done, ready for
use. And, as I said, I then did it three more times.
11. For each font style, I also got the log file window that one
usually gets when processing a TeX file, but this one's called
`ATM to TFM', and shows all the nitty gritty details of the
conversion, including info which may or may not be hugely
important or significant ... or just excesively detailed -- as in
TeX telling you that a line is 3.23947pts too wide ;-)
In any event, my log file had these warnings for all four:
-- above 17 chars appeared more than once
-- saw 253 chars, expected 234 ... (there were 17 repeat
encodings.)
...
-- above 6 chars. in encoding vector, but not in AFM file.
I'm hoping these are benign warnings, and major icebergs just
waiting to float my way at some point in the future ... ;-)
More information about the yandytex
mailing list