Re: upgrading latex (how do i find my previous fonts)



"jfont" <jfont1992@xxxxxxxxx> writes:

>It's time to upgrade our hardware and software (after putting it off
>for some time). Here's our current latex version:
>
>This is TeX, Version 3.1415 (C version 6.1)

that's not latex, that's tex; it would be sort of interesting to know
what latex you're using, but it doesn't much matters.

>Last time I compiled this software was 1999. Due to historical reasons,
>we have to use Latex2e in 2.09 compatibility mode.

i.e., there are limits to what upgrade of software you're willing to
contemplate.

>I won't mind switching to teTeX or a newer LaTeX2e (I'm able to compile
>them from source or use the RedHat rpm)but the "major" problem we
>have is the 'texmf' structure - mktekpk can't find the font.
>
>Most of our documents use fonts which start with "psm". How do I
>"integrate" them to teTeX or LaTeX2e?

apart from doing the obvious thing, viz., just converting them, and
using the psnfss...

>Here's part of our current directory structure under
>/usr/local/lib/texmf (I'm only including the "psm" fonts):
>
>fonts/1075/psmhlvb.pk
>fonts/1290/pshhlvb.pk
>fonts/152/psmhlv.pk
>...
>fonts/psmavgb.tfm
>fonts/psmbkml.tfm
>...
>fonts/psmhlv.180pk
>fonts/psmhlv.240pk

how's about (1) move all those pk files to a directory

$TEXMFLOCAL/fonts/pk/outdated

changing the names so that

fonts/1075/psmhlvb.pk

becomes 1990s format

fonts/pk/outdated/psmhlvb.1075pk

(2) move all the tfm to

fonts/tfm/outdated

(3) finally, create a map file

fonts/map/dvips/outdated/old-adobe.map

and put all the contents of your existing psfonts.map that refers to
these psm fonts into this new map

(4) get the whole lot into your system with

mktexlsr
updmap-sys --enable Map old-adobe.map

>Here is the error message when I process one of our documents:
>
>Document Class: article 2004/02/16 v1.4f Standard LaTeX document class

[omitting the complaints about outdated format]

>(/home/stssjtf/teTeX1/share/texmf-dist/tex/latex/base/size11.clo))kpathsea:
>Running mktextfm psmhlvb
>mktextfm: No such file or directory
>kpathsea: Appending font creation commands to missfont.log.
>
>! Font \psmhlvbxii=psmhlvb at 12.0pt not loadable: Metric (TFM) file
>not found.
><to be read again>
> \relax
>l.2 \newfont{\psmhlvbxii}{psmhlvb at 12pt}

however, if you could bring yourselves to update the documents, you
would get noticeably better results, since you would be taking
advantage of c.15 years' work on metrics for postscript fonts. those
old tfms are usable, but not in any way optimal.

[i wonder what i've forgotten above. i almost forgot the map file...]
--
Robin (http://www.tex.ac.uk/faq) Fairbairns, Cambridge
.



Relevant Pages

  • Re: emergency: Openoffice, Fonts, what a mess
    ... This particular upgrade has had a longer period ... find fonts and you should not have noticed a difference. ... I kept the old packages on the master server, ... Apt will _not_ downgrade OOo automatically, ...
    (Debian-User)
  • System Fonts Have Changed to Symbols
    ... fonts have now been changed to Symbols and Characters ... that I should reinstall Windows. ... First, my copy is an upgrade disc, and when I ... option to Install Windows. ...
    (microsoft.public.windowsxp.general)
  • Re: Emerald fonts - font size?
    ... In learning LaTeX I'm finding its syntax to be almost akin ... I don't understand, therefore, why two fonts should be treated ... I find their use only of a serif Times font and a standard layout - standard ...
    (comp.text.tex)
  • Re: fonts not working in firefox/ icedove
    ... matthew yee-king wrote: ... I recently did an apt-get upgrade on my i386 etch system and now the ... font rendering in icedove and firefox seems to be broken. ... I have switched to nv and now the fonts are fine. ...
    (Debian-User)
  • Re: gnome version
    ... > running Windows and I'm trying to convert them to LateX. ... > which I'm told indicates a bug in the version of gnumeric I'm running, ... > upgrade gnumeric, lest I find myself forced to upgrade a lot of other ... TeX operator, is not recognized as a line terminator in ...
    (comp.os.linux.misc)