From: Alexander Sychev <santucco@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] LaTeX: supplementary tips
Date: Tue, 27 Apr 2010 13:45:14 +0400 [thread overview]
Message-ID: <op.vbtepoq9hipq0d@santucco.avp.ru> (raw)
In-Reply-To: <20100427093639.GA12210@polynum.com>
Hello!
Thank you! I can't check TeX on Plan9 right now, but I'm going to do this
in the nearest future...
Can you please add these tips to the corresponding README on kergis.com?
On Tue, 27 Apr 2010 13:36:39 +0400, tlaronde@polynum.com
<tlaronde@polynum.com> wrote:
> Since it seems that LaTeX users are puzzled about how to do, some
> supplementary tips:
>
> 0) You can retrieve from CTAN:
>
> a) The fonts. For TeX proper (what runs indeed when called as
> latex(1)), it needs the TFM files, not the glyphes by themselves.
> But dvi drivers will need afterwards the fonts by themselves. For
> LaTeX, there are the amsfonts (CTAN::fonts/amsfonts/amsfonts.zip)
> and the LaTeX fonts (CTAN::fonts/latex/). You can retrieve only the
> *.mf and then compile the fonts with METAFONT (look at
> kerTeX_T/conf/KERTEX_T.post-install for the way kerTeX compiles the
> Computer Modern asking for the creation of *.tfm). Alternatively,
> the distribution has the TFM already created.
> But, for TeX, you will have to tell him where to look for TFM.
> This is done whether by adjusting the TEXFONTS env variable, or
> under Plan9 by bind'ing supplementary tfm/ subdirectories on
> /lib/kertex/fonts/tfm (by default, TEXFONTS=".:/lib/kertex/fonts/tfm").
>
> b) The base for LaTeX: CTAN::macros/latex/base.zip (there is also
> the doc.zip).
>
> 1) If the *.tfm for fonts LaTeX uses have been created or installed and
> are found in the path (TEXFONTS), the procedure is explained in
> base::manifest.txt.
>
> For all the include files, you need whether to adjust TEXINPUTS, or to
> bind LaTeX base/ on /lib/kertex/tex/mac, or to put yourself in the LaTeX
> base subdirectory (where the files are).
>
> Start by "unpacking" the files:
>
> echo "\input unpack.ins" | kertex/initex
>
> It will tell you at the end that it has created: latex.ltx.
>
> It creates too files with the .cfg suffix: you can configure some
> things there too.
>
> The following step (dumping the format from latex.ltx) is explained in
> the README.
>
> The only caveats is that amsfonts, for example, are "organized"
> (politically correct version of what I have in the mouth) à la TUG
> hierarchy standard. Just adjust the paths, or bind(1) (Plan9 way) etc.
>
> So I will repeat once more:
>
> LaTeX is a set of macros. The procedure has been embedded, hidden,
> submerged under Terabytes of "things" (to be politically correct), but
> there is no magic there; just undue complexity added so that some can
> advertise themselves as "wizzards". This is FUD: there is nothing
> fondamentally difficult, nor any wizzardery in the process.
>
> You can use LaTeX with kerTeX with the supplementary benefit that you
> can be absolutely on top edge: kerTeX is all the latest versions of
> METAFONT/TeX and auxiliary programs, and once you have mastered the
> process, you can update as soon as you want since it is lightweight.
>
> Some LaTeX user could indeed create a rc script file to hget(1) the
> needed files and to launch the process.
>
> There is something that should alert LaTeX users: LaTeX doesn't exist
> without METAFONT/TeX, but you have been kept TeX illiterates. That has
> been one of my motivation to clean the Augean Stables. It's amazing
> how, in this period of general lies, "free" is used to enslave people.
>
--
Best regards,
santucco
next prev parent reply other threads:[~2010-04-27 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 9:36 tlaronde
2010-04-27 9:45 ` Alexander Sychev [this message]
2010-04-27 10:27 ` tlaronde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=op.vbtepoq9hipq0d@santucco.avp.ru \
--to=santucco@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).