Times smallcaps -- info [was: Re ... IEEETran]

[Christina Thiele]

Robin Fairbairns writes:
>
> ...
> there's plenty in the manuals, and christina has done it recently, so
> she'll help...
>

Thanks, Robin ;-) I just went through and found the text I'd posted
last November on the subject. Here's my experience.

BUT!!!! This is for an NT machine, and thus installation is via ATM.
I'd very much like to see a variation on these instructions for XP
machines, where, they (and the documentation says it, too!) tell me
;-) , installation is done via the Control Panel. It would be good to
have a step-by-step instruction set on that part as well.

So, here goes.

Ch.

========


    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 ... ;-)