Font help
Sanjay Govindjee
s_g at berkeley.edu
Sun Oct 30 21:04:44 CET 2022
Thanks for the suggestions. I will also look in the files and in the
typeset book to see how things match up with the different fonts and
that should give me a decent idea of what each font is supposed to look
like. Most of your suggestions look reasonable from what I have been
able to figure out.
-sanjay
On 10/29/22 2:42 PM, Karl Berry wrote:
> Kumba_symbols.tex:\font\rrmu=mtgu at 10pt
>
> Can't guess, but if you look at the source and output to see what
> characters are typeset in it, and know what "Kumba symbols" are, you
> might be able to.
>
> P04_Zienk.sty:\font\tmb=tib at 15pt
> ptmb8y
> (Times Bold)
>
> P04_Zienk.tex:\font\chapheadfont=TGB2 at 12pt%
> P04_Zienk.tex:%\font\chapfont=TGL at 22pt%
> P04_Zienk.tex:\font\authorfont=TGB at 14pt%
> P04_Zienk.tex:\font\affilfont=TGO at 10pt%
> P04_Zienk.tex:\font\tocfont=TGB at 8pt%
> P04_Zienk.tex:\font\itemheadfont=TGB at 10pt%
>
> As with the Kumba case, If you look at the chapter headings, authors,
> etc., you (or a font identification site) should be able to discern what
> "TGB" is. I can't guess that one, but I bet is something commonly used.
>
> For purposes of getting the doc through TeX, you could just replace them
> with, say, Computer Modern, even though the actual font used is clearly
> something else. (For example: TGB => cmbx10, TGO = cmsl10)
>
> P04_Zienk.tex:\font\zapfont=ZD at 2.75pt%
> pzdr
> (Zapf Dingbats)
>
> P04_Zienk.tex:\font\tabfootfont=HVO at 7.5pt%
> phvro8y
> (Helvetica Oblique)
>
> P04_Zienk.tex:\font\tabentriesfont=HV at 8.5pt%
> phvr8y
> (Helvetica)
>
> P04_Zienk.tex:\font\tabcolheadfont=HVB at 8.5pt%
> phvb8y
> (Helvetica Bold)
>
> P04_Zienk.tex:\font\tabcolheadsupfont=HVO at 5.7pt%
> phvro8y
>
> P04_Zienk.tex:\font\tabcolsubheadfont=HVBO at 8.5pt%
> phvbo8y
> (Helvetica Bold Oblique)
>
> P04_Zienk.tex:\font\titgr=hvmbi at 20pt
> P04_Zienk.tex:\font\higr=hvmbi at 13pt
> Also phvbo8y.
>
> Needless to say, I'm just guessing, and the fonts concerned are
> certainly not 100% identical to what was used in the book, and things
> may break depending on the input encoding(s) used, nor are these
> necessarily the best choices, etc., etc.
>
> But, as I say, for purposes of getting the doc through TeX with some
> rough idea of what's going on, maybe the above will help. --best, karl.
More information about the texhax
mailing list.