🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.next.software
Article #914

Re: TeX disk space inefficiencies. (save ~2 meg)

#914
From: N Tomczak-Jaegermann
Date: Sat, 07 Nov 1992 22:12
52 lines
2725 bytes
fermat@fermat.dartmouth.edu (Michael Glenn) writes:

>After installing amstex and amslatex on my NeXT, I discovered several  
>additional files that were not needed.  Namely duplicate copies of files  
>that could easily be replaced with symbolic links.

>In /usr/lib/tex/formats:

>splain.fmt == slitex.fmt (576k)
>lplain.fmt == latex.fmt  (496k)
>plain.fmt  == tex.fmt    (288k)

>In /usr/bin:

>latex  == tex (184k)
>slitex == tex (184k)
>virtex == tex (184k)

>/usr/bin/tex apparently looks at what command line command was used to  
>execute it to determine which .fmt file is loaded in.

>I've removed latex, slitex, virtex, splain.fmt, lplain.fmt, and plain.fmt,  
>and replaced them with symbolic links, a total savings of 1912k, almost 2  
>meg!

All these 'extra' files were hard links.  You managed to replace
them with symbolic links actually using for this slightly more
disk space then before.

They are there because of way TeX is configured on Unix.  If you
call it as 'latex' it executes 'virtex' with a format file 'latex.fmt'.
Similar deal is with other formats (you may make your own).
A default format is 'plain.fmt'.  Names like 'plain.fmt', 'lplain.fmt'
and so on are needed for compatibility with other installations.

If you search for savings in disk space in your TeX font installation
look rather at bitmap images of fonts in /usr/lib/tex/fonts/pk.
For example, if you have only 400dpi printer you may throw away
from your disk all 300pk fonts and their magnifications.   This will
cut disk usage considerably.  More radical step consist of throwing
away all pk's and generating fonts (NeXT TeX is doing that
automatically) only when they are needed.  After a while you will end
up only with bitmaps for fonts YOU are using.  Since this takes time
you may want to initialize the whole process running through TeX
as an overnight batch job a set of "typical" - for your installation -
texts and continuing from that point.

Other method consist of replacing all bitmap fonts with their PostScript
equivalents from Y&Y.

   Michal Jaegermann
   ntomczak@vega.math.ualberta.ca
Technical Details
Message-ID: <ntomczak.721174349@vega>
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!destroyer!cs.ubc.ca!unixg.ubc.ca!kakwa.ucs.ualberta.ca!vega!ntomczak
References: <1992Nov7.172031.10284@dartvax.dartmouth.edu>

Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.software
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!destroyer!cs.ubc.ca!unixg.ubc.ca!kakwa.ucs.ualberta.ca!vega!ntomczak
From: ntomczak@vega.math.ualberta.ca (N Tomczak-Jaegermann)
Subject: Re: TeX disk space inefficiencies. (save ~2 meg)
Message-ID: <ntomczak.721174349@vega>
Sender: news@kakwa.ucs.ualberta.ca
Nntp-Posting-Host: vega.math.ualberta.ca
Organization: University Of Alberta, Edmonton Canada
References: <1992Nov7.172031.10284@dartvax.dartmouth.edu>
Date: Sat, 7 Nov 1992 22:12:29 GMT
Lines: 52