[yandytex] Lucida fonts with lucimatx in YandY: TeX's OK, preview bombs

[paul]

Murray,

1) Previewer uses .PFM or Print Font Metrics  The previewer knows which font to
use by its facename, in the case of Times-Roman the FontName is Times-Roman.
Windows has an internal translation table that knows tir is assocaited with
Times-Roman. Incidentally, viewing errors are usually caused by a corruption in
this table.  Simply delete the fonts causing the problem and reinstall them.  If
you look under the font families (depending on which version of Windows you are
using) in the windows directory, you will see that they use the FontName
associated with its abbreviated 8+3 dosish name.   IF you are using ATM, then you
may find a file called atmfonts.map.  Iw contains lines such as

Times-Roman=tir.pfb



2) Printer uses .PFB via dvips or another dvips type driver For those using
yandytex you will find a file called standard.sub  It is a tables containing
direct association of the font names with their file names.   The dvips uses a
FontName associated with its abbreviated 8+3 dosish name except the extension is
not associated.  In this system you will find a line such as

 tir      Times-Roman

which indicates to dvipsone to simply replace the callout of Times-Roman with
tir.  For the fun of it replace in your sub file all instances of other fonts,
their filenames that is with say sy (Symbol).   You will find that all of your
characters, after dvipsoneing will come out as symbol.  Note, however, the
dvipreview will not show the Symbol.  All will show correctly there, but when you
print it, the fonts will be all symbol.  Note: keep a copy of your standard.sub
so you can restore the font table.


3) Note: TFMs are not directly assocaited to the filenames.  Depending on the how
they are used, you may have a FD or font definition file that associated a font
encoding with the filenaming.  This is the nittygritty of the NFSS (PSNFSS) that
you are most likely having problems with.  I can barely explain this to myself,
therefore, I am not qualified to answer this section.  There is scads of
information on the NFSS (PSNFSS), note, that YandYTeX cannot use virtual fonts
(.VF).  This may limit the effectiveness of YandYTeX with the PSNFSS.  All I can
say is that the TFM being used by YandTeX is directly related to the font
encoding you are using.  That is why you see different TFMs in the various
folders of the PSNFSS.   Note that in the .FD files you will see lines line

\DeclareFontShape{OT1}[frut}{m}{n}{%
                                                                 <->pfrr7t
}{}

This tells you which font enclding you are using along with the font name. In
this case pfrr7t tells you it is PostScript (ps), Frutiger (fr), Roman (r), 7t
(OT1 endocing)  To add these fonts all that is required is to add the mapping
parameter to the appropriate .MAP file.  That is where the .MAP attached file  I
sent in an earllier Email makes sense.  Pay careful attention to which .MAP file
you are using.   Hence, an example in your .MAP file will be

tir  ptmr8y    %Times-Roman

I hope this answers some of your questions.  A rewminder, the Preview is
independant of the Printer.  The Previewer uses the PFM for viewing, that is
all.  The Printer uses the PFB for printing.   The TFM simply is a dimension
holder table for the particular font character.  It does not contain any drawing
information on the characters of the font.

This information I supplied is a general guideline, it is not meant to be
technical in any way or form.

Cheers,
Paul Mailhot
PreTeX, Inc.



Murray Eisenberg wrote:

> Unfortunately, it is not self-explanatory to me.  My basic question is
> how does the previewer (and print driver) know which pfb file to
> associate with which tmf-name/alias-name pair?
>
> In some cases, the tfm internally has the name of the actual pbf file.
> For example, inside hlcrm.tfm I find the string "LBMR", and there is a
> font file lbmr.psb.  But in other cases this is not the case.  For
> example, inside hlhr8y.tfm I find NO string naming an actual pfb file
> nor, for that matter, giving a longer name for a font.  (The only
> human-readable strings I find in there is: "TeX typewriter and Windows
> ANSI" and then "Y&Y" and then "LucidBri".)
>
> paul wrote:
> > Walter
> >
> > This is a version of the .MAP file.  If you read it ity is self explanatory
> >
> >
> >
> > Walter Schmidt wrote:
> >
> >> Murray Eisenberg schrieb:
> >>> What would get renamed to what under your suggestion?  The newly
> >>> distributed Lucida pfb's and pfm's have the following names:
> >>>
> >>>     lbc.pfm   and lbc.pfb
> >>>     lbd.pfm   etc.
> >>> [...]
> >>>
> >>> But the tfm's have names:
> >>>
> >>> hlcbot8a.tfm
> >>>     hlcbot8c.tfm
> >>>     hlcbot8r.tfm [etc}
> >> In TeX systems such as teTeX and MikTeX, the relation between
> >> TFMs and PFBs is established by a so-called "font map file".
> >> Its entries say, for instance
> >>
> >> hlhr8y LucidaBright "TeXnANSIEncoding ReEncodeFont" <texnansi.enc <lbr.pfb
> >>
> >> which means:
> >>
> >> The TFM with the name "hlhr8y" refers to the font file lbr.pfb,
> >> with the internal /FontName "LucidaBright", and reencoded to
> >> TeXNANSI encoding using the encoding file texnansi.enc
> >>
> >> Another example:
> >>
> >> hlcrim LucidaNewMath-Italic <lbmi.pfb
> >>
> >> Here, the TFM "hlcrim" refers to the font file lbmi.pfb;
> >> the internal /FontName is "LucidaNewMath", and no reencoding
> >> is applied.
> >>
> >> The distribution includes a map lucida.map in the directory
> >> texmf/fonts/map/dvips/lucida.  This files works for teTeX,
> >> MikTeX, etc.
> >>
> >> I don't know how Y&Y-TeX would establish the relation between
> >> TFMs and physical font files.  Is it using a sort of "map file",
> >> too?  If yes, you can perhaps adopt lucida.map or, at least,
> >> take it as a starting point to create a map file for Y&Y-TeX.
> >> And, of course, you would have to remove existing map file entries
> >> that refer to the (non-standard) TFM names of the Lucida fonts
> >> used previously in Y&Y-TeX.
> >>
> >> Note, however, that all TFMs whose names end with "8r" are
> >> irrelevant for Y&Y-TeX, and the related map file entries can
> >> be ignored.  Only the TFMs ending with "8y", plus those for
> >> the math fonts, are useful in Y&Y-TeX.   Also, you need not
> >> install any TFMs whose names end with "8t" or "8c", and which
> >> have to related map file entries, anyway.
> >>
> >> Disclaiamer:  I know alsmost nothing about Y&Y-TeX, and I am
> >> nor running a M$ Win system, so I cannot try out my above
> >> sugestions in practice.  I just hope that I could point _you_
> >> to the right direction.
> >>
> >> HTH
> >> Walter
> >> --
> >> http://tug.org/mailman/listinfo/yandytex
> >>
> >> ------------------------------------------------------------------------
> >>
> >> --
> >> http://tug.org/mailman/listinfo/yandytex
>
> --
> Murray Eisenberg                     murray at math.umass.edu
> Mathematics & Statistics Dept.
> Lederle Graduate Research Tower      phone 413 549-1020 (H)
> University of Massachusetts                413 545-2859 (W)
> 710 North Pleasant Street            fax   413 545-1801
> Amherst, MA 01003-9305