Adrian you're a star! I'll have a crack at it this weekend. :-) Many thanks for all your help. k. On Friday, October 27, 2000 3:28 PM, Adrian Burd [SMTP:adrian@halodule.tamu.edu] wrote:
"Kester" == Kester Clegg
writes: Hi Kester,
Kester> Now I have braved the fontinst documentation, and must say Kester> it looked a tad complicated and it rather put me off, much Kester> in the same manner that the Latex Graphics Companion does, Kester> there's so much in there about fonts where does one start?
LaTeX/TeX and all its accoutrements should really be thought of as a programming language, which goes part way to explaining its complexity. As for fonts, because there is no accepted industry standard (Type-1 differs from TrueType differs from fon files differs from X-windows font files differs from metafont etc) any discussion of fonts is necessarily complicated and invovled. But stick with it and get those hacking instincts going and you'll soon get the hang of it.
Kester> I'm not sure I understand what you say about the CTAN Kester> files - do you mean that mean I could install Adobe type1 Kester> fonts using fontinst with the correct CTAN files and have Kester> it pretty much do all the work for me? (sounds very Kester> unlikely, I must admit!!) Optimistically assuming this is Kester> the case, how does one then sort out the glyphs? What is Kester> the problem with these? (my ignorance of the fontinst Kester> documentation should be very apparent now!)
If you visit a CTAN site you'll find the following directory, tex-archive/fonts/psfonts within which will be sub-directories called things like adobe, xadobe, monotype etc. Within each of these you'll find directories for individual fonts (e.g., under adobe there's agaramon, optima, sabon etc). The x**** directories contain files for expert fontsets from those foundries. Note, the actual fonts are not here, you have to have them already, i.e., you have to provide the *.pfb files. So, let's say you have Sabon. Download the approriate directory from CTAN, then
1) Rename your *.pfb files according to Karl Berry's classification 2) In the directory you downloaded there will be the following directories: tfm, dvi, vf, latex (or something like that). Put the *.tfm files in $LOCALTEXMF/fonts/tfm/adobe/sabon. Put the *.vf files in $LOCALTEXMF/fonts/vf/adobe/sabon. Put the renamed *.pfb files in $LOCALTEXMF/fonts/type1/adobe/sabon. Put the *.fd and *.sty files in $LOCALTEXMF/tex/latex/psnfss/sabon (or something similar). The above assumes that $LOCALTEXMF has been set up to point to something like /usr/local/texmf or /home/kester/texmf (I have two texmf hierarchies, the main one under /usr/share/texmf and a local one under /home/adrian/texmf. This keeps my additions separate, but you have to edit the texmf.cnf file to let it know that Tex has to search those new hierarchies. 3) In the dvips directory will be a file *.map. I put this in the main dvips/config directory (but you can set it to a local one if you wish as well) as sabon.map. Then edit the file updmap and at the top of the file you'll find a place to put in new maps. Then run the script updmap (type ./updmap) and then run texhash. You should then be ready to use the new font.
Hope this helps,
Adrian
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq