[Mac OS X TeX] Officina font

[Ross Moore]

> 
> On Freitag, November 2, 2001, at 07:32  Uhr, William Adams wrote:
> 
> > Do you mean ``hell  re''? (with the ``fi'' ligature missing?)
> 
> It is exactly that behaviour ...
> 
> 
> >
> > How'd you install the font?
> 
> I encountered that problem with TeXtures, so I just dropped the font 
> into the fonts folder. Now I am switching to TeXShop and things are more 
> complicated to handle - but more power for you with all those tools.

This kind of "missing ligatures" problem is typical with Textures,
since it uses Adobe Type Manager to render Type 1 fonts, and this uses a
fixed CMAP encoding. On the Mac, the CMAP cannot be altered according
to font-encoding, whereas on other systems I think it can.

However, it is only a screen-rendering problem.
If you print the document, or distill to PDF, then the correct
ligatures should show.  Please test your file to verify this.
 
 
> 
> >
> > Did you build a virtual font using FontInst or some other tool?
> 

It is possible, using Textures 2.1.4  to dump a "Property list" (.PL)
for the font, in a text-readable format. This can be edited easily(!)
to construct new virtual metrics which remap the character positions
so that you get everything showing both onscreen, and printing correctly.
Then use Textures again (or the EdMetrics application) to read the 
edited .PL list, and save in a new metrics suitcase.

However, that's a lot of work to do; so it's not a quick fix.

It's not just ligatures that are affected, by the way.
Have a look at accented uppercase vowels; e.g. \'A  \"U  etc.
Textures (rather, ATM) shows these on-screen in a small sized version,
so that the letter+accent is the height of a normal 'A'; whereas when
printed, the accent is above the A itself, which is full-size.

By creating a new virtual font, you can make a "composite" character
that looks right, both onscreen and when printed or converted to PDF.

The drawback with this technique, which places 2 glyphs into the
PS output rather than just one glyph, is that you cannot search
a PDF file for instances of \"U (Ucirc = U-umlaut) and find these 
composite characters.


> As said, I have only those files and I have nothing done so far. What I 
> need is a cookbook for installing those fonts.

For Textures ? It's quite a lot of work. 

A better approach is to use  fontinst, as suggested already.
This can be programmed to make the "composite characters" versions
of the accented letters.  With fontinst, you probably want to
get the .AFM metrics for the fonts; else create them from the .PL
files, using some TeX/unix utility (I forget which).  
Once you have the revised .PL files, then read them back into
Textures (or EdMetrics) as above.

For Unix (and MacOS X), the same .PL files can be used to construct
the .vf and .tfm files, and a .map file can be built. 

Then of course you'll need a .fd file to use these fonts smoothly in
LaTeX. But that's easily made by copy/edit from existing .fd files.
And don't forget the .sty to set it all up, in a LaTeX job.
(Those are the easy parts.)


> I discovered the distribution tree and found in 
> /usr/local/teTeX/share/texmf/fontname/itc
> 
> i_____    OfficinaSerif-Book                ITC 6069
> i_____    OfficinaSerif-BookItalic          ITC 6070
> i_____    OfficinaSerif-Bold                ITC 6071
> i_____    OfficinaSerif-BoldItalic          ITC 6072
> i_____    OfficinaSerif-Medium              ITC 6097
> i_____    OfficinaSerif-MediumItalic        ITC 6098
> i_____    OfficinaSerif-ExtraBold           ITC 6099
> i_____    OfficinaSerif-ExtraBoldItalic     ITC 6100
> i_____    OfficinaSerif-Black               ITC 6101
> i_____    OfficinaSerif-BlackItalic         ITC 6102
> i_____    OfficinaSans-BlackItalic          ITC 8089
> 
> These are my fonts, but there are no
> 
> 
> \font\itcone = OfficinaSerif-Book at 11pt
> \font\itctwo = OfficinaSerif-Book at 14pt
> 
> But the console states: can not load font: Metric (TFM) file not found
> >
> > What (re)encoding did you set in the pdftex fontmap file?
> >
> Nothing so far ...

You'll need one, to get everything working smoothly in TeX.
With  fontinst  you can make both T1 (modern LaTeX, 8-bit)
and OT1 (old TeX, 7-bit) encoded virtual fonts, that map to
the glyphs in the real fonts on your system.
You can also make "small-caps" and "companion" fonts, for the special
characters that TeX likes to use, but do not reside in the font itself
--- perhaps constructing some characters as composites.

> 
> Thanks for your help,

Best of luck,

	Ross Moore


> 
> Cyrill
> 
> 
> -----------------------------------------------------------------
> To UNSUBSCRIBE, send email to <info at email.esm.psu.edu> with
> "unsubscribe macosx-tex" (no quotes) in the body.
> For additional HELP, send email to <info at email.esm.psu.edu> with
> "help" (no quotes) in the body.
> This list is not moderated, and I am not responsible for
> messages posted by third parties.
> -----------------------------------------------------------------


-----------------------------------------------------------------
To UNSUBSCRIBE, send email to <info at email.esm.psu.edu> with
"unsubscribe macosx-tex" (no quotes) in the body.
For additional HELP, send email to <info at email.esm.psu.edu> with
"help" (no quotes) in the body.
This list is not moderated, and I am not responsible for
messages posted by third parties.
-----------------------------------------------------------------