From 3b8ae63ca616b0a5d4f056524b53c9b896dee994 Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Sat, 23 May 2009 00:39:11 +0000 Subject: move texlive sources out of texmf-doc git-svn-id: svn://tug.org/texlive/trunk@13415 c570f23f-e606-0410-a88d-b1316a301751 --- .../source/texlive/texlive-common/examples/ex5.tex | 6 - .../source/texlive/texlive-common/examples/ex6.tex | 56 - .../texlive/texlive-common/examples/ex6a.tex | 24 - .../texlive/texlive-common/examples/ex6b.tex | 6 - .../texlive/texlive-common/examples/ex6c.tex | 14 - .../texlive/texlive-common/install-w32-main.png | Bin 50021 -> 0 bytes .../source/texlive/texlive-common/psview.png | Bin 10129 -> 0 bytes .../source/texlive/texlive-common/stdcoll.png | Bin 10661 -> 0 bytes .../source/texlive/texlive-common/tlmgr-config.png | Bin 10167 -> 0 bytes .../source/texlive/texlive-common/tlmgr-gui.png | Bin 11806 -> 0 bytes .../source/texlive/texlive-common/w32client/README | 26 - .../texlive-common/w32client/install-w32client | 177 - .../texlive-common/w32client/install-w32client.bat | 28 - .../texmf-doc/source/texlive/texlive-cz/Makefile | 5 - .../source/texlive/texlive-cz/cs-tex-live.sty | 458 --- .../source/texlive/texlive-cz/csquote.sty | 181 - .../source/texlive/texlive-cz/live4ht.cfg | 47 - .../source/texlive/texlive-cz/texlive-cz.tex | 3030 --------------- .../texmf-doc/source/texlive/texlive-de/Makefile | 3 - .../source/texlive/texlive-de/live4ht.cfg | 47 - .../source/texlive/texlive-de/lmsy10-40.png | Bin 273 -> 0 bytes .../source/texlive/texlive-de/texlive-de.tex | 3091 --------------- .../texmf-doc/source/texlive/texlive-en/Makefile | 69 - Master/texmf-doc/source/texlive/texlive-en/README | 5 - .../source/texlive/texlive-en/archive/bv-live.tex | 84 - .../source/texlive/texlive-en/archive/bvoutln.sty | 193 - .../source/texlive/texlive-en/archive/changemail | 24 - .../source/texlive/texlive-en/archive/l.pl | 44 - .../texlive/texlive-en/archive/live-2003.tex | 3937 ------------------- .../texlive/texlive-en/archive/live-2004.tex | 3854 ------------------- .../texlive/texlive-en/archive/live-2005.tex | 3174 ---------------- .../texlive/texlive-en/archive/live-2007.tex | 3264 ---------------- .../texlive/texlive-en/archive/live-2008.tex | 2951 --------------- .../source/texlive/texlive-en/archive/live-tl7.tex | 3554 ------------------ .../texlive/texlive-en/archive/live4ht.cfg-2004 | 36 - .../source/texlive/texlive-en/archive/mod.pl | 976 ----- .../source/texlive/texlive-en/archive/nocites.tex | 557 --- .../source/texlive/texlive-en/archive/picture.tex | 46 - .../source/texlive/texlive-en/archive/split.pl | 16 - .../source/texlive/texlive-en/archive/status.pl | 31 - .../source/texlive/texlive-en/archive/tex-live.bib | 235 -- .../source/texlive/texlive-en/archive/tex-live.bst | 60 - .../texlive/texlive-en/archive/tex-live.sty-2003 | 378 -- .../texlive/texlive-en/archive/tex-live.sty-2004 | 422 --- .../texlive/texlive-en/archive/tex-live.sty-2005 | 429 --- .../texlive/texlive-en/archive/tex-live.sty-2007 | 429 --- .../texlive/texlive-en/archive/tex-live.sty-2008 | 444 --- .../source/texlive/texlive-en/archive/texlive.pl | 574 --- .../source/texlive/texlive-en/live4ht.cfg | 51 - .../source/texlive/texlive-en/tex-live.css | 44 - .../source/texlive/texlive-en/tex-live.sty | 446 --- .../source/texlive/texlive-en/texlive-en.tex | 2954 --------------- .../texmf-doc/source/texlive/texlive-fr/Makefile | 5 - .../texmf-doc/source/texlive/texlive-fr/live.tex | 3945 -------------------- .../source/texlive/texlive-fr/live4ht.cfg | 47 - .../source/texlive/texlive-fr/tex-live.css | 44 - .../source/texlive/texlive-fr/texlive-fr.tex | 3148 ---------------- .../texmf-doc/source/texlive/texlive-pl/Makefile | 3 - .../source/texlive/texlive-pl/live4ht.cfg | 52 - .../source/texlive/texlive-pl/tex-livep.sty | 446 --- .../source/texlive/texlive-pl/texlive-pl.tex | 3335 ----------------- .../texmf-doc/source/texlive/texlive-ru/Makefile | 3 - .../source/texlive/texlive-ru/live4ht.cfg | 47 - .../source/texlive/texlive-ru/texlive-ru.tex | 2998 --------------- .../source/texlive/texlive-zh-cn/Makefile | 47 - .../source/texlive/texlive-zh-cn/README-live.ZH-CN | 34 - .../source/texlive/texlive-zh-cn/tex-live.sty | 464 --- .../source/texlive/texlive-zh-cn/texlive-zh-cn.tex | 2576 ------------- .../texlive/source/texlive-common/examples/ex5.tex | 6 + .../texlive/source/texlive-common/examples/ex6.tex | 56 + .../source/texlive-common/examples/ex6a.tex | 24 + .../source/texlive-common/examples/ex6b.tex | 6 + .../source/texlive-common/examples/ex6c.tex | 14 + .../source/texlive-common/install-w32-main.png | Bin 0 -> 50021 bytes .../doc/texlive/source/texlive-common/psview.png | Bin 0 -> 10129 bytes .../doc/texlive/source/texlive-common/stdcoll.png | Bin 0 -> 10661 bytes .../texlive/source/texlive-common/tlmgr-config.png | Bin 0 -> 10167 bytes .../texlive/source/texlive-common/tlmgr-gui.png | Bin 0 -> 11806 bytes .../texlive/source/texlive-common/w32client/README | 26 + .../texlive-common/w32client/install-w32client | 177 + .../texlive-common/w32client/install-w32client.bat | 28 + .../texmf/doc/texlive/source/texlive-cz/Makefile | 5 + .../doc/texlive/source/texlive-cz/cs-tex-live.sty | 458 +++ .../doc/texlive/source/texlive-cz/csquote.sty | 181 + .../doc/texlive/source/texlive-cz/live4ht.cfg | 47 + .../doc/texlive/source/texlive-cz/texlive-cz.tex | 3030 +++++++++++++++ .../texmf/doc/texlive/source/texlive-de/Makefile | 3 + .../doc/texlive/source/texlive-de/live4ht.cfg | 47 + .../doc/texlive/source/texlive-de/lmsy10-40.png | Bin 0 -> 273 bytes .../doc/texlive/source/texlive-de/texlive-de.tex | 3091 +++++++++++++++ .../texmf/doc/texlive/source/texlive-en/Makefile | 69 + Master/texmf/doc/texlive/source/texlive-en/README | 5 + .../texlive/source/texlive-en/archive/bv-live.tex | 84 + .../texlive/source/texlive-en/archive/bvoutln.sty | 193 + .../texlive/source/texlive-en/archive/changemail | 24 + .../doc/texlive/source/texlive-en/archive/l.pl | 44 + .../source/texlive-en/archive/live-2003.tex | 3937 +++++++++++++++++++ .../source/texlive-en/archive/live-2004.tex | 3854 +++++++++++++++++++ .../source/texlive-en/archive/live-2005.tex | 3174 ++++++++++++++++ .../source/texlive-en/archive/live-2007.tex | 3264 ++++++++++++++++ .../source/texlive-en/archive/live-2008.tex | 2951 +++++++++++++++ .../texlive/source/texlive-en/archive/live-tl7.tex | 3554 ++++++++++++++++++ .../source/texlive-en/archive/live4ht.cfg-2004 | 36 + .../doc/texlive/source/texlive-en/archive/mod.pl | 976 +++++ .../texlive/source/texlive-en/archive/nocites.tex | 557 +++ .../texlive/source/texlive-en/archive/picture.tex | 46 + .../doc/texlive/source/texlive-en/archive/split.pl | 16 + .../texlive/source/texlive-en/archive/status.pl | 31 + .../texlive/source/texlive-en/archive/tex-live.bib | 235 ++ .../texlive/source/texlive-en/archive/tex-live.bst | 60 + .../source/texlive-en/archive/tex-live.sty-2003 | 378 ++ .../source/texlive-en/archive/tex-live.sty-2004 | 422 +++ .../source/texlive-en/archive/tex-live.sty-2005 | 429 +++ .../source/texlive-en/archive/tex-live.sty-2007 | 429 +++ .../source/texlive-en/archive/tex-live.sty-2008 | 444 +++ .../texlive/source/texlive-en/archive/texlive.pl | 574 +++ .../doc/texlive/source/texlive-en/live4ht.cfg | 51 + .../doc/texlive/source/texlive-en/tex-live.css | 44 + .../doc/texlive/source/texlive-en/tex-live.sty | 446 +++ .../doc/texlive/source/texlive-en/texlive-en.tex | 2954 +++++++++++++++ .../texmf/doc/texlive/source/texlive-fr/Makefile | 5 + .../texmf/doc/texlive/source/texlive-fr/live.tex | 3945 ++++++++++++++++++++ .../doc/texlive/source/texlive-fr/live4ht.cfg | 47 + .../doc/texlive/source/texlive-fr/tex-live.css | 44 + .../doc/texlive/source/texlive-fr/texlive-fr.tex | 3148 ++++++++++++++++ .../texmf/doc/texlive/source/texlive-pl/Makefile | 3 + .../doc/texlive/source/texlive-pl/live4ht.cfg | 52 + .../doc/texlive/source/texlive-pl/tex-livep.sty | 446 +++ .../doc/texlive/source/texlive-pl/texlive-pl.tex | 3335 +++++++++++++++++ .../texmf/doc/texlive/source/texlive-ru/Makefile | 3 + .../doc/texlive/source/texlive-ru/live4ht.cfg | 47 + .../doc/texlive/source/texlive-ru/texlive-ru.tex | 2998 +++++++++++++++ .../doc/texlive/source/texlive-zh-cn/Makefile | 47 + .../texlive/source/texlive-zh-cn/README-live.ZH-CN | 34 + .../doc/texlive/source/texlive-zh-cn/tex-live.sty | 464 +++ .../texlive/source/texlive-zh-cn/texlive-zh-cn.tex | 2576 +++++++++++++ Master/tlpkg/tlpsrc/texlive-common.tlpsrc | 2 - 137 files changed, 53674 insertions(+), 53676 deletions(-) delete mode 100644 Master/texmf-doc/source/texlive/texlive-common/examples/ex5.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-common/examples/ex6.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-common/examples/ex6a.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-common/examples/ex6b.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-common/examples/ex6c.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-common/install-w32-main.png delete mode 100644 Master/texmf-doc/source/texlive/texlive-common/psview.png delete mode 100644 Master/texmf-doc/source/texlive/texlive-common/stdcoll.png delete mode 100644 Master/texmf-doc/source/texlive/texlive-common/tlmgr-config.png delete mode 100644 Master/texmf-doc/source/texlive/texlive-common/tlmgr-gui.png delete mode 100644 Master/texmf-doc/source/texlive/texlive-common/w32client/README delete mode 100755 Master/texmf-doc/source/texlive/texlive-common/w32client/install-w32client delete mode 100755 Master/texmf-doc/source/texlive/texlive-common/w32client/install-w32client.bat delete mode 100644 Master/texmf-doc/source/texlive/texlive-cz/Makefile delete mode 100644 Master/texmf-doc/source/texlive/texlive-cz/cs-tex-live.sty delete mode 100644 Master/texmf-doc/source/texlive/texlive-cz/csquote.sty delete mode 100644 Master/texmf-doc/source/texlive/texlive-cz/live4ht.cfg delete mode 100644 Master/texmf-doc/source/texlive/texlive-cz/texlive-cz.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-de/Makefile delete mode 100644 Master/texmf-doc/source/texlive/texlive-de/live4ht.cfg delete mode 100644 Master/texmf-doc/source/texlive/texlive-de/lmsy10-40.png delete mode 100644 Master/texmf-doc/source/texlive/texlive-de/texlive-de.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/Makefile delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/README delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/bv-live.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/bvoutln.sty delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/changemail delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/l.pl delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/live-2003.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/live-2004.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/live-2005.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/live-2007.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/live-2008.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/live-tl7.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/live4ht.cfg-2004 delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/mod.pl delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/nocites.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/picture.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/split.pl delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/status.pl delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.bib delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.bst delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.sty-2003 delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.sty-2004 delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.sty-2005 delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.sty-2007 delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.sty-2008 delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/archive/texlive.pl delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/live4ht.cfg delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/tex-live.css delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/tex-live.sty delete mode 100644 Master/texmf-doc/source/texlive/texlive-en/texlive-en.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-fr/Makefile delete mode 100644 Master/texmf-doc/source/texlive/texlive-fr/live.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-fr/live4ht.cfg delete mode 100644 Master/texmf-doc/source/texlive/texlive-fr/tex-live.css delete mode 100644 Master/texmf-doc/source/texlive/texlive-fr/texlive-fr.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-pl/Makefile delete mode 100644 Master/texmf-doc/source/texlive/texlive-pl/live4ht.cfg delete mode 100644 Master/texmf-doc/source/texlive/texlive-pl/tex-livep.sty delete mode 100644 Master/texmf-doc/source/texlive/texlive-pl/texlive-pl.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-ru/Makefile delete mode 100644 Master/texmf-doc/source/texlive/texlive-ru/live4ht.cfg delete mode 100644 Master/texmf-doc/source/texlive/texlive-ru/texlive-ru.tex delete mode 100644 Master/texmf-doc/source/texlive/texlive-zh-cn/Makefile delete mode 100644 Master/texmf-doc/source/texlive/texlive-zh-cn/README-live.ZH-CN delete mode 100644 Master/texmf-doc/source/texlive/texlive-zh-cn/tex-live.sty delete mode 100644 Master/texmf-doc/source/texlive/texlive-zh-cn/texlive-zh-cn.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-common/examples/ex5.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-common/examples/ex6.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-common/examples/ex6a.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-common/examples/ex6b.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-common/examples/ex6c.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-common/install-w32-main.png create mode 100644 Master/texmf/doc/texlive/source/texlive-common/psview.png create mode 100644 Master/texmf/doc/texlive/source/texlive-common/stdcoll.png create mode 100644 Master/texmf/doc/texlive/source/texlive-common/tlmgr-config.png create mode 100644 Master/texmf/doc/texlive/source/texlive-common/tlmgr-gui.png create mode 100644 Master/texmf/doc/texlive/source/texlive-common/w32client/README create mode 100755 Master/texmf/doc/texlive/source/texlive-common/w32client/install-w32client create mode 100755 Master/texmf/doc/texlive/source/texlive-common/w32client/install-w32client.bat create mode 100644 Master/texmf/doc/texlive/source/texlive-cz/Makefile create mode 100644 Master/texmf/doc/texlive/source/texlive-cz/cs-tex-live.sty create mode 100644 Master/texmf/doc/texlive/source/texlive-cz/csquote.sty create mode 100644 Master/texmf/doc/texlive/source/texlive-cz/live4ht.cfg create mode 100644 Master/texmf/doc/texlive/source/texlive-cz/texlive-cz.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-de/Makefile create mode 100644 Master/texmf/doc/texlive/source/texlive-de/live4ht.cfg create mode 100644 Master/texmf/doc/texlive/source/texlive-de/lmsy10-40.png create mode 100644 Master/texmf/doc/texlive/source/texlive-de/texlive-de.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-en/Makefile create mode 100644 Master/texmf/doc/texlive/source/texlive-en/README create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/bv-live.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/bvoutln.sty create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/changemail create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/l.pl create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/live-2003.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/live-2004.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/live-2005.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/live-2007.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/live-2008.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/live-tl7.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/live4ht.cfg-2004 create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/mod.pl create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/nocites.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/picture.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/split.pl create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/status.pl create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.bib create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.bst create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.sty-2003 create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.sty-2004 create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.sty-2005 create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.sty-2007 create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.sty-2008 create mode 100644 Master/texmf/doc/texlive/source/texlive-en/archive/texlive.pl create mode 100644 Master/texmf/doc/texlive/source/texlive-en/live4ht.cfg create mode 100644 Master/texmf/doc/texlive/source/texlive-en/tex-live.css create mode 100644 Master/texmf/doc/texlive/source/texlive-en/tex-live.sty create mode 100644 Master/texmf/doc/texlive/source/texlive-en/texlive-en.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-fr/Makefile create mode 100644 Master/texmf/doc/texlive/source/texlive-fr/live.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-fr/live4ht.cfg create mode 100644 Master/texmf/doc/texlive/source/texlive-fr/tex-live.css create mode 100644 Master/texmf/doc/texlive/source/texlive-fr/texlive-fr.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-pl/Makefile create mode 100644 Master/texmf/doc/texlive/source/texlive-pl/live4ht.cfg create mode 100644 Master/texmf/doc/texlive/source/texlive-pl/tex-livep.sty create mode 100644 Master/texmf/doc/texlive/source/texlive-pl/texlive-pl.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-ru/Makefile create mode 100644 Master/texmf/doc/texlive/source/texlive-ru/live4ht.cfg create mode 100644 Master/texmf/doc/texlive/source/texlive-ru/texlive-ru.tex create mode 100644 Master/texmf/doc/texlive/source/texlive-zh-cn/Makefile create mode 100644 Master/texmf/doc/texlive/source/texlive-zh-cn/README-live.ZH-CN create mode 100644 Master/texmf/doc/texlive/source/texlive-zh-cn/tex-live.sty create mode 100644 Master/texmf/doc/texlive/source/texlive-zh-cn/texlive-zh-cn.tex (limited to 'Master') diff --git a/Master/texmf-doc/source/texlive/texlive-common/examples/ex5.tex b/Master/texmf-doc/source/texlive/texlive-common/examples/ex5.tex deleted file mode 100644 index 51a49fb670e..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-common/examples/ex5.tex +++ /dev/null @@ -1,6 +0,0 @@ -TEXMF = {$TEXMFLOCAL,!!$TEXMFMAIN} -TEXINPUTS.latex = .;$TEXMF/tex/{latex,generic;}// -TEXINPUTS.fontinst = .;$TEXMF/tex//;$TEXMF/fonts/afm// -% e-TeX related files -TEXINPUTS.elatex = .;$TEXMF/{etex,tex}/{latex,generic;}// -TEXINPUTS.etex = .;$TEXMF/{etex,tex}/{eplain,plain,generic;}// diff --git a/Master/texmf-doc/source/texlive/texlive-common/examples/ex6.tex b/Master/texmf-doc/source/texlive/texlive-common/examples/ex6.tex deleted file mode 100644 index 7a56896e61c..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-common/examples/ex6.tex +++ /dev/null @@ -1,56 +0,0 @@ -\begin{figure*}[tp] -\centering -\begin{BVerbatim}[fontsize=\small] -debug:start search(file=texmf.cnf, must_exist=1, find_all=1, - path=.:/usr/local/bin/texlive:/usr/local/bin: - /usr/local/bin/texmf/web2c:/usr/local: - /usr/local/texmf/web2c:/.:/./teTeX/TeX/texmf/web2c:). -kdebug:start search(file=ls-R, must_exist=1, find_all=1, - path=~/tex:/usr/local/texmf). -kdebug:search(ls-R) =>/usr/local/texmf/ls-R -kdebug:start search(file=aliases, must_exist=1, find_all=1, - path=~/tex:/usr/local/texmf). -kdebug:search(aliases) => /usr/local/texmf/aliases -kdebug:start search(file=config.ps, must_exist=0, find_all=0, - path=.:~/tex:!!/usr/local/texmf/dvips//). -kdebug:search(config.ps) => /usr/local/texmf/dvips/config/config.ps -kdebug:start search(file=/root/.dvipsrc, must_exist=0, find_all=0, - path=.:~/tex:!!/usr/local/texmf/dvips//). -search(file=/home/goossens/.dvipsrc, must_exist=1, find_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//). -kdebug:search($HOME/.dvipsrc) => -kdebug:start search(file=config.cms, must_exist=0, find_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//). -kdebug:search(config.cms) -=>/usr/local/texmf/dvips/cms/config.cms -\end{BVerbatim} -\caption{Finding configuration files}\label{fig:dvipsdbga} - -\bigskip - -\begin{BVerbatim}[fontsize=\small] -kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro -\end{BVerbatim} -\caption{Finding the prolog file}\label{fig:dvipsdbgb} - -\bigskip - -\begin{BVerbatim}[fontsize=\small] -kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, - path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: - /var/tex/fonts/tfm//). -kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm -kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, - ... - -kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb -[1] -\end{BVerbatim} -\caption{Finding the font file}\label{fig:dvipsdbgc} -\end{figure*} diff --git a/Master/texmf-doc/source/texlive/texlive-common/examples/ex6a.tex b/Master/texmf-doc/source/texlive/texlive-common/examples/ex6a.tex deleted file mode 100644 index bbc9f5b42a7..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-common/examples/ex6a.tex +++ /dev/null @@ -1,24 +0,0 @@ -\begin{BVerbatim}[fontsize=\small] -debug:start search(file=texmf.cnf, must_exist=1, find_all=1, - path=.:/usr/local/bin/texlive:/usr/local/bin: - /usr/local/bin/texmf/web2c:/usr/local: - /usr/local/texmf/web2c:/.:/./teTeX/TeX/texmf/web2c:). -kdebug:start search(file=ls-R, must_exist=1, find_all=1, - path=~/tex:/usr/local/texmf). -kdebug:search(ls-R) =>/usr/local/texmf/ls-R -kdebug:start search(file=aliases, must_exist=1, find_all=1, - path=~/tex:/usr/local/texmf). -kdebug:search(aliases) => /usr/local/texmf/aliases -kdebug:start search(file=config.ps, must_exist=0, find_all=0, - path=.:~/tex:!!/usr/local/texmf/dvips//). -kdebug:search(config.ps) => /usr/local/texmf/dvips/config/config.ps -kdebug:start search(file=/root/.dvipsrc, must_exist=0, find_all=0, - path=.:~/tex:!!/usr/local/texmf/dvips//). -search(file=/home/goossens/.dvipsrc, must_exist=1, find_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//). -kdebug:search($HOME/.dvipsrc) => -kdebug:start search(file=config.cms, must_exist=0, find_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//). -kdebug:search(config.cms) -=>/usr/local/texmf/dvips/cms/config.cms -\end{BVerbatim} \ No newline at end of file diff --git a/Master/texmf-doc/source/texlive/texlive-common/examples/ex6b.tex b/Master/texmf-doc/source/texlive/texlive-common/examples/ex6b.tex deleted file mode 100644 index 5a5a92f1f22..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-common/examples/ex6b.tex +++ /dev/null @@ -1,6 +0,0 @@ -\begin{BVerbatim}[fontsize=\small] -kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro -\end{BVerbatim} \ No newline at end of file diff --git a/Master/texmf-doc/source/texlive/texlive-common/examples/ex6c.tex b/Master/texmf-doc/source/texlive/texlive-common/examples/ex6c.tex deleted file mode 100644 index 5daaeaa184b..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-common/examples/ex6c.tex +++ /dev/null @@ -1,14 +0,0 @@ -\begin{BVerbatim}[fontsize=\small] -kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, - path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: - /var/tex/fonts/tfm//). -kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm -kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, - ... - -kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb -[1] -\end{BVerbatim} \ No newline at end of file diff --git a/Master/texmf-doc/source/texlive/texlive-common/install-w32-main.png b/Master/texmf-doc/source/texlive/texlive-common/install-w32-main.png deleted file mode 100644 index a8cc55f6070..00000000000 Binary files a/Master/texmf-doc/source/texlive/texlive-common/install-w32-main.png and /dev/null differ diff --git a/Master/texmf-doc/source/texlive/texlive-common/psview.png b/Master/texmf-doc/source/texlive/texlive-common/psview.png deleted file mode 100644 index 8322bdda693..00000000000 Binary files a/Master/texmf-doc/source/texlive/texlive-common/psview.png and /dev/null differ diff --git a/Master/texmf-doc/source/texlive/texlive-common/stdcoll.png b/Master/texmf-doc/source/texlive/texlive-common/stdcoll.png deleted file mode 100644 index 16a699ba3c6..00000000000 Binary files a/Master/texmf-doc/source/texlive/texlive-common/stdcoll.png and /dev/null differ diff --git a/Master/texmf-doc/source/texlive/texlive-common/tlmgr-config.png b/Master/texmf-doc/source/texlive/texlive-common/tlmgr-config.png deleted file mode 100644 index 7f2d3123689..00000000000 Binary files a/Master/texmf-doc/source/texlive/texlive-common/tlmgr-config.png and /dev/null differ diff --git a/Master/texmf-doc/source/texlive/texlive-common/tlmgr-gui.png b/Master/texmf-doc/source/texlive/texlive-common/tlmgr-gui.png deleted file mode 100644 index 9c45772503d..00000000000 Binary files a/Master/texmf-doc/source/texlive/texlive-common/tlmgr-gui.png and /dev/null differ diff --git a/Master/texmf-doc/source/texlive/texlive-common/w32client/README b/Master/texmf-doc/source/texlive/texlive-common/w32client/README deleted file mode 100644 index a09ea7cf560..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-common/w32client/README +++ /dev/null @@ -1,26 +0,0 @@ -The w32client pair of scripts configure a Windows system to make use -of an existing read-only TeX Live installation, typically on a -network drive. - -Copy these scripts to the root of the TeX live installation, -i.e. the same directory as texmf, texmf-dist etc. - -This pair of scripts is intended as a prototype. Normally, it should -work as-is, at least after copying to the right place, but you -should review the following items: - -- check which shortcuts you want to include (add_desktop_shortcut - and add_menu_shortcut) - -- Decide which file associations, if any, you want to create - (register_extension and register_filetype). Although we wrote the - functions for it, we decided in the end not to use them in the - regular installation. - -- You can comment out or remove the xetex stanza if you aren't going -- to use xetex. - -- If the directory layout is non-standard, you may have to edit the - texmf.cnf in the root of the installation. Use relative - directories, using $SELFAUTOPARENT, whenever possible. See - texmf/web2c/texmf.cnf for examples. diff --git a/Master/texmf-doc/source/texlive/texlive-common/w32client/install-w32client b/Master/texmf-doc/source/texlive/texlive-common/w32client/install-w32client deleted file mode 100755 index 0de75a465fa..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-common/w32client/install-w32client +++ /dev/null @@ -1,177 +0,0 @@ -#!/usr/bin/env perl -# $Id$ -# copy this file and install-w32client.bat to the same directory -# as texmf, texmf-dist etc. - -# sample mini-installer to give Windows systems access to an -# existing TeXLive installation - -# it assumes a standard directory layout, which avoids hard-coded paths. -# if this is not the case, adjustments may be necessary. - -$^W = 1; - -use TeXLive::TLUtils qw(mkdirhier); -use TeXLive::TLWinGoo qw(non_admin add_texbindir_to_path setenv_reg - init_unshortbat add_desktop_shortcut add_menu_shortcut - register_extension register_file_type - update_assocs broadcast_env - create_uninstaller); -use strict; - -# the code below assumes that this script is in $texdir, -# the directory above texmf, texmf-dist etc. - -my $texdir=$0; -$texdir=~s!\\!/!g; -$texdir=~s!(.*)/.*$!$1!; - -# private runtime-generated files -$::texlive_release = '2008'; -my $texdirw = $ENV{'USERPROFILE'}.'/.texlive'.$::texlive_release; -$texdirw=~s!\\!/!g; -my $private_var = $texdirw.'/texmf-var'; -my $private_var_bsl = $private_var; -$private_var_bsl =~ s!/!\\!g; - -# make only per-user modifications -non_admin(); - -# general - -add_texbindir_to_path($texdir.'/bin/win32'); -broadcast_env(); - -my $mainmenu = "TeX Live 2008"; -my $texbindir_bsl = $texdir.'/bin/win32'; -$texbindir_bsl =~ s!/!\\!g; - -mkdirhier("$texdirw/tlpkg/installer"); -create_uninstaller($texdir, $texdirw, $private_var, $texdirw.'/texmf-config'); -init_unshortbat($texdirw); - -# if the path can't be fixed globally add command prompt -# with texbindir prepended to path - -if (uc(TeXLive::TLWinGoo::win_which_dir('tex.exe')) ne - uc($texdir.'/bin/win32') or - uc(TeXLive::TLWinGoo::win_which_dir('pdftex.exe')) ne - uc($texdir.'/bin/win32') or - uc(TeXLive::TLWinGoo::win_which_dir('luatex.exe')) ne - uc($texdir.'/bin/win32')) { - add_menu_shortcut( - $mainmenu, - 'TeX Live Prompt', - '', - $ENV{'COMSPEC'}, - "/k \"path $texbindir_bsl;%path%\"", - '', - ); -} - -# texlive manual - -add_menu_shortcut( - $mainmenu, - 'TeX Live Manual (en)', - '', # default pdf icon - $texdir.'/texmf-doc/doc/english/texlive-en/texlive-en.pdf', - '', - '', -); - -# texdoctk documentation browser - -if (-e $texdir.'/bin/win32/texdoctk.bat') { - add_menu_shortcut( - $mainmenu, - 'TeXdoc GUI', - '', # icon - $texdir.'/bin/win32/texdoctk.bat', - '', # arguments - 'batgui', # any non-null value to hide command-prompt - ) -} - -# psview - -add_desktop_shortcut( - $texdirw, - 'PS_View', - $texdir.'/tlpkg/tlpsv/psv.exe', # icon, not prog! - $texdir.'/bin/win32/psv.bat', - '', # no args - 'batgui', # any non-null value to hide command-prompt -); -add_menu_shortcut( - $mainmenu, - 'PS_View', - $texdir.'/tlpkg/tlpsv/psv.exe', # icon, not prog! - $texdir.'/bin/win32/psv.bat', - '', # no args - 'batgui', # any non-null value to hide command-prompt -); -# comment out if you prefer gsview -register_extension(".ps", "PostScript"); -register_extension(".eps", "PostScript"); -register_file_type("PostScript", - '"'.$texdir.'/tlpkg/tlpsv/gswxlua.exe" -g '. - '"'.$texdir.'/tlpkg/tlgs/bin/gsdll32.dll" -l '. - '"'.$texdir.'/tlpkg/tlpsv/psv.wx.lua" -p '. - '"'.$texdir.'/tlpkg/tlpsv/psv_view.ps" -sINPUT="%1"'); -update_assocs(); - -# dviout - -add_menu_shortcut( - $mainmenu, - 'DVIOUT', - $texdir.'/tlpkg/dviout/dviout.exe', - 'wscript', - $texdir."/bin/win32/dviout.vbs", - '', -); - -# xetex - -if (-e $texdir.'/bin/win32/xetex.exe') { - my $xetexmfcnf = $private_var.'/web2c'; - my $texmfcnf = $xetexmfcnf.';'.$texdir.'/texmf/web2c'; - setenv_reg('TEXMFCNF', $texmfcnf); - broadcast_env(); - mkdirhier($private_var."/fonts"); - system("xcopy", "/e", "/i", "/q", "/y", "\"$texbindir_bsl\\conf\"", - "\"$private_var_bsl\\fonts\\conf\""); - system("xcopy", "/e", "/i", "/q", "/y", "\"$texbindir_bsl\\cache\"", - "\"$private_var_bsl\\fonts\\cache\""); - if (open(FONTSCONF, "<$texdir/bin/win32/conf/fonts.conf")) { - my @lines = ; - close(FONTSCONF); - if (open(FONTSCONF, ">$private_var/fonts/conf/fonts.conf")) { - my $winfontdir; - $winfontdir = $ENV{'SystemRoot'}.'/fonts'; - $winfontdir =~ s!\\!/!g; - foreach (@lines) { - $_ =~ s!c:/Program Files/texlive/2008!$texdir!; - $_ =~ s!c:/windows/fonts!$winfontdir!; - print FONTSCONF; - } - close(FONTSCONF); - } else { - warn("Cannot open $private_var/fonts/conf/fonts.conf for writing\n"); - } - } else { - warn ("Cannot open $texdir/bin/win32/conf/fonts.conf\n"); - } - mkdirhier($xetexmfcnf); - if (open(TMF, ">$xetexmfcnf/texmf.cnf")) { - print TMF "FONTCONFIG_PATH=\$TEXMFVAR/fonts/conf\n"; - print TMF "FC_CACHEDIR=\$TEXMFVAR/fonts/cache\n"; - close TMF; - } else { - warn("Cannot open $xetexmfcnf/texmf.cnf for writing\n"); - } - $ENV{'TEXMFCNF'} = $texmfcnf; - $ENV{'PATH'} = $texbindir_bsl.';'.$ENV{'PATH'}; - system("\"$texbindir_bsl\\fc-cache.exe\"", "-v", "-r"); -} diff --git a/Master/texmf-doc/source/texlive/texlive-common/w32client/install-w32client.bat b/Master/texmf-doc/source/texlive/texlive-common/w32client/install-w32client.bat deleted file mode 100755 index 0d22ada6688..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-common/w32client/install-w32client.bat +++ /dev/null @@ -1,28 +0,0 @@ -@echo off - -rem copy this file and install-w32client to the same directory -rem as texmf, texmf-dist etc. - -rem TeX Live Root; ends with backslash -rem This may also work with UNC names - -set texdir=%~dp0 -set tldrive=%~d0 - -%tldrive% -cd %texdir% - -rem use provided Perl - -set PERL5SAVE=%PERL5LIB% -set PERL5LIB=%texdir%tlpkg\tlperl\lib;%texdir%tlpkg -"%texdir%tlpkg\tlperl\bin\perl" "%~dpn0" %* -rem pause Done - -rem cleanup in case of start from command-line - -set PERL5LIB=%PERL5SAVE% -set PERL5SAVE= -set tldrive= -set texdir= -pause \ No newline at end of file diff --git a/Master/texmf-doc/source/texlive/texlive-cz/Makefile b/Master/texmf-doc/source/texlive/texlive-cz/Makefile deleted file mode 100644 index acbed97a89b..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-cz/Makefile +++ /dev/null @@ -1,5 +0,0 @@ -include ../texlive-en/Makefile -doc = texlive-cz -lang = czechslovak - - diff --git a/Master/texmf-doc/source/texlive/texlive-cz/cs-tex-live.sty b/Master/texmf-doc/source/texlive/texlive-cz/cs-tex-live.sty deleted file mode 100644 index 7e2569d7776..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-cz/cs-tex-live.sty +++ /dev/null @@ -1,458 +0,0 @@ -\NeedsTeXFormat{LaTeX2e}[1995/12/01] -\ProvidesPackage{cs-tex-live}[2004/11/15 v1.22 TeX Live documentation style] -\RequirePackage{alltt} -\RequirePackage{array} -\RequirePackage{colortbl} -\RequirePackage{graphicx} -%\RequirePackage{here} -\RequirePackage{longtable} -%\iftrue -%\def\Hv@scale{.91} % to match x-height of Palatino -%\RequirePackage{palatino} -%\else -\usepackage{lmodern} -%\fi -\RequirePackage{tabularx} -\RequirePackage{shortvrb} -\RequirePackage[normalem]{ulem} -\RequirePackage[obeyspaces]{url} -\RequirePackage{xspace} -\usepackage[T1]{fontenc} -\usepackage[latin2]{inputenc} -\usepackage[czech]{babel}% -\usepackage{csquote} % do define \uv -\newcommand{\singleuv}[1]{,#1`} -\newcommand{\ctt}{\url{news:comp.text.tex}} -\newcommand{\kB}{KiB} -\newcommand{\MB}{MiB} -\newcommand\TKCS{\textsf{\TeX-kolekce}} -\newcommand\ProTeXt{Pro\TeX t} -\clubpenalty 10000 -\widowpenalty 10000 -\RequirePackage{europs} -\let\euro\EUR -\usepackage{comment} -%\newcommand\ncs{\protect\NN} -%\newcommand\NN[1]{\bgroup\color{red}#1\egroup} -%\def\p.{s.\,} -\def\p.{na stran\v{e}~} -% General squeezed itemize. -\newenvironment{itemize*}% - {\begin{itemize}% - \setlength{\itemsep}{0pt}% - \setlength{\parskip}{0pt}}% - {\end{itemize}} -% -% for a proper \acro command (even in the context of the definition in -% ltugboat -- \DRC overrides without checking) -% -\RequirePackage{relsize} -\DeclareRobustCommand{\acro}[1]{\textsmaller{#1}\@} -% -\RequirePackage{fancyvrb} -\DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=\normalsize} -\DefineVerbatimEnvironment{fverbatim}{Verbatim}{fontsize=\footnotesize} -\DefineVerbatimEnvironment{sverbatim}{Verbatim}{fontsize=\small} -\DefineVerbatimEnvironment{boxedverbatim} - {Verbatim}{fontsize=\scriptsize,frame=single} -\DefineVerbatimEnvironment{Verbatim}{Verbatim}{fontsize=\normalsize} -\def\verbatiminput#1{\VerbatimInput[fontsize=\scriptsize]{#1}} -\def\boxedverbatiminput#1{\VerbatimInput[frame=single,fontsize=\scriptsize]{#1}} -\def\listinginput#1#2{\VerbatimInput[fontsize=\scriptsize,firstnumber=#1,numbers=left]{#2}} -\MakeShortVerb\| -% -% -% Done with packages. -% -% Page layout. -\advance\textwidth by 1.1in -\advance\oddsidemargin by -.55in -\advance\evensidemargin by -.55in -% -\advance\textheight by 1in -\advance\topmargin by -.5in -\advance\footskip by -.5in -\pagestyle{headings} -% -% LaTeX parameters. -\renewcommand{\topfraction}{0.85} -\renewcommand{\floatpagefraction}{0.86} -\renewcommand{\textfraction}{0.1} -\renewcommand{\belowcaptionskip}{4pt} -\setcounter{tocdepth}{2} -\setcounter{topnumber}{5} -\setcounter{totalnumber}{5} -% -% linebreaking, etc. -\pretolerance=1000 -\tolerance=1500 -\hbadness=3000 -\vbadness=3000 -\hyphenpenalty=400 -\emergencystretch=.1\hsize -\relpenalty=500 -% -% fonts -\let\sl\it -\let\slfamily\itfamily -\let\textsl\textit -\def\ttdefault{cmtt} -% -% various sorts of names -\newcommand*{\pkgname}[1]{\textsf{#1}}% package name -\newcommand*{\optname}[1]{\texttt{#1}}% (package,class) option name -\newcommand*{\cmdname}[1]{\textsf{#1}}% command name -\newcommand*{\colname}[1]{\emph{#1}}% collection name -\newcommand*{\dirname}[1]{\path{#1}}% directory name -\newcommand*{\filename}[1]{\path{#1}}% file name -\newcommand*{\envname}[1]{\texttt{#1}}% environment variable name -\newcommand{\code}[1]{\texttt{#1}} -\newcommand{\file}[1]{\texttt{#1}} -\newcommand{\prog}[1]{\texttt{#1}} -\newcommand{\samp}[1]{\singleuv{\texttt{#1}}} -\newcommand{\var}[1]{\emph{#1}} -\newcommand{\ttvar}[1]{\texttt{\var{#1}}} -% Include an image. -% #1 - name of image (pictures/#1.jpg, always .jpg please) -% #2 - bb for html -% #3 - width for TeX -% -\def\tlimage#1#2#3{% - \ifnum \Status=2 % html - \includegraphics[#2]{pictures/#1.jpg} \\[5mm] - \else % not html - \includegraphics[width=#3]{pictures/#1} \\[5mm] - \fi -} - -\def\tlpng#1#2{% - \ifnum \Status=2 % html, want relative path in output - \includegraphics[bb=0 0 1 1]{#1.png}% - \else % not html, handled by TEXINPUTS in Makefile - \includegraphics[width=#2]{#1.png}% - \fi -} - -% underlined command input. -\def\Ucom#1{% - \uline{\rule[-.2\baselineskip]{0pt}{.9\baselineskip}\ttfamily #1}} -\def\CDref#1#2{\href{../../../../#1}{#2}} -\def\OnCD#1{\href{../../../../#1}{\path{#1}}} -%\def\OnCD#1{\hyper@linkurl{\path{#1}}{../../../../#1}} -% GUI menu/button/tab sequence: -\def\guiseq#1{\textsf{#1}} -\def\arw{\unskip\discretionary{\hbox{$\rightarrow$}}{\hbox{$\rightarrow$}}{\hbox{$\rightarrow$}}\ignorespaces} -% -% Special names. -\def\dpi{$\,$dpi\xspace} -\def\bs{{\protect\normalfont\ttfamily\char'134}} -\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} -\def\Q#1{\par\vskip6pt\leftline{#1}\par} -\def\hyph{-} -% -% many abbreviations. -\newcommand{\CS}{$\mathcal{C}\kern-.1667em\lower.5ex% - \hbox{$\mathcal{S}$}\kern-.075em $} -\def\AFMtoTFM{\cmdname{AFM2TFM}\null} -\def\bv{\emph{Baskerville}} -\let\BV=\bv -\def\Dash{\unskip\nobreak\thinspace--\thinspace\ignorespaces} -\def\dvicopy{\cmdname{dvicopy}} -\def\dvidvi{\cmdname{dvidvi}} -\def\dvips{\cmdname{dvips}} -\def\eTeX{$\varepsilon$-\TeX} -\def\fpTeX{\textrm{fp}\TeX\xspace} -\def\GFtoDVI{\cmdname{GFtoDVI}\null} -\def\GFtoPK{\cmdname{GFtoPK}\null} -\def\GFtype{\cmdname{GFtype}} -\def\GUI{\acro{GUI}\xspace} -\def\KPS{Kpathsea} -\def\La{La} -\def\OMEGA{$\Omega$} -\def\OzMF{OzMF} -\def\OzMP{OzMP} -\def\OzTeX{O\kern-.03em z\kern-.15em\TeX} -\def\PKtype{\cmdname{PKtype}} -\def\PLtoTF{\cmdname{PLtoTF}\null} -\def\teTeX{\textrm{te}\TeX\xspace} -\def\TeXLive{\TeX{} Live\xspace} -\let\TL=\TeXLive -\def\TFtoPL{\cmdname{TFtoPL}\null} -\def\TK{\textsf{\TeX-Collection}} -\def\TypeI{Type~1} -\def\VFtoVP{\cmdname{VFtoVP}\null} -\def\VPtoVF{\cmdname{VPtoVF}\null} -\def\Thanh{H\`an~Th\^e\llap{\raise 0.5ex\hbox{\'{}}}~Th\`anh} -\def\XEmTeX{\textrm{XEm}\TeX\xspace} -\def\XEmacs{\textrm{XEmacs}\xspace} -\def\Webc{Web2C} -\providecommand*{\CD}{\acro{CD}\xspace} -\providecommand*{\CTAN}{\acro{CTAN}\xspace} -\providecommand*{\DVD}{\acro{DVD}\xspace} -\providecommand*{\GNU}{\acro{GNU}\xspace} -\providecommand*{\HTML}{\acro{HTML}\xspace} -\providecommand*{\ISO}{\acro{ISO}\xspace} -%\providecommand*{\MacOSX}{Mac\-\acro{OSX}\xspace} -\providecommand*{\MacOSX}{Mac\,\acro{OS\,X}\xspace} -\providecommand*{\PS}{Post\-Script\xspace} -\providecommand*{\GS}{Ghost\-script\xspace} -\providecommand*{\TDS}{\acro{TDS}\xspace} -\providecommand*{\dvi}{\acro{DVI}\xspace} -\providecommand*{\web}{\texttt{web}\xspace} -% -% description-like environment that uses tt instead of bf, and doesn't -% go to the left margin. Without the \hfil, get an underfull box. -% Don't why \descriptionlabel doesn't. -\newenvironment{ttdescription} - {\begin{list}{label must be supplied}{% - \itemsep=0pt % these lists tend to have short descriptions - \let\makelabel=\ttdescriptionlabel}}% - {\end{list}} -\newcommand*\ttdescriptionlabel[1]{\hspace\labelsep - \normalfont\ttfamily #1\hfil} -% -% Likewise, for commands using sans serif. -\newenvironment{cmddescription} - {\begin{list}{label must be supplied}{% - \itemsep=0pt - \let\makelabel=\cmddescriptionlabel}}% - {\end{list}} -\newcommand*\cmddescriptionlabel[1]{%%\hspace\labelsep - \normalfont\sffamily #1\hfil} -% -\newlength\tmplen -\newsavebox{\wbox} -\newenvironment{warningbox}% - {\fboxsep .017\textwidth - \begin{lrbox}{\wbox} - \setlength{\tmplen}{\textwidth}% - \addtolength{\tmplen}{-2\fboxsep}% - \addtolength{\tmplen}{-.8pt}% twolines - \begin{minipage}{\tmplen}} - {\end{minipage}\end{lrbox}% - \bgroup\centering\fbox{\usebox{\wbox}}\egroup} -% -% lrbox is used as a representation marking. I changed it to -% lrBox in tne source file, to get closer to logical marking -\newsavebox{\mylrbox} -\newenvironment{lrBox} - {\begin{lrbox}{\mylrbox}} - {\end{lrbox}} -% -% -% output setup -% -\newif\ifSingleColumn -\providecommand{\Status}{0} -\typeout{Status is \Status, e.g.: } -% -% By default, we won't be creating hyperlinks. -\def\href#1#2{#2} -\def\hypertarget#1#2{} -\def\email#1{\href{mailto:#1}{\path{#1}}} % \path comes from url -\RequirePackage{texnames} -\ifx\PiC\undefined \def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC} \fi -\ifx\PiCTeX\undefined \def\PiCTeX{\PiC\kern-.11em\TeX} \fi -% -% -\ifcase\Status - % \Status = 0 - \typeout{TeX Live documentation for printing} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - \or - % \Status = 1 - \typeout{TeX Live documentation in PDF format} - \RequirePackage[colorlinks,bookmarksopen, - pdfstartview={FitBH -320000},hyperindex]{hyperref} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - \or - % \Status = 2 - \typeout{TeX Live documentation in HTML format} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - % read our config file, live4ht.cfg; q.v., for more definitions. - % hyperref load must come after the tex4ht load. - \RequirePackage[live4ht]{tex4ht} - \RequirePackage[tex4ht]{hyperref} \hyperlinkfileprefix{} - \def\CDref#1#2{\href{../../../../#1}{#2}} - \def\OnCD#1{\href{../../../../#1}{#1}} - \or - % \Status = 3 - \typeout{TeX Live documentation as a Zpravodaj issue!} - \RequirePackage{zpravodaj}% outline of Zpravodaj - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - \or - % \Status = 4 - \typeout{TeX Live documentation as a TUB article} - \@ifundefined{Fonts}% - {\RequirePackage{ae}}% - {\RequirePackage[T1]{\Fonts}} - \SingleColumnfalse - \newenvironment{multicols}[1]{}{} -\fi -% -\ifnum \Status=4 -\else - %\RequirePackage{texnames} - \newcommand\ConTeXt{C\kern-.0333emon\-\kern-.0667em\TeX\kern-.0333emt} - \newcommand\MIKTEX{MiK\kern-.025em \TeX}% per www.miktex.org - \providecommand\TeXXeT{\TeX-{}-% - \kern-.1emX\kern-.125em\lower.5ex\hbox{E}\kern-.1667emT\@} -\fi -% -% hacking at sections etc., to pay attention to baskerville status -\newcommand{\@condend@multicols}{% - \ifSingleColumn - \else - \def\@tempa{multicols}% - \ifx\@tempa\@currenvir - \end{multicols}% - \fi - \fi -} -\let\Section\section -\renewcommand{\section}{% - \@ifstar - {\Section*}% - {% - \@condend@multicols - \@dblarg\@full@section - }% -} -\def\@full@section[#1]#2{% - \Section[#1]{#2}% - \ifSingleColumn\else\begin{multicols}{2}\fi -} -\let\SubSection\subsection -\renewcommand{\subsection}{% - \@ifstar{\SubSection*}% - {% - \@condend@multicols - \@dblarg\@full@subsection - } -} -\def\@full@subsection[#1]#2{% - \SubSection[#1]{#2}% - \ifSingleColumn\else\begin{multicols}{2}\fi -} - -% calm things down a bit if we're in a multiple-column version -\ifSingleColumn -\else - \def\@listI{\leftmargin\leftmargini - \parsep \z@ - \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ - \itemsep \z@ \@plus .1\p@ - } - \let\@listi\@listI - \@listi - \def\@listii{\leftmargin\leftmarginii - \labelwidth\leftmarginii\advance\labelwidth-\labelsep - \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ - \parsep \z@ - \itemsep \z@ \@plus .1\p@ - } - \def\@listiii{\leftmargin\leftmarginiii - \labelwidth\leftmarginiii\advance\labelwidth-\labelsep - \topsep 1\p@ \@plus 1\p@ \@minus 1\p@ - \parsep \z@ - \partopsep \z@ - \itemsep \topsep - } - \def\@listiv{\leftmargin\leftmarginiv - \labelwidth\leftmarginiv\advance\labelwidth-\labelsep - } - \def\@listv{\leftmargin\leftmarginv - \labelwidth\leftmarginv\advance\labelwidth-\labelsep - } - \def\@listvi{\leftmargin\leftmarginvi - \labelwidth\leftmarginvi\advance\labelwidth-\labelsep - } -\fi -% -% array package stuff -\def\arraybackslash{\let\\=\@arraycr} -\newcolumntype{P}[1]{>{\raggedright\arraybackslash}p{#1}} -% -% shaded rows (using facilities of colortbl) -% -\definecolor{pale}{gray}{.9} -\newcount\colrow -\gdef\RowColor{pale} -\def\SetRowColor{% - \rowcolor{\RowColor}% - \global\advance\colrow by1\relax - \ifodd\colrow - \gdef\RowColor{pale}% - \else - \gdef\RowColor{white}% - \fi -} -% redefine to hack up a reference even though we don't need it... -\renewcommand\@bibitem[1]{\if@filesw \immediate\write\@auxout - {\string\bibcite{#1}{?}}\fi\ignorespaces} -% -% \unknownTeXlive is a dummy texlive entry for the biblio -\newcommand\unknownTeXlive[2][\relax]{\textbf{\textsc{unknown}}% - \global\@all@unknown\expandafter{\the\@all@unknown{#2}}% -} -\newtoks\@all@unknown -\global\@all@unknown{} -\AtEndDocument{\@message@unknowns} -\def\@message@unknowns{\edef\@tempa{\the\@all@unknown}% - \ifx\@tempa\@empty - \else - \def\@tempa{*** TeX live package location of }% - \expandafter\@output@unknowns\the\@all@unknown\@empty - \fi -} -\def\@output@unknowns#1{\edef\@tempb{#1}% - \ifx\@tempb\@empty - \typeout{ unknown}% - \else - \message{\@tempa#1,}% - \def\@tempa{}% - \expandafter\@output@unknowns - \fi -} -% -% a hack for the bibliography -\bibliographystyle{tex-live} -\newif\iffirstbibentry -\global\firstbibentrytrue -\let\@@bibitem\bibitem -\renewcommand\bibitem{\iffirstbibentry - \global\firstbibentryfalse - \else - \\\SetRowColor - \fi - \@@bibitem -} - - -% for \Dings -\RequirePackage{pifont} -% available for inter-article dinglines -\def\Dings{\nopagebreak{\footnotesize\dingline{167}}} - -\ifnum \Status=3 -\newfont\fontmanual{logo10} % font used for the METAFONT logo, etc. -\renewcommand\MF{{\fontmanual META}\-{\fontmanual FONT}\spacefactor1000 } -\renewcommand\MP{{\fontmanual META}\-{\fontmanual POST}\spacefactor1000 } -\else -\RequirePackage{mflogo} -%\newfont\fontmanual{logo10} % font used for the METAFONT logo, etc. -%\newcommand\MF{{\fontmanual META}\-{\fontmanual FONT}\spacefactor1000 } -%\newcommand\MP{{\fontmanual META}\-{\fontmanual POST}\spacefactor1000 } -\fi - -% Silence font warnings about no bold typewriter in LM. -\def\@font@warning#1{}% - -% Silence hyperref warnings about \kern. -\def\HyPsd@Warning#1{}% - -\endinput diff --git a/Master/texmf-doc/source/texlive/texlive-cz/csquote.sty b/Master/texmf-doc/source/texlive/texlive-cz/csquote.sty deleted file mode 100644 index 3644143647b..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-cz/csquote.sty +++ /dev/null @@ -1,181 +0,0 @@ -%%%%%%%%%%%%%%%%%%%%%% cut here %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% -% -% File: CSQUOTE.TEX/STY -% Version: 1.1 -% -% Authors: Hunter Goatley -% (parts from QUOTE.TEX/STY) -% Petr Sojka -% -% Warranty: -% -% Copyright (c) 1992 by Hunter Goatley, Petr Sojka -% Permission to copy all or part of this work is granted, provided -% that the copies are not made or distributed for resale, and that -% the copyright notice and this notice are retained. -% -% THIS WORK IS PROVIDED ON AN "AS IS" BASIS. THE AUTHOR PROVIDES NO -% WARRANTY WHATSOEVER, EITHER EXPRESS OR IMPLIED, REGARDING THE WORK, -% INCLUDING WARRANTIES WITH RESPECT TO ITS MERCHANTABILITY OR FITNESS -% FOR ANY PARTICULAR PURPOSE. -% -% If you make any improvements, I'd like to hear about them. -% -% History: -% -% Oct 26, 92 - V1.0 first release -% Dec 14, 92 - V1.1 \uv added -% -% Abstract: -% -% This file defines the macros \csdoublequoteson and \csdoublequotesoff. -% These macros allows switching between standard and following behaviour: -% TeX replace the double-quote character (") with Czech -% left and right double-quotes. For example: -% -% "This is a test." ---> ,,This is a test.'' -% -% The double-quote character is still available via \dq. -% \" is still treated as the umlaut accent. -% -% This macro makes a couple of assumptions about the double-quotes: -% -% 1. Double-quotes are assumed to come in pairs. When replacing -% double-quotes, the macro alternates between ,, and ''. The only -% exception to this is noted in (2) below. -% 2. A double-quote at the beginning of a paragraph is always treated -% as ,,. This correctly handles the case where a quotation is -% continued into a second paragraph: -% -% "This is the first paragraph.\par -% "This is the second paragraph of the same quote." -% -% Normal TeX spacing after ,, and '' is maintained by saving and -% restoring the \spacefactor. -% -% Macros work both with plainTex and LaTeX. -% -%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% -% -% HOW IT WORKS: -% -% The double-quote character (") is made active by \csdoublequoteson. -% The " macro keeps track of left-quote/right-quote pairs and inserts -% the appropriate ,, and '' in its place. -% -% Each character has a \spacefactor associated with it, which specifies -% the amount of stretch or shrink that a space following the character -% can have. Most characters have a factor of 1000, but some punctuation -% marks have higher spacefactors, most notably the period, which has a -% \spacefactor of 3000. This means the space following a period can -% stretch up to 3 times more than the space after a regular character, -% accounting for the increased space at the end of sentences. -% -% The ,, and '' ligatures are assigned \spacefactor's of 0, so that the -% \spacefactor that is applied to the next character is the same as that -% of the character preceding the quotes. Because " has been redefined as -% a macro, any spaces following " are swallowed by TeX. It was necessary -% to have this macro re-insert any needed space so that the following -% cases worked correctly: -% -% "This is a test," she said. --> ,,This is a test,'' she said. -% "This is in a list"; etc. --> ,,This is in a list''; etc. -% -% Without the added space, the first example becomes: -% -% ,,This is a test,''she said. -% -% The solution was to save the current \spacefactor before inserting a -% right double-quote, then resetting the \spacefactor after the -% insertion. The net effect was that the " macro has a \spacefactor -% of 0, which matches the way TeX treats ,, and ''. -% -%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% -{% % Begin a group for which " is active -\catcode`\"=\active % Make " an active character -\catcode`\@=11 % Make @ an active character -% -% \csdoublequoteson -% -% This macro makes " an active character, resets the control sequence -% \dblqu@te to L (left), and defines \dq as a replacement for ". -% -\gdef\csdoublequoteson{% % \csdoublequoteson enables " - \gdef"{\czechquotes}% % Define " as \czechquotes - \global\catcode`\"=\active% % Make " an active character - \global\chardef\dq=`\"% % Double-quote char. via \dq - \global\let\dblqu@te=L% % Always start with a left double-quote - } % End of macro -% -% \bq, \eq -% -% These macros define default characters for czech left and right -% double quotes. Czech opening quote is created from two commas with -% kerning depending on fontdimen four parameter of current font. -% Better solution should be specially designed character with -% proper kernings; if you have such characters in fonts -% (e.g. in DC-fonts), use it instead. (e.g. define -% macros \bq and \eq e.g. \def\bq{\char"130 } -% in your document/style file-- not in csquote.sty!) -% Similar solution is used for czech right quote. -% -% \cs existence test, stolen from TeXbook exercise 7.7 -\def\ifundefined#1{\expandafter\ifx\csname#1\endcsname\relax }% -% -% another macro to be more efficient in time and space -\global\chardef\f@@r=4 -% -\ifundefined{bq}% -\gdef\bq{\kern-.25\fontdimen\f@@r\font,\kern-.8\fontdimen\f@@r\font,% - \kern-.35\fontdimen\f@@r\font}% -\fi -\ifundefined{eq}% -\gdef\eq{\kern-.35\fontdimen\f@@r\font`\kern-.8\fontdimen\f@@r\font`% - \kern-.25\fontdimen\f@@r\font} -\fi -% -% Macro \uv for other usage of \bq and \eq. -% -\ifundefined{uv}% - \gdef\uv#1{\bq #1\eq} -\fi -% -% Define the macro that will be executed whenever " is encountered. -% -\gdef\czechquotes{% - % If the double-quote is the first character in a new paragraph, - % make sure it becomes a left double-quote. This case can be - % detected by checking to see if TeX is currently in vertical mode. - % If so, the double-quote is at the beginning of the paragraph - % (since " hasn't actually generated any horizontal mode tokens - % yet, TeX is still in vertical mode). If the mode is vertical, - % set \dblqu@te equal to L. - % - \ifinner\else\ifvmode\let\dblqu@te=L\fi\fi% - % - % Now insert the appropriate left or right double-quote. - % - % If \dblqu@te is L, insert an opening quote and set \dblqu@te to R. - % - \if L\dblqu@te\bq\global\let\dblqu@te=R% - % - % Otherwise, save the current \spacefactor, insert '', set \dblqu@te - % to L, and reset the original \spacefactor. - % - \else% - \let\xxx=\spacefactor% % Save the \spacefactor - \eq% % Insert ending quote - \global\let\dblqu@te=L% % and reset \dblqu@te - \spacefactor\xxx% % Reset the \spacefactor - \fi% % End of \if L\dblqu@te... - } % End of " macro -} % End of group - -\gdef\csdoublequotesoff{% - \catcode`\"=12% % Set " back to other - } -% -% Czech quotes are default -% -\csdoublequoteson - diff --git a/Master/texmf-doc/source/texlive/texlive-cz/live4ht.cfg b/Master/texmf-doc/source/texlive/texlive-cz/live4ht.cfg deleted file mode 100644 index 3fa6506696b..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-cz/live4ht.cfg +++ /dev/null @@ -1,47 +0,0 @@ -% tex4ht configuration file for the TeX Live documentation. -% Accumulated over many years. Public domain. -% -% html specifies the main output format. -% info for extra debugging info in the log files. - -% better approach is to have html in one piece (including footnotes). -% also the newest TeX4ht could produce UTF-8 output (-utf8 option) -\Preamble{charset=iso-8859-2,html,info,fn-in} - -% add extra stylesheet -\Configure{@HEAD}{\HCode{% -\Hnewline -\Hnewline -}} - -% or LaTeX complains it is missing. -\begin{document} - -\EndPreamble - -% simplify output for HTML. We leave TeX and LaTeX alone, since tex4ht -% actually does the lowered E (and raised A) in CSS. -\def\OMEGA{Omega} -\def\LaTeXe{LaTeX2e} -\def\eTeX{e-\TeX} -\def\acro#1{#1} -\def\MF{Metafont} -\def\BibTeX{BibTeX} -\def\warningbox{} -\def\endwarningbox{} - -\newif\ifhackliterals -\ifx\tldocenglish\undefined \else \hackliteralstrue \fi -\ifx\tldocrussian\undefined \else \hackliteralstrue \fi -\ifx\tldocgerman\undefined \else \hackliteralstrue \fi -% -\ifhackliterals - % these definitions cause "missing } inserted" at \end{tabularx} in - % French and Czech. don't know why. - % - % don't make these into links, as happens with \path. We only have a couple - % special characters that actually occur. - \def\dirname{\texttt\bgroup\catcode`\$=12 \catcode`\_=12 \finishliteral} - \def\finishliteral#1{#1\egroup} - \let\filename=\dirname -\fi diff --git a/Master/texmf-doc/source/texlive/texlive-cz/texlive-cz.tex b/Master/texmf-doc/source/texlive/texlive-cz/texlive-cz.tex deleted file mode 100644 index 77d8ed9ea5e..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-cz/texlive-cz.tex +++ /dev/null @@ -1,3030 +0,0 @@ -% -% czechslovak/live.tex - TeXlive 2008 documentation -- Czech/Slovak translation -% -% TeX Live documentation. Originally written by Sebastian Rahtz and -% Michel Goossens, now maintained by Karl Berry and others. -% Public domain. -% -% 2008/08/12: v1.34 prvni korektury prekladu 2008 -% 2008/08/02: v1.33 aktualizacia prekladu 2008 -% 2007/01/24: v1.32 XeTeX URL and HH (config.manpath) change -% 2007/01/22: v1.31 last minute corrections by Staszek (2x) and ZW -% 2007/01/15: v1.30 corrections and typos -% 2007/01/14: v1.29 texlive2007 version (JB&PS) -% 2005/11/01: v1.28 last minute Staszek additions -% 2005/10/31: v1.27 texlive2005 version (JB&PS) -% 2004/11/18: v1.26 final release cleanup, latest changes by Staszek -% 2004/11/17: v1.24,25 typos corrected -% 2004/11/15: v1.21,22,23 corrections by KB, JB and others entered -% 2004/11/14: v1.20 first texlive2004 version (JB&PS) -% 2004/01/30: v1.19 postbulletin version release for CSTUG web -% 2004/01/22: v1.18 minor changes before final-2003 source release -% 2004/01/19: v1.16, v1.17 last-minute corrections before sending -% Bulletin to print -% 2004/01/18: modifications for CS bulletin by Z. Wagner -% 2004/01/07: version 1.15 -% 2003/12/08-10: Slovak and other Czech typos corrected -% 2003/12/06: Czech language typos/errors entered -% 2003/09/23: prepositions checked, v1.03 -% 2003/09/23: some typos, jch's email, v1.02 -% 2003/09/22: further error corrections, v1.01 -% 2003/09/18: final checking and error corrections, v1.0 release -% 2003/09/17: another changes in English version incorporated -% 2003/09/08: changes in English version from 09/04 to 09/06 incorporated -% 2003/09/06: fixes from Staszek -% 2003/09/05: touched by Karl -% 2003/09/04: fixes from Staszek and Fabrice -% 2003/09/05: translation started from english version as of Sep 1st by -% Petra & Petr S. -% 2003/09/01: fixes from Volker. -% 2003/08/12: fixes from Christer Gustafsson . -% 2003/07/07: substantial revisions by karl. -% ... deleted -% -% TODO -% -% -- Priklady ve slovenske casti aktualizovat z~anglicke verze -% (zustaly dosud z verze TeXlive 6). -% -% Translations: -% Copyright (c) 2003--2008 Petr Sojka -% Copyright (c) 2004--2008 Ján Bu¹a -% Copyright (c) 2003 Petra Sojková -% Copyright (c) 2001 Janka Chlebíková -% Permission is granted to copy, distribute and/or modify this document -% under the terms of the GNU Free Documentation License, Version 1.2 -% or any later version published by the Free Software Foundation; -% with no Invariant Sections, no Front-Cover Texts, and no -% Back-Cover Texts. A copy of the license is included in -% the section entitled "GNU Free Documentation License". - -\newif\ifforbulletin -\forbulletinfalse -%\forbulletintrue -\newcommand\cstlversion{1.34} -\newcommand\cstldate{12.\ srpna 2008} -\ifforbulletin - \providecommand\Status{3} % version for CSTUG bulletin Zpravodaj - \else - \providecommand\Status{1} % 2 html alebo 1 pdf -\fi -% -\ifnum\Status=2 % e.g. html generation via tex4ht - \def\classname{article} % need different doc class for html - \def\classoptions{11pt} -\else - \ifnum\Status=3 % Zpravodaj - \def\classname{article} - \def\classoptions{twoside,a5paper} -% \pdfpaperwidth=147.5mm -% \pdfpaperheight=210mm - \else \def\classname{artikel1} - \def\classoptions{11pt} - \fi -\fi - -\listfiles -\documentclass[\classoptions,slovak,english,czech]{\classname} -\usepackage{cs-tex-live} -\makeatletter -\newcommand\tubreflect[1]{% - \@ifundefined{reflectbox}{% - \message{A graphics package must be loaded for \string\XeTeX}% - }{% - \ifdim \fontdimen1\font>0pt - \raise 1.75ex \hbox{\kern.1em\rotatebox{180}{#1}}\kern-.1em - \else - \reflectbox{#1}% - \fi - }% -} -\def\tubhideheight#1{\setbox0=\hbox{#1}\ht0=0pt \dp0=0pt \box0 } -\def\XeTeX{\leavevmode - \tubhideheight{\hbox{X% - \lower.5ex \hbox{\kern-.125em\tubreflect{E}}% - \kern-.1667em \TeX}}} -\makeatother - -\begin{document} -\ifnum\Status=2 - % this ugliness is because the normal definition of ' for tex4ht - % tries to go into math mode. I don't under - \def'{\char`\'} -\fi - -\selectlanguage{czech} -\title{{\huge\textsf{\TL{} 2008}}\\[3mm] - Pøíruèka \protect\TeXLive{}, CS verze \cstlversion} -\date{\cstldate} - -\author{Karl Berry, editor \\[3mm] - \url{http://tug.org/texlive/}\\[3mm] -%B% \ifnum \Status=2 -%B% \includegraphics[bb=0 0 824 741]{../pictures/front} \\[5mm] -%B%\else -%B%\ifnum \Status=3 -%B% \includegraphics[width=.5\linewidth]{../pictures/bw-front2} \\[5mm] -%B%\else -%B% \includegraphics[width=.5\linewidth]{../pictures/front} \\[5mm] -%B%\fi \fi -%B% \small \textit{Kontaktní osoby pro tuto dokumentaci:}\\[3mm] -%B% \small \begin{tabular}{lcr} -%B% Czech/Slovak & Petr Sojka & \email{sojka (at) fi.muni.cz} \\ -%B% & Janka Chlebíková & \email{chlebikj (at) dcs.fmph.uniba.sk} \\ -%B% & Ján Bu¹a & \email{jan.busa (at) tuke.sk} \\ -%B% English & Karl Berry & \email{karl (at) freefriends.org} \\ -%B% French & Fabrice Popineau & \email{fabrice.popineau (at) supelec.fr} \\ -%B% German & Volker R.\,W.\ Schaa & \email{volker (at) dante.de} \\ -%B% Polish & Staszek Wawrykiewicz & \email{staw (at) gust.org.pl} \\ -%B% Russian & Boris Veytsman & \email{borisv (at) lk.net} -%B% \end{tabular} -% \tlimage{front}{bb=0 0 824 741}{.7\linewidth} - } - -% comes out too close to the toc, and we know it's page one anyway. -\thispagestyle{empty} -\maketitle - -\ifnum\Status=3 - \thispagestyle{csbul} - \ifforbulletin \setcounter{page}{113} % valid for 3-4/2003 - \else \raggedbottom - \fi -\fi - - Pøeklad - 2004--2008 J\'an Bu\v{s}a, - 2001 Janka Chleb\'\i kov\'a, - 2003--2008 Petr Sojka a - 2003 Petra Sojkov\'a - je ¹íøen pod GNU FDL licencí. - - Permission is granted to copy, distribute and/or modify this document - under the terms of the GNU Free Documentation License, Version 1.2 - or any later version published by the Free Software Foundation; - with no Invariant Sections, no Front-Cover Texts, and no - Back-Cover Texts. - -\begin{multicols}{2} -\tableofcontents -\listoftables -\end{multicols} - -\section{Úvodem} -\label{sec:intro} - -\subsection{\TeX\ Live a kolekce \TeX{}u} - -Tento dokument popisuje základní vlastnosti distribuce \TeXLive{} 2008, -co¾ je instalace \TeX{}u a pøíbuzných programù pro \acro{GNU}/Linux a dal¹í -unixové systémy, \MacOSX{} a (32bitové) systémy Windows. - - -\TL{} mù¾ete získat sta¾ením z~internetu, nebo na \TKCS{} \DVD, -které skupiny u¾ivatelù \TeX{}u distribuují mezi svými èleny. -Obsah tohto \DVD je struènì popsán v~oddíle~\ref{sec:tl-coll.dists}. -\TL{} a \TKCS{} spolu jsou výsledkem spoleèného úsilí -skupin u¾ivatelù \TeX u. Tento dokument popisuje pøevá¾nì samotný -\TL{}. - -\TL{} obsahuje \file{.exe} soubory pro \TeX{}, \LaTeXe{}, \ConTeXt, -\MF, \MP, \BibTeX{} a mnoho dal¹ích programù vèetnì obsáhlého -seznamu maker, fontù a dokumentace spolu s~podporou -sazby v~mnoha rùzných svìtových jazycích. - -Aktuální verze pou¾itého software je v~archívu -\acro{CTAN} na \url{http://www.ctan.org/}. - -Krátký seznam hlavních zmìn v~této verzi \TL{} -najdete na konci tohoto dokumentu, v~oddílu~\ref{sec:history} -na stranì~\pageref{sec:history}. - -\subsection{Podpora operaèních systémù} -\label{sec:os.support} - -\TL{} obsahuje binárky pro èetné architektury na bázi Unixu, -vèetnì \MacOSX. Obsa¾ené zdrojové texty by mìly umo¾nit instalaci -pro platformy, pro které nejsou k~dispozici binárky. - -Co se týèe Windows: podporovány jsou jenom Windows 2000 a pozdìj¹í verze. Upustili jsme -od podpory Windows 9\textit{x}, ME a NT. V~dùsledku této zmìny si Windows -vy¾aduje mnohem ménì zvlá¹tního zacházení ve srovnání s~Unixovými -systémy. Pro Windows nejsou k~dispozici 64bitové \file{.exe} soubory, ale -32bitové binárky by mìly bì¾et na 64bitových systémech. - -Alternativní øe¹ení pro Windows a \MacOSX{} najdete -v~oddíle~\ref{sec:tl-coll.dists}. - -\subsection{Základní instalace \protect\TL{}} -\label{sec:basic} - -\TL{} mù¾ete nainstalovat buï z~\DVD{} nebo z~internetu. Samotný sí»ový -instalaèní program je malý a v¹e po¾adované stáhne z~internetu. Sí»ový -instalaèní program je vhodné pou¾ít, kdy¾ potøebujete jenom èást -z~kompletní instalace \TL. - -Instalaèní program na \DVD{} vám umo¾ní instalaci na lokálním disku, av¹ak \TL{} mù¾ete spustit pøímo z~\DVD{} -(nebo z~obrazu \DVD{}, kdy¾ to vá¹ systém podporuje). - -\noindent Toto je popsané detailnì -v~následujících sekcích, zde jen souhrn: - -\begin{itemize*} -\item Instalaèní dávka se jmenuje \filename{install-tl}\,. -Funguje v~re¾imu \GUI{} (pøedvolba pro Windows) i v~textovém re¾imu (pøedvoleném pro v¹echny ostatní systémy). -Jednotlivé re¾imy dosáhnete volbou \code{-gui} nebo \code{-no-gui}. - -\item Jednou souèástí instalace je nový program, `\TL\ Manager', nazvaný \prog{tlmgr}. - Podobnì jako instalaèní program mù¾e být pou¾it v~re¾imu \GUI{} nebo v~textovém re¾imu. - Mù¾ete ho pou¾ít k~nainstalování nebo odinstalování balíkù a na rùzné konfiguraèní èinnosti. -\end{itemize*} - -\subsection{Nápovìda} -\label{sec:help} - -\TeX{}ovská komunita je aktivní, vstøícná a vìt¹ina -seriózních otázek je obvykle zodpovìzena. Podpora je -neformální, je provádìna pøíle¾itostnými ètenáøi a dobrovolníky, -a proto je dùle¾ité, abyste odpovìï na svùj dotaz hledali nejdøíve sami, -ne¾ ho vznesete na fóru. (Pokud tou¾íte po garantované komerèní podpoøe, -mù¾ete na \TL{} zapomenout a zakoupit komerèní distribuci; viz -seznam prodejc\r u na \url{http://tug.org/interest.html#vendors}.) - -Ní¾e je uveden seznam informaèních zdrojù, pøibli¾nì v~poøadí, ve kterém -ho doporuèujeme k~pou¾ití: - -\begin{description} -\item [první kroky] Pokud jste \TeX ovský nováèek, na stránce -\url{http://tug.org/begin.html} najdete krátký úvod do systému. -\item [\TeX{} \acro{FAQ}] \TeX{} \acro{FAQ} je obrovská studnice - znalostí obsahuj\'ic\'i v¹echny druhy otázek, od tìch základních a¾ po - ty nejobskurnìj¹í. - Dokument najdete na \TL{} v~adresáøi \OnCD{texmf-doc/doc/english/FAQ-en/html/index.html} - nebo na internetu na \url{http://www.tex.ac.uk/faq}. Prosíme, zaènìte - své hledání odpovìdi zde. - -\item [\TeX{} Catalogue] Pokud hledáte konkrétní balík, - font, program ap., \TeX{} Catalogue je místo, kde zaèít. - Je to obsáhlá sbírka \TeX{}ových polo¾ek. Viz - \OnCD{http://www.ctan.org/help/Catalogue/}. - -\item [\TeX{}ov\'e odkazy na Webu] Na \url{http://tug.org/interest.html} - najdete mnoho relevantních odkazù na rùzné pøíruèky, - knihy, manuály a èlánky o v¹ech aspektech systému \TeX{}. - -\item [archívy diskusních skupin] - \sloppypar Dvì základní fóra pro hledání øe¹ení problémù jsou - newsová skupina \ctt{} a emailová diskusní - skupina \email{texhax@tug.org}. V~archívech tìchto zdrojù - najdete tisíce pøedchozích dotazù a odpovìdí èekajících na va¹e - hledání. Nahlédnìte na - \url{http://groups.google.com/groups?group=comp.text.tex}, - res\-pek\-ti\-ve na - \url{http://tug.org/mail-archives/texhax}. Dotazem do obecného - vyhledávacího stroje jako \url{http://google.com/} také nic nepokazíte - a pro specifika èe¹tiny a sloven¹tiny najdete dal¹í zdroje - odkazované na \url{http://www.cstug.cz/}. - -\item [kladení dotazù] Pokud nemù¾ete najít odpovìï na svou otázku, - mù¾ete ji polo¾it na \ctt{} pøes Google nebo - newsového klienta nebo emailem na \email{texhax@tug.org}. - Ale døíve, ne¾ tak uèiníte, \emph{prosím,} pøeètìte - si toto doporuèení, abyste maximalizovali vyhlídky na - získání u¾iteèné odpovìdi: - \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. - -\item [podpora \TL{}] Pokud chcete poslat - chybové hlá¹ení, pøipomínku nebo poznámku k~distribuci - \TL{}, její instalaci nebo dokumentaci, - diskusní skupina k~tomu urèená je \email{tex-live@tug.org}. - Pokud v¹ak je va¹e otázka specifická pro program na - \TL{} umístìný, napi¹te prosím pøímo autorovi nebo do diskusní - skupiny urèené pro tento program. Spu¹tìní programu - s~volbou \code{-{}-help} nezøídka - poskytuje adresu pro chybové hlá¹ení. -\end{description} - -\noindent -Druhou stranou mince je odpovídání na dotazy tìch, kdo kladou otázky. -\ctt{} i~list \code{texhax} jsou otevøeny pro kohokoliv. -Pøihlaste se, naslouchejte a zaènìte odpovídat tam, kde mù¾ete. - -% don't use \TL so the \uppercase in the headline works. Also so -% tex4ht ends up with the right TeX. Likewise the \protect's. -\section{Pøehled \protect\TeX\protect\ Live} -\label{sec:overview.tl} - -Tento oddíl popisuje obsah \TL{} a \TKCS{}, jej\'\i\v z~je èástí. - -%Dvì hlavní instalaèní dávky pro Unix a \MacOSX{} jsou -%\texttt{install-tl.sh} a \texttt{install-pkg.sh}. Jsou -%popsány v~oddíle~\ref{sec:unix.install} na -%stranì~\pageref{sec:unix.install}. -%V~dal¹ím oddíle popí¹eme strukturu a obsah \TL{}. - - -\subsection{Kolekce \protect\TeX{}u: \TL, pro\TeX{}t, Mac\TeX} -\label{sec:tl-coll.dists} - -\DVD{} \TKCS{} zahrnuje následující: - -\begin{description} - -\item [\TL] Úplný systém \TeX{}, který mù¾e být spou¹ten pøímo nebo nainstalován na disk. - -\item [Mac\TeX] pro \MacOSX, pøidává pøirozený \MacOSX\ instalaèní program a jiné aplikace Mac k~\TL{}. Jeho domovská stránka je -\url{http://www.tug.org/mactex/}. - -\item [pro\TeX{}t] Roz¹íøení systému \MIKTEX\ pro Windows. -\ProTeXt\ pøidává k~\MIKTEX u nové doplòkové nástroje -a zjednodu¹uje instalaci. Je plnì nezávislý na \TL{} -a má své vlastní pøíkazy. -Domovská stránka projektu \ProTeXt\ je na \url{http://tug.org/protext}. - -\item [CTAN] Výpis obrazovky skladi¹tì \CTAN{}. - -\item [\texttt{texmf-extra}] Adresáø s~rozmanitými doplòkovými balíky. - -%\item [demo] systém spustitelný pøímo z~\CD. Aby to bylo mo¾né, -%byli jsme nuceni vypustit velké kolekce pro sazbu -%èín¹tiny, japon¹tiny a korej¹tiny \acro{CJK}, -%podporu sazby not, nìkterá ménì èasto pou¾ívaná písma. -%Distribuce funguje jen pod Linuxem, \MacOSX{} a systémy Windows. - -\end{description} - - -\CTAN{}, \pkgname{protext} a \dirname{texmf-extra} nemusí mít stejné podmínky -pro kopírování jako \TL{}, proto buïte pozorní pøi ¹íøení nebo modifikaci. - -\subsection{Popis koøenových adresáøù \TL{}} -\label{sec:tld} - -V~koøenovém adresáøi distribuce \TL{} najdete následující -podadresáøe. Na \pkgname{live} \DVD\ je celá \TL{} hierarchie v~podaresáøi -\dirname{texlive}, a ne v~koøenovém adresáøi disku. - -\begin{ttdescription} -\item[bin] Binárky systému \TeX{}, s~podadresáøi dle platforem. -% -\item[readme.html] Webovské stránky se struènými úvody a u¾iteènými -odkazy, v~rùzných jazycích. -% -\item[source] Zdrojové kódy v¹ech programù, vèetnì distribuce - \Webc{} \TeX{}u a \MF{}u. -% -\item[support] Rùzné pomocné balíky a programy. Automaticky %Implicitnì - \emph{nejsou} instalovány. Toto zahrnuje editory - a \TeX{}ová vývojová prostøedí rùzných druhù. - -% -\item[texmf] Viz \dirname{TEXMFMAIN} ní¾e. -% -\item[texmf-dist] Viz \dirname{TEXMFDIST} ní¾e. -% -\item[texmf-doc] Strom samostatné èisté dokumentace, uspoøádán podle jazykù. -% -\item[tlpkg] Skripty, programy a údaje pro správu instalace. Obsahuje -rovnì¾ neveøejné kopie Perlu a Ghostscriptu pro Windows, které jsou mimo -\TL{} neviditelné, a nový prohlí¾eè PostScriptu pro Windows PSView. -\end{ttdescription} - -\smallskip - -V~koøenovém adresáøi distribuce jsou navíc instalaèní dávky a soubory -\filename{README} (v~rùzných jazycích). - -Adresáø \dirname{texmf-doc} obsahuje dokumentaci, která není -souèástí nìjakého konkrétního balíku nebo programu. -Dokumentace programù (manuály, -man-stránky, info-soubory) jsou v~\dirname{texmf/doc}, -proto¾e programy jsou v~adresáøi \dirname{texmf}. -Dokumentace \TeX ových balíkù a formátù je -v~\dirname{texmf-dist/doc}. -K~vyhledání ve¹keré dokumentace na libovolném místì mù¾ete -pou¾ít programy \cmdname{texdoc} nebo \cmdname{texdoctk}. -Souhrnn\'e odkazy v~koøenovém souboru \OnCD{doc.html} mohou -být také u¾iteèné. - -Samotná tato pøíruèka \TL\ je v~adresáøi \dirname{texmf-doc} -a je k~dispozici v~nìkolika jazycích: - -\begin{itemize*} -\item{zjednodu¹ená èín¹tina:} \OnCD{texmf-doc/doc/chinese/texlive-zh-cn} -\item{èesko-slovenská:} \OnCD{texmf-doc/doc/czechslovak/texlive-cz} -\item{anglická:} \OnCD{texmf-doc/doc/english/texlive-en} -\item{francouzská:} \OnCD{texmf-doc/doc/french/texlive-fr} -\item{nìmecká:} \OnCD{texmf-doc/doc/german/texlive-de} -\item{polská:} \OnCD{texmf-doc/doc/polish/texlive-pl} -\item{ruská:} \OnCD{texmf-doc/doc/russian/texlive-ru} -\end{itemize*} - - -\subsection{Pøehled pøeddefinovaných stromù texmf} -\label{sec:texmftrees} - -Tento oddíl uvádí seznam v¹ech pøeddefinovaných promìnných -urèujících stromy texmf, pou¾ívaných systémem, a jejich zamý¹lený úèel, a standardní uspoøádání systému \TL. -Povel \texttt{texconfig -conf} vám uká¾e hodnoty tìchto promìnných, tedy mù¾ete jednodu¹e zjistit, -jak tyto odpovídají názvùm adresáøù ve va¹í instalaci. - -\begin{ttdescription} -\item [TEXMFMAIN] Strom obsahující ¾ivotnì dùle¾ité èásti systému, jako pomocné skripty -(napø. \verb+web2c/mktexdir+) a jiné podpùrné soubory a jejich dokumentaci. -Neobsahuje \TeX ovské formáty a balíky. -\item [TEXMFDIST] Strom obsahující hlavní sadu balíkù maker, - font\r u, atd. z~pùvodní distribuce. -\item [TEXMFLOCAL] Strom, který mohou pou¾ít administrátoøi na instalaci -doplòkových nebo upravených maker, fontù, atd., pro celý systém. -\item [TEXMFHOME] Strom, který mohou pou¾ít u¾ivatelé na svoje osobní instalace -doplòkových nebo upravených maker, fontù, atd. - Roz¹íøení této promìnné se dynamicky nastaví pro ka¾dého u¾ivatele na jeho vlastní osobní adresáø. -\item [TEXMFCONFIG] -Strom pou¾ívan\'y nástroji - \verb+texconfig+, \verb+updmap+ a \verb+fmtutil+ na ulo¾ení - modifikovaných konfiguraèních údajù. Implicitnì pod \envname{TEXMFHOME}. %$ -\item [TEXMFSYSCONFIG] Strom pou¾ívan\'y nástroji \verb+texconfig-sys+, \verb+updmap-sys+ a \verb+fmtutil-sys+ na ulo¾ení modifikovaných konfiguraèních údajù. -\item [TEXMFVAR] Strom pou¾ívan\'y programy \verb+texconfig+, - \verb+updmap+ a \verb+fmtutil+ na (cache) ulo¾ení runtime - údajù jako jsou soubory formátù a generované map-soubory. - Implicitnì pod \envname{TEXMFHOME}. %$ -\item [TEXMFSYSVAR] Strom pou¾ívan\'y programy \verb+texconfig-sys+, - \verb+updmap-sys+, \verb+fmtutil-sys+ a také \verb+tlmgr+, na (cache) ulo¾ení runtime - údajù jako jsou soubory formátù a generované map-soubory. -\end{ttdescription} - - -\noindent -Standardní struktura je: -\begin{description} - \item[system-wide root] mù¾e obsáhnout vícenásobné vydání \TL{}: - \begin{ttdescription} - \item[2007] Pøedchozí vydání. - \begin{ttdescription} - \item [...] - \end{ttdescription} - \item[2008] Nynìj¹í vydání. - \begin{ttdescription} - \item [bin] ~ - \begin{ttdescription} - \item [i386-linux] binárky systému \GNU/Linux - \item [...] - \item [universal-darwin] binárky systému \MacOSX - \item [win32] binárky systému Windows - \end{ttdescription} - \item [texmf] Toto je \envname{TEXMFMAIN}. - \item [texmf-dist] \envname{TEXMFDIST} - \item [texmf-doc] \envname{TEXMFDOC} - \item [texmf-var] \envname{TEXMFSYSVAR} - \item [texmf-config] \envname{TEXMFSYSCONFIG} - \end{ttdescription} - \item [texmf-local] \envname{TEXMFLOCAL}, zamý¹lený být zachován od vydání k~vydání. - \end{ttdescription} - \item[domovský adresáø u¾ivatele] (\texttt{\$HOME} nebo - \texttt{\%USERPROFILE\%}) - \begin{ttdescription} - \item[.texlive2007] Soukromì generované a konfiguraèní údaje pøedchozího vydání. - \item[.texlive2008] Soukromì generované a konfiguraèní údaje aktuálního vydání. - \begin{ttdescription} - \item [texmf-var] \envname{TEXMFVAR} - \item [texmf-config] \envname{TEXMFCONFIG} - \end{ttdescription} - \item[texmf] \envname{TEXMFHOME} Osobní makra - \textit{atd.} - \end{ttdescription} -\end{description} - - -\subsection{Roz¹íøení \protect\TeX{}u} -\label{sec:tex.extensions} - -Samotný \TeX{} je zmrazený, kromì ojedinìlých oprav chyb. Stále je v~\TL\ pøítomen jako program \prog{tex} a tak to zùstane v~dohledné budoucnosti. \TL{} obsahuje nìkolik roz¹íøených verzí \TeX{}u: - -\begin{description} - -\item [\eTeX] pøidává mno¾inu nových -pøíkazù (nazývaných \TeX{}ové primitivy). -\label{text:etex} -Nové pøíkazy se napøíklad týkají makroexpanze, naèítání znakù, -tøíd znaèek (marks), roz¹íøených ladicích mo¾ností -a roz¹íøení \TeXXeT{} pro obousmìrnou sazbu. Implicitnì -je \eTeX{} 100\% kompatibilní se standardním \TeX{}em. -Viz~\OnCD{texmf-dist/doc/etex/base/etex_man.pdf}. -%B% \eTeX{} je nyní sázecím programem pro \LaTeX{} i pdf\LaTeX{}. - -\item [pdf\TeX] vybudován na roz¹íøeních \eTeX{}u pøidává podporu -zápisu ve formátu \acro{PDF} stejnì jako v~\dvi{}. - -%% This is the program -%% invoked for most formats, e.g., \prog{etex}, \prog{latex}, -%% \prog{pdflatex}. -%% See \url{http://www.pdftex.org/}. -%% \OnCD{texmf/doc/pdftex/manual/} for the manual, and -%% \OnCD{texmf/doc/pdftex/manual/samplepdf/samplepdf.tex} for example usage -%% of some of its features. - -Toto je program pou¾ívaný pro vìt¹inu formátù, napøíklad, \prog{etex}, \prog{latex}, -\prog{pdflatex}. Viz \url{http://www.pdftex.org/}, -návod v~adresáøi \OnCD{texmf/doc/pdftex/manual/} a pøíklady pou¾ití nìkterých jeho vlastností v~adresáøi -\OnCD{texmf/doc/pdftex/manual/samplepdf/samplepdf.tex}. - -\item [Lua\TeX] je oznaèován za nástupce pdf\TeX/{}u, se kterým by mìl být zpìtnì kompatibilní. Mìl by také nahradit Aleph, viz dále. Zabudovaný interpret Lua (viz -\url{http://www.lua.org/}) umo¾òuje elegantn9 øe¹ení mnoha o¾ehavých -\TeX ovských problémù. Volaný povelem \filename{texlua}, funguje jako samostatný interpret Lua, a jako taký je ji¾ pou¾it v~rámci \TL. Viz \url{http://www.luatex.org/} a -\OnCD{texmf-dist/doc/luatex/luatexref-t.pdf}. - -\item [\XeTeX] pøidává podporu vstupního kódování -Unicode a OpenType- a systémových fontù, implementovaných pou¾itím zejména knihoven tøetích stran. -Viz \OnCD{texmf-dist/doc/xetex/XeTeX-reference.pdf}. - -\item [\OMEGA\ (Omega)] je zalo¾ena na Unicode. Umo¾òuje sázet v~témìø v¹ech -svìtových jazycích zároveò. Dociluje toho tzv. -pøekladovými procesy (\OMEGA{} Translation Processes, -\acro{OTP}) pro realizaci slo¾itých transformací na jakémkoliv vstupu. Viz -\OnCD{texmf/doc-dist/omega/base/doc-1.8.tex} -(dokumentace v¹ak není zcela aktuální). - -\item [Aleph] kombinuje roz¹íøení \OMEGA\ a \eTeX. -Pro minimální dokumentaci viz \OnCD{texmf-dist/doc/aleph/base}. -\end{description} - - -\subsection{Dal¹í za zmínku stojící programy na \protect\TeXLive} - -Na \TL{} najdete nìkolik èasto pou¾ívaných programù: - -\begin{cmddescription} - -\item [bibtex] podpora práce se seznamem literatury. - -\item [makeindex] vytváøení rejstøíku. Pro èe¹tinu a sloven¹tinu -v¹ak potøebujete verzi programu s~názvem \texttt{csindex} (není zatím -souèástí distribuce, je potøeba instalovat zvlá¹»). - -\item [dvips] pro konverzi \dvi{} do \PS{}. - -\item [xdvi] prohlí¾eè \dvi{} pro systém X~Window. - -\item [dvilj] \dvi{} ovladaè tiskáren HP Laser\-Jet. - -\item [dv2dt, dt2dv] pro konverzi \dvi{} do/z~ascii textu. - -\item [dviconcat, dviselect] pro kopii a vkládání stránek -do/z \dvi{} souborù. - -\item [dvipdfmx] konvertor \dvi{} do \acro{PDF}, alternativní -pøístup vedle pdf\TeX{}u zmínìného vý¹e. Srovnej balíky -\pkgname{ps4pdf} a \pkgname{pdftricks} pro dal¹í -alternativy. - -\item [psselect, psnup, \ldots] programy pro práci s~\PS{}em. - -\item [lacheck] pro kontrolu syntaxe \LaTeX{}u. - -\item [texexec, texmfstart] wrapper pro Con\TeX{}t a práci s~\acro{PDF}. - -\item [tex4ht] konvertor \TeX{}u do \acro{HTML}. - -\end{cmddescription} - - -\subsection{Fonty v~\protect\TL} -\label{sec:tl.fonts} - -\TL{} pøiná¹í mno¾ství vysoce kvalitních vektorových % ?scalable fonts. -fontù. Viz \url{http://tug.org/fonts} a \OnCD{texmf-doc/english/free-math-fonts-survey}. - - -\section{Instalace} -\label{sec:install} - -\subsection{Spu¹tìní instalaèního programu} -\label{sec:inst.start} - -Pro zaèátek si obstarejte \TK{} \DVD{} nebo si stáhnìte sí»ový instalaèní program \TL{}, -a najdìte instalaèní skript: \filename{install-tl} pro Unix, -\filename{install-tl.bat} pro Windows. - -\begin{description} -\item [Sí»ový instalátor:] stáhnìte z~\CTAN{}u, z~adresáøe \dirname{systems/texlive/tlnet}; url -\url{http://mirror.ctan.org/systems/texlive/tlnet} vás automaticky pøesmìruje na blízký, aktuální mirror. -Mù¾ete získat \filename{install-tl.zip}, který mù¾e být pou¾it pod Unixem a Windows nebo -\filename{install-unx.tar.gz}, který je podstatnì men¹í, jenom pro Unix. Po rozbalení se \filename{install-tl} a -\filename{install-tl.bat} objeví v~podadresáøi \dirname{install-tl}. - -\item [\DVD{} \TeX{} kolekce:] vejdìte do podadresáøe \dirname{texlive}. -Pod Windows by se instalátor mìl spustit automaticky po vlo¾ení \DVD. \DVD\ mù¾ete získat, kdy¾ se stanete èlenem -skupiny u¾ivatelù \TeX u (vøele doporuèujeme, -\url{http://tug.org/usergroups.html}), nebo si ho zvlá¹» zakoupíte -(\url{http://tug.org/store}), anebo si vypálíte svoje vlastní z~\ISO\ -obrazu (\url{http://tug.org/texlive/acquire.html}). - -\end{description} -Následující sekce vysvìtlují v¹echno podrobnìji. - -\subsubsection{Unix} - -\begin{figure}[tb] -\begin{boxedverbatim} -======================> TeX Live installation procedure <===================== - -=======> Note: Letters/digits in indicate menu items <======= -=======> for commands or configurable options <======= - - - Detected platform: Intel x86 with GNU/Linux - - binary systems: 1 out of 16 - - Installation scheme (scheme-full) - - Customizing installation scheme: - standard collections - language collections - 83 collections out of 84, disk space required: 1666 MB - - directories: - TEXDIR (the main TeX directory): - !! default location: /usr/local/texlive/2008 - !! is not writable, please select a different one! - TEXMFLOCAL (directory for site-wide local files): - /usr/local/texlive/texmf-local - TEXMFSYSVAR (directory for variable and automatically generated data): - /usr/local/texlive/2008/texmf-var - TEXMFSYSCONFIG (directory for local config): - /usr/local/texlive/2008/texmf-config - TEXMFHOME (directory for user-specific files): - ~/texmf - - options: - [ ] use letter size instead of A4 by default - [X] create all format files - [X] install macro/font doc tree - [X] install macro/font source tree - [ ] create symlinks in standard directories - - Install for running from DVD - -Other actions: - start installation to HD - help - quit - -Enter command: -\end{boxedverbatim} -\caption{Hlavní obrazovka textového instalaèního programu (\GNU/Linux)}\label{fig:text.main} -\end{figure} - -\begin{figure}[tb] -\tlpng{install-w32-main}{\linewidth} -\caption{Základní obrazovka \GUI{} instalaèního programu (Windows)}\label{fig:gui.main} -\end{figure} - -\noindent -Dále, \texttt{>} oznaèuje výzvu (prompt shellu); vstup u¾ivatele vstup je \Ucom{\texttt{zvýraznìn}}. -Po spu¹tìní terminálu v~Unixovském systému je nejjednodu¹¹í zpùsob: -\begin{alltt} -> \Ucom{cd /path/to/installer} -> \Ucom{perl install-tl} -\end{alltt} -(Nebo mù¾ete vyvolat \Ucom{perl /path/to/installer/install-tl}, nebo -\Ucom{./install-tl} kdy¾ je spustitelný, atd.; nechceme opakovat v¹echny tyto variace.) - -K~instalaci v~re¾imu \GUI\ (budete potøebovat modul \dirname{Perl/TK}), pou¾ijte: -\begin{alltt} -> \Ucom{perl install-tl -gui} -\end{alltt} - -Úplný seznam rùzných voleb získáte povelem: -\begin{alltt} -> \Ucom{perl install-tl -help} -\end{alltt} - -\textbf{Varování o oprávnìních Unixu:} Va¹e nastavení \code{umask} v~èase instalace bude respektováno instalaèním programem \TL{}. Proto, kdy¾ chcete, aby byla va¹e instalace pou¾itelná i jinými u¾ivateli ne¾ vámi, ujistìte se, ¾e jsou va¹e nastavení dostateènì tolerantní, napøíklad, \code{umask -002}. Dal¹í informace o nastavení \code{umask}, hledejte v~dokumentaci k~va¹emu systému. - -\subsubsection{Mac\,OS\,X} - -Jak ji¾ bylo zmínìno v~sekci~\ref{sec:tl-coll.dists}, pro \MacOSX je pøipravena samostatná distribuce, nazvaná Mac\TeX\ (\url{http://tug.org/mactex}). -Doporuèujeme pou¾ít pùvodní instalaèní program Mac\TeX\ u namísto instalátoru \TL\ -pod \MacOSX, proto¾e pùvodní (nativní) instalátor mù¾e provést nìkolik nastavení specifických pro Mac, zejména umo¾òuje snadné pøepínání mezi rùznými distribucemi \TeX u pro \MacOSX\ (Mac\TeX, gw\TeX, -Fink, MacPorts, \ldots). - -Mac\TeX\ je silnì zalo¾en na \TL, a hlavní \TeX ovská stromová struktura je pøesnì stejná. Pøidává nìkolik dal¹ích adresáøù s~dokumentací a aplikacemi specifickými pro Mac. - -\subsubsection{Windows} - -Jestli¾e pou¾íváte sí»ový instalátor, nebo instalaèní program \DVD\ se nespustí automaticky, kliknìte dvakrát na soubor \filename{install-tl.bat}. - -Mù¾ete také spustit instalaèní program z~pøíkazového øádku. Dále \texttt{>} oznaèuje prompt shellu; vstup u¾ivatele je \Ucom{\texttt{polotuèný}}. Pokus jste v~adresáøi instalaèního programu, jenom spus»te: -\begin{alltt} -> \Ucom{install-tl} -\end{alltt} - -Mù¾ete to také vyvolat zadáním absolutní polohy, jako napøíklad: -\begin{alltt} -> \Ucom{D:\bs{}texlive\bs{}install-tl} -\end{alltt} -pro \TKCS\ \DVD, za pøedpokladu, ¾e \dirname{D:} je optický disk. - -Pro instalaci v~textovém re¾imu pou¾ijte: -\begin{alltt} -> \Ucom{install-tl -no-gui} -\end{alltt} - -Pro úplný seznam rùzných voleb zadejte: -\begin{alltt} -> \Ucom{install-tl -help} -\end{alltt} - -\subsubsection{Textový instalaèní program} - -Obrázek~\ref{fig:text.main} ukazuje základní obrazovku textového re¾imu pod Unixem. - -Je to instalátor jenom s~pøíkazovým øádkem; vùbec nemá kurzorovou podporu. Napøíklad, nemù¾ete se pohybovat v~zatrhávacích rámeècích nebo vstupních polích. Jenom napí¹ete nìco (s~rozli¹ováním velikosti písma) na pøíkazovém øádku a stlaèíte klávesu Enter, poté se celá obrazovka pøepí¹e s~pøizpùsobeným obsahem. - -Rozhraní textového instalátoru je tak primitivní z~prostého dùvodu: je -navr¾ené tak, aby se dalo spustit na tolika platformách jak je to jen -mo¾né, dokonce i~v~Perlu (pro Windows je zaøazena -podmo¾ina Perlu). - -\subsubsection{Grafický instalaèní program} - -Obrázek~\ref{fig:gui.main} ukazuje grafický instalátor pod Windows. -Vìt¹ina rozdílù pøípustných voleb je patrná z~obrazovky systému Windows a z~pøedchozí obrazovky systému \GNU/Linux. - -\subsection{Spu¹tìní instalaèního programu} -\label{sec:runinstall} - -Instalátor je zamý¹lený jako co nejvíce samovysvìtlující. Nicménì podáme nìkolik poznámek o jednotlivých volbách a dílèích nabídkách: - -\subsubsection{Nabídka binárních systémù (pouze Unix)} -\label{sec:binary} - -\begin{figure}[tbh] -\begin{boxedverbatim} -Available sets of binaries: -=============================================================================== - - a [ ] alpha-linux DEC Alpha with GNU/Linux - b [ ] amd64-freebsd x86_64 with FreeBSD - c [ ] hppa-hpux HP-UX - d [ ] i386-freebsd Intel x86 with FreeBSD - e [X] i386-linux Intel x86 with GNU/Linux - f [ ] i386-openbsd Intel x86 with OpenBSD - g [ ] i386-solaris Intel x86 with Sun Solaris - h [ ] mips-irix SGI IRIX - i [ ] powerpc-aix PowerPC with AIX - j [ ] powerpc-linux PowerPC with GNU/Linux - k~[ ] sparc-linux Sparc with GNU/Linux - l [ ] sparc-solaris Sparc with Solaris - m [ ] universal-darwin universal binaries for MacOSX/Darwin - o [ ] win32 Windows - p [ ] x86_64-linux x86_64 with GNU/Linux -\end{boxedverbatim} -\caption{Nabídka binárek}\label{fig:bin.text} -\end{figure} - -Obrázek~\ref{fig:bin.text} ukazuje nabídku binárek textového re¾imu. Standardnì budou nainstalovány jenom binárky va¹í aktuální platformy. Z~této nabídky si rovnì¾ mù¾ete vybrat binárky pro jinou architekturu. Toto mù¾e být u¾iteèné, pokud sdílíte \TeX ovský strom v~síti heterogenních strojù, nebo na systému s~dvojitým zavádìcím procesem. - -\subsubsection{Volba obsahu instalace} -\label{sec:components} - -\begin{figure}[tbh] -\begin{boxedverbatim} -Select a scheme: -==================================================================== - - a [ ] TeX Live basic scheme - b [ ] TeX Live scheme for ConTeXt - c [X] TeX Live full scheme - d [ ] GUST TeX Live scheme - e [ ] GUTenberg TeX Live scheme - f [ ] TeX Live medium scheme - g [ ] TeX Live minimal scheme - h [ ] TeX Live for Omega users - i [ ] teTeX scheme - j [ ] XML typesetting scheme -\end{boxedverbatim} -\caption{Nabídka schémat}\label{fig:scheme.text} -\end{figure} - -Obrázek~\ref{fig:scheme.text} ukazuje nabídku schémat \TL; tady -vybíráte ``schéma'', co¾ je souhrn kolekcí balíkù. -Pøedvolené schéma \optname{full} nainstaluje v¹e, co je k~dispozici, av¹ak -mù¾ete také zvolit schéma \optname{basic} pro malý systém, -\optname{minimal} pro úèely testování, a schéma \optname{medium} nebo -\optname{teTeX} pro získání nìèeho mezi tím. K~dispozici jsou také rùzná -specializovaná schémata a schémata specifická pro nìkteré zemì. - -\begin{figure}[tbh] -\tlpng{stdcoll}{.7\linewidth} -\caption{Nabídka kolekcí (Linux)}\label{fig:collections.gui} -\end{figure} - -Svùj výbìr schématu mù¾ete upøesnit pomocí nabídek `standard collections' a -`language collections' (obrázek~\ref{fig:collections.gui}, ukázané pro zmìnu v~re¾imu \GUI). - -Kolekce jsou o jednu úroveò podrobnìj¹í ne¾ schémata\Dash v~podstatì, -schéma je tvoøeno nìkolika kolekcemi, kolekci tvoøí jeden nebo více -balíkù, a balík (nejni¾¹í úroveò seskupvání v~\TL) obsahuje vlastní -soubory \TeX ovských maker, soubory fontù, atd. - -Pokud chcete získat vìt¹í kontrolu ne¾ jakou poskytuje nabídka kolekcí, po instalaci mù¾ete pou¾ít program \prog{tlmgr} (viz sekci~\ref{sec:tlmgr}); jeho pou¾itím mù¾ete øídit instalaci na úrovni balíkù. - -\subsubsection{Adresáøe} -\label{sec:directories} - -Standardní uspoøádání je popsáno v~sekci~\ref{sec:texmftrees}, -\p.\pageref{sec:texmftrees}. Standardní umístìní adresáøe \dirname{TEXDIR} se li¹í pro Windows -(|%PROGRAMFILES%\texlive\2008|) a Unix -(\dirname{/usr/local/texlive/2008}). - -Hlavní dùvod pro zmìnu této pøedvolby je nedostatek práv -na zápis pro standardní umístìní. -Nemusíte být zrovna rootem nebo administrátorem, kdy¾ instalujete \TL, ale potøebujete oprávnìní na zápis do cílového adresáøe. - -Logickou alternativou je adresáø uvnitø va¹eho domovského adresáøe, zvlá¹» kdy¾ chcete být výhradním u¾ivatelem. Na naznaèení tohoto pou¾ijte `|~|', jako napøíklad `|~/texlive/2008|'. - -Doporuèujeme do názvu zaèlenit rok, co umo¾ní zachování rùzných vydání \TL{} vedle sebe. (Mù¾ete chtít vytvoøit název nezávislý na verzi, napøíklad \dirname{/usr/local/texlive-cur} pomocí symbolického odkazu, který mù¾e být pozdìji pøepsán po pøezkou¹ení nového vydání.) - -Zmìna \dirname{TEXDIR} v~instalaèním programu vyvolá také zmìny -\dirname{TEXMFLOCAL}, \dirname{TEXMFSYSVAR} a -\dirname{TEXMFSYSCONFIG}. - -\dirname{TEXMFHOME} je doporuèené umístìní osobních souborù maker nebo balíkù. Pøedvolená hodnota je |~/texmf|. Na rozdíl od \dirname{TEXDIR}, je nyní |~| uchována v~novì vytvoøených konfiguraèních souborech, proto¾e to u¾iteènì odkazuje na domovský adresáø bì¾ícího \TeX u. Expanduje se na \dirname{$HOME} pod Unixem a \verb|%USERPROFILE%| pod Windows. - -\subsubsection{Volby} -\label{sec:options} - -\begin{figure}[tbh] -\begin{boxedverbatim} -

use letter size instead of A4 by default: [ ] - create all format files: [X] - install font/macro doc tree: [X] - install font/macro source tree: [X] - create symlinks in standard directories: [ ] - binaries to: - manpages to: - info to: -\end{boxedverbatim} -\caption{Nabídka voleb (Unix)}\label{fig:options.text} -\end{figure} - -Obrázek~\ref{fig:options.text} ukazuje nabídku voleb textového re¾imu. -Zde musíme pøipomenout tøi volby: - -\begin{description} -\item[use letter size instead of A4 by default:] Obvyklý výbìr standardní velikosti papíru. -Jednotlivé dokumenty mohou deklarovat zvlá¹tní rozmìr papíru, pokud je to ¾ádoucí. - -\item[create all format files:] Pøesto¾e si vytvoøení nepotøebných formátù -vy¾aduje èas a diskový prostor pro ulo¾ení, nicménì doporuèujeme nechat -tuto volbu vyznaèenou: kdy¾ ji nevyznaèíte, budou formátové soubory -vytvoøené v~osobních stromech \dirname{TEXMFVAR} u¾ivatelù, kdy¾ budou -zapotøebí. Na tomto místì nebudou automaticky aktualizované, kdy¾ se budou -napøíklad obnovovat binárky nebo vzory dìlení v~instalaci, co mù¾e -skonèit nekompatibilními soubory formátù. - -\item[create symlinks in standard directories] (pouze Unix): -Tato volba obchází potøebu zmìny promìnných prostøedí. Bez této volby je potøebné pøidat adresáøe \TL{} do promìnnných - \envname{PATH}, \envname{MANPATH} a \envname{INFOPATH}. Budete muset pøidìlit práva na zápis cílovým adresáøùm. Není rozumné pøepsat \TeX ovský systém, který pøi¹el s~va¹ím systémem s~touto volbou. Toto je v~první øadì urèeno k~vytváøení odkazù v~standarndích adresáøích, které u¾ivatelé znají, jako napøíklad \dirname{/usr/local/bin}, které neobsahují ¾ádné \TeX ovské soubory. -\end{description} - -Teï, kdy¾ jsou v¹echna tyto nastavení podle va¹eho vkusu, mù¾ete napsat -`I' a spustit instalaèní proces. Po dokonèení pøeskoète na -sekci~\ref{sec:postinstall}, kde se dozvíte, co se má udìlat, pokud vùbec -nìco. - - -\subsubsection{Nastavení spou¹tìní z~DVD{} (pouze v~textovém re¾imu)} -\label{sec:fromdvd} - -K~výbìru této volby napi¹te `|V|'. Toto zmìní hlavní nabídku na nìco podobného jako ukazuje obrázek~\ref{fig:main.fromdvd}. -\begin{figure}[tbh] -\begin{boxedverbatim} -======================> TeX Live installation procedure <===================== - -=======> Note: Letters/digits in indicate menu items <======= -=======> for commands or configurable options <======= - - directories: - TEXDIRW (Writable root): - !! default location: /usr/local/texlive/2008 - !! is not writable, please select a different one! - TEXMFLOCAL (directory for site-wide local files): - /usr/local/texlive/texmf-local - TEXMFSYSVAR (directory for variable and automatically generated data): - /usr/local/texlive/2008/texmf-var - TEXMFSYSCONFIG (directory for local config): - /usr/local/texlive/2008/texmf-config - TEXMFHOME (directory for user-specific files): - ~/texmf - - options: - [ ] use letter size instead of A4 by default - [X] create all format files - - set up for installing to hard disk - -Other actions: - start installation for running from DVD - help - quit -\end{boxedverbatim} -\caption{Hlavní nabídka s~uspoøádáním pro volbu \optname{from DVD}}\label{fig:main.fromdvd} -\end{figure} - -V¹imnìte si zmìny: v¹echny volby k~instalaci zmizely, a èást pro adresáøe se teï zmiòuje -o~\dirname{TEXDIRW} nebo zapisovatelném koøenu. Volba pro symbolické linky také zmizela. - -Instalaèní program bude poøád vytváøet rùzné adresáøe a konfiguraèní -soubory, ale nezkopíruje \dirname{texmf}, -\dirname{texmf-dist} nebo \dirname{texmf-doc} na pevný disk. - -Poinstalaèní konfigurace pro Unix bude o nìco slo¾itej¹í, -proto¾e teï se struktura adresáøù odchyluje od standardu; viz -sekci~\ref{sec:postinstall}. - -V~dùsledku èasových ohranièení není tato volba zapracována do instalaèního programu \GUI{}, ale je k~dispozici pro oba systémy Unix a Windows. U¾ivatelé pod systémem Windows musí spustit instalátor z~pøíkazového øádku, viz sekci~\ref{sec:cmdline}. - -Oddíl \ref{sec:portable.unix} popisuje schùdnìj¹í cestu spu¹tìní \TL, která nedìlá nebo nepo¾aduje zmìny systémové konfigurace, ale ani ¾ádnou konfiguraci neumo¾òuje. - -\subsection{Instalaèní volby pøíkazového øádku} -\label{sec:cmdline} - -K~zobrazení voleb pøíkazového øádku napi¹te -\begin{alltt} -> \Ucom{install-tl -help} -\end{alltt} -K~uvedení názvu volby mohou být pou¾ity |-| nebo také |--|. -Následují nejzajímavìj¹í volby: - -\begin{ttdescription} -\item[-gui] Podle mo¾ností pou¾ijte \GUI{} instalátor. Toto si vy¾aduje modul - Perl/Tk (\url{http://tug.org/texlive/distro.html#perltk}); - pokud Perl/Tk není k~dispozici, pokraèuje instalace v~textovém re¾imu. -\item[-no-gui] Vynutí si pou¾ití instalátoru v~textovém re¾imu, dokonce i pod Windows; - mù¾ete to potøebovat, pokud chcete spustit instalaci s~volbou `from \DVD', ponìvad¾ tato - není k~dispozici v~re¾imu \GUI{}. -\item[-lang {\sl LL}] Specifikuje jazyk instalaèního rozhraní jako jeho standarní dvoupísmenový kód \textsl{LL}. -V~souèasné dobì jsou podporovány jazyky: angliètina (\texttt{en}, pøedvolený), nìmèina - (\texttt{de}), francouz¹tina (\texttt{fr}), nizozem¹tina (\texttt{nl}), pol¹tina - (\texttt{pl}), slovin¹tina (\texttt{sl}) a vietnam¹tina - (\texttt{vi}). Instalaèní program se sám pokusí urèit vhodný jazyk, ale kdy¾ sel¾e nebo kdy¾ není správný jazyk k~dispozici, pak pou¾ije angliètinu jako nouzové øe¹ení. -\item[-profile {\sl profile}] Instalaèní program v¾dycky ulo¾í soubor - \filename{texlive.profile} do \dirname{2008/tlpkg}- nebo do podadresáøe - \dirname{tlpkg} va¹í instalace. Tato volba zpùsobí, ¾e se pou¾ije - soubor \filename{texlive.profile}. - Tady je výpis: - \begin{fverbatim} -# texlive.profile written on Wed Jul 9 16:13:44 2008 UTC -# It will NOT be updated and reflects only the -# installation profile at installation time. -selected_scheme scheme-basic -TEXDIR /usr/local/texlive/2008 -TEXDIRW /usr/local/texlive/2008 -... -TEXMFSYSVAR /usr/local/texlive/2008/texmf-var -collection-basic 1 -... -option_symlinks 0 - \end{fverbatim} - Takto mù¾ete pou¾itím této volby v~dávkovém re¾imu instalovat \TeX\ na - dal¹í systémy, se stejnými volbami, jaké jste uèinili v~pùvodní instalaci. -\item [-location {\sl url/path}] Specifikuje nestandardní zdroj pro balíky; viz dále. -\end{ttdescription} - -\subsubsection{Promìnná \optname{location}} -\label{sec:location} - -Hondota promìnné \optname{location} mù¾e být adresa url s~\texttt{ftp:}, -\texttt{http:} na zaèátku, nebo \texttt{file:/} url, nebo jednoduchá cesta. -Pokud se daný argument nachází na lokální mechanice (jako cesta nebo \texttt{file:/} url), -automaticky je urèen typ instalace (komprimovaná nebo live): -pokud bude nalezen podadresáø \dirname{archive} obsahující soubory \filename{.tar.lzma}, -tak bude pou¾it, dokonce i kdy¾ budou k~dispozici také nekomprimované soubory. - -Kdy¾ je zadáno \texttt{http:} nebo \texttt{ftp:} umístìní, koncové znaky `\texttt{/}' a/nebo koncová slo¾ka `\texttt{/tlpkg}' jsou ignorovány. Napøíklad, mù¾ete si zvolit urèité zrcadlo \CTAN u nìèím jako: -\url{http://ctan.example.org/tex-archive/texlive/tlnet/2008}, -pochopitelnì s~nahrazením vhodného jména hostitele (hostname) a jeho konkrétní koøenovou cestou -\CTAN u (seznam zrcadel \CTAN u je udr¾ován na \url{http://ctan.org/mirrors}) -namísto |ctan.example.org/tex-archive|. Implicitní je automatický výbìr zrcadla, pou¾itím -\url{http://mirror.ctan.org}; v~ka¾dém pøípadì je zvolený hostitel pou¾it pro ve¹kerý download. - - -\subsection{Poinstalaèní èinnosti} -\label{sec:postinstall} - -Po instalaci se mohou hodit nìkteré dal¹í úpravy. - -\subsubsection{Windows} - -Av¹ak pod Windows se instalaèní program o~v¹e postará. - -\subsubsection{Pokud byly vytvoøeny symbolické odkazy} - -Pokud jste zvolili vytvoøení symbolických odkazù v~standardních adresáøích (zmínìných v~sekci~\ref{sec:options}), pak není potøeba editovat promìnné prostøedí. - - -\subsubsection{Promìnné prostøedí pro Unix} -\label{sec:env} - -Adresáø binárek pro va¹i platformu musí být pøidán k~vyhledávacím cestám. -Ka¾dá podporovaná platforma má svùj vlastní podadresáø pod \dirname{TEXDIR/bin}. Seznam podadresáøù a odpovídajících platforem viz na obrázku~\ref{fig:bin.text}. - -Mù¾ete rovnì¾ pøidat dokumentaèní manuálové stránky (man) a adresáøe Info k~jejich -pøíslu¹ejícím vyhledávacím cestám, kdy¾ chcete, aby je na¹ly systémové nástroje. - -Napøíklad pro Bourne-kompatibilní shell, jako je \prog{bash} a pou¾ívaný Intel x86 -GNU/Linux se standardním nastavením adresáøù, mù¾e být vhodné editovat soubor - \filename{$HOME/.profile}. - -\begin{sverbatim} -PATH=/usr/local/texlive/2008/bin/i386-linux:$PATH; export PATH -MANPATH=/usr/local/texlive/2008/texmf/doc/man:$MANPATH; export MANPATH -INFOPATH=/usr/local/texlive/2008/texmf/doc/info:$INFOPATH; export INFOPATH -\end{sverbatim} - -Pro \prog{csh} nebo \prog{tcsh} je editovaný soubor typicky \filename{$HOME/.cshrc} a -øádky k~pøidání mù¾ou vypadat jako: - -\begin{sverbatim} -setenv PATH /usr/local/texlive/2008/bin/i386-linux:$PATH -setenv MANPATH /usr/local/texlive/2008/texmf/doc/man:$MANPATH -setenv INFOPATH /usr/local/texlive/2008/texmf/doc/info:$INFOPATH -\end{sverbatim} - - -\subsubsection{Promìnné prostøedí: globální konfigurace} -\label{sec:envglobal} - -Volba, zda uèinit tyto zmìny globálnì, anebo pro u¾ivatele právì -pøidaného do systému, je na vás; existuje pøíli¹ mnoho variací mezi -systémy, kde a jak se tato nastavení provádìjí. - -Na¹e dvì rady jsou: 1)~mù¾ete chtít vyhledat soubor -\filename{/etc/manpath.config} a pokud existuje, pøidejte øádky jako - -\begin{sverbatim} -MANPATH_MAP /usr/local/texlive/2008/bin/i386-linux \ - /usr/local/texlive/2008/texmf/doc/man -\end{sverbatim} - -A 2)~vyhledejte soubor \filename{/etc/environment}, který mù¾e definovat vyhledávací cestu a dal¹í standardní promìnné prostøedí. - -\subsubsection{Pøi spu¹tìní \protect\TL{} z~DVD} - -Program \TL{} obyèejnì nahlédne do souboru \filename{texmf.cnf} pro -umístìní rùzných stromù. Hledá tento soubor v~øadì míst vztahujících se -k~jeho vlastnímu umístìní. Nicménì, toto schéma selhává, kdy¾ je program -spou¹tìn z~\DVD{}: \DVD{} je pouze ke ètení. %read-only. -Nìkteré cesty zaznamenané v~\filename{texmf.cnf} jsou známé jen bìhem -instalace, tudí¾ tento soubor nemù¾e být na \DVD{} a musí být umístìn -nìkde jinde. To si vynucuje definovat promìnnou prostøedí -\envname{TEXMFCNF}, která sdìlí programùm \TL{}, v~kterém adresáøi je -mo¾né najít tento soubor \filename{texmf.cnf}. -Pøesto je také nutné upravit promìnnou prostøedí \envname{PATH}, jak bylo -popsáno døíve. - -Na konci instalace by instalaèní program mìl vytisknout hlá¹ení o~hodnotì, -na kterou se má nastavit promìnná \envname{TEXMFCNF}. Jestli¾e jste ji -minuli: tato hodnota je \dirname{$TEXMFSYSVAR/web2c}. Na pøedvolbu -\dirname{/usr/local/texlive/2008/texmf-var/web2c} potøebujete øádky -\begin{sverbatim} -TEXMFCNF=/usr/local/texlive/2008/texmf-var/web2c; export TEXMFCNF -\end{sverbatim} -nebo, pro [t]csh: -\begin{sverbatim} -setenv TEXMFCNF /usr/local/texlive/2008/texmf-var/web2c -\end{sverbatim} - -\subsubsection{\ConTeXt{} Mark IV} - -`Starý' \ConTeXt{} by mìl skonèit. %should run out of the box. -Nový \ConTeXt{} `Mark IV' -si vy¾ádá ruèní nastavení; viz -\url{http://wiki.contextgarden.net/Running_Mark_IV}. - - -\subsubsection{Zaèleòování lokálních a osobních maker} -\label{sec:local-personal.macros} - -Toto je ji¾ implicitnì zmínìno v~sekci~\ref{sec:texmftrees}: -adresáø \dirname{TEXMFLOCAL} (standardnì \dirname{/usr/local/texlive/texmf-local} nebo -\verb|C:\Program Files\texlive\texmf-local|) -je urèen pro rozsáhlé systémové % system-wide -lokální fonty a makra; a adresáø -\dirname{TEXMFHOME} (standardnì \dirname{$HOME/texmf} nebo -\verb|%USERPROFILE%\texmf|), je pro osobní fonty a makra. - -Pro oba stromy musí být soubory umístìné v~patøièných podadresáøích; -viz \url{http://tug.org/tds} nebo nahlédni do souboru -\filename{texmf/web2c/texmf.cnf}. Napøíklad, \LaTeX{}ovský soubor tøídy % class file or -nebo balík by mìl být umístìn v~\dirname{TEXMFLOCAL/tex/latex} nebo -\dirname{TEXMFHOME/tex/latex}, nebo v~jejich podadresáøi. - -\dirname{TEXMFLOCAL} vy¾aduje aktuální databázi jmen souborù, jinak -nebudou soubory nalezeny. -Mù¾ete ji obnovit povelem \cmdname{mktexlsr} nebo pou¾ít tlaèítko -`Reinit file database' na konfiguraèní zálo¾ce \prog{tlmgr} v~re¾imu \GUI. - -\subsubsection{Zaèleòování fontù tøetích stran} - -Toto je nane¹tìstí velice komplikované a delikátní téma. -Vyhnìte se tomu, pokud nejste expert. -Prohlédnìte si nejdøíve fonty, které jsou zadarma souèástí distribuce, -viz sekci~\ref{sec:tl.fonts}. - -Mo¾nou alternativou je pou¾ití \XeTeX u (viz sekci~\ref{sec:tex.extensions}), který vám -umo¾ní pou¾ívat fonty operaèního systému bez jakékoliv instalace v~\TeX u. - - -\subsection{Testování instalace} -\label{sec:test.install} - -Po nainstalování \TL{} pøirozenì chcete -systém otestovat a zaèít vytváøet nádherné dokumenty nebo fonty. - -Tento oddíl popisuje základní postupy testování funkènosti nového -systému pod Unixem. Pod \MacOSX{} a -Windows budete patrnì spou¹tìt testy pøes u¾ivatelské grafické rozhraní -(\acro{GUI}), ale principy jsou stejné. - -\begin{enumerate} -\item Nejprve ovìøte, zda se spustí program \cmdname{tex}: - -\begin{alltt} -> \Ucom{tex -{}-version} -TeX 3.1415926 (Web2C 7.5.7) -kpathsea version 3.5.7 -... -\end{alltt} -Pokud obdr¾íte hlá¹ku s~`command not found' místo vý¹e uvedeného, nebo se -star¹í verzí, patrnì nemáte nastavený správný podadresáø -\dirname{bin} v~promìnné prostøedí \envname{PATH}. Vra»te se -k~informacím o~jejich nastavování na stranì~\pageref{sec:env}. - -\item Pøelo¾te ukázkový soubor \LaTeX{}u: -\begin{alltt} -> \Ucom{latex sample2e.tex} -> This is pdfeTeXk, Version 3.1415926... -Output written on sample2e.dvi (3 pages, 7484 bytes). -Transcript written on sample2e.log. -\end{alltt} -Pokud sel¾e nalezení souboru \filename{sample2e.tex} nebo jiných -souborù, nejspí¹e máte aktivní stará nastavení promìnných prostøedí nebo -konfiguraèních souborù; pro zaèátek doporuèujeme zru¹it nastavení v¹ech promìnných prostøedí souvisejících s~\TeX{}em. -Pro hlub¹í analýzu a dohledání problému mù¾ete kdykoliv po¾ádat -\TeX{} o detaily toho, co a kde hledá: viz \uv{Ladicí èinnosti} -na stranì~\pageref{sec:debugging}. - -\item Prohlédnìte si výsledek na obrazovce: -\begin{alltt} -> \Ucom{xdvi sample2e.dvi} -\end{alltt} -(Pod Windows je analogický pøíkaz \cmdname{dviout}.) Mìlo by se -otevøít nové okno s~pìkným dokumentem popisujícím základy -\LaTeX{}u. (Mimochodem, stojí za pøeètení, pokud zaèínáte.) -Musíte mít spu¹tìny -X~Window, aby \cmdname{xdvi} pracovalo. Pokud tomu tak není nebo máte -¹patnì nastavenou promìnnou prostøedí -\envname{DISPLAY}, dostanete chybovou hlá¹ku `Can't open display'. - -\item Vytvoøte \PS{}ový soubor pro tisk nebo prohlí¾ení: -\begin{alltt} -> \Ucom{dvips sample2e.dvi -o sample2e.ps} -\end{alltt} - -\item Vytvoøte \acro{PDF} soubor místo \dvi{}; tento pøíkaz -ze~souboru \filename{.tex} vytvoøí \acro{PDF} pøímo: -\begin{alltt} -> \Ucom{pdflatex sample2e.tex} -\end{alltt} - -\item Prohlédnìte si \acro{PDF} soubor: -\begin{alltt} -> \Ucom{gv sample2e.pdf} -\textrm{nebo:} -> \Ucom{xpdf sample2e.pdf} -\end{alltt} -Bohu¾el ani \cmdname{gv} ani \cmdname{xpdf} nejsou v~souèasné dobì na -\TL{} a musíte je instalovat separátnì. Viz -\url{http://www.gnu.org/software/gv} a -\url{http://www.foolabs.com/xpdf}. (Existuje také velké mno¾ství jiných prohlí¾eèù \acro{PDF}.) - -\item Standardní testovací soubory, které mohou být u¾iteèné kromì \filename{sample2e.tex}: - -\begin{ttdescription} -%B% \item [docstrip.tex] Vytvoøení \TeX{}ového zdroje èi dokumentace ze -%B% souboru~\samp{.dtx}. -\item [small2e.tex] Ukázkový dokument, je¹tì krat¹í ne¾ -\filename{sample2e}. -\item [testpage.tex] Test, jestli va¹e tiskárna neposunuje tiskové zrcadlo. -\item [nfssfont.tex] Pro tisk tabulek fontù a testù fontù. -\item [testfont.tex] Pro toté¾, ale pro plain \TeX{}. -\item [story.tex] Základní (plain) \TeX{}ový testovací soubor. -Musíte napsat \samp{\bs bye} na výzvu \code{*} po \samp{tex -story.tex}. -\end{ttdescription} -\end{enumerate} - -Pokud jste \TeX{}ový zaèáteèník nebo potøebujete pomoc se psaním -\TeX{}ových, respektive \LaTeX{}ových dokumentù, nav¹tivte -\url{http://tug.org/begin.html}, kde najdete úvodní informace -k~instalaci. - -\section{Sí»ové instalace} -\label{sec:netinstall} - -\TL{} byl navr¾ený pro sdílení mezi rùznými u¾ivateli, nebo dokonce pro rùzné systémy na síti. -Se standardní strukturou adresáøù se nekonfigurují ¾ádné % no hard paths are configured -pevné cesty: umístìní souborù potøebných pro programy \TL{} -je definováno relativnì k~umístìním tìchto programù. Mù¾ete to najít v~èinnosti v~konfiguraèním souboru -\filename{$TEXMFMAIN/web2c/texmf.cnf}, který obsahuje øádky jako jsou -\begin{sverbatim} -TEXMFMAIN = $SELFAUTOPARENT/texmf -... -TEXMFLOCAL = $SELFAUTOPARENT/../texmf-local -\end{sverbatim} -To znamená, ¾e jiné systémy nebo jiní u¾ivatelé potøebují pouze pøidat ke -své vyhledávací cestì adresáø binárek \TL{} pro jejich platformu. - -%By the same token, -Stejným zpùsobem mù¾ete nainstalovat \TL{} lokálnì a pak pøesunout celou hierarchii pozdìji na místo na síti. - -Pochopitelnì, u¾ivatelé pod Windows mají jiné oèekávání. Adresáø -\dirname{texmf-doc/source/texlive/texlive-common/w32client} obsahuje vzorový skript \filename{install-w32client}, -který vytváøí nastavení a nabídkové zkratky k~u¾ívání stávající instalace \TL{} na -\acro{LAN}. Pou¾ívá se to pomocí dávkového souboru -\filename{install-w32client.bat} ve stejném adresáøi. - -Víc o konfiguraci \TL{} a vyhledávání cest si mù¾ete pøeèíst v~sekci~\ref{sec:kpathsea}. - - -\section{Maximálnì mobilní \protect\TL{} na DVD a USB} -\label{sec:portable.unix} - -Volba `running from \DVD{}' (spou¹tìní z~\DVD{}) popsaná v~sekci~\ref{sec:fromdvd} -je skvìlá pro vá¹ systém, ale kdy¾ jste hostem na systému nìkoho jiného, -pak by se vám mo¾ná líbilo nìco s~nejmen¹ími vedlej¹ími úèinky. - -V~koøenovém adresáøi \TL{} \DVD, nebo v~podadresáøi \dirname{texlive} \TKCS{} \DVD, jsou skripty \filename{tl-portable} (Unix) a dávkové soubory -\filename{tl-portable.bat} (Windows), které spou¹tí shell s~nastavením prostøedí odpovídajícím pøímému pøístupu \TL{} na \DVD. - -Pøi prvním spu¹téní budou vygenerovány nìkteré soubory v~adresáøi -\dirname{~/.tlportable2008}, co¾ zabere jistý krátký èas. -Nicménì, pøi následných spou¹tìních zaène témìø okam¾itì. - -Zbytek systému si \TL{} nebude uvìdomovat. Pokud chcete, aby byl vá¹ editor informovaný o~tomto \TL, pak ho mù¾ete spustit z~druhé, paralelní, stejné \filename{tl-portable} relace. - -Skripty \filename{tl-portable} mù¾ete také pou¾ít na spu¹tìní \TL{} z~\acro{USB} klíèe. V~tomto pøípadì zkopírujte (pøinejmen¹ím) v¹echny soubory na nejvy¹¹í urovni a obsah adresáøù \dirname{bin}, \dirname{texmf}, -\dirname{texmf-dist} a \dirname{tlpkg} na klíè. To mù¾e nìjaký èas zabrat! -Pokud kopírujete na \acro{USB} klíè formátovaný jako \acro{FAT}32, nezapomeòte zru¹it %dereference -symbolické odkazy (\code{cp -L}). Adresáø \dirname{texmf-local} na klíèi -bude také nalezen a pou¾it. - -Pak spus»te skript \filename{tl-portable} z~koøenového adresáøe klíèe, jak bylo uvedeno vý¹e. -V~tom pøípadì bude skript vnímat klíè jako zapisovatelný a pou¾ije ho pro vytvoøené soubory. - - - -\section{\cmdname{tlmgr}: správa va¹í instalace} -\label{sec:tlmgr} - -\begin{figure}[tb] -\tlpng{tlmgr-gui}{\linewidth} -\caption{\prog{tlmgr} v~re¾imu \GUI. Seznam balíkù/kolekcí/schémat se uká¾e a¾ po kliknutí na tlaèítko `Load'.}\label{fig:tlmgr.gui} -\end{figure} - -\begin{figure}[tb] -\tlpng{tlmgr-config}{\linewidth} -\caption{\texttt{tlmgr} v~re¾imu GUI: konfiguraèní zálo¾ka}\label{fig:tlmgr.config} % Configuration tab -\end{figure} - -Instalaèní program nainstaluje program nazvaný \prog{tlmgr} pro správu \TL{} -po výchozí instalaci. Programy \prog{updmap}, -\prog{fmtutil} a \prog{texconfig} jsou dosud zahrnuté a zùstanou i v~budoucnosti, av¹ak preferovaným rozhraním je nyní \prog{tlmgr}. -Jeho schopnosti zahrnují: - -\begin{itemize*} -\item výpis seznamù schémat, kolekcí a balíkù; -\item instalaci, aktualizaci, zálohování, obnovení a odinstalování jednotlivých balíkù, volitelnì se zapoèítáním závislostí; % optionally taking dependencies into account; -\item vyhledávání balíkù; -\item výpis seznamu a pøidání architektur; -\item zmìna instalaèních voleb jako napøíklad velikosti papíru a umístìní zdrojù (viz sekci~\ref{sec:location}). -\end{itemize*} -\textit{Varování:} \prog{tlmgr} nebyl urèený pro nebo testovaný s~instalacemi, které jsou spou¹tìné z~\DVD. - -\subsection{GUI re¾im \cmdname{tlmgr}} -\prog{tlmgr} mù¾e být spu¹tìn v~re¾imu \GUI{} povelem -\begin{alltt} -> \Ucom{tlmgr -gui} -\end{alltt} -nebo ve Windows prostøednictvím Start menu: \texttt{Start}, \texttt{Programs}, -\texttt{TeX Live 2008}, \texttt{TeX Live Manager}. Po kliknutí na `Load' -se zobrazí seznam balíkù, které jsou k~dispozici, a nainstalovaných -balíkù\Dash poslednì zmínìné jsou oznaèeny `(i)'. Pochopitelnì se -pøedpokládá, ¾e instalaèní zdroj je platný a dosa¾itelný. -Obrázek~\ref{fig:tlmgr.config} ukazuje konfiguraèní zálo¾ku. - - -\subsection{Vzorové realizace \cmdname{tlmgr} z~pøíkazového øádku} - -Tento pøíklad pøidá nìkolik balíkù, vèetnì nového `motoru' (`engine'), z~nestandardní lokace: - -\begin{alltt} -> \Ucom{tlmgr -location http://172.16.18.1/tldev install collection-xetex xkeyval} -\end{alltt} -Vytvoøí následující výstup: -\begin{fverbatim} -install: collection-xetex -install: arabxetex -install: euenc -install: bidi -install: fontspec -install: fontwrap -install: ifxetex -install: philokalia -install: polyglossia -install: xecyr -install: xecyr.i386-linux -install: xepersian -install: xetex -install: xetexconfig -install: xetex.i386-linux -running post install action for xetex -install: xetex-def -install: xetex-pstricks -install: xetexfontinfo -install: xltxtra -install: xunicode -install: xkeyval -running mktexlsr -mktexlsr: Updating /usr/local/texlive/2008/texmf/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-config/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-dist/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-doc/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/../texmf-local/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-var/ls-R... -mktexlsr: Done. -regenerating fmtutil.cnf -running fmtutil-sys --missing -... -Transcript written on xelatex.log. -fmtutil: /usr/local/texlive/2008/texmf-var/web2c/xetex/xelatex.fmt installed. -\end{fverbatim} -Jak vidíte, \prog{tlmgr} nainstaluje závislosti a postará se o~v¹echny potøebné poinstalaèní èinnosti, vèetnì aktualizace databáze názvù souborù a (znovu)vygenerování formátù. (Tady jsme vytvoøili nové formáty pro \XeTeX.) - -Tento pøíklad instaluje nový jazyk. I toto spustí znovuvytvoøení formátù: -\begin{alltt} -> \Ucom{tlmgr install collection-langdutch} -\end{alltt} -K~popisu balíku zadejte: -\begin{alltt} -> \Ucom{tlmgr show collection-wintools} -\end{alltt} -co vytvoøí -\begin{fverbatim} -Package: collection-wintools -Category: Collection -ShortDesc: Windows support programs -LongDesc: Utilities for Windows, since they are not readily available there: - gzip, chktex, jpeg2ps, unzip, wget, xpdf. -Installed: Yes -\end{fverbatim} -Aktualizace celé va¹i instalace na nejnovìj¹í dostupné verze: -\begin{alltt} -> \Ucom{tlmgr update -all} -\end{alltt} -Pokud vás to znepokojuje, zkuste nejdøíve -\begin{alltt} -> \Ucom{tlmgr update -all -dry-run} -\end{alltt} -nebo -\begin{alltt} -> \Ucom{tlmgr update -list} -\end{alltt} -Pro úplnou dokumentaci: -\begin{alltt} -> \Ucom{tlmgr -help} -\end{alltt} - -\section{Poznámky o Windows} -\label{sec:windows} - -\TL\ má jediný instalaèní program, který bì¾í na obou systémech Windows -a Unix. Toto bylo mo¾né jenom sní¾ením podpory star¹ích verzí Windows, -proto je mo¾né instalovat \TL{} pouze na Windows 2000 a novìj¹í. - - -\subsection{Vlastnosti typické pro Windows} %Windows-specific features -\label{sec:winfeatures} - -Pod Windows dìlá instalaèní program nìkteré dodateèné vìci: -\begin{description} -\item[Nabídky a zkratky.] Je nainstalována nová polo¾ka `\TL{}' nabídky - Start, obsahující vstupy pro nìkteré programy \GUI{} - (\prog{tlmgr}, \prog{texdoctk}, prohlí¾eè PostScriptu PS\_View) - a trochu dokumentace. PS\_View také získává ikonku na pracovní plo¹e jako %a drag-and-drop - cíl pro PostScriptové soubory. -\item[Automatické nastavení promìnných prostøedí.] ®ádné ruèní konfiguraèní kroky nejsou potøebné. -\item[Odinstalátor.] Instalaèní program vytvoøí polo¾ku pro \TL{} pod nabídkou `Add/Remove - Programs'. Vztahuje se k~tomu zálo¾ka `Uninstallation' programu \prog{tlmgr}. -\end{description} - -\subsection{Dodateèný obsa¾ený software} - -\begin{figure}[tb] -\tlpng{psview}{.6\linewidth} -\caption{PS\_View: k~dispozici jsou velmi vysoká zvìt¹ení!}\label{fig:psview} -\end{figure} - - -Pro úplnost, instalace \TL{} potøebuje dal¹í balíky a programy, -které na stroji s~Windows obvykle nenajdete. - -\TL{} poskytuje chybìjící souèásti: -\begin{description} -\item[Perl a Ghostscript.] Kvùli dùle¾itosti Perlu a Ghostscriptu - zahrnuje \TL{} `skryté' kopie tìchto programù. - Programy \TL{}, které je potøebují, vìdí, kde je najdou, ale - neprozrazují jejich pøítomnost nastavením promìnných prostøedí nebo - registrù. Nejsou to úplné distribuce a nemìly by pøeká¾et ¾ádným - systémovým instalacím Perlu nebo Ghostscriptu. -\item[Nástroje pøíkazového øádku.] Øada bì¾ných Unixových programù øízených z~pøíkazového øádku je nainstalovaných pod Windows spolu s~bì¾nými binárkami \TL. Tyto zahrnují programy \cmdname{gzip}, \cmdname{chktex}, - \cmdname{jpeg2ps}, \cmdname{unzip}, \cmdname{wget} a pomùcky pøíkazového øádku %command-line utilities - ze skupiny \cmdname{xpdf}. (Samotný prohlí¾eè \cmdname{xpdf} není k~dispozici pro Windows, ale je na nìm zalo¾en prohlí¾eè \acro{PDF} Sumatra: - \url{http://blog.kowalczyk.info/software/sumatrapdf}.) -\item[\texttt{fc-cache}] pomáhá \XeTeX{}u efektivnìji zacházet s~fonty. -\item[PS\_View.] PS\_View, nový prohlí¾eè PostScriptu s~volnou (free) licencí, je také nainstalován; viz obrázek~\ref{fig:psview}. -\end{description} -\begin{description} -\item[Podpùrný adresáø \texttt{support},] ji¾ zmínìný v~sekci~\ref{sec:tld}. -Tento adresáø obsahuje rozlièné programy, které mù¾ou být u¾iteèné ve spojení s~\TeX{}em, zvlá¹tì nìkolik editorù zamìøených na \TeX{} %\TeX-aware editors -a \TeX{}ovských pomùcek (frontends). % frontends. -Software v~tomto adresáøi není pokrytý instalátorem. Tento adresáø obsahuje té¾ prohlí¾eè \dvi{} \cmdname{dviout}; viz následující sekci. -\end{description} - - -\subsection{The Dviout previewer} - -Bohu¾el toto vydání \TL{} nenabízí nainstalovaný prohlí¾eè \dvi{} souborù pro Windows. Nicménì, mù¾ete si nainstalovat \prog{dviout} od -Toshio Oshimy z~adresáøe \path{support/dviout/}, který obsahuje rovnì¾ malý soubor \filename{README} popisující instalaci a konfiguraci \prog{dviout} pro \TL. Pøeètìte si ho, prosím, peèlivì pøed instalací. - -V~první øadì, kdy¾ si prohlí¾íte soubory pomocí \cmdname{dviout}, vytvoøí tento fonty, proto¾e obrazovkové fonty nebyly nainstalovány. Po chvíli budete mít vytvoøenou vìt¹inu vámi pou¾ívaných fontù a málokdy uvidíte okno s~vytváøením fontù. -Dal¹í informace je mo¾né najít ve (velmi dobré) on-line nápovìdì. - - -\subsection{Odkazy na dodateèný software s~mo¾ností sta¾ení z~internetu} - -Url adresy nìkterých dal¹ích nástrojù, které mù¾ete mít v~úmyslu instalovat: - -\begin{description} -\item[\GS{}] \url{http://www.cs.wisc.edu/~ghost/} -\item[Perl] \url{http://www.activestate.com/} s~pomocnými balíky z~\acro{CPAN}u: \url{http://www.cpan.org/} -\item[ImageMagick] \url{http://www.imagemagick.com/} ke zpracování a konverzi grafiky -\item[NetPBM] \url{http://netpbm.sourceforge.net/} také pro grafiku -\item[\TeX{}ové editory] Máte ¹iroký výbìr a je to - individuální volba. Mo¾nosti jsou napøíklad tyto, bez zvlá¹tního uspoøádání: - \begin{itemize*} - \item \cmdname{GNU Emacs} má pro Windows nativní podporu na - \url{http://www.gnu.org/software/emacs/windows/ntemacs.html} - \item \cmdname{Emacs} s~Auc\TeX{}em pro Windows je k~dispozici na \TL{} v~adresáøi \path{support}; jeho domovská stránka je \url{http://www.gnu.org/software/auctex}. - \item \cmdname{WinShell} je dostupný na \TL{} v~adresáøi - \path|support|, jeho domovská stránka je \url{http://www.winshell.de/} - \item \cmdname{WinEdt} je shareware dostupný na \url{http://www.winedt.com/} - \item \cmdname{Vim} je volný editor do\-stup\-ný z~\url{http://www.vim.org/} - \item TeXnicCenter je volný softvér, který získáte na\\ \url{http://www.toolscenter.org/} a v~distribuci pro\TeX t. \item \cmdname{LEd} je dostupný z~\url{http://www.ctan.org/support/LEd}. - \item \cmdname{SciTE} je dostupný z~\url{http://www.scintilla.org/SciTE.html}. - \end{itemize*} -\end{description} - - -\subsection{User Profile je Home} -\label{sec:winhome} - -Windowsovský protìj¹ek domovského (home) adresáøe Unixu je adresáø -\verb|%USERPROFILE%|. Pod Windows XP a Windows 2000 je to obvykle -\verb|C:\Documents and Settings\| a pod Windows Vista -\verb|C:\Users\|. V~souboru -\filename{texmf.cnf} a obecnì pro \KPS{}, se bude \verb|~| expandovat -pøimìøenì v~obou systémech Windows a Unix. - - -\subsection{Registry Windows} -\label{sec:registry} - -Windows ukládá témìø v¹echny konfiguraèní údaje do svých registrù. Registr -obsahuje soubor hierarchicky uspoøádaných klíèù, s~nìkolika koøenovými klíèi. -Nejdùle¾itìj¹í pro instalaèní programy jsou struènì øeèeno -\path{HKEY_CURRENT_USER} a \path{HKEY_LOCAL_MACHINE}, \path{HKCU} a -\path{HKLM}. Èást \path{HKCU} registra je v~domovském adresáøi u¾ivatele (viz sekci~\ref{sec:winhome}). \path{HKLM} je obvykle v~podadresáøi adresáøe Windows. - -V~nìkterých pøípadech je mo¾né získat systémové informace z~promìnných -prostøedí, ale pro dal¹í informace, kupøíkladu umístìní zkratek, je nutné -nahlédnout do registrù. Trvalé nastavení promìnných prostøedí si rovnì¾ -vy¾aduje pøístup k~registrùm. - - -\subsection{Oprávnìní Windows} -\label{sec:winpermissions} - -V~novìj¹ích verzích Windows se dìlá rozdíl mezi bì¾nými u¾ivateli a -administrátory, kdy¾ pouze poslednì zmínìní mají volný pøístup k~celému -operaènímu systému. Ve skuteènosti mù¾ete tyto tøídy u¾ivatelù radìji -oznaèit jako neprivilegovaní u¾ivatelé a normální u¾ivatelé: být -administrátorem je pravidlo, ne výjimka. Pøesto jsme se sna¾ili uèinit -\TL{} instalovatelným bez administrativních výsad. - -Pokud je u¾ivatel administrátor, odkazy (shortcuts) se vytváøejí pro -v¹echny u¾ivatele a systémové prostøedí se upravuje. Jinak jsou odkazy a -polo¾ky nabídky vytváøeny pro aktuálního u¾ivatele a upravuje se prostøedí -u¾ivatele. Pou¾ijte volbu \optname{non-admin} pro \prog{install-tl}, pokud -upøednostòujete nastavení podle u¾ivatele dokonce jako administrátor. - -Bez ohledu na status administrátora je standardní koøenový adresáø \TL{} -navr¾ený instalaèním programem v¾dycky pod \verb|%PROGRAMFILES%|. -Instalátor stále testuje, zda je root zapisovatelný pro aktuálního -u¾ivatele. - -Problém se mù¾e vyskytnout, pokud u¾ivatel není administrátor a \TeX{} ji¾ -existuje ve vyhledávací cestì. Proto¾e skuteèná cesta se sestává ze -systémové cesty následované u¾ivatelskou cestou, nový \TL{} nikdy nezíská -pøednost. -Jako dùsledek %As a workaround, -Toto instalátor obchází vytvoøením odkazù na pøíkazový øádek -(command-prompt), ve kterém je adresáø binárek nového \TL{} -pøedøazený lokální vyhledávací cestì. Nový \TL{} bude pou¾itelný, kdy¾ -bude bì¾et v~relaci pøíkazového øádku spu¹tìné z~takového odkazu. - -\begin{otherlanguage}{slovak} -\frenchspacing -% don't use \Webc so the \uppercase in the headline works. -\section{Pou¾ívateµská príruèka ku systému Web2C} -\Webc{} obsahuje mno¾inu \TeX-príbuzných programov, t.j.\ samotný \TeX{}, -\MF{}, \MP, \BibTeX{}, atï. Je to srdce systému \TL{}. Domovská stránka \Webc{}, -s~aktuálnou príruèkou a ïal¹ími vecami, je -\url{http://tug.org/web2c}. - -Trochu histórie: originálna implementácia pochádza -od Thomasa Rokického, ktorý v~roku 1987 vyvinul prvý -\TeX{}-to-C systém zalo¾ený na zmenových súboroch systému pre Unix, ktoré -boli v~prvom rade pôvodnou prácou Howarda Trickeya a Pavla Curtisa. -Tim Morgan -sa stal spravovateµom systému a poèas jeho obdobia sa meno zmenilo -na Web-to-C\@. V~roku 1990 Karl Berry prebral túto prácu, -asistoval pri tuctoch dodatoèných príspevkov a v~roku 1997 podal -taktovku Olafovi Weberovi, ktorý ju v~roku 2006 vrátil Karlovi. - -\Webc{} systém be¾í pod Unixom, 32bitovými Windows, -\acro{MacOSX} a inými operaènými systémami. Pou¾íva originálne -\TeX{} zdrojové súbory od Knutha a ostatné základné programy napísané -v~systéme kultivovaného programovania \web{}, ktoré sú prelo¾ené do zdrojového kódu jazyka C. -Základné programy \TeX{}u sú spracované týmto spôsobom: -\begin{description} -\renewcommand{\makelabel}[1]{\descriptionlabel{\mdseries\cmdname{#1}}} -\item[bibtex] Spravovanie bibliografií. -\item[dmp] Konverzia \cmdname{troff} do MPX (\MP{} obrázky). -\item[dvicopy] Vytváranie modifikovanej kópie \dvi{} súboru. -\item[dvitomp] Konverzia \dvi{} do MPX (\MP{} obrázky). -\item[dvitype] Konverzia \dvi{} do µudsky èitateµného textu. -\item[gftodvi] Generovanie fontov pre náhµad. -\item[gftopk] Konverzia gf formátu fontov do pakovaných fontov. -\item[gftype] Konverzia gf formátu fontov do µudsky èitateµného textu. -\item[makempx] \MP{} znaèkové sádzanie. -\item[mf] \MF{} -- vytváranie rodín fontov. -\item[mft] Preddefinované \MF ové zdrojové súbory. -\item[mpost] \MP{} -- tvorba technických diagramov. -\item[mpto] \MP{} -- znaèkový výber. -\item[newer] Porovnanie modifikaèných èasov. -\item[patgen] Vytvaránie vzorov rozdeµovania slov. -\item[pktogf] Konverzia pakovaných formátov fontov do -gf formátov. -\item[pktype] Konverzia pakovaných písiem do µudsky èitateµného textu. -\item[pltotf] Konverzia `Property list' do TFM. -\item[pooltype] Zobrazovanie \singleuv{\web{} pool} súborov. -\item[tangle] Konverzia \web{} súborov do Pascalu. -\item[tex] \TeX{} -- sadzba. -\item[tftopl] Konverzia TFM do `property list'. -\item[vftovp] Konverzia virtuálneho fontu do virtuálneho `property list'. -\item[vptovf] Konverzia virtuálneho `property list' do virtuálneho fontu. -\item[weave] Konverzia \web{} súborov do \TeX u. -\end{description} -\noindent Presné funkcie a syntax týchto programov sú popísané -v~dokumentáciách jednotlivých balíkov alebo v~dokumentácii -\Webc{}. Napriek tomu, poznanie niekoµkých princípov, ktoré -platia pre celý balík programov, vám pomô¾e vy»a¾i» èo najviac -z~va¹ej \Webc{} in¹talácie. - -V¹etky programy dodr¾iavajú ¹tandardné \GNU{} voµby: - -\begin{description} -\item[\texttt{--help}] Vypisuje prehµad základného pou¾ívania. -\item[\texttt{--verbose}] Vypisuje detailnú správu spracovania. -\item[\texttt{--version}] Vypisuje informáciu o~verzii, potom skonèí. -\end{description} - -Na vyhµadávanie súborov pou¾ívajú \Webc{} programy prehµadávaciu -kni¾nicu \KPS{} (\url{http://tug.org/kpathsea}). -Táto kni¾nica pou¾íva kombináciu premenných -prostredia a niekoµkých konfiguraèných súborov na optimalizáciu -prehµadávania adresárového stromu \TeX u{}. \Webc{} zvládne -prácu s~viacerými adresárovými stromami súèasne, èo je -u¾itoèné, ak niekto chce udr¾iava» ¹tandardnú distribúciu \TeX u a jeho -lokálne a osobné roz¹írenia v~rozlièných stromoch. Na urýchlenie -vyhµadávania súborov, koreò ka¾dého stromu obsahuje súbor -\file{ls-R} so záznamom obsahujúcim meno a relatívnu cestu ku -v¹etkým súborom umiestneným pod týmto koreòom. - -\subsection{Vyhµadávanie ciest kni¾nicou Kpathsea} -\label{sec:kpathsea} - -Najprv popí¹eme v¹eobecný mechanizmus vyhµadávania ciest -kni¾nicou \KPS{}. - -\emph{Vyhµadávacou cestou} nazveme zoznam \emph{elementov cesty}, -ktorými sú v~prvom rade mená adresárov -oddelené dvojbodkou alebo bodkoèiarkou. -Vyhµadávacia cesta mô¾e pochádza» z~viacerých zdrojov. -Pri vyhµadávaní súboru \samp{my-file} podµa cesty \samp{.:/dir}, -\KPS{} skontroluje ka¾dý element cesty: najprv \file{./my-file}, -potom \file{/dir/my-file}, vracajúc prvý zodpovedajúci nájdený -prvok (alebo prípadne v¹etky zodpovedajúce prvky). - -Aby bolo dosiahnuté prispôsobenie sa konvenciám èo mo¾no najviac -operaèných systémov, na neunixových systémoch \KPS{} mô¾e pou¾íva» -oddeµovaèe názvov súborov rôzne od dvojbodky (\samp{:}) a -lomítka (\samp{/}). - -Pri kontrolovaní urèitého elementu cesty \var{p} \KPS{} najprv -overí, èi sa na naò nevz»ahuje vopred vybudovaná databáza (pozri -\singleuv{Data\-báza názvov súborov} na -strane~\pageref{sec:filename.database}), t.\,j., èi sa databáza nachádza -v~adresári, ktorý je prefixom \var{p}. Ak to tak je, ¹pecifikácia -cesty sa porovnáva s~obsahom databázy. - -Ak databáza neexistuje, alebo sa nevz»ahuje na tento element cesty, alebo -sa v~nej hµadaný súbor nevyskytuje, celý systém súborov je prehµadaný -(pokiaµ to nebolo zakázané ¹pecifikáciou zaèínajúcou \samp{!!} a -hµadaný súbor musí existova»). \KPS{} zostrojí zoznam adresárov -zodpovedajúcich tomuto elementu cesty a potom skontroluje ka¾dý -z~nich, èi sa v~òom nenachádza hµadaný súbor. - -Podmienka \singleuv{súbor musí existova»\kern1pt} sa týka napr.\ súborov typu -\samp{.vf} a vstupných súborov èítaných príkazom \TeX u \cs{openin}. -Takéto súbory nemusia existova» (napr.\ \file{cmr10.vf}) a nebolo -by dobré prehµadáva» kvôli nim celý disk. Preto, ak zabudnete -aktualizova» \file{ls-R} pri in¹talácii nového \samp{.vf} súboru, -súbor nebude nikdy nájdený. Ka¾dý element cesty sa prekontroluje: najprv -databáza, potom disk. Keï je súbor nájdený, vyhµadávanie sa zastaví -a výsledok je vrátený. - -Hoci najjednoduch¹í a najbe¾nej¹í element cesty je meno adresáru, -\KPS{} podporuje aj iné zdroje vo vyhµadávacích cestách: dedièné -(layered) ¹tandardné hodnoty, mená premenných prostredia, hodnoty -súboru \file{config}, domáce adresáre pou¾ívateµov a rekurzívne -prehµadávanie podadresárov. Preto, ak hovoríme, ¾e \KPS{} -\emph{rozbalí} element cesty, znamená to, ¾e pretransformuje v¹etky -¹pecifikácie do základného mena alebo mien adresárov. Toto je -popísané v~nasledujúcich odsekoch. - -V¹imnite si, ¾e keï je meno hµadaného súboru vyjadrené absolútne -alebo explicitne relatívne, t.\,j.\ zaèína \samp{/} alebo \samp{./} -alebo \samp{../}, \KPS{} jednoducho skontroluje, èi taký súbor -existuje. - -\ifSingleColumn -\else -\begin{figure*} -\verbatiminput{examples/ex5.tex} -\setlength{\abovecaptionskip}{0pt} - \caption{Ilustraèný príklad konfiguraèného súboru} - \label{fig:config.sample} -\end{figure*} -\fi - -\subsubsection{Zdroje cesty} -\label{sec:pathsources} - -Vyhµadávacia cesta mô¾e by» vytvorená z~rôznych zdrojov. -\KPS{} ich pou¾íva v~tomto poradí: -\begin{enumerate} -\item - Pou¾ívateµom nastavená premenná prostredia, napríklad \envname{TEXINPUTS}\@. - Premenné prostredia s~pridanou bodkou a menom programu majú prednos» pred - premennými rovnakého mena, ale bez prípony. - Napríklad, keï \samp{latex} je meno práve be¾iaceho programu, potom - premenná \envname{TEXINPUTS.latex} prepí¹e \envname{TEXINPUTS}. -\item - Programovo-¹pecifický konfiguraèný súbor, napríklad riadok - \singleuv{\texttt{S /a:/b}} v~súbore \file{config.ps} \cmdname{dvips}. -\item Konfiguraèný súbor \KPS{} \Dash{} \file{texmf.cnf}, obsahujúci riadok - ako \samp{TEXINPUTS=/c:/d} (pozri ïalej). -\item Predvolené hodnoty poèas kompilácie. -\end{enumerate} -\noindent V¹etky tieto hodnoty vyhµadávacej cesty mô¾ete prezera» -pou¾itím ladiacích mo¾ností (pozri \singleuv{Ladenie} na -strane~\pageref{sec:debugging}). - -\subsubsection{Konfiguraèné súbory} -\tolerance=3500 -\KPS{} èíta poèas behu z~\emph {konfiguraèných súborov} -s~menom \file{texmf.cnf} vyhµadávaciu cestu a ïal¹ie definície. -Vyhµadávacia cesta pou¾ívaná na hµadanie týchto súborov sa -volá \envname{TEXMFCNF} (v~predvolenom nastavení sa tento súbor -nachádza v~podadresári \file{texmf/web2c}). \emph{V¹etky} súbory -\file{texmf.cnf} vo vyhµadávacej ceste budú preèítané a definície -v~posledných naèítaných súborov majú prednos» pred definíciami -èítanými predtým. Preto pri vyhµadávacej ceste \verb|.:$TEXMF|, hodnoty -z~\file{./texmf.cnf} prepí¹u hodnoty z~\verb|$TEXMF/texmf.cnf|. -\tolerance=1500 - -\begin{itemize} -\item - Komentáre zaèínajú znakom \singleuv{\texttt{\%}} a pokraèujú do konca - riadku. -\item - Prázdne riadky sú ignorované. -\item - Znak \bs{} na konci riadku slú¾i ako pokraèovací znak, t.j.\ - nasledujúci riadok je k~nemu pripojený. Prázdne znaky na zaèiatku - pripájaných riadkov nie sú ignorované. -\item - V¹etky ostatné riadky majú tvar: -\begin{alltt} - \var{variable}[.\var{progname}] [=] \var{value} -\end{alltt}% - kde \samp{=} a prázdne znaky naokolo sú nepovinné. -\item - Meno premennej \singleuv{\texttt{\var{variable}}} mô¾e obsahova» - akékoµvek znaky okrem prázdnych znakov, \samp{=}, alebo \samp{.}, - ale obmedzi» sa na znaky \samp{A-Za-z\_} je najbezpeènej¹ie. -\item - Ak je \singleuv{\texttt{.\var{progname}}} neprázdne, definícia sa - pou¾ije iba vtedy, keï práve be¾iaci program má meno - \texttt{\var{progname}} alebo \texttt{\var{progname}.exe}. - Toto umo¾òuje napríklad ma» pre rôzne nadstavby \TeX u rôzne - vyhµadávacie cesty. -\item Hodnota \singleuv{\texttt{\var{value}}} mô¾e obsahova» akékoµvek - znaky okrem \singleuv{\texttt{\%}} a \samp{@}. Na pravej strane nie je - mo¾né pou¾i» \singleuv{\texttt{\$\var{var}.\var{prog}}}; namiesto toho - musíte pou¾i» ïal¹iu premennú. Znak \samp{;} vo - \singleuv{\texttt{\var{value}}} je prelo¾ený do \samp{:} ak sme pod - operaèným systémom Unix. Toto je u¾itoèné, keï chceme ma» jediný - \file{texmf.cnf} súbor pre systémy Unix, MSDOS a Windows. -\item - V¹etky definície sú preèítané skôr, ako sa expandujú. Preto mô¾u - existova» referencie na premenné skôr, ako sú tieto definované. -\end{itemize} -Uká¾kový úsek konfiguraèného súboru, ilustrujúci väè¹inu -týchto bodov\ifSingleColumn -\ignorespaces: -\verbatiminput{examples/ex5.tex} -\else -\space je na obrázku~\ref{fig:config.sample}. -\fi - -\subsubsection{Expanzia cesty} -\label{sec:pathexpansion} - -\KPS{} rozpoznáva urèité zvlá¹tne znaky a kon¹trukcie vo -vyhµadávacích cestách podobné tým, èo existujú v~prostrediach -unixovských interprétov príkazového riadku (shells). Ako v¹eobecný -príklad uvedieme komplexnú cestu \verb+~$USER/{foo,bar}//baz+, %$ -ktorá sa expanduje do v¹etkých podadresárov pod adresármi \file{foo} a \file{bar} -v~domovskom adresári pou¾ívateµa \texttt{\$USER}, ktorý obsahuje -adresár alebo súbor \file{baz}. Tieto kon¹trukcie sú popísané -v~ïal¹ích odsekoch. - -\subsubsection{Predvolená expanzia} -\label{sec:defaultexpansion} -\tolerance=2500 -Ak vyhµadávacia cesta s~najväè¹ou prioritou (pozri \singleuv{Zdroje cesty} -na strane~\pageref{sec:pathsources}) obsahuje \emph{dvojbodku -navy¹e} (t.j.\ zaèiatoènú, koncovú, alebo zdvojenú), \KPS{} vlo¾í na -toto miesto vyhµadávaciu cestu s~druhou najvy¹¹ou prioritou, ktorá -je definovaná. Ak táto vlo¾ená cesta obsahuje dvojbodku navy¹e, to -isté sa stane s~ïal¹ou najvýznamnej¹ou cestou. Keby sme mali -napríklad dané takéto nastavenie premennej prostredia -\tolerance=1500 -\begin{alltt} ->> \Ucom{setenv TEXINPUTS /home/karl:} -\end{alltt} -a hodnotu \code{TEXINPUTS} v~súbore \file{texmf.cnf} -\begin{alltt} - .:\$TEXMF//tex -\end{alltt} -potom koneèná hodnota pou¾itá na vyhµadávanie by bola: -\begin{alltt} - /home/karl:.:\$TEXMF//tex -\end{alltt} -Keï¾e by bolo zbytoèné vklada» predvolenú hodnotu na viac ako jedno -miesto, \KPS{} mení iba nadbytoènú \samp{:}\ a v¹etko ostatné -ponecháva na mieste. Najprv kontroluje zaèiatoènú \samp{:}, potom -koncovú \samp{:} a potom zdvojenú \samp{:}. - -\subsubsection{Expanzia zátvoriek} -U¾itoèná èrta je expanzia zátvoriek, ktorá funguje tak, ¾e -napríklad \verb+v{a,b}w+ sa expanduje na \verb+vaw:vbw+. Vnáranie je -povolené. Toto sa pou¾íva na implementáciu viacnásobných -\TeX{}ovských hierarchií, priradením hodnoty \code{\$TEXMF} -s~pou¾itím zátvoriek. Napríklad v~súbore \file{texmf.cnf} nájdete -nasledujúcu definíciu (pribli¾ne, -v~skutoènosti je tam e¹te viac stromov): -\begin{verbatim} - TEXMF = {$HOMETEXMF,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN} -\end{verbatim} -Keï potom napí¹ete nieèo podobné ako -\begin{verbatim} - TEXINPUTS = .;$TEXMF/tex// -\end{verbatim} -%$ -bude to znamena», ¾e po hµadaní v~aktuálnom adresári sa najprv -prehµadá celý -strom \code{\$HOMETEXMF/tex}, \code{\$TEXMFLOCAL/tex}, -\code{\$TEXMFVAR/tex} a \code{\$TEXMFMAIN/tex} (posledné dva -s~pou¾itím databázových súborov \file{ls-R}). Je to vhodný spôsob ako -spú¹»a» dve paralelné \TeX{} ¹truktúry, jednu nemennú -(napríklad na \CD) a druhú neustále aktualizovanú novými -verziami, akonáhle sú dostupné. Pou¾itím premennej -\code{\$TEXMF} vo v¹etkých definíciách máme istotu, ¾e sa v¾dy ako -prvý prehµadá aktuálny strom. - -\subsubsection{Expanzia podadresárov} -\label{sec:subdirectory.expansion} - -Dva alebo viac za sebou nasledujúcich znakov \samp{/} -v~elemente cesty nasledujúcom za adresárom \var{d} je nahradených v¹etkými -podadresármi \var{d}: najprv podadresármi priamo pod \var{d}, potom -podadresármi pod nimi, atï. Poradie, v~akom sú prehµadávané -podadresáre na ka¾dej úrovni, \emph{nie je ¹pecifikované}. - -Ak po \samp{//} ¹pecifikujete akékoµvek komponenty mena súboru, -pridajú sa iba pod\-adre\-sáre so zodpovedajúcimi komponentami. -Napríklad, \samp{/a//b} sa expanduje do -adresárov \file{/a/1/b}, \file{/a/2/b}, -\file{/a/1/1/b}, atï, ale nie do \file{/a/b/c} alebo \file{/a/1}. - -Viacnásobné kon¹trukcie \samp{//} v~ceste sú mo¾né, ale -pou¾itie \samp{//} na zaèiatku cesty je ignorované. - -\subsubsection{Typy ¹peciálnych znakov a ich význam: zhrnutie} -Nasledujúci zoznam zahàòa %B% význam -zvlá¹tne znaky v~konfiguraèných -súboroch \KPS{}. - -% need a wider space for the item labels here. 3em instead of 2em -\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} -\begin{description} -\item[\CODE{:}]Oddeµovaè v~¹pecifikácii cesty; na zaèiatku alebo - na konci cesty nahrádza predvolenú expanziu cesty.\par -\item[\CODE{;}]Oddeµovaè v~neunixových systémoch (správa sa ako - \samp{:}). -\item[\CODE{\$}]Expanzia premennej. -\item[\CODE{\string~}] Reprezentuje domovský adresár pou¾ívateµa. -\item[\CODE{\char`\{...\char`\}}] Expanzia zátvoriek, napr.\ - z~\verb+a{1,2}b+ sa stane \verb+a1b:a2b+. -\item[\CODE{//}] Expanzia podadresárov. (Mô¾e sa - vyskytnú» kdekoµvek v~ceste, okrem jej zaèiatku). -\item[\CODE{\%}] Zaèiatok komentáru. -\item[\CODE{\bs}] Znak pokraèovania riadku (umo¾òuje viacriadkové vstupy). -\item[\CODE{!!}] Povel na hµadanie súboru \emph{iba} v~databáze, - neprehµadáva disk. -\end{description} - -\subsection{Databázy názvov súborov} -\label{sec:filename.database} - -\KPS{} minimalizuje prístupy na disk pri vyhµadávaní. Predsa v¹ak -pri in¹taláciách s~dostatoèným mno¾stvom adresárov hµadanie súboru -v~ka¾dom mo¾nom adresári mô¾e zabra» prehnane veµa èasu (toto platí -zvlá¹» vtedy, keï musia by» prejdené stovky adresárov s~fontami). -\KPS{} preto pou¾íva externe vytvorený \singleuv{databázový} súbor -nazývaný \file{ls-R}, ktorý mapuje súbory v~adresároch a pomáha tak -vyhnú» sa vyèerpávajúcemu prehµadávaniu disku. - -Skratky mien (\file{aliases}) v~druhom databázovom súbore vám -umo¾òujú da» dodatoèné mená súborom nachádzajúcim sa -v~zozname \file{ls-R}. Toto mô¾e by» u¾itoèné pri prispôsobovaní sa -súborovým konvenciám 8.3 DOSu v~zdrojových súboroch. - -\subsubsection{Súborová databáza} -\label{sec:ls.R} - -Ako bolo vysvetlené hore, meno hlavnej databázy súborov musí -by» \file{ls-R}. Mô¾ete umiestni» jednu do koreòa ka¾dej hierarchie -\TeX u{} vo svojej in¹talácii, ktorú chcete, aby bola prehµadávaná -(predvolená je \code{\$TEXMF}); väè¹inou sa jedná iba o~jednu -hierarchiu. \KPS{} hµadá \file{ls-R} súbory podµa cesty -v~\code{TEXMFDBS}. - -Odporúèaný spôsob ako vytvori» a udr¾iava» \samp{ls-R} je spusti» -skript \code{mktexlsr} zahrnutý v~distribúcii. Je vyvolávaný -rôznymi \samp{mktex...} skriptami. Tento skript v~princípe iba -spú¹»a príkaz -\begin{alltt} -cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R -\end{alltt} -predpokladajúc, ¾e \code{ls} vá¹ho systému vytvára správny výstup -(výstup \GNU \code{ls} je v~poriadku). Aby ste sa ubezpeèili, -¾e databáza bude v¾dy aktuálna, najjednoduch¹ie je pravidelne ju -prebudováva» cez \code{cron}, -tak¾e po zmenách v~in¹talovaných -súboroch \Dash\ napríklad pri in¹talácii alebo aktualizácii balíka -\LaTeX u{} \Dash\ bude súbor \file{ls-R} automaticky aktualizovaný. - -Ak súbor nie je v~databáze nájdený, podµa predvoleného nastavenia -\KPS{} zaène vyhµadáva» na disku. Ak v¹ak urèitý element cesty -zaèína \samp{!!}, bude prehµadávaná \emph{iba} databáza, nikdy nie -disk. - -\subsubsection{kpsewhich: samostatné prehµadávanie cesty} -\label{sec:invoking.kpsewhich} - -Program \texttt{kpsewhich} vykonáva prehµadávanie cesty nezávislé -od ka¾dej aplikácie. Mô¾e by» u¾itoèný ako vyhµadávací \code{find} -program na nájdenie súborov v~hierarchiách \TeX u{} (veµmi sa -vyu¾íva v~distribuovaných \samp{mktex}\dots\ skriptoch). - -\begin{alltt} ->> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} -\end{alltt} -Voµby ¹pecifikované v~\singleuv{\texttt{\var{option}}} mô¾u zaèína» buï -\samp{-} alebo \samp{-{}-} a ka¾dá skratka, ktorá nie je viacznaèná, je -akceptovaná. - -\KPS{} pova¾uje ka¾dý element vstupného riadku, ktorý nie je -argumentom nejakej voµby, za meno súboru, ktorý hµadá, a -vracia prvý súbor, ktorý nájde. Neexistuje voµba umo¾òujúca -vráti» v¹etky súbory s~urèitým menom (na to mô¾ete pou¾i» -nástroj Unixu \samp{find}). - -Najbe¾nej¹ie voµby sú popísané ni¾¹ie. -\begin{description} -\item[\CODE{--dpi=num}]\hfill\break - Nastav rozlí¹enie na \singleuv{\texttt{\var{num}}}; toto má vplyv iba na - \samp{gf} a \samp{pk} vyhµadávanie. \samp{-D} je synonymom, kvôli - kompatibilite s~\cmdname{dvips}. Predvolená hodnota je~600. -\item[\CODE{--format=name}]\hfill\break - Nastav formát na vyhµadávanie na \singleuv{\texttt{\var{name}}}. Podµa - predvoleného nastavenia je formát uhádnutý z~mena súboru. Pre formáty, - ktoré nemajú asociovanú jednoznaènú príponu, ako napríklad podporné - súbory \MP u a konfiguraèné súbory \cmdname{dvips}, musíte - ¹pecifikova» meno ako známe pre \KPS{}, také ako - \texttt{tex} alebo \texttt{enc files}. Zoznam získate spustením - \texttt{kpsewhich -{}-help}. - -\item[\texttt{--mode=\var{string}}]\mbox{}\\ - Nastav meno módu na \singleuv{\texttt{\var{string}}}; toto má vplyv iba na - \samp{gf} a \samp{pk} vyhµadávanie. ®iadna predvolená hodnota: - ka¾dý mód bude nájdený. -\item[\texttt{--must-exist}]\mbox{}\\ - Urob v¹etko preto, aby si na¹iel súbory. Ak je to potrebné, - vrátane hµadania na disku. Normálne je v~záujme efektívnosti - prehµadávaná iba databáza \file{ls-R}. -\item[\texttt{--path=\var{string}}]\mbox{}\\ - Vyhµadávaj podµa cesty \singleuv{\texttt{\var{string}}} (oddeµovaná dvojbodkou - ako zvyèajne) namiesto hádania vyhµadávacej cesty z~mena súboru. - Podporované sú \samp{//} a v¹etky be¾né expanzie. Voµby \samp{--path} - a \samp{--format} sa vzájomne vyluèujú. -\item[\texttt{--progname=\var{name}}]\mbox{}\\ - Nastav meno programu na \singleuv{\texttt{\var{name}}}. Toto nastavenie ovplyvòuje - pou¾itie vyhµadávacej cesty cez nastavenie \singleuv{\texttt{.\var{progname}}} - v~konfiguraèných súboroch. Predvolená hodnota je \samp{kpsewhich}. -\item[\texttt{--show-path=\var{name}}]\mbox{}\\ - Zobrazí cestu pou¾itú na vyhµadávanie súboru s~typom -\singleuv{\texttt{\var{name}}}. - Mô¾e by» pou¾itá buï súborová prípona (\samp{.pk}, \samp{.vf} a pod.) - alebo meno, podobne ako vo voµbe \samp{--format}. -\item[\texttt{--debug=\var{num}}]\mbox{}\\ - Nastaví masku výberu ladiacích mo¾ností na \singleuv{\texttt{\var{num}}}. -\end{description} - -\subsubsection{Príklady pou¾itia} -\label{sec:examples-of.use} - -Pozrime sa na \KPS{} v~akcii. Za podèiarknutým príkazom nasleduje -výsledok vyhµadávania v~nasledujúcich riadkoch. -\begin{alltt} -> \Ucom{kpsewhich article.cls} -/usr/local/texmf-dist/tex/latex/base/article.cls -\end{alltt} -Hµadáme súbor \file{article.cls}. Keï¾e prípona \samp{.cls} je -jednoznaèná, nemusíme ¹pecifikova», ¾e hµadáme súbor typu \singleuv{tex} -(zdrojový súbor \TeX{}). Nájdeme ho v~podadresári -\file{tex/latex/base} pod koreòovým adresárom -\samp{TEXMF-dist}. Podobne, v¹etky nasledujúce súbory budú nájdené bez -problémov vïaka ich jednoznaènej prípone. -\begin{alltt} -> \Ucom{kpsewhich array.sty} - /usr/local/texmf-dist/tex/latex/tools/array.sty -> \Ucom{kpsewhich latin1.def} - /usr/local/texmf-dist/tex/latex/base/latin1.def -> \Ucom{kpsewhich size10.clo} - /usr/local/texmf-dist/tex/latex/base/size10.clo -> \Ucom{kpsewhich small2e.tex} - /usr/local/texmf-dist/tex/latex/base/small2e.tex -> \Ucom{kpsewhich tugboat.bib} - /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib -\end{alltt} - -Mimochodom, posledným súborom je bibliografická databáza \BibTeX u pre -èlánky \textsl{TUGBoatu}. - -\begin{alltt} -> \Ucom{kpsewhich cmr10.pk} -\end{alltt} -Bitmapové súbory fontov typu \file{.pk} sa pou¾ívajú zobrazovacími -programami ako \cmdname{dvips} a \cmdname{xdvi}. V~tomto prípade -je vrátený prázdny výsledok, keï¾e neexistujú ¾iadne vopred -generované Computer Modern \samp{.pk} súbory v~na¹om systéme -(vzhµadom na to, ¾e v~\TL{} implicitne pou¾ívame verzie Type1 ). -\begin{alltt} -> \Ucom{kpsewhich wsuipa10.pk} -\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk -\else /usr/local/texmf-var/fonts/pk/ljfour/public/ -... wsuipa/wsuipa10.600pk -\fi\end{alltt} - -Pre tieto fonty (fonetickú abecedu z~University of Washington) sme museli vygenerova»\ -\samp{.pk} súbory. Keï¾e predvolený mód \MF u v~na¹ej in¹talácii -je \texttt{ljfour} so základným rozlí¹ením 600~dpi (dots per inch), -je vrátená táto in¹tancia. -\begin{alltt} -> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} -\end{alltt} -V~tomto prípade po ¹pecifikovaní, ¾e nás zaujíma rozlí¹enie 300~dpi -(\texttt{-dpi=300}), vidíme, ¾e taký font nie je v~systéme -k~dispozícii. Programy ako \cmdname{dvips} alebo \cmdname{xdvi} -by v~tomto prípade vytvorili po¾adované \texttt{.pk} súbory, pou¾ijúc skript \cmdname{mktexpk}. - -Teraz obrá»me na¹u pozornos» na hlavièkové a konfiguraèné súbory -\cmdname{dvips}. Najprv sa pozrieme na jeden z~be¾ne pou¾ívaných -súborov, v¹eobecný prológový \file{tex.pro} na pod\-poru \TeX u{}, -potom pohµadáme konfiguraèný súbor (\file{config.ps}) a -PostScriptovú mapu fontov \file{psfonts.map} \Dash %B% as of 2004, -mapové a kódové súbory majú svoje vlastné cesty na vyhµadávanie a nové umiestnenie v~stromoch \dirname{texmf}. - -Keï¾e prípona -\samp{.ps} je ne\-jed\-no\-znaèná, musíme pre súbor \texttt{config.ps} -¹pecifikova» explicitne, o ktorý typ sa zaujímame (\optname{dvips -config}). -\begin{alltt} -> \Ucom{kpsewhich tex.pro} - /usr/local/texmf/dvips/base/tex.pro -> \Ucom{kpsewhich --format=`dvips config' config.ps} - /usr/local/texmf/dvips/config/config.ps -> \Ucom{kpsewhich psfonts.map} - /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map -\end{alltt} - -Teraz sa pozrieme na podporné súbory URW Times PostScript. - V~Berryho schéme meno pre -tieto pomenovania fontov je \uv{\texttt{utm}}. Prvý -súbor, ktorý hµadáme, je konfiguraèný súbor, ktorý obsahuje meno -mapového súboru: -\begin{alltt} -> \Ucom{kpsewhich --format="dvips config" config.utm} - /usr/local/texmf-dist/dvips/psnfss/config.utm -\end{alltt} -Obsah tohoto súboru je -\begin{alltt} - p +utm.map -\end{alltt} -èo odkazuje na súbor \file{utm.map}, ktorý ideme ïalej hµada». -\begin{alltt} -> \Ucom{kpsewhich utm.map} - /usr/local/texmf-dist/fonts/map/dvips/times/utm.map -\end{alltt} -Tento mapový súbor definuje mená súborov fontov typu Type1 -PostScript v~kolekcii URW. Jeho obsah vyzerá takto (zobrazili sme -iba jeho èas»): -\begin{alltt} - utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} -\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb -\else /usr/local/texmf-dist/fonts/type1/ -... urw/utm/utmr8a.pfb -\fi\end{alltt} - -Z~týchto príkladov by malo by» zrejmé, ako µahko mô¾ete nájs» -umiestnenie daného súboru. Toto je zvlá¹» dôle¾ité, keï máte -podozrenie, ¾e ste narazili na zlú verziu súboru, -preto¾e \cmdname{kpsewhich} emuluje vyhµadávanie -úplne rovnakým spôsobom ako skutoèný program (\TeX{}, dvips a pod). - - -\subsubsection{Ladiace èinnosti} -\label{sec:debugging} - -Niekedy je potrebné vy¹etri», ako program rozpoznáva referencie na -súbory. Aby toto bolo mo¾né vhodne uskutoèni», \KPS{} ponúka rôzne -stupne ladenia: -\begin{itemize} -\item[\texttt{\ 1}] Volania \texttt{stat} (testy súborov). Pri behu - s~aktuálnou \file{ls-R} databázou by nemal da» takmer ¾iaden výstup. -\item[\texttt{\ 2}] Referencie do ha¹ovacích tabuliek (ako \file{ls-R} - databázy, mapové súbory, konfiguraèné súbory). -\item[\texttt{\ 4}] Operácie otvárania a zatvárania súboru. -\item[\texttt{\ 8}] V¹eobecná informácia o ceste pre typy súborov - hµadaných \KPS. Toto je u¾itoèné pri zis»ovaní, kde bola definovaná - urèitá cesta pre daný súbor. -\item[\texttt{16}] Adresárový zoznam pre ka¾dý element cesty (vz»ahuje - sa iba na vyhµadávanie na disku). -\item[\texttt{32}] Vyhµadávanie súborov. -\item[\texttt{64}] Premenlivé hodnoty. -\end{itemize} -Hodnota \texttt{-1} nastaví v¹etky horeuvedené voµby, v~praxi -pravdepodobne v¾dy pou¾ijete tieto úrovne, ak budete potrebova» -akékoµvek ladenie. - -Podobne s~programom \cmdname{dvips} nastavením kombinácie -ladiacích prepínaèov mô¾ete detailne sledova», odkiaµ sa berú -pou¾ívané súbory. Aktuálny popis parametrov je mo¾né nájs» -v~\path{../texmf/doc/html/dvips/dvips_2.html}. Alternatívne, -keï súbor nie je nájdený, -ladiaca cesta ukazuje, v~ktorých adresároch program daný súbor -hµadal, èo mô¾e naznaèova», v~èom sa asi vyskytol problém. - -V¹eobecne povedané, keï¾e väè¹ina programov volá kni¾nicu \KPS{} -vnútorne, ladiace voµby je mo¾né nastavi» pomocou premennej -prostredia \envname{KPATHSEA\_DEBUG} na potrebnú kombináciu, ako je -to popísané v~horeuvedenom zozname. - -(Poznámka pre pou¾ívateµov Windows: nie je jednoduché -presmerova» v¹etky hlá¹ky v~tomto systéme do súboru. -Na diagnostick\'e úèely mô¾ete doèasne priradi»\hfill\\ -\texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log}). - - -Uva¾ujme ako príklad malý zdrojový súbor -\LaTeX u{}, \file{hello-world.tex}, ktorý obsahuje nasledujúci vstup. -\begin{verbatim} - \documentclass{article} - \begin{document} - Hello World! - \end{document} -\end{verbatim} -Tento malý súbor pou¾íva iba font \file{cmr10}, tak¾e pozrime sa, -ako \cmdname{dvips} pripravuje PostScriptový súbor (chceme pou¾i» -Type1 verziu písiem Computer Modern, preto je nastavená -voµba \texttt{-Pcms}\footnote{Od verzie \TL{}~7 nie -je nutné túto voµbu nastavova», preto¾e Type~1 fonty sú -naèítané implicitne.}. -\begin{alltt} -> \Ucom{dvips -d4100 hello-world -Pcms -o} -\end{alltt} -V~tomto prípade sme skombinovali \cmdname{dvips} ladiacu -triedu~4 (cesty k~fontom) s~expanziou elementu cesty \KPS\ -(pozri Referenèný Manuál -\cmdname{dvips}, \OnCD{texmf/doc/html/dvips/dvips_toc.html}). -%\ifSingleColumn -%We get something -%like the following (we have rearranged the output for easier display): -%\begin{alltt}\small -%\input{examples/ex6.tex} -%\end{alltt} -%\else -Výstup, trochu preusporiadaný, je zobrazený na -obrázku~\ref{fig:dvipsdbga}. - -\begin{figure*}[tp] -\centering -\input{examples/ex6a.tex} -\caption{Hµadanie konfiguraèných súborov}\label{fig:dvipsdbga} - -\bigskip - -\input{examples/ex6b.tex} -\caption{Hµadanie \singleuv{prolog} súboru}\label{fig:dvipsdbgb} - -\bigskip - -\input{examples/ex6c.tex} -\caption{Hµadanie súboru fontu}\label{fig:dvipsdbgc} -\end{figure*} - - -%\input{examples/ex6skfromtl6.tex} % TODO: Janka -- treba aktualizovat -% z ../examples/ex6*.tex - -\cmdname{dvips} zaène lokáciou svojich pracovných súborov. Najprv je -nájdený \file{texmf.cnf}, ktorý obsahuje definície vyhµadávacích -ciest ostatných súborov, potom databáza súborov \file{ls-R} (na -optimalizáciu vyhµadávania súborov) a skratky mien súborov -(\file{aliases}), èo robí mo¾ným deklarova» viacero mien (napr.\ -krátke meno typu \singleuv{8.3} ako v~\acro{DOS}e a dlh¹iu prirodzenej¹iu -verziu) pre ten istý súbor. Potom \cmdname{dvips} pokraèuje -v~hµadaní v¹eobecného konfiguraèného súboru \file{config.ps} skôr, -ako zaène hµada» súbor nastavení \file{.dvipsrc} (ktorý, v~tomto -prípade, \emph{nie je nájdený}). Nakoniec, \cmdname{dvips} nájde -konfiguraèný súbor pre font Computer Modern PostScript, -\file{config.cms} (toto bolo iniciované voµbou\texttt{-Pcms} -v~príkaze \cmdname{dvips}). Tento súbor obsahuje zoznam \uv{mapových} -súborov, ktoré definujú vz»ah medzi menami fontov v~\TeX u, -PostScripte a systéme súborov. -\begin{alltt} -> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} - p +ams.map - p +cms.map - p +cmbkm.map - p +amsbkm.map -\end{alltt} -\cmdname{dvips} preto pokraèuje v~hµadaní v¹etkých týchto súborov plus -v¹eobecného mapového súboru \file{psfonts.map}, ktorý sa naèíta -v¾dy (obsahuje deklarácie be¾ne pou¾ívaných PostScriptových fontov; -pozri poslednú èas» sekcie~\ref{sec:examples-of.use}, kde sa nachádza -viac detailov o narábaní s~mapovými súbormi PostScriptu). - -V~tomto bode sa \cmdname{dvips} identifikuje -pou¾ívateµovi\,\ldots -\begin{alltt}\ifSingleColumn -This is dvips 5.78 Copyright 1998 Radical Eye Software - (www.radicaleye.com) -\else\small{}This is dvips 5.78 Copyright 1998 Radical Eye ... -\fi\end{alltt}% decided to accept slight overrun in tub case - -\ifSingleColumn -\noindent\ldots potom pokraèuje v~hµadaní prológového súboru -\file{texc.pro}: - -\begin{alltt}\small -kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro -\end{alltt} -\else -potom pokraèuje v~hµadaní prológového súboru -\file{texc.pro} (pozri obrázok~\ref{fig:dvipsdbgb}). -\fi -Po nájdení tohoto súboru, \cmdname{dvips} vypí¹e na výstup dátum a -èas a informuje nás, ¾e vygeneruje súbor \file{hello-world.ps}, ¾e -potrebuje súbor s~fontom \file{cmr10}, ktorý bude deklarovaný ako -\uv{rezidentný}: -\begin{alltt}\small -TeX output 1998.02.26:1204' -> hello-world.ps -Defining font () cmr10 at 10.0pt -Font cmr10 is resident. -\end{alltt} -Teraz sa rozbehne hµadanie súboru \file{cmr10.tfm}, ktorý je -nájdený, potom je referencovaných e¹te niekoµko prológových súborov -(nezobrazené) a nakoniec je nájdená in¹tancia fontu -Type1, \file{cmr10.pfb}, ktorá je pridaná do výstupného súboru -(pozri posledný riadok). -\begin{alltt}\small -kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, - path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: - /var/tex/fonts/tfm//). -kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm -kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, - ... - -kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb -[1] -\end{alltt} - -\subsection{Mo¾nosti nastavenia za behu programu} -Ïal¹ou z~pekných èàt distribúcie \Webc{} je mo¾nos» kontroly -mno¾stva pamä»ových parametrov (najmä veµkosti polí) za behu -prostredníctvom súboru \file{texmf.cnf}, -ktorý èíta kni¾nica \KPS{}. Nastavenia v¹etkých parametrov mô¾ete -nájs» v~èasti~3 tohto súboru. Najdôle¾itej¹ie riadiace -premenné (èísla riadkov sa vz»ahujú na súbor \file{texmf.cnf}): - -\begin{description} -\item[\texttt{main\_memory}] - Celkový poèet dostupných slov v~pamäti pre \TeX{}, \MF{} a \MP. - Musíte vytvori» nový formátový súbor pre ka¾dé odli¹né nastavenie. - Napríklad mô¾ete vygenerova» \uv{obrovskú} verziu \TeX u{} - a zavola» súbor s~formátom \texttt{hugetex.fmt}. S~po\-u¾itím - ¹tandardnej ¹pecifikácie mena programu pou¾ívaného kni¾nicou - \KPS{}, konkrétna hodnota premennej \texttt{main\_memory} sa naèíta zo - súboru \file{texmf.cnf}. - %B% (porovnaj v¹eobecnú hodnotu a \uv{obrovskú} hodnotu, ktorá sa in¹tancuje cez \texttt{hugetex}, atï.). -\item[\texttt{extra\_mem\_bot}] - Dodatoèný priestor pre \uv{veµké} dátové ¹truktúry \TeX u{}: - \uv{boxy}, \uv{glue}, \uv{break\-point(y)} a podobne. - Je to u¾itoèné hlavne ak pou¾ívate \PiCTeX{}. -%%PS (riadok 300). -\item[\texttt{font\_mem\_size}] - Poèet dostupných slov pre informáciu o fontoch v~\TeX u. Toto je - viac-menej celková veµkos» v¹etkých preèítaných \acro{TFM} súborov. -\item[\texttt{hash\_extra}] - Dodatoèný priestor pre ha¹ovaciu tabuµku mien riadiacej sekvencie. - Len $\approx$10\,000 riadiacich sekvencií mô¾e by» ulo¾ených v~hlavnej - ha¹ovacej tabuµke; ak máte veµkú knihu s~mnohými krí¾ovými odkazmi, - toto nemusí staèi». Implicitná hodnota \texttt{hash\_extra} je \texttt{50000}. - %B% Vidíte, ¾e obidve volania programov \cmdname{hugetex} a \cmdname{pdftex} po¾adujú - %B% dodatoèných 15\,000 riadiacich sekvencií (preddefinovaná hodnota - %B% hash\_extra je nula). -\end{description} - -Samozrejme, tento prvok nemô¾e nahradi» naozajstné dynamické polia -a alokácie pamäte, ale keï¾e tieto sa veµmi »a¾ko implementujú -v~súèasnej verzii \TeX u, tieto parametre poèas behu programu -poskytujú praktický kompromis, ktorý dovoµuje aspoò nejakú -flexi\-bilitu. -\end{otherlanguage} - -\begin{comment} -\section{Pøeklad pro novou unixovou platformu} - -Pokud pou¾íváte platformu, pro kterou neposkytujeme binárky, nezbude vám -nic jiného, ne¾ si je vytvoøit ze zdrojákù sami. -Není to tak tì¾ké, jak se traduje èi zdá. V¹e, co je tøeba, najdete -v~adresáøi \texttt{source} distribuce. - -\subsection{Pøedpoklady úspìchu} - -Budete potøebovat alespoò 100~Mebibytù diskového prostoru na kompilaci -celého \TeX{}u a podpùrných programù. Budete také potøebovat kompilátor -\acro{ANSI}~C, program \cmdname{make}, lexikální analyzátor a generátor -pøekladaèe. Doporuèujeme \GNU{} verze tìchto programù -(\cmdname{gcc}, \GNU \cmdname{make}, \cmdname{m4}, \cmdname{flex}, -\cmdname{bison}). Mo¾ná uspìjete i s~jinými verzemi kompilátoru~C, -programu \cmdname{make} a dal¹ích programù, ale budete potøebovat -dobrou znalost kompilace unixových programù pro øe¹ení kolizí. - -Také pøíkaz \texttt{uname} musí vracet rozumné hodnoty. - - -\subsection{Konfigurace} - -Pro zaèátek proveïte normální instalaci \TL{} na vá¹ disk (viz -oddíl~\ref{sec:install.disk} na -stranì~\pageref{sec:install.disk}). Mù¾ete pøeskoèit instalaci -v¹ech pøedkompilovaných binárek. - -Potom rozbalte zdroje z~komprimovaného \texttt{tar} archívu z~adresáøe -\dirname{source} na svùj disk a pøejdìte do adresáøe, kam jste zdroje -rozbalili. - -Potom spus»te program \cmdname{configure} napøíklad takto: -\begin{alltt} -> \Ucom{sh configure -prefix=/usr/local/TeX} -\end{alltt} - -Adresáø udaný pøepínaèem \optname{-prefix} je ten, kam jste instalovali -pomocný texmf strom; struktura adresáøù bude jak je popsáno ní¾e (pøièem¾ -\$TEXDIR je adresáø, který jste zvolili): - -\noindent -\begin{tabularx}{\textwidth}{@{}>{\ttfamily}lX@{}} - \dirname{$TEXDIR/share/texmf} & hlavní strom s~fonty, makry, atp.\\ - \dirname{$TEXDIR/man} & unixové manuálové stránky\\ - \dirname{$TEXDIR/info} & \GNU style Info manuály\\ - \dirname{$TEXDIR/bin/$PLATFORM} & binárky -\end{tabularx} -%$ - -Pokud chcete zru¹it extra úroveò adresáøù \dirname{$PLATFORM} pro ka¾dou -platformu, t.j.\ ulo¾it binárky do adresáøe \dirname{$TEXDIR/bin}, -specifikujte volbu \verb|--disable-multiplatform| pro \cmdname{configure}. - -Podívejte se na výstup pøíkazu \verb|./configure --help| pro popis -dal¹ích pøepínaèù, které mù¾ete chtít pou¾ít. Napøíklad mù¾ete chtít -vynechat pøeklad \OMEGA{}y èi \eTeX{}u. - - -\subsection{Spu¹tìní \cmdname{make}} - -Ovìøte, zda promìnná prostøedí nebo volba \texttt{noclobber} není nastavena. -Potom spus»te hlavní \cmdname{make} takto: -\begin{alltt} -> \Ucom{make world} -\end{alltt} -a dejte si chvíli oddechu\ldots - -Pøípadnì si mù¾ete zaznamenat v¹echen výstup takto: -\begin{alltt} -> \Ucom{sh -c \string"make world >world.log 2>\&1\string" \&} -\end{alltt} - -Pøedtím ne¾ uvìøíte, ¾e v¹echno je v~poøádku, zkontrolujte -logovací soubor na chyby: \GNU \cmdname{make} v¾dy pou¾ívá øetìzec -\samp{***}, kdykoliv pøíkaz sel¾e. Také zkontrolujte, zda v¹echny programy -byly opravdu pøelo¾eny: - -\begin{alltt} -> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} -> \Ucom{ls | wc} -\end{alltt} -Výsledkem by mìlo být pøes 200 programù (mù¾ete zkontrolovat pøesný -poèet s~adresáøi \dirname{bin} na~distribuèním médiu). - -Pro závìreèný \texttt{make install} budete potøebovat rootovské -oprávnìní, tak¾e mù¾ete rozdìlit \samp{make world} na dvì èásti: -\begin{alltt} -> \Ucom{make all} -> \Ucom{su} -> \Ucom{make install strip} -\end{alltt} - -Poté, co instalujete v¹echny binárky, mìli byste provést -normální postinstalaèní proceduru, jak je popsána -v~oddíle~\ref{sec:postinstall} -na stranì~\pageref{sec:postinstall}. - -Kdy¾ budete chtít zpøístupnit svoje binárky ostatním, -prosíme kontaktujte nás. -R\'adi je umístíme na webov\'e stránky \TL. -\end{comment} - -\section{Podìkování} - -\TL{} je výsledkem spoleèného úsilí témìø v¹ech skupin u¾ivatelù \TeX u. -Toto vydání editoval \TL{} Karl Berry. -Seznam ostatních hlavních pøisp\v{e}vatelù, minulých i souèasných, následuje. Dìkujeme: - -%B% Toto vydání \TL{} je editováno Sebastianem Rahtzem, pøièem¾ hlavní -%B% pøispìvatel byl Fabrice Popineau, který tvrdì pracoval na podpoøe -%B% Windows (zvlá¹tì na setupu!) a pøispìl mnoha rùznými zpùsoby a nápady, -%B% radami a kódem. Staszek Wawrykiewicz byl hlavní testér distribuce -%B% a koordinoval pøíspìvky z~Polska. - -%B% Kaja Christiansen provádìla neúnavnì opakované -%B% rekompilace na rùzných unixových platformách. Vladimir Volovich odvedl -%B% vynikající práci na vyèi¹tìní zdrojových textù a provedl mnohá -%B% vylep¹ení, zatímco Gerben Wierda dìlal ve¹kerou práci pro \MacOSX. - -\begin{itemize*} -\item Anglickému, nìmeckému, holandskému a polskému sdru¾ení -u¾ivatelù \TeX{}u (\acro{TUG}, \acro{DANTE} e.V., -\acro{NTG} resp. \acro{GUST}), kte\v r\'i spoleènì zajistily -nezbytnou technickou a administrativní infrastrukturu. -Pøipojte se, prosím, k~\TeX ovskému sdru¾ení ve va¹í blizkosti! -(Viz \url{http://tug.org/usergroups.html}.) - -\item Týmu \acro{CTAN}u, nejpozoruhodnìj¹ím Robinu Fairbairnsovi, Jimu Hef{}feronovi -a Raineru Sch\"opfovi, který distribuuje obrazy \TL{} a -poskytuje spoleènou infrastrukturu pro aktualizaci balíkù, -na kterých je \TL{} závislý. - -\item Peteru Breitenlohnerovi a \eTeX\ týmu, kteøí poskytují -stabilní základ budoucnosti \TeX u, a výslovnì Peteru za hvìzdnou pomoc s~pou¾íváním osobních nástrojù GNU v~celém \TL.. - -%B% \item Karlu Berrymu, který poskytl pùvodní distribuci \Webc{}, a -%B% pokraèoval v~poskytování cenných rad, povzbuzení a pomocí. - -%B% \item Mimi Burbankové, která zajistila na Florida State University -%B% School of Computational Science and Information Technology pøístup -%B% k~øadì rùzných poèítaèù rùzných platforem pro pøeklad -%B% \TeX{}ových binárek a distribuce testovala, kdykoliv to bylo potøeba. - -\item Thomasi Esserovi, za pøekrásný balík \teTeX{}, bez nìho¾ by \TL{} -nikdy neexistovala. - -\item Michelu Goossensovi, který je spoluautorem pùvodní dokumentace. - -\item Eitanu Gurarimu, jeho¾ \TeX{}4ht bylo pou¾ito pro -\HTML{} verzi této dokumentace a který obratem -pracoval neúnavnì na jeho roz¹íøeních. - -\item \Thanh ovi, Martinu Schr\"oderovi a pdf\TeX\ týmu (\url{http://pdftex.org}) -za pokraèující roz¹iøování mo¾ností \TeX u. - -\item Hansi Hagenovi, za mnohá testování a pøípravu jeho formátu \ConTeXt\ -(\url{http://pragma-ade.com}) pracujícího uvnitø systému \TL. - -\item Hartmutu Henkelovi, za významný pøíspìvek k~vývoji -pdf\TeX u, Lua\TeX u a více. - -\item Taco Hoekwaterovi, za úsilí pøi obnovení vývoje \MP u i -samotného (Lua)\TeX{}u (\url{http://luatex.org}) a za zaèlenìní \ConTeXt{}u do systému \TL. - -\item Paw{\l}u Jackowsk\'emu, za windowsový instalátor \cmdname{tlpm}, -a Tomaszi {\L}uczakovi, za \cmdname{tlpmgui}, pou¾ívaný v~pøedchozích vydáních. - -\item Akirovi Kakuto, za poskytnutí windowsovských binárek -z~jeho distribuce \acro{W32TEX} pro japonský \TeX{} -(\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}) a za mno¾ství dal¹ích pøíspìvkù. - -\item Jonathanu Kew a \acro{SIL}, za významný -nový vývoj \XeTeX{}u a za èas a trápení pøi jeho integraci do \TL{}, právì tak jako za výchozí verzi instalaèního programu Mac\TeX. - -\item Dicku Kochovi, za údr¾bu Mac\TeX{}u (\url{http://tug.org/mactex}) -ve velmi blízkém tandemu s~\TL{}, a za jeho skvìlé veselí pøitom. % for his great good cheer in doing so. - -\item Reinhardovi Kotuchovi za dùle¾itý pøíspìvek k~infrastruktuøe a instalaènímu programu \TL{} 2008, rovnì¾ za úsilí pøi výzkumu Windows, za skript \texttt{getnonfreefonts} a dal¹í. - -\item Siepu Kroonenbergovi, rovnì¾ also za dùle¾itý pøíspìvek k~infrastruktuøe a instalaènímu programu \TL{} 2008, zvlá¹tì pod Windows a za mno¾ství práce pøi aktualizaci této pøíruèky, popisující nové vlastnosti. - -\item Petru Ol¹ákovi, který koordinoval a kontroloval velmi peèlivì -èeskou a slovenskou podporu na \TeXLive. - -\item Toshio Oshima za jeho windowsový prohlí¾eè \cmdname{dviout}. - -\item Manueli P\'egouri\'e-Gonnardovi, za pomoc pøi aktualizaci balíkù, -vylep¹ení dokumentace a rozvoj dokumentu \cmdname{tldoc}. - -\item Fabrice Popineau, za pùvodní podporu Windows na \TL{} a za francouzskou dokumentaci. - -\item Norbertovi Preiningovi, pøednímu architektovi infrastruktury a instalaèního programu \TL{} 2008 a také za koordinaci Debian verze \TL{} (spoleènì s~Frankem K\"usterem), -za mnohé prùbì¾né návrhy na zlep¹ení. - -\item Sebastian Rahtz, za pùvodní vytvoøení systému \TL{} a za jeho údr¾bu po mnoho let. - -\item Vladimir Volovich, za významnou pomoc s~portováním % with porting -a jinými problémy údr¾by, obzvlá¹tì za to, ¾e udìlal realizovatelným zahrnutí \cmdname{xindy}. - -\item Staszku Wawrykiewiczovi, hlavnímu testérovi v¹eho na \TL{} a -koordinátorovi mnoha dùle¾itých polských pøíspìvkù: fontù, windowsové instalace a dal¹ích. - -\item Olafu Weberovi, pro jeho peèlivou údr¾bu \Webc. - -\item Gerbenu Wierdovi, za vytvoøení a údr¾bu podpory \MacOSX\ a -za mnohou integraci a testování. - -\item Grahamu Williamsovi, na jeho¾ práci na katalogu \TeX{}ovských balíkù závisíme. - -\end{itemize*} - -Tvùrci binárek: -Tigran Aivazian (\pkgname{x86\_64-linux}), -Tim Arnold (\pkgname{hppa-hpux}), -Randy Au (\pkgname{amd64-freebsd}), -Edd Barrett (\pkgname{i386-openbsd}), -Karl Berry (\pkgname{i386-linux}), -Akira Kakuto (\pkgname{win32}), -Dick Koch (\pkgname{universal-darwin}), -Manfred Lotz (\pkgname{i386-freebsd}), -Norbert Preining (\pkgname{alpha-linux}), -Arthur Reutenauer (\pkgname{sparc-linux}), -Thomas Schmitz (\pkgname{powerpc-linux}), -Apostolos Syropoulos (\pkgname{i386-solaris}), -Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-solaris}), -Olaf Weber (\pkgname{mips-irix}). -Pro informaci o procesu budování \TL{}, viz -\url{http://tug.org/texlive/build.html}. - -Obnova dokumentace a pøekladù: -Karl Berry (anglický), -Daniel Flipo (francouzský), -Klaus H\"oppner (nìmecký), -Petr Sojka \& Ján Bu¹a (èesko\slash slovenský),% -\footnote{Ke korektuøe èeského a slovenského pøekladu pøispìli -v~letech 2003--2007 kromì autorù Jaromír Kuben, Milan Matlák, Tomá¹ Ob¹ívaè, -Tomá¹ Pole¹ovský, Libor ©karvada, Zdenìk Wagner a dal¹í. -Libor \v Skarvada korigoval i leto\v sn\'i verzi.} -Boris Veytsman (ruský), -Staszek Wawrykiewicz (polský). -Webovská stránka dokumentace \TL{} je \url{http://tug.org/texlive/doc.html}. -%B% Dále Gerhard Wilhelms, Volker Schaa, Fabrice Popineau, Janka -%B% Chlebíková, Petra Sojková, Staszek Wawrykiewicz, -%B% Erik Frambach a Ulrik Vieth laskavì pøelo¾ili v~rùzných -%B% obdobích dokumentaci do svých mateøských jazykù a poskytli -%B% vítanou zpìtnou reakci. - -Samozøejmì, nejdùle¾itej¹í podìkování patøí Donaldu Knuthovi, -pøedev¹ím za vymy¹lení \TeX u a také za to, ¾e ho vìnoval svìtu. - -\section{Historie vydání} -\label{sec:history} - -\subsection{Minulost} - -Diskuse zaèala koncem roku 1993, kdy holandská skupina u¾ivatelù \TeX{}u -NTG zaèala práci na \CD{} 4All\TeX{} pro u¾ivatele \acro{MS-DOS}u, doufajíc, -¾e doba nazrála pro vydání jednoho \CD{} pro v¹echny -systémy. Byl to na svou dobu pøíli¹ ambiciózní cíl, ale -nenastartoval jen velmi úspì¹né 4All\TeX{} \CD{}, ale také -pracovní skupinu \acro{TUG}u o \emph{\TeX{} Directory Structure} -(\url{http://tug.org/tds}), která specifikovala, -jak vytvoøit konzistentní a spravovatelnou -kolekci \TeX{}ových souborù. Kompletní draft \TDS{} byl publikován -v~prosincovém èísle èasopisu \textsl{TUGboat} v~roce 1995 a -hned ze zaèátku bylo jasné, ¾e jedním z~¾ádaných produktù bude -vzorová struktura \CD{}. Distribuce, kterou nyní máte, je pøímým -výstupem práce této pracovní skupiny. Evidentní úspìch \CD{} 4All\TeX{} -ukázal, ¾e i unixoví u¾ivatelé by tou¾ili po podobnì jednoduchém -systému, a to je také jedno z~hlavních aktiv~\TeXLive. - -Nejprve jsme vytvoøili unixové \TDS{} \CD{} na podzim -1995 a rychle identifikovali \teTeX{} Thomase Essera -jako ideální systém, jeliko¾ ji¾ mìl multi\-platformní -podporu a byl koncipován s~perspektivou -p\v renositelnosti. Thomas souhlasil s~pomocí a seriózní práce zapoèala -zaèátkem roku 1996. První vydání se uskuteènilo -v~kvìtnu 1996. Zaèátkem 1997 Karl Berry dokonèil nové hlavní -vydání \Webc, které obsahovalo témìø v¹echny vlastnosti, -které Thomas Esser pøidal do \teTeX{}u, a tak jsme se rozhodli -druhé vydání \CD{} postavit na standardním -\Webc, s~pøidáním skriptu \texttt{texconfig} z~\teTeX{}u. -Tøetí vydání \CD{} bylo zalo¾eno na dal¹í revizi -\Webc, 7.2, provedené Olafem Weberem; a jeliko¾ zároveò -byla hotova nová verze \teTeX{}u, \TL{} obsahoval -témìø v¹echna její vylep¹ení. -Podobnì ètvrté vydání pou¾ívalo novou -verzi \teTeX{}u a nové vydání \Webc{} (7.3). -\TL{} nyní obsahuje i kompletní systém pro Windows. - -Pro páté vydání (bøezen 2000) bylo mnoho èástí \CD{} revidováno -a zkontrolováno a byly aktualizovány stovky -balíkù. Detaily o balících byly ulo¾eny v~souborech \acro{XML}. -Ale hlavní zmìnou pro \TeX\ Live~5 bylo vynìtí -softwaru, na kterém byla jakákoliv omezení na ¹íøení -(non-free software). V¹e ulo¾ené na \TL{} je nyní -sluèitelné s~tzv.\ `Debian Free Software Guide\-lines' -(\url{http://www.debian.org/intro/free}); udìlali jsme v¹e mo¾né, -abychom zkontrolovali licenèní podmínky v¹ech balíkù, -ale budeme vdìèni za upozornìní na jakékoli chyby. - -©esté vydání (èervenec 2001) mìlo aktualizovaného materiálu -je¹tì více. Hlavní zmìnou byl nový instalaèní pøístup: -u¾ivatel mù¾e volit instalaèní kolekce. -Byly kompletnì reorganizovány jazykové kolekce, -tak¾e jejich výbìrem se instalují -nejen makra, fonty, ale je také pøipraven odpovídající -soubor \texttt{language.dat}. - -Sedmé vydání v~roce 2002 mìlo podstatné roz¹íøení v~pøidání -podpory \MacOSX{}, kromì mno¾ství aktualizací balíkù a programù. -Dùle¾itým cílem byla opìtná integrace s~\teTeX{}em -a korekce odchylek z~pátého a ¹estého vydání. - -\subsubsection{2003} - -V~roce 2003 se neustálou smr¹tí oprav a roz¹íøení stalo to, ¾e -velikost \TL{} ji¾ neumo¾nila jeho smìstnání -na jedno \CD{}, a tak do¹lo k~rozdìlení na tøi rùzné distribuce -(viz oddíl~\ref{sec:tl-coll.dists} na -stranì~\pageref{sec:tl-coll.dists}). Navíc: - -\begin{itemize*} -\item Na ¾ádost \LaTeX{} týmu jsme zmìnili standardní pøíkazy - \cmdname{latex} a \cmdname{pdflatex} tak, ¾e nyní pou¾ívají - \eTeX{} (viz strana~\pageref{text:etex}). -\item Byly pøidány a jsou nyní doporuèovány k~pou¾ívání - nové fonty Latin Modern. -\item Byla zru¹ena podpora OS Alpha \acro{OSF} - (podpora \acro{HPUX} byla zru¹ena ji¾ døíve), jeliko¾ se - nena¹el nikdo, kdo by na tìchto platformách zkompiloval nové binárky. -\item Instalaèní program Windows byl zmìnìn podstatným zpùsobem; poprvé - bylo integrováno u¾ivatelské prostøedí zalo¾ené na XEmacsu. -\item Dùle¾ité pomocné programy pro Windows - (Perl, \GS{}, Image\-Magick, Ispell) jsou nyní instalovány - do instalaèního adresáøe \TL{}. -\item Mapovací soubory jmen fontù pro \cmdname{dvips}, \cmdname{dvipdfm} - a \cmdname{pdftex} jsou nyní generovány novým programem - \cmdname{updmap} a instalovány do \dirname{texmf/fonts/map}. -%+\item \TeX{}, \MF{}, and \MP{} now output 8-bit input -%+ characters as themselves in output (e.g., \verb|\write|) files, -%+ log files, and the terminal, i.e., \emph{not} translated using the -%+ \verb|^^| notation. In \TL{}~7, this translation was -%+ dependent on the system locale settings; now, locale settings do -%+ not influence the \TeX{} programs' behavior. If for some reason -%+ you need the \verb|^^| output, rename the file -%+ \verb|texmf/web2c/cp8bit.tcx|. (Future releases will have cleaner -%+ ways to control this.) -\item \TeX{}, \MF{} a \MP{} nyní dávají na výstup %B% 8-bitové - vìt¹inu vstupních - znakù (32 a vý¹) bez konverze (napøíklad do souborù - zapisovaných pomocí \verb|\write|, - souborù log, na terminál), a tedy \emph{nejsou pøekládány} do - sedmibitové \verb|^^| notace. V~\TL{}~7 bylo toto mapování - závislé na nastavení systémových locale; nyní ji¾ nastavení locale - \emph{neovlivní} chování \TeX{}u. Pokud z~nìjakých dùvodù - potøebujete výstup s~\verb|^^|, pøejmenujte soubor - \verb|texmf/web2c/cp8bit.tcx|. Pøí¹tí verze bude mít èist¹í øe¹ení. -\item Tato dokumentace byla podstatným zpùsobem pøepracována. -\item Koneènì, jeliko¾ èísla verzí \TL{} ji¾ pøíli¹ narostla, - verze je nyní identifikována rokem vydání: \TL{} 2004. -\end{itemize*} - -\subsubsection{2004} - -Rok 2004 pøinesl mnoho zmìn: - -\begin{itemize} - -\item Pokud máte lokálnì instalovány fonty, které -vyu¾ívají své vlastní podp\r urn\'e soubory -\filename{.map} nebo (mnohem ménì pravdìpodobnì) \filename{.enc}, -mo¾ná budete nuceni tyto soubory pøesunout. - -Soubory \filename{.map} jsou nyní vyhledávány jen v~podaresáøích -\dirname{fonts/map} (v~ka¾dém stromì \filename{texmf}), podél cesty -\envname{TEXFONTMAPS}. Podobnì, soubory \filename{.enc} jsou hledány jen v~podadresáøích \dirname{fonts/enc}, podél cesty \envname{ENCFONTS}. \cmdname{updmap} se pokusí vypsat varování o~problematických souborech. -% -O~metodách zpracování té které informace, prosíme viz -\url{http://tug.org/texlive/mapenc.html}. - -\item \TKCS\ byla roz¹íøena pøidáním instalovatelného \CD, -zalo¾eného na \MIKTEX u, pro ty, kteøí dávají pøednost -této implementaci pøed Web2C. -%Také lo\v{n}sk\'e demo \CD{} bylo nahrazeno instalovatelným \CD{} pro Windows. -Viz oddíl~\ref{sec:overview.tl} (stránka~\pageref{sec:overview.tl}). - -\item Uvnitø \TL byl velký strom \dirname{texmf} pøede¹lých vydání nahrazen tøemi: \dirname{texmf}, -\dirname{texmf-dist} a \dirname{texmf-doc}. Viz oddíl~\ref{sec:tld} (stránka~\pageref{sec:tld}) a soubory \filename{README} pro ka¾dý z~nich. - -\item V¹echny vstupní soubory týkajíci se \TeX u jsou teï soustøedìny v~podadresáøi \dirname{tex} stromù \dirname{texmf*} a nemají oddìlené sourozenecké adresáøe \dirname{tex}, \dirname{etex}, -\dirname{pdftex}, \dirname{pdfetex} atd. Viz -\CDref{texmf.doc/doc/english/tds/tds.html\#Extensions} -{\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}. - -\item Pomocn\'e dávky (nemìly by být volány u¾ivateli) jsou teï -umístìny v~novém adresáøi \dirname{scripts} stromù \dirname{texmf*} a jsou vyhledávány prostøednictvím \verb|kpsewhich -format=texmfscripts|. Kdy¾ tedy máte programy volající tyto dávky, budou muset být nastaveny. Viz -\CDref{texmf.doc/doc/english/tds/tds.html\#Scripts} -{\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}. - -\item Témìø v¹echny formáty umo¾òují vìt¹inu znakù tisknout -bez konverze pomocí p\v{r}ekladov\'eho souboru -\filename{cp227.tcx}, místo jejich konverze pomocí -\verb|^^| notace. Konkrétnì, znaky na pozicích 32--256, -plus \uv{tab}, \uv{vertikální tab} a \uv{form feed} jsou pova¾ovány -za tisknutelné a nejsou konvertovány. Výjimky tvoøí plain \TeX\ -(jen 32--127 jsou tisknutelné), \ConTeXt\ (0--255 tisknutelné) a formáty -systému \OMEGA. Toto implicitní chování je témìø stejn\'e, jak na -\TL\,2003, ale je implementováno èistìji, s~více mo¾nostmi pøizpùsobení. -Viz \CDref{texmf/doc/web2c/web2c.html\#TCX-files} -{\texttt{texmf/doc/web2c/web2c.html\#TCX-files}}. -(Mimochodem, se vstupem Unicode, mù¾e \TeX\ na výstupu vypsat posloupnosti -èásteèných znakù pøi výpisu chybových kontextù, proto¾e je bytovì -orientován.) - -\item \textsf{pdfetex} je teï implicitní stroj pro v¹echny formáty -kromì samotného (plain) \textsf{tex}u. (Ten jistì¾e generuje \acro{DVI}, - kdy¾ je spu¹tìn jako \textsf{latex} atd.) To znamená, kromì jiných - vìcí, ¾e mikrotypografické roz\v{s}\'\i\v{r}en\'\i\ -\textsf{pdftex}u jsou dostupné - v~\LaTeX u, \ConTeXt u atd., stejn\v{e} jako roz\v{s}\'\i\v{r}en\'\i\ -\eTeX u (\OnCD{texmf-dist/doc/etex/base/}). - -To také znamená, ¾e u¾ití balíku \pkgname{ifpdf} (pracuje s~plainem -i \LaTeX em) nebo ekvivalentního kódu je \emph{dùle¾itej¹í -ne¾ kdykoliv pøedtím}, proto¾e jednoduché testování, zda -je \cs{pdfoutput} nebo nìjaký jiný primitiv definován, -není spolehlivý zpùsob urèení, zda je generován \acro{PDF} -výstup. Tento zpìtný krok jsme udìlali co nejvíc kompatibilní -letos, ale v~p\v{r}\'\i\v{s}t\'\i m roce \cs{pdfoutput} mù¾e -být definován, dokonce i kdy¾ se zapisuje do \acro{DVI}. - -\item pdf\TeX\ (\url{http://pdftex.org/}) má mno¾ství nových vlastností: - - \begin{itemize*} - - \item \cs{pdfmapfile} a \cs{pdfmapline} poskytují podporu mapování fontù uvnitø dokumentu. - - \item Mikrotypografické roz¹íøení fontu mù¾e být pou¾ito jednodu¹eji.\\ - \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} - - \item V¹echny parametry, které byly pøedtím nastavovány ve - zvlá¹tním konfiguraèním souboru \filename{pdftex.cfg}, musí - teï být nastaveny pomocí primitivù, obyèejnì - v~\filename{pdftexconfig.tex}; \filename{pdftex.cfg} není - dále podporován. V¹echny existující \filename{.fmt} soubory - musí být znovu vytvoøeny pøi zmìnì souboru \filename{pdftexconfig.tex}. - - \item Dal¹í informace viz manuál pdf\TeX u: \OnCD{texmf/doc/pdftex/manual}. - - \end{itemize*} - -\item Primitiv \cs{input} v~\cmdname{tex}u (a \cmdname{mf} a -\cmdname{mpost}) teï akceptuje dvojité uvozovky se jm\'eny obsahujícími -mezery a s~jin\'ymi zvlá¹tními znaky. Typické pøíklady: -\begin{verbatim} -\input "filename with spaces" % plain -\input{"filename with spaces"} % latex -\end{verbatim} -Pro dal¹í informace viz manuál Web2C: \OnCD{texmf/doc/web2c}. - -\item Podpora enc\TeX u je nyní zahrnuta uvnitø Web2C, -v~dùsledku toho ve v¹ech \TeX ových programech, pou¾itím -volby \optname{-enc} \Dash \emph{jen v~pøípadì, ¾e formáty -jsou vytvoøeny}. enc\TeX\ podporuje obecné pøekódování -vstupu a výstupu, èím\v{z} umo¾òuje plnou podporu kódování -Unicode (v~\acro{UTF}-8). Viz \OnCD{texmf-dist/doc/generic/enctex/} a -\url{http://www.olsak.net/enctex.html}. - -\item Aleph, nový stroj kombinující \eTeX\ a \OMEGA, je nyní k~dispozici. -Trochu informace najdete na \OnCD{texmf-dist/doc/aleph/base} -a \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph}. Formát pro -Aleph, zalo¾ený na \LaTeX u se jmenuje \textsf{lamed}. - -\item Nejnovìj¹í vydání \LaTeX u má novou verzi \acro{LPPL} \Dash teï -oficiálnì schválená Debian licence. Rozmanité dal¹í aktualizace najdete -v~souborech \filename{ltnews} v~\OnCD{texmf-dist/doc/latex/base}. - -\item Je dodán \cmdname{dvipng}, nový program pro konvertování \acro{DVI} na -obrazové soubory \acro{PNG}. Viz \OnCD{texmf/doc/man/man1/dvipng.1}. - -\item Zredukovali jsme balík \pkgname{cbgreek} na \uv{støednì} velkou -sadu fontù, se souhlasem a na radu autora (Claudio Beccari). -Odstranìné fonty jsou neviditelné, obrysové, a prùhledné, -relativnì zøídka se pou¾ívají a my jsme potøebovali místo. -Úplná sada je dostupná z~\acro{CTAN} -(\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). - -\item \cmdname{oxdvi} byl odebrán; pou¾ijte jednodu¹e \cmdname{xdvi}. - -\item Pøíkazy \cmdname{ini} a \cmdname{vir} (linky) pro -\cmdname{tex}, \cmdname{mf} a \cmdname{mpost} se ji¾ nevytváøejí, -napøíklad \cmdname{initex}. Funkènost instrukce \cmdname{ini} byla po -celá léta pøístupna prostøednictvím volby \optname{-ini} na~pøíkazovém øádku. - -\item Podpora platformy \textsf{i386-openbsd} byla zru¹ena. -Jeliko¾ balíèek \pkgname{tetex} v~\acro{BSD} Ports systému -je dostupný a \acro{GNU/}Linux a Free\acro{BSD} binárky byly -dostupné, zdálo se nám, ¾e èas dobrovolníkù mù¾e být vyu¾it -lépe nìkde jinde. - -\item Na \textsf{sparc-solaris} (pøinejmen¹ím) jste mo¾ná -museli nastavovat promìnné prostøedí -\envname{LD\_LIBRARY\_PATH}, aby bì¾ely programy \pkgname{t1utils}. -Je to tím, ¾e jsou kompilovány v~C++, -a neexistuje standardní umístìní \singleuv{runtime} knihoven. -(To není novinka roku 2004, ale nebylo to døív zdokumentováno.) -Podobnì, na \textsf{mips-irix}, `runtime' knihovny pro \acro{MIPS} -7.4 jsou nezbytné. -\end{itemize} - -\subsubsection{2005} - -Rok 2005 pøinesl jako obvykle mno¾ství modernizací balíèkù a programù. -Infrastruktura zùstala relativnì stabilní z~roku 2004, ale nutnì také -nastaly nìjaké zmìny: - -\begin{itemize} - -\item Byly zavedeny nové skripty \cmdname{texconfig-sys}, \cmdname{updmap-sys} a - \cmdname{fmtutil-sys}, které mìní konfiguraci v~systémových stromech. - Skripty \cmdname{texconfig}, - \cmdname{updmap} a \cmdname{fmtutil} teï mìní u¾ivatelské (user-specific) soubory - v~\dirname{$HOME/.texlive2005}. %$ - -\item Na specifikaci stromù obsahujících konfiguraèní soubory (u¾ivatelské resp. systémové) - byly zavedeny odpovídající nové promìnné \envname{TEXMFCONFIG} resp. - \envname{TEXMFSYSCONFIG}. Tedy, mo¾ná budete potøebovat pøesunout osobní verze - souborù \filename{fmtutil.cnf} a \filename{updmap.cfg} na tato místa; jiná volba je - pøedefinování \envname{TEXMFCONFIG} nebo \envname{TEXMFSYSCONFIG} v~souboru - \filename{texmf.cnf}. V~ka¾dém pøípadì skuteèná pozice tìchto souborù a - hodnoty \envname{TEXMFCONFIG} a \envname{TEXMFSYSCONFIG} - se musejí shodovat. Viz oddíl~\ref{sec:texmftrees}, - strana~\pageref{sec:texmftrees}. - -\item Loni jsme ponechali \verb|\pdfoutput| a jiné primitivy nedefinovány - pro výstup \dvi, pøesto¾e byl pou¾íván program \cmdname{pdfetex}. - Letos, jak jsme slíbili, jsme odstranili toto kompatibilitní - opatøení. Tedy kdy¾ vá¹ dokument pou¾ívá - \verb|\ifx\pdfoutput\undefined| - na testován\'i výstupu do formátu \acro{PDF}, je nutné ho zmìnit. Mù¾ete - k~tomu pou¾ít balík \pkgname{ifpdf.sty} (který funguje - v~plain \TeX u i \LaTeX u), nebo pou¾ít jeho logiku. - -\item Loni jsme zmìnili vìt¹inu formátù tak, aby vypisovaly (8bitové) znaky - tak jak jsou (viz pøedcházející sekci). Nový TCX soubor - \filename{empty.tcx} teï poskytuje jednodu¹¹í cestu k~dosa¾ení - pùvodního zápisu \verb|^^| kdy¾ si tak budete pøát, jako v~pøípadì: -\begin{verbatim} -latex --translate-file=empty.tcx yourfile.tex -\end{verbatim} - -\item Nový program \cmdname{dvipdfmx} je zaøazen pro pøevedení z~\acro{DVI} do \acro{PDF}; -ten je platnou aktualizací programu -\cmdname{dvipdfm} (který je té¾ je¹tì k~dispozici, i kdy¾ ho nedoporuèujeme). - -\item Nové programy \cmdname{pdfopen} a \cmdname{pdfclose} byly pøidány, aby -poskytly mo¾nost znovu otevøít \acro{PDF} -soubory v~programe Adobe Acrobat Reader bez jeho restartu. -(Jiné prohlí¾eèe \acro{PDF}, pøedev¹ím \cmdname{xpdf}, -\cmdname{gv} a \cmdname{gsview}, nikdy netrpìly tímto problémem.) - -\item Kvùli dùslednosti promìnné \envname{HOMETEXMF} a - \envname{VARTEXMF} byly pøejmenovány na \envname{TEXMFHOME} resp. na - \envname{TEXMFSYSVAR}. Je tu také \envname{TEXMFVAR}, která je - implicitnì u¾ivatelsky závislá (user-specific). Viz první bod vý¹e. -\end{itemize} - -\subsubsection{2006--2007} - -V~letech 2006--2007 byl rozsáhlým pøírustkem na \TL{} program \XeTeX{}, -pøístupný jako programy \texttt{xetex} a \texttt{xelatex}; viz -\url{http://scripts.sil.org/xetex}. - -\MP\ byl také podstatnì aktualizován, s~mnoha plány do budoucnosti -(\url{http://tug.org/metapost/articles}), podobnì pdf\TeX{} -(\url{http://tug.org/applications/pdftex}). - -Formát \TeX\ \filename{.fmt} (vysokorychlostní formát) a podobnì soubory -\MP\ a \MF\ jsou teï ulo¾eny v~podadresáøích \dirname{texmf/web2c}, -namísto pøímého ulo¾ení v~nìm (aèkoliv je adresáø stále prohledáván, -v~zájmu stávajících formátù \filename{.fmt}). Podadresáøe nesou jména -pou¾ívaných programù, napøíklad \filename{tex} -nebo \filename{pdftex} nebo \filename{xetex}. Tato zmìna by mìla pøi -bì¾ném pou¾ívání zùstat nepostøehnuta. - -Program (plain) \texttt{tex} ji¾ neète první øádky \texttt{\%\&} aby -urèil, jaký formát má spustit; je to èistý knuthovský \TeX. -(\LaTeX\ a v¹echny ostatní programy stále ètou øádky \texttt{\%\&}). - -Pochopitelnì se bìhem roku (jako obvykle) vyskytly stovky jiných -aktualizací balíkù a programù. Jako obyèejnì, zkontrolujte, prosím, -aktualizace na \acro{CTAN}u (\url{http://www.ctan.org}). - -Vnitønì, strom zdrojových textù je nyní ulo¾en v~Subversion, se -standardním webovským rozhran\'\i m pro jeho prohlí¾ení, kam smìruje -odkaz z~na¹í domovské stránky. Tøeba¾e není v~koneèné verzi -viditelný, oèekáváme, ¾e to poskytne základ pro stabilní rozvoj -v~letech následujících. - -Nakonec, v~kvìtnu 2006 Thomas Esser oznámil, ¾e u¾ nebude aktualizovat -te\TeX{} (\url{http://tug.org/tetex}). Výsledkem je nárùst zájmu o~\TL{}, -pøedev¹ím mezi distributory \GNU/Linuxu. -(Na \TL{} se nachází nové instalaèní schéma \texttt{tetex}u, -poskytující pøibli¾ný ekvivalent.) Doufáme, ¾e to mo¾ná povede -ke zlep¹ení prostøedí \TeX{}u pro v¹echny. - -\subsection{Sou\v{c}asnost (2008)} -\label{sec:tlcurrent} - -V~roce 2008 byla celá infrastruktura \TL{} pøebudována a znovu -implementována. Úplná informace o~instalaci je nyní -ulo¾ena v~textovém souboru \filename{tlpkg/texlive.tlpdb}. - -Mezi dal¹ími vìcmi je koneènì mo¾ná aktualizace instalace \TL{} -z~internetu po pøedchozí instalaci. Tuto vlastnost poskytoval -MiK\TeX\ ji¾ øadu let. Pøedpokládáme pravidelnou aktualizaci nových -balíkù po jejich vydání na \CTAN{}u. - -Obsa¾ený je významnìj¹í nový stroj (engine) Lua\TeX\ (\url{http://luatex.org}); -kromì lep¹í pøizpùsobivosti v~sázení je mo¾no tento vynikající skriptovací jazyk -pou¾ít jak uvnitø, tak i~mimo \TeX{}ovské dokumenty. - -Podpora Windows a unixových platforem je nyní jednotnìj¹í. -Zejména, vìt¹ina skriptù Perlu a Lua je teï k~dispozici pod Windows, -s~pou¾itím Perlu distribuovaného na~\TL. - -Nový skript \cmdname{tlmgr} (sekce~\ref{sec:tlmgr}) je v¹eobecné rozhraní -pro správu \TL{} po pøedchozí instalaci. Ovládá aktualizaci balíkù -a následující znovuvytvoøení formátù, mapovacích souborù a jazykových souborù, -volitelnì zahrnující lokální doplòky. - -S~pøíchodem programu \cmdname{tlmgr}, èinnosti programu -\cmdname{texconfig} na editaci formátù a konfiguraèních souborù dìlení -slov jsou nyní blokované. - -Program \cmdname{xindy} pro tvorbu rejstøíkù -(\url{http://xindy.sourceforge.net/}) je nyní zahrnut na vìt¹inì -platforem. - -Nástroj \cmdname{kpsewhich} mù¾e nyní ohlásit v¹echny výskyty -pro daný soubor -(option \optname{--all}) a omezené výskyty pro daný podadresáø -(option \optname{--subdir}). - -Program \cmdname{dvipdfmx} zahrnuje nyní funkènost extrakce informace -o `bounding boxu', pomocí povelu \cmdname{extractbb}; toto -byl jeden z~posledních rysù, které poskytoval \cmdname{dvipdfm}, av¹ak ne -\cmdname{dvipdfmx}. - -Fontové pøezdívky \filename{Times-Roman}, \filename{Helvetica}, atd. -byly odstranìné. Rùzné balíky oèekávaly jejich rùzné chování (pøedev¹ím, -¾e budou mít rùzné kódování) a nenalezlo se vhodné øe¹ení tohoto problému. - -Formát \pkgname{platex} byl odstranìn pro konflikt jmen s~japon¹tinou -\pkgname{platex}; -podporu pol¹tiny nyní zaji¹»uje balík \pkgname{polski}. - -Soubory \web{}ovských øetìzcù (pool) jsou nyní zkompilované do binárek pro -usnadnìní aktualizací. - -A nakonec, v~tomto vydání jsou zahrnuty zmìny provedené Donaldem Knuthem -v~jeho \'Uprav\'ach \TeX u roku 2008 (`\TeX\ tuneup of 2008'). -Viz \url{http://tug.org/TUGboat/Articles/tb29-2/tb92knut.pdf}. - -\subsection{Budoucnost} - -\emph{\TL{} není dokonalý!} A~nikdy nebude. Máme v~úmyslu -pokraèovat v~pravidelných vydáních a rádi bychom poskytovali -více podpùrných materiálù, programù, vèetnì instalaèních a jistì¾e -aktualizovaný a lépe zkontrolovaný strom maker a fontù. Tato práce je -provádìna dobrovolníky v~jejich limitovaném volném èase a mnoho -potøebného je¹tì zbývá udìlat. Viz, prosím, -\url{http://tug.org/texlive/contribute.html}. - -Prosíme, po¹lete opravy, návrhy, námìty a nabídky pomoci na: -\begin{quote} -\email{tex-live@tug.org}\\ -\url{http://tug.org/texlive} -\end{quote} -\smallskip\nobreak -\noindent \textsl{©»\kern-.4ptastné \TeX ování!} - -\end{document} diff --git a/Master/texmf-doc/source/texlive/texlive-de/Makefile b/Master/texmf-doc/source/texlive/texlive-de/Makefile deleted file mode 100644 index cecbe52710c..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-de/Makefile +++ /dev/null @@ -1,3 +0,0 @@ -include ../texlive-en/Makefile -doc = texlive-de -lang = german diff --git a/Master/texmf-doc/source/texlive/texlive-de/live4ht.cfg b/Master/texmf-doc/source/texlive/texlive-de/live4ht.cfg deleted file mode 100644 index 4d2aa6b940a..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-de/live4ht.cfg +++ /dev/null @@ -1,47 +0,0 @@ -% tex4ht configuration file for the TeX Live documentation. -% Accumulated over many years. Public domain. -% -% html specifies the main output format. -% info for extra debugging info in the log files. - -% better approach is to have html in one piece (including footnotes). -% also the newest TeX4ht could produce UTF-8 output (-utf8 option) -\Preamble{charset=iso-8859-1,html,info,fn-in} - -% add extra stylesheet -\Configure{@HEAD}{\HCode{% -\Hnewline -\Hnewline -}} - -% or LaTeX complains it is missing. -\begin{document} - -\EndPreamble - -% simplify output for HTML. We leave TeX and LaTeX alone, since tex4ht -% actually does the lowered E (and raised A) in CSS. -\def\OMEGA{Omega} -\def\LaTeXe{LaTeX2e} -\def\eTeX{e-\TeX} -\def\acro#1{#1} -\def\MF{Metafont} -\def\BibTeX{BibTeX} -\def\warningbox{} -\def\endwarningbox{} - -\newif\ifhackliterals -\ifx\tldocenglish\undefined \else \hackliteralstrue \fi -\ifx\tldocrussian\undefined \else \hackliteralstrue \fi -\ifx\tldocgerman\undefined \else \hackliteralstrue \fi -% -\ifhackliterals - % these definitions cause "missing } inserted" at \end{tabularx} in - % French and Czech. don't know why. - % - % don't make these into links, as happens with \path. We only have a couple - % special characters that actually occur. - \def\dirname{\texttt\bgroup\catcode`\$=12 \catcode`\_=12 \finishliteral} - \def\finishliteral#1{#1\egroup} - \let\filename=\dirname -\fi diff --git a/Master/texmf-doc/source/texlive/texlive-de/lmsy10-40.png b/Master/texmf-doc/source/texlive/texlive-de/lmsy10-40.png deleted file mode 100644 index 55c7772320b..00000000000 Binary files a/Master/texmf-doc/source/texlive/texlive-de/lmsy10-40.png and /dev/null differ diff --git a/Master/texmf-doc/source/texlive/texlive-de/texlive-de.tex b/Master/texmf-doc/source/texlive/texlive-de/texlive-de.tex deleted file mode 100644 index 4291b40950e..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-de/texlive-de.tex +++ /dev/null @@ -1,3091 +0,0 @@ -% $Id: texlive-de.tex,v 1.81 2008/08/13 20:34:57 hahe Exp hahe $ -% TeX Live documentation. Originally written by Sebastian Rahtz and -% Michel Goossens, now maintained by Karl Berry and others. -% Public domain. -% -\documentclass{article} -\ifnum\Status=1 - % Create A4 pdf - \pdfpageheight297mm - \pdfpagewidth210mm -\fi -\let\tldocgerman=1 % for live4ht.cfg -\usepackage{ngerman} -\usepackage{tex-live} -\usepackage[latin1]{inputenc} % translators: use your preferred encodings. -\usepackage[T1]{fontenc} - -\def\dante{DANTE~e.\,V\kern-0.15em.} -\begin{document} - -\title{% - {\huge \textit{Anleitung zu \TeX\ Live}\\\smallskip}% - {\LARGE \textsf{\TL{} 2008}}% -} - - -\author{Karl Berry (Herausgeber) \\[3mm] - \url{http://tug.org/texlive/}\\[12mm] - \small{\textit{Verantwortlich für die deutsche Ausgabe}}\\[3mm] - \small{Klaus Höppner, \email{klaus@dante.de}} \\ - \small{(\dante)} \\[3mm] - } -\date{August 2008} - - -\maketitle -\thispagestyle{empty} - -\newpage - -\begin{multicols}{2} - \tableofcontents - \listoffigures -\end{multicols} - -%\renewcommand{\Status}{0} -%\typeout{Status is \Status} - -\clearpage - -% ============================================================== -\section{Einleitung}\label{sec:intro} - -Diese Anleitung beschreibt das \TL-System. Die {\TL} Distribution enthält -\TeX/\LaTeX-Systeme für Linux, verschiedene \acro{UNIX}-Plattformen, {\MacOSX} -und (32-Bit)-Windows. - -Wahrscheinlich haben Sie \TL{} auf einem von zwei Wegen bezogen, entweder -per direktem Download von \TL{} oder als Teil der \DVD{} \TK, die von -vielen \TeX-Vereinen (u.\,a. \dante) an ihre Mitglieder verschickt werden -und in Deutschland über die Fachbuchhandlung Lehmanns (\url{http://www.lob.de}) -vertrieben wird. Abschnitt~\ref{sec:tl-coll-dists} beschreibt kurz den -Inhalt der \TK-\DVD. Sowohl \TL{} und die \TK{} sind durch das Engagement -vieler Freiwilliger aus vielen \TeX-Vereinen entstanden. Im Übrigen -beschränkt sich diese Anleitung auf \TL{} an sich. - -{\TL} enthält lauf"|fähige Versionen von \TeX, \LaTeXe, \ConTeXt, \MF, \MP, -{\BibTeX} und vielen anderen Programmen, -sowie eine umfassende Auswahl an Makros, Zeichensätzen und -Beschreibungen, die gemäß der Standard"=\TeX"=Verzeichnisstruktur (\TDS) -abgelegt sind. - -Wenn Sie neuere Versionen der dort aufgeführten Pakete zu suchen wollen, gehen Sie am besten zu \acro{CTAN}: -\url{http://www.ctan.org/}. - -Eine kurze Zusammenfassung der wesentlichen Änderungen der aktuellen \TL-Version -gegenüber der Vorgängerversion finden Sie im Abschnitt~\ref{sec:history} auf -Seite~\pageref{sec:history}. - -\subsection{Unterstützung verschiedener Betriebssysteme} -\label{sec:os-support} -\TL{} enthält direkt ausführbare Programme für viele Unix-basierte -Betriebssysteme, inklusive \MacOSX. Selbst wenn Ihr Unix-System wider -Erwarten nicht unterstützt wird, sollten Sie in der Lage sein, aus -den mitgelieferten Programm-Quellen ein funktionierendes \TeX-System zu -kompilieren. - -Bezüglich Microsoft Windows werden Versionen ab Windows~2000 unterstützt, -während die aktuelle \TL{} unter Windows 95/98, ME und NT nicht -mehr lauffähig ist. Es existieren zwar keine 64-Bit-Versionen der -Programme, allerdings sollten die 32-Bit-Programme problemlos auf -64-Bit-Systemen funktionieren. - -% ------------------------------------------------------------- -\subsection{Einsatzmöglichkeiten des \TL-Systems der \TK}\label{sec:basic} - -Sie können das \TL-System wahlweise von der \DVD{} oder über das -Internet installieren. Der \emph{Net Installer} ist ein kleines Programm, -das die benötigten Teile aus dem Internet nachlädt. Dieser Weg bietet -sich an (eine schnelle und stabile Internetverbindung voraus gesetzt), -wenn Sie kein komplettes \TL{} installieren wollen, sondern Ihr System nur -mit bestimmten Paketen bestehen soll. - -Wenn Sie die \DVD{} besitzen (oder das ISO-Image der \DVD{} herunter -geladen haben -- dieses kann auf einigen Systemen sogar direkt als -virtuelles Medium ">gemountet"< werden), können Sie \TL{} nach -Wunsch auf Ihrer Festplatte installieren oder direkt von der \DVD -benutzen. - -Beide Methoden werden in den Abschnitten zur Installation beschrieben. -Hier daher nur die kurze Zusammenfassung: - -\begin{itemize*} -\item Das Hauptinstallationsskript ist \cmdname{install-tl}. Es existiert -sowohl im Textmodus als auch in Form einer grafischen Benutzeroberfläche (GUI). -Unter Windows ist der grafische Modus der Standard, auf allen anderen -Systemen der Textmodus. Durch die Optionen \code{-gui} bzw.\ \code{-no-gui} -können Sie gezielt einen der beiden Modi auswählen. -\item \TL installiert u.\,a. den neuen ">\TL Manager"< mit dem Namen -\prog{tlmgr}. Auch dieser unterstützt Text- und GUI-Mode. Mit diesem -Programm können Sie einerseits Pakete von \TL installieren oder deinstallieren, -andererseits \TL konfigurieren. -\end{itemize*} - - -% ------------------------------------------------------------- -\subsection{">Wo bekomme ich Hilfe?"< oder ">Hier werden Sie geholfen!"<}\label{sec:help} - -Die \TeX-Gemeinschaft ist ebenso aktiv wie hilfsbereit, und es wird -praktisch jede ernst gemeinte Frage beantwortet. Diese Hilfe ist allerdings -nicht formal organisiert, sondern wird von Freiwilligen in ihrer -Freizeit geleistet. Es ist daher ernst gemeint, dass Sie vor einer -Fragestellung Ihre ">Hausaufgaben"< gemacht haben. Falls Sie auf -eine garantierte kommerzielle Unterstützung angewiesen sind oder eine solche -bevorzugen, sollten Sie die Finger vollständig vom \TL-System lassen und -in der Aufstellung unter \url{http://tug.org/interest.html#vendors} nach -einem geeigneten Händler suchen. - -Die folgende Liste stellt die leicht zugänglichen Quellen in der -empfohlenen Reihenfolge vor: - -\begin{description} -\item [Einführung:]\mbox{}\\ - Wenn Sie \TeX-Anfänger sind und eine englische Einführung in das System benötigen, - sollten Sie das \acro{WWW}-Dokument \url{http://tug.org/begin.html} (Englisch) lesen. - - Für deutschsprachige \LaTeX-Anfänger ist die ">\LaTeXe-Kurzbeschreibung"< von großem Nutzen - (\OnCD{texmf-doc/doc/german/lshort-german/l2kurz.pdf}). -\item [\TeX-\acro{FAQ}s:]\mbox{}\\ - Die \TeX-\acro{FAQ} (im Deutschen - \file{de-tex-faq} ">\emph{Fragen und Antworten [\acro{FAQ}] über - das Textsatzsystem TeX und \acro{DANTE}, Deutschsprachige - Anwendervereinigung TeX e.V.}"<) ist ein riesiges Kompendium - mit Fragen (und Antworten) aller Art, von der einfachsten - Anfängerfrage bis zu Expertenwissen. - % Sie ist Bestandteil - % des \TL-Systems (\OnCD{texmf-doc/doc/german/FAQ-de/}) und umfasst zur - % Zeit 182~Seiten als PDF-Datei (\OnCD{texmf-doc/doc/german/FAQ-de/de-tex-faq.pdf}). - % Darüber hinaus ist die - % \acro{FAQ} als \HTML-Datei (\OnCD{texmf-doc/doc/german/FAQ-de/html/index.html}) - % und als durchsuchbare Textdatei - % (\OnCD{texmf-doc/doc/german/FAQ-de/text/index.html}) enthalten. - % Im Internet finden Sie die \acro{FAQ} unter - Sie finden die deutschsprachige \acro{FAQ} unter - \url{http://www.dante.de/faq/de-tex-faq/}; zudem wird die - Text"-ver"-sion regelmäßig in die News-Gruppe - \url{news:de.comp.text.tex} - verschickt. Die \acro{FAQ} besteht aus mehreren Teilen, wobei - jeder Teil ohne News-Header nicht länger als ca. 32\,KB ist. - - Des Weiteren existiert eine englischsprachige \acro{FAQ}-Sammlung - (\OnCD{texmf-doc/doc/english/FAQ-en/newfaq.pdf}), die auch im Internet verfügbar ist - (\url{http://www.tex.ac.uk/faq}). - - Bitte nutzen Sie bei Problemen zu allererst diese beiden Möglichkeiten. - -\item [\TeX-Catalogue:]\mbox{}\\ - Wenn Sie auf der Suche nach einem bestimmten Paket, - Font, Programm u.\,ä. sind, empfiehlt sich ein Blick in den - \TeX-Catalogue. Dieser Katalog enthält eine Liste aller verfügbaren - \TeX-spezifischen Dinge (siehe - % \OnCD{texmf-doc/doc/english/catalogue} oder - \url{http://www.ctan.org/tex-archive/help/Catalogue/catalogue.html}). - -\item [\TeX-\acro{WWW}-Ressourcen:]\mbox{}\\ - Im \acro{WWW}-Dokument \url{http://tug.org/interest.html} finden Sie eine große Anzahl \TeX-spezifischer - Links zu Büchern, Manuals und Artikeln zu allen Aspekten des \TeX-Systems. - -\item [Archive:]\mbox{}\\ - Ein Forum für die Hilfestellung sind die Usenet-News-Gruppen - \url{news:de.comp.text.tex} (Deutsch), \url{news:comp.text.tex} (Englisch) - und die Mailing-Liste \email{texhax@tug.org}. In deren Archiven finden - sich die Fragen und Antworten vieler Jahre. Ihre Suche können Sie in Google - beispielsweise mit \url{http://groups.google.de/group/de.comp.text.tex/topics} - starten -- oder auch in \url{http://tug.org/mail-archives/texhax/}. - - Im Allgemeinen ist es recht Erfolg versprechend, eine generelle Suche über Google - \url{http://www.google.de/} durchzuführen (entweder im \emph{WWW} allgemein - oder in den \emph{News-Gruppen}); dies insbesondere, wenn es sich um Fragen über - \PS/PDF, \cmdname{Ghostscript} u.\,ä. handelt. - -\item [Fragen stellen:]\mbox{}\\ - Wenn Sie mit den oben aufgezeigten Möglichkeiten immer noch keine - Antwort auf Ihre Frage gefunden haben, können Sie die Frage auch in einer - News-Gruppe stellen (neudeutsch: \emph{posten}). Hier bietet sich für - den deutschsprachigen Raum die News-Gruppe \url{news:de.comp.text.tex} an. - Benutzen Sie am besten für Anfragen Google - (\url{http://groups.google.de/group/de.comp.text.tex/topics}) - oder einen Newsreader. Fragen an die englischsprachige Gruppe - \url{news:comp.text.tex} - (bei Google: \url{http://groups.google.de/group/comp.text.tex/topics}) - sollten Sie bitte nur in Englisch stellen. - - Zusätzlich existieren E-Mail-Diskussionslisten, wobei hier die deutschsprachige Liste - \email{TeX-D-L@listserv.dfn.de} zu nennen ist (das englischsprachige Äquivalent - ist \email{texhax@tug.org}). Darüber hinaus bietet sich für Mitglieder - von \acro{DANTE}~e.V. der Beraterkreis an (\email{beraterkreis@dante.de}). - Wie Sie sich in die E-Mail-Liste \dirname{TeX-D-L} eintragen können, - finden Sie in der \acro{FAQ} unter ">\texttt{1.3.2 Was ist TeX-D-L?}"<. - - Bevor Sie aber eine Frage absenden, lesen Sie \emph{bitte} die entsprechenden - Einträge der \acro{FAQ} zum Thema ">\emph{Wie stelle ich eine Frage in einer - Newsgroup, damit ich mit hoher Wahrscheinlichkeit eine Antwort bekomme?}"<. So - z.\,B. ">\texttt{1.3.1 Was ist `de.comp.text.tex'?}"< und ">\texttt{1.3.7 Was - sollte ich gelesen haben, bevor ich eine Frage in `de.comp.text.tex' oder der - Diskussionsliste TeX-D-L stelle?}"< oder auch - \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. - -\item [Mithilfe:]\mbox{}\\ - Wenn Sie einen Fehler melden wollen oder Empfehlungen und Kommentare - zur \TL-Verteilung, -Installation oder -Dokumentation geben möchten, sollten Sie die - E-Mail-Liste \email{tex-live@tug.org} nutzen. - Korrekturen, Anmerkungen und Erweiterungen für die deutsche Übersetzung können Sie auch - an \email{cdrom@dante.de} oder schriftlich an die Geschäftsstelle von - \acro{DANTE}~e.V. senden. - - Fragen zu Programmen, die Sie in der {\TK} finden, sollten Sie besser auf - einer der oben genannten Mailing-Listen stellen oder direkt an den Programmautor - richten. -\end{description} - -Auf der anderen Seite können auch Sie mit Ihrem Wissen helfen. Die News-Gruppen -\url{news:de.comp.text.tex} (in Deutsch), \url{news:comp.text.tex} (in Englisch) und -die Mailing-Liste \email{TeX-D-L@listserv.dfn.de} (Deutsch) und \email{texhax@tug.org} (Englisch) -stehen allen offen. Wenn Sie also dort mitlesen, scheuen Sie sich nicht, Fragen, -zu denen Sie eine Antwort wissen, zu beantworten und damit anderen zu helfen. - -% ============================================================== -\section[Überblick zum \protect\TeX Live-System]{Überblick zum \TL-System} -\label{sec:overview-tl} -% don't use \TL so the \uppercase in the headline works. Also so -% tex4ht ends up with the right TeX. Likewise the \protect's. - -In diesem Abschnitt beschreiben wir Struktur und Inhalt des \TL-Systems und der übergeordneten \TK-\DVD. - - -% ------------------------------------------------------------- -\subsection[Die \protect\TeX\protect\ Collection: \TL, pro\TeX{}t, Mac\TeX]% -{Die \protect\TeX\protect\ Collection: \TL, pro\TeX{}t, Mac\TeX}\label{sec:tl-coll-dists} - -Die \DVD ">\TK"< besteht aus: -\begin{description} -\item[\TL] Ein komplettes \TeX-System, wahlweise zur Installation auf Festplatte oder zur direkten Benutzung -von der \DVD. -\item[Mac\TeX] für \MacOSX. Dieses enthält das komplette \TL, bietet zusätzlich aber ein Installationsprogramm -für Mac und einige Zusatzprogramme. Nähere Informationen finden Sie auf der Homepage von Mac\TeX{} unter -\url{http://www.tug.org/mactex/}. -\item[pro\TeX{}t] basiert auf der \MIKTEX-Distribution für Windows. Es enthält noch einige Zusatzprogramme und -stellt eine einfache Installationsanleitung bereit, die Schritt für Schritt den Weg zu einem kompletten -\TeX-System beschreibt. Die Homepage von pro\TeX{}t findet sich unter \url{http://tug.org/protext}. -\item[CTAN] Weiterhin ist auf der \DVD{} ein Ausschnitt der \TeX-bezogenen Software enthalten, die sich -in CTAN, dem \emph{Comprehensive \TeX{} Archive Network} befinden. -\item [\texttt{texmf-extra}] In diesem Verzeichnis befinden sich zusätzliche Pakete, die kein Teil von -\TL sind. -\end{description} - -\CTAN{}, \pkgname{protext} und \dirname{texmf-extra} unterliegen nicht den selben Lizenzregeln wie \TL. -Daher können für Teile hieraus andere Lizenzbedingungen bezüglich einer Weiterverteilung oder -Modifikation gelten, die Sie unbedingt beachten sollten! - -% ------------------------------------------------------------- -\subsection{Basisverzeichnisse von \TL}\label{sec:tld} - -In diesem Abschnitt beschreiben wir die Basisverzeichnisse der \TL-Distribution. - -Auf der \pkgname{live}-\DVD befindet sich die gesamte \TL-Hierarchie im Unterverzeichnis \dirname{texlive} --- nicht im Wurzelverzeichnis der \DVD. - -\begin{center} -%% \begin{longtable}{@{}>{\ttfamily}lp{.63\hsize}@{}} -%% \hline -%% \rm -%% Verzeichnis & Inhalt \\ -%% \hline -%% \endfirsthead -%% \rm -%% Verzeichnis & Inhalt \\ -%% \hline -%% \endhead -%% \hline -%% \endfoot -\begin{tabular}{@{}>{\ttfamily}lp{.75\linewidth}@{}} -bin & ausführbare Programme des \TeX-Systems; - jeweils für die verschiedenen Rechnerplattformen - in Unterverzeichnissen zusammengefasst\\ -readme-html.dir & in diesem Verzeichnis (!) befinden sich HTML-Dateien - in verschiedenen Sprachen, die als schneller - Einstieg in \TL empfehlenswert sind.\\ -readme-txt.dir & in diesem Verzeichnis (!) befinden sich Text-Dateien - mit den gleichen Inhalten wie in {\ttfamily readme-html.dir}.\\ -source & Quelldateien aller Programme inklusive der - \Webc-Quellen für die \TeX- und \MF-Pakete als - komprimierte \file{bzip2}"=Archive\\ -support & verschiedene Programme und Hilfspakete, die \emph{nicht} automatisch - mitinstalliert werden, wie z.\,B. Editoren und \TeX-Shells\\ -texmf & Verzeichnisbaum für Programme und zugehörigen Hilfsdateien und Anleitungen; enthält keine \TeX-Formate - und Pakete (siehe \texttt{TEXMFMAIN} im nächsten Abschnitt)\\ -texmf-dist & Hauptbaum mit Formaten und Paketen (siehe \texttt{TEXMFDIST} im nächsten Abschnitt)\\ -texmf-doc & Verzeichnisbaum mit vollständigen Dokumentationen (ohne andere installierte Dateien); sortiert nach - Sprachen \\ -texmf-var & Verzeichnisbaum für automatisch erzeugte und gespeicherte Dateien - für \TeX, {\MF} und andere (siehe \texttt{TEXMFSYSVAR} im nächsten Abschnitt),\\ -%%\end{longtable} -\end{tabular} -\end{center} -% -Zusätzlich zu den oben aufgeführten Verzeichnissen finden Sie -im Wurzelverzeichnis der Distribution -auch noch die Installationsskripte. - -Das Verzeichnis \OnCD{texmf-doc} enthält zwar nur Anleitungen, bei weitem aber nicht die gesamte Dokumentation: -Die Dokumentation für Programme (Handbücher, ">man~pages"<, \acro{GNU}-\acro{info}-Dateien) beispielsweise finden Sie -im Verzeichnis \OnCD{texmf/doc}, da die Programme selbst sich im Verzeichnis \OnCD{texmf} befinden. Ähnliches -gilt für die Dokumentation der \TeX-Pakete und -Formate im Verzeichnis \OnCD{texmf-dist/doc}. - -Benutzen Sie die Programme \cmdname{texdoc} oder \cmdname{texdoctk}, wenn Sie auf der Suche nach irgendeiner -Dokumentationsdatei sind. Hilfreich in diesem Zusammenhang könnte auch die Link-Sammlung \filename{doc.html} im -Wurzelverzeichnis sein. - -Die Anleitung zu \TL ist in verschiedenen Sprachen verfügbar: -\begin{itemize*} -\item{Chinesisch:} \OnCD{texmf-doc/doc/chinese/texlive-zh-cn/texlive-zh-cn} -\item{Tschechisch/Slowakisch:} \OnCD{texmf-doc/doc/czechslovak/texlive-cz/live} -\item{Englisch:} \OnCD{texmf-doc/doc/english/texlive-en/texlive-en} -\item{Französisch:} \OnCD{texmf-doc/doc/french/texlive-fr/texlive-fr} -\item{Deutsch:} \OnCD{texmf-doc/doc/german/texlive-de/texlive-de} (dieses Dokument) -\item{Polnisch:} \OnCD{texmf-doc/doc/polish/texlive-pl/texlive-pl} -\item{Russisch:} \OnCD{texmf-doc/doc/russian/texlive-ru/texlive-ru} -\end{itemize*} - -% ------------------------------------------------------------- -\subsection{Überblick über die vordefinierten texmf-Bäume} -\label{sec:texmftrees} - -Dieser Abschnitt listet alle vordefinierten texmf-Bäume, die vom System benutzt -werden, und deren Bedeutung auf. Das Kommando \cmdname{texconfig conf} -zeigt Ihnen die aktuellen Einstellungen dieser Variablen an. - -\begin{ttdescription} -\item [TEXMFMAIN] In diesem Baum befinden sich wichtige Teile des Systems, - Hilfsprogramme (wie \verb+web2c/mktexdir+), pool-Dateien und andere - Hilfsdateien. -\item [TEXMFDIST] In diesem Baum befinden sich die wesentlichen Makro-Pakete, - Fonts usw. Dieser Baum enthält systemunabhängige Daten, die prinzipiell - von jedem TDS-kompatiblem \TeX-System nutzbar sein sollten. -\item [TEXMFLOCAL] Dieser Baum ist für Ergänzungen oder Aktualisierungen - von Makros, Fonts etc. gedacht, die Administratoren für alle Nutzer - installieren. -\item [TEXMFHOME] In diesem Baum können einzelne Nutzer Ergänzungen oder - Aktualisierungen von Makros, Fonts etc. ablegen. Standardmäßig befindet - sich dieser Baum unterhalb von \verb+$HOME+, so dass andere Nutzer von - Änderungen hier nicht beeinflusst werden. -\item [TEXMFCONFIG] Dieser Baum wird von den Hilfsprogrammen von te\TeX{} - wie \verb+texconfig+, \verb+updmap+ und \verb+fmtutil+ verwendet. - Standardmäßig befindet sich dieser Baum unterhalb von \verb+$HOME+, - so dass andere Nutzer von Änderungen hier nicht beeinflusst werden. -\item [TEXMFSYSCONFIG] Dieser Baum wird von den Hilfsprogrammen von te\TeX{} - wie \verb+texconfig-sys+, \verb+updmap-sys+ und \verb+fmtutil-sys+ - verwendet, so dass hier das Verhalten des \TL-Systems für alle Nutzer - beeinflusst werden kann. -\item [TEXMFVAR] Dieser Baum wird von Hilfsprogrammen wie \verb+texconfig+, - \verb+updmap+ und \verb+fmtutil+ benutzt, um automatisch generierte - Konfigurations-Dateien abzulegen. -\item [TEXMFSYSVAR] Dieser Baum wird von den systemweiten Hilfsprogrammen - wie \verb+texconfig-sys+, \verb+updmap-sys+ und \verb+fmtutil-sys+ - verwendet, um automatisch generierte Konfigurations-Dateien abzulegen. -\end{ttdescription} - -\noindent -Der Standard der Verzeichnisstruktur von \TL sieht wie folgt aus: -\begin{description} - \item[System-weites Wurzelverzeichnis] kann \TL{}-Versionen aus mehreren Jahren beinhalten: - \begin{ttdescription} - \item[2007] Eine Vorversion von \TL. - \begin{ttdescription} - \item [...] - \end{ttdescription} - \item[2008] Die aktuelle Version. - \begin{ttdescription} - \item [bin] ~ - \begin{ttdescription} - \item [i386-linux] \GNU/Linux binaries - \item [...] - \item [universal-darwin] \MacOSX binaries - \item [win32] Windows binaries - \end{ttdescription} - \item [texmf] Hierauf verweist \envname{TEXMFMAIN}. - \item [texmf-dist] \envname{TEXMFDIST} - \item [texmf-doc] \envname{TEXMFDOC} - \item [texmf-var] \envname{TEXMFSYSVAR} - \item [texmf-config] \envname{TEXMFSYSCONFIG} - \end{ttdescription} - \item [texmf-local] \envname{TEXMFLOCAL}, dieses Verzeichnis gilt für alle installierten \TL-Versionen - (aktuelle Version und Vorgängerversion), so dass hier durchgeführte lokale Änderungen über die - Jahre hinweg erhalten bleiben. - \end{ttdescription} - \item[Home-Verzeichnis des Benutzers] - (\texttt{\$HOME} oder \texttt{\%USERPROFILE\%}): - \begin{ttdescription} - \item[.texlive2007] Vom Nutzer privat erzeugte Dateien and Konfigurationsdaten - der Vorversion. - \item[.texlive2008] Vom Nutzer privat erzeugte Dateien and Konfigurationsdaten - für die aktuelle Version von \TL. - \begin{ttdescription} - \item [texmf-var] \envname{TEXMFVAR} - \item [texmf-config] \envname{TEXMFCONFIG} - \end{ttdescription} - \item[texmf] \envname{TEXMFHOME} Persönliche Makros, Fonts usw. des Nutzers. - \textit{etc.} - \end{ttdescription} -\end{description} - -% ------------------------------------------------------------- -\subsection{\protect\TeX-Erweiterungen}\label{sec:tex-extensions} - -Unter den \TeX-Systemen der {\TL} befinden sich verschiedene -\TeX"=Erweiterungen: - -\begin{description} -\item [\eTeX]\label{text:etex} stellt bei 100\%-iger Kompatibilität zum - normalen {\TeX} einen kleinen, aber mächtigen Satz neuer Befehle - bereit (für Makroexpansion, Character-Scanning, zusätzliche - Klassen für ">marks"<, erweiterte Debug-Möglichkeiten und andere). - Zusätzlich gibt es noch die \TeXXeT-Erweiterungen für den bidirektionalen Textsatz, - wie er beispielsweise im Arabischen gebraucht wird. - Im voreingestellten Modus ist {\eTeX} 100\%-ig kompatibel mit dem ">normalen"< \TeX. - Die Dokumentation zu {\eTeX} finden Sie in der Datei - \OnCD{texmf-dist/doc/etex/base/etex_man.pdf}. -\item [pdf\TeX] enthält die \eTeX\ Erweiterungen und erlaubt zusätzlich - die Ausgabe in PDF-Dateien sowie {\dvi}-Dateien. - Die Dokumentation zu pdf\TeX{} finden Sie unter - \OnCD{texmf-dist/doc/pdftex/manual/pdftex-a.pdf}. - In der Datei - \OnCD{texmf-dist/doc/pdftex/manual/samplepdf/samplepdf.tex} finden - Sie ein Anwendungsbeispiel. Das \LaTeX"=Paket \pkgname{hyperref} - besitzt die Option \optname{pdftex} mit der Möglichkeit - für aktive Querverweise (Hypertext) in PDF-Dateien. -\item [Lua\TeX] befindet sich noch in Entwicklung - und ist als zukünftiger Nachfolger von pdf\TeX\ vorgesehen, - zu dem es abwärtskompatibel bleiben soll. - Weiterhin soll es auch Aleph ersetzen. - Durch den enthaltenen Lua-Interpreter (s.\,\url{http://www.lua.org/}) - können Probleme, die in \TeX{} nur mühsam lösbar sind, - einfach und elegant gelöst werden. - Wird es unter dem Namen \filename{texlua} aufgerufen, - verhält es sich wie ein eigenständiger Lua-Interpreter - -- und wird als solcher in vielen Skripten von \TL bereits benutzt. - Für weitere Informationen siehe \url{http://www.luatex.org/} und - \OnCD{texmf-dist/doc/luatex/luatexref-t.pdf}. -\item [XeTeX] bietet die Unterstützung von Unicode Zeichensätzen und - OpenType Schriften durch diverse zusätzliche Bibliotheken. - Mehr Informationen sind unter \url{http://scripts.sil.org/xetex} - verfügbar. -\item [\OMEGA] (Omega) ist ein \TeX-System, das intern mit Unicode - (16-Bit"=Unicode"=Zeichen) arbeitet und damit das gleichzeitige - Arbeiten mit nahezu allen auf der Welt eingesetzten Schriften - und deren Zeichenkodierungen erlaubt. Außerdem werden über dynamisch - geladene, sogenannte ">{\OMEGA}~Translation~Processes"< (\acro{OTP}s) - Transformationen zur Verfügung gestellt, die beliebige Eingaben - vor der Bearbeitung durch {\TeX} nach bestimmten Regeln - umformen. Die (nicht ganz aktuelle) Anleitung zu {\OMEGA} finden - Sie in dem \TL-System in der Datei \OnCD{texmf-dist/doc/omega/base/doc-1.8.tex}. -\item [$\aleph$] (Aleph) vereinigt die \OMEGA- und \eTeX-Erweiterungen. - Eine Minimaldokumentation finden Sie in \OnCD{texmf-dist/doc/aleph/base}. -\end{description} - -%\clearpage - -% ------------------------------------------------------------- -\subsection{Weitere Programme von \TL} - -{\TL} enthält eine ganze Reihe unterstützender Programme wie - -\smallskip - -\begin{description} -\item[\cmdname{bibtex}] Verwalten von Bibliographien -\item[\cmdname{dv2dt, dt2dv}] \file{dvi} nach ASCII und umgekehrt -\item[\cmdname{dviconcat}] Zusammenfügen von \dvi-Dateien -\item[\cmdname{dvips}] Konversion von {\dvi} in {\PS} -\item[\cmdname{dviselect}] Ausschneiden von Seiten aus \dvi-Dateien -\item[\cmdname{dvipdfmx}] \dvi-nach-PDF-Konverter (erzeugt auch - \acro{CJK}-konformes PDF aus - \dvi-Dateien mit \OMEGA"=Erweiterungen), als Alternative - zu pdf\TeX -\item[\cmdname{dvilj}] Druckertreiber für die HP-LaserJet"=Familie -\item[\cmdname{lacheck}] \LaTeX-Syntax-Überprüfung -\item[\cmdname{makeindex}] Erzeugen eines Stichwortverzeichnisses -\item[\cmdname{mpost}] \MF-ähnliches Grafikprogramm -\item[\cmdname{psnup}] mehrere logische \PS-Seiten auf einem Blatt platzieren -\item[\cmdname{psselect}] Ausschneiden von Seiten aus \PS-Dateien -\item[\cmdname{tex4ht}] \TeX-nach-\HTML-Konvertierung -\item[\cmdname{texexec, texmfstart}] \ConTeXt- und PDF"=Prozessor -\item[\cmdname{xdvi}] \dvi-Bildschirmausgabe im X-Window-System -\end{description} - -\subsection{Fonts in \protect\TL} -\label{sec:tl-fonts} - -\TL{} enthält eine Vielzahl qualitativ hochwertiger Vektorschriften. Weitere Informationen hierzu finden sich unter \url{http://tug.org/fonts} und \OnCD{texmf-doc/doc/english/free-math-font-survey/survey}. - -% ============================================================== -\section[Installation von \TeX Live]{Installation von \protect\TL} -\label{sec:install} - -\subsection{Das Installationsprogramms} -\label{sec:inst-start} - -Zur Installation von \TL benötigen Sie die \TK{}-\DVD{} oer den \emph{\TL{} Net Installer} aus dem Internet. - -\begin{description} -\item [Net Installer:] Verfügbar von \CTAN, unter -\dirname{systems/texlive/tlnet}; die URL -\url{http://mirror.ctan.org/systems/texlive/tlnet} leitet Sie automatisch -an einen nahe gelegenen Server des \CTAN-Netzwerks weiter. -Sie können entweder die Datei \filename{install-tl.zip} herunter laden, -die sowohl für Unix als auch Windows gedacht ist, -oder die deutlich kleinere Datei \filename{install-unx.tar.gz}, -die aber nur den Installer für Unix enthält. -Nach dem Auspacken finden Sie die Dateien \filename{install-tl} (Unix) -bzw.\ \filename{install-tl.bat} (Windows) im Verzeichnis \dirname{install-tl}. - -\item [\TeX{} Collection \DVD:] Hier finden Sie die Dateien \filename{install-tl} (Unix) -bzw.\ \filename{install-tl.bat} (Windows) im Verzeichnis \dirname{texlive} -der \DVD. Unter Windows startet beim Einlegen der DVD i.\,A. automatisch ein Programm, bei dem Sie u.\,a. das -Installationsprogramm von \TL auswählen können. Die \DVD\ erhalten Sie als Mitglied eines \TeX-Vereins -(wie \url{http://www.dante.de} für den deutschsprachigen Raum, weitere Vereine finden Sie unter -\url{http://tug.org/usergroups.html}), oder innerhalb Deutschlands von der Fachbuchhandlung Lehmanns -(\url{http://www.lob.de}) oder international von der \TeX{} Users Group -(\url{http://tug.org/store}). Alternativ können Sie das \ISO-Image der \TL (\url{http://tug.org/texlive/acquire.html}) aus dem Internet laden. - -\end{description} - -Die folgenden Abschnitte beschreiben die Installation für die einzelnen Betriebssysteme. -\subsubsection{Unix} - -\begin{figure}[tb] -\begin{boxedverbatim} -======================> TeX Live installation procedure <===================== - -=======> Note: Letters/digits in indicate menu items <======= -=======> for commands or configurable options <======= - - - Detected platform: Intel x86 with GNU/Linux - - binary systems: 1 out of 16 - - Installation scheme (scheme-full) - - Customizing installation scheme: - standard collections - language collections - 83 collections out of 84, disk space required: 1666 MB - - directories: - TEXDIR (the main TeX directory): - !! default location: /usr/local/texlive/2008 - !! is not writable, please select a different one! - TEXMFLOCAL (directory for site-wide local files): - /usr/local/texlive/texmf-local - TEXMFSYSVAR (directory for variable and automatically generated data): - /usr/local/texlive/2008/texmf-var - TEXMFSYSCONFIG (directory for local config): - /usr/local/texlive/2008/texmf-config - TEXMFHOME (directory for user-specific files): - ~/texmf - - options: - [ ] use letter size instead of A4 by default - [X] create all format files - [X] install macro/font doc tree - [X] install macro/font source tree - [ ] create symlinks in standard directories - - Install for running from DVD - -Other actions: - start installation to HD - help - quit - -Enter command: -\end{boxedverbatim} -\caption{Installationsprogramm im Text-Modus (\GNU/Linux)}\label{fig:text-main} -\end{figure} - -\begin{figure}[tb] -\tlpng{install-w32-main}{\linewidth} -\caption{Grafische Oberfläche des Installationsprogramms (Windows)}\label{fig:gui-main} -\end{figure} - -\noindent -Im Folgenden werden die Eingaben des -Benutzers nach dem Kommando-Prompt \samp{>} \Ucom{fett} dargestellt. - -Öffnen Sie ein Terminalfenster auf Ihrem Unix-System und geben Sie folgende Befehle ein: -\begin{alltt} -> \Ucom{cd /pfad/zum/installer} -> \Ucom{perl install-tl} -\end{alltt} -(Sie können auch direkt \Ucom{perl /pfad/zum/installer/install-tl} eingeben. Wenn Ihre -\DVD so gemountet ist, dass als ausführbar gekennzeichnete Skripte direkt gestartet werden -können, können Sie im Verzeichnis des Installers auch direkt -\Ucom{./install-tl} eingeben.) - -Zum Installieren mit Hilfe einer Benutzeroberfläche verwenden Sie -\begin{alltt} -> \Ucom{perl install-tl -gui} -\end{alltt} - -Alle Optionen des Installationsprogramms werden mit -\begin{alltt} -> \Ucom{perl install-tl -help} -\end{alltt} -angezeigt. - -\textbf{Wichtiger Hinweis zu den Zugriffsrechten unter Unix:} Ihre aktuelle Einstellung von \code{umask} -wird bei der Installation von \TL{} berücksichtigt. Daher müssen Sie darauf achten, dass Sie hierfür -einen sinnvollen Wert einstellen (z.\,B. \code{umask002}), wenn Ihre Installation auch durch andere Nutzer -als Sie benutzt werden soll. Falls Sie unsicher sind, was dies bedeutet, schauen Sie bitte in die Anleitung -zu \code{umask} (indem Sie das Kommando \code{man umask} eingeben). - -\subsubsection{Mac\,OS\,X} - -Wie in Abschnitt~\ref{sec:tl-coll-dists} bereits erwähnt wurde, existiert mit Mac\TeX{} (\url{http://tug.org/mactex}) ein eigenes \TeX-System für \MacOSX. Dieses enthält ein -komplettes \TL mit einem Installationsprogramm, das in Funktionalität und Aussehen der üblichen Installation von Software unter \MacOSX entspricht. Weiterhin sind einige Zusatzprogramme enthalten. - -Wenn Sie die \TK-\DVD besitzen, empfiehlt es sich daher, Mac\TeX{} zu verwenden. - -\subsubsection{Windows} - -Wenn Sie den \emph{Net Installer} verwenden, oder auf Ihrem System beim Einlegen der \DVD das -Installationsprogramm nicht automatisch gestartet wurde, können Sie die Installation von -\TL im Windows-Explorer durch Doppelklick auf \filename{install-tl.bat} (auf der \DVD befindet -sich diese Datei im Verzeichnis \texttt{texlive}) starten. - -Alternativ können Sie eine MS-DOS"=Eingabeaufforderung verwenden, dort in das Verzeichnis wechseln, -in dem sich das Installationsprogramm befindet und dort -\begin{alltt} -D:\bs{}texlive\bs{}> \Ucom{install-tl} -\end{alltt} -eingeben -- \texttt{...>} kennzeichnet hierbei den Eingabeprompt; -Ihre Eingabe ist \Ucom{\texttt{bold/fett}} dargestellt. - -Alternativ können Sie die Installation auch aus einem beliebigen Verzeichnis heraus starten: -\begin{alltt} -> \Ucom{D:\bs{}texlive\bs{}install-tl} -\end{alltt} -wobei wir hier annehmen, dass sich ihre \TK-\DVD im Laufwerk D: befindet. - -Zur Installation im Textmodus verwenden Sie: -\begin{alltt} -> \Ucom{install-tl -no-gui} -\end{alltt} - -Alle vorhandenen Optionen, die beim Starten des Installationsprogramms verwendet werden können, werden -wie folgt angezeigt: -\begin{alltt} -> \Ucom{install-tl -help} -\end{alltt} - -\subsubsection{Installation im Textmodus} - -Abb.~\ref{fig:text-main} zeigt den Eingangsbildschirm des Installationsprogramms im Textmodus. -Dieser ist ein reiner Textmodus, d.\,h., es gibt somit keine Unterstützung zum Wandern durch die -einzelnen Menüpunkte mit den Cursor-Tasten. Alle Befehle wie z.\,B. die Auswahl von Menüpunkten werden -durch Eingabe der entsprechenden Befehle bzw.\ Menükürzel über die Tastatur eingegeben und -dann durch Drücken von \emph{Enter} übernommen. Hierbei wird zwischen Groß- und Kleinschreibung -unterschieden! - -Die Installation im Textmodus ist so spartanisch, weil dieser Modus überall funktionieren soll und daher -auf die Verwendung von Bibliotheken wie \texttt{ncurses} unter Unix verzichtet wurde. - -\subsubsection{Installation mit Benutzeroberfläche} - -Abb.~\ref{fig:gui-main} stellt den Eingangsbildschirm des Installationsprogramms unter -Windows dar. Hier ist die Installation im grafischem Modus voreingestellt. -Der Großteil der Unterschiede in den Menüpunkten -im Vergleich zur Darstellung im Textmodus in Abb.~\ref{fig:text-main} -ergibt sich aus der Tatsache, -dass das hier abgebildete GUI-Fenster unter Windows dargestellt wurde. - -\subsection{Benutzung des Installationsprogramms} -\label{sec:runinstall} - -Das Installationsprogramm sollte (wenn Sie die vorherigen Abschnitte zum Aufbau von \TL und der -verwendeten Verzeichnisstruktur gelesen haben) weitgehend selbsterklärend sein. Trotzdem wollen wir -auf einige Punkte näher eingehen. - -\subsubsection{Auswahl der Binaries (nur für Unix)} -\label{sec:binary} - -\begin{figure}[tbh] -\begin{boxedverbatim} -Available sets of binaries: -=============================================================================== - - a [ ] alpha-linux DEC Alpha with GNU/Linux - b [ ] amd64-freebsd x86_64 with FreeBSD - c [ ] hppa-hpux HP-UX - d [ ] i386-freebsd Intel x86 with FreeBSD - e [X] i386-linux Intel x86 with GNU/Linux - f [ ] i386-openbsd Intel x86 with OpenBSD - g [ ] i386-solaris Intel x86 with Sun Solaris - h [ ] mips-irix SGI IRIX - i [ ] powerpc-aix PowerPC with AIX - j [ ] powerpc-linux PowerPC with GNU/Linux - k [ ] sparc-linux Sparc with GNU/Linux - l [ ] sparc-solaris Sparc with Solaris - m [ ] universal-darwin universal binaries for MacOSX/Darwin - o [ ] win32 Windows - p [ ] x86_64-linux x86_64 with GNU/Linux -\end{boxedverbatim} -\caption{Auswahlmenü für Binaries}\label{fig:bin-text} -\end{figure} - -Abb.~\ref{fig:bin-text} zeigt das Auswahlmenü für die Binaries der einzelnen Betriebssysteme im Textmodus. -Im Allgemeinen sollte hier schon das richtige System ausgewählt sein. Sie können aber problemlos Binaries -für verschiedene Systeme parallel auswählen. Dies bietet sich an, wenn Ihre Installation auf verschiedenen -Rechnern in einem heterogenen Netzwerk sichtbar ist und von dort aus benutzt werden soll. - -\subsubsection{Auswahl der zu installierenden Komponenten} -\label{sec:components} - -\begin{figure}[tbh] -\begin{boxedverbatim} -Select a scheme: -=============================================================================== - - a [ ] TeX Live basic scheme - b [ ] TeX Live scheme for ConTeXt - c [X] TeX Live full scheme - d [ ] GUST TeX Live scheme - e [ ] GUTenberg TeX Live scheme - f [ ] TeX Live medium scheme - g [ ] TeX Live minimal scheme - h [ ] TeX Live for Omega users - i [ ] teTeX scheme - j [ ] XML typesetting scheme -\end{boxedverbatim} -\caption{Menü zur Auswahl des Schemas}\label{fig:scheme-text} -\end{figure} - -Abb.~\ref{fig:scheme-text} zeigt das Auswahlmenü für ein grundsätzliches Installationsschema der -\TL. Durch die Auswahl eines Schemas werden automatisch die Komponenten zur Installation ausgewählt, die -für das gewünschte Schema notwendig bzw.\ sinnvoll sind. Mit einer vollständigen Installation von \TL -(\emph{full scheme}) sind Sie auf der sicheren Seite, da hier einfach alles installiert wird. Sie können -aber auch eines der abgespeckten Schemas wie \emph{basic} (für ein sehr schlankes System), \emph{medium} -oder \emph{minimal} (dies empfiehlt sich aber nur für Testsysteme und weniger zum ernsthaften Arbeiten) -auswählen. Weiter stehen einige Schemas für spezielle Zwecke oder Sprachen zur Verfügung. - -\begin{figure}[tbh] -\tlpng{stdcoll}{.7\linewidth} -\caption{Menü zur Aus- oder Abwahl von Collections (hier unter Linux)}\label{fig:collections-gui} -\end{figure} - -Wenn Sie das Schema ausgewählt haben, können Sie dieses in den Menüpunkten \emph{standard collections} und -\emph{language collections} (s.\,Abb.~\ref{fig:collections-gui}, diesmal zur Abwechslung im GUI-Modus) -individuell nach Ihren Wünschen anpassen. - -Während das Schema nur den grundlegenden Funktionsumfang vorgibt, ist die Auswahl von Komponenten auf der -Ebene der \emph{Collections} viel feiner. Eine Collection besteht dabei aus mehreren Paketen zu einem Thema, -wobei jedes der Pakete aus bestimmten Makrodateien, Fontdateien usw. bestehen kann. - -Noch mehr Kontrolle über die Komponenten Ihres Systems haben Sie nach der Installation mit dem Programm~\prog{tlmgr}, das in Abschnitt~\ref{sec:tlmgr} beschrieben wird. Hier können Sie gezielt einzelne -Pakete installieren oder entfernen. - -\subsubsection{Verzeichnisse} -\label{sec:directories} - -Die Verzeichnisstruktur von \TL wurde bereits im Abschnitt~\ref{sec:texmftrees} auf S.~\pageref{sec:texmftrees} -beschrieben. Als Wurzelverzeichnis für \TL (\dirname{TEXDIR}) wird unter Windows -(|%PROGRAMFILES%\texlive\2008|) und unter Unix (\dirname{/usr/local/texlive/2008}) angenommen. - -Prinzipiell können Sie diesen Pfad problemlos ändern, z.\,B. wenn Sie \TL als normaler Nutzer installieren -wollen und kein Schreibrecht in dem o.\,a. Verzeichnis besitzen. - -Auf Wunsch können Sie \TL also auch in Ihrem Home-Verzeichnis installieren, wenn Sie sowieso der einzige -Verwender von \TL sind. Für Ihr Home-Verzeichnis können Sie den Pfad ">|~|"< verwenden und so -Beispielsweise \TL nach |~/texlive/2008| installieren. - -Wir empfehlen Ihnen, die Jahreszahl im Verzeichnisnamen bei zu behalten. So können Sie von Jahr zu Jahr -einfach die neue Version testen, ohne die alte zu entsorgen. Bei Bedarf können Sie einen symbolischen -Link (z.B. \dirname{/usr/local/texlive-cur}) verwenden, der jeweils auf das Verzeichnis der aktuellen -Version von \TL verweist. - -Wenn Sie die Einstellung \dirname{TEXDIR} im Installationsprogramm ändern, werden die Werte für -\dirname{TEXMFLOCAL}, \dirname{TEXMFSYSVAR} und -\dirname{TEXMFSYSCONFIG} automatisch angepasst. - -Das als \dirname{TEXMFHOME} bezeichnete Verzeichnis ist der Ort, in dem persönliche Makrodateien, -Schriften o.\,ä. abgelegt werden können. Vorgabewert ist |~/texmf|. Im Gegensatz zu \dirname{TEXDIR} -wird |~| hier nicht direkt zum Pfad des Home-Verzeichnisses aufgelöst, sondern unverändert in die -Konfigurationsdateien von \TL übernommen und erst zur Laufzeit aufgelöst. Somit kann jeder Nutzer -des Systems seinen komplett eigenen Pfad haben, der von \TL verwendet wird, und so nach Wunsch auch -eigene Konfigurationsänderungen durchführen. -Zur Laufzeit wird |~| unter Unix durch \dirname{$HOME} und unter Windows durch \verb|%USERPROFILE%| ersetzt. - -\subsubsection{Optionen} -\label{sec:options} - -\begin{figure}[tbh] -\begin{boxedverbatim} -

use letter size instead of A4 by default: [ ] - create all format files: [X] - install font/macro doc tree: [X] - install font/macro source tree: [X] - create symlinks in standard directories: [ ] - binaries to: - manpages to: - info to: -\end{boxedverbatim} -\caption{Auswahlmenü für weitere Optionen (Unix)}\label{fig:options-text} -\end{figure} - -Abb.~\ref{fig:options-text} zeigt das Menü, in dem weitere Einstellungen für die Installation von -\TL möglich sind. Drei dieser Optionen erfordern eine Erläuterung: -\begin{description} -\item[use letter size instead of A4 by default:] Verwendung von Letter statt DIN\,A4 als -Standard\-papier\-größe. Natürlich können Sie später unabhängig davon für einzelne Dokumente eine -beliebige Papiergröße wählen. - -\item[create all format files:] Auch wenn das Erzeugen von Formatdateien für Makropakete, die Sie gar - nicht benötigen, Zeit und Platz kostet, empfehlen wir trotzdem, diese Option ausgewählt zu belassen. - Falls Sie diese Option abwählen, werden Formatdateien jeweils bei Bedarf erzeugt, landen dann aber - im persönlichen \dirname{TEXMFVAR}-Baum des aktuellen Benutzers. Hier liegende Formate werden allerdings - nicht automatisch neu gerneriert, wenn z.\,B. Programme oder Silbentrennmuster aktualisiert werden, so dass - im Extremfall nach einem Update Inkompatibilitäten entstehen können. - -\item[create symlinks in standard directories] (nur unter Unix): - Mit dieser Option können Sie symbolische Links für Programme und Dokumentation in den Standard\-verzeichnissen - Ihres Systems anlegen, so dass Sie Ihre Umgebungsvariablen \envname{PATH}, \envname{MANPATH} und - \envname{INFOPATH} nicht anpassen müssen. Natürlich benötigen Sie für diese Option Schreibrechte in - den entsprechenden Verzeichnissen. Diese Option ist nicht dazu gedacht, ein vorhandenes \TeX-System, das - z.\,B. als Teil Ihrer Linux-Distribution installiert wurde, zu überschreiben. Sie dient vielmehr dazu, - dass die Links in Verzeichnissen angelegt werden, wo die Nutzer sie erwarten -- beispielsweise - \dirname{/usr/local/bin} --, aber sich noch keine \TeX-Programme befinden. -\end{description} - - -\subsubsection[Benutzen von \protect\TL direkt von DVD{}]{Benutzen von \protect\TL direkt von DVD{} (nur im Textmodus verfügbar)} -\label{sec:fromdvd} - -Verwenden Sie die Option ">|V|"<, um die Installation zum Benutzen von \TL direkt von der \DVD einzustellen. -Ihr Installationsbildschirm sollte nun so aussehen wie in Abb.~\ref{fig:main-fromdvd} dargestellt. -Tatsächlich wechselt die Option~|V| jeweils zwischen Installation auf Festplatte und Installation zur -Nutzung von \DVD hin- und her, so dass Sie problemlos zur alten Installations"-einstellung zurück kommen, -wenn Sie diese Option versehentlich ausgewählt haben. - -\begin{figure}[tbh] -\begin{boxedverbatim} -======================> TeX Live installation procedure <===================== - -=======> Note: Letters/digits in indicate menu items <======= -=======> for commands or configurable options <======= - - directories: - TEXDIRW (Writable root): - !! default location: /usr/local/texlive/2008 - !! is not writable, please select a different one! - TEXMFLOCAL (directory for site-wide local files): - /usr/local/texlive/texmf-local - TEXMFSYSVAR (directory for variable and automatically generated data): - /usr/local/texlive/2008/texmf-var - TEXMFSYSCONFIG (directory for local config): - /usr/local/texlive/2008/texmf-config - TEXMFHOME (directory for user-specific files): - ~/texmf - - options: - [ ] use letter size instead of A4 by default - [X] create all format files - - set up for installing to hard disk - -Other actions: - start installation for running from DVD - help - quit -\end{boxedverbatim} -\caption{Haupschirm des Installationsprogrmm, wenn die Option \optname{from DVD} - ausgewählt wurde}\label{fig:main-fromdvd} -\end{figure} - -Wie Sie sehen, hat sich das Hauptmenü an einigen Stellen geändert: Die Menüpunkte zur Auswahl eines -Schemas oder von Collections sowie zum Anlegen symbolischer Links sind verschwunden, und im Abschnitt -\emph{Directories} wird nun die Angabe eines Verzeichnisses für \dirname{TEXDIRW} (writable root) verlangt. - -Auch beim Verwenden von \TL direkt von \DVD müssen einige Verzeichnisse auf der Festplatte angelegt werden, -in denen \TL beispielsweise automatisch generierte Dateien (wie Formate oder Fontmaps) ablegen kann. -Die Verzeichnisse \dirname{texmf}, \dirname{texmf-dist} und \dirname{texmf-doc} werden aber direkt von -\DVD benutzt und daher nicht auf die Festplatte kopiert. - -Die Konfiguration von \TL im Anschluss an die Installation unter Unix ist bei der Verwendung als Live-System -von \DVD etwas komplexer, da hier an einigen Stellen von der normalen Verzeichnisstruktur von \TL abgewichen -werden muss, s.~Abschnitt~\ref{sec:postinstall}. - -Aus Zeitgründen ist die Option für die Benutzung von \TL direkt von \DVD leider nicht im grafischen Modus -des Installationsprogramms enthalten. Daher muss hierfür zwingend der Textmodus verwendet werden. -Zu diesem Zweck muss daher unter Windows die Installation innerhalb einer Eingabeaufforderung mit der -Option~\texttt{-no-gui} gestartet werden (s.\,Abschnitt~\ref{sec:cmdline}). - -Abschnitt~\ref{sec:portable-unix} beschreibt einen portableren Weg um \TL zu benutzen, der keine Änderungen -der Systemkonfiguration erfordert, dafür dann aber keine Konfigurationsänderungen an \TL erlaubt. - - -\subsection{Kommandozeilenoptionen für die Installation} -\label{sec:cmdline} - -Nach Eingabe von -\begin{alltt} -> \Ucom{install-tl -help} -\end{alltt} -erhalten Sie eine Liste der vorhanden Kommando\-zeilen\-optionen. Sie können diese entweder mit |-| oder |--| -verwenden. Die wichtigsten sind: - -\begin{ttdescription} -\item[-gui] Installation im \GUI{}-Modus. Hierfür muss unter Unix Perl/Tk installiert sein - (\url{http://tug.org/texlive/distro.html#perltk}); falls dies nicht der Fall ist, wird die Installation - stattdessen im Textmodus durchgeführt. -\item[-no-gui] Installation im Textmodus. Da dies unter Unix Standard ist, wirkt sich diese Option nur - unter Windows aus. Da die Installation zum Benutzen von \TL direkt von \DVD im grafischen Modus nicht - verfügbar ist, brauchen Sie in diesem Fall unbedingt den Textmodus. -\item[-lang {\sl LL}] Sprache des Installationsprogramms als Sprach-Code in zwei Buchstaben (\textsl{LL}). - Derzeit werden englisch (\texttt{en}, Standard), deutsch (\texttt{de}), französisch (\texttt{fr}), - holländisch (\texttt{nl}), polnisch (\texttt{pl}), slowenisch (\texttt{sl}) und vietnamesisch - (\texttt{vi}) unterstützt. Das Installationsprogramm versucht, die gewünschte Sprache anhand des - Systems herauszufinden. Falls dies scheitert oder die betreffende Sprache nicht verfügbar ist, wird als - Rückfallposition englisch benutzt. -\item[-profile {\sl profile}] Das Installationsprogramm schreibt die ausgewählten Optionen in eine Datei - \filename{texlive.profile} im Unterverzeichnis \dirname{2008/tlpkg}. Mit dieser Option können - Sie eine bereits vorhandene Datei bei der Installation weiter verwenden, z.\,B. wenn Sie äquivalente - Installationen auf mehreren Rechnern realisieren wollen, ohne alle Auswahlschritte der Installation immer - wieder neu durchführen zu müssen. Hier ein Beispiel einer solchen Datei: - \begin{fverbatim} -# texlive.profile written on Wed Jul 9 16:13:44 2008 UTC -# It will NOT be updated and reflects only the -# installation profile at installation time. -selected_scheme scheme-basic -TEXDIR /usr/local/texlive/2008 -TEXDIRW /usr/local/texlive/2008 -... -TEXMFSYSVAR /usr/local/texlive/2008/texmf-var -collection-basic 1 -... -option_symlinks 0 - \end{fverbatim} -\item [-location {\sl url/path}] zur Auswahl eines anderen Verzeichnisses mit den Quellen für Pakete; zur - weiteren Erläuterung siehe den nächsten Abschnitt. -\end{ttdescription} - -\subsubsection{Die Option \optname{location}} -\label{sec:location} - -Der als \optname{location} angegebene Wert kann neben einem ganz normalen Verzeichnispfad auch eine URL sein, -die mit \texttt{ftp:}, \texttt{http:} oder \texttt{file:/} beginnt. Falls sich \optname{location} auf einem -lokalen Laufwerk befindet (Verzeichnispfad oder mit \texttt{file:/} beginnende URL), -wird die Installationsmethode (aus komprimierten Archiven oder einem echten Live-Dateisystem) automatisch -bestimmt: falls bezüglich der angegebenen \optname{location} ein Unterverzeichnis \dirname{archive} existiert, -das Dateien vom Typ \filename{.tar.lzma} enthält, werden diese komprimierte Dateien als Installationsquelle -benutzt, selbst wenn parallel die Pakete ausgepackt in einem Live-Dateisystem vorhanden sind. - -Im Fall einer \optname{location}, die mit \texttt{http:} oder \texttt{ftp:} beginnt, werden -das Zeichen `\texttt{/}' und/oder die Zeichenkette `\texttt{/tlpkg}' am Ende ignoriert. Sie können hier -z.\,B. einen bestimmten \CTAN-Server auswählen, was dann in etwa so aussehen würde: -\url{http://ctan.example.org/tex-archive/texlive/tlnet/2008}. -Hier müssen Sie natürlich einen echten Servernamen und den für diesen Server gültigen Pfad einsetzen -(eine Liste von \CTAN-Servern finden Sie unter \url{http://ctan.org/mirrors}). -Die Standardvorgabe ist, -über \url{http://mirror.ctan.org} einen Server automatisch auszuwählen. -Einmal ausgewählt, wird dieser allerdings zum Herunterladen aller Komponenten verwendet. - -\subsection{Aufgaben im Anschluss an die Installation} -\label{sec:postinstall} - -Je nach System kann es notwendig sein, dass im Anschluss an die Installation noch einige Kleinigkeiten -erledigt werden müssen. - -\subsubsection{Windows} -Benutzer von Windows sind hier in der glücklichen Position, dass das Installationsprogramm alles komplett -erledigt haben sollte. - -\subsubsection{Unix, falls symbolische Links angelegt wurden} - -Wenn Sie bei der Installation angegeben haben, dass und wo symbolische Links angelegt werden sollten -(s.\,Abschnitt~\ref{sec:options}), sollten hier auch keine Nacharbeiten mehr notwendig sein. - -\subsubsection{Umgebungsvariablen für Unix} -\label{sec:env} - -Das Verzeichnis mit den ausführbaren Programmen von \TL muss sich im Suchpfad des Systems befinden. -Jedes unterstützte System besitzt ein eigenes Verzeichnis unterhalb von \dirname{TEXDIR/bin}, deren -Namen Sie in Abb.~\ref{fig:bin-text} finden. - -Weiterhin können Sie die Verzeichnisse mit den Manual-Pages und Info-Dateien zu den entsprechenden -Suchpfaden für Dokumentation hinzu fügen, wenn Sie es wünschen. - -Für Systeme mit einer Bourne-kompatiblen Shell wie \prog{bash} ist hier am Beispiel von GNU/Linux -aufgeführt, wie die Befehle zum Setzen der Umgebungsvariablen (z.\,B. in \filename{$HOME/.profile}) -aussehen könnten: - -\begin{sverbatim} -export PATH=/usr/local/texlive/2008/bin/i386-linux:$PATH -export MANPATH=/usr/local/texlive/2008/texmf/doc/man:$MANPATH -export INFOPATH=/usr/local/texlive/2008/texmf/doc/info:$INFOPATH -\end{sverbatim} - -Für \prog{csh} oder \prog{tcsh} erfolgt die Konfiguration in der Regel in der Datei~\filename{$HOME/.cshrc} -und könnte so aussehen: - -\begin{sverbatim} -setenv PATH /usr/local/texlive/2008/bin/i386-linux:$PATH -setenv MANPATH /usr/local/texlive/2008/texmf/doc/man:$MANPATH -setenv INFOPATH /usr/local/texlive/2008/texmf/doc/info:$INFOPATH -\end{sverbatim} - -\subsubsection{Systemweites Setzen von Umgebungsvariablen} -\label{sec:envglobal} - -Wenn Sie als Administrator die Umgebungsvariablen global für das gesamte System setzen wollen, -gehen wir davon aus, dass Sie sich mit der grundlegenden Systemadministration auskennen. - -Daher hier nur zwei Hinweise: 1)~schauen Sie nach einer Datei -\filename{/etc/manpath.config}. Falls diese vorhanden ist, sollte es reichen, folgende Zeilen -hinzu zu fügen: - -\begin{sverbatim} -MANPATH_MAP /usr/local/texlive/2008/bin/i386-linux \ - /usr/local/texlive/2008/texmf/doc/man -\end{sverbatim} - -Und 2)~prüfen Sie, ob es auf Ihrem System eine Datei \filename{/etc/environment} gibt, in der die -systemweiten Umgebungsvariablen definiert werden. - -\subsubsection{Benutzen von \protect\TL direkt von DVD} -Üblicherweise verwendet \TL eine Datei \filename{texmf.cnf}, um die Verzeichnisbäume, in denen -sich die Komponenten von \TL befinden, zu identifizieren. Diese Methode benutzt relative Pfade, so -dass Ihr \TL-System funktioniert, wo immer Sie es auch hin installieren, solange die Verzeichnisstruktur -erhalten bleibt. - -Diese Methode funktioniert leider nicht mehr, wenn Sie \TL direkt von der \DVD benutzen wollen. -Da die \DVD ein Nur-Lese-Medium ist, einige der Pfade in \filename{texmf.cnf} aber erst nach der -Installation fest stehen, muss sich diese Datei außerhalb der \DVD befinden. -Aus diesem Grund muss eine Umgebungsvariable \envname{TEXMFCNF} gesetzt werden, -die \TL{} mitteilt, in welchem Verzeichnis sich die Datei \filename{texmf.cnf} befindet. -Zusätzlich muss sich natürlich -- wie im vorigen Abschnitt beschrieben -- das -Verzeichnis der \DVD, in dem sich die passenden ausführbaren Programme befinden, innerhalb des -Suchpfads des Systems befinden. - -Beim Abschluss des Installationsprogramms sollten Sie die notwendigen Informationen erhalten haben, -wie Sie \envname{TEXMFCNF} setzen müssen. Falls Sie dies übersehen haben, der Wert ist -\dirname{$TEXMFSYSVAR/web2c}, wobei im Normalfall \dirname{$TEXMFSYSVAR} auf das Verzeichnis -\dirname{/usr/local/texlive/2008/texmf-var/web2c} verweist. In diesem Fall benötigen Sie also für -die \prog{bash} den Befehl -\begin{sverbatim} -TEXMFCNF=/usr/local/texlive/2008/texmf-var/web2c; export TEXMFCNF -\end{sverbatim} -bzw.\ für [t]csh: -\begin{sverbatim} -setenv TEXMFCNF /usr/local/texlive/2008/texmf-var/web2c -\end{sverbatim} - -\subsubsection{\ConTeXt{} Mark IV} -Das ">alte"< \ConTeXt{} sollte direkt lauffähig sein. Falls Sie das neue \ConTeXt{} ">Mark IV"< -verwenden wollen, sind einige manuelle Nacharbeiten notwendig, die unter -\url{http://wiki.contextgarden.net/Running_Mark_IV} beschrieben sind. - -\subsubsection{Integrieren lokaler bzw.\ Nutzer-spezifischer Makros} -\label{sec:local-personal-macros} - -Wie bereits in Abschnitt~\ref{sec:texmftrees} erwähnt, ist der Verzeichnisbaum \dirname{TEXMFLOCAL} (im -Normalfall \dirname{/usr/local/texlive/texmf-local} oder \verb|C:\Program Files\texlive\texmf-local|) -für lokale Ergänzungen wie Makros und Schriften gedacht, die anschließend allen Benutzern des Systems zur -Verfügung stehen. Weiterhin können Benutzer den Verzeichnisbaum \dirname{TEXMFHOME} (im Normalfall -\dirname{$HOME/texmf} oder \verb|%USERPROFILE%\texmf|) für persönliche Ergänzungen verwenden, ohne -dass andere Benutzer davon beeinflusst werden. -Diese Verzeichnisse sollen über verschiedene Versionen von \TL hinweg identisch sein, so dass ein -Update von \TL auf eine neue Version einfach möglich ist, ohne dass Sie Ihre lokalen Ergänzungen -verlieren. Wir empfehlen Ihnen daher, von der vorgegebenen Verzeichnisstruktur nicht abzuweichen. - -Für beide oben genannte Verzeichnisbäume erwartet \TL eine Verzeichnisstruktur innerhalb des Baums, die -dem \emph{\TeX{} Directory Standard} entspricht, wie er in \url{http://tug.org/tds} bzw. -\filename{texmf/web2c/texmf.cnf} definiert ist. -So gehören Dokumentklassen für \LaTeX{} z.\,B. in ein Verzeichnis -unterhalb von \dirname{TEXMFLOCAL/tex/latex} oder \dirname{TEXMFHOME/tex/latex}. - -Der Verzeichnisbaum \dirname{TEXMFLOCAL} wird zur Laufzeit nicht direkt nach Dateien durchsucht. -Stattdessen wird eine Liste von Dateinamen verwendet, sich sich in einer Datei mit dem Namen~\filename{ls-R} -befindet. Denken Sie also daran, nach Änderungen in diesem Baum diese Dateiliste zu aktualisieren, -entweder mit dem Befehl \cmdname{mktexlsr} oder die Schaltfläche \emph{Reinit file database} in -dem Konfigurationsreiter von \prog{tlmgr} im \GUI-Modus. - -\subsubsection{Integrieren von anderen Schriften} -Die Installation von Schriften, die nicht von \TL sind, ist eine recht komplexe Angelegenheit. Sie sollten -sich bereits gut mit dem System auskennen, bevor Sie sich an diese Aufgabe wagen. Schauen Sie vielleicht -vorher in Abschnitt~\ref{sec:tl-fonts} nach, welche Schriften bereits bei \TL mitgeliefert werden. - -Eine Alternative besteht im Benutzen von \XeTeX (s.\,Abschnitt~\ref{sec:tex-extensions}), bei dem -direkt alle vom Betriebssystem installierten Schriften verwendet werden können, ohne dass die Installation -einer \TeX-Unterstützung notwendig ist. - -\subsection{Testen der Installation} -\label{sec:test-install} - -Nach der Installation von \TL wollen Sie es natürlich benutzen, um möglichst schöne Dokumente zu setzen. - -Dieser Abschnitt beschreibt, wie Sie prüfen können, ob Ihr \TL-System funktioniert. -Die folgenden Beispiele sind für Unix, sollten unter Windows und \MacOSX aber sehr ähnlich sein, abgesehen -davon, dass Sie dort eventuell eine grafische Benutzeroberfläche verwenden. - -\begin{enumerate} - -\item Prüfen Sie, ob Sie das Programm \cmdname{tex} ausführen können: - -\begin{alltt} -> \Ucom{tex -{}-version} -TeX 3.1415926 (Web2C 7.5.7) -kpathsea version 3.5.7 -... -\end{alltt} - -Erhalten Sie als Resultat statt der Versionsnummer die Meldung, dass der Befehl nicht gefunden wurde, -so haben Sie wahrscheinlich vergessen, das Verzeichnis mit den ausführbaren Programmen -in Ihren \envname{PATH} aufzunehmen, s.\,Abschnitt~\ref{sec:env} auf S.\,\pageref{sec:env}. - -\item Eine einfache \LaTeX{}-Datei übersetzen: -\begin{alltt} -> \Ucom{latex sample2e.tex} -This is pdfeTeXk, Version 3.1415926... -... -Output written on sample2e.dvi (3 pages, 7484 bytes). -Transcript written on sample2e.log. -\end{alltt} - -Falls dies schief geht, sind wahrscheinlich noch alte Umgebungsvariablen einer vorigen \TeX-Installation -übrig geblieben. Wir empfehlen, die Umgebungsvariablen, die sich auf \TeX{} beziehen, zu entfernen. -Für eine weitere Analyse können Sie \TeX{} anzeigen lassen, wo es bestimmte Dateien sucht, -siehe ">Fehlersuche"< auf Seite~\pageref{sec:debugging}. - -\item Ergebnis auf dem Bildschirm anschauen: -\begin{alltt} -> \Ucom{xdvi sample2e.dvi} -\end{alltt} -(Unter Windows heißt der Befehlt für den Previewer \cmdname{dviout}.) Nun sollte -sich ein Vorschaufenster mit dem soeben gesetzten Beispieldokument öffnen, das die Grundlagen von -\LaTeX{} erläutert (und das Anfänger tatsächlich auch einmal lesen sollten). -Unter Unix muss ein X-Server laufen, damit \cmdname{xdvi} funktioniert; -falls dies nicht der Fall ist oder die Umgebungsvariable \envname{DISPLAY} falsch gesetzt ist, -erhalten Sie die Fehlermeldung \samp{Can't open display}. - -\item Eine \PS{}-Datei erzeugen: -\begin{alltt} -> \Ucom{dvips sample2e.dvi -o sample2e.ps} -\end{alltt} - -\item Direkt eine \acro{PDF}-Datei erzeugen (statt \dvi{}): -\begin{alltt} -> \Ucom{pdflatex sample2e.tex} -\end{alltt} - -\item Eine \acro{PDF}-Datei anschauen: -\begin{alltt} -> \Ucom{gv sample2e.pdf} -\textrm{or:} -> \Ucom{xpdf sample2e.pdf} -\end{alltt} -Leider sind weder \cmdname{gv} noch \cmdname{xpdf} in \TL{} enthalten, daher müssen diese separat installiert -werden, siehe \url{http://www.gnu.org/software/gv} bzw. -\url{http://www.foolabs.com/xpdf}. -(Sie können natürlich auch andere PDF-Viewer verwenden, beispielsweise den Adobe Reader.) - -\item Weitere nützliche Test-Dateien außer -\filename{sample2e.tex}: - -\begin{ttdescription} -\item [small2e.tex] Einfachere Version von \filename{sample2e}, um den Fehler einzugrenzen, wenn Sie -beim Übersetzen von \filename{sample2e} Probleme haben. -\item [testpage.tex] Hiermit können Sie prüfen, ob Ihr Drucker Ihren Ausdruck horizontal oder vertikal verschiebt. -\item [nfssfont.tex] Zum Testen von Fonts und Erzeugen von Schrifttabellen. -\item [testfont.tex] Erzeugen von Schrifttabellen, aber mit plain \TeX. -\item [story.tex] Das einfachste Testdokument von allen (in plain \TeX{}). -Geben Sie am Ende \samp{\bs bye} ein, wenn nach dem Aufruf von \samp{tex -story.tex} der \code{*} erscheint. -\end{ttdescription} - -\end{enumerate} - -\section{Installation im Netzwerk} -\label{sec:netinstall} - -Bei \TL ist nicht nur vorgesehen, dass es von mehreren Benutzern auf einem System verwendet werden kann, -sondern auch in einem Netzwerk. In der normalen Konfiguration von \TL werden nur relative, keine absoluten -Pfade verwendet. Dies erkennt man an Einstellungen in der Datei \filename{$TEXMFMAIN/web2c/texmf.cnf}, -die Zeilen wie die folgenden enthält, -in denen Verzeichnisse relativ zu den Verzeichnissen lokalisiert werden, -in denen sich die Programme befinden: -\begin{sverbatim} -TEXMFMAIN = $SELFAUTOPARENT/texmf -... -TEXMFLOCAL = $SELFAUTOPARENT/../texmf-local -\end{sverbatim} -Daher ist es im Normalfall ausreichend, -das Programm-Verzeichnis in den Suchpfad des Systems aufzunehmen, -alles weitere bestimmt \TL dann automatisch. - -Daher ist es kein Problem, wenn das Grundverzeichnis von \TL als Netzlaufwerk gemountet ist. Tatsächlich -können Sie \TL sogar zunächst lokal installieren und dann auf ein Netzlaufwerk verschieben. - -Für Benutzer von Windows existiert unter \dirname{texmf-doc/source/texlive/texlive-common/w32client} -ein Beispiel-Skript \filename{install-w32client}, das die Einstellungen im Startmenü von Windows -für das Verwenden von \TL über Netzwerk vornimmt. Dieses Skript wird einfach durch Aufruf von -\filename{install-w32client.bat} im selben Verzeichnis gestartet. - -Mehr Informationen zur Konfiguration von \TL und den benutzten Suchpfaden finden Sie im Abschnitt~\ref{sec:kpathsea}. - -\section{Portables \protect\TL{} auf DVD oder USB-Stick} -\label{sec:portable-unix} - -Im Abschnitt~\ref{sec:fromdvd} wurde beschrieben, wie \TL direkt von einer \DVD benutzt werden kann. -Hierbei werden einige Verzeichnisse auf der Festplatte angelegt. Dies ist wahrscheinlich kein Problem, -wenn Sie dies auf Ihrem eigenen Rechner verwenden, aber es kann anders aussehen, wenn Sie auf einem -fremden Rechner ">zu Gast"< sind. - -Sie können die Stellen, an denen beim Benutzen von \TL von \DVD auf der Festplatte Verzeichnisse -angelegt werden, minimieren. Verwenden Sie unter unter Unix das Skript \filename{tl-portable} oder -unter Windows die Batch-Datei \filename{tl-portable.bat}, so werden beim ersten Start die -Konfigurationsdateien für das Verwenden des Live-Modus von \DVD geschrieben. - -Hierzu wird ausschließlich ein Verzeichnis \dirname{~/.tlportable2008} angelegt, in dem diese Dateien -abgelegt werden. Dies kann einen Moment dauern, aber sobald die Dateien einmal da sind, erfolgt -der Start des portablen Modus über die o.\,a. Programme sehr schnell. Die Konfiguration dieses -Modus erfolgt ausschließlich in dem aktuellen Terminalfenster (bzw.\ für die aktuelle Eingabeaufforderung), -der Rest des Systems bleibt davon völlig unberührt. Sie können problemlos in mehreren Sitzungen -parallel den portablen Modus benutzen. - -Wird hier immer ein Verzeichnis auf der Festplatte angelegt, so ist dies komplett überflüssig, wenn -Sie den portablen Modus von USB-Stick verwenden. Kopieren Sie hierfür alle Dateien, die sich direkt im -Verzeichnis \dirname{texlive} der \DVD befinden, sowie (mindestens) die Verzeichnisse \dirname{bin}, -\dirname{texmf}, \dirname{texmf-dist} und \dirname{tlpkg} komplett auf den USB-Stick (dies kann eine -Weile dauern!). Beim Kopieren auf einen mit FAT32 formatierten Stick verwenden Sie unbedingt die Option -zum Auflösen symbolischer Links (\code{cp -L}). Ein auf dem Stick vorhandenes Verzeichnis \dirname{texmf-local} -wird ebenfalls später erkannt und benutzt. - -Wenn Sie nun das Skript \filename{tl-portable} auf dem USB-Stick (wie oben für die \DVD beschrieben) -verwenden, erkennt das Skript, dass der USB-Stick beschreibbar ist und verwendet diesen statt der -Festplatte für die Konfigurationsdateien. - -\section{\cmdname{tlmgr}: Installation verwalten} -\label{sec:tlmgr} - -\begin{figure}[tb] -\tlpng{tlmgr-gui}{\linewidth} -\caption{\prog{tlmgr} im \GUI-Modus. Die Liste der Pakete, Collections und Schemas - wird erst nach Klicken auf ">Load"< angezeigt.}\label{fig:tlmgr-gui} -\end{figure} - -\begin{figure}[tb] -\tlpng{tlmgr-config}{\linewidth} -\caption{\texttt{tlmgr} im \GUI-Modus: Reiter Konfiguration}\label{fig:tlmgr-config} -\end{figure} - -Bei der Installation von \TL wird auch das Programm~\prog{tlmgr} installiert, mit dem Sie anschließend -Ihr \TL-System verwalten können. Die hierfür bisher verwendeten Programme~\prog{updmap}, -\prog{fmtutil} und \prog{texconfig} sind zwar noch vorhanden, werden aber in der Zukunft durch -\prog{tlmgr} ersetzt. Verwenden Sie daher heute schon \prog{tlmgr}. Mit \prog{tlmgr} können Sie -folgende Aufgaben erledigen: -\begin{itemize*} -\item Verfügbare Schemas, Collections und Pakete anzeigen. -\item Installieren, aktualisieren, entfernen, Backup und Restore einzelner Pakete, auf Wunsch mit - Berücksichtigung von Paketabhängigkeiten. -\item Suchen nach Paketen. -\item Anzeigen der Systeme, unter denen \TL läuft; installieren von Binaries für weitere Systeme. -\item Anpassen der Installation, wie Ändern der Papiergröße oder des Quellverzeichnisses für Komponenten - (s.\,Abschnitt~\ref{sec:location}). -\end{itemize*} -\textit{Warning:} \prog{tlmgr} ist für den Live-Modus, bei dem \TL von \DVD genutzt wird, weder gedacht -noch getestet. - -\subsection{\cmdname{tlmgr} im grafischen Modus} -\prog{tlmgr} im \GUI-Modus wird durch -\begin{alltt} -> \Ucom{tlmgr -gui} -\end{alltt} -gestartet. Unter Windows finden Sie das Programm im Start menu: \texttt{Start}, \texttt{Programme}, -\texttt{TeX Live 2008}, \texttt{TeX Live Manager}. Nach Klicken auf ">Load"< -wird eine Liste aller verfügbaren und installierten (letztere durch ">(i)"< gekennzeichnet) angezeigt. Dies -setzt voraus, dass das Verzeichnis, aus dem \TL die Pakete lädt, vorhanden bzw.\ erreichbar ist. - -Abb.~\ref{fig:tlmgr-config} stellt den Reiter zur Konfiguration von \TL dar. - -\subsection{Beispiel zur Verwendung von \cmdname{tlmgr} über Kommandozeile} - -Das folgende Beispiel demonstriert, wie mehrere Pakete -zur Installation hinzu gefügt werden. -Hierbei wird eine andere Adresse zum Herunterladen verwendet. - -\begin{alltt} -> \Ucom{tlmgr -location http://172.16.18.1/tldev install collection-xetex xkeyval} -\end{alltt} -Dies liefert die folgende Ausgabe: -\begin{fverbatim} -install: collection-xetex -install: arabxetex -install: euenc -install: bidi -install: fontspec -install: fontwrap -install: ifxetex -install: philokalia -install: polyglossia -install: xecyr -install: xecyr.i386-linux -install: xepersian -install: xetex -install: xetexconfig -install: xetex.i386-linux -running post install action for xetex -install: xetex-def -install: xetex-pstricks -install: xetexfontinfo -install: xltxtra -install: xunicode -install: xkeyval -running mktexlsr -mktexlsr: Updating /usr/local/texlive/2008/texmf/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-config/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-dist/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-doc/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/../texmf-local/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-var/ls-R... -mktexlsr: Done. -regenerating fmtutil.cnf -running fmtutil-sys --missing -... -Transcript written on xelatex.log. -fmtutil: /usr/local/texlive/2008/texmf-var/web2c/xetex/xelatex.fmt installed. -\end{fverbatim} - -Wie man sieht, beachtet \prog{tlmgr} die Abhängigkeiten von Paketen und installiert im obigen -Beispiel von \XeTeX{} benötigte Komponenten nach. Weiterhin werden automatisch im Anschluss -die Dateilisten der Verzeichnisbäume aktualisiert und fehlende Formate generiert. - -Im folgenden Beispiel wird die Unterstützung für eine weitere Sprache installiert. Im Anschluss -werden automatisch die Formatdateien neu generiert, damit die neuen Trennmuster eingebunden sind. -\begin{alltt} -> \Ucom{tlmgr install collection-langdutch} -\end{alltt} - -Eigenschaften eines Pakets anzeigen: -\begin{alltt} -> \Ucom{tlmgr show collection-wintools} -\end{alltt} - -Hier erhält man folgende Ausgabe: -\begin{fverbatim} -Package: collection-wintools -Category: Collection -ShortDesc: Windows support programs -LongDesc: Utilities for Windows, since they are not readily available there: - gzip, chktex, jpeg2ps, unzip, wget, xpdf. -Installed: Yes -\end{fverbatim} - -Aktualisieren der kompletten Installation: -\begin{alltt} -> \Ucom{tlmgr update -all} -\end{alltt} -Wenn Sie erst wissen wollen, was auf Sie zu kommt, können Sie zunächst folgendes ausprobieren: -\begin{alltt} -> \Ucom{tlmgr update -all -dry-run} -\end{alltt} -oder -\begin{alltt} -> \Ucom{tlmgr update -list} -\end{alltt} - -Zum Anzeigen aller Optionen: -\begin{alltt} -> \Ucom{tlmgr -help} -\end{alltt} - -\section{Hinweise zu Windows} -\label{sec:windows} - -Das Installationsprogramm von \TL\ läuft sowohl unter Windows als auch Unix. Dies war nur dadurch möglich, -dass ältere Versionen von Windows nicht mehr unterstützt werden. Daher kann \TL\ nur noch ab Windows 2000 oder -später installiert werden. - - -\subsection{Windows-spezifische Dinge} -\label{sec:winfeatures} - -Unter Windows kümmert sich das Installationsprogramm auch um folgende Dinge: -\begin{description} -\item[Menüs und Verknüpfungen.] Im Startmenü wird ein Menü ">\TL{}"< hinzu gefügt. Hier sind Einträge für - die grafischen Anwendungen (\prog{tlmgr}, \prog{texdoctk}, den PS\_View PostScript-Previewer) - und einige Verknüpfungen zur Dokumentation vorhanden. Für PS\_View wird eine Verknüpfung auf dem - Desktop angelegt, auf die Sie \PS-Dateien per Drag~\& Drop ziehen können, um diese zu betrachten. -\item[Automatisches Setzen der UmgebungsVariablen.] Hierdurch ist das Setzen dieser Variablen - von Hand überflüssig geworden. -\item[Uninstaller.] Es wird ein Eintrag zum Entfernen von \TL in der Systemsteuerung im Punkt Software angelegt. - Alternativ können Sie \TL über das Programm~\prog{tlmgr} deinstallieren. -\end{description} - -\subsection{Zusätzlich enthaltene Programme} - -\begin{figure}[tb] -\tlpng{psview}{.6\linewidth} -\caption{PS\_View: Anzeige mit hoher Vergrößerung}\label{fig:psview} -\end{figure} - -Zusätzlich werden unter Windows einige Programme installiert, die unter Windows meist noch nicht verfügbar -sind: -\begin{description} -\item[Perl und Ghostscript.] Da Perl und Ghostscript für \TL sehr wichtig ist, werden diese - unter Windows mitgeliefert und werden intern von \TL benutzt. Die in \TL enthaltenen Programme, die - diese Komponenten benötigen, ">wissen"< wo sich diese befinden, ohne dass diese im System durch - Umgebungsvariablen oder Einträge in der Registry sichtbar sind. Es handelt sich um für \TL abgespeckte - Versionen, die zu keinen Konflikten mit eventuell bereits vorhandenen Installationen von Perl und Ghostscript - führen sollten. -\item[Tools für die Kommandozeile.] Für einige unter Unix übliche Programme werden Portierungen für Windows - mitgeliefert. Dies sind z.\,B. \cmdname{gzip}, \cmdname{chktex}, - \cmdname{jpeg2ps}, \cmdname{unzip}, \cmdname{wget} und einige Programme für die Kommandozeile aus der - \cmdname{xpdf}-Suite. (Vom - \cmdname{xpdf}-Viewer selbst gibt es keine Version für Windows, aber der - Sumatra \acro{PDF}-Viewer basiert auf \cmdname{xpdf}: - \url{http://blog.kowalczyk.info/software/sumatrapdf}.) -\item[\texttt{fc-cache}] dient \XeTeX{} zur effizienteren Benutzung von Schriften. -\item[PS\_View.] Weiterhin wird PS\_View installiert, ein neuer PostScript-Viewer, der Freie Software ist, - s.\,Abb.~\ref{fig:psview}. -%\end{description} -% -%\begin{description} -\item[Das Verzeichnis \texttt{support}] wurde bereits in - Abschnitt~\ref{sec:tld} erwähnt. Es enthält einige Programme, die im Zusammenhang mit - \TeX{} nützlich sind, insbesondere einige Editoren mit \TeX-Modus und Benutzeroberflächen für \TeX{}. - Die in diesem Verzeichnis enthaltene Software wird nicht vom Installationsprogramm mit installiert. - Weiterhin findet sich dort der \dvi{}-Previewer \cmdname{dviout}, siehe nächster Abschnitt. -\end{description} - -\subsection{Der Dviout-Previewer} - -Von dieser Version von \TL{} wird leider kein \dvi{}-Previewer für Windows mitinstalliert. -Allerdings können Sie das Programm \prog{dviout} von -Toshio Oshima aus dem Verzeichnis \path{support/dviout/} installieren. Im selben Verzeichnis findet sich -die Datei \filename{README} mit einer kurzen Anleitung zur Installation und Konfiguration von -\prog{dviout} für \TL. Bitte beachten Sie diese Anleitung unbedingt! - -Wenn Sie am Anfang Dokumente mit \cmdname{dviout} anschauen, werden häufig noch Fonts generiert, da -keine fertigen Fontdateien für den Bildschirm mitgeliefert werden. Je mehr Fonts generiert wurden, desto -seltener müssen Schriften nachgeneriert werden, so dass dieser Effekt nach einiger Zeit nur noch selten -auftreten wird. Weitere Informationen finden Sie in der (sehr guten) Online-Hilfe. - -\subsection{Link zu zusätzlicher Software} -Hier einige URLs, hinter denen sich nützliche Software verbirgt: -\begin{description} -\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} -\item[Perl] \url{http://www.perl.org/} mit - Zusatzpaketen von \acro{CPAN}, \url{http://www.cpan.org/}. -\item[ImageMagick] \url{http://www.imagemagick.com}, zum Manipulieren - und Konvertieren von Grafikdateien. -\item[NetPBM] \url{http://netpbm.sourceforge.net/}, ebenfalls zum - Konvertieren von Grafikdateien. -\item[Editoren mit \TeX-Unterstützung] Dies ist lediglich eine grobe Auswahl, - und bekanntlich sind die Geschmäcker verschieden, bei Editoren wie - beim Essen. - \begin{itemize*} - \item \cmdname{GNU Emacs} gibt es auch für Windows, siehe - \url{http://www.gnu.org/software/emacs/windows/ntemacs.html}. - \item \cmdname{Emacs} mit Auc\TeX\ für Windows wird im - \path{support}-Verzeichnis von \TL mitgeliefert. Die Homepage - findet sich unter - \url{http://www.gnu.org/software/auctex}. - \item \cmdname{WinShell} findet sich ebenfalls im \path|support|-Verzeichnis. - Die Homepage lautet \url{http://www.winshell.de}. - \item \cmdname{WinEdt} ist Shareware und verfügbar von - \url{http://www.winedt.com}. - \item \cmdname{Vim} ist freie Software, verfügbar von - \url{http://www.vim.org}. - \item TeXnicCenter ist ebenfalls freie Software, verfügbar von - \url{http://www.toolscenter.org} und Teil von pro\TeX{}t. - \item \cmdname{LEd} ist verfügbar von \url{http://www.ctan.org/support/LEd}. - \item \cmdname{SciTE} ist verfügbar von - \url{http://www.scintilla.org/SciTE.html}. - \end{itemize*} -\end{description} - -\subsection{User Profile unter Windows} -\label{sec:winhome} - -Das Gegenstück von Windows zum HOME-Verzeichnis unter Unix ist das -Verzeichnis \verb|%USERPROFILE%|. Unter Windows XP und Windows 2000 liegt -es meist im Verzeichnis \verb|C:\Documente und Einstellungen\|, unter -Windows Vista \verb|C:\Users\|. In der Datei -\filename{texmf.cnf} und in \KPS{} allgemein wird \verb|~| -sowohl unter Unix und Windows korrekt aufgelöst. - -\subsection{Die Windows-Registry} -\label{sec:registry} - -Windows verwaltet fast all seine Konfigurationseinstellungen in der -Registry. Diese besteht aus einem hierarchisch aufgebauten Baum -von Schlüsseln, wobei mehrere dieser Registry-Bäume existieren. -Die wichtigsten sind \path{HKEY_CURRENT_USER} und \path{HKEY_LOCAL_MACHINE}, -oft abgekürzt als \path{HKCU} bzw.\ \path{HKLM}. -Der \path{HKCU}-Teil der Registry wird im Home-Verzeichnis des Benutzers -gespeichert (s.\,Abschnitt~\ref{sec:winhome}). \path{HKLM} liegt im -Normalfall in einem Unterverzeichnis des Windows-Verzeichnisses. - -In einigen Fällen sind Systeminformationen aus Umgebungsvariablen -ersichtlich, in vielen anderen Fällen liegen diese Informationen -aber in der Registry. - -\subsection{Windows Permissions} -\label{sec:winpermissions} - -In neueren Versionen von Windows wird zwischen normalen Benutzern und -Administratoren unterschieden, wobei nur letztere freien Zugang auf -alle Teile des Betriebsystems haben. Im Gegensatz zu Unix ist es in der -Praxis allerdings häufig so, dass Benutzer zur Klasse der Administratoren -gehören und daher doch alle Freiheiten haben. Trotzdem haben wir einigen -Aufwand getrieben, damit \TL auch unter Windows ohne Administrator-Rechte -installiert werden kann. - -Falls der Benutzer, der \TL installiert, Administrator-Rechte besitzt, -wird \TL für alle Benutzer des Systems installiert, d.\,h. Verknüpfungen, -Menüs und Systemeinträge für alle Nutzer angelegt. Ansonsten werden diese -nur für den aktuellen Benutzer angelegt. Falls Sie Administrator sind, -\TL aber trotzdem nur für sich und nicht für alle installieren wollen, -können Sie dem Programm~\prog{install-tl} die Option~\optname{non-admin} -mit geben. - -Unabhängig davon wird grundsätzlich angenommen, dass das Wurzelverzeichnis -von \TL unter \verb|%PROGRAMFILES%| liegen soll. Allerdings testet das -Installationsprogramm, ob dieses Verzeichnis für den aktuellen Benutzer -schreibbar ist. - -Ein Problem entsteht, wenn \TL ohne Administrator-Rechte installiert -wird und sich bereits ein \TeX{}-System im systemweiten Suchpfad -befindet. Windows benutzt zuerst den Suchpfad des Systems, erst dann -den spezifischen Suchpfad des Nutzers, so dass hier immer zuerst -das alte \TeX-System gefunden wird. Als Workaround wird hier eine -Verknüpfung mit einer Eingabeaufforderung erzeugt, in der das -Programmverzeichnis von \TL im Suchpfad vor den Standard\-such\-pfad -geschrieben wird. Dies bedeutet, dass in diesem Fall nur in einer -Eingabeaufforderung verfügbar ist, die über diese Verknüpfung gestartet -wird. - -% ============================================================== -% don't use \Webc so the \uppercase in the headline works. -\section[Anleitung zum Web2C-System]{Anleitung zum \Webc-System} - -{\Webc} besteht aus einer Reihe von Programmen, die zusammen ein komplettes -\TeX-System darstellen. Dazu gehören natürlich \TeX, -\MF, \MP, {\BibTeX} usw. - -Die erste Implementierung eines \TeX-Systems -in der Programmiersprache C stammt von Tomas~Rokicki und datiert zurück in das -Jahr 1987. Rokicki benutzte als Basis sog. Change-Files unter \acro{UNIX}, die ursprünglich von -Howard~Trickey und Pavel~Curtis entwickelt wurden. Tim~Morgan hat dieses -System, für das der Name Web-to-C\@ eingeführt wurde, gepflegt. -1990 hat Karl~Berry mit Unterstützung vieler Helfer die Weiterentwicklung -übernommen und 1997 an Olaf~Weber weitergegeben, der es 2006 wieder an -Karl zurück gab. - -\Webc{} läuft unter \acro{UNIX}, 32-bit-Versionen von Windows, \MacOSX{} -und auf weiteren Betriebssystemen. Es benutzt die -Original-Quelldateien von Donald E.~Knuth und weitere in der -Sprache {\web} entwickelte Programme als Basis und übersetzt diese -in C-Quell-Code. Darüber hinaus bietet das System viele Makros und -Funktionen zur Nutzung der originalen \TeX-Software. Hier eine -Liste der Basisprogramme eines \TeX-Systems: - -\begin{description} -%\renewcommand{\makelabel}[1]{\descriptionlabel{\mdseries\cmdname{#1}}} -\item[bibtex] Verwalten von Bibliographien -\item[dmp] \cmdname{troff}-nach-MPX-Konverter (\MP-Bilder) -\item[dvicopy] Umwandeln von virtuellen Zeichensätzen in DVI-Dateien -\item[dvitomp] DVI-nach-MPX-Konverter (\MP-Bilder) -\item[dvitype] Textanzeige aus DVI-Dateien -\item[gftodvi] Erzeugen von Prüfausgaben für Zeichensätze -\item[gftopk] Packen von Zeichensätzen -\item[gftype] Anzeige von Zeichensätzen als ASCII-Graphik -\item[makempx] Anzeige von \MP-Beschriftungen -\item[mf] Zeichensatzerzeugung -\item[mft] formatierte Ausgabe von \MF-Quellen -\item[mpost] \MF-ähnliches Grafikprogramm -\item[mpto] Extrahieren von \MP-Beschriftungen -\item[newer] Vergleich von Dateierstellungsdaten -\item[patgen] Erzeugen von Trennmustern -\item[pktogf] Entpacken von Zeichensätzen -\item[pktype] Anzeige gepackter Zeichensätze -\item[pltotf] Umwandeln von Property-Listen in \file{.tfm}-Dateien -\item[pooltype] Anzeige der Bildschirmtexte eines WEB-Programms -\item[tangle] Konverter {\web} nach Pascal -\item[tex] \TeX-Programm -\item[tftopl] Umwandeln einer \file{.tfm}-Datei in eine Property-Liste -\item[vftovp] Umwandeln eines virtuellen Zeichensatzes in eine Property-Liste -\item[vptovf] Umwandeln einer Property-Liste in einen virtuellen Zeichensatz -\item[weave] \web-Code als \TeX-Dokumentation -\end{description} - -Die genaue Funktionsweise und die möglichen Parameter sind der -Beschreibung der jeweiligen Pakete bzw.\ der \Webc-Dokumentation zu entnehmen. -Trotzdem wird ein Überblick über Zusammenspiel und Funktionsweise der -\Webc-Programme Ihnen sicherlich helfen, besser mit dem System zurechtzukommen. - -Zunächst verstehen alle Programme die grundlegenden Parameter der -\acro{GNU}-Software: - -\begin{description} -\item[\texttt{-{}-help}] kurzer Hilfstext -\item[\texttt{-{}-verbose}] ausführliche Ausgaben beim Programmablauf -\item[\texttt{-{}-version}] Ausgabe der Versionsnummer -\end{description} - -Die Programme des \Webc-Systems benutzen zum Lokalisieren der benötigten -Dateien im Dateisystem die \KPS-Bibliothek (\url{http://tug.org/kpathsea}). Diese Bibliothek optimiert und -beschleunigt den Suchprozess im Dateisystem. Ihre Arbeitsweise wird durch -einige Umgebungsvariablen und eine Kon"-fi"-gu"-ra"-tions"-da"-tei gesteuert. -\Webc~7.5 kann mehr als einen Dateibaum gleichzeitig verwalten und ermöglicht -somit die schon beschriebene \TL-Installation unter Verwendung der -\acro{CDROM} oder {\DVD} mit der Ablage modifizierter Konfigurationsdateien -und zusätzlicher Zeichensätze in einem zweiten Dateibaum. Die Suche -nach Dateien wird durch die Analyse der Datei \file{ls-R} beschleunigt, -die in jedem Wurzelverzeichnis eines \TeX-Dateibaums vorhanden ist. -Sie enthält für jede Datei die genaue Position im Dateibaum relativ -zum Wurzelverzeichnis. - -% ------------------------------------------------------------- -\subsection[Dateisuche mit der Kpathsea-Bibliothek]{Dateisuche mit der \protect\KPS-Bibliothek} -\label{sec:kpathsea} - -Wir beschreiben zunächst den grundlegenden Suchmechanismus der \KPS-Bibliothek. - -Ein \emph{Suchpfad} ist eine durch Kommata oder Semikola getrennte Liste von -\emph{Pfadkomponenten}, die üblicherweise Verzeichnisnamen darstellen. -Ein Suchpfad kann sich aus vielen Komponenten zusammensetzen. Die Suche nach -einer Datei \samp{my-file} über den Suchpfad \samp{.:/dir} bewirkt, dass -{\KPS} jede Komponente nacheinander überprüft, also zunächst -\samp{./my-file} und dann \samp{/dir/my-file}. Als Ergebnis wird entweder die -erste gefundene Datei oder eine Liste aller passenden Dateien geliefert. - -Um auf allen Dateisystemen effizient arbeiten zu können, verwendet {\KPS} ggf. andere -Datei-/""Verzeich"-nis-Separatoren als \samp{:} und \samp{/}. - -Beim Überprüfen einer Pfadkomponente \var{p} überprüft {\KPS} zunächst, -ob eine Dateinamen"=Datenbank (siehe auch Dateinamen"=Datenbank auf -Seite~\pageref{sec:filename-database}) für die Pfadkomponente zuständig ist, -d.\,h. beispielsweise steht die Datenbank in einem Verzeichnis, das im Pfad -vor der zu überprüfenden Komponente \var{p} steht. In diesem Fall wird -zur Bestimmung der Position der gesuchten Datei die Datenbank herangezogen. - -Nur wenn keine passende Datenbank existiert oder wenn die Datei nicht -in der Datenbank gefunden wird, durchsucht {\KPS} das Dateisystem. Diese -zeitaufwändige Suche kann über die Spezifikation der Pfadkomponente \var{p} -mit dem Präfix \samp{!!}\ unterbunden werden. Zur Suche erzeugt {\KPS} eine -Liste der Verzeichnisse, die im Pfadelement enthalten sind, und durchsucht -jedes dieser Verzeichnisse nach der gesuchten Datei. - -Für Dateien kann auch ein Schalter \samp{file~must~exist} gesetzt -werden (">Datei muss vorhanden sein"<). Wenn dieser Schalter nicht -gesetzt ist und beispielsweise über das \TeX-Kommando -\cs{openin} eine VF-Datei wie \file{cmr10.vf} gelesen werden -soll, wäre es falsch, nach dieser Datei zu suchen, weil es sie gar -nicht gibt. Speziell für neu installierte VF-Dateien sollten Sie -also unbedingt die Dateinamen"=Datenbank (\cmdname{ls-R}) -aktualisieren, weil die Dateien sonst nicht gelesen werden und -kein Fehler angezeigt wird. Dieser Vorgang wiederholt sich für jede -Komponente eines Suchpfades: zunächst wird die Datenbank -überprüft, danach ggf. das Dateisystem. Wird die Datei gefunden, -stoppt die Suche (normalerweise) und als Ergebnis wird der komplette Pfad zur -gesuchten Datei ausgegeben. - -Außer Verzeichnisnamen dürfen Pfadkomponenten für {\KPS} folgende -Elemente enthalten: (verschachtelte) Vorgaben, Umgebungsvariablen, -Werte aus der Konfigurationsdatei, Home-Verzeich"-nisse von -Benutzern und Startverzeichnisse für eine rekursive Suche. Diese -Elemente werden vor einer Dateisuche von {\KPS} in gewöhnliche -Verzeichnis- oder Dateinamen expandiert. Diese Expansion wird in -den folgenden Abschnitten erklärt, und zwar genau in der -Reihenfolge, wie die Elemente auch von {\KPS} bearbeitet werden. - -Beachten Sie, dass {\KPS} bei absoluten und explizit relativen Komponenten, -d.\,h. wenn die Komponente mit den Zeichen \samp{/}, \samp{./} oder -\samp{../} beginnt, nur überprüft, ob die Datei existiert. - -\ifSingleColumn -\else - -\begin{figure*}[tp] -\verbatiminput{examples/ex5.tex} -\setlength{\abovecaptionskip}{0pt} - \caption{An illustrative configuration file sample} - \label{fig:config-sample} -\end{figure*} -\fi - -% .............................................................. -\subsubsection{Bestandteile von Pfadkomponenten}\label{Path-sources} -\label{sec:path-sources} - -Ein Suchpfad kann aus vielen verschiedenen Bestandteilen aufgebaut werden. -Dies sind in der Reihenfolge, wie {\KPS} sie auswertet: - -\begin{enumerate} -\item - eine benutzerdefinierte Umgebungsvariable, z.\,B. \envname{TEXINPUTS}: - Wird an den Inhalt der Variablen ein Punkt und ein Programmname angehängt, wie - beispielsweise bei \envname{TEXINPUTS.latex}, hat diese Form Vorrang - vor den ">gewöhnlichen"< Variablen. -\item - Einträge aus programmspezifischen Konfigurationsdateien, - beispielsweise zum Programm {\dvips} eine Zeile \samp{S /a:/b} - in der Konfigurationsdatei \file{config.ps} -\item - Einträge aus der \KPS-Konfigurationsdatei \file{texmf.cnf}, - z.\,B. \samp{TEXINPUTS=/c:/d} (siehe folgenden Text) -\item - Einstellung beim Übersetzen der Programme -\end{enumerate} - -Unter Verwendung der Parameter zur Fehlersuche können Sie sich diese -Werte für einen Suchpfad auch anzeigen lassen. (Siehe dazu den Abschnitt -Fehlersuche auf Seite~\pageref{sec:debugging}.) - -% .............................................................. -\subsubsection{Konfigurationsdateien} - -%\tolerance=3500 -Die \KPS-Bibliothek liest zur Laufzeit die \emph{Konfigurationsdateien} mit den Namen -\file{texmf.cnf}. Der zugehörige Suchpfad zum Auf"|finden dieser -Konfigurationsdateien steht in der Umgebungsvariablen \envname{TEXMFCNF} -(die Voreinstellung ist \file{texmf/web2c}). {\KPS} liest \emph{alle} -Dateien mit den Namen \file{texmf.cnf}, die es in diesem Suchpfad findet. -Die zuerst gelesenen Definitionen haben dabei Vorrang vor später gelesenen -Werten. -Wenn der Suchpfad auf \dirname{.:\$TEXMF} steht, überschreiben die Einstellungen -in \file{./texmf.cnf} diejenigen in \dirname{\$TEXMF/texmf.cnf}. - -%\tolerance=1500 - -Im Folgenden wird die Syntax der Datei \file{texmf.cnf} angegeben. -Konsultieren Sie zum besseren Verständnis beim Lesen die auf der -{\acro{CDROM}} oder {\DVD} enthaltene Konfigurationsdatei. -%, die ab Seite~\pageref{app:texmf.cnf} im Anhang dieser Anleitung -% abgedruckt ist. - -\begin{itemize} -\item - Kommentare beginnen mit einem \samp{\%} und erstrecken sich bis zum - Zeilenende. -\item - Leerzeilen werden überlesen. -\item - Ein \samp{\bs} am Zeilenende fasst die aktuelle mit der folgenden Zeile - zusammen. Leerraum in der Folgezeile wird \emph{nicht} überlesen. -\item - Sonstige Zeilen haben den folgenden Aufbau: - -\begin{alltt} - \var{Variable}[.\var{Programmname}] [=] \var{Wert} -\end{alltt}% - - Das Zeichen ">="< und umgebender Leerraum dürfen entfallen. -\item - Der Name von \var{Variable} kann alle Zeichen außer Leerzeichen, - \samp{=} und \samp{.} enthalten. Verwenden Sie am besten nur die Zeichen - \samp{A-Za-z\_}. -\item - Wenn das Suffix ">\code{.\var{Programmname}}"< angegeben wird, gilt die - Variable nur für das entsprechende Programm ">\var{Programmname}"< oder - ">\code{\var{Programmname}.exe}"<. Auf diese Weise können - beispielsweise verschiedene - \TeX-Formate mit unterschiedlichen Suchpfaden arbeiten. -\item - \texttt{\var{Wert}} darf alle Zeichen außer \texttt{\%} und \texttt{@} - enthalten. - Die Einschränkung der Werte auf bestimmte Programme über ein Suffix - ist nicht zulässig. Ein \samp{;} in \texttt{\var{Wert}} wird unter - \acro{UNIX} in \samp{:} umgewandelt. Dadurch ist die Verwendung der gleichen - Konfigurationsdateien für \acro{UNIX} und \acro{DOS}/""Windows"=Systeme möglich. -\item - Die Definitionen werden komplett eingelesen, bevor eine Expansion - stattfindet. Dadurch können Sie die Variable schon vor Ihrer Definition - referieren. -\end{itemize} - -Der Ausschnitt einer Konfigurationsdatei demonstriert diese -Möglichkeiten. -\ifSingleColumn -\verbatiminput{examples/ex5.tex} -\else -Betrachten Sie Abbildung~\ref{fig:config-sample}. -\fi - -% .............................................................. -\subsubsection{Expansion von Pfadkomponenten} -\label{sec:path-expansion} - -{\KPS} verwendet in Suchpfaden ähnliche Zeichen und Konstrukte wie -\acro{UNIX}-Shells. Beispielsweise wird die Definition -\verb|~$USER/{foo,bar}//baz| in alle Unterverzeichnisse von \file{foo} und -\file{bar} unterhalb vom Home-Verzeichnis von \dirname{\$USER} expandiert, -die eine Datei oder ein Unterverzeichnis namens \file{baz} enthalten. Der -Expansionsmechanismus wird im Folgenden erklärt. - -% .............................................................. -\subsubsection{Expansion der Voreinstellungen} -\label{sec:default-expansion} - -Wenn der Suchpfad mit der höchsten Priorität (siehe hierzu ">Bestandteile von -Pfadkomponenten"< auf Seite~\pageref{sec:path-sources}) einen zusätzlichen -(vorangestellten, nachgestellten oder verdoppelten) Doppelpunkt enthält, -wird an dieser Stelle der Suchpfad eingefügt, der als nächstes in der -Hierarchie folgt. Auch bei diesem gilt dieselbe Regel. Wenn beispielsweise -die Umgebungsvariable - -\begin{alltt} -> \Ucom{setenv TEXINPUTS /home/karl:} -\end{alltt} - -gesetzt wird (hier: C-Shell) und in \file{texmf.cnf} die Variable -\code{TEXINPUTS} folgenden Wert erhält - -\begin{alltt} - .:\$TEXMF//tex -\end{alltt} - -dann lautet der Suchpfad schließlich: - -\begin{alltt} - /home/karl:.:\$TEXMF//tex -\end{alltt} - -Da es sinnlos wäre, denselben Pfad mehrfach einzufügen, wird die Ersetzung -nur einmal vorgenommen, und zwar in der Reihenfolge vorne, hinten und -Mitte. Mehrfach verdoppelte Doppelpunkte bleiben unverändert. - -% .............................................................. -\subsubsection{Expansion geschweifter Klammern} - -Die Expansion geschweifter Klammern ist zur Definition mehrerer -\TeX-Hierarchien sehr nützlich. Beispielsweise wird |v{a,b}w| -zu |vaw:vbw|. Verschachtelungen sind dabei erlaubt. -Diese Technik wird dazu benutzt, durch eine Zuweisung an -\code{\$TEXMF} verschiedene \TeX-Hierarchien einzuführen. -Als Beispiel finden Sie in \file{texmf.cnf} folgende Definition -(etwas gekürzt, tatsächlich ist es etwas komplexer): -%(Zeile 75): %%%% to be checked !!!! checked&corrected vrws 01.06.05 - -\begin{verbatim} - TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN} -\end{verbatim} - -Eine Anwendung wie - -\begin{verbatim} - TEXINPUTS = .;$TEXMF/tex// -\end{verbatim} -%$ -führt dann dazu, dass erst im aktuellen Verzeichnis gesucht wird, dann -im gesamten Dateibaum \code{\$TEXMFHOME/tex} und \code{\$TEXMFLOCAL/tex} -(auf der Festplatte) und -schließlich im gesamten Dateibaum \dirname{\$TEXMFVAR/tex} sowie -\code{\$TEXMFMAIN/tex} (nur in der Datenbank \file{ls-R}) -durchsucht wird. Dadurch kann man bequem -zwei parallel installierte \TeX-Hierarchien durchsuchen, -beispielsweise eine unveränderliche auf \acro{CDROM}/{\DVD} und eine dynamisch -angepasste auf Festplatte, in der neue Programmversionen und zusätzliche -Zeichensätze installiert werden. Durch die Verwendung der Variablen -\code{\$TEXMF} in allen Definitionen wird grundsätzlich zuerst der -neuere Dateibaum durchsucht. - -% .............................................................. -\subsubsection{Expansion von Unterverzeichnissen} -\label{sec:subdirectory-expansion} - -Zwei oder mehrere aufeinanderfolgende Schrägstriche (\texttt{//}) in -einer Pfadkomponente, die auf einen Verzeichnisnamen \var{d} folgen, -werden expandiert zu allen Unterverzeichnissen von \var{d}. Dieser -Vorgang findet rekursiv statt, wobei erst alle Verzeichnisse auf -einer Ebene bearbeitet werden, dann deren Unterverzeichnisse, usw. -Auf den jeweiligen Ebenen ist nicht beeinflussbar, in welcher -Reihenfolge die Unterverzeichnisse bearbeitet werden. - -Wenn nach den Schrägstrichen Namen angegeben werden, dann werden nur -Unterverzeichnisse mit passenden Namen in die Suche einbezogen. -Beispielsweise wird \samp{/a//b} in die Pfade \file{/a/1/b}, -\file{/a/2/b}, \file{/a/1/1/b} usw. expandiert, aber nicht -zu \file{/a/b/c} oder \file{/a/1}. -(Jeweils vorausgesetzt, dass die Verzeichnisse existieren.) - -Mehrere \samp{//}-Konstruktionen innerhalb einer Pfadkomponente -sind zulässig, allerdings nicht am Pfadanfang. - -% .............................................................. -\subsubsection{Liste der Sonderzeichen und ihre Bedeutung: eine Zusammenfassung} - -Die folgende Zusammenfassung fasst alle Sonderzeichen zusammen, die in den -\KPS"=Konfigurationsdateien auftreten können: - -% ++++++++++++++++++++++++ -\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} -% ++++++++++++++++++++++++ - -\begin{description} -\item[\CODE{:}] Trennzeichen für Pfadkomponenten; als erstes - oder letztes Zeichen im Pfad bewirkt es die - Expansion der Voreinstellungen. -\item[\CODE{;}] Trennzeichen für Pfadkomponenten für andere - Rechnerplattformen als \acro{UNIX} (Verwendung wie - ">\code{:}"<) -\item[\CODE{\$}] Expansion von Variableninhalten -\item[\CODE{\string~}] Home-Verzeichnis eines Benutzers (Tilde) -\item[\CODE{\char`\{...\char`\}}] Expansion geschweifter Klammern: - beispielsweise wird |a{1,2}b| zu |a1b:a2b|. -\item[\CODE{//}] Expansion von Unterverzeichnissen: tritt niemals - am Anfang einer Pfadkomponente auf. -\item[\CODE{\%}] Kommentar -\item[\CODE{\bs}] Konkatenation mit Folgezeile(n) -\item[\CODE{!!}] Einschränkung der Suche \emph{ausschließlich} auf die - Dateinamen"=Datenbank: Das Dateisystem wird \emph{nicht} - durchsucht! -\end{description} - -% ------------------------------------------------------------- -\subsection{Dateinamen"=Datenbanken} -\label{sec:filename-database} - -{\KPS} unternimmt etliche Anstrengungen, um den Zugriff auf Festplatte und -\acro{CDROM}/{\DVD} zur Suche nach Dateien zu reduzieren. Auf \TeX-Systemen mit -vielen Unterverzeichnissen kann die Suche in jedem möglichen Verzeichnis -nach einer bestimmten Datei eine lange Zeit in Anspruch nehmen, besonders -wenn einige Hundert Zeichensatzverzeichnisse durchforstet werden müssen. -Um dieses Problem abzumildern, benutzt {\KPS} eine Art Datenbankdatei -namens \file{ls-R}, die die Zuordnung von Dateinamen auf Verzeichnisse -enthält. Dadurch muss nicht jedesmal die Festplatte durchsucht werden. - -Eine zweite Datenbank in der Datei \file{aliases} kann eine Zuordnung -zwischen den Namen in \file{ls-R} und weiteren Namen vornehmen und so -beispielsweise hilfreich bei der Umsetzung von \samp{8.3}-\acro{DOS}-Dateinamen -auf die ">echten"<, aussagekräftigen Dateinamen zur Seite stehen. - -% .............................................................. -\subsubsection{Die \texttt{ls-R}-Datenbank} -\label{sec:ls-R} - -Wie schon öfters erwähnt, muss die Dateinamen"=Datenbank in der Datei -\file{ls-R} gespeichert sein. Sie sollten eine solche Datenbank für jede -\TeX-Hierarchie (normalerweise in \code{\$TEXMF}) Ihres Systems anlegen. -Die meisten \TeX-Systeme arbeiten nur mit einer Hierarchie. {\KPS} sucht -die Datenbanken \file{ls-R} über den Pfad \code{TEXMFDBS}. - -Es wird empfohlen, die Pflege der \code{ls-R}-Dateien dem mitgelieferten -Skript \cmdname{mktexlsr} zu überlassen. Dieses Skript wird automatisch von den -verschiedenen \samp{mktex*}-Skripten aufgerufen. Das Skript ruft -grob gesagt den Befehl - -\begin{alltt} -cd /\var{your}/\var{texmf}/\var{root} && ls -LAR ./ >ls-R -\end{alltt} - -auf, falls das Kommando \code{ls} Ihres Rechners eine Ausgabe im richtigen -Format liefert. (So wie das \acro{GNU}-\code{ls}.) Wenn Sie ganz sichergehen -wollen, dass die Datenbank immer auf dem neuesten Stand ist, sollten Sie sie -in regelmäßigen Abständen mit Hilfe eines \cmdname{crontab}-Eintrags -aktualisieren lassen. Dadurch wird nach einer Installation eines -Pakets per Hand trotzdem sichergestellt, dass die Datenbank aktuell ist. - -Wenn eine Datei nicht über die Datenbank gefunden wird, sucht -{\KPS} normalerweise auf der Festplatte weiter. Wenn eine Pfadkomponente -mit \samp{!!} beginnt, wird dagegen niemals die Festplatte durchsucht. - -% .............................................................. -\subsubsection{\cmdname{kpsewhich}: Dateisuche} -\label{sec:invoking-kpsewhich} - -Mit dem Programm \cmdname{kpsewhich} können Sie unabhängig vom Aufruf -irgendeines \TeX-Programms nach Dateien in der \TeX-Hierarchie suchen -(als schnellere Alternative zu dem Befehl \cmdname{find}). Dies -wird von den verschiedenen \samp{mktex\dots}-Skripten bis zum -Exzess vorexerziert. - -\begin{alltt} -> \Ucom{kpsewhich \var{option}{\dots} \var{filename}{\dots}} -\end{alltt} - -Die Optionen werden entweder mit \samp{-} oder mit \samp{-{}-} eingeleitet. -Jede eindeutige Abkürzung ist zulässig. - -Argumente der Kommandozeile, die keine Optionen darstellen, werden als -Dateinamen interpretiert. Für jeden Dateinamen wird der erste passende -Pfad gemeldet. Um eine Liste aller passenden Pfade zu erhalten, müssen Sie -das \acro{UNIX}-Kommando \cmdname{find} aufrufen. - -Im Folgenden werden die häufiger benutzten Optionen beschrieben. - -\begin{description} -\item[\texttt{-{}-dpi=}\var{num}]\mbox{}\\ - Stellt die Auf"|lösung für die Suche nach Zeichensätzen - (nur \file{.gf} oder \file{.pk}) auf \var{num}\,dpi. Alternativ - kann die Option \optname{-D} (kommt von \dvips) benutzt werden. - Voreinstellung ist~600. -\item[\texttt{-{}-format=}\var{name}]\mbox{}\\ - Setzt das Format zur Suche auf \var{name}. Per Voreinstellung - versucht \cmdname{kpsewhich} das Format über den Dateinamen - zu erschließen. Bei Formaten ohne zugeordnete Namens\-endung wie den - zu {\MP} gehörenden Dateien und den Konfigurationsdateien zu - {\dvips} müssen Sie den entsprechenden Namen so eingeben, wie er - \KPS{} bekannt ist. -\item[\texttt{-{}-mode=}\var{string}]\mbox{}\\ - Setzt für die Zeichensatzsuche den Generierungsmodus (betrifft nur - \file{.gf}- oder \file{.pk}-Dateien). Normalerweise werden alle - Zeichensätze gemeldet. -\item[\texttt{-{}-must-exist}]\mbox{}\\ - Es wird versucht, die Dateien notfalls durch eine Suche auf der - Festplatte zu finden. Normalerweise wird nur die \file{ls-R}-Datenbank - konsultiert. -\item[\texttt{-{}-path=}\var{string}]\mbox{}\\ - Sucht entlang des angegebenen Pfads statt des Standardpfads, - der auf Grund der Endung gewählt wird. Alle Expansionen sind - zulässig. Bei Verwendung der Option \texttt{-{}-path} darf nicht - die Option \texttt{-{}-format} angegeben werden. -\item[\texttt{-{}-progname=}\var{name}]\mbox{}\\ - Setzt den Programmnamen für die genauere Variablenspezifikation - über \samp{.\var{Programmname}}. Voreinstellung ist \samp{kpsewhich}. -\item[\texttt{-{}-show-path=}\var{name}]\mbox{}\\ - Zeigt den Suchpfad für die angegebene Namens\-endung. Diese kann entweder - als Namens\-endung (\samp{.pk}, \samp{.vf}, usw.) oder als Name (wie bei der - Option \optname{-{}-format}) spezifiziert werden. -\item[\texttt{-{}-debug=}\var{num}]\mbox{}\\ - Legt den Umfang für die Fehlersuche fest. -\end{description} - -% .............................................................. -\subsubsection{Anwendungsbeispiele} -\label{sec:examples-of-use} - -Wir schauen uns nun die Funktionsweise von {\KPS} anhand einiger Beispiele an. - -\begin{alltt} -> \Ucom{kpsewhich article.cls} - /usr/local/texmf-dist/tex/latex/base/article.cls -\end{alltt} - -Wir suchen unter den \TeX-Quelldateien nach der Datei \file{article.cls}. -Da die Namens\-endung \samp{.cls} eindeutig ist, müssen wir den Typ -\samp{.tex} nicht angeben. Die \samp{texmf-dist}-Hierarchie enthält die -Datei im Unterverzeichnis \dirname{tex/latex/base}. Ähnlich bereiten -die folgenden Beispiele auf Grund eindeutiger Namens\-endungen keine Probleme. - -\begin{alltt} -> \Ucom{kpsewhich array.sty} - /usr/local/texmf-dist/tex/latex/tools/array.sty -> \Ucom{kpsewhich latin1.def} - /usr/local/texmf-dist/tex/latex/base/latin1.def -> \Ucom{kpsewhich size10.clo} - /usr/local/texmf-dist/tex/latex/base/size10.clo -> \Ucom{kpsewhich small2e.tex} - /usr/local/texmf-dist/tex/latex/base/small2e.tex -> \Ucom{kpsewhich tugboat.bib} - /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib -\end{alltt} - -Beim letzten Beispiel handelt es sich übrigens um eine \BibTeX-Literaturdatenbank -für \textsl{TUGBoat}-Artikel. - -\begin{alltt} -> \Ucom{kpsewhich cmr10.pk} -\end{alltt} - -Zeichensatzdateien mit der Namens\-endung \samp{.pk} werden -von Anzeige- oder Druckaufbereitungsprogrammen wie {\dvips} und -\cmdname{xdvi} verwendet. Nachdem wir aufgrund der Voreinstellung keine \file{.pk}-Dateien verwenden, -sondern die \PS-\TypeI-Zeichensätze, die auf der \acro{CDROM}/{\DVD} enthalten -sind, wird auch keine \file{.pk}-Datei angezeigt. - -\begin{alltt} -> \Ucom{kpsewhich wsuipa10.pk} -\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk -\else /usr/local/texmf-var/fonts/pk/ljfour/public/ -... wsuipa/wsuipa10.600pk -\fi\end{alltt} -Für diesen Zeichensatz (Teil der \acro{IPA}-Fonts% -\footnote{\acro{IPA}: International Phonetic Alphabet} -von der Universität von Washington) liegen noch keine -\TypeI-Umsetzungen vor und \samp{.pk}-Dateien müssen generiert werden. Da unser voreingestellter \MF-Modus -\samp{ljfour} eine Auf"|lösung von 600\,dpi besitzt, -finden wir (nachdem er schon einmal gebraucht und automatisch -erzeugt wurde) eine entsprechende Instanz dieses Zeichensatzes. - -\begin{alltt} -> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} -\end{alltt} - -Durch die Angabe ">\optname{-dpi=300}"< interessieren wir uns nur -für Zeichensätze mit der Auf"|lösung 300\,dpi. Es wurde keiner gefunden. -Programme wie {\dvips} oder \cmdname{xdvi} lassen einen solchen fehlenden -Zeichensatz durch den Aufruf des Skripts \cmdname{mktexpk} mit entsprechenden -Parametern automatisch erzeugen. - -Als nächstes wenden wir uns den Header- und Konfigurationsdateien -von {\dvips} zu. -Zunächst suchen wir nach der Konfiguration für die \TeX-Unterstützung, -dem Prolog \file{tex.pro}. Danach suchen wir die allgemeine Konfigurationsdatei -(\file{config.ps}) und schließlich die \PS-Zeichensatzzuordnungsdatei -\file{psfonts.map}. Dateien dieser Art haben seit der 2004er-Version der {\TL} ihre eigenen Suchpfade und einen neuen Aufbewahrungsort im \OnCD{texmf}-Baum. Da die Namens\-endung \samp{.ps} nicht eindeutig ist, -müssen wir den gewünschten Typ (\samp{dvips config}) -für die Datei \file{config.ps} spezifizieren. - -\begin{alltt} -> \Ucom{kpsewhich tex.pro} - /usr/local/texmf/dvips/base/tex.pro -> \Ucom{kpsewhich --format="dvips config" config.ps} - /usr/local/texmf/dvips/config/config.ps -> \Ucom{kpsewhich psfonts.map} - /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map -\end{alltt} - -Jetzt suchen wir nach den Dateien für den \PS-Zeichensatz ">URW Times"<. -Nach dem Namensschema von Karl~Berry beginnen die Namen mit ">\texttt{utm}"<. -Zunächst suchen wir die Konfigurationsdatei, die den Namen der -Zeichensatzzuordnungsdatei enthält. - -\begin{alltt} -> \Ucom{kpsewhich --format="dvips config" config.utm} - /usr/local/texmf-dist/dvips/psnfss/config.utm -\end{alltt} - -Diese Datei enthält folgende Anweisung: - -\begin{alltt} - p +utm.map -\end{alltt} - -Die angegebene Datei \file{utm.map} wollen wir als nächstes suchen: - -\begin{alltt} -> \Ucom{kpsewhich utm.map} - /usr/local/texmf-dist/fonts/map/dvips/times/utm.map -\end{alltt} - -Diese Zuordnungsdatei wird im Unterverzeichnis \file{urw} bei den -Hilfsdateien für {\dvips} gefunden. Sie enthält die Dateinamen der -\TypeI-\PS-Zeichensätze, die für URW Times benutzt werden. Ein -kleiner Auszug aus dieser Datei: - -\begin{alltt} - utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} -\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb -\else /usr/local/texmf-dist/fonts/type1/ -... urw/utm/utmr8a.pfb -\fi\end{alltt} - -Diese Beispiele sollten deutlich gemacht haben, wie leicht bestimmte Dateien -im \TeX-Dateibaum gefunden werden können. Dies ist sehr wichtig, wenn Sie -den Verdacht haben, dass eine falsche Version einer Datei verwendet wird: -Sie lassen sich einfach die verwendete Datei von \cmdname{kpsewhich} -anzeigen. - -% .............................................................. -\subsubsection{Fehlersuche} -\label{sec:debugging} - -Manchmal ist wichtig, bis ins Detail nachzuvollziehen, wie ein Programm eine -bestimmte Datei findet. Zu diesem Zweck bietet die \KPS-Bibliothek verschiedene -Stufen für den Umfang der Fehlersuche an. - -\begin{itemize} -\item[\texttt{\ 1}] \code{stat}-Aufrufe (Überprüfung, ob Datei - existiert); mit einer aktuellen \file{ls-R}-Datenbank sollten Sie fast - keine Meldungen erhalten. -\item[\texttt{\ 2}] Zugriffe auf Suchlisten (wie \file{ls-R}-Datenbanken, - Zuordnungsdateien (\texttt{.map}), Konfigurationsdateien) -\item[\texttt{\ 4}] Öffnen und Schließen von Dateien -\item[\texttt{\ 8}] Auf"|listen der voreingestellten Pfade für Extensionen -\item[\texttt{16}] Verzeichnisliste für jede Pfadkomponente (nur bei Festplattenzugriff) -\item[\texttt{32}] Suchaktionen nach Dateien -\item[\texttt{64}] Werte von Variablen. -\end{itemize} - -Durch die Angabe von \samp{-1} setzen Sie alle Stufen gleichzeitig. -Für eine effiziente Fehlersuche sollten Sie sich auf die wichtigsten -Ausgaben beschränken. - -Für {\dvips} gibt es einen ähnlichen Mechanismus zur Erzeugung -von Analysemeldungen, um herauszufinden, warum bestimmte Dateien geöffnet -wurden bzw.\ wo vielleicht das Problem liegt, wenn Dateien nicht gefunden -werden. - -Da fast alle Programme die \KPS-Bibliothek benutzen, können Sie die -gewünschte Stufe auch über die Umgebungsvariable \envname{KPATHSEA\_DEBUG} -einstellen, indem Sie einen der Werte oder eine additive Kombination -spezifizieren. - -Anmerkung für Windows-Benutzer: Es ist nicht einfach, alle Meldungen in eine Datei umzulenken. Für die Fehlersuche -jedoch ist die folgende (temporäre!) Vereinbarung sinnvoll: - -\indent\texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log} - -Wir betrachten als Beispiel eine kleine \LaTeX-Quelldatei mit dem Namen -\file{hello-world.tex} mit folgendem Inhalt: - -\begin{verbatim} - \documentclass{article} - \begin{document} - Hello World! - \end{document} -\end{verbatim} - -Diese Datei verwendet nur einen Zeichensatz, nämlich \file{cmr10}. Wir sehen uns -jetzt einmal genau an, wie {\dvips} die \PS-Datei erzeugt. -Da wir die \TypeI-Variante der Computer-Modern-Roman-Zeichensätze -verwenden wollen, haben wir die Option \optname{-Pcms} verwendet. - -\begin{alltt} -> \Ucom{dvips -d4100 hello-world -Pcms -o} -\end{alltt} - -Hier haben wir als Stufe zur Fehlersuche eine Kombination der Stufe~\code{4} von -{\dvips} (siehe \dvips-Handbuch, -\dirname{texmf/doc/html/dvips/dvips\_toc.html}?). -%\ifSingleColumn -%We get something -%like the following (we have rearranged the output for easier display): -%\begin{alltt}\small -%\input{examples/ex6.tex} -%\end{alltt} -%\else -Die Ausgabe sieht ungefähr so wie in -Abbildung~\ref{fig:dvipsdbga} dargestellt aus (die Ausgabe wurde für einen besseren Überblick -etwas umgestaltet). - -\begin{figure*}[tp] -\centering -\input{examples/ex6a.tex} -\caption{Suche nach Konfigurationsdateien}\label{fig:dvipsdbga} - -\bigskip - -\input{examples/ex6b.tex} -\caption{Suche nach Prologdateien}\label{fig:dvipsdbgb} - -\bigskip - -\input{examples/ex6c.tex} -\caption{Suche nach Font-Dateien}\label{fig:dvipsdbgc} -\end{figure*} - -Zunächst sucht {\dvips} (bzw.\ \KPS) seine Konfigurationsdateien, -nämlich \file{texmf.cnf} (das die Pfade der anderen Dateien enthält), -dann die Dateinamen"=Datenbank \file{ls-R} (zur Optimierung der Suche) -und die Datei \file{aliases}, mit deren Hilfe für eine Datei -mehrere Namen vereinbart werden können, z.\,B. um die kurzen -\samp{8.3}-\acro{DOS}-Namen mit aussagefähigen, langen Namen zu assoziieren. -Danach wird die allgemeine \dvips-Konfigurationsdatei -\file{config.ps}, anschließend die benutzerspezifische Konfigurationsdatei -\file{.dvipsrc} (wird hier \emph{nicht} gefunden) gesucht. -Als letztes sucht {\dvips} die Zuordnungsdatei für -Computer-Modern-{\PS}"=Zeichensätze \file{config.cms} (bedingt durch die -Option \optname{-Pcms} beim Aufruf von \dvips). Diese -Datei enthält die Dateinamen der Listen, die die Zuordnung zwischen -Dateinamen und Zeichensatznamen herstellen. - -\begin{alltt} -> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} - p +ams.map - p +cms.map - p +cmbkm.map - p +amsbkm.map -\end{alltt} - -{\dvips} versucht, diese Dateien und zusätzlich die -allgemeine Zeichensatzzuordnungstabelle \file{psfonts.map} zu -laden, die immer konsultiert wird; der letzte Teil von -Abschnitt~\ref{sec:examples-of-use} erklärt diese Tabellen genauer. - -Jetzt erfolgt die normale Startmeldung von \dvips: - -\begin{alltt}\ifSingleColumn -dvips(k) 5.94a -kpathsea version -Copyright (C) 2003 Radical Eye Software. -... -\else\small{}dvips(k) 5.94a -kpathsea version -Copyright (C) 2003 Radical Eye Software. -... -\fi\end{alltt}% decided to accept slight overrun in tub case -\ifSingleColumn -Danach wird nach \file{texc.pro} gesucht: - -\begin{alltt}\small -kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro -\end{alltt} -\else -Danach wird nach \file{texc.pro} gesucht (siehe Abbildung~\ref{fig:dvipsdbgb}). -\fi -Dann gibt {\dvips} Datum und Uhrzeit aus und meldet den Dateinamen -der erzeugten \PS-Datei \file{hello-world.ps}. Jetzt wird die -Zeichensatzdatei \file{cmr10} benötigt, die {\dvips} als -">resident"< meldet. - -\enlargethispage{1ex} -\begin{alltt}\small -TeX output 1998.02.26:1204' -> hello-world.ps -Defining font () cmr10 at 10.0pt -Font cmr10 is resident. -\end{alltt} - -Es geht weiter mit \file{cmr10.tfm} und einigen weiteren Prologdateien, -deren Ausgaben wir hier weglassen. Letztlich wird die \TypeI-Zeichensatzdatei -\file{cmr10.pfb} gesucht (und gefunden) und in die Ausgabedatei integriert -(siehe letzte Zeile). - -\begin{alltt}\small -kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, - path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: - /var/tex/fonts/tfm//). -kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm -kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, - ... - -kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb -[1] -\end{alltt} - -% ------------------------------------------------------------- -\subsection{Einstellungen zur Laufzeit} - -Zu den willkommenen Erweiterungen von {\Webc} zählt die Möglichkeit, -zur Laufzeit einige Speicher"-größen über die Datei \file{texmf.cnf} anpassen -zu können (insbesondere die Größe einiger Stacks). Eine ausführliche Liste -der veränderbaren Parameter finden Sie in der Datei \file{texmf.cnf}. -Die wichtigsten Werte sind: - -\begin{description} -\item[\texttt{main\_memory}]\mbox{}\\ - Arbeitsspeicher für \TeX, {\MF} und {\MP} in Worten: Für jede Einstellung - muss eine eigene Format-Datei erstellt werden. Allerdings können Sie - mehrere Versionen von {\TeX} unter verschiedenen Namen erzeugen und - in der Konfigurationsdatei jeweils eigene Einträge vorsehen. Hier gibt - es ein Monster-{\TeX} namens \samp{hugetex} mit der zugehörigen Format-Datei - \file{hugetex.fmt}, wobei der spezielle Wert der - Variablen \texttt{main\_memory} dann - aus der Datei \file{texmf.cnf} gelesen wird. -\item[\texttt{extra\_mem\_bot}]\mbox{}\\ - Extraspeicher für ">große"< \TeX-Datenstrukturen wie Boxen, Glue, - Breakpoints, usw.: Besonders bei Anwendung von {\PiCTeX} sollte dieser - Wert erhöht werden. -\item[\texttt{font\_mem\_size}]\mbox{}\\ - Anzahl der Worte für Speicherung von Zeichensatzinformationen: Entspricht - ungefähr dem Speicherbedarf der gelesenen \acro{TFM}-Dateien. -\item[\texttt{hash\_extra}]\mbox{}\\ - Zusätzlicher Platz für Suchlisten: In der Hauptliste können - ca. 10000~Einträge verwaltet werden. Bei einem Buch mit vielen Querverweisen - reicht dieser Platz unter Umständen nicht aus. - Die Voreinstellung für \texttt{hash\_extra} ist \texttt{50000}. -\end{description} - -Natürlich sind diese Parameter kein Ersatz für eine wirklich dynamische -Speicherverwaltung. Mit der gegenwärtigen Version von {\TeX} ist dieses -Konzept aber nur extrem schwer zu implementieren; darum stellt dieses -Verfahren eine praktikable Lösung dar. - -\begin{comment} -%\clearpage -% ============================================================== -\section{Installation von {\TeX} auf einer neuen \acro{UNIX}-Plattform} - -Wenn Sie eine Rechnerplattform einsetzen, für die wir keine Binärdateien -zur Verfügung gestellt haben, müssen Sie {\TeX} und die zugehörigen -Programme mit Hilfe der Quell-Codes selbst übersetzen. Das ist gar nicht so -schwer, wie es klingt. Alles, was Sie brauchen, finden Sie auf der {\DVD} -im Verzeichnis \texttt{source}. - -Zunächst sollten Sie jedoch die von {\TeX} benötigten Dateien durch -eine Installation ohne Binärdateien auf die Festplatte kopieren bzw. -durch ">Mounten"< der {\DVD} verfügbar machen. - -% ------------------------------------------------------------- -\subsection{Voraussetzungen} - -Zum Übersetzen von {\TeX} und allen weiteren benötigten -Programmen benötigen Sie ca. 100\,MB Festplattenkapazität. -Dazu kommen ein \acro{ANSI}-C-Compiler, \cmdname{make} sowie -ein Scanner- und Parser-Generator. Die \acro{GNU}-Programme -(\cmdname{gcc}, \acro{GNU}-\cmdname{make}, \cmdname{m4}, -\cmdname{flex} und \cmdname{bison}) sind praxiserprobt -und auf den meisten Plattformen verfügbar. Eventuell können -Sie auch andere C-Compiler oder \cmdname{make}-Programme einsetzen, -doch dann sollten Sie sich wirklich gut mit Ihrem System auskennen, -wenn es Schwierigkeiten während des Übersetzungsprozesses gibt. -Der Befehl \cmdname{uname} muss einen gültigen Namen liefern. - -% ------------------------------------------------------------- -\subsection{Konfiguration} - -\begin{itemize} -\item Beginnen Sie mit einer ganz normalen \TL-Installation auf -Festplatte (siehe Abschnitt~\ref{sec:install-disk} auf -Seite~\pageref{sec:install-disk}). Das Installieren der -fertigen Binaries können Sie getrost überspringen. - -\item Dann entpacken Sie das komprimierte Archiv (\cmdname{tar}) in -\dirname{source} auf Ihre Festplatte und wechseln in dieses Verzeichnis. - -\item Legen Sie einen Pfad fest, unter dem das \TeX-System -installiert werden soll. Natürlich sollte das derselbe Pfad sein, -den Sie schon zum Kopieren der Daten verwendet haben -(z.\,B. \dirname{/usr/local} oder \dirname{/usr/local/TeX}). -\end{itemize} - -Die automatische Systemerkennung und -anpassung wird durch -\textsf{configure} mit folgendem Aufruf gestartet: - -\begin{alltt} -> \Ucom{./configure -prefix=/usr/local/TeX} -\end{alltt} - -Bei der Option \optname{prefix} geben Sie das Verzeichnis an, in dem sich die -bereits kopierten \TL-Dateien befinden; -dieses Verzeichnis wird weiter strukturiert (\dirname{\$TEXDIR} -ist dabei das Installationsverzeichnis): - - -\begin{tabular}{>{\ttfamily}ll@{}} - \dirname{\$TEXDIR/man} & Anleitungen im - \acro{UNIX}-\cmdname{man}-Format\\ - \dirname{\$TEXDIR/share/texmf} & \TeX-Daten mit Zeichensätzen, - Makros, usw.\\ - \dirname{\$TEXDIR/info} & Anleitungen im - \acro{GNU}-\cmdname{info}-Format\\ - \dirname{\$TEXDIR/bin/\$PLATFORM} & ausführbare Programme\\ -\end{tabular} -%$ - -Wenn Sie wollen, können Sie ">\dirname{share/}"< als Namensbestandteil -von \OnCD{texmf} weglassen, da sowohl -\dirname{\$TEXDIR/share/texmf} als auch \dirname{\$TEXDIR/texmf} -automatisch von \cmdname{configure} erkannt werden. Sollten Sie ein anderes -Verzeichnis vorziehen, müssen Sie dieses \cmdname{configure} mit dem -Kommandozeilenparameter \optname{-{}-datadir} mitteilen. - -Wenn Sie die erkannte Plattform nicht als \dirname{\$PLATFORM} im -Pfad der ausführbaren Programme haben wollen, sondern z.\,B. -direkt in \dirname{\$TEXDIR/bin} installieren wollen, verwenden Sie -die Option \optname{-{}-disable-multiplatform}. - -Zum Weglassen spezieller \TeX-Systeme wie {\OMEGA} oder {\eTeX} gibt -es eine Reihe von Optionen, die Sie durch die Eingabe von -\samp{./configure --help} angezeigt bekommen. - -% ------------------------------------------------------------- -\subsection{Aufruf von \cmdname{make}} - -Vergewissern Sie sich, dass die Shell-Variable \envname{noclobber} nicht -gesetzt ist und geben - -\begin{alltt} -> \Ucom{make world} -\end{alltt} - -ein. Jetzt können Sie sich entspannt zurücklehnen oder wie ein -{\TeX}ie sagt: |\relax|. - -Eine gute Idee ist auch das Speichern der Meldungen beim -Übersetzen durch das Anlegen eines Protokolls: - -\begin{alltt} -> \Ucom{sh -c "make world >world.log 2>\&1" \&} -\end{alltt} - -Nehmen Sie nicht fälschlicherweise nach dem Durchlauf von \cmdname{make} -an, dass alles gut gegangen ist, sondern vergewissern sich durch eine -Kontrolle des Protokolls. (\acro{GNU} \cmdname{make} zeigt Fehler -z.\,B. immer mit der Zeichenkette ">\texttt{***}"< an.) -Außerdem sollten Sie sich vergewissern, dass alle ausführbaren -Programme auch erzeugt wurden: - -\begin{alltt} -> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} -> \Ucom{ls | wc} -\end{alltt} - -Das Ergebnis sollte über 200 liegen (Sie können die exakte Zahl -mit der Anzahl der lauf"|fähigen Programme [Binaries] im Verzeichnis \OnCD{bin} vergleichen). -Der Aufruf \samp{make~world} ist übrigens äquivalent zu -\samp{make~all~install~strip}. - -Wenn für den Aufruf von \samp{make~install} besondere -Systemverwalterrechte notwendig sein sollten, können Sie die -Anweisung \samp{make~world} auch in zwei Durchgängen absetzen: - -\begin{alltt} -> \Ucom{make all} -> \Ucom{su} -> \Ucom{make install strip} -\end{alltt} - -Nachdem Sie Ihre Binaries installiert haben, sollten Sie die normalen -Installationsnacharbeiten durchführen, die im Abschnitt~\ref{sec:postinstall} -auf Seite~\pageref{sec:postinstall} beschrieben sind. - -Wenn Sie lauf"|fähige Programme erstellt haben und diese Anderen zur Verfügung stellen wollen, sollten Sie uns kontaktieren. Wir würden uns freuen, sie auf den \TL-\acro{WWW}-Seiten anzubieten. -\end{comment} - -% ============================================================== -\section{Danksagungen} - -Die {\TL} ist eine gemeinsame Arbeit faktisch aller {\TeX} Users -Groups. - -Die Entwicklung des vorliegende \TL-Releases wurde Karl~Berry geleitet; -die übrigen Haupt-Mitarbeiter sind im Folgenden aufgelistet. - -\begin{itemize} -\item Den englisch-, deutsch-, niederländisch-, und polnisch-sprachigen - \TeX-Anwendervereinigun\-gen (\acro{TUG}, \acro{DANTE} e.V., - \acro{NTG}, and \acro{GUST}), - die zusammen die technische und administrative Infrastruktur - zur Verfügung stellen. Wir würden uns freuen wenn Sie bei einer der - Anwendervereinigungen Mitglied werden. -\item Dem \acro{CTAN} Team, insbesondere Robin Fairbairns, Jim Hef{}feron, - und Rainer Schöpf, das die \TL{}-CD-Images und die Infrastruktur - für Paketupdates zur Verfügung stellt, von denen \TL{} abhängt. -\item Peter Breitenlohner (und das \eTeX\-Team) für den stabilen Grundstock zu {\TeX}s Zukunft, und Peter speziell für wertvolle Hilfe zum Verwenden - von GNU autotools in \TL; -\item Thomas~Esser, der mit dem exzellenten {\teTeX} die Basis - für dieses {\TL} schuf; -\item Michel~Goossens, als Coautor der englischen Original-Dokumentation; -\item Eitan~Gurari, mit dessen {\TeX4ht} die \HTML-Version dieser - Anleitung erstellt wurde und der unermüdlich daran gearbeitet - hat, es auf Zuruf zu verbessern; -\item \Thanh, Martin~Schröder und das pdf\TeX-Team (\url{http://pdftex.org}), - die die Arbeiten zur Erweiterung der Möglichkeiten von - {\TeX} fortgesetzt haben; -\item Hans Hagen, für zahlreiche Tests und Aktivitäten, damit \ConTeXt{} - (\url{http://pragma-ade.com}) ein Teil von \TL sein kann; -\item Taco Hoekwater, für neue Entwicklungen von MetaPost und (Lua)\TeX\ - (\url{http://luatex.org}), und ebenfalls für die Unterstützung beim - \ConTeXt-Teil von \TL; -\item Pawe{\l} Jackowski für das Installationsprogramm \cmdname{tlpm} für - Windows, - Tomasz {\L}uczak für \cmdname{tlpmgui} in früheren Versionen von \TL; -\item Akira Kakuto, für Windows-Programme im Rahmen seines - \acro{W32TEX} Distribution - (\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}); - -\item Jonathan Kew und \acro{SIL}, für die - Neuentwicklung von Xe\TeX{} und die Zeit und Mühe es in \TL{} zu - integrieren, sowie für die erste Version des Mac\TeX-Installers; - -\item Dick Koch für die Betreuung von Mac\TeX\ (\url{http://tug.org/mactex}); - - -\item Reinhard Kotucha, für die Unterstützung bei der Infrastruktur von - \TL{} und das Installationsprogramm, für seine Windows-Untersuchungen, für das \texttt{getnonfreefonts} - Script, und vieles mehr; - -\item Siep Kroonenberg, für wertvolle Beiträge zur Infrastruktur von - \TL\,2008 und den Installer, insbesondere unter Windows, und für einen - Großteil der Arbeit, die Dokumentation dafür zu schreiben; - -\item Petr~Olsak, der das tschechische und slowakische Material sehr sorgfältig er- und überarbeitet hat; - -\item Toshio Oshima, für den \cmdname{dviout}-Previewer für Windows; - -\item Manuel P\'egouri\'e-Gonnard, für die Mithilfe beim Aktualisieren - von Paketen, der Dokumentation und Arbeit an \cmdname{tldoc}; - -\item Fabrice Popineau für die erste Windows-Version von \TL und Mithilfe - bei der französischen Dokumentation; - -\item Norbert Preining, Hauptkoordinator für \TL{}-Infrastruktur und - den Installer, für die Koordination der Debian Version von \TL{} - (zusammen mit Frank Küster), und die daraus resultierenden - Verbesserungsvorschläge; - -\item Sebastian Rahtz für die Erfindung von \TL und die langjährige - Leitung des Projekts; - -\item Vladimir Volovich für viele substanzielle Mithilfe, und dafür, dass - er es möglich gemacht hat, \cmdname{xindy} in \TL aufzunehmen; - -\item Staszek~Wawrykiewicz, der Haupttester für alles, was mit {\TeX} zusammen hängt, Koordinator der polnischen - Beiträge, Windows-Installation und mehr; - -\item Olaf~Weber für die Geduld beim Pflegen von \Webc; -\item Gerben~Wierda für das Erstellen und Pflegen des \MacOSX-Teils und für viele Integrations- und Testarbeiten; -\item Graham~Williams, dessen Arbeit das Makro- und Paketverzeichnis möglich gemacht hat. -\end{itemize} - -\textbf{Lauf"|fähige Programme:} -Reinhard Kotucha (\pkgname{x86\_64-linux}), -Tim Arnold (\pkgname{hppa-hpux}), -Randy Au (\pkgname{amd64-freebsd}), -Edd Barrett (\pkgname{i386-openbsd}), -Karl Berry (\pkgname{i386-linux}), -Akira Kakuto (\pkgname{win32}), -Dick Koch (\pkgname{universal-darwin}), -Manfred Lotz (\pkgname{i386-freebsd}), -Norbert Preining (\pkgname{alpha-linux}), -Arthur Reutenauer (\pkgname{sparc-linux}), -Thomas Schmitz (\pkgname{powerpc-linux}), -Apostolos Syropoulos (\pkgname{i386-solaris}), -Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-solaris}), -Olaf Weber (\pkgname{mips-irix}). - -Informationen dazu, wie Binaries für \TL{} erzeugt werden, -finden sich unter \url{http://tug.org/texlive/build.html}. - -\textbf{Dokumentation und Anpassung der Übersetzungen:} - -\begin{itemize*} -\item Karl~Berry (Englisch), -\item Daniel~Flipo (Französisch), -\item Klaus Höppner \& Hartmut~Henkel (Deutsch) -\item Petr~Sojka \& Jan~Busa (Tschechisch/""Slowakisch), -\item Boris~Veytsman (Russisch), -\item Staszek~Wawrykiewicz (Polnisch). -\end{itemize*} - -Natürlich haben wir am meisten Donald~Knuth zu danken, einmal dafür, dass er {\TeX} erfand und dann dafür, dass er es -der Welt schenkte. - -% ------------------------------------------------------------- -\section{Geschichtliches}\label{sec:history} - -Diese Ausgabe der {\TL} ist in Zusammenarbeit der \TeX{} Users Group (\acro{TUG}), der -\acro{UKTUG}, der französischen \TeX-Vereinigung GUTenberg -und der deutschsprachigen \TeX-Anwendervereinigung (DANTE e.\,V.) -unter Mithilfe der niederländischen, tschechischen/""slowakischen, -indischen, polnischen und russischen \TeX-Benutzergruppen -entstanden. - -\subsection{Vergangenheit} - -Die niederländische \TeX-Benutzergruppe hatte Ende 1993 mit der -Produktion der 4All\TeX-{\acro{CDROM}} für \acro{MS-DOS} die Diskussion angeregt, -eine einzige {\acro{CDROM}} für alle Rechnersysteme zu entwickeln. Zum -damaligen Zeitpunkt war dieses Ziel zu hoch gesteckt, doch immerhin -entstand aus dieser Diskussion nicht nur die sehr erfolgreiche -4All\TeX-{\acro{CDROM}}, sondern auch die \acro{TUG}-Arbeitsgruppe zur Definition -der {\TeX} Directory Structure \TDS, die die zur Arbeit mit {\TeX} -notwendigen und hilfreichen Dateien in eine konsistente und -handhabbare Verzeichnisstruktur einbettet. Das ">Final~Draft"<-Dokument, -das diese Verzeichnisstruktur festlegt, wurde in der Dezember-Ausgabe -1995 der TUGBoat veröffentlicht. Schon frühzeitig war den Beteiligten -klar, dass eine {\acro{CDROM}} auf der Basis der {\TDS} sehr zu begrüßen wäre. -Die \TL-{\acro{CDROM}} war das direkte Resultat der Beratungen der -\TDS-Arbeitsgruppe. Außerdem hat der Erfolg der 4All\TeX-{\acro{CDROM}} -klargemacht, dass ein ähnliches System auch für \acro{UNIX}-Benutzer eine -Erleichterung darstellen würde. Dies war der zweite Beweggrund für -die \TL-\acro{CDROM}. - -Im Herbst 1995 wurde das Projekt, eine \TDS-basierte \acro{UNIX}-{\acro{CDROM}} -zu entwickeln, in Angriff genommen. Sehr schnell stießen die -Verantwortlichen auf das \teTeX-System von Thomas~Esser als -idealen Ausgangspunkt für diese Arbeit, weil es verschiedene -Rechnerplattformen unterstützte und für die Arbeit mit verschiedenen -Dateisystemen vorgesehen war. Anfang 1996 wurde in Zusammenarbeit -mit Thomas~Esser ernsthaft mit der Arbeit begonnen und im Mai~1996 -die erste Ausgabe der {\acro{CDROM}} veröffentlicht. - -Anfang 1997 stellte -Karl~Berry eine neue Version seines \Webc-\TeX-Systems vor, das -schon nahezu alle Ausstattungsmerkmale aufwies, die Thomas~Esser -mit {\teTeX} verwirklicht hatte. Die \acro{TUG} entschied sich daraufhin, -die zweite Version der {\acro{CDROM}} auf der Basis von {\Webc} unter -Verwendung des Installations-Skripts \cmdname{texconfig} aus dem -\teTeX-Paket zu entwickeln. - -Die dritte Ausgabe basierte auf der -inzwischen von Olaf~Weber gepflegten und weiter entwickelten -{\Webc}~Version~7.2; {\TL} unterstützte fast alle Eigenschaften -der zur selben Zeit entstandenen neuen Version von \teTeX. - -Die vierte Ausgabe folgte demselben Schema, indem ihr neue -Versionen von {\teTeX} und {\Webc}~(7.5) zugrunde lagen. -Fast die gesamte {\acro{CDROM}} wurde einer kritischen Überprüfung -unterzogen, wobei besonders darauf geachtet wurde, dass doppelte -Dateien entfernt wurden und die Einordnung der Pakete konsistent -erfolgte. Zudem enthielt diese Ausgabe ein komplettes Windows-Setup. - -Für die fünfte Ausgabe im März~2000 wurden wiederum große Teile der -{\acro{CDROM}} ersetzt, wobei Hunderte von überarbeiteten Paketen aufgenommen -wurden. {\OMEGA}, {pdf\TeX} und Teile der \TeX-Support-Programme (hier -insbesondere \cmdname{xdvi}, \cmdname{dvips} und \cmdname{tex4ht}) -lagen in neuer Version vor. -Die Hauptänderung bei der \TL\,5 betraf die \samp{non-free}-Software. -Alles auf dieser {\acro{CDROM}} war nun in Übereinstimmung mit den \emph{Debian -Free Software Guidelines} (\url{http://www.debian.org/intro/free}). -Wir haben unser Bestes versucht, die Lizenzbedingungen aller Pakete -zu überprüfen, sind aber dankbar, wenn wir auf Fehler hingewiesen werden. - -Die sechste Ausgabe der {\TL} vom Juli/August~2001 -enthielt die neuesten Versionen aller Pakete und Programme. -Das neue Installationskonzept stellte die größte Änderung dar: -Der Benutzer konnte nun viel genauer -gewünschte bzw.\ nicht erwünschte Sammlungen -und Pakete auswählen. Dabei wurden die sprachspezifischen Sammlungen -komplett überarbeitet, so dass sie jetzt automatisch nicht nur -Makros, Fonts usw. installierten, sondern zusätzlich die notwendigen -Einträge in \file{language.dat} vornahmen. - -Die siebte Ausgabe vom Mai~2002 enthält als größte -Änderungen {\MacOSX} und wieder unzählige Updates aller Pakete und Programme. -Ein wesentliches Ziel war zudem die Wiedererstellung einer gemeinsamen -Quelle mit {\teTeX}, um das Auseinanderlaufen seit \TL\,5 und \TL\,6 -zu korrigieren. - -\subsection{2003} - -Im Jahr 2003 war die Flut von Updates und neuen Paketen so groß geworden, -dass wir feststellen mussten: ">{\TL} passt nicht mehr auf eine einzelne -\acro{CDROM}"<. Und so wurde sie in drei verschiedene Distributionen aufgeteilt -(siehe Abschnitt~\ref{sec:tl-coll-dists} auf Seite~\pageref{sec:tl-coll-dists}). -Des Weiteren: - -\begin{itemize} -\item Auf Wunsch des \LaTeX-Teams wurde der Standard für \cmdname{latex} - und \cmdname{pdflatex} verändert; beide benutzen nun {\eTeX} als Basis - (siehe Seite~\pageref{text:etex}). -\item Die neuen ">Latin Modern Fonts"< wurden aufgenommen (und werden - zur Benutzung empfohlen). -\item Der Support für Alpha-\acro{OSF} wurde aufgegeben (den - \acro{HPUX}-Support hatte es schon zuvor ereilt), da - niemand mehr in der Lage war, neue Binaries zu kompilieren. -\item Das Setup für Windows wurde grundlegend überarbeitet. - Zum ersten Mal wurde eine integrierte Umgebung eingeführt, - die auf \cmdname{XEmacs} basiert. -\item Wichtige Hilfsprogramme für Windows (Perl, Ghost\-script, - Image\-Magick, Ispell) werden nun im \TL-Verzeichnis - installiert. -\item Die von \cmdname{dvips}, \cmdname{dvipdfm} und \cmdname{pdftex} - benutzten Font-Mapfiles werden vom neuen Programm - \cmdname{updmap} generiert und in \dirname{texmf/fonts/map} - installiert. -\item \TeX, {\MF} und {\MP} geben nun die meisten 8"~Bit-Input"~Zeichen (Position 32 und oberhalb) unverändert - aus in (\verb|\write|)-Files, Logfiles und auf dem Terminal. - Das bedeutet, dass sie \emph{nicht} mit der \verb|^^|-Notierung - übersetzt ausgegeben werden. Auf der \TL\,7 war diese - Übersetzung abhängig von der \cmdname{locale}-Einstellung des - Systems; nun beeinflussen \cmdname{locale}-Einstellung nicht - {\TeX}s Programmverhalten. Falls Sie aus irgendwelchen - Gründen die \verb|^^|-Ausgabe benötigen, müssen Sie in Ihrem System - die Datei \file{texmf/web2c/cp8bit.tcx} umbenennen - (zukünftige Versionen werden eine sauberere Schnittstelle zur - Kontrolle dieses Verhaltens anbieten). -\item Die Dokumentation wurde grundlegend überarbeitet. -\item Zum Abschluss einigten wir uns auf eine neue Edition-Nummerierung. - Ab diesem Jahr trägt die {\TL} statt einer fortlaufenden Nummer - die Jahreszahl: \TL~2003. -\end{itemize} - -\subsection{2004} - -\begin{itemize} -\item Wenn Sie lokal installierte Zeichensätze mit ihren eigenen \filename{.map}- oder (weniger wahrscheinlich) - \filename{.enc}-Dateien benutzen, müssen Sie möglicherweise diese Dateien verschieben. - - Nach den \filename{.map}-Dateien wird jetzt in den \dirname{fonts/map}-Unterverzeichnissen im - \envname{TEXFONTMAPS}-Pfad gesucht (in jedem \filename{texmf}-Baum). - Gleichzeitig werden \filename{.enc}-Dateien jetzt in den \dirname{fonts/enc}-Unterverzeichnissen entlang des - \envname{ENCFONTS}-Pfads gesucht. Das Programm \cmdname{updmap} versucht, bei problematischen Dateien zu warnen. - - Informationen darüber, wie das gehandhabt wird, und zusätzliche Informationen finden Sie unter - \url{http://tug.org/texlive/mapenc.html}. - -\item Die \TK\ wurde für all diejenigen, die diese Implementierung {\Webc} vorziehen, um eine \MIKTEX-basierte und - installierbare {\acro{CDROM}} erweitert. Siehe dazu auch Abschnitt~\ref{sec:overview-tl} auf - Seite~\pageref{sec:overview-tl}. - -\item In der {\TL} wurde der umfangreiche \dirname{texmf}-Baum früherer Versionen durch drei Teilbäume ersetzt: - \OnCD{texmf}, \OnCD{texmf-dist} und \OnCD{texmf-doc}. Siehe dazu Abschnitt~\ref{sec:tld} auf - Seite~\pageref{sec:tld} und die \filename{README}-Dateien in den drei Zweigen. - -\item Alle \TeX-relevanten Eingabedateien sind jetzt in den \dirname{tex}-Unterverzeichnissen der - \dirname{texmf*}-Bäume zusammengefasst und nicht mehr in den parallelen Verzeichnissen \dirname{tex}, - \dirname{etex}, \dirname{pdftex}, \dirname{pdfetex}, usw. Siehe dazu - \CDref{texmf-doc/doc/english/tds/tds.html\#Extensions}{\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}. - -\item Hilfs-Skripte, die der Anwender nicht selbst aufruft, werden jetzt in den \mbox{neuen} - \dirname{scripts}-Unterverzeichnissen der \dirname{texmf*}-Bäume aufbewahrt. Nach ihnen wird per - \samp{kpsewhich -format=texmfscripts} gesucht. Wenn Sie Programme einsetzen, die solche Skripte aufrufen, müssen - sie angepasst werden. Siehe dazu \CDref{texmf-doc/doc/english/tds/tds.html\#Scripts} -{\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}. - -\item (Fast) alle Formate interpretieren -- an Stelle einer Übersetzung durch die \verb|^^|-Notation -- mittels - des ">translation files"< \filename{cp227.tcx} die meisten Zeichen als direkt ausgebbar. Insbesondere werden - die Zeichen an den Positionen 32--256, zusätzlich \acro{TAB}, \acro{VT} (vertical tab; vertikaler Tab) und - \acro{FF} (form feed; Seitenvorschub), als druckbar angesehen und daher nicht übersetzt. Ausnahmen sind - plain \TeX, bei dem nur die Zeichen an den Positionen 32--127 druckbar sind, {\ConTeXt} (mit druckbaren Zeichen an - den Positionen 0--255) und die \OMEGA-verwandten Formate. Dieses voreingestellte Verhalten ist (fast) identisch - mit dem in \TL\,2003; es ist aber jetzt klarer und mit umfangreicheren Anpassungsmöglichkeiten implementiert. - Siehe dazu \CDref{texmf/doc/web2c/web2c.html\#TCX-files} -{\texttt{texmf/doc/web2c/web2c.html\#TCX-files}}. - - \textbf{Anmerkung:} Da {\TeX} byte-orientiert ist, können bei einer Unicode-Eingabe (2-Byte-Zeichen) im Kontext - von Fehlermeldungen Folgen von 1-Byte-Zeichen ausgegeben werden. - -\item \cmdname{pdfetex} ist jetzt die voreingestellte ">Engine"< für alle Formate mit Ausnahme von - \mbox{(plain-)\cmdname{tex}} selbst (natürlich generiert es \dvi-Code, wenn es als \cmdname{latex}, usw. - aufgerufen wird.). Das bedeutet unter vielen anderen Dingen, dass die mikrotypographischen Fähigkeiten von - \cmdname{pdftex} - wie auch die Erweiterungen von {\eTeX} in \LaTeX, \ConTeXt usw. zur Verfügung stehen - (\OnCD{texmf-dist/doc/etex/base/}). - - Das bedeutet, dass es \emph{wichtiger denn je} ist, das Paket \pkgname{ifpdf} zu benutzen (es arbeitet sowohl mit - {plain \TeX} als auch mit \LaTeX), da der einfache Test, ob \cs{pdfoutput} oder ein anderer \TeX-Grundbefehl - (primitive) definiert ist, nicht verlässlich genug ist für die Entscheidung, ob eine PDF-Ausgabe erzeugt wird. - Wir haben das rückwärts-kompatibel gemacht, so gut wir das dieses Jahr konnten; nächstes Jahr aber soll - \cs{pdfoutput} so beschaffen sein, dass dieser Befehl auch dann definiert ist, wenn {\dvi}-Code erzeugt wird. - -\item pdf\TeX\ (\url{http://pdftex.org/}) hat viele neue Besonderheiten: - \begin{itemize} - \item Die Befehle \cs{pdfmapfile} und \cs{pdfmapline} ermöglichen einen Font"~Map-Support innerhalb eines - Dokuments. - \item Mikrotypografische Zeichensatz-Expansion (font expansion) kann jetzt viel leichter benutzt werden - \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html}. - \item Alle Parameter, die früher in der speziellen Konfigurationsdatei \filename{pdftex.cfg} definiert wurden, - müssen jetzt mit Hilfe von pdf\TeX-Grundbefehlen gesetzt werden, typischerweise in - \filename{pdftexconfig.tex}; die Konfigurationsdatei \filename{pdftex.cfg} wird nicht länger unterstützt. - Jede schon bestehende Format-Datei (\filename{.fmt}) muss neu erstellt werden, wenn - \filename{pdftexconfig.tex} geändert wird. - \item Für zusätzliche Informationen siehe das pdf\TeX-Handbuch: \OnCD{texmf-dist/doc/pdftex/manual}. - \end{itemize} - -\item Der Grundbefehl \cs{input} in \cmdname{tex} (\cmdname{mf} und \cmdname{mpost}) akzeptiert jetzt doppelte - Anführungszeichen und andere Spezialzeichen. Typische Beispiele: - -\begin{verbatim} -\input "filename with spaces" % plain -\input{"filename with spaces"} % latex -\end{verbatim} - - Für zusätzliche Informationen siehe das \Webc-Handbuch: \OnCD{texmf/doc/web2c}. - -\item enc\TeX\ wird jetzt in {\Webc} und damit auch in allen \TeX-Programmen unterstützt. Dazu wird \emph{beim - Generieren neuer Formate} die Option \optname{-enc} benutzt. enc\TeX\ unterstützt allgemein die Umkodierung der - Ein- und Ausgabe und ermöglicht eine volle Unicode-Unterstützung (in \acro{UTF}-8). - Siehe \OnCD{texmf-dist/doc/generic/enctex/} und \url{http://www.olsak.net/enctex.html}. - -\item Aleph (\ensuremath{\aleph}), eine neue ">Engine"<, die {\eTeX} und {\OMEGA} vereinigt, ist verfügbar. Ein bisschen - Information darüber finden Sie in \OnCD{texmf-dist/doc/aleph/base} und - \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph}. Das \LaTeX-basierte Aleph-Format heißt - \cmdname{lamed}. - -\item Das neueste \LaTeX-Release enthält eine neue Version der \acro{LPPL}% - \footnote{LPPL: LaTeX Project Public License}, - die jetzt eine offiziell von Debian anerkannte Lizenz ist. Zusammen mit anderen Updates finden Sie Informationen - dazu in den \filename{ltnews}-Dateien in \OnCD{texmf-dist/doc/latex/base}. - -\item \cmdname{dvipng} -- ein neues Programm zum Konvertieren von \dvi-Dateien in \acro{PNG}-Bilddateien, ist - Bestandteil von \TL. Siehe \OnCD{texmf/doc/man/man1/dvipng.1}. - -\item Auf Vorschlag des Autors (Claudio~Beccari) haben wir das Paket \pkgname{cbgreek} auf einen ">mittelgroßen"< Satz - von Fonts reduziert. Herausgenommen wurden die ">invisible"<, Outline- und ">Transparency"<-Fonts, - die relativ selten benutzt werden -- denn wir benötigen den Platz. In seinem vollen Umfang ist das Paket natürlich - weiterhin auf \acro{CTAN} verfügbar (\url{http://www.ctan.org/tex-archive/fonts/greek/cb/}). - -\item \cmdname{oxdvi} wurde entfernt; benutzen Sie jetzt \cmdname{xdvi}. - -\item Die \cmdname{ini}- und \cmdname{vir}-Befehle (Links) für \cmdname{tex}, \cmdname{mf} and \cmdname{mpost} sind - nicht mehr länger verfügbar, so auch \cmdname{initex}. Das ist kein richtiger Verlust, da die - \cmdname{ini}-Funktionalität schon seit mehreren Jahren über den Aufrufparameter \optname{-ini} zur Verfügung - steht. - -\item Die Unterstützung der Plattform \cmdname{i386-openbsd} wurde entfernt. Da das Paket \pkgname{tetex} im - \acro{BSD}-Ports-System zur Verfügung steht und Binaries für \acro{GNU}/""Linux and Free\acro{BSD} erhältlich sind, - erschien es sinnvoll, die Zeit der Freiwilligen besser zu nutzen. - -\item Zumindest auf \cmdname{sparc-solaris} müssen Sie ggf. die En"-viron"-ment-Variable \envname{LD\_LIBRARY\_PATH} - setzen, um die \pkgname{t1utils}-Programme laufen lassen zu können. Ursache dafür ist, dass die Programme mit C++ - kompiliert wurden und dass es keinen Standard-Platz für Laufzeit-Bibliotheken gibt (das ist zwar auch im Jahre - 2004 nicht neu, wurde aber bisher nicht dokumentiert.) Unter \cmdname{mips-irix} werden die - \acro{MIPS}pro-7.4-Laufzeit-Bibliotheken benötigt. -\end{itemize} - -\subsection{2005} - -Im Jahr 2005 gab es -- wie üblich -- viele aktualisierte Pakete und -Programme. Die Struktur des Systems blieb weitgehend gleich, mit folgenden -Ausnahmen: - -\begin{itemize} -\item Die neuen Skripte \cmdname{texconfig-sys}, \cmdname{updmap-sys} und - \cmdname{fmtutil-sys} für die systemweite Konfiguration des Systems wurden - hinzugefügt. Die Skripte \cmdname{texconfig}, \cmdname{updmap} und - \cmdname{fmtutil} modifizieren nun die Konfiguration für einen einzelnen - Nutzer unter \dirname{\$HOME/.texlive2005}. -\item Analog spezifizieren die Pfade \envname{TEXMFCONFIG} und - \envname{TEXMFSYSCONFIG} nun, wo die Konfigurationsdateien gefunden - werden (für einen einzelnen Nutzer bzw.\ systemweit). Möglicherweise - müssen Sie daher vorhandene eigene Versionen von - \filename{fmtutil.cnf} oder \filename{updmap.cfg} in die entsprechenden - Pfade verschieben. Alternativ können Sie \envname{TEXMFCONFIG} und - \envname{TEXMFSYSCONFIG} in der Datei \filename{texmf.cnf} umdefinieren, - dass diese auf die Speicherorte Ihrer eigenen Konfigurationsdateien - verweisen. Siehe Abschnitt~\ref{sec:texmftrees} auf Seite~\pageref{sec:texmftrees}. -\item Im letzten Jahr wurden für die Programme, die DVI als Ausgabeformat - erzeugen, die Primitive wie \verb|PDFoutput| auf undefiniert gesetzt, - obwohl immer \cmdname{pdfetex} verwendet wurde. In diesem Jahr wurde dies - wie angekündigt nicht mehr getan. Falls in Dokumenten nun die Abfrage - \verb|\ifxPDFoutput\undefined| zum Test benutzt wird, ob PDF oder DVI - erzeugt wird, müssen diese geändert werden! Benutzen Sie das Paket - \pkgname{ifpdf.sty}, das auch mit dem geänderten Verhalten funktioniert, - oder orientieren Sie sich an dessen Code. -\item Im letzten Jahr wurden die Formate so geändert, dass sie Zeichen - als 8-bit ausgeben. Die neue TCX-Datei \filename{empty.tcx} eröffnet nun - einen einfachen Weg, die originale Ausgabe mit \verb|^^|-Notation zu - erhalten, wenn Sie es wünschen: -\begin{verbatim} -latex --translate-file=empty.tcx yourfile.tex -\end{verbatim} -\item Das Programm \cmdname{dvipdfmx} für die Konvertierung von DVI nach - PDF ist neu hinzugekommen. Dies ist eine aktiv gepflegte Erweiterung von - \cmdname{dvipdfm}, das zwar noch verfügbar ist, aber als obsolet angesehen - werden kann. -\item Ebenso sind die Programme \cmdname{pdfopen} und \cmdname{pdfclose} neu - hinzugekommen. Diese erlauben ein Reload von PDF-Dateien im Acrobat Reader, - ohne diesen neu starten zu müssen (andere PDF-Viewer wie \cmdname{xpdf}, - \cmdname{gv} oder \cmdname{gsview} hatten damit nie Probleme). -\item Aus Konsistenzgründen wurden die Variablen \envname{HOMETEXMF} und - \envname{VARTEXMF} in \envname{TEXMFHOME} bzw.\ \envname{TEXMFSYSVAR} - umbenannt. Weiterhin existiert \envname{TEXMFVAR} für einen Baum, der - spezifisch für einen einzelnen Nutzer ist. -\end{itemize} - -\subsection{2006--2007} -\label{tlcurrent} - -Der wichtigeste Neuzuwachs in der Ausgabe 2006--2007 von \TL{} war das Xe\TeX{} -Programm, verfügbar durch die \texttt{xetex} und \texttt{xelatex} -Programme; siehe \url{http://scripts.sil.org/xetex}. - -Auch MetaPost erhielt ein bemerkenswertes Update, mit weiteren geplannten -Änderungen (\url{http://tug.org/metapost/articles}), ebenso pdf\TeX{} -(\url{http://tug.org/applications/pdftex}). - -Das (plain) \texttt{tex}-Programm liest nicht mehr erste Zeilen mit -\texttt{\%\&} um das Format zu bestimmen. Es ist ein reines Knuth-\TeX. -(\LaTeX\ und alle anderen Formate lesen weiterhin \texttt{\%\&}-Zeilen). - -Weiters wurden wie üblich hunderte von Paketen und Programmen auf einen -neueren Stand gebracht. Für weiter Updates wenden Sie sich bitte an -\acro{CTAN} (\url{http://www.ctan.org}). - -Die Entwicklungsumgebung wurde auf Subversion umgestellt, was ein Webinterface -für den Entwicklungsbaum beisteuerte. Dieses Webinterface ist von der -Homepage verlinkt. Obwohl dieser Umstieg in der Distribution nicht zu -erkennen ist, erwarten wir uns ein stabiles Fundament für die Entwicklung -in den nächsten Jahren. - -Schließlich hat im Mai~2006 Thomas Esser das Ende seiner Entwicklung von -te\TeX{} (\url{http://tug.org/tetex}) angekündigt. Als Konsequenz ist das -Interesse an \TL{}, besonders unter den \acro{GNU}/Linux-Distributoren -angestiegen. (\TL{} bietet nun ein \texttt{tetex}-Installationsschema, dass -annähernd den Umfang von te\TeX{} umfasst.) Wir hoffen dass dies -schlussendlich zu einer Verbesserung der \TeX-Umgebung für jederman führt. - -\medskip\noindent -Abschließende Bemerkung zur Vergangenheit: Alle Versionen von \TL, -inklusive Beimaterial wie CD-Labels, finden sich unter -\url{ftp://tug.org/historic/systems/texlive}. - -\subsection{Gegenwart} -\label{sec:tlcurrent} - -Die komplette Infrastruktur von \TL wurde 2008 neu entwickelt. Die -gesamten Daten, die für die Installation benötigt werden, finden sich -nun in einer einzigen Textdatei mit dem Namen \filename{tlpkg/texlive.tlpdb}. - -Dies ermöglicht es unter anderem, ein Update einer installierten Version -von \TL über das Internet durchzuführen, was für MiK\TeX{} schon seit -Jahren möglich ist. Wir planen regelmäßige Updates bereitzustellen, -wenn Pakete auf \CTAN{} aktualisiert werden oder neu erscheinen. - -Als neues Programm ist Lua\TeX\ (\url{http://luatex.org}) enthalten, -das neben neuen Möglichkeiten innerhalb des Satzsystems eine -hervorragende Skriptsprache zur Verfügung stellt, die inner- und -außerhalb von \TeX{} benutzt werden kann. - -Die Unterstützung von \TL für Windows und Unix ist mittlerweile praktisch -äquivalent. Die meisten Perl- und Lua-Skripte können nun auch unter -Windows verwendet werden, da innerhalb von \TL Perl integriert ist. - -Das neue \cmdname{tlmgr}-Programm (Abschnitt~\ref{sec:tlmgr}) ist -eine komplette Oberfläche zum Verwalten von \TL nach der Installation. -Es ermöglicht das Aktualisieren von Paketen, die Neugenerierung von -Formatdateien, Fontmaps und die Konfiguration der \TeX-Unterstützung -für verschiedene Sprachen. - -Nach der Einführung von \cmdname{tlmgr} sind die Funktionen von -\cmdname{texconfig} zur Konfiguration von Formatdateien und -Trennmustern deaktiviert worden. - -Der Index-Prozessor \cmdname{xindy} (\url{http://xindy.sourceforge.net/}) -ist nun für die meisten Betriebssysteme integriert. - -Das Programm \cmdname{kpsewhich} kann nun alle Fundstellen für eine -gesuchte Datei anzeigen (Option \optname{--all}) oder die Suche -auf ein bestimmtes Verzeichnis einschränken (Option \optname{--subdir}). - -Das Programm \cmdname{dvipdfmx} kann nun Informationen über die -Bounding Box liefern, was über die Kommandozeile mit dem Befehl -\cmdname{extractbb} aufgerufen werden kann; dies war die letzte -Funktion von \cmdname{dvipdfm}, die noch nicht in \cmdname{dvipdfmx} -vorhanden war. - -Die Font-Aliasnamen \filename{Times-Roman}, \filename{Helvetica} usw. -wurden abgeschafft. - -Das Makro-Format \pkgname{platex} wurde entfernt, um den Namenskonflikt -mit dem japanischen \pkgname{platex} auf zu lösen; Unterstützung -für polnisch wird nun vom Paket \pkgname{polski} zur Verfügung gestellt. - -Die \web{} string pool files wurden in die Programme einkompiliert, -um Updates zu vereinfachen. - -Und abschließend sind die Änderungen von Donald Knuth in seinem -\emph{\TeX\ tuneup of 2008} in \TL eingearbeitet, -\url{http://tug.org/TUGboat/Articles/tb29-2/tb92knut.pdf}. -% ------------------------------------------------------------- -\subsection{Zukunft} - -\emph{{\TL} ist nicht perfekt! -- und wird es auch nie sein.} Wir planen -Neuauf"|lagen zu produzieren, die umfangreichere -Hilfstexte, mehr Hilfsprogramme, mehr Installationshilfen und (natürlich) -den ständig verbesserten und überprüften Satz der Makros und Zeichensätze -enthalten. Diese Arbeit wird von Freiwilligen in ihrer knappen Freizeit -geleistet. Viel Arbeit steht noch an. Wenn Sie uns helfen können, -zögern Sie keine Sekunde, sich bei uns zu melden. - -Verbesserungen, Anregungen und Erweiterungen für künftige Ausgaben -der {\TK} senden Sie bitte an:\hfill\null - -\begin{quote} -\email{tex-live@tug.org}\\ -\url{http://tug.org/texlive/} -\end{quote} - -Neue Versionen, Anmerkungen und zusätzliches Material werden über -die \CTAN-Server im Verzeichnis \dirname{info/texlive} zur Verfügung gestellt. -Im \acro{WWW} können Sie sich über die Adresse -\url{http://www.tug.org/tex-live/} informieren und die Bestellformalitäten -einsehen. - -\end{document} diff --git a/Master/texmf-doc/source/texlive/texlive-en/Makefile b/Master/texmf-doc/source/texlive/texlive-en/Makefile deleted file mode 100644 index 170161df9c3..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/Makefile +++ /dev/null @@ -1,69 +0,0 @@ -# $Id$ -# Makefile for TeX Live documentation. Public domain. -doc = texlive-en -lang = english - -all: pdf html - -env = TEXINPUTS=../texlive-common:../texlive-en:; export TEXINPUTS; - -pdf: - rm -f *.aux *.toc *.lof *.lot *.xref* *.tmp *.out - $(env) pdflatex '\nonstopmode\def\Status{1}\input $(doc)' - $(env) pdflatex '\nonstopmode\def\Status{1}\input $(doc)' - $(env) pdflatex '\nonstopmode\def\Status{1}\input $(doc)' - $(env) pdflatex '\nonstopmode\def\Status{1}\input $(doc)' - -html: - rm -f *.aux *.toc *.lof *.lot *.xref* *.tmp *.out *.4tc -# this sequence is equivalent to running "ht latex $(doc)". We do it -# this way so we can \def\Status for the \ifcase in tex-live.sty. - $(env) latex '\nonstopmode\def\Status{2}\input $(doc)' - $(env) latex '\nonstopmode\def\Status{2}\input $(doc)' - $(env) latex '\nonstopmode\def\Status{2}\input $(doc)' - $(env) latex '\nonstopmode\def\Status{2}\input $(doc)' - $(env) tex4ht $(doc) - $(env) t4ht $(doc) - -clean: - rm -f *.aux *.log *.blg *.toc *.out *.lot tex4ht.ps *.4* - rm -f *.xref* *.lg *.idv *.out *.otc *.tmp tmp.* - rm -f $(doc).dvi $(doc).ps - -realclean: clean - rm -f $(doc).pdf - rm -f *.html *.htm $(doc).css *.gif *.jpg - - -insttop = ../../../doc -instfiles = $(doc)*html $(doc).css $(doc).pdf -install: -# lang=`dirname \`pwd\` | sed 's,.*/,,'`; - lang=$(lang); \ - tldir=`pwd | sed 's,.*/,,'`; \ - instdir=$(insttop)/$$lang/$$tldir; \ - echo tldoc install to $$instdir; \ - for f in $(instfiles); do \ - cmp -s $$f $$instdir/$$f && rm -v $$f && continue; \ - mv -v $$f $$instdir/$$f; \ - done - - -# don't use these, they don't work. -dvi: - rm -f *.aux *.toc - latex '\nonstopmode\def\Status{0}\input $(doc)' - latex '\nonstopmode\def\Status{0}\input $(doc)' - latex '\nonstopmode\def\Status{0}\input $(doc)' - -baskerville: - rm -f *.aux *.toc - latex '\def\Status{3}\input $(doc)' - latex '\def\Status{3}\input $(doc)' - latex '\def\Status{3}\input $(doc)' - -tugboat: - rm -f *.aux *.toc - latex '\def\Status{4}\input $(doc)' - latex '\def\Status{4}\input $(doc)' - latex '\def\Status{4}\input $(doc)' diff --git a/Master/texmf-doc/source/texlive/texlive-en/README b/Master/texmf-doc/source/texlive/texlive-en/README deleted file mode 100644 index dc5fb6b124d..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/README +++ /dev/null @@ -1,5 +0,0 @@ -$Id$ -TeX Live documentation. This file is public domain. - -We only generate the documentation in PDF and HTML formats -- see the -Makefile. This saves us having to have the images in EPS format too. diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/bv-live.tex b/Master/texmf-doc/source/texlive/texlive-en/archive/bv-live.tex deleted file mode 100644 index ad044e568cb..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/bv-live.tex +++ /dev/null @@ -1,84 +0,0 @@ -% this is the baskerville version of the live documentation -\providecommand{\Status}{3} - -\setcounter{errorcontextlines}{999} -\documentclass{article} -\advance\textwidth by 1in -\advance\oddsidemargin by -1in -\advance\evensidemargin by -1in -\newsavebox{\warnbox} -\def\Q#1{\par\vskip6pt\leftline{#1}\par} -\setcounter{tocdepth}{2} -\pretolerance=1000 -\tolerance=1500 -\hbadness=3000 -\vbadness=3000 -\hyphenpenalty=400 -\renewcommand{\topfraction}{0.85} -\renewcommand{\floatpagefraction}{0.86} -\renewcommand{\textfraction}{0.1} -\setcounter{topnumber}{5} -\setcounter{totalnumber}{5} -\def\eTeX{$\varepsilon$-\TeX} -%\def\CTAN{\textsc{ctan}} -%\def\TUB{\textsc{tub}} -\def\Dash{---} -\def\hyph{-} -%\def\TeXXeT{\TeX-XeT} -\def\OMEGA{$\Omega$} -\def\bs{{\protect\normalfont\ttfamily\char'134}} -\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} -%\def\cs#1{\mbox{\normalfont\ttfamily\bs#1}} -\def\La{La} -\let\textsl\textit -\let\sl\it -\let\slfamily\itfamily -\def\ttdefault{cmtt} -\usepackage{tex-live} -\begin{document} -%\author{Sebastian Rahtz\\ -%\texttt{s.rahtz@elsevier.co.uk}\\ -%Michel Goossens\\ -%\texttt{m.goossens@cern.ch}} -%\title{The \protect\TeX\ Live Guide, 3rd edition} -%\date{March 1998} - -\BASKyear{1998} -\BASKmonth{April} -\BASKvol{8} -\BASKno{2} -\BASKed*{Robin Fairbairns} -\BASKfonts{Y\&Y European Modern} -\makeBSKtitle - -\input editorial -\ifbaskerville -\end{multicols} -%\vfill\Dings\vfill -\fi -\clearpage - -\begin{center} - \LARGE The \TeX\ Live Guide, 3rd edition -\end{center} -\title{\TeX\ Live Guide, 3rd edition} - -\ifbaskerville\begin{multicols}{2}\fi -\tableofcontents -\listoftables -\ifbaskerville -\end{multicols} -\Dings -\fi - -\input tex-live -\appendix - -\Dings - -\input live-app - -\vfill\Dings\vfill -\clearpage -\input sec -\end{document} diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/bvoutln.sty b/Master/texmf-doc/source/texlive/texlive-en/archive/bvoutln.sty deleted file mode 100644 index 92f19fd027b..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/bvoutln.sty +++ /dev/null @@ -1,193 +0,0 @@ -% extracts of baskerville.cls for use with the tex-live documentation -% when we're producing a bv issue with it. - -% **************************************** -% * PAGE LAYOUT * -% **************************************** -% -% SIDE MARGINS: -\oddsidemargin -2.5pc \evensidemargin -2.5pc -\marginparwidth 4pc % don't use marginal notes... -\marginparsep 0.5pc % ...in the UK TUG newsletter - -% VERTICAL SPACING: -\topmargin -3pc -\headheight 12\p@ -\headsep 15\p@ -\topskip 10\p@ -\footskip 15\p@ - -% DIMENSION OF TEXT: - -\textheight 250mm % height of text on a page (A4 paper) -\textwidth 180mm % total width of a page -\columnseprule 0.5\p@ % width of line in the inter-column gutter -\columnsep 10mm % space between columns -\tolerance 9999 % make those columns justify - -% FOOTNOTES: -\footnotesep 6\p@ -\skip\footins 19.5\p@ plus 12\p@ \@minus 1\p@ - -% FLOATS: -\floatsep 12\p@ plus 5.5\p@ \@minus 1\p@ -\textfloatsep 15\p@ plus 4.5\p@ \@minus 3\p@ -\intextsep 12\p@ plus 5.5\p@ \@minus 2\p@ -\dblfloatsep 12\p@ plus 5.5\p@ \@minus 2\p@ -\dbltextfloatsep 15\p@ plus 4.5\p@ \@minus 3\p@ -\@fptop 0\p@ plus 0fil -\@fpsep 12\p@ plus 0fil -\@fpbot 0\p@ plus 3fil -\@dblfptop 0\p@ plus 0fil -\@dblfpsep 12\p@ plus 0fil -\@dblfpbot 0\p@ plus 3fil -\marginparpush 5\p@ - -% **************************************** -% * TITLES AND ABSTRACT * -% **************************************** -% - -%% Volume Number (ie Year - 1990) -\def\BASKvol#1{\gdef\BASK@vol{#1}} -\BASKvol{?} - -%% Issue Number (ie Month/2, roughly) -\def\BASKno#1{\gdef\BASK@no{#1}} -\BASKno{?} - -% Editor, Star form for Guest editor -\def\BASKed{\@ifstar{\BASK@ed{Guest }}{\BASK@ed{}}} -\def\BASK@ed#1#2{\gdef\BASK@editor{#1Editor: #2}} -\BASKed{????????} - -%% Year (4 digits) -\def\BASKyear#1{\gdef\thisyear{#1}} -\BASKyear{????} - -% Month (as a Word) -\def\BASKmonth#1{\gdef\thismonth{#1}} -\BASKmonth{?????} - -\def\makeBSKtitle{\par - \begingroup - \vspace*{-\headheight}% - \@maketitle - \bigskip\hrule\bigskip - \thispagestyle{plain} - \endgroup - \let\maketitle\relax - \let\@maketitle\relax -} -\newbox\BSKbox -\def\@maketitle{% - \centerline{\BASK@titleline}% - \medskip - \hbox to \textwidth{\bfseries The Annals of the UK \TeX\ Users - Group\hfill \BASK@editor\hfill Vol.~\BASK@vol\ No.~\BASK@no}% - \smallskip\hbox to \textwidth{\bfseries ISSN 1354--5930 - \hfill \thismonth\ \thisyear}% - \medskip - \noindent\ignorespaces - \BASK@headparone} - -% The Journal title command. -% You probably only want to change this if you want to use a design-size -% font rather than let \scaletowidth scale for some special issue. -\def\BASKtitle#1{\gdef\BASK@titleline{#1}} -\let\scaletowidth=\resizebox% added by Sean K. Harbour for Textures -\BASKtitle{% - \fontfamily{mbvx}\bfseries - \scaletowidth{\textwidth}{!}{% modified by Sean K. Harbour - B\,a\,s\,k\,e\,r\,v\,i\,l\,l\,e}} - - -% The first paragraph. Needs to be reset if a special issue used a -% different font set. -\def\BASKheadparone#1{\gdef\BASK@headparone{#1}} -\BASKheadparone{% -This issue of \BV\ is set in \@BASKfonts, and printed on a Xerox Docutech. Production and distribution is -undertaken in Cambridge by Robin Fairbairns. } - - -\def\BASKfonts#1{\gdef\@BASKfonts{#1}} -\BASKfonts{Monotype Baskerville, with Computer Modern Typewriter for - literal text} - -% -% for \Dings -\RequirePackage{pifont} -% -% available for inter-article dinglines -% -\def\Dings{\nopagebreak{\footnotesize\dingline{167}}} - -% -% hack representation of appendices -\let\BV@@appendix\appendix -\renewcommand{\appendix}{\BV@@appendix - \renewcommand\@seccntformat[1]{\@ifundefined{@seccnt@##1}% - {\csname the##1\endcsname\quad}% - {\csname @seccnt@##1\endcsname}} - \newcommand\@seccnt@section{Appendix~\thesection~} -} - -% -% page styles -% -% \ps@empty defined in LATEX.TEX -% -\def\ps@plain{\let\@mkboth\markboth - \def\@oddhead{} - \def\@evenhead{} - \def\@oddfoot{\rm \hfil --\thepage--\hfil} - \def\@evenfoot{\rm \hfil --\thepage--\hfil} -} -\def\ps@headings{\let\@mkboth\markboth - \def\@oddhead{\hfill\emph{\@title}\hfill} - \def\@oddfoot{\rm \hfil --\thepage--\hfil} - \def\@evenhead{\it Baskerville \hfill - Volume \BASK@vol, Number \BASK@no} - \def\@evenfoot{\rm \hfil --\thepage--\hfil} -} - -% -% allow setting of pagehead title -\def\title{\@ifnextchar [{\@titletwo}{\@titleone}} -\def\@titletwo[#1]#2{\gdef\@title{#1}\gdef\@longtitle{#2}} -\def\@titleone#1{\gdef\@title{#1}\gdef\@longtitle{#1}} - -% -% more exciting page parameters -\@twosidetrue -\pagestyle{headings} - -\providecommand{\ukt}{UK \acro{TUG}} - -\newcommand{\standardtitles}{% - \def\section{%\typeout{** section!}% - \@startsection {section}{1}{\z@} - {-12\p@ \@plus -6\p@ \@minus -.1\p@} - {6\p@} - {\raggedright\large\bfseries}} - \def\subsection{\@startsection{subsection}{2}{\z@} - {-4\p@ \@plus -2\p@ \@minus -.1\p@} - {0.1\p@ \@plus 2\p@} - {\raggedright\normalsize\itshape}} - \def\subsubsection{\@startsection{subsubsection}{3}{\z@} - {-6\p@ \@plus -3\p@ \@minus -1\p@} - {0.1\p@ \@plus 2\p@} - {\raggedright\normalsize\it}} - \def\paragraph{\@startsection{paragraph}{4}{\z@} - {12\p@ \@plus 2.25\p@ \@minus -1\p@} - {-0.5em} - {\normalsize\bfseries}} - \def\subparagraph{\@startsection{subparagraph}{5}{\z@} - {12\p@ \@plus 2.25\p@ \@minus 1\p@} - {-0.5em} - {\normalsize\it}} - \setcounter{secnumdepth}{-1} -} - -\endinput - diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/changemail b/Master/texmf-doc/source/texlive/texlive-en/archive/changemail deleted file mode 100644 index dd792a25f78..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/changemail +++ /dev/null @@ -1,24 +0,0 @@ -s/J.Smart@ed.ac.uk/??/ -s/gerd@uni-koblenz.de/??/ -s/Meijer@rulfsw.fsw.LeidenUniv.nl/??/ -s/wl@gnu.org/xlwy01@uxp1.hrz.uni-dortmund.de/ -s/weissert@SJUPHIL.SJU.EDU/Tom@Weissert.net/ -s/mehlich@informatik.uni-muenchen.de/mmehlich@semdesigns.com/ -s/eijkhout@math.ucla.edu/victor@eijkhout.net/ -s/ca_rowley@vax.acs.open.ac.uk/c.a.rowley@open.ac.uk/ -s/B.Jackowski@gust.s.org.pl/B.Jackowski@gust.org.pl/ -s/P.Pianowski@gusts.org.pl/P.Pianowski@gust.org.pl/ -s/mittelbach@mzdmza.zdv.uni-mainz.de/Frank.Mittelbach@Uni-Mainz.de/ -s/mcjones@pa.dec.com/paul.mcjones@acm.org/ -s/h.harders@tu-bs.de/Harald.Harders@dlr.de/ -s/pwilson@cme.nist.gov/peter.r.wilson@boeing.com/ -s/wikner@ariel.nac.ac.za/wikner@nac.ac.za/ -s/vitus@agropc.msk.su/vitus@ice.ru/ -s/greg@bic.mni.mcgill.ca/gward@python.net/ -s/mittelbach@mzdmza.zdv.uni-mainz.de/frank.mittelbach@latex-project.org/ -s/fbraun@rz.uni-potsdam.de/fbraun@atdot.org/ -s/david@dcarlisle.demon.co.uk/david.carlisle@latex-project.org/ -s/davidc@nag.co.uk/david.carlisle@latex-project.org/ -s/rf@cl.cam.ac.uk/rf10@cam.ac.uk/ -s/robin.fairbairns@cl.cam.ac.uk/rf10@cam.ac.uk/ -s/robin@lsl.co.uk/rf10@cam.ac.uk/ \ No newline at end of file diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/l.pl b/Master/texmf-doc/source/texlive/texlive-en/archive/l.pl deleted file mode 100644 index d74f313a5cc..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/l.pl +++ /dev/null @@ -1,44 +0,0 @@ -require "status.pl"; -require "texlive.pl"; -while (<>) { - chop; - s/,$//; - if (/^\@TeXIndex/) - { - ($nam) = /^\@TeXIndex.(.*)/; - print "\@TeXIndex\{$nam"; - $Status=1; - $Texlive=1; - $Modified=0; - } - elsif (/^ *modified/) { s/, *$//; $mod=$_; } - elsif (/^ *status/) { $Status=0; - if ($L{$nam}) - { print ",\n status\t= \{$L{$nam}\}"; - $Modified=1;} - else { print ",\n$_"; } - } - elsif (/^ *texlive/) { $Texlive=0; - if ($texlive{$nam} ne "") - { print ",\n texlive\t= \{$texlive{$nam}\}"; - $Modified=1;} - } - elsif (/^}/) { - if ($Status) { - print ",\n status\t= \{unknown\}"; - } - if ($Texlive && $texlive{$nam} ne "") - { print ",\n texlive\t= \{$texlive{$nam}\},\n"; } - if ($Modified) - { print ",\n modified\t= {1999/03/26 10:00:00 }\n"; } - elsif ($M{$nam} ne "") - { print ",\n modified\t= \{$M{$nam}\}\n"; } - else - {print ",\n$mod\n"; } - print "}\n"; - } - - elsif (/= {/) { print ",\n$_"; } - else { print "\n$_"; } - } - diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/live-2003.tex b/Master/texmf-doc/source/texlive/texlive-en/archive/live-2003.tex deleted file mode 100644 index 55c1551a628..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/live-2003.tex +++ /dev/null @@ -1,3937 +0,0 @@ -% $Id$ -% change history (started May 13th 2002) -% 2003/09/06: fixes from Staszek -% 2003/09/05: touched by Karl -% 2003/09/04: fixes from Staszek and Fabrice -% 2003/09/01: fixes from Volker -% 2003/08/24: win32 updates, by Fabrice -% 2003/08/12: fixes from Christer Gustafsson . -% 2003/07/07: substantial revisions by karl. -% 2002/05/25: remove mention of sizes, and bsr-interpolated; add Gutenberg -% 2002/05/18: win32 updates, by Fabrice -% 2002/05/14: corrected example files, other small errors noted by Volker -% 2002/05/13: added tex-langafrican to list of collections -% -\documentclass{article} -\usepackage{tex-live} -% -% -\begin{document} - -\title{{\huge\textsf{\TK{} 2003}}\\[3mm] - The \protect\TeXLive{} Guide} -\date{September 2003} - -\author{Sebastian Rahtz, editor \\[3mm] - \email{tex-live@tug.org}\\ - \url{http://tug.org/texlive/}\\[10mm] -\ifnum \Status=2 - \includegraphics[bb=0 0 824 741]{../pictures/front.jpg} \\[5mm] -\else - \includegraphics[width=.5\linewidth]{../pictures/front} \\[5mm] -\fi - \small \textit{Documentation contacts:}\\[3mm] - \small \begin{tabular}{lcr} - Czech/Slovak & Petr Sojka & \email{sojka@fi.muni.cz} \\ - & Janka Chleb\'\i kov\'a & \email{chlebikj (at) dcs.fmph.uniba.sk} \\ - English & Karl Berry & \email{karl@freefriends.org} \\ - French & Fabrice Popineau & \email{fabrice.popineau@supelec.fr} \\ - German & Volker RW Schaa & \email{volker@dante.de} \\ - Polish & Staszek Wawrykiewicz & \email{staw@gust.org.pl} \\ - Russian & Boris Veytsman & \email{borisv@lk.net} \\ - \end{tabular} - } - -% comes out too close to the toc, and we know it's page one anyway. -\thispagestyle{empty} - -\maketitle -\newpage - -\begin{multicols}{2} -\tableofcontents -\listoftables -\end{multicols} - -\section{Introduction} -\label{sec:intro} - -This document describes the main features of the \TeXLive{} software -distribution\Dash a \TeX{} and \LaTeX{} distribution for Linux and other -Unix flavors, \MacOSX, and (32-bit) Windows systems. (Warning: it is -not especially useful for older Mac or \acro{MS-DOS} systems.) It -includes precompiled binaries for \TeX{}, \LaTeXe{}, \MF, \MP, -\BibTeX{} and many other programs; an extensive collection of -macros, fonts and documentation; and support for typesetting in many -different scripts from around the~world. - -For the 2003 release, the last update of packages and programs was made -on September 3, 2003. For newer versions, please consult \acro{CTAN}, -\url{http://www.ctan.org}. - -For a brief summary of the major changes in this edition of \TeXLive{}, -see section~\ref{sec:history} on p.~\pageref{sec:history}. - - -\subsection{Basic usage of \protect\TeXLive{}} -\label{sec:basic} - -You can use \TeXLive{} in three principal ways: - -\begin{enumerate} - -\item You can run \TeXLive{} directly from the distribution media -(except for the \pkgname{inst} distribution; see -section~\ref{sec:multiple-dist} on p.~\pageref{sec:multiple-dist}). -This takes almost no disk space, as you might expect, and gives you -immediate access to everything in \TeXLive{}. Of course performance -will be worse than running on local disk, but you may well find it -acceptable. - -\item You can install all or part of \TeXLive{} to a local disk. This -is the most common use of \TeXLive. You will need a minimum of 120 -megabytes, 360 megabytes for a recommended system, and 800 megabytes for -a full system. - -\item You can integrate a particular package or collection into your -existing \TeX{} system, either a \TeXLive{} system you installed earlier -or a different system. - -\end{enumerate} - -\noindent All of these are described in detail in the \acro{OS}-specific -installation sections. - - -\subsection{Getting help} -\label{sec:help} - -The \TeX{} community is both active and friendly, and virtually all -serious questions end up getting answered. However, the support is -informal, done by volunteers and casual readers, so it's especially -important that you do your homework before asking. (If you prefer -commercial-style support, you can forego \TeXLive{} completely and -purchase a vendor's system; see -\url{http://tug.org/interest.html#vendors} for a list.) - -Here is a list of resources, approximately in the order we recommend -using them: - -\begin{description} -\item [\TeX{} \acro{FAQ}] The \TeX{} \acro{FAQ} is a huge compendium of -answers to all sorts of questions, from the most basic to the most -arcane. It is included on \TeXLive{} in \OnCD{FAQ/english}, and is -available on the Internet through \url{http://faq.tug.org}. Please -check here first. - -\item [\TeX{} Catalogue] If you are specifically looking for a package, -font, program, etc., the \TeX{} Catalogue is the place to look. It is a -huge list of all \TeX{}-related items. See -\OnCD{texmf/doc/html/catalogue}, or -\url{http://www.ctan.org/tex-archive/help/Catalogue/catalogue.html}. - -\item [\TeX{} Web Resources] This web page has many \TeX{}-related -links, in particular for numerous books, manuals, and articles on all -aspects of the system: \url{http://tug.org/interest.html}. - -\item [support archives] The two principal forums for support are the -Usenet newsgroup \url{news:comp.text.tex} and the mailing list -\email{texhax@tug.org}. So, their archives have thousands of past -questions and answers for your searching pleasure. See -\url{http://groups.google.com/groups?group=comp.text.tex} and -\url{http://tug.org/mail-archives/texhax}, respectively. A query on a -general web search engine, such as \url{http://google.com}, never hurts. - -\item [posting questions] If you cannot find an answer, you can post to -\dirname{comp.text.tex} through Google or your newsreader, or through -email to \email{texhax@tug.org}. But before you post, \emph{please} -read this \acro{FAQ} entry for advice on asking questions in such a way -that you're most likely to get an answer: -\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. - -\item [\TeXLive{} support] If you want to report a bug or have -suggestions or comments on the \TeXLive{} distribution, installation, or -documentation, the mailing list is \email{tex-live@tug.org}. However, -if your question is about how to use a particular program included in -\TeXLive{}, you are better off writing to that program's maintainer or -mailing list. - -\end{description} - -The other side of the coin is helping others who have questions. Both -\dirname{comp.text.tex} and \code{texhax} are open to anyone, so feel -free to join, start reading, and help out where you can. Welcome to -\TeX{}! - - -\section{Structure of \protect\TeXLive} -\label{sec:struct-tl} - -The main two installation scripts for Unix and \MacOSX{} are -\texttt{install-tl.sh} and \texttt{install-pkg.sh}. We discuss them -in section \ref{sec:unix-install} on p.~\pageref{sec:unix-install}. -Here, we describe the structure and contents of \TeXLive{}. - - -\subsection{Multiple distributions: \protect\pkgname{live}, - \protect\pkgname{inst}, \protect\pkgname{demo}} -\label{sec:multiple-dist} - -As of 2003, space limitations of \acro{CD-ROM} format have forced us to -divide \TeXLive{} into three distributions, as follows. - -\begin{description} - -\item [live] a complete, runnable system on \acro{DVD}; it is too large -for \acro{CD-ROM}. (The \DVD{} also includes a snapshot of the \CTAN{} -repository, completely independent of \TeXLive{}.) - -\item [inst(allable)] a complete system on \CD; in order to make it fit, -we had to compress everything we could. Therefore, it is not possible -to run \TeX\ directly from the installable \CD, you have to install it to -disk (hence its name). Installation is described in subsequent sections. - -\item [demo] a live system runnable directly from \CD; in order to make -this fit, we omitted the very large collection of \acro{CJK} (Chinese, -Japanese, Korean) language support, support for typesetting music, some -less-commonly used fonts, and included executables only for Linux, -\MacOSX, and Windows systems. - -\end{description} - -\noindent You can tell which type of distribution you're in by looking -for a \texttt{00\var{type}.TL} file in this top-level directory. - - -\subsection{Top level directories} - -Here is a brief listing and description of the top level directories in -the \TeXLive{} distribution. - -\smallskip -\begin{tabular}{>{\ttfamily}lp{.8\hsize}} -bin & The \TeX{} system programs, arranged by platform. \\ -Books & Examples from some of the books about \TeX\ (see - \filename{Books/README}). \\ -FAQ & Current versions of major FAQ collections. \\ -info & A few manuals in \acro{GNU} Info format, where available. \\ -\MacOSX & Supporting software for \MacOSX (see - section~\ref{sec:mac-install} on p.~\pageref{sec:mac-install}). \\ -man & Unix man pages. \\ -source & The source of all programs, including the main \Webc{} - \TeX{} and \MF{} distributions. These are stored in a - \cmdname{bzip2}-compressed tar archive. \\ -support & assorted auxiliary packages and programs. These are - \emph{not} installed by default. This includes - \cmdname{Ghostscript}, \cmdname{netpbm}, and assorted editors and - \TeX\ shells. \\ -texmf & root of installed packages, fonts, config files, etc. \\ -usergrps & Material about a few of the \TeX\ user groups. (Visit - \url{http://tug.org/usergroups.html} for a current list.) \\ -xemtex & The \cmdname{XEmacs} editor and other support programs for - Windows (see section~\ref{sec:win-xemtex} on p.~\pageref{sec:win-xemtex}). - These programs generally come pre-installed on Unix systems, or are - at least easy to compile. \\ -\end{tabular} - - -\subsection{Extensions to \TeX} -\label{sec:tex-extensions} - -\TeXLive{} contains three extended versions of \TeX: - -\begin{description} - -\item [\eTeX] adds a small but powerful set of new primitives -\label{text:etex} -(related to macro expansion, character scanning, classes of marks, -additional debugging features, and more) and the \TeXXeT{} extensions -for bidirectional typesetting. In default mode, \eTeX{} is 100\% -compatible with ordinary \TeX. See -\OnCD{texmf/doc/etex/base/etex_man.pdf}. \eTeX{} is now the default for -\LaTeX{} and pdf\LaTeX{}. - -\item [pdf\TeX] writes Acrobat PDF format as well as \dvi{}. The -\LaTeX{} \pkgname{hyperref} package has an option `\optname{pdftex}' -which turns on all the program features. See -\OnCD{texmf/doc/pdftex/pdftex-l.pdf} and -\OnCD{texmf/doc/pdftex/base/example.tex}. - -\item [\OMEGA\ (Omega)] based on Unicode (16-bit characters), thus -supports working with almost all the world's scripts simultaneously. It -also supports so-called `\OMEGA{} Translation Processes' (\acro{OTP}s), -for performing complex transformations on arbitrary input. See -\OnCD{texmf/doc/omega/base/doc-1.8.tex} (not completely up-to-date). - -\end{description} - - -\subsection{Other notable programs in \protect\TeXLive} - -Here are a few other commonly-used programs included in \TeXLive{}: - -\begin{cmddescription} - -\item [bibtex] bibliography support. - -\item [makeindex] index support. - -\item [dvips] convert \dvi{} to \PS{}. - -\item [xdvi] \dvi{} previewer for the X Window System. - -\item [dvilj] HP LaserJet driver. - -\item [dv2dt, dt2dv] convert \dvi{} to/from plain text. - -\item [dviconcat, dviselect] cut and paste pages -from \dvi{} files. - -\item [dvipdfm] convert \dvi{} to PDF, an alternative approach -to pdf\TeX\ (mentioned above). See the \pkgname{ps4pdf} and -\pkgname{pdftricks} packages for still more alternatives. - -\item [psselect, psnup, \ldots] \PS{} -utilities. - -\item [lacheck] \LaTeX{} syntax checker. - -\item [texexec] Con\TeX{}t and PDF processor. - -\item [tex4ht] \TeX{} to HTML converter. - -\end{cmddescription} - - -\section{Unix installation} -\label{sec:unix-install} - -As introduced in section~\ref{sec:basic} on p.~\pageref{sec:basic}, -\TeXLive{} has three principal uses: - -\begin{enumerate} -\item Run directly from media. -\item Install to disk. -\item Integrate a particular package or collection into your existing -\TeX{} installation. -\end{enumerate} - -\noindent The following sections describes the Unix-specific procedures -for each of these. - -\ifSingleColumn \begin{figure}[ht]\noindent \fi -\begin{warningbox} -\textbf{Warning: } The \TK{} \CD{}s and \DVD{} are in ISO 9660 (High Sierra) -format, \emph{with} Rock Ridge (and Joliet, for Windows) -extensions. Therefore, in order to take full advantage of the \TK{} -under Unix, your system needs to be able to use the Rock Ridge -extensions. Please consult the documentation for your \cmdname{mount} -command to see how to do this. If you have several different machines -on a local network, you may be able to mount the \CD{}s on one which -does support Rock Ridge, and use this with the others. - -\leavevmode\quad Linux, Free\acro{BSD}, Sun, \acro{SGI} and -Alpha systems should be able to use the \CD{}s without problems. We -would appreciate receiving detailed advice from users on other systems -who succeed, for future versions of this documentation. - -\leavevmode\quad -The discussion below assumes you have been able to mount -the \CD{}s with full Rock Ridge compatibility. -\end{warningbox} -\ifSingleColumn\end{figure}\fi - - -% -\subsection{Running \protect\TeXLive{} directly from media (Unix)} - -\def\runlive{% text repeated in windows section -It is possible to use the \TeX{} system directly from the \pkgname{demo} -\CD{} or the \pkgname{live} \DVD{}, without installing the distribution -to disk. (Thus the name `\TeXLive', in fact.) It is \emph{not} -possible to run \TeX{} directly from the \pkgname{inst} \CD (see -section~\ref{sec:multiple-dist} on p.~\pageref{sec:multiple-dist}). -} - -Only Linux, \MacOSX, and Windows binaries are included on the demo \CD; -if you want to run live on other Unix systems, you'll need to use the -\DVD. - -\def\startinst{% repeated in other subsections -To start, we must mount the \CD{} or \DVD{}, with Rock Ridge extensions -enabled. The exact command to do this varies from system to system; the -following works under Linux, except the name of the device -(\filename{/dev/cdrom}, here) may vary. (All our examples will use -\texttt{>} as the shell prompt; user input is \underline{underlined}.) -\begin{alltt} -> \Ucom{mount -t iso9660 /dev/cdrom /mnt/cdrom} -\end{alltt} - -\noindent Change the current directory to the mount point: -\begin{alltt} -> \Ucom{cd /mnt/cdrom} -\end{alltt} - -\noindent Under \MacOSX, the directory is typically under -\dirname{/Volumes}, and the media will be mounted automatically. -} - -\startinst - -Run the installation script \filename{install-tl.sh}: -\begin{alltt} -> \Ucom{sh install-tl.sh} -Welcome to TeX Live... -\end{alltt} - -\def\firstinstcommand{% -\noindent After various greeting messages and a list of the main menu -options, the installation will ask you to enter a command. Do this by -typing the desired character and hitting return; don't type the angle -brackets. Either uppercase or lowercase is ok; we'll use lowercase in -our examples. -} -\firstinstcommand - -For running live, our first command will be \Ucom{d} and then the -subcommand \Ucom{1} to set directories. Even in this case, we must -choose a directory on the local disk to place files that the \TeX{} -system itself generates, such as fonts and formats, and also to provide -a place for updated configuration files, if need be. We'll use -\dirname{/usr/local/texmf-local} in this example. (If the default value -of \dirname{/usr/TeX} works for you, then you can skip this step.) -\begin{alltt} -Enter command: \Ucom{d} -Current directories setup: -<1> TEXDIR: /usr/TeX -... -Enter command: \Ucom{1} -New value for TEXDIR [/usr/TeX]: \Ucom{/usr/local/texmf-local} -... -Enter command: \Ucom{r} -\end{alltt} - -\noindent Back at the main menu, our second and last command is -\Ucom{r}, to set up for running live off the media without installing -to disk: -\begin{alltt} -Enter command: \Ucom{r} -Preparing destination directories... -... -Welcome to the TeX Live system! -> -\end{alltt} - -\noindent And we are back at the system prompt, as shown. - -Next, it is necessary to alter two environment variables: -\envname{PATH}, to an architecture-dependent value (so that we can run -the programs), and \envname{VARTEXMF}, to the value specified above. See -table~\ref{tab:archlist} for a list of the architecture names for the -different systems, and whether they are available on the \pkgname{demo} -\CD. All systems are available in the \pkgname{inst} and \pkgname{live} -distributions. (In addition to the version-specific names listed here, -there are generic names without the version numbers. For instance, -\dirname{sparc-solaris} links to \dirname{sparc-solaris2.7}. The -generic names can be used to protect against the version numbers -changing in the future, if you wish.) - -\def\runtexconfig{% -After the main installation has completed, and environment variables -have been set, the next step is to run \cmdname{texconfig} to customize -your installation for your needs. This is explained in -section~\ref{sec:texconfig}, p.~\pageref{sec:texconfig}. -} -\runtexconfig - -\begin{table*}[ht] -\caption{Supported system architectures.} -\label{tab:archlist} -\begin{tabular}{>{\ttfamily}lll} -alpha-linux & HP Alpha Linux & \\ -alphaev5-osf4.0d & HP Alphaev5 OSF & \\ -%hppa2.0-hpux10.20 & HP9000 HPUX 10.20 & \\ -i386-freebsd4.8 & Intel x86 FreeBSD & \\ -i386-linux & Intel x86 GNU/Linux & demo \CD\\ -i386-openbsd3.3 & Intel x86 OpenBSD & \\ -i386-solaris2.8 & Intel x86 Solaris & \\ -mips-irix6.5 & SGI IRIX & \\ -powerpc-aix4.3.3.0 & IBM RS/6000 AIX & \\ -powerpc-darwin6.3 & \MacOSX & demo \CD\\ -sparc-solaris2.7 & Sun Sparc Solaris & \\ -sparc64-linux & Sun Sparc Linux & \\ -win32 & Windows (32-bit) & demo \CD\\ -\hline -\end{tabular} -\end{table*} - -\label{text:path} -The syntax for setting the environment variables, and the initialization -file to put them in, depends on the shell you use. If you use a -Bourne-compatible shell (\cmdname{sh}, \cmdname{bash}, \cmdname{ksh}, et -al.), put the following into your \filename{$HOME/.profile} file: -\begin{alltt} -PATH=/mnt/cdrom/bin/\Ucom{\emph{archname}}:$PATH; export PATH -VARTEXMF=/usr/local/texmf-local/texmf-var; export VARTEXMF -\end{alltt} - -\noindent For C shell-compatible shells (csh, tcsh), put the following -into your \filename{$HOME/.cshrc} file: -\begin{alltt} -setenv PATH /mnt/cdrom/bin/\Ucom{\emph{archname}}:$PATH -setenv VARTEXMF /usr/local/texmf-local/texmf-var -\end{alltt} - -\def\donewithinst{% -\noindent Then log out, log back in, and test your installation -(see section~\ref{sec:test-install} on p.~\pageref{sec:test-install}). -} -\donewithinst - -\def\ifindoubt{% -If in doubt, please ask any local system gurus to help you with -problems; for example, the way to mount the \TeXLive{} media, which -directory or directories to use, and precise details of the changes to -your personal initialization files can and do vary from site to site. -} -\ifindoubt - - -% -\subsection{Installing \protect\TeXLive{} to disk} -\label{sec:unix-install-disk} - -It is possible, indeed typical, to install the \TeX{} system from the -\TeXLive{} to disk. This can be done either from the \pkgname{live} -\DVD, or the \pkgname{inst} \CD. It can also be done from the -\pkgname{demo} \CD, if you don't need the omitted packages or systems. -(See section~\ref{sec:multiple-dist} on p.~\pageref{sec:multiple-dist} -for an explanation of the different distributions.) - -\startinst - -Run the installation script \filename{install-tl.sh}: -\begin{alltt} -> \Ucom{sh install-tl.sh} -Welcome to TeX Live... -\end{alltt} - -\firstinstcommand - -Here is an introductory list of the options in the main menu. The order -in which you select the options makes little difference, except that -\Ucom{i} must be last. It's reasonable to go through them in the -order presented~here. - -% apparently here.sty [H] doesn't support table*. -\begin{table}[H] -\caption{Main menu options for the installation.} -\label{tab:main-menu-options} -\begin{tabular}{>{\ttfamily}ll} -p & The system you are running on.\\ -b & The architectures to install binaries for.\\ -s & The base installation scheme to use (minimal, recommended, - full, etc.)\\ -c & Override the installation scheme for individual collections.\\ -l & Override for language collections.\\ -d & Directories in which to install.\\ -o & General options.\\ -i & Perform the installation.\\ -\end{tabular} -\end{table} - -Here are further details on each option. - -\textbf{\optname{p} -- Current platform.} Since the installation script -automatically guesses which platform you're running on, this is -generally unnecessary to override. It's there in case the automatic -detection fails. - -\textbf{\optname{b} -- Binary architectures.} By default, only the -binaries for your current platform will be installed. From this menu, -you can select installation of binaries for other architectures as well -(or not install the current platforms). This is often useful if you -are sharing a \TeX\ tree across a network of heterogenous machines. For -a list of the supported architectures, see table~\ref{tab:archlist}, -p.~\pageref{tab:archlist}. - -\textbf{\optname{s} -- Base installation scheme.} From this menu, you -can choose an overall common set of packages. The default is a -recommended set for typical needs, but you can also choose a basic set -to conserve disk space, or a full set to get absolutely everything. The -\pkgname{Live} scheme is used for creating the \TeXLive{} -\pkgname{demo} distribution itself, and isn't generally useful to select -for a particular site. There are also specific sets for Omega and -\acro{XML} users. - -\textbf{\optname{c} -- Individual collections.} From this menu, you can -override the basic scheme's choice of which collections to install. -Each collection\Dash TeX macro files, Metafont font families, and so -on\Dash consists of several packages. In this menu, selection letters -are case-sensitive. - -\textbf{\optname{l} -- Language collections}. This menu has the same -basic functionality as \Ucom{c}, to override collection choices. In -this case, the collections are specifically for different languages. -Selection letters are case-sensitive here. Here is a list of the -language collections in \TeXLive: - -% xx really should generate list from texmf/tpm/collection/tex-lang* -% a la install-tl.sh. -\begin{tabbing} -\hspace{.25\linewidth} \= -\hspace{.25\linewidth} \= -\hspace{.25\linewidth} \= -\hspace{.25\linewidth} \kill - (some) African scripts \> - Armenian \> - Chinese,Japanese,Korean \> -Croatian \\ - Cyrillic \> - Czech/Slovak \> - Danish \> -Dutch \\ - Finnish \> - French \> - German \> -Greek \\ - Hungarian \> - Indic \> - Italian \> -Latin \\ - Manju \> - Mongolian \> - Norwegian \> -Polish \\ - Portuguese \> - Spanish \> - Swedish \> -Tibetan \\ - \acro{UK} English \> -Vietnamese \\ -\end{tabbing} - -\noindent Language collections typically includes fonts, macros, -hyphenation patterns, and other support files. (For instance, -\pkgname{frenchle.sty} is installed if you select the \optname{French} -collection.) In addition, installing a language collection will alter -the \filename{language.dat} configuration file controlling which -hyphenations are loaded. - -\textbf{\optname{d} -- Installation directories}. Three directories can -be changed here: -\label{text:instdir} - -\begin{ttdescription} -\item [TEXDIR] By default, the top-level directory under which -everything else will be installed. The default value is -\dirname{/usr/TeX}, and is often changed. For example, changing to a -value such as \dirname{/usr/local/texlive2003} would make it possible to -keep different releases of \TeXLive{} separate. You may then wish to -make \dirname{/usr/local/texlive} a symbolic link, after testing the new -release. - -Under \MacOSX, the usual frontends look for \TeX{} in -\dirname{/usr/local/teTeX}, so you may wish to install \TeXLive{} there. - -\item [TEXMFLOCAL] This tree is where the \TeX{} system scripts install -non-version-specific files, primarily fonts. The default value is -\dirname{TEXDIR/texmf-local}. It's also the recommended location to put -any local packages or configuration settings. Therefore, it's desirable -to change it to a location independent of the current \TeXLive{} -release; for example, \dirname{/usr/local/texmf-local}. - -\item [VARTEXMF] This tree is where the scripts install files that -\emph{are} version-specific, primarily format files and the -configuration files which are modified by \cmdname{texconfig} (see -section~\ref{sec:texconfig}, p.~\pageref{sec:texconfig}). The default -value is \dirname{TEXDIR/texmf-var}, and there's generally no reason to -change it. - -\end{ttdescription} - -\textbf{\optname{o} - General options.} From this menu, you can select -three general options affecting the installation: - -\begin{ttdescription} -\item [a] Specify an alternate directory for generated fonts. -The default is to use the \envname{VARTEXMF} tree, as explained above. -Setting this is useful if you plan to mount the main tree read-only, and -therefore another location (perhaps machine-specific) must be used for -dynamically created fonts. - -\item [l] Create symbolic links for the binaries, man pages, -and/or \acro{GNU} Info files in other locations. For example, you may -wish to make the man pages available under \dirname{/usr/local/man} and -the Info files available under \dirname{/usr/local/info}. (Of course -you need appropriate privileges to write in the specified directories.) - -\item [d] Skip installation of the font/macro documentation tree. -This is useful to save space, or if you've previously installed the -documentation elsewhere. - -\item [s] Skip installation of the main font/macro source -tree. This is useful if you are arranging to share that tree between -machines and/or architectures in some other way, such as \acro{NFS} or -\cmdname{automount}. - -\end{ttdescription} - -\textbf{i - Perform installation.} When you're satisfied with your -configuration options, enter \Ucom{i} to actually do the installation -from the media to your chosen locations. - -The last step is to include the architecture-specific subdirectory of -\dirname{TEXDIR/bin} in your -\envname{PATH}, so the newly-installed programs can be found. The -architecture names are listed in table~\ref{tab:archlist}, -p.~\pageref{tab:archlist}, or you can simply list the directory -\dirname{TEXDIR/bin}. - -The syntax for doing this, and the initialization file to put it in, -depends on the shell you use. If you use a Bourne-compatible shell -(\cmdname{sh}, \cmdname{bash}, \cmdname{ksh}, et al.), put the following -into your \filename{$HOME/.profile} file: -\begin{alltt} -PATH=/\Ucom{\emph{TEXDIR}}/bin/\Ucom{\emph{archname}}:$PATH; export PATH -\end{alltt} - -\noindent For C shell-compatible shells (\cmdname{csh}, \cmdname{tcsh}), -put the following into your \filename{$HOME/.cshrc} file: -\begin{alltt} -setenv PATH /\Ucom{\emph{TEXDIR}}/bin/\Ucom{\emph{archname}}:$PATH -\end{alltt} - -\runtexconfig - -Here is a brief annotated example which selects a full installation, -with binaries for the current system only, with directory changes as -recommended above. The prompts and \acro{RETURN} keys are omitted for -brevity. - -\begin{alltt} -> \Ucom{sh install-tl.sh} -\Ucom{s} \Ucom{b} \Ucom{r} # scheme, full, return to main -\Ucom{d} # change directories -\Ucom{1} \Ucom{/usr/local/texlive2003} # top-level dir -\Ucom{2} \Ucom{/usr/local/texmf-local} # TEXMFLOCAL outside TEXDIR -\Ucom{r} # return to main -\Ucom{i} # perform installation -> \Ucom{texconfig} ... -# New PATH, assuming Linux: -> \Ucom{PATH=/usr/local/texlive2003/bin/i386-linux:$PATH; export PATH} -\end{alltt} - -\ifindoubt - - -% -\subsection{Installing individual packages to disk} - -You can add individual packages or collections from the current -distribution to an existing non-\TeXLive{} setup, or an earlier -\TeXLive{} installation. You can do this from the \pkgname{demo} \CD{} -or the \pkgname{live} \DVD{}, but \emph{not} from the \pkgname{inst} -\CD. (See section~\ref{sec:multiple-dist} on -p.~\pageref{sec:multiple-dist}.) - -\startinst - -Run the installation script \filename{install-pkg.sh} (not -\filename{install-tl.sh}, which is intended for complete installations -only): -\begin{alltt} -> \Ucom{sh install-pkg.sh \emph{options}} -\end{alltt} - -This first set of options controls what gets read: - -\begin{ttdescription} -\item [-{}-package=\emph{pkgname}] The individual package to work on. - -\item [-{}-collection=\emph{colname}] The individual collection to work on. - -\item [-{}-nodoc] Exclude documentation files from the operation. - -\item [-{}-nosrc] Exclude source files from the operation. - -\item [-{}-cddir=\emph{dir}] Source directory to read from; defaults -to the current directory. If you followed the instructions above, that -will be the distribution directory, and won't need to be changed. - -\item [-{}-listdir=\emph{dir}] The so-called `lists' directory within -\emph{cddir} from which to read the package information. The default is -\texttt{\emph{cddir}/texmf/tpm/lists}; the only reason to change it is -if you're making changes to \TeXLive{} yourself. - -\end{ttdescription} - -What actually happens is controlled by the following options. If -neither of these are specified, the default action is to install the -selected files. The main destination tree is found by expanding -\envname{\$TEXMFMAIN} with \cmdname{kpsewhich}. You can override it by -setting either the environment variable \envname{TEXMFMAIN} or -\envname{TEXMF}. - -\begin{ttdescription} -\item [-{}-listonly] List the files that would be installed, but don't -actually install anything. - -\item [-{}-archive=\emph{tarfile}] Instead of installing the files into -the \TeX{} system, make a \cmdname{tar} archive. - -\end{ttdescription} - -Additional options: - -\begin{ttdescription} - -\item [-{}-config] After installation, run \code{texconfig init}. - -\item [-{}-nohash] After installation, don't run \cmdname{mktexlsr} to -rebuild the filename database. - -\item [-{}-verbose] Give more information as the script runs. - -\end{ttdescription} - -Here are some usage examples: - -\begin{enumerate} - -\item To see the files in the package \pkgname{fancyhdr} without -installing it: - -\begin{alltt} -\ifSingleColumn> \Ucom{sh install-pkg.sh --package=fancyhdr --listonly} -\else> \Ucom{sh install-pkg.sh --package=fancyhdr \bs} -> \Ucom{--listonly} -\fi{} -texmf/doc/latex/fancyhdr/README -texmf/doc/latex/fancyhdr/fancyhdr.dvi -texmf/doc/latex/fancyhdr/fancyhdr.pdf -... -\end{alltt} - -\item Install the \LaTeX{} package \pkgname{natbib}: -\begin{alltt} -> \Ucom{sh install-pkg.sh --package=natbib} -\end{alltt} - -\item Install the \LaTeX{} package \pkgname{alg} without source files or -documentation: -\begin{alltt} -\ifSingleColumn> \Ucom{sh install-pkg.sh --package=alg --nosrc --nodoc} -\else> \Ucom{sh install-pkg.sh -{}-package=alg \bs} -> \Ucom{-{}-nosrc -{}-nodoc} -\fi\end{alltt} - -\item Install all the packages in the collection of additional -plain \TeX\ macros: -\begin{alltt} -> \Ucom{sh install-pkg.sh --collection=tex-plainextra} -\end{alltt} - -\item Write all files in the \pkgname{pstricks} package to a -\cmdname{tar} file in \path|/tmp|: -\begin{alltt} -\ifSingleColumn> \Ucom{sh install-pkg.sh --package=pstricks --archive=/tmp/pstricks.tar} -\else -> \Ucom{sh install-pkg.sh -{}-package=pstricks \bs} -> \Ucom{-{}-archive=/tmp/pstricks.tar} -\fi\end{alltt} - -\end{enumerate} - -\ifindoubt - - -% -\section{Post-installation} -\label{sec:postinstall} - -After the main installation is done, for any operating system, the -remaining steps are to configure the system for your local needs, and -perform some basic tests. - -Another sort of post-installation is to acquire packages, fonts, or -programs that were not included in \TeXLive{}. The basic idea is to -install such additions in the \envname{TEXMFLOCAL} tree (if you -installed to disk), or \envname{VARTEXMF} (if you are running live). -See ``Installation directories'' on p.~\pageref{text:instdir}. - -Unfortunately, the details can vary widely, and so we do not attempt to -address them here. Please see -\url{http://www.ctan.org/tex-archive/info/beginlatex/html/chapter5.html#pkginst} -for a good description, and -\url{http://www.ctan.org/tex-archive/info/Type1fonts} for font creation -and installation information in particular. - - -\subsection{The \protect\cmdname{texconfig} program} -\label{sec:texconfig} - -At any time after installation, you can and should use the program -\cmdname{texconfig} to configure the system to fit your local needs. It -is installed in the architecture-specific subdirectory -\texttt{TEXDIR/bin/\emph{arch}} along with everything else. - -If you run it without arguments, it will enter full-screen mode and -allow you to view and change options interactively. - -You can also run it with various command-line options. Here are some of -the most commonly used: - -\begin{ttdescription} - -\item [texconfig dvips paper letter] Set default paper size for -\cmdname{dvips} to be letter-size. - -\item [texconfig xdvi us] Likewise, for \cmdname{xdvi}. - -\item [texconfig rehash] Update all the \TeX{} system filename databases. - -\item [texconfig faq] Show the \teTeX{} \acro{FAQ}. -(See also the main \TeX{} \acro{FAQ} in the \dirname{FAQ} subdirectory -of \TeXLive.) - -\item [texconfig help] Output help information. - -\end{ttdescription} - -Of course, \cmdname{texconfig} only supports changing a few of the many -options and configuration parameters in a \TeX{} system. The main -configuration file for the base \Webc{} programs is named -\filename{texmf.cnf}. You can find its location by running -\samp{kpsewhich texmf.cnf}; it contains many comments explaining the -default settings and useful alternatives. - - -\subsection{Testing the installation} -\label{sec:test-install} - -After installing \TeXLive{} as best you can, you naturally want to test -it out, so you can start creating beautiful documents and/or fonts. - -This section gives some basic procedures for testing that the new system -is functional. We described the Unix commands; under \MacOSX{} and -Windows, you're more likely to run the tests through a graphical -interface, but the principles are the same. - -\begin{enumerate} - -\item Make sure that you can run the \cmdname{tex} program in the first -place: - -\begin{alltt} -> \Ucom{tex -{}-version} -TeX (Web2c 7.5.2) 3.141592 -kpathsea version 3.5.2 -Copyright (C) 1997-2003 D.E. Knuth. -... -\end{alltt} -If this comes back with `command not found' instead of version and -copyright information, most likely you don't have the correct -\dirname{bin} subdirectory in your \envname{PATH}. See -the environment-setting information on p.~\pageref{text:path}. - -\item Process a basic \LaTeX{} file: -\begin{alltt} -> \Ucom{latex sample2e.tex} ->TeX (Web2c 7.5.2) 3.141592 -... -Output written on sample2e.dvi (3 pages, 7256 bytes). -Transcript written on sample2e.log. -\end{alltt} -If this fails to find \filename{sample2e.tex} or other files, perhaps -you have interference from old environment variables or configuration -files. For a deep analysis, you can always ask \TeX{} to report on -exactly what it is searching for, and finding; see ``Debugging actions'' -on page~\pageref{Debugging}. - -\item Preview the result online: -\begin{alltt} -> \Ucom{xdvi sample2e.dvi} -\end{alltt} -Under Windows, the analogous command is \cmdname{windvi}. You should -see a new window with a nice document explaining some of the basics of -\LaTeX{}. (Well worth reading, if you're new to the system.) You do -have to be running under X for \cmdname{xdvi} to work; if you're not, or -your \envname{DISPLAY} environment variable is set incorrectly, you'll -get an error \samp{Can't open display}. - -\item Create a \PS{} file for printing or display: -\begin{alltt} -> \Ucom{dvips sample2e.dvi -o sample2e.ps} -\end{alltt} - -\item Create a \acro{PDF} file instead of \dvi{}; this processes the -\filename{.tex} file and writes \acro{PDF} directly: -\begin{alltt} -> \Ucom{pdflatex sample2e.tex} -\end{alltt} - -\item Preview the \acro{PDF} file: -\begin{alltt} -> \Ucom{gv sample2e.pdf} -\textrm{or:} -> \Ucom{xpdf sample2e.pdf} -\end{alltt} -Unfortunately neither \cmdname{gv} nor \cmdname{xpdf} are currently -included in \TeXLive{}, so you must install them separately. See -\url{http://wwwthep.physik.uni-mainz.de/~plass/gv} and -\url{http://www.foolabs.com/xpdf}, respectively. - -\item Other standard test files you may find useful: - -\begin{ttdescription} -\item [docstrip.tex] Produce \TeX{} source or documentation from a -\samp{.dtx} file. -\item [small2e.tex] A simpler document than \filename{sample2e}, to -reduce the input size if you're having troubles. -\item [testpage.tex] Test if your printer introduces any offsets. -\item [nfssfont.tex] For printing font tables and tests. -\item [testfont.tex] Also for font tables, but using plain \TeX{}. -\item [story.tex] The most canonical (plain) \TeX{} test file of all. -You must type \samp{\bs bye} to the \code{*} prompt after \samp{tex -story.tex}. -\end{ttdescription} -You can process these in the same way as we did with -\filename{sample2e.tex}. - -\end{enumerate} - -If you are new to \TeX{}, or otherwise need help with actually -constructing \TeX{} or \LaTeX{} documents, please visit -\url{http://tug.org/begin.html}. We especially recommend the -\textsl{Formatting Information} manual by Peter Flynn, available at -\url{http://www.ctan.org/tex-archive/documentation/beginlatex}. - - -\section{\MacOSX{} installation} -\label{sec:mac-install} - -\TeXLive{} supports \MacOSX, but no prior Macintosh versions. (If you -are running an older Mac version, you can view the files by installing -the Joliet system extension available from -\url{http://www.tempel.org/joliet}; however, the \TeXLive{} binaries -will not run.) - -Installation of \TeX{} under \MacOSX{} can be done in two ways: - -\begin{enumerate} -\item With the \filename{install*} scripts, as with Unix. -\item With the \cmdname{i-Installer} included in -\filename{MacOSX/II2.dmg}. -\end{enumerate} - -\noindent Each of these is described in a following section. - -In addition, typical use of \TeX{} under \MacOSX\ goes through a -\emph{frontend}. This is also described below. - - -\subsection{\protect\cmdname{i-Installer}: Internet installation} -\label{sec:i-Installer} - -The \cmdname{i-Installer} is included in the \TeXLive{} distribution as -an alternative to normal installation. It does not use the contents of -the \TeXLive{} distribution at all; instead, the system (approximately -70 megabytes) is downloaded over the Internet. - -One advantage of \cmdname{i-Installer} is that it makes updates -relatively painless. If you are interested, please see the -\cmdname{i-Installer} \TeX{} home page at \url{http://www.rna.nl/tex.html}. - -To use it, mount \filename{./MacOSX/II2.dmg}. Read the documentation, -launch it, and install at least \emph{TeX Foundation} and \emph{TeX -Programs}. The first will finish without configuration, as soon as the -second is installed you will be presented with a graphical interface to -setting up your \TeX{} system. - -The \cmdname{i-Installer} distribution uses the \teTeX{} \dirname{texmf} -tree with some additions. Due to differences between \TeXLive{} and -\teTeX{} you cannot update a \TeXLive{} installation with an -\cmdname{i-Installer} \emph{TeX Programs} i-Package. - - -\subsection{\protect\cmdname{install*.sh}: \protect\TeXLive{} installation} - -In order to run the installation scripts under \MacOSX, you need to have -the \cmdname{bash} shell installed. If you are running \MacOSX~10.2 -or later, you have \cmdname{bash}, and can proceed. If you're running -an earlier \MacOSX{} version, however, the default shell is -\cmdname{zsh}, which won't work; please see the -subsection~\ref{sec:mac-bash} (p.~\pageref{sec:mac-bash}) below for -instructions on installing bash \cmdname{bash}. - -Once you have \cmdname{bash}, the Unix installation documentation in the -previous section can be followed. See section~\ref{sec:unix-install} on -p.~\pageref{sec:unix-install}; \MacOSX-specific notes are included where -needed. - - -\subsection{\MacOSX{} frontends} - -Using \TeX{} on a Macintosh typically goes through a front end program, -comprising an execution shell, editor, previewer, and other facilities. -Here are the principal frontends: - -\begin{cmddescription} -\item [TeXShop] Included in \TeXLive{} as -\filename{./MacOSX/texshop.dmg}. See -\url{http://www.uoregon.edu/~koch/texshop/texshop.html}. - -\item [ITeXMac] Included in \TeXLive{} as -\filename{./MacOSX/iTeXMac-*.dmg}. See -\url{http://itexmac.sourceforge.net}. - -\item [Mac-emacs] A port of Emacs to \MacOSX{}, integrating -\pkgname{AucTeX}. See \url{http://www.cs.man.ac.uk/~franconi/mac-emacs}. - -\end{cmddescription} - -The frontends use \dirname{/usr/local/teTeX} as the default location; -therefore, you must either install \TeXLive{} there, or change the -configuration of the frontend. - - -\subsection{\cmdname{bash} installation for older \MacOSX{} versions} -\label{sec:mac-bash} - -\MacOSX{} versions 10.1 and earlier do not include \cmdname{bash} by -default, and the default shell does not run the \TeXLive{} installation -scripts properly. This section explains how to install \cmdname{bash}. - -First, check if bash is already installed. `Launch Terminal' -(\filename{/Applications/utilities/Terminal}) and type \code{rehash; -which bash}. If the answer is a filename (for example, -\code{/bin/bash}), then \cmdname{bash} is already installed, and you're done -here; go back to the main installation instructions. -If the answer is \code{bash: command not found}, proceed here. - -There are two ways to install \cmdname{bash} if you need it\Dash via the -\acro{GUI} or via command line. - -To install via \acro{GUI}, double-click the \filename{MacOSX/bash.dmg} -file in \TeXLive{}. The disk image (volume) will be mounted. Then -start the \cmdname{i-Installer} application on that volume. You will be -asked to authenticate; if you have never seen that before, you might not -have enough privileges to install. Just enter your own user name and -password. Hit install. Bash will be installed on your system. - -To install via command line: -\begin{enumerate} -\item ensure you have admin privileges: log in as the -\code{admin} user, the System Administrator, a user with Admin -privileges, using \cmdname{sudo}, etc. - -\item copy \filename{MacOSX/bash.tar.gz} from the \TeXLive{} -distribution to your home directory. - -\item Launch Terminal, and run: -\begin{alltt} -(cd /usr/local/; sudo tar xvzf ~/bash.tar.gz) -\end{alltt} -You'll be asked for your password, and then \cmdname{bash} will be -installed. - -\item Quit Terminal. - -\end{enumerate} - -After using either installation method, be sure to recheck that -\cmdname{bash} is installed with \code{rehash; which bash} in a new -Terminal window. - - -\section{Windows installation} -\label{sec:win-install} - -\TeXLive{} can be installed on systems running Windows 9x, \acro{ME}, -\acro{NT}, \acro{2K} or \acro{XP}. Older versions of Windows (3.1x) -and \acro{MS-DOS} are not supported. - -It is necessary to have your Windows set up so that it uses the -Microsoft Joliet extensions for reading \CD{}s; simply look at the \CD{} -in Explorer and see whether it shows long, mixed-case, file names. If it -does not, you must install the Joliet extensions. - -The Windows \TeX{} system included in \TeXLive{} is no more and no less -than the \fpTeX{} distribution. It includes a \texttt{dvi} previewer, -\textsf{Windvi}, which is similar in usage to the established Unix -\textsf{xdvi}. The documentation can be found in -\OnCD{texmf/doc/html/windvi/windvi.html}. - -\subsection{The \texttt{TeXLive.exe} program} - -\begin{figure*} - \begin{center} - \ifnum \Status=1 - \includegraphics[width=.7\textwidth]{../pictures/Welcome-to-TeXLive} - \else - \ifnum \Status=2 - \includegraphics[bb=0 0 551 534]{../pictures/Welcome-to-TeXLive.jpg} - \else - \includegraphics[width=.7\textwidth]{../pictures/Welcome-to-TeXLive} - \fi - \fi - \end{center} - \caption{``Welcome to \TeXLive'' window}\label{graph:welcome} -\end{figure*} - -If your computer is configured to let the \CD{} autostart, then a dialog -box with a menu bar will popup on the screen, and you will have several -choices from there: - -\begin{itemize} -\item Install \TeX{} on your hard disk -\item Do maintenance on your \TeX{} system. -\item Remove the \TeX{} system. -\item Use \TeX{} off the \TeXLive{} \CD{} or \DVD{}. -\item Browse documentation: \TeXLive{} documentation, TUG web - pages, \fpTeX web pages. -\item Run the \cmdname{TeXdocTK} application to find specific documentation. -\end{itemize} - -If your \CD{} does not autostart, you can explicitly run the program -by double clicking on \path|bin/win32/TeXLive.exe| on the \CD{} from -the explorer window. - -\subsection{Running \protect\TeXLive{} directly from media (Windows)} - -\runlive - -To run live under Windows, from the menu, chose \verb|Explore CD-Rom|, then -\verb|Run TeX off CD-Rom|. This will launch the \cmdname{XEmacs} editor. - -%% To run live under Windows, do the following: - -%% \begin{enumerate} -%% \item from the menu, chose \verb|Explore CD-Rom|, then -%% \verb|Run TeX off CD-Rom|, that will launch the \cmdname{XEmacs} editor. - -%% This program needs to be a \TeX{} oriented editor. It must be able -%% to run the \TeX{} compiler, previewer and any other needed tool. If -%% you don't have one already installed on your system, you can install -%% one from the \CD{}, details section~{\ref{sec:texlive-install}}. - -%% \emph{There is no way we can guess if the program you will -%% select is actually a text editor, so be careful}. -%% Here is a list of frequently used \TeX{} editors: -%% \begin{center} -%% \begin{tabular}[H]{ll} -%% GNU Emacs & \path|c:\Program Files\NTEmacs\bin\runemacs.exe| \\ -%% XEmacs & \path|c:\Program Files\XEmacs\XEmacs-21.2\i586-pc-win32\xemacs.exe| \\ -%% WinShell & \path|c:\Program Files\WinShell\WinShell.exe| \\ -%% WinEdt & \path|c:\Program Files\WinEdt Team\WinEdt\WinEdt.exe|\\ -%% TeXnicCenter & \path|c:\Program Files\TeXnicCenter\TEXCNTR.exe| -%% \end{tabular} -%% \end{center} -%% The program -%% selected will be memorized as the editor to use for future runs. - -%% \item from the menu, chose \verb|Explore CD-Rom|, then -%% \verb|Run TeX off CD-Rom|. The environment will be modified, a small -%% temporary directory created and some configuration files copied -%% there. Then, the selected editor selected will be launched, and you -%% will be able to type in some text, let \TeX{} typeset it and the -%% view it or print it. - -%% If Ghostscript is not detected on your machine, you will be warned -%% that rendering your DVI files might fail. You can install it from -%% the \path|Install|, \path|Support| menu item. See -%% section~\ref{sec:texlive-install} for details. - -%% \item you can select a different text editor any time you want. - -%% \item if you chose \verb|Cleanup CD-Rom setup|, everything \TeX{} -%% needed will be removed, comprised the selection of your text -%% editor, but not the extra packages you may have downloaded and -%% installed. If you installed \cmdname{WinShell} or \cmdname{NTEmacs}, -%% they won't be removed. -%% \end{enumerate} - -XEmacs startup file will set the environment variables needed. XEmacs will also -setup a temporary \acro{TDS} compliant texmf tree in the temporary area of your -computer. It is needed to store files that may be built on the fly, such as -\path|pk| bitmap fonts, or format files. Configuration files are copied from -the \CD{} to this texmf tree, so that you can edit them if needed. The -\path|ls-R| database is computed for this texmf tree. The AUC-\TeX{} mode will -be entered Whenever you will visit or create a \TeX{} file, providing all the -bells and whistles for \TeX{} support XEmacs is capable of. - -If you run 'M-x shell' within XEmacs, then you will have access to all the TeXLive -tools from the command line provided by XEmacs. - -\smallskip {\small\noindent \textbf{[For advanced users:]} You can also - use the small batch file \path|mkloctex.bat| to be called in a - directory \path|bin\win32| of the \CD. From the Start menu select - `Run', then browse the \acro{CD} drive and select - \path|mkloctex.bat|. Before starting it, you should add two parameters - separated by a space: the letter of your \acro{CD} drive and the - letter of the drive where you want to install the \TeX\ directory. - The whole line should read, e.g., \verb+d:\bin\win32\mkloctex.bat d c+. - When installation is complete, please read carefully the information - on screen. If you are running Windows 9x/\acro{ME}, then you will have to - restart Windows.} - -\subsection{Support packages for Windows} -\label{sec:win-xemtex} - -To be complete, a \TeXLive installation needs support packages that are not -commonly found on a Windows machine. -Many scripts are written using the Perl language. Some important tools require -the Ghostscript \PS{} interpreter to render or to convert files. A graphic -file toolbox is also needed in some cases. Last but not least, a \TeX-oriented -editor makes it easy to type in your \TeX{} files. - -All these tools are quite easy to find for Windows, but in order to try to make -your life even easier, we have put such a set of tools on \TeXLive: -\begin{itemize} -\item \cmdname{Ghostscript} 7.07 -\item a minimal \cmdname{Perl} 5.8, sufficient to run all the \TeXLive{} -Perl scripts -\item a subset of \cmdname{ImageMagick} 5.5.6 -\item the \cmdname{ISpell} checker -\item \cmdname{XEmacs} 21.5.14 with a selection of packages to support -\TeX{} typesetting. -\end{itemize} - -These packages should be installed only all at once. The bundle is -known as the \XEmTeX{} bundle. - -If you didn't install \XEmTeX{}, \cmdname{Perl} and \cmdname{Ghostscript} are -installed anyway if they are not detected on your machine. This is because they are -required by many important tools. The \envname{PERL5LIB} and \verb|GS_LIB| -environment variables will be set too. - -When you are under -\cmdname{XEmacs}, the tools provided shadow any other version you might -have installed previously. The point here is that \path|TeXSetup.exe| -will not install anything outside of the \TeXLive location, neither will -it run foreign installers, nor will it try to autodetect installed -products using unreliable rules of thumb. The \XEmTeX{} bundle is -standalone and is meant to evolve in the future. The reference site is -\url{http://www.fptex.org/xemtex/}. - -If you don't want to install this bundle, then you are on your own to -install the required tools to complete your \TeXLive{} system. Here is a -list of places to get those tools: - -\begin{description} -\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} -\item[Perl] \url{http://www.activestate.com/} (but you might need some - supplementary packages from CPAN: \url{http://www.cpan.org/}) -\item[ImageMagick] \url{http://www.imagemagick.com} -\item[NetPBM] alternatively, you could use NetPBM instead of ImageMagick to - process or convert your graphic files. NetPBM home page is - \url{http://netpbm.sourceforge.net/} -\item[\TeX-oriented editors] There is a wide choice, and it is a matter of the - user's taste. Here is a selection: - \begin{itemize} - \item \cmdname{GNU Emacs} is available natively under Windows, the - reference url is - \url{http://www.gnu.org/software/emacs/windows/ntemacs.html} - \item \cmdname{XEmacs} is available natively under Windows, the - reference url is \url{http://www.xemacs.org/} - \item \cmdname{WinShell} is available on \TeXLive in the \path|support| - directory, the reference url is \url{http://www.winshell.de} - \item \cmdname{WinEdt} is shareware available from \url{http://www.winedt.com} - \item TeXnicCenter is available from - \url{http://www.toolscenter.org/products/texniccenter/} - \item \cmdname{Vim} is available on \TeXLive{} in the - \path|support\vim| directory and the - reference site is \url{http://www.vim.org} - \item \cmdname{SciTE} is available from \url{http://www.scintilla.org/SciTE.html} - \end{itemize} -\end{description} - -You might want to install other tools that are not free\footnote{Not -free, that is, in the sense of freedom to modify and redistribute, -following Debian's guidelines. This does not mean you can't acquire -them for no money.} and therefore not included on \TeXLive{}, such as -\cmdname{GSView}, the \cmdname{Ghostscript} companion to more -conveniently view PS/PDF files. \cmdname{GSView} is available from -\url{http://www.cs.wisc.edu/~ghost/gsview/} or any \acro{CTAN} site. - -%% \subsection{Installing editors or support packages} -%% \label{sec:texlive-install} - -%% You can use the \path|TeXSetup.exe| program to install a -%% single (not \TeX{}-dependent) package. This might be an editor -%% such as \cmdname{WinShell} or \cmdname{NTEmacs}, -%% or a support package like \cmdname{NetPBM} -%% (graphics formats conversion) or \cmdname{Ghostscript}. - -%% Some of the packages are not free, or not with the same meaning as for -%% the rest of the \CD{}. These packages have been made available through -%% the Internet. You need to enable an Internet connection in order to -%% install them. Chosing the \path|Enable Internet access| subitem will -%% search your system for an active Internet connection, or start one if -%% possible. \emph{If your computer is not connected to the Internet, -%% then the timeout might be long, 30s or more}. So try to enable it -%% only if you know you have a connection. - -%% Only a few packages are available from the \CD{}, but the most -%% important of them: \cmdname{NTEmacs} and \cmdname{WinShell} for the -%% editors, \cmdname{Ghostscript} and \cmdname{NetPBM} for the other -%% support packages. \cmdname{NetPBM} is needed for running \TeX{}4ht. - -%% The downloadable packages are sometimes huge: \cmdname{Perl} is 10Mb, -%% \cmdname{XEmacs} is 50Mb, so be warned that it can take a lot of time -%% to install such things. \path|TeXSetup.exe| does not yet provide an -%% estimation of the time needed to complete the download. - -%% When installing these packages, \path|TeXSetup| is working in -%% unattended mode. However, the programs that have their own installer -%% like WinEdt or Ghostscript for example will require human interaction. - -%% Those packages who have no specific installer will be unpacked and configured -%% for your system. You will be required to select some directory where -%% they will be installed. The directory to select should be the root -%% directory of the whole installation. Assuming you want to install -%% NTEmacs and NetPBM, the archive files already contain the -%% \path|NTEmacs\| and \path|NetPBM\| part, so the directory you have to -%% select is something like \path|c:\Local| or \path|c:\Program Files|. - -\subsection{Installing \TeXLive{} to disk} - -\textbf{Warning: Win9x users must ensure they have enough environment - space before undertaking installation. The \cmdname{TeXSetup.exe} - program won't change the environment size for them. A few environment - variables will be created and it is possible you run out of - environment space. Add "SHELL=COMMAND.COM /E:4096 /P" in the - config.sys file in order to increase your environment size.} - -Installation is started by letting the media autostart. The program run -is \path|TeXSetup.exe| if you are using the inst disk. If you are using -the live or the demo disk, you will have to select the item -\path|TeXLive Software| from the menu, then the subitem \path|Install on -Hard Disk|. This will invoke \path|TeXSetup.exe|. You can also find it -in the \path|bin/win32| directory and run it, if the autostart fails for -any reason. \path|TeXSetup.exe| is a Windows wizard and it will display -several pages while running. - -\begin{description} -\item[Welcome Page] - You can choose a \emph{quick} installation from - here. In this case, the installation will run without any human - assistance from beginning to end, with all the default settings - (Figure~\ref{graph:setup-src}, - \ifnum \Status = 1 - on the left% - \else\ifnum \Status=2 - at the top% - \else - on the left% - \fi\fi - ). If you have enough privileges (administrator or power user - rights) under a Windows version where this is applicable, then you can - decide to install the \TeXLive{} for all users or for yourself only by - checking the appropriate box. - For installing the whole \XEmTeX{} bundle (XEmacs, Ghost\-script, - Perl, ImageMagick and Ispell) you can check \emph{Install XEmTeX - Support} box. - \begin{figure*}[!htb] - The \cmdname{TeXSetup} Wizard\hfill - Source directories for the \TeXLive{} files - - \begin{center} - \ifnum \Status=1 - \includegraphics[width=.48\textwidth]{../pictures/setup-wizard.jpg}\hfill% - \includegraphics[width=.48\textwidth]{../pictures/source-for-texlive.jpg} - \else - \ifnum \Status=2 -\includegraphics[bb=0 0 506 403]{../pictures/setup-wizard.jpg} -\includegraphics[bb=0 0 506 403]{../pictures/source-for-texlive.jpg} - \else - \includegraphics[width=.48\textwidth]{../pictures/setup-wizard}% - \hfill% - \includegraphics[width=.48\textwidth]{../pictures/source-for-texlive} - \fi - \fi - \caption{The \TeXLive{} setup wizard}\label{graph:setup-src} - \end{center} -\end{figure*} -\item[Source Page] - This page is a bit complex. It will allow you to select two source - directories for your \TeXLive{} system - (Figure~\ref{graph:setup-src}, - \ifnum \Status = 1 - on the right% - \else\ifnum \Status=2 - at the bottom% - \else - on the right% - \fi\fi - ). You will need a \emph{local - source directory} and possibly a \emph{remote source directory}. - -Why do we need both these directories? The files consisting of the -\TeXLive{} system are on the \CD{}, of course, but some other useful -packages are not, either because of space lacking or because their -license was not compatible with \TeXLive{}. You need to enable Internet -downloading if you want to install these packages that are marked with a -specific ``remote'' icon. - - However, don't panic: the default parameters of the setup will allow - you to install a full system using the \CD{} only. Simply, you won't - have \file{WinEdt} (for example), but you will be able to install it - later. - - So you can take your files from: - \begin{itemize} - \item the \CD{} or any similar flat tree of files, available through - some standard directory (this means the \CD{} can be mounted on - some remote machine and be made available through network - sharing), - \item a set of \file{.zip} files (this is the case when you are - installing from the demo \CD{} or the \fpTeX{} distribution), - \item the Internet; in this case, the program takes care of - downloading the \file{.zip} files it needs for you. - \end{itemize} - This option is available only if you enable Internet file - downloading in the right part of the page. You also need to - configure this Internet access by selecting to connect either using - Internet Explorer~5 \file{wininet.dll}, or using a direct connection (\texttt{ftp}, - \texttt{http}). -% or using a proxy server. -% Last, you can be assisted in defining the \emph{local source -% directory} and \emph{remote source directory} which will be used -% to copy the files onto your hard disk. The \texttt{browse} buttons -% allow to select a directory for the former, and an url among a list -% of mirrors for the latter. -\item[Root Page] - On this page, you will tell where you want the files to be - installed (Figure~\ref{graph:root-schm}, - \ifnum \Status = 1 - on the left% - \else\ifnum \Status=2 - at the top% - \else - on the left% - \fi\fi - ). Only the root directory really matters, the other ones - are set according to the root one. You may want to make - \path|$TEXMFEXTRA| point to some TDS compliant directory with other - \TeX{} files or assign a different value to - \path|$HOMETEXMF|, which is set by default to whatever Windows think - is your `HOME' location. -\begin{figure*}[!htb] - Root and directories\hfill% - Scheme selection - \begin{center} - \ifnum \Status=1 - \includegraphics[width=.46\textwidth]{../pictures/root-of-installation.jpg}\hfill% - \includegraphics[width=.46\textwidth]{../pictures/scheme-selection.jpg} - \else - \ifnum \Status=2 -\includegraphics[bb=0 0 506 403]{../pictures/root-of-installation.jpg} -\includegraphics[bb=0 0 506 403]{../pictures/scheme-selection.jpg} - \else - \includegraphics[width=.46\textwidth]{../pictures/root-of-installation}% - \hfill% - \includegraphics[width=.46\textwidth]{../pictures/scheme-selection} - \fi - \fi - \caption{\TeXLive-Setup: Root and directories / Schemes}\label{graph:root-schm} - \end{center} -\end{figure*} -\item[Get TPM Page] - This page does not require any manual intervention. The \file{.tpm} - files which describe collections and packages are retrieved - (possibly from the Internet), unzipped if needed and parsed. -\item[Schemes Page] - On this page, you will select the global scheme of your - installation (Figure~\ref{graph:root-schm}, - \ifnum \Status = 1 - on the right% - \else\ifnum \Status=2 - at the bottom% - \else - on the right% - \fi\fi - ). A scheme is a large set of files targeted at some kind - of usage. There are 3 generic schemes for basic, recommended and - full installation. The other ones are devoted to LUGs (what GUST or - GUTenberg propose for their members) or applications (XML and - \TeX{}). - When a scheme is selected, it is still possible to refine the - selection by checking the appropriate box. If doing so, you will be - presented the packages page to change your selection, else you will - jump to the review page. -\item[Packages Page] - Collections and packages are presented in a tree form - (Figure~\ref{graph:win32-support}, - \ifnum \Status = 1 - on the left% - \else\ifnum \Status=2 - at the top% - \else - on the left% - \fi\fi - ). The links - in the tree are dependency links. Collections \emph{depend on} - packages and maybe other collections, and it is the same for each - package. You can select any package or collection individually, but - your request will be granted only if the object is not requested by - another one which is selected. For example, you can't deselect - \texttt{tex-basic} without deselecting all the collections that - request it. - - The \texttt{tex-xemtex} collection displayed on the picture is Win32 specific. It - holds a number of bonus packages (Figure~\ref{graph:win32-support}, - \ifnum \Status = 1 - on the right% - \else\ifnum \Status=2 - at the bottom% - \else - on the right% - \fi\fi - ) which can be installed - automatically and individually: Ghostscript (the \PS{} - interpreter), XEmacs editor preconfigured for \TeX{}, tools like Perl, - ImageMagick, Ispell. \emph{None of these packages are selected by - default}. - - On this page, you also have the information about disk space - needed, for each object, and for the set of those who are selected, - and also the disk space available on the partition selected for the - installation. Last, you can choose to install or not the - documentation files and source files associated with each package. -\item[Review Page] - You will find there a summary of your choices - (Figure~\ref{graph:review}, - \ifnum \Status = 1 - on the left% - \else\ifnum \Status=2 - at the top% - \else - on the left% - \fi\fi - ). It is still possible to - go back to change them. -\begin{figure*}[!htb] - Packages Page\hfill% - Win32 Support - \begin{center} - \ifnum \Status=1 - \includegraphics[width=.48\textwidth]{../pictures/package-selection}\hfill% - \includegraphics[width=.48\textwidth]{../pictures/win32-support} - \else - \ifnum \Status=2 -\includegraphics[bb=0 0 506 403]{../pictures/package-selection.jpg}\hfill% -\includegraphics[bb=0 0 506 403]{../pictures/win32-support.jpg} - \else - \includegraphics[width=.48\textwidth]{../pictures/package-selection}% - \hfill% - \includegraphics[width=.48\textwidth]{../pictures/win32-support} - \fi - \fi - \end{center} - \caption{Packages Page / Win32 goodies} - \label{graph:win32-support} -\end{figure*} -\item[Files Copy Page] - The selected files are copied on your hard disk (Figure~\ref{graph:file-copy}, - \ifnum \Status = 1 - on the right% - \else\ifnum \Status=2 - at the bottom% - \else - on the right% - \fi\fi - ). All the files not - yet available on your local disk are first downloaded from the - remote source directory on the Internet. Then every package is - unpacked (if \path|.zip| files), or copied from the \CD{}. -\item[Configuration Page] Several packages need some configuration - step to make them usable (Figure~\ref{graph:configuration}, - \ifnum \Status = 1 - on the left% - \else\ifnum \Status=2 - at the top% - \else - on the left% - \fi\fi - ). Also the \TeXLive{} system needs some post-processing step - (format files generation, ls-R databases generation, environment - variables, etc.). All these operations are done there, some of them - can be lengthy. -\begin{figure*}[!htb] - \textbf{Review Page}\hfill% - \textbf{File Copy Page} - \begin{center} - \ifnum \Status=1 - \includegraphics[width=.48\textwidth]{../pictures/review-settings}\hfill% - \includegraphics[width=.48\textwidth]{../pictures/file-copy} - \else - \ifnum \Status=2 - \includegraphics[bb=0 0 506 403]{../pictures/review-settings.jpg}\hfill% - \includegraphics[bb=0 0 506 403]{../pictures/file-copy.jpg} - \else - \includegraphics[width=.48\textwidth]{../pictures/review-settings}\hfill% - \includegraphics[width=.48\textwidth]{../pictures/file-copy}% - \fi - \fi - \end{center} - \caption{Review Page / File Copy Page} - \label{graph:review}\label{graph:file-copy} -\end{figure*} -\item[Final Page] The installation being over, you may want to display - the Windows specific documentation (HTML format) and / or the log - file of the setup process (Figure~\ref{graph:final} - \ifnum \Status = 1 - on the right% - \else\ifnum \Status=2 - at the bottom% - \else - on the right% - \fi\fi - ). If it is needed (Win9x/WinME), you will - be asked to reboot your computer. -\end{description} - -\begin{figure*}[!htb] - \textbf{Configuration Page}\hfill% - \textbf{Final Page} - \begin{center} - \ifnum \Status=1 - \includegraphics[width=.48\textwidth]{../pictures/configuration}\hfill% - \includegraphics[width=.48\textwidth]{../pictures/congratulations} - \else - \ifnum \Status=2 - \includegraphics[bb=0 0 506 403]{../pictures/configuration.jpg}\hfill% - \includegraphics[bb=0 0 506 403]{../pictures/congratulations.jpg} - \else - \includegraphics[width=.48\textwidth]{../pictures/configuration}\hfill% - \includegraphics[width=.48\textwidth]{../pictures/congratulations}% - \fi - \fi - \end{center} - \caption{Configuration Page / Final page} -\label{graph:configuration}\label{graph:final} -\end{figure*} - -Please be aware that the choice of cluster size on DOS disk -partitions can radically affect the size of your \TeX\ -installation. The support tree has hundreds of small files, and it is -not unusual for a complete installation to take up to four times the -amount of space used on the \CD. - - -\section{Windows maintenance and post-installation} - -\subsection{What's different in Windows?} - -The Windows version of \Webc{} has some specific features that should be -pointed out. - -\begin{description} -\item[\KPS{}] The hash-tables that \KPS{} builds are quite large for - the \TeXLive{}. In order to cut down the starting time of any - \KPS{}-enabled program, these hash-tables have been put in shared - memory. This way, when you chain the execution of several such - programs, like \path|tex| calling \path|mpost| calling \path|tex|, - the overhead when starting each of the subprograms is - reduced. This change is hidden to the user, except if you set the - debug flag of kpathsea to the \path|-1| value: you will then trace - access to the shared memory, which is not what you want (it is - accessed very often!). What is useful in a log trace of the shared - memory access is still to be defined, so the situation might evolve - in the future. -\item[\cmdname{kpsecheck}] This command provides some options that did - not fit well into \cmdname{kpsewhich}. It will allow you to list all - the files that occur multiple times across your texmf trees. This - could be handy, but most of the time you will also get unwanted - output (like dozens of \path|README| files)\footnote{It is noticeable - that all these files result in clashes inside the \KPS{}-hashing - mechanism; fortunately, \KPS{} never looks for these files.}. For - this reason, you can combine the \path|-multiple-occurences| with 2 - other options for including or excluding any filename that match - some pattern (you can request for several patterns). - - The \cmdname{kpsecheck} command will also report the status of shared - memory: in use or not used. That might be useful to know because if - the status reported is \samp{in use}, that means one or several - processes are working, and the effect of any \cmdname{mktexlsr} - command will be delayed until the next time where no \KPS{} linked - process will be running. - - Last, this same command will report about the location it thinks - Ghostscript can be found. Under Win32, for many programs, it is - easier to use the Ghostscript dll, and find it by using the - Ghostscript registry key than to change the \path|PATH|, which has a - limited length anyway. -\item[\Webc{}] The engines have a few more options than in Unix - \Webc{}, and one option with a different behaviour: - \begin{itemize} -%% \item the \path|-fmt| option behaves differently. Previously and -%% with the regular \Webc{} distribution, this option has 2 different -%% meanings when you are in ``ini'' or ``vir'' mode. Under Win32, it -%% has the same meaning: preload the format file specified with the -%% argument. The meaning of building a format of such name in ini -%% mode is obtained by the new \path|-job-name| option. -%% \item \path|-job-name| option: allows to set the name of the file -%% resulting from the compilation process. In normal mode, it will -%% change the base name of all files produced (\path|.dvi|, -%% \path|.aux|, etc.), while in ini mode, it will set the name of -%% the format file written. - \item \path|-halt-on-error| stop the compilation at the first error. - \item \path|-job-time| set the job time to the same timestamp as the - file given in argument. -\item \path|-oem| use the DOS codepage for console output. - \item \path|-output-directory| allow to write all the output files in the - specified directory. - \item \path|-time-statistics| print statistics about the job run - time. It is to be noted that Win9x not being a true multitasking - operating system, it has no reliable timer for short periods, so - the value printed is an approximation. Under NT/2K/XP, the result - is quite accurate with user time and system time values allocated - for this run. For Unix - users: the \path|time| command is not usually available to Windows - users. - \end{itemize} -\end{description} - -\subsection{Adding packages to your installation} - -You will find an option in the \guiseq{TeXLive} menu (or go to -\guiseq{Start\arw Programs \arw TeXLive \arw Add TeX package} menu) to -run \file{TeXSetup.exe} in maintenance mode. The steps are almost the -same as in the initial installation. - -We'll discuss differences below, but first, whatever changes you make, -\textbf{do not forget to rebuild the ls-R database files}. Otherwise, -your new files will not be found. You can do this either via the -\acro{GUI} (\guiseq{Start \arw Programs \arw TeXLive \arw Maintenance -\arw Rebuild ls-R}), or manually running the \file{mktexlsr} command. - -The main difference is in the packages selection page. In maintenance -mode, the list of installed packages is compared to the list of packages -available from your source directories. Packages that are not installed -will be displayed in green, out of date packages will be displayed in -red and up-to-date, installed packages are displayed in black. - -This way, you can choose to add or upgrade components, either from -\TeXLive{} or from the Internet, where you are likely to find some more -recent version of your packages. - -It is up to you to select which packages you want to install. The rest -of the process is similar to the first installation. - -If you want to add files that are not provided by the \TeXLive{} (or -\fpTeX{}) distribution, it is recommended to put them in the -\path|$TEXMFLOCAL| directory. This way, you will be safe against -upgrades of the \TeXLive{} software. - -The directory pointed to by \path|$TEXMFLOCAL| is initially empty. If, -for example, you want to add the support file for the Maple symbolic -computation program, you will have to put the style files in:\\ -\path|c:\Program Files\TeXLive\texmf-local\tex\latex\maple\|\\ and the -documentation files in:\\ \path|c:\Program -Files\TeXLive\texmf-local\doc\latex\maple\| - -\subsection{Uninstalling \protect\TeXLive{}} - -The uninstall procedure is available either from the \file{TeXLive.exe} -program, from the \path|TeXLive| menu or from the control panel -(\guiseq{Start \arw Control Panel, Add/Remove Programs}). This procedure -will cleanup your hard disk of most of the \TeXLive{} files. However, -\TeX{} is a system that is creating files and there is no mechanism to -keep track of all of them. Moreover, Win32 support packages have their -own uninstall procedure, which you will have to run separately (provided -you want to get rid of them). Last, the files you may have stored in -\path|$TEXMFLOCAL| won't be removed. So, even if the vast majority of -files are automatically removed by the uninstall procedure, you will -have to do some manual cleanup to actually remove all of them. - -\subsection{Running \texttt{TeXSetup.exe} from the command line} - -The \path|TeXSetup.exe| program has a number of other useful -options. You can get the list by running: -\begin{verbatim} -c:\>TeXSetup --help -\end{verbatim} - -Here is the description: -\begin{description} -\item[\path|--automatic-reboot|] reboot without waiting user - confirmation once installation is over; -\item[\path|--dry-run|] do nothing, just log everything that will be - done without this option; -\item[\path|--quick|] use the recommended installation and default - directories, ask nothing up to rebooting; -\item[\path|--with-xemtex|] selects the \XEmTeX{} bundle; -\item[\path|--net-method (=ie5/direct)|] enable to download components with - restricted licenses from the Internet (either using direct - connection of Internet Explorer 5 DLLs): you need to have an available - network connection and some of the packages are huge; -\item[\path|--remote-source-directory |] this is the base url for the remote packages; -\item[\path|--local-source-directory

|] by default, \path|TeXSetup.exe| - will guess the root directory of the set of files you want it to act on, if you ever - upgrade \path|TeXSetup.exe|, you won't be able to copy the new version - onto your \CD{}, so you will need to use this option to specify the - root of the \CD{}; -\item[\path|--installation-directory |] this is the root of your - installation, all files will be copied under this location. The - default value is \verb+c:\Program Files\TeXLive+; -\item[\path|--texmfmain-directory |] -\item[\path|--texmflocal-directory |] -\item[\path|--texmfextra-directory |] -\item[\path|--texmfhome-directory |] -\item[\path|--vartexmf-directory |] -\item[\path|--vartexfonts-directory |] these are the directories - used to configure the location of your files. They map directly to - the \path|texmf.cnf| variables. -\item[\path|--with-source-files(=yes/no)|] copy the source files - for \TeX{} packages, default value is no; -\item[\path|--with-documentation-files(=yes/no)|] copy documentation files for \TeX{} - packages. Default value is yes. Beware: this is only documentation about specific - packages, general documentation will be installed anyway; -\item[\path|--program-folder |] the name of the folder under - which you will find the menus; -\item[\path|--add-package |] this is used to add or update a specific - package after a first regular installation; -\item[\path|--scheme |] install the named scheme instead of the - default \path|texlive-recommended| scheme; -\item[\path|--maintenance|] mostly the same as \path|--add-package| - without specifying a package to add; -\item[\path|--uninstall|] this option will remove anything \TeX{} related coming from - the \CD{}, which means there can be files left if you added style - files or format files, and also that supplementary tools will not be - removed. This option is still a bit crude in this release; -\item[\path|--help|] this option opens up a box with the list of options. -\end{description} - -\subsection{Network installation} - -\KPS{} knows about UNC names, so you can use them to get your TEXMF -tree from the network. But there is better than this. -All the support files and configuration files, everything except the files in the -\path|bin/win32| are shareable with a \teTeX{} or Unix \TeXLive{} installation. That means -you can use Samba either to mount from an NT server to a Unix -workstation or the converse. Several strategies are possible: -\begin{itemize} -\item Put everything on the server. Just add each set of files for the os and -architecture you want to use in the \path|bin| directory. That means -for example \path|bin/win32| and \path|bin/i386-linux|. Next configure -your main variables. You can use UNC names to -point to the right directories under Win32. -\item Install a local copy for the binaries and format files. In this - case, assign \path|$TEXMFMAIN| to the main \path|texmf| tree that - will be accessed remotely. Set \path|$VARTEXMF| to be a local - directory which will hold local configuration files and on-the-fly - generated files. -\end{itemize} - -\subsection{Personal configurations} - -\subsubsection{Dvips} - -The configuration file for dvips can be found in\\ -\verb+C:\Program Files\TeXLive\texmf-var\dvips\config\config.ps+\\ -You may open it with any editor - %(\cmdname{WinShell} will do fine) - and change some parameters: - -\begin{description} -\item [fonts] you can change the default printer \MF{} mode or printer - resolution in case \cmdname{dvips} needs to generate PK fonts. By default it - is configured to use Type~1 versions of the CM fonts, so it should - not call \cmdname{mktexpk} too often; -\item[printer] you can tell dvips where you want to print by default. If - the \optname{o} option is not followed by a printer name, then a - \file{.ps} \PS{} file is written. You can give dvips a printer - name such as: -\begin{verbatim} -o lpt1: -% o | lpr -S server -P myprinter -% o \\server\myprinter -\end{verbatim} -\item[paper] Next, you might want - to change the paper size from European (A4) to US letter - by making the US letter the first paper size mentioned in the file. - Scroll to the group of lines beginning with \code{@}. Move - the appropriate lines so that this section begins with the lines:\\ -\hspace*{1em} @ letterSize 8.5in 11in\\ -\hspace*{1em} @ letter 8.5in 11in\\ -\hspace*{1em} @+ \%\%BeginPaperSize: Letter\\ -\hspace*{1em} @+ letter\\ -\hspace*{1em} @+ \%\%EndPaperSize -\end{description} - -The current \TeXLive{} distribution implements the procedure of making -always up-to-date fontmaps files for Dvips and Pdftex. This is done by -the \cmdname{updmap} program during installation, as well as during any -font package addition. If you add new packages by hand, edit the file -\verb+updmap.cfg+ in \path|$VARTEXMF/web2c|. - -\subsubsection{Pdftex} - -If you use the program pdf{}latex to write \acro{PDF} format directly, -and you are using \acro{US} letter-size paper, edit the file -\verb+C:\Program Files\TeXLive\texmf-var\pdftex\config\pdftex.cfg+ and -change \samp{page\_width} and \samp{page\_height}. These entries should read: -\begin{alltt} -page_width 8.5 true in -page_height 11 true in -\end{alltt} -Save the file and exit the editor. - -\subsubsection{GSView} -GSView is now distributed under the Aladdin License, and therefore is no longer included in -\TeXLive{}. - -If you may want to change the page size to US letter size. If so, open -GSView from the \guiseq{Start} menu, and select \guiseq{Media\arw Letter}. - -Also, there are menu settings that are supposed to give you the most -readable screen image. On \guiseq{Media \arw Display Settings}, set both -\optname{Text Alpha} and \optname{Graphics Alpha} to 4~bits. - -Note that the installation process has set all \code{.ps} and -\code{.eps} files to automatically open with \cmdname{GSView}. - -For printing instructions, see section~\ref{printing} below. - -\subsubsection{WinDvi} -\label{sub:windvi} - -The \file{TeXSetup.exe} program takes care of associating the files -with the \file{.dvi} extension with \file{Windvi}. - -Open it with \guiseq{Start\arw Programs\arw TeXLive\arw DVI Viewer}. - -You can set it for US letter-size paper by going to \guiseq{View\arw -Options\arw Papertype} and selecting US (8.5\verb+"+ x 11\verb+"+) (and -then \optname{OK}. Exit \cmdname{windvi}. - -You can change other parameters from there as well, such as the ability -to execute system commands specified by the document (disabled by -default for security reasons). Also, the first time you view any .dvi -file, you may find the magnification too large. Zoom out until you get -an appropriate size. - -%There are two important parameters related to printing that can't yet -%be set from the dialog boxes, namely the resolution and the \MF{} mode -%for the printer. You can set them once for all by specifying them on -%the command line: -%\begin{verbatim} -%c:\>windvi -p 360 -mfmode canonbjc foo.dvi -%\end{verbatim} -%When you will exit Windvi, these parameters will be stored in the -%configuration file. The available modes are found in this file:\\ -%\path|c:\Program Files\TeXLive\texmf\metafont\misc\modes.mf| - -All configuration settings for \cmdname{Windvi} are stored in a file -named \path|windvi.cnf| file. You can find it by running this command at -the prompt: -\begin{verbatim} -c:\>kpsewhich --expand-var $HOME/windvi.cnf -\end{verbatim} - -Should you have problems with \cmdname{Windvi}, please remove the configuration -file and test your problem against a vanilla configuration. - -\subsection{Testing} - -For generic verification procedures, see section~\ref{sec:test-install} -on p.~\pageref{sec:test-install}. This section describes -Windows-specific tests. - -Open the file \verb+sample2e.tex+ in your editor (Xemacs, WinShell), -found in \path|C:\Local\TeX\texmf\tex\latex\base|. The \LaTeX\ source -should appear on the screen. Process it by clicking on the -\guiseq{Command\arw LaTeX} menu (XEmacs) or \LaTeX\ icon on the toolbar -(WinShell), then view it by clicking on the \guiseq{Command\arw View DVI} -menu (XEmacs) or Preview (Windvi) icon (WinShell). - -At first, when you preview files with Windvi, it will create fonts because -screen fonts were not installed. After a while, you will have created most -of the fonts you use, and you will rarely see the font-creation window. - -\textbf{Hint for the future:} If a \LaTeX\ run stops because \LaTeX\ -cannot find a file, you can press Ctrl-z to quit. - - -\subsection{Printing} -\label{printing} - -It is possible to print from Windvi. In this case, printing will be done -using the Windows unified printer driver. By definition, it is -compatible with all printers. However, there is some drawback: it can -generate some huge spool files, and some (older) versions of Windows -just don't like them. The advantage is that you can use features like -embedding BMP or WMF images. You also need to make sure that the printer -parameters are correctly set (subsection~\ref{sub:windvi}), else you -will get scaled printing (printing at 600\dpi{} on a 300\dpi{} printer -will give you only one quadrant of your page). - - -Printing is faster and more reliable if you run \cmdname{dvips} to make -a \filename{.ps} file and then print from \cmdname{GSView}. In -\cmdname{GSview}, select \guiseq{File\arw Print\ldots}. A \guiseq{Print} -window will appear. - -If you are using a \PS{} printer, \textit{be sure to select -\guiseq{\PS{} Printer}}. This is done in the \guiseq{Print Method} box -at the bottom left of the \guiseq{Print} window. You can then select any -of the printers that you have previously installed. If you fail to -check the box for \optname{\PS{} Printer}, printing will not work. - -If you will be using your own non-\PS{} printer, select -\guiseq{Ghostscript device} in the \guiseq{Print Method} box, then click -on the button to the right labelled \guiseq{djet500} and select your -printer type from the list that pops up. (In the older version of -\cmdname{GSView}, make sure \optname{\PS{} Printer} is \textit{not} -selected, then select your printer type from the \guiseq{Device} list.) - -%If you use \cmdname{WinShell} and a \PS{} printer, probably the -%most convenient way to print is to add an icon to the \cmdname{WinShell} -%toolbar that invokes dvips in a way that sends the output directly to a -%default printer. For detailed instructions on how to do this, see -%the next section. - -%% \subsection{\cmdname{WinShell}} -%% \label{winshell:more} - -%% \subsubsection{Configuring \cmdname{WinShell}} -%% \label{sec:winshell} - -%% Start this program from the Start menu or from the Desktop shortcut. -%% Go to \guiseq{Options \arw Program Calls}. - -%% \begin{itemize}\itemsep 0pt -%% \item In the DVIWin tab, if the filename is \filename{yap}, replace it -%% with \filename{windvi.exe}. -%% \item In the Ghostview tab, make sure it gives the correct path for -%% gsview32.exe:\\ -%% \hspace*{1em} \verb+C:\ghostgum\gsview\gsview32.exe+ (for 3.6, the -%% current version)\\ -%% or \\ -%% \hspace*{1em} \verb+C:\gstools\gsview\gsview32.exe+ (for the older -%% version) - -%% \end{itemize} - -%% Click \guiseq{OK}. - -%% Note that the install process sets all files with the \texttt{.tex} -%% extension to open with \cmdname{WinShell}. Unless you plan to use another editor -%% (such as WinEdt or Emacs), this is appropriate. - -%% Unfortunately, \cmdname{WinShell} does not have a spell-checking -%% feature. However, if you have installed the \path|tex-extrabin| -%% collection, your installation includes \cmdname{Ispell} (a spell -%% checking program found on most Unix systems). The executable is in your -%% PATH so \verb+ispell.exe+ will be found if you invoke it from a DOS -%% window. If you installed documentation, look at \path|C:\Program -%% Files\TeXLive\texmf\doc\html\manpages\ispell.html|for information on -%% Ispell. (Otherwise, you can find \verb+ispell.html+ on the CD.) If you -%% rely on spell checking, you may want to add an Ispell icon to -%% \cmdname{WinShell}. See subsection~\ref{winshell:ispell} of this -%% document for how to do that. - -%% For an excellent commercial (but inexpensive) spelling checker, -%% see \url{http://www.microspell.com}. - -%% \cmdname{WinShell} also has on-line help, which you can access via the -%% $\textbf{\underbar{?}}$ on the menu bar. - -%% Other information about using \cmdname{WinShell} can be found in -%% section \ref{winshell:more} on p.~\pageref{winshell:more}. - - -%% \subsubsection{Installing Bug Fixes} - -%% \cmdname{WinShell}'s author (\href{mailto:idb@winshell.de}{Ingo de Boer}, -%% thanks to him) sometimes releases beta versions of the next \cmdname{WinShell} -%% version which are also bug fixes. You can grab them from -%% \url{http://www.winshell.de}. Usually they are \file{.zip} files that -%% only require to be unpacked in \cmdname{WinShell} directory (\path|c:\Program -%% Files\WinShell| by default), either using WinZip or a similar tool, or -%% by using \file{unzip} on the command line. If you got some -%% \file{winshellbugfix.zip} file and that you saved it in the \cmdname{WinShell} -%% directory, then you need to run: -%% \begin{verbatim} -%% c:\>cd c:\"Program Files"\WinShell -%% c:\>c:\local\bin\unzip winshellbugfix.zip -%% \end{verbatim} -%% Say \optname{yes} if you are asked if some files should be overwritten. The -%% \path|unzip.exe| programme can be found in the -%% \path|support/gnu-utils| package. If you -%% do not have it on your machine, you can use any archiver tool like -%% WinZip to achieve the same effect. - -%% \subsubsection{The \cmdname{Project} feature: organizing many files} - -%% If your document is split into several files (for example a thesis), -%% look into \cmdname{WinShell}'s \cmdname{Project} feature. From the -%% \guiseq{Project} menu, you give the project a name (e.g., \code{Thesis}), -%% supply the name of the main (or root) file, and then \code{add} other -%% files. These filenames display on the left of the screen where you can -%% double click the names to view and switch between them. Clicking the -%% \guiseq{\LaTeX} icon always processes the main file. - -%% Note the icons on the toolbar for toggling the project space (on the left) -%% and the log space (at the bottom). If you are not using the Project -%% feature, you may want to toggle off the space on the left, using the full -%% screen width to display your file. - -%% \subsubsection{Printing from \cmdname{WinShell} to a \PS{} Printer} -%% \label{winshell:print} - -%% The Dvips icon on the \cmdname{WinShell} toolbar puts the \PS{} output -%% in a file, which you can then view with GSView and print from there if -%% you choose. However, it's convenient to add a \cmdname{WinShell} -%% ``program call'' to dvips which sends the output directly to a -%% designated \PS{} printer. The steps below show how to do this for the -%% printer \optname{vclw}; you should substitute the name of your most -%% frequently-used printer. -%% \begin{enumerate} -%% \item Make the program aware of the printer: -%% \begin{itemize} - -%% \item Open \cmdname{WinShell}, go to \guiseq{Options\arw Program -%% Calls\arw User defined}. - -%% \item Click on \guiseq{Tool 1} in the list on the right and fill in the -%% fields to the left as follows:\vspace{-6pt} -%% \begin{quote} -%% Name: \verb+Print+\\ -%% exe file: \verb+dvips+\\ -%% cmd-line: \verb+ -D600 %m -o vclw+\\ -%% Uncheck the box for \guiseq{DVIPS first} -%% \end{quote}%\vspace{-12pt} -%% \item Click \guiseq{OK} -%% \end{itemize} -%% \item Add \guiseq{Print} to the toolbar: -%% \begin{itemize} -%% \item Go to \guiseq{Options\arw View\arw Customize}. -%% \item In the \guiseq{Category} box, select \guiseq{User-Programs}. -%% \item Select \guiseq{Print} and drag it to the toolbar, placing it just to -%% the right of the \cmdname{GSView} icon. -%% \item You then have a choice of \guiseq{Image only}, \guiseq{Text only}, -%% or \guiseq{Image and Text}. The easiest is to select \guiseq{Text only} -%% and click \guiseq{OK}. You should then see \guiseq{Print} on the -%% toolbar. (If you prefer, you can select \guiseq{Image only\arw Edit}, -%% and edit the displayed picture to your satisfaction.) -%% \end{itemize} -%% \end{enumerate} -%% Now, to print a \LaTeX\ document, just click on the \guiseq{Print} icon -%% to send to your selected printer. To use a different printer, you will -%% need to click on the \guiseq{Dvips} icon to print to a file. Then click -%% on the \cmdname{GSView} icon and use \cmdname{GSView} to send to any -%% printer you have installed on your \acro{PC}. - -%% \subsubsection{Adding Ispell to \cmdname{WinShell}} -%% \label{winshell:ispell} -%% \begin{enumerate} -%% \item Add Ispell to User Tools: -%% \begin{itemize} -%% \item Open \cmdname{WinShell}, go to \guiseq{Options\arw Program -%% Calls\arw User defined}. -%% \item In the list on the right, click on \guiseq{Tool~1} (or -%% \guiseq{Tool~2} if you have already used \guiseq{Tool~1}) and fill in -%% the fields to the left as follows:\vspace{-6pt} -%% \begin{quote} -%% Name: \verb+Ispell+\\ -%% exe file: \verb+ispell+\\ -%% cmd-line: \verb+ -t -d american %c.tex+\\ -%% Uncheck the boxes for \guiseq{LaTeX first} and \guiseq{DVIPS first} -%% \end{quote} -%% \item Click \guiseq{OK}. -%% \end{itemize} - -%% \item Add Ispell to the toolbar: -%% \begin{itemize}\itemsep 0pt -%% \item Go to \guiseq{Options\arw View\arw Customize}. -%% \item In the \guiseq{Category} box, select \guiseq{User-Programs}. -%% \item Select \guiseq{Ispell} and drag it to the toolbar, placing it just to -%% the right of the \cmdname{GSView} icon (or the last icon you added). -%% \item You then have a choice of `\guiseq{mage only}, \guiseq{Text only}, -%% or \guiseq{Image and Text}. The easiest is to select \guiseq{Text only} -%% and click \guiseq{OK}. You should then see \guiseq{Ispell} on the -%% toolbar. (If you prefer, you can select \guiseq{Image only\arw Edit}, -%% and edit the displayed picture to your satisfaction.) -%% \end{itemize} -%% \end{enumerate} -%% Now, when you have a \LaTeX\ document open, you can click on -%% \guiseq{Ispell} to perform spell checking. Ispell will open another -%% window and display the first misspelled word on the left with the -%% filename on the right. Below that you will see the context in which the -%% misspelling appears; often several suggestions for replacements are also -%% displayed. To replace the word, enter the number corresponding to the -%% desired replacement. Other possible responses are listed below; for -%% example, you can press the space bar to ignore the misspelled word. For -%% more information on Ispell, read the manual page: -%% \verb+C:\Program Files\TeXLive\texmf\doc\html\manpages\ispell.html+. - -%% Note that when you replace a word, you will not see the correction in -%% your \cmdname{WinShell} window until you close the file (click the -%% \guiseq{X} in the upper right corner) and then open it again (use the -%% \guiseq{File} menu). - -\subsection{Tips and tricks for Win32} - -\subsubsection{Different flavors of Win32} - -What we call Win32 is not an operating system by itself. It is a large -set of functions (around 12,000 in the header files of the Microsoft -\acro{SDK}) that you can use to write programs for different operating -systems of the Windows family. - -Windows comes in different flavors: -\begin{itemize} -\item Win95, Win98 and Win\acro{ME}, which \emph{are not true multitasking, - multithreading} environments. They are the latest\Dash and hopefully - last\Dash metamorphosis of \acro{DOS}. This can be more or less proven - by the fact that when booting, the PC will load the \path|command.com| - interpreter, and if you stop the boot process at this point, you can - ask for the current (\acro{DOS}) version and it will answer something - like \samp{MS-DOS 7.0} (at least for the old versions of Win9x). -\item Windows \acro{NT}, which is a new operating system written from - scratch, capable of true multitasking behaviour, and including many - high level features. -\item Windows 2000, based on \acro{NT}, with all the bells and - whistles of Win98. -\item Windows \acro{XP}, which comes with Personal and Pro flavors. This is - the last step in merging both lines of products (Win9x based and - \acro{NT} based). \acro{XP} is based on \acro{NT}. -\end{itemize} - -Win9x are able to run 32~bits programs and 16~bits programs -concurrently. But the operating system by itself is not entirely -written in 32~bits mode, and does not support memory protection: 16bits -applications can overwrite parts of the operating system memory! Some -parts of the system like the \acro{GDI} (Graphical Device Interface) -manage limited resources like bitmaps, fonts, pens and so on for the set -of all programs that run concurrently. All the bitmaps headers available -at the same time can't amount for more than 64kB. This explains the -performance tool and the fact that you can put your system on his knees -by making intensive use of graphic objects for example. - -NT, 2K and XP do not suffer from these limitations, and neither from -other Win9x limitations. They are true multitasking environments, with -protected memory. They are much more responsive than Win9x because -of better memory management, better file system and so on. - -\subsubsection{Command line prompt} - -You may wonder, ``Why would I need to use a command line prompt when -I have Windows?'' - -Good question. The problem is of very general nature. Not all operations -can be done easily using only a \acro{GUI}. Command line gives you -programming power\Dash assuming a clever command interpreter. - -But the problem here is more fundamental: \TeX{} is \emph{a batch} -tool. Not an interactive one. \TeX{} needs to compute the best -layout for each page, resolve cross-references and so on. This can be -done only by a global processing of the document. It is not (yet) a -task that can be done interactively. - -This means that you should use \TeX{} from a command line. In fact the -situation is not so bad. There is an advantage to write command line -tools for complex processing: they are better debugged, because they are -independent of any \acro{GUI} problems, and \acro{GUI} tools can be -designed to interface to the command line tools. This is the case for -\TeX{}, where you will mostly interact with it through a \acro{GUI} text -editor. - -However, you may need to use the command line prompt in a number of -situations. One is when you are having difficulties and want to debug -your setup. - -\begin{description} - \item[Win9x] You can open a command line prompt by looking either for - the \acro{MS-DOS} icon in the \guiseq{Start\arw Programs} menu, - or by choosing \guiseq{Start\arw Run} menu typing in - \path|command.com| as the progrm name. - \item[NT, 2K, XP] You can open a command line prompt by looking for - \guiseq{Command Prompt} in the \guiseq{Start\arw Accessories} menu. - You can also choose \guiseq{Start\arw Run} and type in - \path|cmd.exe|, which is the name of the brand new command - interpreter for \acro{NT} (thus, it is untrue to call this a - \emph{DOS} box!). -\end{description} - -These locations may change across different Windows versions. - - -\subsubsection{Path separators} - -The Win32 API understands both \path|/| and \path|\| characters as PATH -separators. But the command interpreters do not! So whenever a path name -is used programmatically, you can use both separators, and even mix them -up in the same path name. But on the command line, you must type -\path|\| as path separator. The reason is compatibility: the command -processor used \samp{/} to introduce arguments to commands. - -All this to say: do not be surprised to read path names written using -the Unix convention; \fpTeX{} is a port of \Webc, and aims to be compatible -across platforms. For this reason, all the configuration files that -need to specify path names use the Unix convention. - -\subsubsection{File systems} -\label{sec:clusters} - -The worst feature of Win9x with regard to \TeX{} is probably the -so-called FAT file system. \TeX{} uses many many small files, with size -around 1--3kB. The \acro{FAT} file system is old, and predates by -decades the multi-gigabytes hard disks we have today. As a result, it -cannot manage efficiently the tens of thousands of \TeX{} files found in -\TeXLive{}. The \acro{FAT} file system allocates a minimum of 32kB for -\emph{any} file on a huge partition. It means that \TeX{} will use much -more disk space than it actually needs. - -The other, more modern, file systems available, \acro{FAT32} and -\acro{NTFS}, do not have this drawback. They manage clusters of 4kB -only. (You can lower the limit to 512 bytes on \acro{NTFS}.) - -\subsubsection{How to add some directory to your PATH} - -There are pairs of variables and values which behave much like global -variables inside your programs. The set of those variables is called the -environment. Each program is initialized with a copy of the -environment when it is run. It can request and change the -value of any variable. The changes happen in the copy of the -environment, and is not at all propagated to the other running -programs. - -Your PATH is a special environment variable used to search for -programs you want to run. -There is a different procedure to change it for Win9x, WinME and NT/2K/XP: - -\begin{description} -\item[Windows 95/98] Edit your \path|autoexec.bat|. In this file should be a line - starting with \texttt{PATH=} and followed by a list of directories separated - by \path|;|. Please add the directory with the executables in this line. - After this, this line could look as follows: -\begin{verbatim} -PATH=c:\windows;c:\windows\system;c:\"Program Files"\TeXLive\bin\win32 -\end{verbatim} -\item[Windows ME] You need to run the special program - \path|c:\windows\system\msconfig.exe| to be able to change any - environment variable. From this program, select the `Environment' - tab, and then add or modify the variable you want. You will be asked to reboot the - machine upon any change. -\item[Windows NT/2K/XP] - Click left on \guiseq{Start \arw Settings \arw Control Panel}. Now the - window with the control panel icons opens. Double click on System. The - System Properties window opens. Click on the tab \textsf{Environment} - or look for a button named \guiseq{Environment Variables} among the - dialog boxes. Now you can change the environment variables for your - user account. Note: There are also displayed the environment settings - for the system. Normally, you can't change the system variables - unless you have administrator rights on your machine. If you want to - change the \texttt{PATH} for all users, you will have to contact your - system administrator or be the system administrator yourself\Dash in - the latter case you should know what you are doing. - - If there is already a \texttt{PATH} setting for your user account, - left click on \texttt{PATH}. In the field \textsf{Variable} appears - \texttt{PATH} while the field Value shows the current setting of - \texttt{PATH} as a list of directories separated by \path|;|. Add - the directory where the executables are located (e.g. - \path|c:\Program Files\TeXLive\bin\win32|). If there isn't a \texttt{PATH} variable - for your user account, simply click in the field Variable and type - in \texttt{PATH}, click in the field \textsf{Value} - and type in the directory with the executables. Important: Click on - the \textsf{Apply} button before clicking \textsf{Ok}, otherwise the - changes to \texttt{PATH} won't apply to your system. Be careful when - changing the environment settings. -\end{description} - -The best way to be sure that a variable has been properly set is to -open a console and type: -\begin{verbatim} -set VARIABLE -\end{verbatim} -which should return the corresponding value. - -\subsubsection{\TeX{} engines} - -If you have a look at the \Webc{} documentation, you will read that all -the various \TeX{} derived programs use the same base engine. For -example, \path|tex.exe| and \path|latex.exe| are exact copies of the -same program, but each one will use a different format file, based on -its calling name. - -Under Unix, this feature is implemented through \emph{symbolic -links}. It saves up a bit of disk space, because some engines are -used with many different format files. - -The Win32 API does not know about file links. So to save up almost -the same amount of memory, all the \TeX{} base engines have been put -in DLLs (\emph{Dynamic Linked Library}). This means that you will have -the following layout: -\begin{alltt} -13/05/2002 17:06 3 584 latex.exe -13/05/2002 17:06 266 240 tex.dll -13/05/2002 17:06 3 584 tex.exe -\end{alltt} -and the \path|latex.exe| file is nothing but a rough copy of -\path|tex.exe| using the same core \path|tex.dll|. -The same trick has been used for the \path|mktex*.exe| family of programs which are -linked to the \path|mktex.dll| library. - -In fact, a generic tool called \path|lnexe.exe| is provided to build the -equivalent of Unix hard links for executable files only under Win32. - -\subsection{In case of problems} -\label{sec:troubleshooting} - -\subsubsection{What to do if \texttt{latex} does not find your files?} - -\begin{itemize} - -\item \cmdname{kpsewhich} is the tool of choice to debug any -problem. Unfortunately, \cmdname{kpsewhich} outputs debug information -to stderr, and the Windows console does not know how to redirect stderr -to a file\footnote{Well, NT and Win2k consoles know how to do that. But -the trick will work for any console.}. For diagnostic purposes you can -temporarily set an environment variable (in a \acro{DOS} box): - -\begin{verbatim} -SET KPATHSEA_DEBUG_OUTPUT=err.log -\end{verbatim} -You can also set the debug level: -\begin{verbatim} -SET KPATHSEA_DEBUG=-1 -\end{verbatim} - -If you want to redirect stderr to stdout, which is not possible -Windows, then do: -\begin{verbatim} -SET KPATHSEA_DEBUG_OUTPUT=con: -\end{verbatim} -This way you can capture both stdout and stderr in the same file. - -\item Assuming the installation has been done in \path|c:/Program Files/TeXLive|, check - the following values: \\ - {\small - \begin{tabular}{ll} - \path|kpsewhich -expand-path $SELFAUTOPARENT| & \path|c:/Program Files/TeXLive| \\ - \path|kpsewhich -expand-path $TEXMF| & \path|c:/Program Files/TeXLive/texmf| \\ - \path|kpsewhich -expand-path $TEXMFCNF| & - \path|.;c:/Program Files/TeXLive/texmf/web2c;| \\ - & \path|c:/Program Files/TeXLive/bin/win32;| \\ - & \path|c:/Program Files/TeXLive/bin;| \\ - & \path|c:/Program Files/TeXLive| \\ - \path|kpsewhich -expand-var $TEXINPUTS| & \path|.;c:/Program Files/TeXLive/texmf/tex//| - \end{tabular} -} -\item If you have other \TeX{}-related values already set in your - environment, please, remove them. They are overriding the ones in - texmf.cnf. -\item Check the values from:\\ -{\small - \begin{tabular}{ll} - \texttt{kpsewhich cmr10.tfm} & \path|c:/Program Files/TeXLive/texmf/fonts/tfm/public/cm/cmr10.tfm|\\ - \texttt{kpsewhich latex.fmt}& \path|c:/Program Files/TeXLive/texmf/web2c/latex.fmt| - \end{tabular} -} -\item At this point, if everything is correct, \TeX{} and friends - should work. If it is not the case, you will need to play with - the \path|-debug=n| option from \path|kpsewhich|, and check back all - the values. Try to identify and report the problem. -\end{itemize} - -\subsubsection{What to do if your setup still does not work as expected?} - -Here are several questions to investigate: - -\begin{enumerate} -\item Is \file{tex.exe} in my \path|PATH|? - -\item Is the \path|TEXMFCNF| variable correctly set to -\path|c:/Program Files/TeXLive/texmf-var/web2c| (default value)? - -\item Are there any errors in the log file generated by the -\file{TeXSetup.exe} program? You can find this by searching for the -string \samp{Error}. - -\item Are there any relevant bug fixes at \url{http://tug.org/texlive/}? -(Unlikely, but it doesn't hurt to check.) - -\item Check the web pages at -\url{http://www.fptex.org/}, or consider subscribing to the \fpTeX{} -mailing list, via \url{http://tug.org/mailman/listinfo/fptex}. - -\end{enumerate} - - -The \TeXLive{} software consists of hundreds and programs and tens of -thousands of files, all from varying sources. So it is quite difficult to -predict all possible causes for problems. Nevertheless, we will do our -best to help you. (see section~\ref{sec:help} on p.~\pageref{sec:help}.) - - -\subsection{Compiling the source files} - -You have the whole set of source files, in the -\path|source/source.tar.bz2| archive available in the distribution together with -a patch file for Win32. To -be able to compile the whole distribution for Windows, you will need: - -\begin{itemize} -\item Windows 2K/XP -\item Microsoft Visual Studio .Net 2003 -\item a set of Unix tools (\texttt{sed}, - \texttt{grep}, \texttt{gawk}, etc.) and also Perl, Flex and Bison, -\item to adjust the paths in the - \path|win32/make/common.mak| file according to your installation -\item to adjust the paths in the Perl script file - \path|win32/perl/build.pl|, -\item run the compilation from the \path|mswin32/| directory using this - command: -\begin{verbatim} -c:\texlive\source\mswin32>perl ./perl/build.pl --install --log=install.log -\end{verbatim} -\end{itemize} - -There is a lot of work to do to make this process easier and cleaner. - -\subsection{Where to get more information} - -The Windows \TeX{} system included on \TeXLive{} is also known as -\fpTeX. The packaging differs, but \fpTeX{} is no more no less than the -current \TeXLive\ release for Windows. - -The \fpTeX{} home page is \url{http://www.fptex.org}. - -The current \fpTeX release is available from any \CTAN site in -\url{htp://www.ctan.org/tex-archive/systems/win32/fptex}. - -The main ftp site for \fpTeX\ is \url{ftp://ftp.dante.de/pub/fptex/} -from where beta versions of \fpTeX\ and additionnal tools are available. -This main site is (partially) mirrored daily by all \CTAN{} sites at -\path|systems/win32/fptex|. - -The \TeX{} Users Group is kindly hosting a mailing list dedicated to -\fpTeX. It is used for announcements, bug reports, enhancement requests, -and general discussion about \fpTeX. To subscribe, visit -\url{http://tug.org/mailman/listinfo/fptex}. The mailing list -address is \email{fptex@tug.org}. - - -\section{A user's guide to \protect\Webc{}} - -\Webc{} is an integrated collection of \TeX-related programs: \TeX{} -itself, \MF{}, \MP, \BibTeX{}, etc. It is the heart of \TeXLive{}. - -A bit of history: The original implementation was by Tomas Rokicki who, -in 1987, developed a first \TeX{}-to-C system adapting change files -under Unix, which were primarily the work of Howard Trickey and Pavel -Curtis. Tim Morgan became the maintainer of the system, and during this -period the name changed to Web-to-C\@. In 1990, Karl Berry took over -the work, assisted by dozens of additional contributors, and in 1997 he -handed the baton to Olaf Weber. - -The \Webc{} system runs on Unix, 32-bit Windows systems, \MacOSX{}, and -other operating systems. It uses Knuth's original sources for \TeX{} and -other basic programs written in \web{} and translates them into C source -code. The core \TeX{} programs are: - -\begin{cmddescription} -\item[bibtex] Maintaining bibliographies. -\item[dmp] \cmdname{troff} to MPX (\MP{} pictures). -\item[dvicopy] Expands virtual font references in \dvi{} files. -\item[dvitomp] \dvi{} to MPX (MetaPost pictures). -\item[dvitype] \dvi{} to human-readable text. -\item[gftodvi] Generic font proofsheets. -\item[gftopk] Generic to packed fonts. -\item[gftype] GF to human-readable text. -\item[makempx] \MP{} label typesetting. -\item[mf] Creating typeface families. -\item[mft] Prettyprinting \MF{} source. -\item[mpost] Creating technical diagrams. -\item[mpto] MetaPost label extraction. -\item[newer] Compare modification times. -\item[patgen] Creating hyphenation patterns. -\item[pktogf] Packed to generic fonts. -\item[pktype] PK to human-readable text. -\item[pltotf] Plain text property list to TFM. -\item[pooltype] Display \web{} pool files. -\item[tangle] \web{} to Pascal. -\item[tex] Typesetting. -\item[tftopl] TFM to plain text property list. -\item[vftovp] Virtual font to virtual property list. -\item[vptovf] Virtual property list to virtual font. -\item[weave] \web{} to \TeX. -\end{cmddescription} - -\noindent The precise functions and syntax of these programs are -described in the documentation of the individual packages and of \Webc{} -itself. However, knowing a few principles governing the whole family of -programs will help you take advantage of your \Webc{} installation. - -All programs honor these standard \acro{GNU} options: -\begin{ttdescription} -\item[-{}-help] print basic usage summary. -\item[-{}-verbose] print detailed progress report. -\item[-{}-version] print version information, then exit. -\end{ttdescription} - -For locating files the \Webc{} programs use the path searching library -\KPS{}. This library uses a combination of environment variables and a -configuration files to optimize searching the (huge) collection of -\TeX{} files. \Webc{} can look at more than one directory tree -simultaneously, which is useful in maintaining \TeX's standard -distribution and local extensions in two distinct trees. To speed up -file searches the root of each tree has a file \file{ls-R}, containing -an entry showing the name and relative pathname for all files under that -root. - -\subsection{\protect\KPS\ path searching} - -Let us first describe the generic path searching mechanism of the \KPS{} -library. - -We call a \emph{search path} a colon- or semicolon\hyph sepa\-rated list -of \emph{path elements}, which are basically directory names. A -search path can come from (a combination of) many sources. To look up -a file \samp{my-file} along a path \samp{.:/dir}, \KPS{} checks each -element of the path in turn: first \file{./my-file}, then -\file{/dir/my-file}, returning the first match (or possibly all -matches). - -In order to adapt optimally to all operating systems' conventions, on -non-Unix systems \KPS{} can use filename separators different from -colon (\samp{:}) and slash (\samp{/}). - -To check a particular path element \var{p}, \KPS{} first checks if a -prebuilt database (see ``Filename data\-base'' on -page~\pageref{Filename-database}) applies to \var{p}, i.e., if the database -is in a directory that is a prefix of \var{p}. If so, the path -specification is matched against the contents of the database. - -If the database does not exist, or does not apply to this path -element, or contains no matches, the filesystem is searched (if this -was not forbidden by a specification starting with \samp{!!}\ and if -the file being searched for must exist). \KPS{} constructs the list -of directories that correspond to this path element, and then checks -in each for the file being sought. - -The ``file must exist'' condition comes into play with \samp{.vf} files and -input files read by \TeX's \cs{openin} command. Such files may not -exist (e.g., \file{cmr10.vf}), and so it would be wrong to search the -disk for them. Therefore, if you fail to update \file{ls-R} when you -install a new \samp{.vf} file, it will never be found. -Each path element is checked in turn: first the database, then the -disk. If a match is found, the search stops and the result is -returned. - -Although the simplest and most common path element is a directory -name, \KPS{} supports additional features in search paths: layered -default values, environment variable names, config file values, users' -home directories, and recursive subdirectory searching. Thus, we say -that \KPS{} \emph{expands} a path element, meaning it transforms all -the specifications into basic directory name or names. This is -described in the following sections in the same order as it takes -place. - -Note that if the filename being searched for is absolute or explicitly -relative, i.e., starts with \samp{/} or \samp{./} or \samp{../}, -\KPS{} simply checks if that file exists. - -\ifSingleColumn -\else -\begin{figure*} -\verbatiminput{../examples/ex5.tex} -\setlength{\abovecaptionskip}{0pt} - \caption{An illustrative configuration file sample} - \label{fig:config-sample} -\end{figure*} -\fi - -\subsubsection{Path sources} -\label{Path-sources} - -A search path can come from many sources. In the order in which -\KPS{} uses them: - -\begin{enumerate} -\item - A user-set environment variable, for instance, \envname{TEXINPUTS}\@. - Environment variables with a period and a program name appended - override; e.g., if \samp{latex} is the name of the program being run, - then \envname{TEXINPUTS.latex} will override \envname{TEXINPUTS}. -\item - A program-specific configuration file, for exam\-ple, a line - \samp{S /a:/b} in \cmdname{dvips}'s \file{config.ps}. -\item A \KPS{} configuration file \file{texmf.cnf}, containing a line like - \samp{TEXINPUTS=/c:/d} (see below). -\item The compile-time default. -\end{enumerate} -\noindent You can see each of these values for a given -search path by using the debugging options (see ``Debugging actions'' -on page~\pageref{Debugging}). - -\subsubsection{Config files} - -\begingroup\tolerance=3500 -\KPS{} reads \emph{runtime configuration files} named \file{texmf.cnf} -for search path and other definitions. The search path used to look -for these files is named \envname{TEXMFCNF} (by default such a file lives -in the \file{texmf/web2c} subdirectory). \emph{All} -\file{texmf.cnf} files in the search path will be read and definitions -in earlier files override those in later files. Thus, with a search -path of \verb|.:$TEXMF|, values from \file{./texmf.cnf} override those -from \verb|$TEXMF/texmf.cnf|. -\endgroup - -\begin{itemize} -\item - Comments start with \code{\%} and continue to the end of the line. -\item - Blank lines are ignored. -\item - A \bs{} at the end of a line acts as a continuation character, - i.e., the next line is appended. Whitespace at the beginning of - continuation lines is not ignored. -\item - Each remaining line has the form: -\begin{alltt} - \emph{variable}[.\emph{progname}] [=] \emph{value} -\end{alltt}% - where the \samp{=} and surrounding whitespace are optional. -\item - The \ttvar{variable} name may contain any character other - than whitespace, \samp{=}, or \samp{.}, but sticking to - \samp{A-Za-z\_} is safest. -\item - If \samp{.\var{progname}} is present, the definition only - applies if the program that is running is named - \texttt{\var{progname}} or \texttt{\var{progname}.exe}. This allows - different flavors of \TeX{} to have different search paths, for - example. -\item \var{value} may contain any characters except - \code{\%} and \samp{@}. The - \code{\$\var{var}.\var{prog}} feature is not available on the - right-hand side; instead, you must use an additional variable. A - \samp{;}\ in \var{value} is translated to \samp{:}\ if - running under Unix; this is useful to be able to have a single - \file{texmf.cnf} for Unix, \acro{MS-DOS} and Windows systems. -\item - All definitions are read before anything is expanded, so - variables can be referenced before they are defined. -\end{itemize} -A configuration file fragment illustrating most of these points is -\ifSingleColumn -shown below: - -\verbatiminput{../examples/ex5.tex} -\else -shown in Figure~\ref{fig:config-sample}. -\fi - -\subsubsection{Path expansion} -\label{Path-expansion} - - -\KPS{} recognizes certain special characters and constructions in -search paths, similar to those available in Unix shells. As a -general example, the complex path, -\verb+~$USER/{foo,bar}//baz+, expands to all subdirectories under -directories \file{foo} and \file{bar} in \texttt{\$USER}'s home -directory that contain a directory or file \file{baz}. These -expansions are explained in the sections below. -%$ -\subsubsection{Default expansion} -\label{Default-expansion} - -\tolerance=2500 -If the highest-priority search path (see ``Path sources'' on -page~\pageref{Path-sources}) contains an \emph{extra colon} (i.e., -leading, trailing, or doubled), \KPS{} inserts at that point the -next-highest-prio\-rity search path that is defined. If that inserted -path has an extra colon, the same happens with the next highest. For -example, given an environment variable setting - -\tolerance=1500 - -\begin{alltt} -> \Ucom{setenv TEXINPUTS /home/karl:} -\end{alltt} -and a \code{TEXINPUTS} value from \file{texmf.cnf} of - -\begin{alltt} - .:\$TEXMF//tex -\end{alltt} -then the final value used for searching will be: - -\begin{alltt} - /home/karl:.:\$TEXMF//tex -\end{alltt} - -Since it would be useless to insert the default value in more than one -place, \KPS{} changes only one extra \samp{:}\ and leaves any others in -place: it checks first for a leading \samp{:}, then a trailing -\samp{:}, then a doubled \samp{:}. - -\subsubsection{Brace expansion} - -A useful feature is brace expansion, which means that, for instance, -\verb+v{a,b}w+ expands to \verb+vaw:vbw+. Nesting is allowed. -This can be used to implement multiple \TeX{} hierarchies, by -assigning a brace list to \code{\$TEXMF}. -For example, in \file{texmf.cnf}, you find -the following definition: -\begin{verbatim} - TEXMF = {$HOMETEXMF,$TEXMFLOCAL,!!$VARTEXMF,!!$TEXMFMAIN} -\end{verbatim} -Using this you can then write something like -\begin{verbatim} - TEXINPUTS = .;$TEXMF/tex// -\end{verbatim} -%$ -which means that, after looking in the current directory, the -\code{\$HOMETEXMF/tex}, \code{\$TEXMFLOCAL/tex}, \code{\$VARTEXMF/tex} -and \code{\$TEXMFMAIN/tex} trees \emph{only}) will be searched (the -last two use using \file{ls-R} data base files). It is a convenient -way for running two parallel \TeX{} structures, one ``frozen'' (on a -\CD, for instance) and the other being continuously updated with new -versions as they become available. By using the \code{\$TEXMF} -variable in all definitions, one is sure to always search the -up-to-date tree first. - -\subsubsection{Subdirectory expansion} -\label{Subdirectory-expansion} - -Two or more consecutive slashes in a path element following a directory -\var{d} is replaced by all subdirectories of \var{d}: first those -subdirectories directly under \var{d}, then the subsubdirectories under -those, and so on. At each level, the order in which the directories are -searched is \emph{unspecified}. - -If you specify any filename components after the \samp{//}, only -subdirectories with matching components are included. For example, -\samp{/a//b} expands into directories \file{/a/1/b}, \file{/a/2/b}, -\file{/a/1/1/b}, and so on, but not \file{/a/b/c} or \file{/a/1}. - -Multiple \samp{//} constructs in a path are possible, but -\samp{//} at the beginning of a path is ignored. - -\subsubsection{List of special characters and their meaning: a summary} - -The following list summarises the meaning of special characters -in \KPS{} configuration files. - -\newcommand{\CODE}[1]{\makebox[2.5em][l]{\code{#1}}} -\begin{ttdescription} -\item[\CODE{:}] Separator in path specification; at the beginning or - the end of a path it substitutes the default path expansion. -\item[\CODE{;}] Separator on non-Unix systems (acts like \code{:}). -\item[\CODE{\$}] Variable expansion. -\item[\CODE{\string~}] Represents the user's home directory. -\item[\CODE{\char`\{\dots\char`\}}] Brace expansion. -\item[\CODE{//}] Subdirectory expansion (can occur anywhere in - a path, except at its beginning). -\item[\CODE{\%}] Start of comment. -\item[\CODE{\bs}] Continuation character (allows multi-line entries). -\item[\CODE{!!}] Search \emph{only} database to locate file, \emph{do - not} search the disk. -\end{ttdescription} - - -\subsection{Filename databases} -\label{Filename-database} - -\KPS{} goes to some lengths to minimize disk accesses for searches. -Nevertheless, at installations with enough directories, searching each -possible directory for a given file can take an excessively long time -(this is especially true if many hundreds of font directories have to -be traversed.) Therefore, \KPS{} can use an externally-built plain text -``database'' file named \file{ls-R} that maps files to directories, -thus avoiding the need to exhaustively search the disk. - -A second database file \file{aliases} allows you to give additional -names to the files listed in \file{ls-R}. This can be helpful to -confirm to \acro{DOS} 8.3 filename conventions in source files. - -\subsubsection{The filename database} -\label{ls-R} - -As explained above, the name of the main filename database must be -\file{ls-R}. You can put one at the root of each \TeX{} hierarchy in -your installation that you wish to be searched (\code{\$TEXMF} by -default); most sites have only one hierarchy. \KPS{} looks for -\file{ls-R} files along the \code{TEXMFDBS} path. - -The recommended way to create and maintain \samp{ls-R} is to run the -\code{mktexlsr} script included with the distribution. It is invoked -by the various \samp{mktex}\dots\ scripts. In principle, this script -just runs the command -\begin{alltt} -cd \var{/your/texmf/root} && ls -LAR ./ >ls-R -\end{alltt} -presuming your system's \code{ls} produces the right output format -(\acro{GNU}'s \code{ls} is all right). To ensure that the database is always -up-to-date, it is easiest to rebuild it regularly via \code{cron}, so -that for changes in the installed files\Dash perhaps after installing or -updating a \LaTeX{} package\Dash the file \file{ls-R} is automatically -updated. - -If a file is not found in the database, by default \KPS{} goes ahead -and searches the disk. If a particular path element begins with -\samp{!!}, however, \emph{only} the database will be searched for that -element, never the disk. - - -\subsubsection{kpsewhich: Standalone path searching} -\label{Invoking-kpsewhich} - -The \texttt{kpsewhich} program exercises path searching independent of any -particular application. This can be useful as a sort of \code{find} -program to locate files in \TeX{} hierarchies (this is used heavily in -the distributed \samp{mktex}\dots\ scripts). - -\begin{alltt} -> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} -\end{alltt} -The options specified in \ttvar{option} start with either \samp{-} -or \samp{-{}-}, and any unambiguous abbreviation is accepted. - -\KPS{} looks up each non-option argument on the command line as a -filename, and returns the first file found. There is no option to -return all the files with a particular name (you can run the Unix -\samp{find} utility for that). - -The more important options are described next. - -\begin{ttdescription} -\item[\texttt{-{}-dpi=\var{num}}]\mbox{} - Set the resolution to \ttvar{num}; this only affects \samp{gf} - and \samp{pk} lookups. \samp{-D} is a synonym, for compatibility - with \cmdname{dvips}. Default is 600. - -\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ - Set the format for lookup to \ttvar{name}. By default, the - format is guessed from the filename. For formats which do not have - an associated unambiguous suffix, such as \MP{} support files and - \cmdname{dvips} configuration files, you have to specify the name as - found in the first column of Table~\ref{tab:kpathsea}, which lists - currently recognized names, a description, possible file extensions, - and associated environment variables. -\end{ttdescription} - - -\def\KpathKey#1#2#3#4#5{% name, number, description, variables, - % suffixes -\SetRowColor#1 & #3 & #4 & #5\\} -\def\HEAD#1{\multicolumn{1}{l}{\emph{#1}}} -% -\begin{small} -% a footnoterule immediately under a bottom-of-page rule looks dead -% silly, so we suppress it -\renewcommand\footnoterule{\relax} -% -\begin{longtable}{@{}% - >{\ttfamily}P{.16\textwidth}% Col.1 - P{.3\textwidth}% Col 2 - >{\ttfamily\footnotesize}P{.29\textwidth}% Col 3 - >{\ttfamily}P{.14\textwidth}% Col 4 -@{}} -\caption{Kpathsea file types.}\label{tab:kpathsea}\\ -\emph{Name} & \HEAD{Description} & \HEAD{Variables} -& \HEAD{Suffixes}\\ -\hline -\endfirsthead -\multicolumn{3}{l}{Kpathsea file types \emph{continued}}\\ -\emph{Name} & \HEAD{Description} & \HEAD{Variables} -& \HEAD{Suffixes}\\ -\hline -\noalign{\vspace{2pt}} -\endhead -\mbox{}\\ -\hline -\endfoot -\KpathKey - {afm} - {4} - {Adobe font metrics} - {AFMFONTS} - {.afm} -\KpathKey - {base} - {5} - {Metafont memory dump} - {MFBASES, TEXMFINI} - {.base} -\KpathKey - {bib} - {6} - {\BibTeX{} bibliography source} - {BIBINPUTS, TEXBIB} - {.bib} -\KpathKey - {} - {2} - {bitmap fonts} - {GLYPHFONTS, TEXFONTS} - {} -\KpathKey - {bst} - {7} - {\BibTeX{} style files} - {BSTINPUTS} - {.bst} -\KpathKey - {cnf} - {8} - {Runtime configuration files} - {TEXMFCNF} - {.cnf} -\KpathKey - {dvips config} - {34} - {\textsf{dvips} configuration files, e.g., \file{config.ps} - and \file{psfonts.map}} - {TEXCONFIG} - {.map} -\KpathKey - {fmt} - {10} - {\TeX{} memory dump} - {TEXFORMATS, TEXMFINI} - {.fmt, .efmt, .efm} -\KpathKey - {gf} - {0} - {generic font bitmap} - {GFFONTS} - {.gf} -\KpathKey - {graphic/figure} - {25} - {Encapsulated \PS{} figures} - {TEXPICTS, TEXINPUTS} - {.eps, .epsi} -\KpathKey - {ist} - {35} - {\textsf{makeindex} style files} - {TEXINDEXSTYLE, INDEXSTYLE} - {.ist} -\KpathKey - {ls-R} - {9} - {Filename databases} - {TEXMFDBS} - {} -\KpathKey - {map} - {11} - {Fontmaps} - {TEXFONTMAPS} - {.map} -\KpathKey - {mem} - {12} - {MetaPost memory dump} - {MPMEMS, TEXMFINI} - {.mem} -\KpathKey - {mf} - {13} - {Metafont source} - {MFINPUTS} - {.mf} -\KpathKey - {mfpool} - {14} - {Metafont program strings} - {MFPOOL, TEXMFINI} - {.pool} -\KpathKey - {mft} - {15} - {MFT style file} - {MFTINPUTS} - {.mft} -\KpathKey - {} - {41} - {miscellaneous fonts} - {MISCFONTS} - {} -\KpathKey - {mp} - {16} - {MetaPost source} - {MPINPUTS} - {.mp} -\KpathKey - {mppool} - {17} - {MetaPost program strings} - {MPPOOL, TEXMFINI} - {.pool} -\KpathKey - {MetaPost support} - {18} - {MetaPost support files, used by DMP} - {MPSUPPORT} - {} -\KpathKey - {ocp} - {19} - {\OMEGA{} compiled process files} - {OCPINPUTS} - {.ocp} -\KpathKey - {ofm} - {20} - {\OMEGA{} font metrics} - {OFMFONTS, TEXFONTS} - {.ofm, .tfm} -\KpathKey - {opl} - {21} - {\OMEGA{} property lists} - {OPLFONTS, TEXFONTS} - {.opl} -\KpathKey - {otp} - {22} - {\OMEGA{} translation process files} - {OTPINPUTS} - {.otp} -\KpathKey - {ovf} - {23} - {\OMEGA{} virtual fonts} - {OVFFONTS, TEXFONTS} - {.ovf} -\KpathKey - {ovp} - {24} - {\OMEGA{} virtual property lists} - {OVPFONTS, TEXFONTS} - {.ovp} -\KpathKey - {pk} - {1} - {packed bitmap fonts} - {\emph{program}FONTS \textrm{(\texttt{\emph{program}} being - \textsmaller{\cmdname{XDVI}}, - etc.)}, PKFONTS, TEXPKS, GLYPHFONTS, TEXFONTS} - {.pk} -\KpathKey - {\PS{} header} - {30} - {downloadable \PS{}} - {TEXPSHEADERS, PSHEADERS} - {.pro, .enc} -\KpathKey - {tex} - {26} - {\TeX{} source} - {TEXINPUTS} - {.tex, .cls, .sty, .clo, .def} -\KpathKey - {TeX system documentation} - {27} - {Documentation files for the \TeX{} system} - {TEXDOCS} - {} -\KpathKey - {TeX system sources} - {29} - {Source files for the \TeX{} system} - {TEXSOURCES} - {} -\KpathKey - {texpool} - {28} - {\TeX{} program strings} - {TEXPOOL, TEXMFINI} - {.pool} -\KpathKey - {tfm} - {3} - {\TeX{} font metrics} - {TFMFONTS, TEXFONTS} - {.tfm} -\KpathKey - {Troff fonts} - {31} - {Troff fonts, used by DMP} - {TRFONTS} - {} -\KpathKey - {truetype fonts} - {36} - {TrueType outline fonts} - {TTFONTS} - {.ttf, .ttc} -\KpathKey - {Type~1 fonts} - {32} - {Type 1 \PS{} outline fonts} - {T1FONTS, T1INPUTS, TEXPSHEADERS, DVIPSHEADERS} - {.pfa, .pfb} -\KpathKey - {type42 fonts} - {37} - {Type 42 \PS{} outline fonts} - {T42FONTS} - {} -\KpathKey - {vf} - {33} - {virtual fonts} - {VFFONTS, TEXFONTS} - {.vf} -\KpathKey - {web2c files} - {38} - {\Webc{} support files} - {WEB2C} - {} -\KpathKey - {other text files} - {39} - {text files used by `\textsf{foo}'} - {FOOINPUTS} - {} -\KpathKey - {other binary files} - {40} - {binary files used by `\textsf{foo}'} - {FOOINPUTS} - {} -\end{longtable} -\end{small} - - -\begin{multicols}{2} - - The last two entries in Table~\ref{tab:kpathsea} are special - cases, where the paths and environment variables depend on the name - of the program: the variable name is constructed by converting the - program name to upper case, and then appending \texttt{INPUTS}. - - The environment variables are set by default in the configuration - file \file{texmf.cnf}. It is only when you want to override one or - more of the values specified in that file that you might want to set - them explicitly in your execution environment. - - The \samp{-{}-format} and \samp{-{}-path} options are mutually - exclusive. - -\begin{ttdescription} - -\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ - Set the mode name to \ttvar{string}; this only affects \samp{gf} - and \samp{pk} lookups. No default: any mode will be found. -\item[\texttt{-{}-must-exist}]\mbox{}\\ - Do everything possible to find the files, notably including - searching the disk. By default, only the \file{ls-R} database is - checked, in the interest of efficiency. -\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ - Search along the path \ttvar{string} (colon-separated as usual), - instead of guessing the search path from the filename. \samp{//} and - all the usual expansions are supported. The options \samp{-{}-path} - and \samp{-{}-format} are mutually exclusive. -\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ - Set the program name to \texttt{\var{name}}. - This can affect the search paths via the \texttt{.\var{progname}} - feature. - The default is \cmdname{kpsewhich}. -\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ - shows the path used for file lookups of file type \texttt{\var{name}}. - Either a filename extension (\code{.pk}, \code{.vf}, etc.) or a - name can be used, just as with \samp{-{}-format} option. -\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ - sets the debugging options to \texttt{\var{num}}. -\end{ttdescription} - - -\subsubsection{Examples of use} -\label{SExamplesofuse} - -Let us now have a look at \KPS{} in action. Here's a straightforward search: - -\begin{alltt} -> \Ucom{kpsewhich article.cls} -/usr/local/texmf/tex/latex/base/article.cls -\end{alltt} -We are looking for the file \file{article.cls}. Since the \samp{.cls} -suffix is unambiguous we do not need to specify that we want to look for a -file of type \optname{tex} (\TeX{} source file directories). We find it in -the subdirectory \file{tex/latex/base} below the \samp{TEXMF} root -directory. Similarly, all of the following are found without problems -thanks to their unambiguous suffix. -\begin{alltt} -> \Ucom{kpsewhich array.sty} - /usr/local/texmf/tex/latex/tools/array.sty -> \Ucom{kpsewhich latin1.def} - /usr/local/texmf/tex/latex/base/latin1.def -> \Ucom{kpsewhich size10.clo} - /usr/local/texmf/tex/latex/base/size10.clo -> \Ucom{kpsewhich small2e.tex} - /usr/local/texmf/tex/latex/base/small2e.tex -> \Ucom{kpsewhich tugboat.bib} - /usr/local/texmf/bibtex/bib/beebe/tugboat.bib -\end{alltt} - -The latter is a \BibTeX{} bibliography database for \textsl{TUGBoat} articles. - -\begin{alltt} -> \Ucom{kpsewhich cmr10.pk} -\end{alltt} -Font bitmap glyph files of type \file{.pk} are used by display -programs like \cmdname{dvips} and \cmdname{xdvi}. Nothing is returned in -this case since there are no pre-generated Computer Modern \samp{.pk} -files on our system (since we use the Type~1 versions included in \TeXLive{}). -\begin{alltt} -> \Ucom{kpsewhich ecrm1000.pk} -\ifSingleColumn /usr/local/texmf/fonts/pk/ljfour/jknappen/ec/ecrm1000.600pk -\else -/usr/local/texmf/fonts/pk/ljfour/jknappen/ -... ec/ecrm1000.600pk -\fi\end{alltt} -For the extended Computer Modern files we had to generate \samp{.pk} -files, and since the default \MF{} mode on our installation is -\texttt{ljfour} with a base resolution of 600\dpi{} (dots per inch), -this instantiation is returned. -\begin{alltt} -> \Ucom{kpsewhich -dpi=300 ecrm1000.pk} -\end{alltt} -In this case, when specifying that we are interested in a resolution -of 300\dpi{} (\texttt{-dpi=300}) we see that no such font is available on -the system. In fact, a program like \cmdname{dvips} or \cmdname{xdvi} would -go off and actually build the \texttt{.pk} files at the required -resolution using the script \cmdname{mktexpk}. - -Next we turn our attention to \cmdname{dvips}'s header and configuration -files. We first look at one of the commonly used files, the general -prolog \file{tex.pro} for \TeX{} support, before turning our attention -to the generic configuration file (\file{config.ps}) and the -\PS{} font map \file{psfonts.map}. As the \samp{.ps} suffix is -ambiguous we have to specify explicitly which type we are considering -(\optname{dvips config}) for the file \texttt{config.ps}. -\begin{alltt} -> \Ucom{kpsewhich tex.pro} - /usr/local/texmf/dvips/base/tex.pro -> \Ucom{kpsewhich --format="dvips config" config.ps} - /usr/local/texmf/config/config.ps -> \Ucom{kpsewhich psfonts.map} - /usr/local/texmf/dvips/base/psfonts.map -\end{alltt} - -We now take a closer look at the \acro{URW} Times \PS{} support -files. The prefix for these in the standard font naming scheme is -\samp{utm}. The first file we look at is the configuration file, -which contains the name of the map file: -\begin{alltt} -> \Ucom{kpsewhich --format="dvips config" config.utm} -/usr/local/texmf/dvips/psnfss/config.utm -\end{alltt} -The contents of that file is -\begin{alltt} - p +utm.map -\end{alltt} -which points to the file \file{utm.map}, which we want to -locate next. -\begin{alltt} -> \Ucom{kpsewhich --format="dvips config" utm.map} -/usr/local/texmf/dvips/psnfss/utm.map -\end{alltt} -This map file defines the file names of the Type~1 \PS{} fonts in -the URW collection. Its contents look like (we only show part of the -lines): -\begin{alltt} -utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} -\ifSingleColumn /usr/local/texmf/fonts/type1/urw/utm/utmr8a.pfb -\else /usr/local/texmf/fonts/type1/ -...urw/utm/utmr8a.pfb -\fi\end{alltt} - -It should be evident from these few examples how you can easily locate -the whereabouts of a given file. This is especially important if you -suspect that the wrong version of a file is picked up somehow, since -\cmdname{kpsewhich} will show you the first file encountered. - -\subsubsection{Debugging actions} -\label{Debugging} - -Sometimes it is necessary to investigate how a program resolves file -references. To make this practical, \KPS{} offers various levels of -debugging output: - -\begin{ttdescription} -\item[\texttt{\ 1}] \texttt{stat} calls (disk lookups). When running - with an up-to-date \file{ls-R} database this should almost give no - output. -\item[\texttt{\ 2}] References to hash tables (such as the \file{ls-R} - database, map files, configuration files). -\item[\texttt{\ 4}] File open and close operations. -\item[\texttt{\ 8}] General path information for file types - searched by \KPS. This is useful to find out where a particular - path for the file was defined. -\item[\texttt{16}] Directory list for each path element (only relevant - for searches on disk). -\item[\texttt{32}] File searches. -\end{ttdescription} -A value of \texttt{-1} will set all the above options; in practice, -this is usually the most convenient value touse. - -Similarly, with the \cmdname{dvips} program, by setting a combination of -debug switches, one can follow in detail where files are being picked up -from. Alternatively, when a file is not found, the debug trace shows in -which directories the program looks for the given file, so that one can -get an indication what the problem~is. - -Generally speaking, as most programs call the \KPS{} library -internally, one can select a debug option by using the -\envname{KPATHSEA\_DEBUG} environment variable, and setting it to (a -combination of) values as described in the above list. - -(Note for Windows users: it is not easy to redirect -all messages to a file in this system. For diagnostic purposes -you can temporarily \texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log}). - -Let us consider, as an example, a small \LaTeX{} source file, -\file{hello-world.tex}, which contains the following input. -\begin{verbatim} - \documentclass{article} - \begin{document} - Hello World! - \end{document} -\end{verbatim} -This little file only uses the font \file{cmr10}, so let us look -how \cmdname{dvips} prepares the \PS{} file (we want to use the Type~1 -version of the Computer Modern fonts, hence the option \texttt{-Pcms}). -\begin{alltt} -> \Ucom{dvips -d4100 hello-world -Pcms -o} -\end{alltt} -In this case we have combined \cmdname{dvips}'s debug class 4 (font -paths) with \KPS's path element expansion (see \cmdname{dvips} Reference -Manual, \OnCD{texmf/doc/html/dvips/dvips_toc.html}). -The output (slightly rearranged) appears in -Figure~\ref{fig:dvipsdbga}. -\begin{figure*}[tp] -\centering -\input{../examples/ex6a.tex} -\caption{Finding configuration files}\label{fig:dvipsdbga} - -\bigskip - -\input{../examples/ex6b.tex} -\caption{Finding the prolog file}\label{fig:dvipsdbgb} - -\bigskip - -\input{../examples/ex6c.tex} -\caption{Finding the font file}\label{fig:dvipsdbgc} -\end{figure*} - -\cmdname{dvips} starts by locating its working files. First, -\file{texmf.cnf} is found, which gives the definitions of the search -paths for the other files, then the file database \file{ls-R} (to -optimize file searching) and the file \file{aliases}, which makes it -possible to declare several names (e.g., a short \acro{DOS}-like 8.3 and -a more natural longer version) for the same file. Then \cmdname{dvips} -goes on to find the generic configuration file \file{config.ps} -before looking for the customization file \file{.dvipsrc} (which, in -this case is \emph{not found}). Finally, \cmdname{dvips} locates the -config file for the Computer Modern \PS{} fonts \file{config.cms} -(this was initiated with the \texttt{-Pcms} option on the \cmdname{dvips} -command). This file contains the list of the map files which -define the relation between the \TeX{}, \PS{} and file system -names of the fonts. -\begin{alltt} -> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} - p +ams.map - p +cms.map - p +cmbkm.map - p +amsbkm.map -\end{alltt} -\cmdname{dvips} thus goes on to find all these files, plus the generic -map file \file{psfonts.map}, which is always loaded (it contains -declarations for commonly used \PS{} fonts; see the last part of -Section \ref{SExamplesofuse} for more details about \PS{} map -file handling). - -At this point \cmdname{dvips} identifies itself to the user: -\begin{alltt} -This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) -\end{alltt} -\ifSingleColumn -Then it goes on to look for the prolog file \file{texc.pro}: -\begin{alltt}\small -kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro -\end{alltt} -\else -Then it goes on to look for the prolog file \file{texc.pro} (see -Figure~\ref{fig:dvipsdbgb}). -\fi - -After having found the file in question, \cmdname{dvips} outputs -date and time, and informs us that it will generate the -file \file{hello-world.ps}, then that it needs the font file -\file{cmr10}, and that the latter is declared as ``resident'' (no -bitmaps needed): -\begin{alltt}\small -TeX output 1998.02.26:1204' -> hello-world.ps -Defining font () cmr10 at 10.0pt -Font cmr10 is resident. -\end{alltt} -Now the search is on for the file \file{cmr10.tfm}, which is found, -then a few more prolog files (not shown) are referenced, and finally -the Type~1 instance \file{cmr10.pfb} of the font is located and -included in the output file (see last line). -\begin{alltt}\small -kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, - path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: - /var/tex/fonts/tfm//). -kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm -kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, - ... - -kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb -[1] -\end{alltt} - -\subsection{Runtime options} - -Another useful feature of \Webc{} is its possibility to control a number -of memory parameters (in particular, array sizes) via the runtime file -\file{texmf.cnf} read by \KPS{}. The memory settings can be found in -Part 3 of that file in the \TeXLive{} distribution. The more important -are: - -\begin{ttdescription} -\item[\texttt{main\_memory}] - Total words of memory available, for - \TeX{}, \MF{} and \MP. You must make a new format file for each - different setting. For instance, you could generate a ``huge'' - version of \TeX{}, and call the format file \texttt{hugetex.fmt}. - Using the standard way of specifying the program name used by \KPS{}, - the particular value of the \texttt{main\_memory} variable will then - be read from \file{texmf.cnf} (compare the generic value - and the huge one instantiated by \texttt{hugetex}, - etc.). -\item[\texttt{extra\_mem\_bot}] - Extra space for ``large'' \TeX{} data structures: - boxes, glue, breakpoints, etc. Especially useful if you use - \PiCTeX{}. -\item[\texttt{font\_mem\_size}] - Number of words for font information available for \TeX. This - is more or less the total size of all TFM files read. -\item[\texttt{hash\_extra}] - Additional space for the hash table of control sequence names. - Approximately 10,000 control sequences can be stored in the main - hash table; if you have a large book with numerous cross-references, - this might not be enough. You can see that both the - \cmdname{hugetex} and \cmdname{pdflatex} program invocations ask for - an extra 15,000 control sequences (the default value of - \texttt{hash\_extra} is zero). -\end{ttdescription} - -\noindent Of course, this facility is no substitute for truly dynamic -arrays and memory allocation, but since this is extremely difficult to -implement in the present \TeX{} source, these runtime parameters provide -a practical compromise allowing some flexibility. - - -\section{Building on a new Unix platform} - -If you have a platform for which we have not created executables, you -will need to compile \TeX{} and friends from scratch. This is not as -hard as it sounds. What you need is all in the directory \texttt{source} -in the distribution. - -\subsection{Prerequisites} - -You will need at least 100 megabytes of disk space to compile all of -\TeX{} and its support programs. You'll also need an \acro{ANSI} C -compiler, a \cmdname{make} utility, a lexical scanner, and a parser -generator. We recommend the \acro{GNU} version of these programs -(\cmdname{gcc}, \acro{GNU} \cmdname{make}, \cmdname{m4}, \cmdname{flex}, -\cmdname{bison}). You may be able to work with other C compilers and -\cmdname{make} programs, but you will need a good understanding of -building Unix programs to sort out problems. - -Also, the command \texttt{uname} must return a sensible value. - - -\subsection{Configuration} - -To begin, perform a normal installation of \TeXLive{} to your disk (see -section~\ref{sec:unix-install-disk} on -p.~\pageref{sec:unix-install-disk}). You may wish to skip installing -any of the prebuilt binaries. - -Then, unpack the source from the compressed \texttt{tar} file in the -directory \dirname{source} to your disk and change directory to where -you placed it. - -Next, run \cmdname{configure} with a command line like this: -\begin{alltt} -> \Ucom{sh configure -prefix=/usr/local/TeX} -\end{alltt} - -The \optname{-prefix} directory is the one where you installed the -support tree; the directory layout will be as follows (where \$TEXDIR -stands for the directory you chose): - -\noindent -\begin{tabular}{>{\ttfamily}ll@{}} - \dirname{$TEXDIR/share/texmf} & main tree with fonts,\\ - & \qquad macros, etc\\ - \dirname{$TEXDIR/man} & Unix manual pages\\ - \dirname{$TEXDIR/info} & \acro{GNU} style Info manuals\\ - \dirname{$TEXDIR/bin/$PLATFORM} & binaries\\ -\end{tabular} -%$ - -If you want to leave out the \dirname{$PLATFORM} directory level, -i.e., put the binaries directly into \dirname{$TEXDIR/bin}, specify -the \verb|--disable-multiplatform| option to \cmdname{configure}. - -Have a look at the output of \verb|./configure --help| for more -options you can use. For example, you can skip building of \OMEGA{} and -\eTeX{}. - - -\subsection{Running \cmdname{make}} - -Make sure the shell variable or option \texttt{noclobber} is not set. -Then, run the main \cmdname{make} like this: -\begin{alltt} -> \Ucom{make world} -\end{alltt} -and relax\ldots - -Alternatively, you want to log all the output, as in: -\begin{alltt} -> \Ucom{sh -c "make world >world.log 2>\&1" \&} -\end{alltt} - -Before you believe that everything went ok, please check the log file -for errors: \acro{GNU} \cmdname{make} always uses the string \samp{***} -whenever a command fails. Also, check if all the programs were built: - -\begin{alltt} -> \Ucom{cd \emph{TEXDIR}/bin/\emph{archname}} -> \Ucom{ls | wc} -\end{alltt} -The result should be over 200 (you can check the exact number with the -\dirname{bin} directory contents in the distribution). - -If you need special privileges for \texttt{make install}, you can -separate the \samp{make world} into two different runs, like this: -\begin{alltt} -> \Ucom{make all} -> \Ucom{su} -> \Ucom{make install strip} -\end{alltt} - -After you've installed your new binaries, you should follow the normal -post-installation procedures, given in section~\ref{sec:postinstall} -on p.~\pageref{sec:postinstall}. - - -\section{Last words} - -This edition of \TeXLive{} is edited by Sebastian Rahtz, with the major -contributors being Fabrice Popineau, who has worked away unceasingly at -the Windows part of the package (especially the setup!)\ and contributed -in many different ways with ideas, advice and code, and Staszek -Wawrykiewicz, who provided great testing feedback, and co-ordinated the -Polish contributions. - -Kaja Christiansen performed a vital role in endless recompilations on -assorted Unix platforms. Vladimir Volovich did great work on cleaning -the source and making other improvements, while Gerben Wierda did all -the work for \MacOSX. - -\subsection{Acknowledgements} - -\TeXLive{} is a joint effort by virtually all \TeX{} Users Groups. In -particular, we are very grateful for past and present help from: - -\begin{itemize} - -\item The German-speaking \TeX{} Users (\acro{DANTE} e.V.), who provide -the hardware the \TeXLive{} source repository; and Rainer Sch\"opf and -Reinhard Zierke who look after it. \acro{DANTE} president Volker Schaa -coordinated production with the Lehmann's Bookstore -(\url{http://www.lob.de}). - -\item The Perforce corporation (\url{http://www.perforce.com}), for providing -a free copy of their excellent change management system, which we use to -manage. - -\item Karl Berry, who provided the original \Webc{} distribution, and -has continued to give invaluable advice, encouragement, and help. - -\item Mimi Burbank, who arranged access at the Florida State University -School of Computational Science and Information Technology to a slew of -different computers to compile \TeX{} on, and acted as an essential -guinea-pig whenever asked. - -\item Thomas Esser, without whose marvellous \teTeX{} package \TeXLive{} -would certainly not exist, and whose continual help makes it a better -product. - -\item Michel Goossens, who co-authored the documentation. - -\item Eitan Gurari, whose \TeX4ht was used to create the \HTML{} -version of this documentation, and who worked tirelessly to improve -it at short notice. - -\item Petr Olsak, who coordinated and checked all the Czech and Slovak -material very carefully. - -\item Olaf Weber, for his patient assembly and maintenance of Web2c. - -\item Graham Williams, on whose work the catalogue of packages depends. - -\end{itemize} - -In addition, Gerhard Wilhelms, Volker Schaa, Fabrice Popineau, Janka -Chleb\'\i{}kov\'a, Staszek Wawrykiewicz, Erik Frambach, and Ulrik Vieth -kindly translated documentation at various times into their respective -languages, checked other documentation, and provided very welcome -feedback. - - -\subsection{Release history} -\label{sec:history} - -Discussion began in late 1993 when the Dutch \TeX{} Users Group was -starting work on its 4All\TeX{} \CD{} for \acro{MS-DOS} users, and it -was hoped at that time to issue a single, rational, \CD{} for all -systems. This was too ambitious a target for the time, but it did spawn -not only the very successful 4All\TeX{} \CD{}, but also the \acro{TUG} -Technical Council working group on a \emph{\TeX{} Directory Structure} -(\url{http://tug.org/tds}), which specified how to create consistent and -manageable collections of \TeX{} support files. A complete draft of the -\TDS{} was published in the December 1995 issue of \textsl{TUGboat}, and -it was clear from an early stage that one desirable product would be a -model structure on \CD{}. The distribution you now have is a very direct -result of the working group's deliberations. It was also clear that the -success of the 4All\TeX{} \CD{} showed that Unix users would benefit -from a similarly easy system, and this is the other main strand of -\TeXLive. - -We first undertook to make a new Unix-based \TDS{} \CD{} in the autumn -of 1995, and quickly identified Thomas Esser's \teTeX{} as the ideal -setup, as it already had multi-platform support and was built with -portability across file systems in mind. Thomas agreed to help, and work -began seriously at the start of 1996. The first edition was released in -May 1996. At the start of 1997, Karl Berry completed a major new release -of Web2c, which included nearly all the features which Thomas Esser had -added in \teTeX, and we decided to base the 2nd edition of the \CD{} on -the standard \Webc, with the addition of \teTeX's \texttt{texconfig} -script. The 3rd edition of the \CD{} was based on a major revision of -\Webc, 7.2, by Olaf Weber; at the same time, a new revision of \teTeX -was being made, and \TeXLive{} included almost all of its features. The -4th edition followed the same pattern, using a new version of \teTeX, -and a new release of \Webc{} (7.3). The system now included a complete -Windows setup. - -For the 5th edition (March 2000) many parts of the \CD{} were revised -and checked, updating hundreds of packages. Package details were stored -in XML files. But the major change for \TeX\ Live 5 was that all -non-free software was removed. Everything in \TeXLive{} is now intended -to be compatible with the Debian Free Software Guidelines -(\url{http://www.debian.org/intro/free}); we have done our best to check -the license conditions of all packages, but we would very much -appreciate hearing of any mistakes. - -The 6th edition (July 2001) had much more material updated. The major -change was a new install concept: the user could select a more exact set -of needed collections. Language-related collections were completely -reorganized, so selecting any of them installs not only macros, fonts, -etc., but also prepares an appropriate \texttt{language.dat}. - -The 7th edition of 2002 had the notable addition of \MacOSX{} support, -and the usual myriad of updates to all sorts of packages and -programs. An important goal was integration of the source back with -\teTeX, to correct the drift apart in versions~5 and~6. - -In 2003, with the continuing flood of updates and additions, we found -that \TeXLive{} had grown so large it could no longer be contained on a -single \CD, so we split it into three different distributions (see -section~\ref{sec:multiple-dist} on p.~\pageref{sec:multiple-dist}). In -addition: - -\begin{itemize} -\item At the request of the \LaTeX{} team, we changed the standard - \cmdname{latex} and \cmdname{pdflatex} commands to now use \eTeX{} (see - p.~\pageref{text:etex}). -\item The new Latin Modern fonts were included (and are recommended). -\item Support for Alpha \acro{OSF} was removed - (\acro{HPUX} support was removed previously), since no one had (or - volunteered) hardware available on which to compile new binaries. -\item Windows setup was substantially changed; for the first time - an integrated environment based on XEmacs was introduced. -\item Important supplementary programs for Windows - (Perl, Ghost\-script, Image\-Magick, Ispell) are now installed - in the \TeXLive{} installation directory. -\item Font map files used by \cmdname{dvips}, \cmdname{dvipdfm} - and \cmdname{pdftex} are now generated by the new program - \cmdname{updmap} and installed into \dirname{texmf/fonts/map}. -\item \TeX{}, \MF{}, and \MP{} now, by default, output 8-bit input - characters as themselves in output (e.g., \verb|\write|) files, - log files, and the terminal, i.e., \emph{not} translated using the - \verb|^^| notation. In \TeXLive{}~7, this translation was - dependent on the system locale settings; now, locale settings do - not influence the \TeX{} programs' behavior. If for some reason - you need the \verb|^^| output, rename the file - \verb|texmf/web2c/cp8bit.tcx|. (Future releases will have cleaner - ways to control this.) -\item This documentation was substantially revised. -\item Finally, since the edition numbers had grown unwieldy, - the version is now simply identified by the year: \TeXLive{} 2003. -\end{itemize} - - -\subsection{Future releases} - -\emph{\TeXLive{} is not perfect!} (And never will be.) We intend to -continue to release new versions yearly, and would like to provide more -help material, more utilities, more installation programs, and (of -course) an ever-improved and checked tree of macros and fonts. This work -is all done by hard-pressed volunteers in their limited spare time, and -a great deal remains to be done. If you can help, don't hesitate to put -your name forward! - -Please send corrections, suggestions, and offers of help to:\hfill\null -\begin{quote} -Sebastian Rahtz \ / \ 7 Stratfield Road \ / \ Oxford OX2 7BG \ / \ UK \\ -\email{tex-live@tug.org} \\ -\url{http://tug.org/texlive} -\end{quote} - -\medskip -\noindent \textsl{Happy \TeX'ing!} - -\end{multicols} -\end{document} diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/live-2004.tex b/Master/texmf-doc/source/texlive/texlive-en/archive/live-2004.tex deleted file mode 100644 index 10e50ee5832..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/live-2004.tex +++ /dev/null @@ -1,3854 +0,0 @@ -% $Id$ -% TeX Live documentation. Originally written by Sebastian Rahtz and -% Michel Goossens, now maintained by Karl Berry and others. -% Public domain. -% -\documentclass{article} -\let\tldocenglish=1 % for live4ht.cfg -\usepackage{tex-live} -\begin{document} - -\title{% - {\huge \textit{The \protect\TL{} Guide}\\\strut} - {\LARGE \textsf{\TK{} 2004}} -} - -\author{Sebastian Rahtz \& Karl Berry, editors \\[3mm] - \url{http://tug.org/texlive/} - } - -\date{November 2004} - -\maketitle - -\begin{multicols}{2} -\tableofcontents -\listoftables -\end{multicols} - -\section{Introduction} -\label{sec:intro} - -This document describes the main features of the \TL{} software -distribution\Dash a \TeX{} and \LaTeX{} distribution for Linux and other -Unix flavors, \MacOSX, and (32-bit) Windows systems. (Warning: it is -not especially useful for older Mac or \acro{MS-DOS} systems.) - -\TL{} includes precompiled binaries for \TeX{}, \LaTeXe{}, \MF, \MP, -\BibTeX{} and many other programs; an extensive collection of macros, -fonts and documentation; and support for typesetting in many different -scripts from around the world. It is part of the even larger \TK{} -(briefly described below in section~\ref{sec:struct-tl}, -\p.\pageref{sec:struct-tl}), a cooperative effort by the \TeX\ user -groups. - -For newer versions of the packages included here, please check -\acro{CTAN}: \url{http://www.ctan.org} - -For a brief summary of the major changes in this edition of \TL{}, -see section~\ref{sec:history} (\p.\pageref{sec:history}). - - -\subsection{Basic usage of \protect\TL{}} -\label{sec:basic} - -You can use \TL{} in three principal ways: - -\begin{enumerate} - -\item You can run \TL{} directly from the \DVD -(see section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}). -This takes almost no disk space, as you might expect, and gives you -immediate access to everything in \TL{}. Of course performance -will be worse than running on local disk, but you may well find it -acceptable. - -\item You can install all or part of \TL{} to a local disk. This -is the most common use of \TL. You will need (approximately) a -minimum of 100 megabytes, 310 megabytes for a recommended system, and -730 megabytes for a full system. - -\item You can integrate a particular package or collection into your -existing \TeX{} system, either a \TL{} system you installed -earlier, or a different system. - -\end{enumerate} - -\noindent All of these are described in detail in the \acro{OS}-specific -installation sections following, but here is a quick start: - -\begin{itemize*} - -\item The main installation script for Unix and \MacOSX{} is -\texttt{install-tl.sh}; - -\item The single package installation script is \texttt{install-pkg.sh}. - -\item Unfortunately, this version of \TL{} has no Windows installer, due -to technical difficulties. See section~\ref{sec:win-install} below -for more information. - -\end{itemize*} - - -\subsection{Getting help} -\label{sec:help} - -The \TeX{} community is both active and friendly, and virtually all -serious questions end up getting answered. However, the support is -informal, done by volunteers and casual readers, so it's especially -important that you do your homework before asking. (If you prefer -guaranteed commercial support, you can forego \TL{} completely and -purchase a vendor's system; \url{http://tug.org/interest.html#vendors} -has a list.) - -Here is a list of resources, approximately in the order we recommend -using them: - -\begin{description} -\item [Getting Started] If you are new to \TeX, the web page -\url{http://tug.org/begin.html} gives a brief introduction to the system. - -\item [\TeX{} \acro{FAQ}] The \TeX{} \acro{FAQ} is a huge compendium of -answers to all sorts of questions, from the most basic to the most -arcane. It is included on \TL{} in \OnCD{texmf-doc/doc/english/FAQ-en}, and is -available on the Internet through \url{http://www.tex.ac.uk/faq}. -Please check here first. - -\item [\TeX{} Catalogue] If you are looking for a specific package, -font, program, etc., the \TeX{} Catalogue is the place to look. It is a -huge list of all \TeX{}-related items. See -\OnCD{texmf-doc/doc/english/catalogue}, or -\url{http://www.ctan.org/tex-archive/help/Catalogue}. - -\item [\TeX{} Web Resources] The web page -\url{http://tug.org/interest.html} has many \TeX{}-related links, in -particular for numerous books, manuals, and articles on all aspects of -the system. - -\item [support archives] The two principal support forums are the -Usenet newsgroup \url{news:comp.text.tex} and the mailing list -\email{texhax@tug.org}. Their archives have years of past -questions and answers for your searching pleasure, via -\url{http://groups.google.com/groups?group=comp.text.tex} and -\url{http://tug.org/mail-archives/texhax}, respectively. And a general web -search, for example on \url{http://google.com}, never hurts. - -\item [asking questions] If you cannot find an answer, you can post to -\dirname{comp.text.tex} through Google or your newsreader, or to -\email{texhax@tug.org} through email. But before you post, -\emph{please} read this \acro{FAQ} entry for advice on asking questions -in such a way that you're most likely to get an answer: -\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. - -\item [\TL{} support] If you want to report a bug or have -suggestions or comments on the \TL{} distribution, installation, or -documentation, the mailing list is \email{tex-live@tug.org}. However, -if your question is about how to use a particular program included in -\TL{}, you are better off writing to that program's maintainer or -mailing list. - -\end{description} - -The other side of the coin is helping others who have questions. Both -\dirname{comp.text.tex} and \code{texhax} are open to anyone, so feel -free to join, start reading, and help out where you can. Welcome to -\TeX{}! - - -% don't use \TL so the \uppercase in the headline works. Also so -% tex4ht ends up with the right TeX. Likewise the \protect's. -\section{Structure of \protect\TeX\protect\ Live} -\label{sec:struct-tl} - -This section describes the structure and contents of \TL{} and the -\TK{} of which it is a part. - -\subsection{Multiple distributions: \protect\pkgname{live}, - \protect\pkgname{inst}, - \protect\pkgname{protext}} -\label{sec:multiple-dist} - -Space limitations of \acro{CD-ROM} format have forced us to divide -\TK{} into several distributions, as follows. - -\begin{description} - -\item [live] A complete system on \acro{DVD}; it is too large -for \acro{CD}. It can be run live or installed to disk. It also -includes a snapshot of the \CTAN{} repository, entirely independent of -\TL{}, as well as assorted other packages in a -\texttt{texmf-extra} directory. - -Unfortunately, this release of \TL{} does not include a Windows -installer, due to technical difficulties. (We hope there will be an -installer again in a few months.) Therefore, when the \DVD{} is mounted -on Windows, the setup program offers to start the \pkgname{protext} -installation (see below), and also mentions \CTAN{} and \TL{}, which are -in subdirectories of the top level of the \DVD{}. - -\CTAN{} and \texttt{texmf-extra} do not follow the same copying -conditions as \TL{}, so be careful when redistributing or -modifying. - -\item [inst(allable)] A complete system on \CD; in order to make this fit, -the packages and programs are compressed. Therefore, it is not possible -to run \TeX\ directly from the installable \CD, you have to install it -to disk (hence its name). Furthermore, it can only be installed on Unix -(including Linux, \MacOSX, etc.)\ systems, not Windows, although a set -of experimental Windows binaries is included (for sharing across -platforms). Installation is described in subsequent sections. - -\item [protext] An enhancement of the \MIKTEX\ system, for Windows. -\ProTeXt\ adds a few extra tools to \MIKTEX, and simplifies -installation. It is entirely independent of \TL{}, and has its own -installation instructions. It can be run live, or installed to disk. -The \ProTeXt\ home page is \url{http://tug.org/protext}. - -\ProTeXt\ is provided as both the top level of the \pkgname{live} \DVD\ -and on its own \CD\ (for those who cannot use the \DVD). - -\end{description} - -\noindent You can tell which type of distribution you're in by looking -for a \texttt{00\var{type}.TL} file at the top of the \TL{} directory. -This file also contains the \TL{} release date. - -Naturally, each user group chooses what to distribute, at its own -discretion. (\acro{TUG} is sending all three discs above to all of its -members.) - - -\subsection{Top level directories} -\label{sec:tld} - -Here is a brief listing and description of the top level directories in -the \TL{} distribution. This has changed considerably in 2004: the -single \texttt{texmf} tree has been split into several smaller trees. - -Also, on the \pkgname{live} \DVD, the entire \TL{} hierarchy is in a -subdirectory \dirname{texlive2004}, not at the top level of the disc. - -\smallskip -\begingroup - \renewcommand{\arraystretch}{1.3} % open up interrow spacing -\begin{tabular}{>{\ttfamily}lp{.78\hsize}} -bin & The \TeX{} system programs, arranged by platform. \\ -MacOSX & Supporting software for \MacOSX (see - section~\ref{sec:mac-install}, \p.\pageref{sec:mac-install}). \\ -source & The source of all programs, including the main \Webc{} - \TeX{} and \MF{} distributions. These are stored in a - \cmdname{bzip2}-compressed tar archive. \\ -support & Assorted auxiliary packages and programs. These are - \emph{not} installed automatically. This includes - assorted editors and \TeX\ shells. \\ -texmf & Tree for the programs, along with their support files and - documentation. Does not include \TeX\ formats and packages. \\ -texmf-dist & The main tree of formats and packages. \\ -texmf-doc & Tree for self-contained pure documentation, with no other - installed files.\hfil\break Arranged by language. \\ -texmf-var & Tree for files automatically generated and stored. \\ -xemtex & The \cmdname{XEmacs} editor and other support programs for - Windows. - These programs generally come pre-installed on Unix systems, or are - at least easy to compile. \\ -\end{tabular} -\endgroup - -\smallskip - -In addition to the directories above, the installation scripts and -\filename{README} files (in various languages) are at the top level of -the distribution. - -The (new) \dirname{texmf-doc} directory contains only documentation, but -it does not contain all the documentation. The documentation for the -programs (manuals, man pages, Info files) is in \dirname{texmf/doc}, -since the programs are in \dirname{texmf}. Similarly, the documentation -for \TeX\ packages and formats is in \dirname{texmf-dist/doc}. You can -use the \cmdname{texdoc} or \cmdname{texdoctk} programs to find any -documentation wherever it's located. The comprehensive links in the -top-level file \OnCD{doc.html} may also be helpful. - - -\subsection{Extensions to \protect\TeX} -\label{sec:tex-extensions} - -\TL{} contains several extended versions of \TeX: - -\begin{description} - -\item [\eTeX] adds a small but powerful set of new primitives -\label{text:etex} (related to macro expansion, character scanning, -classes of marks, additional debugging features, and more) and the -\TeXXeT{} extensions for bidirectional typesetting. In default mode, -\eTeX{} is 100\% compatible with ordinary \TeX. See -\OnCD{texmf-dist/doc/etex/base/etex_man.pdf}. - -\item [pdf\TeX] writes Acrobat \acro{PDF} format as well as \dvi{}. The -\LaTeX{} \pkgname{hyperref} package has an option `\optname{pdftex}' -which turns on all the program features. See -\OnCD{texmf/doc/pdftex/manual/pdftex-a.pdf} (A4 paper) or -\OnCD{texmf/doc/pdftex/manual/pdftex-l.pdf} (letter paper), and -\OnCD{texmf/doc/pdftex/examples/example.tex}. - -\item [pdfe\TeX] combines the pdf\TeX\ and \eTeX\ extensions. This is -the default program for all formats except plain \TeX. -See above for documentation. - -\item [\OMEGA\ (Omega)] is based on Unicode (16-bit characters), thus -supports working with almost all the world's scripts simultaneously. It -also supports so-called `\OMEGA{} Translation Processes' (\acro{OTP}s), -for performing complex transformations on arbitrary input. See -\OnCD{texmf-dist/doc/omega/base/doc-1.8.tex} (not completely up-to-date). - -\item [Aleph] combines the \OMEGA\ and \eTeX\ extensions. -See \OnCD{texmf-dist/doc/aleph/base} for some minimal documentation. - -\end{description} - - -\subsection{Other notable programs in \protect\TL} - -Here are a few other commonly-used programs included in \TL{}: - -\begin{cmddescription} - -\item [bibtex] bibliography support. - -\item [makeindex] index support. - -\item [dvips] convert \dvi{} to \PS{}. - -\item [xdvi] \dvi{} previewer for the X Window System. - -\item [dvilj] \dvi{} drive for the HP LaserJet family. - -\item [dv2dt, dt2dv] convert \dvi{} to/from plain text. - -\item [dviconcat, dviselect] cut and paste pages -from \dvi{} files. - -\item [dvipdfm] convert \dvi{} to \acro{PDF}, an alternative approach -to pdf\TeX\ (mentioned above). See the \pkgname{ps4pdf} and -\pkgname{pdftricks} packages for still more alternatives. - -\item [psselect, psnup, \ldots] \PS{} -utilities. - -\item [lacheck] \LaTeX{} syntax checker. - -\item [texexec] Con\TeX{}t and \acro{PDF} processor. - -\item [tex4ht] \TeX{} to \acro{HTML} converter. - -\end{cmddescription} - - -\section{Unix installation} -\label{sec:unix-install} - -As introduced in section~\ref{sec:basic} (\p.\pageref{sec:basic}), -\TL{} has three principal uses: - -\begin{enumerate} -\item Run directly from media. -\item Install to disk. -\item Integrate a particular package or collection into your existing -\TeX{} installation. -\end{enumerate} - -\noindent The following sections describes the Unix-specific procedures -for each of these. - -\ifSingleColumn \begin{figure}[ht]\noindent \fi -\begin{warningbox} -\textbf{Warning: } The \TK{} \CD{}s and \DVD{} are in ISO 9660 (High Sierra) -format, \emph{with} Rock Ridge (and Joliet, for Windows) -extensions. Therefore, in order to take full advantage of the \TK{} -under Unix, your system needs to be able to use the Rock Ridge -extensions. Please consult the documentation for your \cmdname{mount} -command to see how to do this. If you have several different machines -on a local network, you may be able to mount the \CD{}s on one which -does support Rock Ridge, and use this with the others. - -\leavevmode\quad Linux, \acro{BSD}, Sun, and \acro{SGI} -systems should be able to use the \CD{}s without problems. We -would appreciate receiving detailed advice from users on other systems -who succeed, for future versions of this documentation. - -\leavevmode\quad -The discussion below assumes you have been able to mount -the \CD{}s with full Rock Ridge compatibility. -\end{warningbox} -\ifSingleColumn\end{figure}\fi - - -% -\subsection{Running \protect\TL{} directly from media (Unix)} - -\def\runlive{% text repeated in windows section -It is possible to use the \TeX{} system directly from the \pkgname{live} -\DVD{}, without installing the distribution to disk. (Thus the name -\TeX\ `Live', in fact.) It is \emph{not} possible to run \TeX{} -directly from the other \CD s (see section~\ref{sec:multiple-dist}, -\p.\pageref{sec:multiple-dist}). -} - -\def\startinst{% repeated in other subsections -To start, you mount the \CD{} or \DVD{}, with Rock Ridge extensions -enabled. The exact command to do this varies from system to system; the -following works under Linux, except the name of the device -(\filename{/dev/cdrom}, here) may vary. (All our examples will use -\texttt{>} as the shell prompt; user input is -\Ucom{\texttt{underlined}}.) -\begin{alltt} -> \Ucom{mount -t iso9660 /dev/cdrom /mnt/cdrom} -\end{alltt} - -\noindent Change the current directory to the mount point: -\begin{alltt} -> \Ucom{cd /mnt/cdrom} -\end{alltt} - -\noindent Under \MacOSX, the directory is typically under -\dirname{/Volumes}, and the media will be mounted automatically. - -Run the installation script \filename{install-tl.sh}: -\begin{alltt} -> \Ucom{sh install-tl.sh}\\ -Welcome to TeX Live... -\end{alltt} - -\noindent After various greeting messages and a list of the main menu -options, the installation will ask you to enter a command. Do this by -typing the desired character and hitting return; don't type the angle -brackets. Either uppercase or lowercase is ok; we'll use lowercase in -our examples. -} - -\runlive -\startinst - -For running live, our first command will be \Ucom{d} and then the -subcommand \Ucom{1} to set directories. Even in this case, we must -choose a directory on the local disk to place files that the \TeX{} -system itself generates, such as fonts and formats, and also to provide -a place for updated configuration files, if need be. We'll use -\dirname{/usr/local/texmf-local} in this example. (If the default value -of \dirname{/usr/TeX} works for you, then you can skip this step.) -\begin{alltt} -Enter command: \Ucom{d} -Current directories setup: -<1> TEXDIR: /usr/TeX -... -Enter command: \Ucom{1} -New value for TEXDIR [/usr/TeX]: \Ucom{/usr/local/texmf-local} -... -Enter command: \Ucom{r} -\end{alltt} - -\noindent Back at the main menu, our second and last command is -\Ucom{r}, to set up for running live off the media without installing -to disk: -\begin{alltt} -Enter command: \Ucom{r} -Preparing destination directories... -... -Welcome to TeX Live! -> -\end{alltt} - -\noindent And we are back at the system prompt, as shown. - -Next, it is necessary to alter two environment variables: -\envname{PATH}, to an architecture-dependent value (so that we can run -the programs), and \envname{VARTEXMF}, to the value specified above. See -table~\ref{tab:archlist} for a list of the architecture names for the -different systems. - - -\def\textruntexconfig{% -After the main installation has completed, and environment variables -have been set, the last step is to run \cmdname{texconfig} to customize -your installation for your needs. This is explained in -section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig}. -} -\textruntexconfig - -\begin{table*}[ht] -\caption[Supported system architectures.]{Supported system -architectures. In addition to the version-specific names listed here, -there are generic names without the version numbers. For instance, -\texttt{sparc-solaris} links to \texttt{sparc-solaris2.7}. The generic -names can be used to protect against the version numbers changing in the -future, if you wish.} -\label{tab:archlist} -\begin{tabular}{>{\ttfamily}ll} -alpha-linux & HP Alpha GNU/Linux \\ -%alphaev5-osf4.0d & HP Alphaev5 OSF \\ -%hppa2.0-hpux10.20 & HP9000 HPUX 10.20 \\ -i386-freebsd4.10 & Intel x86 FreeBSD \\ -i386-linux & Intel x86 GNU/Linux \\ -%i386-openbsd3.3 & Intel x86 OpenBSD \\ -%i386-solaris2.8 & Intel x86 Solaris \\ -mips-irix6.5 & SGI IRIX \\ -powerpc-aix4.3.3.0 & IBM RS/6000 AIX \\ -powerpc-darwin6.8 & \MacOSX \\ -sparc-solaris2.7 & Sun Sparc Solaris \\ -sparc64-linux & Sun Sparc GNU/Linux \\ -win32 & Windows (32-bit) \\ -x86\_64-linux & Intel/AMD 64-bit GNU/Linux \\ -\hline -\end{tabular} -\end{table*} - -\label{text:path} -The syntax for setting the environment variables, and the initialization -file to put them in, depends on the shell you use. If you use a -Bourne-compatible shell (\cmdname{sh}, \cmdname{bash}, \cmdname{ksh}, et -al.), put the following into your \filename{$HOME/.profile} file: -\begin{alltt} -PATH=/mnt/cdrom/bin/\var{archname}:$PATH; export PATH -VARTEXMF=/usr/local/texmf-local/texmf-var; export VARTEXMF -\end{alltt} - -\noindent For C shell-compatible shells (\cmdname{csh}, \cmdname{tcsh}), -put the following into your \filename{$HOME/.cshrc} file: -\begin{alltt} -setenv PATH /mnt/cdrom/bin/\var{archname}:$PATH -setenv VARTEXMF /usr/local/texmf-local/texmf-var -\end{alltt} - -\noindent Then log out, log back in, and test your installation -(see section~\ref{sec:test-install}, \p.\pageref{sec:test-install}). - -\def\textifindoubt{% -If in doubt, please ask any local system gurus to help you with -problems; for example, the way to mount the \TL{} media, which -directory or directories to use, and precise details of the changes to -your personal initialization files can and do vary from site to site. -} -\textifindoubt - - -% -\subsection{Installing \protect\TeX\protect\ Live to disk} -\label{sec:unix-install-disk} - -It is possible, indeed typical, to install the \TeX{} system from the -\TL{} to disk. This can be done either from any of the \TK{} discs. -(See section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}, -for an explanation of the different distributions.) - -\startinst - -Table~\ref{tab:main-menu-options} briefly lists the options in the main -menu. The order in which you select the options makes little -difference, except that \Ucom{i} must be last. It's reasonable to go -through them in the order presented here. - -% apparently here.sty [H] doesn't support table*. -\begin{table}[H] -\caption{Main menu options for the installation.} -\label{tab:main-menu-options} -\begin{tabular}{>{\ttfamily}ll} -p & The platform you are running on.\\ -b & The architectures for which to install binaries.\\ -s & The base installation scheme to use (minimal, recommended, - full, etc.)\\ -c & Override the base scheme for individual collections.\\ -l & Override for language collections.\\ -d & Directories in which to install.\\ -o & Other options.\\ -i & Perform the installation.\\ -\end{tabular} -\end{table} - -Here are further details on each option. - -\textbf{\optname{p} -- Current platform.} Since the installation script -automatically guesses which platform you're running on, it is generally -unnecessary to use this option. It's there in case you need to override -the automatic detection. - -\textbf{\optname{b} -- Binary architectures.} By default, only the -binaries for your current platform will be installed. From this menu, -you can select installation of binaries for other architectures as well -(or not install the current platforms). This can be useful if you are -sharing a \TeX\ tree across a network of heterogenous machines. For a -list of the supported architectures, see table~\ref{tab:archlist}, -\p.\pageref{tab:archlist}. - -\textbf{\optname{s} -- Base installation scheme.} From this menu, you -can choose an overall common set of packages, called a ``scheme''. The -default \optname{recommended} scheme suffices for typical needs, but you -can also choose the \optname{basic} scheme if you are low on disk space, -or \optname{full} to get absolutely everything. There are also specific -sets for Omega and \acro{XML}. - -\textbf{\optname{c} -- Individual collections.} From this menu, you can -override the base scheme's set of collections to install. Collections -are one level lower than schemes\Dash collections consist of -one or more packages, where packages (the lowest level grouping in \TL) -contain the actual \TeX\ macro files, font families, and so on. -In this menu, selection letters are case-sensitive. - -\textbf{\optname{l} -- Language collections}. This menu has the same -basic purpose as \Ucom{c}, to override the base scheme. In this case, -the collections are specifically for different languages. Selection -letters are case-sensitive here. Here is a list of the language -collections in \TL: - -% xx really should generate list from texmf/tpm/collection/tex-lang* -% a la install-tl.sh. -\begin{tabbing} -\hspace{.25\linewidth} \= -\hspace{.25\linewidth} \= -\hspace{.25\linewidth} \= -\hspace{.25\linewidth} \kill -(some) African scripts \> -Arabic \> -Armenian \> -Chinese\,Japanese\,Korean \\ -Croatian \> -Cyrillic \> -Czech/Slovak \> -Danish \\ -Dutch \> -Finnish \> -French \> -German \\ -Greek \> -Hungarian \> -Indic \> -Italian \\ -Latin \> -Manju \> -Mongolian \> -Norwegian \\ -Polish \> -Portuguese \> -Spanish \> -Swedish \\ -Tibetan \> -\acro{UK} English \> -Vietnamese \\ -\end{tabbing} - -\noindent Language collections typically include fonts, macros, -hyphenation patterns, and other support files. (For instance, -\pkgname{frenchle.sty} is installed if you select the \optname{French} -collection.) In addition, installing a language collection will alter -the \filename{language.dat} configuration file controlling which -hyphenation patterns are loaded. - -\textbf{\optname{d} -- Installation directories}. Three directories can -be changed here: -\label{text:instdir} - -\begin{ttdescription} -\item [TEXDIR] The top-level directory under which -everything else will be installed. The default value is -\dirname{/usr/TeX}, and is often changed. For example, changing to a -value such as \dirname{/usr/local/texlive2003} would make it possible to -keep different releases of \TL{} separate. (You may then wish to make -\dirname{/usr/local/texlive} a symbolic link, after testing the new -release.) - -Under \MacOSX, the usual frontends look for \TeX{} in -\dirname{/usr/local/teTeX}, so you may wish to install \TL{} there. - -\item [TEXMFLOCAL] This tree is where the \TeX{} system (not as part of -installation, but rather over time) puts non-version-specific files, -primarily fonts. The default value is \dirname{TEXDIR/texmf-local}. -However, it's also the recommended location to put any local packages or -configuration settings. Therefore, it's desirable to change it to a -location independent of the current \TL{} release; for example, -\dirname{/usr/local/texmf-local}. - -\item [VARTEXMF] This tree is where the system puts files that -\emph{are} version-specific, primarily format files and the -configuration files which are modified by \cmdname{texconfig} (see -section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig}). The default -value is \dirname{TEXDIR/texmf-var}, and there's generally no reason to -change it. - -\end{ttdescription} - -\textbf{\optname{o} -- Other options.} From this menu, you can select -the following general options: - -\begin{ttdescription} -\item [a] Specify an alternate directory for generated fonts. -The default is to use the \envname{VARTEXMF} tree, as explained above. -Setting this is useful if you plan to mount the main tree read-only, and -therefore you need another location (perhaps host-specific) for -dynamically created fonts. - -\item [l] Create symbolic links for the binaries, man pages, -and\slash or \acro{GNU} Info files in other locations. For example, you may -wish to make the man pages available under \dirname{/usr/local/man} and -the Info files available under \dirname{/usr/local/info}. (Of course -you need appropriate privileges to write in the specified directories.) - -It is not advisable to overwrite a \TeX\ system that came with your -system with this option. It's intended more for having the links in -standard directories known to users, such as \dirname{/usr/local/bin}, -which don't already contain any \TeX\ files. - -\item [d] Skip installation of the font/macro documentation tree. -This is useful if you need to save space, or if you've previously -installed the documentation elsewhere. - -\item [s] Skip installation of the main font/macro source -tree. This is useful if you are arranging to share that tree between -machines and\slash or architectures in some other way, such as \acro{NFS}. - -\end{ttdescription} - -\textbf{i -- Perform installation.} When you're satisfied with your -configuration options, enter \Ucom{i} to actually do the installation -from the media to your chosen locations. - -% text is similar to above, but no VARTEXMF, so we have to write out. -After the installation completes, your next step is to include the -architecture-specific subdirectory of \dirname{TEXDIR/bin} in your -\envname{PATH}, so the newly-installed programs can be found. The -architecture names are listed in table~\ref{tab:archlist}, -\p.\pageref{tab:archlist}, or you can simply list the directory -\dirname{TEXDIR/bin}. - -The syntax for doing this, and the initialization file to use, depends -on your shell. If you use a Bourne-compatible shell (\cmdname{sh}, -\cmdname{bash}, \cmdname{ksh}, et al.), put the following into your -\filename{$HOME/.profile} file: - -\begin{alltt} -PATH=/mnt/cdrom/bin/\var{archname}:$PATH; export PATH -\end{alltt} - -\noindent For C shell-compatible shells (\cmdname{csh}, \cmdname{tcsh}), -put the following into your \filename{$HOME/.cshrc} file: -\begin{alltt} -setenv PATH /mnt/cdrom/bin/\var{archname}:$PATH -\end{alltt} - -\textruntexconfig - -Here is a brief annotated example which selects a full installation, -with binaries for the current system only, with directory changes as -recommended above. The prompts and \acro{RETURN}s are omitted for -brevity. - -\begin{alltt} -> \Ucom{sh install-tl.sh} -\Ucom{s} \Ucom{b} \Ucom{r} # scheme, full, return to main -\Ucom{d} # change directories -\Ucom{1} \Ucom{/usr/local/texlive2003} # top-level dir -\Ucom{2} \Ucom{/usr/local/texmf-local} # TEXMFLOCAL outside TEXDIR -\Ucom{r} # return to main -\Ucom{i} # perform installation -> \Ucom{texconfig} ... -# New PATH, with Linux as the example: -> \Ucom{PATH=/usr/local/texlive2003/bin/i386-linux:$PATH; export PATH} -\end{alltt} - -\textifindoubt - - -% -\subsection{Installing individual packages to disk} - -You can add individual packages or collections from the current -distribution to an existing non-\TL{} setup, or an earlier -\TL{} installation. - -\startinst - -Run the installation script \filename{install-pkg.sh} (not -\filename{install-tl.sh}, which is intended for complete installations -only): -\begin{alltt} -> \Ucom{sh install-pkg.sh \var{options}} -\end{alltt} - -The first set of options controls what gets read: - -\begin{ttdescription} -\item [-{}-package=\var{pkgname}] The individual package to work on. - -\item [-{}-collection=\var{colname}] The individual collection to work on. - -\item [-{}-nodoc] Exclude documentation files from the operation. - -\item [-{}-nosrc] Exclude source files from the operation. - -\item [-{}-cddir=\var{dir}] Source directory to read from; defaults -to the current directory. If you followed the instructions above, that -will be the distribution directory, and won't need to be changed. - -\item [-{}-listdir=\var{dir}] The so-called `lists' directory within -\var{cddir} from which to read the package information. The only -reason to change the default is if you're making changes to \TL{} -yourself. - -\end{ttdescription} - -What actually happens is controlled by the following options. If -neither of these are specified, the default action is to install the -selected files. The main destination tree is found by expanding -\envname{\$TEXMFMAIN} with \cmdname{kpsewhich}. You can override it by -setting either the environment variable \envname{TEXMFMAIN} or -\envname{TEXMF}. - -\begin{ttdescription} -\item [-{}-listonly] List the files that would be installed, but don't -actually install anything. - -\item [-{}-archive=\var{tarfile}] Instead of installing the files into -the \TeX{} system, make a \cmdname{tar} archive. - -\end{ttdescription} - -Additional options: - -\begin{ttdescription} - -\item [-{}-config] After installation, run \code{texconfig init}. - -\item [-{}-nohash] After installation, don't run \cmdname{mktexlsr} to -rebuild the filename database. - -\item [-{}-verbose] Give more information as the script runs. - -\end{ttdescription} - -Here are some usage examples: - -\begin{enumerate} - -\item To see the files in the package \pkgname{fancyhdr} without -installing it: - -\begin{alltt} -\ifSingleColumn> \Ucom{sh install-pkg.sh --package=fancyhdr --listonly} -\else> \Ucom{sh install-pkg.sh --package=fancyhdr \bs} -> \Ucom{--listonly} -\fi{} -texmf/doc/latex/fancyhdr/README -texmf/doc/latex/fancyhdr/fancyhdr.dvi -texmf/doc/latex/fancyhdr/fancyhdr.pdf -... -\end{alltt} - -\item Install the \LaTeX{} package \pkgname{natbib}: -\begin{alltt} -> \Ucom{sh install-pkg.sh --package=natbib} -\end{alltt} - -\item Install the \LaTeX{} package \pkgname{alg} without source files or -documentation: -\begin{alltt} -\ifSingleColumn> \Ucom{sh install-pkg.sh --package=alg --nosrc --nodoc} -\else> \Ucom{sh install-pkg.sh -{}-package=alg \bs} -> \Ucom{-{}-nosrc -{}-nodoc} -\fi\end{alltt} - -\item Install all the packages in the collection of additional -plain \TeX\ macros: -\begin{alltt} -> \Ucom{sh install-pkg.sh --collection=tex-plainextra} -\end{alltt} - -\item Write all files in the \pkgname{pstricks} package to a -\cmdname{tar} file in \path|/tmp|: -\begin{alltt} -\ifSingleColumn> \Ucom{sh install-pkg.sh --package=pstricks --archive=/tmp/pstricks.tar} -\else -> \Ucom{sh install-pkg.sh -{}-package=pstricks \bs} -> \Ucom{-{}-archive=/tmp/pstricks.tar} -\fi\end{alltt} - -\end{enumerate} - -\textifindoubt - - -% -\section{Post-installation} -\label{sec:postinstall} - -After the main installation is done, for any operating system, the -remaining steps are to configure the system for your local needs, and -perform some basic tests. - -Another sort of post-installation is to acquire packages, fonts, or -programs that were not included in \TL{}. The basic idea is to -install such additions in the \envname{TEXMFLOCAL} tree (if you -installed to disk), or \envname{VARTEXMF} (if you are running live). -See the ``Installation directories'' option on \p.\pageref{text:instdir}. - -Unfortunately, the details can and do vary widely, and so we do not attempt to -address them here. Here are some external links to descriptions: -\begin{itemize*} -\item -\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instpackages} -\item -\url{http://www.ctan.org/installationadvice} -\item -\url{http://www.ctan.org/tex-archive/info/beginlatex/html/chapter5.html#pkginst} -\item -\url{http://www.ctan.org/tex-archive/info/Type1fonts} for font creation -and installation information in particular. -\end{itemize*} - - -\subsection{The \protect\cmdname{texconfig} program} -\label{sec:texconfig} - -At any time after installation, you can and should use the program -\cmdname{texconfig} to configure the system to fit your local needs. It -is installed in the architecture-specific subdirectory -\texttt{TEXDIR/bin/\var{arch}} along with everything else. - -If you run it without arguments, it will enter full-screen mode and -allow you to view and change options interactively. - -You can also run it with various command-line options. Here are some of -the most common (a \TL{} installation is configured for the A4 paper -size by default): - -\begin{ttdescription} - -\item [texconfig paper letter] Set default paper size for -various programs and drivers (\cmdname{pdftex}, \cmdname{dvips}, -\cmdname{dvipdfm}, \cmdname{xdvi}) to be \acro{US} letter. The other -allowable size is \optname{a4}, which is the default. - -\item [texconfig localsetup] Verify that paths are set ok. - -\item [texconfig rehash] Update all the \TeX{} system filename databases. - -\item [texconfig faq] Show the \teTeX{} \acro{FAQ}. -(See also the main \TeX{} \acro{FAQ} in \OnCD{texmf-doc/doc/english/FAQ-en}.) - -\item [texconfig help] Output help information for \cmdname{texconfig}. - -\end{ttdescription} - -Of course, \cmdname{texconfig} can only support changing a few of the -many options and configuration parameters in a \TeX{} system. The main -configuration file for the base \Webc{} programs is named -\filename{texmf.cnf}. You can find its location by running -\samp{kpsewhich texmf.cnf}; it contains many comments explaining the -default settings and useful alternatives. - - -\subsection{Testing the installation} -\label{sec:test-install} - -After installing \TL{} as best you can, you naturally want to test -it out, so you can start creating beautiful documents and\slash or fonts. - -This section gives some basic procedures for testing that the new system -is functional. We give Unix commands; under \MacOSX{} and Windows, -you're more likely to run the tests through a graphical interface, but -the principles are the same. - -\begin{enumerate} - -\item Make sure that you can run the \cmdname{tex} program in the first -place: - -\begin{alltt} -> \Ucom{tex -{}-version} -TeX 3.141592 (Web2C 7.5.3) -kpathsea version 3.5.3 -Copyright (C) 1997-2004 D.E. Knuth. -... -\end{alltt} -If this comes back with `command not found' instead of version and -copyright information, most likely you don't have the correct -\dirname{bin} subdirectory in your \envname{PATH}. See -the environment-setting information on \p.\pageref{text:path}. - -\item Process a basic \LaTeX{} file: -\begin{alltt} -> \Ucom{latex sample2e.tex} -This is pdfeTeXk, Version 3.141592... -... -Output written on sample2e.dvi (3 pages, 7496 bytes). -Transcript written on sample2e.log. -\end{alltt} -If this fails to find \filename{sample2e.tex} or other files, perhaps -you have interference from old environment variables or configuration -files. For a deep analysis, you can always ask \TeX{} to report on -exactly what it is searching for, and finding; see ``Debugging actions'' -on page~\pageref{Debugging}. - -\item Preview the result online: -\begin{alltt} -> \Ucom{xdvi sample2e.dvi} -\end{alltt} -(Under Windows, the analogous command is \cmdname{windvi}.) You should -see a new window with a nice document explaining some of the basics of -\LaTeX{}. (Well worth reading, by the way if you're new to the system.) -You do have to be running under X for \cmdname{xdvi} to work; if you're -not, or your \envname{DISPLAY} environment variable is set incorrectly, -you'll get an error \samp{Can't open display}. - -\item Create a \PS{} file for printing or display: -\begin{alltt} -> \Ucom{dvips sample2e.dvi -o sample2e.ps} -\end{alltt} - -\item Create a \acro{PDF} file instead of \dvi{}; this processes the -\filename{.tex} file and writes \acro{PDF} directly: -\begin{alltt} -> \Ucom{pdflatex sample2e.tex} -\end{alltt} - -\item Preview the \acro{PDF} file: -\begin{alltt} -> \Ucom{gv sample2e.pdf} -\textrm{or:} -> \Ucom{xpdf sample2e.pdf} -\end{alltt} -Unfortunately neither \cmdname{gv} nor \cmdname{xpdf} are currently -included in \TL{}, so you must install them separately. See -\url{http://wwwthep.physik.uni-mainz.de/~plass/gv} and -\url{http://www.foolabs.com/xpdf}, respectively. - -\item Other standard test files you may find useful: - -\begin{ttdescription} -\item [small2e.tex] A simpler document than \filename{sample2e}, to -reduce the input size if you're having troubles. -\item [testpage.tex] Test if your printer introduces any offsets. -\item [nfssfont.tex] For printing font tables and tests. -\item [testfont.tex] Also for font tables, but using plain \TeX{}. -\item [story.tex] The most canonical (plain) \TeX{} test file of all. -You must type \samp{\bs bye} to the \code{*} prompt after \samp{tex -story.tex}. -\end{ttdescription} -You can process these in the same way as we did with -\filename{sample2e.tex}. - -\end{enumerate} - -If you are new to \TeX{}, or otherwise need help with actually -constructing \TeX{} or \LaTeX{} documents, please visit -\url{http://tug.org/begin.html}. We especially recommend the -\textsl{Formatting Information} manual by Peter Flynn, available at -\url{http://www.ctan.org/tex-archive/documentation/beginlatex}. - - -\section{\MacOSX{} installation} -\label{sec:mac-install} - -\TL{} supports \MacOSX, but no prior Macintosh versions. (If you -are running an older Mac version, you can view the files by installing -the Joliet system extension available from -\url{http://www.tempel.org/joliet}; however, the \TL{} binaries -will not run.) - -Installation of \TeX{} under \MacOSX{} can be done in two ways: - -\begin{enumerate} -\item With the \filename{install*} scripts, as with Unix. -\item With the \cmdname{i-Installer} included in -\filename{MacOSX/II2.dmg}. -\end{enumerate} - -\noindent Each of these is described in a following section. - -In addition, \TeX{} under \MacOSX\ typically uses a ``frontend''. This -is also described below. - - -\subsection{\protect\cmdname{i-Installer}: Internet installation} -\label{sec:i-Installer} - -The \cmdname{i-Installer} is included in the \TL{} distribution as -an alternative to normal installation. It does not use the contents of -the \TL{} distribution at all; instead, the system (approximately -70 megabytes) is downloaded over the Internet. - -One advantage of \cmdname{i-Installer} is that it makes updates -relatively painless. If you are interested, please see the -\cmdname{i-Installer} \TeX{} home page at \url{http://www.rna.nl/tex.html}. - -To use it, mount \filename{./MacOSX/II2.dmg}. Read the documentation, -launch it, and install at least \texttt{TeX Foundation} and \texttt{TeX -Programs}. The first will finish without configuration, as soon as the -second is installed you will be presented with a graphical interface to -setting up your \TeX{} system. - -The \cmdname{i-Installer} distribution uses the \teTeX{} \dirname{texmf} -tree with some additions. Due to differences between \TL{} and -\teTeX{} you cannot update a \TL{} installation with an -\cmdname{i-Installer} \texttt{TeX Programs} i-Package. - - -\subsection{\protect\cmdname{install*.sh}: \protect\TL{} installation} - -In order to run the installation scripts under \MacOSX, you need to have -the \cmdname{bash} shell installed. If you are running \MacOSX~10.2 -or later, you have \cmdname{bash}, and can proceed. If you're running -an earlier \MacOSX{} version, however, the default shell is -\cmdname{zsh}, which won't work; you'll need to get \cmdname{bash} from -the Internet, or more likely upgrade your system. - -Once you have \cmdname{bash}, the Unix installation documentation in the -previous section can be followed. See section~\ref{sec:unix-install} on -\p.\pageref{sec:unix-install}; \MacOSX-specific notes are included there -where needed. - - -\subsection{\MacOSX{} frontends} - -Using \TeX{} on a Macintosh typically goes through a front end program, -comprising an execution shell, editor, previewer, and other facilities, -with a graphical interface. Here are the principal frontends: - -\begin{cmddescription} -\item [TeXShop] Included in \TL{} as \filename{./MacOSX/texshop.dmg}. - \\See \url{http://www.uoregon.edu/~koch/texshop/texshop.html}. - -\item [ITeXMac] Included in \TL{} as \filename{./MacOSX/iTM-*.dmg}. - \\See \url{http://itexmac.sourceforge.net}. - -\item [Mac-emacs] A port of Emacs to \MacOSX{}, integrating \pkgname{AucTeX}. - \\See \url{http://www.cs.man.ac.uk/~franconi/mac-emacs}. - -\end{cmddescription} - -The frontends use \dirname{/usr/local/teTeX} as the default location; -therefore, you must either install \TL{} there, or change the -configuration of the frontend. - - -\section{Windows installation} -\label{sec:win-install} - -Unfortunately, this release of \TL{} does not include a Windows -installer, due to technical difficulties. We hope that an installer -will be available again in a few months. (It is being completely -rewritten to use standard Microsoft libraries, instead of the homegrown -\filename{TeXSetup.exe}.) - -A set of experimental Windows binaries is included, nevertheless. You -can install them with the Unix \filename{install-tl.sh} script: select -the \optname{win32} system from the \optname{S} option of the top-level -menu. The \pkgname{XEmacs} package is not included, however, due to -space. - -(Meanwhile, if you are an experienced Windows programmer and would like -to help with the project, email us!) - - -\begin{comment} -\TL{} can be installed on systems running Windows 9x, \acro{ME}, -\acro{NT}, \acro{2K} or \acro{XP}. Older versions of Windows (3.1x) -and \acro{MS-DOS} are not supported. - -It is necessary to have your Windows set up so that it uses the -Microsoft Joliet extensions for reading \CD{}s; simply look at the \CD{} -in Explorer and see whether it shows long, mixed-case, file names. If it -does not, you must install the Joliet extensions. - -The Windows \TeX{} system included in \TL{} is no more and no less -than the \fpTeX{} distribution. It includes a \texttt{dvi} previewer, -\textsf{Windvi}, which is similar in usage to the established Unix -\textsf{xdvi}. The documentation can be found in -\OnCD{texmf/doc/html/windvi/windvi.html}. - -\subsection{The \texttt{TeXLive.exe} program} - -\begin{figure*} - \begin{center} - \ifnum \Status=1 - \includegraphics[width=.7\textwidth]{pictures/Welcome-to-TeXLive} - \else - \ifnum \Status=2 - \includegraphics[bb=0 0 551 534]{pictures/Welcome-to-TeXLive.jpg} - \else - \includegraphics[width=.7\textwidth]{pictures/Welcome-to-TeXLive} - \fi - \fi - \end{center} - \caption{``Welcome to \TL'' window}\label{graph:welcome} -\end{figure*} - -If your computer is configured to let the \CD{} autostart, then a dialog -box with a menu bar will popup on the screen, and you will have several -choices from there: - -\begin{itemize*} -\item Install \TeX{} on your hard disk -\item Do maintenance on your \TeX{} system. -\item Remove the \TeX{} system. -\item Use \TeX{} off the \TL{} \CD{} or \DVD{}. -\item Browse documentation: \TL{} documentation, TUG web - pages, \fpTeX web pages. -\item Run the \cmdname{TeXdocTK} application to find specific documentation. -\end{itemize*} - -If your \CD{} does not autostart, you can explicitly run the program -by double clicking on \path|bin/win32/TeXLive.exe| on the \CD{} from -the explorer window. - -\subsection{Running \protect\TL{} directly from media (Windows)} - -\runlive - -To run live under Windows, from the menu, chose \verb|Explore CD-Rom|, then -\verb|Run TeX off CD-Rom|. This will launch the \cmdname{XEmacs} editor. - -XEmacs startup file will set the environment variables needed. XEmacs will also -setup a temporary \acro{TDS} compliant texmf tree in the temporary area of your -computer. It is needed to store files that may be built on the fly, such as -\path|pk| bitmap fonts, or format files. Configuration files are copied from -the \CD{} to this texmf tree, so that you can edit them if needed. The -\path|ls-R| database is computed for this texmf tree. The AUC-\TeX{} mode will -be entered Whenever you will visit or create a \TeX{} file, providing all the -bells and whistles for \TeX{} support XEmacs is capable of. - -If you run 'M-x shell' within XEmacs, then you will have access to all the TeXLive -tools from the command line provided by XEmacs. - -\smallskip {\small\noindent \textbf{[For advanced users:]} You can also - use the small batch file \path|mkloctex.bat| to be called in a - directory \path|bin\win32| of the \CD. From the Start menu select - `Run', then browse the \acro{CD} drive and select - \path|mkloctex.bat|. Before starting it, you should add two parameters - separated by a space: the letter of your \acro{CD} drive and the - letter of the drive where you want to install the \TeX\ directory. - The whole line should read, e.g., \verb+d:\bin\win32\mkloctex.bat d c+. - When installation is complete, please read carefully the information - on screen. If you are running Windows 9x/\acro{ME}, then you will have to - restart Windows.} - -\subsection{Support packages for Windows} -\label{sec:win-xemtex} - -To be complete, a \TL installation needs support packages that are not -commonly found on a Windows machine. -Many scripts are written using the Perl language. Some important tools require -the Ghostscript \PS{} interpreter to render or to convert files. A graphic -file toolbox is also needed in some cases. Last but not least, a \TeX-oriented -editor makes it easy to type in your \TeX{} files. - -All these tools are quite easy to find for Windows, but in order to try to make -your life even easier, we have put such a set of tools on \TL: -\begin{itemize*} -\item \cmdname{Ghostscript} 7.07 -\item a minimal \cmdname{Perl} 5.8, sufficient to run all the \TL{} -Perl scripts -\item a subset of \cmdname{ImageMagick} 5.5.6 -\item the \cmdname{ISpell} checker -\item \cmdname{XEmacs} 21.5.14 with a selection of packages to support -\TeX{} typesetting. -\end{itemize*} - -These packages should be installed only all at once. The bundle is -known as the \XEmTeX{} bundle. - -If you didn't install \XEmTeX{}, \cmdname{Perl} and \cmdname{Ghostscript} are -installed anyway if they are not detected on your machine. This is because they are -required by many important tools. The \envname{PERL5LIB} and \verb|GS_LIB| -environment variables will be set too. - -When you are under -\cmdname{XEmacs}, the tools provided shadow any other version you might -have installed previously. The point here is that \path|TeXSetup.exe| -will not install anything outside of the \TL location, neither will -it run foreign installers, nor will it try to autodetect installed -products using unreliable rules of thumb. The \XEmTeX{} bundle is -standalone and is meant to evolve in the future. The reference site is -\url{http://www.fptex.org/xemtex/}. - -If you don't want to install this bundle, then you are on your own to -install the required tools to complete your \TL{} system. Here is a -list of places to get those tools: - -\begin{description} -\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} -\item[Perl] \url{http://www.activestate.com/} (but you might need some - supplementary packages from CPAN: \url{http://www.cpan.org/}) -\item[ImageMagick] \url{http://www.imagemagick.com} -\item[NetPBM] alternatively, you could use NetPBM instead of ImageMagick to - process or convert your graphic files. NetPBM home page is - \url{http://netpbm.sourceforge.net/} -\item[\TeX-oriented editors] There is a wide choice, and it is a matter of the - user's taste. Here is a selection: - \begin{itemize*} - \item \cmdname{GNU Emacs} is available natively under Windows, the - reference url is - \url{http://www.gnu.org/software/emacs/windows/ntemacs.html} - \item \cmdname{XEmacs} is available natively under Windows, the - reference url is \url{http://www.xemacs.org/} - \item \cmdname{WinShell} is available on \TL in the \path|support| - directory, the reference url is \url{http://www.winshell.de} - \item \cmdname{WinEdt} is shareware available from \url{http://www.winedt.com} - \item TeXnicCenter is available from\\ - \url{http://www.toolscenter.org} - \item \cmdname{Vim} is available on \TL{} in the - \path|support\vim| directory and the - reference site is \url{http://www.vim.org} - \item \cmdname{SciTE} is available from \url{http://www.scintilla.org/SciTE.html} - \end{itemize*} -\end{description} - -You might want to install other tools that are not free\footnote{Not -free, that is, in the sense of freedom to modify and redistribute, -following free software guidelines. This does not mean you can't acquire -them for no money.} and therefore not included on \TL{}, such as -\cmdname{GSView}, the \cmdname{Ghostscript} companion to more -conveniently view PS/PDF files. \cmdname{GSView} is available from -\url{http://www.cs.wisc.edu/~ghost/gsview/} or any \acro{CTAN} site. - -\subsection{Installing \protect\TeX\protect\ Live to disk} - -\textbf{Warning: Win9x users must ensure they have enough environment - space before undertaking installation. The \cmdname{TeXSetup.exe} - program won't change the environment size for them. A few environment - variables will be created and it is possible you run out of - environment space. Add \texttt{SHELL=COMMAND.COM /E:4096 /P} in the - config.sys file in order to increase your environment size.} - -Installation is started by letting the media autostart. The program run -is \path|TeXSetup.exe| if you are using the inst disk. If you are using -the live or the demo disk, you will have to select the item -\path|TeXLive Software| from the menu, then the subitem \path|Install on -Hard Disk|. This will invoke \path|TeXSetup.exe|. You can also find it -in the \path|bin/win32| directory and run it, if the autostart fails for -any reason. \path|TeXSetup.exe| is a Windows wizard and it will display -several pages while running. - -\begin{description} -\item[Welcome Page] - You can choose a \emph{quick} installation from - here. In this case, the installation will run without any human - assistance from beginning to end, with all the default settings - (Figure~\ref{graph:setup-src}, - \ifnum \Status = 1 - on the left% - \else\ifnum \Status=2 - at the top% - \else - on the left% - \fi\fi - ). If you have enough privileges (administrator or power user - rights) under a Windows version where this is applicable, then you can - decide to install the \TL{} for all users or for yourself only by - checking the appropriate box. - For installing the whole \XEmTeX{} bundle (XEmacs, Ghost\-script, - Perl, ImageMagick and Ispell) you can check \emph{Install XEmTeX - Support} box. - \begin{figure*}[!htb] - The \cmdname{TeXSetup} Wizard\hfill - Source directories for the \TL{} files - - \begin{center} - \ifnum \Status=1 - \includegraphics[width=.48\textwidth]{pictures/setup-wizard.jpg}\hfill% - \includegraphics[width=.48\textwidth]{pictures/source-for-texlive.jpg} - \else - \ifnum \Status=2 -\includegraphics[bb=0 0 506 403]{pictures/setup-wizard.jpg} -\includegraphics[bb=0 0 506 403]{pictures/source-for-texlive.jpg} - \else - \includegraphics[width=.48\textwidth]{pictures/setup-wizard}% - \hfill% - \includegraphics[width=.48\textwidth]{pictures/source-for-texlive} - \fi - \fi - \caption{The \TL{} setup wizard}\label{graph:setup-src} - \end{center} -\end{figure*} -\item[Source Page] - This page is a bit complex. It will allow you to select two source - directories for your \TL{} system - (Figure~\ref{graph:setup-src}, - \ifnum \Status = 1 - on the right% - \else\ifnum \Status=2 - at the bottom% - \else - on the right% - \fi\fi - ). You will need a \emph{local - source directory} and possibly a \emph{remote source directory}. - -Why do we need both these directories? The files consisting of the -\TL{} system are on the \CD{}, of course, but some other useful -packages are not, either because of space lacking or because their -license was not compatible with \TL{}. You need to enable Internet -downloading if you want to install these packages that are marked with a -specific ``remote'' icon. - - However, don't panic: the default parameters of the setup will allow - you to install a full system using the \CD{} only. Simply, you won't - have \file{WinEdt} (for example), but you will be able to install it - later. - - So you can take your files from: - \begin{itemize} - \item the \CD{} or any similar flat tree of files, available through - some standard directory (this means the \CD{} can be mounted on - some remote machine and be made available through network - sharing), - \item a set of \file{.zip} files (this is the case when you are - installing from the demo \CD{} or the \fpTeX{} distribution), - \item the Internet; in this case, the program takes care of - downloading the \file{.zip} files it needs for you. - \end{itemize} - This option is available only if you enable Internet file - downloading in the right part of the page. You also need to - configure this Internet access by selecting to connect either using - Internet Explorer~5 \file{wininet.dll}, or using a direct connection (\texttt{ftp}, - \texttt{http}). -% or using a proxy server. -% Last, you can be assisted in defining the \emph{local source -% directory} and \emph{remote source directory} which will be used -% to copy the files onto your hard disk. The \texttt{browse} buttons -% allow to select a directory for the former, and an url among a list -% of mirrors for the latter. -\item[Root Page] - On this page, you will tell where you want the files to be - installed (Figure~\ref{graph:root-schm}, - \ifnum \Status = 1 - on the left% - \else\ifnum \Status=2 - at the top% - \else - on the left% - \fi\fi - ). Only the root directory really matters, the other ones - are set according to the root one. You may want to make - \path|$TEXMFEXTRA| point to some TDS compliant directory with other - \TeX{} files or assign a different value to - \path|$HOMETEXMF|, which is set by default to whatever Windows think - is your `HOME' location. -\begin{figure*}[!htb] - Root and directories\hfill% - Scheme selection - \begin{center} - \ifnum \Status=1 - \includegraphics[width=.46\textwidth]{pictures/root-of-installation.jpg}\hfill% - \includegraphics[width=.46\textwidth]{pictures/scheme-selection.jpg} - \else - \ifnum \Status=2 -\includegraphics[bb=0 0 506 403]{pictures/root-of-installation.jpg} -\includegraphics[bb=0 0 506 403]{pictures/scheme-selection.jpg} - \else - \includegraphics[width=.46\textwidth]{pictures/root-of-installation}% - \hfill% - \includegraphics[width=.46\textwidth]{pictures/scheme-selection} - \fi - \fi - \caption{\TL-Setup: Root and directories / Schemes}\label{graph:root-schm} - \end{center} -\end{figure*} -\item[Get TPM Page] - This page does not require any manual intervention. The \file{.tpm} - files which describe collections and packages are retrieved - (possibly from the Internet), unzipped if needed and parsed. -\item[Schemes Page] - On this page, you will select the global scheme of your - installation (Figure~\ref{graph:root-schm}, - \ifnum \Status = 1 - on the right% - \else\ifnum \Status=2 - at the bottom% - \else - on the right% - \fi\fi - ). A scheme is a large set of files targeted at some kind - of usage. There are 3 generic schemes for basic, recommended and - full installation. The other ones are devoted to LUGs (what GUST or - GUTenberg propose for their members) or applications (XML and - \TeX{}). - When a scheme is selected, it is still possible to refine the - selection by checking the appropriate box. If doing so, you will be - presented the packages page to change your selection, else you will - jump to the review page. -\item[Packages Page] - Collections and packages are presented in a tree form - (Figure~\ref{graph:win32-support}, - \ifnum \Status = 1 - on the left% - \else\ifnum \Status=2 - at the top% - \else - on the left% - \fi\fi - ). The links - in the tree are dependency links. Collections \emph{depend on} - packages and maybe other collections, and it is the same for each - package. You can select any package or collection individually, but - your request will be granted only if the object is not requested by - another one which is selected. For example, you can't deselect - \texttt{tex-basic} without deselecting all the collections that - request it. - - The \texttt{tex-xemtex} collection displayed on the picture is Win32 specific. It - holds a number of bonus packages (Figure~\ref{graph:win32-support}, - \ifnum \Status = 1 - on the right% - \else\ifnum \Status=2 - at the bottom% - \else - on the right% - \fi\fi - ) which can be installed - automatically and individually: Ghostscript (the \PS{} - interpreter), XEmacs editor preconfigured for \TeX{}, tools like Perl, - ImageMagick, Ispell. \emph{None of these packages are selected by - default}. - - On this page, you also have the information about disk space - needed, for each object, and for the set of those who are selected, - and also the disk space available on the partition selected for the - installation. Last, you can choose to install or not the - documentation files and source files associated with each package. -\item[Review Page] - You will find there a summary of your choices - (Figure~\ref{graph:review}, - \ifnum \Status = 1 - on the left% - \else\ifnum \Status=2 - at the top% - \else - on the left% - \fi\fi - ). It is still possible to - go back to change them. -\begin{figure*}[!htb] - Packages Page\hfill% - Win32 Support - \begin{center} - \ifnum \Status=1 - \includegraphics[width=.48\textwidth]{pictures/package-selection}\hfill% - \includegraphics[width=.48\textwidth]{pictures/win32-support} - \else - \ifnum \Status=2 -\includegraphics[bb=0 0 506 403]{pictures/package-selection.jpg}\hfill% -\includegraphics[bb=0 0 506 403]{pictures/win32-support.jpg} - \else - \includegraphics[width=.48\textwidth]{pictures/package-selection}% - \hfill% - \includegraphics[width=.48\textwidth]{pictures/win32-support} - \fi - \fi - \end{center} - \caption{Packages Page / Win32 goodies} - \label{graph:win32-support} -\end{figure*} -\item[Files Copy Page] - The selected files are copied on your hard disk (Figure~\ref{graph:file-copy}, - \ifnum \Status = 1 - on the right% - \else\ifnum \Status=2 - at the bottom% - \else - on the right% - \fi\fi - ). All the files not - yet available on your local disk are first downloaded from the - remote source directory on the Internet. Then every package is - unpacked (if \path|.zip| files), or copied from the \CD{}. -\item[Configuration Page] Several packages need some configuration - step to make them usable (Figure~\ref{graph:configuration}, - \ifnum \Status = 1 - on the left% - \else\ifnum \Status=2 - at the top% - \else - on the left% - \fi\fi - ). Also the \TL{} system needs some post-processing step - (format files generation, ls-R databases generation, environment - variables, etc.). All these operations are done there, some of them - can be lengthy. -\begin{figure*}[!htb] - \textbf{Review Page}\hfill% - \textbf{File Copy Page} - \begin{center} - \ifnum \Status=1 - \includegraphics[width=.48\textwidth]{pictures/review-settings}\hfill% - \includegraphics[width=.48\textwidth]{pictures/file-copy} - \else - \ifnum \Status=2 - \includegraphics[bb=0 0 506 403]{pictures/review-settings.jpg}\hfill% - \includegraphics[bb=0 0 506 403]{pictures/file-copy.jpg} - \else - \includegraphics[width=.48\textwidth]{pictures/review-settings}\hfill% - \includegraphics[width=.48\textwidth]{pictures/file-copy}% - \fi - \fi - \end{center} - \caption{Review Page / File Copy Page} - \label{graph:review}\label{graph:file-copy} -\end{figure*} -\item[Final Page] The installation being over, you may want to display - the Windows specific documentation (HTML format) and / or the log - file of the setup process (Figure~\ref{graph:final} - \ifnum \Status = 1 - on the right% - \else\ifnum \Status=2 - at the bottom% - \else - on the right% - \fi\fi - ). If it is needed (Win9x/WinME), you will - be asked to reboot your computer. -\end{description} - -\begin{figure*}[!htb] - \textbf{Configuration Page}\hfill% - \textbf{Final Page} - \begin{center} - \ifnum \Status=1 - \includegraphics[width=.48\textwidth]{pictures/configuration}\hfill% - \includegraphics[width=.48\textwidth]{pictures/congratulations} - \else - \ifnum \Status=2 - \includegraphics[bb=0 0 506 403]{pictures/configuration.jpg}\hfill% - \includegraphics[bb=0 0 506 403]{pictures/congratulations.jpg} - \else - \includegraphics[width=.48\textwidth]{pictures/configuration}\hfill% - \includegraphics[width=.48\textwidth]{pictures/congratulations}% - \fi - \fi - \end{center} - \caption{Configuration Page / Final page} -\label{graph:configuration}\label{graph:final} -\end{figure*} - -Please be aware that the choice of cluster size on DOS disk -partitions can radically affect the size of your \TeX\ -installation. The support tree has hundreds of small files, and it is -not unusual for a complete installation to take up to four times the -amount of space used on the \CD. - -\end{comment} - - -\section{Windows maintenance and post-installation} - -Although this version of \TL{} cannot be installed on Windows, enough of -this section is relevant to existing installations or cross-mounted -installations that it seemed worth leaving in. - -It will be thoroughly updated when a complete \TL{} Windows distribution -is released. For now, please ignore references to -\filename{TeXSetup.exe}, etc. - - -\subsection{What's different in Windows?} - -The Windows version of \Webc{} has some specific features that should be -pointed out. - -\begin{description} -\item[\KPS{}] The hash-tables that \KPS{} builds are quite large for - the \TL{}. In order to cut down the starting time of any - \KPS{}-enabled program, these hash-tables have been put in shared - memory. This way, when you chain the execution of several such - programs, like \path|tex| calling \path|mpost| calling \path|tex|, - the overhead when starting each of the subprograms is - reduced. This change is hidden to the user, except if you set the - debug flag of kpathsea to the \path|-1| value: you will then trace - access to the shared memory, which is not what you want (it is - accessed very often!). What is useful in a log trace of the shared - memory access is still to be defined, so the situation might evolve - in the future. -\item[\cmdname{kpsecheck}] This command provides some options that did - not fit well into \cmdname{kpsewhich}. It will allow you to list all - the files that occur multiple times across your texmf trees. This - could be handy, but most of the time you will also get unwanted - output (like dozens of \path|README| files)\footnote{It is noticeable - that all these files result in clashes inside the \KPS{}-hashing - mechanism; fortunately, \KPS{} never looks for these files.}. For - this reason, you can combine the \path|-multiple-occurrences| with 2 - other options for including or excluding any filename that match - some pattern (you can request for several patterns). - - The \cmdname{kpsecheck} command will also report the status of shared - memory: in use or not used. That might be useful to know because if - the status reported is \samp{in use}, that means one or several - processes are working, and the effect of any \cmdname{mktexlsr} - command will be delayed until the next time where no \KPS{} linked - process will be running. - - Last, this same command will report about the location it thinks - Ghostscript can be found. Under Win32, for many programs, it is - easier to use the Ghostscript dll, and find it by using the - Ghostscript registry key than to change the \path|PATH|, which has a - limited length anyway. -\item[\Webc{}] The engines have a few more options than in Unix - \Webc{}, and one option with a different behavior: - \begin{itemize} - \item \path|-halt-on-error| stop the compilation at the first error. - \item \path|-job-time| set the job time to the same timestamp as the - file given in argument. -\item \path|-oem| use the DOS codepage for console output. - \item \path|-output-directory| allow to write all the output files in the - specified directory. - \item \path|-time-statistics| print statistics about the job run - time. It is to be noted that Win9x not being a true multitasking - operating system, it has no reliable timer for short periods, so - the value printed is an approximation. Under NT/2K/XP, the result - is quite accurate with user time and system time values allocated - for this run. For Unix - users: the \path|time| command is not usually available to Windows - users. - \end{itemize} -\end{description} - -\subsection{Adding packages to your installation} - -You will find an option in the \guiseq{TeXLive} menu (or go to -\guiseq{Start\arw Programs \arw TeXLive \arw Add TeX package} menu) to -run \file{TeXSetup.exe} in maintenance mode. The steps are almost the -same as in the initial installation. - -We'll discuss differences below, but first, whatever changes you make, -\textbf{do not forget to rebuild the ls-R database files}. Otherwise, -your new files will not be found. You can do this either via the -\acro{GUI} (\guiseq{Start \arw Programs \arw TeXLive \arw Maintenance -\arw Rebuild ls-R}), or manually running the \file{mktexlsr} command. - -The main difference is in the packages selection page. In maintenance -mode, the list of installed packages is compared to the list of packages -available from your source directories. Packages that are not installed -will be displayed in green, out of date packages will be displayed in -red and up-to-date, installed packages are displayed in black. - -This way, you can choose to add or upgrade components, either from -\TL{} or from the Internet, where you are likely to find some more -recent version of your packages. - -It is up to you to select which packages you want to install. The rest -of the process is similar to the first installation. - -If you want to add files that are not provided by the \TL{} (or -\fpTeX{}) distribution, it is recommended to put them in the -\path|$TEXMFLOCAL| directory. This way, you will be safe against -upgrades of the \TL{} software. - -The directory pointed to by \path|$TEXMFLOCAL| is initially empty. If, -for example, you want to add the support file for the Maple symbolic -computation program, you will have to put the style files in:\\ -\path|c:\Program Files\TeXLive\texmf-local\tex\latex\maple\|\\ and the -documentation files in:\\ \path|c:\Program -Files\TeXLive\texmf-local\doc\latex\maple\| - -\subsection{Uninstalling \protect\TL{}} - -The uninstall procedure is available either from the \file{TeXLive.exe} -program, from the \path|TeXLive| menu or from the control panel -(\guiseq{Start \arw Control Panel, Add/Remove Programs}). This procedure -will cleanup your hard disk of most of the \TL{} files. However, -\TeX{} is a system that is creating files and there is no mechanism to -keep track of all of them. Moreover, Win32 support packages have their -own uninstall procedure, which you will have to run separately (provided -you want to get rid of them). Last, the files you may have stored in -\path|$TEXMFLOCAL| won't be removed. So, even if the vast majority of -files are automatically removed by the uninstall procedure, you will -have to do some manual cleanup to actually remove all of them. - -\subsection{Running \texttt{TeXSetup.exe} from the command line} - -The \path|TeXSetup.exe| program has a number of other useful -options. You can get the list by running: -\begin{verbatim} -c:\>TeXSetup --help -\end{verbatim} - -Here is the description: -\begin{description} -\item[\path|--automatic-reboot|] reboot without waiting user - confirmation once installation is over; -\item[\path|--dry-run|] do nothing, just log everything that will be - done without this option; -\item[\path|--quick|] use the recommended installation and default - directories, ask nothing up to rebooting; -\item[\path|--with-xemtex|] selects the \XEmTeX{} bundle; -\item[\path|--net-method (=ie5/direct)|] enable to download components with - restricted licenses from the Internet (either using direct - connection of Internet Explorer 5 DLLs): you need to have an available - network connection and some of the packages are huge; -\item[\path|--remote-source-directory |] this is the base url for the remote packages; -\item[\path|--local-source-directory |] by default, \path|TeXSetup.exe| - will guess the root directory of the set of files you want it to act on, if you ever - upgrade \path|TeXSetup.exe|, you won't be able to copy the new version - onto your \CD{}, so you will need to use this option to specify the - root of the \CD{}; -\item[\path|--installation-directory |] this is the root of your - installation, all files will be copied under this location. The - default value is \verb+c:\Program Files\TL+; -\item[\path|--texmfmain-directory |] -\item[\path|--texmflocal-directory |] -\item[\path|--texmfextra-directory |] -\item[\path|--texmfhome-directory |] -\item[\path|--vartexmf-directory |] -\item[\path|--vartexfonts-directory |] these are the directories - used to configure the location of your files. They map directly to - the \path|texmf.cnf| variables. -\item[\path|--with-source-files(=yes/no)|] copy the source files - for \TeX{} packages, default value is no; -\item[\path|--with-documentation-files(=yes/no)|] copy documentation files for \TeX{} - packages. Default value is yes. Beware: this is only documentation about specific - packages, general documentation will be installed anyway; -\item[\path|--program-folder |] the name of the folder under - which you will find the menus; -\item[\path|--add-package |] this is used to add or update a specific - package after a first regular installation; -\item[\path|--scheme |] install the named scheme instead of the - default \path|texlive-recommended| scheme; -\item[\path|--maintenance|] mostly the same as \path|--add-package| - without specifying a package to add; -\item[\path|--uninstall|] this option will remove anything \TeX{} related coming from - the \CD{}, which means there can be files left if you added style - files or format files, and also that supplementary tools will not be - removed. This option is still a bit crude in this release; -\item[\path|--help|] this option opens up a box with the list of options. -\end{description} - -\subsection{Network installation} - -\KPS{} knows about UNC names, so you can use them to get your TEXMF -tree from the network. But there is better than this. -All the support files and configuration files, everything except the files in the -\path|bin/win32| are shareable with a \teTeX{} or Unix \TL{} installation. That means -you can use Samba either to mount from an NT server to a Unix -workstation or the converse. Several strategies are possible: -\begin{itemize} -\item Put everything on the server. Just add each set of files for the os and -architecture you want to use in the \path|bin| directory. That means -for example \path|bin/win32| and \path|bin/i386-linux|. Next configure -your main variables. You can use UNC names to -point to the right directories under Win32. -\item Install a local copy for the binaries and format files. In this - case, assign \path|$TEXMFMAIN| to the main \path|texmf| tree that - will be accessed remotely. Set \path|$VARTEXMF| to be a local - directory which will hold local configuration files and on-the-fly - generated files. -\end{itemize} - -\subsection{Personal configurations} - -\subsubsection{Dvips} - -The configuration file for dvips can be found in\\ -\verb+C:\Program Files\TeXLive\texmf-var\dvips\config\config.ps+\\ -You may open it with any editor - %(\cmdname{WinShell} will do fine) - and change some parameters: - -\begin{description} -\item [fonts] you can change the default printer \MF{} mode or printer - resolution in case \cmdname{dvips} needs to generate PK fonts. By default it - is configured to use Type~1 versions of the CM fonts, so it should - not call \cmdname{mktexpk} too often; -\item[printer] you can tell dvips where you want to print by default. If - the \optname{o} option is not followed by a printer name, then a - \file{.ps} \PS{} file is written. You can give dvips a printer - name such as: -\begin{verbatim} -o lpt1: -% o | lpr -S server -P myprinter -% o \\server\myprinter -\end{verbatim} -\item[paper] Next, you might want - to change the paper size from European (A4) to US letter - by making the US letter the first paper size mentioned in the file. - Scroll to the group of lines beginning with \code{@}. Move - the appropriate lines so that this section begins with the lines:\\ -\hspace*{1em} @ letterSize 8.5in 11in\\ -\hspace*{1em} @ letter 8.5in 11in\\ -\hspace*{1em} @+ \%\%BeginPaperSize: Letter\\ -\hspace*{1em} @+ letter\\ -\hspace*{1em} @+ \%\%EndPaperSize -\end{description} - -The current \TL{} distribution implements the procedure of making -always up-to-date fontmaps files for Dvips and Pdftex. This is done by -the \cmdname{updmap} program during installation, as well as during any -font package addition. If you add new packages by hand, edit the file -\verb+updmap.cfg+ in \path|$VARTEXMF/web2c|. - -\subsubsection{Pdftex} - -If you use the program pdf{}latex to write \acro{PDF} format directly, -and you are using \acro{US} letter-size paper, edit the file -\verb+C:\Program Files\TeXLive\texmf-var\tex\generic\config\pdftexconfig.tex+ and -change \samp{\bs pdfpagewidth} and \samp{\bs pdfpageheight}. These entries should read: -\begin{alltt} -\bs{}pdfpagewidth=8.5 true in -\bs{}pdfpageheight=11 true in -\end{alltt} -Save the file and exit the editor. - -\subsubsection{GSView} -GSView is now distributed under the Aladdin License, and therefore is no longer included in -\TL{}. - -If you may want to change the page size to US letter size. If so, open -GSView from the \guiseq{Start} menu, and select \guiseq{Media\arw Letter}. - -Also, there are menu settings that are supposed to give you the most -readable screen image. On \guiseq{Media \arw Display Settings}, set both -\optname{Text Alpha} and \optname{Graphics Alpha} to 4~bits. - -Note that the installation process has set all \code{.ps} and -\code{.eps} files to automatically open with \cmdname{GSView}. - -For printing instructions, see section~\ref{printing} below. - -\subsubsection{WinDvi} -\label{sub:windvi} - -The \file{TeXSetup.exe} program takes care of associating the files -with the \file{.dvi} extension with \file{Windvi}. - -Open it with \guiseq{Start\arw Programs\arw TeXLive\arw DVI Viewer}. - -You can set it for US letter-size paper by going to \guiseq{View\arw -Options\arw Papertype} and selecting US (8.5\verb+"+ x 11\verb+"+) (and -then \optname{OK}. Exit \cmdname{windvi}. - -You can change other parameters from there as well, such as the ability -to execute system commands specified by the document (disabled by -default for security reasons). Also, the first time you view any .dvi -file, you may find the magnification too large. Zoom out until you get -an appropriate size. - -%There are two important parameters related to printing that can't yet -%be set from the dialog boxes, namely the resolution and the \MF{} mode -%for the printer. You can set them once for all by specifying them on -%the command line: -%\begin{verbatim} -%c:\>windvi -p 360 -mfmode canonbjc foo.dvi -%\end{verbatim} -%When you will exit Windvi, these parameters will be stored in the -%configuration file. The available modes are found in this file:\\ -%\path|c:\Program Files\TeXLive\texmf\metafont\misc\modes.mf| - -All configuration settings for \cmdname{Windvi} are stored in a file -named \path|windvi.cnf| file. You can find it by running this command at -the prompt: -\begin{verbatim} -c:\>kpsewhich --expand-var $HOME/windvi.cnf -\end{verbatim} - -Should you have problems with \cmdname{Windvi}, please remove the configuration -file and test your problem against a vanilla configuration. - -\subsection{Testing} - -For generic verification procedures, see section~\ref{sec:test-install} -(\p.\pageref{sec:test-install}). This section describes -Windows-specific tests. - -Open the file \verb+sample2e.tex+ in your editor (Xemacs, WinShell), -found in \path|C:\Local\TeX\texmf\tex\latex\base|. The \LaTeX\ source -should appear on the screen. Process it by clicking on the -\guiseq{Command\arw LaTeX} menu (XEmacs) or \LaTeX\ icon on the toolbar -(WinShell), then view it by clicking on the \guiseq{Command\arw View DVI} -menu (XEmacs) or Preview (Windvi) icon (WinShell). - -At first, when you preview files with Windvi, it will create fonts because -screen fonts were not installed. After a while, you will have created most -of the fonts you use, and you will rarely see the font-creation window. - -\textbf{Hint for the future:} If a \LaTeX\ run stops because \LaTeX\ -cannot find a file, you can press Ctrl-z to quit. - - -\subsection{Printing} -\label{printing} - -It is possible to print from Windvi. In this case, printing will be done -using the Windows unified printer driver. By definition, it is -compatible with all printers. However, there is some drawback: it can -generate some huge spool files, and some (older) versions of Windows -just don't like them. The advantage is that you can use features like -embedding BMP or WMF images. You also need to make sure that the printer -parameters are correctly set (subsection~\ref{sub:windvi}), else you -will get scaled printing (printing at 600\dpi{} on a 300\dpi{} printer -will give you only one quadrant of your page). - - -Printing is faster and more reliable if you run \cmdname{dvips} to make -a \filename{.ps} file and then print from \cmdname{GSView}. In -\cmdname{GSview}, select \guiseq{File\arw Print\ldots}. A \guiseq{Print} -window will appear. - -If you are using a \PS{} printer, \textit{be sure to select -\guiseq{\PS{} Printer}}. This is done in the \guiseq{Print Method} box -at the bottom left of the \guiseq{Print} window. You can then select any -of the printers that you have previously installed. If you fail to -check the box for \optname{\PS{} Printer}, printing will not work. - -If you will be using your own non-\PS{} printer, select -\guiseq{Ghostscript device} in the \guiseq{Print Method} box, then click -on the button to the right labelled \guiseq{djet500} and select your -printer type from the list that pops up. (In the older version of -\cmdname{GSView}, make sure \optname{\PS{} Printer} is \textit{not} -selected, then select your printer type from the \guiseq{Device} list.) - -\subsection{Tips and tricks for Win32} - -\subsubsection{Different flavors of Win32} - -What we call Win32 is not an operating system by itself. It is a large -set of functions (around 12,000 in the header files of the Microsoft -\acro{SDK}) that you can use to write programs for different operating -systems of the Windows family. - -Windows comes in different flavors: -\begin{itemize} -\item Win95, Win98 and Win\acro{ME}, which \emph{are not true multitasking, - multithreading} environments. They are the latest\Dash and hopefully - last\Dash metamorphosis of \acro{DOS}. This can be more or less proven - by the fact that when booting, the PC will load the \path|command.com| - interpreter, and if you stop the boot process at this point, you can - ask for the current (\acro{DOS}) version and it will answer something - like \samp{MS-DOS 7.0} (at least for the old versions of Win9x). -\item Windows \acro{NT}, which is a new operating system written from - scratch, capable of true multitasking behavior, and including many - high level features. -\item Windows 2000, based on \acro{NT}, with all the bells and - whistles of Win98. -\item Windows \acro{XP}, which comes with Personal and Pro flavors. This is - the last step in merging both lines of products (Win9x based and - \acro{NT} based). \acro{XP} is based on \acro{NT}. -\end{itemize} - -Win9x are able to run 32~bits programs and 16~bits programs -concurrently. But the operating system by itself is not entirely -written in 32~bits mode, and does not support memory protection: 16bits -applications can overwrite parts of the operating system memory! Some -parts of the system like the \acro{GDI} (Graphical Device Interface) -manage limited resources like bitmaps, fonts, pens and so on for the set -of all programs that run concurrently. All the bitmaps headers available -at the same time can't amount for more than 64kB. This explains the -performance tool and the fact that you can put your system on his knees -by making intensive use of graphic objects for example. - -NT, 2K and XP do not suffer from these limitations, and neither from -other Win9x limitations. They are true multitasking environments, with -protected memory. They are much more responsive than Win9x because -of better memory management, better file system and so on. - -\subsubsection{Command line prompt} - -You may wonder, ``Why would I need to use a command line prompt when -I have Windows?'' - -Good question. The problem is of very general nature. Not all operations -can be done easily using only a \acro{GUI}. Command line gives you -programming power\Dash assuming a clever command interpreter. - -But the problem here is more fundamental: \TeX{} is \emph{a batch} -tool. Not an interactive one. \TeX{} needs to compute the best -layout for each page, resolve cross-references and so on. This can be -done only by a global processing of the document. It is not (yet) a -task that can be done interactively. - -This means that you should use \TeX{} from a command line. In fact the -situation is not so bad. There is an advantage to write command line -tools for complex processing: they are better debugged, because they are -independent of any \acro{GUI} problems, and \acro{GUI} tools can be -designed to interface to the command line tools. This is the case for -\TeX{}, where you will mostly interact with it through a \acro{GUI} text -editor. - -However, you may need to use the command line prompt in a number of -situations. One is when you are having difficulties and want to debug -your setup. - -\begin{description} - \item[Win9x] You can open a command line prompt by looking either for - the \acro{MS-DOS} icon in the \guiseq{Start\arw Programs} menu, - or by choosing \guiseq{Start\arw Run} menu typing in - \path|command.com| as the progrm name. - \item[NT, 2K, XP] You can open a command line prompt by looking for - \guiseq{Command Prompt} in the \guiseq{Start\arw Accessories} menu. - You can also choose \guiseq{Start\arw Run} and type in - \path|cmd.exe|, which is the name of the brand new command - interpreter for \acro{NT} (thus, it is untrue to call this a - \emph{DOS} box!). -\end{description} - -These locations may change across different Windows versions. - - -\subsubsection{Path separators} - -The Win32 API understands both \path|/| and \path|\| characters as PATH -separators. But the command interpreters do not! So whenever a path name -is used programmatically, you can use both separators, and even mix them -up in the same path name. But on the command line, you must type -\path|\| as path separator. The reason is compatibility: the command -processor used \samp{/} to introduce arguments to commands. - -All this to say: do not be surprised to read path names written using -the Unix convention; \fpTeX{} is a port of \Webc, and aims to be compatible -across platforms. For this reason, all the configuration files that -need to specify path names use the Unix convention. - -\subsubsection{File systems} -\label{sec:clusters} - -The worst feature of Win9x with regard to \TeX{} is probably the -so-called FAT file system. \TeX{} uses very many small files, with size -around 1--3kB. The \acro{FAT} file system is old, and predates by -decades the multi-gigabytes hard disks we have today. As a result, it -cannot manage efficiently the tens of thousands of \TeX{} files found in -\TL{}. The \acro{FAT} file system allocates a minimum of 32kB for -\emph{any} file on a huge partition. It means that \TeX{} will use much -more disk space than it actually needs. - -The other, more modern, file systems available, \acro{FAT32} and -\acro{NTFS}, do not have this drawback. They manage clusters of 4kB -only. (You can lower the limit to 512 bytes on \acro{NTFS}.) - -\subsubsection{How to add some directory to your PATH} - -There are pairs of variables and values which behave much like global -variables inside your programs. The set of those variables is called the -environment. Each program is initialized with a copy of the -environment when it is run. It can request and change the -value of any variable. The changes happen in the copy of the -environment, and is not at all propagated to the other running -programs. - -Your PATH is a special environment variable used to search for -programs you want to run. -There is a different procedure to change it for Win9x, WinME and NT/2K/XP: - -\begin{description} -\item[Windows 95/98] Edit your \path|autoexec.bat|. In this file should be a line - starting with \texttt{PATH=} and followed by a list of directories separated - by \path|;|. Please add the directory with the executables in this line. - After this, this line could look as follows: -\begin{verbatim} -PATH=c:\windows;c:\windows\system;c:\"Program Files"\TL\bin\win32 -\end{verbatim} -\item[Windows ME] You need to run the special program - \path|c:\windows\system\msconfig.exe| to be able to change any - environment variable. From this program, select the `Environment' - tab, and then add or modify the variable you want. You will be asked to reboot the - machine upon any change. -\item[Windows NT/2K/XP] - Click left on \guiseq{Start \arw Settings \arw Control Panel}. Now the - window with the control panel icons opens. Double click on System. The - System Properties window opens. Click on the tab \textsf{Environment} - or look for a button named \guiseq{Environment Variables} among the - dialog boxes. Now you can change the environment variables for your - user account. Note: There are also displayed the environment settings - for the system. Normally, you can't change the system variables - unless you have administrator rights on your machine. If you want to - change the \texttt{PATH} for all users, you will have to contact your - system administrator or be the system administrator yourself\Dash in - the latter case you should know what you are doing. - - If there is already a \texttt{PATH} setting for your user account, - left click on \texttt{PATH}. In the field \textsf{Variable} appears - \texttt{PATH} while the field Value shows the current setting of - \texttt{PATH} as a list of directories separated by \path|;|. Add - the directory where the executables are located (e.g. - \path|c:\Program Files\TeXLive\bin\win32|). If there isn't a \texttt{PATH} variable - for your user account, simply click in the field Variable and type - in \texttt{PATH}, click in the field \textsf{Value} - and type in the directory with the executables. Important: Click on - the \textsf{Apply} button before clicking \textsf{Ok}, otherwise the - changes to \texttt{PATH} won't apply to your system. Be careful when - changing the environment settings. -\end{description} - -The best way to be sure that a variable has been properly set is to -open a console and type: -\begin{verbatim} -set VARIABLE -\end{verbatim} -which should return the corresponding value. - -\subsubsection{\TeX{} engines} - -If you have a look at the \Webc{} documentation, you will read that all -the various \TeX{} derived programs use the same base engine. For -example, \path|tex.exe| and \path|latex.exe| are exact copies of the -same program, but each one will use a different format file, based on -its calling name. - -Under Unix, this feature is implemented through \emph{symbolic -links}. It saves up a bit of disk space, because some engines are -used with many different format files. - -The Win32 API does not know about file links. So to save up almost -the same amount of memory, all the \TeX{} base engines have been put -in DLLs (\emph{Dynamic Linked Library}). This means that you will have -the following layout: -\begin{alltt} -13/05/2002 17:06 3 584 latex.exe -13/05/2002 17:06 266 240 tex.dll -13/05/2002 17:06 3 584 tex.exe -\end{alltt} -and the \path|latex.exe| file is nothing but a rough copy of -\path|tex.exe| using the same core \path|tex.dll|. -The same trick has been used for the \path|mktex*.exe| family of programs which are -linked to the \path|mktex.dll| library. - -In fact, a generic tool called \path|lnexe.exe| is provided to build the -equivalent of Unix hard links for executable files only under Win32. - -\subsection{In case of problems} -\label{sec:troubleshooting} - -\subsubsection{What to do if \texttt{latex} does not find your files?} - -\begin{itemize} - -\item \cmdname{kpsewhich} is the tool of choice to debug any -problem. Unfortunately, \cmdname{kpsewhich} outputs debug information -to stderr, and the Windows console does not know how to redirect stderr -to a file\footnote{Well, NT and Win2k consoles know how to do that. But -the trick will work for any console.}. For diagnostic purposes you can -temporarily set an environment variable (in a \acro{DOS} box): - -\begin{verbatim} -SET KPATHSEA_DEBUG_OUTPUT=err.log -\end{verbatim} -You can also set the debug level: -\begin{verbatim} -SET KPATHSEA_DEBUG=-1 -\end{verbatim} - -If you want to redirect stderr to stdout, which is not possible -Windows, then do: -\begin{verbatim} -SET KPATHSEA_DEBUG_OUTPUT=con: -\end{verbatim} -This way you can capture both stdout and stderr in the same file. - -\item Assuming the installation has been done in \path|c:/Program Files/TeXLive|, check - the following values: \\ - {\small - \begin{tabular}{ll} - \path|kpsewhich -expand-path $SELFAUTOPARENT| & \path|c:/Program Files/TeXLive| \\ - \path|kpsewhich -expand-path $TEXMF| & \path|c:/Program Files/TeXLive/texmf| \\ - \path|kpsewhich -expand-path $TEXMFCNF| & - \path|.;c:/Program Files/TeXLive/texmf/web2c;| \\ - & \path|c:/Program Files/TeXLive/bin/win32;| \\ - & \path|c:/Program Files/TeXLive/bin;| \\ - & \path|c:/Program Files/TeXLive| \\ - \path|kpsewhich -expand-var $TEXINPUTS| & \path|.;c:/Program Files/TeXLive/texmf/tex//| - \end{tabular} -} -\item If you have other \TeX{}-related values already set in your - environment, please, remove them. They are overriding the ones in - texmf.cnf. -\item Check the values from:\\ -{\small - \begin{tabular}{ll} - \texttt{kpsewhich cmr10.tfm} & \path|c:/Program Files/TeXLive/texmf/fonts/tfm/public/cm/cmr10.tfm|\\ - \texttt{kpsewhich latex.fmt}& \path|c:/Program Files/TeXLive/texmf/web2c/latex.fmt| - \end{tabular} -} -\item At this point, if everything is correct, \TeX{} and friends - should work. If it is not the case, you will need to play with - the \path|-debug=n| option from \path|kpsewhich|, and check back all - the values. Try to identify and report the problem. -\end{itemize} - -\subsubsection{What to do if your setup still does not work as expected?} - -Here are several questions to investigate: - -\begin{enumerate} -\item Is \file{tex.exe} in my \path|PATH|? - -\item Is the \path|TEXMFCNF| variable correctly set to -\path|c:/Program Files/TeXLive/texmf-var/web2c| (default value)? - -\item Are there any errors in the log file generated by the -\file{TeXSetup.exe} program? You can find this by searching for the -string \samp{Error}. - -\item Are there any relevant bug fixes at \url{http://tug.org/texlive/}? -(Unlikely, but it doesn't hurt to check.) - -\item Check the web pages at -\url{http://www.fptex.org/}, or consider subscribing to the \fpTeX{} -mailing list, via \url{http://tug.org/mailman/listinfo/fptex}. - -\end{enumerate} - - -The \TL{} software consists of hundreds of programs and tens of -thousands of files, all from varying sources. So it is quite difficult to -predict all possible causes for problems. Nevertheless, we will do our -best to help you. (See section~\ref{sec:help}, \p.\pageref{sec:help}.) - - -\subsection{Compiling the source files} - -The whole set of source files is available in the distribution as the -\path|source/source.tar.bz2| archive, together with a separate source -archive for Windows. To be able to compile the whole distribution for -Windows, you will need: - -\begin{itemize*} -\item Windows 2K/XP -\item Microsoft Visual Studio .Net 2003 -\item a set of Unix tools (\texttt{sed}, - \texttt{grep}, \texttt{gawk}, etc.) and also Perl, Flex and Bison, -\item to adjust the paths in the - \path|win32/make/common.mak| file according to your installation -\item to adjust the paths in the Perl script file - \path|win32/perl/build.pl|, -\item run the compilation from the \path|mswin32/| directory using this - command: -\begin{verbatim} -c:\texlive\source\mswin32>perl ./perl/build.pl --install --log=install.log -\end{verbatim} -\end{itemize*} - -There is a lot of work to do to make this process easier and cleaner. - -\subsection{Where to get more information} - -The Windows \TeX{} system included on \TL{} is also known as -\fpTeX. The packaging differs, but \fpTeX{} is no more no less than the -current \TL\ release for Windows. - -The \fpTeX{} home page is \url{http://www.fptex.org}. - -The current \fpTeX release is available from any \CTAN site in -\url{htp://www.ctan.org/tex-archive/systems/win32/fptex}. - -The main ftp site for \fpTeX\ is \url{ftp://ftp.dante.de/pub/fptex/} -from where beta versions of \fpTeX\ and additionnal tools are available. -This main site is (partially) mirrored daily by all \CTAN{} sites at -\path|systems/win32/fptex|. - -The \TeX{} Users Group is kindly hosting a mailing list dedicated to -\fpTeX. It is used for announcements, bug reports, enhancement requests, -and general discussion about \fpTeX. To subscribe, visit -\url{http://tug.org/mailman/listinfo/fptex}. The mailing list -address is \email{fptex@tug.org}. - - -% don't use \Webc so the \uppercase in the headline works. -\section{A user's guide to Web2C} - -\Webc{} is an integrated collection of \TeX-related programs: \TeX{} -itself, \MF{}, \MP, \BibTeX{}, etc. It is the heart of \TL{}. - -A bit of history: The original implementation was by Tomas Rokicki who, -in 1987, developed a first \TeX{}-to-C system based on change files -under Unix, which were primarily the original work of Howard Trickey and -Pavel Curtis. Tim Morgan became the maintainer of the system, and -during this period the name changed to Web-to-C\@. In 1990, Karl Berry -took over the work, assisted by dozens of additional contributors, and -in 1997 he handed the baton to Olaf Weber. - -The \Webc{} system runs on Unix, 32-bit Windows systems, \MacOSX{}, and -other operating systems. It uses Knuth's original sources for \TeX{} and -other basic programs written in \web{} and translates them into C source -code. The core \TeX{} programs are: - -\begin{cmddescription} -\item[bibtex] Maintaining bibliographies. -\item[dmp] \cmdname{troff} to MPX (\MP{} pictures). -\item[dvicopy] Expands virtual font references in \dvi{} files. -\item[dvitomp] \dvi{} to MPX (MetaPost pictures). -\item[dvitype] \dvi{} to human-readable text. -\item[gftodvi] Generic font proofsheets. -\item[gftopk] Generic to packed fonts. -\item[gftype] GF to human-readable text. -\item[makempx] \MP{} label typesetting. -\item[mf] Creating typeface families. -\item[mft] Prettyprinting \MF{} source. -\item[mpost] Creating technical diagrams. -\item[mpto] MetaPost label extraction. -\item[newer] Compare modification times. -\item[patgen] Creating hyphenation patterns. -\item[pktogf] Packed to generic fonts. -\item[pktype] PK to human-readable text. -\item[pltotf] Plain text property list to TFM. -\item[pooltype] Display \web{} pool files. -\item[tangle] \web{} to Pascal. -\item[tex] Typesetting. -\item[tftopl] TFM to plain text property list. -\item[vftovp] Virtual font to virtual property list. -\item[vptovf] Virtual property list to virtual font. -\item[weave] \web{} to \TeX. -\end{cmddescription} - -\noindent The precise functions and syntax of these programs are -described in the documentation of the individual packages and of \Webc{} -itself. However, knowing a few principles governing the whole family of -programs will help you take advantage of your \Webc{} installation. - -All programs honor these standard \acro{GNU} options: -\begin{ttdescription} -\item[-{}-help] print basic usage summary. -\item[-{}-verbose] print detailed progress report. -\item[-{}-version] print version information, then exit. -\end{ttdescription} - -For locating files the \Webc{} programs use the path searching library -\KPS{}. This library uses a combination of environment variables and a -configuration files to optimize searching the (huge) collection of -\TeX{} files. \Webc{} can look at more than one directory tree -simultaneously, which is useful in maintaining \TeX's standard -distribution and local extensions in two distinct trees. To speed up -file searches the root of each tree has a file \file{ls-R}, containing -an entry showing the name and relative pathname for all files under that -root. - -\subsection{Kpathsea path searching} - -Let us first describe the generic path searching mechanism of the \KPS{} -library. - -We call a \emph{search path} a colon- or semicolon\hyph sepa\-rated list -of \emph{path elements}, which are basically directory names. A -search path can come from (a combination of) many sources. To look up -a file \samp{my-file} along a path \samp{.:/dir}, \KPS{} checks each -element of the path in turn: first \file{./my-file}, then -\file{/dir/my-file}, returning the first match (or possibly all -matches). - -In order to adapt optimally to all operating systems' conventions, on -non-Unix systems \KPS{} can use filename separators different from -colon (\samp{:}) and slash (\samp{/}). - -To check a particular path element \var{p}, \KPS{} first checks if a -prebuilt database (see ``Filename data\-base'' on -page~\pageref{Filename-database}) applies to \var{p}, i.e., if the database -is in a directory that is a prefix of \var{p}. If so, the path -specification is matched against the contents of the database. - -If the database does not exist, or does not apply to this path -element, or contains no matches, the filesystem is searched (if this -was not forbidden by a specification starting with \samp{!!}\ and if -the file being searched for must exist). \KPS{} constructs the list -of directories that correspond to this path element, and then checks -in each for the file being sought. - -The ``file must exist'' condition comes into play with \samp{.vf} files and -input files read by \TeX's \cs{openin} command. Such files may not -exist (e.g., \file{cmr10.vf}), and so it would be wrong to search the -disk for them. Therefore, if you fail to update \file{ls-R} when you -install a new \samp{.vf} file, it will never be found. -Each path element is checked in turn: first the database, then the -disk. If a match is found, the search stops and the result is -returned. - -Although the simplest and most common path element is a directory -name, \KPS{} supports additional features in search paths: layered -default values, environment variable names, config file values, users' -home directories, and recursive subdirectory searching. Thus, we say -that \KPS{} \emph{expands} a path element, meaning it transforms all -the specifications into basic directory name or names. This is -described in the following sections in the same order as it takes -place. - -Note that if the filename being searched for is absolute or explicitly -relative, i.e., starts with \samp{/} or \samp{./} or \samp{../}, -\KPS{} simply checks if that file exists. - -\ifSingleColumn -\else -\begin{figure*} -\verbatiminput{examples/ex5.tex} -\setlength{\abovecaptionskip}{0pt} - \caption{An illustrative configuration file sample} - \label{fig:config-sample} -\end{figure*} -\fi - -\subsubsection{Path sources} -\label{Path-sources} - -A search path can come from many sources. In the order in which -\KPS{} uses them: - -\begin{enumerate} -\item - A user-set environment variable, for instance, \envname{TEXINPUTS}\@. - Environment variables with a period and a program name appended - override; e.g., if \samp{latex} is the name of the program being run, - then \envname{TEXINPUTS.latex} will override \envname{TEXINPUTS}. -\item - A program-specific configuration file, for exam\-ple, a line - \samp{S /a:/b} in \cmdname{dvips}'s \file{config.ps}. -\item A \KPS{} configuration file \file{texmf.cnf}, containing a line like - \samp{TEXINPUTS=/c:/d} (see below). -\item The compile-time default. -\end{enumerate} -\noindent You can see each of these values for a given -search path by using the debugging options (see ``Debugging actions'' -on page~\pageref{Debugging}). - -\subsubsection{Config files} - -\begingroup\tolerance=3500 -\KPS{} reads \emph{runtime configuration files} named \file{texmf.cnf} -for search path and other definitions. The search path used to look -for these files is named \envname{TEXMFCNF} (by default such a file lives -in the \file{texmf/web2c} subdirectory). \emph{All} -\file{texmf.cnf} files in the search path will be read and definitions -in earlier files override those in later files. Thus, with a search -path of \verb|.:$TEXMF|, values from \file{./texmf.cnf} override those -from \verb|$TEXMF/texmf.cnf|. -\endgroup - -\begin{itemize} -\item - Comments start with \code{\%} and continue to the end of the line. -\item - Blank lines are ignored. -\item - A \bs{} at the end of a line acts as a continuation character, - i.e., the next line is appended. Whitespace at the beginning of - continuation lines is not ignored. -\item - Each remaining line has the form: -\begin{alltt} - \var{variable}[.\var{progname}] [=] \var{value} -\end{alltt}% - where the \samp{=} and surrounding whitespace are optional. -\item - The \ttvar{variable} name may contain any character other - than whitespace, \samp{=}, or \samp{.}, but sticking to - \samp{A-Za-z\_} is safest. -\item - If \samp{.\var{progname}} is present, the definition only - applies if the program that is running is named - \texttt{\var{progname}} or \texttt{\var{progname}.exe}. This allows - different flavors of \TeX{} to have different search paths, for - example. -\item \var{value} may contain any characters except - \code{\%} and \samp{@}. The - \code{\$\var{var}.\var{prog}} feature is not available on the - right-hand side; instead, you must use an additional variable. A - \samp{;}\ in \var{value} is translated to \samp{:}\ if - running under Unix; this is useful to be able to have a single - \file{texmf.cnf} for Unix, \acro{MS-DOS} and Windows systems. -\item - All definitions are read before anything is expanded, so - variables can be referenced before they are defined. -\end{itemize} -A configuration file fragment illustrating most of these points is -\ifSingleColumn -shown below: - -\verbatiminput{examples/ex5.tex} -\else -shown in Figure~\ref{fig:config-sample}. -\fi - -\subsubsection{Path expansion} -\label{Path-expansion} - - -\KPS{} recognizes certain special characters and constructions in -search paths, similar to those available in Unix shells. As a -general example, the complex path, -\verb+~$USER/{foo,bar}//baz+, expands to all subdirectories under -directories \file{foo} and \file{bar} in \texttt{\$USER}'s home -directory that contain a directory or file \file{baz}. These -expansions are explained in the sections below. -%$ -\subsubsection{Default expansion} -\label{Default-expansion} - -\tolerance=2500 -If the highest-priority search path (see ``Path sources'' on -page~\pageref{Path-sources}) contains an \emph{extra colon} (i.e., -leading, trailing, or doubled), \KPS{} inserts at that point the -next-highest-prio\-rity search path that is defined. If that inserted -path has an extra colon, the same happens with the next highest. For -example, given an environment variable setting - -\tolerance=1500 - -\begin{alltt} -> \Ucom{setenv TEXINPUTS /home/karl:} -\end{alltt} -and a \code{TEXINPUTS} value from \file{texmf.cnf} of - -\begin{alltt} - .:\$TEXMF//tex -\end{alltt} -then the final value used for searching will be: - -\begin{alltt} - /home/karl:.:\$TEXMF//tex -\end{alltt} - -Since it would be useless to insert the default value in more than one -place, \KPS{} changes only one extra \samp{:}\ and leaves any others in -place. It checks first for a leading \samp{:}, then a trailing -\samp{:}, then a doubled \samp{:}. - -\subsubsection{Brace expansion} - -A useful feature is brace expansion, which means that, for instance, -\verb+v{a,b}w+ expands to \verb+vaw:vbw+. Nesting is allowed. -This can be used to implement multiple \TeX{} hierarchies, by -assigning a brace list to \code{\$TEXMF}. -For example, in \file{texmf.cnf}, you find -the following definition: -\begin{verbatim} - TEXMF = {$HOMETEXMF,$TEXMFLOCAL,!!$VARTEXMF,!!$TEXMFMAIN} -\end{verbatim} -Using this you can then write something like -\begin{verbatim} - TEXINPUTS = .;$TEXMF/tex// -\end{verbatim} -%$ -which means that, after looking in the current directory, the -\code{\$HOMETEXMF/tex}, \code{\$TEXMFLOCAL/tex}, \code{\$VARTEXMF/tex} -and \code{\$TEXMFMAIN/tex} trees \emph{only}) will be searched (the -last two use using \file{ls-R} data base files). It is a convenient -way for running two parallel \TeX{} structures, one ``frozen'' (on a -\CD, for instance) and the other being continuously updated with new -versions as they become available. By using the \code{\$TEXMF} -variable in all definitions, one is sure to always search the -up-to-date tree first. - -\subsubsection{Subdirectory expansion} -\label{Subdirectory-expansion} - -Two or more consecutive slashes in a path element following a directory -\var{d} is replaced by all subdirectories of \var{d}: first those -subdirectories directly under \var{d}, then the subsubdirectories under -those, and so on. At each level, the order in which the directories are -searched is \emph{unspecified}. - -If you specify any filename components after the \samp{//}, only -subdirectories with matching components are included. For example, -\samp{/a//b} expands into directories \file{/a/1/b}, \file{/a/2/b}, -\file{/a/1/1/b}, and so on, but not \file{/a/b/c} or \file{/a/1}. - -Multiple \samp{//} constructs in a path are possible, but -\samp{//} at the beginning of a path is ignored. - -\subsubsection{List of special characters and their meaning: a summary} - -The following list summarizes the special characters in \KPS{} -configuration files. - -% need a wider space for the item labels here. -\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} -\begin{ttdescription} -\item[\CODE{:}] Separator in path specification; at the beginning or - the end of a path it substitutes the default path expansion.\par -\item[\CODE{;}] Separator on non-Unix systems (acts like \code{:}). -\item[\CODE{\$}] Variable expansion. -\item[\CODE{\string~}] Represents the user's home directory. -\item[\CODE{\char`\{...\char`\}}] Brace expansion. -\item[\CODE{//}] Subdirectory expansion (can occur anywhere in - a path, except at its beginning). -\item[\CODE{\%}] Start of comment. -\item[\CODE{\bs}] Continuation character (allows multi-line entries). -\item[\CODE{!!}] Search \emph{only} database to locate file, \emph{do - not} search the disk. -\end{ttdescription} - - -\subsection{Filename databases} -\label{Filename-database} - -\KPS{} goes to some lengths to minimize disk accesses for searches. -Nevertheless, at installations with enough directories, searching each -possible directory for a given file can take an excessively long time -(this is especially true if many hundreds of font directories have to -be traversed.) Therefore, \KPS{} can use an externally-built plain text -``database'' file named \file{ls-R} that maps files to directories, -thus avoiding the need to exhaustively search the disk. - -A second database file \file{aliases} allows you to give additional -names to the files listed in \file{ls-R}. This can be helpful to -confirm to \acro{DOS} 8.3 filename conventions in source files. - -\subsubsection{The filename database} -\label{ls-R} - -As explained above, the name of the main filename database must be -\file{ls-R}. You can put one at the root of each \TeX{} hierarchy in -your installation that you wish to be searched (\code{\$TEXMF} by -default); most sites have only one hierarchy. \KPS{} looks for -\file{ls-R} files along the \code{TEXMFDBS} path. - -The recommended way to create and maintain \samp{ls-R} is to run the -\code{mktexlsr} script included with the distribution. It is invoked -by the various \samp{mktex}\dots\ scripts. In principle, this script -just runs the command -\begin{alltt} -cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R -\end{alltt} -presuming your system's \code{ls} produces the right output format -(\acro{GNU} \code{ls} is all right). To ensure that the database is -always up-to-date, it is easiest to rebuild it regularly via -\code{cron}, so that it is automatically updated when the installed -files change, such as after installing or updating a \LaTeX{} package. - -If a file is not found in the database, by default \KPS{} goes ahead -and searches the disk. If a particular path element begins with -\samp{!!}, however, \emph{only} the database will be searched for that -element, never the disk. - - -\subsubsection{kpsewhich: Standalone path searching} -\label{Invoking-kpsewhich} - -The \texttt{kpsewhich} program exercises path searching independent of any -particular application. This can be useful as a sort of \code{find} -program to locate files in \TeX{} hierarchies (this is used heavily in -the distributed \samp{mktex}\dots\ scripts). - -\begin{alltt} -> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} -\end{alltt} -The options specified in \ttvar{option} start with either \samp{-} -or \samp{-{}-}, and any unambiguous abbreviation is accepted. - -\KPS{} looks up each non-option argument on the command line as a -filename, and returns the first file found. There is no option to -return all the files with a particular name (you can run the Unix -\samp{find} utility for that). - -The more important options are described next. - -\begin{ttdescription} -\item[\texttt{-{}-dpi=\var{num}}]\mbox{} - Set the resolution to \ttvar{num}; this only affects \samp{gf} - and \samp{pk} lookups. \samp{-D} is a synonym, for compatibility - with \cmdname{dvips}. Default is 600. - -\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ - Set the format for lookup to \ttvar{name}. By default, the - format is guessed from the filename. For formats which do not have - an associated unambiguous suffix, such as \MP{} support files and - \cmdname{dvips} configuration files, you have to specify the name as - found in the first column of table~\ref{tab:kpathsea}, which lists - currently recognized names, a description, possible file extensions, - and associated environment variables. -\end{ttdescription} - - -\def\KpathKey#1#2#3#4#5{% name, number, description, variables, - % suffixes -\SetRowColor#1 & #3 & #4 & #5\\} -\def\HEAD#1{\multicolumn{1}{l}{\emph{#1}}} -% -\begin{small} -% a footnoterule immediately under a bottom-of-page rule looks dead -% silly, so we suppress it -\renewcommand\footnoterule{\relax} -% -\begin{longtable}{@{}% - >{\ttfamily}P{.16\textwidth}% Col.1 - P{.3\textwidth}% Col 2 - >{\ttfamily\footnotesize}P{.29\textwidth}% Col 3 - >{\ttfamily}P{.14\textwidth}% Col 4 -@{}} -\caption{Kpathsea file types.}\label{tab:kpathsea}\\ -\emph{Name} & \HEAD{Description} & \HEAD{Variables} -& \HEAD{Suffixes}\\ -\hline -\endfirsthead -\multicolumn{3}{l}{Kpathsea file types \emph{continued}}\\ -\emph{Name} & \HEAD{Description} & \HEAD{Variables} -& \HEAD{Suffixes}\\ -\hline -\noalign{\vspace{2pt}} -\endhead -\mbox{}\\ -\hline -\endfoot -\KpathKey - {afm} - {4} - {Adobe font metrics} - {AFMFONTS} - {.afm} -\KpathKey - {base} - {5} - {Metafont memory dump} - {MFBASES, TEXMFINI} - {.base} -\KpathKey - {bib} - {6} - {\BibTeX{} bibliography source} - {BIBINPUTS, TEXBIB} - {.bib} -\KpathKey - {} - {2} - {bitmap fonts} - {GLYPHFONTS, TEXFONTS} - {} -\KpathKey - {bst} - {7} - {\BibTeX{} style files} - {BSTINPUTS} - {.bst} -\KpathKey - {cnf} - {8} - {Runtime configuration files} - {TEXMFCNF} - {.cnf} -\KpathKey - {dvips config} - {34} - {\textsf{dvips} configuration files, e.g., \file{config.ps}} - {TEXCONFIG} - {} -\KpathKey - {enc} - {34} - {Font encoding files} - {ENCFONTS} - {.enc} -\KpathKey - {fmt} - {10} - {\TeX{} memory dump} - {TEXFORMATS, TEXMFINI} - {.fmt, .efmt, .efm} -\KpathKey - {gf} - {0} - {generic font bitmap} - {GFFONTS} - {.gf} -\KpathKey - {graphic/figure} - {25} - {Encapsulated \PS{} figures} - {TEXPICTS, TEXINPUTS} - {.eps, .epsi} -\KpathKey - {ist} - {35} - {\textsf{makeindex} style files} - {TEXINDEXSTYLE, INDEXSTYLE} - {.ist} -\KpathKey - {ls-R} - {9} - {Filename databases} - {TEXMFDBS} - {} -\KpathKey - {map} - {11} - {Fontmaps} - {TEXFONTMAPS} - {.map} -\KpathKey - {mem} - {12} - {MetaPost memory dump} - {MPMEMS, TEXMFINI} - {.mem} -\KpathKey - {mf} - {13} - {Metafont source} - {MFINPUTS} - {.mf} -\KpathKey - {mfpool} - {14} - {Metafont program strings} - {MFPOOL, TEXMFINI} - {.pool} -\KpathKey - {mft} - {15} - {MFT style file} - {MFTINPUTS} - {.mft} -\KpathKey - {} - {41} - {miscellaneous fonts} - {MISCFONTS} - {} -\KpathKey - {mp} - {16} - {MetaPost source} - {MPINPUTS} - {.mp} -\KpathKey - {mppool} - {17} - {MetaPost program strings} - {MPPOOL, TEXMFINI} - {.pool} -\KpathKey - {MetaPost support} - {18} - {MetaPost support files, used by DMP} - {MPSUPPORT} - {} -\KpathKey - {ocp} - {19} - {\OMEGA{} compiled process files} - {OCPINPUTS} - {.ocp} -\KpathKey - {ofm} - {20} - {\OMEGA{} font metrics} - {OFMFONTS, TEXFONTS} - {.ofm, .tfm} -\KpathKey - {opl} - {21} - {\OMEGA{} property lists} - {OPLFONTS, TEXFONTS} - {.opl} -\KpathKey - {otp} - {22} - {\OMEGA{} translation process files} - {OTPINPUTS} - {.otp} -\KpathKey - {ovf} - {23} - {\OMEGA{} virtual fonts} - {OVFFONTS, TEXFONTS} - {.ovf} -\KpathKey - {ovp} - {24} - {\OMEGA{} virtual property lists} - {OVPFONTS, TEXFONTS} - {.ovp} -\KpathKey - {pdftex config} - {18} - {\textsf{pdftex} configuration files} - {PDFTEXCONFIG} - {} -\KpathKey - {pk} - {1} - {packed bitmap fonts} - {\var{program}FONTS \textrm{(\texttt{\var{program}} being - \textsmaller{\cmdname{XDVI}}, - etc.)}, PKFONTS, TEXPKS, GLYPHFONTS, TEXFONTS} - {.pk} -\KpathKey - {\PS{} header} - {30} - {downloadable \PS{}} - {TEXPSHEADERS, PSHEADERS} - {.pro, .enc} -\KpathKey - {tex} - {26} - {\TeX{} source} - {TEXINPUTS} - {.tex, .cls, .sty, .clo, .def} -\KpathKey - {texmfscripts} - {20} - {Scripts distributed in the \file{texmf} tree} - {TEXMFSCRIPTS} - {} -\KpathKey - {TeX system documentation} - {27} - {Documentation files for the \TeX{} system} - {TEXDOCS} - {} -\KpathKey - {TeX system sources} - {29} - {Source files for the \TeX{} system} - {TEXSOURCES} - {} -\KpathKey - {texpool} - {28} - {\TeX{} program strings} - {TEXPOOL, TEXMFINI} - {.pool} -\KpathKey - {tfm} - {3} - {\TeX{} font metrics} - {TFMFONTS, TEXFONTS} - {.tfm} -\KpathKey - {Troff fonts} - {31} - {Troff fonts, used by DMP} - {TRFONTS} - {} -\KpathKey - {truetype fonts} - {36} - {TrueType outline fonts} - {TTFONTS} - {.ttf, .ttc} -\KpathKey - {Type~1 fonts} - {32} - {Type 1 \PS{} outline fonts} - {T1FONTS, T1INPUTS, TEXPSHEADERS, DVIPSHEADERS} - {.pfa, .pfb} -\KpathKey - {type42 fonts} - {37} - {Type 42 \PS{} outline fonts} - {T42FONTS} - {} -\KpathKey - {vf} - {33} - {virtual fonts} - {VFFONTS, TEXFONTS} - {.vf} -\KpathKey - {web2c files} - {38} - {\Webc{} support files} - {WEB2C} - {} -\KpathKey - {other text files} - {39} - {text files used by `\textsf{foo}'} - {FOOINPUTS} - {} -\KpathKey - {other binary files} - {40} - {binary files used by `\textsf{foo}'} - {FOOINPUTS} - {} -\end{longtable} -\end{small} - - -\begin{multicols}{2} - - The last two entries in table~\ref{tab:kpathsea} are special - cases, where the paths and environment variables depend on the name - of the program: the variable name is constructed by converting the - program name to upper case, and then appending \texttt{INPUTS}. - - The environment variables are set by default in the configuration - file \file{texmf.cnf}. It is only when you want to override one or - more of the values specified in that file that you might want to set - them explicitly in your execution environment. - - The \samp{-{}-format} and \samp{-{}-path} options are mutually - exclusive. - -\begin{ttdescription} - -\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ - Set the mode name to \ttvar{string}; this only affects \samp{gf} - and \samp{pk} lookups. No default: any mode will be found. -\item[\texttt{-{}-must-exist}]\mbox{}\\ - Do everything possible to find the files, notably including - searching the disk. By default, only the \file{ls-R} database is - checked, in the interest of efficiency. -\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ - Search along the path \ttvar{string} (colon-separated as usual), - instead of guessing the search path from the filename. \samp{//} and - all the usual expansions are supported. The options \samp{-{}-path} - and \samp{-{}-format} are mutually exclusive. -\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ - Set the program name to \texttt{\var{name}}. - This can affect the search paths via the \texttt{.\var{progname}} - feature. - The default is \cmdname{kpsewhich}. -\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ - shows the path used for file lookups of file type \texttt{\var{name}}. - Either a filename extension (\code{.pk}, \code{.vf}, etc.) or a - name can be used, just as with \samp{-{}-format} option. -\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ - sets the debugging options to \texttt{\var{num}}. -\end{ttdescription} - - -\subsubsection{Examples of use} -\label{SExamplesofuse} - -Let us now have a look at \KPS{} in action. Here's a straightforward search: - -\begin{alltt} -> \Ucom{kpsewhich article.cls} - /usr/local/texmf-dist/tex/latex/base/article.cls -\end{alltt} -We are looking for the file \file{article.cls}. Since the \samp{.cls} -suffix is unambiguous we do not need to specify that we want to look for a -file of type \optname{tex} (\TeX{} source file directories). We find it in -the subdirectory \file{tex/latex/base} below the \samp{texmf-dist} \TL\ -directory. Similarly, all of the following are found without problems -thanks to their unambiguous suffix. -\begin{alltt} -> \Ucom{kpsewhich array.sty} - /usr/local/texmf-dist/tex/latex/tools/array.sty -> \Ucom{kpsewhich latin1.def} - /usr/local/texmf-dist/tex/latex/base/latin1.def -> \Ucom{kpsewhich size10.clo} - /usr/local/texmf-dist/tex/latex/base/size10.clo -> \Ucom{kpsewhich small2e.tex} - /usr/local/texmf-dist/tex/latex/base/small2e.tex -> \Ucom{kpsewhich tugboat.bib} - /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib -\end{alltt} - -That last is a \BibTeX{} bibliography database for \textsl{TUGBoat} articles. - -\begin{alltt} -> \Ucom{kpsewhich cmr10.pk} -\end{alltt} -Font bitmap glyph files of type \file{.pk} are used by display -programs like \cmdname{dvips} and \cmdname{xdvi}. Nothing is returned in -this case since there are no pre-generated Computer Modern \samp{.pk} -files in \TL{}\Dash the Type~1 variants are used by default. -\begin{alltt} -> \Ucom{kpsewhich wsuipa10.pk} -\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk -\else /usr/local/texmf-var/fonts/pk/ljfour/public/ -... wsuipa/wsuipa10.600pk -\fi\end{alltt} - -For these fonts (a phonetic alphabet from the University of Washington) -we had to generate \samp{.pk} files, and since the default \MF{} mode on -our installation is \texttt{ljfour} with a base resolution of 600\dpi{} -(dots per inch), this instantiation is returned. -\begin{alltt} -> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} -\end{alltt} -In this case, when specifying that we are interested in a resolution -of 300\dpi{} (\texttt{-dpi=300}) we see that no such font is available on -the system. A program like \cmdname{dvips} or \cmdname{xdvi} would -go off and actually build the required \texttt{.pk} files -using the script \cmdname{mktexpk}. - -Next we turn our attention to \cmdname{dvips}'s header and configuration -files. We first look at one of the commonly used files, the general -prolog \file{tex.pro} for \TeX{} support, before turning our attention -to the generic configuration file (\file{config.ps}) and the \PS{} font -map \file{psfonts.map}\Dash as of 2004, map and encoding files have -their own search paths and new location in \dirname{texmf} trees. As -the \samp{.ps} suffix is ambiguous we have to specify explicitly which -type we are considering (\optname{dvips config}) for the file -\texttt{config.ps}. -\begin{alltt} -> \Ucom{kpsewhich tex.pro} - /usr/local/texmf/dvips/base/tex.pro -> \Ucom{kpsewhich --format="dvips config" config.ps} - /usr/local/texmf/dvips/config/config.ps -> \Ucom{kpsewhich psfonts.map} - /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map -\end{alltt} - -We now take a closer look at the \acro{URW} Times \PS{} support -files. The prefix for these in the standard font naming scheme is -\samp{utm}. The first file we look at is the configuration file, -which contains the name of the map file: -\begin{alltt} -> \Ucom{kpsewhich --format="dvips config" config.utm} - /usr/local/texmf-dist/dvips/psnfss/config.utm -\end{alltt} -The contents of that file is -\begin{alltt} - p +utm.map -\end{alltt} -which points to the file \file{utm.map}, which we want to -locate next. -\begin{alltt} -> \Ucom{kpsewhich utm.map} - /usr/local/texmf-dist/fonts/map/dvips/times/utm.map -\end{alltt} -This map file defines the file names of the Type~1 \PS{} fonts in -the URW collection. Its contents look like (we only show part of the -lines): -\begin{alltt} -utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} -\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb -\else /usr/local/texmf-dist/fonts/type1/ -... urw/utm/utmr8a.pfb -\fi\end{alltt} - -It should be evident from these examples how you can easily locate the -whereabouts of a given file. This is especially important if you suspect -that the wrong version of a file is picked up somehow, since -\cmdname{kpsewhich} will show you the first file encountered. - -\subsubsection{Debugging actions} -\label{Debugging} - -Sometimes it is necessary to investigate how a program resolves file -references. To make this practical, \KPS{} offers various levels of -debugging output: - -\begin{ttdescription} -\item[\texttt{\ 1}] \texttt{stat} calls (disk lookups). When running - with an up-to-date \file{ls-R} database this should almost give no - output. -\item[\texttt{\ 2}] References to hash tables (such as \file{ls-R} - databases, map files, configuration files). -\item[\texttt{\ 4}] File open and close operations. -\item[\texttt{\ 8}] General path information for file types - searched by \KPS. This is useful to find out where a particular - path for the file was defined. -\item[\texttt{16}] Directory list for each path element (only relevant - for searches on disk). -\item[\texttt{32}] File searches. -\end{ttdescription} -A value of \texttt{-1} will set all the above options; in practice, -this is usually the most convenient. - -Similarly, with the \cmdname{dvips} program, by setting a combination of -debug switches, one can follow in detail where files are being picked up -from. Alternatively, when a file is not found, the debug trace shows in -which directories the program looks for the given file, so that one can -get an indication what the problem~is. - -Generally speaking, as most programs call the \KPS{} library -internally, one can select a debug option by using the -\envname{KPATHSEA\_DEBUG} environment variable, and setting it to (a -combination of) values as described in the above list. - -(Note for Windows users: it is not easy to redirect -all messages to a file in this system. For diagnostic purposes -you can temporarily \texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log}). - -Let us consider, as an example, a small \LaTeX{} source file, -\file{hello-world.tex}, which contains the following input. -\begin{verbatim} - \documentclass{article} - \begin{document} - Hello World! - \end{document} -\end{verbatim} -This little file only uses the font \file{cmr10}, so let us look -how \cmdname{dvips} prepares the \PS{} file (we want to use the Type~1 -version of the Computer Modern fonts, hence the option \texttt{-Pcms}). -\begin{alltt} -> \Ucom{dvips -d4100 hello-world -Pcms -o} -\end{alltt} -In this case we have combined \cmdname{dvips}'s debug class 4 (font -paths) with \KPS's path element expansion (see \cmdname{dvips} Reference -Manual, \OnCD{texmf/doc/html/dvips/dvips_toc.html}). -The output (slightly rearranged) appears in -Figure~\ref{fig:dvipsdbga}. -\begin{figure*}[tp] -\centering -\input{examples/ex6a.tex} -\caption{Finding configuration files}\label{fig:dvipsdbga} - -\bigskip - -\input{examples/ex6b.tex} -\caption{Finding the prolog file}\label{fig:dvipsdbgb} - -\bigskip - -\input{examples/ex6c.tex} -\caption{Finding the font file}\label{fig:dvipsdbgc} -\end{figure*} - -\cmdname{dvips} starts by locating its working files. First, -\file{texmf.cnf} is found, which gives the definitions of the search -paths for the other files, then the file database \file{ls-R} (to -optimize file searching) and the file \file{aliases}, which makes it -possible to declare several names (e.g., a short \acro{DOS}-like 8.3 and -a more natural longer version) for the same file. Then \cmdname{dvips} -goes on to find the generic configuration file \file{config.ps} -before looking for the customization file \file{.dvipsrc} (which, in -this case is \emph{not found}). Finally, \cmdname{dvips} locates the -config file for the Computer Modern \PS{} fonts \file{config.cms} -(this was initiated with the \texttt{-Pcms} option on the \cmdname{dvips} -command). This file contains the list of the map files which -define the relation between the \TeX{}, \PS{} and file system -names of the fonts. -\begin{alltt} -> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} - p +ams.map - p +cms.map - p +cmbkm.map - p +amsbkm.map -\end{alltt} -\cmdname{dvips} thus goes on to find all these files, plus the generic -map file \file{psfonts.map}, which is always loaded (it contains -declarations for commonly used \PS{} fonts; see the last part of -Section \ref{SExamplesofuse} for more details about \PS{} map -file handling). - -At this point \cmdname{dvips} identifies itself to the user: -\begin{alltt} -This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) -\end{alltt} -\ifSingleColumn -Then it goes on to look for the prolog file \file{texc.pro}: -\begin{alltt}\small -kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro -\end{alltt} -\else -Then it goes on to look for the prolog file \file{texc.pro} (see -Figure~\ref{fig:dvipsdbgb}). -\fi - -After having found the file in question, \cmdname{dvips} outputs -date and time, and informs us that it will generate the -file \file{hello-world.ps}, then that it needs the font file -\file{cmr10}, and that the latter is declared as ``resident'' (no -bitmaps needed): -\begin{alltt}\small -TeX output 1998.02.26:1204' -> hello-world.ps -Defining font () cmr10 at 10.0pt -Font cmr10 is resident. -\end{alltt} -Now the search is on for the file \file{cmr10.tfm}, which is found, -then a few more prolog files (not shown) are referenced, and finally -the Type~1 instance \file{cmr10.pfb} of the font is located and -included in the output file (see last line). -\begin{alltt}\small -kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, - path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: - /var/tex/fonts/tfm//). -kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm -kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, - ... - -kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb -[1] -\end{alltt} - -\subsection{Runtime options} - -Another useful feature of \Webc{} is its possibility to control a number -of memory parameters (in particular, array sizes) via the runtime file -\file{texmf.cnf} read by \KPS{}. The memory settings can be found in -Part 3 of that file in the \TL{} distribution. The more important -are: - -\begin{ttdescription} -\item[\texttt{main\_memory}] - Total words of memory available, for - \TeX{}, \MF{} and \MP. You must make a new format file for each - different setting. For instance, you could generate a ``huge'' - version of \TeX{}, and call the format file \texttt{hugetex.fmt}. - Using the standard way of specifying the program name used by \KPS{}, - the particular value of the \texttt{main\_memory} variable will then - be read from \file{texmf.cnf}. - etc.). -\item[\texttt{extra\_mem\_bot}] - Extra space for ``large'' \TeX{} data structures: - boxes, glue, breakpoints, etc. Especially useful if you use - \PiCTeX{}. -\item[\texttt{font\_mem\_size}] - Number of words for font information available for \TeX. This - is more or less the total size of all TFM files read. -\item[\texttt{hash\_extra}] - Additional space for the hash table of control sequence names. - Approximately 10,000 control sequences can be stored in the main - hash table; if you have a large book with numerous cross-references, - this might not be enough. The default value of - \texttt{hash\_extra} is \texttt{50000}. -\end{ttdescription} - -\noindent Of course, this facility is no substitute for truly dynamic -arrays and memory allocation, but since these are extremely difficult to -implement in the present \TeX{} source, these runtime parameters provide -a practical compromise allowing some flexibility. - - -\section{Building on a new Unix platform} - -If you have a platform for which executables are not included, you will -need to compile \TeX{} and friends. This is not as hard as it -sounds. What you need is all in the directory \texttt{source} in the -distribution. - -\subsection{Prerequisites} - -You will need at least 100 megabytes of disk space to compile all of -\TeX{} and its support programs. You'll also need an \acro{ANSI} C -compiler, a \cmdname{make} utility, a lexical scanner, and a parser -generator. We recommend the \acro{GNU} version of these programs -(\cmdname{gcc}, \acro{GNU} \cmdname{make}, \cmdname{m4}, \cmdname{flex}, -\cmdname{bison}). You may be able to work with other C compilers and -\cmdname{make} programs, but you will need a good understanding of -building Unix programs to sort out problems. - -Also, the command \texttt{uname} must return a sensible value. - - -\subsection{Configuration} - -To begin, perform a normal installation of \TL{} to your disk (see -section~\ref{sec:unix-install-disk} on -\p.\pageref{sec:unix-install-disk}). You may wish to skip installing -all of the prebuilt binaries. - -Then, unpack the source from the compressed \texttt{tar} file in the -directory \dirname{source} to your disk and change directory to where -you placed it. - -Next, run \cmdname{configure} with a command line like this: -\begin{alltt} -> \Ucom{sh configure -prefix=/usr/local/TeX} -\end{alltt} - -The \optname{-prefix} directory is the one where you installed the -support tree; the directory layout will be as follows (where \$TEXDIR -stands for the directory you chose): - -\noindent -\begin{tabular}{>{\ttfamily}ll@{}} - \dirname{$TEXDIR/share/texmf} & main tree with fonts,\\ - & \qquad macros, etc\\ - \dirname{$TEXDIR/man} & Unix manual pages\\ - \dirname{$TEXDIR/info} & \acro{GNU} style Info manuals\\ - \dirname{$TEXDIR/bin/$PLATFORM} & binaries\\ -\end{tabular} -%$ - -If you want to leave out the \dirname{$PLATFORM} directory level, -i.e., put the binaries directly into \dirname{$TEXDIR/bin}, specify -the \verb|--disable-multiplatform| option to \cmdname{configure}. - -Have a look at the output of \verb|./configure --help| for more -options you can use. For example, you can skip building of \OMEGA{} and -\eTeX{}. - - -\subsection{Running \cmdname{make}} - -Make sure the shell variable or option \texttt{noclobber} is not set. -Then, run the main \cmdname{make} like this: -\begin{alltt} -> \Ucom{make world} -\end{alltt} -and relax\ldots - -Alternatively, you want to log all the output, as in: -\begin{alltt} -> \Ucom{sh -c "make world >world.log 2>\&1" \&} -\end{alltt} - -Before you believe that everything went ok, please check the log file -for errors: \acro{GNU} \cmdname{make} always uses the string \samp{***} -whenever a command fails. Also, check if all the programs were built: - -\begin{alltt} -> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} -> \Ucom{ls | wc} -\end{alltt} -The result should be over 200 (you can check the exact number with the -\dirname{bin} directory contents in the distribution). - -If you need special privileges for \texttt{make install}, you can -separate the \samp{make world} into two different runs, like this: -\begin{alltt} -> \Ucom{make all} -> \Ucom{su} -> \Ucom{make install strip} -\end{alltt} - -After you've installed your new binaries, you should follow the normal -post-installation procedures, given in section~\ref{sec:postinstall} -(\p.\pageref{sec:postinstall}). - -Also, if you'd like to make your binaries available to others, please -contact us. We'll be happy to put them on the \TL\ web pages. - - -\section{Acknowledgements} - -\TL{} is a joint effort by virtually all of the \TeX{} user groups. -This edition of \TL{} was overseen by Sebastian Rahtz and Karl Berry. -The other principal contributors are listed below. - -\begin{itemize*} - -\item The German-speaking \TeX{} Users (\acro{DANTE} e.V.), who provide -the hardware for the \TL{} source repository; and Rainer Sch\"opf and -Reinhard Zierke who look after it. \acro{DANTE} officers Volker Schaa -and Klaus Hoeppner coordinated production with the Lehmann's Bookstore -(\url{http://www.lob.de}). - -\item The Perforce corporation (\url{http://www.perforce.com}), for providing -a free copy of their excellent change management system, which we used -to manage the \TL{} sources. - -\item Peter Breitenlohner and the \eTeX\ team for the stable foundation -of future \TeX's. - -\item Thomas Esser, without whose marvelous \teTeX{} package \TL{} -would certainly not exist, and whose continual help makes it a better -product. - -\item Michel Goossens, who co-authored the original documentation. - -\item Eitan Gurari, whose \TeX4ht was used to create the \HTML{} -version of this documentation, and who worked tirelessly to improve -it at short notice. - -\item Hans Hagen, for major testing and making the \ConTeXt\ format -conform to \TL's needs. - -\item \Thanh, Martin Schr\"oder, and the pdf\TeX\ team for continuing -enhancements of \TeX's abilities. - -\item Petr Olsak, who coordinated and checked all the Czech and Slovak -material very carefully. - -\item Fabrice Popineau, for the Windows side of \TL{} and devising the -new directory layout. - -\item Staszek Wawrykiewicz, the principal tester for all of \TL{}, and -coordinator of the Polish contributions. - -\item Olaf Weber, for his patient assembly and maintenance of Web2C, -upon which all else depends. - -\item Gerben Wierda, for creating and maintaining the \MacOSX\ support, -and much integration and testing. - -\item Graham Williams, on whose work the catalogue of packages depends. - -\end{itemize*} - -Builders of the binaries: -Tigran Aivazian (\pkgname{x86\_64-linux}), -Manfred Lotz (\pkgname{i386-freebsd}), -Maksym Polyakov (\pkgname{sparc-solaris}), -Fabrice Popineau (\pkgname{win32}), -Norbert Preining (\pkgname{alpha-linux}), -Vladimir Volovich (\pkgname{powerpc-aix} and \pkgname{sparc64-linux}), -Staszek Wawrykiewicz (\pkgname{i386-linux}), -Olaf Weber (\pkgname{mips-irix}), -Gerben Wierda (\pkgname{powerpc-darwin}). - -Documentation and translation updates: -Karl Berry (English), -Daniel Flipo \& Fabrice Popineau (French), -G\"unter Partosch \& Hartmut Henkel (German), -Petr Sojka \& Jan Busa (Czech\slash Slovak), -Boris Veytsman (Russian), -Staszek Wawrykiewicz (Polish). - -Of course the most important acknowledgement must go to Donald Knuth, first -for inventing \TeX, and then for giving it to the world. - - -\section{Release history} -\label{sec:history} - -\subsection{Past} - -Discussion began in late 1993 when the Dutch \TeX{} Users Group was -starting work on its 4All\TeX{} \CD{} for \acro{MS-DOS} users, and it -was hoped at that time to issue a single, rational, \CD{} for all -systems. This was too ambitious a target for the time, but it did spawn -not only the very successful 4All\TeX{} \CD{}, but also the \acro{TUG} -Technical Council working group on a \emph{\TeX{} Directory Structure} -(\url{http://tug.org/tds}), which specified how to create consistent and -manageable collections of \TeX{} support files. A complete draft of the -\TDS{} was published in the December 1995 issue of \textsl{TUGboat}, and -it was clear from an early stage that one desirable product would be a -model structure on \CD{}. The distribution you now have is a very direct -result of the working group's deliberations. It was also clear that the -success of the 4All\TeX{} \CD{} showed that Unix users would benefit -from a similarly easy system, and this is the other main strand of -\TL. - -We first undertook to make a new Unix-based \TDS{} \CD{} in the autumn -of 1995, and quickly identified Thomas Esser's \teTeX{} as the ideal -setup, as it already had multi-platform support and was built with -portability across file systems in mind. Thomas agreed to help, and work -began seriously at the start of 1996. The first edition was released in -May 1996. At the start of 1997, Karl Berry completed a major new release -of Web2c, which included nearly all the features which Thomas Esser had -added in \teTeX, and we decided to base the 2nd edition of the \CD{} on -the standard \Webc, with the addition of \teTeX's \texttt{texconfig} -script. The 3rd edition of the \CD{} was based on a major revision of -\Webc, 7.2, by Olaf Weber; at the same time, a new revision of \teTeX -was being made, and \TL{} included almost all of its features. The -4th edition followed the same pattern, using a new version of \teTeX, -and a new release of \Webc{} (7.3). The system now included a complete -Windows setup. - -For the 5th edition (March 2000) many parts of the \CD{} were revised -and checked, updating hundreds of packages. Package details were stored -in XML files. But the major change for \TeX\ Live 5 was that all -non-free software was removed. Everything in \TL{} is now intended -to be compatible with the Debian Free Software Guidelines -(\url{http://www.debian.org/intro/free}); we have done our best to check -the license conditions of all packages, but we would very much -appreciate hearing of any mistakes. - -The 6th edition (July 2001) had much more material updated. The major -change was a new install concept: the user could select a more exact set -of needed collections. Language-related collections were completely -reorganized, so selecting any of them installs not only macros, fonts, -etc., but also prepares an appropriate \texttt{language.dat}. - -The 7th edition of 2002 had the notable addition of \MacOSX{} support, -and the usual myriad of updates to all sorts of packages and -programs. An important goal was integration of the source back with -\teTeX, to correct the drift apart in versions~5 and~6. - -In 2003, with the continuing flood of updates and additions, we found -that \TL{} had grown so large it could no longer be contained on a -single \CD, so we split it into three different distributions (see -section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}). In -addition: - -\begin{itemize*} -\item At the request of the \LaTeX{} team, we changed the standard - \cmdname{latex} and \cmdname{pdflatex} commands to now use \eTeX{} (see - \p.\pageref{text:etex}). -\item The new Latin Modern fonts were included (and are recommended). -\item Support for Alpha \acro{OSF} was removed - (\acro{HPUX} support was removed previously), since no one had (or - volunteered) hardware available on which to compile new binaries. -\item Windows setup was substantially changed; for the first time - an integrated environment based on XEmacs was introduced. -\item Important supplementary programs for Windows - (Perl, Ghost\-script, Image\-Magick, Ispell) are now installed - in the \TL{} installation directory. -\item Font map files used by \cmdname{dvips}, \cmdname{dvipdfm} - and \cmdname{pdftex} are now generated by the new program - \cmdname{updmap} and installed into \dirname{texmf/fonts/map}. -\item \TeX{}, \MF{}, and \MP{} now, by default, output most input - characters (32 and above) as themselves in output (e.g., - \verb|\write|) files, - log files, and the terminal, i.e., \emph{not} translated using the - \verb|^^| notation. In \TL{}~7, this translation was - dependent on the system locale settings; now, locale settings do - not influence the \TeX{} programs' behavior. If for some reason - you need the \verb|^^| output, rename the file - \verb|texmf/web2c/cp8bit.tcx|. (Future releases will have cleaner - ways to control this.) -\item This documentation was substantially revised. -\item Finally, since the edition numbers had grown unwieldy, - the version is now simply identified by the year: \TL{} 2003. -\end{itemize*} - -\subsection{Present} -\label{tlcurrent} - -2004 saw the usual huge number of updates to packages and programs. -Here are the most notable changes, including one important backward -incompatibility: - -\begin{itemize} - -\item If you have locally-installed fonts which use their own -\filename{.map} or (much less likely) \filename{.enc} support files, you -may need to move those support files. - -\filename{.map} files are now searched for in subdirectories of -\dirname{fonts/map} only (in each \filename{texmf} tree), along the -\envname{TEXFONTMAPS} path. Similarly, \filename{.enc} files are now -searched for in subdirectories of \dirname{fonts/enc} only, along the -\envname{ENCFONTS} path. \cmdname{updmap} will attempt to warn about -problematic files. - -For methods of handling this and other information, please see -\url{http://tug.org/texlive/mapenc.html}. - -\item The \TK\ has been expanded with the addition of a \MIKTEX-based -installable \CD, for those who prefer that implementation to Web2C. -See section~\ref{sec:struct-tl} (\p.\pageref{sec:struct-tl}). - -\item Within \TL, the single large \dirname{texmf} tree of previous -releases has been replaced by three: \dirname{texmf}, -\dirname{texmf-dist}, and \dirname{texmf-doc}. See -section~\ref{sec:tld} (\p.\pageref{sec:tld}), and the \filename{README} -files for each. - -\item All \TeX-related input files are now collected in -the \dirname{tex} subdirectory of \dirname{texmf*} trees, rather than -having separate sibling directories \dirname{tex}, \dirname{etex}, -\dirname{pdftex}, \dirname{pdfetex}, etc. See -\CDref{texmf-doc/doc/english/tds/tds.html\#Extensions} -{\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}. - -\item Helper scripts (not meant to be invoked by users) are now located -in a new \dirname{scripts} directory of \dirname{texmf*} trees, and -searched for via \verb|kpsewhich -format=texmfscripts|. So if you have -programs which call such scripts, they'll need to be adjusted. See -\CDref{texmf-doc/doc/english/tds/tds.html\#Scripts} -{\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}. - -\item Almost all formats leave most characters printable as -themselves via the ``translation file'' \filename{cp227.tcx}, instead of -translating them with the \verb|^^| notation. Specifically, characters -at positions 32--256, plus tab, vertical tab, and form feed are -considered printable and not translated. The exceptions are plain \TeX\ -(only 32--126 printable), \ConTeXt\ (0--255 printable), and the -\OMEGA-related formats. This default behavior is almost the same as in -\TL\,2003, but it's implemented more cleanly, with more possibilities -for customization. See \CDref{texmf/doc/web2c/web2c.html\#TCX-files} -{\texttt{texmf/doc/web2c/web2c.html\#TCX-files}}. -(By the way, with Unicode input, \TeX\ may output partial character -sequences when showing error contexts, since it is byte-oriented.) - -\item \textsf{pdfetex} is now the default engine for all formats -except (plain) \textsf{tex} itself. (Of course it generates \acro{DVI} -when run as \textsf{latex}, etc.) This means, among other things, that -the microtypographic features of \textsf{pdftex} are available in -\LaTeX, \ConTeXt, etc., as well as the \eTeX\ features -(\OnCD{texmf-dist/doc/etex/base/}). - -It also means it's \emph{more important than ever} to use the -\pkgname{ifpdf} package (works with both plain and \LaTeX) or equivalent -code, because simply testing whether \cs{pdfoutput} or some other -primitive is defined is not a reliable way to determine if \acro{PDF} -output is being generated. We made this backward compatible as best we -could this year, but next year, \cs{pdfoutput} may be defined even when -\acro{DVI} is being written. - -\item pdf\TeX\ (\url{http://pdftex.org}) has many new features: - - \begin{itemize*} - - \item \cs{pdfmapfile} and \cs{pdfmapline} provide font map support - from within a document. - - \item Microtypographic font expansion can be used more easily.\\ - \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} - - \item All parameters previously set through the special configuration - file \filename{pdftex.cfg} must now be set through primitives, - typically in \filename{pdftexconfig.tex}; \filename{pdftex.cfg} is no - longer supported. Any extant \filename{.fmt} files must be redumped - when \filename{pdftexconfig.tex} is changed. - - \item See the pdf\TeX\ manual for more: \OnCD{texmf/doc/pdftex/manual}. - - \end{itemize*} - -\item The \cs{input} primitive in \cmdname{tex} (and \cmdname{mf} and -\cmdname{mpost}) now accepts double quotes containing spaces and other -special characters. Typical examples: -\begin{verbatim} -\input "filename with spaces" % plain -\input{"filename with spaces"} % latex -\end{verbatim} -See the Web2C manual for more: \OnCD{texmf/doc/web2c}. - -\item enc\TeX\ support is now included within Web2C and consequently all -\TeX\ programs, via the \optname{-enc} option\Dash \emph{only when -formats are built}. enc\TeX\ supports general re-encoding of input and -output, enabling full support of Unicode (in \acro{UTF}-8). See -\OnCD{texmf-dist/doc/generic/enctex/} and -\url{http://www.olsak.net/enctex.html}. - -\item Aleph, a new engine combining \eTeX\ and \OMEGA, is available. -A little information is available in \OnCD{texmf-dist/doc/aleph/base} -and \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph}. The -\LaTeX-based format for Aleph is named \textsf{lamed}. - -\item The latest \LaTeX\ release has a new version of the -\acro{LPPL}\Dash now officially a Debian-approved license. Assorted -other updates, see the \filename{ltnews} files in -\OnCD{texmf-dist/doc/latex/base}. - -\item \cmdname{dvipng}, a new program for converting \acro{DVI} to -\acro{PNG} image files, is included. See \OnCD{texmf/doc/man/man1/dvipng.1}. - -\item We reduced the \pkgname{cbgreek} package to a ``medium'' sized set -of fonts, with the assent and advice of the author (Claudio Beccari). -The excised fonts are the invisible, outline, and transparency ones, -which are relatively rarely used, and we needed the space. The full set -is of course available from \acro{CTAN} -(\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). - -\item \cmdname{oxdvi} has been removed; just use \cmdname{xdvi}. - -\item The \cmdname{ini} and \cmdname{vir} commands (links) for -\cmdname{tex}, \cmdname{mf}, and \cmdname{mpost} are no longer created, -such as \cmdname{initex}. The \cmdname{ini} functionality has been -available through the command-line option \optname{-ini} for years now. - -\item \textsf{i386-openbsd} platform support was removed. Since the -\pkgname{tetex} package in the \acro{BSD} Ports system is available, and -\acro{GNU/}Linux and Free\acro{BSD} binaries were available, it seemed -volunteer time could be better spent elsewhere. - -\item On \textsf{sparc-solaris} (at least), you may have to set the -\envname{LD\_LIBRARY\_PATH} environment variable to run the -\pkgname{t1utils} programs. This is because they are compiled with C++, -and there is no standard location for the runtime libraries. (This is -not new in 2004, but wasn't previously documented.) Similarly, on -\textsf{mips-irix}, the \acro{MIPS}pro 7.4 runtimes are required. - -\end{itemize} - - -\subsection{Future} - -\emph{\TL{} is not perfect!} (And never will be.) We intend to -continue to release new versions yearly, and would like to provide more -help material, more utilities, more installation programs, and (of -course) an ever-improved and checked tree of macros and fonts. This work -is all done by hard-pressed volunteers in their limited spare time, and -a great deal remains to be done. If you can help, don't hesitate to put -your name forward! - -Please send corrections, suggestions, and offers of help to:\hfill\null -\begin{quote} -Sebastian Rahtz \ / \ 7 Stratfield Road \ / \ Oxford OX2 7BG \ / \ UK \\ -\email{tex-live@tug.org} \\ -\url{http://tug.org/texlive} -\end{quote} - -\medskip -\noindent \textsl{Happy \TeX ing!} - -\end{multicols} -\end{document} diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/live-2005.tex b/Master/texmf-doc/source/texlive/texlive-en/archive/live-2005.tex deleted file mode 100644 index 5b525535c63..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/live-2005.tex +++ /dev/null @@ -1,3174 +0,0 @@ -% $Id: live.tex 1513 2006-02-13 00:22:35Z karl $ -% TeX Live documentation. Originally written by Sebastian Rahtz and -% Michel Goossens, now maintained by Karl Berry and others. -% Public domain. -% -\documentclass{article} -\let\tldocenglish=1 % for live4ht.cfg -\usepackage{tex-live} -\begin{document} - -\title{% - {\huge \textit{The \protect\TL{} Guide}\\\strut} - {\LARGE \textsf{\TK{} 2005}} -} - -\author{Sebastian Rahtz \& Karl Berry, editors \\[3mm] - \url{http://tug.org/texlive/} - } - -\date{October 2005} - -\maketitle - -\begin{multicols}{2} -\tableofcontents -\listoftables -\end{multicols} - -\section{Introduction} -\label{sec:intro} - -This document describes the main features of the \TL{} software -distribution\Dash \TeX{} and friends for \acro{GNU}/Linux and other Unix -flavors, \MacOSX, and (32-bit) Windows systems. (Warning: it is not -especially useful for older Mac or \acro{MS-DOS} systems.) - -\TL{} includes executables for \TeX{}, \LaTeXe{}, \ConTeXt, \MF, \MP, -\BibTeX{} and many other programs; an extensive collection of macros, -fonts and documentation; and support for typesetting in many different -scripts from around the world. It is part of the even larger \TK{} -(briefly described below in section~\ref{sec:struct-tl}, -\p.\pageref{sec:struct-tl}). Both are cooperative efforts by the \TeX\ -user groups. - -For newer versions of the packages included here, please check -\acro{CTAN}: \url{http://www.ctan.org}. - -For a brief summary of the major changes in this edition of \TL{}, -see the end of the document, section~\ref{sec:history} -(\p.\pageref{sec:history}). - - -\subsection{Basic usage of \protect\TL{}} -\label{sec:basic} - -You can use \TL{} in three principal ways: - -\begin{enumerate} - -\item You can run \TL{} directly from the \pkgname{live} \DVD -(see section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}). -This takes almost no disk space, and gives you immediate access to -everything in \TL{}. Of course performance will be worse than running -on local disk, but you may well find it useful. - -\item You can install all or part of \TL{} to a local disk, from either -the \DVD\ or the \pkgname{inst} \acro{CD}. This is the most common use -of \TL. You will need (approximately) 100 megabytes for the most -minimal system, and upwards of 1.3 gigabytes for a full system. - -\item You can integrate a particular package or collection into your -existing \TeX{} system, either a \TL{} system you installed -earlier, or a different system. - -\end{enumerate} - -\noindent All of these are described in detail in the \acro{OS}-specific -installation sections following, but here is a quick start: - -\begin{itemize*} - -\item The main installation script for Unix and \MacOSX{} is -\texttt{install-tl.sh}. - -\item The single package installation script is \texttt{install-pkg.sh}. - -\item The installation program for Windows is \texttt{tlpmgui.exe}. -It can be used also for adding or removing the packages. -See section~\ref{sec:win-install} below for more information. - -\end{itemize*} - - -\subsection{Getting help} -\label{sec:help} - -The \TeX{} community is both active and friendly, and virtually all -serious questions end up getting answered. However, the support is -informal, done by volunteers and casual readers, so it's especially -important that you do your homework before asking. (If you prefer -guaranteed commercial support, you can forego \TL{} completely and -purchase a vendor's system; \url{http://tug.org/interest.html#vendors} -has a list.) - -Here is a list of resources, approximately in the order we recommend -using them: - -\begin{description} -\item [Getting Started] If you are new to \TeX, the web page -\url{http://tug.org/begin.html} gives a brief introduction to the system. - -\item [\TeX{} \acro{FAQ}] The \TeX{} \acro{FAQ} is a huge compendium of -answers to all sorts of questions, from the most basic to the most -arcane. It is included on \TL{} in \OnCD{texmf-doc/doc/english/FAQ-en}, and is -available on the Internet through \url{http://www.tex.ac.uk/faq}. -Please check here first. - -\item [\TeX{} Catalogue] If you are looking for a specific package, -font, program, etc., the \TeX{} Catalogue is the place to look. It is a -huge collection of all \TeX{}-related items. See -\OnCD{texmf-doc/doc/english/catalogue}, or -\url{http://www.ctan.org/tex-archive/help/Catalogue}. - -\item [\TeX{} Web Resources] The web page -\url{http://tug.org/interest.html} has many \TeX{}-related links, in -particular for numerous books, manuals, and articles on all aspects of -the system. - -\item [support archives] The two principal support forums are the -Usenet newsgroup \url{news:comp.text.tex} and the mailing list -\email{texhax@tug.org}. Their archives have years of past -questions and answers for your searching pleasure, via -\url{http://groups.google.com/groups?group=comp.text.tex} and -\url{http://tug.org/mail-archives/texhax}, respectively. And a general web -search, for example on \url{http://google.com}, never hurts. - -\item [asking questions] If you cannot find an answer, you can post to -\dirname{comp.text.tex} through Google or your newsreader, or to -\email{texhax@tug.org} through email. But before you post, -\emph{please} read this \acro{FAQ} entry on asking questions in such a -way that you're most likely to get an answer: -\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. - -\item [\TL{} support] If you want to report a bug or have -suggestions or comments on the \TL{} distribution, installation, or -documentation, the mailing list is \email{tex-live@tug.org}. However, -if your question is about how to use a particular program included in -\TL{}, you are better off writing to that program's maintainer or -mailing list. - -\end{description} - -The other side of the coin is helping others who have questions. Both -\dirname{comp.text.tex} and \code{texhax} are open to anyone, so feel -free to join, start reading, and help out where you can. Welcome to -\TeX{}! - - -% don't use \TL so the \uppercase in the headline works. Also so -% tex4ht ends up with the right TeX. Likewise the \protect's. -\section{Structure of \protect\TeX\protect\ Live} -\label{sec:struct-tl} - -This section describes the structure and contents of \TL{} and the -\TK{} of which it is a part. - -\subsection{Multiple distributions: \protect\pkgname{live}, - \protect\pkgname{inst}, - \protect\pkgname{protext}} -\label{sec:multiple-dist} - -Space limitations of \acro{CD-ROM} format have forced us to divide -\TK{} into several distributions, as follows. - -\begin{description} - -\item [live] A complete system on \acro{DVD}; it is too large -for \acro{CD}. It can be run live or installed to disk. It also -includes a snapshot of the \CTAN{} repository, the \pkgname{protext} -distribution for Windows and the Mac\TeX\ distribution for \MacOSX, entirely -independent of \TL{}, as well as assorted other packages in a -\texttt{texmf-extra} directory. - -\CTAN{}, \pkgname{protext}, Mac\TeX, and \texttt{texmf-extra} do not follow -the same copying conditions as \TL{}, so be careful when redistributing or -modifying. - -\item [inst(allable)] A complete system on \CD; in order to make this fit, -the packages and programs are compressed. Therefore, it is not possible -to run \TeX\ directly from the installable \CD, you have to install it -to disk (hence its name). Installation is described in subsequent sections. - -\item [protext] An enhancement of the \MIKTEX\ distribution for Windows, -\ProTeXt\ adds a few extra tools to \MIKTEX, and simplifies -installation. It is entirely independent of \TL{}, and has its own -installation instructions. It can be run live, or installed to disk. -The \ProTeXt\ home page is \url{http://tug.org/protext}. - -\ProTeXt\ is provided as both the top level of the \pkgname{live} \DVD\ -and on its own \CD\ (for those who cannot use the \DVD). - -\end{description} - -\noindent You can tell which type of distribution you're in by looking -for a \texttt{00\var{type}.TL} file at the top of the \TL{} directory. -This file also contains the \TL{} release date. - -Naturally, each user group chooses what to distribute, at its own -discretion. (\acro{TUG} is sending all three discs above to all of its -members.) - - -\subsection{Top level directories} -\label{sec:tld} - -Here is a brief listing and description of the top level directories in -the \TL{} distribution. On the \pkgname{live} \DVD, the entire \TL{} -hierarchy is in a subdirectory \dirname{texlive2005}, not at the top -level of the disc. - -\smallskip -\begingroup - \renewcommand{\arraystretch}{1.3} % open up interrow spacing -\begin{tabular}{>{\ttfamily}lp{.78\hsize}} -bin & The \TeX{} system programs, arranged by platform. \\ -source & The source of all programs, including the main \Webc{} - \TeX{} and \MF{} distributions. These are stored in a - \cmdname{bzip2}-compressed tar archive. \\ -support & Assorted auxiliary packages and programs. These are - \emph{not} installed automatically. This includes - assorted editors and \TeX\ shells. \\ -texmf & Tree for the programs, along with their support files and - documentation. Does not include \TeX\ formats and packages. - (\texttt{TEXMFMAIN} in the next section.) \\ -texmf-dist & The main tree of formats and packages. - (\texttt{TEXMFDIST} in the next section.) \\ -texmf-doc & Tree for self-contained pure documentation, arranged by - language. \\ -texmf-var & Tree for files automatically generated and stored. - (\texttt{TEXMFSYSVAR} in the next section.) \\ -xemtex & Tree for supporting programs used only in Windows. - These programs generally come pre-installed on Unix systems, or are - at least easy to compile. \\ -\end{tabular} -\endgroup - -\smallskip - -In addition to the directories above, the installation scripts and -\filename{README} files (in various languages) are at the top level of -the distribution. - -The \dirname{texmf-doc} directory contains only documentation, but -it does not contain all the documentation. The documentation for the -programs (manuals, man pages, Info files) is in \dirname{texmf/doc}, -since the programs are in \dirname{texmf}. Similarly, the documentation -for \TeX\ packages and formats is in \dirname{texmf-dist/doc}. You can -use the \cmdname{texdoc} or \cmdname{texdoctk} programs to find any -documentation wherever it's located. The comprehensive links in the -top-level file \OnCD{doc.html} may also be helpful. - - -\subsection{Overview of the predefined texmf trees} -\label{sec:texmftrees} - -This section lists all predefined variables specifying texmf trees used -by the system, and their intended purpose. The command \texttt{texconfig -conf} shows you the values of these variables, so that you can easily -find out how they map to directory names in your installation. - -\begin{ttdescription} -\item [TEXMFMAIN] The tree which holds vital parts of the system - such as helper scripts (e.g., \verb+web2c/mktexdir+), pool files and - other support files. -\item [TEXMFDIST] The tree which holds the main set of macro packages, - fonts, etc., as originally distributed. -\item [TEXMFLOCAL] The tree which administrators can use for system-wide - installation of additional or updated macros, fonts, etc. -\item [TEXMFHOME] The tree which users can use for their own individual - installations of additional or updated macros, fonts, etc. - The expansion of this variable depends on \verb+$HOME+ by default, % $ - which dynamically adjusts for each user to an individual - directory. -\item [TEXMFCONFIG] The tree used by te\TeX's utilities - \verb+texconfig+, \verb+updmap+, and \verb+fmtutil+ to store modified - configuration data. Under \verb+$HOME+ by default. %$ -\item [TEXMFSYSCONFIG] The tree used by te\TeX's utilities - \verb+texconfig-sys+, \verb+updmap-sys+, and \verb+fmtutil-sys+ to - store modified configuration data. -\item [TEXMFVAR] The tree used by \verb+texconfig+, \verb+updmap+ and - \verb+fmtutil+ to store (cached) runtime data such as format files and - generated map files. Under \verb+$HOME+ by default. %$ -\item [TEXMFSYSVAR] The tree used by \verb+texconfig-sys+, - \verb+updmap-sys+ and \verb+fmtutil-sys+ to store (cached) runtime - data such as format files and generated map files. -\end{ttdescription} - -For more discussion of \texttt{texconfig} and related utilities, please -see section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig}. - - -\subsection{Extensions to \protect\TeX} -\label{sec:tex-extensions} - -\TL{} contains several extended versions of \TeX: - -\begin{description} - -\item [\eTeX] adds a small but powerful set of new primitives -\label{text:etex} (related to macro expansion, character scanning, -classes of marks, additional debugging features, and more) and the -\TeXXeT{} extensions for bidirectional typesetting. In default mode, -\eTeX{} is 100\% compatible with ordinary \TeX. See -\OnCD{texmf-dist/doc/etex/base/etex_man.pdf}. - -\item [pdf\TeX] writes Acrobat \acro{PDF} format as well as \dvi{}. The -\LaTeX{} \pkgname{hyperref} package has an option `\optname{pdftex}' -which turns on all the program features. See -\OnCD{texmf/doc/pdftex/manual/} for the manual, and -\OnCD{texmf/doc/pdftex/manual/samplepdf/samplepdf.tex}. - -\item [pdfe\TeX] combines the pdf\TeX\ and \eTeX\ extensions. This is -the default program for all formats except plain \TeX. -See above for documentation. - -\item [\OMEGA\ (Omega)] is based on Unicode (16-bit characters), thus -supports working with almost all the world's scripts simultaneously. It -also supports so-called `\OMEGA{} Translation Processes' (\acro{OTP}s), -for performing complex transformations on arbitrary input. See -\OnCD{texmf-dist/doc/omega/base/doc-1.8.tex} (not completely up-to-date). - -\item [Aleph] combines the \OMEGA\ and \eTeX\ extensions. -See \OnCD{texmf-dist/doc/aleph/base} for some minimal documentation. - -\end{description} - - -\subsection{Other notable programs in \protect\TL} - -Here are a few other commonly-used programs included in \TL{}: - -\begin{cmddescription} - -\item [bibtex] bibliography support. - -\item [makeindex] index support. - -\item [dvips] convert \dvi{} to \PS{}. - -\item [xdvi] \dvi{} previewer for the X Window System. - -\item [dvilj] \dvi{} drive for the HP LaserJet family. - -\item [dv2dt, dt2dv] convert \dvi{} to/from plain text. - -\item [dviconcat, dviselect] cut and paste pages -from \dvi{} files. - -\item [dvipdfmx] convert \dvi{} to \acro{PDF}, an alternative approach -to pdf\TeX\ (mentioned above). See the \pkgname{ps4pdf} and -\pkgname{pdftricks} packages for still more alternatives. - -\item [psselect, psnup, \ldots] \PS{} -utilities. - -\item [lacheck] \LaTeX{} syntax checker. - -\item [texexec] Con\TeX{}t and \acro{PDF} processor. - -\item [tex4ht] \TeX{} to \acro{HTML} converter. - -\end{cmddescription} - - -\section{Unix installation} -\label{sec:unix-install} - -As introduced in section~\ref{sec:basic} (\p.\pageref{sec:basic}), -\TL{} has three principal uses: - -\begin{enumerate} -\item Run directly from media. -\item Install to disk. -\item Integrate a particular package or collection into your existing -\TeX{} installation. -\end{enumerate} - -\noindent The following sections describes the Unix-specific procedures -for each of these. - -\ifSingleColumn \begin{figure}[ht]\noindent \fi -\begin{warningbox} -\textbf{Warning: } The \TK{} \CD{}s and \DVD{} are in ISO 9660 (High Sierra) -format, \emph{with} Rock Ridge (and Joliet, for Windows) -extensions. Therefore, in order to take full advantage of the \TK{} -under Unix, your system needs to be able to use the Rock Ridge -extensions. Please consult the documentation for your \cmdname{mount} -command to see how to do this. If you have several different machines -on a local network, you may be able to mount the discs on one which -does support Rock Ridge, and use this with the others. - -\leavevmode\quad Modern systems should be able to use the discs without -problems. If troubles, let us know. The discussion below assumes you -have been able to mount the \CD{}s with full Rock Ridge compatibility. -\end{warningbox} -\ifSingleColumn\end{figure}\fi - - -% -\subsection{Running \protect\TL{} directly from media (Unix)} - -\def\runlive{% text repeated in windows section -It is possible to use the \TeX{} system directly from the \pkgname{live} -\DVD{}, without installing the distribution to disk. (Thus the name -\TeX\ `Live', in fact.) It is \emph{not} possible to run \TeX{} -directly from the other \CD{}s (see section~\ref{sec:multiple-dist}, -\p.\pageref{sec:multiple-dist}). -} - -\def\startinst{% repeated in other subsections -To start, you mount the \CD{} or \DVD{}, with Rock Ridge extensions -enabled. The exact command to do this varies from system to system; the -following works under Linux, except the name of the device -(\filename{/dev/cdrom}, here) may vary. (All our examples will use -\texttt{>} as the shell prompt; user input is -\Ucom{\texttt{underlined}}.) -\begin{alltt} -> \Ucom{mount -t iso9660 /dev/cdrom /mnt/cdrom} -\end{alltt} - -\noindent Change the current directory to the mount point: -\begin{alltt} -> \Ucom{cd /mnt/cdrom} -\end{alltt} - -\noindent Under \MacOSX, the directory is typically under -\dirname{/Volumes}, and the media will be mounted automatically. -} - -\def\installtlsh{ -Run the installation script \filename{install-tl.sh}: -\begin{alltt} -> \Ucom{sh install-tl.sh}\\ -Welcome to TeX Live... -\end{alltt} - -\noindent After various greeting messages and a list of the main menu -options, the installation will ask you to enter a command. Do this by -typing the desired character and hitting return; don't type the angle -brackets shown. Either uppercase or lowercase is ok; we'll use -lowercase in our examples. -} - -\runlive -\startinst -\installtlsh - -For running live, our first command will be \Ucom{d} and then the -subcommand \Ucom{1} to set directories. Even in this case, we must -choose a directory on the local disk to place files that the \TeX{} -system itself generates, such as fonts and formats, and also to provide -a place for updated configuration files, if need be. - -We'll use \dirname{/opt/texlive2005} in this example. It's good to -include the year in the name, as these generated files are not -compatible from release to release. (If the default value of -\dirname{/usr/local/texlive/2005} works for you, then you can skip this -step.) - -\begin{alltt} -Enter command: \Ucom{d} -Current directories setup: -<1> TEXDIR: /usr/local/texlive/2005 -... -Enter command: \Ucom{1} -New value for TEXDIR [/usr/local/texlive/TeX]: \Ucom{/opt/texlive2005} -... -Enter command: \Ucom{r} -\end{alltt} - -\noindent Back at the main menu, our second and last command is -\Ucom{r}, to set up for running live off the media without installing -to disk: -\begin{alltt} -Enter command: \Ucom{r} -Preparing destination directories... -... -Welcome to TeX Live! -> -\end{alltt} - -\noindent And we are back at the system prompt, as shown. - -Next, it is necessary to alter two environment variables: -\envname{PATH}, to an architecture-dependent value (so that we can run -the programs), and \envname{TEXMFSYSVAR}, to the value specified above. -See table~\ref{tab:archlist} for a list of the architecture names for -the different systems. - - -\def\textruntexconfig{% -After the main installation has completed, and environment variables -have been set, the last step is to run \cmdname{texconfig} or -\cmdname{texconfig-sys} to customize your installation to your needs. -This is explained in section~\ref{sec:texconfig}, -\p.\pageref{sec:texconfig}. -} -\textruntexconfig - -\begin{table*}[ht] -\caption[Supported system architectures.]{Supported system -architectures.} -\label{tab:archlist} -\begin{tabular}{>{\ttfamily}ll} -alpha-linux & HP Alpha GNU/Linux \\ -%alphaev5-osf4.0d & HP Alphaev5 OSF \\ -%hppa2.0-hpux10.20 & HP9000 HPUX 10.20 \\ -i386-darwin & Intel x86 \MacOSX \\ -i386-freebsd & Intel x86 FreeBSD \\ -i386-linux & Intel x86 GNU/Linux \\ -%i386-openbsd3.3 & Intel x86 OpenBSD \\ -%i386-solaris2.8 & Intel x86 Solaris \\ -mips-irix & SGI IRIX \\ -powerpc-aix & IBM RS/6000 AIX \\ -powerpc-darwin & PowerPC \MacOSX \\ -sparc-linux & Sun Sparc GNU/Linux \\ -sparc-solaris & Sun Sparc Solaris \\ -win32 & Windows (32-bit) \\ -x86\_64-linux & Intel x86 64-bit GNU/Linux \\ -\hline -\end{tabular} -\end{table*} - -\label{text:path} -The syntax for setting the environment variables, and the initialization -file to put them in, depends on the shell you use. If you use a -Bourne-compatible shell (\cmdname{sh}, \cmdname{bash}, \cmdname{ksh}, et -al.), put the following into your \filename{$HOME/.profile} file: -\begin{alltt} -PATH=/mnt/cdrom/bin/\var{archname}:$PATH; export PATH -TEXMFSYSVAR=/opt/texlive2005/texmf-var; export TEXMFVAR -\end{alltt} - -\noindent For C shell-compatible shells (\cmdname{csh}, \cmdname{tcsh}), -put the following into your \filename{$HOME/.cshrc} file: -\begin{alltt} -setenv PATH /mnt/cdrom/bin/\var{archname}:$PATH -setenv TEXMFSYSVAR /opt/texlive2005/texmf-var -\end{alltt} - -\noindent Then log out, log back in, and test your installation -(see section~\ref{sec:test-install}, \p.\pageref{sec:test-install}). - -\def\textifindoubt{% -If in doubt, please ask any local system gurus to help you with -problems; for example, the way to mount the \TL{} media, which -directory or directories to use, and precise details of the changes to -your personal initialization files can and do vary from site to site. -} -\textifindoubt - - -% -\subsection{Installing \protect\TeX\protect\ Live to disk} -\label{sec:unix-install-disk} - -It is possible, indeed typical, to install the \TL{} distribution to -hard disk. This can be done from either the \pkgname{live} or -\pkgname{inst} distributions. (See section~\ref{sec:multiple-dist}, -\p.\pageref{sec:multiple-dist}, for an explanation of the different -distributions.) - -\startinst -\installtlsh - -Table~\ref{tab:main-menu-options} briefly lists the options in the main -menu. The order in which you select the options makes little -difference, except that \Ucom{i} must be last. It's reasonable to go -through them in the order presented here. - -% apparently here.sty [H] doesn't support table*. -\begin{table}[H] -\caption{Main menu options for the installation.} -\label{tab:main-menu-options} -\begin{tabular}{>{\ttfamily}ll} -p & The platform you are running on.\\ -b & The architectures for which to install binaries.\\ -s & The base installation scheme to use (minimal, recommended, - full, etc.)\\ -c & Override the base scheme for individual collections.\\ -l & Override for language collections.\\ -d & Directories in which to install.\\ -o & Other options.\\ -i & Perform the installation.\\ -\end{tabular} -\end{table} - -Here are further details on each option. - -\textbf{\optname{p} -- Current platform.} Since the installation script -automatically guesses which platform you're running on, it is usually -unnecessary to use this option. It's there in case you need to override -the automatic detection. - -\textbf{\optname{b} -- Binary architectures.} By default, only the -binaries for your current platform will be installed. From this menu, -you can select installation of binaries for other architectures as well -(or omit installing the current platform). This can be useful if you are -sharing a \TeX\ tree across a network of heterogenous machines. For a -list of the supported architectures, see table~\ref{tab:archlist}, -\p.\pageref{tab:archlist}. - -\textbf{\optname{s} -- Base installation scheme.} From this menu, you -can choose an overall set of package collections, called a ``scheme''. -The default \optname{full} scheme installs everything available, but you -can also choose the \optname{basic} scheme for a minimal system, or -\optname{medium} to get something in between. There are also specific -sets for Omega and \acro{XML}. - -\textbf{\optname{c} -- Individual collections.} From this menu, you can -override the scheme's set of collections to install. Collections are -one level more detailed than schemes\Dash collections consist of one or -more packages, where packages (the lowest level grouping in \TL) contain -the actual \TeX\ macro files, font families, and so on. In this menu, -selection letters are case-sensitive. - -\textbf{\optname{l} -- Language collections}. This menu has the same -basic purpose as \Ucom{c}, to override the collection set in the chosen -scheme. In this case, the collections are specifically for different -languages. Selection letters are case-sensitive here too. Here is a -list of the language collections in \TL: - -% xx really should generate list from texmf/tpm/collection/tex-lang* -% a la install-tl.sh. -\begin{tabbing} -\hspace{.25\linewidth} \= -\hspace{.25\linewidth} \= -\hspace{.25\linewidth} \= -\hspace{.25\linewidth} \kill -(some) African scripts \> -Arabic \> -Armenian \> -Chinese\,Japanese\,Korean \\ -Croatian \> -Cyrillic \> -Czech/Slovak \> -Danish \\ -Dutch \> -Finnish \> -French \> -German \\ -Greek \> -Hebrew \> -Hungarian \> -Indic \\ -Italian \> -Latin \> -Manju \> -Mongolian \\ -Norwegian \> -Polish \> -Portuguese \> -Spanish \\ -Swedish \> -Tibetan \> -\acro{UK} English \> -Vietnamese \\ -\end{tabbing} - -\noindent Language collections typically include fonts, macros, -hyphenation patterns, and other support files. (For instance, -\pkgname{frenchle.sty} is installed if you select the \optname{French} -collection.) In addition, installing a language collection will alter -the \filename{language.dat} configuration file controlling which -hyphenation patterns are loaded. - -\textbf{\optname{d} -- Installation directories}. Three directories can -be changed here: -\label{text:instdir} - -\begin{ttdescription} -\item [TEXDIR] The top-level directory under which -everything else will be installed. The default value is -\dirname{/usr/local/texlive/2005}, and is often changed. We recommend -including the year in the name, to keep different releases of \TL{} -separate. (You may wish to make a version-independent name such -\dirname{/usr/local/texlive} via a symbolic link, which you can then -update after testing the new release.) - -Under \MacOSX, the usual frontends look for \TeX{} in -\dirname{/usr/local/teTeX}, so you may wish to install \TL{} there. - -\item [TEXMFLOCAL] This tree is where the \TeX{} system (not as part of -the initial installation, but rather as time goes by) puts -non-version-specific files, primarily fonts. The default value is -\dirname{/usr/local/texlive/texmf-local}, independent of the current -\TL{} release, because it's also the recommended location to put any -local packages or configuration settings. - -\item [TEXMFSYSVAR] This tree is where \cmdname{texconfig-sys} puts -files that \emph{are} version-specific. The default value is -\dirname{TEXDIR/texmf-var}, and there's generally no reason to change -it. There is also \envname{TEXMFSYSCONFIG}, which is where -\cmdname{texconfig} looks for modified configuration data. See -section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig} for more -information. - -\end{ttdescription} - -\textbf{\optname{o} -- Other options.} From this menu, you can select -the following general options: - -\begin{ttdescription} -\item [a] Specify an alternate directory for generated fonts. -The default is to use the \envname{TEXMFVAR} tree, as explained above. -Setting this is useful if you plan to mount the main tree read-only, and -therefore you need another location (perhaps host-specific) for -dynamically created fonts. - -\item [l] Create symbolic links for the binaries, man pages, -and\slash or \acro{GNU} Info files in other locations. For example, you may -wish to make the man pages available under \dirname{/usr/local/man} and -the Info files available under \dirname{/usr/local/info}. (Of course -you need appropriate privileges to write in the specified directories.) - -It is not advisable to overwrite a \TeX\ system that came with your -system with this option. It's intended primarily for creating the links -in standard directories that are known to users, such as -\dirname{/usr/local/bin}, which don't already contain any \TeX\ files. - -\item [d] Skip installation of the font/macro documentation tree. -This is useful if you need to save space, or if you've previously -installed the documentation elsewhere. - -\item [s] Skip installation of the main font/macro source -tree. This is useful if you are arranging to share that tree between -machines and\slash or architectures in some other way, such as \acro{NFS}. - -\end{ttdescription} - -\textbf{i -- Perform installation.} When you're satisfied with your -configuration options, enter \Ucom{i} to actually do the installation -from the media to your chosen locations. - -% text is similar to above, but no TEXMFSYSVAR, so we have to write out. -After the installation completes, your next step is to include the -architecture-specific subdirectory of \dirname{TEXDIR/bin} in your -\envname{PATH}, so the newly-installed programs can be found. The -architecture names are listed in table~\ref{tab:archlist}, -\p.\pageref{tab:archlist}, or you can simply list the directory -\dirname{TEXDIR/bin}. - -The syntax for doing this, and the initialization file to use, depends -on your shell. If you use a Bourne-compatible shell (\cmdname{sh}, -\cmdname{bash}, \cmdname{ksh}, et al.), put the following into your -\filename{$HOME/.profile} file: - -\begin{alltt} -PATH=/usr/local/texlive/2005/bin/\var{archname}:$PATH; export PATH -\end{alltt} - -\noindent For C shell-compatible shells (\cmdname{csh}, \cmdname{tcsh}), -put the following into your \filename{$HOME/.cshrc} file: -\begin{alltt} -setenv PATH /usr/local/texlive/2005/bin/\var{archname}:$PATH -\end{alltt} - -\textruntexconfig - -Here is a minimal annotated example which accepts the default -directories and installs binaries for the current system only. Thus, -only one command is needed, \Ucom{i} for install. The \texttt{>} is the -shell prompt as usual. - -\begin{alltt} -> \Ucom{sh install-tl.sh} -\Ucom{i} # perform installation -> \Ucom{texconfig} ... # see section \ref{sec:texconfig} -# New PATH element, with Linux as the example: -> \Ucom{PATH=/usr/local/texlive/2005/bin/i386-linux:$PATH; export PATH} -\end{alltt} - -\textifindoubt - - -% -\subsection{Installing individual packages to disk} - -You can add individual packages or collections from the current -distribution to an existing non-\TL{} setup, or an earlier -\TL{} installation. - -\startinst - -Run the installation script \filename{install-pkg.sh} (not -\filename{install-tl.sh}, which is intended for complete installations -only): -\begin{alltt} -> \Ucom{sh install-pkg.sh \var{options}} -\end{alltt} - -The first set of options controls what gets read: - -\begin{ttdescription} -\item [-{}-package=\var{pkgname}] The individual package to work on. - -\item [-{}-collection=\var{colname}] The individual collection to work on. - -\item [-{}-nodoc] Exclude documentation files from the operation. - -\item [-{}-nosrc] Exclude source files from the operation. - -\item [-{}-cddir=\var{dir}] Source directory to read from; defaults -to the current directory. If you followed the instructions above, that -will be the distribution directory, and won't need to be changed. - -\item [-{}-listdir=\var{dir}] The so-called `lists' directory within -\var{cddir} from which to read the package information. The only -reason to change the default is if you're making changes to \TL{} -yourself. - -\end{ttdescription} - -What actually happens is controlled by the following options. If -neither of these are specified, the default action is to install the -selected files. The main destination tree is found by expanding -\envname{\$TEXMFMAIN} with \cmdname{kpsewhich}. You can override it by -setting either the environment variable \envname{TEXMFMAIN} or -\envname{TEXMF}. - -\begin{ttdescription} -\item [-{}-listonly] List the files that would be installed, but don't -actually install anything. - -\item [-{}-archive=\var{tarfile}] Instead of installing the files into -the \TeX{} system, make a \cmdname{tar} archive. - -\end{ttdescription} - -Additional options: - -\begin{ttdescription} - -\item [-{}-config] After installation, run \code{texconfig init}. - -\item [-{}-nohash] After installation, don't run \cmdname{mktexlsr} to -rebuild the filename database. - -\item [-{}-verbose] Give more information as the script runs. - -\end{ttdescription} - -Here are some usage examples: - -\begin{enumerate} - -\item To see the files in the package \pkgname{fancyhdr} without -installing it: - -\begin{alltt} -\ifSingleColumn> \Ucom{sh install-pkg.sh --package=fancyhdr --listonly} -\else> \Ucom{sh install-pkg.sh --package=fancyhdr \bs} -> \Ucom{--listonly} -\fi{} -texmf/doc/latex/fancyhdr/README -texmf/doc/latex/fancyhdr/fancyhdr.pdf -... -\end{alltt} - -\item Install the \LaTeX{} package \pkgname{natbib}: -\begin{alltt} -> \Ucom{sh install-pkg.sh --package=natbib} -\end{alltt} - -\item Install the \LaTeX{} package \pkgname{alg} without source files or -documentation: -\begin{alltt} -\ifSingleColumn> \Ucom{sh install-pkg.sh --package=alg --nosrc --nodoc} -\else> \Ucom{sh install-pkg.sh -{}-package=alg \bs} -> \Ucom{-{}-nosrc -{}-nodoc} -\fi\end{alltt} - -\item Install all the packages in the collection of additional -plain \TeX\ macros: -\begin{alltt} -> \Ucom{sh install-pkg.sh --collection=tex-plainextra} -\end{alltt} - -\item Write all files in the \pkgname{pstricks} package to a -\cmdname{tar} file in \path|/tmp|: -\begin{alltt} -\ifSingleColumn> \Ucom{sh install-pkg.sh --package=pstricks --archive=/tmp/pstricks.tar} -\else -> \Ucom{sh install-pkg.sh -{}-package=pstricks \bs} -> \Ucom{-{}-archive=/tmp/pstricks.tar} -\fi\end{alltt} - -\end{enumerate} - -\textifindoubt - - -% -\section{Post-installation} -\label{sec:postinstall} - -After the main installation is done, for any operating system, the -remaining steps are to configure the system for your local needs, and -perform some basic tests. - -Another sort of post-installation is to acquire packages, fonts, or -programs that were not included in \TL{}. The basic idea is to -install such additions in the \envname{TEXMFLOCAL} tree (if you -installed to disk), or \envname{TEXMFSYSVAR} (if you are running live). -See the ``Installation directories'' option on \p.\pageref{text:instdir}. - -Unfortunately, the details can and do vary widely, and so we do not attempt to -address them here. Here are some external links to descriptions: -\begin{itemize*} -\item -\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instpackages} -\item -\url{http://www.ctan.org/installationadvice} -\item -\url{http://www.ctan.org/tex-archive/info/beginlatex/html/chapter5.html#pkginst} -\item -\url{http://www.ctan.org/tex-archive/info/Type1fonts} for -installation information for fonts in particular. -\end{itemize*} - - -\subsection{The \protect\cmdname{texconfig} program} -\label{sec:texconfig} - -At any time after installation, you can and should use the program -\cmdname{texconfig} to configure the system to fit your local needs. It -is installed in the architecture-specific subdirectory -\texttt{TEXDIR/bin/\var{arch}} along with everything else. - -If you run it without arguments, it will enter full-screen mode and -allow you to view and change options interactively. - -You can also run it with various command-line options. Here are some of -the most common (\TL{} is configured for the A4 paper size by default): - -\begin{ttdescription} - -\item [texconfig paper letter] Set default paper size for -various programs and drivers (\cmdname{pdftex}, \cmdname{dvips}, -\cmdname{dvipdfm}, \cmdname{xdvi}) to be \acro{US} letter. The other -allowable size is \optname{a4}, which is the default. - -\item [texconfig rehash] Update all the \TeX{} ``filename databases'', -after adding or removing files. - -\item [texconfig faq] Show the \teTeX{} \acro{FAQ}. -(See also the main \TeX{} \acro{FAQ} in \OnCD{texmf-doc/doc/english/FAQ-en}.) - -\item [texconfig help] Output help information for \cmdname{texconfig}. - -\end{ttdescription} - -Of course, \cmdname{texconfig} can only support changing a few of the -many options and configuration parameters in a \TeX{} system. The main -configuration file for the base \Webc{} programs is named -\filename{texmf.cnf}. You can find its location by running -\samp{kpsewhich texmf.cnf}; it contains many comments explaining the -default settings and useful alternatives. - -As of 2005, \cmdname{texconfig} alters files in a user-specific -directory, namely \dirname{$HOME/.texlive2005}. If you install \TeX\ -just for yourself, that is unlikely to make a difference. But if you -install \TeX\ on a multi-user system, you will want to change the -configuration for the whole system. In this case, run -\cmdname{texconfig-sys} instead of \cmdname{texconfig}. - -Likewise, the \cmdname{updmap} and \cmdname{fmtutil} scripts were -changed, to work under \dirname{$HOME/.texlive2005}. To alter system -directories, use \cmdname{updmap-sys} and \cmdname{fmtutil-sys}. - -In particular, for multi-user systems, you will probably want to -pregenerate the standard formats with \texttt{fmtutil-sys --missing}. -Otherwise, each user will end up with their own formats. - -Also, if you have a personally-modified copy of \filename{fmtutil.cnf} -or \filename{updmap.cfg}, instead of using the ones generated by -installation, they must be installed in the tree referenced by the -variable \envname{TEXMFSYSCONFIG}. - -The variables specifying the directories altered by these commands are -listed in section~\ref{sec:texmftrees}, \p.\pageref{sec:texmftrees}. -You can see the actual directories by running \texttt{texconfig conf}, -and you can change them by editing \filename{texmf.cnf}. - - -\subsection{Testing the installation} -\label{sec:test-install} - -After installing \TL{} as best you can, you naturally want to test -it out, so you can start creating beautiful documents and\slash or fonts. - -This section gives some basic procedures for testing that the new system -is functional. We give Unix commands; under \MacOSX{} and Windows, -you're more likely to run the tests through a graphical interface, but -the principles are the same. - -\begin{enumerate} - -\item Make sure that you can run the \cmdname{tex} program in the first -place: - -\begin{alltt} -> \Ucom{tex -{}-version} -TeX 3.141592 (Web2C 7.5.5) -kpathsea version 3.5.5 -... -\end{alltt} -If this comes back with `command not found' instead of version and -copyright information, most likely you don't have the correct -\dirname{bin} subdirectory in your \envname{PATH}. See -the environment-setting information on \p.\pageref{text:path}. - -\item Process a basic \LaTeX{} file: -\begin{alltt} -> \Ucom{latex sample2e.tex} -This is pdfeTeXk, Version 3.141592... -... -Output written on sample2e.dvi (3 pages, 7496 bytes). -Transcript written on sample2e.log. -\end{alltt} -If this fails to find \filename{sample2e.tex} or other files, perhaps -you have interference from old environment variables or configuration -files. For a deep analysis, you can always ask \TeX{} to report on -exactly what it is searching for, and finding; see ``Debugging actions'' -on page~\pageref{Debugging}. - -\item Preview the result online: -\begin{alltt} -> \Ucom{xdvi sample2e.dvi} -\end{alltt} -(Under Windows, the analogous command is \cmdname{windvi}.) You should -see a new window with a nice document explaining some of the basics of -\LaTeX{}. (Well worth reading, by the way if you're new to the system.) -You do have to be running under X for \cmdname{xdvi} to work; if you're -not, or your \envname{DISPLAY} environment variable is set incorrectly, -you'll get an error \samp{Can't open display}. - -\item Create a \PS{} file for printing or display: -\begin{alltt} -> \Ucom{dvips sample2e.dvi -o sample2e.ps} -\end{alltt} - -\item Create a \acro{PDF} file instead of \dvi{}; this processes the -\filename{.tex} file and writes \acro{PDF} directly: -\begin{alltt} -> \Ucom{pdflatex sample2e.tex} -\end{alltt} - -\item Preview the \acro{PDF} file: -\begin{alltt} -> \Ucom{gv sample2e.pdf} -\textrm{or:} -> \Ucom{xpdf sample2e.pdf} -\end{alltt} -Unfortunately neither \cmdname{gv} nor \cmdname{xpdf} are currently -included in \TL{}, so you must install them separately. See -\url{http://www.gnu.org/software/gv} and -\url{http://www.foolabs.com/xpdf}, respectively. - -\item Other standard test files you may find useful: - -\begin{ttdescription} -\item [small2e.tex] A simpler document than \filename{sample2e}, to -reduce the input size if you're having troubles. -\item [testpage.tex] Test if your printer introduces any offsets. -\item [nfssfont.tex] For printing font tables and tests. -\item [testfont.tex] Also for font tables, but using plain \TeX{}. -\item [story.tex] The most canonical (plain) \TeX{} test file of all. -You must type \samp{\bs bye} to the \code{*} prompt after \samp{tex -story.tex}. -\end{ttdescription} -You can process these in the same way as we did with -\filename{sample2e.tex}. - -\end{enumerate} - -If you are new to \TeX{}, or otherwise need help with actually -constructing \TeX{} or \LaTeX{} documents, please visit -\url{http://tug.org/begin.html} for some introductory resources. - - -\section{\MacOSX{} installation} -\label{sec:mac-install} - -The recommended way to install \TeX\ on \MacOSX\ is from the Mac\TeX\ -distribution, new in 2005. This is provided on the \pkgname{live} -\DVD{} in the top-level \dirname{mactex/} directory. It contains its -own (native) installer for a full \TeX\ distribution, based on a -combination of te\TeX\ and \TL, along with many additional applications -and documentation. The project web page is \url{http://tug.org/mactex}. - -If you prefer, installation of \TeX{} under \MacOSX{} can also be done -directly from \TL, using the \filename{install*} scripts, as follows. - -In order to run the installation scripts under \MacOSX, you need to have -the \cmdname{bash} shell installed. If you are running \MacOSX~10.2 -or later, you have \cmdname{bash}, and can proceed. If you're running -an earlier \MacOSX{} version, however, the default shell is -\cmdname{zsh}, which won't work; you'll need to get \cmdname{bash} from -the Internet, or more likely upgrade your system. - -Once you have \cmdname{bash}, the Unix installation documentation in the -previous section can be followed. See section~\ref{sec:unix-install} on -\p.\pageref{sec:unix-install}; \MacOSX-specific notes are included there -where needed. - -\section{Windows installation} -\label{sec:win-install} - -In this release of \TL{}, happily, the distribution once -again has a native Windows installer, named \cmdname{tlpmgui.exe}. (See -section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}, for an -explanation of the different distributions.) - -\cmdname{tlpmgui} has essentially the same options as the Unix -installer, only done through a GUI interface: selecting schemes, -individual collections, installation directories, and so on. -Section~\ref{sec:unix-install-disk} on -\p.\pageref{sec:unix-install-disk} describes the basic elements. It -also allows some post-installation activities such as adding/removing -packages, updating the filename database and building formats. -Moreover, \cmdname{tlpmgui} can setup the system for running -programs directly from the \DVD. - -For those who like to look underneath the hood, \cmdname{tlpmgui} uses -as its ``engine'' a command-line Windows program named \cmdname{tlpm}. - -The Windows \TeX{} system included in \TL{} is based on new binaries -borrowed from the \XEmTeX{} project, formerly known as \fpTeX{} (see -\url{http://www.metz.supelec.fr/~popineau/xemtex-1.html}). -It also includes some older (but still working) tools, notably -a \texttt{dvi} previewer, \textsf{Windvi}, which is similar in usage to -the established Unix \textsf{xdvi}. The documentation can be found in -\OnCD{texmf/doc/html/windvi/windvi.html}. - -\TL{} can be installed on systems running Windows 98, \acro{ME}, -\acro{NT}, \acro{2K} or \acro{XP}. Older versions of Windows (3.1x) -and \acro{MS-DOS} are not supported. - -\textbf{Warning:} Win9.x users must ensure they have enough environment - space before undertaking installation. The \cmdname{tlpmgui.exe} - program won't change the environment size for them. A few environment - variables will be created and it is possible you run out of - environment space. Add \texttt{SHELL=COMMAND.COM /E:4096 /P} in the - config.sys file in order to increase your environment size. - -\subsection{Installing \protect\TeX\protect\ Live to disk} - -After inserting the \TL{} CD into the \acro{CD} drive, autostart should -activate \cmdname{tlpmgui}. If it does not, click \guiseq{Start\arw Run}, -then type \verb|:\setup-win32\tplmgui.exe| (or -\verb|:\texlive\setup-win32\tplmgui.exe| if you are -installing from the TeX Collection DVD), where \verb|| -is the drive letter with the TeX Live CD (or TeX Collection DVD), and -then click OK. - -The installation window titled \guiseq{TeX Live installation and maintenance -utility} should open. It contains the following sections: \guiseq{Main -customization}, \guiseq{Install}, \guiseq{Select a scheme}, \guiseq{Select -systems}, \guiseq{Directories} and \guiseq{Options}. - -In the \guiseq{Directories} section the installation drive (directory) next -to the \guiseq{CD/DVD} button should be displayed (e.g., \texttt{F:/} or \texttt{F:/texlive/} for the DVD), but -if it is not, then click the \guiseq{CD/DVD} button and select the \acro{CD/DVD} -drive, with the \TL{} CD (or TeX Collection DVD). - -The directory in which you wish to install the software can be set by -clicking the \guiseq{TLroot} button. This directory will be set as -\path|TLroot| environment variable for later usage. The \path|TEXMFTEMP| and -\path|TEXMFCNF| environment variables as displayed next to the -\guiseq{TEXMFTEMP} and \guiseq{TEXMFCNF} buttons will be adjusted -automatically and set during installation, but they can also be adjusted -manually now to suit special needs. - -In the \guiseq{Select a scheme} section the desired \TL{} installation scheme -should be chosen by clicking the radio button labelled with the installation -scheme name (e.g., \guiseq{scheme-gust}). Each scheme is accompanied by an -\guiseq{Info} button which, when clicked, displays a short description of the -relevant scheme. - -A scheme is a large set of files targeted at some kind of usage. There are -generic schemes for basic, medium and full installations. The remaining ones -are either targeted at certain LUGs (i.e., what GUST or GUTenberg propose -for their members) or application targeted (e.g., for XML and \TeX{} -cooperation). A preselected scheme can be refined. This is done in the -\guiseq{Main customization} section by choosing additional collections from -\guiseq{Standard collections} or \guiseq{Language collections}. For example, -by clicking the \guiseq{Select} button labelled \guiseq{Standard -collections}, additional collections like Metapost, Omega or documentation -in different languages can be selected. - -\textbf{Note:} The \guiseq{Ghostscript}, \guiseq{Perl} and \guiseq{Wintools} -collections are selected by default and should be installed unless they are -already installed and you really know what you are doing. This is because -they are required by many important tools. The \verb|PERL5LIB| and -\verb|GS_LIB| environment variables will be set too. - -Next, clicking the \guiseq{Select} button labelled \guiseq{Language -Collections} in the \guiseq{Main customization} section opens the -\guiseq{Language collections} window in which the installation language can -be chosen by ticking the box next to the language. - -Next, click the \guiseq{Install} button in the \guiseq{Install} section to -start the installation proper process. - -The \TL{} system needs some post-processing steps (format files -generation, ls-R databases generation, environment variables, etc.). All -these operations are done there, some of them can be lengthy. So please wait -until you see a statement about the successfully finished installation. - -The shortcut for \cmdname{tlpmgui} will be added to the -\guiseq{Start\arw Programs\arw TeXLive2005} menu. - -If it is needed (Win9x/WinME), you will be asked to reboot your computer. - -\subsection{Support packages for Windows} -\label{sec:win-xemtex} - -To be complete, a \TL installation needs support packages that are not -commonly found on a Windows machine. Many scripts are written using the Perl -language. Some important tools require the Ghostscript \PS{} interpreter to -render or to convert files. A graphic file toolbox is also needed in some -cases. Last but not least, a \TeX-oriented editor makes it easy to type in -your \TeX{} files. - -All these tools are quite easy to find for Windows, but in order to try to -make your life even easier, we have put such a set of tools on \TL: -\begin{itemize*} -\item GNU \cmdname{Ghostscript} 7.07 -\item a minimal \cmdname{Perl} 5.8, sufficient to run all the \TL{} - Perl scripts. -\item win-tools is a set of small programs (bzip2, gzip, jpeg2ps - and tiff2png) -%\item a subset of \cmdname{ImageMagick} 5.5.6 -%\item the \cmdname{ISpell} checker -%\item \cmdname{XEmacs} 21.5.14 with a selection of packages to support -%\TeX{} typesetting. -\end{itemize*} - -These packages are borrowed from the \XEmTeX{} distribution -(the successor of fp\TeX). - -Perl and Ghostscript are installed by default; you may explicitly -deselect them during installation if you already have them. - -If you don't want to install this bundle, then you are on your own to -install the required tools to complete your \TL{} system. Here is a -list of places to get those tools: - -\begin{description} -\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} -\item[Perl] \url{http://www.activestate.com/} (but you might need some - supplementary packages from CPAN: \url{http://www.cpan.org/}) -\item[ImageMagick] \url{http://www.imagemagick.com} -\item[NetPBM] alternatively, you could use NetPBM instead of ImageMagick to - process or convert your graphic files. NetPBM home page is - \url{http://netpbm.sourceforge.net/} -\item[\TeX-oriented editors] There is a wide choice, and it is a matter of the - user's taste. Here is a selection: - \begin{itemize*} - \item \cmdname{GNU Emacs} is available natively under Windows, see - \url{http://www.gnu.org/software/emacs/windows/ntemacs.html} - \item \cmdname{XEmacs} is available natively under Windows, see - \url{http://www.xemacs.org/} - \item \cmdname{WinShell} is available on \TL in the \path|support| - directory, see \url{http://www.winshell.de} - \item \cmdname{WinEdt} is shareware available from \url{http://www.winedt.com} - \item \cmdname{Vim} is available on \TL{} in the - \path|support\vim| directory and the - reference site is \url{http://www.vim.org} - \item TeXnicCenter is free software, available from - \url{http://www.toolscenter.org} and in the proTeXt distribution. - \item \cmdname{LEd} is available from \url{http://www.ctan.org/support/LEd} - \item \cmdname{SciTE} is available from \url{http://www.scintilla.org/SciTE.html} - \end{itemize*} -\end{description} - -You might want to install other tools that are not free\footnote{Not -free, that is, in the sense of freedom to modify and redistribute, -following free software guidelines. This does not mean you can't acquire -them for no money.} and therefore not included on \TL{}, such as -\cmdname{GSView}, the \cmdname{Ghostscript} companion to more -conveniently view PS/PDF files. \cmdname{GSView} is available from -\url{http://www.cs.wisc.edu/~ghost/gsview/} or any \acro{CTAN} site. - -\section{Maintenance of the installation in Windows} - -If you have TeX Live installed, you can use \cmdname{tlpmgui} again -for modyfying and maintaining your installation. - -\subsection{Adding/removing packages} - -As the \cmdname{tlpmgui} shortcut is available in the \guiseq{Start\arw -Programs\arw TeXLive2005} menu, start it from here. The maintenance window -titled \guiseq{TeX Live installation and maintenance utility} shows. It -contains several tabs: \guiseq{Add Packages}, \guiseq{Remove packages}, -\guiseq{Manage installation}, \guiseq{Remove installation}. - -Click the tab labelled \guiseq{Add packages} or \guiseq{Remove packages} -to enter the relevant functionality and then: - -\begin{itemize} -\item In the first tab select the proper \CD{} drive (or \DVD with - \texttt{texlive} directory) by pressing the \guiseq{CD/DVD} button. -\item Click the \guiseq{Search} button in the \guiseq{Buttons} section to -display or refresh in the \guiseq{Select packages to\dots} section the -list of packages to install or remove. - -When adding packages, the list of installed packages is compared to the list -of packages available from your \CD/\DVD. Only packages not already installed are -displayed. It is up to you to select which packages you want to -install. - -When removing individual packages, only a list of installed packages -will be displayed. - -Please note that for both \guiseq{Add packages} and \guiseq{Remove packages} -the collections are listed first. - -\item Select a package by clicking on the name of the package. Clicking the -\guiseq{Info} button in the \guiseq{Buttons} section displays a short -description of the selected package in the window located in the \guiseq{Info -about the selected item} section. To select several packages at once hold -down one of the Ctrl or Shift keys at your keyboard while holding down the -left mouse button or drag the mouse pointer while holding down the left mouse -button. - -\item Click the \guiseq{Install} or \guiseq{Remove} button in the -\guiseq{Buttons} section to perform the appropriate action. -\end{itemize} - -\subsection{Configuring and other management tasks} - -The functions available in the tab labelled \guiseq{Manage the installation} -are helpful in performing actions needed when you want to add support for a -language which was not selected during the installation, or add/regenerate a -format which was not selected during the installation or was modified after -the installation. - -The following actions can be performed: - -\begin{itemize} -\item Refresh the \filename{ls-R} database -\item Create formats (All or Missing) -\item Edit \filename{language.dat} -\item Edit \filename{fmtutil.cnf} -\item Edit \filename{updmap.cfg} -\end{itemize} - -Note: you can close the Edit\dots{} window with the \guiseq{Cancel} or -\guiseq{Done} button; the latter will start rebuilding the format files -(or the fontmap files if you have edited \filename{updmap.cfg}), followed by a -\filename{ls-R} database files refresh. - -For more information about the configuration see section~\ref{sec:persconf}, -\p.\pageref{sec:persconf}. - -\subsection{Uninstalling \protect\TL{}} - -The tab labelled \guiseq{Remove the TeX Live installation} opens a window -which contains functionality not worth describing and we do not know who would -need it and what it is for\dots :-) - -Anyway, if you have the \path|texmf-local| directory for your local additions, -the removal procedure will not wipe it out or delete things in it. The \path|setup-win32| -directory containing \cmdname{tlpmgui} and related files will not be deleted. You will have to do some manual cleanup to -actually remove them. - -\subsection{Adding your own packages to the installation} - -First, whatever changes you make, \textbf{do not forget to rebuild the ls-R -database files}. Otherwise, your new files will not be found. You can do this -either via the \cmdname{tlpmgui} run and selection of the appropriate action -from the \guiseq{Manage the installation} tab, or manually running the -\file{mktexlsr} command. - -If you want to add files that are not provided by the \TL{} distribution, -it is recommended to put them in the \path|$TEXMFLOCAL| directory. This -way, you will be safe against upgrades of the \TL{} software. - -The directory pointed to by \path|$TEXMFLOCAL| is initially empty. If, -for example, you want to add the support file for the Maple symbolic -computation program, you will have to put the style files in:\\ -\path|c:\TeXLive2005\texmf-local\tex\latex\maple\|\\ and the -documentation files in:\\ \path|c:\TeXLive2005\texmf-local\doc\latex\maple\| - -\subsection{Running \texttt{tlmp.exe} from the command line} -The \cmdname{tlpm.exe} program which is used as engine by \cmdname{tlpmgui} -has a number of other useful options. You can get the list by running: -\begin{verbatim} -tlpm --help -\end{verbatim} - -More information and examples of use can be found in \path|tlpm.readme|. - -\subsection{Network installation} - -\KPS{} knows about UNC names, so you can use them to get your TEXMF -tree from the network. But there is better than this. -All the support files and configuration files, everything except the files in the -\path|bin/win32| are shareable with a \teTeX{} or Unix \TL{} installation. That means -you can use Samba either to mount from an NT server to a Unix -workstation or the converse. Several strategies are possible: -\begin{itemize} -\item Put everything on the server. Just add each set of files for the OS and -architecture you want to use in the \path|bin| directory. That means -for example \path|bin/win32| and \path|bin/i386-linux|. Next configure -your main variables. You can use UNC names to -point to the right directories under Win32. -\item Install a local copy for the binaries and format files. In this - case, assign \path|$TEXMFMAIN| to the main \path|texmf| tree that - will be accessed remotely. Set \path|$TEXMFVAR| to be a local - directory which will hold local configuration files and on-the-fly - generated files. -\end{itemize} - -\subsection{What's different in Windows?} - -The Windows version of \Webc{} has some specific features that should be -pointed out. - -\begin{description} -\item[\KPS{}] The hash-tables that \KPS{} builds are quite large for - the \TL{}. In order to cut down the starting time of any - \KPS{}-enabled program, these hash-tables have been put in shared - memory. This way, when you chain the execution of several such - programs, like \path|tex| calling \path|mpost| calling \path|tex|, - the overhead when starting each of the subprograms is - reduced. This change is hidden to the user, except if you set the - debug flag of kpathsea to the \path|-1| value: you will then trace - access to the shared memory, which is not what you want (it is - accessed very often!). What is useful in a log trace of the shared - memory access is still to be defined, so the situation might evolve - in the future. -\item[\cmdname{kpsecheck}] This command provides some options that did - not fit well into \cmdname{kpsewhich}. It will allow you to list all - the files that occur multiple times across your texmf trees. This - could be handy, but most of the time you will also get unwanted - output (like dozens of \path|README| files). It is noticeable - that all these files result in clashes inside the \KPS{}-hashing - mechanism; fortunately, \KPS{} never looks for these files. For - this reason, you can combine the \path|-multiple-occurrences| with 2 - other options for including or excluding any filename that match - some pattern (you can request for several patterns). - - The \cmdname{kpsecheck} command will also report the status of shared - memory: in use or not used. That might be useful to know because if - the status reported is \samp{in use}, that means one or several - processes are working, and the effect of any \cmdname{mktexlsr} - command will be delayed until the next time where no \KPS{} linked - process will be running. - - Last, this same command will report about the location it thinks - Ghostscript can be found. Under Win32, for many programs, it is - easier to use the Ghostscript dll, and find it by using the - Ghostscript registry key than to change the \path|PATH|, which has a - limited length anyway. -\item[\Webc{}] The engines have a few more options than in Unix - \Webc{}, and one option with a different behavior: - \begin{itemize} - \item \path|-halt-on-error| stop the compilation at the first error. - \item \path|-job-time| set the job time to the same timestamp as the - file given in argument. -\item \path|-oem| use the DOS codepage for console output. - \item \path|-output-directory| allow to write all the output files in the - specified directory. - \item \path|-time-statistics| print statistics about the job run - time. It is to be noted that Win9x not being a true multitasking - operating system, it has no reliable timer for short periods, so - the value printed is an approximation. Under NT/2K/XP, the result - is quite accurate with user time and system time values allocated - for this run. For Unix - users: the \path|time| command is not usually available to Windows - users. - \end{itemize} -\end{description} - -\subsection{Personal configurations} -\label{sec:persconf} - -\subsubsection{Dvips} - -The configuration file for dvips can be found in\\ -\verb+C:\TeXLive2005\texmf-var\dvips\config\config.ps+\\ -You may open it with any editor - %(\cmdname{WinShell} will do fine) - and change some parameters: - -\begin{description} -\item [fonts] you can change the default printer \MF{} mode or printer - resolution in case \cmdname{dvips} needs to generate PK fonts. By default it - is configured to use Type~1 versions of the CM fonts, so it should - not call \cmdname{mktexpk} too often; -\item[printer] you can tell dvips where you want to print by default. If - the \optname{o} option is not followed by a printer name, then a - \file{.ps} \PS{} file is written. You can give dvips a printer - name such as: -\begin{verbatim} -o lpt1: -% o | lpr -S server -P myprinter -% o \\server\myprinter -\end{verbatim} -\item[paper] Next, you might want - to change the paper size from European (A4) to US letter - by making the US letter the first paper size mentioned in the file. - Scroll to the group of lines beginning with \code{@}. Move - the appropriate lines so that this section begins with the lines:\\ -\hspace*{1em} @ letterSize 8.5in 11in\\ -\hspace*{1em} @ letter 8.5in 11in\\ -\hspace*{1em} @+ \%\%BeginPaperSize: Letter\\ -\hspace*{1em} @+ letter\\ -\hspace*{1em} @+ \%\%EndPaperSize -\end{description} - -The current \TL{} distribution implements the procedure of making -always up-to-date fontmaps files for Dvips and Pdftex. This is done by -the \cmdname{updmap} program during installation, as well as during any -font package addition. If you add new packages by hand, edit the file -\verb+updmap.cfg+ in \path|$TEXMFVAR/web2c|. - -\subsubsection{PdfTeX} - -If you use the program pdf{}latex to write \acro{PDF} format directly, -and you are using \acro{US} letter-size paper, edit the file -\verb+C:\TeXLive2005\texmf-var\tex\generic\config\pdftexconfig.tex+ and -change \samp{\bs pdfpagewidth} and \samp{\bs pdfpageheight}. These entries -should read: -\begin{alltt} -\bs{}pdfpagewidth=8.5 true in -\bs{}pdfpageheight=11 true in -\end{alltt} -Save the file and exit the editor. - -\subsubsection{GSView} -GSView is now distributed under the Aladdin License, and therefore is no -longer included in \TL{}. - -If you may want to change the page size to US letter size. If so, open -GSView from the \guiseq{Start} menu, and select \guiseq{Media\arw Letter}. - -Also, there are menu settings that are supposed to give you the most -readable screen image. On \guiseq{Media \arw Display Settings}, set both -\optname{Text Alpha} and \optname{Graphics Alpha} to 4~bits. - -Note that the installation process has set all \code{.ps} and -\code{.eps} files to automatically open with \cmdname{GSView}. - -For printing instructions, see section~\ref{printing} below. - -\subsubsection{WinDvi} -\label{sub:windvi} - -The \file{tlpmgui.exe} program takes care of associating the files -with the \file{.dvi} extension with \file{Windvi}, but it doesn't make an icon -on the desktop, so please do it yourself. - -Open \cmdname{windvi} by clicking an icon or from the command line. - -You can set it for US letter-size paper by going to \guiseq{View\arw -Options\arw Papertype} and selecting US (8.5\verb+"+ x 11\verb+"+) (and -then \optname{OK}. Exit \cmdname{windvi}. - -You can change other parameters from there as well, such as the ability -to execute system commands specified by the document (disabled by -default for security reasons). Also, the first time you view any .dvi -file, you may find the magnification too large. Zoom out until you get -an appropriate size. - -All configuration settings for \cmdname{windvi} are stored in a file -named \path|windvi.cnf| file. You can find it by running this command at -the prompt: -\begin{verbatim} -c:\>kpsewhich --expand-var $HOME/windvi.cnf -\end{verbatim} - -Should you have problems with \cmdname{windvi}, please remove the -configuration file and test your problem against a vanilla configuration. - -\subsection{Testing} - -For generic verification procedures, see section~\ref{sec:test-install} -(\p.\pageref{sec:test-install}). This section describes -Windows-specific tests. - -Open the file \verb+sample2e.tex+ in your editor (Xemacs, WinShell), -found in \path|C:\TeXLive2005\texmf-dist\tex\latex\base|. The \LaTeX\ source -should appear on the screen. Process it by clicking on the -\guiseq{Command\arw LaTeX} menu (XEmacs) or \LaTeX\ icon on the toolbar -(WinShell), then view it by clicking on the \guiseq{Command\arw View DVI} -menu (XEmacs) or Preview (Windvi) icon (WinShell). - -At first, when you preview files with Windvi, it will create fonts because -screen fonts were not installed. After a while, you will have created most -of the fonts you use, and you will rarely see the font-creation window. - -\textbf{Hint for the future:} If a \LaTeX\ run stops because \LaTeX\ -cannot find a file, you can press Ctrl-z to quit. - - -\subsection{Printing} -\label{printing} - -It is possible to print from Windvi. In this case, printing will be done -using the Windows unified printer driver. By definition, it is -compatible with all printers. However, there is some drawback: it can -generate some huge spool files, and some (older) versions of Windows -just don't like them. The advantage is that you can use features like -embedding BMP or WMF images. You also need to make sure that the printer -parameters are correctly set (subsection~\ref{sub:windvi}), else you -will get scaled printing (printing at 600\dpi{} on a 300\dpi{} printer -will give you only one quadrant of your page). - -Printing is faster and more reliable if you run \cmdname{dvips} to make -a \filename{.ps} file and then print from \cmdname{GSView}. In -\cmdname{GSview}, select \guiseq{File\arw Print\ldots}. A \guiseq{Print} -window will appear. - -If you are using a \PS{} printer, \textit{be sure to select -\guiseq{\PS{} Printer}}. This is done in the \guiseq{Print Method} box -at the bottom left of the \guiseq{Print} window. You can then select any -of the printers that you have previously installed. If you fail to -check the box for \optname{\PS{} Printer}, printing will not work. - -If you will be using your own non-\PS{} printer, select -\guiseq{Ghostscript device} in the \guiseq{Print Method} box, then click -on the button to the right labelled \guiseq{djet500} and select your -printer type from the list that pops up. (In the older version of -\cmdname{GSView}, make sure \optname{\PS{} Printer} is \textit{not} -selected, then select your printer type from the \guiseq{Device} list.) - -\subsection{Tips and tricks for Win32} - -\subsubsection{Different flavors of Win32} - -What we call Win32 is not an operating system by itself. It is a large -set of functions (around 12,000 in the header files of the Microsoft -\acro{SDK}) that you can use to write programs for different operating -systems of the Windows family. - -Windows comes in different flavors: -\begin{itemize} -\item Win95, Win98 and Win\acro{ME}, which \emph{are not true multitasking, - multithreading} environments. They are the latest\Dash and hopefully - last\Dash metamorphosis of \acro{DOS}. This can be more or less proven - by the fact that when booting, the PC will load the \path|command.com| - interpreter, and if you stop the boot process at this point, you can - ask for the current (\acro{DOS}) version and it will answer something - like \samp{MS-DOS 7.0} (at least for the old versions of Win9x). -\item Windows \acro{NT}, which is a new operating system written from - scratch, capable of true multitasking behavior, and including many - high level features. -\item Windows 2000, based on \acro{NT}, with all the bells and - whistles of Win98. -\item Windows \acro{XP}, which comes with Personal and Pro flavors. This is - the last step in merging both lines of products (Win9x based and - \acro{NT} based). \acro{XP} is based on \acro{NT}. -\end{itemize} - -Win9x are able to run 32~bits programs and 16~bits programs -concurrently. But the operating system by itself is not entirely -written in 32~bits mode, and does not support memory protection: 16bits -applications can overwrite parts of the operating system memory! Some -parts of the system like the \acro{GDI} (Graphical Device Interface) -manage limited resources like bitmaps, fonts, pens and so on for the set -of all programs that run concurrently. All the bitmaps headers available -at the same time can't amount for more than 64kB. This explains the -performance tool and the fact that you can put your system on his knees -by making intensive use of graphic objects for example. - -NT, 2K and XP do not suffer from these limitations, and neither from -other Win9x limitations. They are true multitasking environments, with -protected memory. They are much more responsive than Win9x because -of better memory management, better file system and so on. - -\subsubsection{Command line prompt} - -You may wonder, ``Why would I need to use a command line prompt when -I have Windows?'' - -Good question. The problem is of very general nature. Not all operations -can be done easily using only a \acro{GUI}. Command line gives you -programming power\Dash assuming a clever command interpreter. - -But the problem here is more fundamental: \TeX{} is \emph{a batch} -tool. Not an interactive one. \TeX{} needs to compute the best -layout for each page, resolve cross-references and so on. This can be -done only by a global processing of the document. It is not (yet) a -task that can be done interactively. - -This means that you should use \TeX{} from a command line. In fact the -situation is not so bad. There is an advantage to write command line -tools for complex processing: they are better debugged, because they are -independent of any \acro{GUI} problems, and \acro{GUI} tools can be -designed to interface to the command line tools. This is the case for -\TeX{}, where you will mostly interact with it through a \acro{GUI} text -editor. - -However, you may need to use the command line prompt in a number of -situations. One is when you are having difficulties and want to debug -your setup. - -\begin{description} - \item[Win9x] You can open a command line prompt by looking either for - the \acro{MS-DOS} icon in the \guiseq{Start\arw Programs} menu, - or by choosing \guiseq{Start\arw Run} menu typing in - \path|command.com| as the progrm name. - \item[NT, 2K, XP] You can open a command line prompt by looking for - \guiseq{Command Prompt} in the \guiseq{Start\arw Accessories} menu. - You can also choose \guiseq{Start\arw Run} and type in - \path|cmd.exe|, which is the name of the brand new command - interpreter for \acro{NT} (thus, it is untrue to call this a - \emph{DOS} box!). -\end{description} - -These locations may change across different Windows versions. - -\subsubsection{Path separators} - -The Win32 API understands both \path|/| and \path|\| characters as PATH -separators. But the command interpreters do not! So whenever a path name -is used programmatically, you can use both separators, and even mix them -up in the same path name. But on the command line, you must type -\path|\| as path separator. The reason is compatibility: the command -processor used \samp{/} to introduce arguments to commands. - -All this to say: do not be surprised to read path names written using -the Unix convention; \fpTeX{} is a port of \Webc, and aims to be compatible -across platforms. For this reason, all the configuration files that -need to specify path names use the Unix convention. - -\subsubsection{File systems} -\label{sec:clusters} - -The worst feature of Win9x with regard to \TeX{} is probably the -so-called FAT file system. \TeX{} uses very many small files, with size -around 1--3kB. The \acro{FAT} file system is old, and predates by -decades the multi-gigabytes hard disks we have today. As a result, it -cannot manage efficiently the tens of thousands of \TeX{} files found in -\TL{}. The \acro{FAT} file system allocates a minimum of 32kB for -\emph{any} file on a huge partition. It means that \TeX{} will use much -more disk space than it actually needs. - -The other, more modern, file systems available, \acro{FAT32} and -\acro{NTFS}, do not have this drawback. They manage clusters of 4kB -only. (You can lower the limit to 512 bytes on \acro{NTFS}.) - -\subsubsection{How to add some directory to your PATH} - -There are pairs of variables and values which behave much like global -variables inside your programs. The set of those variables is called the -environment. Each program is initialized with a copy of the -environment when it is run. It can request and change the -value of any variable. The changes happen in the copy of the -environment, and is not at all propagated to the other running -programs. - -Your PATH is a special environment variable used to search for -programs you want to run. -There is a different procedure to change it for Win9x, WinME and NT/2K/XP: - -\begin{description} -\item[Windows 95/98] Edit your \path|autoexec.bat|. In this file should be a line - starting with \texttt{PATH=} and followed by a list of directories separated - by \path|;|. Please add the directory with the executables in this line. - After this, this line could look as follows: -\begin{verbatim} -PATH=c:\windows;c:\windows\system;c:\TeXLive2005\bin\win32 -\end{verbatim} -\item[Windows ME] You need to run the special program - \path|c:\windows\system\msconfig.exe| to be able to change any - environment variable. From this program, select the `Environment' - tab, and then add or modify the variable you want. You will be asked to reboot the - machine upon any change. -\item[Windows NT/2K/XP] - Click left on \guiseq{Start \arw Settings \arw Control Panel}. Now the - window with the control panel icons opens. Double click on System. The - System Properties window opens. Click on the tab \textsf{Environment} - or look for a button named \guiseq{Environment Variables} among the - dialog boxes. Now you can change the environment variables for your - user account. Note: There are also displayed the environment settings - for the system. Normally, you can't change the system variables - unless you have administrator rights on your machine. If you want to - change the \texttt{PATH} for all users, you will have to contact your - system administrator or be the system administrator yourself\Dash in - the latter case you should know what you are doing. - - If there is already a \texttt{PATH} setting for your user account, - left click on \texttt{PATH}. In the field \textsf{Variable} appears - \texttt{PATH} while the field Value shows the current setting of - \texttt{PATH} as a list of directories separated by \path|;|. Add - the directory where the executables are located (e.g. - \path|c:\TeXLive2005\bin\win32|). If there isn't a \texttt{PATH} variable - for your user account, simply click in the field Variable and type - in \texttt{PATH}, click in the field \textsf{Value} - and type in the directory with the executables. Important: Click on - the \textsf{Apply} button before clicking \textsf{Ok}, otherwise the - changes to \texttt{PATH} won't apply to your system. Be careful when - changing the environment settings. -\end{description} - -The best way to be sure that a variable has been properly set is to -open a console and type: -\begin{verbatim} -set VARIABLE -\end{verbatim} -which should return the corresponding value. - -\subsubsection{\TeX{} engines} - -If you have a look at the \Webc{} documentation, you will read that all -the various \TeX{} derived programs use the same base engine. For -example, \path|tex.exe| and \path|latex.exe| are exact copies of the -same program, but each one will use a different format file, based on -its calling name. - -Under Unix, this feature is implemented through \emph{symbolic -links}. It saves up a bit of disk space, because some engines are -used with many different format files. - -The Win32 API does not know about file links. So to save up almost -the same amount of memory, all the \TeX{} base engines have been put -in DLLs (\emph{Dynamic Linked Library}). This means that you will have -the following layout: -\begin{alltt} -18/09/2005 14:19 3 584 latex.exe -18/09/2005 14:19 3 584 pdfetex.exe -18/09/2005 14:19 524 288 tl90pdfetex.dll -\end{alltt} -and the \path|latex.exe| file is nothing but a rough copy of -\path|pdfetex.exe| using the same core \path|tl90pdfetex.dll|. -The same trick has been used for the \path|mktex*.exe| family of programs -which are linked to the \path|mktex.dll| library. - -In fact, a generic tool called \path|irun.exe| is provided to build the -equivalent of Unix hard links for executable files only under Win32. - -\subsection{In case of problems} -\label{sec:troubleshooting} - -\subsubsection{What to do if \texttt{latex} does not find your files?} - -\begin{itemize} - -\item \cmdname{kpsewhich} is the tool of choice to debug any -problem. Unfortunately, \cmdname{kpsewhich} outputs debug information -to stderr, and the older Windows consoles do not know how to redirect stderr -to a file. (NT and Windows 2000 consoles know how to do that. But -the trick will work for any console.) For diagnostic purposes you can -temporarily set an environment variable (in a \acro{DOS} box): - -\begin{verbatim} -SET KPATHSEA_DEBUG_OUTPUT=err.log -\end{verbatim} -You can also set the debug level: -\begin{verbatim} -SET KPATHSEA_DEBUG=-1 -\end{verbatim} - -If you want to redirect stderr to stdout, which is not possible -Windows, then do: -\begin{verbatim} -SET KPATHSEA_DEBUG_OUTPUT=con: -\end{verbatim} -This way you can capture both stdout and stderr in the same file. - -\item Assuming the installation has been done in \path|c:/TeX|, check - the following values: \\ - {\small - \begin{tabular}{ll} - \path|kpsewhich -expand-path $SELFAUTOPARENT| & \path|c:/TeX| \\ - \path|kpsewhich -expand-path $TEXMF| & \path|c:/TeX/texmf....| \\ - \path|kpsewhich -expand-path $TEXMFCNF| & - \path|.;c:/TeX/texmf-var/web2c;| \\ - \path|kpsewhich -expand-var $TEXINPUTS| & \path|.;c:/TeX/texmf/tex//| - \end{tabular} -} -\item If you have other \TeX{}-related values already set in your - environment, please, remove them. They are overriding the ones in - texmf.cnf. -\item Check the values from:\\ -{\small - \begin{tabular}{ll} - \texttt{kpsewhich cmr10.tfm} & \path|c:/TeX/texmf/fonts/tfm/public/cm/cmr10.tfm|\\ - \texttt{kpsewhich latex.fmt}& \path|c:/TeX/texmf/web2c/latex.fmt| - \end{tabular} -} -\item At this point, if everything is correct, \TeX{} and friends - should work. If it is not the case, you will need to play with - the \path|-debug=n| option from \path|kpsewhich|, and check back all - the values. Try to identify and report the problem. -\end{itemize} - -\subsubsection{What to do if your setup still does not work as expected?} - -Here are several questions to investigate: - -\begin{enumerate} -\item Is \file{tex.exe} in my \path|PATH|? - -\item Is the \path|TEXMFCNF| variable correctly set to -\path|c:/TeXLive2005/texmf-var/web2c| (default value)? - -\item Are there any errors in the log file generated by the -\file{tlmpgui.exe} program? -\file{tlmpgui.log} can be found in your -\file{TEMP} directory. You can find this by searching for the -string \samp{Error}. Hint: the log file can show some errors after -building all format files. Please do not panic: perhaps some formats -weren't already installed. - -\item Are there any relevant bug fixes at \url{http://tug.org/texlive/}? -(Unlikely, but it doesn't hurt to check.) - -\end{enumerate} - -The \TL{} software consists of hundreds of programs and tens of -thousands of files, all from varying sources. So it is quite difficult to -predict all possible causes for problems. Nevertheless, we will do our -best to help you. (See section~\ref{sec:help}, \p.\pageref{sec:help}.) - -% don't use \Webc so the \uppercase in the headline works. -\section{A user's guide to Web2C} - -\Webc{} is an integrated collection of \TeX-related programs: \TeX{} -itself, \MF{}, \MP, \BibTeX{}, etc. It is the heart of \TL{}. - -A bit of history: The original implementation was by Tomas Rokicki who, -in 1987, developed a first \TeX{}-to-C system based on change files -under Unix, which were primarily the original work of Howard Trickey and -Pavel Curtis. Tim Morgan became the maintainer of the system, and -during this period the name changed to Web-to-C\@. In 1990, Karl Berry -took over the work, assisted by dozens of additional contributors, and -in 1997 he handed the baton to Olaf Weber. - -The \Webc{} system runs on Unix, 32-bit Windows systems, \MacOSX{}, and -other operating systems. It uses Knuth's original sources for \TeX{} and -other basic programs written in \web{} and translates them into C source -code. The core \TeX{} programs are: - -\begin{cmddescription} -\item[bibtex] Maintaining bibliographies. -\item[dmp] \cmdname{troff} to MPX (\MP{} pictures). -\item[dvicopy] Expands virtual font references in \dvi{} files. -\item[dvitomp] \dvi{} to MPX (MetaPost pictures). -\item[dvitype] \dvi{} to human-readable text. -\item[gftodvi] Generic font proofsheets. -\item[gftopk] Generic to packed fonts. -\item[gftype] GF to human-readable text. -\item[makempx] \MP{} label typesetting. -\item[mf] Creating typeface families. -\item[mft] Prettyprinting \MF{} source. -\item[mpost] Creating technical diagrams. -\item[mpto] MetaPost label extraction. -\item[newer] Compare modification times. -\item[patgen] Creating hyphenation patterns. -\item[pktogf] Packed to generic fonts. -\item[pktype] PK to human-readable text. -\item[pltotf] Plain text property list to TFM. -\item[pooltype] Display \web{} pool files. -\item[tangle] \web{} to Pascal. -\item[tex] Typesetting. -\item[tftopl] TFM to plain text property list. -\item[vftovp] Virtual font to virtual property list. -\item[vptovf] Virtual property list to virtual font. -\item[weave] \web{} to \TeX. -\end{cmddescription} - -\noindent The precise functions and syntax of these programs are -described in the documentation of the individual packages and of \Webc{} -itself. However, knowing a few principles governing the whole family of -programs will help you take advantage of your \Webc{} installation. - -All programs honor these standard \acro{GNU} options: -\begin{ttdescription} -\item[-{}-help] print basic usage summary. -\item[-{}-verbose] print detailed progress report. -\item[-{}-version] print version information, then exit. -\end{ttdescription} - -For locating files the \Webc{} programs use the path searching library -\KPS{}. This library uses a combination of environment variables and a -configuration files to optimize searching the (huge) collection of -\TeX{} files. \Webc{} can look at more than one directory tree -simultaneously, which is useful in maintaining \TeX's standard -distribution and local extensions in two distinct trees. To speed up -file searches the root of each tree has a file \file{ls-R}, containing -an entry showing the name and relative pathname for all files under that -root. - -\subsection{Kpathsea path searching} - -Let us first describe the generic path searching mechanism of the \KPS{} -library. - -We call a \emph{search path} a colon- or semicolon\hyph sepa\-rated list -of \emph{path elements}, which are basically directory names. A -search path can come from (a combination of) many sources. To look up -a file \samp{my-file} along a path \samp{.:/dir}, \KPS{} checks each -element of the path in turn: first \file{./my-file}, then -\file{/dir/my-file}, returning the first match (or possibly all -matches). - -In order to adapt optimally to all operating systems' conventions, on -non-Unix systems \KPS{} can use filename separators different from -colon (\samp{:}) and slash (\samp{/}). - -To check a particular path element \var{p}, \KPS{} first checks if a -prebuilt database (see ``Filename data\-base'' on -page~\pageref{Filename-database}) applies to \var{p}, i.e., if the database -is in a directory that is a prefix of \var{p}. If so, the path -specification is matched against the contents of the database. - -If the database does not exist, or does not apply to this path -element, or contains no matches, the filesystem is searched (if this -was not forbidden by a specification starting with \samp{!!}\ and if -the file being searched for must exist). \KPS{} constructs the list -of directories that correspond to this path element, and then checks -in each for the file being sought. - -The ``file must exist'' condition comes into play with \samp{.vf} files and -input files read by \TeX's \cs{openin} command. Such files may not -exist (e.g., \file{cmr10.vf}), and so it would be wrong to search the -disk for them. Therefore, if you fail to update \file{ls-R} when you -install a new \samp{.vf} file, it will never be found. -Each path element is checked in turn: first the database, then the -disk. If a match is found, the search stops and the result is -returned. - -Although the simplest and most common path element is a directory -name, \KPS{} supports additional features in search paths: layered -default values, environment variable names, config file values, users' -home directories, and recursive subdirectory searching. Thus, we say -that \KPS{} \emph{expands} a path element, meaning it transforms all -the specifications into basic directory name or names. This is -described in the following sections in the same order as it takes -place. - -Note that if the filename being searched for is absolute or explicitly -relative, i.e., starts with \samp{/} or \samp{./} or \samp{../}, -\KPS{} simply checks if that file exists. - -\ifSingleColumn -\else -\begin{figure*} -\verbatiminput{examples/ex5.tex} -\setlength{\abovecaptionskip}{0pt} - \caption{An illustrative configuration file sample} - \label{fig:config-sample} -\end{figure*} -\fi - -\subsubsection{Path sources} -\label{Path-sources} - -A search path can come from many sources. In the order in which -\KPS{} uses them: - -\begin{enumerate} -\item - A user-set environment variable, for instance, \envname{TEXINPUTS}\@. - Environment variables with a period and a program name appended - override; e.g., if \samp{latex} is the name of the program being run, - then \envname{TEXINPUTS.latex} will override \envname{TEXINPUTS}. -\item - A program-specific configuration file, for exam\-ple, a line - \samp{S /a:/b} in \cmdname{dvips}'s \file{config.ps}. -\item A \KPS{} configuration file \file{texmf.cnf}, containing a line like - \samp{TEXINPUTS=/c:/d} (see below). -\item The compile-time default. -\end{enumerate} -\noindent You can see each of these values for a given -search path by using the debugging options (see ``Debugging actions'' -on page~\pageref{Debugging}). - -\subsubsection{Config files} - -\begingroup\tolerance=3500 -\KPS{} reads \emph{runtime configuration files} named \file{texmf.cnf} -for search path and other definitions. The search path used to look -for these files is named \envname{TEXMFCNF} (by default such a file lives -in the \file{texmf/web2c} subdirectory). \emph{All} -\file{texmf.cnf} files in the search path will be read and definitions -in earlier files override those in later files. Thus, with a search -path of \verb|.:$TEXMF|, values from \file{./texmf.cnf} override those -from \verb|$TEXMF/texmf.cnf|. -\endgroup - -\begin{itemize} -\item - Comments start with \code{\%} and continue to the end of the line. -\item - Blank lines are ignored. -\item - A \bs{} at the end of a line acts as a continuation character, - i.e., the next line is appended. Whitespace at the beginning of - continuation lines is not ignored. -\item - Each remaining line has the form: -\begin{alltt} - \var{variable}[.\var{progname}] [=] \var{value} -\end{alltt}% - where the \samp{=} and surrounding whitespace are optional. -\item - The \ttvar{variable} name may contain any character other - than whitespace, \samp{=}, or \samp{.}, but sticking to - \samp{A-Za-z\_} is safest. -\item - If \samp{.\var{progname}} is present, the definition only - applies if the program that is running is named - \texttt{\var{progname}} or \texttt{\var{progname}.exe}. This allows - different flavors of \TeX{} to have different search paths, for - example. -\item \var{value} may contain any characters except - \code{\%} and \samp{@}. The - \code{\$\var{var}.\var{prog}} feature is not available on the - right-hand side; instead, you must use an additional variable. A - \samp{;}\ in \var{value} is translated to \samp{:}\ if - running under Unix; this is useful to be able to have a single - \file{texmf.cnf} for Unix, \acro{MS-DOS} and Windows systems. -\item - All definitions are read before anything is expanded, so - variables can be referenced before they are defined. -\end{itemize} -A configuration file fragment illustrating most of these points is -\ifSingleColumn -shown below: - -\verbatiminput{examples/ex5.tex} -\else -shown in Figure~\ref{fig:config-sample}. -\fi - -\subsubsection{Path expansion} -\label{Path-expansion} - - -\KPS{} recognizes certain special characters and constructions in -search paths, similar to those available in Unix shells. As a -general example, the complex path, -\verb+~$USER/{foo,bar}//baz+, expands to all subdirectories under -directories \file{foo} and \file{bar} in \texttt{\$USER}'s home -directory that contain a directory or file \file{baz}. These -expansions are explained in the sections below. -%$ -\subsubsection{Default expansion} -\label{Default-expansion} - -\tolerance=2500 -If the highest-priority search path (see ``Path sources'' on -page~\pageref{Path-sources}) contains an \emph{extra colon} (i.e., -leading, trailing, or doubled), \KPS{} inserts at that point the -next-highest-prio\-rity search path that is defined. If that inserted -path has an extra colon, the same happens with the next highest. For -example, given an environment variable setting - -\tolerance=1500 - -\begin{alltt} -> \Ucom{setenv TEXINPUTS /home/karl:} -\end{alltt} -and a \code{TEXINPUTS} value from \file{texmf.cnf} of - -\begin{alltt} - .:\$TEXMF//tex -\end{alltt} -then the final value used for searching will be: - -\begin{alltt} - /home/karl:.:\$TEXMF//tex -\end{alltt} - -Since it would be useless to insert the default value in more than one -place, \KPS{} changes only one extra \samp{:}\ and leaves any others in -place. It checks first for a leading \samp{:}, then a trailing -\samp{:}, then a doubled \samp{:}. - -\subsubsection{Brace expansion} - -A useful feature is brace expansion, which means that, for instance, -\verb+v{a,b}w+ expands to \verb+vaw:vbw+. Nesting is allowed. -This is used to implement multiple \TeX{} hierarchies, by -assigning a brace list to \code{\$TEXMF}. -For example, in \file{texmf.cnf}, the following definition -(appproximately; there are actually even more trees) is made: -\begin{verbatim} - TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN} -\end{verbatim} -Using this you can then write something like -\begin{verbatim} - TEXINPUTS = .;$TEXMF/tex// -\end{verbatim} -%$ -which means that, after looking in the current directory, the -\code{\$TEXMFHOME/tex}, \code{\$TEXMFLOCAL/tex}, \code{\$TEXMFVAR/tex} -and \code{\$TEXMFMAIN/tex} trees \emph{only}) will be searched (the -last two use using \file{ls-R} data base files). It is a convenient -way for running two parallel \TeX{} structures, one ``frozen'' (on a -\CD, for instance) and the other being continuously updated with new -versions as they become available. By using the \code{\$TEXMF} -variable in all definitions, one is sure to always search the -up-to-date tree first. - -\subsubsection{Subdirectory expansion} -\label{Subdirectory-expansion} - -Two or more consecutive slashes in a path element following a directory -\var{d} is replaced by all subdirectories of \var{d}: first those -subdirectories directly under \var{d}, then the subsubdirectories under -those, and so on. At each level, the order in which the directories are -searched is \emph{unspecified}. - -If you specify any filename components after the \samp{//}, only -subdirectories with matching components are included. For example, -\samp{/a//b} expands into directories \file{/a/1/b}, \file{/a/2/b}, -\file{/a/1/1/b}, and so on, but not \file{/a/b/c} or \file{/a/1}. - -Multiple \samp{//} constructs in a path are possible, but -\samp{//} at the beginning of a path is ignored. - -\subsubsection{List of special characters and their meaning: a summary} - -The following list summarizes the special characters in \KPS{} -configuration files. - -% need a wider space for the item labels here. -\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} -\begin{ttdescription} -\item[\CODE{:}] Separator in path specification; at the beginning or - the end of a path it substitutes the default path expansion.\par -\item[\CODE{;}] Separator on non-Unix systems (acts like \code{:}). -\item[\CODE{\$}] Variable expansion. -\item[\CODE{\string~}] Represents the user's home directory. -\item[\CODE{\char`\{...\char`\}}] Brace expansion. -\item[\CODE{//}] Subdirectory expansion (can occur anywhere in - a path, except at its beginning). -\item[\CODE{\%}] Start of comment. -\item[\CODE{\bs}] Continuation character (allows multi-line entries). -\item[\CODE{!!}] Search \emph{only} database to locate file, \emph{do - not} search the disk. -\end{ttdescription} - - -\subsection{Filename databases} -\label{Filename-database} - -\KPS{} goes to some lengths to minimize disk accesses for searches. -Nevertheless, at installations with enough directories, searching each -possible directory for a given file can take an excessively long time -(this is especially true if many hundreds of font directories have to -be traversed.) Therefore, \KPS{} can use an externally-built plain text -``database'' file named \file{ls-R} that maps files to directories, -thus avoiding the need to exhaustively search the disk. - -A second database file \file{aliases} allows you to give additional -names to the files listed in \file{ls-R}. This can be helpful to -confirm to \acro{DOS} 8.3 filename conventions in source files. - -\subsubsection{The filename database} -\label{ls-R} - -As explained above, the name of the main filename database must be -\file{ls-R}. You can put one at the root of each \TeX{} hierarchy in -your installation that you wish to be searched (\code{\$TEXMF} by -default); most sites have only one hierarchy. \KPS{} looks for -\file{ls-R} files along the \code{TEXMFDBS} path. - -The recommended way to create and maintain \samp{ls-R} is to run the -\code{mktexlsr} script included with the distribution. It is invoked -by the various \samp{mktex}\dots\ scripts. In principle, this script -just runs the command -\begin{alltt} -cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R -\end{alltt} -presuming your system's \code{ls} produces the right output format -(\acro{GNU} \code{ls} is all right). To ensure that the database is -always up-to-date, it is easiest to rebuild it regularly via -\code{cron}, so that it is automatically updated when the installed -files change, such as after installing or updating a \LaTeX{} package. - -If a file is not found in the database, by default \KPS{} goes ahead -and searches the disk. If a particular path element begins with -\samp{!!}, however, \emph{only} the database will be searched for that -element, never the disk. - - -\subsubsection{kpsewhich: Standalone path searching} -\label{Invoking-kpsewhich} - -The \texttt{kpsewhich} program exercises path searching independent of any -particular application. This can be useful as a sort of \code{find} -program to locate files in \TeX{} hierarchies (this is used heavily in -the distributed \samp{mktex}\dots\ scripts). - -\begin{alltt} -> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} -\end{alltt} -The options specified in \ttvar{option} start with either \samp{-} -or \samp{-{}-}, and any unambiguous abbreviation is accepted. - -\KPS{} looks up each non-option argument on the command line as a -filename, and returns the first file found. There is no option to -return all the files with a particular name (you can run the Unix -\samp{find} utility for that). - -The more important options are described next. - -\begin{ttdescription} -\item[\texttt{-{}-dpi=\var{num}}]\mbox{} - Set the resolution to \ttvar{num}; this only affects \samp{gf} - and \samp{pk} lookups. \samp{-D} is a synonym, for compatibility - with \cmdname{dvips}. Default is 600. - -\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ - Set the format for lookup to \ttvar{name}. By default, the - format is guessed from the filename. For formats which do not have - an associated unambiguous suffix, such as \MP{} support files and - \cmdname{dvips} configuration files, you have to specify the name as - known to \KPS{}, such as \texttt{tex} or \texttt{enc files}. Run - \texttt{kpsewhich -{}-help} for a list. - -\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ - Set the mode name to \ttvar{string}; this only affects \samp{gf} - and \samp{pk} lookups. No default: any mode will be found. -\item[\texttt{-{}-must-exist}]\mbox{}\\ - Do everything possible to find the files, notably including - searching the disk. By default, only the \file{ls-R} database is - checked, in the interest of efficiency. -\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ - Search along the path \ttvar{string} (colon-separated as usual), - instead of guessing the search path from the filename. \samp{//} and - all the usual expansions are supported. The options \samp{-{}-path} - and \samp{-{}-format} are mutually exclusive. -\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ - Set the program name to \texttt{\var{name}}. - This can affect the search paths via the \texttt{.\var{progname}} - feature. - The default is \cmdname{kpsewhich}. -\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ - shows the path used for file lookups of file type \texttt{\var{name}}. - Either a filename extension (\code{.pk}, \code{.vf}, etc.) or a - name can be used, just as with \samp{-{}-format} option. -\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ - sets the debugging options to \texttt{\var{num}}. -\end{ttdescription} - - -\subsubsection{Examples of use} -\label{SExamplesofuse} - -Let us now have a look at \KPS{} in action. Here's a straightforward search: - -\begin{alltt} -> \Ucom{kpsewhich article.cls} - /usr/local/texmf-dist/tex/latex/base/article.cls -\end{alltt} -We are looking for the file \file{article.cls}. Since the \samp{.cls} -suffix is unambiguous we do not need to specify that we want to look for a -file of type \optname{tex} (\TeX{} source file directories). We find it in -the subdirectory \file{tex/latex/base} below the \samp{texmf-dist} \TL\ -directory. Similarly, all of the following are found without problems -thanks to their unambiguous suffix. -\begin{alltt} -> \Ucom{kpsewhich array.sty} - /usr/local/texmf-dist/tex/latex/tools/array.sty -> \Ucom{kpsewhich latin1.def} - /usr/local/texmf-dist/tex/latex/base/latin1.def -> \Ucom{kpsewhich size10.clo} - /usr/local/texmf-dist/tex/latex/base/size10.clo -> \Ucom{kpsewhich small2e.tex} - /usr/local/texmf-dist/tex/latex/base/small2e.tex -> \Ucom{kpsewhich tugboat.bib} - /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib -\end{alltt} - -That last is a \BibTeX{} bibliography database for \textsl{TUGBoat} articles. - -\begin{alltt} -> \Ucom{kpsewhich cmr10.pk} -\end{alltt} -Font bitmap glyph files of type \file{.pk} are used by display -programs like \cmdname{dvips} and \cmdname{xdvi}. Nothing is returned in -this case since there are no pre-generated Computer Modern \samp{.pk} -files in \TL{}\Dash the Type~1 variants are used by default. -\begin{alltt} -> \Ucom{kpsewhich wsuipa10.pk} -\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk -\else /usr/local/texmf-var/fonts/pk/ljfour/public/ -... wsuipa/wsuipa10.600pk -\fi\end{alltt} - -For these fonts (a phonetic alphabet from the University of Washington) -we had to generate \samp{.pk} files, and since the default \MF{} mode on -our installation is \texttt{ljfour} with a base resolution of 600\dpi{} -(dots per inch), this instantiation is returned. -\begin{alltt} -> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} -\end{alltt} -In this case, when specifying that we are interested in a resolution -of 300\dpi{} (\texttt{-dpi=300}) we see that no such font is available on -the system. A program like \cmdname{dvips} or \cmdname{xdvi} would -go off and actually build the required \texttt{.pk} files -using the script \cmdname{mktexpk}. - -Next we turn our attention to \cmdname{dvips}'s header and configuration -files. We first look at one of the commonly used files, the general -prolog \file{tex.pro} for \TeX{} support, before turning our attention -to the generic configuration file (\file{config.ps}) and the \PS{} font -map \file{psfonts.map}\Dash as of 2004, map and encoding files have -their own search paths and new location in \dirname{texmf} trees. As -the \samp{.ps} suffix is ambiguous we have to specify explicitly which -type we are considering (\optname{dvips config}) for the file -\texttt{config.ps}. -\begin{alltt} -> \Ucom{kpsewhich tex.pro} - /usr/local/texmf/dvips/base/tex.pro -> \Ucom{kpsewhich --format="dvips config" config.ps} - /usr/local/texmf/dvips/config/config.ps -> \Ucom{kpsewhich psfonts.map} - /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map -\end{alltt} - -We now take a closer look at the \acro{URW} Times \PS{} support -files. The prefix for these in the standard font naming scheme is -\samp{utm}. The first file we look at is the configuration file, -which contains the name of the map file: -\begin{alltt} -> \Ucom{kpsewhich --format="dvips config" config.utm} - /usr/local/texmf-dist/dvips/psnfss/config.utm -\end{alltt} -The contents of that file is -\begin{alltt} - p +utm.map -\end{alltt} -which points to the file \file{utm.map}, which we want to -locate next. -\begin{alltt} -> \Ucom{kpsewhich utm.map} - /usr/local/texmf-dist/fonts/map/dvips/times/utm.map -\end{alltt} -This map file defines the file names of the Type~1 \PS{} fonts in -the URW collection. Its contents look like (we only show part of the -lines): -\begin{alltt} -utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} -\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb -\else /usr/local/texmf-dist/fonts/type1/ -... urw/utm/utmr8a.pfb -\fi\end{alltt} - -It should be evident from these examples how you can easily locate the -whereabouts of a given file. This is especially important if you suspect -that the wrong version of a file is picked up somehow, since -\cmdname{kpsewhich} will show you the first file encountered. - -\subsubsection{Debugging actions} -\label{Debugging} - -Sometimes it is necessary to investigate how a program resolves file -references. To make this practical, \KPS{} offers various levels of -debugging output: - -\begin{ttdescription} -\item[\texttt{\ 1}] \texttt{stat} calls (disk lookups). When running - with an up-to-date \file{ls-R} database this should almost give no - output. -\item[\texttt{\ 2}] References to hash tables (such as \file{ls-R} - databases, map files, configuration files). -\item[\texttt{\ 4}] File open and close operations. -\item[\texttt{\ 8}] General path information for file types - searched by \KPS. This is useful to find out where a particular - path for the file was defined. -\item[\texttt{16}] Directory list for each path element (only relevant - for searches on disk). -\item[\texttt{32}] File searches. -\end{ttdescription} -A value of \texttt{-1} will set all the above options; in practice, -this is usually the most convenient. - -Similarly, with the \cmdname{dvips} program, by setting a combination of -debug switches, one can follow in detail where files are being picked up -from. Alternatively, when a file is not found, the debug trace shows in -which directories the program looks for the given file, so that one can -get an indication what the problem~is. - -Generally speaking, as most programs call the \KPS{} library -internally, one can select a debug option by using the -\envname{KPATHSEA\_DEBUG} environment variable, and setting it to (a -combination of) values as described in the above list. - -(Note for Windows users: it is not easy to redirect -all messages to a file in this system. For diagnostic purposes -you can temporarily \texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log}). - -Let us consider, as an example, a small \LaTeX{} source file, -\file{hello-world.tex}, which contains the following input. -\begin{verbatim} - \documentclass{article} - \begin{document} - Hello World! - \end{document} -\end{verbatim} -This little file only uses the font \file{cmr10}, so let us look at -how \cmdname{dvips} prepares the \PS{} file (we want to use the Type~1 -version of the Computer Modern fonts, hence the option \texttt{-Pcms}). -\begin{alltt} -> \Ucom{dvips -d4100 hello-world -Pcms -o} -\end{alltt} -In this case we have combined \cmdname{dvips}'s debug class 4 (font -paths) with \KPS's path element expansion (see \cmdname{dvips} Reference -Manual, \OnCD{texmf/doc/html/dvips/dvips_toc.html}). -The output (slightly rearranged) appears in -Figure~\ref{fig:dvipsdbga}. -\begin{figure*}[tp] -\centering -\input{examples/ex6a.tex} -\caption{Finding configuration files}\label{fig:dvipsdbga} - -\bigskip - -\input{examples/ex6b.tex} -\caption{Finding the prolog file}\label{fig:dvipsdbgb} - -\bigskip - -\input{examples/ex6c.tex} -\caption{Finding the font file}\label{fig:dvipsdbgc} -\end{figure*} - -\cmdname{dvips} starts by locating its working files. First, -\file{texmf.cnf} is found, which gives the definitions of the search -paths for the other files, then the file database \file{ls-R} (to -optimize file searching) and the file \file{aliases}, which makes it -possible to declare several names (e.g., a short \acro{DOS}-like 8.3 and -a more natural longer version) for the same file. Then \cmdname{dvips} -goes on to find the generic configuration file \file{config.ps} -before looking for the customization file \file{.dvipsrc} (which, in -this case is \emph{not found}). Finally, \cmdname{dvips} locates the -config file for the Computer Modern \PS{} fonts \file{config.cms} -(this was initiated with the \texttt{-Pcms} option on the \cmdname{dvips} -command). This file contains the list of the map files which -define the relation between the \TeX{}, \PS{} and file system -names of the fonts. -\begin{alltt} -> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} - p +ams.map - p +cms.map - p +cmbkm.map - p +amsbkm.map -\end{alltt} -\cmdname{dvips} thus goes on to find all these files, plus the generic -map file \file{psfonts.map}, which is always loaded (it contains -declarations for commonly used \PS{} fonts; see the last part of -Section \ref{SExamplesofuse} for more details about \PS{} map -file handling). - -At this point \cmdname{dvips} identifies itself to the user: -\begin{alltt} -This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) -\end{alltt} -\ifSingleColumn -Then it goes on to look for the prolog file \file{texc.pro}: -\begin{alltt}\small -kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro -\end{alltt} -\else -Then it goes on to look for the prolog file \file{texc.pro} (see -Figure~\ref{fig:dvipsdbgb}). -\fi - -After having found the file in question, \cmdname{dvips} outputs -date and time, and informs us that it will generate the -file \file{hello-world.ps}, then that it needs the font file -\file{cmr10}, and that the latter is declared as ``resident'' (no -bitmaps needed): -\begin{alltt}\small -TeX output 1998.02.26:1204' -> hello-world.ps -Defining font () cmr10 at 10.0pt -Font cmr10 is resident. -\end{alltt} -Now the search is on for the file \file{cmr10.tfm}, which is found, -then a few more prolog files (not shown) are referenced, and finally -the Type~1 instance \file{cmr10.pfb} of the font is located and -included in the output file (see last line). -\begin{alltt}\small -kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, - path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: - /var/tex/fonts/tfm//). -kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm -kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, - ... - -kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb -[1] -\end{alltt} - -\subsection{Runtime options} - -Another useful feature of \Webc{} is its possibility to control a number -of memory parameters (in particular, array sizes) via the runtime file -\file{texmf.cnf} read by \KPS{}. The memory settings can be found in -Part 3 of that file in the \TL{} distribution. The more important -are: - -\begin{ttdescription} -\item[\texttt{main\_memory}] - Total words of memory available, for - \TeX{}, \MF{} and \MP. You must make a new format file for each - different setting. For instance, you could generate a ``huge'' - version of \TeX{}, and call the format file \texttt{hugetex.fmt}. - Using the standard way of specifying the program name used by \KPS{}, - the particular value of the \texttt{main\_memory} variable will then - be read from \file{texmf.cnf}. - etc.). -\item[\texttt{extra\_mem\_bot}] - Extra space for ``large'' \TeX{} data structures: - boxes, glue, breakpoints, etc. Especially useful if you use - \PiCTeX{}. -\item[\texttt{font\_mem\_size}] - Number of words for font information available for \TeX. This - is more or less the total size of all TFM files read. -\item[\texttt{hash\_extra}] - Additional space for the hash table of control sequence names. - Approximately 10,000 control sequences can be stored in the main - hash table; if you have a large book with numerous cross-references, - this might not be enough. The default value of - \texttt{hash\_extra} is \texttt{50000}. -\end{ttdescription} - -\noindent Of course, this facility is no substitute for truly dynamic -arrays and memory allocation, but since these are extremely difficult to -implement in the present \TeX{} source, these runtime parameters provide -a practical compromise allowing some flexibility. - - -\begin{comment} -\section{Building on a new Unix platform} - -If you have a platform for which executables are not included, you will -need to compile \TeX{} and friends. This is not as hard as it -sounds. What you need is all in the directory \texttt{source} in the -distribution. - -\subsection{Prerequisites} - -You will need at least 100 megabytes of disk space to compile all of -\TeX{} and its support programs. You'll also need an \acro{ANSI} C -compiler, a \cmdname{make} utility, a lexical scanner, and a parser -generator. We recommend the \acro{GNU} version of these programs -(\cmdname{gcc}, \acro{GNU} \cmdname{make}, \cmdname{m4}, \cmdname{flex}, -\cmdname{bison}). You may be able to work with other C compilers and -\cmdname{make} programs, but you will need a good understanding of -building Unix programs to sort out problems. - -Also, the command \texttt{uname} must return a sensible value. - - -\subsection{Configuration} - -To begin, perform a normal installation of \TL{} to your disk (see -section~\ref{sec:unix-install-disk} on -\p.\pageref{sec:unix-install-disk}). You may wish to skip installing -all of the prebuilt binaries. - -Then, unpack the source from the compressed \texttt{tar} file in the -directory \dirname{source} to your disk and change directory to where -you placed it. - -Next, run \cmdname{configure} with a command line like this: -\begin{alltt} -> \Ucom{sh configure -prefix=/usr/local/TeX} -\end{alltt} - -The \optname{-prefix} directory is the one where you installed the -support tree; the directory layout will be as follows (where \$TEXDIR -stands for the directory you chose): - -\noindent -\begin{tabular}{>{\ttfamily}ll@{}} - \dirname{$TEXDIR/share/texmf} & main tree with fonts,\\ - & \qquad macros, etc\\ - \dirname{$TEXDIR/man} & Unix manual pages\\ - \dirname{$TEXDIR/info} & \acro{GNU} style Info manuals\\ - \dirname{$TEXDIR/bin/$PLATFORM} & binaries\\ -\end{tabular} -%$ - -If you want to leave out the \dirname{$PLATFORM} directory level, -i.e., put the binaries directly into \dirname{$TEXDIR/bin}, specify -the \verb|--disable-multiplatform| option to \cmdname{configure}. - -Have a look at the output of \verb|./configure --help| for more -options you can use. For example, you can skip building of \OMEGA{} and -\eTeX{}. - - -\subsection{Running \cmdname{make}} - -Make sure the shell variable or option \texttt{noclobber} is not set. -Then, run the main \cmdname{make} like this: -\begin{alltt} -> \Ucom{make world} -\end{alltt} -and relax\ldots - -Alternatively, you want to log all the output, as in: -\begin{alltt} -> \Ucom{sh -c "make world >world.log 2>\&1" \&} -\end{alltt} - -Before you believe that everything went ok, please check the log file -for errors: \acro{GNU} \cmdname{make} always uses the string \samp{***} -whenever a command fails. Also, check if all the programs were built: - -\begin{alltt} -> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} -> \Ucom{ls | wc} -\end{alltt} -The result should be over 200 (you can check the exact number with the -\dirname{bin} directory contents in the distribution). - -If you need special privileges for \texttt{make install}, you can -separate the \samp{make world} into two different runs, like this: -\begin{alltt} -> \Ucom{make all} -> \Ucom{su} -> \Ucom{make install strip} -\end{alltt} - -After you've installed your new binaries, you should follow the normal -post-installation procedures, given in section~\ref{sec:postinstall} -(\p.\pageref{sec:postinstall}). - -Also, if you'd like to make your binaries available to others, please -contact us. We'll be happy to put them on the \TL\ web pages. -\end{comment} - -\section{Acknowledgements} - -\TL{} is a joint effort by virtually all of the \TeX{} user groups. -This edition of \TL{} was overseen by Sebastian Rahtz and Karl Berry. -The other principal contributors are listed below. - -\begin{itemize*} - -\item The German-speaking \TeX{} Users (\acro{DANTE} e.V.), who provide -the hardware for the \TL{} source repository; and Rainer Sch\"opf and -Reinhard Zierke who look after it. \acro{DANTE} officers Volker Schaa -and Klaus H\"oppner coordinate production with the Lehmann's Bookstore -(\url{http://www.lob.de}). - -\item The Perforce corporation (\url{http://www.perforce.com}), for providing -a free copy of their excellent change management system, which we use -to manage the \TL{} sources. - -\item Peter Breitenlohner and the \eTeX\ team for the stable foundation -of future \TeX's. - -\item Thomas Esser, without whose marvelous \teTeX{} package \TL{} -would certainly not exist, and whose continual help makes it a better -product. - -\item Michel Goossens, who co-authored the original documentation. - -\item Eitan Gurari, whose \TeX4ht was used to create the \HTML{} -version of this documentation, and who worked tirelessly to improve -it at short notice. - -\item Hans Hagen, for major testing and making the \ConTeXt\ format -conform to \TL's needs. - -\item Pawe{\l} Jackowski, for the Windows installer \cmdname{tlpm}, -and Tomasz {\L}uczak, for \cmdname{tlpmgui}. - -\item \Thanh, Martin Schr\"oder, and the pdf\TeX\ team for continuing -enhancements of \TeX's abilities. - -\item Petr Olsak, who coordinated and checked all the Czech and Slovak -material very carefully. - -\item Fabrice Popineau, for the Windows binaries in \TL{}. - -\item Staszek Wawrykiewicz, the principal tester for all of \TL{}, -and coordinator of the many major Polish contributions: fonts, Windows -installation, and more. - -\item Olaf Weber, for his patient assembly and maintenance of Web2C, -upon which all else depends. - -\item Gerben Wierda, for creating and maintaining the \MacOSX\ support, -and much integration and testing. - -\item Graham Williams, on whose work the catalogue of packages depends. - -\end{itemize*} - -Builders of the binaries: -Tigran Aivazian (\pkgname{x86\_64-linux}), -Manfred Lotz (\pkgname{i386-freebsd}), -Fabrice Popineau (\pkgname{win32}), -Norbert Preining (\pkgname{alpha-linux}), -Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-linux}, - \pkgname{sparc-solaris}), -Staszek Wawrykiewicz (\pkgname{i386-linux}), -Olaf Weber (\pkgname{mips-irix}), -Gerben Wierda (\pkgname{i386-darwin}, \pkgname{powerpc-darwin}). - -Documentation and translation updates: -Karl Berry (English), -Daniel Flipo \& Fabrice Popineau (French), -G\"unter Partosch \& Hartmut Henkel (German), -Petr Sojka \& Jan Busa (Czech\slash Slovak), -Boris Veytsman (Russian), -Staszek Wawrykiewicz (Polish). - -Of course the most important acknowledgement must go to Donald Knuth, first -for inventing \TeX, and then for giving it to the world. - - -\section{Release history} -\label{sec:history} - -\subsection{Past} - -Discussion began in late 1993 when the Dutch \TeX{} Users Group was -starting work on its 4All\TeX{} \CD{} for \acro{MS-DOS} users, and it -was hoped at that time to issue a single, rational, \CD{} for all -systems. This was too ambitious a target for the time, but it did spawn -not only the very successful 4All\TeX{} \CD{}, but also the \acro{TUG} -Technical Council working group on a \emph{\TeX{} Directory Structure} -(\url{http://tug.org/tds}), which specified how to create consistent and -manageable collections of \TeX{} support files. A complete draft of the -\TDS{} was published in the December 1995 issue of \textsl{TUGboat}, and -it was clear from an early stage that one desirable product would be a -model structure on \CD{}. The distribution you now have is a very direct -result of the working group's deliberations. It was also clear that the -success of the 4All\TeX{} \CD{} showed that Unix users would benefit -from a similarly easy system, and this is the other main strand of -\TL. - -We first undertook to make a new Unix-based \TDS{} \CD{} in the autumn -of 1995, and quickly identified Thomas Esser's \teTeX{} as the ideal -setup, as it already had multi-platform support and was built with -portability across file systems in mind. Thomas agreed to help, and work -began seriously at the start of 1996. The first edition was released in -May 1996. At the start of 1997, Karl Berry completed a major new release -of Web2c, which included nearly all the features which Thomas Esser had -added in \teTeX, and we decided to base the 2nd edition of the \CD{} on -the standard \Webc, with the addition of \teTeX's \texttt{texconfig} -script. The 3rd edition of the \CD{} was based on a major revision of -\Webc, 7.2, by Olaf Weber; at the same time, a new revision of \teTeX -was being made, and \TL{} included almost all of its features. The -4th edition followed the same pattern, using a new version of \teTeX, -and a new release of \Webc{} (7.3). The system now included a complete -Windows setup. - -For the 5th edition (March 2000) many parts of the \CD{} were revised -and checked, updating hundreds of packages. Package details were stored -in XML files. But the major change for \TeX\ Live 5 was that all -non-free software was removed. Everything in \TL{} is now intended -to be compatible with the Debian Free Software Guidelines -(\url{http://www.debian.org/intro/free}); we have done our best to check -the license conditions of all packages, but we would very much -appreciate hearing of any mistakes. - -The 6th edition (July 2001) had much more material updated. The major -change was a new install concept: the user could select a more exact set -of needed collections. Language-related collections were completely -reorganized, so selecting any of them installs not only macros, fonts, -etc., but also prepares an appropriate \texttt{language.dat}. - -The 7th edition of 2002 had the notable addition of \MacOSX{} support, -and the usual myriad of updates to all sorts of packages and -programs. An important goal was integration of the source back with -\teTeX, to correct the drift apart in versions~5 and~6. - -\subsubsection{2003} - -In 2003, with the continuing flood of updates and additions, we found -that \TL{} had grown so large it could no longer be contained on a -single \CD, so we split it into three different distributions (see -section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}). In -addition: - -\begin{itemize*} -\item At the request of the \LaTeX{} team, we changed the standard - \cmdname{latex} and \cmdname{pdflatex} commands to now use \eTeX{} (see - \p.\pageref{text:etex}). -\item The new Latin Modern fonts were included (and are recommended). -\item Support for Alpha \acro{OSF} was removed - (\acro{HPUX} support was removed previously), since no one had (or - volunteered) hardware available on which to compile new binaries. -\item Windows setup was substantially changed; for the first time - an integrated environment based on XEmacs was introduced. -\item Important supplementary programs for Windows - (Perl, Ghost\-script, Image\-Magick, Ispell) are now installed - in the \TL{} installation directory. -\item Font map files used by \cmdname{dvips}, \cmdname{dvipdfm} - and \cmdname{pdftex} are now generated by the new program - \cmdname{updmap} and installed into \dirname{texmf/fonts/map}. -\item \TeX{}, \MF{}, and \MP{} now, by default, output most input - characters (32 and above) as themselves in output (e.g., - \verb|\write|) files, - log files, and the terminal, i.e., \emph{not} translated using the - \verb|^^| notation. In \TL{}~7, this translation was - dependent on the system locale settings; now, locale settings do - not influence the \TeX{} programs' behavior. If for some reason - you need the \verb|^^| output, rename the file - \verb|texmf/web2c/cp8bit.tcx|. (Future releases will have cleaner - ways to control this.) -\item This documentation was substantially revised. -\item Finally, since the edition numbers had grown unwieldy, - the version is now simply identified by the year: \TL{} 2003. -\end{itemize*} - - -\subsubsection{2004} - -2004 saw many changes: - -\begin{itemize} - -\item If you have locally-installed fonts which use their own -\filename{.map} or (much less likely) \filename{.enc} support files, you -may need to move those support files. - -\filename{.map} files are now searched for in subdirectories of -\dirname{fonts/map} only (in each \filename{texmf} tree), along the -\envname{TEXFONTMAPS} path. Similarly, \filename{.enc} files are now -searched for in subdirectories of \dirname{fonts/enc} only, along the -\envname{ENCFONTS} path. \cmdname{updmap} will attempt to warn about -problematic files. - -For methods of handling this and other information, please see -\url{http://tug.org/texlive/mapenc.html}. - -\item The \TK\ has been expanded with the addition of a \MIKTEX-based -installable \CD, for those who prefer that implementation to Web2C. -See section~\ref{sec:struct-tl} (\p.\pageref{sec:struct-tl}). - -\item Within \TL, the single large \dirname{texmf} tree of previous -releases has been replaced by three: \dirname{texmf}, -\dirname{texmf-dist}, and \dirname{texmf-doc}. See -section~\ref{sec:tld} (\p.\pageref{sec:tld}), and the \filename{README} -files for each. - -\item All \TeX-related input files are now collected in -the \dirname{tex} subdirectory of \dirname{texmf*} trees, rather than -having separate sibling directories \dirname{tex}, \dirname{etex}, -\dirname{pdftex}, \dirname{pdfetex}, etc. See -\CDref{texmf-doc/doc/english/tds/tds.html\#Extensions} -{\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}. - -\item Helper scripts (not meant to be invoked by users) are now located -in a new \dirname{scripts} directory of \dirname{texmf*} trees, and -searched for via \verb|kpsewhich -format=texmfscripts|. So if you have -programs which call such scripts, they'll need to be adjusted. See -\CDref{texmf-doc/doc/english/tds/tds.html\#Scripts} -{\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}. - -\item Almost all formats leave most characters printable as -themselves via the ``translation file'' \filename{cp227.tcx}, instead of -translating them with the \verb|^^| notation. Specifically, characters -at positions 32--256, plus tab, vertical tab, and form feed are -considered printable and not translated. The exceptions are plain \TeX\ -(only 32--126 printable), \ConTeXt\ (0--255 printable), and the -\OMEGA-related formats. This default behavior is almost the same as in -\TL\,2003, but it's implemented more cleanly, with more possibilities -for customization. See \CDref{texmf/doc/web2c/web2c.html\#TCX-files} -{\texttt{texmf/doc/web2c/web2c.html\#TCX-files}}. -(By the way, with Unicode input, \TeX\ may output partial character -sequences when showing error contexts, since it is byte-oriented.) - -\item \textsf{pdfetex} is now the default engine for all formats -except (plain) \textsf{tex} itself. (Of course it generates \acro{DVI} -when run as \textsf{latex}, etc.) This means, among other things, that -the microtypographic features of \textsf{pdftex} are available in -\LaTeX, \ConTeXt, etc., as well as the \eTeX\ features -(\OnCD{texmf-dist/doc/etex/base/}). - -It also means it's \emph{more important than ever} to use the -\pkgname{ifpdf} package (works with both plain and \LaTeX) or equivalent -code, because simply testing whether \cs{pdfoutput} or some other -primitive is defined is not a reliable way to determine if \acro{PDF} -output is being generated. We made this backward compatible as best we -could this year, but next year, \cs{pdfoutput} may be defined even when -\acro{DVI} is being written. - -\item pdf\TeX\ (\url{http://pdftex.org}) has many new features: - - \begin{itemize*} - - \item \cs{pdfmapfile} and \cs{pdfmapline} provide font map support - from within a document. - - \item Microtypographic font expansion can be used more easily.\\ - \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} - - \item All parameters previously set through the special configuration - file \filename{pdftex.cfg} must now be set through primitives, - typically in \filename{pdftexconfig.tex}; \filename{pdftex.cfg} is no - longer supported. Any extant \filename{.fmt} files must be redumped - when \filename{pdftexconfig.tex} is changed. - - \item See the pdf\TeX\ manual for more: \OnCD{texmf/doc/pdftex/manual}. - - \end{itemize*} - -\item The \cs{input} primitive in \cmdname{tex} (and \cmdname{mf} and -\cmdname{mpost}) now accepts double quotes containing spaces and other -special characters. Typical examples: -\begin{verbatim} -\input "filename with spaces" % plain -\input{"filename with spaces"} % latex -\end{verbatim} -See the Web2C manual for more: \OnCD{texmf/doc/web2c}. - -\item enc\TeX\ support is now included within Web2C and consequently all -\TeX\ programs, via the \optname{-enc} option\Dash \emph{only when -formats are built}. enc\TeX\ supports general re-encoding of input and -output, enabling full support of Unicode (in \acro{UTF}-8). See -\OnCD{texmf-dist/doc/generic/enctex/} and -\url{http://www.olsak.net/enctex.html}. - -\item Aleph, a new engine combining \eTeX\ and \OMEGA, is available. -A little information is available in \OnCD{texmf-dist/doc/aleph/base} -and \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph}. The -\LaTeX-based format for Aleph is named \textsf{lamed}. - -\item The latest \LaTeX\ release has a new version of the -\acro{LPPL}\Dash now officially a Debian-approved license. Assorted -other updates, see the \filename{ltnews} files in -\OnCD{texmf-dist/doc/latex/base}. - -\item \cmdname{dvipng}, a new program for converting \acro{DVI} to -\acro{PNG} image files, is included. See \OnCD{texmf/doc/man/man1/dvipng.1}. - -\item We reduced the \pkgname{cbgreek} package to a ``medium'' sized set -of fonts, with the assent and advice of the author (Claudio Beccari). -The excised fonts are the invisible, outline, and transparency ones, -which are relatively rarely used, and we needed the space. The full set -is of course available from \acro{CTAN} -(\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). - -\item \cmdname{oxdvi} has been removed; just use \cmdname{xdvi}. - -\item The \cmdname{ini} and \cmdname{vir} commands (links) for -\cmdname{tex}, \cmdname{mf}, and \cmdname{mpost} are no longer created, -such as \cmdname{initex}. The \cmdname{ini} functionality has been -available through the command-line option \optname{-ini} for years now. - -\item \textsf{i386-openbsd} platform support was removed. Since the -\pkgname{tetex} package in the \acro{BSD} Ports system is available, and -\acro{GNU/}Linux and Free\acro{BSD} binaries were available, it seemed -volunteer time could be better spent elsewhere. - -\item On \textsf{sparc-solaris} (at least), you may have to set the -\envname{LD\_LIBRARY\_PATH} environment variable to run the -\pkgname{t1utils} programs. This is because they are compiled with C++, -and there is no standard location for the runtime libraries. (This is -not new in 2004, but wasn't previously documented.) Similarly, on -\textsf{mips-irix}, the \acro{MIPS}pro 7.4 runtimes are required. - -\end{itemize} - -\subsection{Present} -\label{tlcurrent} - -2005 saw the usual huge number of updates to packages and programs. -The infrastructure stayed relatively stable from 2004, but inevitably -there were some changes there as well: - -\begin{itemize} - -\item New scripts \cmdname{texconfig-sys}, \cmdname{updmap-sys}, and - \cmdname{fmtutil-sys} were introduced, which modify the - configuration in the system trees. The \cmdname{texconfig}, - \cmdname{updmap}, and \cmdname{fmtutil} scripts now modify - user-specific files, under \dirname{$HOME/.texlive2005}. - See section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig}. - -\item Corresponding new variables \envname{TEXMFCONFIG} and - \envname{TEXMFSYSCONFIG} to specify the trees where configuration - files (user or system, respectively) are found. Thus, you may - need to move personal versions of \filename{fmtutil.cnf} and - \filename{updmap.cfg} to these places; another option is to - redefine \envname{TEXMFCONFIG} or \envname{TEXMFSYSCONFIG} in - \filename{texmf.cnf}. In any case the real location of these files - and the values of \envname{TEXMFCONFIG} and \envname{TEXMFSYSCONFIG} - must agree. - See section~\ref{sec:texmftrees}, \p.\pageref{sec:texmftrees}. - -\item Last year, we kept \verb|\pdfoutput| and other primitives undefined - for DVI output, even though the \cmdname{pdfetex} program was - being used. This year, as promised, we undid that compatibility - measure. So if your document uses \verb|\ifx\pdfoutput\undefined| - to test if PDF is being output, it will need to be changed. You - can use the package \pkgname{ifpdf.sty} (which works under both - plain \TeX\ and \LaTeX) to do this, or steal its logic. - -\item Last year, we changed most formats to output (8-bit) characters as - themselves (see previous section). The new TCX file - \filename{empty.tcx} now provides an easier way to get the - original \verb|^^| notation if you so desire, as in: -\begin{verbatim} -latex --translate-file=empty.tcx yourfile.tex -\end{verbatim} - -\item The new program \cmdname{dvipdfmx} is included for translation of - DVI to PDF; this is an actively maintained update of - \cmdname{dvipdfm} (which is also still available for now, though - no longer recommended). - -\item The new programs \cmdname{pdfopen} and \cmdname{pdfclose} are included - to allow reloading of pdf files in the Adobe Acrobat Reader without - restarting the program. (Other pdf readers, notably \cmdname{xpdf}, - \cmdname{gv}, and \cmdname{gsview}, have never suffered from this - problem.) - -\item For consistency, the variables \envname{HOMETEXMF} and - \envname{VARTEXMF} have been renamed to \envname{TEXMFHOME} and - \envname{TEXMFSYSVAR}, respectively. There is also - \envname{TEXMFVAR}, which is by default user-specific. See the - first point above. - -\end{itemize} - -\subsection{Future} - -\emph{\TL{} is not perfect!} (And never will be.) We intend to -continue to release new versions yearly, and would like to provide more -help material, more utilities, more installation programs, and (of -course) an ever-improved and checked tree of macros and fonts. This work -is all done by hard-pressed volunteers in their limited spare time, and -a great deal remains to be done. If you can help, don't hesitate to put -your name forward! - -Please send corrections, suggestions, and offers of help to:\hfill\null -\begin{quote} -Sebastian Rahtz \ / \ 7 Stratfield Road \ / \ Oxford OX2 7BG \ / \ UK \\ -\email{tex-live@tug.org} \\ -\url{http://tug.org/texlive} -\end{quote} - -\medskip -\noindent \textsl{Happy \TeX ing!} - -\end{document} diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/live-2007.tex b/Master/texmf-doc/source/texlive/texlive-en/archive/live-2007.tex deleted file mode 100644 index 8232db8becf..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/live-2007.tex +++ /dev/null @@ -1,3264 +0,0 @@ -% $Id: live.tex 3938 2007-02-06 01:49:45Z karl $ -% TeX Live documentation. Originally written by Sebastian Rahtz and -% Michel Goossens, now maintained by Karl Berry and others. -% Public domain. -% -\documentclass{article} -\let\tldocenglish=1 % for live4ht.cfg -\usepackage{tex-live} -\begin{document} - -\title{% - {\huge \textit{The \protect\TL{} Guide}\\\strut} - {\LARGE \textsf{\TL{} 2007}} -} - -\author{Karl Berry, editor \\[3mm] - \url{http://tug.org/texlive/} - } - -\date{January 2007} - -\maketitle - -\begin{multicols}{2} -\tableofcontents -\listoftables -\end{multicols} - -\section{Introduction} -\label{sec:intro} - -This document describes the main features of the \TL{} software -distribution\Dash \TeX{} and friends for \acro{GNU}/Linux and other Unix -flavors, \MacOSX, and (32-bit) Windows systems. (Warning: it is not -especially useful for older Mac or \acro{MS-DOS} systems.) - -\TL{} includes executables for \TeX{}, \LaTeXe{}, \ConTeXt, \MF, \MP, -\BibTeX{} and many other programs; an extensive collection of macros, -fonts and documentation; and support for typesetting in many different -scripts from around the world. It is part of the even larger \TK{} -(briefly described below in section~\ref{sec:struct-tl}, -\p.\pageref{sec:struct-tl}). Both are cooperative efforts by the \TeX\ -user groups. - -For newer versions of the packages included here, please check -\acro{CTAN}: \url{http://www.ctan.org}. - -For a brief summary of the major changes in this edition of \TL{}, -see the end of the document, section~\ref{sec:history} -(\p.\pageref{sec:history}). - - -\subsection{Basic usage of \protect\TL{}} -\label{sec:basic} - -You can use \TL{} in three principal ways: - -\begin{enumerate} - -\item You can run \TL{} directly from the \pkgname{live} \DVD -(see section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}). -This takes almost no disk space, and gives you immediate access to -everything in \TL{}. Of course performance will be worse than running -on local disk, but you may well find it useful. - -\item You can install all or part of \TL{} to a local disk, from either -the \DVD\ or the \pkgname{inst} \acro{CD}. This is the most common use -of \TL. You will need (approximately) 100 megabytes for the most -minimal system, and upwards of 1.3 gigabytes for a full system. - -\item You can integrate a particular package or collection into your -existing \TeX{} system, either a \TL{} system you installed -earlier, or a different system. - -\end{enumerate} - -\noindent All of these are described in detail in the \acro{OS}-specific -installation sections following, but here is a quick start: - -\begin{itemize*} - -\item The main installation script for Unix and \MacOSX{} is -\texttt{install-tl.sh}. -GNU/Linux users can also try a new GUI installation program: -run \texttt{setuptl/tlpmgui}. More information -can be found in section \ref{sec:win-install} on -p.~\pageref{sec:win-install}. - -\item The single package installation script is \texttt{install-pkg.sh}. -(After installation on Linux with \texttt{tlpmgui}, you can also try -running \texttt{tlpmgui} again to add or remove individual packages or -collections.) - -\item The installation program for Windows is \texttt{tlpmgui.exe}. -It can be used also for adding or removing the packages. -See section~\ref{sec:win-install} below for more information. - -\end{itemize*} - - -\subsection{Getting help} -\label{sec:help} - -The \TeX{} community is both active and friendly, and virtually all -serious questions end up getting answered. However, the support is -informal, done by volunteers and casual readers, so it's especially -important that you do your homework before asking. (If you prefer -guaranteed commercial support, you can forego \TL{} completely and -purchase a vendor's system; \url{http://tug.org/interest.html#vendors} -has a list.) - -Here is a list of resources, approximately in the order we recommend -using them: - -\begin{description} -\item [Getting Started] If you are new to \TeX, the web page -\url{http://tug.org/begin.html} gives a brief introduction to the system. - -\item [\TeX{} \acro{FAQ}] The \TeX{} \acro{FAQ} is a huge compendium of -answers to all sorts of questions, from the most basic to the most -arcane. It is included on \TL{} in \OnCD{texmf-doc/doc/english/FAQ-en}, and is -available on the Internet through \url{http://www.tex.ac.uk/faq}. -Please check here first. - -\item [\TeX{} Catalogue] If you are looking for a specific package, -font, program, etc., the \TeX{} Catalogue is the place to look. It is a -huge collection of all \TeX{}-related items. See -\OnCD{texmf-doc/doc/english/catalogue}, or -\url{http://www.ctan.org/tex-archive/help/Catalogue}. - -\item [\TeX{} Web Resources] The web page -\url{http://tug.org/interest.html} has many \TeX{}-related links, in -particular for numerous books, manuals, and articles on all aspects of -the system. - -\item [support archives] The two principal support forums are the -Usenet newsgroup \url{news:comp.text.tex} and the mailing list -\email{texhax@tug.org}. Their archives have years of past -questions and answers for your searching pleasure, via -\url{http://groups.google.com/groups?group=comp.text.tex} and -\url{http://tug.org/mail-archives/texhax}, respectively. And a general web -search, for example on \url{http://google.com}, never hurts. - -\item [asking questions] If you cannot find an answer, you can post to -\dirname{comp.text.tex} through Google or your newsreader, or to -\email{texhax@tug.org} through email. But before you post, -\emph{please} read this \acro{FAQ} entry on asking questions in such a -way that you're most likely to get an answer: -\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. - -\item [\TL{} support] If you want to report a bug or have -suggestions or comments on the \TL{} distribution, installation, or -documentation, the mailing list is \email{tex-live@tug.org}. However, -if your question is about how to use a particular program included in -\TL{}, you are better off writing to that program's maintainer or -mailing list. - -\end{description} - -The other side of the coin is helping others who have questions. Both -\dirname{comp.text.tex} and \code{texhax} are open to anyone, so feel -free to join, start reading, and help out where you can. Welcome to -\TeX{}! - - -% don't use \TL so the \uppercase in the headline works. Also so -% tex4ht ends up with the right TeX. Likewise the \protect's. -\section{Structure of \protect\TeX\protect\ Live} -\label{sec:struct-tl} - -This section describes the structure and contents of \TL{} and the -\TK{} of which it is a part. - -\subsection{Multiple distributions: \protect\pkgname{live}, - \protect\pkgname{inst}, - \protect\pkgname{protext}} -\label{sec:multiple-dist} - -Space limitations of \acro{CD-ROM} format have forced us to divide -\TK{} into several distributions, as follows. - -\begin{description} - -\item [live] A complete system on \acro{DVD}; it is too large -for \acro{CD}. It can be run live or installed to disk. It also -includes a snapshot of the \CTAN{} repository, the \pkgname{protext} -distribution for Windows and the Mac\TeX\ distribution for \MacOSX, entirely -independent of \TL{}, as well as assorted other packages in a -\texttt{texmf-extra} directory. - -\CTAN{}, \pkgname{protext}, Mac\TeX, and \texttt{texmf-extra} do not follow -the same copying conditions as \TL{}, so be careful when redistributing or -modifying. - -\item [inst(allable)] A complete system on \CD; in order to make this fit, -the packages and programs are compressed. Therefore, it is not possible -to run \TeX\ directly from the installable \CD, you have to install it -to disk (hence its name). Installation is described in subsequent sections. - -\item [protext] An enhancement of the \MIKTEX\ distribution for Windows, -\ProTeXt\ adds a few extra tools to \MIKTEX, and simplifies -installation. It is entirely independent of \TL{}, and has its own -installation instructions. It can be run live, or installed to disk. -The \ProTeXt\ home page is \url{http://tug.org/protext}. - -\ProTeXt\ is provided as both the top level of the \pkgname{live} \DVD\ -and on its own \CD\ (for those who cannot use the \DVD). - -\end{description} - -\noindent You can tell which type of distribution you're in by looking -for a \texttt{00\var{type}.TL} file at the top of the \TL{} directory. -This file also contains the \TL{} release date. - -Naturally, each user group chooses what to distribute to its own members. - - -\subsection{Top level directories} -\label{sec:tld} - -Here is a brief listing and description of the top level directories in -the \TL{} distribution. On the \pkgname{live} \DVD, the entire \TL{} -hierarchy is in a subdirectory \dirname{texliveYYYY}, not at the top -level of the disc. - -\smallskip -\begingroup - \renewcommand{\arraystretch}{1.3} % open up interrow spacing -\begin{tabular}{>{\ttfamily}lp{.78\hsize}} -bin & The \TeX{} system programs, arranged by platform. \\ -source & The source of all programs, including the main \Webc{} - \TeX{} and \MF{} distributions. These are stored in a - \cmdname{bzip2}-compressed tar archive. \\ -setuptl & Installation programs for Linux and Windows. \\ -support & Assorted auxiliary packages and programs. These are - \emph{not} installed automatically. This includes - assorted editors and \TeX\ shells. \\ -texmf & Tree for the programs, along with their support files and - documentation. Does not include \TeX\ formats and packages. - (\texttt{TEXMFMAIN} in the next section.) \\ -texmf-dist & The main tree of formats and packages. - (\texttt{TEXMFDIST} in the next section.) \\ -texmf-doc & Tree for self-contained pure documentation, arranged by - language. \\ -texmf-var & Tree for files automatically generated and stored. - (\texttt{TEXMFSYSVAR} in the next section.) \\ -\end{tabular} -\endgroup - -\smallskip - -In addition to the directories above, the installation scripts and -\filename{README} files (in various languages) are at the top level of -the distribution. - -The \dirname{texmf-doc} directory contains only documentation, but -it does not contain all the documentation. The documentation for the -programs (manuals, man pages, Info files) is in \dirname{texmf/doc}, -since the programs are in \dirname{texmf}. Similarly, the documentation -for \TeX\ packages and formats is in \dirname{texmf-dist/doc}. You can -use the \cmdname{texdoc} or \cmdname{texdoctk} programs to find any -documentation wherever it's located. The comprehensive links in the -top-level file \OnCD{doc.html} may also be helpful. - - -\subsection{Overview of the predefined texmf trees} -\label{sec:texmftrees} - -This section lists all predefined variables specifying texmf trees used -by the system, and their intended purpose. The command \texttt{texconfig -conf} shows you the values of these variables, so that you can easily -find out how they map to directory names in your installation. - -\begin{ttdescription} -\item [TEXMFMAIN] The tree which holds vital parts of the system - such as helper scripts (e.g., \verb+web2c/mktexdir+), pool files and - other support files. -\item [TEXMFDIST] The tree which holds the main set of macro packages, - fonts, etc., as originally distributed. -\item [TEXMFLOCAL] The tree which administrators can use for system-wide - installation of additional or updated macros, fonts, etc. -\item [TEXMFHOME] The tree which users can use for their own individual - installations of additional or updated macros, fonts, etc. - The expansion of this variable depends on \verb+$HOME+ by default, % $ - which dynamically adjusts for each user to an individual - directory. -\item [TEXMFCONFIG] The tree used by te\TeX's utilities - \verb+texconfig+, \verb+updmap+, and \verb+fmtutil+ to store modified - configuration data. Under \verb+$HOME+ by default. %$ -\item [TEXMFSYSCONFIG] The tree used by te\TeX's utilities - \verb+texconfig-sys+, \verb+updmap-sys+, and \verb+fmtutil-sys+ to - store modified configuration data. -\item [TEXMFVAR] The tree used by \verb+texconfig+, \verb+updmap+ and - \verb+fmtutil+ to store (cached) runtime data such as format files and - generated map files. Under \verb+$HOME+ by default. %$ -\item [TEXMFSYSVAR] The tree used by \verb+texconfig-sys+, - \verb+updmap-sys+ and \verb+fmtutil-sys+ to store (cached) runtime - data such as format files and generated map files. -\end{ttdescription} - -For more discussion of \texttt{texconfig} and related utilities, please -see section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig}. - - -\subsection{Extensions to \protect\TeX} -\label{sec:tex-extensions} - -\TL{} contains several extended versions of \TeX: - -\begin{description} - -\item [\eTeX] adds a small but powerful set of new primitives -\label{text:etex} (related to macro expansion, character scanning, -classes of marks, additional debugging features, and more) and the -\TeXXeT{} extensions for bidirectional typesetting. In default mode, -\eTeX{} is 100\% compatible with ordinary \TeX. See -\OnCD{texmf-dist/doc/etex/base/etex_man.pdf}. - -\item [pdf\TeX] builds on the \eTeX\ extensions, adding support for -writing \acro{PDF} output as well as \dvi{}. See -\OnCD{texmf/doc/pdftex/manual/} for the manual, and -\OnCD{texmf/doc/pdftex/manual/samplepdf/samplepdf.tex}. This is the -default program for all formats except plain \TeX. - -\item [Xe\TeX] adds support for Unicode input and OpenType fonts, using -third-party libraries. See \url{http://scripts.sil.org/xetex}. - -\item [\OMEGA\ (Omega)] is based on Unicode (16-bit characters), thus -supports working with almost all the world's scripts simultaneously. It -also supports so-called `\OMEGA{} Translation Processes' (\acro{OTP}s), -for performing complex transformations on arbitrary input. See -\OnCD{texmf-dist/doc/omega/base/doc-1.8.tex} (not completely up-to-date). - -\item [Aleph] combines the \OMEGA\ and \eTeX\ extensions. -See \OnCD{texmf-dist/doc/aleph/base} for some minimal documentation. - -\end{description} - - -\subsection{Other notable programs in \protect\TL} - -Here are a few other commonly-used programs included in \TL{}: - -\begin{cmddescription} - -\item [bibtex] bibliography support. - -\item [makeindex] index support. - -\item [dvips] convert \dvi{} to \PS{}. - -\item [xdvi] \dvi{} previewer for the X Window System. - -\item [dvilj] \dvi{} drive for the HP LaserJet family. - -\item [dv2dt, dt2dv] convert \dvi{} to/from plain text. - -\item [dviconcat, dviselect] cut and paste pages -from \dvi{} files. - -\item [dvipdfmx] convert \dvi{} to \acro{PDF}, an alternative approach -to pdf\TeX\ (mentioned above). See the \pkgname{ps4pdf} and -\pkgname{pdftricks} packages for still more alternatives. - -\item [psselect, psnup, \ldots] \PS{} -utilities. - -\item [lacheck] \LaTeX{} syntax checker. - -\item [texexec] Con\TeX{}t and \acro{PDF} processor. - -\item [tex4ht] \TeX{} to \acro{HTML} converter. - -\end{cmddescription} - - -\section{Unix installation} -\label{sec:unix-install} - -As introduced in section~\ref{sec:basic} (\p.\pageref{sec:basic}), -\TL{} has three principal uses: - -\begin{enumerate} -\item Run directly from media. -\item Install to disk. -\item Integrate a particular package or collection into your existing -\TeX{} installation. -\end{enumerate} - -\noindent The following sections describes the Unix-specific procedures -for each of these. - -\ifSingleColumn \begin{figure}[ht]\noindent \fi -\begin{warningbox} -\textbf{Warning: } The \TK{} \CD{}s and \DVD{} are in ISO 9660 (High Sierra) -format, \emph{with} Rock Ridge (and Joliet, for Windows) -extensions. Therefore, in order to take full advantage of the \TK{} -under Unix, your system needs to be able to use the Rock Ridge -extensions. Please consult the documentation for your \cmdname{mount} -command to see how to do this. If you have several different machines -on a local network, you may be able to mount the discs on one which -does support Rock Ridge, and use this with the others. - -\leavevmode\quad Modern systems should be able to use the discs without -problems. If troubles, let us know. The discussion below assumes you -have been able to mount the \CD{}s with full Rock Ridge compatibility. -\end{warningbox} -\ifSingleColumn\end{figure}\fi - - -% -\subsection{Running \protect\TL{} directly from media (Unix)} - -\def\runlive{% text repeated in windows section -It is possible to use the \TeX{} system directly from the \pkgname{live} -\DVD{}, without installing the distribution to disk. (Thus the name -\TeX\ `Live', in fact.) It is \emph{not} possible to run \TeX{} -directly from the other \CD{}s (see section~\ref{sec:multiple-dist}, -\p.\pageref{sec:multiple-dist}). -} - -\def\startinst{% repeated in other subsections -To start, you mount the \CD{} or \DVD{}, with Rock Ridge extensions -enabled. The exact command to do this varies from system to system; the -following works under Linux, except the name of the device -(\filename{/dev/cdrom}, here) may vary. (All our examples will use -\texttt{>} as the shell prompt; user input is -\Ucom{\texttt{underlined}}.) -\begin{alltt} -> \Ucom{mount -t iso9660 /dev/cdrom /mnt/cdrom} -\end{alltt} - -\noindent Change the current directory to the mount point: -\begin{alltt} -> \Ucom{cd /mnt/cdrom} -\end{alltt} - -\noindent Under \MacOSX, the directory is typically under -\dirname{/Volumes}, and the media will be mounted automatically. -} - -\def\installtlsh{ -Run the installation script \filename{install-tl.sh}: -\begin{alltt} -> \Ucom{sh install-tl.sh}\\ -Welcome to TeX Live... -\end{alltt} - -\noindent After various greeting messages and a list of the main menu -options, the installation will ask you to enter a command. Do this by -typing the desired character and hitting return; don't type the angle -brackets shown. Either uppercase or lowercase is ok; we'll use -lowercase in our examples. -} - -\runlive -\startinst -\installtlsh - -For running live, our first command will be \Ucom{d} and then the -subcommand \Ucom{1} to set directories. Even in this case, we must -choose a directory on the local disk to place files that the \TeX{} -system itself generates, such as fonts and formats, and also to provide -a place for updated configuration files, if need be. - -We'll use \dirname{/opt/texlive2007} in this example. It's good to -include the year in the name, as these generated files are not -in general compatible from release to release. (If the default value of -\dirname{/usr/local/texlive/2007} works for you, then you can skip this -step.) - -\begin{alltt} -Enter command: \Ucom{d} -Current directories setup: -<1> TEXDIR: /usr/local/texlive/2007 -... -Enter command: \Ucom{1} -New value for TEXDIR [/usr/local/texlive/TeX]: \Ucom{/opt/texlive2007} -... -Enter command: \Ucom{r} -\end{alltt} - -\noindent Back at the main menu, our second and last command is -\Ucom{r}, to set up for running live off the media without installing -to disk: -\begin{alltt} -Enter command: \Ucom{r} -Preparing destination directories... -... -Welcome to TeX Live! -> -\end{alltt} - -\noindent And we are back at the system prompt, as shown. - -Next, it is necessary to alter two environment variables: -\envname{PATH}, to an architecture-dependent value (so that we can run -the programs), and \envname{TEXMFSYSVAR}, to the value specified above. -See table~\ref{tab:archlist} for a list of the architecture names for -the different systems. - - -\def\textruntexconfig{% -After the main installation has completed, and environment variables -have been set, the last step is to run \cmdname{texconfig} or -\cmdname{texconfig-sys} to customize your installation to your needs. -This is explained in section~\ref{sec:texconfig}, -\p.\pageref{sec:texconfig}. -} -\textruntexconfig - -\begin{table*}[ht] -\caption[Supported system architectures.]{Supported system -architectures.} -\label{tab:archlist} -\begin{tabular}{>{\ttfamily}ll} -alpha-linux & HP Alpha GNU/Linux \\ -hppa-hpux & HPPA HP-UX \\ -i386-darwin & x86 \MacOSX \\ -i386-freebsd & x86 FreeBSD \\ -i386-linux & x86 GNU/Linux \\ -i386-openbsd & x86 OpenBSD \\ -i386-solaris & x86 Solaris \\ -mips-irix & SGI IRIX \\ -powerpc-aix & IBM RS/6000 AIX \\ -powerpc-darwin & PowerPC \MacOSX \\ -powerpc-linux & PowerPC GNU/Linux \\ -sparc-linux & Sun Sparc GNU/Linux \\ -sparc-solaris & Sun Sparc Solaris \\ -win32 & Windows (32-bit) \\ -x86\_64-linux & x86 64-bit GNU/Linux \\ -\hline -\end{tabular} -\end{table*} - -\label{text:path} -The syntax for setting the environment variables, and the initialization -file to put them in, depends on the shell you use. If you use a -Bourne-compatible shell (\cmdname{sh}, \cmdname{bash}, \cmdname{ksh}, et -al.), put the following into your \filename{$HOME/.profile} file: -\begin{alltt} -PATH=/mnt/cdrom/bin/\var{archname}:$PATH; export PATH -TEXMFSYSVAR=/opt/texlive2007/texmf-var; export TEXMFSYSVAR -\end{alltt} - -\noindent For C shell-compatible shells (\cmdname{csh}, \cmdname{tcsh}), -put the following into your \filename{$HOME/.cshrc} file: -\begin{alltt} -setenv PATH /mnt/cdrom/bin/\var{archname}:$PATH -setenv TEXMFSYSVAR /opt/texlive2007/texmf-var -\end{alltt} - -\noindent Then log out, log back in, and test your installation -(see section~\ref{sec:test-install}, \p.\pageref{sec:test-install}). - -\def\textifindoubt{% -If in doubt, please ask any local system gurus to help you with -problems; for example, the way to mount the \TL{} media, which -directory or directories to use, and precise details of the changes to -your personal initialization files can and do vary from site to site. -} -\textifindoubt - - -% -\subsection{Installing \protect\TeX\protect\ Live to disk} -\label{sec:unix-install-disk} - -It is possible, indeed typical, to install the \TL{} distribution to -hard disk. This can be done from either the \pkgname{live} or -\pkgname{inst} distributions. (See section~\ref{sec:multiple-dist}, -\p.\pageref{sec:multiple-dist}, for an explanation of the different -distributions.) - -\startinst -\installtlsh - -Table~\ref{tab:main-menu-options} briefly lists the options in the main -menu. The order in which you select the options makes little -difference, except that \Ucom{i} must be last. It's reasonable to go -through them in the order presented here. - -% apparently here.sty [H] doesn't support table*. -\begin{table}[H] -\caption{Main menu options for the installation.} -\label{tab:main-menu-options} -\begin{tabular}{>{\ttfamily}ll} -p & The platform you are running on.\\ -b & The architectures for which to install binaries.\\ -s & The base installation scheme to use (minimal, recommended, - full, etc.)\\ -c & Override the base scheme for individual collections.\\ -l & Override for language collections.\\ -d & Directories in which to install.\\ -o & Other options.\\ -i & Perform the installation.\\ -\end{tabular} -\end{table} - -Here are further details on each option. - -\textbf{\optname{p} -- Current platform.} Since the installation script -automatically guesses which platform you're running on, it is usually -unnecessary to use this option. It's there in case you need to override -the automatic detection. - -\textbf{\optname{b} -- Binary architectures.} By default, only the -binaries for your current platform will be installed. From this menu, -you can select installation of binaries for other architectures as well -(or omit installing the current platform). This can be useful if you are -sharing a \TeX\ tree across a network of heterogenous machines. For a -list of the supported architectures, see table~\ref{tab:archlist}, -\p.\pageref{tab:archlist}. - -\textbf{\optname{s} -- Base installation scheme.} From this menu, you -can choose an overall set of package collections, called a ``scheme''. -The default \optname{full} scheme installs everything available, but you -can also choose the \optname{basic} scheme for a minimal system, or -\optname{medium} to get something in between. There are also specific -sets for Omega and \acro{XML}. - -\textbf{\optname{c} -- Individual collections.} From this menu, you can -override the scheme's set of collections to install. Collections are -one level more detailed than schemes\Dash collections consist of one or -more packages, where packages (the lowest level grouping in \TL) contain -the actual \TeX\ macro files, font families, and so on. In this menu, -selection letters are case-sensitive. - -\textbf{\optname{l} -- Language collections}. This menu has the same -basic purpose as \Ucom{c}, to override the collection set in the chosen -scheme. In this case, the collections are specifically for different -languages. Selection letters are case-sensitive here too. Here is a -list of the language collections in \TL: - -% xx really should generate list from texmf/tpm/collection/tex-lang* -% a la install-tl.sh. -\begin{tabbing} -\hspace{.25\linewidth} \= -\hspace{.25\linewidth} \= -\hspace{.25\linewidth} \= -\hspace{.25\linewidth} \kill -(some) African scripts \> -Arabic \> -Armenian \> -Chinese\,Japanese\,Korean \\ -Croatian \> -Cyrillic \> -Czech/Slovak \> -Danish \\ -Dutch \> -Finnish \> -French \> -German \\ -Greek \> -Hebrew \> -Hungarian \> -Indic \\ -Italian \> -Latin \> -Manju \> -Mongolian \\ -Norwegian \> -Polish \> -Portuguese \> -Spanish \\ -Swedish \> -Tibetan \> -\acro{UK} English \> -Vietnamese \\ -\end{tabbing} - -\noindent Language collections typically include fonts, macros, -hyphenation patterns, and other support files. (For instance, -\pkgname{frenchle.sty} is installed if you select the \optname{French} -collection.) In addition, installing a language collection will alter -the \filename{language.dat} configuration file controlling which -hyphenation patterns are loaded. - -\textbf{\optname{d} -- Installation directories}. Three directories can -be changed here: -\label{text:instdir} - -\begin{ttdescription} -\item [TEXDIR] The top-level directory under which -everything else will be installed. The default value is -\dirname{/usr/local/texlive/2007}, and is often changed. We recommend -including the year in the name, to keep different releases of \TL{} -separate. (You may wish to make a version-independent name such -\dirname{/usr/local/texlive} via a symbolic link, which you can then -update after testing the new release.) - -Under \MacOSX, the usual frontends look for \TeX{} in -\dirname{/usr/local/teTeX}, so you may wish to install \TL{} there. - -\item [TEXMFLOCAL] This tree is where the \TeX{} system (not as part of -the initial installation, but rather as time goes by) puts -non-version-specific files, primarily fonts. The default value is -\dirname{/usr/local/texlive/texmf-local}, independent of the current -\TL{} release, because it's also the recommended location to put any -local packages or configuration settings. - -\item [TEXMFSYSVAR] This tree is where \cmdname{texconfig-sys} puts -files that \emph{are} version-specific. The default value is -\dirname{TEXDIR/texmf-var}, and there's generally no reason to change -it. There is also \envname{TEXMFSYSCONFIG}, which is where -\cmdname{texconfig} looks for modified configuration data. See -section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig} for more -information. - -\end{ttdescription} - -\textbf{\optname{o} -- Other options.} From this menu, you can select -the following general options: - -\begin{ttdescription} -\item [a] Specify an alternate directory for generated fonts. -The default is to use the \envname{TEXMFVAR} tree, as explained above. -Setting this is useful if you plan to mount the main tree read-only, and -therefore you need another location (perhaps host-specific) for -dynamically created fonts. - -\item [l] Create symbolic links for the binaries, man pages, -and\slash or \acro{GNU} Info files in other locations. For example, you may -wish to make the man pages available under \dirname{/usr/local/man} and -the Info files available under \dirname{/usr/local/info}. (Of course -you need appropriate privileges to write in the specified directories.) - -It is not advisable to overwrite a \TeX\ system that came with your -system with this option. It's intended primarily for creating the links -in standard directories that are known to users, such as -\dirname{/usr/local/bin}, which don't already contain any \TeX\ files. - -\item [d] Skip installation of the font/macro documentation tree. -This is useful if you need to save space, or if you've previously -installed the documentation elsewhere. - -\item [s] Skip installation of the main font/macro source -tree. This is useful if you are arranging to share that tree between -machines and\slash or architectures in some other way, such as \acro{NFS}. - -\end{ttdescription} - -\textbf{i -- Perform installation.} When you're satisfied with your -configuration options, enter \Ucom{i} to actually do the installation -from the media to your chosen locations. - -% text is similar to above, but no TEXMFSYSVAR, so we have to write out. -After the installation completes, your next step is to include the -architecture-specific subdirectory of \dirname{TEXDIR/bin} in your -\envname{PATH}, so the newly-installed programs can be found. The -architecture names are listed in table~\ref{tab:archlist}, -\p.\pageref{tab:archlist}, or you can simply list the directory -\dirname{TEXDIR/bin}. - -The syntax for doing this, and the initialization file to use, depends -on your shell. If you use a Bourne-compatible shell (\cmdname{sh}, -\cmdname{bash}, \cmdname{ksh}, et al.), put the following into your -\filename{$HOME/.profile} file: - -\begin{alltt} -PATH=/usr/local/texlive/2007/bin/\var{archname}:$PATH; export PATH -\end{alltt} - -\noindent For C shell-compatible shells (\cmdname{csh}, \cmdname{tcsh}), -put the following into your \filename{$HOME/.cshrc} file: -\begin{alltt} -setenv PATH /usr/local/texlive/2007/bin/\var{archname}:$PATH -\end{alltt} - -\textruntexconfig - -Here is a minimal annotated example which accepts the default -directories and installs binaries for the current system only. Thus, -only one command is needed, \Ucom{i} for install. The \texttt{>} is the -shell prompt as usual. - -\begin{alltt} -> \Ucom{sh install-tl.sh} -\Ucom{i} # perform installation -> \Ucom{texconfig} ... # see section \ref{sec:texconfig} -# New PATH element, with Linux as the example: -> \Ucom{PATH=/usr/local/texlive/2007/bin/i386-linux:$PATH; export PATH} -\end{alltt} - -If your Unix system supports the \cmdname{manpath} command (type \code{man -manpath} to learn more), you can make the \TL\ manual pages available -system-wide via the normal \cmdname{man} command by editing the file -\filename{/etc/manpath.config}; you might need root permissions for this. -With the following entry in \filename{/etc/manpath.config} the \TL\ -manual pages will be found at their original places within the \TL\ tree -(adapt the binary path for your system architecture): - -\begin{verbatim} -MANPATH_MAP /usr/local/texlive/2007/bin/i386-linux \ - /usr/local/texlive/2007/texmf/doc/man -\end{verbatim} - -\textifindoubt - - -\subsubsection{Non-interactive installation} -\label{sec:noninteractive-install} - -It is possible to override the default directories with environment -variables, and then install non-interactively. Example: -\begin{alltt} -> \Ucom{TEXLIVE_INSTALL_PREFIX=/opt/texlive} -> \Ucom{export TEXLIVE_INSTALL_PREFIX} -> \Ucom{echo i | sh install-tl.sh} -\end{alltt} - -The \envname{TEXLIVE\_INSTALL\_PREFIX} variable overrides the default -location of \dirname{/usr/local/texlive}, leaving all else -unchanged---so with the above invocation, the main installation will go -to \dirname{/opt/texlive/2007}. - -In the usual Unix way, the final \Ucom{echo i} can be replaced by any -sequence of input commands via a here document, so any sequence of -commands can be scripted. - -Here are all the possible overrides: - -\begin{ttdescription} -\item [TEXLIVE\_INSTALL\_PREFIX] - Override \dirname{/usr/local/texlive}. -\item [TEXLIVE\_INSTALL\_TEXDIR] - Override \dirname{\$TEXLIVE_INSTALL_PREFIX}/2007. -\item [TEXLIVE\_INSTALL\_TEXMFLOCAL] - Override \dirname{\$TEXLIVE_INSTALL_PREFIX/texmf-var}. -\item [TEXLIVE\_INSTALL\_TEXMFSYSVAR] - Override \dirname{\$TEXLIVE_INSTALL_TEXDIR/texmf-var}. -\item [TEXLIVE\_INSTALL\_TEXMFHOME] - Override \dirname{\$HOME/texmf}. -\end{ttdescription} - -It would be better to support a standard \acro{GNU}-style -\filename{configure} with options, instead of these environment -variables. Volunteers are welcome! - - -% -\subsection{Installing individual packages to disk} - -You can add individual packages or collections from the current -distribution to an existing non-\TL{} setup, or an earlier -\TL{} installation. - -\startinst - -Run the installation script \filename{install-pkg.sh} (not -\filename{install-tl.sh}, which is intended for complete installations -only): -\begin{alltt} -> \Ucom{sh install-pkg.sh \var{options}} -\end{alltt} - -The first set of options controls what gets read: - -\begin{ttdescription} -\item [-{}-package=\var{pkgname}] The individual package to work on. - -\item [-{}-collection=\var{colname}] The individual collection to work on. - -\item [-{}-nodoc] Exclude documentation files from the operation. - -\item [-{}-nosrc] Exclude source files from the operation. - -\item [-{}-cddir=\var{dir}] Source directory to read from; defaults -to the current directory. If you followed the instructions above, that -will be the distribution directory, and won't need to be changed. - -\item [-{}-listdir=\var{dir}] The so-called `lists' directory within -\var{cddir} from which to read the package information. The only -reason to change the default is if you're making changes to \TL{} -yourself. - -\end{ttdescription} - -What actually happens is controlled by the following options. If -neither of these are specified, the default action is to install the -selected files. The main destination tree is found by expanding -\envname{\$TEXMFMAIN} with \cmdname{kpsewhich}. You can override it by -setting either the environment variable \envname{TEXMFMAIN} or -\envname{TEXMF}. - -\begin{ttdescription} -\item [-{}-listonly] List the files that would be installed, but don't -actually install anything. - -\item [-{}-archive=\var{tarfile}] Instead of installing the files into -the \TeX{} system, make a \cmdname{tar} archive. - -\end{ttdescription} - -Additional options: - -\begin{ttdescription} - -\item [-{}-config] After installation, run \code{texconfig init}. - -\item [-{}-nohash] After installation, don't run \cmdname{mktexlsr} to -rebuild the filename database. - -\item [-{}-verbose] Give more information as the script runs. - -\end{ttdescription} - -Here are some usage examples: - -\begin{enumerate} - -\item To see the files in the package \pkgname{fancyhdr} without -installing it: - -\begin{alltt} -\ifSingleColumn> \Ucom{sh install-pkg.sh --package=fancyhdr --listonly} -\else> \Ucom{sh install-pkg.sh --package=fancyhdr \bs} -> \Ucom{--listonly} -\fi{} -texmf/doc/latex/fancyhdr/README -texmf/doc/latex/fancyhdr/fancyhdr.pdf -... -\end{alltt} - -\item Install the \LaTeX{} package \pkgname{natbib}: -\begin{alltt} -> \Ucom{sh install-pkg.sh --package=natbib} -\end{alltt} - -\item Install the \LaTeX{} package \pkgname{alg} without source files or -documentation: -\begin{alltt} -\ifSingleColumn> \Ucom{sh install-pkg.sh --package=alg --nosrc --nodoc} -\else> \Ucom{sh install-pkg.sh -{}-package=alg \bs} -> \Ucom{-{}-nosrc -{}-nodoc} -\fi\end{alltt} - -\item Install all the packages in the collection of additional -plain \TeX\ macros: -\begin{alltt} -> \Ucom{sh install-pkg.sh --collection=tex-plainextra} -\end{alltt} - -\item Write all files in the \pkgname{pstricks} package to a -\cmdname{tar} file in \path|/tmp|: -\begin{alltt} -\ifSingleColumn> \Ucom{sh install-pkg.sh --package=pstricks --archive=/tmp/pstricks.tar} -\else -> \Ucom{sh install-pkg.sh -{}-package=pstricks \bs} -> \Ucom{-{}-archive=/tmp/pstricks.tar} -\fi\end{alltt} - -\end{enumerate} - -\textifindoubt - - -% -\section{Post-installation} -\label{sec:postinstall} - -After the main installation is done, for any operating system, the -remaining steps are to configure the system for your local needs, and -perform some basic tests. - -Another sort of post-installation is to acquire packages, fonts, or -programs that were not included in \TL{}. The basic idea is to -install such additions in the \envname{TEXMFLOCAL} tree (if you -installed to disk), or \envname{TEXMFSYSVAR} (if you are running live). -See the ``Installation directories'' option on \p.\pageref{text:instdir}. - -Unfortunately, the details can and do vary widely, and so we do not attempt to -address them here. Here are some external links to descriptions: -\begin{itemize*} -\item -\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instpackages} -\item -\url{http://www.ctan.org/installationadvice} -\item -\url{http://www.ctan.org/tex-archive/info/beginlatex/html/chapter5.html#pkginst} -\item -\url{http://www.ctan.org/tex-archive/info/Type1fonts} for -installation information for fonts in particular. -\end{itemize*} - - -\subsection{The \protect\cmdname{texconfig} program} -\label{sec:texconfig} - -At any time after installation, you can and should use the program -\cmdname{texconfig} to configure the system to fit your local needs. It -is installed in the architecture-specific subdirectory -\texttt{TEXDIR/bin/\var{arch}} along with everything else. - -If you run it without arguments, it will enter full-screen mode and -allow you to view and change options interactively. - -You can also run it with various command-line options. Here are some of -the most common (\TL{} is configured for the A4 paper size by default): - -\begin{ttdescription} - -\item [texconfig paper letter] Set default paper size for -various programs and drivers (\cmdname{pdftex}, \cmdname{dvips}, -\cmdname{dvipdfm}, \cmdname{xdvi}) to be \acro{US} letter. The other -allowable size is \optname{a4}, which is the default. - -\item [texconfig rehash] Update all the \TeX{} ``filename databases'', -after adding or removing files. - -\item [texconfig faq] Show the \teTeX{} \acro{FAQ}. -(See also the main \TeX{} \acro{FAQ} in \OnCD{texmf-doc/doc/english/FAQ-en}.) - -\item [texconfig help] Output help information for \cmdname{texconfig}. - -\end{ttdescription} - -Of course, \cmdname{texconfig} can only support changing a few of the -many options and configuration parameters in a \TeX{} system. The main -configuration file for the base \Webc{} programs is named -\filename{texmf.cnf}. You can find its location by running -\samp{kpsewhich texmf.cnf}; it contains many comments explaining the -default settings and useful alternatives. - -\cmdname{texconfig} alters files in a user-specific directory, as in -\dirname{$HOME/.texlive2007}. If you install \TeX\ just for yourself, -that is unlikely to make a difference. But if you install \TeX\ on a -multi-user system, you will want to change the configuration for the -whole system. In this case, run \cmdname{texconfig-sys} instead of -\cmdname{texconfig}. - -Likewise, the \cmdname{updmap} and \cmdname{fmtutil} scripts were -changed, to work under \dirname{$HOME/.texliveYYYY}. To alter system -directories, use \cmdname{updmap-sys} and \cmdname{fmtutil-sys}. - -In particular, for multi-user systems, you will probably want to -pregenerate the standard formats with \texttt{fmtutil-sys --missing}. -Otherwise, each user will end up with their own formats. - -Also, if you have a personally-modified copy of \filename{fmtutil.cnf} -or \filename{updmap.cfg}, instead of using the ones generated by -installation, they must be installed in the tree referenced by the -variable \envname{TEXMFSYSCONFIG}. - -The variables specifying the directories altered by these commands are -listed in section~\ref{sec:texmftrees}, \p.\pageref{sec:texmftrees}. -You can see the actual directories by running \texttt{texconfig conf}, -and you can change them by editing \filename{texmf.cnf}. - - -\subsection{Testing the installation} -\label{sec:test-install} - -After installing \TL{} as best you can, you naturally want to test -it out, so you can start creating beautiful documents and\slash or fonts. - -This section gives some basic procedures for testing that the new system -is functional. We give Unix commands; under \MacOSX{} and Windows, -you're more likely to run the tests through a graphical interface, but -the principles are the same. - -\begin{enumerate} - -\item Make sure that you can run the \cmdname{tex} program in the first -place: - -\begin{alltt} -> \Ucom{tex -{}-version} -TeX 3.141592 (Web2C 7.5.5) -kpathsea version 3.5.5 -... -\end{alltt} -If this comes back with `command not found' instead of version and -copyright information, most likely you don't have the correct -\dirname{bin} subdirectory in your \envname{PATH}. See -the environment-setting information on \p.\pageref{text:path}. - -\item Process a basic \LaTeX{} file: -\begin{alltt} -> \Ucom{latex sample2e.tex} -This is pdfeTeXk, Version 3.141592... -... -Output written on sample2e.dvi (3 pages, 7496 bytes). -Transcript written on sample2e.log. -\end{alltt} -If this fails to find \filename{sample2e.tex} or other files, perhaps -you have interference from old environment variables or configuration -files. For a deep analysis, you can always ask \TeX{} to report on -exactly what it is searching for, and finding; see ``Debugging actions'' -on page~\pageref{Debugging}. - -\item Preview the result online: -\begin{alltt} -> \Ucom{xdvi sample2e.dvi} -\end{alltt} -(Under Windows, the analogous command is \cmdname{dviout}.) You should -see a new window with a nice document explaining some of the basics of -\LaTeX{}. (Well worth reading, by the way if you're new to the system.) -You do have to be running under X for \cmdname{xdvi} to work; if you're -not, or your \envname{DISPLAY} environment variable is set incorrectly, -you'll get an error \samp{Can't open display}. - -\item Create a \PS{} file for printing or display: -\begin{alltt} -> \Ucom{dvips sample2e.dvi -o sample2e.ps} -\end{alltt} - -\item Create a \acro{PDF} file instead of \dvi{}; this processes the -\filename{.tex} file and writes \acro{PDF} directly: -\begin{alltt} -> \Ucom{pdflatex sample2e.tex} -\end{alltt} - -\item Preview the \acro{PDF} file: -\begin{alltt} -> \Ucom{gv sample2e.pdf} -\textrm{or:} -> \Ucom{xpdf sample2e.pdf} -\end{alltt} -Unfortunately neither \cmdname{gv} nor \cmdname{xpdf} are currently -included in \TL{}, so you must install them separately. See -\url{http://www.gnu.org/software/gv} and -\url{http://www.foolabs.com/xpdf}, respectively. - -\item Other standard test files you may find useful: - -\begin{ttdescription} -\item [small2e.tex] A simpler document than \filename{sample2e}, to -reduce the input size if you're having troubles. -\item [testpage.tex] Test if your printer introduces any offsets. -\item [nfssfont.tex] For printing font tables and tests. -\item [testfont.tex] Also for font tables, but using plain \TeX{}. -\item [story.tex] The most canonical (plain) \TeX{} test file of all. -You must type \samp{\bs bye} to the \code{*} prompt after \samp{tex -story.tex}. -\end{ttdescription} -You can process these in the same way as we did with -\filename{sample2e.tex}. - -\end{enumerate} - -If you are new to \TeX{}, or otherwise need help with actually -constructing \TeX{} or \LaTeX{} documents, please visit -\url{http://tug.org/begin.html} for some introductory resources. - - -\section{\MacOSX{} installation} -\label{sec:mac-install} - -The recommended way to install \TeX\ on \MacOSX\ is from the Mac\TeX\ -distribution, new in 2005. This is provided on the \pkgname{live} -\DVD{} in the top-level \dirname{mactex/} directory. It contains its -own (native) installer for a full \TeX\ distribution, based on a -combination of te\TeX\ and \TL, along with many additional applications -and documentation. The project web page is \url{http://tug.org/mactex}. - -If you prefer, installation of \TeX{} under \MacOSX{} can also be done -directly from \TL, using the \filename{install*} scripts, as follows. - -In order to run the installation scripts under \MacOSX, you need to have -the \cmdname{bash} shell installed. If you are running \MacOSX~10.2 -or later, you have \cmdname{bash}, and can proceed. If you're running -an earlier \MacOSX{} version, however, the default shell is -\cmdname{zsh}, which won't work; you'll need to get \cmdname{bash} from -the Internet, or more likely upgrade your system. - -Once you have \cmdname{bash}, the Unix installation documentation in the -previous section can be followed. See section~\ref{sec:unix-install} on -\p.\pageref{sec:unix-install}; \MacOSX-specific notes are included there -where needed. - -\section{Windows installation} -\label{sec:win-install} - -In this release of \TL{}, happily, the distribution once -again has a native Windows installer, named \cmdname{tlpmgui.exe}. (See -section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}, for an -explanation of the different distributions.) - -\cmdname{tlpmgui} has essentially the same options as the Unix -installer, only done through a GUI interface: selecting schemes, -individual collections, installation directories, and so on. -Section~\ref{sec:unix-install-disk} on -\p.\pageref{sec:unix-install-disk} describes the basic elements. It -also allows some post-installation activities such as adding/removing -packages, updating the filename database and building formats. -Moreover, \cmdname{tlpmgui} can setup the system for running -programs directly from the \DVD. - -For those who like to look underneath the hood, \cmdname{tlpmgui} uses -as its ``engine'' a command-line Windows program named \cmdname{tlpm}. - -The Windows \TeX{} system included in \TL{} is based on new binaries -borrowed from the \acro{W32TEX} distribution, kindly provided by Akira Kakuto. -It also includes some older (but still working) tools made by Fabrice -Popineau, and also a new \texttt{dvi} previewer, \textsf{dviout} by -Toshio Oshima. - -\TL{} can be installed on systems running Windows 98, \acro{ME}, -\acro{NT}, \acro{2K} or \acro{XP}. Older versions of Windows (3.1x) -and \acro{MS-DOS} are not supported. - -\textbf{Warning:} Win9.x users must ensure they have enough environment - space before undertaking installation. The \cmdname{tlpmgui.exe} - program won't change the environment size for them. A few environment - variables will be created and it is possible you run out of - environment space. Add \texttt{SHELL=COMMAND.COM /E:4096 /P} in the - config.sys file in order to increase your environment size. - -\subsection{Installing \protect\TeX\protect\ Live to disk} - -After inserting the \TL{} \acro{CD} into the \acro{CD} drive, autostart should -activate \cmdname{tlpmgui}. If it does not, click \guiseq{Start\arw Run}, -then type \verb|:\setuptl\tplmgui.exe| (or -\verb|:\texlive\setuptl\tplmgui.exe| if you are -installing from the \TeX\ Collection \acro{DVD}), where \verb|| -is the drive letter with the \TeX\ Live \acro{CD} (or TeX Collection -\acro{DVD}), and then click \acro{OK}. - -The installation window titled \guiseq{TeX Live installation and maintenance -utility} should open. It contains the following sections: \guiseq{Main -customization}, \guiseq{Install}, \guiseq{Select a scheme}, \guiseq{Select -systems}, \guiseq{Directories} and \guiseq{Options}. - -By default, \cmdname{tlpmgui} tries to detect if \TeX{} is already -installed and depending on the result starts either in fresh -installation or maintenance mode. If you have \TeX{} already installed -but want to install the new version nevertheless, you can use -\texttt{tlpmgui~--install-mode} to force installation mode; but you -should know what you are doing, as the new \TL{} installation will -override the environment variables and other settings of the existing -installation; reverting to your old installation is not automatically -supported. - -Diagnostic information is collected by \cmdname{tlpmgui} in a log file -which is deleted at the end of the run, along with any other temporary -files. Invoking with \texttt{--debug} displays the names and contents -of all \cmdname{tlpmgui} temporary files in a separate window. - -In the \guiseq{Directories} section the installation drive (directory) -next to the \guiseq{CD/DVD} button should be displayed (e.g., -\texttt{F:/} or \texttt{F:/texlive/} for the \acro{DVD}), but if it is not, -then click the \guiseq{CD/DVD} button and select the \acro{CD/DVD} -drive, with the \TL{} \acro{CD} (or \TeX\ Collection \acro{DVD}). - -The directory in which you wish to install the software can be set by -clicking the \guiseq{TLroot} button. This directory will be set as -\path|TLroot| environment variable for later usage. - -In the \guiseq{Select a scheme} section the desired \TL{} installation scheme -should be chosen by clicking the radio button labelled with the installation -scheme name (e.g., \guiseq{scheme-gust}). Each scheme is accompanied by an -\guiseq{Info} button which, when clicked, displays a short description of the -relevant scheme. - -A scheme is a large set of files targeted at some kind of usage. There are -generic schemes for basic, medium and full installations. The remaining ones -are either targeted at certain LUGs (i.e., what GUST or GUTenberg propose -for their members) or application targeted (e.g., for XML and \TeX{} -cooperation). A preselected scheme can be refined. This is done in the -\guiseq{Main customization} section by choosing additional collections from -\guiseq{Standard collections} or \guiseq{Language collections}. For example, -by clicking the \guiseq{Select} button labelled \guiseq{Standard -collections}, additional collections like Metapost, Omega or documentation -in different languages can be selected. - -\guiseq{Wintools} collection is selected by default as it contains many small -programs, usually absent in Windows, which can be handy, like graphics -converters: \cmdname{sam2p}, \cmdname{jpeg2ps}, \cmdname{tiff2png}; -(de)compression programs: \cmdname{bzip2}, \cmdname{gzip}, \cmdname{unzip}, -and \cmdname{wget} which is needed for \cmdname{getnonfreefonts} (new) -utility. - -Next, clicking the \guiseq{Select} button labelled \guiseq{Language -Collections} in the \guiseq{Main customization} section opens the -\guiseq{Language collections} window in which the installation language can -be chosen by ticking the box next to the language. - -Next, click the \guiseq{Install} button in the \guiseq{Install} section to -start the installation proper process. - -\textbf{Note:} The \guiseq{Perl} and \guiseq{Ghostscript} are installed only -on demand. They should be installed unless they are already installed and you -really know what you are doing. Both programs are required by many important -tools. The \verb|PERL5LIB| and \verb|GS_LIB| environment variables will be -set too, as well the path to Ghostscript binaries will be added to the -\verb|PATH| variable. - -The \TL{} system needs some post-processing steps (format files -generation, ls-R databases generation, environment variables, etc.). All -these operations are done there, some of them can be lengthy. So please wait -until you see a statement about the successfully finished installation. - -The shortcut for \cmdname{tlpmgui} (and also \cmdname{dviout}, if installed) -will be added to the menu \guiseq{Start\arw Programs\arw TeXLive2007}. - -If it is needed (Win9x/WinME), you will be asked to reboot your computer. - -\subsection{Support packages for Windows} -\label{sec:win-xemtex} - -To be complete, a \TL installation needs support packages that are not -commonly found on a Windows machine. Many scripts are written using the Perl -language. Some important tools require the Ghostscript \PS{} interpreter to -render or to convert files. A graphic file toolbox is also needed in some -cases. Last but not least, a \TeX-oriented editor makes it easy to type in -your \TeX{} files. - -All these tools are quite easy to find for Windows, but in order to try to -make your life even easier, we have put such a set of tools on \TL: -\begin{itemize*} -\item GNU \cmdname{Ghostscript} 8.54 -\item a minimal \cmdname{Perl} 5.8, sufficient to run all the \TL{} - Perl scripts. -\item win-tools is a set of small programs (bzip2, gzip, jpeg2ps - and tiff2png) -%\item a subset of \cmdname{ImageMagick} 5.5.6 -%\item the \cmdname{ISpell} checker -%\item \cmdname{XEmacs} 21.5.14 with a selection of packages to support -%\TeX{} typesetting. -\end{itemize*} - -Perl and Ghostscript are installed upon request; you may explicitly -deselect them during installation if you already have them. - -If you don't want to install this bundle, then you are on your own to -install the required tools to complete your \TL{} system. Here is a -list of places to get those tools: - -\begin{description} -\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} -\item[Perl] \url{http://www.activestate.com/} (but you might need some - supplementary packages from CPAN: \url{http://www.cpan.org/}) -\item[ImageMagick] \url{http://www.imagemagick.com} -\item[NetPBM] alternatively, you could use NetPBM instead of ImageMagick to - process or convert your graphic files. NetPBM home page is - \url{http://netpbm.sourceforge.net/} -\item[\TeX-oriented editors] There is a wide choice, and it is a matter of the - user's taste. Here is a selection: - \begin{itemize*} - \item \cmdname{GNU Emacs} is available natively under Windows, see - \url{http://www.gnu.org/software/emacs/windows/ntemacs.html} - \item \cmdname{Emacs} with AucTeX is available natively under Windows, see - \url{ftp://alpha.gnu.org/gnu/auctex} - \item \cmdname{WinShell} is available on \TL in the \path|support| - directory, see \url{http://www.winshell.de} - \item \cmdname{WinEdt} is shareware available from \url{http://www.winedt.com} - \item \cmdname{Vim} is available from \url{http://www.vim.org} - \item TeXnicCenter is free software, available from - \url{http://www.toolscenter.org} and in the proTeXt distribution. - \item \cmdname{LEd} is available from \url{http://www.ctan.org/support/LEd} - \item \cmdname{SciTE} is available from \url{http://www.scintilla.org/SciTE.html} - \end{itemize*} -\end{description} - -You might want to install other tools that are not free\footnote{Not -free, that is, in the sense of freedom to modify and redistribute, -following free software guidelines. This does not mean you can't acquire -them for no money.} and therefore not included on \TL{}, such as -\cmdname{GSView}, the \cmdname{Ghostscript} companion to more -conveniently view PS/PDF files. \cmdname{GSView} is available from -\url{http://www.cs.wisc.edu/~ghost/gsview/} or any \acro{CTAN} site. - -\section{Maintenance of the installation in Windows} - -If you have \TeX\ Live installed, you can use \cmdname{tlpmgui} again -for modifying and maintaining your installation. - -\subsection{Adding/removing packages} - -As the \cmdname{tlpmgui} shortcut is available in the \guiseq{Start\arw -Programs\arw TeXLive2007} menu, start it from here. The maintenance window -titled \guiseq{TeX Live installation and maintenance utility} shows. It -contains several tabs: \guiseq{Add Packages}, \guiseq{Remove packages}, -\guiseq{Manage installation}, \guiseq{Remove installation}. - -Click the tab labelled \guiseq{Add packages} or \guiseq{Remove packages} -to enter the relevant functionality and then: - -\begin{itemize} -\item In the first tab select the proper \CD{} drive (or \DVD with - \texttt{texlive} directory) by pressing the \guiseq{CD/DVD} button. -\item Click the \guiseq{Search} button in the \guiseq{Buttons} section to -display or refresh in the \guiseq{Select packages to\dots} section the -list of packages to install or remove. - -When adding packages, the list of installed packages is compared to the list -of packages available from your \CD/\DVD. Only packages not already installed are -displayed. It is up to you to select which packages you want to -install. - -When removing individual packages, only a list of installed packages -will be displayed. - -Please note that for both \guiseq{Add packages} and \guiseq{Remove packages} -the collections are listed first. - -\item Select a package by clicking on the name of the package. Clicking the -\guiseq{Info} button in the \guiseq{Buttons} section displays a short -description of the selected package in the window located in the \guiseq{Info -about the selected item} section. To select several packages at once hold -down one of the Ctrl or Shift keys at your keyboard while holding down the -left mouse button or drag the mouse pointer while holding down the left mouse -button. - -\item Click the \guiseq{Install} or \guiseq{Remove} button in the -\guiseq{Buttons} section to perform the appropriate action. -\end{itemize} - -\subsection{Configuring and other management tasks} - -The functions available in the tab labelled \guiseq{Manage the installation} -are helpful in performing actions needed when you want to add support for a -language which was not selected during the installation, or add/regenerate a -format which was not selected during the installation or was modified after -the installation. - -The following actions can be performed: - -\begin{itemize} -\item Refresh the \filename{ls-R} database -\item Create formats (All or Missing) -\item Edit \filename{language.dat} -\item Edit \filename{fmtutil.cnf} -\item Edit \filename{updmap.cfg} -\end{itemize} - -Note: you can close the Edit\dots{} window with the \guiseq{Cancel} or -\guiseq{Done} button; the latter will start rebuilding the format files -(or the fontmap files if you have edited \filename{updmap.cfg}), followed by a -\filename{ls-R} database files refresh. - -For more information about the configuration see section~\ref{sec:persconf}, -\p.\pageref{sec:persconf}. - -\subsection{Uninstalling \protect\TL{}} - -The tab labelled \guiseq{Remove the TeX Live installation} opens a window -which contains functionality not worth describing and we do not know who would -need it and what it is for\dots :-) - -Anyway, if you have the \path|texmf-local| directory for your local additions, -the removal procedure will not wipe it out or delete things in it. However, -it will be done only if you select it explicitly. The \path|setuptl| -directory containing \cmdname{tlpmgui} and related files will not be deleted. -You will have to do some manual cleanup to actually remove them. - -\subsection{Adding your own packages to the installation} - -First, whatever changes you make, \textbf{do not forget to rebuild the ls-R -database files}. Otherwise, your new files will not be found. You can do this -either via the \cmdname{tlpmgui} run and selection of the appropriate action -from the \guiseq{Manage the installation} tab, or manually running the -\file{mktexlsr} command. - -If you want to add files that are not provided by the \TL{} distribution, -it is recommended to put them in the \path|$TEXMFLOCAL| directory. This -way, you will be safe against upgrades of the \TL{} software. - -The directory pointed to by \path|$TEXMFLOCAL| is initially empty. If, -for example, you want to add the support file for the Maple symbolic -computation program, you will have to put the style files in:\\ -\path|c:\TeXLive2007\texmf-local\tex\latex\maple\|\\ and the -documentation files in:\\ \path|c:\TeXLive2007\texmf-local\doc\latex\maple\| - -\subsection{Running \texttt{tlmp.exe} from the command line} -The \cmdname{tlpm.exe} program which is used as engine by \cmdname{tlpmgui} -has a number of other useful options. You can get the list by running: -\begin{verbatim} -tlpm --help -\end{verbatim} - -More information and examples of use can be found in \path|tlpm.readme|. - -\subsection{Network installation} - -\KPS{} knows about UNC names, so you can use them to get your TEXMF -tree from the network. But there is better than this. -All the support files and configuration files, everything except the files in the -\path|bin/win32| are shareable with a \teTeX{} or Unix \TL{} installation. That means -you can use Samba either to mount from an NT server to a Unix -workstation or the converse. Several strategies are possible: -\begin{itemize} -\item Put everything on the server. Just add each set of files for the OS and -architecture you want to use in the \path|bin| directory. That means -for example \path|bin/win32| and \path|bin/i386-linux|. Next configure -your main variables. You can use UNC names to -point to the right directories under Win32. -\item Install a local copy for the binaries and format files. In this - case, assign \path|$TEXMFMAIN| to the main \path|texmf| tree that - will be accessed remotely. Set \path|$TEXMFVAR| to be a local - directory which will hold local configuration files and on-the-fly - generated files. -\end{itemize} - -\subsection{What's different in Windows?} - -The Windows version of \Webc{} has some specific features that should be -pointed out. - -\begin{description} -\item[\cmdname{kpsecheck}] This command provides some options that did - not fit well into \cmdname{kpsewhich}. It will allow you to list all - the files that occur multiple times across your texmf trees. This - could be handy, but most of the time you will also get unwanted - output (like dozens of \path|README| files). It is noticeable - that all these files result in clashes inside the \KPS{}-hashing - mechanism; fortunately, \KPS{} never looks for these files. For - this reason, you can combine the \path|-multiple-occurrences| with 2 - other options for including or excluding any filename that match - some pattern (you can request for several patterns). - - The \cmdname{kpsecheck} command will also report the status of shared - memory: in use or not used. That might be useful to know because if - the status reported is \samp{in use}, that means one or several - processes are working, and the effect of any \cmdname{mktexlsr} - command will be delayed until the next time where no \KPS{} linked - process will be running. - - Last, this same command will report about the location it thinks - Ghostscript can be found. Under Win32, for many programs, it is - easier to use the Ghostscript dll, and find it by using the - Ghostscript registry key than to change the \path|PATH|, which has a - limited length anyway. -\item[\Webc{}] The engines have one more option than in Unix \Webc: - \begin{itemize} - \item \path|-proctimes| print statistics about the job run - time. It is to be noted that Win9x not being a true multitasking - operating system, it has no reliable timer for short periods, so - the value printed is an approximation. Under NT/2K/XP, the result - is quite accurate with user time and system time values allocated - for this run. For Unix - users: the \path|time| command is not usually available to Windows - users. - \end{itemize} -\end{description} - -\subsection{Personal configurations} -\label{sec:persconf} - -\subsubsection{Dvips} - -The configuration file for dvips can be found in\\ -\verb+C:\TeXLive2007\texmf-var\dvips\config\config.ps+\\ -You may open it with any editor - %(\cmdname{WinShell} will do fine) - and change some parameters: - -\begin{description} -\item [fonts] you can change the default printer \MF{} mode or printer - resolution in case \cmdname{dvips} needs to generate PK fonts. By default it - is configured to use Type~1 versions of the CM fonts, so it should - not call \cmdname{mktexpk} too often; -\item[printer] you can tell dvips where you want to print by default. If - the \optname{o} option is not followed by a printer name, then a - \file{.ps} \PS{} file is written. You can give dvips a printer - name such as: -\begin{verbatim} -o lpt1: -% o | lpr -S server -P myprinter -% o \\server\myprinter -\end{verbatim} -\item[paper] Next, you might want - to change the paper size from European (A4) to US letter - by making the US letter the first paper size mentioned in the file. - Scroll to the group of lines beginning with \code{@}. Move - the appropriate lines so that this section begins with the lines:\\ -\hspace*{1em} @ letterSize 8.5in 11in\\ -\hspace*{1em} @ letter 8.5in 11in\\ -\hspace*{1em} @+ \%\%BeginPaperSize: Letter\\ -\hspace*{1em} @+ letter\\ -\hspace*{1em} @+ \%\%EndPaperSize -\end{description} - -The current \TL{} distribution implements the procedure of making always -up-to-date fontmaps files for Dvips and Pdftex. This is done by the -\cmdname{updmap} program during installation. -If you add new font packages using the installation program or by hand, -edit the file \verb+updmap.cfg+ in \path|$TEXMFVAR/web2c|. - -\subsubsection{PdfTeX} - -If you use the program pdf{}latex to write \acro{PDF} format directly, -and you are using \acro{US} letter-size paper, edit the file -\verb+C:\TeXLive2007\texmf-var\tex\generic\config\pdftexconfig.tex+ and -change \samp{\bs pdfpagewidth} and \samp{\bs pdfpageheight}. These entries -should read: -\begin{alltt} -\bs{}pdfpagewidth=8.5 true in -\bs{}pdfpageheight=11 true in -\end{alltt} -Save the file and exit the editor. - -\subsubsection{Xe\TeX} -Xe\TeX{} for Windows is linked statically with fontconfig 2.4.2. -A configuration file for fontconfig is \verb+fonts.conf+. For details, -see the file \verb+fonts.conf+ itself which is in a directory shown by -the command \texttt{kpsewhich --var-value=FONTCONFIG\_PATH}. - -\subsubsection{GSView} -GSView is now distributed under the Aladdin License, and therefore is no -longer included in \TL{}. - -You may want to change the page size to US letter size. If so, open -GSView from the \guiseq{Start} menu, and select \guiseq{Media\arw Letter}. - -Also, there are menu settings that are supposed to give you the most -readable screen image. On \guiseq{Media \arw Display Settings}, set both -\optname{Text Alpha} and \optname{Graphics Alpha} to 4~bits. - -Note that the installation process has set all \code{.ps} and -\code{.eps} files to automatically open with \cmdname{GSView}. - -For printing instructions, see section~\ref{printing} below. - - -\subsection{Testing} - -For generic verification procedures, see section~\ref{sec:test-install} -(\p.\pageref{sec:test-install}). This section describes -Windows-specific tests. - -Open the file \verb+sample2e.tex+ in your editor (Xemacs, WinShell), -found in \path|C:\TeXLive2007\texmf-dist\tex\latex\base|. The \LaTeX\ source -should appear on the screen. Process it by clicking on the -\guiseq{Command\arw LaTeX} menu (XEmacs) or \LaTeX\ icon on the toolbar -(WinShell), then view it by clicking on the \guiseq{Command\arw View DVI} -menu (XEmacs) or Preview (dviout) icon (WinShell). - -At first, when you preview files with \cmdname{dviout}, it will create fonts -because screen fonts were not installed. After a while, you will have created -most of the fonts you use, and you will rarely see the font-creation window. - -\textbf{Hint for the future:} If a \LaTeX\ run stops because \LaTeX\ -cannot find a file, you can press Ctrl-z to quit. - - -\subsection{Printing} -\label{printing} - -It is possible to print from \cmdname{dviout}. In this case, printing -will be done using the Windows unified printer driver. By definition, it is -compatible with all printers. However, there is some drawback: it can -generate some huge spool files, and some (older) versions of Windows -just don't like them. The advantage is that you can use features like -embedding BMP or WMF images. You also need to make sure that the printer -parameters are correctly set, else you -will get scaled printing (printing at 600\dpi{} on a 300\dpi{} printer -will give you only one quadrant of your page). - -Printing is faster and more reliable if you run \cmdname{dvips} to make -a \filename{.ps} file and then print from \cmdname{GSView}. In -\cmdname{GSview}, select \guiseq{File\arw Print\ldots}. A \guiseq{Print} -window will appear. - -If you are using a \PS{} printer, \textit{be sure to select -\guiseq{\PS{} Printer}}. This is done in the \guiseq{Print Method} box -at the bottom left of the \guiseq{Print} window. You can then select any -of the printers that you have previously installed. If you fail to -check the box for \optname{\PS{} Printer}, printing will not work. - -If you will be using your own non-\PS{} printer, select -\guiseq{Ghostscript device} in the \guiseq{Print Method} box, then click -on the button to the right labelled \guiseq{djet500} and select your -printer type from the list that pops up. (In the older version of -\cmdname{GSView}, make sure \optname{\PS{} Printer} is \textit{not} -selected, then select your printer type from the \guiseq{Device} list.) - -\subsection{Tips and tricks for Win32} - -\subsubsection{Different flavors of Win32} - -What we call Win32 is not an operating system by itself. It is a large -set of functions (around 12,000 in the header files of the Microsoft -\acro{SDK}) that you can use to write programs for different operating -systems of the Windows family. - -Windows comes in different flavors: -\begin{itemize} -\item Win95, Win98 and Win\acro{ME}, which \emph{are not true multitasking, - multithreading} environments, but rather updated incarnations of - \acro{DOS}. This can be more or less proven by the fact that when - booting, the PC will load the \path|command.com| interpreter, and if - you stop the boot process at this point, you can ask for the current - (\acro{DOS}) version and it will answer something like \samp{MS-DOS - 7.0} (at least for the old versions of Win9x). -\item Windows \acro{NT}, which is a new operating system written from - scratch, capable of true multitasking behavior, and including many - high level features. -\item Windows 2000, based on \acro{NT}, with all the bells and - whistles of Win98. -\item Windows \acro{XP}, which comes with Personal and Pro flavors. This is - the last step in merging both lines of products (Win9x based and - \acro{NT} based). \acro{XP} is based on \acro{NT}. -\end{itemize} - -Win9x are able to run 32~bits programs and 16~bits programs -concurrently. But the operating system by itself is not entirely -written in 32~bits mode, and does not support memory protection: 16bits -applications can overwrite parts of the operating system memory! Some -parts of the system like the \acro{GDI} (Graphical Device Interface) -manage limited resources like bitmaps, fonts, pens and so on for the set -of all programs that run concurrently. All the bitmaps headers available -at the same time can't amount for more than 64kB. This explains the -performance tool and the fact that you can put your system on his knees -by making intensive use of graphic objects for example. - -NT, 2K and XP do not suffer from these limitations, and neither from -other Win9x limitations. They are true multitasking environments, with -protected memory. They are much more responsive than Win9x because -of better memory management, better file system and so on. - -\subsubsection{Command line prompt} - -You may wonder, ``Why would I need to use a command line prompt when -I have Windows?'' - -Good question! The problem is of very general nature. Not all operations -can be done easily using only a \acro{GUI}. Command line gives you -programming power\Dash assuming a clever command interpreter. - -But the problem here is more fundamental: \TeX{} is \emph{a batch} -tool. Not an interactive one. \TeX{} needs to compute the best -layout for each page, resolve cross-references and so on. This can be -done only by a global processing of the document. It is not (yet) a -task that can be done interactively. - -This means that you should use \TeX{} from a command line. In fact the -situation is not so bad. There is an advantage to write command line -tools for complex processing: they are better debugged, because they are -independent of any \acro{GUI} problems, and \acro{GUI} tools can be -designed to interface to the command line tools. This is the case for -\TeX{}, where you will mostly interact with it through a \acro{GUI} text -editor. - -However, you may need to use the command line prompt in a number of -situations. One is when you are having difficulties and want to debug -your setup. - -\begin{description} - \item[Win9x] You can open a command line prompt by looking either for - the \acro{MS-DOS} icon in the \guiseq{Start\arw Programs} menu, - or by choosing \guiseq{Start\arw Run} menu typing in - \path|command.com| as the program name. - \item[NT, 2K, XP] You can open a command line prompt by looking for - \guiseq{Command Prompt} in the \guiseq{Start\arw Accessories} menu. - You can also choose \guiseq{Start\arw Run} and type in - \path|cmd.exe|, which is the name of the brand new command - interpreter for \acro{NT} (thus, it is untrue to call this a - \emph{DOS} box!). -\end{description} - -These locations may change across different Windows versions. - -\subsubsection{Path separators} - -The Win32 API understands both \path|/| and \path|\| characters as PATH -separators. But the command interpreters do not! So whenever a path name -is used programmatically, you can use both separators, and even mix them -up in the same path name. But on the command line, you must type -\path|\| as path separator. The reason is compatibility: the command -processor used \samp{/} to introduce arguments to commands. - -All this to say: do not be surprised to read path names written using -the Unix convention; Windows-\TL{} is a port of \Webc, and aims to be -compatible across platforms. For this reason, all the configuration files -that need to specify path names use the Unix convention. - -\subsubsection{File systems} -\label{sec:clusters} - -The worst feature of Win9x with regard to \TeX{} is probably the -so-called FAT file system. \TeX{} uses very many small files, with size -around 1--3kB. The \acro{FAT} file system is old, and predates by -decades the multi-gigabytes hard disks we have today. As a result, it -cannot manage efficiently the tens of thousands of \TeX{} files found in -\TL{}. The \acro{FAT} file system allocates a minimum of 32kB for -\emph{any} file on a huge partition. It means that \TeX{} will use much -more disk space than it actually needs. - -The other, more modern, file systems available, \acro{FAT32} and -\acro{NTFS}, do not have this drawback. They manage clusters of 4kB -only. (You can lower the limit to 512 bytes on \acro{NTFS}.) - -\subsubsection{How to add some directory to your PATH} - -There are pairs of variables and values which behave much like global -variables inside your programs. The set of those variables is called the -environment. Each program is initialized with a copy of the -environment when it is run. It can request and change the -value of any variable. The changes happen in the copy of the -environment, and is not at all propagated to the other running -programs. - -Your PATH is a special environment variable used to search for -programs you want to run. -There is a different procedure to change it for Win9x, WinME and NT/2K/XP: - -\begin{description} -\item[Windows 95/98] Edit your \path|autoexec.bat|. In this file should be a line - starting with \texttt{PATH=} and followed by a list of directories separated - by \path|;|. Please add the directory with the executables in this line. - After this, this line could look as follows: -\begin{verbatim} -PATH=c:\windows;c:\windows\system;c:\TeXLive2007\bin\win32 -\end{verbatim} -\item[Windows ME] You need to run the special program - \path|c:\windows\system\msconfig.exe| to be able to change any - environment variable. From this program, select the `Environment' - tab, and then add or modify the variable you want. You will be asked to reboot the - machine upon any change. -\item[Windows NT/2K/XP] - Click left on \guiseq{Start \arw Settings \arw Control Panel}. Now the - window with the control panel icons opens. Double click on System. The - System Properties window opens. Click on the tab \textsf{Environment} - or look for a button named \guiseq{Environment Variables} among the - dialog boxes. Now you can change the environment variables for your - user account. Note: There are also displayed the environment settings - for the system. Normally, you can't change the system variables - unless you have administrator rights on your machine. If you want to - change the \texttt{PATH} for all users, you will have to contact your - system administrator or be the system administrator yourself\Dash in - the latter case you should know what you are doing. - - If there is already a \texttt{PATH} setting for your user account, - left click on \texttt{PATH}. In the field \textsf{Variable} appears - \texttt{PATH} while the field Value shows the current setting of - \texttt{PATH} as a list of directories separated by \path|;|. Add - the directory where the executables are located (e.g. - \path|c:\TeXLive2007\bin\win32|). If there isn't a \texttt{PATH} variable - for your user account, simply click in the field Variable and type - in \texttt{PATH}, click in the field \textsf{Value} - and type in the directory with the executables. Important: Click on - the \textsf{Apply} button before clicking \textsf{Ok}, otherwise the - changes to \texttt{PATH} won't apply to your system. Be careful when - changing the environment settings. -\end{description} - -The best way to be sure that a variable has been properly set is to -open a console and type: -\begin{verbatim} -set VARIABLE -\end{verbatim} -which should return the corresponding value. - -\subsubsection{\TeX{} engines} - -If you have a look at the \Webc{} documentation, you will read that all -the various \TeX{} derived programs use the same base engine. For -example, \path|tex.exe| and \path|latex.exe| are exact copies of the -same program, but each one will use a different format file, based on -its calling name. - -Under Unix, this feature is implemented through \emph{symbolic -links}. It saves up a bit of disk space, because some engines are -used with many different format files. - -The Win32 API does not know about file links. So to save up almost -the same amount of memory, all the \TeX{} base engines have been put -in DLLs (\emph{Dynamic Linked Library}). This means that you will have -the following layout: -\begin{alltt} -2006-11-23 07:06 2 560 latex.exe -2007-01-06 23:54 1 073 664 pdftex.dll -2006-01-28 08:05 2 560 pdftex.exe -\end{alltt} -and the \path|latex.exe| file is nothing but a rough copy of -\path|pdftex.exe| using the same core \path|pdftex.dll|. -The same trick has been used for the \path|mktex*.exe| family of programs -which are linked to the \path|mktex.dll| library. - -In fact, a generic tool called \path|irun.exe| is provided to build the -equivalent of Unix hard links for executable files only under Win32. - -\subsection{In case of problems} -\label{sec:troubleshooting} - -\subsubsection{What to do if \texttt{latex} does not find your files?} - -\begin{itemize} - -\item \cmdname{kpsewhich} is the tool of choice to debug any -problem. However, \cmdname{kpsewhich} outputs debug information to -stderr, and the older Windows consoles do not know how to redirect -stderr to a file. (Windows NT and later do support redirections, but -the trick below will work for any console.) For diagnostic purposes you -can temporarily set an environment variable (in a \acro{DOS}/\acro{cmd} box): - -\begin{verbatim} -SET KPATHSEA_DEBUG_OUTPUT=err.log -\end{verbatim} -You can also set the debug level: -\begin{verbatim} -SET KPATHSEA_DEBUG=-1 -\end{verbatim} - -Similarly, to redirect stderr to stdout: -\begin{verbatim} -SET KPATHSEA_DEBUG_OUTPUT=con: -\end{verbatim} -This way you can capture both stdout and stderr in the same file. -\item Assuming the installation has been done in \path|c:/TeX|, check - the following values: \\ - {\small - \begin{tabular}{ll} - \path|kpsewhich -expand-path $SELFAUTOPARENT| & \path|c:/TeX| \\ - \path|kpsewhich -expand-path $TEXMF| & \path|c:/TeX/texmf....| \\ - \path|kpsewhich -expand-path $TEXMFCNF| & - \path|.;c:/TeX/texmf-var/web2c;| \\ - \path|kpsewhich -expand-var $TEXINPUTS| & \path|.;c:/TeX/texmf/tex//| - \end{tabular} -} -\item If you have other \TeX{}-related values already set in your - environment, please, remove them. They are overriding the ones in - texmf.cnf. -\item Check the values from:\\ -{\small - \begin{tabular}{ll} - \texttt{kpsewhich cmr10.tfm} & \path|c:/TeX/texmf-dist/fonts/tfm/public/cm/cmr10.tfm|\\ - \texttt{kpsewhich latex.fmt}& \path|c:/TeX/texmf-var/web2c/latex.fmt| - \end{tabular} -} -\item At this point, if everything is correct, \TeX{} and friends - should work. If it is not the case, you will need to play with - the \path|-debug=n| option from \path|kpsewhich|, and check back all - the values. Try to identify and report the problem. -\end{itemize} - -\subsubsection{What to do if your setup still does not work as expected?} - -Here are several questions to investigate: - -\begin{enumerate} -\item Is \file{tex.exe} in my \path|PATH|? - -\item Is the \path|TEXMFCNF| variable correctly set to -\path|c:/TeXLive2007/texmf-var/web2c| (default value)? - -\item Are there any errors in the log file generated by the -\file{tlmpgui.exe} program? -\file{tlmpgui.log} can be found in your -\file{TEMP} directory. You can find this by searching for the -string \samp{Error}. Hint: the log file can show some errors after -building all format files. Please do not panic: perhaps some formats -weren't already installed. - -\item Are there any relevant bug fixes at \url{http://tug.org/texlive/}? -(Unlikely, but it doesn't hurt to check.) - -\end{enumerate} - -The \TL{} software consists of hundreds of programs and tens of -thousands of files, all from varying sources. So it is quite difficult to -predict all possible causes for problems. Nevertheless, we will do our -best to help you. (See section~\ref{sec:help}, \p.\pageref{sec:help}.) - -% don't use \Webc so the \uppercase in the headline works. -\section{A user's guide to Web2C} - -\Webc{} is an integrated collection of \TeX-related programs: \TeX{} -itself, \MF{}, \MP, \BibTeX{}, etc. It is the heart of \TL{}. - -A bit of history: The original implementation was by Tomas Rokicki who, -in 1987, developed a first \TeX{}-to-C system based on change files -under Unix, which were primarily the original work of Howard Trickey and -Pavel Curtis. Tim Morgan became the maintainer of the system, and -during this period the name changed to Web-to-C\@. In 1990, Karl Berry -took over the work, assisted by dozens of additional contributors, and -in 1997 he handed the baton to Olaf Weber. - -The \Webc{} system runs on Unix, 32-bit Windows systems, \MacOSX{}, and -other operating systems. It uses Knuth's original sources for \TeX{} and -other basic programs written in \web{} and translates them into C source -code. The core \TeX{} programs are: - -\begin{cmddescription} -\item[bibtex] Maintaining bibliographies. -\item[dmp] \cmdname{troff} to MPX (\MP{} pictures). -\item[dvicopy] Expands virtual font references in \dvi{} files. -\item[dvitomp] \dvi{} to MPX (MetaPost pictures). -\item[dvitype] \dvi{} to human-readable text. -\item[gftodvi] Generic font proofsheets. -\item[gftopk] Generic to packed fonts. -\item[gftype] GF to human-readable text. -\item[makempx] \MP{} label typesetting. -\item[mf] Creating typeface families. -\item[mft] Prettyprinting \MF{} source. -\item[mpost] Creating technical diagrams. -\item[mpto] MetaPost label extraction. -\item[newer] Compare modification times. -\item[patgen] Creating hyphenation patterns. -\item[pktogf] Packed to generic fonts. -\item[pktype] PK to human-readable text. -\item[pltotf] Plain text property list to TFM. -\item[pooltype] Display \web{} pool files. -\item[tangle] \web{} to Pascal. -\item[tex] Typesetting. -\item[tftopl] TFM to plain text property list. -\item[vftovp] Virtual font to virtual property list. -\item[vptovf] Virtual property list to virtual font. -\item[weave] \web{} to \TeX. -\end{cmddescription} - -\noindent The precise functions and syntax of these programs are -described in the documentation of the individual packages and of \Webc{} -itself. However, knowing a few principles governing the whole family of -programs will help you take advantage of your \Webc{} installation. - -All programs honor these standard \acro{GNU} options: -\begin{ttdescription} -\item[-{}-help] print basic usage summary. -\item[-{}-verbose] print detailed progress report. -\item[-{}-version] print version information, then exit. -\end{ttdescription} - -For locating files the \Webc{} programs use the path searching library -\KPS{}. This library uses a combination of environment variables and a -configuration files to optimize searching the (huge) collection of -\TeX{} files. \Webc{} can look at more than one directory tree -simultaneously, which is useful in maintaining \TeX's standard -distribution and local extensions in two distinct trees. To speed up -file searches the root of each tree has a file \file{ls-R}, containing -an entry showing the name and relative pathname for all files under that -root. - -\subsection{Kpathsea path searching} - -Let us first describe the generic path searching mechanism of the \KPS{} -library. - -We call a \emph{search path} a colon- or semicolon\hyph sepa\-rated list -of \emph{path elements}, which are basically directory names. A -search path can come from (a combination of) many sources. To look up -a file \samp{my-file} along a path \samp{.:/dir}, \KPS{} checks each -element of the path in turn: first \file{./my-file}, then -\file{/dir/my-file}, returning the first match (or possibly all -matches). - -In order to adapt optimally to all operating systems' conventions, on -non-Unix systems \KPS{} can use filename separators different from -colon (\samp{:}) and slash (\samp{/}). - -To check a particular path element \var{p}, \KPS{} first checks if a -prebuilt database (see ``Filename data\-base'' on -page~\pageref{Filename-database}) applies to \var{p}, i.e., if the database -is in a directory that is a prefix of \var{p}. If so, the path -specification is matched against the contents of the database. - -If the database does not exist, or does not apply to this path -element, or contains no matches, the filesystem is searched (if this -was not forbidden by a specification starting with \samp{!!}\ and if -the file being searched for must exist). \KPS{} constructs the list -of directories that correspond to this path element, and then checks -in each for the file being sought. - -The ``file must exist'' condition comes into play with \samp{.vf} files and -input files read by \TeX's \cs{openin} command. Such files may not -exist (e.g., \file{cmr10.vf}), and so it would be wrong to search the -disk for them. Therefore, if you fail to update \file{ls-R} when you -install a new \samp{.vf} file, it will never be found. -Each path element is checked in turn: first the database, then the -disk. If a match is found, the search stops and the result is -returned. - -Although the simplest and most common path element is a directory -name, \KPS{} supports additional features in search paths: layered -default values, environment variable names, config file values, users' -home directories, and recursive subdirectory searching. Thus, we say -that \KPS{} \emph{expands} a path element, meaning it transforms all -the specifications into basic directory name or names. This is -described in the following sections in the same order as it takes -place. - -Note that if the filename being searched for is absolute or explicitly -relative, i.e., starts with \samp{/} or \samp{./} or \samp{../}, -\KPS{} simply checks if that file exists. - -\ifSingleColumn -\else -\begin{figure*} -\verbatiminput{examples/ex5.tex} -\setlength{\abovecaptionskip}{0pt} - \caption{An illustrative configuration file sample} - \label{fig:config-sample} -\end{figure*} -\fi - -\subsubsection{Path sources} -\label{Path-sources} - -A search path can come from many sources. In the order in which -\KPS{} uses them: - -\begin{enumerate} -\item - A user-set environment variable, for instance, \envname{TEXINPUTS}\@. - Environment variables with a period and a program name appended - override; e.g., if \samp{latex} is the name of the program being run, - then \envname{TEXINPUTS.latex} will override \envname{TEXINPUTS}. -\item - A program-specific configuration file, for exam\-ple, a line - \samp{S /a:/b} in \cmdname{dvips}'s \file{config.ps}. -\item A \KPS{} configuration file \file{texmf.cnf}, containing a line like - \samp{TEXINPUTS=/c:/d} (see below). -\item The compile-time default. -\end{enumerate} -\noindent You can see each of these values for a given -search path by using the debugging options (see ``Debugging actions'' -on page~\pageref{Debugging}). - -\subsubsection{Config files} - -\begingroup\tolerance=3500 -\KPS{} reads \emph{runtime configuration files} named \file{texmf.cnf} -for search path and other definitions. The search path used to look -for these files is named \envname{TEXMFCNF} (by default such a file lives -in the \file{texmf/web2c} subdirectory). \emph{All} -\file{texmf.cnf} files in the search path will be read and definitions -in earlier files override those in later files. Thus, with a search -path of \verb|.:$TEXMF|, values from \file{./texmf.cnf} override those -from \verb|$TEXMF/texmf.cnf|. -\endgroup - -\begin{itemize} -\item - Comments start with \code{\%} and continue to the end of the line. -\item - Blank lines are ignored. -\item - A \bs{} at the end of a line acts as a continuation character, - i.e., the next line is appended. Whitespace at the beginning of - continuation lines is not ignored. -\item - Each remaining line has the form: -\begin{alltt} - \var{variable}[.\var{progname}] [=] \var{value} -\end{alltt}% - where the \samp{=} and surrounding whitespace are optional. -\item - The \ttvar{variable} name may contain any character other - than whitespace, \samp{=}, or \samp{.}, but sticking to - \samp{A-Za-z\_} is safest. -\item - If \samp{.\var{progname}} is present, the definition only - applies if the program that is running is named - \texttt{\var{progname}} or \texttt{\var{progname}.exe}. This allows - different flavors of \TeX{} to have different search paths, for - example. -\item \var{value} may contain any characters except - \code{\%} and \samp{@}. The - \code{\$\var{var}.\var{prog}} feature is not available on the - right-hand side; instead, you must use an additional variable. A - \samp{;}\ in \var{value} is translated to \samp{:}\ if - running under Unix; this is useful to be able to have a single - \file{texmf.cnf} for Unix, \acro{MS-DOS} and Windows systems. -\item - All definitions are read before anything is expanded, so - variables can be referenced before they are defined. -\end{itemize} -A configuration file fragment illustrating most of these points is -\ifSingleColumn -shown below: - -\verbatiminput{examples/ex5.tex} -\else -shown in Figure~\ref{fig:config-sample}. -\fi - -\subsubsection{Path expansion} -\label{Path-expansion} - - -\KPS{} recognizes certain special characters and constructions in -search paths, similar to those available in Unix shells. As a -general example, the complex path, -\verb+~$USER/{foo,bar}//baz+, expands to all subdirectories under -directories \file{foo} and \file{bar} in \texttt{\$USER}'s home -directory that contain a directory or file \file{baz}. These -expansions are explained in the sections below. -%$ -\subsubsection{Default expansion} -\label{Default-expansion} - -\tolerance=2500 -If the highest-priority search path (see ``Path sources'' on -page~\pageref{Path-sources}) contains an \emph{extra colon} (i.e., -leading, trailing, or doubled), \KPS{} inserts at that point the -next-highest-prio\-rity search path that is defined. If that inserted -path has an extra colon, the same happens with the next highest. For -example, given an environment variable setting - -\tolerance=1500 - -\begin{alltt} -> \Ucom{setenv TEXINPUTS /home/karl:} -\end{alltt} -and a \code{TEXINPUTS} value from \file{texmf.cnf} of - -\begin{alltt} - .:\$TEXMF//tex -\end{alltt} -then the final value used for searching will be: - -\begin{alltt} - /home/karl:.:\$TEXMF//tex -\end{alltt} - -Since it would be useless to insert the default value in more than one -place, \KPS{} changes only one extra \samp{:}\ and leaves any others in -place. It checks first for a leading \samp{:}, then a trailing -\samp{:}, then a doubled \samp{:}. - -\subsubsection{Brace expansion} - -A useful feature is brace expansion, which means that, for instance, -\verb+v{a,b}w+ expands to \verb+vaw:vbw+. Nesting is allowed. -This is used to implement multiple \TeX{} hierarchies, by -assigning a brace list to \code{\$TEXMF}. -For example, in \file{texmf.cnf}, the following definition -(appproximately; there are actually even more trees) is made: -\begin{verbatim} - TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN} -\end{verbatim} -Using this you can then write something like -\begin{verbatim} - TEXINPUTS = .;$TEXMF/tex// -\end{verbatim} -%$ -which means that, after looking in the current directory, the -\code{\$TEXMFHOME/tex}, \code{\$TEXMFLOCAL/tex}, \code{\$TEXMFVAR/tex} -and \code{\$TEXMFMAIN/tex} trees \emph{only}) will be searched (the -last two use using \file{ls-R} data base files). It is a convenient -way for running two parallel \TeX{} structures, one ``frozen'' (on a -\CD, for instance) and the other being continuously updated with new -versions as they become available. By using the \code{\$TEXMF} -variable in all definitions, one is sure to always search the -up-to-date tree first. - -\subsubsection{Subdirectory expansion} -\label{Subdirectory-expansion} - -Two or more consecutive slashes in a path element following a directory -\var{d} is replaced by all subdirectories of \var{d}: first those -subdirectories directly under \var{d}, then the subsubdirectories under -those, and so on. At each level, the order in which the directories are -searched is \emph{unspecified}. - -If you specify any filename components after the \samp{//}, only -subdirectories with matching components are included. For example, -\samp{/a//b} expands into directories \file{/a/1/b}, \file{/a/2/b}, -\file{/a/1/1/b}, and so on, but not \file{/a/b/c} or \file{/a/1}. - -Multiple \samp{//} constructs in a path are possible, but -\samp{//} at the beginning of a path is ignored. - -\subsubsection{List of special characters and their meaning: a summary} - -The following list summarizes the special characters in \KPS{} -configuration files. - -% need a wider space for the item labels here. -\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} -\begin{ttdescription} -\item[\CODE{:}] Separator in path specification; at the beginning or - the end of a path it substitutes the default path expansion.\par -\item[\CODE{;}] Separator on non-Unix systems (acts like \code{:}). -\item[\CODE{\$}] Variable expansion. -\item[\CODE{\string~}] Represents the user's home directory. -\item[\CODE{\char`\{...\char`\}}] Brace expansion. -\item[\CODE{//}] Subdirectory expansion (can occur anywhere in - a path, except at its beginning). -\item[\CODE{\%}] Start of comment. -\item[\CODE{\bs}] Continuation character (allows multi-line entries). -\item[\CODE{!!}] Search \emph{only} database to locate file, \emph{do - not} search the disk. -\end{ttdescription} - - -\subsection{Filename databases} -\label{Filename-database} - -\KPS{} goes to some lengths to minimize disk accesses for searches. -Nevertheless, at installations with enough directories, searching each -possible directory for a given file can take an excessively long time -(this is especially true if many hundreds of font directories have to -be traversed.) Therefore, \KPS{} can use an externally-built plain text -``database'' file named \file{ls-R} that maps files to directories, -thus avoiding the need to exhaustively search the disk. - -A second database file \file{aliases} allows you to give additional -names to the files listed in \file{ls-R}. This can be helpful to -confirm to \acro{DOS} 8.3 filename conventions in source files. - -\subsubsection{The filename database} -\label{ls-R} - -As explained above, the name of the main filename database must be -\file{ls-R}. You can put one at the root of each \TeX{} hierarchy in -your installation that you wish to be searched (\code{\$TEXMF} by -default); most sites have only one hierarchy. \KPS{} looks for -\file{ls-R} files along the \code{TEXMFDBS} path. - -The recommended way to create and maintain \samp{ls-R} is to run the -\code{mktexlsr} script included with the distribution. It is invoked -by the various \samp{mktex}\dots\ scripts. In principle, this script -just runs the command -\begin{alltt} -cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R -\end{alltt} -presuming your system's \code{ls} produces the right output format -(\acro{GNU} \code{ls} is all right). To ensure that the database is -always up-to-date, it is easiest to rebuild it regularly via -\code{cron}, so that it is automatically updated when the installed -files change, such as after installing or updating a \LaTeX{} package. - -If a file is not found in the database, by default \KPS{} goes ahead -and searches the disk. If a particular path element begins with -\samp{!!}, however, \emph{only} the database will be searched for that -element, never the disk. - - -\subsubsection{kpsewhich: Standalone path searching} -\label{Invoking-kpsewhich} - -The \texttt{kpsewhich} program exercises path searching independent of any -particular application. This can be useful as a sort of \code{find} -program to locate files in \TeX{} hierarchies (this is used heavily in -the distributed \samp{mktex}\dots\ scripts). - -\begin{alltt} -> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} -\end{alltt} -The options specified in \ttvar{option} start with either \samp{-} -or \samp{-{}-}, and any unambiguous abbreviation is accepted. - -\KPS{} looks up each non-option argument on the command line as a -filename, and returns the first file found. There is no option to -return all the files with a particular name (you can run the Unix -\samp{find} utility for that). - -The more important options are described next. - -\begin{ttdescription} -\item[\texttt{-{}-dpi=\var{num}}]\mbox{} - Set the resolution to \ttvar{num}; this only affects \samp{gf} - and \samp{pk} lookups. \samp{-D} is a synonym, for compatibility - with \cmdname{dvips}. Default is 600. - -\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ - Set the format for lookup to \ttvar{name}. By default, the - format is guessed from the filename. For formats which do not have - an associated unambiguous suffix, such as \MP{} support files and - \cmdname{dvips} configuration files, you have to specify the name as - known to \KPS{}, such as \texttt{tex} or \texttt{enc files}. Run - \texttt{kpsewhich -{}-help} for a list. - -\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ - Set the mode name to \ttvar{string}; this only affects \samp{gf} - and \samp{pk} lookups. No default: any mode will be found. -\item[\texttt{-{}-must-exist}]\mbox{}\\ - Do everything possible to find the files, notably including - searching the disk. By default, only the \file{ls-R} database is - checked, in the interest of efficiency. -\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ - Search along the path \ttvar{string} (colon-separated as usual), - instead of guessing the search path from the filename. \samp{//} and - all the usual expansions are supported. The options \samp{-{}-path} - and \samp{-{}-format} are mutually exclusive. -\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ - Set the program name to \texttt{\var{name}}. - This can affect the search paths via the \texttt{.\var{progname}} - feature. - The default is \cmdname{kpsewhich}. -\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ - shows the path used for file lookups of file type \texttt{\var{name}}. - Either a filename extension (\code{.pk}, \code{.vf}, etc.) or a - name can be used, just as with \samp{-{}-format} option. -\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ - sets the debugging options to \texttt{\var{num}}. -\end{ttdescription} - - -\subsubsection{Examples of use} -\label{SExamplesofuse} - -Let us now have a look at \KPS{} in action. Here's a straightforward search: - -\begin{alltt} -> \Ucom{kpsewhich article.cls} - /usr/local/texmf-dist/tex/latex/base/article.cls -\end{alltt} -We are looking for the file \file{article.cls}. Since the \samp{.cls} -suffix is unambiguous we do not need to specify that we want to look for a -file of type \optname{tex} (\TeX{} source file directories). We find it in -the subdirectory \file{tex/latex/base} below the \samp{texmf-dist} \TL\ -directory. Similarly, all of the following are found without problems -thanks to their unambiguous suffix. -\begin{alltt} -> \Ucom{kpsewhich array.sty} - /usr/local/texmf-dist/tex/latex/tools/array.sty -> \Ucom{kpsewhich latin1.def} - /usr/local/texmf-dist/tex/latex/base/latin1.def -> \Ucom{kpsewhich size10.clo} - /usr/local/texmf-dist/tex/latex/base/size10.clo -> \Ucom{kpsewhich small2e.tex} - /usr/local/texmf-dist/tex/latex/base/small2e.tex -> \Ucom{kpsewhich tugboat.bib} - /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib -\end{alltt} - -That last is a \BibTeX{} bibliography database for \textsl{TUGBoat} articles. - -\begin{alltt} -> \Ucom{kpsewhich cmr10.pk} -\end{alltt} -Font bitmap glyph files of type \file{.pk} are used by display -programs like \cmdname{dvips} and \cmdname{xdvi}. Nothing is returned in -this case since there are no pre-generated Computer Modern \samp{.pk} -files in \TL{}\Dash the Type~1 variants are used by default. -\begin{alltt} -> \Ucom{kpsewhich wsuipa10.pk} -\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk -\else /usr/local/texmf-var/fonts/pk/ljfour/public/ -... wsuipa/wsuipa10.600pk -\fi\end{alltt} - -For these fonts (a phonetic alphabet from the University of Washington) -we had to generate \samp{.pk} files, and since the default \MF{} mode on -our installation is \texttt{ljfour} with a base resolution of 600\dpi{} -(dots per inch), this instantiation is returned. -\begin{alltt} -> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} -\end{alltt} -In this case, when specifying that we are interested in a resolution -of 300\dpi{} (\texttt{-dpi=300}) we see that no such font is available on -the system. A program like \cmdname{dvips} or \cmdname{xdvi} would -go off and actually build the required \texttt{.pk} files -using the script \cmdname{mktexpk}. - -Next we turn our attention to \cmdname{dvips}'s header and configuration -files. We first look at one of the commonly used files, the general -prolog \file{tex.pro} for \TeX{} support, before turning our attention -to the generic configuration file (\file{config.ps}) and the \PS{} font -map \file{psfonts.map}\Dash as of 2004, map and encoding files have -their own search paths and new location in \dirname{texmf} trees. As -the \samp{.ps} suffix is ambiguous we have to specify explicitly which -type we are considering (\optname{dvips config}) for the file -\texttt{config.ps}. -\begin{alltt} -> \Ucom{kpsewhich tex.pro} - /usr/local/texmf/dvips/base/tex.pro -> \Ucom{kpsewhich --format="dvips config" config.ps} - /usr/local/texmf/dvips/config/config.ps -> \Ucom{kpsewhich psfonts.map} - /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map -\end{alltt} - -We now take a closer look at the \acro{URW} Times \PS{} support -files. The prefix for these in the standard font naming scheme is -\samp{utm}. The first file we look at is the configuration file, -which contains the name of the map file: -\begin{alltt} -> \Ucom{kpsewhich --format="dvips config" config.utm} - /usr/local/texmf-dist/dvips/psnfss/config.utm -\end{alltt} -The contents of that file is -\begin{alltt} - p +utm.map -\end{alltt} -which points to the file \file{utm.map}, which we want to -locate next. -\begin{alltt} -> \Ucom{kpsewhich utm.map} - /usr/local/texmf-dist/fonts/map/dvips/times/utm.map -\end{alltt} -This map file defines the file names of the Type~1 \PS{} fonts in -the URW collection. Its contents look like (we only show part of the -lines): -\begin{alltt} -utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} -\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb -\else /usr/local/texmf-dist/fonts/type1/ -... urw/utm/utmr8a.pfb -\fi\end{alltt} - -It should be evident from these examples how you can easily locate the -whereabouts of a given file. This is especially important if you suspect -that the wrong version of a file is picked up somehow, since -\cmdname{kpsewhich} will show you the first file encountered. - -\subsubsection{Debugging actions} -\label{Debugging} - -Sometimes it is necessary to investigate how a program resolves file -references. To make this practical, \KPS{} offers various levels of -debugging output: - -\begin{ttdescription} -\item[\texttt{\ 1}] \texttt{stat} calls (disk lookups). When running - with an up-to-date \file{ls-R} database this should almost give no - output. -\item[\texttt{\ 2}] References to hash tables (such as \file{ls-R} - databases, map files, configuration files). -\item[\texttt{\ 4}] File open and close operations. -\item[\texttt{\ 8}] General path information for file types - searched by \KPS. This is useful to find out where a particular - path for the file was defined. -\item[\texttt{16}] Directory list for each path element (only relevant - for searches on disk). -\item[\texttt{32}] File searches. -\end{ttdescription} -A value of \texttt{-1} will set all the above options; in practice, -this is usually the most convenient. - -Similarly, with the \cmdname{dvips} program, by setting a combination of -debug switches, one can follow in detail where files are being picked up -from. Alternatively, when a file is not found, the debug trace shows in -which directories the program looks for the given file, so that one can -get an indication what the problem~is. - -Generally speaking, as most programs call the \KPS{} library -internally, one can select a debug option by using the -\envname{KPATHSEA\_DEBUG} environment variable, and setting it to (a -combination of) values as described in the above list. - -(Note for Windows users: it is not easy to redirect -all messages to a file in this system. For diagnostic purposes -you can temporarily \texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log}). - -Let us consider, as an example, a small \LaTeX{} source file, -\file{hello-world.tex}, which contains the following input. -\begin{verbatim} - \documentclass{article} - \begin{document} - Hello World! - \end{document} -\end{verbatim} -This little file only uses the font \file{cmr10}, so let us look at -how \cmdname{dvips} prepares the \PS{} file (we want to use the Type~1 -version of the Computer Modern fonts, hence the option \texttt{-Pcms}). -\begin{alltt} -> \Ucom{dvips -d4100 hello-world -Pcms -o} -\end{alltt} -In this case we have combined \cmdname{dvips}'s debug class 4 (font -paths) with \KPS's path element expansion (see \cmdname{dvips} Reference -Manual, \OnCD{texmf/doc/html/dvips/dvips_toc.html}). -The output (slightly rearranged) appears in -Figure~\ref{fig:dvipsdbga}. -\begin{figure*}[tp] -\centering -\input{examples/ex6a.tex} -\caption{Finding configuration files}\label{fig:dvipsdbga} - -\bigskip - -\input{examples/ex6b.tex} -\caption{Finding the prolog file}\label{fig:dvipsdbgb} - -\bigskip - -\input{examples/ex6c.tex} -\caption{Finding the font file}\label{fig:dvipsdbgc} -\end{figure*} - -\cmdname{dvips} starts by locating its working files. First, -\file{texmf.cnf} is found, which gives the definitions of the search -paths for the other files, then the file database \file{ls-R} (to -optimize file searching) and the file \file{aliases}, which makes it -possible to declare several names (e.g., a short \acro{DOS}-like 8.3 and -a more natural longer version) for the same file. Then \cmdname{dvips} -goes on to find the generic configuration file \file{config.ps} -before looking for the customization file \file{.dvipsrc} (which, in -this case is \emph{not found}). Finally, \cmdname{dvips} locates the -config file for the Computer Modern \PS{} fonts \file{config.cms} -(this was initiated with the \texttt{-Pcms} option on the \cmdname{dvips} -command). This file contains the list of the map files which -define the relation between the \TeX{}, \PS{} and file system -names of the fonts. -\begin{alltt} -> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} - p +ams.map - p +cms.map - p +cmbkm.map - p +amsbkm.map -\end{alltt} -\cmdname{dvips} thus goes on to find all these files, plus the generic -map file \file{psfonts.map}, which is always loaded (it contains -declarations for commonly used \PS{} fonts; see the last part of -Section \ref{SExamplesofuse} for more details about \PS{} map -file handling). - -At this point \cmdname{dvips} identifies itself to the user: -\begin{alltt} -This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) -\end{alltt} -\ifSingleColumn -Then it goes on to look for the prolog file \file{texc.pro}: -\begin{alltt}\small -kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro -\end{alltt} -\else -Then it goes on to look for the prolog file \file{texc.pro} (see -Figure~\ref{fig:dvipsdbgb}). -\fi - -After having found the file in question, \cmdname{dvips} outputs -date and time, and informs us that it will generate the -file \file{hello-world.ps}, then that it needs the font file -\file{cmr10}, and that the latter is declared as ``resident'' (no -bitmaps needed): -\begin{alltt}\small -TeX output 1998.02.26:1204' -> hello-world.ps -Defining font () cmr10 at 10.0pt -Font cmr10 is resident. -\end{alltt} -Now the search is on for the file \file{cmr10.tfm}, which is found, -then a few more prolog files (not shown) are referenced, and finally -the Type~1 instance \file{cmr10.pfb} of the font is located and -included in the output file (see last line). -\begin{alltt}\small -kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, - path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: - /var/tex/fonts/tfm//). -kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm -kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, - ... - -kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb -[1] -\end{alltt} - -\subsection{Runtime options} - -Another useful feature of \Webc{} is its possibility to control a number -of memory parameters (in particular, array sizes) via the runtime file -\file{texmf.cnf} read by \KPS{}. The memory settings can be found in -Part 3 of that file in the \TL{} distribution. The more important -are: - -\begin{ttdescription} -\item[\texttt{main\_memory}] - Total words of memory available, for - \TeX{}, \MF{} and \MP. You must make a new format file for each - different setting. For instance, you could generate a ``huge'' - version of \TeX{}, and call the format file \texttt{hugetex.fmt}. - Using the standard way of specifying the program name used by \KPS{}, - the particular value of the \texttt{main\_memory} variable will then - be read from \file{texmf.cnf}. -\item[\texttt{extra\_mem\_bot}] - Extra space for ``large'' \TeX{} data structures: - boxes, glue, breakpoints, etc. Especially useful if you use - \PiCTeX{}. -\item[\texttt{font\_mem\_size}] - Number of words for font information available for \TeX. This - is more or less the total size of all TFM files read. -\item[\texttt{hash\_extra}] - Additional space for the hash table of control sequence names. - Approximately 10,000 control sequences can be stored in the main - hash table; if you have a large book with numerous cross-references, - this might not be enough. The default value of - \texttt{hash\_extra} is \texttt{50000}. -\end{ttdescription} - -\noindent Of course, this facility is no substitute for truly dynamic -arrays and memory allocation, but since these are extremely difficult to -implement in the present \TeX{} source, these runtime parameters provide -a practical compromise allowing some flexibility. - - -\begin{comment} -\section{Building on a new Unix platform} - -If you have a platform for which executables are not included, you will -need to compile \TeX{} and friends. This is not as hard as it -sounds. What you need is all in the directory \texttt{source} in the -distribution. - -\subsection{Prerequisites} - -You will need at least 100 megabytes of disk space to compile all of -\TeX{} and its support programs. You'll also need an \acro{ANSI} C -compiler, a \cmdname{make} utility, a lexical scanner, and a parser -generator. We recommend the \acro{GNU} version of these programs -(\cmdname{gcc}, \acro{GNU} \cmdname{make}, \cmdname{m4}, \cmdname{flex}, -\cmdname{bison}). You may be able to work with other C compilers and -\cmdname{make} programs, but you will need a good understanding of -building Unix programs to sort out problems. - -Also, the command \texttt{uname} must return a sensible value. - - -\subsection{Configuration} - -To begin, perform a normal installation of \TL{} to your disk (see -section~\ref{sec:unix-install-disk} on -\p.\pageref{sec:unix-install-disk}). You may wish to skip installing -all of the prebuilt binaries. - -Then, unpack the source from the compressed \texttt{tar} file in the -directory \dirname{source} to your disk and change directory to where -you placed it. - -Next, run \cmdname{configure} with a command line like this: -\begin{alltt} -> \Ucom{sh configure -prefix=/usr/local/TeX} -\end{alltt} - -The \optname{-prefix} directory is the one where you installed the -support tree; the directory layout will be as follows (where \$TEXDIR -stands for the directory you chose): - -\noindent -\begin{tabular}{>{\ttfamily}ll@{}} - \dirname{$TEXDIR/share/texmf} & main tree with fonts,\\ - & \qquad macros, etc\\ - \dirname{$TEXDIR/man} & Unix manual pages\\ - \dirname{$TEXDIR/info} & \acro{GNU} style Info manuals\\ - \dirname{$TEXDIR/bin/$PLATFORM} & binaries\\ -\end{tabular} -%$ - -If you want to leave out the \dirname{$PLATFORM} directory level, -i.e., put the binaries directly into \dirname{$TEXDIR/bin}, specify -the \verb|--disable-multiplatform| option to \cmdname{configure}. - -Have a look at the output of \verb|./configure --help| for more -options you can use. For example, you can skip building of \OMEGA{} and -\eTeX{}. - - -\subsection{Running \cmdname{make}} - -Make sure the shell variable or option \texttt{noclobber} is not set. -Then, run the main \cmdname{make} like this: -\begin{alltt} -> \Ucom{make world} -\end{alltt} -and relax\ldots - -Alternatively, you want to log all the output, as in: -\begin{alltt} -> \Ucom{sh -c "make world >world.log 2>\&1" \&} -\end{alltt} - -Before you believe that everything went ok, please check the log file -for errors: \acro{GNU} \cmdname{make} always uses the string \samp{***} -whenever a command fails. Also, check if all the programs were built: - -\begin{alltt} -> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} -> \Ucom{ls | wc} -\end{alltt} -The result should be over 200 (you can check the exact number with the -\dirname{bin} directory contents in the distribution). - -If you need special privileges for \texttt{make install}, you can -separate the \samp{make world} into two different runs, like this: -\begin{alltt} -> \Ucom{make all} -> \Ucom{su} -> \Ucom{make install strip} -\end{alltt} - -After you've installed your new binaries, you should follow the normal -post-installation procedures, given in section~\ref{sec:postinstall} -(\p.\pageref{sec:postinstall}). - -Also, if you'd like to make your binaries available to others, please -contact us. We'll be happy to put them on the \TL\ web pages. -\end{comment} - -\section{Acknowledgements} - -\TL{} is a joint effort by virtually all of the \TeX{} user groups. -This edition of \TL{} was overseen by Sebastian Rahtz and Karl Berry. -The other principal contributors are listed below. - -\begin{itemize*} - -\item The English, German, Dutch, and Polish \TeX{} user groups -(\acro{TUG}, \acro{DANTE} e.V., \acro{NTG}, and \acro{GUST}, -respectively), which together provide the necessary technical -and administrative infrastructure. Please join your local user group! - -\item The \acro{CTAN} team, which distributes the \TL{} images and -provides the common infrastructure for package updates, upon which \TL{} -depends. - -\item Peter Breitenlohner and the \eTeX\ team for the stable foundation -of future \TeX's. - -\item Thomas Esser, without whose marvelous \teTeX{} package \TL{} -would certainly not exist, and whose continual help makes it a better -product. - -\item Michel Goossens, who co-authored the original documentation. - -\item Eitan Gurari, whose \TeX4ht was used to create the \HTML{} -version of this documentation, and who worked tirelessly to improve -it at short notice. - -\item Hans Hagen, for major testing and making the \ConTeXt\ format -conform to \TL's needs. - -\item \Thanh, Martin Schr\"oder, and the pdf\TeX\ team for continuing -enhancements of \TeX's abilities. - -\item Taco Hoekwater, for renewed development efforts on MetaPost and -\TeX\ itself. - -\item Pawe{\l} Jackowski, for the Windows installer \cmdname{tlpm}, -and Tomasz {\L}uczak, for \cmdname{tlpmgui}. - -\item Akira Kakuto, for great assistance in incorporating the Windows -binaries from his \acro{W32TEX} distribution -(\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}). - -\item Jonathan Kew and his employer \acro{SIL}, for the major new -development of Xe\TeX{} and taking the time and trouble to integrate it -in \TL{}. - -\item Reinhard Kotucha, for helping with the massive task of updating -packages in \TL{}, as well as Windows research efforts, the -\texttt{getnonfreefonts} script, and more. - -\item Petr Ol\v{s}ak, who coordinated and checked all the Czech and Slovak -material very carefully. - -\item Toshio Oshima, for his \cmdname{dviout} previewer for Windows. - -\item Fabrice Popineau, for the original Windows support in \TL{}. - -\item Norbert Preining, for helping with the \TL{} infrastructure and -package updates, and coordinating the Debian version of \TL{} (together -with Frank K\"uster), making many suggestions for improvement along the -way. - -\item Staszek Wawrykiewicz, the principal tester for all of \TL{}, -and coordinator of the many major Polish contributions: fonts, Windows -installation, and more. - -\item Olaf Weber, for his patient assembly and maintenance of Web2C, -upon which all else depends. - -\item Gerben Wierda, for creating and maintaining the \MacOSX\ support, -and much integration and testing. - -\item Graham Williams, on whose work the catalogue of packages depends. - -\end{itemize*} - -Builders of the binaries: -Tigran Aivazian and Hartmut Henkel (\pkgname{x86\_64-linux}), -Akira Kakuto and Fabrice Popineau (\pkgname{win32}), -Manfred Lotz (\pkgname{i386-freebsd}), -Norbert Preining (\pkgname{alpha-linux}), -Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-linux}, - \pkgname{sparc-solaris}), -Karl Berry (\pkgname{i386-linux}), -Olaf Weber (\pkgname{mips-irix}), -Gerben Wierda (\pkgname{i386-darwin}, \pkgname{powerpc-darwin}). - -Documentation and translation updates: -Karl Berry (English), -Daniel Flipo \& Fabrice Popineau (French), -G\"unter Partosch \& Hartmut Henkel (German), -Petr Sojka \& Jan Busa (Czech\slash Slovak), -Boris Veytsman (Russian), -Staszek Wawrykiewicz (Polish). - -Of course the most important acknowledgement must go to Donald Knuth, first -for inventing \TeX, and then for giving it to the world. - - -\section{Release history} -\label{sec:history} - -\subsection{Past} - -Discussion began in late 1993 when the Dutch \TeX{} Users Group was -starting work on its 4All\TeX{} \CD{} for \acro{MS-DOS} users, and it -was hoped at that time to issue a single, rational, \CD{} for all -systems. This was too ambitious a target for the time, but it did spawn -not only the very successful 4All\TeX{} \CD{}, but also the \acro{TUG} -Technical Council working group on a \emph{\TeX{} Directory Structure} -(\url{http://tug.org/tds}), which specified how to create consistent and -manageable collections of \TeX{} support files. A complete draft of the -\TDS{} was published in the December 1995 issue of \textsl{TUGboat}, and -it was clear from an early stage that one desirable product would be a -model structure on \CD{}. The distribution you now have is a very direct -result of the working group's deliberations. It was also clear that the -success of the 4All\TeX{} \CD{} showed that Unix users would benefit -from a similarly easy system, and this is the other main strand of -\TL. - -We first undertook to make a new Unix-based \TDS{} \CD{} in the autumn -of 1995, and quickly identified Thomas Esser's \teTeX{} as the ideal -setup, as it already had multi-platform support and was built with -portability across file systems in mind. Thomas agreed to help, and work -began seriously at the start of 1996. The first edition was released in -May 1996. At the start of 1997, Karl Berry completed a major new release -of Web2c, which included nearly all the features which Thomas Esser had -added in \teTeX, and we decided to base the 2nd edition of the \CD{} on -the standard \Webc, with the addition of \teTeX's \texttt{texconfig} -script. The 3rd edition of the \CD{} was based on a major revision of -\Webc, 7.2, by Olaf Weber; at the same time, a new revision of \teTeX -was being made, and \TL{} included almost all of its features. The -4th edition followed the same pattern, using a new version of \teTeX, -and a new release of \Webc{} (7.3). The system now included a complete -Windows setup. - -For the 5th edition (March 2000) many parts of the \CD{} were revised -and checked, updating hundreds of packages. Package details were stored -in XML files. But the major change for \TeX\ Live 5 was that all -non-free software was removed. Everything in \TL{} is now intended -to be compatible with the Debian Free Software Guidelines -(\url{http://www.debian.org/intro/free}); we have done our best to check -the license conditions of all packages, but we would very much -appreciate hearing of any mistakes. - -The 6th edition (July 2001) had much more material updated. The major -change was a new install concept: the user could select a more exact set -of needed collections. Language-related collections were completely -reorganized, so selecting any of them installs not only macros, fonts, -etc., but also prepares an appropriate \texttt{language.dat}. - -The 7th edition of 2002 had the notable addition of \MacOSX{} support, -and the usual myriad of updates to all sorts of packages and -programs. An important goal was integration of the source back with -\teTeX, to correct the drift apart in versions~5 and~6. - -\subsubsection{2003} - -In 2003, with the continuing flood of updates and additions, we found -that \TL{} had grown so large it could no longer be contained on a -single \CD, so we split it into three different distributions (see -section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}). In -addition: - -\begin{itemize*} -\item At the request of the \LaTeX{} team, we changed the standard - \cmdname{latex} and \cmdname{pdflatex} commands to now use \eTeX{} (see - \p.\pageref{text:etex}). -\item The new Latin Modern fonts were included (and are recommended). -\item Support for Alpha \acro{OSF} was removed - (\acro{HPUX} support was removed previously), since no one had (or - volunteered) hardware available on which to compile new binaries. -\item Windows setup was substantially changed; for the first time - an integrated environment based on XEmacs was introduced. -\item Important supplementary programs for Windows - (Perl, Ghost\-script, Image\-Magick, Ispell) are now installed - in the \TL{} installation directory. -\item Font map files used by \cmdname{dvips}, \cmdname{dvipdfm} - and \cmdname{pdftex} are now generated by the new program - \cmdname{updmap} and installed into \dirname{texmf/fonts/map}. -\item \TeX{}, \MF{}, and \MP{} now, by default, output most input - characters (32 and above) as themselves in output (e.g., - \verb|\write|) files, - log files, and the terminal, i.e., \emph{not} translated using the - \verb|^^| notation. In \TL{}~7, this translation was - dependent on the system locale settings; now, locale settings do - not influence the \TeX{} programs' behavior. If for some reason - you need the \verb|^^| output, rename the file - \verb|texmf/web2c/cp8bit.tcx|. (Future releases will have cleaner - ways to control this.) -\item This documentation was substantially revised. -\item Finally, since the edition numbers had grown unwieldy, - the version is now simply identified by the year: \TL{} 2003. -\end{itemize*} - - -\subsubsection{2004} - -2004 saw many changes: - -\begin{itemize} - -\item If you have locally-installed fonts which use their own -\filename{.map} or (much less likely) \filename{.enc} support files, you -may need to move those support files. - -\filename{.map} files are now searched for in subdirectories of -\dirname{fonts/map} only (in each \filename{texmf} tree), along the -\envname{TEXFONTMAPS} path. Similarly, \filename{.enc} files are now -searched for in subdirectories of \dirname{fonts/enc} only, along the -\envname{ENCFONTS} path. \cmdname{updmap} will attempt to warn about -problematic files. - -For methods of handling this and other information, please see -\url{http://tug.org/texlive/mapenc.html}. - -\item The \TK\ has been expanded with the addition of a \MIKTEX-based -installable \CD, for those who prefer that implementation to Web2C. -See section~\ref{sec:struct-tl} (\p.\pageref{sec:struct-tl}). - -\item Within \TL, the single large \dirname{texmf} tree of previous -releases has been replaced by three: \dirname{texmf}, -\dirname{texmf-dist}, and \dirname{texmf-doc}. See -section~\ref{sec:tld} (\p.\pageref{sec:tld}), and the \filename{README} -files for each. - -\item All \TeX-related input files are now collected in -the \dirname{tex} subdirectory of \dirname{texmf*} trees, rather than -having separate sibling directories \dirname{tex}, \dirname{etex}, -\dirname{pdftex}, \dirname{pdfetex}, etc. See -\CDref{texmf-doc/doc/english/tds/tds.html\#Extensions} -{\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}. - -\item Helper scripts (not meant to be invoked by users) are now located -in a new \dirname{scripts} directory of \dirname{texmf*} trees, and -searched for via \verb|kpsewhich -format=texmfscripts|. So if you have -programs which call such scripts, they'll need to be adjusted. See -\CDref{texmf-doc/doc/english/tds/tds.html\#Scripts} -{\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}. - -\item Almost all formats leave most characters printable as -themselves via the ``translation file'' \filename{cp227.tcx}, instead of -translating them with the \verb|^^| notation. Specifically, characters -at positions 32--256, plus tab, vertical tab, and form feed are -considered printable and not translated. The exceptions are plain \TeX\ -(only 32--126 printable), \ConTeXt\ (0--255 printable), and the -\OMEGA-related formats. This default behavior is almost the same as in -\TL\,2003, but it's implemented more cleanly, with more possibilities -for customization. See \CDref{texmf/doc/web2c/web2c.html\#TCX-files} -{\texttt{texmf/doc/web2c/web2c.html\#TCX-files}}. -(By the way, with Unicode input, \TeX\ may output partial character -sequences when showing error contexts, since it is byte-oriented.) - -\item \textsf{pdfetex} is now the default engine for all formats -except (plain) \textsf{tex} itself. (Of course it generates \acro{DVI} -when run as \textsf{latex}, etc.) This means, among other things, that -the microtypographic features of \textsf{pdftex} are available in -\LaTeX, \ConTeXt, etc., as well as the \eTeX\ features -(\OnCD{texmf-dist/doc/etex/base/}). - -It also means it's \emph{more important than ever} to use the -\pkgname{ifpdf} package (works with both plain and \LaTeX) or equivalent -code, because simply testing whether \cs{pdfoutput} or some other -primitive is defined is not a reliable way to determine if \acro{PDF} -output is being generated. We made this backward compatible as best we -could this year, but next year, \cs{pdfoutput} may be defined even when -\acro{DVI} is being written. - -\item pdf\TeX\ (\url{http://pdftex.org}) has many new features: - - \begin{itemize*} - - \item \cs{pdfmapfile} and \cs{pdfmapline} provide font map support - from within a document. - - \item Microtypographic font expansion can be used more easily.\\ - \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} - - \item All parameters previously set through the special configuration - file \filename{pdftex.cfg} must now be set through primitives, - typically in \filename{pdftexconfig.tex}; \filename{pdftex.cfg} is no - longer supported. Any extant \filename{.fmt} files must be redumped - when \filename{pdftexconfig.tex} is changed. - - \item See the pdf\TeX\ manual for more: \OnCD{texmf/doc/pdftex/manual}. - - \end{itemize*} - -\item The \cs{input} primitive in \cmdname{tex} (and \cmdname{mf} and -\cmdname{mpost}) now accepts double quotes containing spaces and other -special characters. Typical examples: -\begin{verbatim} -\input "filename with spaces" % plain -\input{"filename with spaces"} % latex -\end{verbatim} -See the Web2C manual for more: \OnCD{texmf/doc/web2c}. - -\item enc\TeX\ support is now included within Web2C and consequently all -\TeX\ programs, via the \optname{-enc} option\Dash \emph{only when -formats are built}. enc\TeX\ supports general re-encoding of input and -output, enabling full support of Unicode (in \acro{UTF}-8). See -\OnCD{texmf-dist/doc/generic/enctex/} and -\url{http://www.olsak.net/enctex.html}. - -\item Aleph, a new engine combining \eTeX\ and \OMEGA, is available. -A little information is available in \OnCD{texmf-dist/doc/aleph/base} -and \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph}. The -\LaTeX-based format for Aleph is named \textsf{lamed}. - -\item The latest \LaTeX\ release has a new version of the -\acro{LPPL}\Dash now officially a Debian-approved license. Assorted -other updates, see the \filename{ltnews} files in -\OnCD{texmf-dist/doc/latex/base}. - -\item \cmdname{dvipng}, a new program for converting \acro{DVI} to -\acro{PNG} image files, is included. See \OnCD{texmf/doc/man/man1/dvipng.1}. - -\item We reduced the \pkgname{cbgreek} package to a ``medium'' sized set -of fonts, with the assent and advice of the author (Claudio Beccari). -The excised fonts are the invisible, outline, and transparency ones, -which are relatively rarely used, and we needed the space. The full set -is of course available from \acro{CTAN} -(\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). - -\item \cmdname{oxdvi} has been removed; just use \cmdname{xdvi}. - -\item The \cmdname{ini} and \cmdname{vir} commands (links) for -\cmdname{tex}, \cmdname{mf}, and \cmdname{mpost} are no longer created, -such as \cmdname{initex}. The \cmdname{ini} functionality has been -available through the command-line option \optname{-ini} for years now. - -\item \textsf{i386-openbsd} platform support was removed. Since the -\pkgname{tetex} package in the \acro{BSD} Ports system is available, and -\acro{GNU/}Linux and Free\acro{BSD} binaries were available, it seemed -volunteer time could be better spent elsewhere. - -\item On \textsf{sparc-solaris} (at least), you may have to set the -\envname{LD\_LIBRARY\_PATH} environment variable to run the -\pkgname{t1utils} programs. This is because they are compiled with C++, -and there is no standard location for the runtime libraries. (This is -not new in 2004, but wasn't previously documented.) Similarly, on -\textsf{mips-irix}, the \acro{MIPS}pro 7.4 runtimes are required. - -\end{itemize} - -\subsubsection{2005} - -2005 saw the usual huge number of updates to packages and programs. -The infrastructure stayed relatively stable from 2004, but inevitably -there were some changes there as well: - -\begin{itemize} - -\item New scripts \cmdname{texconfig-sys}, \cmdname{updmap-sys}, and - \cmdname{fmtutil-sys} were introduced, which modify the - configuration in the system trees. The \cmdname{texconfig}, - \cmdname{updmap}, and \cmdname{fmtutil} scripts now modify - user-specific files, under \dirname{$HOME/.texlive2005}. - See section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig}. - -\item Corresponding new variables \envname{TEXMFCONFIG} and - \envname{TEXMFSYSCONFIG} to specify the trees where configuration - files (user or system, respectively) are found. Thus, you may - need to move personal versions of \filename{fmtutil.cnf} and - \filename{updmap.cfg} to these places; another option is to - redefine \envname{TEXMFCONFIG} or \envname{TEXMFSYSCONFIG} in - \filename{texmf.cnf}. In any case the real location of these files - and the values of \envname{TEXMFCONFIG} and \envname{TEXMFSYSCONFIG} - must agree. - See section~\ref{sec:texmftrees}, \p.\pageref{sec:texmftrees}. - -\item Last year, we kept \verb|\pdfoutput| and other primitives undefined - for DVI output, even though the \cmdname{pdfetex} program was - being used. This year, as promised, we undid that compatibility - measure. So if your document uses \verb|\ifx\pdfoutput\undefined| - to test if PDF is being output, it will need to be changed. You - can use the package \pkgname{ifpdf.sty} (which works under both - plain \TeX\ and \LaTeX) to do this, or steal its logic. - -\item Last year, we changed most formats to output (8-bit) characters as - themselves (see previous section). The new TCX file - \filename{empty.tcx} now provides an easier way to get the - original \verb|^^| notation if you so desire, as in: -\begin{verbatim} -latex --translate-file=empty.tcx yourfile.tex -\end{verbatim} - -\item The new program \cmdname{dvipdfmx} is included for translation of - DVI to PDF; this is an actively maintained update of - \cmdname{dvipdfm} (which is also still available for now, though - no longer recommended). - -\item The new programs \cmdname{pdfopen} and \cmdname{pdfclose} are included - to allow reloading of pdf files in the Adobe Acrobat Reader without - restarting the program. (Other pdf readers, notably \cmdname{xpdf}, - \cmdname{gv}, and \cmdname{gsview}, have never suffered from this - problem.) - -\item For consistency, the variables \envname{HOMETEXMF} and - \envname{VARTEXMF} have been renamed to \envname{TEXMFHOME} and - \envname{TEXMFSYSVAR}, respectively. There is also - \envname{TEXMFVAR}, which is by default user-specific. See the - first point above. - -\end{itemize} - - -\subsection{Present} -\label{tlcurrent} - -In 2006--2007, the major new addition to \TL{} was the Xe\TeX{} program, -available as the \texttt{xetex} and \texttt{xelatex} programs; see -\url{http://scripts.sil.org/xetex}. - -MetaPost also received a notable update, with more planned for the -future (\url{http://tug.org/metapost/articles}), likewise pdf\TeX{} -(\url{http://tug.org/applications/pdftex}) - -The \TeX\ \filename{.fmt} (high-speed format) and the similar files for -MetaPost and \MF\ are now stored in subdirectories of \dirname{texmf/web2c}, -instead of in the directory itself (although the directory is still -searched, for the sake of existing \filename{.fmt}'s). The -subdirectories are named for the `engine' in use, such as \filename{tex} -or \filename{pdftex} or \filename{xetex}. This change should be -invisible in normal use. - -The (plain) \texttt{tex} program no longer reads \texttt{\%\&} first -lines to determine what format to run; it is the pure Knuthian \TeX. -(\LaTeX\ and everything else do still read \texttt{\%\&} lines). - -The installation scripts now accept various environment variables to -allow for non-interactive installation; see -section~\ref{sec:noninteractive-install}. - -Of course the year also saw (the usual) hundreds of other updates to -packages and programs. As usual, please check \acro{CTAN} -(\url{http://www.ctan.org}) for updates. - -Internally, the source tree is now stored in Subversion, with a standard -web interface for viewing the tree, as linked from our home page. -Although not visible in the final distribution, we expect this will -provide a stable development foundation for future years. - -Finally, in May 2006 Thomas Esser announced that he would no longer be -updating te\TeX{} (\url{http://tug.org/tetex}). As a result, there was -been a surge of interest in \TL{}, especially among \acro{GNU}/Linux -distributors. (There is a new \texttt{tetex} installation scheme in -\TL{}, which provides an approximate equivalent.) We hope this will -eventually translate to improvements in the \TeX\ environment for -everyone. - - -\subsection{Future} - -\emph{\TL{} is not perfect!} (And never will be.) We intend to -continue to release new versions, and would like to provide more -help material, more utilities, more installation programs, and (of -course) an ever-improved and checked tree of macros and fonts. This work -is all done by hard-pressed volunteers in their limited spare time, and -a great deal remains to be done. If you can help, don't hesitate to put -your name forward! - -Please send corrections, suggestions, and offers of help to:\hfill\null -\begin{quote} -\email{tex-live@tug.org} \\ -\url{http://tug.org/texlive} -\end{quote} - -\medskip -\noindent \textsl{Happy \TeX ing!} - -\end{document} diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/live-2008.tex b/Master/texmf-doc/source/texlive/texlive-en/archive/live-2008.tex deleted file mode 100644 index a172d5f409e..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/live-2008.tex +++ /dev/null @@ -1,2951 +0,0 @@ -% $Id: live.tex 9531 2008-07-13 21:12:58Z siepo $ -% TeX Live documentation. Originally written by Sebastian Rahtz and -% Michel Goossens, now maintained by Karl Berry and others. -% Public domain. -% -\documentclass{article} -\let\tldocenglish=1 % for live4ht.cfg -\usepackage{tex-live} -\usepackage[latin1]{inputenc} % translators: use your preferred encodings. -\usepackage[T1]{fontenc} - -\begin{document} - -\title{% - {\huge \textit{The \TeX\ Live Guide}\\\smallskip}% - {\LARGE \textsf{\TL{} 2008}}% -} - -\author{Karl Berry, editor \\[3mm] - \url{http://tug.org/texlive/} - } - -\date{August 2008} - -\maketitle - -\begin{multicols}{2} -\tableofcontents -%\listoftables -\end{multicols} - -\section{Introduction} -\label{sec:intro} - -\subsection{\TeX\ Live and the \TeX\ Collection} - -This document describes the main features of the \TL{} software -distribution\Dash \TeX{} and related programs for \GNU/Linux -and other Unix flavors, \MacOSX, and Windows systems. - -You may have acquired \TL{} by downloading, or on the \TK{} \DVD, -which \TeX{} usergroups distribute among their members. Section -\ref{sec:tl-coll-dists} briefly describes the contents of this \DVD. -Both \TL{} and the \TK{} are cooperative efforts by the \TeX{} user -groups. This document mainly describes \TL{} itself. - -\TL{} includes executables for \TeX{}, \LaTeXe{}, \ConTeXt, -\MF, \MP, \BibTeX{} and many other programs; an extensive collection -of macros, fonts and documentation; and support for typesetting in -many different scripts from around the world. - -\TL{} packages are regularly updated from -\acro{CTAN}: \url{http://www.ctan.org}. - -For a brief summary of the major changes in this edition of \TL{}, -see the end of the document, section~\ref{sec:history} -(\p.\pageref{sec:history}). - -\subsection{Operating system support} -\label{sec:os-support} - -\TL{} contains binaries for many Unix-based architectures, -including \MacOSX. The included sources should enable installation -on platforms for which we do not have binaries. - -As to Windows: only Windows 2000 and later are supported. Windows -9\textit{x}, ME and NT have been dropped. Because of this -change, Windows requires much less special treatment compared to -the Unix systems. There are no 64-bit executables for Windows, but the -32-bit executables should run on 64-bit systems. - -See section~\ref{sec:tl-coll-dists} for alternate solutions -for Windows and \MacOSX. - -\subsection{Basic installation of \protect\TL{}} -\label{sec:basic} - -You can install \TL{} either from \DVD{} or over the Internet. The net -installer itself is small, and downloads everything requested from the -Internet. The net installer is an attractive option if you need only a -fraction of the complete \TL. - -The \DVD{} installer lets you install to a local disk, but you can -also run \TL{} directly from the \DVD{} (or from a \DVD{} image, if -your system supports that). - -\noindent This is described in the -installation sections following, but here is a quick start: - -\begin{itemize*} - -\item The installation script is named \filename{install-tl}. It can - operate in both a \GUI{} mode (default for Windows) and - a text mode (default for everything else). You can force one mode or - the other with the options \code{-gui} and \code{-no-gui}, respectively. - -\item One of the installed items is a new program, the `\TL\ Manager', - named \prog{tlmgr}. Like the installer, it can be used in both \GUI{} - mode and in text mode. You can use it to install and uninstall - packages and do various configuration tasks. - -\end{itemize*} - - -\subsection{Getting help} -\label{sec:help} - -The \TeX{} community is both active and friendly, and most serious -questions end up getting answered. However, the support is informal, -done by volunteers and casual readers, so it's especially important that -you do your homework before asking. (If you prefer guaranteed -commercial support, you can forego \TL{} completely and purchase a -vendor's system; \url{http://tug.org/interest.html#vendors} has a list.) - -Here is a list of resources, approximately in the order we recommend -using them: - -\begin{description} -\item [Getting Started] If you are new to \TeX, the web page -\url{http://tug.org/begin.html} gives a brief introduction to the system. - -\item [\TeX{} \acro{FAQ}] The \TeX{} \acro{FAQ} is a huge compendium - of answers to all sorts of questions, from the most basic to the - most arcane. It is included on \TL{} in - \OnCD{texmf-doc/doc/english/FAQ-en/html/index.html}, and is available - on the Internet through \url{http://www.tex.ac.uk/faq}. Please - check here first. - -\item [\TeX{} Catalogue] If you are looking for a specific package, -font, program, etc., the \TeX{} Catalogue is the place to look. It is a -huge collection of all \TeX{}-related items. See -\url{http://www.ctan.org/help/Catalogue/}. - -\item [\TeX{} Web Resources] The web page -\url{http://tug.org/interest.html} has many \TeX{}-related links, in -particular for numerous books, manuals, and articles on all aspects of -the system. - -\item [support archives] The two principal support forums are the -Usenet newsgroup \url{news:comp.text.tex} and the mailing list -\email{texhax@tug.org}. Their archives have years of past -questions and answers for your searching pleasure, via -\url{http://groups.google.com/group/comp.text.tex/topics} and -\url{http://tug.org/mail-archives/texhax}, respectively. And a general web -search, for example on \url{http://google.com}, never hurts. - -\item [asking questions] If you cannot find an answer, you can post to -\dirname{comp.text.tex} through Google or your newsreader, or to -\email{texhax@tug.org} through email. But before you post, -\emph{please} read this \acro{FAQ} entry, to maximize -your chances of getting a useful answer: -\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. - -\item [\TL{} support] If you want to report a bug or have -suggestions or comments on the \TL{} distribution, installation, or -documentation, the mailing list is \email{tex-live@tug.org}. However, -if your question is about how to use a particular program included in -\TL{}, please write to that program's maintainer or -mailing list. Often running a program with the \code{-{}-help} option -will provide a bug reporting address. - -\end{description} - -The other side of the coin is helping others who have questions. Both -\dirname{comp.text.tex} and \code{texhax} are open to anyone, so feel -free to join, start reading, and help out where you can. - - -% don't use \TL so the \uppercase in the headline works. Also so -% tex4ht ends up with the right TeX. Likewise the \protect's. -\section{Overview of \protect\TeX\protect\ Live} -\label{sec:overview-tl} - -This section describes the contents of \TL{} and the \TK{} of which it -is a part. - -\subsection{The \protect\TeX\protect\ Collection: \TL, pro\TeX{}t, Mac\TeX} -\label{sec:tl-coll-dists} - -The \TK{} \DVD{} comprises the following: - -\begin{description} - -\item [\TL] A complete \TeX{} system which can be run live or - installed to disk. - -\item [Mac\TeX] for \MacOSX, this adds a native \MacOSX\ installer and other -Mac applications to \TL{}. Its home page is -\url{http://www.tug.org/mactex/}. - -\item [pro\TeX{}t] An enhancement of the \MIKTEX\ distribution for Windows, -\ProTeXt\ adds a few extra tools to \MIKTEX, and simplifies -installation. It is entirely independent of \TL{}, and has its own -installation instructions. The \ProTeXt\ home page is -\url{http://tug.org/protext}. - -\item [CTAN] A snapshot of the \CTAN{} repository. - -\item [\texttt{texmf-extra}] A directory with assorted additional packages. - -\end{description} - -\CTAN{}, \pkgname{protext}, and \dirname{texmf-extra} do not -necessarily follow the same copying conditions as \TL{}, so be careful -when redistributing or modifying. - - -\subsection{Top level \TL{} directories} -\label{sec:tld} - -Here is a brief listing and description of the top level directories in -the \TL{} distribution. On the \pkgname{live} \DVD, the entire \TL{} -hierarchy is in a subdirectory \dirname{texlive}, not at the top -level of the disc. - -\begin{ttdescription} -\item[bin] The \TeX{} system programs, arranged by platform. -% -\item[readme.html] Web pages with a quick introduction and useful links, -in various languages. -% -\item[source] The source to all included programs, including the main \Webc{} - \TeX{} and \MF{} distributions. -% -\item[support] Various auxiliary packages and programs. These are - \emph{not} installed automatically. This includes - assorted editors and \TeX\ shells. -% -\item[texmf] See \dirname{TEXMFMAIN} below. -% -\item[texmf-dist] See \dirname{TEXMFDIST} below. -% -\item[texmf-doc] Tree for self-contained pure documentation, arranged by - language. -% -\item[tlpkg] Scripts, programs and data for managing the - installation. It also contains private copies of - Perl and Ghostscript for Windows, which are invisible outside \TL, - and a new Windows PostScript viewer PSView. -\end{ttdescription} - -In addition to the directories above, the installation scripts and -\filename{README} files (in various languages) are at the top level of -the distribution. - -The \dirname{texmf-doc} directory contains documentation which does -not belong to any particular package or program. The documentation -for the programs (manuals, man pages, Info files) is in -\dirname{texmf/doc}. The documentation for \TeX\ packages and -formats is in \dirname{texmf-dist/doc}. You can use the -\cmdname{texdoc} or \cmdname{texdoctk} programs to find any -documentation wherever it is located. The comprehensive links in -the top-level file \OnCD{doc.html} may also be helpful. - -This \TL\ documentation itself is in \dirname{texmf-doc} and is -available in several languages: - -\begin{itemize*} -\item{Simplified Chinese:} \OnCD{texmf-doc/doc/chinese/texlive-zh-cn} -\item{Czech/Slovak:} \OnCD{texmf-doc/doc/czechslovak/texlive-cz} -\item{English:} \OnCD{texmf-doc/doc/english/texlive-en} -\item{French:} \OnCD{texmf-doc/doc/french/texlive-fr} -\item{German:} \OnCD{texmf-doc/doc/german/texlive-de} -\item{Polish:} \OnCD{texmf-doc/doc/polish/texlive-pl} -\item{Russian:} \OnCD{texmf-doc/doc/russian/texlive-ru} -\end{itemize*} - -\subsection{Overview of the predefined texmf trees} -\label{sec:texmftrees} - -This section lists all predefined variables specifying the texmf trees -used by the system, and their intended purpose, and the default -layout of a \TL{} system. The command \texttt{texconfig conf} shows -you the values of these variables, so that you can easily find out -how they map to directory names in your installation. - -\begin{ttdescription} -\item [TEXMFMAIN] The tree which holds vital parts of the system - such as helper scripts (e.g., \verb+web2c/mktexdir+) and other - support files and their documentation. Does not include - \TeX\ formats and packages. -\item [TEXMFDIST] The tree which holds the main set of macro packages, - fonts, etc., as originally distributed. -\item [TEXMFLOCAL] The tree which administrators can use for system-wide - installation of additional or updated macros, fonts, etc. -\item [TEXMFHOME] The tree which users can use for their own individual - installations of additional or updated macros, fonts, etc. - The expansion of this variable dynamically adjusts for each user to - their own individual directory. -\item [TEXMFCONFIG] The tree used by the utilities - \verb+texconfig+, \verb+updmap+, and \verb+fmtutil+ to store modified - configuration data. Under \envname{TEXMFHOME} by default. -\item [TEXMFSYSCONFIG] The tree used by the utilities - \verb+texconfig-sys+, \verb+updmap-sys+, and \verb+fmtutil-sys+ to - store modified configuration data. -\item [TEXMFVAR] The tree used by \verb+texconfig+, \verb+updmap+ and - \verb+fmtutil+ to store (cached) runtime data such as format files and - generated map files. Under \envname{TEXMFHOME} by default. -\item [TEXMFSYSVAR] The tree used by \verb+texconfig-sys+, - \verb+updmap-sys+ and \verb+fmtutil-sys+, and also by \verb+tlmgr+, to - store (cached) runtime data such as format files and generated map files. -\end{ttdescription} - -\noindent -The default layout is: -\begin{description} - \item[system-wide root] can span multiple \TL{} releases: - \begin{ttdescription} - \item[2007] A previous release. - \begin{ttdescription} - \item [...] - \end{ttdescription} - \item[2008] The current release. - \begin{ttdescription} - \item [bin] ~ - \begin{ttdescription} - \item [i386-linux] \GNU/Linux binaries - \item [...] - \item [universal-darwin] \MacOSX binaries - \item [win32] Windows binaries - \end{ttdescription} - \item [texmf] This is \envname{TEXMFMAIN}. - \item [texmf-dist] \envname{TEXMFDIST} - \item [texmf-doc] \envname{TEXMFDOC} - \item [texmf-var] \envname{TEXMFSYSVAR} - \item [texmf-config] \envname{TEXMFSYSCONFIG} - \end{ttdescription} - \item [texmf-local] \envname{TEXMFLOCAL}, intended to be - retained from release to release. - \end{ttdescription} - \item[user's home] (\texttt{\$HOME} or - \texttt{\%USERPROFILE\%}) - \begin{ttdescription} - \item[.texlive2007] Privately generated and configuration data - for a previous release. - \item[.texlive2008] Privately generated and configuration data - for the current release. - \begin{ttdescription} - \item [texmf-var] \envname{TEXMFVAR} - \item [texmf-config] \envname{TEXMFCONFIG} - \end{ttdescription} - \item[texmf] \envname{TEXMFHOME} Personal macros. - \textit{etc.} - \end{ttdescription} -\end{description} - - -\subsection{Extensions to \protect\TeX} -\label{sec:tex-extensions} - -\TeX{} itself is frozen, apart from rare bug fixes. It is still present -in \TL\ as the program \prog{tex}, and will remain so in the -foreseeable future. \TL{} contains several extended versions of \TeX: - -\begin{description} - -\item [\eTeX] adds a set of new primitives -\label{text:etex} (related to macro expansion, character scanning, -classes of marks, additional debugging features, and more) and the -\TeXXeT{} extensions for bidirectional typesetting. In default mode, -\eTeX{} is 100\% compatible with ordinary \TeX. See -\OnCD{texmf-dist/doc/etex/base/etex_man.pdf}. - -\item [pdf\TeX] builds on the \eTeX\ extensions, adding support for -writing \acro{PDF} output as well as \dvi{}. This is the program -invoked for most formats, e.g., \prog{etex}, \prog{latex}, -\prog{pdflatex}. See \url{http://www.pdftex.org/}. -\OnCD{texmf-dist/doc/pdftex/manual/pdftex-a.pdf} for the manual, and -\OnCD{texmf-dist/doc/pdftex/manual/samplepdf/samplepdf.tex} for example usage -of some of its features. - -\item [Lua\TeX] is the designated successor of pdf\TeX, with which it -is intended to be backward-compatible. It should also supersede Aleph, -see below. The incorporated Lua interpreter (see -\url{http://www.lua.org/}) enables elegant solutions for many thorny -\TeX{} problems. When called as \filename{texlua}, it functions as a -standalone Lua interpreter, and is already used as such within \TL. See -\url{http://www.luatex.org/} and -\OnCD{texmf-dist/doc/luatex/luatexref-t.pdf}. - -\item [\XeTeX] adds support for Unicode input and OpenType- and system -fonts, implemented using standard third-party libraries. See -\url{http://scripts.sil.org/xetex}. - -\item [\OMEGA\ (Omega)] is based on Unicode (16-bit characters), thus -supports working with almost all the world's scripts simultaneously. It -also supports so-called `\OMEGA{} Translation Processes' (\acro{OTP}s), -for performing complex transformations on arbitrary input. See -\OnCD{texmf-dist/doc/omega/base/doc-1.8.tex} (not completely up-to-date). - -\item [Aleph] combines the \OMEGA\ and \eTeX\ extensions. -See \OnCD{texmf-dist/doc/aleph/base} for some minimal documentation. - -\end{description} - - -\subsection{Other notable programs in \protect\TL} - -Here are a few other commonly-used programs included in \TL{}: - -\begin{cmddescription} - -\item [bibtex] bibliography support. - -\item [makeindex] index support. - -\item [dvips] convert \dvi{} to \PS{}. - -\item [xdvi] \dvi{} previewer for the X Window System. - -\item [dvilj] \dvi{} drive for the HP LaserJet family. - -\item [dv2dt, dt2dv] convert \dvi{} to/from plain text. - -\item [dviconcat, dviselect] cut and paste pages -from \dvi{} files. - -\item [dvipdfmx] convert \dvi{} to \acro{PDF}, an alternative approach -to pdf\TeX\ (mentioned above). See the \pkgname{ps4pdf} and -\pkgname{pdftricks} packages for still more alternatives. - -\item [psselect, psnup, \ldots] \PS{} -utilities. - -\item [lacheck] \LaTeX{} syntax checker. - -\item [texexec, texmfstart] Con\TeX{}t and \acro{PDF} processor. - -\item [tex4ht] \TeX{} to \acro{HTML} (and \acro{XML} and more) converter. - -\end{cmddescription} - - -\subsection{Fonts in \protect\TL} -\label{sec:tl-fonts} - -\TL{} comes with many high-quality scalable fonts. See -\url{http://tug.org/fonts} and -\OnCD{texmf-doc/doc/english/free-math-font-survey}. - - - -\section{Installation} -\label{sec:install} - -\subsection{Starting the installer} -\label{sec:inst-start} - -To start with, get the \TK{} \DVD{} or download the \TL{} net installer, -and locate the installer script: \filename{install-tl} for Unix, -\filename{install-tl.bat} for Windows. - -\begin{description} -\item [Net installer:] Download from \CTAN, under -\dirname{systems/texlive/tlnet}; the url -\url{http://mirror.ctan.org/systems/texlive/tlnet} will automatically -redirect to a nearby, up-to-date, mirror. You can retrieve either -\filename{install-tl.zip} which can be used under Unix and Windows and -\filename{install-unx.tar.gz} which is considerably smaller, for Unix -only. After unpacking, \filename{install-tl} and -\filename{install-tl.bat} will be in the \dirname{install-tl} -subdirectory. - -\item [\TeX{} Collection \DVD:] go to its \dirname{texlive} -subdirectory. Under Windows, the installer should start automatically -when you insert the \DVD. You can get the \DVD\ by becoming a member of -a \TeX\ user group (highly recommended, -\url{http://tug.org/usergroups.html}), or purchasing it separately -(\url{http://tug.org/store}), or burning your own from the \ISO\ -image (\url{http://tug.org/texlive/acquire.html}). - -\end{description} -The following sections explain in more detail. - -\subsubsection{Unix} - -\begin{figure}[tb] -\begin{boxedverbatim} -======================> TeX Live installation procedure <===================== - -=======> Note: Letters/digits in indicate menu items <======= -=======> for commands or configurable options <======= - - - Detected platform: Intel x86 with GNU/Linux - - binary systems: 1 out of 16 - - Installation scheme (scheme-full) - - Customizing installation scheme: - standard collections - language collections - 83 collections out of 84, disk space required: 1666 MB - - directories: - TEXDIR (the main TeX directory): - !! default location: /usr/local/texlive/2008 - !! is not writable, please select a different one! - TEXMFLOCAL (directory for site-wide local files): - /usr/local/texlive/texmf-local - TEXMFSYSVAR (directory for variable and automatically generated data): - /usr/local/texlive/2008/texmf-var - TEXMFSYSCONFIG (directory for local config): - /usr/local/texlive/2008/texmf-config - TEXMFHOME (directory for user-specific files): - ~/texmf - - options: - [ ] use letter size instead of A4 by default - [X] create all format files - [X] install macro/font doc tree - [X] install macro/font source tree - [ ] create symlinks in standard directories - - Install for running from DVD - -Other actions: - start installation to HD - help - quit - -Enter command: -\end{boxedverbatim} -\caption{Main text installer screen (\GNU/Linux)}\label{fig:text-main} -\end{figure} - -\begin{figure}[tb] -\tlpng{install-w32-main}{\linewidth} -\caption{Main \GUI{} installer screen (Windows)}\label{fig:gui-main} -\end{figure} - -\noindent -Below, \texttt{>} denotes the shell prompt; user input is -\Ucom{\texttt{bold}}. -Starting in a terminal window on a Unix-compatible system, the simplest -way: -\begin{alltt} -> \Ucom{cd /path/to/installer} -> \Ucom{perl install-tl} -\end{alltt} -(Or you can invoke \Ucom{perl /path/to/installer/install-tl}, or -\Ucom{./install-tl} if it stayed executable, etc.; we won't repeat all -these variations.) - -To install in \GUI\ mode (you'll need the \dirname{Perl/TK} module), use: -\begin{alltt} -> \Ucom{perl install-tl -gui} -\end{alltt} - -For a complete listing of the various options: -\begin{alltt} -> \Ucom{perl install-tl -help} -\end{alltt} - -\textbf{Warning about Unix permissions:} Your \code{umask} at the time -of installation will be respected by the \TL{} installer. Therefore, if -you want your installation to be usable by users other than you, make -sure your setting is sufficiently permissive, for instance, \code{umask -002}. For more information about \code{umask}, consult your system -documentation. - - -\subsubsection{Mac\,OS\,X} - -As mentioned in section~\ref{sec:tl-coll-dists}, a separate distribution -is prepared for \MacOSX, named Mac\TeX\ (\url{http://tug.org/mactex}). -We recommend using the native Mac\TeX\ installer instead of the \TL\ -installer on \MacOSX, because the native installer can make a few -Mac-specific adjustments, in particular to allow easily switching -between the various \TeX\ distributions for \MacOSX\ (Mac\TeX, gw\TeX, -Fink, MacPorts, \ldots). - -Mac\TeX\ is firmly based on \TL, and the main \TeX\ trees are precisely -the same. It does add a few extra folders with Mac-specific -documentation and applications. - - -\subsubsection{Windows} - -If you are using the net installer, or the \DVD\ installer failed to -start automatically, double-click \filename{install-tl.bat}. - -You can also start the installer from the command-prompt. Below, -\texttt{>} denotes the prompt; user input is \Ucom{\texttt{bold}}. If -you are in the installer directory, run just: -\begin{alltt} -> \Ucom{install-tl} -\end{alltt} - -Or you can invoke it with an absolute location, such as: -\begin{alltt} -> \Ucom{D:\bs{}texlive\bs{}install-tl} -\end{alltt} -for the \TK\ \DVD, supposing that \dirname{D:} is the optical drive. - -To install in text mode, use: -\begin{alltt} -> \Ucom{install-tl -no-gui} -\end{alltt} - -For a complete listing of the various options: -\begin{alltt} -> \Ucom{install-tl -help} -\end{alltt} - -\subsubsection{The text installer} - -Figure~\ref{fig:text-main} displays the main text mode screen under -Unix. - -This is only a command-line installer; there is no cursor support at -all. For instance, you cannot tab around checkboxes or input fields. -You just type something (case-sensitive) at the prompt and press the -Enter key, and then the entire terminal screen will be rewritten, with -adjusted content. - -The text installer interface is this primitive for a reason: it -is designed to run on as many platforms as possible, even with a -very barebones Perl (for Windows, a Perl subset is included). - -\subsubsection{The graphical installer} - -Figure~\ref{fig:gui-main} displays the graphical installer under -Windows. Most differences in available options are due to this -screenshot being from Windows, and the previous text screen being -from \GNU/Linux. - -\subsection{Running the installer} -\label{sec:runinstall} - -The installer is intended to be mostly self-explanatory. Still, a few -quick notes about the various options and submenus: - -\subsubsection{Binary systems menu (Unix only)} -\label{sec:binary} - -\begin{figure}[tbh] -\begin{boxedverbatim} -Available sets of binaries: -=============================================================================== - - a [ ] alpha-linux DEC Alpha with GNU/Linux - b [ ] amd64-freebsd x86_64 with FreeBSD - c [ ] hppa-hpux HP-UX - d [ ] i386-freebsd Intel x86 with FreeBSD - e [X] i386-linux Intel x86 with GNU/Linux - f [ ] i386-openbsd Intel x86 with OpenBSD - g [ ] i386-solaris Intel x86 with Sun Solaris - h [ ] mips-irix SGI IRIX - i [ ] powerpc-aix PowerPC with AIX - j [ ] powerpc-linux PowerPC with GNU/Linux - k [ ] sparc-linux Sparc with GNU/Linux - l [ ] sparc-solaris Sparc with Solaris - m [ ] universal-darwin universal binaries for MacOSX/Darwin - o [ ] win32 Windows - p [ ] x86_64-linux x86_64 with GNU/Linux -\end{boxedverbatim} -\caption{Binaries menu}\label{fig:bin-text} -\end{figure} - -Figure~\ref{fig:bin-text} displays the text mode binaries menu. By -default, only the binaries for your current platform will be installed. -From this menu, you can select installation of binaries for other -architectures as well. This can be useful if you are sharing a \TeX\ -tree across a network of heterogenous machines, or for a dual-boot -system. - -\subsubsection{Selecting what is going to be installed} -\label{sec:components} - -\begin{figure}[tbh] -\begin{boxedverbatim} -Select a scheme: -=============================================================================== - - a [ ] TeX Live basic scheme - b [ ] TeX Live scheme for ConTeXt - c [X] TeX Live full scheme - d [ ] GUST TeX Live scheme - e [ ] GUTenberg TeX Live scheme - f [ ] TeX Live medium scheme - g [ ] TeX Live minimal scheme - h [ ] TeX Live for Omega users - i [ ] teTeX scheme - j [ ] XML typesetting scheme -\end{boxedverbatim} -\caption{Scheme menu}\label{fig:scheme-text} -\end{figure} - -Figure~\ref{fig:scheme-text} displays the \TL\ scheme menu; from here, -you choose a ``scheme'', which is an overall set of package collections. -The default \optname{full} scheme installs everything available, but you -can also choose the \optname{basic} scheme for a small system, -\optname{minimal} for testing purposes, and \optname{medium} or -\optname{teTeX} to get something in between. There are also various -specialized and country-specific schemes. - -\begin{figure}[tbh] -\tlpng{stdcoll}{.7\linewidth} -\caption{Collections menu (Linux)}\label{fig:collections-gui} -\end{figure} - -You can refine your scheme selection with the `standard collections' and -`language collections' menus (figure~\ref{fig:collections-gui}, shown in -\GUI\ mode for a change). - -Collections are one level more detailed than schemes\Dash in essence, a -scheme consists of several collections, a collection consists of one or -more packages, and a package (the lowest level grouping in \TL) contains -the actual \TeX\ macro files, font files, and so on. - -If you want more control than the collection menus provide, you can use -the \prog{tlmgr} program after installation (see -section~\ref{sec:tlmgr}); using that, you can control the installation -at the package level. - -\subsubsection{Directories} -\label{sec:directories} - -The default layout is described in section~\ref{sec:texmftrees}, -\p.\pageref{sec:texmftrees}. The default location of -\dirname{TEXDIR} is different between Windows -(|%PROGRAMFILES%\texlive\2008|) and Unix -(\dirname{/usr/local/texlive/2008}). - -The main reason to change this default is if you lack write permission -for the default location. You don't have to be root or adminstrator to -install \TL, but you do need write access to the target directory. - -A logical alternate choice is a directory under your home directory, -especially if you will be the sole user. Use -`|~|' to indicate this, as in `|~/texlive/2008|'. - -We recommend including the year in the name, to enable keeping different -releases of \TL{} side by side. (You may wish to make a -version-independent name such as \dirname{/usr/local/texlive-cur} via a -symbolic link, which you can then update after testing the new release.) - -Changing \dirname{TEXDIR} in the installer will also change -\dirname{TEXMFLOCAL}, \dirname{TEXMFSYSVAR} and -\dirname{TEXMFSYSCONFIG}. - -\dirname{TEXMFHOME} is the recommended location for personal -macro files or packages. The default value is |~/texmf|. In -contrast to \dirname{TEXDIR}, here a |~| is preserved in the -newly-written configuration files, since it usefully refers to the home -directory of each individual running \TeX. It expands to -\dirname{$HOME} on Unix and \verb|%USERPROFILE%| on Windows. - -\subsubsection{Options} -\label{sec:options} - -\begin{figure}[tbh] -\begin{boxedverbatim} -

use letter size instead of A4 by default: [ ] - create all format files: [X] - install font/macro doc tree: [X] - install font/macro source tree: [X] - create symlinks in standard directories: [ ] - binaries to: - manpages to: - info to: -\end{boxedverbatim} -\caption{Options menu (Unix)}\label{fig:options-text} -\end{figure} - -Figure~\ref{fig:options-text} displays the text mode options menu. -Three of the options here need mentioning: - -\begin{description} -\item[use letter size instead of A4 by default:] The usual default paper - size selection. Of course, individual documents can specify a specific - paper size, if desired. - -\item[create all format files:] Although unnecessary format files - take time to generate and disk space to store, it is still recommended - to leave this option checked: if you don't, then format files will be - generated in people's private \dirname{TEXMFVAR} tree as they are - needed. In that location, they will not be updated automatically if - (say) binaries or hyphenation patterns are updated in the - installation, and thus could end up with incompatible format files. - -\item[create symlinks in standard directories] (Unix only): - This option bypasses the need to change environment - variables. Without this option, \TL{} directories have to be added - to \envname{PATH}, \envname{MANPATH} and \envname{INFOPATH}. You will - need write permissions to the target directories. It is not - advisable to overwrite a \TeX\ system that came with your system - with this option. It is intended primarily for creating the links - in standard directories that are known to users, such as - \dirname{/usr/local/bin}, which don't already contain any - \TeX\ files. -\end{description} - -Now when all these settings are to your liking, you can type `I' to -start the installation process. When it is done, skip to -section~\ref{sec:postinstall} to read what else needs to be done, if -anything. - -\subsubsection{Set up for running from DVD{} (text mode only)} -\label{sec:fromdvd} - -Type `|V|' to select this option. This changes the main menu into something -like figure~\ref{fig:main-fromdvd}. -\begin{figure}[tbh] -\begin{boxedverbatim} -======================> TeX Live installation procedure <===================== - -=======> Note: Letters/digits in indicate menu items <======= -=======> for commands or configurable options <======= - - directories: - TEXDIRW (Writable root): - !! default location: /usr/local/texlive/2008 - !! is not writable, please select a different one! - TEXMFLOCAL (directory for site-wide local files): - /usr/local/texlive/texmf-local - TEXMFSYSVAR (directory for variable and automatically generated data): - /usr/local/texlive/2008/texmf-var - TEXMFSYSCONFIG (directory for local config): - /usr/local/texlive/2008/texmf-config - TEXMFHOME (directory for user-specific files): - ~/texmf - - options: - [ ] use letter size instead of A4 by default - [X] create all format files - - set up for installing to hard disk - -Other actions: - start installation for running from DVD - help - quit -\end{boxedverbatim} -\caption{The main menu with \optname{from DVD} - set}\label{fig:main-fromdvd} -\end{figure} - -Note the changes: all options about what to install have -disappeared, and the directories section now talks about -\dirname{TEXDIRW} or writable root. The symlinks option has also -disappeared. - -The installer will still create various directories and -configuration files, but won't copy \dirname{texmf}, -\dirname{texmf-dist} or \dirname{texmf-doc} to hard disk. - -Post-install configuration for Unix will be slightly more complicated, -because now the directory layout deviates from the default; see -section~\ref{sec:postinstall}. - -Due to time constraints, this option didn't make it into the \GUI{} -installer, but it is available both for Unix and for -Windows. Windows users have to start the installer from a command -prompt, see section~\ref{sec:cmdline}. - -Section \ref{sec:portable-unix} describes a more strictly portable -way to run \TL, which doesn't make or require changes in the -system's configuration, but doesn't allow any configuration either. - -\subsection{Command-line install options} -\label{sec:cmdline} - -Type -\begin{alltt} -> \Ucom{install-tl -help} -\end{alltt} -for a listing of command-line options. Either |-| or |--| can be used -to introduce option names. These are the more -interesting ones: - -\begin{ttdescription} -\item[-gui] If possible, use the \GUI{} installer. This requires the - Perl/Tk module (\url{http://tug.org/texlive/distro.html#perltk}); - if Perl/Tk is not available, installation continues in text mode. -\item[-no-gui] Force using the text mode installer, even under - Windows; you'll need this if you want a `from \DVD' installation, - since that is not available in \GUI{} mode. -\item[-lang {\sl LL}] Specify the installer interface - language as its standard two-letter code \textsl{LL}. Currently - supported languages: English (\texttt{en}, default), German - (\texttt{de}), French (\texttt{fr}), Dutch (\texttt{nl}), Polish - (\texttt{pl}), Slovenian (\texttt{sl}) and Vietnamese - (\texttt{vi}). The installer tries to determine the right language - itself but if it fails, or if the right language is not available, - then it uses English as a fallback. -\item[-profile {\sl profile}] The installer always writes a file - \filename{texlive.profile} to the \dirname{2008/tlpkg}- or - \dirname{tlpkg} subdirectory of your installation. This option tells - the installer to re-use such a profile file. Here's an excerpt: - \begin{fverbatim} -# texlive.profile written on Wed Jul 9 16:13:44 2008 UTC -# It will NOT be updated and reflects only the -# installation profile at installation time. -selected_scheme scheme-basic -TEXDIR /usr/local/texlive/2008 -TEXDIRW /usr/local/texlive/2008 -... -TEXMFSYSVAR /usr/local/texlive/2008/texmf-var -collection-basic 1 -... -option_symlinks 0 - \end{fverbatim} - Thus, using this option you can install in batch mode on - subsequent systems, reproducing the choices you made for the - original installation. -\item [-location {\sl url/path}] Specify a non-default source for - packages; see below. -\end{ttdescription} - -\subsubsection{The \optname{location} parameter} -\label{sec:location} - -The location value can be a url starting with \texttt{ftp:}, -\texttt{http:}, or \texttt{file:/} url, or a plain path. If the given -argument is on a local drive (either a path or a \texttt{file:/} url), -the installation type (compressed or live) is automatically determined: -if an \dirname{archive} subdirectory with \filename{.tar.lzma} files is -found then it will be used, even if uncompressed files are available as -well. - -When giving an \texttt{http:} or \texttt{ftp:} location, trailing -`\texttt{/}' characters and/or a trailing `\texttt{/tlpkg}' component -are ignored. For example, you could choose a particular \CTAN\ mirror -with something like: -\url{http://ctan.example.org/tex-archive/texlive/tlnet/2008}, -substituting of course a proper hostname and its particular top-level -\CTAN\ path (the list of \CTAN\ mirrors is maintained at -\url{http://ctan.org/mirrors}) for |ctan.example.org/tex-archive|. The -default is to pick a mirror automatically, using -\url{http://mirror.ctan.org}; in any case, the chosen host is used for -the entire download. - - -\subsection{Post-install actions} -\label{sec:postinstall} - -Some post-install may be required. - -\subsubsection{Windows} - -But on Windows, the installer takes care of everything. - -\subsubsection{If symlinks were created} - -If you elected to create symlinks in standard directories (mentioned in -section~\ref{sec:options}), then there is no need to edit environment -variables. - -\subsubsection{Environment variables for Unix} -\label{sec:env} - -The directory of the binaries for your platform must be added to -the search path. Each supported platform has its own subdirectory -under \dirname{TEXDIR/bin}. See figure~\ref{fig:bin-text} for the -list of subdirectories and corresponding platforms. - -You can also add the documentation man and Info directories to their -respective search paths, if you want the system tools to find them. - -For Bourne-compatible shells such as \prog{bash}, and using Intel x86 -GNU/Linux and a default directory setup as an example, the file to edit -might be \filename{$HOME/.profile} (or another file sourced by -\filename{.profile}, and the lines to add would look like this: - -\begin{sverbatim} -PATH=/usr/local/texlive/2008/bin/i386-linux:$PATH; export PATH -MANPATH=/usr/local/texlive/2008/texmf/doc/man:$MANPATH; export MANPATH -INFOPATH=/usr/local/texlive/2008/texmf/doc/info:$INFOPATH; export INFOPATH -\end{sverbatim} - -For csh or tcsh, the file to edit is typically \filename{$HOME/.cshrc}, and -the lines to add might look like: - -\begin{sverbatim} -setenv PATH /usr/local/texlive/2008/bin/i386-linux:$PATH -setenv MANPATH /usr/local/texlive/2008/texmf/doc/man:$MANPATH -setenv INFOPATH /usr/local/texlive/2008/texmf/doc/info:$INFOPATH -\end{sverbatim} - -Of course, you may well already have settings somewhere in your ``dot'' -files, and so then the \TL\ directories should simply be merged in as -appropriate. - -\subsubsection{Environment variables: global configuration} -\label{sec:envglobal} - -If you want to make these changes globally, or for a user newly added to -the system, then you are on your own; there is just too much variation -between systems in how and where these things are configured. - -Our two hints are: 1)~you may want to check for a file -\filename{/etc/manpath.config} and, if present, add lines such as - -\begin{sverbatim} -MANPATH_MAP /usr/local/texlive/2008/bin/i386-linux \ - /usr/local/texlive/2008/texmf/doc/man -\end{sverbatim} - -And 2)~check for a file \filename{/etc/environment} which may define the -search path and other default environment variables. - - -\subsubsection{When running from DVD} - -Normally, a \TL{} program consults a file \filename{texmf.cnf} for the -location of the various trees. It looks for this file in a series of -locations relative to its own location. However, this scheme breaks down -when a program is run from \DVD{}: the \DVD{} is read-only. Some of the -paths to be recorded in \filename{texmf.cnf} are only known at -installation time, so this file cannot be on the \DVD{} and must be -placed somewhere else. This makes it necessary to define an environment -\envname{TEXMFCNF} variable which tells \TL{} programs in what directory -to find this \filename{texmf.cnf}. It is also still necessary to modify -the \envname{PATH} environment variable, as described before. - -At the end of the installation, the installer should have printed a -message giving the value to which \envname{TEXMFCNF} should be set. In -case you missed it: this value is \dirname{$TEXMFSYSVAR/web2c}. For the -default, \dirname{/usr/local/texlive/2008/texmf-var/web2c}, you need the -lines -\begin{sverbatim} -TEXMFCNF=/usr/local/texlive/2008/texmf-var/web2c; export TEXMFCNF -\end{sverbatim} -or, for [t]csh: -\begin{sverbatim} -setenv TEXMFCNF /usr/local/texlive/2008/texmf-var/web2c -\end{sverbatim} - - -\subsubsection{\ConTeXt{} Mark IV} - -The `old' \ConTeXt{} should run out of the box. The new `Mark IV' -\ConTeXt{} will require manual setup; see -\url{http://wiki.contextgarden.net/Running_Mark_IV}. - - -\subsubsection{Integrating local and personal macros} -\label{sec:local-personal-macros} - -This is already mentioned implicitly in section~\ref{sec:texmftrees}: -\dirname{TEXMFLOCAL} (by default, -\dirname{/usr/local/texlive/texmf-local} or -\verb|C:\Program Files\texlive\texmf-local|) - -is intended for system-wide local fonts and macros; and -\dirname{TEXMFHOME} (by default, \dirname{$HOME/texmf} or -\verb|%USERPROFILE%\texmf|), is for personal fonts and macros. These -directories are intended to stick around from release to release, and -have their content seen automatically by a new \TL{} release. -Therefore, it is best to refrain from changing the definition of -\dirname{TEXMFLOCAL} to be too far away from the main \TL{} directory, -or you will need to manually change future releases. - -For both trees, files should be placed in their proper subdirectories; -see \url{http://tug.org/tds} or consult -\filename{texmf/web2c/texmf.cnf}. For instance, a \LaTeX{} class file or -package should be placed in \dirname{TEXMFLOCAL/tex/latex} or -\dirname{TEXMFHOME/tex/latex}, or a subdirectory thereof. - -\dirname{TEXMFLOCAL} requires an up-to-date filename database, or files -will not be found. You can update it with the command -\cmdname{mktexlsr} or use the `Reinit file database' button on the -configuration tab of \prog{tlmgr} in \GUI\ mode. - -\subsubsection{Integrating third-party fonts} - -This is unfortunately a very complicated and messy topic. Forget -about it unless you really know your way around blindfolded in a -\TeX{} installation. Don't forget to check first what you get for -free: see section~\ref{sec:tl-fonts}. - -A possible alternative is to use \XeTeX (see -section~\ref{sec:tex-extensions}), which lets you use operating system -fonts without any installation in \TeX. - - -\subsection{Testing the installation} -\label{sec:test-install} - -After installing \TL{} as best you can, you naturally want to test -it out, so you can start creating beautiful documents and\slash or fonts. - -This section gives some basic procedures for testing that the new system -is functional. We give Unix commands here; under \MacOSX{} and Windows, -you're more likely to run the tests through a graphical interface, but -the principles are the same. - -\begin{enumerate} - -\item Make sure that you can run the \cmdname{tex} program in the first -place: - -\begin{alltt} -> \Ucom{tex -{}-version} -TeX 3.1415926 (Web2C 7.5.7) -kpathsea version 3.5.7 -... -\end{alltt} -If this comes back with `command not found' instead of version and -copyright information, or with an older version, most likely you don't -have the correct \dirname{bin} subdirectory in your \envname{PATH}. See -the environment-setting information on \p.\pageref{sec:env}. - -\item Process a basic \LaTeX{} file: -\begin{alltt} -> \Ucom{latex sample2e.tex} -This is pdfeTeXk, Version 3.1415926... -... -Output written on sample2e.dvi (3 pages, 7484 bytes). -Transcript written on sample2e.log. -\end{alltt} -If this fails to find \filename{sample2e.tex} or other files, most -likely you have interference from old environment variables or -configuration files; we recommend unsetting all \TeX-related environment -variables for a start. (For a deep analysis, you can ask \TeX{} to -report on exactly what it is searching for, and finding; see ``Debugging -actions'' on page~\pageref{sec:debugging}.) - -\item Preview the result online: -\begin{alltt} -> \Ucom{xdvi sample2e.dvi} -\end{alltt} -(Under Windows, the analogous command is \cmdname{dviout}.) You should -see a new window with a nice document explaining some of the basics of -\LaTeX{}. (Well worth reading, by the way if you're new to the system.) -You do have to be running under X for \cmdname{xdvi} to work; if you're -not, or your \envname{DISPLAY} environment variable is set incorrectly, -you'll get an error \samp{Can't open display}. - -\item Create a \PS{} file for printing or display: -\begin{alltt} -> \Ucom{dvips sample2e.dvi -o sample2e.ps} -\end{alltt} - -\item Create a \acro{PDF} file instead of \dvi{}; this processes the -\filename{.tex} file and writes \acro{PDF} directly: -\begin{alltt} -> \Ucom{pdflatex sample2e.tex} -\end{alltt} - -\item Preview the \acro{PDF} file: -\begin{alltt} -> \Ucom{gv sample2e.pdf} -\textrm{or:} -> \Ucom{xpdf sample2e.pdf} -\end{alltt} -Unfortunately neither \cmdname{gv} nor \cmdname{xpdf} are currently -included in \TL{}, so you must install them separately. See -\url{http://www.gnu.org/software/gv} and -\url{http://www.foolabs.com/xpdf}, respectively. (There are plenty of -other \acro{PDF} viewers, too.) - -\item Standard test files you may find useful in addition to -\filename{sample2e.tex}: - -\begin{ttdescription} -\item [small2e.tex] A simpler document than \filename{sample2e}, to -reduce the input size if you're having troubles. -\item [testpage.tex] Test if your printer introduces any offsets. -\item [nfssfont.tex] For printing font tables and tests. -\item [testfont.tex] Also for font tables, but using plain \TeX{}. -\item [story.tex] The most canonical (plain) \TeX{} test file of all. -You must type \samp{\bs bye} to the \code{*} prompt after \samp{tex -story.tex}. -\end{ttdescription} - -\end{enumerate} - -If you are new to \TeX{}, or otherwise need help with actually writing -\TeX{} or \LaTeX{} documents, please visit -\url{http://tug.org/begin.html} for some introductory resources. - - -\section{Network installations} -\label{sec:netinstall} - -\TL{} has been designed to be shared between different users, and even -different systems on a network. With a standard directory layout, no -hard paths are configured: the locations for files needed by \TL{} -programs are defined relative to the places of those programs. You can -see this at work in the configuration file -\filename{$TEXMFMAIN/web2c/texmf.cnf}, which contains lines such as -\begin{sverbatim} -TEXMFMAIN = $SELFAUTOPARENT/texmf -... -TEXMFLOCAL = $SELFAUTOPARENT/../texmf-local -\end{sverbatim} -This means that other systems or other users merely need to add the -directory for \TL{} binaries for their platform to their search path. - -By the same token, you can also install \TL{} locally and then move -the entire hierarchy afterwards to a network location. - -Of course, Windows users have different expectations. The directory -\dirname{texmf-doc/source/texlive/texlive-common/w32client} contains a -sample script \filename{install-w32client} which creates settings and -menu shortcuts for using an existing \TL{} installation on a -\acro{LAN}. It is to be invoked through a batch file -\filename{install-w32client.bat} in the same directory. - -You can read more about \TL{} configuration and path searching in -section~\ref{sec:kpathsea}. - -\section{Maximally portable \protect\TL{} on DVD and USB} -\label{sec:portable-unix} - -The `running from \DVD{}' option described in -section~\ref{sec:fromdvd} is fine for your own system, but if you -are a guest on somebody else's system then you would probably like -something with minimal side effects. - -In the root of the \TL{} \DVD, or the \dirname{texlive} subdirectory of -the \TK{} \DVD, are a \filename{tl-portable} script (Unix) and a -\filename{tl-portable.bat} batchfile (Windows) which start up a -secondary shell\slash command prompt with environment settings suitable -for directly accessing the \TL{} on the \DVD. - -When it runs for the first time, some files will be generated in a -directory \dirname{~/.tlportable2008}, which will take a little time. -On subsequent runs, though, it will start almost instantaneously. - -The rest of the system will be unaware of \TL. If you want your editor -to be aware of this \TL, then you can start it from a second, parallel, -such \filename{tl-portable} session. - -You can also use \filename{tl-portable} to run \TL{} on a -\acro{USB} stick. In this case, copy all the top-level files and -the contents of the \dirname{bin}, \dirname{texmf}, -\dirname{texmf-dist}, and \dirname{tlpkg} directories (at least) to -the stick. This may take quite a while! If you are copying to a -\acro{FAT}32-formatted \acro{USB} stick, make sure to dereference -symbolic links (\code{cp -L}). A \dirname{texmf-local} directory on -the stick will also be found and used. - -Then run \filename{tl-portable} from the root of the stick, as above. -In this case, the script will notice that the stick is writable and use -it for generated files. You could burn the resulting contents of the -stick back to \DVD{} if that is more convenient to (for example) give to -others. - - -\section{\cmdname{tlmgr}: Managing your installation} -\label{sec:tlmgr} - -\begin{figure}[tb] -\tlpng{tlmgr-gui}{\linewidth} -\caption{\prog{tlmgr} in \GUI\ mode. The list of - packages/collections/schemes only shows up after clicking the - `Load' button.}\label{fig:tlmgr-gui} -\end{figure} - -\begin{figure}[tb] -\tlpng{tlmgr-config}{\linewidth} -\caption{\texttt{tlmgr} in GUI mode: Configuration tab}\label{fig:tlmgr-config} -\end{figure} - -The installer installs a program named \prog{tlmgr} for managing \TL{} -after the initial installation. The programs \prog{updmap}, -\prog{fmtutil} and \prog{texconfig} are still included and will be -retained in the future, but \prog{tlmgr} is now the preferred interface. -Its capabilities include: - -\begin{itemize*} -\item listing schemes, collections and packages; -\item installing, updating, backing up, restoring and uninstalling - individual packages, optionally taking dependencies into account; -\item searching for packages; -\item listing and adding architectures; -\item changing installation options such as paper size and source - location (see section~\ref{sec:location}). -\end{itemize*} -\textit{Warning:} \prog{tlmgr} has not been designed for or tested -with installations which run from \DVD. - -\subsection{\cmdname{tlmgr} GUI mode} -\prog{tlmgr} can be started in \GUI{} mode with -\begin{alltt} -> \Ucom{tlmgr -gui} -\end{alltt} -or in Windows via the Start menu: \texttt{Start}, \texttt{Programs}, -\texttt{TeX Live 2008}, \texttt{TeX Live Manager}. After clicking `Load' -it displays a list of available and installed packages\Dash the latter -prepended with `(i)'. This assumes of course that the installation -source is valid and reachable. - -Figure~\ref{fig:tlmgr-config} shows the configuration tab. - -\subsection{Sample \cmdname{tlmgr} command-line invocations} - -This example adds several packages, including a new `engine', from a -non-default location: - -\begin{alltt} -> \Ucom{tlmgr -location http://172.16.18.1/tldev install collection-xetex xkeyval} -\end{alltt} -It generates the following output: -\begin{fverbatim} -install: collection-xetex -install: arabxetex -install: euenc -install: bidi -install: fontspec -install: fontwrap -install: ifxetex -install: philokalia -install: polyglossia -install: xecyr -install: xecyr.i386-linux -install: xepersian -install: xetex -install: xetexconfig -install: xetex.i386-linux -running post install action for xetex -install: xetex-def -install: xetex-pstricks -install: xetexfontinfo -install: xltxtra -install: xunicode -install: xkeyval -running mktexlsr -mktexlsr: Updating /usr/local/texlive/2008/texmf/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-config/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-dist/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-doc/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/../texmf-local/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-var/ls-R... -mktexlsr: Done. -regenerating fmtutil.cnf -running fmtutil-sys --missing -... -Transcript written on xelatex.log. -fmtutil: /usr/local/texlive/2008/texmf-var/web2c/xetex/xelatex.fmt installed. -\end{fverbatim} -As you see, \prog{tlmgr} installs dependencies, and takes care of any -necessary post-install actions, including updating the filename database -and (re)generating formats. (Here we generated new formats for \XeTeX.) - -This example installs a new language. This also triggers format -regeneration: -\begin{alltt} -> \Ucom{tlmgr install collection-langdutch} -\end{alltt} -To describe a package: -\begin{alltt} -> \Ucom{tlmgr show collection-wintools} -\end{alltt} -which produces -\begin{fverbatim} -Package: collection-wintools -Category: Collection -ShortDesc: Windows support programs -LongDesc: Utilities for Windows, since they are not readily available there: - gzip, chktex, jpeg2ps, unzip, wget, xpdf. -Installed: Yes -\end{fverbatim} -Updating your entire installation to the latest versions available: -\begin{alltt} -> \Ucom{tlmgr update -all} -\end{alltt} -If this makes you nervous, first try -\begin{alltt} -> \Ucom{tlmgr update -all -dry-run} -\end{alltt} -or -\begin{alltt} -> \Ucom{tlmgr update -list} -\end{alltt} -For full documentation: -\begin{alltt} -> \Ucom{tlmgr -help} -\end{alltt} - - -\section{Notes on Windows} -\label{sec:windows} - -\TL\ has a single installer which runs on both Windows and Unix. This -was only possible by dropping support for older Windows versions, so -\TL\ can now be installed only on Windows 2000 and later. - - -\subsection{Windows-specific features} -\label{sec:winfeatures} - -Under Windows, the installer does some extra things: -\begin{description} -\item[Menus and shortcuts.] A new `\TL{}' submenu of the - Start menu is installed, which contains entries for some \GUI{} programs - (\prog{tlmgr}, \prog{texdoctk}, the PS\_View PostScript previewer) - and some documentation. PS\_View also gets a shortcut on the - desktop as a drag-and-drop target for PostScript files. -\item[Automatic setting of environment variables.] No manual - configuration steps are required. -\item[Uninstaller.] The installer creates an entry under `Add/Remove - Programs' for \TL. The uninstall tab of\prog{tlmgr} refers to - this. -\end{description} - -\subsection{Additional included software} - -\begin{figure}[tb] -\tlpng{psview}{.6\linewidth} -\caption{PS\_View: very high magnifications available!}\label{fig:psview} -\end{figure} - -To be complete, a \TL installation needs support packages that are not -commonly found on a Windows machine. \TL{} provides the missing -pieces: -\begin{description} -\item[Perl and Ghostscript.] Because of the importance of Perl and - Ghostscript, \TL{} includes `hidden' copies of these - programs. \TL{} programs that need them know where to find them, - but they don't betray their presence through environment variables - or registry settings. They aren't full-scale distributions, and - shouldn't interfere with any system installations of Perl or - Ghostscript. -\item[Command-line tools.] A number of Windows ports of common Unix - command-line programs are installed along with the usual \TL{} - binaries. These include \cmdname{gzip}, \cmdname{chktex}, - \cmdname{jpeg2ps}, \cmdname{unzip}, \cmdname{wget} and the - command-line utilities from the \cmdname{xpdf} suite. (The - \cmdname{xpdf} viewer itself is not available for Windows, but the - Sumatra \acro{PDF} viewer is based on it: - \url{http://blog.kowalczyk.info/software/sumatrapdf}.) -\item[\texttt{fc-cache}] helps \XeTeX{} to handle fonts more - efficiently. -\item[PS\_View.] Also installed is PS\_View, a new PostScript viewer - with a free license; see figure~\ref{fig:psview}. -\end{description} -\begin{description} -\item[The \texttt{support} directory,] already mentioned in - section~\ref{sec:tld}. This directory contains various programs - which can be useful in connection with \TeX, in particular a - number of \TeX-aware editors and \TeX{} frontends. The software in - this directory isn't covered by the installer. This directory also - contains the \cmdname{dviout} \dvi{} previewer; see the next section. -\end{description} - -\subsection{The Dviout previewer} - -This \TL{} release unfortunately doesn't offer a preinstalled \dvi{} -previewer for Windows. However, you can install \prog{dviout} by -Toshio Oshima from the \path{support/dviout/} directory, which -contains also a short \filename{README} describing how to install -and configure \prog{dviout} for \TL. Please read this carefully -before installation. - -At first, when you preview files with \cmdname{dviout}, it will create fonts, -because screen fonts were not installed. After a while, you will have created -most of the fonts you use, and you will rarely see the font-creation window. -More information can be found in the (very good) on-line help. - -\subsection{Links for additional downloadable software} - -Urls for some other tools you may consider installing: -\begin{description} -\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} -\item[Perl] \url{http://www.perl.org/} with - supplementary packages from \acro{CPAN}, \url{http://www.cpan.org/} -\item[ImageMagick] \url{http://www.imagemagick.com}, for graphics - processing and conversion -\item[NetPBM] \url{http://netpbm.sourceforge.net/}, also for graphics. - -\item[\TeX-oriented editors] There is a wide choice, and it is a matter of the - user's taste. Here is a selection, in no particular order: - \begin{itemize*} - \item \cmdname{GNU Emacs} is available natively under Windows, see - \url{http://www.gnu.org/software/emacs/windows/ntemacs.html}. - \item \cmdname{Emacs} with Auc\TeX\ for Windows is available in \TL's - \path{support} directory; its home page is - \url{http://www.gnu.org/software/auctex}. - \item \cmdname{WinShell} is available in \TL's \path|support| - directory; its home page is \url{http://www.winshell.de}. - \item \cmdname{WinEdt} is shareware available from - \url{http://www.winedt.com}. - \item \cmdname{Vim} is free software, available from - \url{http://www.vim.org}. - \item TeXnicCenter is free software, available from - \url{http://www.toolscenter.org} and in the pro\TeX{}t distribution. - \item \cmdname{LEd} is available from \url{http://www.ctan.org/support/LEd}. - \item \cmdname{SciTE} is available from - \url{http://www.scintilla.org/SciTE.html}. - \end{itemize*} -\end{description} - - -\subsection{User Profile is Home} -\label{sec:winhome} - -The Windows counterpart of a Unix home directory is the -\verb|%USERPROFILE%| directory. Under Windows XP and Windows 2000, this -is usually \verb|C:\Documents and Settings\|, and under -Windows Vista \verb|C:\Users\|. In the -\filename{texmf.cnf} file, and \KPS{} in general, \verb|~| will expand -appropriately on both Windows and Unix. - - -\subsection{The Windows registry} -\label{sec:registry} - -Windows stores nearly all configuration data in its registry. The -registry contains a set of hierarchically organized keys, with several -root keys. The most important ones for installation programs are -\path{HKEY_CURRENT_USER} and \path{HKEY_LOCAL_MACHINE}, \path{HKCU} and -\path{HKLM} in short. The \path{HKCU} part of the registry is in the -user's home directory (see section~\ref{sec:winhome}). \path{HKLM} is -normally in a subdirectory of the Windows directory. - -In some cases, system information could be obtained from environment -variables but for other information, for example the location of -shortcuts, it is necessary to consult the registry. Setting environment -variables permanently also requires registry access. - - -\subsection{Windows permissions} -\label{sec:winpermissions} - -In later versions of Windows, a distinction is made between regular -users and administrators, where only the latter have free access to the -entire operating system. In practice, though, you could better describe -these classes of users as unprivileged users and normal users: being an -administrator is the rule, not the exception. Nevertheless, we have made -an effort to make \TL{} installable without administrative privileges. - -If the user is an administrator, shortcuts are created for all users, -and the system environment is modified. Otherwise, shortcuts and menu -entries are created for the current user, and the user environment is -modified. Use the \optname{non-admin} option to \prog{install-tl} if -you prefer per-user settings even as an administrator. - -Regardless of administrator status, the default root of \TL{} proposed -by the installer is always under \verb|%PROGRAMFILES%|. The installer -always tests whether the root is writable for the current user. - -A problem may arise if the user is not an administrator and \TeX{} -already exists in the search path. Since the effective path consists of -the system path followed by the user path, the new \TL{} will never get -precedence. As a workaround, in this case the installer creates -shortcuts to the command-prompt in which the new \TL{} binary directory -is prepended to the local searchpath. The new \TL{} will be usable when -run in a command-line session started from such a shortcut. - - -\section{A user's guide to Web2C} - -\Webc{} is an integrated collection of \TeX-related programs: \TeX{} -itself, \MF{}, \MP, \BibTeX{}, etc. It is the heart of \TL{}. The home -page for \Webc{}, with the current manual and more, is -\url{http://tug.org/web2c}. - -A bit of history: The original implementation was by Tomas Rokicki who, -in 1987, developed a first \TeX{}-to-C system based on change files -under Unix, which were primarily the original work of Howard Trickey and -Pavel Curtis. Tim Morgan became the maintainer of the system, and -during this period the name changed to Web-to-C\@. In 1990, Karl Berry -took over the work, assisted by dozens of additional contributors, and -in 1997 he handed the baton to Olaf Weber, who returned it to Karl in -2006. - -The \Webc{} system runs on Unix, 32-bit Windows systems, \MacOSX{}, and -other operating systems. It uses Knuth's original sources for \TeX{} and -other basic programs written in the \web{} literate programming system -and translates them into C source code. The core \TeX{} programs -handled in this way are: - -\begin{cmddescription} -\item[bibtex] Maintaining bibliographies. -\item[dmp] \cmdname{troff} to MPX (\MP{} pictures). -\item[dvicopy] Expands virtual font references in \dvi{} files. -\item[dvitomp] \dvi{} to MPX (MetaPost pictures). -\item[dvitype] \dvi{} to human-readable text. -\item[gftodvi] Generic font proofsheets. -\item[gftopk] Generic to packed fonts. -\item[gftype] GF to human-readable text. -\item[makempx] \MP{} label typesetting. -\item[mf] Creating typeface families. -\item[mft] Prettyprinting \MF{} source. -\item[mpost] Creating technical diagrams. -\item[mpto] MetaPost label extraction. -\item[newer] Compare modification times. -\item[patgen] Creating hyphenation patterns. -\item[pktogf] Packed to generic fonts. -\item[pktype] PK to human-readable text. -\item[pltotf] Plain text property list to TFM. -\item[pooltype] Display \web{} pool files. -\item[tangle] \web{} to Pascal. -\item[tex] Typesetting. -\item[tftopl] TFM to plain text property list. -\item[vftovp] Virtual font to virtual property list. -\item[vptovf] Virtual property list to virtual font. -\item[weave] \web{} to \TeX. -\end{cmddescription} - -\noindent The precise functions and syntax of these programs are -described in the documentation of the individual packages and of \Webc{} -itself. However, knowing a few principles governing the whole family of -programs will help you take advantage of your \Webc{} installation. - -All programs honor these standard \GNU options: -\begin{ttdescription} -\item[-{}-help] print basic usage summary. -\item[-{}-verbose] print detailed progress report. -\item[-{}-version] print version information, then exit. -\end{ttdescription} - -For locating files the \Webc{} programs use the path searching library -\KPS{} (\url{http://tug.org/kpathsea}). This library uses a combination -of environment variables and a configuration files to optimize searching -the (huge) collection of \TeX{} files. \Webc{} can look at many -directory trees simultaneously, which is useful in maintaining \TeX's -standard distribution and local and personal extensions in distinct -trees. To speed up file searches, the root of each tree has a file -\file{ls-R}, containing an entry showing the name and relative pathname -for all files under that root. - - -\subsection{Kpathsea path searching} -\label{sec:kpathsea} - -Let us first describe the generic path searching mechanism of the \KPS{} -library. - -We call a \emph{search path} a colon- or semicolon\hyph sepa\-rated list -of \emph{path elements}, which are basically directory names. A -search path can come from (a combination of) many sources. To look up -a file \samp{my-file} along a path \samp{.:/dir}, \KPS{} checks each -element of the path in turn: first \file{./my-file}, then -\file{/dir/my-file}, returning the first match (or possibly all -matches). - -In order to adapt optimally to all operating systems' conventions, on -non-Unix systems \KPS{} can use filename separators different from -colon (\samp{:}) and slash (\samp{/}). - -To check a particular path element \var{p}, \KPS{} first checks if a -prebuilt database (see ``Filename data\-base'' on -page~\pageref{sec:filename-database}) applies to \var{p}, i.e., if the -database is in a directory that is a prefix of \var{p}. If so, the path -specification is matched against the contents of the database. - -If the database does not exist, or does not apply to this path -element, or contains no matches, the filesystem is searched (if this -was not forbidden by a specification starting with \samp{!!}\ and if -the file being searched for must exist). \KPS{} constructs the list -of directories that correspond to this path element, and then checks -in each for the file being sought. - -The ``file must exist'' condition comes into play with \samp{.vf} files and -input files read by \TeX's \cs{openin} command. Such files may not -exist (e.g., \file{cmr10.vf}), and so it would be wrong to search the -disk for them. Therefore, if you fail to update \file{ls-R} when you -install a new \samp{.vf} file, it will never be found. -Each path element is checked in turn: first the database, then the -disk. If a match is found, the search stops and the result is -returned. - -Although the simplest and most common path element is a directory -name, \KPS{} supports additional features in search paths: layered -default values, environment variable names, config file values, users' -home directories, and recursive subdirectory searching. Thus, we say -that \KPS{} \emph{expands} a path element, meaning it transforms all -the specifications into basic directory name or names. This is -described in the following sections in the same order as it takes -place. - -Note that if the filename being searched for is absolute or explicitly -relative, i.e., starts with \samp{/} or \samp{./} or \samp{../}, -\KPS{} simply checks if that file exists. - -\ifSingleColumn -\else -\begin{figure*} -\verbatiminput{examples/ex5.tex} -\setlength{\abovecaptionskip}{0pt} - \caption{An illustrative configuration file sample} - \label{fig:config-sample} -\end{figure*} -\fi - -\subsubsection{Path sources} -\label{sec:path-sources} - -A search path can come from many sources. In the order in which -\KPS{} uses them: - -\begin{enumerate} -\item - A user-set environment variable, for instance, \envname{TEXINPUTS}\@. - Environment variables with a period and a program name appended - override; e.g., if \samp{latex} is the name of the program being run, - then \envname{TEXINPUTS.latex} will override \envname{TEXINPUTS}. -\item - A program-specific configuration file, for exam\-ple, a line - \samp{S /a:/b} in \cmdname{dvips}'s \file{config.ps}. -\item A \KPS{} configuration file \file{texmf.cnf}, containing a line like - \samp{TEXINPUTS=/c:/d} (see below). -\item The compile-time default. -\end{enumerate} -\noindent You can see each of these values for a given search path by -using the debugging options (see ``Debugging actions'' on -page~\pageref{sec:debugging}). - -\subsubsection{Config files} - -\begingroup\tolerance=3500 -\KPS{} reads \emph{runtime configuration files} named \file{texmf.cnf} -for search path and other definitions. The search path used to look -for these files is named \envname{TEXMFCNF} (by default such a file lives -in the \file{texmf/web2c} subdirectory). \emph{All} -\file{texmf.cnf} files in the search path will be read and definitions -in earlier files override those in later files. Thus, with a search -path of \verb|.:$TEXMF|, values from \file{./texmf.cnf} override those -from \verb|$TEXMF/texmf.cnf|. -\endgroup - -\begin{itemize} -\item - Comments start with \code{\%} and continue to the end of the line. -\item - Blank lines are ignored. -\item - A \bs{} at the end of a line acts as a continuation character, - i.e., the next line is appended. Whitespace at the beginning of - continuation lines is not ignored. -\item - Each remaining line has the form: -\begin{alltt} - \var{variable}[.\var{progname}] [=] \var{value} -\end{alltt}% - where the \samp{=} and surrounding whitespace are optional. -\item - The \ttvar{variable} name may contain any character other - than whitespace, \samp{=}, or \samp{.}, but sticking to - \samp{A-Za-z\_} is safest. -\item - If \samp{.\var{progname}} is present, the definition only - applies if the program that is running is named - \texttt{\var{progname}} or \texttt{\var{progname}.exe}. This allows - different flavors of \TeX{} to have different search paths, for - example. -\item \var{value} may contain any characters except - \code{\%} and \samp{@}. The - \code{\$\var{var}.\var{prog}} feature is not available on the - right-hand side; instead, you must use an additional variable. A - \samp{;}\ in \var{value} is translated to \samp{:}\ if - running under Unix; this is useful to be able to have a single - \file{texmf.cnf} for Unix, \acro{MS-DOS} and Windows systems. -\item - All definitions are read before anything is expanded, so - variables can be referenced before they are defined. -\end{itemize} -A configuration file fragment illustrating most of these points is -\ifSingleColumn -shown below: - -\verbatiminput{examples/ex5.tex} -\else -shown in Figure~\ref{fig:config-sample}. -\fi - -\subsubsection{Path expansion} -\label{sec:path-expansion} - - -\KPS{} recognizes certain special characters and constructions in -search paths, similar to those available in Unix shells. As a -general example, the complex path, -\verb+~$USER/{foo,bar}//baz+, expands to all subdirectories under -directories \file{foo} and \file{bar} in \texttt{\$USER}'s home -directory that contain a directory or file \file{baz}. These -expansions are explained in the sections below. -%$ -\subsubsection{Default expansion} -\label{sec:default-expansion} - -\tolerance=2500 -If the highest-priority search path (see ``Path sources'' on -page~\pageref{sec:path-sources}) contains an \emph{extra colon} (i.e., -leading, trailing, or doubled), \KPS{} inserts at that point the -next-highest-prio\-rity search path that is defined. If that inserted -path has an extra colon, the same happens with the next highest. For -example, given an environment variable setting - -\tolerance=1500 - -\begin{alltt} -> \Ucom{setenv TEXINPUTS /home/karl:} -\end{alltt} -and a \code{TEXINPUTS} value from \file{texmf.cnf} of - -\begin{alltt} - .:\$TEXMF//tex -\end{alltt} -then the final value used for searching will be: - -\begin{alltt} - /home/karl:.:\$TEXMF//tex -\end{alltt} - -Since it would be useless to insert the default value in more than one -place, \KPS{} changes only one extra \samp{:}\ and leaves any others in -place. It checks first for a leading \samp{:}, then a trailing -\samp{:}, then a doubled \samp{:}. - -\subsubsection{Brace expansion} - -A useful feature is brace expansion, which means that, for instance, -\verb+v{a,b}w+ expands to \verb+vaw:vbw+. Nesting is allowed. -This is used to implement multiple \TeX{} hierarchies, by -assigning a brace list to \code{\$TEXMF}. -For example, in \file{texmf.cnf}, the following definition -(appproximately; there are actually even more trees) is made: -\begin{verbatim} - TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN} -\end{verbatim} -Using this you can then write something like -\begin{verbatim} - TEXINPUTS = .;$TEXMF/tex// -\end{verbatim} -%$ -which means that, after looking in the current directory, the -\code{\$TEXMFHOME/tex}, \code{\$TEXMFLOCAL/tex}, \code{\$TEXMFVAR/tex} -and \code{\$TEXMFMAIN/tex} trees \emph{only}) will be searched (the -last two use using \file{ls-R} data base files). It is a convenient -way for running two parallel \TeX{} structures, one ``frozen'' (on a -\CD, for instance) and the other being continuously updated with new -versions as they become available. By using the \code{\$TEXMF} -variable in all definitions, one is sure to always search the -up-to-date tree first. - -\subsubsection{Subdirectory expansion} -\label{sec:subdirectory-expansion} - -Two or more consecutive slashes in a path element following a directory -\var{d} is replaced by all subdirectories of \var{d}: first those -subdirectories directly under \var{d}, then the subsubdirectories under -those, and so on. At each level, the order in which the directories are -searched is \emph{unspecified}. - -If you specify any filename components after the \samp{//}, only -subdirectories with matching components are included. For example, -\samp{/a//b} expands into directories \file{/a/1/b}, \file{/a/2/b}, -\file{/a/1/1/b}, and so on, but not \file{/a/b/c} or \file{/a/1}. - -Multiple \samp{//} constructs in a path are possible, but -\samp{//} at the beginning of a path is ignored. - -\subsubsection{List of special characters and their meaning: a summary} - -The following list summarizes the special characters in \KPS{} -configuration files. - -% need a wider space for the item labels here. -\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} -\begin{ttdescription} -\item[\CODE{:}] Separator in path specification; at the beginning or - the end of a path it substitutes the default path expansion.\par -\item[\CODE{;}] Separator on non-Unix systems (acts like \code{:}). -\item[\CODE{\$}] Variable expansion. -\item[\CODE{\string~}] Represents the user's home directory. -\item[\CODE{\char`\{...\char`\}}] Brace expansion. -\item[\CODE{//}] Subdirectory expansion (can occur anywhere in - a path, except at its beginning). -\item[\CODE{\%}] Start of comment. -\item[\CODE{\bs}] Continuation character (allows multi-line entries). -\item[\CODE{!!}] Search \emph{only} database to locate file, \emph{do - not} search the disk. -\end{ttdescription} - - -\subsection{Filename databases} -\label{sec:filename-database} - -\KPS{} goes to some lengths to minimize disk accesses for searches. -Nevertheless, at installations with enough directories, searching each -possible directory for a given file can take an excessively long time -(this is especially true if many hundreds of font directories have to -be traversed.) Therefore, \KPS{} can use an externally-built plain text -``database'' file named \file{ls-R} that maps files to directories, -thus avoiding the need to exhaustively search the disk. - -A second database file \file{aliases} allows you to give additional -names to the files listed in \file{ls-R}. This can be helpful to -confirm to \acro{DOS} 8.3 filename conventions in source files. - -\subsubsection{The filename database} -\label{sec:ls-R} - -As explained above, the name of the main filename database must be -\file{ls-R}. You can put one at the root of each \TeX{} hierarchy in -your installation that you wish to be searched (\code{\$TEXMF} by -default); most sites have only one hierarchy. \KPS{} looks for -\file{ls-R} files along the \code{TEXMFDBS} path. - -The recommended way to create and maintain \samp{ls-R} is to run the -\code{mktexlsr} script included with the distribution. It is invoked -by the various \samp{mktex}\dots\ scripts. In principle, this script -just runs the command -\begin{alltt} -cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R -\end{alltt} -presuming your system's \code{ls} produces the right output format -(\GNU \code{ls} is all right). To ensure that the database is -always up-to-date, it is easiest to rebuild it regularly via -\code{cron}, so that it is automatically updated when the installed -files change, such as after installing or updating a \LaTeX{} package. - -If a file is not found in the database, by default \KPS{} goes ahead -and searches the disk. If a particular path element begins with -\samp{!!}, however, \emph{only} the database will be searched for that -element, never the disk. - - -\subsubsection{kpsewhich: Standalone path searching} -\label{sec:invoking-kpsewhich} - -The \texttt{kpsewhich} program exercises path searching independent of any -particular application. This can be useful as a sort of \code{find} -program to locate files in \TeX{} hierarchies (this is used heavily in -the distributed \samp{mktex}\dots\ scripts). - -\begin{alltt} -> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} -\end{alltt} -The options specified in \ttvar{option} start with either \samp{-} -or \samp{-{}-}, and any unambiguous abbreviation is accepted. - -\KPS{} looks up each non-option argument on the command line as a -filename, and returns the first file found. There is no option to -return all the files with a particular name (you can run the Unix -\samp{find} utility for that). - -The most common options are described next. - -\begin{ttdescription} -\item[\texttt{-{}-dpi=\var{num}}]\mbox{} - Set the resolution to \ttvar{num}; this only affects \samp{gf} - and \samp{pk} lookups. \samp{-D} is a synonym, for compatibility - with \cmdname{dvips}. Default is 600. - -\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ - Set the format for lookup to \ttvar{name}. By default, the - format is guessed from the filename. For formats which do not have - an associated unambiguous suffix, such as \MP{} support files and - \cmdname{dvips} configuration files, you have to specify the name as - known to \KPS{}, such as \texttt{tex} or \texttt{enc files}. Run - \texttt{kpsewhich -{}-help} for a list. - -\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ - Set the mode name to \ttvar{string}; this only affects \samp{gf} - and \samp{pk} lookups. No default: any mode will be found. -\item[\texttt{-{}-must-exist}]\mbox{}\\ - Do everything possible to find the files, notably including - searching the disk. By default, only the \file{ls-R} database is - checked, in the interest of efficiency. -\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ - Search along the path \ttvar{string} (colon-separated as usual), - instead of guessing the search path from the filename. \samp{//} and - all the usual expansions are supported. The options \samp{-{}-path} - and \samp{-{}-format} are mutually exclusive. -\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ - Set the program name to \texttt{\var{name}}. - This can affect the search paths via the \texttt{.\var{progname}} - feature. - The default is \cmdname{kpsewhich}. -\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ - shows the path used for file lookups of file type \texttt{\var{name}}. - Either a filename extension (\code{.pk}, \code{.vf}, etc.) or a - name can be used, just as with \samp{-{}-format} option. -\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ - sets the debugging options to \texttt{\var{num}}. -\end{ttdescription} - - -\subsubsection{Examples of use} -\label{sec:examples-of-use} - -Let us now have a look at \KPS{} in action. Here's a straightforward search: - -\begin{alltt} -> \Ucom{kpsewhich article.cls} - /usr/local/texmf-dist/tex/latex/base/article.cls -\end{alltt} -We are looking for the file \file{article.cls}. Since the \samp{.cls} -suffix is unambiguous we do not need to specify that we want to look for a -file of type \optname{tex} (\TeX{} source file directories). We find it in -the subdirectory \file{tex/latex/base} below the \samp{texmf-dist} \TL\ -directory. Similarly, all of the following are found without problems -thanks to their unambiguous suffix. -\begin{alltt} -> \Ucom{kpsewhich array.sty} - /usr/local/texmf-dist/tex/latex/tools/array.sty -> \Ucom{kpsewhich latin1.def} - /usr/local/texmf-dist/tex/latex/base/latin1.def -> \Ucom{kpsewhich size10.clo} - /usr/local/texmf-dist/tex/latex/base/size10.clo -> \Ucom{kpsewhich small2e.tex} - /usr/local/texmf-dist/tex/latex/base/small2e.tex -> \Ucom{kpsewhich tugboat.bib} - /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib -\end{alltt} - -By the way, that last is a \BibTeX{} bibliography database for \textsl{TUGBoat} articles. - -\begin{alltt} -> \Ucom{kpsewhich cmr10.pk} -\end{alltt} -Font bitmap glyph files of type \file{.pk} are used by display -programs like \cmdname{dvips} and \cmdname{xdvi}. Nothing is returned in -this case since there are no pre-generated Computer Modern \samp{.pk} -files in \TL{}\Dash the Type~1 variants are used by default. -\begin{alltt} -> \Ucom{kpsewhich wsuipa10.pk} -\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk -\else /usr/local/texmf-var/fonts/pk/ljfour/public/ -... wsuipa/wsuipa10.600pk -\fi\end{alltt} -For these fonts (a phonetic alphabet from the University of Washington) -we had to generate \samp{.pk} files, and since the default \MF{} mode on -our installation is \texttt{ljfour} with a base resolution of 600\dpi{} -(dots per inch), this instantiation is returned. -\begin{alltt} -> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} -\end{alltt} -In this case, when specifying that we are interested in a resolution -of 300\dpi{} (\texttt{-dpi=300}) we see that no such font is available on -the system. A program like \cmdname{dvips} or \cmdname{xdvi} would -go off and actually build the required \texttt{.pk} files -using the script \cmdname{mktexpk}. - -Next we turn our attention to \cmdname{dvips}'s header and configuration -files. We first look at one of the commonly used files, the general -prologue \file{tex.pro} for \TeX{} support, before turning our attention -to the generic configuration file (\file{config.ps}) and the \PS{} font -map \file{psfonts.map}\Dash as of 2004, map and encoding files have -their own search paths and new location in \dirname{texmf} trees. As -the \samp{.ps} suffix is ambiguous we have to specify explicitly which -type we are considering (\optname{dvips config}) for the file -\texttt{config.ps}. -\begin{alltt} -> \Ucom{kpsewhich tex.pro} - /usr/local/texmf/dvips/base/tex.pro -> \Ucom{kpsewhich --format="dvips config" config.ps} - /usr/local/texmf/dvips/config/config.ps -> \Ucom{kpsewhich psfonts.map} - /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map -\end{alltt} - -We now take a closer look at the \acro{URW} Times \PS{} support -files. The prefix for these in the standard font naming scheme is -\samp{utm}. The first file we look at is the configuration file, -which contains the name of the map file: -\begin{alltt} -> \Ucom{kpsewhich --format="dvips config" config.utm} - /usr/local/texmf-dist/dvips/psnfss/config.utm -\end{alltt} -The contents of that file is -\begin{alltt} - p +utm.map -\end{alltt} -which points to the file \file{utm.map}, which we want to -locate next. -\begin{alltt} -> \Ucom{kpsewhich utm.map} - /usr/local/texmf-dist/fonts/map/dvips/times/utm.map -\end{alltt} -This map file defines the file names of the Type~1 \PS{} fonts in -the URW collection. Its contents look like (we only show part of the -lines): -\begin{alltt} -utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} -\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb -\else /usr/local/texmf-dist/fonts/type1/ -... urw/utm/utmr8a.pfb -\fi\end{alltt} - -It should be evident from these examples how you can easily locate the -whereabouts of a given file. This is especially important if you suspect -that the wrong version of a file is picked up somehow, since -\cmdname{kpsewhich} will show you the first file encountered. - -\subsubsection{Debugging actions} -\label{sec:debugging} - -Sometimes it is necessary to investigate how a program resolves file -references. To make this practical, \KPS{} offers various levels of -debugging output: - -\begin{ttdescription} -\item[\texttt{\ 1}] \texttt{stat} calls (disk lookups). When running - with an up-to-date \file{ls-R} database this should almost give no - output. -\item[\texttt{\ 2}] References to hash tables (such as \file{ls-R} - databases, map files, configuration files). -\item[\texttt{\ 4}] File open and close operations. -\item[\texttt{\ 8}] General path information for file types - searched by \KPS. This is useful to find out where a particular - path for the file was defined. -\item[\texttt{16}] Directory list for each path element (only relevant - for searches on disk). -\item[\texttt{32}] File searches. -\item[\texttt{64}] Variable values. -\end{ttdescription} -A value of \texttt{-1} will set all the above options; in practice, -this is usually the most convenient. - -Similarly, with the \cmdname{dvips} program, by setting a combination of -debug switches, one can follow in detail where files are being picked up -from. Alternatively, when a file is not found, the debug trace shows in -which directories the program looks for the given file, so that one can -get an indication what the problem~is. - -Generally speaking, as most programs call the \KPS{} library -internally, one can select a debug option by using the -\envname{KPATHSEA\_DEBUG} environment variable, and setting it to (a -combination of) values as described in the above list. - -(Note for Windows users: it is not easy to redirect -all messages to a file in this system. For diagnostic purposes -you can temporarily \texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log}). - -Let us consider, as an example, a small \LaTeX{} source file, -\file{hello-world.tex}, which contains the following input. -\begin{verbatim} - \documentclass{article} - \begin{document} - Hello World! - \end{document} -\end{verbatim} -This little file only uses the font \file{cmr10}, so let us look at -how \cmdname{dvips} prepares the \PS{} file (we want to use the Type~1 -version of the Computer Modern fonts, hence the option \texttt{-Pcms}). -\begin{alltt} -> \Ucom{dvips -d4100 hello-world -Pcms -o} -\end{alltt} -In this case we have combined \cmdname{dvips}'s debug class 4 (font -paths) with \KPS's path element expansion (see \cmdname{dvips} Reference -Manual, \OnCD{texmf/doc/dvips/dvips.pdf}). -The output (slightly rearranged) appears in -Figure~\ref{fig:dvipsdbga}. -\begin{figure*}[tp] -\centering -\input{examples/ex6a.tex} -\caption{Finding configuration files}\label{fig:dvipsdbga} - -\bigskip - -\input{examples/ex6b.tex} -\caption{Finding the prolog file}\label{fig:dvipsdbgb} - -\bigskip - -\input{examples/ex6c.tex} -\caption{Finding the font file}\label{fig:dvipsdbgc} -\end{figure*} - -\cmdname{dvips} starts by locating its working files. First, -\file{texmf.cnf} is found, which gives the definitions of the search -paths for the other files, then the file database \file{ls-R} (to -optimize file searching) and the file \file{aliases}, which makes it -possible to declare several names (e.g., a short \acro{DOS}-like 8.3 and -a more natural longer version) for the same file. Then \cmdname{dvips} -goes on to find the generic configuration file \file{config.ps} -before looking for the customization file \file{.dvipsrc} (which, in -this case is \emph{not found}). Finally, \cmdname{dvips} locates the -config file for the Computer Modern \PS{} fonts \file{config.cms} -(this was initiated with the \texttt{-Pcms} option on the \cmdname{dvips} -command). This file contains the list of the map files which -define the relation between the \TeX{}, \PS{} and file system -names of the fonts. -\begin{alltt} -> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} - p +ams.map - p +cms.map - p +cmbkm.map - p +amsbkm.map -\end{alltt} -\cmdname{dvips} thus goes on to find all these files, plus the generic -map file \file{psfonts.map}, which is always loaded (it contains -declarations for commonly used \PS{} fonts; see the last part of -Section \ref{sec:examples-of-use} for more details about \PS{} map -file handling). - -At this point \cmdname{dvips} identifies itself to the user: -\begin{alltt} -This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) -\end{alltt} -\ifSingleColumn -Then it goes on to look for the prolog file \file{texc.pro}: -\begin{alltt}\small -kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro -\end{alltt} -\else -Then it goes on to look for the prolog file \file{texc.pro} (see -Figure~\ref{fig:dvipsdbgb}). -\fi - -After having found the file in question, \cmdname{dvips} outputs -the date and time, and informs us that it will generate the -file \file{hello-world.ps}, then that it needs the font file -\file{cmr10}, and that the latter is declared as ``resident'' (no -bitmaps needed): -\begin{alltt}\small -TeX output 1998.02.26:1204' -> hello-world.ps -Defining font () cmr10 at 10.0pt -Font cmr10 is resident. -\end{alltt} -Now the search is on for the file \file{cmr10.tfm}, which is found, -then a few more prolog files (not shown) are referenced, and finally -the Type~1 instance \file{cmr10.pfb} of the font is located and -included in the output file (see last line). -\begin{alltt}\small -kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, - path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: - /var/tex/fonts/tfm//). -kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm -kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, - ... - -kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb -[1] -\end{alltt} - -\subsection{Runtime options} - -Another useful feature of \Webc{} is its possibility to control a number -of memory parameters (in particular, array sizes) via the runtime file -\file{texmf.cnf} read by \KPS{}. The memory settings can be found in -Part 3 of that file in the \TL{} distribution. The more important -are: - -\begin{ttdescription} -\item[\texttt{main\_memory}] - Total words of memory available, for - \TeX{}, \MF{} and \MP. You must make a new format file for each - different setting. For instance, you could generate a ``huge'' - version of \TeX{}, and call the format file \texttt{hugetex.fmt}. - Using the standard way of specifying the program name used by \KPS{}, - the particular value of the \texttt{main\_memory} variable will then - be read from \file{texmf.cnf}. -\item[\texttt{extra\_mem\_bot}] - Extra space for ``large'' \TeX{} data structures: - boxes, glue, breakpoints, etc. Especially useful if you use - \PiCTeX{}. -\item[\texttt{font\_mem\_size}] - Number of words for font information available for \TeX. This - is more or less the total size of all \acro{TFM} files read. -\item[\texttt{hash\_extra}] - Additional space for the hash table of control sequence names. - Only $\approx$10,000 control sequences can be stored in the main - hash table; if you have a large book with numerous cross-references, - this might not be enough. The default value of - \texttt{hash\_extra} is \texttt{50000}. -\end{ttdescription} - -\noindent Of course, this facility is no substitute for truly dynamic -arrays and memory allocation, but since these are extremely difficult to -implement in the present \TeX{} source, these runtime parameters provide -a practical compromise allowing some flexibility. - - -\begin{comment} -\section{Building on a new Unix platform} - -If you have a platform for which executables are not included, you will -need to compile \TeX{} and friends. This is not as hard as it -sounds. What you need is all in the directory \texttt{source} in the -distribution. - -\subsection{Prerequisites} - -You will need at least 100 megabytes of disk space to compile all of -\TeX{} and its support programs. You'll also need an \acro{ANSI} C -compiler, a \cmdname{make} utility, a lexical scanner, and a parser -generator. We recommend the \GNU version of these programs -(\cmdname{gcc}, \GNU \cmdname{make}, \cmdname{m4}, \cmdname{flex}, -\cmdname{bison}). You may be able to work with other C compilers and -\cmdname{make} programs, but you will need a good understanding of -building Unix programs to sort out problems. - -Also, the command \texttt{uname} must return a sensible value. - - -\subsection{Configuration} - -To begin, perform a normal installation of \TL{} to your disk (see -section~\ref{sec:install-disk} on -\p.\pageref{sec:install-disk}). You may wish to skip installing -all of the prebuilt binaries. - -Then, unpack the source from the compressed \texttt{tar} file in the -directory \dirname{source} to your disk and change directory to where -you placed it. - -Next, run \cmdname{configure} with a command line like this: -\begin{alltt} -> \Ucom{sh configure -prefix=/usr/local/TeX} -\end{alltt} - -The \optname{-prefix} directory is the one where you installed the -support tree; the directory layout will be as follows (where \$TEXDIR -stands for the directory you chose): - -\noindent -\begin{tabular}{>{\ttfamily}ll@{}} - \dirname{$TEXDIR/share/texmf} & main tree with fonts,\\ - & \qquad macros, etc\\ - \dirname{$TEXDIR/man} & Unix manual pages\\ - \dirname{$TEXDIR/info} & \GNU style Info manuals\\ - \dirname{$TEXDIR/bin/$PLATFORM} & binaries\\ -\end{tabular} -%$ - -If you want to leave out the \dirname{$PLATFORM} directory level, -i.e., put the binaries directly into \dirname{$TEXDIR/bin}, specify -the \verb|--disable-multiplatform| option to \cmdname{configure}. - -Have a look at the output of \verb|./configure --help| for more -options you can use. For example, you can skip building of \OMEGA{} and -\eTeX{}. - - -\subsection{Running \cmdname{make}} - -Make sure the shell variable or option \texttt{noclobber} is not set. -Then, run the main \cmdname{make} like this: -\begin{alltt} -> \Ucom{make world} -\end{alltt} -and relax\ldots - -Alternatively, you want to log all the output, as in: -\begin{alltt} -> \Ucom{sh -c "make world >world.log 2>\&1" \&} -\end{alltt} - -Before you believe that everything went ok, please check the log file -for errors: \GNU \cmdname{make} always uses the string \samp{***} -whenever a command fails. Also, check if all the programs were built: - -\begin{alltt} -> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} -> \Ucom{ls | wc} -\end{alltt} -The result should be over 200 (you can check the exact number with the -\dirname{bin} directory contents in the distribution). - -If you need special privileges for \texttt{make install}, you can -separate the \samp{make world} into two different runs, like this: -\begin{alltt} -> \Ucom{make all} -> \Ucom{su} -> \Ucom{make install strip} -\end{alltt} - -After you've installed your new binaries, you should follow the normal -post-installation procedures, given in section~\ref{sec:postinstall} -(\p.\pageref{sec:postinstall}). - -Also, if you'd like to make your binaries available to others, please -contact us. We'll be happy to put them on the \TL\ web pages. -\end{comment} - -\ifx\HCode\undefined\else\HCode{} -\section{Acknowledgements} - -\TL{} is a joint effort by virtually all of the \TeX{} user groups. -This edition of \TL{} was overseen by Karl Berry. The other principal -contributors, past and present, are listed below. - -\begin{itemize*} - -\item The English, German, Dutch, and Polish \TeX{} user groups -(\acro{TUG}, \acro{DANTE} e.V., \acro{NTG}, and \acro{GUST}, -respectively), which provide the necessary technical and administrative -infrastructure. Please join the \TeX\ user group near you! (See -\url{http://tug.org/usergroups.html}.) - -\item The \acro{CTAN} team, most notably Robin Fairbairns, Jim Hef{}feron, -and Rainer Sch\"opf, which distributes the \TL{} images and provides the -common infrastructure for package updates, upon which \TL{} depends. - -\item Peter Breitenlohner (and the \eTeX\ team) for the stable foundation -of future \TeX's, and Peter specifically for stellar help with the GNU -autotools usage throughout \TL. - -\item Thomas Esser, without whose marvelous \teTeX{} package \TL{} -would have never existed. - -\item Michel Goossens, who co-authored the original documentation. - -\item Eitan Gurari, whose \TeX4ht was used to create the \HTML{} -version of this documentation, and who worked tirelessly to improve -it at short notice. - -\item \Thanh, Martin Schr\"oder, and the pdf\TeX\ team -(\url{http://pdftex.org}) for continuing enhancements of \TeX's -abilities. - -\item Hans Hagen, for much testing and making his \ConTeXt\ format -(\url{http://pragma-ade.com}) work within \TL's framework. - -\item Hartmut Henkel, for significant development contributions to -pdf\TeX\, Lua\TeX, and more. - -\item Taco Hoekwater, for renewed development efforts on MetaPost and -(Lua)\TeX\ (\url{http://luatex.org}) itself, and for incorporating -\ConTeXt\ into \TL. - -\item Pawe{\l} Jackowski, for the Windows installer \cmdname{tlpm}, -and Tomasz {\L}uczak, for \cmdname{tlpmgui}, used in past releases. - -\item Akira Kakuto, for providing the Windows -binaries from his \acro{W32TEX} distribution for Japanese \TeX\ -(\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}), and many -other contributions. - -\item Jonathan Kew and \acro{SIL}, for the major new development of -\XeTeX{} and taking the time and trouble to integrate it in \TL{}, as -well as the initial version of the Mac\TeX\ installer. - -\item Dick Koch, for maintaining Mac\TeX\ (\url{http://tug.org/mactex}) -in very close tandem with \TL{}, and for his great good cheer in doing -so. - -\item Reinhard Kotucha, for major contributions to the \TL{} 2008 -infrastructure and installer, as well as Windows research efforts, the -\texttt{getnonfreefonts} script, and more. - -\item Siep Kroonenberg, also for major contributions to the \TL{} 2008 -infrastructure and installer, especially on Windows, and for the bulk of -work updating this manual describing the new features. - -\item Petr Ol\v{s}ak, who coordinated and checked all the Czech and Slovak -material very carefully. - -\item Toshio Oshima, for his \cmdname{dviout} previewer for Windows. - -\item Manuel P\'egouri\'e-Gonnard, for helping with package updates, -documentation improvements, and \cmdname{tldoc} development. - -\item Fabrice Popineau, for the original Windows support in \TL{} and -work on the French documentation. - -\item Norbert Preining, the principal architect of the \TL{} 2008 -infrastructure and installer, and also for coordinating the Debian -version of \TL{} (together with Frank K\"uster), making many suggestions -along the way. - -\item Sebastian Rahtz, for originally creating \TL{} and maintaining it -for many years. - -\item Vladimir Volovich, for substantial help with porting and other -maintenance issues, and especially for making it feasible to include -\cmdname{xindy}. - -\item Staszek Wawrykiewicz, the principal tester for all of \TL{}, -and coordinator of the many major Polish contributions: fonts, Windows -installation, and more. - -\item Olaf Weber, for his patient maintenance of \Webc. - -\item Gerben Wierda, for creating and maintaining the \MacOSX\ support, -and much integration and testing. - -\item Graham Williams, on whose work the \TeX\ Catalogue of packages depends. - -\end{itemize*} - -Builders of the binaries: -Reinhard Kotucha (\pkgname{x86\_64-linux}), -Tim Arnold (\pkgname{hppa-hpux}), -Randy Au (\pkgname{amd64-freebsd}), -Edd Barrett (\pkgname{i386-openbsd}), -Karl Berry (\pkgname{i386-linux}), -Akira Kakuto (\pkgname{win32}), -Dick Koch (\pkgname{universal-darwin}), -Manfred Lotz (\pkgname{i386-freebsd}), -Norbert Preining (\pkgname{alpha-linux}), -Arthur Reutenauer (\pkgname{sparc-linux}), -Thomas Schmitz (\pkgname{powerpc-linux}), -Apostolos Syropoulos (\pkgname{i386-solaris}), -Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-solaris}), -Olaf Weber (\pkgname{mips-irix}). -For information on the \TL{} build process, see -\url{http://tug.org/texlive/build.html}. - -Documentation and translation updates: -Karl Berry (English), -Daniel Flipo (French), -Klaus H\"oppner (German), -Petr Sojka \& Jan Busa (Czech\slash Slovak), -Boris Veytsman (Russian), -Staszek Wawrykiewicz (Polish). The \TL{} documentation web page -is \url{http://tug.org/texlive/doc.html}. - -Of course the most important acknowledgement must go to Donald Knuth, -first for inventing \TeX, and then for giving it to the world. - - - -\section{Release history} -\label{sec:history} - -\subsection{Past} - -Discussion began in late 1993 when the Dutch \TeX{} Users Group was -starting work on its 4All\TeX{} \CD{} for \acro{MS-DOS} users, and it -was hoped at that time to issue a single, rational, \CD{} for all -systems. This was too ambitious a target for the time, but it did spawn -not only the very successful 4All\TeX{} \CD{}, but also the \acro{TUG} -Technical Council working group on a \emph{\TeX{} Directory Structure} -(\url{http://tug.org/tds}), which specified how to create consistent and -manageable collections of \TeX{} support files. A complete draft of the -\TDS{} was published in the December 1995 issue of \textsl{TUGboat}, and -it was clear from an early stage that one desirable product would be a -model structure on \CD{}. The distribution you now have is a very direct -result of the working group's deliberations. It was also clear that the -success of the 4All\TeX{} \CD{} showed that Unix users would benefit -from a similarly easy system, and this is the other main strand of -\TL. - -We first undertook to make a new Unix-based \TDS{} \CD{} in the autumn -of 1995, and quickly identified Thomas Esser's \teTeX{} as the ideal -setup, as it already had multi-platform support and was built with -portability across file systems in mind. Thomas agreed to help, and work -began seriously at the start of 1996. The first edition was released in -May 1996. At the start of 1997, Karl Berry completed a major new release -of Web2c, which included nearly all the features which Thomas Esser had -added in \teTeX, and we decided to base the 2nd edition of the \CD{} on -the standard \Webc, with the addition of \teTeX's \texttt{texconfig} -script. The 3rd edition of the \CD{} was based on a major revision of -\Webc, 7.2, by Olaf Weber; at the same time, a new revision of \teTeX -was being made, and \TL{} included almost all of its features. The -4th edition followed the same pattern, using a new version of \teTeX, -and a new release of \Webc{} (7.3). The system now included a complete -Windows setup. - -For the 5th edition (March 2000) many parts of the \CD{} were revised -and checked, updating hundreds of packages. Package details were stored -in XML files. But the major change for \TeX\ Live 5 was that all -non-free software was removed. Everything in \TL{} is now intended -to be compatible with the Debian Free Software Guidelines -(\url{http://www.debian.org/intro/free}); we have done our best to check -the license conditions of all packages, but we would very much -appreciate hearing of any mistakes. - -The 6th edition (July 2001) had much more material updated. The major -change was a new install concept: the user could select a more exact set -of needed collections. Language-related collections were completely -reorganized, so selecting any of them installs not only macros, fonts, -etc., but also prepares an appropriate \texttt{language.dat}. - -The 7th edition of 2002 had the notable addition of \MacOSX{} support, -and the usual myriad of updates to all sorts of packages and -programs. An important goal was integration of the source back with -\teTeX, to correct the drift apart in versions~5 and~6. - -\subsubsection{2003} - -In 2003, with the continuing flood of updates and additions, we found -that \TL{} had grown so large it could no longer be contained on a -single \CD, so we split it into three different distributions (see -section~\ref{sec:tl-coll-dists}, \p.\pageref{sec:tl-coll-dists}). In -addition: - -\begin{itemize*} -\item At the request of the \LaTeX{} team, we changed the standard - \cmdname{latex} and \cmdname{pdflatex} commands to now use \eTeX{} (see - \p.\pageref{text:etex}). -\item The new Latin Modern fonts were included (and are recommended). -\item Support for Alpha \acro{OSF} was removed - (\acro{HPUX} support was removed previously), since no one had (or - volunteered) hardware available on which to compile new binaries. -\item Windows setup was substantially changed; for the first time - an integrated environment based on XEmacs was introduced. -\item Important supplementary programs for Windows - (Perl, Ghost\-script, Image\-Magick, Ispell) are now installed - in the \TL{} installation directory. -\item Font map files used by \cmdname{dvips}, \cmdname{dvipdfm} - and \cmdname{pdftex} are now generated by the new program - \cmdname{updmap} and installed into \dirname{texmf/fonts/map}. -\item \TeX{}, \MF{}, and \MP{} now, by default, output most input - characters (32 and above) as themselves in output (e.g., - \verb|\write|) files, - log files, and the terminal, i.e., \emph{not} translated using the - \verb|^^| notation. In \TL{}~7, this translation was - dependent on the system locale settings; now, locale settings do - not influence the \TeX{} programs' behavior. If for some reason - you need the \verb|^^| output, rename the file - \verb|texmf/web2c/cp8bit.tcx|. (Future releases will have cleaner - ways to control this.) -\item This documentation was substantially revised. -\item Finally, since the edition numbers had grown unwieldy, - the version is now simply identified by the year: \TL{} 2003. -\end{itemize*} - - -\subsubsection{2004} - -2004 saw many changes: - -\begin{itemize} - -\item If you have locally-installed fonts which use their own -\filename{.map} or (much less likely) \filename{.enc} support files, you -may need to move those support files. - -\filename{.map} files are now searched for in subdirectories of -\dirname{fonts/map} only (in each \filename{texmf} tree), along the -\envname{TEXFONTMAPS} path. Similarly, \filename{.enc} files are now -searched for in subdirectories of \dirname{fonts/enc} only, along the -\envname{ENCFONTS} path. \cmdname{updmap} will attempt to warn about -problematic files. - -For methods of handling this and other information, please see -\url{http://tug.org/texlive/mapenc.html}. - -\item The \TK\ has been expanded with the addition of a \MIKTEX-based -installable \CD, for those who prefer that implementation to Web2C. -See section~\ref{sec:overview-tl} (\p.\pageref{sec:overview-tl}). - -\item Within \TL, the single large \dirname{texmf} tree of previous -releases has been replaced by three: \dirname{texmf}, -\dirname{texmf-dist}, and \dirname{texmf-doc}. See -section~\ref{sec:tld} (\p.\pageref{sec:tld}), and the \filename{README} -files for each. - -\item All \TeX-related input files are now collected in -the \dirname{tex} subdirectory of \dirname{texmf*} trees, rather than -having separate sibling directories \dirname{tex}, \dirname{etex}, -\dirname{pdftex}, \dirname{pdfetex}, etc. See -\CDref{texmf-doc/doc/english/tds/tds.html\#Extensions} -{\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}. - -\item Helper scripts (not meant to be invoked by users) are now located -in a new \dirname{scripts} directory of \dirname{texmf*} trees, and -searched for via \verb|kpsewhich -format=texmfscripts|. So if you have -programs which call such scripts, they'll need to be adjusted. See -\CDref{texmf-doc/doc/english/tds/tds.html\#Scripts} -{\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}. - -\item Almost all formats leave most characters printable as -themselves via the ``translation file'' \filename{cp227.tcx}, instead of -translating them with the \verb|^^| notation. Specifically, characters -at positions 32--256, plus tab, vertical tab, and form feed are -considered printable and not translated. The exceptions are plain \TeX\ -(only 32--126 printable), \ConTeXt\ (0--255 printable), and the -\OMEGA-related formats. This default behavior is almost the same as in -\TL\,2003, but it's implemented more cleanly, with more possibilities -for customization. See \CDref{texmf/doc/web2c/web2c.html\#TCX-files} -{\texttt{texmf/doc/web2c/web2c.html\#TCX-files}}. -(By the way, with Unicode input, \TeX\ may output partial character -sequences when showing error contexts, since it is byte-oriented.) - -\item \textsf{pdfetex} is now the default engine for all formats -except (plain) \textsf{tex} itself. (Of course it generates \acro{DVI} -when run as \textsf{latex}, etc.) This means, among other things, that -the microtypographic features of \textsf{pdftex} are available in -\LaTeX, \ConTeXt, etc., as well as the \eTeX\ features -(\OnCD{texmf-dist/doc/etex/base/}). - -It also means it's \emph{more important than ever} to use the -\pkgname{ifpdf} package (works with both plain and \LaTeX) or equivalent -code, because simply testing whether \cs{pdfoutput} or some other -primitive is defined is not a reliable way to determine if \acro{PDF} -output is being generated. We made this backward compatible as best we -could this year, but next year, \cs{pdfoutput} may be defined even when -\acro{DVI} is being written. - -\item pdf\TeX\ (\url{http://pdftex.org}) has many new features: - - \begin{itemize*} - - \item \cs{pdfmapfile} and \cs{pdfmapline} provide font map support - from within a document. - - \item Microtypographic font expansion can be used more easily.\\ - \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} - - \item All parameters previously set through the special configuration - file \filename{pdftex.cfg} must now be set through primitives, - typically in \filename{pdftexconfig.tex}; \filename{pdftex.cfg} is no - longer supported. Any extant \filename{.fmt} files must be redumped - when \filename{pdftexconfig.tex} is changed. - - \item See the pdf\TeX\ manual for more: \OnCD{texmf-dist/doc/pdftex/manual/pdftex-a.pdf}. - - \end{itemize*} - -\item The \cs{input} primitive in \cmdname{tex} (and \cmdname{mf} and -\cmdname{mpost}) now accepts double quotes containing spaces and other -special characters. Typical examples: -\begin{verbatim} -\input "filename with spaces" % plain -\input{"filename with spaces"} % latex -\end{verbatim} -See the Web2C manual for more: \OnCD{texmf/doc/web2c}. - -\item enc\TeX\ support is now included within Web2C and consequently all -\TeX\ programs, via the \optname{-enc} option\Dash \emph{only when -formats are built}. enc\TeX\ supports general re-encoding of input and -output, enabling full support of Unicode (in \acro{UTF}-8). See -\OnCD{texmf-dist/doc/generic/enctex/} and -\url{http://www.olsak.net/enctex.html}. - -\item Aleph, a new engine combining \eTeX\ and \OMEGA, is available. -A little information is available in \OnCD{texmf-dist/doc/aleph/base} -and \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph}. The -\LaTeX-based format for Aleph is named \textsf{lamed}. - -\item The latest \LaTeX\ release has a new version of the -\acro{LPPL}\Dash now officially a Debian-approved license. Assorted -other updates, see the \filename{ltnews} files in -\OnCD{texmf-dist/doc/latex/base}. - -\item \cmdname{dvipng}, a new program for converting \acro{DVI} to -\acro{PNG} image files, is included. See \OnCD{texmf/doc/man/man1/dvipng.1}. - -\item We reduced the \pkgname{cbgreek} package to a ``medium'' sized set -of fonts, with the assent and advice of the author (Claudio Beccari). -The excised fonts are the invisible, outline, and transparency ones, -which are relatively rarely used, and we needed the space. The full set -is of course available from \acro{CTAN} -(\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). - -\item \cmdname{oxdvi} has been removed; just use \cmdname{xdvi}. - -\item The \cmdname{ini} and \cmdname{vir} commands (links) for -\cmdname{tex}, \cmdname{mf}, and \cmdname{mpost} are no longer created, -such as \cmdname{initex}. The \cmdname{ini} functionality has been -available through the command-line option \optname{-ini} for years now. - -\item \textsf{i386-openbsd} platform support was removed. Since the -\pkgname{tetex} package in the \acro{BSD} Ports system is available, and -\acro{GNU/}Linux and Free\acro{BSD} binaries were available, it seemed -volunteer time could be better spent elsewhere. - -\item On \textsf{sparc-solaris} (at least), you may have to set the -\envname{LD\_LIBRARY\_PATH} environment variable to run the -\pkgname{t1utils} programs. This is because they are compiled with C++, -and there is no standard location for the runtime libraries. (This is -not new in 2004, but wasn't previously documented.) Similarly, on -\textsf{mips-irix}, the \acro{MIPS}pro 7.4 runtimes are required. - -\end{itemize} - -\subsubsection{2005} - -2005 saw the usual huge number of updates to packages and programs. -The infrastructure stayed relatively stable from 2004, but inevitably -there were some changes there as well: - -\begin{itemize} - -\item New scripts \cmdname{texconfig-sys}, \cmdname{updmap-sys}, and - \cmdname{fmtutil-sys} were introduced, which modify the - configuration in the system trees. The \cmdname{texconfig}, - \cmdname{updmap}, and \cmdname{fmtutil} scripts now modify - user-specific files, under \dirname{$HOME/.texlive2005}. - -\item Corresponding new variables \envname{TEXMFCONFIG} and - \envname{TEXMFSYSCONFIG} to specify the trees where configuration - files (user or system, respectively) are found. Thus, you may - need to move personal versions of \filename{fmtutil.cnf} and - \filename{updmap.cfg} to these places; another option is to - redefine \envname{TEXMFCONFIG} or \envname{TEXMFSYSCONFIG} in - \filename{texmf.cnf}. In any case the real location of these files - and the values of \envname{TEXMFCONFIG} and \envname{TEXMFSYSCONFIG} - must agree. - See section~\ref{sec:texmftrees}, \p.\pageref{sec:texmftrees}. - -\item Last year, we kept \verb|\pdfoutput| and other primitives undefined - for \dvi\ output, even though the \cmdname{pdfetex} program was - being used. This year, as promised, we undid that compatibility - measure. So if your document uses \verb|\ifx\pdfoutput\undefined| - to test if PDF is being output, it will need to be changed. You - can use the package \pkgname{ifpdf.sty} (which works under both - plain \TeX\ and \LaTeX) to do this, or steal its logic. - -\item Last year, we changed most formats to output (8-bit) characters as - themselves (see previous section). The new TCX file - \filename{empty.tcx} now provides an easier way to get the - original \verb|^^| notation if you so desire, as in: -\begin{verbatim} -latex --translate-file=empty.tcx yourfile.tex -\end{verbatim} - -\item The new program \cmdname{dvipdfmx} is included for translation of - DVI to PDF; this is an actively maintained update of - \cmdname{dvipdfm} (which is also still available for now, though - no longer recommended). - -\item The new programs \cmdname{pdfopen} and \cmdname{pdfclose} are included - to allow reloading of pdf files in the Adobe Acrobat Reader without - restarting the program. (Other pdf readers, notably \cmdname{xpdf}, - \cmdname{gv}, and \cmdname{gsview}, have never suffered from this - problem.) - -\item For consistency, the variables \envname{HOMETEXMF} and - \envname{VARTEXMF} have been renamed to \envname{TEXMFHOME} and - \envname{TEXMFSYSVAR}, respectively. There is also - \envname{TEXMFVAR}, which is by default user-specific. See the - first point above. - -\end{itemize} - - -\subsubsection{2006--2007} - -In 2006--2007, the major new addition to \TL{} was the \XeTeX{} program, -available as the \texttt{xetex} and \texttt{xelatex} programs; see -\url{http://scripts.sil.org/xetex}. - -MetaPost also received a notable update, with more planned for the -future (\url{http://tug.org/metapost/articles}), likewise pdf\TeX{} -(\url{http://tug.org/applications/pdftex}). - -The \TeX\ \filename{.fmt} (high-speed format) and the similar files for -MetaPost and \MF\ are now stored in subdirectories of \dirname{texmf/web2c}, -instead of in the directory itself (although the directory is still -searched, for the sake of existing \filename{.fmt}'s). The -subdirectories are named for the `engine' in use, such as \filename{tex} -or \filename{pdftex} or \filename{xetex}. This change should be -invisible in normal use. - -The (plain) \texttt{tex} program no longer reads \texttt{\%\&} first -lines to determine what format to run; it is the pure Knuthian \TeX. -(\LaTeX\ and everything else do still read \texttt{\%\&} lines). - -Of course the year also saw (the usual) hundreds of other updates to -packages and programs. As usual, please check \acro{CTAN} -(\url{http://www.ctan.org}) for updates. - -Internally, the source tree is now stored in Subversion, with a standard -web interface for viewing the tree, as linked from our home page. -Although not visible in the final distribution, we expect this will -provide a stable development foundation for future years. - -Finally, in May 2006 Thomas Esser announced that he would no longer be -updating te\TeX{} (\url{http://tug.org/tetex}). As a result, there was -been a surge of interest in \TL{}, especially among \GNU/Linux -distributors. (There is a new \texttt{tetex} installation scheme in -\TL{}, which provides an approximate equivalent.) We hope this will -eventually translate to improvements in the \TeX\ environment for -everyone. - -\medskip \noindent -Final note on the past: all releases of \TL{}, along with ancillary -material such as \CD\ labels, are available at -\url{ftp://tug.org/historic/systems/texlive}. - -\ifx\HCode\undefined\else\HCode{} -\subsection{Present} -\label{sec:tlcurrent} - -In 2008, the entire \TL{} infrastructure was redesigned and -reimplemented. Complete information about an installation is now stored -in a plain text file \filename{tlpkg/texlive.tlpdb}. - -Among other things, this finally makes possible upgrading a \TL{} -installation over the Internet after the initial installation, a feature -MiK\TeX\ has provided for many years. We expect to regularly update new -packages as they are released to \CTAN. - -The major new engine Lua\TeX\ (\url{http://luatex.org}) is included; -besides a new level of flexibility in typesetting, this provides an -excellent scripting language for use both inside and outside of \TeX\ -documents. - -Support among Windows and the Unix-based platforms is now much more -uniform. In particular, most Perl and Lua scripts are now available on -Windows, using the Perl internally distributed with \TL. - -The new \cmdname{tlmgr} script (section~\ref{sec:tlmgr}) is the -general interface for managing \TL{} after the initial installation. -It handles package updates and consequent regeneration of formats, map -files, and language files, optionally including local additions. - -With the advent of \cmdname{tlmgr}, the \cmdname{texconfig} actions to -edit the format and hyphenation configuration files are now disabled. - -The \cmdname{xindy} indexing program -(\url{http://xindy.sourceforge.net/}) is now included on most platforms. - -The \cmdname{kpsewhich} tool can now report all matches for a given file -(option \optname{--all}) and limit matches to a given subdirectory -(option \optname{--subdir}). - -The \cmdname{dvipdfmx} program now includes functionality to extract -bounding box information, via the command name \cmdname{extractbb}; this -was one of the last features provided by \cmdname{dvipdfm} not in -\cmdname{dvipdfmx}. - -The font aliases \filename{Times-Roman}, \filename{Helvetica}, and so on -have been removed. Different packages expected them to behave -differently (in particular, to have different encodings), and there was -no good way to resolve this. - -The \pkgname{platex} format has been removed, to resolve a name conflict -with a completely different Japanese \pkgname{platex}; the -\pkgname{polski} package is now the main Polish support. - -Internally, the \web\ string pool files are now compiled into the -binaries, to ease upgrades. - -Finally, the changes made by Donald Knuth in his `\TeX\ tuneup of 2008' -are included in this release. See -\url{http://tug.org/TUGboat/Articles/tb29-2/tb92knut.pdf}. - - -\subsection{Future} - -\emph{\TL{} is not perfect!} (And never will be.) We intend to -continue to release new versions, and would like to provide more help -material, more utilities, more installation programs, and (of course) an -ever-improved and better-checked tree of macros and fonts. This work is -all done by hard-pressed volunteers in their limited spare time, and a -great deal remains to be done. Please see -\url{http://tug.org/texlive/contribute.html}. - -Please send corrections, suggestions, and offers of help to: -\begin{quote} -\email{tex-live@tug.org} \\ -\url{http://tug.org/texlive} -\end{quote} - -\medskip -\noindent \textsl{Happy \TeX ing!} - -\end{document} diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/live-tl7.tex b/Master/texmf-doc/source/texlive/texlive-en/archive/live-tl7.tex deleted file mode 100644 index 1e8ee77312b..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/live-tl7.tex +++ /dev/null @@ -1,3554 +0,0 @@ -% -% change history (started May 13th 2002) -% 2002/05/13: added tex-langafrican to list of collections -% 2002/05/14: corrected example files, other small errors noted by Volker -% 2002/05/18: win32 updates, by Fabrice -% 2002/05/25: remove mention of sizes, and bsr-interpolated; add Gutenberg -\documentclass{article} -\advance\textwidth by 1in -\advance\oddsidemargin by -1in -\advance\evensidemargin by -1in -\newsavebox{\warnbox} -\def\Q#1{\par\vskip6pt\leftline{#1}\par} -\setcounter{tocdepth}{2} -\pretolerance=1000 -\tolerance=1500 -\hbadness=3000 -\vbadness=3000 -\hyphenpenalty=400 -\renewcommand{\topfraction}{0.85} -\renewcommand{\floatpagefraction}{0.86} -\renewcommand{\textfraction}{0.1} -\setcounter{topnumber}{5} -\setcounter{totalnumber}{5} -\def\eTeX{$\varepsilon$-\TeX} -\def\Dash{---} -\def\hyph{-} -\def\OMEGA{$\Omega$} -\def\bs{{\protect\normalfont\ttfamily\char'134}} -\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} -\def\La{La} -\let\textsl\textit -\let\sl\it -\let\slfamily\itfamily -\def\ttdefault{cmtt} -\usepackage{tex-live} -\begin{document} -%\makeatletter\@ifundefined{HRestore}{}{\HRestore\noalign}\makeatother -\author{Sebastian Rahtz\\ -\texttt{sebastian.rahtz@oucs.ox.ac.uk} -%Michel Goossens\\ -%\texttt{m.goossens@cern.ch} -} -\title{The \protect\TeX\ Live Guide, 7th edition} -\date{May 2002} -\maketitle -\begin{multicols}{2} -\tableofcontents -\listoftables -\end{multicols} -\section{Introduction}\label{sec:intro} -This documentation describes the - main features of the \TeXLive{} 7 \CD{}\Dash a \TeX{}/\LaTeX{} - distribution for Unix, Linux, MacOSX, and Windows32 systems that includes - \TeX{}, \LaTeXe{}, \MF, \MP, \cmdname{Makeindex}, and \BibTeX{}; and - a wide-ranging set of macros, fonts and documentation conforming to - the \emph{\TeX{} Directory Standard} (\TDS{})\Dash which can be used - with nearly every \TeX{} setup. - - This \TeX{} package uses the \Webc{} version 7.3.7 - implementation of the programs, which tries to make \TeX{}ing as - easy as possible, and takes full advantage of the efficient and - highly customizable \KPS{} library from Karl Berry and Olaf Weber. - It can be run either directly from the \CD{} or installed on a hard - disk. - -Most of the runnable systems on the \CD{} include a large set of -drivers and support programs for \TeX, including \cmdname{dvips} -(PostScript driver), \cmdname{dvipdfm} (dvi to PDF), -\cmdname{xdvi} (X Windows previewer), -\cmdname{dvilj} (HP LaserJet driver), \cmdname{lacheck} (\LaTeX{} -syntax checker), \cmdname{tex4ht} (\TeX{} to HTML converter), -\cmdname{dviconcat} and \cmdname{dviselect}, \cmdname{dv2dt} and - \cmdname{dt2dv} (\texttt{dvi} to ASCII and vice versa), and Angus - Duggan's PostScript utilities. - -\subsection{Extensions to \TeX} - -The \TeXLive{} runnable systems contain three extended versions of -standard \TeX: -\begin{enumerate} -\item \eTeX, which adds a small but powerful set of new primitives, - and the \TeXXeT{} extensions for left to right typesetting; in - default mode, \eTeX{} is 100\% compatible with ordinary \TeX. See - \OnCD{texmf/doc/etex/base/etex_man.pdf} on the \CD{} for details. -\item pdf\TeX, which can optionally write Acrobat PDF format instead - of \dvi{}. You will find the user manual in - \OnCD{texmf/doc/pdftex/pdftex-l.pdf}. The - file \OnCD{texmf/doc/pdftex/samplepdf/samplepdf.tex} shows how it is - used. The \LaTeX{} \pkgname{hyperref} package has an option - `\optname{pdftex}', which turns on all the program features. -\item \OMEGA{} (Omega), which works internally with 16-bit characters, - using Unicode; this allows it to directly work with almost all the - world's scripts simultaneously. It also supports dynamically loaded - `\OMEGA{} Translation Processes' (\acro{OTP}s), which allow the user - to define complex transformations to be performed on arbitrary - streams of input. See \OnCD{texmf/doc/omega/base/doc-1.8.tex} for some - (not necessarily up to date) documentation. -\end{enumerate} -\eTeX{} (version 2.1) is stable, although subsequent releases will add -new functionality. pdf\TeX{} (version 1.00b) is also stable, -but is still being improved. -\OMEGA{} (version 1.23) is under development; the version -on this \CD{} is that current as of May 2002. - - -\section[Structure and contents of the CD-ROM]{Structure - and contents of the \protect\CD{}} -The important \CD{} top-level directories are listed below. -\begin{description} -\item[bin] The \TeX{} family programs, arranged in separate platform - directories. -\item[Books] Examples related to some books about \TeX. -\item[FAQ] Frequently Asked Questions, in English, French, and German. -\item[MacOSX] Support programs for MacOSX users -\item[info] Documentation in \acro{GNU} `info' format for the \TeX{} - system. -\item[man] Documentation in the form of Unix man pages for the \TeX{} - system. -\item[setupw32] directory contains material for installation and use - under Windows (see section \ref{sec:wintex} on p.~\pageref{sec:wintex}). -\item[source] The source of all programs, including the main \Webc{} - \TeX{} and \MF{} distributions. These are stored in a bzip2-compressed - tar archive. -\item[support] Various bits of \TeX-related software which are - \emph{not} installed by default, support programs, and a complete - distribution of \cmdname{Ghostscript} version 7.05. - You can find here some other programs (editors, \TeX\ shells), which - are usually absent from Windows installations, dedicated for beginners. - They can be installed with the \texttt{TeXSetup.exe} Windows installation - program. -\item[texmf] The main support tree of macros, fonts and documentation; -\item[usergrps] Material about \TeX\ User Groups. -\end{description} - -There are also two installation scripts for Unix systems, -\texttt{install-cd.sh} and \texttt{install-pkg.sh}; we discuss -them on in section \ref{sec:install} on p.~\pageref{sec:install}. - -\subsection[Packages and collections]{Packages and collections} -\label{packages} -The \TeXLive{} \texttt{texmf} tree consists of various `collections', -each of which refers to a set of `packages', of which there are over 700 -on the \CD{}. Normal installation allows the -user to copy all of a collection to a local hard disk from the \CD{}, but -it is also possible to install just one package of a collection. - -The collections add functionality to a \TeX\ system. One of them, named -`tex-basic', is necessary for almost all \TeX\ tasks, -and two others, called `tex-latex' and `tex-pdftex' are highly -recommended for most users. All others are optional. -The collections (defined by XML files in \texttt{texmf/tpm/collections}) -and their short descriptions are listed below. - -\begin{description} - \item[tex-basic] - These files are regarded as basic for any \TeX\ system, covering -plain \TeX\ macros, Computer Modern fonts, and configuration for common -drivers. - \item[tex-bibtexextra] - Additional, extensive libraries of BibTeX styles and bibliographies. - \item[tex-chemistry] - Essential chemistry - \item[tex-context] - Hans Hagen's powerful macro package, ConText - \item[tex-documentation] - Assorted useful documentation and guides - \item[tex-etex] - Support files for an extended \TeX\ - \item[tex-extrabin] - Various useful, but non-essential, support programs. Includes - programs and macros for texinfo system; programs for dvi file - manipulation, etc. - \item[tex-fontbin] - Programs for conversion between font formats, testing fonts - (virtual fonts stuff, .gf and .pk manipulation, - mft, fontinst, etc.) - \item[tex-fontsextra] - All sorts of extra fonts - \item[tex-formatsextra] - A collection of \TeX\ `formats', ie large-scale -macro packages designed to be dumped into .fmt file - \item[tex-games] - Setups for typesetting various board games, including chess - \item[tex-genericextra] - This is a mixed bag of macro packages and fonts which do not seem -to belong elsewhere - \item[tex-htmlxml] - Packages to convert \LaTeX\ to XML/HTML, and typeset XML/SGML - \item[tex-langafrican] - Support for some African scripts - \item[tex-langarmenian] - Essential armenian - \item[tex-langcjk] -Essential CJK (Chinese, Japanese, Korean) macros and fonts - \item[tex-langcroatian] - Essential croatian - \item[tex-langcyrillic] - Fonts and macro packages to typeset Cyrillic texts. - \item[tex-langczechslovak] - Pick this if you want Czech/Slovak fonts and other packages - \item[tex-langdanish] - Essential Danish - \item[tex-langdutch] - Essential Dutch - \item[tex-langfinnish] - Essential Finnish - \item[tex-langfrench] - Essential French - \item[tex-langgerman] - Essential German - \item[tex-langgreek] - Essential Greek - \item[tex-langhungarian] - Essential Hungarian - \item[tex-langindic] - Essential Indic - \item[tex-langitalian] - Essential Italian - \item[tex-langlatin] - Essential Latin - \item[tex-langmanju] - Essential Manju - \item[tex-langmongolian] - Essential mongolian - \item[tex-langnorwegian] - Essential Norwegian - \item[tex-langother] - Other languages - \item[tex-langpolish] - Pick this if you want Polish fonts and other packages - \item[tex-langportuguese] - Essential Portuguese - \item[tex-langspanish] - Essential Spanish - \item[tex-langswedish] - Essential Swedish - \item[tex-langtibetan] - Fonts and support for typesetting Tibetan - \item[tex-langukenglish] - Essential UK English - \item[tex-langvietnamese] - Essential Vietnamese - \item[tex-latex] - These packages are either mandated by the core \LaTeX\ team, -or very commonly recommended - \item[tex-latexextra] - A large collection of add-on packages for \LaTeX\ - \item[tex-mathextra] - Extra math - \item[tex-metapost] - MetaPost (and MetaFont) drawing packages - \item[tex-music] - Music typesetting packages - \item[tex-omega] - Omega, a 16-bit extended \TeX\ by John Plaice and Yannis Haralambous - \item[tex-pdftex] - Support files for Han The Thanh's variant of \TeX\ which can -generate PDF output - \item[tex-pictures] - Essential graphics - \item[tex-plainextra] - Plain \TeX\ extra macros - \item[tex-psfonts] - Essential psfonts - \item[tex-psutils] - Utilities to manipulate PostScript files - \item[tex-publishers] - Essential publishers - \item[tex-t1utils] - Utilities to manipulate Type1 fonts - \item[tex-texbooks] - Examples and other material from various books about TeX/LaTeX. - \item[tex-theses] - Macro packages from various Universities for their thesis styles - \item[tex-ttfutils] - Utilities to manipulate TrueType fonts - \item[win32-support] - You can choose individual tools from this collection. - There are many \TeX\ oriented editors, graphics files - toolsets, etc. -\end{description} - -The directory \texttt{texmf/tpm/packages} contains lists -of all files in each package (used by the installation programs). - -\section{Installation and use under Unix} -\label{sec:install} -You can use the \TeXLive{} \CD{} in three ways: -\begin{enumerate} -\item You can mount the \CD{} on your file system, run -the \texttt{install-cd.sh} script, and select the option \verb|| - (`do not install files, set up to run off CD-ROM'), - and run everything off the \CD; this takes very - little disk space, and gives you immediate access to everything on - the \CD; although the performance will not be optimal, it is - perfectly acceptable on, for instance, PCs running Linux. You could - also copy the entire CD contents to your hard disk and work in this way. -\item You can install all or part of the system to your local hard - disk; this is the best method for many people, if they have enough - disk space to spare (a minimum of about 100 megabytes, or 300 - megabytes for a recommended good-sized system). -\item You can install selected packages to work either with your - existing \TeX{} system or a \TeXLive{} system you installed earlier. -\end{enumerate} -Each of these methods is described in more detail in the following -sections. - -\ifSingleColumn -\begin{figure*} - \begin{center} - \leavevmode -\fi -\begin{warningbox} -\textbf{Warning: } This \CD{} is in ISO 9660 (High Sierra) format, -with Rock Ridge and Joliet extensions. In order to take full advantage -of the \CD{} on a Unix system, your system needs to be able to use -the Rock Ridge extensions. Please consult the documentation for your -\cmdname{mount} command to see if it is possible. If you have several -different machines on a local network, see if you can mount the -\CD{} on one which \emph{does} support Rock Ridge, and use this with -the others. - -\leavevmode\quad -Linux, FreeBSD, Sun, SGI and DEC Alpha systems should be able to use -the \CD{} with no problems. We would appreciate receiving detailed advice -from other system users who also succeed, for future versions of this -documentation. - -\leavevmode\quad -The discussion below about installation assumes you have been able to mount -the \CD{} with full Rock Ridge compatibility. -\end{warningbox} -\ifSingleColumn - \end{center} -\end{figure*} -\fi - -%\begin{addbymb} -\subsection[Pre-installation procedure for MacOSX users] -{Pre-installation procedure for MacOSX users} -If you do not run MacOSX, you should skip this section. - -The \texttt{install-cd.sh} script is a \emph{sh} script (begins with -``\verb=#!/bin/sh=''), but -on MacOSX \cmdname{sh} is unable to run it because -\cmdname{sh} is -emulated. However, \cmdname{bash} will run it. Unfortunately (again) -\cmdname{bash} is not -installed by default on MacOSX\footnote{there are some suggestions this will -change in the future and even -that \cmdname{bash} will be used to emulate \cmdname{sh}, -in which case it might be true -that in future versions of MacOSX, the script will just work.}. -\begin{enumerate} -\item\label{test-bash} (optional) See if \path|bash| is already installed. -Launch \path|Terminal| -(\path|/Applications/utilities/Terminal|) and type in a window -\begin{alltt} ->> \Ucom{rehash; which bash} -\end{alltt} -the answer will be: -\begin{itemize} -\item the bash location (e.g. \path|/bin/bash| or \path|/usr/local/bin/bash|) if installed; -\item \texttt{bash: command not found} if not installed. -\end{itemize} - -If bash is already installed, skip to \ref{std-install} - -\item bash installation: -\begin{description} -\item[Mac friendly procedure] -Look in the \path|MacOSX| directory of the \CD{} -for an image disk named \path|bash.dmg|. mount that -file by double-clicking it. The disk image (volume) will be mounted. -Then start the \path|i-Installer| application on that volume. You will be asked -to authenticate, if you have never seen that before, you might not have -enough privileges to install. Just enter your own user name and -password. Hit install. \path|bash| will be installed on your system. -\item[Terminal procedure] -\begin{enumerate} -\item Log in as an admin user, at least a user with Admin privileges or -sudo user or as the System Administrator. -\item Open the \path|MacOSX| directory on the \CD{} and copy -\path|bash.tar.gz| -to your home directory (\texttt{\~{}/}) -\item Then launch \path|Terminal| and type or copy/paste the -line below in a Terminal window): -\begin{alltt} ->> \Ucom{(cd /usr/local/; sudo tar xvzf ~/bash.tar.gz)} -\end{alltt} -type a carriage-return: you will be asked for your password, and -\path|bash| will be -installed. -\item Quit \path|Terminal|. -\end{enumerate} -\end{description} -\item Now after using either install method, goto \ref{test-bash}: -you must obtain \path|/usr/local/bin/bash|\ldots{} (if not, try to log out and in). -\item\label{std-install} The installation procedure is the -same on MacOSX than on other UNIX platforms (as MacOSX is UNIX, -that's quite normal!). Nevertheless, you should read what follows: -\begin{itemize} - \item Note that in all commands of the following sections, -\cmdname{sh} must be replaced by \texttt{sudo bash}: -\begin{alltt} ->> \Ucom{sh install-cd.sh} -\end{alltt} -becomes -\begin{alltt} ->> \Ucom{sudo bash install-cd.sh} -\end{alltt} -etc. -\item On MacOSX, cd are auto-mounted: you \emph{don't} need to use -\texttt{mount}. The \CD{} will be mounted in the \path|/Volumes/| -directory: in order to make it the current directory, you just have to -type in \path|Terminal|: -\begin{alltt} ->> \Ucom{cd /Volumes/TeXLive-7...} -\end{alltt} -(complete this line with the real name of the \CD{}: using -``auto completion'' by pressing the \texttt{} -key will do it). -\end{itemize} -\end{enumerate} -%\end{addbymb} - -\subsection[Running \protect\TeXLive{} from the CD-ROM]{Running \protect\TeXLive{} from the \protect\CD} -The organisation of \Webc{} means that you can run programs simply by -adding the appropriate directory under \path|bin| on the \CD{} to -your \texttt{PATH}, and the support files will all be found with no further -ado. The following shows the list of available systems and the -corresponding directories. \textbf{Only x86 Linux, Mac OSX, and - Windows are available on the default CD. You need to ask -for the Unix CD if you need the other systems.} - -\begin{flushleft} -\begin{tabular}{@{}l>{\ttfamily}ll} -Compaq Alpha Linux & alpha-linux & CD2\\ -Compaq Alphaev5 OSF 4.0d & alphaev5-osf4.0d & CD2\\ -HP9000 HPUX 10.20 & hppa2.0-hpux10.20 & CD2\\ -IBM RS 6000 AIX 4.2.* & rs6000-aix4.2.1.0 & CD2\\ -Intel x86 Solaris 2.8 & i386-solaris2.8 & CD2\\ -Intel x86 with GNU/Linux & i386-linux & CD1\\ -Mac OSX & powerpc-darwin5.3 & CD1\\ -Sun Sparc Solaris 2.7 & sparc-solaris2.7 & CD2\\ -Windows 9X/ME/NT/2K/XP & win32 & CD1\\ -\end{tabular} -\end{flushleft} - -You may worry that when you subsequently make fonts or change -configuration, things will go wrong because you cannot change files on -the \CD{}. However, you can maintain a parallel, writeable, \TeX{} -tree on your hard disk; this is searched before the main tree on the -\CD{}. The default location is \path|texmf-var| on the CD -(which does not exist!), so you \emph{must} override this by setting -the \texttt{VARTEXMF} environment variable. - - -Thus \emph{sh} or \emph{bash} users on an Intel PC -running Linux can mount the \TeXLive{} \CD{} on -\file{/mnt/cdrom} by issuing the command: - -\begin{alltt} ->> \Ucom{mount -t iso9660 /dev/cdrom /mnt/cdrom} -\end{alltt} -Then they should change the current directory to \path|/mnt/cdrom|, run -\begin{alltt} ->> \Ucom{sh install-cd.sh} -\end{alltt} -and select the option \verb|| (\emph{do not install files, set up to run -off CD-ROM}). After that, they should include the directory containing -the binaries for the given architecture into the search path -by updating the \texttt{PATH} variable. -\begin{verbatim} -PATH=/mnt/cdrom/bin/i386-linux:$PATH -export PATH -VARTEXMF=/usr/TeX/texmf-var -export VARTEXMF -\end{verbatim} -%\begin{addbymb} -\begin{description} - \item[MacOSX users] On MacOSX, the default shell is \texttt{tcsh}: -\begin{verbatim} -setenv PATH /Volumes//bin/powerpc-darwin5.3:${PATH} -setenv VARTEXMF /usr/TeX/texmf-var -\end{verbatim} -\end{description} -%\end{addbymb} -For convenience, these statements can also be entered into the -\texttt{.profile} script. -%\begin{addbymb} -(for \texttt{tcsh} on MacOSX, -\verb=~/Library/init/tcsh/rc.mine=). -%\end{addbymb} - -If in doubt, ask your local system support guru to help you work out -how to mount your \CD{} or which directory to use for your system. - -Appropriate support files will be installed on your hard disk the -first time you need them. You can edit and change local configuration -files which are stored to the directory designated -by \texttt{\$VARTEXMF}. Any format file that is needed -will be generated and stored here. - -%------------------------------------------------ -\subsection{Installing \protect\TeXLive{} to a hard disk} -All of the necessary steps to install all or part of the distribution -on your hard disk are achieved by mounting the \CD{}, changing to the -top-level directory, and typing: -\begin{alltt} ->> \Ucom{sh install-cd.sh} -\end{alltt} -(On some Unix systems, you may need to use \cmdname{sh5} or -\cmdname{bash}.) This script works by accessing lists of collections -and packages from the \CD{}, and trying to guess what sort of computer -system you are on. It should start by displaying the following: -\verbatiminput{../examples/ex1.tex} -It will then show the main control screen -(Figure~\ref{ins1}), which lets you change five -things: -\begin{enumerate} -\item the type of system you are on, or want to install for; -\item the \emph{installation scheme} you want to use (eg full, - recommended, basic etc) -\item the collections you want to change from -the installation scheme (they are organised into two sets: -\emph{standard collections} and \emph{language collections}); -\item the location on your hard disk to put the files; -\item some runtime behaviour features. -\end{enumerate} - -\begin{figure*} -\begin{center} -\ifnum\Status=2 -\boxedverbatiminput{../examples/ex2.tex} -\else -\begin{minipage}{0.8\textwidth} -\boxedverbatiminput{../examples/ex2.tex} -\end{minipage} -\fi -\caption{Main control screen}\label{ins1} -\end{center} -\end{figure*} - -You choose options by typing a letter or number and pressing `return'. -In the example, a Linux GNU/Linux system has been detected, the -default set of collections will be installed, and -the default installation directory is \path|/usr/TeX|; note -that the disk space required for the current installation -configuration is also displayed. If you make a suggested setup, you -need about 60 megabytes of disk free; however, the basic setup will -only take about 30 megabytes, and you can enhance it with selected -packages as you need them. - -%\begin{addbymb} -\begin{description} - \item[MacOSX users] Most frontends (\emph{TeXShop}, - \emph{ITeXMac}\ldots) use the \teTeX{} default location - which is \path|/usr/local/teTeX|, so, Mac users could find interest - in installing \TeXLive{} in \path|/usr/local/teTeX| -rather than in \path|/usr/TeX|. -\end{description} -%\end{addbymb} - -Under the directory you choose for installation, the installation -script will put the binaries in a subdirectory of \path|bin|, and the -support tree in \path|texmf|. An additional tree \path|texmf-var| -will contain copies of configuration files (except the main -\path|texmf.cnf|), which are to be modified by \path|texconfig| program. -This tree will also store generated format files for \TeX, \MF, etc. - -\begin{figure*} -\begin{center} -\ifnum\Status=2 -\boxedverbatiminput{../examples/ex3.tex} -\else -\begin{minipage}{.80\linewidth} -\footnotesize -\boxedverbatiminput{../examples/ex3.tex} -\end{minipage} -\fi -\caption{Selecting standard collections}\label{ins2} -\end{center} -\end{figure*} - -\begin{figure*} -\begin{center} -\ifnum\Status=2 -\boxedverbatiminput{../examples/ex4.tex} -\else -\begin{minipage}{.80\linewidth} -\footnotesize -\boxedverbatiminput{../examples/ex4.tex} -\end{minipage} -\fi -\caption{Selecting language collections}\label{ins3} -\end{center} -\end{figure*} - -When you choose || for \emph{standard collections}, you will see -the display of available collections (Figure \ref{ins2}). Each -collection --- TeX macro files, Metafont font families, and so on --- -consists of several packages. You can toggle their inclusion on or -off by pressing the key. Note that the selection letter keys are case -sensitive. - -When you choose || for \emph{language collections}, you will see -the display of available language support collections (Figure -\ref{ins3}). Each collection consists of several packages, which -provide features like hyphenation files and fonts. - -The || for \emph{options} item lets you decide whether to make new fonts -be created in another location (if you want the main package mounted -read-only for most users), and whether to make symbolic links for the -binaries, \cmdname{man} and \acro{GNU} \cmdname{info} pages in the `standard' -locations; you'll need `root' permissions for tasks to do this, of course. - -When you are finished, return to the main screen, and ask the -installation to start. It will take each of the collections and -systems that you requested, consult the list of files on the \CD{}, -and build a master list of files to transfer. These will then be -copied to your hard disk. If you installed a system, -an initialization sequence is now run -(creating format files, etc.). When this has finished, all you need do -is add the correct subdirectory of \texttt{bin} in the \TeX{} -installation to your path, and start using \TeX. If you want, you can -move the binaries up one level, e.g.\ from -\path|/usr/local/bin/alpha-osf3.2| -to \path|/usr/local/bin|; if you do this, however, you must -edit \path|texmf/web2c/texmf.cnf| (see Appendix~\ref{app:texmf.cnf}) -and change the line near the start which reads -\begin{verbatim} - TEXMFMAIN = $SELFAUTOPARENT -\end{verbatim} -to -\begin{verbatim} - TEXMFMAIN = $SELFAUTODIR -\end{verbatim} - -If you move the whole installation to another directory tree entirely, you -need to edit \envname{TEXMFMAIN} to specify the support tree explicitly, and -set \envname{TEXMFCNF} in your environment to \path|$TEXMFMAIN/texmf/web2c|. - -%------------------------------------------------ - -\subsection{Installing individual packages from \protect\TeXLive{} to a hard - disk} You may want to use the \TeXLive{} \CD{} to either update an -existing setup, or add features to an earlier installation from the -\CD{}. The main installation program is intended for the first time -only, and subsequently you should use the \texttt{install-pkg.sh} -script on the \CD{}. Run this by mounting the \CD{}, changing to -the mounted directory, and typing - -\begin{alltt} ->> \Ucom{sh install-pkg.sh \emph{options}} -\end{alltt} - - -The script supports nine options; the first four let you set the -individual package you want to install, the whole collection (i.e., -\texttt{tex-mathextra}), the name of the mounted \CD{} directory, and -the name of the directory containing the list files (normally these -latter two will be set automatically): - -\begin{tabular}{ll} -\texttt{-{}-package=}\emph{name} & \\ -\texttt{-{}-collection=}\emph{name} & \\ -\texttt{-{}-cddir=}\emph{name} & \\ -\texttt{-{}-listdir=}\emph{name} & \\ -\end{tabular} - -What actually happens is controlled by four more switches; the first -two allow you to exclude documentation or source files from the -installation, the third stops the default action of running -\texttt{mktexlsr} on completion to rebuild the file database, and -the last does nothing but list the files that would be installed: - -\begin{tabular}{ll} -\texttt{-{}-nodoc} & \\ -\texttt{-{}-nosrc} & \\ -\texttt{-{}-nohash} & \\ -\texttt{-{}-listonly} & \\ -\end{tabular} - -Finally, you can specify that, instead of installing the files, the script -should make a \cmdname{tar} archive in a specified location: - -\begin{tabular}{ll} -\texttt{-{}-archive=}\emph{name} & \\ -\end{tabular} - -Thus, if we simply wanted to see the files that make up the package -\pkgname{fancyhdr} before we installed it, our command and output would be -as follows: - -\begin{alltt} -\ifSingleColumn>> \Ucom{sh install-pkg.sh --package=fancyhdr --listonly} -\else>> \Ucom{sh install-pkg.sh -{}-package=fancyhdr \bs} ->> \Ucom{-{}-listonly} -\fi{} -texmf/doc/latex/fancyhdr/fancyhdr.dvi -texmf/doc/latex/fancyhdr/fancyhdr.tex -texmf/lists/fancyhdr -texmf/source/latex/fancyhdr/README -texmf/source/latex/fancyhdr/fancyheadings.new -texmf/tex/latex/fancyhdr/extramarks.sty -texmf/tex/latex/fancyhdr/fancyhdr.sty -texmf/tex/latex/fancyhdr/fixmarks.sty -\end{alltt} -Other examples of usage are: -\begin{itemize} -\item Install the \LaTeX{} package \texttt{natbib}: -\begin{alltt} ->> \Ucom{sh install-pkg.sh --package=natbib} -\end{alltt} -\item Install the \LaTeX{} package \texttt{alg} with no source files and no -documentation: -\begin{alltt} -\ifSingleColumn>> \Ucom{sh install-pkg.sh --package=alg --nosrc --nodoc} -\else>> \Ucom{sh install-pkg.sh -{}-package=alg \bs} ->> \Ucom{-{}-nosrc -{}-nodoc} -\fi\end{alltt} -\item Install all the packages available in the collection containing additional -Plain \TeX\ macros: -\begin{alltt} ->> \Ucom{sh install-pkg.sh --collection=tex-plainextra} -\end{alltt} -\item Place all files which are needed for PSTricks -in a \cmdname{tar} file in \path|/tmp|: -\begin{alltt} -\ifSingleColumn>> \Ucom{sh install-pkg.sh --package=pstricks --archive=/tmp/pstricks.tar} -\else ->> \Ucom{sh install-pkg.sh -{}-package=pstricks \bs} ->> \Ucom{-{}-archive=/tmp/pstricks.tar} -\fi\end{alltt} -\end{itemize} - -\subsection{The texconfig program} -\label{ssec:tex} - -After the installation program has copied all files to their final -locations, you can use a program called \cmdname{texconfig} that -allows you to configure the system to fit your local needs. This can -be called at any other time to change your setup, with a full-screen -(which requires the \cmdname{dialog} program, included as part of the -binary packages) or command-line interface. -It should be used for all maintenance, such as changes of installed -printers, or rebuilding the file database. Both modes have help text -to guide you through the facilities. - -\section{Installation and use under Windows} -\label{sec:wintex} -This section only applies to systems running Windows 9x, \acro{ME}, -\acro{NT}, \acro{2K} or \acro{XP}. - -It is also necessary to have your Windows set up so that it uses the -Microsoft Joliet extensions for reading \CD s; simply look at the -\CD{} in Explorer and see whether it shows long, mixed-case, file -names. If it does not, you cannot use the ready-to-run system on the -\CD. - -This Win32 \TeX{} systems includes a \texttt{dvi} previewer, -\textsf{Windvi}, which is similar in usage to the established Unix -\textsf{xdvi}. The documentation can be found in -\OnCD{texmf/doc/html/windvi/windvi.html}. - -\subsection[The TeXLive.exe program]{The \texttt{TeXLive.exe} program} - -\begin{figure*} - \begin{center} - \ifnum \Status=1 - \includegraphics[width=.7\textwidth]{../pictures/Welcome-to-TeXLive} - \else - \ifnum \Status=2 -\includegraphics[bb=20 20 575 432]{../pictures/Welcome-to-TeXLive.gif} - \else - \includegraphics[width=.7\textwidth]{../pictures/Welcome-to-TeXLive} - \fi - \fi - \end{center} - \caption{``Welcome to \TeXLive'' window}\label{graph:welcome} -\end{figure*} - -If your computer is configured to let the \CD{} autostart, then a -dialog box with a menu bar will popup on the screen, and you will have several choices -from there: -\begin{itemize} -\item Install \TeX{} on your hard disk, -\item Install TeX-oriented editors on your hard disk, -\item Install support packages on your hard disk (Ghostscript, NetPBM, - \ldots) -\item Do some maintenance on you \TeX{} system, -\item Remove the \TeX{} system, -\item Use \TeX{} off the \CD{}, -\item Cleanup the temporary files created on your hard disk when using - \TeX{} off the \CD{}, -\item Update some of the DLLs on your system, -\item Browse some documentation: \TeXLive{} documentation, TUG web - pages, \fpTeX web pages, -\item Run the \cmdname{TeXdocTK} application to find specific documentation. -\end{itemize} - -If your \CD{} does not autostart, you can explicitly run the program -by double clicking on \path|bin/win32/TeXLive.exe| on the \CD{} from -the explorer window. - -\subsection[Running \protect\TeXLive{} from the CD-ROM]{Running from -the \protect\CD{}} -You can run all the \TeX{} programs directly off the \CD, and have -access to all the macros and fonts immediately, at the price of a -slower performance than if you install on the hard disk. -To work effectively, one needs to modify -environment variables and to create some small auxiliary directories on a -hard disk. These directories will contain necessary configuration files -allowing the user to modify programs settings and to generate a necessary -format file. Moreover, automatically generated font files will be stored -there too. - -Should you want to run \TeX{} this way, you will have to follow these -steps: -\begin{enumerate} -\item from the menu, chose \verb|Explore CD-Rom|, then - \verb|Select a text editor|, a dialog box will open to select some \path|.exe| - program. - - This program needs to be a \TeX{} oriented editor. It must be able - to run the \TeX{} compiler, previewer and any other needed tool. If - you don't have one already installed on your system, you can install - one from the \CD{}, details section~{\ref{sec:texlive-install}}. - - \emph{There is no way we can guess if the program you will - select is actually a text editor, so be careful}. - Here is a list of frequently used \TeX{} editors: -\begin{center} - \begin{tabular}[ht]{ll} - GNU Emacs & \path|c:\Program Files\NTEmacs\bin\runemacs.exe| \\ - XEmacs & \path|c:\Program Files\XEmacs\XEmacs-21.2\i586-pc-win32\xemacs.exe| \\ - WinShell & \path|c:\Program Files\WinShell\WinShell.exe| \\ - WinEdt & \path|c:\Program Files\WinEdt Team\WinEdt\WinEdt.exe|\\ - TeXnicCenter & \path|c:\Program Files\TeXnicCenter\TEXCNTR.exe| - \end{tabular} -\end{center} - The program - selected will be memorized as the editor to use for future runs. - -\item from the menu, chose \verb|Explore CD-Rom|, then - \verb|Run TeX off CD-Rom|. The environment will be modified, a small - temporary directory created and some configuration files copied - there. Then, the selected editor selected will be launched, and you - will be able to type in some text, let \TeX{} typeset it and the - view it or print it. - - If Ghostscript is not detected on your machine, you will be warned - that rendering your DVI files might fail. You can install it from - the \path|Install|, \path|Support| menu item. See - section~\ref{sec:texlive-install} for details. - -\item you can select a different text editor any time you want. - -\item if you chose \verb|Cleanup CD-Rom setup|, everything \TeX{} - needed will be removed, comprised the selection of your text - editor, but not the extra packages you may have downloaded and - installed. If you installed \cmdname{WinShell} or \cmdname{NTEmacs}, -they won't be removed. -\end{enumerate} - -The editor is run inside a modified environment. A temporary TDS -compliant texmf tree is build in the temporary area of your computer. -It is needed to store files that may be build on the fly like pk font -files or format files. Configuration files are copied from the \CD{} -to this texmf tree, so that you can edit them if needed. The \path|ls-R| -database is computed for this texmf tree. -Then the \texttt{PATH} and \texttt{TEXMFCNF} environment -variables are set locally, and the editor is run in -this local environment. From within your editor\footnote{Actually, you can - state any other program than a text editor, and select your command - processor for example. You will then get a console with the right - settings to use \TeX{} from the \CD{}.}, you have access to a full -\TeXLive{} environment, all files referenced on the \CD{}. - - -\smallskip {\small\noindent \textbf{[For advanced users:]} You can - also use the small batch file \path|mkloctex.bat| to be called in a - directory \path|setupw32| of the \CD. From the Start menu select - `Run', then browse CD drive and select \path|mkloctex.bat|. Before - starting it, you should add two parameters separated by a space: the - letter of your CD drive and the letter of the hard disk where you - want to install the \TeX\ directory. The whole line should read, - e.g., \verb+d:\setupw32\mkloctex.bat d c+. When installation is - complete, please read carefully the information on screen. If you - are running Windows 9x/ME, then you will have to restart Windows. } - -\subsection{Installing editors or support packages} -\label{sec:texlive-install} - -You can already use the \path|TeXSetup.exe| program to install a -single, not \TeX{} dependent package. This might be either an editor -like \cmdname{WinShell} or \cmdname{NTEmacs}, -or also a support package like \cmdname{NetPBM} -(graphics formats conversion) or \cmdname{Ghostscript}. - -Some of the packages are not free, or not with the same meaning as for -the rest of the \CD{}. These packages have been made available through -the Internet. You need to enable an Internet connection in order to -install them. Chosing the \path|Enable Internet access| subitem will -search your system for an active Internet connection, or start one if -possible. \emph{If your computer is not connected to the Internet, - then the timeout might be long, 30s or more}. So try to enable it -only if you know you have a connection. - -Only a few packages are available from the \CD{}, but the most -important of them: \cmdname{NTEmacs} and \cmdname{WinShell} for the -editors, \cmdname{Ghostscript} and \cmdname{NetPBM} for the other -support packages. \cmdname{NetPBM} is needed for running \TeX{}4ht. - -The downloadable packages are sometimes huge: \cmdname{Perl} is 10Mb, -\cmdname{XEmacs} is 50Mb, so be warned that it can take a lot of time -to install such things. \path|TeXSetup.exe| does not yet provide an -estimation of the time needed to complete the download. - -When installing these packages, \path|TeXSetup| is working in -unattended mode. However, the programs that have their own installer -like WinEdt or Ghostscript for example will require human interaction. - -Those packages who have no specific installer will be unpacked and configured -for your system. You will be required to select some directory where -they will be installed. The directory to select should be the root -directory of the whole installation. Assuming you want to install -NTEmacs and NetPBM, the archive files already contain the -\path|NTEmacs\| and \path|NetPBM\| part, so the directory you have to -select is something like \path|c:\Local| or \path|c:\Program Files|. - -\subsection{Installing to your hard disk} - -Installation is started by letting the CD autostart, and -selecting the item \verb|Install| from the menu, then the subitem -\verb|TeXLive|. This will invoke the \path|TeXSetup.exe|. You can also find -it in the \path|bin/win32| directory and run it. \path|TeXSetup.exe| -is a Windows wizard and it will display several pages while running. - -\begin{description} -\item[Welcome Page] - You can choose a \emph{quick} installation from - there, in this case, the installation will run without any human - assistance from beginning to end, with all the default settings - (Figure~\ref{graph:setup-src}, - \ifnum \Status = 1 - on the left% - \else\ifnum \Status=2 - at the top% - \else - on the left% - \fi\fi - ). However, if you chose to install any support program that has its - own installer like WinEdt or Ghostscript, your intervention might be required. - If you have enough privileges (administrator or power user rights) - under a Windows version where it is applicable, then you can decide - to install the \TeXLive{} for all users or for yourself only by - checking the appropriate box. - - \begin{figure*}[!htb] - The \cmdname{TeXSetup} Wizard\hfill - Source directories for the \TeXLive{} files - - \begin{center} - \ifnum \Status=1 - \includegraphics[width=.48\textwidth]{../pictures/setup-wizard.jpg}\hfill% - \includegraphics[width=.48\textwidth]{../pictures/source-for-texlive.jpg} - \else - \ifnum \Status=2 -\includegraphics[bb=0 0 506 403]{../pictures/setup-wizard.gif} -\includegraphics[bb=0 0 506 403]{../pictures/source-for-texlive.gif} - \else - \includegraphics[width=.48\textwidth]{../pictures/setup-wizard}% - \hfill% - \includegraphics[width=.48\textwidth]{../pictures/source-for-texlive} - \fi - \fi - \caption{The \TeXLive{} setup wizard}\label{graph:setup-src} - \end{center} -\end{figure*} -\item[Source Page] - This page is a bit complex. It will allow you to select two source - directories for your \TeXLive{} system - (Figure~\ref{graph:setup-src}, - \ifnum \Status = 1 - on the right% - \else\ifnum \Status=2 - at the bottom% - \else - on the right% - \fi\fi - ). You will need a \emph{local - source directory} and possibly a \emph{remote source directory}. - - Why do we need both these directories? The very files of the - \TeXLive{} system are on the \CD{}, but some other packages useful - under a Win32 system are not, either because of space lacking or - because their license was not compatible with the \TeXLive{}'s one. - You need to enable Internet downloading if you want to install these - support packages. - - However, don't panic: the default parameters of the setup will allow - you to install a full system using the \CD{} only. Simply, you won't - have \file{WinEdt} for example, but you will be able to install it - later. - - So you can take your files from: - \begin{itemize} - \item the \CD{} or any similar flat tree of files, available through - some standard directory (this means the \CD{} can be mounted on - some remote machine and be made available through network - sharing), - \item a set of \file{.zip} files (this is the case when you are - installing the - \fpTeX{} distribution), - \item the Internet, in this case, the program takes care of - downloading the \file{.zip} files it needs for you. - \end{itemize} - This option is available only if you enable Internet file - downloading in the right part of the page. You also need to - configure this Internet access by selecting to connect either using - Internet Explorer~5 \file{wininet.dll}, or using a direct connection (\texttt{ftp}, - \texttt{http}). -% or using a proxy server. -% Last, you can be assisted in defining the \emph{local source -% directory} and \emph{remote source directory} which will be used -% to copy the files onto your hard disk. The \texttt{browse} buttons -% allow to select a directory for the former, and an url among a list -% of mirrors for the latter. -\item[Root Page] - On this page, you will tell where you want the files to be - installed (Figure~\ref{graph:root-schm}, - \ifnum \Status = 1 - on the left% - \else\ifnum \Status=2 - at the top% - \else - on the left% - \fi\fi - ). Only the root directory really matters, the other ones - are set according to the root one. You may want to make - \path|$TEXMFEXTRA| point to some TDS compliant directory with other - \TeX{} files or assign a different value to - \path|$HOMETEXMF|, which is set by default to whatever Windows think - is your `HOME' location. -\begin{figure*}[!htb] - Root and directories\hfill% - Scheme selection - \begin{center} - \ifnum \Status=1 - \includegraphics[width=.46\textwidth]{../pictures/root-of-installation.jpg}\hfill% - \includegraphics[width=.46\textwidth]{../pictures/scheme-selection.jpg} - \else - \ifnum \Status=2 -\includegraphics[bb=0 0 506 403]{../pictures/root-of-installation.gif} -\includegraphics[bb=0 0 506 403]{../pictures/scheme-selection.gif} - \else - \includegraphics[width=.46\textwidth]{../pictures/root-of-installation}% - \hfill% - \includegraphics[width=.46\textwidth]{../pictures/scheme-selection} - \fi - \fi - \caption{\TeXLive-Setup: Root and directories / Schemes}\label{graph:root-schm} - \end{center} -\end{figure*} -\item[Get TPM Page] - This page does not require any manual intervention. The \file{.tpm} - files which describe collections and packages are retrieved - (possibly from the Internet), unzipped if needed and parsed. -\item[Schemes Page] - On this page, you will select the global scheme of your - installation (Figure~\ref{graph:root-schm}, - \ifnum \Status = 1 - on the right% - \else\ifnum \Status=2 - at the bottom% - \else - on the right% - \fi\fi - ). A scheme is a large set of files targeted at some kind - of usage. There are 3 generic schemes for basic, recommended and - full installation. The other ones are devoted to LUGs (what GUST or - GUTenberg propose for their members) or applications (XML and - \TeX{}). - When a scheme is selected, it is still possible to refine the - selection by checking the appropriate box. If doing so, you will be - presented the packages page to change your selection, else you will - jump to the review page. -\item[Packages Page] - Collections and packages are presented in a tree form - (Figure~\ref{graph:win32-support}, - \ifnum \Status = 1 - on the left% - \else\ifnum \Status=2 - at the top% - \else - on the left% - \fi\fi - ). The links - in the tree are dependency links. Collections \emph{depend on} - packages and maybe other collections, and it is the same for each - package. You can select any package or collection individually, but - your request will be granted only if the object is not requested by - another one which is selected. For example, you can't deselect - \texttt{tex-basic} without deselecting all the collections that - request it. - - The \texttt{win32-support} collection displayed on the picture is Win32 specific. It - holds a number of bonus packages (Figure~\ref{graph:win32-support}, - \ifnum \Status = 1 - on the right% - \else\ifnum \Status=2 - at the bottom% - \else - on the right% - \fi\fi - ) which can be installed - automatically and individually: Ghostscript, the PostScript - interpreter, \TeX{} oriented editors, tools like Perl, - \LaTeX{}2HTML, etc. \emph{None of these packages are selected by - default}. Some of them have an Internet Explorer icon on their - right, this means that they are not on the \CD{} and they will be - available only if you previously enabled Internet - downloading. \emph{This collection cannot be selected entirely at - once: you need to select the packages individually}. This is to - avoid unwanted downloads of huge files. - - On this page, you also have the information about disk space - needed, for each object, and for the set of those who are selected, - and also the disk space available on the partition selected for the - installation. Last, you can choose to install or not the - documentation files and source files associated with each package. -\item[Review Page] - You will find there a summary of your choices - (Figure~\ref{graph:review}, - \ifnum \Status = 1 - on the left% - \else\ifnum \Status=2 - at the top% - \else - on the left% - \fi\fi - ). It is still time to - go back to change them. -\begin{figure*}[!htb] - Packages Page\hfill% - Win32 Support - \begin{center} - \ifnum \Status=1 - \includegraphics[width=.48\textwidth]{../pictures/package-selection}\hfill% - \includegraphics[width=.48\textwidth]{../pictures/win32-support} - \else - \ifnum \Status=2 -\includegraphics[bb=0 0 506 403]{../pictures/package-selection.gif}\hfill% -\includegraphics[bb=0 0 506 403]{../pictures/win32-support.gif} - \else - \includegraphics[width=.48\textwidth]{../pictures/package-selection}% - \hfill% - \includegraphics[width=.48\textwidth]{../pictures/win32-support} - \fi - \fi - \end{center} - \caption{Packages Page / Win32 goodies} - \label{graph:win32-support} -\end{figure*} -\item[Files Copy Page] - The selected files are copied on your hard disk (Figure~\ref{graph:file-copy}, - \ifnum \Status = 1 - on the right% - \else\ifnum \Status=2 - at the bottom% - \else - on the right% - \fi\fi - ). All the files not - yet available on your local disk are first downloaded from the - remote source directory on the Internet. Then every package is - unpacked (if \path|.zip| files), or copied from the \CD{}. -\item[Configuration Page] Several packages need some configuration - step to make them usable (Figure~\ref{graph:configuration}, - \ifnum \Status = 1 - on the left% - \else\ifnum \Status=2 - at the top% - \else - on the left% - \fi\fi - ). Also the \TeXLive{} system needs some post-processing step - (format files generation, ls-R databases generation, environment - variables, etc.). All these operations are done there, some of them - can be lengthy. -\begin{figure*}[!htb] - \textbf{Review Page}\hfill% - \textbf{File Copy Page} - \begin{center} - \ifnum \Status=1 - \includegraphics[width=.48\textwidth]{../pictures/review-settings}\hfill% - \includegraphics[width=.48\textwidth]{../pictures/file-copy} - \else - \ifnum \Status=2 - \includegraphics[bb=0 0 506 403]{../pictures/review-settings.gif}\hfill% - \includegraphics[bb=0 0 506 403]{../pictures/file-copy.gif} - \else - \includegraphics[width=.48\textwidth]{../pictures/review-settings}\hfill% - \includegraphics[width=.48\textwidth]{../pictures/file-copy}% - \fi - \fi - \end{center} - \caption{Review Page / File Copy Page} - \label{graph:review}\label{graph:file-copy} -\end{figure*} -\item[Final Page] The installation being over, you may want to display - the Windows specific documentation (HTML format) and / or the log - file of the setup process (Figure~\ref{graph:final} - \ifnum \Status = 1 - on the right% - \else\ifnum \Status=2 - at the bottom% - \else - on the right% - \fi\fi - ). If it is needed (Win9x/WinME), you will - be asked to reboot your computer. -\end{description} - -\begin{figure*}[!htb] - \textbf{Configuration Page}\hfill% - \textbf{Final Page} - \begin{center} - \ifnum \Status=1 - \includegraphics[width=.48\textwidth]{../pictures/configuration}\hfill% - \includegraphics[width=.48\textwidth]{../pictures/congratulations} - \else - \ifnum \Status=2 - \includegraphics[bb=0 0 506 403]{../pictures/configuration.gif}\hfill% - \includegraphics[bb=0 0 506 403]{../pictures/congratulations.gif} - \else - \includegraphics[width=.48\textwidth]{../pictures/configuration}\hfill% - \includegraphics[width=.48\textwidth]{../pictures/congratulations}% - \fi - \fi - \end{center} - \caption{Configuration Page / Final page} -\label{graph:configuration}\label{graph:final} -\end{figure*} - -Please be aware that the choice of cluster size on DOS disk -partitions can radically affect the size of your \TeX\ -installation. The support tree has hundreds of small files, and it is -not unusual for a complete installation to take up to 4 times the -amount of space used on the \CD. - - -\section[Maintenance and other aspects of the \protect\TeXLive{} -installation under Windows]{Maintenance and other aspects of the \protect\TeXLive{} -installation under Windows} - -\subsection{What's different under Win32 from the standard \Webc ?} -The Win32 version of \Webc{} has some specific features that need to -be noticed. - -\begin{description} -\item[\KPS{}] the hash-tables that \KPS{} builds are quite large for - the \TeXLive{}. In order to cut down the starting time of any - \KPS{}-enabled program, these hash-tables have been put in shared - memory. This way, when you chain the execution of several such - programs, like \path|tex| calling \path|mpost| calling \path|tex|, - the overhead when starting each of the programs but the first will - be reduced. This change is hidden to the user, except if you set the - debug flag of kpathsea to the \path|-1| value: you will then trace - access to the shared memory, which is not what you want (it is - accessed very often!). What is useful in a log trace of the shared - memory access is still to be defined, so the situation might evolve - in the future. -\item[\cmdname{kpsecheck}] this command provides some option that did - not fit well into \cmdname{kpsewhich}. It will allow you to list all - the files that occur multiple times across your texmf trees. This - could be handy, but most of the time you will also get unwanted - output (like dozens of \path|README| files)\footnote{It is noticeable - that all these files result in clashes inside the \KPS{}-hashing - mechanism, fortunately, \KPS{} never look for these files.}. For - this reason, you can combine the \path|-multiple-occurences| with 2 - other options for including or excluding any filename that match - some pattern (you can request for several patterns). - - The \cmdname{kpsecheck} command will also report the status of - shared memory: in use or not used. That might be useful to know - because if the status reported is ``in use'', that means one or - several processes are working, and the effect of any - \cmdname{mktexlsr} command will be delayed until the next time where - no \KPS{} linked process will be running. - - Last, this same command will report about the location it thinks - Ghostscript can be found. Under Win32, for many programs, it is - easier to use the Ghostscript dll, and find it by using the - Ghostscript registry key than to change the \path|PATH|, which has a - limited length anyway. -\item[\Webc{}] the engines have a few more options than the ones from regular - \Webc{}, and one option with a different behaviour: - \begin{itemize} - \item the \path|-fmt| option behaves differently. Previously and - with the regular \Webc{} distribution, this option has 2 different - meanings when you are in ``ini'' or ``vir'' mode. Under Win32, it - has the same meaning: preload the format file specified with the - argument. The meaning of building a format of such name in ``ini'' - mode is obtained by the new \path|-job-name| option. - \item \path|-job-name| option: allows to set the name of the file - resulting from the compilation process. In normal mode, it will - change the base name of all files produced (\path|.dvi|, - \path|.aux|, etc.), while in ``ini'' mode, it will set the name of - the format file written. - \item \path|-halt-on-error| stop the compilation at the first error. - \item \path|-job-time| set the job time to the same timestamp as the - file given in argument. - \item \path|-output-directory| allow to write all the output files in the - specified directory. - \item \path|-time-statistics| print statistics about the job run - time. It is to be noted that Win9x not being a true multitasking - operating system, it has no reliable timer for short periods, so - the value printed is an approximation. Under NT/2K/XP, the result - is quite accurate with user time and system time values allocated - for this run. For Unix - users: the \path|time| command is not usually available to Windows - users. - \end{itemize} -\end{description} - -\subsection{Adding packages to your installation} - -You will find an option in the \texttt{TeXLive} menu (or go to -\texttt{Start -> Programs -> TeXLive -> Add TeX package} menu) to run again -\file{TeXSetup.exe}, but in maintenance mode this time. The steps you -will go through are almost identical to the ones the first time you -run it. - -The only different step is about the packages selection page. In -maintenance mode, the list of installed packages is compared to the -list of packages available from your source directories. Packages that -are not installed will be displayed in green, out of date packages -will be displayed in red and up to date, installed packages are -displayed in black. - -This way, you can choose to add or upgrade components, either from -your \CD{} or from the -Internet, where you are likely to find some more recent version of -your packages. - -It is up to you to select which ones of the packages you want to -install. The rest of the process is similar to the first installation. - -If you want to add files that are not provided by the \TeXLive{} (or -\fpTeX{}) distribution, it is recommended to put them in the -\path|$TEXMFLOCAL| directory. This way, you will be safe against -upgrades of the \TeXLive{} software. - -The directory pointed to by \path|$TEXMFLOCAL| is initially empty. If -you want to add there the support file for Maple (symbolic computation -program) for example, you will have to put the style files in:\\ -\path|c:\Program Files\TeXLive\texmf-local\tex\latex\maple\|\\ -and the documentation files in:\\ -\path|c:\Program Files\TeXLive\texmf-local\doc\latex\maple\| - -Next, \textbf{do not forget to rebuild the ls-R databases files}, -either by using the right menu (Start -> Programs -> TeXLive - -> Maintenance), either by manually running the \file{mktexlsr} - command. - -\subsection[Removing \protect\TeXLive{} from your hard disk]{Removing - \protect\TeXLive{} from your hard disk} - -The uninstall procedure is available either from the -\file{TeXLive.exe} program, from the \path|TeXLive| menu or from the -control panel (Start menu -> Control Panel, Add/Remove Programs -option). This procedure will cleanup your hard disk of most of the -\TeXLive{} files. However, \TeX{} is a system that is creating files -and there is no mechanism to keep track of all of them. Moreover, -Win32 support packages have their own uninstall procedure, which you -will have to run separately (provided you want to get rid of them). Last, -the files you may have stored in \path|$TEXMFLOCAL| won't be -removed. So, even if the vast majority of files are automatically -removed by the uninstall procedure, you will have to do some manual -cleanup to actually remove all of them. - -\subsection{Running \texttt{TeXSetup.exe} from the command line} - -The \path|TeXSetup.exe| program has a number of other interesting -options. You can get the list by running: -\begin{verbatim} -c:\>TeXSetup --help -\end{verbatim} - -Here is the description: -\begin{description} -\item[\path|--automatic-reboot|] reboot without waiting user - confirmation once installation is over; -\item[\path|--dry-run|] do nothing, just log everything that will be - done without this option; -\item[\path|--quick|] use the recommended installation and default - directories, ask nothing up to rebooting; -\item[\path|--net-method (=ie5/direct)|] enable to download components with - restricted licenses from the Internet (either using direct - connection of Internet Explorer 5 DLLs): you need to have an available - network connection and some of the packages are huge; -\item[\path|--remote-source-directory |] this is the base url for the remote packages; -\item[\path|--local-source-directory

|] by default, \path|TeXSetup.exe| - will guess the root directory of the set of files you want it to act on, if you ever - upgrade \path|TeXSetup.exe|, you won't be able to copy the new version - onto your \CD{}, so you will need to use this option to specify the - root of the \CD{}; -\item[\path|--installation-directory |] this is the root of your - installation, all files will be copied under this location. The - default value is \verb+c:\Program Files\TeXLive+; -\item[\path|--texmfmain-directory |] -\item[\path|--texmflocal-directory |] -\item[\path|--texmfextra-directory |] -\item[\path|--texmfhome-directory |] -\item[\path|--vartexmf-directory |] -\item[\path|--vartexfonts-directory |] these are the directories - used to configure the location of your files. They map directly to - the \path|texmf.cnf| variables. -\item[\path|--with-source-files(=yes/no)|] copy the source files - for \TeX{} packages, default value is no; -\item[\path|--with-documentation-files(=yes/no)|] copy documentation files for \TeX{} - packages. Default value is yes. Beware: this is only documentation about specific - packages, general documentation will be installed anyway; -\item[\path|--program-folder |] the name of the folder under - which you will find the menus; -\item[\path|--add-package |] this is used to add or update a specific - package after a first regular installation; -\item[\path|--scheme |] install the named scheme instead of the - default \path|texlive-recommended| scheme; -\item[\path|--maintenance|] mostly the same as \path|--add-package| - without specifying a package to add; -\item[\path|--uninstall|] this option will remove anything \TeX{} related coming from - the \CD{}, which means there can be files left if you added style - files or format files, and also that supplementary tools will not be - removed\footnote{This option is still a bit crude as of \today}; -\item[\path|--help|] this option opens up a box with the list of options. -\end{description} - -\subsection{Network installation} - -\KPS{} knows about UNC names, so you can use them to get your TEXMF -tree from the network. But there is better than this. -All the support files and configuration files, everything except the files in the -\path|bin/win32| are shareable with a \teTeX{} or Unix \TeXLive{} installation. That means -you can use Samba either to mount from an NT server to a Unix -workstation or the converse. Several strategies are possible: -\begin{itemize} -\item Put everything on the server. Just add each set of files for the os and -architecture you want to use in the \path|bin| directory. That means -for example \path|bin/win32| and \path|bin/i386-linux|. Next configure -your main variables. You can use UNC names to -point to the right directories under Win32. -\item Install a local copy for the binaries and format files. In this - case, assign \path|$TEXMFMAIN| to the main \path|texmf| tree that - will be accessed remotely. Set \path|$VARTEXMF| to be a local - directory which will hold local configuration files and on-the-fly - generated files. -\end{itemize} - -\subsection{Personal Configurations} - -\subsubsection{\cmdname{WinShell}} -\label{sec:winshell} - -Start this program from the Start menu or from the Desktop shortcut. -Go to \textbf{Options} \verb+->+ \textbf{Program Calls}. - -\begin{itemize}\itemsep 0pt -\item In the DVIWin tab, if the filename is \textbf{yap}, replace it -with \textbf{windvi.exe}. -\item In Ghostview tab, make sure it gives the correct path for -gsview32.exe:\\ -\hspace*{1em} \verb+C:\ghostgum\gsview\gsview32.exe+ (for 3.6, the -current version)\\ -or \\ -\hspace*{1em} \verb+C:\gstools\gsview\gsview32.exe+ (for the older -version) - -\end{itemize} - -Click \textbf{OK}. - -Note that the install process sets all files with the \texttt{.tex} -extension to open with \cmdname{WinShell}. Unless you plan to use another editor -(such as WinEdt or Emacs), this is appropriate. - -Unfortunately, \cmdname{WinShell} does not have a spell-checking feature. -However, if you have installed the \path|tex-extrabin| collection, -your installation includes \textbf{Ispell} (a spell checking program -found on most Unix systems). The executable is in your PATH so -\verb+ispell.exe+ will be found if you invoke it from a DOS window. -If you installed documentation, look -at\\ -\verb+C:\Program Files\TeXLive\texmf\doc\html\manpages\ispell.html+\\ -for information on Ispell. (Otherwise, you can find -\verb+ispell.html+ on the CD.) If you rely on spell checking, you may -want to add an Ispell icon to \cmdname{WinShell}. See -subsection~\ref{winshell:ispell} of this document for how to do that. - -For an excellent commercial (but inexpensive) spelling checker, -see \url{http://www.microspell.com}. - -%Appendix B also contains other information about using \cmdname{WinShell}, such as: -% -%\begin{itemize} -%\item How to apply a bug fix you probably need -%\item How to print directly from \cmdname{WinShell} -%\item How to use the Project feature for multiple-file documents -%\end{itemize} - -\cmdname{WinShell} also has on-line help, which you can access via the -$\textbf{\underbar{?}}$ on the menu bar. - -Other information about using \cmdname{WinShell} can be found in -section \ref{winshell:more} on p.~\pageref{winshell:more}. - -\subsubsection{Dvips} - -The configuration file for dvips can be found in\\ -\verb+C:\Program Files\TeXLive\texmf-var\dvips\config\config.ps+\\ -You may open it with any editor (\cmdname{WinShell} will do fine) and change -some parameters: - -\begin{description} -\item [fonts] you can change the default printer \MF{} mode or printer - resolution in case dvips needs to generate PK fonts. By default it - is configured to use type1 versions of the CM fonts, so it should - not call \cmdname{mktexpk} too often; -\item[printer] you can tell dvips where you want to print by - default. If the `o' option is not followed by a printer name, then a - \file{.ps} PostScript file is written. You can give dvips a printer - name such as: -\begin{verbatim} -o lpt1: -% o | lpr -S server -P myprinter -% o \\server\myprinter -\end{verbatim} -\item[paper] Next, you might want - to change the paper size from European (A4) to US letter - by making the US letter the first paper size mentioned in the file. - Scroll to the group of lines beginning with ``@''. Move - the appropriate lines so that this section begins with the lines:\\ -\hspace*{1em} @ letterSize 8.5in 11in\\ -\hspace*{1em} @ letter 8.5in 11in\\ -\hspace*{1em} @+ \%\%BeginPaperSize: Letter\\ -\hspace*{1em} @+ letter\\ -\hspace*{1em} @+ \%\%EndPaperSize -\end{description} - -\textbf{Note:} The current \TeXLive{} distribution has implemented (for -the first time!) the procedure of making always up-to-date fontmaps files -for Dvips and Pdftex. This is done by \cmdname{updmap} program -during installation, as well as during any font package addition. -If you add new packages by hand, edit the file \verb+updmap.cfg+ -in \path|$VARTEXMF/web2c|. - -\subsubsection{Pdftex} -If you want to use the program pdf{}latex to convert directly to -pdf format, and you are using US letter file, edit the file\\ -\verb+C:\Program Files\TeXLive\texmf-var\pdftex\config\pdftex.cfg+\\ -and change ``page\_width'' and ``page\_height'' to specify letter-size paper. -These entries should read:\\ -\hspace*{1em} page\_width 8.5 true in\\ -\hspace*{1em} page\_height 11 true in\\[6pt] -Save the file and exit the editor. - -\subsubsection{GSView} -Starting from versions compatible with Ghostscript 6.50, GSView is not -free anymore, but shareware. So it is not on the \CD{} anymore. - -You may want to change the papersize to US letter size. If so, -open GSView from the Start menu. \\ -From the \textbf{Media} menu, select \textbf{Letter}. - -Also, there are menu settings that are supposed to give you the -most readable screen image:\\[4pt] - From \textbf{Media} \verb+->+ \textbf{Display Settings}, -set \textbf{Text Alpha} -and \textbf{Graphics Alpha} both to 4 bits. - -Note that the installation process has set all .ps and .eps files -to automatically open with GSView. - -For printing instructions, see section~\ref{printing} below. - -\subsubsection{WinDvi} -\label{sub:windvi} - -The \file{TeXSetup.exe} program takes care of associating the files -with the \file{.dvi} extension with \file{Windvi}. - -Open it from the Start menu (Programs \verb+->+ TeXLive \verb+->+ DVI Viewer). -You can set it for US letter paper by going to \textbf{View} \verb+->+ \textbf{Options} -and next to \textbf{Papertype}, -selecting US (8.5\verb+"+ x 11\verb+"+). -Click \textbf{OK}. -Exit Windvi. -You can change other parameters from there, like the ability to -execute commands included in path|\special{}|. -Also, the first time you -view any .dvi file, you may find the magnification too large. Zoom out -until you get an appropriate size. - -%There are two important parameters related to printing that can't yet -%be set from the dialog boxes, namely the resolution and the \MF{} mode -%for the printer. You can set them once for all by specifying them on -%the command line: -%\begin{verbatim} -%c:\>windvi -p 360 -mfmode canonbjc foo.dvi -%\end{verbatim} -%When you will exit Windvi, these parameters will be stored in the -%configuration file. The available modes are found in this file:\\ -%\path|c:\Program Files\TeXLive\texmf\metafont\misc\modes.mf| - -All the configuration for Windvi is stored in the -\path|$HOME/windvi.cnf| file. You can find it by running this command -at the prompt: -\begin{verbatim} -c:\>kpsewhich --expand-var $HOME/windvi.cnf -\end{verbatim} - -Should you have problems with Windvi, please remove the configuration -file and test your problem against a vanilla configuration. - -\subsection{Testing} - -You can test \cmdname{WinShell} by opening the file \verb+sample2e.tex+, found in -\path|C:\Local\TeX\texmf\tex\latex\base|. The \LaTeX\ source should appear -on the screen. Process it by clicking on the \LaTeX\ icon on the toolbar, -then view it by clicking on the Preview (Windvi) icon. - -At first, when you preview files with Windvi, it will create fonts because -screen fonts were not installed. After a while, you will have created most -of the fonts you use, and you will rarely see the font-creation window. -Return to \cmdname{WinShell} and try dvips, then GSView. - -\textbf{Hint for the future:} If a \LaTeX\ run stops because \LaTeX\ -cannot find a file, you can press \textbf{Ctrl-z} to quit. - -\subsection{Printing}\label{printing} - -It is possible to print from Windvi. In this case, printing will -be done using the Windows unified printer driver. By definition, it -is compatible with all printers. However, there is some drawback: it -can generate some huge spool files, and some (older) versions of Windows just -don't like them. The advantage is that you can use features like -embedding BMP or WMF images. You also need to make sure that the -printer parameters are correctly set (subsection~\ref{sub:windvi}), -else you will get scaled printing (printing at 600dpi on a 300dpi -printer will give you only one quadrant of your page). - - -Printing is faster and more reliable if you run dvips to make a -.ps file and then print from GSView. To print from GSView, first select -\textbf{Print...} from the \textbf{File} menu. A Print window will appear. - -If you will be using a PostScript printer, \textit{be sure to select -\textbf{PostScript Printer}}. In the newer version this is done in -the ``Print Method'' box at the bottom left of the Print window. You -can then select any of the printers that you have previously installed -on your PC. If you fail to check the box for PostScript Printer, -printing will not work. - -If you will be using your own non-PostScript printer, select -\textbf{Ghostscript device} in the ``Print Method'' box, then click on -the button to the right labelled \textbf{djet500} and select your -printer type from the list that pops up. (In the older version of -GSView, make sure PostScript Printer is \textit{not} selected, then -select your printer type from the ``Device'' list.) - -If you use \cmdname{WinShell} and a PostScript printer, probably the most -convenient way to print is to add an icon to the \cmdname{WinShell} toolbar that -invokes dvips in a way that sends the output directly to a default -printer. For detailed instructions on how to do this, see -\ref{winshell:print} on p.~\pageref{winshell:print} -(\textit{More About \cmdname{WinShell}}). - -\subsection{More About \cmdname{WinShell}}\label{winshell:more} -\subsubsection{Installing Bug Fixes} - -\cmdname{WinShell}'s author (\href{mailto:idb@winshell.de}{Ingo de Boer}, -thanks to him) sometimes releases beta versions of the next \cmdname{WinShell} -version which are also bug fixes. You can grab them from -\url{http://www.winshell.de}. Usually they are \file{.zip} files that -only require to be unpacked in \cmdname{WinShell} directory (\path|c:\Program -Files\WinShell| by default), either using WinZip or a similar tool, or -by using \file{unzip} on the command line. If you got some -\file{winshellbugfix.zip} file and that you saved it in the \cmdname{WinShell} -directory, then you need to run: -\begin{verbatim} -c:\>cd c:\"Program Files"\WinShell -c:\>c:\local\bin\unzip winshellbugfix.zip -\end{verbatim} -Say `yes' if you are asked if some files should be overwritten. The -\path|unzip.exe| programme can be found in the -\path|support/gnu-utils| package. If you -do not have it on your machine, you can use any archiver tool like -WinZip to achieve the same effect. - -\subsubsection{Using the Project Feature} -If your document is split into several files -(for example a thesis), look into \cmdname{WinShell}'s ``Project'' feature. From the -\textbf{Project} menu, you give the project a name (e.g., Thesis), -supply the name of the main (or root) file, and then ``add'' other -files. These filenames display on the left of the screen where you can -double click the names to view and switch between them. Clicking -the \textbf{\LaTeX} icon always processes the main file. - -Note the icons on the toolbar for toggling the project space (on the left) -and the log space (at the bottom). If you are not using the Project -feature, you may want to toggle off the space on the left, using the full -screen width to display your file. - -\subsubsection{Printing from \cmdname{WinShell} to a PostScript Printer} -\label{winshell:print} - -The Dvips icon on the \cmdname{WinShell} toolbar puts the PostScript output in a file, -which you can then view with GSView and print from there if you choose. -However, it's convenient to add a \cmdname{WinShell} ``program call'' to dvips which -sends the output directly to a designated PostScript printer. The steps -below show how to do this for the printer \textbf{vclw}; you should -substitute the name of your most frequently-used printer for \textbf{vclw}. -\begin{enumerate} -\item Make the program aware of the printer: -\begin{itemize} - -\item Open \cmdname{WinShell}, go to \textbf{Options} \verb+->+ -\textbf{Program Calls} \verb+->+ \textbf{User defined}. - -\item Click on \textbf{Tool 1} in the list on the right and fill in the -fields to the left as follows:\vspace{-6pt} -\begin{quote} -Name: \verb+Print+\\ -exe file: \verb+dvips+\\ -cmd-line: \verb+ -D600 %m -o vclw+\\ -Uncheck the box for ``DVIPS first'' -\end{quote}%\vspace{-12pt} -\item Click \textbf{OK} -\end{itemize} -\item Add Print to the toolbar: -\begin{itemize} -\item Go to \textbf{Options} \verb+->+ \textbf{View} \verb+->+ \textbf{Customize}. -\item In the Category box, select \textbf{User-Programs}. -\item Select \textbf{Print} and drag it to the toolbar, placing it just to - the right of the GSView icon. -\item You then have a choice of ``Image only'', ``Text only'', or ``Image and -Text''. The easiest is to select ``Text only'' and click \textbf{OK}. -You should then see \textbf{Print} on the toolbar. (If you prefer, you can -select ``Image only'', then ``Edit'', and edit the displayed picture to your -satisfaction.) -\end{itemize} -\end{enumerate} -Now, to print a \LaTeX\ document, just click on the \textbf{Print} icon to -send to your selected printer. To use a different printer, you will need to -click on the \textbf{Dvips} icon to print to a file. Then click on the -GSView icon and use GSView to send to any printer you have installed on -your PC. - -\subsubsection{Adding Ispell to \cmdname{WinShell}} -\label{winshell:ispell} -\begin{enumerate} -\item Add Ispell to User Tools: -\begin{itemize} -\item Open \cmdname{WinShell}, go to \textbf{Options} \verb+->+ -\textbf{Program Calls} \verb+->+ \textbf{User defined}. -\item In the list on the right, click on \textbf{Tool 1} (or \textbf{Tool - 2} if you have already used \textbf{Tool 1}) and fill in the -fields to the left as follows:\vspace{-6pt} -\begin{quote} -Name: \verb+Ispell+\\ -exe file: \verb+ispell+\\ -cmd-line: \verb+ -t -d american %c.tex+\\ -Uncheck the boxes for ``LaTeX first'' and ``DVIPS first'' -\end{quote}%\vspace{-12pt} -\item Click \textbf{OK} -\end{itemize} - -\item Add Ispell to the toolbar: %\vspace{-14pt} -\begin{itemize}\itemsep 0pt -\item Go to \textbf{Options} \verb+->+ \textbf{View} \verb+->+ \textbf{Customize}. -\item In the Category box, select \textbf{User-Programs}. -\item Select \textbf{Ispell} and drag it to the toolbar, placing it just to - the right of the GSView icon (or the last icon you added). -\item You then have a choice of ``Image only'', ``Text only'', or ``Image and -Text''. The easiest is to select ``Text only'' and click \textbf{OK}. -You should then see \textbf{Ispell} on the toolbar. (If you prefer, you can -select ``Image only'', then ``Edit'', and edit the displayed picture to your -satisfaction.) -\end{itemize} -\end{enumerate} -Now, when you have a \LaTeX\ document open, you can click on -\textbf{Ispell} to perform spell checking. Ispell will open another window -and display the first misspelled word on the left with the filename on the -right. Below that you will see the context in which the misspelling appears; -often several suggestions for replacements are also displayed. To replace -the word, enter the number corresponding to the desired replacement. Other -possible responses are listed below; for example, you can press the space -bar to ignore the misspelled word. For more information on Ispell, read the -manual page: \verb+C:\Program Files\TeXLive\texmf\doc\html\manpages\ispell.html+. - -Note that when you replace a word, you will not see the correction in your -\cmdname{WinShell} window until you close the file (click the X in the upper right -corner) and then open it again (use the File menu). - -\subsection{Tips and tricks about the Win32 platform} - -\subsubsection{Different flavors of Win32} - -What we call Win32 is not an operating system by itself. It is a set -of functions -- and a large one\footnote{Around 12000 functions in the - header files of the Microsoft SDK} -- that you can use to write -programs for different operating systems of the Windows family. - -Windows comes in different flavors: -\begin{itemize} -\item Win95, Win98 and WinME, which \emph{are not true multitasking, - multithreading} environments. They are the latest -- and hopefully - last -- metamorphosis of DOS. This can be more or less proven by the - fact that when booting, the PC will load the \path|command.com| - interpreter, and if you stop the boot process at this point, you can - ask for the current (DOS) version and it will answer something like - 'MS-DOS 7.0' (at least for the old versions of Win9x); -\item Windows NT, which is a new operating system written from scratch, - capable of - true multitasking behaviour, and loaded with high level features; -\item Windows 2K, written on an NT basis, with all the bells and - whistles of Win98. -\item Windows XP, which comes with Personal and Pro flavors. This is - the last step in merging both lines of products (Win9x based and NT - based). XP is written on an NT basis. -\end{itemize} - -Win9x are able to run 32~bits programs and 16~bits programs -concurrently. But the operating system by itself is not entirely -written in 32~bits mode, and does not support memory protection: 16bits -applications can overwrite parts of the operating system memory! Some -parts of the system like the GDI (Graphical Device Interface) manage -limited resources like bitmaps, fonts, pens and so on for the set of -all programs that run concurrently. All the bitmaps headers available -at the same time can't amount for more than 64kb. This explains the -performance tool and the fact that you can put your system on his -knees by making intensive use of graphic objects for example. - -NT, 2K and XP do not suffer from these limitations, and neither from -other Win9x limitations. They are true multitasking environments, with -protected memory. They are much more responsive than Win9x because -of better memory management, better file system and so on. - -\subsubsection{Command line prompt} - -You will wonder: ``why would I need to use a command line prompt when -I have Windows?''. - -Good question. The problem is of very general nature. Not all -operations can be done easily using only a GUI. Command line gives you -programming power -- assuming a clever command interpreter. - -But the problem here is more fundamental: \TeX{} is \emph{a batch} -tool. Not an interactive one. \TeX{} needs to compute the best -layout for each page, resolve cross-references and so on. This can be -done only by a global processing of the document. It is not (yet) a -task that can be done interactively. - -This means that you should use \TeX{} from a command line. In fact the -situation is not so bad. There is an advantage to write command line -tools for complex processing: they are better debugged, because not -tied to GUI problems, and GUI tools can be designed to interface the -command line tools. This is the case for \TeX{} where you will -interact with it most of the time through a GUI text editor -- see -section~\ref{sec:winshell} for example. - -However, you may need to use the command line prompt in a number of -situations, by example in case of problems and you want to debug your -setup -- see - section~\ref{sec:troubleshooting}. - - \begin{description} - \item[Win9x] You will open a command line prompt by looking either - for the MS-DOS icon in the ``Start->Programs'' menu, either by - choosing ``Start->Run'' menu and typing in \path|command.com| - \item[NT, 2K, XP] You will open a command line prompt by looking - for the ``Command Prompt'' in the ``Start->Accessories'' - menu\footnote{These locations may change across different OS - versions.}. You can also choose the ``Start->Run'' menu and type - in \path|cmd.exe|, which is the name of the brand new command - interpreter for NT\footnote{Which explains why it is untrue to - call this a \emph{DOS} box under NT!}. -\end{description} - -\subsubsection{Path separators} - -The Win32 API understands both \path|/| and \path|\| characters as -PATH separators. But the command interpreters do not! So whenever a -path name is used programmatically, you can use both separators, and -even mix them up in the same path name. But on the command line, you -must type \path|\| as path separator. The reason is compatibility: -the command processor used the \path|/| to introduce arguments to -commands. - -All this to say: do not be surprised to read path names written using -the Unix convention; \fpTeX{} is a port of \Webc, and aims to be compatible -across platforms. For this reason, all the configuration files that -need to specify path names use the Unix convention. - -\subsubsection{File systems} -\label{sec:clusters} - -The worse feature of Win9x with regard to \TeX{} is probably the -so-called FAT file system. \TeX{} uses many many small files, with -size around 1kb -- 3kb. The FAT file system is old, and predates by -far the multi-gigabytes hard disks we have today. It means it can't -manage efficiently the 30000 \TeX{} files found on the \CD{}. The FAT -file system will allocate a minimum of 32kb for \emph{any} file on a -huge partition. It means that \TeX{} will use much more disk space -than it actually needs. - -The other, more modern, file systems available -- namely FAT32 and -NTFS -- do not have this drawback. They manage clusters of 4kb -only\footnote{You can lower the limit to 512 bytes on NTFS}. - -\subsubsection{How to add some directory to your PATH} - -There are pairs of variables and values which behave much like global -variables inside your programs. The set of those variables is called the -environment. Each program is initialized with a copy of the -environment when it is run. It can request and change the -value of any variable. The changes happen in the copy of the -environment, and is not at all propagated to the other running -programs. - -Your PATH is a special environment variable used to search for -programs you want to run. -There is a different procedure to change it for Win9x, WinME and NT/2K/XP: - -\begin{description} -\item[Windows 95/98] Edit your \path|autoexec.bat|. In this file should be a line - starting with \texttt{PATH=} and followed by a list of directories separated - by \path|;|. Please add the directory with the executables in this line. - After this, this line could look as follows: -\begin{verbatim} -PATH=c:\windows;c:\windows\system;c:\"Program Files"\TeXLive\bin\win32 -\end{verbatim} -\item[Windows ME] You need to run the special program - \path|c:\windows\system\msconfig.exe| to be able to change any - environment variable. From this program, select the `Environment' - tab, and then add or modify the variable you want. You will be asked to reboot the - machine upon any change. -\item[Windows NT/2K/XP] - Click left on \texttt{Start --> Settings --> Control Panel}. Now the window - with the control panel icons opens. Double click on System. The - System Properties window opens. Click on the tab - \textsf{Environment} or look for a button named `Environment - Variables' among the dialog boxes. Now - you can change the environment variables for your user account. Note: - There are also displayed the environment settings for the system. - Normally, you can't change the system variables unless you have - administrator rights on your machine. If you want to change the \texttt{PATH} - for all users, you will have to contact your system administrator or - be the system administrator yourself--in the later case you should - know what you are doing. - - If there is already a \texttt{PATH} setting for your user account, - left click on \texttt{PATH}. In the field \textsf{Variable} appears - \texttt{PATH} while the field Value shows the current setting of - \texttt{PATH} as a list of directories separated by \path|;|. Add - the directory where the executables are located (e.g. - \path|c:\Program Files\TeXLive\bin\win32|). If there isn't a \texttt{PATH} variable - for your user account, simply click in the field Variable and type - in \texttt{PATH}, click in the field \textsf{Value} - and type in the directory with the executables. Important: Click on - the \textsf{Apply} button before clicking \textsf{Ok}, otherwise the - changes to \texttt{PATH} won't apply to your system. Be careful when - changing the environment settings. -\end{description} - -The best way to be sure that a variable has been properly set is to -open a console and type: -\begin{verbatim} -set VARIABLE -\end{verbatim} -which should return the corresponding value. - -\subsubsection{\TeX{} engines} - -If you have a look at the \Webc{} documentation, you will read that all -the various \TeX{} derived programs use the same base engine. For -example, \path|tex.exe| and \path|latex.exe| are exact copies of the -same program, but each one will use a different format file, based on -its calling name. - -Under Unix, this feature is implemented through \emph{symbolic - links}. It saves up a bit of disk space, because some engines are -used with many different format files. - -The Win32 API does not know about file links. So to save up almost -the same amount of memory, all the \TeX{} base engines have been put -in DLLs (\emph{Dynamic Linked Library}). This means that you will have -the following layout: -\begin{alltt} -13/05/2002 17:06 3 584 latex.exe -13/05/2002 17:06 266 240 tex.dll -13/05/2002 17:06 3 584 tex.exe -\end{alltt} -and the \path|latex.exe| file is nothing but a rough copy of -\path|tex.exe| using the same core \path|tex.dll|. -The same trick has been used for the \path|mktex*.exe| family of programs which are -linked to the \path|mktex.dll| library. - -In fact, a generic tool called \path|lnexe.exe| is provided to build the -equivalent of Unix hard links for executable files only under Win32. - -\subsection{In case of problems} -\label{sec:troubleshooting} - -\subsubsection{What to do if \texttt{latex} does not - find your files?} - -\begin{itemize} -\item \cmdname{kpsewhich} is the tool of choice to debug any -problem. Unfortunately, kpsewhich outputs debug information to -stderr, and the Windows console does not know how to redirect stderr -to a file\footnote{Well, NT and Win2k consoles know how to do - that. But the trick will work for any console.}. -For diagnostic purposes you can temporarily set an -environment variable (in DOS box): -\begin{verbatim} -SET KPATHSEA_DEBUG_OUTPUT=err.log -\end{verbatim} -You can also set the debug level: -\begin{verbatim} -SET KPATHSEA_DEBUG=-1 -\end{verbatim} - -If you want to redirect stderr to stdout, which is not possible under -either W9x or NT/2K/XP, then just do: -\begin{verbatim} -SET KPATHSEA_DEBUG_OUTPUT=con: -\end{verbatim} -This way you can capture both stdout and stderr in the same file. - -\item Assuming the installation has been done in \path|c:/Program Files/TeXLive|, check - the following values: \\ - {\small - \begin{tabular}{ll} - \path|kpsewhich -expand-path $SELFAUTOPARENT| & \path|c:/Program Files/TeXLive| \\ - \path|kpsewhich -expand-path $TEXMF| & \path|c:/Program Files/TeXLive/texmf| \\ - \path|kpsewhich -expand-path $TEXMFCNF| & - \path|.;c:/Program Files/TeXLive/texmf/web2c;| \\ - & \path|c:/Program Files/TeXLive/bin/win32;| \\ - & \path|c:/Program Files/TeXLive/bin;| \\ - & \path|c:/Program Files/TeXLive| \\ - \path|kpsewhich -expand-var $TEXINPUTS| & \path|.;c:/Program Files/TeXLive/texmf/tex//| - \end{tabular} -} -\item If you have other \TeX{}-related values already set in your - environment, please, remove them. They are overriding the ones in - texmf.cnf. -\item Check the values from:\\ -{\small - \begin{tabular}{ll} - \texttt{kpsewhich cmr10.tfm} & \path|c:/Program Files/TeXLive/texmf/fonts/tfm/public/cm/cmr10.tfm|\\ - \texttt{kpsewhich latex.fmt}& \path|c:/Program Files/TeXLive/texmf/web2c/latex.fmt| - \end{tabular} -} -\item At this point, if everything is correct, \path|tex.exe| and - co. should work. If it is not the case, you will need to play with - the \path|-debug=n| option from \path|kpsewhich|, and check back all - the values. Try to identify and report the problem. -\end{itemize} - -\subsubsection{What to do if your setup still does not work as expected?} - -There are several questions to ask about: -\begin{enumerate} -\item Is \file{tex.exe} on my \path|PATH|? -\item Is the \path|TEXMFCNF| variable correctly set to - \path|c:/Program Files/TeXLive/texmf-var/web2c| (default value)? -\item Are there any errors in the log file generated by the - \file{TeXSetup.exe} program? Errors are flagged with the sequence - \path|Error|. -% \item If everything seems correct up there, then you need to read the -% documentation in \path|texmf/doc/fptex/fptex.pdf| or -% \path|texmf/doc/html/fptex/fptex.html| for a more detailed procedure -% (available on your hard disk or on the \CD{}). -\item One can also go to \url{http://www.tug.org/tex-live.html} and - check for any bug fix. -\item The Windows distribution on the \CD{} is no more no less than - the \fpTeX{} distribution, so you can also go to the Web pages at - \url{http://www.fptex.org}, or consider subscribing to the \fpTeX{} - mailing-list by consulting - \url{http://www.tug.org/mailman/listinfo/fptex} . -\end{enumerate} - - -The \TeXLive{} software is complex and made of more than 250 programs -and around 40000 files from various sources. It is quite difficult to -predict all possible causes for problems. Nevertheless, we will do our -best to help you in every case. - - -\subsection{Compiling the source files} - -You have the whole set of source files, comprised for -Windows in the \path|source/source.tar.bz2| archive available on the -\CD{}. To be able to compile the whole distribution for Windows, you -will need: -\begin{itemize} -\item Windows 2K/XP -\item Microsoft Visual Studio .Net -\item a set of Unix tools (\texttt{sed}, - \texttt{grep}, \texttt{gawk}, etc.) and also Perl, Flex and Bison, -\item to adjust the paths in the - \path|win32/make/common.mak| file according to your installation -\item adjust the paths in the Perl script file - \path|win32/perl/build.pl|, -\item run the compilation from the \path|win32/| directory using this - command: -\begin{verbatim} -c:\texlive\source\win32>perl ./perl/build.pl --install --log=install.log -\end{verbatim} -\end{itemize} - -There is a lot of work to do to make this process easier and cleaner. - -\subsection{Where to get more information?} - -The Win32 \TeX{} distribution on the \CD{} is also known as -\fpTeX. Only the packaging differs, but \fpTeX{} is no more no less -than the current \TeXLive\ release for Windows. - -The \fpTeX home on the Web is at:\\ -\url{http://www.fptex.org/} - -The current \fpTeX release is available from any -\href{http://www.ctan.org}{CTAN} %(see also the section -%\ref{sec:ctan}) -site in the directory~:\\ -\noindent\url{ftp://ctan.tug.org/tex-archive/systems/win32/fptex/}. - -The main ftp site for \fpTeX\ is \url{ftp://ftp.dante.de/pub/fptex/} from -where beta versions of \fpTeX\ and additionnal tools are available. -This main site is (partially) mirrored daily by the CTAN backbones in their -\path|systems/win32/fptex| directory. - -% You can reach me at my email address: -% \url{mailto:Fabrice.Popineau@supelec.fr}. - -The \TeX{} Users Group is kindly hosting a mailing-list dedicated to -\fpTeX. This is a very low volume one. It is used for announcements, -bugs reports or as well to discuss about improvements or various users -problems. To subscribe, read the page at -\url{http://www.tug.org/mailman/listinfo/fptex}. The mailing list -address is \EmailURL{fptex@tug.org}. - -\section{Building on a new Unix platform} -If you have a platform for which we have not provided binary sources, -you will need to compile \TeX{} and friends from scratch. This is not -as hard as it sounds. What you need is all in the directory -\texttt{source} on the \CD{}. - -You should first install the support tree from the \TeXLive{} \CD{} (do -a basic install, with no system binaries chosen). - -\subsection{Prerequisites} -You will need about 100 megabytes of disk space to compile all of -\TeX{} and its support programs. You'll also need an \acro{ANSI} C -compiler, a \cmdname{make} utility, a lexical scanner, and a parser -generator. The \acro{GNU} utilities (\cmdname{gcc}, \acro{GNU} -\cmdname{make}, \cmdname{m4}, \cmdname{flex}, \cmdname{bison}) are the -most widely tested on different platforms. \cmdname{gcc}-2.7.* -\cmdname{flex}-2.4.7 and \acro{GNU}\,\cmdname{make}-3.72.1 or newer -should work well. You may be able to work with other C compilers and -\cmdname{make} programs, but you will need a good understanding of -building Unix programs to sort out problems. The command -\texttt{uname} must return a sensible value. - - - -\subsection{Configuration} -First, unpack the source from the compressed -\texttt{tar} file in the directory \dirname{source} to your disk and change -directory to where you placed it. Decide where the `root' of the -installation will be, e.g.\ \path|/usr/local| or -\path|/usr/local/TeX|. Obviously you should use the same location -that you specified when you installed the support tree. - -Now, start the build process by running \textsf{configure} with -a command-line like -\begin{alltt} ->> \Ucom{./configure -prefix=/usr/local/TeX} -\end{alltt} - -The `prefix' directory is the one where you installed the support -tree; the directory layout that will be used is as follows (where -\$TEXDIR stands for the directory you chose): - -\noindent -\begin{tabular}{>{\ttfamily}ll@{}} - \dirname{$TEXDIR/man} & Unix manual pages\\ - \dirname{$TEXDIR/share/texmf} & main tree with fonts,\\ - & \qquad macros, etc\\ - \dirname{$TEXDIR/info} & \acro{GNU} style info manuals\\ - \dirname{$TEXDIR/bin/$PLATFORM} & binaries\\ -\end{tabular} -%$ - -You can omit the use of `\dirname{share/}' part for the -\dirname{texmf} directory if you want, as -\dirname{$TEXDIR/share/texmf} and \dirname{$TEXDIR/texmf} are -auto-detected by configure. If you choose something different, you -have to specify that directory with the \verb|--datadir| option of -\textsf{configure}. - - -If you want to leave out the \dirname{$PLATFORM} directory level -(i.e.\ put the binaries directly into \dirname{$TEXDIR/bin}), specify -the \verb|--disable-multiplatform| option for \textsf{configure}. - - -Have a look at the output of \texttt{./configure --help} for more -options you can use (such as omitting optional packages such as \OMEGA\ -or \eTeX). - -\subsection{Running \textsf{make}} -Make sure the shell variable \texttt{noclobber} is not set, and -then type -\begin{alltt} ->> \Ucom{make world} -\end{alltt} -and relax\ldots. - -It could also be useful to log all the output, e.g.\ by -typing -\begin{alltt} ->> \Ucom{sh -c "make world >world.log 2>\&1" \&} -\end{alltt} -Before you think that everything is ok, please check the log file for -errors (\acro{GNU} \cmdname{make} always uses the string -``\texttt{Error:}'' whenever a command returns an error code) and -check if all binaries are built: -\begin{alltt} ->> \Ucom{cd /usr/local/TeX/bin/i686-pc-linux-gnu} ->> \Ucom{ls | wc} -\end{alltt} -The result should be 209. - -If you need special privileges for \texttt{make install}, you can -run two \cmdname{make} jobs in separate runs: -\begin{alltt} ->> \Ucom{make all} ->> \Ucom{su} ->> \Ucom{make install strip} -\end{alltt} - -\subsection{Final configuration steps} -Set up your \envname{PATH} to include the directory containing the -just-installed binaries (e.g.\ -\dirname{/usr/local/TeX/bin/mips-sgi-irix6.5}); similarly, -\envname{MANPATH} and \envname{INFOPATH} to include the relevant newly -installed subdirectories, i.e.\ \dirname{$TEXDIR/man} and -\dirname{$TEXDIR/info}. - -The program \textsf{texconfig} allows you to set the defaults for -hyphenation, paper size, print command, \MF{} mode, etc. You can -run this command interactively and see what options it offers, or type -\begin{alltt} ->> \Ucom{texconfig help} -\end{alltt} - -For example, if you are not using A4 format paper, you can make -`lettersize' the default using: -\begin{alltt} ->> \Ucom{texconfig dvips paper letter} ->> \Ucom{texconfig xdvi paper us} -\end{alltt} - -\section{A user's guide to the \protect\Webc{} system} - -%-------------------------------------------------------- - -\Webc{} contains a set of \TeX-related programs, i.e., \TeX{} itself, -\MF{}, \MP, \BibTeX{}, etc. The original implementation was by Tomas -Rokicki who, in 1987, developed a first \TeX{}-to-C system adapting -change files under Unix, which were primarily the work of Howard -Trickey and Pavel Curtis. Tim Morgan became the maintainer of the -system, and during this period the name changed to Web-to-C\@. In -1990, Karl Berry took over the work, assisted by dozens of additional -contributors, and in 1997 he handed the baton to Olaf Weber. The -latest result is \Webc{} Version 7.3, which was released in March -1999. Our version has some updates for the forthcoming new release, -and identifies itself as 7.3.7 - -The \Webc{} 7.3 system runs on Unix, Windows 3.1, 9x/ME/\acro{NT}/\acro{2K}/\acro{XP}, -\acro{DOS}, and other operating systems. It uses Knuth's -original sources for \TeX{} and other basic programs written in \web{} -and translates them into C source code. Moreover, the system offers a -large set of macros and functions developed to augment the original -\TeX{} software. The core \TeX{} family components are: - -\begin{description} -\renewcommand{\makelabel}[1]{\descriptionlabel{\mdseries\cmdname{#1}}} -\item[bibtex] Maintaining bibliographies. -\item[dmp] \cmdname{troff} to MPX (\MP{} pictures). -\item[dvicopy] Produces modified copy of \dvi{} file. -\item[dvitomp] \dvi{} to MPX (MetaPost pictures). -\item[dvitype] \dvi{} to human-readable text. -\item[gftodvi] Generic font proofsheets. -\item[gftopk] Generic to packed fonts. -\item[gftype] GF to human-readable text. -\item[makempx] \MP{} label typesetting. -\item[mf] Creating typeface families. -\item[mft] Prettyprinting \MF{} source. -\item[mpost] Creating technical diagrams. -\item[mpto] MetaPost label extraction. -\item[newer] Compare modification times. -\item[patgen] Creating hyphenation patterns. -\item[pktogf] Packed to generic fonts. -\item[pktype] PK to human-readable text. -\item[pltotf] Property list to TFM. -\item[pooltype] Display \web{} pool files. -\item[tangle] \web{} to Pascal. -\item[tex] Typesetting. -\item[tftopl] TFM to property list. -\item[vftovp] Virtual font to virtual property list -\item[vptovf] Virtual property list to virtual font. -\item[weave] \web{} to \TeX. -\end{description} -\noindent The precise functions and syntax of these programs are described in -the documentation of the individual packages or of \Webc{} itself. -However, knowing a few principles governing the whole family of -programs will help you to benefit optimally from your \Webc{} -installation. - -All programs honor the standard \acro{GNU} options: -\begin{description} -\item[\texttt{-{}-help\ \ \ }] print basic usage summary. -\item[\texttt{-{}-verbose}] print detailed progress report. -\item[\texttt{-{}-version}] print version information, then exit. -\end{description} - -For locating files the \Webc{} programs use the path searching library -\KPS{}. This library uses a combination of environment variables and a -few configuration files to optimize searching the \TeX{} directory -tree. \Webc{} can handle more than one directory tree -simultaneously, which is useful if one wants to maintain \TeX's -standard distribution and local extensions in two distinct trees. To -speed up file searches the root of each tree has a file \file{ls-R}, -containing an entry showing the name and relative pathname for all -files ``hanging'' under that root. - -\subsection{\protect\KPS\ path searching} - -Let us first describe the generic path searching mechanism of the \KPS{} -library. - -We call a \emph{search path} a colon- or semicolon\hyph sepa\-rated list -of \emph{path elements}, which are basically directory names. A -search path can come from (a combination of) many sources. To look up -a file \samp{my-file} along a path \samp{.:/dir}, \KPS{} checks each -element of the path in turn: first \file{./my-file}, then -\file{/dir/my-file}, returning the first match (or possibly all -matches). - -In order to adapt optimally to all operating systems' conventions, on -non-Unix systems \KPS{} can use filename separators different from -``colon'' (\samp{:}) and ``slash'' (\samp{/}). - -To check a particular path element \var{p}, \KPS{} first checks if a -prebuilt database (see ``Filename data\-base'' on -page~\pageref{Filename-database}) applies to \var{p}, i.e., if the database -is in a directory that is a prefix of \var{p}. If so, the path -specification is matched against the contents of the database. - -If the database does not exist, or does not apply to this path -element, or contains no matches, the filesystem is searched (if this -was not forbidden by a specification starting with \samp{!!}\ and if -the file being searched for must exist). \KPS{} constructs the list -of directories that correspond to this path element, and then checks -in each for the file being sought. - -The ``file must exist'' condition comes into play with \samp{.vf} files and -input files read by \TeX's \cs{openin} command. Such files may not -exist (e.g., \file{cmr10.vf}), and so it would be wrong to search the -disk for them. Therefore, if you fail to update \file{ls-R} when you -install a new \samp{.vf} file, it will never be found. -Each path element is checked in turn: first the database, then the -disk. If a match is found, the search stops and the result is -returned. - -Although the simplest and most common path element is a directory -name, \KPS{} supports additional features in search paths: layered -default values, environment variable names, config file values, users' -home directories, and recursive subdirectory searching. Thus, we say -that \KPS{} \emph{expands} a path element, meaning it transforms all -the specifications into basic directory name or names. This is -described in the following sections in the same order as it takes -place. - -Note that if the filename being searched for is absolute or explicitly -relative, i.e., starts with \samp{/} or \samp{./} or \samp{../}, -\KPS{} simply checks if that file exists. - -\ifSingleColumn -\else -\begin{figure*} -\verbatiminput{../examples/ex5.tex} -\setlength{\abovecaptionskip}{0pt} - \caption{An illustrative configuration file sample} - \label{fig:config-sample} -\end{figure*} -\fi - -\subsubsection{Path sources} -\label{Path-sources} - -A search path can come from many sources. In the order in which -\KPS{} uses them: - -\begin{enumerate} -\item - A user-set environment variable, for instance, \envname{TEXINPUTS}\@. - Environment variables with a period and a program name appended - override; e.g., if \samp{latex} is the name of the program being run, - then \envname{TEXINPUTS.latex} will override \envname{TEXINPUTS}. -\item - A program-specific configuration file, for exam\-ple, a line - ``\texttt{S /a:/b}'' in \cmdname{dvips}'s \file{config.ps}. -\item A \KPS{} configuration file \file{texmf.cnf}, containing a line like - \samp{TEXINPUTS=/c:/d} (see below). -\item The compile-time default. -\end{enumerate} -\noindent You can see each of these values for a given -search path by using the debugging options (see ``Debugging actions'' -on page~\pageref{Debugging}). - -\subsubsection{Config files} - -\tolerance=3500 -\KPS{} reads \emph{runtime configuration files} named \file{texmf.cnf} -for search path and other definitions. The search path used to look -for these files is named \envname{TEXMFCNF} (by default such a file lives -in the \file{texmf/web2c} subdirectory). \emph{All} -\file{texmf.cnf} files in the search path will be read and definitions -in earlier files override those in later files. Thus, with a search -path of \verb|.:$TEXMF|, values from \file{./texmf.cnf} override those -from \verb|$TEXMF/texmf.cnf|. - -\tolerance=1500 - -While reading the description of the format of the file -\file{texmf.cnf} below, please also refer to -appendix~\ref{app:texmf.cnf}, starting on -page~\pageref{app:texmf.cnf}, which lists the \file{texmf.cnf} file on -the \CD. - -\begin{itemize} -\item - Comments start with ``\texttt{\%}'' and continue to the end of the line. -\item - Blank lines are ignored. -\item - A \bs{} at the end of a line acts as a continuation character, - i.e., the next line is appended. Whitespace at the beginning of - continuation lines is not ignored. -\item - Each remaining line has the form: -\begin{alltt} - \emph{variable}[.\emph{progname}] [=] \emph{value} -\end{alltt}% - where the \samp{=} and surrounding whitespace are optional. -\item - The ``\texttt{\var{variable}}'' name may contain any character other - than whitespace, \samp{=}, or \samp{.}, but sticking to - \samp{A-Za-z\_} is safest. -\item - If ``\texttt{.\var{progname}}'' is present, the definition only - applies if the program that is running is named - \texttt{\var{progname}} or \texttt{\var{progname}.exe}. This allows - different flavors of \TeX{} to have different search paths, for - example. -\item ``\texttt{\var{value}}'' may contain any characters except - ``\texttt{\%}'' and \samp{@}. The - ``\texttt{\$\var{var}.\var{prog}}'' feature is not available on the - right-hand side; instead, you must use an additional variable. A - \samp{;}\ in ``\texttt{\var{value}}'' is translated to \samp{:}\ if - running under Unix; this is useful to be able to have a single - \file{texmf.cnf} for Unix, MSDOS and Windows systems. -\item - All definitions are read before anything is expanded, so - variables can be referenced before they are defined. -\end{itemize} -A configuration file fragment illustrating most of these points is -\ifSingleColumn -shown below: - -\verbatiminput{../examples/ex5.tex} -\else -shown in Figure~\ref{fig:config-sample}. -\fi - -\subsubsection{Path expansion} -\label{Path-expansion} - - -\KPS{} recognizes certain special characters and constructions in -search paths, similar to those available in Unix shells. As a -general example, the complex path, -\verb+~$USER/{foo,bar}//baz+, expands to all subdirectories under -directories \file{foo} and \file{bar} in \texttt{\$USER}'s home -directory that contain a directory or file \file{baz}. These -expansions are explained in the sections below. -%$ -\subsubsection{Default expansion} -\label{Default-expansion} - -\tolerance=2500 -If the highest-priority search path (see ``Path sources'' on -page~\pageref{Path-sources}) contains an \emph{extra colon} (i.e., -leading, trailing, or doubled), \KPS{} inserts at that point the -next-highest-prio\-rity search path that is defined. If that inserted -path has an extra colon, the same happens with the next highest. For -example, given an environment variable setting - -\tolerance=1500 - -\begin{alltt} ->> \Ucom{setenv TEXINPUTS /home/karl:} -\end{alltt} -and a \code{TEXINPUTS} value from \file{texmf.cnf} of - -\begin{alltt} - .:\$TEXMF//tex -\end{alltt} -then the final value used for searching will be: - -\begin{alltt} - /home/karl:.:\$TEXMF//tex -\end{alltt} - -Since it would be useless to insert the default value in more than one -place, \KPS{} changes only one extra \samp{:}\ and leaves any others in -place: it checks first for a leading \samp{:}, then a trailing -\samp{:}, then a doubled \samp{:}. - -\subsubsection{Brace expansion} - -A useful feature is brace expansion, which means that, for instance, -\verb+v{a,b}w+ expands to \verb+vaw:vbw+. Nesting is allowed. -This can be used to implement multiple \TeX{} hierarchies, by -assigning a brace list to \code{\$TEXMF}. -For example, in \file{texmf.cnf}, you find -the following definition: -\begin{verbatim} - TEXMF = {$HOMETEXMF,$TEXMFLOCAL,!!$VARTEXMF,!!$TEXMFMAIN} -\end{verbatim} -Using this you can then write something like -\begin{verbatim} - TEXINPUTS = .;$TEXMF/tex// -\end{verbatim} -%$ -which means that, after looking in the current directory, the -\code{\$HOMETEXMF/tex}, \code{\$TEXMFLOCAL/tex}, \code{\$VARTEXMF/tex} -and \code{\$TEXMFMAIN/tex} trees \emph{only}) will be searched (the -last two use using \file{ls-R} data base files). It is a convenient -way for running two parallel \TeX{} structures, one ``frozen'' (on a -\CD, for instance) and the other being continuously updated with new -versions as they become available. By using the \code{\$TEXMF} -variable in all definitions, one is sure to always search the -up-to-date tree first. - -\subsubsection{Subdirectory expansion} -\label{Subdirectory-expansion} - -Two or more consecutive slashes in a path element following a directory -\var{d} is replaced by all subdirectories of \var{d}: first those -subdirectories directly under \var{d}, then the subsubdirectories under -those, and so on. At each level, the order in which the directories are -searched is \emph{unspecified}. - -If you specify any filename components after the \samp{//}, only -subdirectories with matching components are included. For example, -\samp{/a//b} expands into directories \file{/a/1/b}, \file{/a/2/b}, -\file{/a/1/1/b}, and so on, but not \file{/a/b/c} or \file{/a/1}. - -Multiple \samp{//} constructs in a path are possible, but -\samp{//} at the beginning of a path is ignored. - -\subsubsection{List of special characters and their meaning: a summary} - -The following list summarises the meaning of special characters -in \KPS{} configuration files. - -\newcommand{\CODE}[1]{\makebox[2.2em][l]{\code{#1}}} -\begin{description} -\item[\CODE{:}] Separator in path specification; at the beginning or - the end of a path it substitutes the default path expansion. -\item[\CODE{;}] Separator on non-Unix systems (acts like \code{:}). -\item[\CODE{\$}] Variable expansion. -\item[\CODE{\string~}] Represents the user's home directory. -\item[\CODE{\char`\{\dots\char`\}}] Brace expansion, e.g., - \verb+a{1,2}b+ will become \verb+a1b:a2b+. -\item[\CODE{//}] Subdirectory expansion (can occur anywhere in - a path, except at its beginning). -\item[\CODE{\%}] Start of comment. -\item[\CODE{\bs}] Continuation character (allows multi-line entries). -\item[\CODE{!!}] Search \emph{only} database to locate file, \emph{do - not} search the disk. -\end{description} - - -\subsection{Filename databases} -\label{Filename-database} - - -\KPS{} goes to some lengths to minimize disk accesses for searches. -Nevertheless, at installations with enough directories, searching each -possible directory for a given file can take an excessively long time -(this is especially true if many hundreds of font directories have to -be traversed.) Therefore, \KPS{} can use an externally-built -``database'' file named \file{ls-R} that maps files to directories, -thus avoiding the need to exhaustively search the disk. - -A second database file \file{aliases} allows you to give additional -names to the files listed in \file{ls-R}. This can be helpful to -adapt to DOS-like ``8.3'' filename conventions in source files. - -\subsubsection{The filename database} -\label{ls-R} - -As explained above, the name of the main filename database must be -\file{ls-R}. You can put one at the root of each \TeX{} hierarchy in -your installation that you wish to be searched (\code{\$TEXMF} by -default); most sites have only one hierarchy. \KPS{} looks for -\file{ls-R} files along the \code{TEXMFDBS} path. - -The recommended way to create and maintain \samp{ls-R} is to run the -\code{mktexlsr} script included with the distribution. It is invoked -by the various \samp{mktex}\dots\ scripts. In principle, this script -just runs the command -\begin{alltt} -cd \var{/your/texmf/root} && ls -LAR ./ >ls-R -\end{alltt} -presuming your system's \code{ls} produces the right output format -(\acro{GNU}'s \code{ls} is all right). To ensure that the database is always -up to date, it is easiest to rebuild it regularly via \code{cron}, so -that for changes in the installed files\Dash perhaps after installing or -updating a \LaTeX{} package\Dash the file \file{ls-R} is automatically -updated. - -If a file is not found in the database, by default \KPS{} goes ahead -and searches the disk. If a particular path element begins with -\samp{!!}, however, \emph{only} the database will be searched for that -element, never the disk. - - -\subsubsection{kpsewhich: Standalone path searching} -\label{Invoking-kpsewhich} - -The \texttt{kpsewhich} program exercises path searching independent of any -particular application. This can be useful as a sort of \code{find} -program to locate files in \TeX{} hierarchies (this is used heavily in -the distributed \samp{mktex}\dots\ scripts). - -\begin{alltt} ->> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} -\end{alltt} -The options specified in ``\texttt{\var{option}}'' can start with either \samp{-} -or \samp{-{}-}, and any unambiguous abbreviation is accepted. - -\KPS{} looks up each non-option argument on the command line as a -filename, and returns the first file found. There is no option to -return all the files with a particular name (you can run the Unix -\samp{find} utility for that). - -The more important options are described next. - -\begin{description} -\item[\texttt{-{}-dpi=\var{num}}]\mbox{} - Set the resolution to ``\texttt{\var{num}}''; this only affects \samp{gf} - and \samp{pk} lookups. \samp{-D} is a synonym, for compatibility - with \cmdname{dvips}. Default is 600. -\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ - Set the format for lookup to ``\texttt{\var{name}}''. By default, the - format is guessed from the filename. For formats which do not have - an associated unambiguous suffix, such as \MP{} support files and - \cmdname{dvips} configuration files, you have to specify the name as - found in the first column of Table~\ref{TABKpathsea}, which lists - currently recognized names, a description, - associated environment variables%, - \footnote{You can find definitions for these environment variables - in the file \file{texmf.cnf} (page~\pageref{app:texmf.cnf})}, and - possible file extensions. -\end{description} - - -\def\KpathKey#1#2#3#4#5{% name, number, description, variables, - % suffixes -\SetRowColor#1 & #3 & #4 & #5\\} -\def\HEAD#1{\multicolumn{1}{l}{\emph{#1}}} -% -\begin{small} -% a footnoterule immediately under a bottom-of-page rule looks dead -% silly, so we suppress it -\renewcommand\footnoterule{\relax} -% -\begin{longtable}{@{}% - >{\ttfamily}P{.16\textwidth}% Col.1 - P{.3\textwidth}% Col 2 - >{\ttfamily\footnotesize}P{.29\textwidth}% Col 3 - >{\ttfamily}P{.14\textwidth}% Col 4 -@{}} -\caption{Kpathsea file types}\label{TABKpathsea}\\ -\emph{Name} & \HEAD{Description} & \HEAD{Variables} -& \HEAD{Suffixes}\\ -\hline -\endfirsthead -\multicolumn{3}{l}{Kpathsea file types \emph{continued}}\\ -\emph{Name} & \HEAD{Description} & \HEAD{Variables} -& \HEAD{Suffixes}\\ -\hline -\noalign{\vspace{2pt}} -\endhead -\mbox{}\\ -\hline -\endfoot -\KpathKey - {afm} - {4} - {Adobe font metrics} - {AFMFONTS} - {.afm} -\KpathKey - {base} - {5} - {Metafont memory dump} - {MFBASES, TEXMFINI} - {.base} -\KpathKey - {bib} - {6} - {\BibTeX{} bibliography source} - {BIBINPUTS, TEXBIB} - {.bib} -\KpathKey - {} - {2} - {bitmap fonts} - {GLYPHFONTS, TEXFONTS} - {} -\KpathKey - {bst} - {7} - {\BibTeX{} style files} - {BSTINPUTS} - {.bst} -\KpathKey - {cnf} - {8} - {Runtime configuration files} - {TEXMFCNF} - {.cnf} -\KpathKey - {dvips config} - {34} - {\textsf{dvips} configuration files, e.g., \file{config.ps} - and \file{psfonts.map}} - {TEXCONFIG} - {.map} -\KpathKey - {fmt} - {10} - {\TeX{} memory dump} - {TEXFORMATS, TEXMFINI} - {.fmt, .efmt, .efm} -\KpathKey - {gf} - {0} - {generic font bitmap} - {GFFONTS} - {.gf} -\KpathKey - {graphic/figure} - {25} - {Encapsulated PostScript figures} - {TEXPICTS, TEXINPUTS} - {.eps, .epsi} -\KpathKey - {ist} - {35} - {\textsf{makeindex} style files} - {TEXINDEXSTYLE, INDEXSTYLE} - {.ist} -\KpathKey - {ls-R} - {9} - {Filename databases} - {TEXMFDBS} - {} -\KpathKey - {map} - {11} - {Fontmaps} - {TEXFONTMAPS} - {.map} -\KpathKey - {mem} - {12} - {MetaPost memory dump} - {MPMEMS, TEXMFINI} - {.mem} -\KpathKey - {mf} - {13} - {Metafont source} - {MFINPUTS} - {.mf} -\KpathKey - {mfpool} - {14} - {Metafont program strings} - {MFPOOL, TEXMFINI} - {.pool} -\KpathKey - {mft} - {15} - {MFT style file} - {MFTINPUTS} - {.mft} -\KpathKey - {} - {41} - {miscellaneous fonts} - {MISCFONTS} - {} -\KpathKey - {mp} - {16} - {MetaPost source} - {MPINPUTS} - {.mp} -\KpathKey - {mppool} - {17} - {MetaPost program strings} - {MPPOOL, TEXMFINI} - {.pool} -\KpathKey - {MetaPost support} - {18} - {MetaPost support files, used by DMP} - {MPSUPPORT} - {} -\KpathKey - {ocp} - {19} - {\OMEGA{} compiled process files} - {OCPINPUTS} - {.ocp} -\KpathKey - {ofm} - {20} - {\OMEGA{} font metrics} - {OFMFONTS, TEXFONTS} - {.ofm, .tfm} -\KpathKey - {opl} - {21} - {\OMEGA{} property lists} - {OPLFONTS, TEXFONTS} - {.opl} -\KpathKey - {otp} - {22} - {\OMEGA{} translation process files} - {OTPINPUTS} - {.otp} -\KpathKey - {ovf} - {23} - {\OMEGA{} virtual fonts} - {OVFFONTS, TEXFONTS} - {.ovf} -\KpathKey - {ovp} - {24} - {\OMEGA{} virtual property lists} - {OVPFONTS, TEXFONTS} - {.ovp} -\KpathKey - {pk} - {1} - {packed bitmap fonts} - {\emph{program}FONTS \textrm{(\texttt{\emph{program}} being - \textsmaller{\cmdname{XDVI}}, - etc.)}, PKFONTS, TEXPKS, GLYPHFONTS, TEXFONTS} - {.pk} -\KpathKey - {PostScript header} - {30} - {downloadable PostScript} - {TEXPSHEADERS, PSHEADERS} - {.pro, .enc} -\KpathKey - {tex} - {26} - {\TeX{} source} - {TEXINPUTS} - {.tex, .cls, .sty, .clo, .def} -\KpathKey - {TeX system documentation} - {27} - {Documentation files for the \TeX{} system} - {TEXDOCS} - {} -\KpathKey - {TeX system sources} - {29} - {Source files for the \TeX{} system} - {TEXSOURCES} - {} -\KpathKey - {texpool} - {28} - {\TeX{} program strings} - {TEXPOOL, TEXMFINI} - {.pool} -\KpathKey - {tfm} - {3} - {\TeX{} font metrics} - {TFMFONTS, TEXFONTS} - {.tfm} -\KpathKey - {Troff fonts} - {31} - {Troff fonts, used by DMP} - {TRFONTS} - {} -\KpathKey - {truetype fonts} - {36} - {TrueType outline fonts} - {TTFONTS} - {.ttf, .ttc} -\KpathKey - {type1 fonts} - {32} - {Type 1 PostScript outline fonts} - {T1FONTS, T1INPUTS, TEXPSHEADERS, DVIPSHEADERS} - {.pfa, .pfb} -\KpathKey - {type42 fonts} - {37} - {Type 42 PostScript outline fonts} - {T42FONTS} - {} -\KpathKey - {vf} - {33} - {virtual fonts} - {VFFONTS, TEXFONTS} - {.vf} -\KpathKey - {web2c files} - {38} - {\Webc{} support files} - {WEB2C} - {} -\KpathKey - {other text files} - {39} - {text files used by `\textsf{foo}'} - {FOOINPUTS} - {} -\KpathKey - {other binary files} - {40} - {binary files used by `\textsf{foo}'} - {FOOINPUTS} - {} -\end{longtable} -\end{small} - - -\begin{multicols}{2} - -\begin{description} -\item[] The last two entries in Table~\ref{TABKpathsea} are special - cases, where the paths and environment variables depend on the name - of the program: the variable name is constructed by converting the - program name to upper case, and then appending \texttt{INPUTS}. - - The environment variables are set by default in the configuration - file \file{texmf.cnf}. It is only when you want to override one or - more of the values specified in that file that you might want to set - them explicitly in your execution environment. - - Note that the \samp{-{}-format} and \samp{-{}-path} options are mutually - exclusive. -\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ - Set the mode name to ``\texttt{\var{string}}''; this only affects \samp{gf} - and \samp{pk} lookups. No default: any mode will be found. -\item[\texttt{-{}-must-exist}]\mbox{}\\ - Do everything possible to find the files, notably including - searching the disk. By default, only the \file{ls-R} database is - checked, in the interest of efficiency. -\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ - Search along the path ``\texttt{\var{string}}'' (colon-% - separated as usual), - instead of guessing the search path from the filename. \samp{//} - and all the usual expansions are supported. - The options \samp{-{}-path} and \samp{-{}-format} are mutually - exclusive. -\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ - Set the program name to ``\texttt{\var{name}}''. - This can affect the search paths via the ``\texttt{.\var{prognam}}'' - feature in configuration files. - The default is \samp{kpsewhich}. -\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ - shows the path used for file lookups of file type ``\texttt{\var{name}}''. - Either a filename extension (\samp{.pk}, \samp{.vf}, etc.) or a - name can be used, just as with \samp{-{}-format} option. -\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ - sets the debugging options to ``\texttt{\var{num}}''. -\end{description} - - -\subsubsection{Examples of use} -\label{SExamplesofuse} - -Let us now have a look at \KPS{} in action. - -\begin{alltt} ->> \Ucom{kpsewhich article.cls} -/usr/local/texmf/tex/latex/base/article.cls -\end{alltt} -We are looking for the file \file{article.cls}. Since the \samp{.cls} -suffix is unambiguous we do not need to specify that we want to look for a -file of type ``tex'' (\TeX{} source file directories). We find it in -the subdirectory \file{tex/latex/base} below the \samp{TEXMF} root -directory. Similarly, all of the following are found without problems -thanks to their unambiguous suffix. -\begin{alltt} ->> \Ucom{kpsewhich array.sty} - /usr/local/texmf/tex/latex/tools/array.sty ->> \Ucom{kpsewhich latin1.def} - /usr/local/texmf/tex/latex/base/latin1.def ->> \Ucom{kpsewhich size10.clo} - /usr/local/texmf/tex/latex/base/size10.clo ->> \Ucom{kpsewhich small2e.tex} - /usr/local/texmf/tex/latex/base/small2e.tex ->> \Ucom{kpsewhich tugboat.bib} - /usr/local/texmf/bibtex/bib/beebe/tugboat.bib -\end{alltt} - -The latter is a \BibTeX{} bibliography database for \textsl{TUGBoat} articles. - -\begin{alltt} ->> \Ucom{kpsewhich cmr10.pk} -\end{alltt} -Font bitmap glyph files of type \file{.pk} are used by display -programs like \cmdname{dvips} and \cmdname{xdvi}. Nothing is returned in -this case since there are no pre-generated Computer Modern \samp{.pk} -files on our system (since we use the Type1 versions on the \CD{}). -\begin{alltt} ->> \Ucom{kpsewhich ecrm1000.pk} -\ifSingleColumn /usr/local/texmf/fonts/pk/ljfour/jknappen/ec/ecrm1000.600pk -\else -/usr/local/texmf/fonts/pk/ljfour/jknappen/ -... ec/ecrm1000.600pk -\fi\end{alltt} -For the extended Computer Modern files we had to generate \samp{.pk} -files, and since the default \MF{} mode on our installation is -\texttt{ljfour} with a base resolution of 600 dpi (dots per inch), -this instantiation is returned. -\begin{alltt} ->> \Ucom{kpsewhich -dpi=300 ecrm1000.pk} -\end{alltt} -In this case, when specifying that we are interested in a resolution -of 300dpi (\texttt{-dpi=300}) we see that no such font is available on -the system. In fact, a program like \cmdname{dvips} or \cmdname{xdvi} would -go off and actually build the \texttt{.pk} files at the required -resolution using the script \cmdname{mktexpk}. - -Next we turn our attention to \cmdname{dvips}'s header and configuration -files. We first look at one of the commonly used files, the general -prolog \file{tex.pro} for \TeX{} support, before turning our attention -to the generic configuration file (\file{config.ps}) and the -PostScript font map \file{psfonts.map}. As the \samp{.ps} suffix is -ambiguous we have to specify explicitly which type we are considering -(``\texttt{dvips config}'') for the file \texttt{config.ps}. -\begin{alltt} ->> \Ucom{kpsewhich tex.pro} - /usr/local/texmf/dvips/base/tex.pro ->> \Ucom{kpsewhich --format="dvips config" config.ps} - /usr/local/texmf/config/config.ps ->> \Ucom{kpsewhich psfonts.map} - /usr/local/texmf/dvips/base/psfonts.map -\end{alltt} - -We now take a closer look at the URW Times PostScript support files. -The name for these in Berry's font naming scheme is ``\texttt{utm}''. -The first file we look at is the configuration file, which contains -the name of the map file: -\begin{alltt} ->> \Ucom{kpsewhich --format="dvips config" config.utm} -/usr/local/texmf/dvips/psnfss/config.utm -\end{alltt} -The contents of that file is -\begin{alltt} - p +utm.map -\end{alltt} -which points to the file \file{utm.map}, which we want to -locate next. -\begin{alltt} ->> \Ucom{kpsewhich --format="dvips config" utm.map} - /usr/local/texmf/dvips/psnfss/utm.map -\end{alltt} -This map file defines the file names of the Type1 PostScript fonts in -the URW collection. Its contents look like (we only show part of the -lines): -\begin{alltt} - utmb8r NimbusRomNo9L-Medi ... > \Ucom{kpsewhich utmr8a.pfb} -\ifSingleColumn /usr/local/texmf/fonts/type1/urw/utm/utmr8a.pfb -\else /usr/local/texmf/fonts/type1/ -... urw/utm/utmr8a.pfb -\fi\end{alltt} - -It should be evident from these few examples how you can easily locate -the whereabouts of a given file. This is especially important if you -suspect that the wrong version of a file is picked up somehow, since -\cmdname{kpsewhich} will show you the first file encountered. - -\subsubsection{Debugging actions} -\label{Debugging} - -Sometimes it is necessary to investigate how a program resolves -file references. To make this feasible in a convenient way \KPS{} -offers various debug levels: -\begin{itemize} -\item[\texttt{\ 1}] \texttt{stat} calls (file tests). When running - with an up-to-date \file{ls-R} database this should almost give no - output. -\item[\texttt{\ 2}] References to hash tables (like \file{ls-R} - database, map files, configuration files). -\item[\texttt{\ 4}] File open and close operations. -\item[\texttt{\ 8}] General path information for file types - searched by \KPS. This is useful to find out where a particular - path for the file was defined. -\item[\texttt{16}] Directory list for each path element (only relevant - for searches on disk). -\item[\texttt{32}] File searches. -\end{itemize} -A value of \texttt{-1} will set all the above options; in practice you -will probably always use these levels if you need any debugging. - -Similarly, with the \cmdname{dvips} program, by setting a -combination of debug switches, one can follow in detail where files are being picked -up from. Alternatively, when a file is not found, the debug trace -shows in which directories the program looks for the given file, so -that one can get an indication what the problem~is. - -Generally speaking, as most programs call the \KPS{} library -internally, one can select a debug option by using the -\envname{KPATHSEA\_DEBUG} environment variable, and setting it to (a -combination of) values as described in the above list. - -(Note for Windows users: it is not easy to redirect -all messages to a file in this system. For diagnostic purposes -you can temporarily \texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log}). - -Let us consider, as an example, a small \LaTeX{} source file, -\file{hello-world.tex}, which contains the following input. -\begin{verbatim} - \documentclass{article} - \begin{document} - Hello World! - \end{document} -\end{verbatim} -This little file only uses the font \file{cmr10}, so let us look -how \cmdname{dvips} prepares the PostScript file (we want to use the Type1 -version of the Computer Modern fonts, hence the option \texttt{-Pcms}). -\begin{alltt} ->> \Ucom{dvips -d4100 hello-world -Pcms -o} -\end{alltt} -In this case we have combined \cmdname{dvips}'s debug class 4 (font -paths) with \KPS's path element expansion (see \cmdname{dvips} Reference -Manual, \OnCD{texmf/doc/html/dvips/dvips_toc.html}). -%\ifSingleColumn -%We get something -%like the following (we have rearranged the output for easier display): -%\begin{alltt}\small -%\input{../examples/ex6.tex} -%\end{alltt} -%\else -The output (slightly rearranged) appears in -Figure~\ref{fig:dvipsdbga}. -\begin{figure*}[tp] -\centering -\input{../examples/ex6a.tex} -\caption{Finding configuration files}\label{fig:dvipsdbga} - -\bigskip - -\input{../examples/ex6b.tex} -\caption{Finding the prolog file}\label{fig:dvipsdbgb} - -\bigskip - -\input{../examples/ex6c.tex} -\caption{Finding the font file}\label{fig:dvipsdbgc} -\end{figure*} -\cmdname{dvips} starts by locating its working files. First, -\file{texmf.cnf} is found, which gives the definitions of the search -paths for the other files, then the file database \file{ls-R} (to -optimize file searching) and the file \file{aliases}, which makes it -possible to declare several names (e.g., a short \acro{DOS}-like ``8.3'' and -a more natural longer version) for the same file. Then \cmdname{dvips} -goes on to find the generic configuration file \file{config.ps} -before looking for the customization file \file{.dvipsrc} (which, in -this case is \emph{not found}). Finally, \cmdname{dvips} locates the -config file for the Computer Modern PostScript fonts \file{config.cms} -(this was initiated with the \texttt{-Pcms} option on the \cmdname{dvips} -command). This file contains the list of the ``map'' files which -define the relation between the \TeX{}, PostScript and file system -names of the fonts. -\begin{alltt} ->> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} - p +ams.map - p +cms.map - p +cmbkm.map - p +amsbkm.map -\end{alltt} -\cmdname{dvips} thus goes on to find all these files, plus the generic -map file \file{psfonts.map}, which is always loaded (it contains -declarations for commonly used PostScript fonts; see the last part of -Section \ref{SExamplesofuse} for more details about PostScript map -file handling). - -At this point \cmdname{dvips} identifies itself to the user\ldots -\begin{alltt}\ifSingleColumn -This is dvips 5.78 Copyright 1998 Radical Eye Software (www.radicaleye.com) -\else\small{}This is dvips 5.78 Copyright 1998 Radical Eye... -\fi\end{alltt}% decided to accept slight overrun in tub case -\ifSingleColumn -\ldots and then goes on to look for the prolog file \file{texc.pro}, -\begin{alltt}\small -kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro -\end{alltt} -\else -then goes on to look for the prolog file \file{texc.pro} (see -Figure~\ref{fig:dvipsdbgb}). - -\fi -After having found the file in question, \cmdname{dvips} outputs -date and time, and informs us that it will generate the -file \file{hello-world.ps}, then that it needs the font file -\file{cmr10}, and that the latter is declared as ``resident'': -\begin{alltt}\small -TeX output 1998.02.26:1204' -> hello-world.ps -Defining font () cmr10 at 10.0pt -Font cmr10 is resident. -\end{alltt} -Now the search is on for the file \file{cmr10.tfm}, which is found, -then a few more prolog files (not shown) are referenced, and finally -the Type1 instance \file{cmr10.pfb} of the font is located and -included in the output file (see last line). -\begin{alltt}\small -kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, - path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: - /var/tex/fonts/tfm//). -kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm -kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, - ... - -kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb -[1] -\end{alltt} - -\subsection{Runtime options} - -Another of the nice features of \Webc{} is its possibility to -control a number of memory parameters (in particular, array sizes) via -the runtime file \file{texmf.cnf} read by \KPS{}. The listing of -\file{texmf.cnf} is shown in Appendix~\ref{app:texmf.cnf}, starting on -page~\pageref{app:texmf.cnf}; the settings of all parameters can be -found in Part 3 of that file. The more important control variables are: -\begin{description} -\item[\texttt{main\_memory}] - Total words of memory available, for - \TeX{}, \MF{} and \MP. You must make a new format file for each - different setting. For instance, you could generate a ``huge'' - version of \TeX{}, and call the format file \texttt{hugetex.fmt}. - Using the standard way of specifying the program name used by \KPS{}, - the particular value of the \texttt{main\_memory} variable will then - be read from \file{texmf.cnf} (compare the generic value - and the ``huge'' one instantiated by \texttt{hugetex}, - etc.). -\item[\texttt{extra\_mem\_bot}] - Extra space for ``large'' \TeX{} data structures: - boxes, glue, breakpoints, etc. Especially useful if you use - \PiCTeX{}. -\item[\texttt{font\_mem\_size}] - Number of words for font information available for \TeX. This - is more or less the total size of all TFM files read. -\item[\texttt{hash\_extra}] - Additional space for the hash table of control sequence names. - Approximately 10,000 control sequences can be stored in the main - hash table; if you have a large book with numerous cross-references, - this might not be enough. You can see that both the - \cmdname{hugetex} and \cmdname{pdflatex} program invocations ask for - an extra 15,000 control sequences (the default value of - \texttt{hash\_extra} is zero). -\end{description} -Of course, this facility is no substitute for truly dynamic arrays and -memory allocation, but since this is extremely difficult to implement -in present \TeX, these runtime parameters provide a practical compromise -allowing some flexibility. - -%-------------------------------------------------------- - - -\section{Acknowledgements}\label{sec:acknowl} -This edition of TeXLive is edited by Sebastian Rahtz, with the -major contributors being Fabrice Popineau, who has worked away -unceasingly at the Win32 part of the package (especially the setup!) -and contributed in many different ways with ideas, advice and code; -and Staszek Wawrykiewicz, who provided great checking feedback, and -co-ordinated the Polish contributions. Kaja Christiansen performed a -vital role in endless recompilations on assorted Unix platforms, and -Robin Laakso coordinated production for TUG. Vladimir Volovich -did great work on cleaning the source and making other improvements, -while Gerben Wierda did all the work for MacOSX. - -We are very grateful for past and present help from -\begin{itemize} -\item The German-speaking \TeX{} Users (DANTE e.V.), who provided a machine - on which the master of the CD-ROM is developed and maintained; and Rainer -Sch\"opf and Reinhard Zierke who look after it; -\item The Perforce company, for providing a free copy of their -excellent change management system, which we have used to - manage the CD-ROM -contents; -\item Karl Berry, who provided the original \Webc{} distribution, and - has continued to give invaluable advice, encouragement, and help; -\item Mimi Burbank, who arranged access - at the Florida State University School of Computational Science - and Information Technology - to a slew of different - computers to compile \TeX{} on, and acted as an essential guinea-pig - whenever asked; -\item Kaja Christiansen, who provided essential feedback, compilation, and - documentation preparation; -\item Thomas Esser, without whose marvellous \teTeX{} package this - \CD{} would certainly not exist, and whose continual help makes it a - better product; -\item Michel Goossens, who co-authored the documentation; -\item Eitan Gurari, whose \TeX4ht was used to create the \HTML{} - version of this documentation, and who worked tirelessly to improve - it at short notice; -\item Art Ogawa and Pat Monohon, who coordinated releases for TUG; -\item Petr Olsak, who coordinated and checked all the Czech/Slovak - material very carefully; -\item Olaf Weber, for his patient assembly and maintenance of Web2c; -\item Graham Williams, on whose work the catalogue of packages depends. -\end{itemize} - -Gerhard Wilhelms, Volker Schaa, Fabrice Popineau, Janka -Chleb\'\i{}kov\'a, Staszek Wawrykiewicz, Erik Frambach, and Ulrik -Vieth kindly translated documentation at various times into their -respective languages, checked other documentation, and provided very -welcome feedback. - - -\section{History} - -This \CD{} distribution is a joint effort by many \TeX{} Users -Groups, including those from Germany, the Netherlands, the UK, France, -the Czech Republic/Slovakia, India, Poland and Russia, as well as -the international TUG. -Discussion began in late 1993 when the Dutch \TeX{} Users Group was -starting work on its 4All\TeX{} \CD{} for \acro{MS-DOS} users, and it was -hoped at that time to issue a single, rational, \CD{} for all -systems. This was far too ambitious a target, but it did spawn not -only the very successful 4All\TeX{} \CD{}, but also the \acro{TUG} -Technical Council working group on a \emph{\TeX{} Directory - Structure}, which specified how to create consistent and manageable -collections of \TeX{} support files. The final draft of the \TDS{} was -published in the December 1995 issue of \textsl{TUGboat}, and it was clear from -an early stage that one desirable product would be a model structure -on \CD{}. The \CD{} you now have is a very direct result of the -working group's deliberations. It was also clear that the success of -the 4All\TeX{} \CD{} showed that Unix users would benefit from a -similarly easy system, and this is the other main strand of \TeXLive. - -We undertook to make a new Unix-based \TDS{} \CD{} in the autumn of -1995, and quickly identified Thomas Esser's \teTeX{} as the ideal -setup, as it already had multi-platform support and was built with -portability across file systems in mind. Thomas agreed to help, and -work began seriously at the start of 1996. The first edition was -released in May 1996. At the start of 1997, Karl Berry completed a -major new release of his \Webc{} package, which included nearly all -the features which Thomas Esser had added in \teTeX, and we decided to -base the 2nd edition of the \CD{} on the standard \Webc, with the -addition of \teTeX's \texttt{texconfig} script. The 3rd edition of the -\CD{} was based on a major revision of \Webc, 7.2, by Olaf Weber; at the -same time, a new revision of \teTeX was being made, -and \TeXLive{} shares almost all of its features. The 4th edition -followed the same pattern, using a new version of te\TeX, and a new -release of \Webc{} (7.3). The system now included a complete Windows setup. - -For the 5th edition (March 2000) many parts of the \CD{} were revised -and checked, updating hundreds of packages. Package details were -stored in XML files. But the major change for \TeX\ Live 5 was that -all non-free software was removed. Everything on this \CD{} should be -compatible with the Debian Free Software Guidelines -(\url{http://www.debian.org/intro/free}); we have done our best to -check the license conditions of all packages, but we would very much -appreciate hearing of any mistakes. - -The 6th edition (July 2001) had a lot material updated. The major -change was a new install concept: the user could select a more exact set -of needed collections. Language-related collections were completely -reorganized, so selecting any of them installs not only macros, fonts, -etc., but also prepares an appropriate \texttt{language.dat}. - -The 7th edition of 2002 had as a major addition a setup -for MacOSX, and the usual myriad of updates to all sorts -of packages and programs. An important goal was integration -of the source back with teTeX, to correct the drift apart -in versions 5 and 6. - -\section{Future versions} - -\emph{This \CD{} is not a perfect product!} We plan to re-issue it -once a year, and would like to provide more help material, more -utilities, more installation programs, and (of course) an -ever-improved and checked tree of macros and fonts. This work is all -done by hard-pressed volunteers in their limited spare time, and a -great deal remains to be done. If you can help, don't hesitate to put -your name forward! - -Corrections, suggestions and additions for future revisions -should be sent to:\hfill\null -\begin{quote} -Sebastian Rahtz\\ -{}7 Stratfield Road\\ -Oxford OX2 7BG\\ -United Kingdom\\ -\EmailURL{rahtz@tug.org} -\end{quote} - - -Updates, notes, and suggestions will be made available on \CTAN{} -in \path|info/texlive|. A \acro{WWW} page for -information and ordering details is at -\url{http://www.tug.org/tex-live.html}. - -\end{multicols} - -\Section{The texmf.cnf file} -\label{app:texmf.cnf} -\begin{small} -\listinginput{1}{../examples/texmf.cnf} -\end{small} - -\end{document} - - - -Notes on Nicolle Zellner's problems: ------------------------------------- -- autoexec.bat gave error, ``too many parameters''. -fix: in setvars.bat file, put "" around %PATH% to take care of spaces. - -- ``out of environment space'' when rebooting meant that autoexec.bat was -not executing properly-- path and texmfhome variable were not being set. -fix: put in config.sys file the line: shell=c:\command.com /e:1024 /p -(and reboot probably) - -[Note: alternative advice written by Pat: - The environment space is an area of memory in which the OS stores - variables such as path. To increase the memory size do the following: - - Open a MS-DOS window. Click on the Properties icon (looks like a hand - holding a sheet of paper). Click on the Memory tab in the Properties - window. Change the value under Initial Environment: to 4096. Apply the - properties. Click OK on the warning about needing to restart your computer. - The new environment memory will be in effect after the reboot.] - -- windvi did not retain settings. -fix: in setvars.bat file, add command: set Home=c:\Home and also create -the directory c:\Home. -copy windvi.cnf to c:\Home\ -reboot - --ispell doesn't work (can't write to c:\tmp, can't create dictionary) -In addition to the the c:\Home addition above, create the folder: -d:\tmp\ (d: is where the files are that she is using.) -Now ispell should work from the command line. -Still can't get it to work from within \cmdname{WinShell}. (change cmd line to %c.tex, -it was reading the project main file) - - - -Notes on installing WinEdt: ---------------------------- -If you choose to install WinEdt, you will be asked for a folder name: any -folder name will do, as this is for temporary storage. An acceptable -choice is \verb+C:\Winedt+. Click \textbf{unzip}, then \textbf{OK}, -and finally \textbf{Close}. ---- - -later, to complete WinEdt installation: - -Run "winedt5.exe" and complete the setup procedure. - -Get from ftp://ftp.dante.de/pub/fptex/supplementary/ -30/08/2000 20:17 70 844 winedt5-cnf.zip -10/09/2000 10:43 839 086 winedt5-patch4.zip - -then unpack (use unzip or winzip with subdir creation enabled, NOT pkunzkip) - "winedt5-patch4.zip" inside the "c:\program files\winedt" directory -then at last unpack "winedt5-cnf.zip". - -When this is done, go inside the 'Options->Configurations' menu, -choose the "fpTeX Direct" option. - -If windvi previewer doesn't work, go to options->menu setup-> accessories -and change the Menu Setup so the call for DVI Preview is analogous to -the call for Dvips-- i.e., don't use "DVIVIEW" in the command line, -but rather fptex-bin and dviwin.exe. - - diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/live4ht.cfg-2004 b/Master/texmf-doc/source/texlive/texlive-en/archive/live4ht.cfg-2004 deleted file mode 100644 index 8700827d62a..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/live4ht.cfg-2004 +++ /dev/null @@ -1,36 +0,0 @@ -% $Id$ -% tex4ht configuration file for the TeX Live documentation. -% -% The 2 means to separate output files for only the top sectioning levels. -% xhtml specifies the main output format. -% info for extra debugging info in the log files. -% Without the \begin{document}, LaTeX complains that it is missing. -% -\Preamble{2,xhtml,info} \begin{document} \EndPreamble - -% simplify output for HTML. We leave TeX and LaTeX alone, since tex4ht -% actually does the lowered E (and raised A) in CSS. -\def\OMEGA{Omega} -\def\LaTeXe{LaTeX2e} -\def\eTeX{e-\TeX} -\def\acro#1{#1} -\def\MF{Metafont} -\def\BibTeX{BibTeX} -\def\warningbox{} -\def\endwarningbox{} - -\newif\ifhackliterals -\ifx\tldocenglish\undefined \else \hackliteralstrue \fi -\ifx\tldocrussian\undefined \else \hackliteralstrue \fi -\ifx\tldocgerman\undefined \else \hackliteralstrue \fi -% -\ifhackliterals - % these definitions cause "missing } inserted" at \end{tabularx} in - % French and Czech. don't know why. - % - % don't make these into links, as happens with \path. We only have a couple - % special characters that actually occur. - \def\dirname{\texttt\bgroup\catcode`\$=12 \catcode`\_=12 \finishliteral} - \def\finishliteral#1{#1\egroup} - \let\filename=\dirname -\fi diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/mod.pl b/Master/texmf-doc/source/texlive/texlive-en/archive/mod.pl deleted file mode 100644 index 4f8df5df762..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/mod.pl +++ /dev/null @@ -1,976 +0,0 @@ - -$M{"a0poster"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; -$M{"a4"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"a4wide"}="18 May 1996 11:33:54 Graham.Williams\@cmis.csiro.au"; -$M{"a5"}="19 Apr 1998 15:19:21 Graham.Williams\@cmis.csiro.au"; -$M{"a5comb"}="19 Apr 1998 15:19:21 Graham.Williams\@cmis.csiro.au"; -$M{"aaai"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; -$M{"abc2mtex"}="27 Nov 1996 13:50:01 Graham.Williams\@cmis.csiro.au"; -$M{"abstbook"}="5 Mar 1997 16:28:20 Graham.Williams\@cmis.csiro.au"; -$M{"abstyles"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"accents"}="25 Feb 1999 09:06:12 Graham.Williams\@cmis.csiro.au"; -$M{"accfonts"}="30 Jan 1999 06:16:19 Graham.Williams\@cmis.csiro.au"; -$M{"achemso"}="8 Jul 1998 08:11:28 Graham.Williams\@cmis.csiro.au"; -$M{"acronym"}="17 Nov 1997 09:21:35 Graham.Williams\@cmis.csiro.au"; -$M{"acroread"}="20 May 1997 18:04:58 Graham.Williams\@cmis.csiro.au"; -$M{"acrotex"}="2 Dec 1998 09:52:54 Graham.Williams\@cmis.csiro.au"; -$M{"adfathesis"}="23 Feb 1999 16:11:03 Graham.Williams\@cmis.csiro.au"; -$M{"adobe"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"adobeother"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"adobestd"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"adrlist"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"advdate"}="5 Mar 1997 11:25:37 Graham.Williams\@cmis.csiro.au"; -$M{"ae"}="5 Dec 1998 08:56:53 Graham.Williams\@cmis.csiro.au"; -$M{"afterpage"}="13 Aug 1998 05:36:56 Graham.Williams\@cmis.csiro.au"; -$M{"afthesis"}="15 Dec 1996 19:08:54 Graham.Williams\@cmis.csiro.au"; -$M{"aguplus"}="16 Sep 1998 06:02:47 Graham.Williams\@cmis.csiro.au"; -$M{"aiaa"}="24 Feb 1999 09:15:44 Graham.Williams\@cmis.csiro.au"; -$M{"akletter"}="1 Jun 1998 12:04:46 Graham.Williams\@cmis.csiro.au"; -$M{"alatex"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"alg"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"algorithms"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"alltt"}="28 May 1996 16:23:49 Graham.Williams\@cmis.csiro.au"; -$M{"alphanum"}="10 Mar 1998 06:11:22 Graham.Williams\@cmis.csiro.au"; -$M{"altfont"}="1 Jul 1996 21:06:06 Graham.Williams\@cmis.csiro.au"; -$M{"altfont"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"amiweb2c"}="25 Mar 1998 09:12:31 Graham.Williams\@cmis.csiro.au"; -$M{"amsbsy"}="18 Jun 1997 19:16:14 Graham.Williams\@cmis.csiro.au"; -$M{"amscd"}="1 Nov 1996 08:34:08 Graham.Williams\@cmis.csiro.au"; -$M{"amsfonts"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"amsfonts"}="9 Nov 1996 15:43:40 Graham.Williams\@cmis.csiro.au"; -$M{"amslatex"}="9 Nov 1996 15:40:28 Graham.Williams\@cmis.csiro.au"; -$M{"amslatex"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"amsltx11"}="9 Nov 1996 15:46:01 Graham.Williams\@cmis.csiro.au"; -$M{"amsmath"}="9 Nov 1996 16:15:32 Graham.Williams\@cmis.csiro.au"; -$M{"amsppt"}="24 Sep 1996 08:42:35 Graham.Williams\@cmis.csiro.au"; -$M{"amsppt1"}="25 Sep 1996 09:41:18 Graham.Williams\@cmis.csiro.au"; -$M{"amssym"}="25 Sep 1996 09:44:00 Graham.Williams\@cmis.csiro.au"; -$M{"amssymb"}="11 Nov 1996 20:19:40 Graham.Williams\@cmis.csiro.au"; -$M{"amstex"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"amstex"}="9 Nov 1996 15:47:35 Graham.Williams\@cmis.csiro.au"; -$M{"amstext"}="11 Nov 1996 20:24:24 Graham.Williams\@cmis.csiro.au"; -$M{"answers"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"answers"}="29 May 1996 13:08:24 Graham.Williams\@cmis.csiro.au"; -$M{"anttvf"}="5 Feb 1998 09:27:21 Graham.Williams\@cmis.csiro.au"; -$M{"anttvf"}="08 Feb 1998 staw\@gust.org.pl"; -$M{"antyktor"}="18 Jun 1998 10:23:35 Graham.Williams\@cmis.csiro.au"; -$M{"apa"}="12 Nov 1998 11:38:01 Graham.Williams\@cmis.csiro.au"; -$M{"apacite"}="12 Jul 1996 10:10:07 Graham.Williams\@cmis.csiro.au"; -$M{"apasoft"}="15 Sep 1998 06:39:47 Graham.Williams\@cmis.csiro.au"; -$M{"apl"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"appendix"}="11 Dec 1998 05:36:39 Graham.Williams\@cmis.csiro.au"; -$M{"ar"}="24 Apr 1998 16:02:22 Graham.Williams\@cmis.csiro.au"; -$M{"arabtex"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"arabtex"}="13 May 1997 16:45:22 Graham.Williams\@cmis.csiro.au"; -$M{"armenian"}="3 Jul 1997 08:23:26 Graham.Williams\@cmis.csiro.au"; -$M{"arosgn"}="21 Oct 1996 10:32:18 Graham.Williams\@cmis.csiro.au"; -$M{"arrow"}="7 Nov 1996 19:31:04 Graham.Williams\@cmis.csiro.au"; -$M{"asaetr"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; -$M{"ascii"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"astro"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"at"}="12 Nov 1996 09:27:11 Graham.Williams\@cmis.csiro.au"; -$M{"auctex"}="19 Oct 1998 06:10:29 Graham.Williams\@cmis.csiro.au"; -$M{"aurora"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"authorindex"}="16 Feb 1998 17:29:41 Graham.Williams\@cmis.csiro.au"; -$M{"autotab"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"babel"}="12 Jan 1997 11:26:33 Graham.Williams\@cmis.csiro.au"; -$M{"backgammon"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"bakoma-fonts"}="13 Dec 1996 08:26:36 Graham.Williams\@cmis.csiro.au"; -$M{"bakoma"}="22 Jan 1999 07:17:26 Graham.Williams\@cmis.csiro.au"; -$M{"barcode2"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"barcodes"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"barcodes"}="7 Jun 1996 13:43:47 Graham.Williams\@cmis.csiro.au"; -$M{"barr"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"bayer"}="10 Feb 1998 09:30:02 Graham.Williams\@cmis.csiro.au"; -$M{"bbding"}="13 May 1996 06:15:45 Graham.Williams\@cmis.csiro.au"; -$M{"bbding"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"bbm"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"beebe"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"belleek"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"beton"}="28 May 1996 16:24:30 Graham.Williams\@cmis.csiro.au"; -$M{"bez123"}="21 Oct 1998 09:36:53 Graham.Williams\@cmis.csiro.au"; -$M{"bezos"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"bibarts"}="19 Apr 1998 15:55:19 Graham.Williams\@cmis.csiro.au"; -$M{"bibindex"}="12 Jan 1997 14:53:39 Graham.Williams\@cmis.csiro.au"; -$M{"biblio"}="4 Oct 1996 08:44:47 Graham.Williams\@cmis.csiro.au"; -$M{"biblios"}="16 Aug 1996 14:40:47 Graham.Williams\@cmis.csiro.au"; -$M{"biblist"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"biblook"}="12 Jan 1997 14:53:39 Graham.Williams\@cmis.csiro.au"; -$M{"bibsort"}="12 Nov 1996 10:28:11 Graham.Williams\@cmis.csiro.au"; -$M{"bibtex8bit"}="19 Aug 1996 22:05:26 Graham.Williams\@cmis.csiro.au"; -$M{"bibtool"}="24 Feb 1998 13:38:41 Graham.Williams\@cmis.csiro.au"; -$M{"bibunits"}="29 May 1997 12:15:06 Graham.Williams\@cmis.csiro.au"; -$M{"bibweb"}="28 Nov 1997 09:12:23 Graham.Williams\@cmis.csiro.au"; -$M{"bidstobibtex"}="21 Oct 1996 13:54:10 Graham.Williams\@cmis.csiro.au"; -$M{"bitstrea"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"blackboard"}="9 Jul 1998 05:37:01 Graham.Williams\@cmis.csiro.au"; -$M{"blue"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"bluesky"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"bm"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"booktabs"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"borceux"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"bosisio"}="1 May 1998 16:53:18 Graham.Williams\@cmis.csiro.au"; -$M{"boxedminipage"}="19 Apr 1998 15:20:55 Graham.Williams\@cmis.csiro.au"; -$M{"breqn"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"bridge"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"brief"}="30 May 1996 11:22:14 Graham.Williams\@cmis.csiro.au"; -$M{"brushscr"}="24 Jun 1998 12:56:02 Graham.Williams\@cmis.csiro.au"; -$M{"btparse"}="20 Feb 1998 14:21:13 Graham.Williams\@cmis.csiro.au"; -$M{"c-pascal"}="3 Mar 1998 15:29:06 Graham.Williams\@cmis.csiro.au"; -$M{"c2cweb"}="29 Nov 1996 15:27:19 Graham.Williams\@cmis.csiro.au"; -$M{"calc"}="12 Aug 1998 06:27:04 Graham.Williams\@cmis.csiro.au"; -$M{"calendar"}="18 Mar 1997 13:07:53 Graham.Williams\@cmis.csiro.au"; -$M{"calendar"}="4 Feb 1998 13:36:58 Graham.Williams\@cmis.csiro.au"; -$M{"calligra"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"calrsfs"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"calrsfs"}="12 Jun 1996 09:16:09 Graham.Williams\@cmis.csiro.au"; -$M{"camel"}="5 Mar 1997 16:31:57 Graham.Williams\@cmis.csiro.au"; -$M{"cancel"}="26 May 1997 12:53:21 Graham.Williams\@cmis.csiro.au"; -$M{"capt-of"}="15 Dec 1996 19:04:36 Graham.Williams\@cmis.csiro.au"; -$M{"caption"}="12 Nov 1996 20:23:42 Graham.Williams\@cmis.csiro.au"; -$M{"carlisle"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"cases"}="15 Dec 1996 19:14:30 Graham.Williams\@cmis.csiro.au"; -$M{"casyl"}="24 Feb 1999 09:19:05 Graham.Williams\@cmis.csiro.au"; -$M{"catalogue"}="22 May 1996 16:49:04 Graham.Williams\@cmis.csiro.au"; -$M{"catdoc"}="5 Nov 1998 11:47:57 Graham.Williams\@cmis.csiro.au"; -$M{"cbgreek"}="24 Oct 1998 07:42:16 Graham.Williams\@cmis.csiro.au"; -$M{"cc-pl"}="09 Jun 1998 staw\@gust.org.pl"; -$M{"ccaption"}="27 Jan 1999 09:40:41 Graham.Williams\@cmis.csiro.au"; -$M{"ccfonts"}="23 Jun 1998 15:52:05 Graham.Williams\@cmis.csiro.au"; -$M{"cchess"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"cd-cover"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"cdcover"}="10 Feb 1998 09:31:30 Graham.Williams\@cmis.csiro.au"; -$M{"cdlabeler"}="2 Jan 1999 21:57:44 Graham.Williams\@cmis.csiro.au"; -$M{"cellular"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"cep"}="27 Jan 1998 16:53:11 Graham.Williams\@cmis.csiro.au"; -$M{"cep"}="08 Feb 1998 staw\@gust.org.pl"; -$M{"changebar"}="7 Oct 1997 09:02:24 Graham.Williams\@cmis.csiro.au"; -$M{"chapterbib"}="15 Dec 1996 19:13:07 Graham.Williams\@cmis.csiro.au"; -$M{"chemcono"}="21 Oct 1996 14:28:23 Graham.Williams\@cmis.csiro.au"; -$M{"chemcono"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"chemsym"}="8 Jul 1998 08:11:58 Graham.Williams\@cmis.csiro.au"; -$M{"cheq"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"cherokee"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"chess"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"china2e"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; -$M{"china2e"}="26 Feb 1998 08:51:49 Graham.Williams\@cmis.csiro.au"; -$M{"chktex"}="21 Oct 1996 13:51:58 Graham.Williams\@cmis.csiro.au"; -$M{"circ"}="18 Mar 1998 09:29:16 Graham.Williams\@cmis.csiro.au"; -$M{"circle"}="13 Oct 1998 09:09:47 Graham.Williams\@cmis.csiro.au"; -$M{"circuit-macro"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"circuit-macros"}="6 Sep 1998 05:00:37 Graham.Williams\@cmis.csiro.au"; -$M{"cirth"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"cite"}="15 Dec 1996 19:10:42 Graham.Williams\@cmis.csiro.au"; -$M{"cjk-fonts"}="8 Jan 1999 08:02:11 Graham.Williams\@cmis.csiro.au"; -$M{"cjk"}="8 Jan 1999 08:01:13 Graham.Williams\@cmis.csiro.au"; -$M{"cm"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"cmactex"}="9 Aug 1998 06:47:00 Graham.Williams\@cmis.csiro.au"; -$M{"cmbright"}="28 Dec 1998 09:33:43 Graham.Williams\@cmis.csiro.au"; -$M{"cmcyr"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"cmcyralt"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"cmdtrack"}="22 Feb 1999 16:17:02 Graham.Williams\@cmis.csiro.au"; -$M{"cmextra"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"cmpica"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"cmps"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"cmsd"}="19 Feb 1998 09:45:20 Graham.Williams\@cmis.csiro.au"; -$M{"cmtt"}="1 Jun 1996 15:43:59 Graham.Williams\@cmis.csiro.au"; -$M{"cmyk-hax"}="12 May 1997 10:23:51 Graham.Williams\@cmis.csiro.au"; -$M{"cmyk-hax"}="08 Feb 1998 staw\@gust.org.pl"; -$M{"code128"}="7 Jun 1996 13:42:22 Graham.Williams\@cmis.csiro.au"; -$M{"codepage"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"color"}="24 Sep 1996 08:56:07 Graham.Williams\@cmis.csiro.au"; -$M{"colorsep"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"colortbl"}="24 Jun 1998 13:01:21 Graham.Williams\@cmis.csiro.au"; -$M{"comma"}="11 Feb 1998 07:46:23 Graham.Williams\@cmis.csiro.au"; -$M{"comment"}="8 Sep 1998 06:29:57 Graham.Williams\@cmis.csiro.au"; -$M{"compsci"}="21 Oct 1996 14:11:57 Graham.Williams\@cmis.csiro.au"; -$M{"concmath"}="25 Dec 1996 UV"; -$M{"concprog"}="22 Oct 1996 09:37:54 Graham.Williams\@cmis.csiro.au"; -$M{"concrete-wrap"}="27 Nov 1996 13:57:24 Graham.Williams\@cmis.csiro.au"; -$M{"concrete"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"consdiag"}="21 Jan 1999 19:26:28 Graham.Williams\@cmis.csiro.au"; -$M{"context"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"corelpak"}="21 Jan 1999 14:00:25 Graham.Williams\@cmis.csiro.au"; -$M{"count1to"}="24 Oct 1998 09:04:16 Graham.Williams\@cmis.csiro.au"; -$M{"covington"}="22 Apr 1997 14:32:07 Graham.Williams\@cmis.csiro.au"; -$M{"croatian"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"crop"}="8 Dec 1998 09:21:42 Graham.Williams\@cmis.csiro.au"; -$M{"crossword"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"crosswrd"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"csfonts"}="3 May 1997 s.rahtz\@elsevier.co.uk"; -$M{"cslatex"}="3 May 1997 s.rahtz\@elsevier.co.uk"; -$M{"csplain"}="3 May 1997 s.rahtz\@elsevier.co.uk"; -$M{"cspsfonts"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"cstug"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"csx"}="12 Jul 1998 05:30:19 Graham.Williams\@cmis.csiro.au"; -$M{"cursor"}="20 Jan 1999 14:56:10 Graham.Williams\@cmis.csiro.au"; -$M{"custom-bib"}="18 Aug 1998 18:00:42 Graham.Williams\@cmis.csiro.au"; -$M{"cwebbin"}="16 Oct 1998 06:27:49 Graham.Williams\@cmis.csiro.au"; -$M{"cwebx"}="17 Feb 1999 16:44:14 Graham.Williams\@cmis.csiro.au"; -$M{"cwpuzzle"}="28 Nov 1996 10:09:18 Graham.Williams\@cmis.csiro.au"; -$M{"cyrtug"}="8 Oct 1998 11:51:48 Graham.Williams\@cmis.csiro.au"; -$M{"dancers"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"dante-src"}="11 Feb 1998 07:50:55 Graham.Williams\@cmis.csiro.au"; -$M{"dates"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"dblfont"}="1 May 1998 16:53:44 Graham.Williams\@cmis.csiro.au"; -$M{"dbprocess"}="2 Jan 1999 21:55:59 Graham.Williams\@cmis.csiro.au"; -$M{"dc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"dc"}="2 Jun 1996 11:09:21 Graham.Williams\@cmis.csiro.au"; -$M{"dco"}="16 Aug 1996 14:14:54 Graham.Williams\@cmis.csiro.au"; -$M{"dcounter"}="28 Dec 1998 09:21:00 Graham.Williams\@cmis.csiro.au"; -$M{"default"}="18 Jul 1998 06:43:35 Graham.Williams\@cmis.csiro.au"; -$M{"deleq"}="8 Jul 1998 08:12:25 Graham.Williams\@cmis.csiro.au"; -$M{"devanagari"}="7 Dec 1998 05:46:30 Graham.Williams\@cmis.csiro.au"; -$M{"dialogl"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"dinbrief"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"dinbrief"}="4 Nov 1996 09:56:05 Graham.Williams\@cmis.csiro.au"; -$M{"directory"}="10 Mar 1998 05:30:54 Graham.Williams\@cmis.csiro.au"; -$M{"dn2"}="13 Mar 1998 09:10:15 Graham.Williams\@cmis.csiro.au"; -$M{"doc"}="19 Aug 1996 22:19:13 Graham.Williams\@cmis.csiro.au"; -$M{"dotseqn"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"doublestroke"}="21 Oct 1996 13:56:41 Graham.Williams\@cmis.csiro.au"; -$M{"draftcopy"}="21 May 1996 12:52:54 Graham.Williams\@cmis.csiro.au"; -$M{"dratex"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"dropcaps"}="19 Jun 1996 13:38:04 Graham.Williams\@cmis.csiro.au"; -$M{"dropping"}="9 Jul 1998 06:27:48 Graham.Williams\@cmis.csiro.au"; -$M{"duerer"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"dvgtk"}="29 Apr 1997 14:45:04 Graham.Williams\@cmis.csiro.au"; -$M{"dvi2tty"}="7 Jun 1996 20:12:43 Graham.Williams\@cmis.csiro.au"; -$M{"dviconcat"}="1 Nov 1996 08:10:15 Graham.Williams\@cmis.csiro.au"; -$M{"dvicopy"}="= {1 Nov 1996 08:30:05 Graham.Williams\@cmis.csiro.au"; -$M{"dviljk"}="6 Apr 1998 06:10:01 Graham.Williams\@cmis.csiro.au"; -$M{"dvipaste"}="23 Feb 1998 15:46:09 Graham.Williams\@cmis.csiro.au"; -$M{"dvipdfm"}="2 Dec 1998 05:56:54 Graham.Williams\@cmis.csiro.au"; -$M{"dvips-os2"}="21 Jan 1999 13:57:52 Graham.Williams\@cmis.csiro.au"; -$M{"dvips-shell"}="5 Mar 1998 22:29:41 Graham.Williams\@cmis.csiro.au"; -$M{"dvips"}="13 May 1997 09:51:53 Graham.Williams\@cmis.csiro.au"; -$M{"dvipsdoc"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"dvipsk"}="6 Apr 1998 05:56:12 Graham.Williams\@cmis.csiro.au"; -$M{"ean"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"ean"}="7 Jun 1996 13:44:26 Graham.Williams\@cmis.csiro.au"; -$M{"easy"}="18 Aug 1998 18:24:49 Graham.Williams\@cmis.csiro.au"; -$M{"easybib"}="7 Mar 1997 16:54:36 Graham.Williams\@cmis.csiro.au"; -$M{"easybmat"}="18 Aug 1998 18:27:38 Graham.Williams\@cmis.csiro.au"; -$M{"easyeqn"}="18 Nov 1997 15:21:55 Graham.Williams\@cmis.csiro.au"; -$M{"easymat"}="18 Aug 1998 18:28:31 Graham.Williams\@cmis.csiro.au"; -$M{"easytable"}="18 Aug 1998 18:28:50 Graham.Williams\@cmis.csiro.au"; -$M{"easyvector"}="18 Nov 1997 15:22:16 Graham.Williams\@cmis.csiro.au"; -$M{"ec-plain"}="21 Apr 1998 08:38:32 Graham.Williams\@cmis.csiro.au"; -$M{"ec"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"ecc"}="11 Dec 1998 08:59:53 Graham.Williams\@cmis.csiro.au"; -$M{"ecltree"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"eco"}="22 Jul 1998 09:13:53 Graham.Williams\@cmis.csiro.au"; -$M{"ecpk"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"edmac"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"eepic"}="28 Dec 1998 09:32:41 Graham.Williams\@cmis.csiro.au"; -$M{"egplot"}="9 Jul 1998 06:27:09 Graham.Williams\@cmis.csiro.au"; -$M{"eiad"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"eijkhout"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"elsevier"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"elvish"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"emp"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; -$M{"emp"}="26 Feb 1998 08:53:14 Graham.Williams\@cmis.csiro.au"; -$M{"emtex-os2"}="31 Jul 1998 10:16:40 Graham.Williams\@cmis.csiro.au"; -$M{"emtex"}="31 Jul 1998 10:16:40 Graham.Williams\@cmis.csiro.au"; -$M{"emtexgi"}="12 Jan 1997 11:32:36 Graham.Williams\@cmis.csiro.au"; -$M{"emtextds"}="30 Sep 1998 07:58:58 Graham.Williams\@cmis.csiro.au"; -$M{"emulateapj"}="27 Nov 1997 17:06:10 Graham.Williams\@cmis.csiro.au"; -$M{"encodings"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"endfloat"}="21 Jun 1996 14:52:55 Graham.Williams\@cmis.csiro.au"; -$M{"endnotes"}="3 Sep 1996 09:20:05 Graham.Williams\@cmis.csiro.au"; -$M{"endnotes"}="4 Feb 1998 13:33:16 Graham.Williams\@cmis.csiro.au"; -$M{"engwar"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"enumerate"}="22 Jul 1998 05:47:30 Graham.Williams\@cmis.csiro.au"; -$M{"envbig"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"envlab"}="17 Jul 1997 14:37:23 Graham.Williams\@cmis.csiro.au"; -$M{"epic"}="24 Jul 1998 06:18:39 Graham.Williams\@cmis.csiro.au"; -$M{"epigraph"}="1 Dec 1998 12:42:01 Graham.Williams\@cmis.csiro.au"; -$M{"eplain"}="19 Aug 1996 22:10:25 Graham.Williams\@cmis.csiro.au"; -$M{"epmtfe"}="23 Feb 1999 15:01:08 Graham.Williams\@cmis.csiro.au"; -$M{"epsfx"}="09 Jun 1998 staw\@gust.org.pl"; -$M{"epslatex"}="9 Feb 1998 09:22:51 Graham.Williams\@cmis.csiro.au"; -$M{"eqname"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"esieecv"}="26 Feb 1998 08:54:52 Graham.Williams\@cmis.csiro.au"; -$M{"esieecv"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; -$M{"esindex"}="10 Nov 1998 10:40:44 Graham.Williams\@cmis.csiro.au"; -$M{"eso-pic"}="22 Jul 1998 06:17:37 Graham.Williams\@cmis.csiro.au"; -$M{"et"}="24 Feb 1998 13:45:45 Graham.Williams\@cmis.csiro.au"; -$M{"etexbase"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"ethiop"}="13 Dec 1998 15:02:18 Graham.Williams\@cmis.csiro.au"; -$M{"euler"}="5 Jun 1996 10:03:48 Graham.Williams\@cmis.csiro.au"; -$M{"euro"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"eurofont"}="31 Jan 1999 07:41:02 Graham.Williams\@cmis.csiro.au"; -$M{"europs"}="21 Jan 1999 13:04:27 Graham.Williams\@cmis.csiro.au"; -$M{"eurosans"}="27 Jan 1999 08:25:26 Graham.Williams\@cmis.csiro.au"; -$M{"eurosym"}="6 Jan 1999 07:26:11 Graham.Williams\@cmis.csiro.au"; -$M{"everysel"}="10 Aug 1998 09:05:43 Graham.Williams\@cmis.csiro.au"; -$M{"everyshi"}="10 Aug 1998 09:20:24 Graham.Williams\@cmis.csiro.au"; -$M{"exam"}="16 Dec 1998 08:31:47 Graham.Williams\@cmis.csiro.au"; -$M{"examdesign"}="20 Jan 1998 22:03:03 Graham.Williams\@cmis.csiro.au"; -$M{"exams"}="29 May 1996 13:09:04 Graham.Williams\@cmis.csiro.au"; -$M{"excalibur"}="8 Nov 1998 07:01:25 Graham.Williams\@cmis.csiro.au"; -$M{"expdlist"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"expl3"}="1 Jun 1998 12:09:40 Graham.Williams\@cmis.csiro.au"; -$M{"export"}="12 Jan 1997 11:45:06 Graham.Williams\@cmis.csiro.au"; -$M{"export"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"exscale"}="12 Jun 1996 06:53:11 Graham.Williams\@cmis.csiro.au"; -$M{"extdash"}="28 Dec 1998 09:21:00 Graham.Williams\@cmis.csiro.au"; -$M{"fancybox"}="2 Mar 1998 09:20:57 Graham.Williams\@cmis.csiro.au"; -$M{"fancyhdr"}="9 Sep 1998 06:51:16 Graham.Williams\@cmis.csiro.au"; -$M{"fancyref"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"fancyvrb"}="1 Apr 1998 06:01:31 Graham.Williams\@cmis.csiro.au"; -$M{"faq"}="1 Jul 1998 10:31:39 Graham.Williams\@cmis.csiro.au"; -$M{"fax"}="13 Dec 1996 09:32:37 Graham.Williams\@cmis.csiro.au"; -$M{"fc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"fc"}="5 Mar 1998 22:19:31 Graham.Williams\@cmis.csiro.au"; -$M{"fepslatex"}="6 Nov 1998 05:54:05 Graham.Williams\@cmis.csiro.au"; -$M{"feynmf"}="30 May 1996 06:34:12 Graham.Williams\@cmis.csiro.au"; -$M{"fihyph"}=" from fihyph.tex to make the Finnish accented"; -$M{"fihyph"}="6 Nov 1998 06:34:36 Graham.Williams\@cmis.csiro.au"; -$M{"finbib"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"finplain"}="29 Jun 1998 10:04:25 Graham.Williams\@cmis.csiro.au"; -$M{"fix2col"}="19 Aug 1998 16:52:30 Graham.Williams\@cmis.csiro.au"; -$M{"fixfloat"}="23 May 1997 09:28:11 Graham.Williams\@cmis.csiro.au"; -$M{"flabels"}="21 Jul 1997 09:34:31 Graham.Williams\@cmis.csiro.au"; -$M{"flatex"}="24 Sep 1996 08:59:43 Graham.Williams\@cmis.csiro.au"; -$M{"flatten"}="18 Jun 1996 09:36:48 Graham.Williams\@cmis.csiro.au"; -$M{"float"}="25 May 1996 07:26:32 Graham.Williams\@cmis.csiro.au"; -$M{"floatflt"}="8 Jul 1998 08:16:33 Graham.Williams\@cmis.csiro.au"; -$M{"fltpage"}="19 Nov 1998 05:29:33 Graham.Williams\@cmis.csiro.au"; -$M{"fncychap"}=" Each can be using a set of simple commands."; -$M{"fncychap"}="13 Dec 1996 08:41:01 Graham.Williams\@cmis.csiro.au"; -$M{"fnpara"}="10 Sep 1996 09:23:00 Graham.Williams\@cmis.csiro.au"; -$M{"foilhtml"}="19 Feb 1998 09:39:43 Graham.Williams\@cmis.csiro.au"; -$M{"foiltex"}="15 Aug 1998 07:01:05 Graham.Williams\@cmis.csiro.au"; -$M{"fontinst"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"fontmisc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"fontname"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"fonts"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"footbib"}="19 Jun 1997 11:31:23 Graham.Williams\@cmis.csiro.au"; -$M{"footmisc"}="22 Jun 1998 16:47:47 Graham.Williams\@cmis.csiro.au"; -$M{"footnpag"}="10 Sep 1996 09:26:38 Graham.Williams\@cmis.csiro.au"; -$M{"formats"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"formlett"}="27 May 1997 09:39:35 Graham.Williams\@cmis.csiro.au"; -$M{"formula"}="18 Jun 1998 10:24:39 Graham.Williams\@cmis.csiro.au"; -$M{"fourtex"}="21 Nov 1998 05:32:50 Graham.Williams\@cmis.csiro.au"; -$M{"fp"}="4 Nov 1996 09:45:28 Graham.Williams\@cmis.csiro.au"; -$M{"freefonts"}="10 Sep 1998 18:50:47 Graham.Williams\@cmis.csiro.au"; -$M{"freetype"}="2 Jan 1999 22:37:14 Graham.Williams\@cmis.csiro.au"; -$M{"french"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"fribrief"}="20 Jan 1998 21:50:51 Graham.Williams\@cmis.csiro.au"; -$M{"ftetx"}="24 Feb 1998 13:52:42 Graham.Williams\@cmis.csiro.au"; -$M{"ftn"}="10 Sep 1996 09:43:47 Graham.Williams\@cmis.csiro.au"; -$M{"ftnright"}="19 Aug 1996 22:20:55 Graham.Williams\@cmis.csiro.au"; -$M{"fullblck"}="18 Nov 1998 09:21:36 Graham.Williams\@cmis.csiro.au"; -$M{"fullpict"}="18 Feb 1999 10:39:07 Graham.Williams\@cmis.csiro.au"; -$M{"fundus"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"funnelweb"}="25 Jun 1996 12:38:19 Graham.Williams\@cmis.csiro.au"; -$M{"futhark"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"g-brief"}="20 Feb 1998 14:17:49 Graham.Williams\@cmis.csiro.au"; -$M{"gb4e"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"genealogy"}="31 May 1996 14:10:08 Graham.Williams\@cmis.csiro.au"; -$M{"genmisc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"gentl-gr"}="29 Jan 1999 09:40:36 Graham.Williams\@cmis.csiro.au"; -$M{"geometry"}="8 Apr 1998 14:26:57 Graham.Williams\@cmis.csiro.au"; -$M{"geomsty"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; -$M{"geomsty"}="26 Feb 1998 08:58:15 Graham.Williams\@cmis.csiro.au"; -$M{"german"}="15 Jul 1998 07:33:39 Graham.Williams\@cmis.csiro.au"; -$M{"germbib"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"germdoc"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"getrefs"}="12 Nov 1998 20:22:10 Graham.Williams\@cmis.csiro.au"; -$M{"ghostscript"}="20 May 1997 14:12:34 Graham.Williams\@cmis.csiro.au"; -$M{"ghostview-mac"}="27 Mar 1998 05:51:48 Graham.Williams\@cmis.csiro.au"; -$M{"ghyphen"}="8 Jul 1998 08:55:23 Graham.Williams\@cmis.csiro.au"; -$M{"gleitobjekte"}="17 Feb 1998 09:09:23 Graham.Williams\@cmis.csiro.au"; -$M{"gloss"}="19 Apr 1998 15:58:24 Graham.Williams\@cmis.csiro.au"; -$M{"glosstex"}="25 Feb 1998 09:12:56 Graham.Williams\@cmis.csiro.au"; -$M{"gn-logic"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"gnhyph"}="16 Sep 1998 09:18:43 Graham.Williams\@cmis.csiro.au"; -$M{"gnuplot-ps"}="30 May 1996 11:22:14 Graham.Williams\@cmis.csiro.au"; -$M{"go"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"gothic"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"graphfig"}="1 May 1998 16:54:18 Graham.Williams\@cmis.csiro.au"; -$M{"graphics"}="1 Nov 1996 08:16:13 Graham.Williams\@cmis.csiro.au"; -$M{"graphicx"}="12 Jun 1996 06:47:22 Graham.Williams\@cmis.csiro.au"; -$M{"gray"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"grfguide"}="11 Jun 1997 16:17:05 Graham.Williams\@cmis.csiro.au"; -$M{"grfpaste"}="23 Feb 1998 15:39:11 Graham.Williams\@cmis.csiro.au"; -$M{"grnumalt"}="23 Feb 1998 15:49:56 Graham.Williams\@cmis.csiro.au"; -$M{"gsftopk"}="12 Nov 1996 09:08:05 Graham.Williams\@cmis.csiro.au"; -$M{"gustlib"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"gustlib"}="March 1998, s.rahtz\@elsevier.co.uk"; -$M{"hands"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"hanging"}="11 Dec 1998 05:38:02 Graham.Williams\@cmis.csiro.au"; -$M{"harpoon"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"harvmac"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"hellas"}="10 Mar 1998 06:00:34 Graham.Williams\@cmis.csiro.au"; -$M{"here"}="25 May 1996 07:24:51 Graham.Williams\@cmis.csiro.au"; -$M{"hh"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"hilowres"}="21 Jan 1999 19:31:07 Graham.Williams\@cmis.csiro.au"; -$M{"histogr"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"hlatex"}="28 May 1997 16:04:14 Graham.Williams\@cmis.csiro.au"; -$M{"hoekwater"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"html"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"html2latex"}="30 Sep 1998 07:55:02 Graham.Williams\@cmis.csiro.au"; -$M{"huhyph"}="5 Nov 1998 05:50:17 Graham.Williams\@cmis.csiro.au"; -$M{"hvdashln"}="13 May 1997 09:36:00 Graham.Williams\@cmis.csiro.au"; -$M{"hyper"}="30 Aug 1997 12:04:32 Graham.Williams\@cmis.csiro.au"; -$M{"hyperlatex"}="27 Dec 1998 20:25:24 Graham.Williams\@cmis.csiro.au"; -$M{"hyperref"}="17 Feb 1999 16:41:40 Graham.Williams\@cmis.csiro.au"; -$M{"hyphenat"}="22 Feb 1999 16:42:36 Graham.Williams\@cmis.csiro.au"; -$M{"hypht1"}="3 May 1997 20:57:53 Graham.Williams\@cmis.csiro.au"; -$M{"ibm"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"idealfonts"}="20 Feb 1998 14:34:54 Graham.Williams\@cmis.csiro.au"; -$M{"ifacmtg"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"imac"}="24 Sep 1998 05:27:35 Graham.Williams\@cmis.csiro.au"; -$M{"indxcite"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"indxcite"}="24 Jun 1996 15:17:51 Graham.Williams\@cmis.csiro.au"; -$M{"info"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"inhyph"}="7 Oct 1997 08:54:26 Graham.Williams\@cmis.csiro.au"; -$M{"inputenc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"insbox"}="25 Feb 1998 09:20:32 Graham.Williams\@cmis.csiro.au"; -$M{"ipa"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"isostds"}="21 Oct 1998 09:38:15 Graham.Williams\@cmis.csiro.au"; -$M{"ithyph"}="4 Aug 1998 05:39:19 Graham.Williams\@cmis.csiro.au"; -$M{"izhitsa"}="30 Jan 1999 06:34:27 Graham.Williams\@cmis.csiro.au"; -$M{"jadetex"}="3 May 1997 s.rahtz\@elsevier.co.uk"; -$M{"javatex"}="8 Oct 1998 12:03:35 Graham.Williams\@cmis.csiro.au"; -$M{"jknappen"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"jknappen"}="10 Mar 1998 09:10:20 Graham.Williams\@cmis.csiro.au"; -$M{"jsmisc"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"jspell"}="= {5 Nov 1998 15:43:30 Graham.Williams\@cmis.csiro.au"; -$M{"jura"}="11 Jul 1998 17:22:01 Graham.Williams\@cmis.csiro.au"; -$M{"kalendar"}="27 Mar 1998 05:44:58 Graham.Williams\@cmis.csiro.au"; -$M{"kalender"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"karnaugh"}="24 Sep 1998 05:26:10 Graham.Williams\@cmis.csiro.au"; -$M{"kdgreek"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; -$M{"kix"}="19 Sep 1998 08:58:56 Graham.Williams\@cmis.csiro.au"; -$M{"kluwer"}="31 May 1997 20:08:21 Graham.Williams\@cmis.csiro.au"; -$M{"knst"}="21 Oct 1996 13:44:44 Graham.Williams\@cmis.csiro.au"; -$M{"knuth"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"koi8"}="21 Oct 1996 13:48:21 Graham.Williams\@cmis.csiro.au"; -$M{"koma-script"}="30 Nov 1998 09:41:00 Graham.Williams\@cmis.csiro.au"; -$M{"kpathsea"}="3 Feb 1999 10:29:24 Graham.Williams\@cmis.csiro.au"; -$M{"kuvio"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"lamstex"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"lated"}="11 Feb 1998 07:41:10 Graham.Williams\@cmis.csiro.au"; -$M{"latex"}="2 Jul 1998 12:56:15 Graham.Williams\@cmis.csiro.au"; -$M{"latex209"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"latex209"}="4 Jul 1996 10:07:05 Graham.Williams\@cmis.csiro.au"; -$M{"latex2e"}="4 Jul 1996 09:53:38 Graham.Williams\@cmis.csiro.au"; -$M{"latex2html"}="8 Jul 1996 23:00:59 Graham.Williams\@cmis.csiro.au"; -$M{"latex2man"}="9 Sep 1998 05:33:13 Graham.Williams\@cmis.csiro.au"; -$M{"latex2rtf"}="17 Nov 1998 08:56:23 Graham.Williams\@cmis.csiro.au"; -$M{"latexcad"}="20 Mar 1998 09:32:43 Graham.Williams\@cmis.csiro.au"; -$M{"latexfonts"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"latexmk"}="12 Jan 1997 11:30:28 Graham.Williams\@cmis.csiro.au"; -$M{"latexn"}="27 Nov 1997 17:04:03 Graham.Williams\@cmis.csiro.au"; -$M{"latin2jk"}="7 Oct 1997 08:56:04 Graham.Williams\@cmis.csiro.au"; -$M{"layout"}="13 Aug 1998 05:42:38 Graham.Williams\@cmis.csiro.au"; -$M{"layouts"}="31 Jan 1999 06:43:57 Graham.Williams\@cmis.csiro.au"; -$M{"leaflet"}="30 Sep 1998 08:20:21 Graham.Williams\@cmis.csiro.au"; -$M{"leftidx"}="4 Feb 1998 13:16:00 Graham.Williams\@cmis.csiro.au"; -$M{"letter"}="6 Nov 1998 13:26:58 Graham.Williams\@cmis.csiro.au"; -$M{"lettrine"}="25 Mar 1998 09:11:24 Graham.Williams\@cmis.csiro.au"; -$M{"levy"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"lexikon"}="1 Apr 1998 06:05:45 Graham.Williams\@cmis.csiro.au"; -$M{"lgreek"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"lgrind-win32"}="24 Mar 1998 11:41:55 Graham.Williams\@cmis.csiro.au"; -$M{"lgrind"}="5 Aug 1998 06:33:28 Graham.Williams\@cmis.csiro.au"; -$M{"lh"}="2 Oct 1998 07:20:00 Graham.Williams\@cmis.csiro.au"; -$M{"lhcyr"}="21 Jan 1999 19:44:44 Graham.Williams\@cmis.csiro.au"; -$M{"lilypond"}="21 Oct 1998 09:41:28 Graham.Williams\@cmis.csiro.au"; -$M{"lineno"}="20 Jan 1999 14:57:13 Graham.Williams\@cmis.csiro.au"; -$M{"linguex"}="1 Jun 1998 11:57:34 Graham.Williams\@cmis.csiro.au"; -$M{"lintex"}="16 Jun 1998 10:19:01 Graham.Williams\@cmis.csiro.au"; -$M{"lips"}="21 Oct 1996 10:30:25 Graham.Williams\@cmis.csiro.au"; -$M{"listings"}="11 Nov 1998 05:44:14 Graham.Williams\@cmis.csiro.au"; -$M{"lkort"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"llncs"}="4 Oct 1996 08:48:06 Graham.Williams\@cmis.csiro.au"; -$M{"localloc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"logic"}="3 May 1997 s.rahtz\@elsevier.co.uk"; -$M{"logo-ps"}="25 Jul 1998 06:24:28 Graham.Williams\@cmis.csiro.au"; -$M{"lollipop"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"longtable"}="21 Jun 1996 08:12:11 Graham.Williams\@cmis.csiro.au"; -$M{"lscape"}="7 Nov 1996 19:36:31 Graham.Williams\@cmis.csiro.au"; -$M{"lshort-english"}="21 Jan 1999 19:27:28 Graham.Williams\@cmis.csiro.au"; -$M{"lshort-finnish"}="21 Jan 1999 19:12:55 Graham.Williams\@cmis.csiro.au"; -$M{"lshort-french"}="5 Feb 1998 09:10:02 Graham.Williams\@cmis.csiro.au"; -$M{"lshort-german"}="30 Jan 1999 07:28:37 Graham.Williams\@cmis.csiro.au"; -$M{"lshort-mongolian"}="30 Jan 1999 07:28:04 Graham.Williams\@cmis.csiro.au"; -$M{"lshort-polish"}="25 Feb 1999 14:09:31 Graham.Williams\@cmis.csiro.au"; -$M{"lshort-russian"}="13 Oct 1998 09:11:31 Graham.Williams\@cmis.csiro.au"; -$M{"lshort-spanish"}="21 Jan 1999 19:12:55 Graham.Williams\@cmis.csiro.au"; -$M{"ltoh"}="8 Apr 1998 09:41:19 Graham.Williams\@cmis.csiro.au"; -$M{"ltx2rtf"}="28 Dec 1998 09:11:53 Graham.Williams\@cmis.csiro.au"; -$M{"ltx2x"}="26 Jan 1997 10:24:09 Graham.Williams\@cmis.csiro.au"; -$M{"ltxbase"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"ltxinput"}="26 Nov 1996 16:30:38 Graham.Williams\@cmis.csiro.au"; -$M{"ltxmisc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"ltxsrc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"lucida"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"lucold"}="4 Feb 1998 13:23:16 Graham.Williams\@cmis.csiro.au"; -$M{"lw35nfsx"}="28 Jul 1998 05:36:21 Graham.Williams\@cmis.csiro.au"; -$M{"ly1"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"m-pictex"}="24 Feb 1998 13:55:54 Graham.Williams\@cmis.csiro.au"; -$M{"macbibtex"}="7 Nov 1996 13:35:35 Graham.Williams\@cmis.csiro.au"; -$M{"magaz"}="17 Feb 1999 17:33:54 Graham.Williams\@cmis.csiro.au"; -$M{"mailing"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"makeindex"}="23 May 1997 13:18:35 Graham.Williams\@cmis.csiro.au"; -$M{"malayalam"}="23 Jun 1998 15:49:27 Graham.Williams\@cmis.csiro.au"; -$M{"malvern"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"manyfoot"}="28 Dec 1998 09:24:33 Graham.Williams\@cmis.csiro.au"; -$M{"mapcodes"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"maple"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"margbib"}="24 Feb 1998 13:20:27 Graham.Williams\@cmis.csiro.au"; -$M{"marvosym-mac"}="5 Nov 1998 15:47:46 Graham.Williams\@cmis.csiro.au"; -$M{"marvosym"}="21 Jul 1998 05:27:14 Graham.Williams\@cmis.csiro.auy"; -$M{"mathcmd"}="abstract Provides a slightly version of the commands for"; -$M{"mathcmd"}="1 May 1998 16:54:49 Graham.Williams\@cmis.csiro.au"; -$M{"mathcomp"}="10 Sep 1998 18:44:41 Graham.Williams\@cmis.csiro.au"; -$M{"mathematica"}="20 Jan 1998 22:00:24 Graham.Williams\@cmis.csiro.au"; -$M{"mathenv"}="1 May 1998 16:55:25 Graham.Williams\@cmis.csiro.au"; -$M{"mathinst"}="10 Sep 1998 18:54:03 Graham.Williams\@cmis.csiro.au"; -$M{"mathkit"}="4 Feb 1998 13:20:21 Graham.Williams\@cmis.csiro.au"; -$M{"mathpple"}="21 Jan 1999 19:34:23 Graham.Williams\@cmis.csiro.au"; -$M{"mathrsfs"}="27 Mar 1998 05:58:42 Graham.Williams\@cmis.csiro.au"; -$M{"mathtime"}="29 May 1996 10:39:52 Graham.Williams\@cmis.csiro.au"; -$M{"mcite"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"mdwtools"}="16 Jun 1998 10:36:35 Graham.Williams\@cmis.csiro.au"; -$M{"meta-mode"}="1 May 1997 10:10:22 Graham.Williams\@cmis.csiro.au"; -$M{"metapost"}="25 Jun 1996 10:58:40 Graham.Williams\@cmis.csiro.au"; -$M{"method"}="21 Jan 1999 07:58:21 Graham.Williams\@cmis.csiro.au"; -$M{"mex"}="08 Feb 1998 staw\@gust.org.pl"; -$M{"mf-ps"}="4 Feb 1998 13:18:00 Graham.Williams\@cmis.csiro.au"; -$M{"mf-ps"}="08 Feb 1998 staw\@gust.org.pl"; -$M{"mf2pt3"}="2 Jan 1999 21:45:21 Graham.Williams\@cmis.csiro.au"; -$M{"mf2tex"}="3 May 1997 21:09:52 Graham.Williams\@cmis.csiro.au"; -$M{"mff"}="24 Oct 1996 10:27:31 Graham.Williams\@cmis.csiro.au"; -$M{"mff"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"mflogo"}="25 Dec 1996 UV"; -$M{"mfnfss"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"mfpic"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"mftoeps"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; -$M{"mhs"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"midnight"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"mif2xfig"}="20 Nov 1996 11:23:52 Graham.Williams\@cmis.csiro.au"; -$M{"miktex-axp"}="25 Sep 1997 14:01:19 Graham.Williams\@cmis.csiro.au"; -$M{"miktex"}="23 Feb 1999 16:12:25 Graham.Williams\@cmis.csiro.au"; -$M{"miniltx"}="20 May 1996 10:13:07 Graham.Williams\@cmis.csiro.au"; -$M{"minitoc"}="12 Jan 1997 11:20:36 Graham.Williams\@cmis.csiro.au"; -$M{"mirr"}="12 May 1997 10:27:47 Graham.Williams\@cmis.csiro.au"; -$M{"mirr"}="08 Feb 1998 staw\@gust.org.pl"; -$M{"miscpk"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"mitpress"}="19 Sep 1998 10:11:07 Graham.Williams\@cmis.csiro.au"; -$M{"mkpic"}="2 Jan 1999 21:52:06 Graham.Williams\@cmis.csiro.au"; -$M{"mla"}="28 Apr 1997 09:48:03 Graham.Williams\@cmis.csiro.au"; -$M{"mlbib"}="5 Nov 1996 09:15:29 Graham.Williams\@cmis.csiro.au"; -$M{"mltex"}="28 Dec 1998 09:15:09 Graham.Williams\@cmis.csiro.au"; -$M{"mmtools"}="23 Jul 1997 09:16:45 Graham.Williams\@cmis.csiro.au"; -$M{"mnras"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"modes"}="11 Aug 1998 05:29:08 Graham.Williams\@cmis.csiro.au"; -$M{"monotype"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"monster"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"montex"}="29 Jan 1999 09:53:15 Graham.Williams\@cmis.csiro.au"; -$M{"morehelp"}="19 Feb 1998 09:36:53 Graham.Williams\@cmis.csiro.au"; -$M{"moresize"}="17 Jul 1997 14:08:56 Graham.Williams\@cmis.csiro.au"; -$M{"moreverb"}="29 May 1996 11:58:07 Graham.Williams\@cmis.csiro.au"; -$M{"moreverb"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"morse"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; -$M{"morse"}="26 Feb 1998 09:08:33 Graham.Williams\@cmis.csiro.au"; -$M{"mpattern"}="30 Sep 1998 11:00:52 Graham.Williams\@cmis.csiro.au"; -$M{"mpfnmark"}="13 Dec 1996 08:30:22 Graham.Williams\@cmis.csiro.au"; -$M{"mpfnmark"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"ms"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"mslapa"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"mslapa"}="12 Jul 1996 10:06:59 Graham.Williams\@cmis.csiro.au"; -$M{"mt11p"}="14 Feb 1997 09:21:04 Graham.Williams\@cmis.csiro.au"; -$M{"mtbe"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"multenum"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; -$M{"multicol"}="21 Dec 1998 13:35:30 Graham.Williams\@cmis.csiro.au"; -$M{"multido"}="19 Mar 1998 10:41:51 Graham.Williams\@cmis.csiro.au"; -$M{"multirow"}="25 Nov 1998 06:06:17 Graham.Williams\@cmis.csiro.au"; -$M{"multitoc"}="8 Sep 1998 05:46:30 Graham.Williams\@cmis.csiro.au"; -$M{"musictex"}="27 Nov 1996 13:59:30 Graham.Williams\@cmis.csiro.au"; -$M{"musixtex"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"mxedruli"}="25 Jul 1998 06:28:00 Graham.Williams\@cmis.csiro.au"; -$M{"mylatex"}="1 May 1998 17:00:39 Graham.Williams\@cmis.csiro.au"; -$M{"myletter"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"nassflow"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"natbib"}="17 Jul 1998 16:12:29 Graham.Williams\@cmis.csiro.au"; -$M{"nb4latex"}="21 Nov 1996 16:56:44 Graham.Williams\@cmis.csiro.au"; -$M{"nccfoots"}="28 Dec 1998 09:25:59 Graham.Williams\@cmis.csiro.au"; -$M{"ncctools"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"netpbm-win"}="10 Sep 1998 18:37:04 Graham.Williams\@cmis.csiro.au"; -$M{"newsletr"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"newthm"}="abstract A version of the theorem-style which provides"; -$M{"newthm"}="14 Feb 1997 09:30:36 Graham.Williams\@cmis.csiro.au"; -$M{"newthm"}="13 May 1997 10:24:58 Robin Fairbairns "; -$M{"niceframe"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"nomencl"}="27 May 1997 09:24:37 Graham.Williams\@cmis.csiro.au"; -$M{"norbib"}="2 Jul 1998 12:55:09 Graham.Williams\@cmis.csiro.au"; -$M{"nrc"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"ntemacs"}="19 Oct 1998 06:03:28 Graham.Williams\@cmis.csiro.au"; -$M{"ntgclass"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"ntheorem"}="11 Dec 1998 05:44:07 Graham.Williams\@cmis.csiro.au"; -$M{"numline"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"numline"}="28 May 1996 16:02:33 Graham.Williams\@cmis.csiro.au"; -$M{"objectz"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"oca"}="3 May 1997 s.rahtz\@elsevier.co.uk"; -$M{"ocr-a"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"ocr-a"}="18 May 1996 14:10:28 Graham.Williams\@cmis.csiro.au"; -$M{"ocr-b"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"ocr-b"}="18 May 1996 14:10:28 Graham.Williams\@cmis.csiro.au"; -$M{"ogham"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"ogonek"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"oldstyle"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"omega"}="11 Feb 1998 08:05:12 Graham.Williams\@cmis.csiro.au"; -$M{"omegabase"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"omegafonts"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"onepagem"}="18 Jul 1997 14:23:48 Graham.Williams\@cmis.csiro.au"; -$M{"oryia"}="1 Jul 1998 10:29:59 Graham.Williams\@cmis.csiro.au"; -$M{"os2tex"}="3 Jan 1999 10:42:23 Graham.Williams\@cmis.csiro.au"; -$M{"osmanian"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"ot2cyr"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"overcite"}="15 Dec 1996 19:11:52 Graham.Williams\@cmis.csiro.au"; -$M{"overpic"}="27 Nov 1997 17:00:55 Graham.Williams\@cmis.csiro.au"; -$M{"overword"}="13 Dec 1996 08:37:08 Graham.Williams\@cmis.csiro.au"; -$M{"overword"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"oxford"}="11 Jan 1998 20:39:42 Graham.Williams\@cmis.csiro.au"; -$M{"oztex-german"}="25 Mar 1998 09:10:39 Graham.Williams\@cmis.csiro.au"; -$M{"oztex"}="27 Dec 1998 20:16:46 Graham.Williams\@cmis.csiro.au"; -$M{"pageno"}="23 Sep 1998 09:40:33 Graham.Williams\@cmis.csiro.au"; -$M{"pandey"}="30 Sep 1998 07:56:09 Graham.Williams\@cmis.csiro.au"; -$M{"pandora"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"paper"}="20 May 1996 06:33:20 Graham.Williams\@cmis.csiro.au"; -$M{"paradissa"}="14 Jun 1996 16:18:31 Graham.Williams\@cmis.csiro.au"; -$M{"paralist"}="21 Jan 1999 19:49:45 Graham.Williams\@cmis.csiro.au"; -$M{"patch"}="3 May 1997 s.rahtz\@elsevier.co.uk"; -$M{"path"}="25 Jun 1996 09:13:30 Graham.Williams\@cmis.csiro.au"; -$M{"pawpict"}="10 Feb 1998 09:32:45 Graham.Williams\@cmis.csiro.au"; -$M{"pb-diagram"}="30 Nov 1998 13:48:18 Graham.Williams\@cmis.csiro.au"; -$M{"pcfonts"}="21 Oct 1996 13:32:14 Graham.Williams\@cmis.csiro.au"; -$M{"pdcmac"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"pdftex-djgpp"}="23 Feb 1998 15:51:42 Graham.Williams\@cmis.csiro.au"; -$M{"pdftex"}="13 Aug 1998 05:51:13 Graham.Williams\@cmis.csiro.au"; -$M{"permute"}="28 Dec 1998 09:09:59 Graham.Williams\@cmis.csiro.au"; -$M{"pf2afm"}="18 Jun 1998 10:13:25 Graham.Williams\@cmis.csiro.au"; -$M{"phonetic"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"phppcf"}="14 Jun 1996 12:35:55 Graham.Williams\@cmis.csiro.au"; -$M{"physe"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"phyzzx"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"pictex"}="24 Feb 1998 13:53:44 Graham.Williams\@cmis.csiro.au"; -$M{"piff"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"piq"}="ctan fonts/okuda//"; -$M{"piq"}="17 Nov 1996 11:28:28 Graham.Williams\@cmis.csiro.au"; -$M{"pkfind"}=" utility to understand those specials, and to act"; -$M{"pkfind"}="3 Mar 1998 15:39:16 Graham.Williams\@cmis.csiro.au"; -$M{"pl-mf"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"pl-mf"}="08 Feb 1998 staw\@gust.org.pl"; -$M{"pl-qx"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"pl"}="25 Feb 1998, s.rahtz\@elsevier.co.uk"; -$M{"plainmisc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"plaintex"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"plari"}="6 Nov 1998 06:24:51 Graham.Williams\@cmis.csiro.au"; -$M{"platex"}="18 Jun 1998 10:22:09 Graham.Williams\@cmis.csiro.au"; -$M{"plcalendar"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"plfonts"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"plgraph"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"plpsfont"}="08 Feb 1998 staw\@gust.org.pl"; -$M{"pmcstex"}="27 Nov 1997 17:12:37 Graham.Williams\@cmis.csiro.au"; -$M{"pmgraph"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"poligraf"}="17 Nov 1996 11:34:19 Graham.Williams\@cmis.csiro.au"; -$M{"poligraf"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"poligraf"}="08 Feb 1998 staw\@gust.org.pl"; -$M{"polish"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"polyglot"}="12 Sep 1997 10:32:34 Graham.Williams\@cmis.csiro.au"; -$M{"ppchtex"}="15 Jan 1997 09:54:55 Graham.Williams\@cmis.csiro.au"; -$M{"prelim2e"}="10 Aug 1998 09:16:01 Graham.Williams\@cmis.csiro.au"; -$M{"prettyref"}="29 Jul 1998 05:41:53 Graham.Williams\@cmis.csiro.au"; -$M{"progkeys"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"program"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"proofs"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"prv"}="11 Dec 1998 05:33:29 Graham.Williams\@cmis.csiro.au"; -$M{"ps_conv"}="17 Nov 1996 11:34:19 Graham.Williams\@cmis.csiro.au"; -$M{"ps_view"}="25 Jun 1998 staw\@gust.org.pl"; -$M{"psfig"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"psfixbb"}="23 Jun 1998 15:54:54 Graham.Williams\@cmis.csiro.au"; -$M{"psfont"}="1 Jul 1996 21:00:54 Graham.Williams\@cmis.csiro.au"; -$M{"psfonts"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"psfrag"}="24 Jun 1998 12:56:59 Graham.Williams\@cmis.csiro.au"; -$M{"psizzl"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"pslatex"}="2 Aug 1996 12:28:03 Graham.Williams\@cmis.csiro.au"; -$M{"pslatex"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"psmerge"}="1 Nov 1996 08:12:01 Graham.Williams\@cmis.csiro.au"; -$M{"psnfss"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"psnfss"}="24 Apr 1997 16:16:14 Graham.Williams\@cmis.csiro.au"; -$M{"psnfssx"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"pspicture"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"pstotext"}="31 Oct 1996 13:39:09 Graham.Williams\@cmis.csiro.au"; -$M{"pstricks"}="30 May 1996 11:20:11 Graham.Williams\@cmis.csiro.au"; -$M{"punk"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"qfig"}="24 Jul 1998 06:25:39 Graham.Williams\@cmis.csiro.au"; -$M{"qfonts"}="18 Jun 1998 10:17:31 Graham.Williams\@cmis.csiro.au"; -$M{"qobitree"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"qsymbols"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"quotchap"}="24 Feb 1998 13:20:08 Graham.Williams\@cmis.csiro.au"; -$M{"quotes"}="1 May 1998 16:55:48 Graham.Williams\@cmis.csiro.au"; -$M{"r-und-s"}="3 Jul 1997 08:10:21 Graham.Williams\@cmis.csiro.au"; -$M{"ragged2e"}="10 Aug 1998 09:09:43 Graham.Williams\@cmis.csiro.au"; -$M{"rail"}="1 Oct 1998 07:36:00 Graham.Williams\@cmis.csiro.au"; -$M{"rangecite"}="28 May 1996 16:31:55 Graham.Williams\@cmis.csiro.au"; -$M{"rawfonts"}="6 Jun 1997 11:32:53 Graham.Williams\@cmis.csiro.au"; -$M{"rawprint"}="21 Oct 1996 13:50:40 Graham.Williams\@cmis.csiro.au"; -$M{"rcsinfo"}="25 Feb 1999 11:36:47 Graham.Williams\@cmis.csiro.au"; -$M{"realcalc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"recipe"}="26 Nov 1996 16:28:13 Graham.Williams\@cmis.csiro.au"; -$M{"refcheck"}="12 May 1997 10:18:04 Graham.Williams\@cmis.csiro.au"; -$M{"refman"}="1 Jun 1998 12:05:47 Graham.Williams\@cmis.csiro.au"; -$M{"relenc"}="23 Feb 1999 16:14:26 Graham.Williams\@cmis.csiro.au"; -$M{"remreset"}="7 Oct 1997 08:58:13 Graham.Williams\@cmis.csiro.au"; -$M{"repeat"}="5 Jan 1999 08:27:22 Graham.Williams\@cmis.csiro.au"; -$M{"revnum"}="3 Mar 1998 15:31:13 Graham.Williams\@cmis.csiro.au"; -$M{"revtex"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"revtex"}="31 Oct 1996 13:44:58 Graham.Williams\@cmis.csiro.au"; -$M{"rlepsf"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"rmpage"}="5 Feb 1998 14:07:37 Graham.Williams\@cmis.csiro.au"; -$M{"romaniantex"}="15 Nov 1996 14:57:19 Graham.Williams\@cmis.csiro.au"; -$M{"romanneg"}="19 Apr 1998 15:22:21 Graham.Williams\@cmis.csiro.au"; -$M{"rotating"}="12 Jun 1996 06:45:47 Graham.Williams\@cmis.csiro.au"; -$M{"rplain"}="23 Sep 1998 09:45:08 Graham.Williams\@cmis.csiro.au"; -$M{"rsfs-ps"}="25 Apr 1998 06:14:30 Graham.Williams\@cmis.csiro.au"; -$M{"rsfs"}="12 Jun 1996 06:57:19 Graham.Williams\@cmis.csiro.au"; -$M{"ruhyphen"}="8 Oct 1998 11:53:41 Graham.Williams\@cmis.csiro.au"; -$M{"ruler"}="22 May 1996 16:04:57 Graham.Williams\@cmis.csiro.au"; -$M{"s2latex"}="7 Jun 1996 20:13:54 Graham.Williams\@cmis.csiro.au"; -$M{"saferef"}="4 Feb 1997 09:57:44 Graham.Williams\@cmis.csiro.au"; -$M{"sanskrit"}="19 Mar 1997 12:03:33 Graham.Williams\@cmis.csiro.au"; -$M{"sauter"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"sauterfonts"}="12 Nov 1998 20:16:14 Graham.Williams\@cmis.csiro.au"; -$M{"scale"}="6 Nov 1998 06:19:58 Graham.Williams\@cmis.csiro.au"; -$M{"scalefnt"}="7 Oct 1997 08:58:13 Graham.Williams\@cmis.csiro.au"; -$M{"schedule"}="18 Feb 1998 10:30:16 Graham.Williams\@cmis.csiro.au"; -$M{"script"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"section"}="1 May 1998 17:01:43 Graham.Williams\@cmis.csiro.au"; -$M{"sectsty"}="13 Dec 1998 05:29:30 Graham.Williams\@cmis.csiro.au"; -$M{"semantic"}="13 May 1996 06:13:26 Graham.Williams\@cmis.csiro.au"; -$M{"seminar"}="28 May 1996 16:32:44 Graham.Williams\@cmis.csiro.au"; -$M{"setspace"}="27 Nov 1998 09:26:04 Graham.Williams\@cmis.csiro.au"; -$M{"sfg"}="8 Jul 1998 09:15:14 Graham.Williams\@cmis.csiro.au"; -$M{"sfheaders"}="17 Feb 1998 09:11:27 Graham.Williams\@cmis.csiro.au"; -$M{"shadbox"}="5 Aug 1996 12:14:57 Graham.Williams\@cmis.csiro.au"; -$M{"shadbox"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"shadethm"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"shading"}="24 Sep 1996 08:55:09 Graham.Williams\@cmis.csiro.au"; -$M{"shadow"}="21 Oct 1996 10:39:52 Graham.Williams\@cmis.csiro.au"; -$M{"shalom"}="30 May 1996 11:22:14 Graham.Williams\@cmis.csiro.au"; -$M{"shapepar"}="3 Jul 1996 15:23:38 Graham.Williams\@cmis.csiro.au"; -$M{"shhyphl"}="7 Jan 1999 07:27:53 Graham.Williams\@cmis.csiro.au"; -$M{"shortlst"}="29 Nov 1998 18:20:51 Graham.Williams\@cmis.csiro.au"; -$M{"shorttoc"}="22 Jul 1998 06:07:50 Graham.Williams\@cmis.csiro.au"; -$M{"showdim"}="30 Jul 1998 05:30:48 Graham.Williams\@cmis.csiro.au"; -$M{"showlabels"}="23 Feb 1999 13:56:22 Graham.Williams\@cmis.csiro.au"; -$M{"siam"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"sidecap"}="6 Nov 1998 06:07:25 Graham.Williams\@cmis.csiro.au"; -$M{"siggraph"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"simpsons"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; -$M{"sinhala"}="31 Oct 1996 09:54:37 Graham.Williams\@cmis.csiro.au"; -$M{"sirlin"}="16 Aug 1996 14:13:00 Graham.Williams\@cmis.csiro.au"; -$M{"siunits"}="23 Jan 1999 05:00:33 Graham.Williams\@cmis.csiro.au"; -$M{"slashbox"}="20 Feb 1998 14:26:38 Graham.Williams\@cmis.csiro.au"; -$M{"slashed"}="11 Feb 1998 07:48:41 Graham.Williams\@cmis.csiro.au"; -$M{"slidenotes"}="16 Dec 1998 08:33:45 Graham.Williams\@cmis.csiro.au"; -$M{"slides"}="17 Jun 1997 20:12:00 Graham.Williams\@cmis.csiro.au"; -$M{"smallcap"}="28 May 1996 15:57:18 Graham.Williams\@cmis.csiro.au"; -$M{"smallcap"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"smartmn"}="5 Nov 1996 09:14:21 Graham.Williams\@cmis.csiro.au"; -$M{"sobolev"}="1 May 1998 16:56:12 Graham.Williams\@cmis.csiro.au"; -$M{"somedefs"}="12 Aug 1998 06:35:40 Graham.Williams\@cmis.csiro.au"; -$M{"songbook"}="30 Jun 1998 10:54:02 Graham.Williams\@cmis.csiro.au"; -$M{"sorhyph"}="12 May 1997 10:30:15 Graham.Williams\@cmis.csiro.au"; -$M{"soul"}="21 Jan 1999 19:15:44 Graham.Williams\@cmis.csiro.au"; -$M{"spanish"}="21 May 1996 13:04:45 Graham.Williams\@cmis.csiro.au"; -$M{"spanishb"}="5 Oct 1998 11:43:25 Graham.Williams\@cmis.csiro.au"; -$M{"sphack"}="28 May 1998 16:16:55 Graham.Williams\@cmis.csiro.au"; -$M{"sprite"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"ssqquote"}="25 Dec 1996 UV"; -$M{"startex"}="21 Oct 1996 14:23:19 Graham.Williams\@cmis.csiro.au"; -$M{"startex"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"stdclsdv"}="21 Jan 1999 12:51:23 Graham.Williams\@cmis.csiro.au"; -$M{"stmaryrd-ps"}="25 Jul 1998 06:01:40 Graham.Williams\@cmis.csiro.au"; -$M{"stmaryrd"}="25 Apr 1998 06:19:27 Graham.Williams\@cmis.csiro.au"; -$M{"subeqn"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"supertabular"}="7 Oct 1997 09:01:35 Graham.Williams\@cmis.csiro.au"; -$M{"swift"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"syngen"}="19 Nov 1996 08:42:42 Graham.Williams\@cmis.csiro.au"; -$M{"synttree"}="12 Aug 1998 06:13:18 Graham.Williams\@cmis.csiro.au"; -$M{"t2"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"tabbing"}="10 Feb 1998 12:54:11 Graham.Williams\@cmis.csiro.au"; -$M{"tabls"}="15 Dec 1996 19:17:27 Graham.Williams\@cmis.csiro.au"; -$M{"tap"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"tap"}="08 Feb 1998 staw\@gust.org.pl"; -$M{"taylor"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"tbe"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"tcvn"}="21 Jan 1999 19:18:03 Graham.Williams\@cmis.csiro.au"; -$M{"tcx"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"tds"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; -$M{"techexplorer"}="19 Aug 1998 07:13:20 Graham.Williams\@cmis.csiro.au"; -$M{"tengwar"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"tensind"}="18 Jun 1998 10:06:41 Graham.Williams\@cmis.csiro.au"; -$M{"tensor"}="7 Jun 1996 08:52:37 Graham.Williams\@cmis.csiro.au"; -$M{"termcal"}="14 Jan 1997 10:10:12 Graham.Williams\@cmis.csiro.au"; -$M{"tetex"}="11 Jun 1997 19:22:32 Graham.Williams\@cmis.csiro.au"; -$M{"tex-math"}="8 Jul 1996 14:14:25 Graham.Williams\@cmis.csiro.au"; -$M{"tex-ps"}="09 Jun 1998 staw\@gust.org.pl"; -$M{"tex2bib"}="27 Jan 1998 16:50:26 Graham.Williams\@cmis.csiro.au"; -$M{"tex2html"}="29 Jan 1998 09:10:30 Graham.Williams\@cmis.csiro.au"; -$M{"tex2ltx"}="28 Oct 1998 11:56:39 Graham.Williams\@cmis.csiro.au"; -$M{"tex2rtf"}="25 Jun 1996 08:56:43 Graham.Williams\@cmis.csiro.au"; -$M{"tex4ht"}="23 Oct 1998 05:35:34 Graham.Williams\@cmis.csiro.au"; -$M{"tex98"}="12 Aug 1998 06:09:09 Graham.Williams\@cmis.csiro.au"; -$M{"texdraw"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"texed"}="11 Nov 1998 05:47:04 Graham.Williams\@cmis.csiro.au"; -$M{"texi2html"}="3 Feb 1999 10:27:21 Graham.Williams\@cmis.csiro.au"; -$M{"texi2www"}="2 Jul 1996 10:33:31 Graham.Williams\@cmis.csiro.au"; -$M{"texinfo"}="3 Feb 1999 10:28:52 Graham.Williams\@cmis.csiro.au"; -$M{"texip"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"texlist"}="31 Jan 1999 07:36:23 Graham.Williams\@cmis.csiro.au"; -$M{"texperf"}="16 Aug 1996 14:08:55 Graham.Williams\@cmis.csiro.au"; -$M{"texshell32"}="28 Mar 1998 07:07:28 Graham.Williams\@cmis.csiro.au"; -$M{"texsis"}="27 Jan 1998 16:44:10 Graham.Williams\@cmis.csiro.au"; -$M{"texsk"}="7 Mar 1997 16:53:45 Graham.Williams\@cmis.csiro.au"; -$M{"text1"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"textcase"}="11 Feb 1998 07:49:12 Graham.Williams\@cmis.csiro.au"; -$M{"textfit"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"textmerg"}="31 May 1996 08:43:05 Graham.Williams\@cmis.csiro.au"; -$M{"textoolspro"}=" LaTeX- code, so you can write sections in a"; -$M{"textoolspro"}="21 Jan 1999 13:03:19 Graham.Williams\@cmis.csiro.au"; -$M{"textpos"}="23 Feb 1999 13:54:56 Graham.Williams\@cmis.csiro.au"; -$M{"tfmpk"}="16 Dec 1998 08:30:00 Graham.Williams\@cmis.csiro.au"; -$M{"thesis"}="20 May 1996 10:22:19 Graham.Williams\@cmis.csiro.au"; -$M{"threed"}="13 Apr 1998 06:37:38 Graham.Williams\@cmis.csiro.au"; -$M{"threeparttable"}="15 Dec 1996 19:16:24 Graham.Williams\@cmis.csiro.au"; -$M{"thumb"}="10 Feb 1998 09:34:21 Graham.Williams\@cmis.csiro.au"; -$M{"thumbpdf"}="17 Feb 1999 16:50:56 Graham.Williams\@cmis.csiro.au"; -$M{"tiff"}="11 Nov 1998 05:43:39 Graham.Williams\@cmis.csiro.au"; -$M{"tiff2ps"}="06 May 1998 staw\@gust.org.pl"; -$M{"time"}="7 Jun 1996 09:04:45 Graham.Williams\@cmis.csiro.au"; -$M{"times"}="28 May 1997 16:25:37 Graham.Williams\@cmis.csiro.au"; -$M{"timesht"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"timing"}="3 May 1997 s.rahtz\@elsevier.co.uk"; -$M{"tipa"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"titlefoot"}="18 Mar 1998 09:30:36 Graham.Williams\@cmis.csiro.au"; -$M{"titleref"}="15 Dec 1996 19:19:50 Graham.Williams\@cmis.csiro.au"; -$M{"titlesec"}="23 Feb 1999 14:58:36 Graham.Williams\@cmis.csiro.au"; -$M{"titletoc"}="23 Feb 1999 14:58:46 Graham.Williams\@cmis.csiro.au"; -$M{"tkbibtex"}="10 Aug 1998 06:27:23 Graham.Williams\@cmis.csiro.au"; -$M{"tmview"}="29 Jun 1998 10:00:32 Graham.Williams\@cmis.csiro.au"; -$M{"tocbibind"}="21 Jan 1999 12:54:08 Graham.Williams\@cmis.csiro.au"; -$M{"tocloft"}="21 Jan 1999 12:57:14 Graham.Williams\@cmis.csiro.au"; -$M{"tocvsec2"}="21 Jan 1999 12:52:58 Graham.Williams\@cmis.csiro.au"; -$M{"toil"}="27 Jan 1998 16:54:47 Graham.Williams\@cmis.csiro.au"; -$M{"toil"}="08 Feb 1998 staw\@gust.org.pl"; -$M{"tools"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"topcapt"}="15 Dec 1996 19:04:36 Graham.Williams\@cmis.csiro.au"; -$M{"tracking"}="5 Aug 1996 12:11:48 Graham.Williams\@cmis.csiro.au"; -$M{"tracking"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"trans"}="17 Nov 1996 11:34:19 Graham.Williams\@cmis.csiro.au"; -$M{"trans"}="08 Feb 1998 staw\@gust.org.pl"; -$M{"transfig"}="8 Jul 1998 09:08:50 Graham.Williams\@cmis.csiro.au"; -$M{"treesvr"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"truncate"}="15 Dec 1996 19:23:52 Graham.Williams\@cmis.csiro.au"; -$M{"tsconfig"}="27 Nov 1996 13:48:24 Graham.Williams\@cmis.csiro.au"; -$M{"ttf2mf"}="25 Nov 1998 05:37:46 Graham.Williams\@cmis.csiro.au"; -$M{"ttf2pk"}="2 Jan 1999 22:03:00 Graham.Williams\@cmis.csiro.au"; -$M{"ttf2tfm"}="2 Jan 1999 22:05:48 Graham.Williams\@cmis.csiro.au"; -$M{"ttftogf"}="19 Sep 1998 08:12:18 Graham.Williams\@cmis.csiro.au"; -$M{"tth-rpm"}="13 Feb 1999 08:51:59 Graham.Williams\@cmis.csiro.au"; -$M{"tth-win"}="10 Sep 1998 18:39:22 Graham.Williams\@cmis.csiro.au"; -$M{"tth"}="27 Mar 1998 12:45:38 Graham.Williams\@cmis.csiro.au"; -$M{"ttt"}="19 Mar 1997 08:34:45 Graham.Williams\@cmis.csiro.au"; -$M{"tubtoc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"tugboat-toc"}="28 Dec 1998 09:28:11 Graham.Williams\@cmis.csiro.au"; -$M{"tugboat"}="3 May 1997 s.rahtz\@elsevier.co.uk"; -$M{"tugboat"}="3 Jul 1997 08:01:03 Graham.Williams\@cmis.csiro.au"; -$M{"twg-list"}="25 Feb 1998 09:33:34 Graham.Williams\@cmis.csiro.au"; -$M{"twoup"}="19 Mar 1998 10:39:40 Graham.Williams\@cmis.csiro.au"; -$M{"type1"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"type1"}="February 1998, s.rahtz\@elsevier.co.uk"; -$M{"type1cm"}="7 Mar 1997 16:50:06 Graham.Williams\@cmis.csiro.au"; -$M{"type1cm"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"typearea"}="12 Jun 1996 13:18:22 Graham.Williams\@cmis.csiro.au"; -$M{"typehtml"}="27 Nov 1997 17:08:38 Graham.Williams\@cmis.csiro.au"; -$M{"typespec"}="2 Jul 1998 13:03:32 Graham.Williams\@cmis.csiro.au"; -$M{"uaclasses"}="19 Mar 1997 12:05:52 Graham.Williams\@cmis.csiro.au"; -$M{"uaclasses"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"ucthesis"}="abstract A version of the standard \LaTeX{} report style"; -$M{"ukhyph"}="21 Oct 1996 10:37:20 Graham.Williams\@cmis.csiro.au"; -$M{"ulem"}="28 May 1996 16:34:03 Graham.Williams\@cmis.csiro.au"; -$M{"ulsy"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"umlaute"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"umrand"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"underlin"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; -$M{"underscore"}="17 Jul 1998 07:34:04 Graham.Williams\@cmis.csiro.au"; -$M{"uniqleaf"}="2 Aug 1996 12:44:23 Graham.Williams\@cmis.csiro.au"; -$M{"units"}="6 Aug 1998 06:17:29 Graham.Williams\@cmis.csiro.au"; -$M{"universa"}="6 Sep 1998 05:46:31 Graham.Williams\@cmis.csiro.au"; -$M{"url"}="3 Jul 1996 15:23:38 Graham.Williams\@cmis.csiro.au"; -$M{"urw"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"urwstd"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"urwvf"}="5 Feb 1998 09:33:04 Graham.Williams\@cmis.csiro.au"; -$M{"ut-backref"}="10 Nov 1998 10:38:10 Graham.Williams\@cmis.csiro.au"; -$M{"ut-thesis"}="23 Feb 1999 15:02:00 Graham.Williams\@cmis.csiro.au"; -$M{"utorontothesis"}="20 Feb 1998 14:27:24 Graham.Williams\@cmis.csiro.au"; -$M{"utthesis"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"uwthesis"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"vdm"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"vector"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"verbatim"}="29 May 1996 11:58:52 Graham.Williams\@cmis.csiro.au"; -$M{"vertex"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"vfcomb"}="24 Oct 1996 10:25:22 Graham.Williams\@cmis.csiro.au"; -$M{"vfinst"}="10 Sep 1998 18:41:42 Graham.Williams\@cmis.csiro.au"; -$M{"viiptart"}="8 Jul 1998 09:20:53 Graham.Williams\@cmis.csiro.au"; -$M{"vmargin"}="12 Jun 1996 13:14:31 Graham.Williams\@cmis.csiro.au"; -$M{"vncmr"}="19 Jul 1996 08:45:39 Graham.Williams\@cmis.csiro.au"; -$M{"vrb"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"vrsion"}="8 Jul 1998 08:17:05 Graham.Williams\@cmis.csiro.au"; -$M{"vruler"}="24 Oct 1996 11:15:39 Graham.Williams\@cmis.csiro.au"; -$M{"warpcol"}="13 Sep 1998 06:27:36 Graham.Williams\@cmis.csiro.au"; -$M{"wasy-ps"}="25 Jul 1998 06:05:00 Graham.Williams\@cmis.csiro.au"; -$M{"wasy"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"wasy2-ps"}="5 Aug 1998 06:26:09 Graham.Williams\@cmis.csiro.au"; -$M{"wasy2"}="25 Jul 1998 06:18:23 Graham.Williams\@cmis.csiro.au"; -$M{"wasysym"}="5 Jan 1999 07:44:43 Graham.Williams\@cmis.csiro.au"; -$M{"web2c-win32"}="3 Apr 1998 06:38:58 Graham.Williams\@cmis.csiro.au"; -$M{"web2c"}="20 Mar 1998 09:27:08 Graham.Williams\@cmis.csiro.au"; -$M{"williams"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"win95-guide"}="12 Apr 1998 20:46:26 Graham.Williams\@cmis.csiro.au"; -$M{"windvi"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"winedt"}="2 Jul 1998 13:00:44 Graham.Williams\@cmis.csiro.au"; -$M{"winemtex"}="3 Aug 1998 18:15:29 Graham.Williams\@cmis.csiro.au"; -$M{"winshell"}="21 Nov 1998 05:34:40 Graham.Williams\@cmis.csiro.au"; -$M{"wmf2eps"}="12 Nov 1998 20:15:28 Graham.Williams\@cmis.csiro.au"; -$M{"wnri"}="30 Jun 1998 10:56:34 Graham.Williams\@cmis.csiro.au"; -$M{"wntamil"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"word2x"}="29 Apr 1997 14:47:38 Graham.Williams\@cmis.csiro.au"; -$M{"wp-conv"}="1 Aug 1998 05:39:06 Graham.Williams\@cmis.csiro.au"; -$M{"wp2latex"}="23 Sep 1998 05:24:28 Graham.Williams\@cmis.csiro.au"; -$M{"wsuipa"}="13 Aug 1998 05:27:18 Graham.Williams\@cmis.csiro.au"; -$M{"wtex95"}="24 Feb 1998 14:01:24 Graham.Williams\@cmis.csiro.au"; -$M{"xdvi"}="28 Jun 1996 10:08:55 Graham.Williams\@cmis.csiro.au"; -$M{"xdvik"}="6 Apr 1998 05:53:45 Graham.Williams\@cmis.csiro.au"; -$M{"xfig"}="8 Jul 1998 09:08:50 Graham.Williams\@cmis.csiro.au"; -$M{"xtab"}="21 Oct 1998 09:32:30 Graham.Williams\@cmis.csiro.au"; -$M{"xtcapts"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"xtem"}="27 Nov 1997 17:13:37 Graham.Williams\@cmis.csiro.au"; -$M{"xymtex"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"xypic"}="21 Nov 1998 05:35:39 Graham.Williams\@cmis.csiro.au"; -$M{"yannisgr"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; -$M{"yfonts"}="27 Jan 1999 08:26:02 Graham.Williams\@cmis.csiro.au"; -$M{"yhmath"}="16 May 1996 s.rahtz\@elsevier.co.uk"; -$M{"yi4latex"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; -$M{"youngtab"}="29 Jun 1998 10:06:42 Graham.Williams\@cmis.csiro.au"; -$M{"yplan99"}="11 Dec 1998 05:45:33 Graham.Williams\@cmis.csiro.au"; -$M{"ytex"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; -$M{"zefonts"}="30 Sep 1998 07:50:57 Graham.Williams\@cmis.csiro.au"; -1; diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/nocites.tex b/Master/texmf-doc/source/texlive/texlive-en/archive/nocites.tex deleted file mode 100644 index 759b379f30e..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/nocites.tex +++ /dev/null @@ -1,557 +0,0 @@ -\nocite{a0poster} -\nocite{aaai} -\nocite{abstyles} -\nocite{accfonts} -\nocite{achemso} -\nocite{acronym} -\nocite{adfathesis} -\nocite{adobeother} -\nocite{adobestd} -\nocite{adrlist} -\nocite{ae} -\nocite{aguplus} -\nocite{aiaa} -\nocite{akletter} -\nocite{alatex} -\nocite{algorithms} -\nocite{alg} -\nocite{alphaev5-osf4.0d} -\nocite{altfont} -\nocite{amsfonts} -\nocite{amslatex} -\nocite{amstex} -\nocite{answers} -\nocite{antyktor} -\nocite{apa} -\nocite{apl} -\nocite{appendix} -\nocite{arabtex} -\nocite{arydshln} -\nocite{ar} -\nocite{asaetr} -\nocite{ascii} -\nocite{astro} -\nocite{aurora} -\nocite{authorindex} -\nocite{autotab} -\nocite{babel} -\nocite{backgammon} -\nocite{bakoma} -\nocite{barcode2} -\nocite{barcodes} -\nocite{barr} -\nocite{bbding} -\nocite{bbm} -\nocite{bbold} -\nocite{bbtbase} -\nocite{bbtdoc} -\nocite{beebe} -\nocite{belleek} -\nocite{beton} -\nocite{bez123} -\nocite{bezos} -\nocite{bibarts} -\nocite{biblist} -\nocite{bluesky} -\nocite{blue} -\nocite{booktabs} -\nocite{borceux} -\nocite{bosisio} -\nocite{bridge} -\nocite{brushscr} -\nocite{c-pascal} -\nocite{calendar} -\nocite{calligra} -\nocite{calrsfs} -\nocite{camel} -\nocite{caption} -\nocite{carlisle} -\nocite{casyl} -\nocite{catalog} -\nocite{cbgreek} -\nocite{cc-pl} -\nocite{ccaption} -\nocite{ccfonts} -\nocite{cchess} -\nocite{cdcover} -\nocite{cellular} -\nocite{changebar} -\nocite{chemcono} -\nocite{chemsym} -\nocite{cheq} -\nocite{cherokee} -\nocite{chess} -\nocite{china2e} -\nocite{circ} -\nocite{cirth} -\nocite{cite} -\nocite{cjk} -\nocite{cmbright} -\nocite{cmcyralt} -\nocite{cmcyr} -\nocite{cmdtrack} -\nocite{cmextra} -\nocite{cmpica} -\nocite{cmpk} -\nocite{cmsd} -\nocite{cm} -\nocite{codepage} -\nocite{colorsep} -\nocite{colortab} -\nocite{comment} -\nocite{concmath} -\nocite{concrete} -\nocite{context} -\nocite{covington} -\nocite{croatian} -\nocite{crop} -\nocite{crossword} -\nocite{crosswrd} -\nocite{csfonts} -\nocite{cslatex} -\nocite{csplain} -\nocite{cspsfonts} -\nocite{cstug} -\nocite{cursor} -\nocite{curves} -\nocite{custom-bib} -\nocite{cyrillic} -\nocite{dancers} -\nocite{deleq} -\nocite{devanagari} -\nocite{dialogl} -\nocite{dinbrief} -\nocite{directory} -\nocite{dotseqn} -\nocite{draftcopy} -\nocite{dratex} -\nocite{dropping} -\nocite{dstroke} -\nocite{dtk} -\nocite{duerer} -\nocite{dvipdfm} -\nocite{dvipsbase} -\nocite{dvipsdoc} -\nocite{ean} -\nocite{easy} -\nocite{ecc} -\nocite{ecltree} -\nocite{eco} -\nocite{ecpk} -\nocite{ec} -\nocite{edmac} -\nocite{eepic} -\nocite{egplot} -\nocite{eiad} -\nocite{eijkhout} -\nocite{elsevier} -\nocite{elvish} -\nocite{emp} -\nocite{emulateapj} -\nocite{encodings} -\nocite{endfloat} -\nocite{engwar} -\nocite{envbig} -\nocite{envlab} -\nocite{epigraph} -\nocite{eplain} -\nocite{eqname} -\nocite{eqnarray} -\nocite{esieecv} -\nocite{etexbase} -\nocite{etruscan} -\nocite{euler} -\nocite{euro2} -\nocite{eurofont} -\nocite{europs} -\nocite{eurosans} -\nocite{eurosym} -\nocite{euro} -\nocite{euxm} -\nocite{examdesign} -\nocite{exam} -\nocite{expdlist} -\nocite{expl3} -\nocite{export} -\nocite{fancybox} -\nocite{fancyhdr} -\nocite{fancyref} -\nocite{fancyvrb} -\nocite{fax} -\nocite{fc} -\nocite{feynmf} -\nocite{finbib} -\nocite{floatfig} -\nocite{floatflt} -\nocite{float} -\nocite{fltpage} -\nocite{fncychap} -\nocite{foilhtml} -\nocite{foiltex} -\nocite{fontinst} -\nocite{fontname} -\nocite{footbib} -\nocite{footmisc} -\nocite{footnpag} -\nocite{formats} -\nocite{formula} -\nocite{fp} -\nocite{frankenstein} -\nocite{french} -\nocite{fribrief} -\nocite{fullblck} -\nocite{fullpict} -\nocite{fundus} -\nocite{futhark} -\nocite{g-brief} -\nocite{gb4e} -\nocite{genealogy} -\nocite{general} -\nocite{genmisc} -\nocite{geometry} -\nocite{geomsty} -\nocite{german} -\nocite{germbib} -\nocite{germdoc} -\nocite{gloss} -\nocite{gn-logic} -\nocite{gothic} -\nocite{go} -\nocite{graphics} -\nocite{greek6cbc} -\nocite{grnumalt} -\nocite{grtimes} -\nocite{guides} -\nocite{gustlib} -\nocite{hands} -\nocite{hanging} -\nocite{harpoon} -\nocite{harvard} -\nocite{harvmac} -\nocite{hh} -\nocite{hilowres} -\nocite{histogr} -\nocite{hoekwater} -\nocite{hppa1.1-hpux10.10} -\nocite{html} -\nocite{hvmaths} -\nocite{hyperref} -\nocite{hyper} -\nocite{hyphenat} -\nocite{hyphen} -\nocite{i386-linux-libc5} -\nocite{i386-linux} -\nocite{ibm} -\nocite{ieeepes} -\nocite{ifacmtg} -\nocite{imac} -\nocite{indxcite} -\nocite{info} -\nocite{ini} -\nocite{insbox} -\nocite{ipa} -\nocite{isostds} -\nocite{jadetex} -\nocite{jhep} -\nocite{jknappen} -\nocite{jsmisc} -\nocite{jura} -\nocite{kalender} -\nocite{karnaugh} -\nocite{kdgreek} -\nocite{kluwer} -\nocite{knuth} -\nocite{koma-script} -\nocite{kuvio} -\nocite{labels} -\nocite{lamstex} -\nocite{lastpage} -\nocite{latexfonts} -\nocite{layouts} -\nocite{leaflet} -\nocite{leftidx} -\nocite{lettrine} -\nocite{levy} -\nocite{lgc} -\nocite{lgreek} -\nocite{lhcyr} -\nocite{lh} -\nocite{lineno} -\nocite{linguex} -\nocite{listings} -\nocite{lkort} -\nocite{localloc} -\nocite{logic} -\nocite{lollipop} -\nocite{ltablex} -\nocite{ltx2rtf} -\nocite{ltxbase} -\nocite{ltxdoc} -\nocite{ltxmisc} -\nocite{lucida} -\nocite{ly1} -\nocite{mailing} -\nocite{makeindex} -\nocite{malayalam} -\nocite{malvern} -\nocite{mapcodes} -\nocite{maple} -\nocite{margbib} -\nocite{marvosym} -\nocite{mathcomp} -\nocite{mathematica} -\nocite{mathpple} -\nocite{mcite} -\nocite{mdwtools} -\nocite{metasupp} -\nocite{method} -\nocite{mex} -\nocite{mff} -\nocite{mflogo} -\nocite{mfmisc} -\nocite{mfnfss} -\nocite{mfpic} -\nocite{mftoeps} -\nocite{mft} -\nocite{mhs} -\nocite{midnight} -\nocite{minitoc} -\nocite{mips-irix6.2} -\nocite{misc209} -\nocite{mltex} -\nocite{mnras} -\nocite{monotype} -\nocite{montex} -\nocite{morehelp} -\nocite{moresize} -\nocite{moreverb} -\nocite{morse} -\nocite{mpattern} -\nocite{mpbase} -\nocite{mpfnmark} -\nocite{mslapa} -\nocite{ms} -\nocite{mtbe} -\nocite{multenum} -\nocite{multirow} -\nocite{multi} -\nocite{musictex} -\nocite{musixtex} -\nocite{nassflow} -\nocite{natbib} -\nocite{ncctools} -\nocite{newalg} -\nocite{newlfm} -\nocite{newsletr} -\nocite{newthm} -\nocite{niceframe} -\nocite{nomencl} -\nocite{nrc} -\nocite{ntgclass} -\nocite{ntg} -\nocite{ntheorem} -\nocite{numline} -\nocite{objectz} -\nocite{oca} -\nocite{ocr-a} -\nocite{ogham} -\nocite{ogonek} -\nocite{oldstyle} -\nocite{omegabase} -\nocite{omegafonts} -\nocite{osmanian} -\nocite{ot2cyr} -\nocite{overpic} -\nocite{pacioli} -\nocite{pageno} -\nocite{pandora} -\nocite{paper} -\nocite{paralist} -\nocite{parallel} -\nocite{patch} -\nocite{pawpict} -\nocite{pb-diagram} -\nocite{pdcmac} -\nocite{pdfscreen} -\nocite{pdftex} -\nocite{permute} -\nocite{phoenician} -\nocite{phonetic} -\nocite{physe} -\nocite{phyzzx} -\nocite{picinpar} -\nocite{picins} -\nocite{pictex} -\nocite{piff} -\nocite{pl-qx} -\nocite{plainmisc} -\nocite{plaintex} -\nocite{plari} -\nocite{platex} -\nocite{play} -\nocite{plcalendar} -\nocite{plfonts} -\nocite{plgraph} -\nocite{plpatch} -\nocite{pl} -\nocite{pmgraph} -\nocite{poligraf} -\nocite{polish} -\nocite{polyglot} -\nocite{prettyref} -\nocite{progkeys} -\nocite{program} -\nocite{proofs} -\nocite{protex} -\nocite{psafm} -\nocite{psfig} -\nocite{psfrag} -\nocite{psizzl} -\nocite{pslatex} -\nocite{psnfssx} -\nocite{psnfss} -\nocite{pspicture} -\nocite{pstricks} -\nocite{punk} -\nocite{qfonts} -\nocite{qobitree} -\nocite{qsymbols} -\nocite{quotchap} -\nocite{r-und-s} -\nocite{rcsinfo} -\nocite{rcs} -\nocite{realcalc} -\nocite{refcheck} -\nocite{refman} -\nocite{relenc} -\nocite{revtex} -\nocite{rlepsf} -\nocite{rmpage} -\nocite{rotating} -\nocite{rotfloat} -\nocite{rplain} -\nocite{rs6000-aix4.1.4.0} -\nocite{rsfs} -\nocite{ruhyphen} -\nocite{runic} -\nocite{sanskrit} -\nocite{sauterfonts} -\nocite{scale} -\nocite{schedule} -\nocite{script} -\nocite{sectsty} -\nocite{semantic} -\nocite{seminar} -\nocite{setspace} -\nocite{shadbox} -\nocite{shadethm} -\nocite{shortlst} -\nocite{shorttoc} -\nocite{showdim} -\nocite{showlabels} -\nocite{siam} -\nocite{sidecap} -\nocite{siggraph} -\nocite{simpsons} -\nocite{siunits} -\nocite{slashbox} -\nocite{slidenotes} -\nocite{smallcap} -\nocite{songbook} -\nocite{soul} -\nocite{sparc-solaris2.5.1} -\nocite{sprite} -\nocite{ssqquote} -\nocite{startex} -\nocite{stdclsdv} -\nocite{stmaryrd} -\nocite{subeqnarray} -\nocite{subeqn} -\nocite{subfigure} -\nocite{supertabular} -\nocite{synttree} -\nocite{t2} -\nocite{tabbing} -\nocite{tap} -\nocite{taylor} -\nocite{tbe} -\nocite{tcx} -\nocite{tds} -\nocite{tengwar} -\nocite{tetex} -\nocite{tex-ps} -\nocite{tex4ht} -\nocite{texdraw} -\nocite{texinfo} -\nocite{texip} -\nocite{texlive} -\nocite{texsis} -\nocite{text1} -\nocite{textfit} -\nocite{textmerg} -\nocite{textpos} -\nocite{thesis} -\nocite{threed} -\nocite{thumbpdf} -\nocite{thumb} -\nocite{timesht} -\nocite{timing} -\nocite{tipa} -\nocite{titlefoot} -\nocite{titlesec} -\nocite{tmmaths} -\nocite{tocbibind} -\nocite{tocloft} -\nocite{tocvsec2} -\nocite{tools} -\nocite{tracking} -\nocite{treesvr} -\nocite{treetex} -\nocite{ttf2pk} -\nocite{tugboat} -\nocite{tug} -\nocite{type1cm} -\nocite{type1} -\nocite{typespec} -\nocite{uaclasses} -\nocite{ucthesis} -\nocite{ulsy} -\nocite{umlaute} -\nocite{umrand} -\nocite{underlin} -\nocite{units} -\nocite{universa} -\nocite{uni} -\nocite{unsupported} -\nocite{urwstd} -\nocite{useful} -\nocite{ut-thesis} -\nocite{utthesis} -\nocite{uwthesis} -\nocite{vdm} -\nocite{vector} -\nocite{vertex} -\nocite{vita} -\nocite{vrb} -\nocite{vrsion} -\nocite{warpcol} -\nocite{wasysym} -\nocite{wasy} -\nocite{williams} -\nocite{win32} -\nocite{windvi} -\nocite{wnri} -\nocite{wntamil} -\nocite{wsuipa} -\nocite{xtab} -\nocite{xtcapts} -\nocite{xymtex} -\nocite{xypic} -\nocite{yannisgr} -\nocite{yfonts} -\nocite{yhmath} -\nocite{yi4latex} -\nocite{youngtab} -\nocite{ytex} -\nocite{zed-csp} -\nocite{zefonts} diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/picture.tex b/Master/texmf-doc/source/texlive/texlive-en/archive/picture.tex deleted file mode 100644 index 098cfe18f10..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/picture.tex +++ /dev/null @@ -1,46 +0,0 @@ -\documentclass{artikel3} -\pagestyle{empty} -\usepackage{pstcol,pst-text,lucidbrb} -\font\manual=manfnt %logo10 doesn't have what we need -\hyphenchar\manual=-1 -\def\MF{{\manual META}\-{\manual FONT}} -\begin{document} -\sffamily -\psset{unit=1mm} -\def\Size#1#2{\fontsize{#1}{#2}\selectfont} -\begin{pspicture}(-58,-58)(58,58) -\pscircle[linewidth=.3pt,linecolor=lightgray]{58} -%\pscircle{23} -\psset{linestyle=none} -% top of circle -\pstextpath[c]{\psarcn(0,0){48}{180}{0}} -{\Size{1.2cm}{1cm}\bfseries \TeX\ Live 4} -\rput(0,34){\begin{minipage}{8cm}\centering \textbf{March 1999}\\[3mm] -\Size{9}{10.5}Ready-to-run \TeX\ system for Linux, Unix (DEC,\\ HP, IBM, -SGI, Sun), and Win32 systems, \\ -based on Web2c 7.3\\ -\end{minipage}} -% bottom of circle -\rput(30,10){\begin{minipage}{2.7cm}\raggedleft\footnotesize -ISO 9660 with Joliet \\and Rock Ridge \\ -extensions\end{minipage}} -\rput(0,-30){\begin{minipage}{7cm}\centering -Macros, fonts, documentation to the\\ -\emph{{\TeX} Directory Structure} standard.\\[2mm] -Editor: Sebastian Rahtz -\end{minipage}} -\pstextpath[c]{\psarc(0,0){45}{180}{0}} -{ -{\Size{14}{14}\ttfamily http://www.tug.org/texlive/} } -\pstextpath[c]{\psarc(0,0){53}{180}{0}} -{\Size{13.2}{14}\bfseries -CSTUG $\bullet$ -Dante e.V. $\bullet$ -GUST $\bullet$ -GUTenberg $\bullet$ -NTG $\bullet$ -TUG $\bullet$ -TUG India $\bullet$ -UK TUG} -\end{pspicture} -\end{document} diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/split.pl b/Master/texmf-doc/source/texlive/texlive-en/archive/split.pl deleted file mode 100644 index bca00584335..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/split.pl +++ /dev/null @@ -1,16 +0,0 @@ -#@TeXIndex{a0poster, -open TMP, ">/dev/null"; -while (<>) { - chop; - if (/\@TeXIndex/) { - print TMP "\n"; - close TMP; - $keep=$_; - s/\@TeXIndex{(.*),.*/$1/; - print "[$_]\n"; - open TMP, ">$_.bib"; - print TMP "$keep\n"; - } - else { print TMP "$_\n" ; } - -} diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/status.pl b/Master/texmf-doc/source/texlive/texlive-en/archive/status.pl deleted file mode 100644 index 28c3d0d6d4c..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/status.pl +++ /dev/null @@ -1,31 +0,0 @@ -#package: pIq -#license: pd -#(but erasing the headers is not allowed) -#Note that I made the most recent change, but -#Mark Shoulson (shoulson@ctr.columbia.edu) -#wrote the initial version. He should be named -#in the catalogue, too. - -#csuov@csv.warwick.ac.uk -#Subject: cmtt -#To: krab@iesd.auc.dk -#Subject: ftn -#To: inas@MIB.HARZ.DE -#Subject: newthm -#To: reckdahl@leland.stanford.edu -#Subject: epslatex -#To: miktex-bug@ronin.in-berlin.de -#Subject: miktex -#To: de8827@blackjack.usma.edu -#Subject: lated -#To: jdyoung@AFIT.AF.MIL -#Subject: afthesis -#xlwy01@uxp1.hrz.uni-dortmund.de (c2cweb) - -$L{"newlfm"}="free-latex"; -$L{"pacioli"}="gpl"; -$L{"etruscan"}="gpl"; -$L{"phoenician"}="gpl"; -$L{"greek6bc"}="gpl"; -$L{"runic"}="gpl"; -1; diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.bib b/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.bib deleted file mode 100644 index 17c75e197b7..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.bib +++ /dev/null @@ -1,235 +0,0 @@ -@TeXIndex{mips-irix6.2, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {System binaries for SGI running Irix 6.2}, - status = {free}, - texlive = {systems1} -} - -@TeXIndex{alpha-osf3.2, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {System binaries for Alpha running OSF 3.2.}, - status = {free}, - texlive = {systems1} -} - -@TeXIndex{alphaev5-osf4.0d, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {System binaries for Alphaev5 running OSF 4.0d.}, - status = {free}, - texlive = {systems1} -} - -@TeXIndex{alphaev5-osf4.0b, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {System binaries for Alphaev5 running OSF 4.0b.}, - status = {free}, - texlive = {systems1} -} - -@TeXIndex{bbtbase, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {Basic \BibTeX{} support files.}, - status = {free}, - texlive = {bibtex1} -} - -@TeXIndex{bbtdoc, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {Basic \BibTeX{} documentation.}, - status = {free}, - texlive = {bibtex2} -} - -@TeXIndex{catalog, - modified = {February 1999, s.rahtz@elsevier.co.uk}, - abstract = {Graham Williams' Catalogue of \TeX{} packages.}, - status = {free}, - texlive = {doc2} -} - -@TeXIndex{cmpk, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {Computer Modern fonts in PK format.}, - status = {free}, - texlive = {fonts3} -} - -@TeXIndex{dtk, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {Macros for the DANTE publication.}, - status = {free}, - texlive = {latex3} -} - -@TeXIndex{dvipsbase, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {Basic support files for dvips.}, - status = {free}, - texlive = {dvips1} -} - -@TeXIndex{general, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {Useful general documentation.}, - status = {free}, - texlive = {doc1} -} - -@TeXIndex{guides, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {Guides to using \LaTeX, in English, German, French, - Greek and Polish.}, - status = {free}, - texlive = {doc2} -} - -@TeXIndex{hppa1.1-hpux10.10, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {System binaries for HP running hpux10.10.}, - status = {free}, - texlive = {systems1} -} - -@TeXIndex{hyphen, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {Collection of hyphenation patterns.}, - email = {s.rahtz@elsevier.co.uk}, - author = {LaTeX3 Project}, - status = {free}, - texlive = {lang1} -} - -@TeXIndex{i386-linux, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {System binaries for Intel machines running Linux.}, - status = {free}, - texlive = {systems1} -} - -@TeXIndex{i386-linux-libc5, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {System binaries for Intel machines - running Linux, with libc5}, - status = {free}, - texlive = {systems1} -} - -@TeXIndex{ini, - modified = {February 1999, s.rahtz@elsevier.co.uk}, - abstract = {Startup files for building formats.}, - status = {free}, - texlive = {texlive1} -} - -@TeXIndex{lgc, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {Examples from the \emph{\LaTeX{} Graphics Companion}.}, - status = {free}, - texlive = {doc3} -} - -@TeXIndex{metasupp, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {MetaPost support files.}, - status = {free}, - texlive = {texlive1} -} - -@TeXIndex{mfmisc, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {Small support files for \MF.}, - status = {free}, - texlive = {fonts1} -} - -@TeXIndex{mft, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {Support files for MFT.}, - status = {free}, - texlive = {texlive1} -} - -@TeXIndex{misc209, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {Miscellaneous small macro files for \LaTeX 2.09.}, - status = {free}, - texlive = {latex2} -} - -@TeXIndex{mpbase, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {Basic MetaPost support files.}, - status = {free}, - texlive = {metapost1} -} - -@TeXIndex{multi, - modified = {February 1999, s.rahtz@elsevier.co.uk}, - abstract = {dvips header for making n-up pages.}, - status = {free}, - texlive = {dvips3} -} - -@TeXIndex{psafm, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {AFM files for PostScript fonts.}, - status = {free}, - texlive = {fonts3} -} - -@TeXIndex{pspk, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {PK files for common PostScript fonts.}, - status = {free}, - texlive = {fonts3} -} - -@TeXIndex{rs6000-aix4.1, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {System binaries for RS6000 running AIX 4.1.}, - status = {free}, - texlive = {systems1} -} - -@TeXIndex{rs6000-aix4.1.4.0, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {System binaries for RS6000 running AIX 4.1.4.0}, - status = {free}, - texlive = {systems1} -} - -@TeXIndex{sparc-solaris2.5.1, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {System binaries for Sun Sparc running Solaris 2.5.1.}, - status = {free}, - texlive = {systems1} -} - -@TeXIndex{texlive, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {Basic material for \TeXLive{}.}, - status = {free}, - texlive = {texlive1} -} - -@TeXIndex{tug, - modified = {February 1999, s.rahtz@elsevier.co.uk}, - abstract = {\TeX\ Users Group information.}, - status = {free}, - texlive = {doc3} -} - -@TeXIndex{useful, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {Useful documentation; various \LaTeX{} guides, FAQ, - fontname docs, etc.}, - status = {free}, - texlive = {doc2} -} - -@TeXIndex{win32, - modified = {February 1999 s.rahtz@elsevier.co.uk}, - abstract = {System binaries for Windows 32.}, - status = {free}, - texlive = {systems1} -} diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.bst b/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.bst deleted file mode 100644 index a4954030c95..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.bst +++ /dev/null @@ -1,60 +0,0 @@ -ENTRY - { - name - status - abstract - texlive - author - ctan - keywords - version - also - modified - } - {} % no integer entry variables - { label extra.label sort.label } % label entry variables - - -STRINGS { s t a.name } - - -FUNCTION {not} -{ { #0 } - { #1 } - if$ -} - -FUNCTION {and} -{ 'skip$ - { pop$ #0 } - if$ -} - -FUNCTION {or} -{ { pop$ #1 } - 'skip$ - if$ -} - -INTEGERS { nameptr namesleft numnames } - - -FUNCTION {TexIndex} { - texlive empty$ - { } - { "\bibitem{" cite$ * "}" * write$ - cite$ "&" * write$ - status "&" * write$ - texlive "&" * write$ - newline$ - abstract write$ - newline$ - } - if$ - } - - -READ - -ITERATE {call.type$} - diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.sty-2003 b/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.sty-2003 deleted file mode 100644 index 3b75b7b5bfd..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.sty-2003 +++ /dev/null @@ -1,378 +0,0 @@ -\NeedsTeXFormat{LaTeX2e}[1995/12/01] -\ProvidesPackage{tex-live}[2003/09/01 v1.0 TeX Live documentation style] -% -\RequirePackage{alltt} -\RequirePackage{array} -\RequirePackage{colortbl} -\RequirePackage{graphicx} -\RequirePackage{here} -\RequirePackage{longtable} -\RequirePackage{pslatex} -\RequirePackage{shortvrb} -\RequirePackage[normalem]{ulem} -\RequirePackage[obeyspaces]{url} -\RequirePackage{xspace} -\usepackage[T1]{fontenc} -\usepackage[latin1]{inputenc} -%\usepackage[textcomp]{lmodern} -% -\RequirePackage{europs} -\let\euro\EUR -% -\RequirePackage{mflogo} -\def\MP{MetaPost} -\let\mf\MF -% -% for a proper \acro command (even in the context of the definition in -% ltugboat -- \DRC overrides without checking) -\RequirePackage{relsize} -\DeclareRobustCommand{\acro}[1]{\textsmaller{#1}\@} -% -\RequirePackage{fancyvrb} -\DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=\normalsize} -\DefineVerbatimEnvironment{fverbatim}{Verbatim}{fontsize=\footnotesize} -\DefineVerbatimEnvironment{sverbatim}{Verbatim}{fontsize=\small} -\DefineVerbatimEnvironment{boxedverbatim} - {Verbatim}{fontsize=\scriptsize,frame=single} -\DefineVerbatimEnvironment{Verbatim}{Verbatim}{fontsize=\normalsize} -\def\verbatiminput#1{\VerbatimInput[fontsize=\scriptsize]{#1}} -\def\boxedverbatiminput#1{\VerbatimInput[frame=single,fontsize=\scriptsize]{#1}} -\def\listinginput#1#2{\VerbatimInput[fontsize=\scriptsize,firstnumber=#1,numbers=left]{#2}} -\MakeShortVerb\| -% -% -% Done with packages. -% -% Page layout. -\advance\textwidth by 1.1in -\advance\oddsidemargin by -.55in -\advance\evensidemargin by -.55in -% -\advance\textheight by 1in -\advance\topmargin by -.5in -\advance\footskip by -.5in -\pagestyle{headings} -% -% LaTeX parameters. -\renewcommand{\topfraction}{0.85} -\renewcommand{\floatpagefraction}{0.86} -\renewcommand{\textfraction}{0.1} -\renewcommand{\belowcaptionskip}{4pt} -\setcounter{tocdepth}{2} -\setcounter{topnumber}{5} -\setcounter{totalnumber}{5} -% -% linebreaking, etc. -\pretolerance=1000 -\tolerance=1500 -\hbadness=3000 -\vbadness=3000 -\hyphenpenalty=400 -\emergencystretch=.1\hsize -\relpenalty=500 -% -% fonts -\let\sl\it -\let\slfamily\itfamily -\let\textsl\textit -%\def\ttdefault{cmtt} -\def\ttdefault{lmtt} -% -% various sorts of names -\newcommand*{\pkgname}[1]{\textsf{#1}}% package name -\newcommand*{\optname}[1]{\texttt{#1}}% (package,class) option name -\newcommand*{\cmdname}[1]{\textsf{#1}}% command name -\newcommand*{\colname}[1]{\emph{#1}}% collection name -\newcommand*{\dirname}[1]{\path{#1}}% directory name -\newcommand*{\filename}[1]{\path{#1}}% file name -\newcommand*{\envname}[1]{\texttt{#1}}% environment variable name -\newcommand{\code}[1]{\texttt{#1}} -\newcommand{\file}[1]{\texttt{#1}} -\newcommand{\prog}[1]{\texttt{#1}} -\newcommand{\samp}[1]{`\texttt{#1}'} -\newcommand{\var}[1]{\emph{#1}} -\newcommand{\ttvar}[1]{\texttt{\var{#1}}} -% -% underlined command input. -\def\Ucom#1{% - \uline{\rule[-.2\baselineskip]{0pt}{.9\baselineskip}\ttfamily #1}} -\def\OnCD#1{\href{../../../../#1}{\path{#1}}} -% -% GUI menu/button/tab sequence: -\def\guiseq#1{\textsf{#1}} -\def\arw{\unskip$\rightarrow$\ignorespaces} -% -% Special names. -\def\dpi{$\,$dpi\xspace} -\def\bs{{\protect\normalfont\ttfamily\char'134}} -\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} -\def\Q#1{\par\vskip6pt\leftline{#1}\par} -\def\hyph{-} -% -% many abbreviations. -\newcommand{\CS}{$\mathcal{C}\kern-.1667em\lower.5ex% - \hbox{$\mathcal{S}$}\kern-.075em $} -\def\AFMtoTFM{\cmdname{AFM2TFM}\null} -\def\bv{\emph{Baskerville}} -\let\BV=\bv -\def\Dash{\unskip\nobreak\thinspace---\thinspace\ignorespaces} -\def\dvicopy{\cmdname{dvicopy}} -\def\dvidvi{\cmdname{dvidvi}} -\def\dvips{\cmdname{dvips}} -\def\eTeX{$\varepsilon$-\TeX} -\def\fpTeX{\textrm{fp}\TeX\xspace} -\def\GFtoDVI{\cmdname{GFtoDVI}\null} -\def\GFtoPK{\cmdname{GFtoPK}\null} -\def\GFtype{\cmdname{GFtype}} -\def\KPS{Kpathsea} -\def\La{La} -\def\OMEGA{$\Omega$} -\def\OzMF{OzMF} -\def\OzMP{OzMP} -\def\OzTeX{O\kern-.03em z\kern-.15em\TeX} -\def\PKtype{\cmdname{PKtype}} -\def\PLtoTF{\cmdname{PLtoTF}\null} -\def\teTeX{\textrm{te}\TeX\xspace} -\def\TeXLive{\TeX{} Live\xspace} -\def\TFtoPL{\cmdname{TFtoPL}\null} -\def\TK{\textsf{\TeX-Collection}} -\def\TypeI{Type~1} -\def\VFtoVP{\cmdname{VFtoVP}\null} -\def\VPtoVF{\cmdname{VPtoVF}\null} -\def\XEmTeX{\textrm{XEm}\TeX\xspace} -\def\XEmacs{\textrm{XEmacs}\xspace} -\def\Webc{Web2C} -\providecommand*{\CD}{\acro{CD}\xspace} -\providecommand*{\CTAN}{\acro{CTAN}\xspace} -\providecommand*{\DVD}{\acro{DVD}\xspace} -\providecommand*{\HTML}{\acro{HTML}\xspace} -\providecommand*{\MacOSX}{Mac\,\acro{OS\,X}\xspace} -\providecommand*{\PS}{Post\-Script\xspace} -\providecommand*{\TDS}{\acro{TDS}\xspace} -\providecommand*{\dvi}{\acro{DVI}\xspace} -\providecommand*{\web}{\texttt{web}\xspace} -% -% description-like environment that uses tt instead of bf, and doesn't -% go to the left margin. Without the \hfil, get an underfull box. -% Don't why \descriptionlabel doesn't. -\newenvironment{ttdescription} - {\begin{list}{label must be supplied}{% - \itemsep=0pt % these lists tend to have short descriptions - \let\makelabel=\ttdescriptionlabel}}% - {\end{list}} -\newcommand*\ttdescriptionlabel[1]{\hspace\labelsep - \normalfont\ttfamily #1\hfil} -% -% Likewise, for commands using sans serif. -\newenvironment{cmddescription} - {\begin{list}{label must be supplied}{% - \itemsep=0pt - \let\makelabel=\cmddescriptionlabel}}% - {\end{list}} -\newcommand*\cmddescriptionlabel[1]{\hspace\labelsep - \normalfont\sffamily #1\hfil} -% -\newsavebox{\wbox} -\newenvironment{warningbox} - {\begin{lrbox}{\wbox} - \begin{minipage}{.95\textwidth}} - {\end{minipage}\end{lrbox}\fbox{\usebox{\wbox}}} -% -% lrbox is used as a representation marking. I changed it to -% lrBox in tne source file, to get closer to logical marking -\newsavebox{\mylrbox} -\newenvironment{lrBox} - {\begin{lrbox}{\mylrbox}} - {\end{lrbox}} -% -% -% output setup -% -\newif\ifSingleColumn -\providecommand{\Status}{0} -%\typeout{Status is \Status} -% -% By default, we won't be creating hyperlinks. -\def\href#1#2{#2} -\def\hypertarget#1#2{} -\def\email#1{\href{mailto:#1}{\path{#1}}} % \path comes from url -% -% -\ifcase\Status - % \Status = 0 - \typeout{TeX Live documentation for printing} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - \or - % \Status = 1 - \typeout{TeX Live documentation in PDF format} - \RequirePackage[colorlinks,bookmarksopen, - pdfstartview={FitBH -320000},hyperindex]{hyperref} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - \or - % \Status = 2 - \typeout{TeX Live documentation in HTML format} - \RequirePackage[latex4ht]{tex4ht} - \or - % \Status = 3 - \typeout{TeX Live documentation as a Baskerville issue} - \@ifundefined{Fonts}% - {\RequirePackage{ae}}% - {\RequirePackage[T1]{\Fonts}} - \RequirePackage{bvoutln}% outline of baskerville - \RequirePackage{multicol} - \SingleColumnfalse - \or - % \Status = 4 - \typeout{TeX Live documentation as a TUB article} - \@ifundefined{Fonts}% - {\RequirePackage{ae}}% - {\RequirePackage[T1]{\Fonts}} - \SingleColumnfalse - \newenvironment{multicols}[1]{}{} -\fi -% -\ifnum \Status=4 -\else - \RequirePackage{texnames} - \providecommand\TeXXeT{\TeX-{}-% - \kern-.1emX\kern-.125em\lower.5ex\hbox{E}\kern-.1667emT\@} -\fi -% -% hacking at sections etc., to pay attention to baskerville status -\newcommand{\@condend@multicols}{% - \ifSingleColumn - \else - \def\@tempa{multicols}% - \ifx\@tempa\@currenvir - \end{multicols}% - \fi - \fi -} -\let\Section\section -\renewcommand{\section}{% - \@ifstar - {\Section*}% - {% - \@condend@multicols - \@dblarg\@full@section - }% -} -\def\@full@section[#1]#2{% - \Section[#1]{#2}% - \ifSingleColumn\else\begin{multicols}{2}\fi -} -\let\SubSection\subsection -\renewcommand{\subsection}{% - \@ifstar{\SubSection*}% - {% - \@condend@multicols - \@dblarg\@full@subsection - } -} -\def\@full@subsection[#1]#2{% - \SubSection[#1]{#2}% - \ifSingleColumn\else\begin{multicols}{2}\fi -} - -% calm things down a bit if we're in a multiple-column version -\ifSingleColumn -\else - \def\@listI{\leftmargin\leftmargini - \parsep \z@ - \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ - \itemsep \z@ \@plus .1\p@ - } - \let\@listi\@listI - \@listi - \def\@listii{\leftmargin\leftmarginii - \labelwidth\leftmarginii\advance\labelwidth-\labelsep - \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ - \parsep \z@ - \itemsep \z@ \@plus .1\p@ - } - \def\@listiii{\leftmargin\leftmarginiii - \labelwidth\leftmarginiii\advance\labelwidth-\labelsep - \topsep 1\p@ \@plus 1\p@ \@minus 1\p@ - \parsep \z@ - \partopsep \z@ - \itemsep \topsep - } - \def\@listiv{\leftmargin\leftmarginiv - \labelwidth\leftmarginiv\advance\labelwidth-\labelsep - } - \def\@listv{\leftmargin\leftmarginv - \labelwidth\leftmarginv\advance\labelwidth-\labelsep - } - \def\@listvi{\leftmargin\leftmarginvi - \labelwidth\leftmarginvi\advance\labelwidth-\labelsep - } -\fi -% -% array package stuff -\def\arraybackslash{\let\\=\@arraycr} -\newcolumntype{P}[1]{>{\raggedright\arraybackslash}p{#1}} -% -% shaded rows (using facilities of colortbl) -% -\definecolor{pale}{gray}{.9} -\newcount\colrow -\gdef\RowColor{pale} -\def\SetRowColor{% - \rowcolor{\RowColor}% - \global\advance\colrow by1\relax - \ifodd\colrow - \gdef\RowColor{pale}% - \else - \gdef\RowColor{white}% - \fi -} -% redefine to hack up a reference even though we don't need it... -\renewcommand\@bibitem[1]{\if@filesw \immediate\write\@auxout - {\string\bibcite{#1}{?}}\fi\ignorespaces} -% -% \unknownTeXlive is a dummy texlive entry for the biblio -\newcommand\unknownTeXlive[2][\relax]{\textbf{\textsc{unknown}}% - \global\@all@unknown\expandafter{\the\@all@unknown{#2}}% -} -\newtoks\@all@unknown -\global\@all@unknown{} -\AtEndDocument{\@message@unknowns} -\def\@message@unknowns{\edef\@tempa{\the\@all@unknown}% - \ifx\@tempa\@empty - \else - \def\@tempa{*** TeX live package location of }% - \expandafter\@output@unknowns\the\@all@unknown\@empty - \fi -} -\def\@output@unknowns#1{\edef\@tempb{#1}% - \ifx\@tempb\@empty - \typeout{ unknown}% - \else - \message{\@tempa#1,}% - \def\@tempa{}% - \expandafter\@output@unknowns - \fi -} -% -% a hack for the bibliography -\bibliographystyle{tex-live} -\newif\iffirstbibentry -\global\firstbibentrytrue -\let\@@bibitem\bibitem -\renewcommand\bibitem{\iffirstbibentry - \global\firstbibentryfalse - \else - \\\SetRowColor - \fi - \@@bibitem -} - - -% for \Dings -\RequirePackage{pifont} -% available for inter-article dinglines -\def\Dings{\nopagebreak{\footnotesize\dingline{167}}} - -\endinput diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.sty-2004 b/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.sty-2004 deleted file mode 100644 index 54ff32dbe53..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.sty-2004 +++ /dev/null @@ -1,422 +0,0 @@ -% $Id$ -% TeX Live documentation style. Written by many people over many years. -% Public domain. -% -\NeedsTeXFormat{LaTeX2e}[1995/12/01] -\ProvidesPackage{tex-live}[2004/11/07 v1.0 TeX Live documentation style] -% -\RequirePackage{alltt} -\RequirePackage{array} -\RequirePackage{colortbl} -\RequirePackage{comment} -\RequirePackage{graphicx} -\RequirePackage{here} -\RequirePackage{longtable} -\RequirePackage{shortvrb} -\RequirePackage[normalem]{ulem} -\RequirePackage[obeyspaces]{url} -\RequirePackage{xspace} -% -\RequirePackage{lmodern} -\usepackage{textcomp}% including \textbullet -\usepackage[T1]{fontenc} -\usepackage[latin1]{inputenc} -% -% for a proper \acro command (even in the context of the definition in -% ltugboat -- \DRC overrides without checking) -\RequirePackage{relsize} -\DeclareRobustCommand{\acro}[1]{\textsmaller{#1}\@} -% -\RequirePackage{fancyvrb} -\DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=\normalsize} -\DefineVerbatimEnvironment{fverbatim}{Verbatim}{fontsize=\footnotesize} -\DefineVerbatimEnvironment{sverbatim}{Verbatim}{fontsize=\small} -\DefineVerbatimEnvironment{boxedverbatim} - {Verbatim}{fontsize=\scriptsize,frame=single} -\DefineVerbatimEnvironment{Verbatim}{Verbatim}{fontsize=\normalsize} -\def\verbatiminput#1{\VerbatimInput[fontsize=\scriptsize]{#1}} -\def\boxedverbatiminput#1{\VerbatimInput[frame=single,fontsize=\scriptsize]{#1}} -\def\listinginput#1#2{\VerbatimInput[fontsize=\scriptsize,firstnumber=#1,numbers=left]{#2}} -\MakeShortVerb\| -% -% -% Done with packages. -% -% Page layout. -\advance\textwidth by 1.1in -\advance\oddsidemargin by -.55in -\advance\evensidemargin by -.55in -% -\advance\textheight by 1in -\advance\topmargin by -.5in -\advance\footskip by -.5in -\pagestyle{headings} -% -% LaTeX parameters. -\renewcommand{\topfraction}{0.85} -\renewcommand{\floatpagefraction}{0.86} -\renewcommand{\textfraction}{0.1} -\renewcommand{\belowcaptionskip}{4pt} -\setcounter{tocdepth}{2} -\setcounter{topnumber}{5} -\setcounter{totalnumber}{5} -% -% linebreaking, etc. -\hbadness=4000 -\vbadness=4000 -\emergencystretch=.1\hsize -\relpenalty=500 -% -\def\slash{/\penalty\z@\hskip\z@skip } -% -% various sorts of names -\newcommand*{\pkgname}[1]{\textsf{#1}}% package name -\newcommand*{\optname}[1]{\texttt{#1}}% (package,class) option name -\newcommand*{\cmdname}[1]{\textsf{#1}}% command name -\newcommand*{\colname}[1]{\emph{#1}}% collection name -\newcommand*{\dirname}[1]{\path{#1}}% directory name -\newcommand*{\filename}[1]{\path{#1}}% file name -\newcommand*{\envname}[1]{\texttt{#1}}% environment variable name -\newcommand{\code}[1]{\texttt{#1}} -\newcommand{\file}[1]{\texttt{#1}} -\newcommand{\prog}[1]{\texttt{#1}} -\newcommand{\samp}[1]{`\texttt{#1}'} -\newcommand{\var}[1]{{\sl #1}}% not \textsl, for roman not typewriter slanted. -\newcommand{\ttvar}[1]{\texttt{\var{#1}}} -% -% underlined command input. -\def\Ucom#1{% - \uline{\rule[-.2\baselineskip]{0pt}{.9\baselineskip}\ttfamily #1}} -% -% \CDref is for url's with a #, where we need to write the target url and -% displayed url separately in the input, due to catcode madness. -% (We could simplify/remove this next time, I think.) -\def\CDref#1#2{\texttt{#1}} -% -% \OnCD is currently for any other reference to a file or directory in -% the distribution. PDF readers only open .pdf files, though, so we -% should change this to only use \href for those. Or more likely use -% different macros in the source. -\def\OnCD#1{\href{../../../../#1}{\path{#1}}} -% -% \href incorrectly appends .pdf to anything without an extension; these -% definitions using \hyper@linkurl do not, but they fail for .pdf -% references -- which are the only ones that work anyway. So this is -% useless, in practice. -%\def\CDref#1#2{\hyper@linkurl{#2}{../../../../#1}} -%\def\OnCD#1{\hyper@linkurl{\path{#1}}{../../../../#1}} - -% GUI menu/button/tab sequence: -\def\guiseq#1{\textsf{#1}} -\def\arw{\unskip$\rightarrow$\ignorespaces} -% -% Special names. -\def\dpi{$\,$dpi\xspace} -\def\bs{{\protect\normalfont\ttfamily\char'134}} -\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} -\def\Q#1{\par\vskip6pt\leftline{#1}\par} -\def\hyph{-} -% -% many abbreviations. -\newcommand{\CS}{$\mathcal{C}\kern-.1667em\lower.5ex% - \hbox{$\mathcal{S}$}\kern-.075em $} -\def\AFMtoTFM{\cmdname{AFM2TFM}\null} -\def\bv{\emph{Baskerville}} -\let\BV=\bv -\def\Dash{\unskip\nobreak\thinspace---\thinspace\ignorespaces} -\def\dvicopy{\cmdname{dvicopy}} -\def\dvidvi{\cmdname{dvidvi}} -\def\dvips{\cmdname{dvips}} -\def\eTeX{$\varepsilon$-\TeX} -\def\fpTeX{\textrm{fp}\TeX\xspace} -\def\GFtoDVI{\cmdname{GFtoDVI}\null} -\def\GFtoPK{\cmdname{GFtoPK}\null} -\def\GFtype{\cmdname{GFtype}} -\def\KPS{Kpathsea} -\def\La{La} -\def\OMEGA{$\Omega$} -\def\OzMF{OzMF} -\def\OzMP{OzMP} -\def\OzTeX{O\kern-.03em z\kern-.15em\TeX} -\def\p.{p.\,} -\def\PKtype{\cmdname{PKtype}} -\def\PLtoTF{\cmdname{PLtoTF}\null} -\def\ProTeXt{Pro\TeX t} -\def\teTeX{\textrm{te}\TeX\xspace} -\def\TeXLive{\TeX{} Live\xspace} -\def\TFtoPL{\cmdname{TFtoPL}\null} -\def\TK{\textsf{\TeX-Collection}} -\let\TL=\TeXLive -\def\TypeI{Type~1} -\def\VFtoVP{\cmdname{VFtoVP}\null} -\def\VPtoVF{\cmdname{VPtoVF}\null} -\def\Thanh{H\`an~Th\^e\llap{\raise 0.5ex\hbox{\'{}}}~Th\`anh} -\def\XEmTeX{\textrm{XEm}\TeX\xspace} -\def\XEmacs{\textrm{XEmacs}\xspace} -\def\Webc{Web2C} -\providecommand*{\CD}{\acro{CD}\xspace} -\providecommand*{\CTAN}{\acro{CTAN}\xspace} -\providecommand*{\DVD}{\acro{DVD}\xspace} -\providecommand*{\HTML}{\acro{HTML}\xspace} -\providecommand*{\MacOSX}{Mac\,\acro{OS\,X}\xspace} -\providecommand*{\PS}{Post\-Script\xspace} -\providecommand*{\TDS}{\acro{TDS}\xspace} -\providecommand*{\dvi}{\acro{DVI}\xspace} -\providecommand*{\web}{\texttt{web}\xspace} - -% Include an image. -% #1 - name of image (pictures/#1.jpg, always .jpg please) -% #2 - bb for html -% #3 - width for TeX -% -\def\tlimage#1#2#3{% - \ifnum \Status=2 % html, want relative path in output - \includegraphics[#2]{../../general/texlive-common/pictures/#1.jpg} - \else % not html, handled by TEXINPUTS in Makefile - \includegraphics[width=#3]{pictures/#1.jpg} - \fi - \\[5mm] -} -% -% description-like environment that uses tt instead of bf, and doesn't -% go to the left margin. Without the \hfil, get an underfull box. -% Don't know why \descriptionlabel doesn't. -% -\newenvironment{ttdescription} - {\begin{list}{label must be supplied}{% - \itemsep=0pt % these lists tend to have short descriptions - \parindent=0pt - \let\makelabel=\ttdescriptionlabel}}% - {\end{list}} -\newcommand*\ttdescriptionlabel[1]{\hspace\labelsep - \normalfont\ttfamily #1\hfil} -% -% Likewise, for commands using sans serif. -\newenvironment{cmddescription} - {\begin{list}{label must be supplied}{% - \itemsep=0pt - \let\makelabel=\cmddescriptionlabel}}% - {\end{list}} -\newcommand*\cmddescriptionlabel[1]{\hspace\labelsep - \normalfont\sffamily #1\hfil} - -% General squeezed itemize. -\newenvironment{itemize*}% - {\begin{itemize}% - \setlength{\itemsep}{0pt}% - \setlength{\parskip}{0pt}}% - {\end{itemize}} - -\newsavebox{\wbox} -\newenvironment{warningbox} - {\begin{lrbox}{\wbox} - \begin{minipage}{.95\textwidth}} - {\end{minipage}\end{lrbox}\fbox{\usebox{\wbox}}} -% -% lrbox is used as a representation marking. I changed it to -% lrBox in tne source file, to get closer to logical marking -\newsavebox{\mylrbox} -\newenvironment{lrBox} - {\begin{lrbox}{\mylrbox}} - {\end{lrbox}} - - -% emacs-page output setup -% -\newif\ifSingleColumn -\providecommand{\Status}{0} -%\typeout{Status is \Status} -% -% By default, we won't be creating hyperlinks. -\def\href#1#2{#2} -\def\hypertarget#1#2{} -\def\email#1{\href{mailto:#1}{\path{#1}}} % \path comes from url -% -\definecolor{hypercolor}{rgb}{0.5,0.0,0.5} % purplish external links. -% -% -\ifcase\Status - % \Status = 0 - \typeout{TeX Live documentation in DVI format} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - \or - % \Status = 1 - \typeout{TeX Live documentation in PDF format} - \RequirePackage[breaklinks, - colorlinks,linkcolor=hypercolor,citecolor=hypercolor, - pagecolor=hypercolor,urlcolor=hypercolor, - filecolor=hypercolor, - bookmarksopen,pdfstartview={FitBH -320000},hyperindex] - {hyperref} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - \or - % \Status = 2 - \typeout{TeX Live documentation in HTML format} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - % read our config file, live4ht.cfg; q.v., for more definitions. - % hyperref load must come after the tex4ht load. - \RequirePackage[live4ht]{tex4ht} - \RequirePackage[tex4ht]{hyperref} \hyperlinkfileprefix{} - % definitions need simplifying for TeX4ht to make relative paths work. - \def\CDref#1#2{\href{../../../../#1}{#2}} - \def\OnCD#1{\href{../../../../#1}{#1}} - \or - % \Status = 3 - \typeout{TeX Live documentation as a Baskerville issue} - \@ifundefined{Fonts}% - {\RequirePackage{ae}}% - {\RequirePackage[T1]{\Fonts}} - \RequirePackage{bvoutln}% outline of baskerville - \SingleColumnfalse - \RequirePackage{multicol} - \or - % \Status = 4 - \typeout{TeX Live documentation as a TUB article} - \@ifundefined{Fonts}% - {\RequirePackage{ae}}% - {\RequirePackage[T1]{\Fonts}} - \SingleColumnfalse - \newenvironment{multicols}[1]{}{} -\fi -% -\ifnum \Status=4 -\else - \RequirePackage{texnames} - \providecommand\TeXXeT{\TeX-{}-% - \kern-.1emX\kern-.125em\lower.5ex\hbox{E}\kern-.1667emT\@} - \def\MP{MetaPost} - \let\mf\MF - \newcommand\ConTeXt{C\kern-.0333emon\-\kern-.0667em\TeX\kern-.0333emt} - \newcommand\MIKTEX{MiK\kern-.025em \TeX}% per www.miktex.org - % from pictex.tex: - \ifx\PiC\undefined \def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC} \fi - \ifx\PiCTeX\undefined \def\PiCTeX{\PiC\kern-.11em\TeX} \fi -\fi -% -% hacking at sections etc., to pay attention to baskerville status -\newcommand{\@condend@multicols}{% - \ifSingleColumn - \else - \def\@tempa{multicols}% - \ifx\@tempa\@currenvir - \end{multicols}% - \fi - \fi -} -\let\Section\section -\renewcommand{\section}{% - \@ifstar - {\Section*}% - {% - \@condend@multicols - \@dblarg\@full@section - }% -} -\def\@full@section[#1]#2{% - \Section[#1]{#2}% - \ifSingleColumn\else\begin{multicols}{2}\fi -} -\let\SubSection\subsection -\renewcommand{\subsection}{% - \@ifstar{\SubSection*}% - {% - \@condend@multicols - \@dblarg\@full@subsection - } -} -\def\@full@subsection[#1]#2{% - \SubSection[#1]{#2}% - \ifSingleColumn\else\begin{multicols}{2}\fi -} - -% calm things down a bit if we're in a multiple-column version -\ifSingleColumn -\else - \def\@listI{\leftmargin\leftmargini - \parsep \z@ - \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ - \itemsep \z@ \@plus .1\p@ - } - \let\@listi\@listI - \@listi - \def\@listii{\leftmargin\leftmarginii - \labelwidth\leftmarginii\advance\labelwidth-\labelsep - \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ - \parsep \z@ - \itemsep \z@ \@plus .1\p@ - } - \def\@listiii{\leftmargin\leftmarginiii - \labelwidth\leftmarginiii\advance\labelwidth-\labelsep - \topsep 1\p@ \@plus 1\p@ \@minus 1\p@ - \parsep \z@ - \partopsep \z@ - \itemsep \topsep - } - \def\@listiv{\leftmargin\leftmarginiv - \labelwidth\leftmarginiv\advance\labelwidth-\labelsep - } - \def\@listv{\leftmargin\leftmarginv - \labelwidth\leftmarginv\advance\labelwidth-\labelsep - } - \def\@listvi{\leftmargin\leftmarginvi - \labelwidth\leftmarginvi\advance\labelwidth-\labelsep - } -\fi -% -% array package stuff -\def\arraybackslash{\let\\=\@arraycr} -\newcolumntype{P}[1]{>{\raggedright\arraybackslash}p{#1}} -% -% shaded rows (using facilities of colortbl) -% -\definecolor{pale}{gray}{.9} -\newcount\colrow -\gdef\RowColor{pale} -\def\SetRowColor{% - \rowcolor{\RowColor}% - \global\advance\colrow by1\relax - \ifodd\colrow - \gdef\RowColor{pale}% - \else - \gdef\RowColor{white}% - \fi -} -% redefine to hack up a reference even though we don't need it... -\renewcommand\@bibitem[1]{\if@filesw \immediate\write\@auxout - {\string\bibcite{#1}{?}}\fi\ignorespaces} -% -% \unknownTeXlive is a dummy texlive entry for the biblio -\newcommand\unknownTeXlive[2][\relax]{\textbf{\textsc{unknown}}% - \global\@all@unknown\expandafter{\the\@all@unknown{#2}}% -} -\newtoks\@all@unknown -\global\@all@unknown{} -\AtEndDocument{\@message@unknowns} -\def\@message@unknowns{\edef\@tempa{\the\@all@unknown}% - \ifx\@tempa\@empty - \else - \def\@tempa{*** TeX live package location of }% - \expandafter\@output@unknowns\the\@all@unknown\@empty - \fi -} -\def\@output@unknowns#1{\edef\@tempb{#1}% - \ifx\@tempb\@empty - \typeout{ unknown}% - \else - \message{\@tempa#1,}% - \def\@tempa{}% - \expandafter\@output@unknowns - \fi -} - - -% Silence font warnings about no bold typewriter in LM. -\def\@font@warning#1{}% - -% Silence hyperref warnings about \kern. -\def\HyPsd@Warning#1{}% - -\endinput diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.sty-2005 b/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.sty-2005 deleted file mode 100644 index 487c8b8d7a2..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.sty-2005 +++ /dev/null @@ -1,429 +0,0 @@ -% $Id: tex-live.sty 1513 2006-02-13 00:22:35Z karl $ -% TeX Live documentation style. Written by many people over many years. -% Public domain. -% -\NeedsTeXFormat{LaTeX2e}[1995/12/01] -\ProvidesPackage{tex-live}[2005/09/24 v1.5 TeX Live documentation style] -% -\RequirePackage{alltt} -\RequirePackage{array} -\RequirePackage{colortbl} -\RequirePackage{comment} -\RequirePackage{float} -\RequirePackage{graphicx} -\RequirePackage{longtable} -\RequirePackage{shortvrb} -\RequirePackage[normalem]{ulem} -\RequirePackage[obeyspaces]{url} -\RequirePackage{xspace} -% -\RequirePackage{lmodern} -\usepackage{textcomp}% including \textbullet -\usepackage[T1]{fontenc} -\usepackage[latin1]{inputenc} -% -% for a proper \acro command (even in the context of the definition in -% ltugboat -- \DRC overrides without checking) -\RequirePackage{relsize} -\DeclareRobustCommand{\acro}[1]{\textsmaller{#1}\@} -% -\RequirePackage{fancyvrb} -\DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=\normalsize} -\DefineVerbatimEnvironment{fverbatim}{Verbatim}{fontsize=\footnotesize} -\DefineVerbatimEnvironment{sverbatim}{Verbatim}{fontsize=\small} -\DefineVerbatimEnvironment{boxedverbatim} - {Verbatim}{fontsize=\scriptsize,frame=single} -\DefineVerbatimEnvironment{Verbatim}{Verbatim}{fontsize=\normalsize} -\def\verbatiminput#1{\VerbatimInput[fontsize=\scriptsize]{#1}} -\def\boxedverbatiminput#1{\VerbatimInput[frame=single,fontsize=\scriptsize]{#1}} -\def\listinginput#1#2{\VerbatimInput[fontsize=\scriptsize,firstnumber=#1,numbers=left]{#2}} -\MakeShortVerb\| -% -% -% Done with packages. -% -% Page layout. -\advance\textwidth by 1.1in -\advance\oddsidemargin by -.55in -\advance\evensidemargin by -.55in -% -\advance\textheight by 1in -\advance\topmargin by -.5in -\advance\footskip by -.5in -\pagestyle{headings} -% -% LaTeX parameters. -\renewcommand{\topfraction}{0.85} -\renewcommand{\floatpagefraction}{0.86} -\renewcommand{\textfraction}{0.1} -\renewcommand{\belowcaptionskip}{4pt} -\setcounter{tocdepth}{2} -\setcounter{topnumber}{5} -\setcounter{totalnumber}{5} -% -% linebreaking, etc. -\hbadness=4000 -\vbadness=4000 -\emergencystretch=.1\hsize -\relpenalty=500 -% -\def\slash{/\penalty\z@\hskip\z@skip } -% -% various sorts of names -\newcommand*{\pkgname}[1]{\textsf{#1}}% package name -\newcommand*{\optname}[1]{\texttt{#1}}% (package,class) option name -\newcommand*{\cmdname}[1]{\textsf{#1}}% command name -\newcommand*{\colname}[1]{\emph{#1}}% collection name -\newcommand*{\dirname}[1]{\path{#1}}% directory name -\newcommand*{\filename}[1]{\path{#1}}% file name -\newcommand*{\envname}[1]{\texttt{#1}}% environment variable name -\newcommand{\code}[1]{\texttt{#1}} -\newcommand{\file}[1]{\texttt{#1}} -\newcommand{\prog}[1]{\texttt{#1}} -\newcommand{\samp}[1]{`\texttt{#1}'} -\newcommand{\var}[1]{{\sl #1}}% not \textsl, for roman not typewriter slanted. -\newcommand{\ttvar}[1]{\texttt{\var{#1}}} -% -% underlined command input. -\def\Ucom#1{% - \uline{\rule[-.2\baselineskip]{0pt}{.9\baselineskip}\ttfamily #1}} -% -% \CDref is for url's with a #, where we need to write the target url and -% displayed url separately in the input, due to catcode madness. -% (We could simplify/remove this next time, I think.) -\def\CDref#1#2{\texttt{#1}} -% -% \OnCD is currently for any other reference to a file or directory in -% the distribution. PDF readers only open .pdf files, though, so we -% should change this to only use \href for those. Or more likely use -% different macros in the source. -\def\OnCD#1{\href{../../../../#1}{\path{#1}}} -% -% \href incorrectly appends .pdf to anything without an extension; these -% definitions using \hyper@linkurl do not, but they fail for .pdf -% references -- which are the only ones that work anyway. So this is -% useless, in practice. -%\def\CDref#1#2{\hyper@linkurl{#2}{../../../../#1}} -%\def\OnCD#1{\hyper@linkurl{\path{#1}}{../../../../#1}} - -% GUI menu/button/tab sequence: -\def\guiseq#1{\textsf{#1}} -\def\arw{\unskip$\rightarrow$\ignorespaces} -% -% Special names. -\def\dpi{$\,$dpi\xspace} -\def\bs{{\protect\normalfont\ttfamily\char'134}} -\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} -\def\Q#1{\par\vskip6pt\leftline{#1}\par} -\def\hyph{-} -% -% many abbreviations. -\newcommand{\CS}{$\mathcal{C}\kern-.1667em\lower.5ex% - \hbox{$\mathcal{S}$}\kern-.075em $} -\def\AFMtoTFM{\cmdname{AFM2TFM}\null} -\def\bv{\emph{Baskerville}} -\let\BV=\bv -\def\Dash{\unskip\nobreak\thinspace---\thinspace\ignorespaces} -\def\dvicopy{\cmdname{dvicopy}} -\def\dvidvi{\cmdname{dvidvi}} -\def\dvips{\cmdname{dvips}} -\def\eTeX{$\varepsilon$-\TeX} -\def\fpTeX{\textrm{fp}\TeX\xspace} -\def\GFtoDVI{\cmdname{GFtoDVI}\null} -\def\GFtoPK{\cmdname{GFtoPK}\null} -\def\GFtype{\cmdname{GFtype}} -\def\KPS{Kpathsea} -\def\La{La} -\def\OMEGA{$\Omega$} -\def\OzMF{OzMF} -\def\OzMP{OzMP} -\def\OzTeX{O\kern-.03em z\kern-.15em\TeX} -\def\p.{p.\,} -\def\PKtype{\cmdname{PKtype}} -\def\PLtoTF{\cmdname{PLtoTF}\null} -\def\ProTeXt{Pro\TeX t} -\def\teTeX{\textrm{te}\TeX\xspace} -\def\TeXLive{\TeX{} Live\xspace} -\def\TFtoPL{\cmdname{TFtoPL}\null} -\def\TK{\textsf{\TeX\ Collection}} -\let\TL=\TeXLive -\def\TypeI{Type~1} -\def\VFtoVP{\cmdname{VFtoVP}\null} -\def\VPtoVF{\cmdname{VPtoVF}\null} -\def\Thanh{H\`an~Th\^e\llap{\raise 0.5ex\hbox{\'{}}}~Th\`anh} -\def\XEmTeX{\textrm{XEm}\TeX\xspace} -\def\XEmacs{\textrm{XEmacs}\xspace} -\def\Webc{Web2C} -\providecommand*{\CD}{\acro{CD}\xspace} -\providecommand*{\CTAN}{\acro{CTAN}\xspace} -\providecommand*{\DVD}{\acro{DVD}\xspace} -\providecommand*{\HTML}{\acro{HTML}\xspace} -\providecommand*{\MacOSX}{Mac\,\acro{OS\,X}\xspace} -\providecommand*{\PS}{Post\-Script\xspace} -\providecommand*{\TDS}{\acro{TDS}\xspace} -\providecommand*{\dvi}{\acro{DVI}\xspace} -\providecommand*{\web}{\texttt{web}\xspace} - -% Include an image. -% #1 - name of image (pictures/#1.jpg, always .jpg please) -% #2 - bb for html -% #3 - width for TeX -% -\def\tlimage#1#2#3{% - \ifnum \Status=2 % html, want relative path in output - \includegraphics[#2]{../../general/texlive-common/pictures/#1.jpg} - \else % not html, handled by TEXINPUTS in Makefile - \includegraphics[width=#3]{pictures/#1.jpg} - \fi - \\[5mm] -} -% -% description-like environment that uses tt instead of bf, and doesn't -% go to the left margin. Without the \hfil, get an underfull box. -% Don't know why \descriptionlabel doesn't. -% -\newenvironment{ttdescription} - {\begin{list}{label must be supplied}{% - \itemsep=0pt % these lists tend to have short descriptions - \parindent=0pt - \let\makelabel=\ttdescriptionlabel}}% - {\end{list}} -\newcommand*\ttdescriptionlabel[1]{\hspace\labelsep - \normalfont\ttfamily #1\hfil} -% -% Likewise, for commands using sans serif. -\newenvironment{cmddescription} - {\begin{list}{label must be supplied}{% - \itemsep=0pt - \let\makelabel=\cmddescriptionlabel}}% - {\end{list}} -\newcommand*\cmddescriptionlabel[1]{\hspace\labelsep - \normalfont\sffamily #1\hfil} - -% General squeezed itemize. -\newenvironment{itemize*}% - {\begin{itemize}% - \setlength{\itemsep}{0pt}% - \setlength{\parskip}{0pt}}% - {\end{itemize}} - -\newsavebox{\wbox} -\newenvironment{warningbox} - {\begin{lrbox}{\wbox} - \begin{minipage}{.95\textwidth}} - {\end{minipage}\end{lrbox}\fbox{\usebox{\wbox}}} -% -% lrbox is used as a representation marking. I changed it to -% lrBox in tne source file, to get closer to logical marking -\newsavebox{\mylrbox} -\newenvironment{lrBox} - {\begin{lrbox}{\mylrbox}} - {\end{lrbox}} - - -% emacs-page output setup -% -\ifx \HCode\UnDef - \providecommand{\Status}{0}% running TeX -\else - \providecommand{\Status}{2}% running TeX4ht -\fi -%\typeout{Status is \Status} -% -\newif\ifSingleColumn -% -% By default, we won't be creating hyperlinks. -\def\href#1#2{#2} -\def\hypertarget#1#2{} -\def\email#1{\href{mailto:#1}{\path{#1}}} % \path comes from url -% -\definecolor{hypercolor}{rgb}{0.5,0.0,0.5} % purplish external links. -% -% -\ifcase\Status - % \Status = 0 - \typeout{TeX Live documentation in DVI format} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - \or - % \Status = 1 - \typeout{TeX Live documentation in PDF format} - \RequirePackage[breaklinks, - colorlinks,linkcolor=hypercolor,citecolor=hypercolor, - pagecolor=hypercolor,urlcolor=hypercolor, - filecolor=hypercolor, - bookmarksopen, - %pdfstartview={FitBH -320000}, % fails with acrobat7 - hyperindex] - {hyperref} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - \or - % \Status = 2 - \typeout{TeX Live documentation in HTML format} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - % read our config file, live4ht.cfg; q.v., for more definitions. - % hyperref load must come after the tex4ht load. - \RequirePackage[live4ht]{tex4ht} - \RequirePackage[tex4ht]{hyperref} \hyperlinkfileprefix{} - % definitions need simplifying for TeX4ht to make relative paths work. - \def\CDref#1#2{\href{../../../../#1}{#2}} - \def\OnCD#1{\href{../../../../#1}{#1}} - \or - % \Status = 3 - \typeout{TeX Live documentation as a Baskerville issue} - \@ifundefined{Fonts}% - {\RequirePackage{ae}}% - {\RequirePackage[T1]{\Fonts}} - \RequirePackage{bvoutln}% outline of baskerville - \SingleColumnfalse - \RequirePackage{multicol} - \or - % \Status = 4 - \typeout{TeX Live documentation as a TUB article} - \@ifundefined{Fonts}% - {\RequirePackage{ae}}% - {\RequirePackage[T1]{\Fonts}} - \SingleColumnfalse - \newenvironment{multicols}[1]{}{} -\fi -% -\ifnum \Status=4 -\else - \RequirePackage{texnames} - \providecommand\TeXXeT{\TeX-{}-% - \kern-.1emX\kern-.125em\lower.5ex\hbox{E}\kern-.1667emT\@} - \def\MP{MetaPost} - \let\mf\MF - \newcommand\ConTeXt{C\kern-.0333emon\-\kern-.0667em\TeX\kern-.0333emt} - \newcommand\MIKTEX{MiK\kern-.025em \TeX}% per www.miktex.org - % from pictex.tex: - \ifx\PiC\undefined \def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC} \fi - \ifx\PiCTeX\undefined \def\PiCTeX{\PiC\kern-.11em\TeX} \fi -\fi -% -% hacking at sections etc., to pay attention to baskerville status -\newcommand{\@condend@multicols}{% - \ifSingleColumn - \else - \def\@tempa{multicols}% - \ifx\@tempa\@currenvir - \end{multicols}% - \fi - \fi -} -\let\Section\section -\renewcommand{\section}{% - \@ifstar - {\Section*}% - {% - \@condend@multicols - \@dblarg\@full@section - }% -} -\def\@full@section[#1]#2{% - \Section[#1]{#2}% - \ifSingleColumn\else\begin{multicols}{2}\fi -} -\let\SubSection\subsection -\renewcommand{\subsection}{% - \@ifstar{\SubSection*}% - {% - \@condend@multicols - \@dblarg\@full@subsection - } -} -\def\@full@subsection[#1]#2{% - \SubSection[#1]{#2}% - \ifSingleColumn\else\begin{multicols}{2}\fi -} - -% calm things down a bit if we're in a multiple-column version -\ifSingleColumn -\else - \def\@listI{\leftmargin\leftmargini - \parsep \z@ - \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ - \itemsep \z@ \@plus .1\p@ - } - \let\@listi\@listI - \@listi - \def\@listii{\leftmargin\leftmarginii - \labelwidth\leftmarginii\advance\labelwidth-\labelsep - \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ - \parsep \z@ - \itemsep \z@ \@plus .1\p@ - } - \def\@listiii{\leftmargin\leftmarginiii - \labelwidth\leftmarginiii\advance\labelwidth-\labelsep - \topsep 1\p@ \@plus 1\p@ \@minus 1\p@ - \parsep \z@ - \partopsep \z@ - \itemsep \topsep - } - \def\@listiv{\leftmargin\leftmarginiv - \labelwidth\leftmarginiv\advance\labelwidth-\labelsep - } - \def\@listv{\leftmargin\leftmarginv - \labelwidth\leftmarginv\advance\labelwidth-\labelsep - } - \def\@listvi{\leftmargin\leftmarginvi - \labelwidth\leftmarginvi\advance\labelwidth-\labelsep - } -\fi -% -% array package stuff -\def\arraybackslash{\let\\=\@arraycr} -\newcolumntype{P}[1]{>{\raggedright\arraybackslash}p{#1}} -% -% shaded rows (using facilities of colortbl) -% -\definecolor{pale}{gray}{.9} -\newcount\colrow -\gdef\RowColor{pale} -\def\SetRowColor{% - \rowcolor{\RowColor}% - \global\advance\colrow by1\relax - \ifodd\colrow - \gdef\RowColor{pale}% - \else - \gdef\RowColor{white}% - \fi -} -% redefine to hack up a reference even though we don't need it... -\renewcommand\@bibitem[1]{\if@filesw \immediate\write\@auxout - {\string\bibcite{#1}{?}}\fi\ignorespaces} -% -% \unknownTeXlive is a dummy texlive entry for the biblio -\newcommand\unknownTeXlive[2][\relax]{\textbf{\textsc{unknown}}% - \global\@all@unknown\expandafter{\the\@all@unknown{#2}}% -} -\newtoks\@all@unknown -\global\@all@unknown{} -\AtEndDocument{\@message@unknowns} -\def\@message@unknowns{\edef\@tempa{\the\@all@unknown}% - \ifx\@tempa\@empty - \else - \def\@tempa{*** TeX live package location of }% - \expandafter\@output@unknowns\the\@all@unknown\@empty - \fi -} -\def\@output@unknowns#1{\edef\@tempb{#1}% - \ifx\@tempb\@empty - \typeout{ unknown}% - \else - \message{\@tempa#1,}% - \def\@tempa{}% - \expandafter\@output@unknowns - \fi -} - - -% Silence font warnings about no bold typewriter in LM. -\def\@font@warning#1{}% - -% Silence hyperref warnings about \kern. -\def\HyPsd@Warning#1{}% - -\endinput diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.sty-2007 b/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.sty-2007 deleted file mode 100644 index 487c8b8d7a2..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.sty-2007 +++ /dev/null @@ -1,429 +0,0 @@ -% $Id: tex-live.sty 1513 2006-02-13 00:22:35Z karl $ -% TeX Live documentation style. Written by many people over many years. -% Public domain. -% -\NeedsTeXFormat{LaTeX2e}[1995/12/01] -\ProvidesPackage{tex-live}[2005/09/24 v1.5 TeX Live documentation style] -% -\RequirePackage{alltt} -\RequirePackage{array} -\RequirePackage{colortbl} -\RequirePackage{comment} -\RequirePackage{float} -\RequirePackage{graphicx} -\RequirePackage{longtable} -\RequirePackage{shortvrb} -\RequirePackage[normalem]{ulem} -\RequirePackage[obeyspaces]{url} -\RequirePackage{xspace} -% -\RequirePackage{lmodern} -\usepackage{textcomp}% including \textbullet -\usepackage[T1]{fontenc} -\usepackage[latin1]{inputenc} -% -% for a proper \acro command (even in the context of the definition in -% ltugboat -- \DRC overrides without checking) -\RequirePackage{relsize} -\DeclareRobustCommand{\acro}[1]{\textsmaller{#1}\@} -% -\RequirePackage{fancyvrb} -\DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=\normalsize} -\DefineVerbatimEnvironment{fverbatim}{Verbatim}{fontsize=\footnotesize} -\DefineVerbatimEnvironment{sverbatim}{Verbatim}{fontsize=\small} -\DefineVerbatimEnvironment{boxedverbatim} - {Verbatim}{fontsize=\scriptsize,frame=single} -\DefineVerbatimEnvironment{Verbatim}{Verbatim}{fontsize=\normalsize} -\def\verbatiminput#1{\VerbatimInput[fontsize=\scriptsize]{#1}} -\def\boxedverbatiminput#1{\VerbatimInput[frame=single,fontsize=\scriptsize]{#1}} -\def\listinginput#1#2{\VerbatimInput[fontsize=\scriptsize,firstnumber=#1,numbers=left]{#2}} -\MakeShortVerb\| -% -% -% Done with packages. -% -% Page layout. -\advance\textwidth by 1.1in -\advance\oddsidemargin by -.55in -\advance\evensidemargin by -.55in -% -\advance\textheight by 1in -\advance\topmargin by -.5in -\advance\footskip by -.5in -\pagestyle{headings} -% -% LaTeX parameters. -\renewcommand{\topfraction}{0.85} -\renewcommand{\floatpagefraction}{0.86} -\renewcommand{\textfraction}{0.1} -\renewcommand{\belowcaptionskip}{4pt} -\setcounter{tocdepth}{2} -\setcounter{topnumber}{5} -\setcounter{totalnumber}{5} -% -% linebreaking, etc. -\hbadness=4000 -\vbadness=4000 -\emergencystretch=.1\hsize -\relpenalty=500 -% -\def\slash{/\penalty\z@\hskip\z@skip } -% -% various sorts of names -\newcommand*{\pkgname}[1]{\textsf{#1}}% package name -\newcommand*{\optname}[1]{\texttt{#1}}% (package,class) option name -\newcommand*{\cmdname}[1]{\textsf{#1}}% command name -\newcommand*{\colname}[1]{\emph{#1}}% collection name -\newcommand*{\dirname}[1]{\path{#1}}% directory name -\newcommand*{\filename}[1]{\path{#1}}% file name -\newcommand*{\envname}[1]{\texttt{#1}}% environment variable name -\newcommand{\code}[1]{\texttt{#1}} -\newcommand{\file}[1]{\texttt{#1}} -\newcommand{\prog}[1]{\texttt{#1}} -\newcommand{\samp}[1]{`\texttt{#1}'} -\newcommand{\var}[1]{{\sl #1}}% not \textsl, for roman not typewriter slanted. -\newcommand{\ttvar}[1]{\texttt{\var{#1}}} -% -% underlined command input. -\def\Ucom#1{% - \uline{\rule[-.2\baselineskip]{0pt}{.9\baselineskip}\ttfamily #1}} -% -% \CDref is for url's with a #, where we need to write the target url and -% displayed url separately in the input, due to catcode madness. -% (We could simplify/remove this next time, I think.) -\def\CDref#1#2{\texttt{#1}} -% -% \OnCD is currently for any other reference to a file or directory in -% the distribution. PDF readers only open .pdf files, though, so we -% should change this to only use \href for those. Or more likely use -% different macros in the source. -\def\OnCD#1{\href{../../../../#1}{\path{#1}}} -% -% \href incorrectly appends .pdf to anything without an extension; these -% definitions using \hyper@linkurl do not, but they fail for .pdf -% references -- which are the only ones that work anyway. So this is -% useless, in practice. -%\def\CDref#1#2{\hyper@linkurl{#2}{../../../../#1}} -%\def\OnCD#1{\hyper@linkurl{\path{#1}}{../../../../#1}} - -% GUI menu/button/tab sequence: -\def\guiseq#1{\textsf{#1}} -\def\arw{\unskip$\rightarrow$\ignorespaces} -% -% Special names. -\def\dpi{$\,$dpi\xspace} -\def\bs{{\protect\normalfont\ttfamily\char'134}} -\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} -\def\Q#1{\par\vskip6pt\leftline{#1}\par} -\def\hyph{-} -% -% many abbreviations. -\newcommand{\CS}{$\mathcal{C}\kern-.1667em\lower.5ex% - \hbox{$\mathcal{S}$}\kern-.075em $} -\def\AFMtoTFM{\cmdname{AFM2TFM}\null} -\def\bv{\emph{Baskerville}} -\let\BV=\bv -\def\Dash{\unskip\nobreak\thinspace---\thinspace\ignorespaces} -\def\dvicopy{\cmdname{dvicopy}} -\def\dvidvi{\cmdname{dvidvi}} -\def\dvips{\cmdname{dvips}} -\def\eTeX{$\varepsilon$-\TeX} -\def\fpTeX{\textrm{fp}\TeX\xspace} -\def\GFtoDVI{\cmdname{GFtoDVI}\null} -\def\GFtoPK{\cmdname{GFtoPK}\null} -\def\GFtype{\cmdname{GFtype}} -\def\KPS{Kpathsea} -\def\La{La} -\def\OMEGA{$\Omega$} -\def\OzMF{OzMF} -\def\OzMP{OzMP} -\def\OzTeX{O\kern-.03em z\kern-.15em\TeX} -\def\p.{p.\,} -\def\PKtype{\cmdname{PKtype}} -\def\PLtoTF{\cmdname{PLtoTF}\null} -\def\ProTeXt{Pro\TeX t} -\def\teTeX{\textrm{te}\TeX\xspace} -\def\TeXLive{\TeX{} Live\xspace} -\def\TFtoPL{\cmdname{TFtoPL}\null} -\def\TK{\textsf{\TeX\ Collection}} -\let\TL=\TeXLive -\def\TypeI{Type~1} -\def\VFtoVP{\cmdname{VFtoVP}\null} -\def\VPtoVF{\cmdname{VPtoVF}\null} -\def\Thanh{H\`an~Th\^e\llap{\raise 0.5ex\hbox{\'{}}}~Th\`anh} -\def\XEmTeX{\textrm{XEm}\TeX\xspace} -\def\XEmacs{\textrm{XEmacs}\xspace} -\def\Webc{Web2C} -\providecommand*{\CD}{\acro{CD}\xspace} -\providecommand*{\CTAN}{\acro{CTAN}\xspace} -\providecommand*{\DVD}{\acro{DVD}\xspace} -\providecommand*{\HTML}{\acro{HTML}\xspace} -\providecommand*{\MacOSX}{Mac\,\acro{OS\,X}\xspace} -\providecommand*{\PS}{Post\-Script\xspace} -\providecommand*{\TDS}{\acro{TDS}\xspace} -\providecommand*{\dvi}{\acro{DVI}\xspace} -\providecommand*{\web}{\texttt{web}\xspace} - -% Include an image. -% #1 - name of image (pictures/#1.jpg, always .jpg please) -% #2 - bb for html -% #3 - width for TeX -% -\def\tlimage#1#2#3{% - \ifnum \Status=2 % html, want relative path in output - \includegraphics[#2]{../../general/texlive-common/pictures/#1.jpg} - \else % not html, handled by TEXINPUTS in Makefile - \includegraphics[width=#3]{pictures/#1.jpg} - \fi - \\[5mm] -} -% -% description-like environment that uses tt instead of bf, and doesn't -% go to the left margin. Without the \hfil, get an underfull box. -% Don't know why \descriptionlabel doesn't. -% -\newenvironment{ttdescription} - {\begin{list}{label must be supplied}{% - \itemsep=0pt % these lists tend to have short descriptions - \parindent=0pt - \let\makelabel=\ttdescriptionlabel}}% - {\end{list}} -\newcommand*\ttdescriptionlabel[1]{\hspace\labelsep - \normalfont\ttfamily #1\hfil} -% -% Likewise, for commands using sans serif. -\newenvironment{cmddescription} - {\begin{list}{label must be supplied}{% - \itemsep=0pt - \let\makelabel=\cmddescriptionlabel}}% - {\end{list}} -\newcommand*\cmddescriptionlabel[1]{\hspace\labelsep - \normalfont\sffamily #1\hfil} - -% General squeezed itemize. -\newenvironment{itemize*}% - {\begin{itemize}% - \setlength{\itemsep}{0pt}% - \setlength{\parskip}{0pt}}% - {\end{itemize}} - -\newsavebox{\wbox} -\newenvironment{warningbox} - {\begin{lrbox}{\wbox} - \begin{minipage}{.95\textwidth}} - {\end{minipage}\end{lrbox}\fbox{\usebox{\wbox}}} -% -% lrbox is used as a representation marking. I changed it to -% lrBox in tne source file, to get closer to logical marking -\newsavebox{\mylrbox} -\newenvironment{lrBox} - {\begin{lrbox}{\mylrbox}} - {\end{lrbox}} - - -% emacs-page output setup -% -\ifx \HCode\UnDef - \providecommand{\Status}{0}% running TeX -\else - \providecommand{\Status}{2}% running TeX4ht -\fi -%\typeout{Status is \Status} -% -\newif\ifSingleColumn -% -% By default, we won't be creating hyperlinks. -\def\href#1#2{#2} -\def\hypertarget#1#2{} -\def\email#1{\href{mailto:#1}{\path{#1}}} % \path comes from url -% -\definecolor{hypercolor}{rgb}{0.5,0.0,0.5} % purplish external links. -% -% -\ifcase\Status - % \Status = 0 - \typeout{TeX Live documentation in DVI format} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - \or - % \Status = 1 - \typeout{TeX Live documentation in PDF format} - \RequirePackage[breaklinks, - colorlinks,linkcolor=hypercolor,citecolor=hypercolor, - pagecolor=hypercolor,urlcolor=hypercolor, - filecolor=hypercolor, - bookmarksopen, - %pdfstartview={FitBH -320000}, % fails with acrobat7 - hyperindex] - {hyperref} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - \or - % \Status = 2 - \typeout{TeX Live documentation in HTML format} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - % read our config file, live4ht.cfg; q.v., for more definitions. - % hyperref load must come after the tex4ht load. - \RequirePackage[live4ht]{tex4ht} - \RequirePackage[tex4ht]{hyperref} \hyperlinkfileprefix{} - % definitions need simplifying for TeX4ht to make relative paths work. - \def\CDref#1#2{\href{../../../../#1}{#2}} - \def\OnCD#1{\href{../../../../#1}{#1}} - \or - % \Status = 3 - \typeout{TeX Live documentation as a Baskerville issue} - \@ifundefined{Fonts}% - {\RequirePackage{ae}}% - {\RequirePackage[T1]{\Fonts}} - \RequirePackage{bvoutln}% outline of baskerville - \SingleColumnfalse - \RequirePackage{multicol} - \or - % \Status = 4 - \typeout{TeX Live documentation as a TUB article} - \@ifundefined{Fonts}% - {\RequirePackage{ae}}% - {\RequirePackage[T1]{\Fonts}} - \SingleColumnfalse - \newenvironment{multicols}[1]{}{} -\fi -% -\ifnum \Status=4 -\else - \RequirePackage{texnames} - \providecommand\TeXXeT{\TeX-{}-% - \kern-.1emX\kern-.125em\lower.5ex\hbox{E}\kern-.1667emT\@} - \def\MP{MetaPost} - \let\mf\MF - \newcommand\ConTeXt{C\kern-.0333emon\-\kern-.0667em\TeX\kern-.0333emt} - \newcommand\MIKTEX{MiK\kern-.025em \TeX}% per www.miktex.org - % from pictex.tex: - \ifx\PiC\undefined \def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC} \fi - \ifx\PiCTeX\undefined \def\PiCTeX{\PiC\kern-.11em\TeX} \fi -\fi -% -% hacking at sections etc., to pay attention to baskerville status -\newcommand{\@condend@multicols}{% - \ifSingleColumn - \else - \def\@tempa{multicols}% - \ifx\@tempa\@currenvir - \end{multicols}% - \fi - \fi -} -\let\Section\section -\renewcommand{\section}{% - \@ifstar - {\Section*}% - {% - \@condend@multicols - \@dblarg\@full@section - }% -} -\def\@full@section[#1]#2{% - \Section[#1]{#2}% - \ifSingleColumn\else\begin{multicols}{2}\fi -} -\let\SubSection\subsection -\renewcommand{\subsection}{% - \@ifstar{\SubSection*}% - {% - \@condend@multicols - \@dblarg\@full@subsection - } -} -\def\@full@subsection[#1]#2{% - \SubSection[#1]{#2}% - \ifSingleColumn\else\begin{multicols}{2}\fi -} - -% calm things down a bit if we're in a multiple-column version -\ifSingleColumn -\else - \def\@listI{\leftmargin\leftmargini - \parsep \z@ - \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ - \itemsep \z@ \@plus .1\p@ - } - \let\@listi\@listI - \@listi - \def\@listii{\leftmargin\leftmarginii - \labelwidth\leftmarginii\advance\labelwidth-\labelsep - \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ - \parsep \z@ - \itemsep \z@ \@plus .1\p@ - } - \def\@listiii{\leftmargin\leftmarginiii - \labelwidth\leftmarginiii\advance\labelwidth-\labelsep - \topsep 1\p@ \@plus 1\p@ \@minus 1\p@ - \parsep \z@ - \partopsep \z@ - \itemsep \topsep - } - \def\@listiv{\leftmargin\leftmarginiv - \labelwidth\leftmarginiv\advance\labelwidth-\labelsep - } - \def\@listv{\leftmargin\leftmarginv - \labelwidth\leftmarginv\advance\labelwidth-\labelsep - } - \def\@listvi{\leftmargin\leftmarginvi - \labelwidth\leftmarginvi\advance\labelwidth-\labelsep - } -\fi -% -% array package stuff -\def\arraybackslash{\let\\=\@arraycr} -\newcolumntype{P}[1]{>{\raggedright\arraybackslash}p{#1}} -% -% shaded rows (using facilities of colortbl) -% -\definecolor{pale}{gray}{.9} -\newcount\colrow -\gdef\RowColor{pale} -\def\SetRowColor{% - \rowcolor{\RowColor}% - \global\advance\colrow by1\relax - \ifodd\colrow - \gdef\RowColor{pale}% - \else - \gdef\RowColor{white}% - \fi -} -% redefine to hack up a reference even though we don't need it... -\renewcommand\@bibitem[1]{\if@filesw \immediate\write\@auxout - {\string\bibcite{#1}{?}}\fi\ignorespaces} -% -% \unknownTeXlive is a dummy texlive entry for the biblio -\newcommand\unknownTeXlive[2][\relax]{\textbf{\textsc{unknown}}% - \global\@all@unknown\expandafter{\the\@all@unknown{#2}}% -} -\newtoks\@all@unknown -\global\@all@unknown{} -\AtEndDocument{\@message@unknowns} -\def\@message@unknowns{\edef\@tempa{\the\@all@unknown}% - \ifx\@tempa\@empty - \else - \def\@tempa{*** TeX live package location of }% - \expandafter\@output@unknowns\the\@all@unknown\@empty - \fi -} -\def\@output@unknowns#1{\edef\@tempb{#1}% - \ifx\@tempb\@empty - \typeout{ unknown}% - \else - \message{\@tempa#1,}% - \def\@tempa{}% - \expandafter\@output@unknowns - \fi -} - - -% Silence font warnings about no bold typewriter in LM. -\def\@font@warning#1{}% - -% Silence hyperref warnings about \kern. -\def\HyPsd@Warning#1{}% - -\endinput diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.sty-2008 b/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.sty-2008 deleted file mode 100644 index 6bb5d7fb57b..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/tex-live.sty-2008 +++ /dev/null @@ -1,444 +0,0 @@ -% $Id: tex-live.sty 10332 2008-08-14 01:04:30Z karl $ -% TeX Live documentation style. Written by many people over many years. -% Public domain. -% -\NeedsTeXFormat{LaTeX2e}[1995/12/01] -\ProvidesPackage{tex-live}[2008/08/08 v1.6 TeX Live documentation style] -% -\RequirePackage{alltt} -\RequirePackage{array} -\RequirePackage{colortbl} -\RequirePackage{comment} -\RequirePackage{float} -\RequirePackage{graphicx} -\RequirePackage{longtable} -\RequirePackage{shortvrb} -\RequirePackage[normalem]{ulem} -\RequirePackage[obeyspaces]{url} -\RequirePackage{xspace} -% -\RequirePackage{lmodern} -\usepackage{textcomp}% including \textbullet -\def\p.{p.\,} - -% for a proper \acro command. -\RequirePackage{relsize} -%\DeclareRobustCommand{\acro}[1]{\textscale{.9}{#1}\@} -\def\acro#1{\textscale{.9}{#1}\@} -% -\RequirePackage{fancyvrb} -\DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=\normalsize} -\DefineVerbatimEnvironment{fverbatim}{Verbatim}{fontsize=\footnotesize} -\DefineVerbatimEnvironment{sverbatim}{Verbatim}{fontsize=\small} -\DefineVerbatimEnvironment{boxedverbatim} - {Verbatim}{fontsize=\scriptsize,frame=single} -\DefineVerbatimEnvironment{Verbatim}{Verbatim}{fontsize=\normalsize} -\def\verbatiminput#1{\VerbatimInput[fontsize=\scriptsize]{#1}} -\def\boxedverbatiminput#1{\VerbatimInput[frame=single,fontsize=\scriptsize]{#1}} -\def\listinginput#1#2{\VerbatimInput[fontsize=\scriptsize,firstnumber=#1,numbers=left]{#2}} -\MakeShortVerb\| -% -% -% Done with packages. -% -% Page layout. -\advance\textwidth by 1.1in -\advance\oddsidemargin by -.55in -\advance\evensidemargin by -.55in -% -\advance\textheight by 1in -\advance\topmargin by -.5in -\advance\footskip by -.5in -\pagestyle{headings} -% -% LaTeX parameters. -\renewcommand{\topfraction}{0.85} -\renewcommand{\floatpagefraction}{0.86} -\renewcommand{\textfraction}{0.1} -\renewcommand{\abovecaptionskip}{4pt} -\renewcommand{\belowcaptionskip}{4pt} -\setcounter{tocdepth}{3} -\setcounter{secnumdepth}{3} -\setcounter{topnumber}{5} -\setcounter{totalnumber}{5} -% -% linebreaking, etc. -\hbadness=4000 -\vbadness=4000 -\emergencystretch=.1\hsize -\relpenalty=500 -% -\def\slash{/\penalty\z@\hskip\z@skip } -% -% various sorts of names -\newcommand*{\pkgname}[1]{\textsf{#1}}% package name -\newcommand*{\optname}[1]{\texttt{#1}}% (package,class) option name -\newcommand*{\cmdname}[1]{\textsf{#1}}% command name -\newcommand*{\colname}[1]{\emph{#1}}% collection name -\newcommand*{\dirname}[1]{\path{#1}}% directory name -\newcommand*{\filename}[1]{\path{#1}}% file name -\newcommand*{\envname}[1]{\texttt{#1}}% environment variable name -\newcommand{\code}[1]{\texttt{#1}} -\newcommand{\file}[1]{\texttt{#1}} -\newcommand{\prog}[1]{\textsf{#1}}% same as \cmdname -\newcommand{\samp}[1]{`\texttt{#1}'} -\newcommand{\var}[1]{{\sl #1}}% not \textsl, for roman not typewriter slanted. -\newcommand{\ttvar}[1]{\texttt{\var{#1}}} -% -% underlined command input. -%\def\Ucom#1{% -% \uline{\rule[-.2\baselineskip]{0pt}{.9\baselineskip}\ttfamily #1}} -% bold command input -\def\Ucom#1{{\bfseries\ttfamily #1}} -% -% \CDref is for url's with a #, where we need to write the target url and -% displayed url separately in the input, due to catcode madness. -% (We could simplify/remove this next time, I think.) -\def\CDref#1#2{\texttt{#1}} -% -% \OnCD is currently for any other reference to a file or directory in -% the distribution. PDF readers only open .pdf files, though, so we -% should change this to only use \href for those. Or more likely use -% different macros in the source. -\def\OnCD#1{\href{../../../../#1}{\path{#1}}} -% -% \href incorrectly appends .pdf to anything without an extension; these -% definitions using \hyper@linkurl do not, but they fail for .pdf -% references -- which are the only ones that work anyway. So this is -% useless, in practice. -%\def\CDref#1#2{\hyper@linkurl{#2}{../../../../#1}} -%\def\OnCD#1{\hyper@linkurl{\path{#1}}{../../../../#1}} - -% GUI menu/button/tab sequence: -\def\guiseq#1{\textsf{#1}} -\def\arw{\unskip$\rightarrow$\ignorespaces} -% -% Special names. -\def\dpi{$\,$dpi\xspace} -\def\bs{{\protect\normalfont\ttfamily\char'134}} -\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} -\def\Q#1{\par\vskip6pt\leftline{#1}\par} -\def\hyph{-} -% -% many abbreviations. -\newcommand{\CS}{$\mathcal{C}\kern-.1667em\lower.5ex% - \hbox{$\mathcal{S}$}\kern-.075em $} -\def\AFMtoTFM{\cmdname{AFM2TFM}\null} -\def\bv{\emph{Baskerville}} -\let\BV=\bv -\def\Dash{\unskip\nobreak\thinspace---\thinspace\ignorespaces} -\def\dvicopy{\cmdname{dvicopy}} -\def\dvidvi{\cmdname{dvidvi}} -\def\dvips{\cmdname{dvips}} -\def\eTeX{$\varepsilon$-\TeX} -\def\fpTeX{\textrm{fp}\TeX\xspace} -\def\GFtoDVI{\cmdname{GFtoDVI}\null} -\def\GFtoPK{\cmdname{GFtoPK}\null} -\def\GFtype{\cmdname{GFtype}} -\def\GUI{\acro{GUI}\xspace} -\def\KPS{Kpathsea} -\def\La{La} -\def\OMEGA{$\Omega$} -\def\OzMF{OzMF} -\def\OzMP{OzMP} -\def\OzTeX{O\kern-.03em z\kern-.15em\TeX} -\def\PKtype{\cmdname{PKtype}} -\def\PLtoTF{\cmdname{PLtoTF}\null} -\def\ProTeXt{Pro\TeX t} -\def\teTeX{\textrm{te}\TeX\xspace} -\def\TeXLive{\TeX{} Live\xspace} -\def\TFtoPL{\cmdname{TFtoPL}\null} -\def\TK{\TeX\ Collection} -\let\TL=\TeXLive -\def\TypeI{Type~1} -\def\VFtoVP{\cmdname{VFtoVP}\null} -\def\VPtoVF{\cmdname{VPtoVF}\null} -\def\Thanh{H\`an~Th\ifx % get Unicode char in tex4ht's HTML output - \HCode\UnDef\^e\llap{\raise 0.5ex\hbox{\'{}}}\else - \HCode{\string&\#x1EBF;}\fi~Th\`anh} -\def\XEmTeX{\textrm{XEm}\TeX\xspace} -\def\XEmacs{\textrm{XEmacs}\xspace} -\def\XeTeX{Xe\TeX\xspace} -\def\Webc{Web2C} -\providecommand*{\CD}{\acro{CD}\xspace} -\providecommand*{\CTAN}{\acro{CTAN}\xspace} -\providecommand*{\DVD}{\acro{DVD}\xspace} -\providecommand*{\GNU}{\acro{GNU}\xspace} -\providecommand*{\HTML}{\acro{HTML}\xspace} -\providecommand*{\ISO}{\acro{ISO}\xspace} -\providecommand*{\MacOSX}{Mac\,\acro{OS\,X}\xspace} -\providecommand*{\PS}{Post\-Script\xspace} -\providecommand*{\TDS}{\acro{TDS}\xspace} -\providecommand*{\dvi}{\acro{DVI}\xspace} -\providecommand*{\web}{\texttt{WEB}\xspace} - -% Include an image. -% #1 - name of image (pictures/#1.jpg, always .jpg please) -% #2 - bb for html -% #3 - width for TeX -% -\def\tlimage#1#2#3{% - \ifnum \Status=2 % html, want relative path in output - \includegraphics[#2]{../../general/texlive-common/pictures/#1.jpg} - \else % not html, handled by TEXINPUTS in Makefile - \includegraphics[width=#3]{pictures/#1.jpg} - \fi - \\[5mm] -} - -\def\tlpng#1#2{% - \ifnum \Status=2 % html, want relative path in output - \includegraphics[bb=0 0 1 1]{#1.png}% - \else % not html, handled by TEXINPUTS in Makefile - \includegraphics[width=#2]{#1.png}% - \fi -} -% -% description-like environment that uses tt instead of bf, and doesn't -% go to the left margin. Without the \hfil, get an underfull box. -% Don't know why \descriptionlabel doesn't. -% -\newenvironment{ttdescription} - {\begin{list}{label must be supplied}{% - \itemsep=0pt % these lists tend to have short descriptions - \parindent=0pt - \let\makelabel=\ttdescriptionlabel}}% - {\end{list}} -\newcommand*\ttdescriptionlabel[1]{\hspace\labelsep - \normalfont\ttfamily #1\hfil} -% -% Likewise, for commands using sans serif. -\newenvironment{cmddescription} - {\begin{list}{label must be supplied}{% - \itemsep=0pt - \let\makelabel=\cmddescriptionlabel}}% - {\end{list}} -\newcommand*\cmddescriptionlabel[1]{\hspace\labelsep - \normalfont\sffamily #1\hfil} - -% General squeezed itemize. -\newenvironment{itemize*}% - {\begin{itemize}% - \setlength{\itemsep}{0pt}% - \setlength{\parskip}{0pt}}% - {\end{itemize}} - -\newsavebox{\wbox} -\newenvironment{warningbox} - {\begin{lrbox}{\wbox} - \begin{minipage}{.95\textwidth}} - {\end{minipage}\end{lrbox}\fbox{\usebox{\wbox}}} -% -% lrbox is used as a representation marking. I changed it to -% lrBox in tne source file, to get closer to logical marking -\newsavebox{\mylrbox} -\newenvironment{lrBox} - {\begin{lrbox}{\mylrbox}} - {\end{lrbox}} - - -% emacs-page output setup -% -\ifx \HCode\UnDef - \providecommand{\Status}{0}% running TeX -\else - \providecommand{\Status}{2}% running TeX4ht -\fi -%\typeout{Status is \Status} -% -\newif\ifSingleColumn -% -% By default, we won't be creating hyperlinks. -\def\href#1#2{#2} -\def\hypertarget#1#2{} -\def\email#1{\href{mailto:#1}{\path{#1}}} % \path comes from url -% -\definecolor{hypercolor}{rgb}{0.5,0.0,0.5} % purplish external links. -% -% -\ifcase\Status - % \Status = 0 - \typeout{TeX Live documentation in DVI format} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - \or - % \Status = 1 - \typeout{TeX Live documentation in PDF format} - \RequirePackage[breaklinks, - colorlinks,linkcolor=hypercolor,citecolor=hypercolor, - urlcolor=hypercolor,filecolor=hypercolor, - bookmarksopen, - %pdfstartview={FitBH -320000}, % fails with acrobat7 - hyperindex] - {hyperref} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - \or - % \Status = 2 - \typeout{TeX Live documentation in HTML format} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - % read our config file, live4ht.cfg; q.v., for more definitions. - % hyperref load must come after the tex4ht load. - \RequirePackage[live4ht]{tex4ht} - \RequirePackage[tex4ht]{hyperref} \hyperlinkfileprefix{} - % definitions need simplifying for TeX4ht to make relative paths work. - \def\CDref#1#2{\href{../../../../#1}{#2}} - \def\OnCD#1{\href{../../../../#1}{#1}} - \or - % \Status = 3 - \typeout{TeX Live documentation as a Baskerville issue} - \@ifundefined{Fonts}% - {\RequirePackage{ae}}% - {\RequirePackage[T1]{\Fonts}} - \RequirePackage{bvoutln}% outline of baskerville - \SingleColumnfalse - \RequirePackage{multicol} - \or - % \Status = 4 - \typeout{TeX Live documentation as a TUB article} - \@ifundefined{Fonts}% - {\RequirePackage{ae}}% - {\RequirePackage[T1]{\Fonts}} - \SingleColumnfalse - \newenvironment{multicols}[1]{}{} -\fi -% -\ifnum \Status=4 -\else - \RequirePackage{texnames} - \providecommand\TeXXeT{\TeX-{}-% - \kern-.1emX\kern-.125em\lower.5ex\hbox{E}\kern-.1667emT\@} - \def\MP{MetaPost} - \let\mf\MF - \newcommand\ConTeXt{C\kern-.0333emon\-\kern-.0667em\TeX\kern-.0333emt} - \newcommand\MIKTEX{MiK\kern-.025em \TeX}% per www.miktex.org - % from pictex.tex: - \ifx\PiC\undefined \def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC} \fi - \ifx\PiCTeX\undefined \def\PiCTeX{\PiC\kern-.11em\TeX} \fi -\fi -% -% hacking at sections etc., to pay attention to baskerville status -\newcommand{\@condend@multicols}{% - \ifSingleColumn - \else - \def\@tempa{multicols}% - \ifx\@tempa\@currenvir - \end{multicols}% - \fi - \fi -} -\let\Section\section -\renewcommand{\section}{% - \@ifstar - {\Section*}% - {% - \@condend@multicols - \@dblarg\@full@section - }% -} -\def\@full@section[#1]#2{% - \Section[#1]{#2}% - \ifSingleColumn\else\begin{multicols}{2}\fi -} -\let\SubSection\subsection -\renewcommand{\subsection}{% - \@ifstar{\SubSection*}% - {% - \@condend@multicols - \@dblarg\@full@subsection - } -} -\def\@full@subsection[#1]#2{% - \SubSection[#1]{#2}% - \ifSingleColumn\else\begin{multicols}{2}\fi -} - -% calm things down a bit if we're in a multiple-column version -\ifSingleColumn -\else - \def\@listI{\leftmargin\leftmargini - \parsep \z@ - \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ - \itemsep \z@ \@plus .1\p@ - } - \let\@listi\@listI - \@listi - \def\@listii{\leftmargin\leftmarginii - \labelwidth\leftmarginii\advance\labelwidth-\labelsep - \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ - \parsep \z@ - \itemsep \z@ \@plus .1\p@ - } - \def\@listiii{\leftmargin\leftmarginiii - \labelwidth\leftmarginiii\advance\labelwidth-\labelsep - \topsep 1\p@ \@plus 1\p@ \@minus 1\p@ - \parsep \z@ - \partopsep \z@ - \itemsep \topsep - } - \def\@listiv{\leftmargin\leftmarginiv - \labelwidth\leftmarginiv\advance\labelwidth-\labelsep - } - \def\@listv{\leftmargin\leftmarginv - \labelwidth\leftmarginv\advance\labelwidth-\labelsep - } - \def\@listvi{\leftmargin\leftmarginvi - \labelwidth\leftmarginvi\advance\labelwidth-\labelsep - } -\fi -% -% array package stuff -\def\arraybackslash{\let\\=\@arraycr} -\newcolumntype{P}[1]{>{\raggedright\arraybackslash}p{#1}} -% -% shaded rows (using facilities of colortbl) -% -\definecolor{pale}{gray}{.9} -\newcount\colrow -\gdef\RowColor{pale} -\def\SetRowColor{% - \rowcolor{\RowColor}% - \global\advance\colrow by1\relax - \ifodd\colrow - \gdef\RowColor{pale}% - \else - \gdef\RowColor{white}% - \fi -} -% redefine to hack up a reference even though we don't need it... -\renewcommand\@bibitem[1]{\if@filesw \immediate\write\@auxout - {\string\bibcite{#1}{?}}\fi\ignorespaces} -% -% \unknownTeXlive is a dummy texlive entry for the biblio -\newcommand\unknownTeXlive[2][\relax]{\textbf{\textsc{unknown}}% - \global\@all@unknown\expandafter{\the\@all@unknown{#2}}% -} -\newtoks\@all@unknown -\global\@all@unknown{} -\AtEndDocument{\@message@unknowns} -\def\@message@unknowns{\edef\@tempa{\the\@all@unknown}% - \ifx\@tempa\@empty - \else - \def\@tempa{*** TeX live package location of }% - \expandafter\@output@unknowns\the\@all@unknown\@empty - \fi -} -\def\@output@unknowns#1{\edef\@tempb{#1}% - \ifx\@tempb\@empty - \typeout{ unknown}% - \else - \message{\@tempa#1,}% - \def\@tempa{}% - \expandafter\@output@unknowns - \fi -} - - -% Silence font warnings about no bold typewriter in LM. -\def\@font@warning#1{}% - -% Silence hyperref warnings about \kern. -\def\HyPsd@Warning#1{}% - -\endinput diff --git a/Master/texmf-doc/source/texlive/texlive-en/archive/texlive.pl b/Master/texmf-doc/source/texlive/texlive-en/archive/texlive.pl deleted file mode 100644 index 33a19a801d6..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/archive/texlive.pl +++ /dev/null @@ -1,574 +0,0 @@ -$texlive{"a0poster"}="latex3"; -$texlive{"aaai"}="latex3"; -$texlive{"abstyles"}="bibtex3"; -$texlive{"accfonts"}="fonts3"; -$texlive{"achemso"}="latex3"; -$texlive{"acronym"}="latex3"; -$texlive{"adfathesis"}="latex3"; -$texlive{"adobeother"}="fonts3"; -$texlive{"adobestd"}="fonts1"; -$texlive{"adrlist"}="latex3"; -$texlive{"ae"}="fonts2"; -$texlive{"aguplus"}="latex3"; -$texlive{"aiaa"}="latex3"; -$texlive{"akletter"}="latex3"; -$texlive{"alatex"}="formats3"; -$texlive{"alg"}="latex3"; -$texlive{"algorithms"}="latex3"; -$texlive{"alphaev5-osf4.0d"}="systems1"; -$texlive{"alphaev5-osf4.0d"}="systems2"; -$texlive{"alphaev5-osf4.0d"}="systems3"; -$texlive{"altfont"}="latex3"; -$texlive{"amsfonts"}="fonts2"; -$texlive{"amslatex"}="latex2"; -$texlive{"amstex"}="plain2"; -$texlive{"answers"}="latex3"; -$texlive{"antyktor"}="fonts3"; -$texlive{"apa"}="latex3"; -$texlive{"apl"}="fonts3"; -$texlive{"appendix"}="latex3"; -$texlive{"ar"}="fonts3"; -$texlive{"arabtex"}="lang3"; -$texlive{"arydshln"}="latex3"; -$texlive{"asaetr"}="latex3"; -$texlive{"ascii"}="fonts3"; -$texlive{"astro"}="fonts3"; -$texlive{"aurora"}="dvips3"; -$texlive{"authorindex"}="latex3"; -$texlive{"autotab"}="latex3"; -$texlive{"babel"}="generic2"; -$texlive{"backgammon"}="fonts3"; -$texlive{"bakoma"}="fonts2"; -$texlive{"barcode2"}="fonts3"; -$texlive{"barcodes"}="fonts3"; -$texlive{"barr"}="graphics3"; -$texlive{"bbding"}="fonts3"; -$texlive{"bbm"}="fonts3"; -$texlive{"bbold"}="fonts3"; -$texlive{"bbtbase"}="bibtex1"; -$texlive{"bbtdoc"}="bibtex2"; -$texlive{"beebe"}="bibtex2"; -$texlive{"belleek"}="fonts2"; -$texlive{"beton"}="latex3"; -$texlive{"bez123"}="latex3"; -$texlive{"bezos"}="latex3"; -$texlive{"bibarts"}="bibtex3"; -$texlive{"biblist"}="latex3"; -$texlive{"blue"}="formats3"; -$texlive{"bluesky"}="fonts1"; -$texlive{"booktabs"}="latex2"; -$texlive{"borceux"}="graphics3"; -$texlive{"bosisio"}="latex3"; -$texlive{"bridge"}="latex3"; -$texlive{"brushscr"}="fonts3"; -$texlive{"c-pascal"}="generic3"; -$texlive{"calendar"}="latex3"; -$texlive{"calligra"}="fonts3"; -$texlive{"calrsfs"}="latex3"; -$texlive{"camel"}="latex3"; -$texlive{"caption"}="latex2"; -$texlive{"carlisle"}="latex2"; -$texlive{"casyl"}="lang3"; -$texlive{"catalog"}="doc2"; -$texlive{"cbgreek"}="fonts3"; -$texlive{"cc-pl"}="fonts2"; -$texlive{"ccaption"}="latex3"; -$texlive{"ccfonts"}="latex3"; -$texlive{"cchess"}="fonts3"; -$texlive{"cdcover"}="latex3"; -$texlive{"cellular"}="plain3"; -$texlive{"changebar"}="latex2"; -$texlive{"chemcono"}="latex3"; -$texlive{"chemsym"}="latex3"; -$texlive{"cheq"}="fonts3"; -$texlive{"cherokee"}="fonts3"; -$texlive{"chess"}="fonts3"; -$texlive{"china2e"}="latex3"; -$texlive{"circ"}="graphics3"; -$texlive{"cirth"}="fonts3"; -$texlive{"cite"}="latex2"; -$texlive{"cjk"}="lang3"; -$texlive{"cm"}="fonts1"; -$texlive{"cmbright"}="fonts2"; -$texlive{"cmcyr"}="fonts3"; -$texlive{"cmcyralt"}="latex3"; -$texlive{"cmdtrack"}="latex2"; -$texlive{"cmextra"}="fonts2"; -$texlive{"cmpica"}="fonts3"; -$texlive{"cmpk"}="fonts3"; -$texlive{"cmsd"}="latex3"; -$texlive{"codepage"}="latex3"; -$texlive{"colorsep"}="dvips3"; -$texlive{"colortab"}="plain3"; -$texlive{"comment"}="latex3"; -$texlive{"concmath"}="fonts3"; -$texlive{"concrete"}="fonts3"; -$texlive{"context"}="formats2"; -$texlive{"covington"}="latex3"; -$texlive{"croatian"}="lang3"; -$texlive{"crop"}="latex3"; -$texlive{"crossword"}="latex3"; -$texlive{"crosswrd"}="latex3"; -$texlive{"csfonts"}="fonts2"; -$texlive{"cslatex"}="lang2"; -$texlive{"csplain"}="lang2"; -$texlive{"cspsfonts"}="fonts2"; -$texlive{"cstug"}="doc3"; -$texlive{"cursor"}="latex3"; -$texlive{"curves"}="graphics3"; -$texlive{"custom-bib"}="bibtex2"; -$texlive{"cyrillic"}="lang2"; -$texlive{"dancers"}="fonts3"; -$texlive{"deleq"}="latex3"; -$texlive{"devanagari"}="lang3"; -$texlive{"dialogl"}="latex3"; -$texlive{"dinbrief"}="latex3"; -$texlive{"directory"}="bibtex3"; -$texlive{"dotseqn"}="latex3"; -$texlive{"draftcopy"}="latex3"; -$texlive{"dratex"}="graphics3"; -$texlive{"dropping"}="latex3"; -$texlive{"dstroke"}="fonts3"; -$texlive{"dtk"}="latex3"; -$texlive{"duerer"}="fonts3"; -$texlive{"dvipdfm"}="doc2"; -$texlive{"dvipsbase"}="dvips1"; -$texlive{"dvipsdoc"}="dvips2"; -$texlive{"ean"}="generic3"; -$texlive{"easy"}="latex3"; -$texlive{"ec"}="fonts2"; -$texlive{"ecc"}="fonts3"; -$texlive{"ecltree"}="latex2"; -$texlive{"eco"}="fonts3"; -$texlive{"ecpk"}="fonts3"; -$texlive{"edmac"}="plain3"; -$texlive{"eepic"}="graphics2"; -$texlive{"egplot"}="latex3"; -$texlive{"eiad"}="fonts3"; -$texlive{"eijkhout"}="generic3"; -$texlive{"elsevier"}="latex3"; -$texlive{"elvish"}="fonts3"; -$texlive{"emp"}="latex3"; -$texlive{"emulateapj"}="latex3"; -$texlive{"encodings"}="omega2"; -$texlive{"endfloat"}="latex3"; -$texlive{"engwar"}="fonts3"; -$texlive{"envbig"}="latex3"; -$texlive{"envlab"}="latex3"; -$texlive{"epigraph"}="latex3"; -$texlive{"eplain"}="formats2"; -$texlive{"eqname"}="latex3"; -$texlive{"eqnarray"}="latex3"; -$texlive{"esieecv"}="latex3"; -$texlive{"etexbase"}="etex2"; -$texlive{"etruscan"}="fonts3"; -$texlive{"euler"}="latex3"; -$texlive{"euro"}="fonts2"; -$texlive{"euro2"}="latex3"; -$texlive{"eurofont"}="fonts2"; -$texlive{"europs"}="fonts2"; -$texlive{"eurosans"}="latex3"; -$texlive{"eurosym"}="fonts2"; -$texlive{"euxm"}="fonts3"; -$texlive{"exam"}="latex3"; -$texlive{"examdesign"}="latex3"; -$texlive{"expdlist"}="latex3"; -$texlive{"expl3"}="latex3"; -$texlive{"export"}="latex3"; -$texlive{"fancybox"}="latex2"; -$texlive{"fancyhdr"}="latex2"; -$texlive{"fancyref"}="latex2"; -$texlive{"fancyvrb"}="latex2"; -$texlive{"fax"}="latex3"; -$texlive{"fc"}="fonts3"; -$texlive{"feynmf"}="graphics3"; -$texlive{"finbib"}="bibtex3"; -$texlive{"float"}="latex2"; -$texlive{"floatfig"}="latex3"; -$texlive{"floatflt"}="latex3"; -$texlive{"fltpage"}="latex3"; -$texlive{"fncychap"}="latex3"; -$texlive{"foilhtml"}="latex3"; -$texlive{"foiltex"}="latex3"; -$texlive{"fontinst"}="generic2"; -$texlive{"fontname"}="doc2"; -$texlive{"footbib"}="latex3"; -$texlive{"footmisc"}="latex2"; -$texlive{"footnpag"}="latex3"; -$texlive{"formats"}="texlive2"; -$texlive{"formula"}="latex3"; -$texlive{"fp"}="latex3"; -$texlive{"frankenstein"}="latex3"; -$texlive{"french"}="lang2"; -$texlive{"fribrief"}="latex3"; -$texlive{"fullblck"}="latex3"; -$texlive{"fullpict"}="latex3"; -$texlive{"fundus"}="latex3"; -$texlive{"futhark"}="fonts3"; -$texlive{"g-brief"}="latex3"; -$texlive{"gb4e"}="latex3"; -$texlive{"genealogy"}="fonts3"; -$texlive{"general"}="doc1"; -$texlive{"genmisc"}="generic3"; -$texlive{"geometry"}="latex3"; -$texlive{"geomsty"}="latex3"; -$texlive{"german"}="lang2"; -$texlive{"germbib"}="bibtex2"; -$texlive{"germdoc"}="doc2"; -$texlive{"gloss"}="latex3"; -$texlive{"gn-logic"}="latex3"; -$texlive{"go"}="fonts3"; -$texlive{"gothic"}="fonts3"; -$texlive{"graphics"}="latex1"; -$texlive{"greek6cbc"}="fonts3"; -$texlive{"grnumalt"}="latex3"; -$texlive{"grtimes"}="lang3"; -$texlive{"guides"}="doc2"; -$texlive{"gustlib"}="plain2"; -$texlive{"hands"}="fonts3"; -$texlive{"hanging"}="latex3"; -$texlive{"harpoon"}="latex3"; -$texlive{"harvard"}="bibtex2"; -$texlive{"harvmac"}="plain3"; -$texlive{"hh"}="latex3"; -$texlive{"hilowres"}="latex3"; -$texlive{"histogr"}="latex3"; -$texlive{"hoekwater"}="fonts2"; -$texlive{"hppa1.1-hpux10.10"}="systems1"; -$texlive{"hppa1.1-hpux10.10"}="systems2"; -$texlive{"hppa1.1-hpux10.10"}="systems3"; -$texlive{"html"}="doc2"; -$texlive{"hvmaths"}="fonts3"; -$texlive{"hyper"}="latex3"; -$texlive{"hyperref"}="latex2"; -$texlive{"hyphen"}="lang1"; -$texlive{"hyphenat"}="latex3"; -$texlive{"i386-linux"}="systems1"; -$texlive{"i386-linux"}="systems2"; -$texlive{"i386-linux"}="systems3"; -$texlive{"i386-linux-libc5"}="systems1"; -$texlive{"i386-linux-libc5"}="systems2"; -$texlive{"i386-linux-libc5"}="systems3"; -$texlive{"ibm"}="fonts3"; -$texlive{"ieeepes"}="latex3"; -$texlive{"ifacmtg"}="latex3"; -$texlive{"imac"}="latex3"; -$texlive{"indxcite"}="latex3"; -$texlive{"info"}="doc2"; -$texlive{"ini"}="texlive1"; -$texlive{"insbox"}="generic3"; -$texlive{"ipa"}="latex3"; -$texlive{"isostds"}="latex3"; -$texlive{"jadetex"}="formats2"; -$texlive{"jhep"}="latex3"; -$texlive{"jknappen"}="latex2"; -$texlive{"jsmisc"}="plain3"; -$texlive{"jura"}="latex3"; -$texlive{"kalender"}="latex3"; -$texlive{"karnaugh"}="latex3"; -$texlive{"kdgreek"}="fonts3"; -$texlive{"kluwer"}="latex3"; -$texlive{"knuth"}="doc3"; -$texlive{"koma-script"}="latex3"; -$texlive{"kuvio"}="graphics3"; -$texlive{"labels"}="latex3"; -$texlive{"lamstex"}="formats3"; -$texlive{"lastpage"}="latex3"; -$texlive{"latexfonts"}="latex1"; -$texlive{"layouts"}="latex3"; -$texlive{"leaflet"}="latex3"; -$texlive{"leftidx"}="latex3"; -$texlive{"lettrine"}="latex3"; -$texlive{"levy"}="latex3"; -$texlive{"lgc"}="doc3"; -$texlive{"lgreek"}="latex3"; -$texlive{"lh"}="fonts2"; -$texlive{"lhcyr"}="latex3"; -$texlive{"lineno"}="latex3"; -$texlive{"linguex"}="latex3"; -$texlive{"listings"}="latex3"; -$texlive{"lkort"}="doc3"; -$texlive{"localloc"}="latex3"; -$texlive{"logic"}="fonts3"; -$texlive{"lollipop"}="formats3"; -$texlive{"ltablex"}="latex3"; -$texlive{"ltx2rtf"}="texlive2"; -$texlive{"ltxbase"}="latex1"; -$texlive{"ltxdoc"}="doc2"; -$texlive{"ltxdoc"}="latex1"; -$texlive{"ltxmisc"}="latex2"; -$texlive{"lucida"}="fonts2"; -$texlive{"ly1"}="latex3"; -$texlive{"mailing"}="latex3"; -$texlive{"makeindex"}="doc1"; -$texlive{"malayalam"}="lang3"; -$texlive{"malvern"}="fonts3"; -$texlive{"mapcodes"}="latex3"; -$texlive{"maple"}="latex3"; -$texlive{"margbib"}="latex3"; -$texlive{"marvosym"}="fonts3"; -$texlive{"mathcomp"}="latex2"; -$texlive{"mathematica"}="fonts3"; -$texlive{"mathpple"}="fonts3"; -$texlive{"mcite"}="latex3"; -$texlive{"mdwtools"}="latex3"; -$texlive{"metasupp"}="texlive1"; -$texlive{"method"}="latex3"; -$texlive{"mex"}="lang2"; -$texlive{"mff"}="latex3"; -$texlive{"mflogo"}="latex2"; -$texlive{"mfmisc"}="fonts1"; -$texlive{"mfnfss"}="latex2"; -$texlive{"mfpic"}="graphics3"; -$texlive{"mft"}="texlive1"; -$texlive{"mftoeps"}="fonts3"; -$texlive{"mhs"}="latex3"; -$texlive{"midnight"}="generic3"; -$texlive{"minitoc"}="latex3"; -$texlive{"mips-irix6.2"}="systems1"; -$texlive{"mips-irix6.2"}="systems2"; -$texlive{"mips-irix6.2"}="systems3"; -$texlive{"misc209"}="latex2"; -$texlive{"mltex"}="latex2"; -$texlive{"mnras"}="plain3"; -$texlive{"monotype"}="fonts3"; -$texlive{"montex"}="lang3"; -$texlive{"morehelp"}="latex3"; -$texlive{"moresize"}="latex3"; -$texlive{"moreverb"}="latex3"; -$texlive{"morse"}="fonts3"; -$texlive{"mpattern"}="metapost2"; -$texlive{"mpbase"}="metapost1"; -$texlive{"mpfnmark"}="latex3"; -$texlive{"ms"}="latex3"; -$texlive{"mslapa"}="latex3"; -$texlive{"mtbe"}="plain3"; -$texlive{"multenum"}="latex3"; -$texlive{"multi"}="dvips3"; -$texlive{"multirow"}="latex3"; -$texlive{"musictex"}="generic3"; -$texlive{"musixtex"}="generic3"; -$texlive{"nassflow"}="latex3"; -$texlive{"natbib"}="bibtex2"; -$texlive{"ncctools"}="latex2"; -$texlive{"newalg"}="latex3"; -$texlive{"newlfm"}="latex3"; -$texlive{"newsletr"}="plain3"; -$texlive{"newthm"}="latex3"; -$texlive{"niceframe"}="latex3"; -$texlive{"nomencl"}="latex3"; -$texlive{"nrc"}="latex3"; -$texlive{"ntg"}="doc3"; -$texlive{"ntgclass"}="latex2"; -$texlive{"ntheorem"}="latex3"; -$texlive{"numline"}="latex3"; -$texlive{"objectz"}="latex3"; -$texlive{"oca"}="fonts3"; -$texlive{"ocr-a"}="fonts3"; -$texlive{"ogham"}="fonts3"; -$texlive{"ogonek"}="latex3"; -$texlive{"oldstyle"}="latex3"; -$texlive{"omegabase"}="omega2"; -$texlive{"omegafonts"}="omega2"; -$texlive{"osmanian"}="fonts3"; -$texlive{"ot2cyr"}="fonts2"; -$texlive{"overpic"}="latex3"; -$texlive{"pacioli"}="fonts3"; -$texlive{"pageno"}="latex3"; -$texlive{"pandora"}="fonts3"; -$texlive{"paper"}="latex3"; -$texlive{"paralist"}="latex3"; -$texlive{"parallel"}="latex3"; -$texlive{"patch"}="latex2"; -$texlive{"pawpict"}="latex3"; -$texlive{"pb-diagram"}="latex3"; -$texlive{"pdcmac"}="plain3"; -$texlive{"pdfscreen"}="latex3"; -$texlive{"pdftex"}="pdftex2"; -$texlive{"permute"}="latex3"; -$texlive{"phoenician"}="fonts3"; -$texlive{"phonetic"}="fonts3"; -$texlive{"physe"}="formats3"; -$texlive{"phyzzx"}="formats3"; -$texlive{"picinpar"}="latex3"; -$texlive{"picins"}="latex3"; -$texlive{"pictex"}="graphics2"; -$texlive{"piff"}="latex3"; -$texlive{"pl"}="latex3"; -$texlive{"pl-qx"}="fonts2"; -$texlive{"plainmisc"}="plain1"; -$texlive{"plaintex"}="plain1"; -$texlive{"plari"}="latex3"; -$texlive{"platex"}="lang2"; -$texlive{"play"}="latex3"; -$texlive{"plcalendar"}="plain3"; -$texlive{"plfonts"}="fonts2"; -$texlive{"plgraph"}="generic3"; -$texlive{"plpatch"}="plain3"; -$texlive{"pmgraph"}="latex3"; -$texlive{"poligraf"}="generic3"; -$texlive{"polish"}="doc3"; -$texlive{"polyglot"}="latex3"; -$texlive{"prettyref"}="latex3"; -$texlive{"progkeys"}="latex3"; -$texlive{"program"}="latex3"; -$texlive{"proofs"}="latex3"; -$texlive{"protex"}="generic3"; -$texlive{"psafm"}="fonts3"; -$texlive{"psfig"}="generic3"; -$texlive{"psfrag"}="graphics2"; -$texlive{"psizzl"}="formats3"; -$texlive{"pslatex"}="latex2"; -$texlive{"psnfss"}="latex1"; -$texlive{"psnfssx"}="latex2"; -$texlive{"pspicture"}="latex2"; -$texlive{"pstricks"}="graphics2"; -$texlive{"punk"}="fonts3"; -$texlive{"qfonts"}="fonts2"; -$texlive{"qobitree"}="graphics3"; -$texlive{"qsymbols"}="latex3"; -$texlive{"quotchap"}="latex3"; -$texlive{"r-und-s"}="latex3"; -$texlive{"rcs"}="latex3"; -$texlive{"rcsinfo"}="latex3"; -$texlive{"realcalc"}="generic3"; -$texlive{"refcheck"}="latex3"; -$texlive{"refman"}="latex3"; -$texlive{"relenc"}="latex3"; -$texlive{"revtex"}="latex2"; -$texlive{"rlepsf"}="generic3"; -$texlive{"rmpage"}="latex3"; -$texlive{"rotating"}="latex2"; -$texlive{"rotfloat"}="latex3"; -$texlive{"rplain"}="latex3"; -$texlive{"rs6000-aix4.1.4.0"}="systems1"; -$texlive{"rs6000-aix4.1.4.0"}="systems2"; -$texlive{"rs6000-aix4.1.4.0"}="systems3"; -$texlive{"rsfs"}="fonts2"; -$texlive{"ruhyphen"}="lang1"; -$texlive{"runic"}="fonts3"; -$texlive{"sanskrit"}="fonts3"; -$texlive{"sauterfonts"}="latex3"; -$texlive{"scale"}="latex3"; -$texlive{"schedule"}="latex3"; -$texlive{"script"}="latex3"; -$texlive{"sectsty"}="latex3"; -$texlive{"semantic"}="latex3"; -$texlive{"seminar"}="latex2"; -$texlive{"setspace"}="latex3"; -$texlive{"shadbox"}="latex3"; -$texlive{"shadethm"}="latex3"; -$texlive{"shortlst"}="latex3"; -$texlive{"shorttoc"}="latex3"; -$texlive{"showdim"}="latex3"; -$texlive{"showlabels"}="latex3"; -$texlive{"siam"}="generic3"; -$texlive{"sidecap"}="latex3"; -$texlive{"siggraph"}="latex3"; -$texlive{"simpsons"}="fonts3"; -$texlive{"siunits"}="latex3"; -$texlive{"slashbox"}="latex3"; -$texlive{"slidenotes"}="latex3"; -$texlive{"smallcap"}="latex3"; -$texlive{"songbook"}="latex3"; -$texlive{"soul"}="latex3"; -$texlive{"sparc-solaris2.5.1"}="systems1"; -$texlive{"sparc-solaris2.5.1"}="systems2"; -$texlive{"sparc-solaris2.5.1"}="systems3"; -$texlive{"sprite"}="graphics3"; -$texlive{"ssqquote"}="latex3"; -$texlive{"startex"}="formats3"; -$texlive{"stdclsdv"}="latex3"; -$texlive{"stmaryrd"}="fonts2"; -$texlive{"subeqn"}="latex3"; -$texlive{"subeqnarray"}="latex3"; -$texlive{"subfigure"}="latex3"; -$texlive{"supertabular"}="latex3"; -$texlive{"synttree"}="latex3"; -$texlive{"t2"}="lang3"; -$texlive{"tabbing"}="latex3"; -$texlive{"tap"}="generic2"; -$texlive{"taylor"}="graphics3"; -$texlive{"tbe"}="plain3"; -$texlive{"tcx"}="texlive1"; -$texlive{"tds"}="doc1"; -$texlive{"tengwar"}="fonts3"; -$texlive{"tetex"}="doc1"; -$texlive{"tex-ps"}="generic2"; -$texlive{"tex4ht"}="latex2"; -$texlive{"texdraw"}="graphics3"; -$texlive{"texinfo"}="plain2"; -$texlive{"texip"}="formats3"; -$texlive{"texlive"}="texlive1"; -$texlive{"texsis"}="formats3"; -$texlive{"text1"}="formats3"; -$texlive{"textfit"}="latex3"; -$texlive{"textmerg"}="latex3"; -$texlive{"textpos"}="latex3"; -$texlive{"thesis"}="latex3"; -$texlive{"threed"}="metapost2"; -$texlive{"thumb"}="latex3"; -$texlive{"thumbpdf"}="latex3"; -$texlive{"timesht"}="latex3"; -$texlive{"timing"}="latex3"; -$texlive{"tipa"}="fonts2"; -$texlive{"titlefoot"}="latex3"; -$texlive{"titlesec"}="latex3"; -$texlive{"tmmaths"}="fonts3"; -$texlive{"tocbibind"}="latex3"; -$texlive{"tocloft"}="latex3"; -$texlive{"tocvsec2"}="latex3"; -$texlive{"tools"}="latex1"; -$texlive{"tracking"}="latex3"; -$texlive{"treesvr"}="latex3"; -$texlive{"treetex"}="plain3"; -$texlive{"ttf2pk"}="texlive2"; -$texlive{"tug"}="doc3"; -$texlive{"tugboat"}="generic2"; -$texlive{"type1"}="fonts2"; -$texlive{"type1cm"}="latex3"; -$texlive{"typespec"}="plain3"; -$texlive{"uaclasses"}="latex3"; -$texlive{"ucthesis"}="latex3"; -$texlive{"ulsy"}="latex3"; -$texlive{"umlaute"}="latex3"; -$texlive{"umrand"}="fonts3"; -$texlive{"underlin"}="latex3"; -$texlive{"uni"}="fonts3"; -$texlive{"units"}="latex3"; -$texlive{"universa"}="fonts3"; -$texlive{"unsupported"}="fonts3"; -$texlive{"urwstd"}="fonts2"; -$texlive{"useful"}="doc2"; -$texlive{"ut-thesis"}="latex3"; -$texlive{"utthesis"}="latex3"; -$texlive{"uwthesis"}="latex3"; -$texlive{"vdm"}="latex3"; -$texlive{"vector"}="latex3"; -$texlive{"vertex"}="plain3"; -$texlive{"vita"}="latex3"; -$texlive{"vrb"}="latex3"; -$texlive{"vrsion"}="latex3"; -$texlive{"warpcol"}="latex3"; -$texlive{"wasy"}="fonts2"; -$texlive{"wasysym"}="latex2"; -$texlive{"williams"}="latex3"; -$texlive{"win32"}="systems1"; -$texlive{"win32"}="systems2"; -$texlive{"win32"}="systems3"; -$texlive{"windvi"}="doc1"; -$texlive{"wnri"}="fonts3"; -$texlive{"wntamil"}="lang3"; -$texlive{"wsuipa"}="fonts2"; -$texlive{"xtab"}="latex3"; -$texlive{"xtcapts"}="latex3"; -$texlive{"xymtex"}="latex3"; -$texlive{"xypic"}="graphics2"; -$texlive{"yannisgr"}="fonts3"; -$texlive{"yfonts"}="latex3"; -$texlive{"yhmath"}="latex3"; -$texlive{"yi4latex"}="lang3"; -$texlive{"youngtab"}="latex3"; -$texlive{"ytex"}="formats3"; -$texlive{"zed-csp"}="latex3"; -$texlive{"zefonts"}="fonts2"; diff --git a/Master/texmf-doc/source/texlive/texlive-en/live4ht.cfg b/Master/texmf-doc/source/texlive/texlive-en/live4ht.cfg deleted file mode 100644 index 3435925813d..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/live4ht.cfg +++ /dev/null @@ -1,51 +0,0 @@ -% tex4ht configuration file for the TeX Live documentation. -% Accumulated over many years. Public domain. -% -% html specifies the main output format. -% info for extra debugging info in the log files. - -% have html in one piece (including footnotes). -\Preamble{charset=iso-8859-1,html,info,fn-in} - -% add extra stylesheet -\Configure{@HEAD}{\HCode{% -\Hnewline -\Hnewline -}} -% use png graphics as-is -\Configure{graphics*} - {png} - {\Needs{""}% - \Picture[pict]{\csname Gin@base\endcsname.png}% - } -% or LaTeX complains it is missing. -\begin{document} - -\EndPreamble - -% simplify output for HTML. We leave TeX and LaTeX alone, since tex4ht -% actually does the lowered E (and raised A) in CSS. -\def\OMEGA{Omega} -\def\LaTeXe{LaTeX2e} -\def\eTeX{e-\TeX} -\def\acro#1{#1} -\def\MF{Metafont} -\def\BibTeX{BibTeX} -\def\warningbox{} -\def\endwarningbox{} - -\newif\ifhackliterals -\ifx\tldocenglish\undefined \else \hackliteralstrue \fi -\ifx\tldocrussian\undefined \else \hackliteralstrue \fi -\ifx\tldocgerman\undefined \else \hackliteralstrue \fi -% -\ifhackliterals - % these definitions cause "missing } inserted" at \end{tabularx} in - % French and Czech. don't know why. - % - % don't make these into links, as happens with \path. We only have a couple - % special characters that actually occur. - \def\dirname{\texttt\bgroup\catcode`\$=12 \catcode`\_=12 \finishliteral} - \def\finishliteral#1{#1\egroup} - \let\filename=\dirname -\fi diff --git a/Master/texmf-doc/source/texlive/texlive-en/tex-live.css b/Master/texmf-doc/source/texlive/texlive-en/tex-live.css deleted file mode 100644 index 5062bc0d229..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/tex-live.css +++ /dev/null @@ -1,44 +0,0 @@ -/* $Id$ - Simple CSS for TeX Live that adds margins and a little color. - original by Bzyl Wlodzimierz, edited by Karl Berry, 2005. - Public domain. */ - -html { - // top left bottom right - margin: 15pt 15pt 15pt 15pt; - background: rgb(255,255,224); -} - -body { - margin: 0 5pt 0 5pt; - padding: 0; - //matw: background: rgb(224,255,224); - // (It looks better to me to have a consistent background --karl) -// fonts in browser are low resolution; -// therefore generated serif are poor quality, -// so they disturb reading (that is my opinion) - font-family: sans-serif; - font-style: normal; -} - -/* (It looks better to me to not vary colors at every level --karl) */ - -h3.sectionHead { - padding: 12pt 10pt 12pt 20pt; - //matw: background: rgb(192,224,255); - background: rgb(224,224,255); - color: rgb(0,0,32); -} - -h4.subsectionHead { - padding: 7pt 10pt 7pt 40pt; - background: rgb(224,224,255); - color: rgb(0,0,32); -} - -h5.subsubsectionHead { - padding: 3pt 10pt 3pt 40pt; - //matw: background: rgb(224,255,255); - background: rgb(224,224,255); - color: rgb(0,0,32); -} diff --git a/Master/texmf-doc/source/texlive/texlive-en/tex-live.sty b/Master/texmf-doc/source/texlive/texlive-en/tex-live.sty deleted file mode 100644 index 09956bd2a3e..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/tex-live.sty +++ /dev/null @@ -1,446 +0,0 @@ -% $Id$ -% TeX Live documentation style. Written by many people over many years. -% Public domain. -% -\NeedsTeXFormat{LaTeX2e}[1995/12/01] -\ProvidesPackage{tex-live}[2008/08/08 v1.6 TeX Live documentation style] -% -\RequirePackage{alltt} -\RequirePackage{array} -\RequirePackage{colortbl} -\RequirePackage{comment} -\RequirePackage{float} -\RequirePackage{graphicx} -\RequirePackage{longtable} -\RequirePackage{shortvrb} -\RequirePackage[normalem]{ulem} -\RequirePackage[obeyspaces]{url} -\RequirePackage{xspace} -% -\RequirePackage{lmodern} -\usepackage{textcomp}% including \textbullet -\def\p.{p.\,} - -% for a proper \acro command. -\RequirePackage{relsize} -%\DeclareRobustCommand{\acro}[1]{\textscale{.9}{#1}\@} -\def\acro#1{\textscale{.9}{#1}\@} -% -\RequirePackage{fancyvrb} -\DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=\normalsize} -\DefineVerbatimEnvironment{fverbatim}{Verbatim}{fontsize=\footnotesize} -\DefineVerbatimEnvironment{sverbatim}{Verbatim}{fontsize=\small} -\DefineVerbatimEnvironment{boxedverbatim} - {Verbatim}{fontsize=\scriptsize,frame=single} -\DefineVerbatimEnvironment{Verbatim}{Verbatim}{fontsize=\normalsize} -\def\verbatiminput#1{\VerbatimInput[fontsize=\scriptsize]{#1}} -\def\boxedverbatiminput#1{\VerbatimInput[frame=single,fontsize=\scriptsize]{#1}} -\def\listinginput#1#2{\VerbatimInput[fontsize=\scriptsize,firstnumber=#1,numbers=left]{#2}} -\MakeShortVerb\| -% -% -% Done with packages. -% -% Page layout. -\advance\textwidth by 1.1in -\advance\oddsidemargin by -.55in -\advance\evensidemargin by -.55in -% -\advance\textheight by 1in -\advance\topmargin by -.5in -\advance\footskip by -.5in -\pagestyle{headings} -% -% LaTeX parameters. -\renewcommand{\topfraction}{0.85} -\renewcommand{\floatpagefraction}{0.86} -\renewcommand{\textfraction}{0.1} -\renewcommand{\abovecaptionskip}{4pt} -\renewcommand{\belowcaptionskip}{4pt} -\setcounter{tocdepth}{3} -\setcounter{secnumdepth}{3} -\setcounter{topnumber}{5} -\setcounter{totalnumber}{5} -% -% linebreaking, etc. -\hbadness=4000 -\vbadness=4000 -\emergencystretch=.1\hsize -\relpenalty=500 -% -\def\slash{/\penalty\z@\hskip\z@skip } -% -% various sorts of names -\newcommand*{\pkgname}[1]{\textsf{#1}}% package name -\newcommand*{\optname}[1]{\texttt{#1}}% (package,class) option name -\newcommand*{\cmdname}[1]{\textsf{#1}}% command name -\newcommand*{\colname}[1]{\emph{#1}}% collection name -\newcommand*{\dirname}[1]{\path{#1}}% directory name -\newcommand*{\filename}[1]{\path{#1}}% file name -\newcommand*{\envname}[1]{\texttt{#1}}% environment variable name -\newcommand{\code}[1]{\texttt{#1}} -\newcommand{\file}[1]{\texttt{#1}} -\newcommand{\prog}[1]{\textsf{#1}}% same as \cmdname -\newcommand{\samp}[1]{`\texttt{#1}'} -\newcommand{\var}[1]{{\sl #1}}% not \textsl, for roman not typewriter slanted. -\newcommand{\ttvar}[1]{\texttt{\var{#1}}} -% -% underlined command input. -%\def\Ucom#1{% -% \uline{\rule[-.2\baselineskip]{0pt}{.9\baselineskip}\ttfamily #1}} -% bold command input -\def\Ucom#1{{\bfseries\ttfamily #1}} -% -% \CDref is for url's with a #, where we need to write the target url and -% displayed url separately in the input, due to catcode madness. -% (We could simplify/remove this next time, I think.) -\def\CDref#1#2{\texttt{#1}} -% -% \OnCD is currently for any other reference to a file or directory in -% the distribution. PDF readers only open .pdf files, though, so we -% should change this to only use \href for those. Or more likely use -% different macros in the source. -\def\OnCD#1{\href{../../../../#1}{\path{#1}}} -% -% \href incorrectly appends .pdf to anything without an extension; these -% definitions using \hyper@linkurl do not, but they fail for .pdf -% references -- which are the only ones that work anyway. So this is -% useless, in practice. -%\def\CDref#1#2{\hyper@linkurl{#2}{../../../../#1}} -%\def\OnCD#1{\hyper@linkurl{\path{#1}}{../../../../#1}} - -% GUI menu/button/tab sequence: -\def\guiseq#1{\textsf{#1}} -\def\arw{\unskip$\rightarrow$\ignorespaces} -% -% Special names. -\def\dpi{$\,$dpi\xspace} -\def\bs{{\protect\normalfont\ttfamily\char'134}} -\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} -\def\Q#1{\par\vskip6pt\leftline{#1}\par} -\def\hyph{-} -% -% many abbreviations. -\newcommand{\CS}{$\mathcal{C}\kern-.1667em\lower.5ex% - \hbox{$\mathcal{S}$}\kern-.075em $} -\def\AFMtoTFM{\cmdname{AFM2TFM}\null} -\def\bv{\emph{Baskerville}} -\let\BV=\bv -\def\Dash{\unskip\nobreak\thinspace---\thinspace\ignorespaces} -\def\dvicopy{\cmdname{dvicopy}} -\def\dvidvi{\cmdname{dvidvi}} -\def\dvips{\cmdname{dvips}} -\def\eTeX{$\varepsilon$-\TeX} -\def\fpTeX{\textrm{fp}\TeX\xspace} -\def\GFtoDVI{\cmdname{GFtoDVI}\null} -\def\GFtoPK{\cmdname{GFtoPK}\null} -\def\GFtype{\cmdname{GFtype}} -\def\GUI{\acro{GUI}\xspace} -\def\KPS{Kpathsea} -\def\La{La} -\def\OMEGA{$\Omega$} -\def\OzMF{OzMF} -\def\OzMP{OzMP} -\def\OzTeX{O\kern-.03em z\kern-.15em\TeX} -\def\PKtype{\cmdname{PKtype}} -\def\PLtoTF{\cmdname{PLtoTF}\null} -\def\ProTeXt{Pro\TeX t} -\def\teTeX{\textrm{te}\TeX\xspace} -\def\TeXLive{\TeX{} Live\xspace} -\def\TFtoPL{\cmdname{TFtoPL}\null} -\def\TK{\TeX\ Collection} -\let\TL=\TeXLive -\def\TypeI{Type~1} -\def\VFtoVP{\cmdname{VFtoVP}\null} -\def\VPtoVF{\cmdname{VPtoVF}\null} -\def\Thanh{H\`an~Th\ifx % get Unicode char in tex4ht's HTML output - \HCode\UnDef\^e\llap{\raise 0.5ex\hbox{\'{}}}\else - \HCode{\string&\#x1EBF;}\fi~Th\`anh} -\def\XEmTeX{\textrm{XEm}\TeX\xspace} -\def\XEmacs{\textrm{XEmacs}\xspace} -\def\XeTeX{Xe\TeX\xspace} -\def\Webc{Web2C} -\providecommand*{\CD}{\acro{CD}\xspace} -\providecommand*{\CTAN}{\acro{CTAN}\xspace} -\providecommand*{\DVD}{\acro{DVD}\xspace} -\providecommand*{\GNU}{\acro{GNU}\xspace} -\providecommand*{\HTML}{\acro{HTML}\xspace} -\providecommand*{\ISO}{\acro{ISO}\xspace} -\providecommand*{\MacOSX}{Mac\,\acro{OS\,X}\xspace} -\providecommand*{\PS}{Post\-Script\xspace} -\providecommand*{\TDS}{\acro{TDS}\xspace} -\providecommand*{\dvi}{\acro{DVI}\xspace} -\providecommand*{\web}{\texttt{WEB}\xspace} - -% Include an image. -% #1 - name of image (pictures/#1.jpg, always .jpg please) -% #2 - bb for html -% #3 - width for TeX -% -\def\tlimage#1#2#3{% - \ifnum \Status=2 % html, want relative path in output - \includegraphics[#2]{../../general/texlive-common/pictures/#1.jpg} - \else % not html, handled by TEXINPUTS in Makefile - \includegraphics[width=#3]{pictures/#1.jpg} - \fi - \\[5mm] -} - -\def\tlpng#1#2{% - \ifnum \Status=2 % html, want relative path in output - \includegraphics[bb=0 0 1 1]{#1.png}% - \else % not html, handled by TEXINPUTS in Makefile - \includegraphics[width=#2]{#1.png}% - \fi -} -% -% description-like environment that uses tt instead of bf, and doesn't -% go to the left margin. Without the \hfil, get an underfull box. -% Don't know why \descriptionlabel doesn't. -% -\newenvironment{ttdescription} - {\begin{list}{label must be supplied}{% - \itemsep=0pt % these lists tend to have short descriptions - \parindent=0pt - \let\makelabel=\ttdescriptionlabel}}% - {\end{list}} -\newcommand*\ttdescriptionlabel[1]{\hspace\labelsep - \normalfont\ttfamily #1\hfil} -% -% Likewise, for commands using sans serif. -\newenvironment{cmddescription} - {\begin{list}{label must be supplied}{% - \itemsep=0pt - \let\makelabel=\cmddescriptionlabel}}% - {\end{list}} -\newcommand*\cmddescriptionlabel[1]{\hspace\labelsep - \normalfont\sffamily #1\hfil} - -% General squeezed itemize. -\newenvironment{itemize*}% - {\begin{itemize}% - \setlength{\itemsep}{0pt}% - \setlength{\parskip}{0pt}}% - {\end{itemize}} - -\newsavebox{\wbox} -\newenvironment{warningbox} - {\begin{lrbox}{\wbox} - \begin{minipage}{.95\textwidth}} - {\end{minipage}\end{lrbox}\fbox{\usebox{\wbox}}} -% -% lrbox is used as a representation marking. I changed it to -% lrBox in tne source file, to get closer to logical marking -\newsavebox{\mylrbox} -\newenvironment{lrBox} - {\begin{lrbox}{\mylrbox}} - {\end{lrbox}} - - -% emacs-page output setup -% -\ifx \HCode\UnDef - \providecommand{\Status}{0}% running TeX -\else - \providecommand{\Status}{2}% running TeX4ht -\fi -%\typeout{Status is \Status} -% -\newif\ifSingleColumn -% -% By default, we won't be creating hyperlinks. -\def\href#1#2{#2} -\def\hypertarget#1#2{} -\def\email#1{\href{mailto:#1}{\path{#1}}} % \path comes from url -\def\htmlanchor#1{} -% -\definecolor{hypercolor}{rgb}{0.5,0.0,0.5} % purplish external links. -% -% -\ifcase\Status - % \Status = 0 - \typeout{TeX Live documentation in DVI format} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - \or - % \Status = 1 - \typeout{TeX Live documentation in PDF format} - \RequirePackage[breaklinks, - colorlinks,linkcolor=hypercolor,citecolor=hypercolor, - urlcolor=hypercolor,filecolor=hypercolor, - bookmarksopen, - %pdfstartview={FitBH -320000}, % fails with acrobat7 - hyperindex] - {hyperref} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - \or - % \Status = 2 - \typeout{TeX Live documentation in HTML format} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - % read our config file, live4ht.cfg; q.v., for more definitions. - % hyperref load must come after the tex4ht load. - \RequirePackage[live4ht]{tex4ht} - \RequirePackage[tex4ht]{hyperref} \hyperlinkfileprefix{} - % definitions need simplifying for TeX4ht to make relative paths work. - \def\CDref#1#2{\href{../../../../#1}{#2}} - \def\OnCD#1{\href{../../../../#1}{#1}} - \def\htmlanchor#1{\HCode{} - \or - % \Status = 3 - \typeout{TeX Live documentation as a Baskerville issue} - \@ifundefined{Fonts}% - {\RequirePackage{ae}}% - {\RequirePackage[T1]{\Fonts}} - \RequirePackage{bvoutln}% outline of baskerville - \SingleColumnfalse - \RequirePackage{multicol} - \or - % \Status = 4 - \typeout{TeX Live documentation as a TUB article} - \@ifundefined{Fonts}% - {\RequirePackage{ae}}% - {\RequirePackage[T1]{\Fonts}} - \SingleColumnfalse - \newenvironment{multicols}[1]{}{} -\fi -% -\ifnum \Status=4 -\else - \RequirePackage{texnames} - \providecommand\TeXXeT{\TeX-{}-% - \kern-.1emX\kern-.125em\lower.5ex\hbox{E}\kern-.1667emT\@} - \def\MP{MetaPost} - \let\mf\MF - \newcommand\ConTeXt{C\kern-.0333emon\-\kern-.0667em\TeX\kern-.0333emt} - \newcommand\MIKTEX{MiK\kern-.025em \TeX}% per www.miktex.org - % from pictex.tex: - \ifx\PiC\undefined \def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC} \fi - \ifx\PiCTeX\undefined \def\PiCTeX{\PiC\kern-.11em\TeX} \fi -\fi -% -% hacking at sections etc., to pay attention to baskerville status -\newcommand{\@condend@multicols}{% - \ifSingleColumn - \else - \def\@tempa{multicols}% - \ifx\@tempa\@currenvir - \end{multicols}% - \fi - \fi -} -\let\Section\section -\renewcommand{\section}{% - \@ifstar - {\Section*}% - {% - \@condend@multicols - \@dblarg\@full@section - }% -} -\def\@full@section[#1]#2{% - \Section[#1]{#2}% - \ifSingleColumn\else\begin{multicols}{2}\fi -} -\let\SubSection\subsection -\renewcommand{\subsection}{% - \@ifstar{\SubSection*}% - {% - \@condend@multicols - \@dblarg\@full@subsection - } -} -\def\@full@subsection[#1]#2{% - \SubSection[#1]{#2}% - \ifSingleColumn\else\begin{multicols}{2}\fi -} - -% calm things down a bit if we're in a multiple-column version -\ifSingleColumn -\else - \def\@listI{\leftmargin\leftmargini - \parsep \z@ - \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ - \itemsep \z@ \@plus .1\p@ - } - \let\@listi\@listI - \@listi - \def\@listii{\leftmargin\leftmarginii - \labelwidth\leftmarginii\advance\labelwidth-\labelsep - \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ - \parsep \z@ - \itemsep \z@ \@plus .1\p@ - } - \def\@listiii{\leftmargin\leftmarginiii - \labelwidth\leftmarginiii\advance\labelwidth-\labelsep - \topsep 1\p@ \@plus 1\p@ \@minus 1\p@ - \parsep \z@ - \partopsep \z@ - \itemsep \topsep - } - \def\@listiv{\leftmargin\leftmarginiv - \labelwidth\leftmarginiv\advance\labelwidth-\labelsep - } - \def\@listv{\leftmargin\leftmarginv - \labelwidth\leftmarginv\advance\labelwidth-\labelsep - } - \def\@listvi{\leftmargin\leftmarginvi - \labelwidth\leftmarginvi\advance\labelwidth-\labelsep - } -\fi -% -% array package stuff -\def\arraybackslash{\let\\=\@arraycr} -\newcolumntype{P}[1]{>{\raggedright\arraybackslash}p{#1}} -% -% shaded rows (using facilities of colortbl) -% -\definecolor{pale}{gray}{.9} -\newcount\colrow -\gdef\RowColor{pale} -\def\SetRowColor{% - \rowcolor{\RowColor}% - \global\advance\colrow by1\relax - \ifodd\colrow - \gdef\RowColor{pale}% - \else - \gdef\RowColor{white}% - \fi -} -% redefine to hack up a reference even though we don't need it... -\renewcommand\@bibitem[1]{\if@filesw \immediate\write\@auxout - {\string\bibcite{#1}{?}}\fi\ignorespaces} -% -% \unknownTeXlive is a dummy texlive entry for the biblio -\newcommand\unknownTeXlive[2][\relax]{\textbf{\textsc{unknown}}% - \global\@all@unknown\expandafter{\the\@all@unknown{#2}}% -} -\newtoks\@all@unknown -\global\@all@unknown{} -\AtEndDocument{\@message@unknowns} -\def\@message@unknowns{\edef\@tempa{\the\@all@unknown}% - \ifx\@tempa\@empty - \else - \def\@tempa{*** TeX live package location of }% - \expandafter\@output@unknowns\the\@all@unknown\@empty - \fi -} -\def\@output@unknowns#1{\edef\@tempb{#1}% - \ifx\@tempb\@empty - \typeout{ unknown}% - \else - \message{\@tempa#1,}% - \def\@tempa{}% - \expandafter\@output@unknowns - \fi -} - - -% Silence font warnings about no bold typewriter in LM. -\def\@font@warning#1{}% - -% Silence hyperref warnings about \kern. -\def\HyPsd@Warning#1{}% - -\endinput diff --git a/Master/texmf-doc/source/texlive/texlive-en/texlive-en.tex b/Master/texmf-doc/source/texlive/texlive-en/texlive-en.tex deleted file mode 100644 index 24fbb5d1c1b..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-en/texlive-en.tex +++ /dev/null @@ -1,2954 +0,0 @@ -% $Id: live.tex 9531 2008-07-13 21:12:58Z siepo $ -% TeX Live documentation. Originally written by Sebastian Rahtz and -% Michel Goossens, now maintained by Karl Berry and others. -% Public domain. -% -\documentclass{article} -\let\tldocenglish=1 % for live4ht.cfg -\usepackage{tex-live} -\usepackage[latin1]{inputenc} % translators: use your preferred encodings. -\usepackage[T1]{fontenc} - -\begin{document} - -\title{% - {\huge \textit{The \TeX\ Live Guide}\\\smallskip}% - {\LARGE \textsf{\TL{} 2008}}% -} - -\author{Karl Berry, editor \\[3mm] - \url{http://tug.org/texlive/} - } - -\date{September 2008} - -\maketitle - -\begin{multicols}{2} -\tableofcontents -%\listoftables -\end{multicols} - -\section{Introduction} -\label{sec:intro} - -\subsection{\TeX\ Live and the \TeX\ Collection} - -This document describes the main features of the \TL{} software -distribution\Dash \TeX{} and related programs for \GNU/Linux -and other Unix flavors, \MacOSX, and Windows systems. - -You may have acquired \TL{} by downloading, or on the \TK{} \DVD, -which \TeX{} usergroups distribute among their members. Section -\ref{sec:tl-coll-dists} briefly describes the contents of this \DVD. -Both \TL{} and the \TK{} are cooperative efforts by the \TeX{} user -groups. This document mainly describes \TL{} itself. - -\TL{} includes executables for \TeX{}, \LaTeXe{}, \ConTeXt, -\MF, \MP, \BibTeX{} and many other programs; an extensive collection -of macros, fonts and documentation; and support for typesetting in -many different scripts from around the world. - -\TL{} packages are regularly updated from -\acro{CTAN}: \url{http://www.ctan.org}. - -For a brief summary of the major changes in this edition of \TL{}, -see the end of the document, section~\ref{sec:history} -(\p.\pageref{sec:history}). - -\subsection{Operating system support} -\label{sec:os-support} - -\TL{} contains binaries for many Unix-based architectures, -including \MacOSX. The included sources should enable installation -on platforms for which we do not have binaries. - -As to Windows: only Windows 2000 and later are supported. Windows -9\textit{x}, ME and NT have been dropped. Because of this -change, Windows requires much less special treatment compared to -the Unix systems. There are no 64-bit executables for Windows, but the -32-bit executables should run on 64-bit systems. - -See section~\ref{sec:tl-coll-dists} for alternate solutions -for Windows and \MacOSX. - -\subsection{Basic installation of \protect\TL{}} -\label{sec:basic} - -You can install \TL{} either from \DVD{} or over the Internet. The net -installer itself is small, and downloads everything requested from the -Internet. The net installer is an attractive option if you need only a -fraction of the complete \TL. - -The \DVD{} installer lets you install to a local disk, but you can -also run \TL{} directly from the \DVD{} (or from a \DVD{} image, if -your system supports that). - -\noindent This is described in the -installation sections following, but here is a quick start: - -\begin{itemize*} - -\item The installation script is named \filename{install-tl}. It can - operate in both a \GUI{} mode (default for Windows) and - a text mode (default for everything else). You can force one mode or - the other with the options \code{-gui} and \code{-no-gui}, respectively. - -\item One of the installed items is a new program, the `\TL\ Manager', - named \prog{tlmgr}. Like the installer, it can be used in both \GUI{} - mode and in text mode. You can use it to install and uninstall - packages and do various configuration tasks. - -\end{itemize*} - - -\subsection{Getting help} -\label{sec:help} - -The \TeX{} community is both active and friendly, and most serious -questions end up getting answered. However, the support is informal, -done by volunteers and casual readers, so it's especially important that -you do your homework before asking. (If you prefer guaranteed -commercial support, you can forego \TL{} completely and purchase a -vendor's system; \url{http://tug.org/interest.html#vendors} has a list.) - -Here is a list of resources, approximately in the order we recommend -using them: - -\begin{description} -\item [Getting Started] If you are new to \TeX, the web page -\url{http://tug.org/begin.html} gives a brief introduction to the system. - -\item [\TeX{} \acro{FAQ}] The \TeX{} \acro{FAQ} is a huge compendium - of answers to all sorts of questions, from the most basic to the - most arcane. It is included on \TL{} in - \OnCD{texmf-doc/doc/english/FAQ-en/html/index.html}, and is available - on the Internet through \url{http://www.tex.ac.uk/faq}. Please - check here first. - -\item [\TeX{} Catalogue] If you are looking for a specific package, -font, program, etc., the \TeX{} Catalogue is the place to look. It is a -huge collection of all \TeX{}-related items. See -\url{http://www.ctan.org/help/Catalogue/}. - -\item [\TeX{} Web Resources] The web page -\url{http://tug.org/interest.html} has many \TeX{}-related links, in -particular for numerous books, manuals, and articles on all aspects of -the system. - -\item [support archives] The two principal support forums are the -Usenet newsgroup \url{news:comp.text.tex} and the mailing list -\email{texhax@tug.org}. Their archives have years of past -questions and answers for your searching pleasure, via -\url{http://groups.google.com/group/comp.text.tex/topics} and -\url{http://tug.org/mail-archives/texhax}, respectively. And a general web -search, for example on \url{http://google.com}, never hurts. - -\item [asking questions] If you cannot find an answer, you can post to -\dirname{comp.text.tex} through Google or your newsreader, or to -\email{texhax@tug.org} through email. But before you post, -\emph{please} read this \acro{FAQ} entry, to maximize -your chances of getting a useful answer: -\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. - -\item [\TL{} support] If you want to report a bug or have -suggestions or comments on the \TL{} distribution, installation, or -documentation, the mailing list is \email{tex-live@tug.org}. However, -if your question is about how to use a particular program included in -\TL{}, please write to that program's maintainer or -mailing list. Often running a program with the \code{-{}-help} option -will provide a bug reporting address. - -\end{description} - -The other side of the coin is helping others who have questions. Both -\dirname{comp.text.tex} and \code{texhax} are open to anyone, so feel -free to join, start reading, and help out where you can. - - -% don't use \TL so the \uppercase in the headline works. Also so -% tex4ht ends up with the right TeX. Likewise the \protect's. -\section{Overview of \protect\TeX\protect\ Live} -\label{sec:overview-tl} - -This section describes the contents of \TL{} and the \TK{} of which it -is a part. - -\subsection{The \protect\TeX\protect\ Collection: \TL, pro\TeX{}t, Mac\TeX} -\label{sec:tl-coll-dists} - -The \TK{} \DVD{} comprises the following: - -\begin{description} - -\item [\TL] A complete \TeX{} system which can be run live or - installed to disk. - -\item [Mac\TeX] for \MacOSX, this adds a native \MacOSX\ installer and other -Mac applications to \TL{}. Its home page is -\url{http://www.tug.org/mactex/}. - -\item [pro\TeX{}t] An enhancement of the \MIKTEX\ distribution for Windows, -\ProTeXt\ adds a few extra tools to \MIKTEX, and simplifies -installation. It is entirely independent of \TL{}, and has its own -installation instructions. The \ProTeXt\ home page is -\url{http://tug.org/protext}. - -\item [CTAN] A snapshot of the \CTAN{} repository. - -\item [\texttt{texmf-extra}] A directory with assorted additional packages. - -\end{description} - -\CTAN{}, \pkgname{protext}, and \dirname{texmf-extra} do not -necessarily follow the same copying conditions as \TL{}, so be careful -when redistributing or modifying. - - -\subsection{Top level \TL{} directories} -\label{sec:tld} - -Here is a brief listing and description of the top level directories in -the \TL{} distribution. On the \pkgname{live} \DVD, the entire \TL{} -hierarchy is in a subdirectory \dirname{texlive}, not at the top -level of the disc. - -\begin{ttdescription} -\item[bin] The \TeX{} system programs, arranged by platform. -% -\item[readme.html] Web pages with a quick introduction and useful links, -in various languages. -% -\item[source] The source to all included programs, including the main \Webc{} - \TeX{} and \MF{} distributions. -% -\item[support] Various auxiliary packages and programs. These are - \emph{not} installed automatically. This includes - assorted editors and \TeX\ shells. -% -\item[texmf] See \dirname{TEXMFMAIN} below. -% -\item[texmf-dist] See \dirname{TEXMFDIST} below. -% -\item[texmf-doc] Tree for self-contained pure documentation, arranged by - language. -% -\item[tlpkg] Scripts, programs and data for managing the - installation. It also contains private copies of - Perl and Ghostscript for Windows, which are invisible outside \TL, - and a new Windows PostScript viewer PSView. -\end{ttdescription} - -In addition to the directories above, the installation scripts and -\filename{README} files (in various languages) are at the top level of -the distribution. - -The \dirname{texmf-doc} directory contains documentation which does -not belong to any particular package or program. The documentation -for the programs (manuals, man pages, Info files) is in -\dirname{texmf/doc}. The documentation for \TeX\ packages and -formats is in \dirname{texmf-dist/doc}. You can use the -\cmdname{texdoc} or \cmdname{texdoctk} programs to find any -documentation wherever it is located. The comprehensive links in -the top-level file \OnCD{doc.html} may also be helpful. - -This \TL\ documentation itself is in \dirname{texmf-doc} and is -available in several languages: - -\begin{itemize*} -\item{Simplified Chinese:} \OnCD{texmf-doc/doc/chinese/texlive-zh-cn} -\item{Czech/Slovak:} \OnCD{texmf-doc/doc/czechslovak/texlive-cz} -\item{English:} \OnCD{texmf-doc/doc/english/texlive-en} -\item{French:} \OnCD{texmf-doc/doc/french/texlive-fr} -\item{German:} \OnCD{texmf-doc/doc/german/texlive-de} -\item{Polish:} \OnCD{texmf-doc/doc/polish/texlive-pl} -\item{Russian:} \OnCD{texmf-doc/doc/russian/texlive-ru} -\end{itemize*} - -\subsection{Overview of the predefined texmf trees} -\label{sec:texmftrees} - -This section lists all predefined variables specifying the texmf trees -used by the system, and their intended purpose, and the default -layout of a \TL{} system. The command \texttt{texconfig conf} shows -you the values of these variables, so that you can easily find out -how they map to directory names in your installation. - -\begin{ttdescription} -\item [TEXMFMAIN] The tree which holds vital parts of the system - such as helper scripts (e.g., \verb+web2c/mktexdir+) and other - support files and their documentation. Does not include - \TeX\ formats and packages. -\item [TEXMFDIST] The tree which holds the main set of macro packages, - fonts, etc., as originally distributed. -\item [TEXMFLOCAL] The tree which administrators can use for system-wide - installation of additional or updated macros, fonts, etc. -\item [TEXMFHOME] The tree which users can use for their own individual - installations of additional or updated macros, fonts, etc. - The expansion of this variable dynamically adjusts for each user to - their own individual directory. -\item [TEXMFCONFIG] The tree used by the utilities - \verb+texconfig+, \verb+updmap+, and \verb+fmtutil+ to store modified - configuration data. Under \envname{TEXMFHOME} by default. -\item [TEXMFSYSCONFIG] The tree used by the utilities - \verb+texconfig-sys+, \verb+updmap-sys+, and \verb+fmtutil-sys+ to - store modified configuration data. -\item [TEXMFVAR] The tree used by \verb+texconfig+, \verb+updmap+ and - \verb+fmtutil+ to store (cached) runtime data such as format files and - generated map files. Under \envname{TEXMFHOME} by default. -\item [TEXMFSYSVAR] The tree used by \verb+texconfig-sys+, - \verb+updmap-sys+ and \verb+fmtutil-sys+, and also by \verb+tlmgr+, to - store (cached) runtime data such as format files and generated map files. -\end{ttdescription} - -\noindent -The default layout is: -\begin{description} - \item[system-wide root] can span multiple \TL{} releases: - \begin{ttdescription} - \item[2007] A previous release. - \begin{ttdescription} - \item [...] - \end{ttdescription} - \item[2008] The current release. - \begin{ttdescription} - \item [bin] ~ - \begin{ttdescription} - \item [i386-linux] \GNU/Linux binaries - \item [...] - \item [universal-darwin] \MacOSX binaries - \item [win32] Windows binaries - \end{ttdescription} - \item [texmf] This is \envname{TEXMFMAIN}. - \item [texmf-dist] \envname{TEXMFDIST} - \item [texmf-doc] \envname{TEXMFDOC} - \item [texmf-var] \envname{TEXMFSYSVAR} - \item [texmf-config] \envname{TEXMFSYSCONFIG} - \end{ttdescription} - \item [texmf-local] \envname{TEXMFLOCAL}, intended to be - retained from release to release. - \end{ttdescription} - \item[user's home] (\texttt{\$HOME} or - \texttt{\%USERPROFILE\%}) - \begin{ttdescription} - \item[.texlive2007] Privately generated and configuration data - for a previous release. - \item[.texlive2008] Privately generated and configuration data - for the current release. - \begin{ttdescription} - \item [texmf-var] \envname{TEXMFVAR} - \item [texmf-config] \envname{TEXMFCONFIG} - \end{ttdescription} - \item[texmf] \envname{TEXMFHOME} Personal macros. - \textit{etc.} - \end{ttdescription} -\end{description} - - -\subsection{Extensions to \protect\TeX} -\label{sec:tex-extensions} - -\TeX{} itself is frozen, apart from rare bug fixes. It is still present -in \TL\ as the program \prog{tex}, and will remain so in the -foreseeable future. \TL{} contains several extended versions of \TeX: - -\begin{description} - -\item [\eTeX] adds a set of new primitives -\label{text:etex} (related to macro expansion, character scanning, -classes of marks, additional debugging features, and more) and the -\TeXXeT{} extensions for bidirectional typesetting. In default mode, -\eTeX{} is 100\% compatible with ordinary \TeX. See -\OnCD{texmf-dist/doc/etex/base/etex_man.pdf}. - -\item [pdf\TeX] builds on the \eTeX\ extensions, adding support for -writing \acro{PDF} output as well as \dvi{}. This is the program -invoked for most formats, e.g., \prog{etex}, \prog{latex}, -\prog{pdflatex}. See \url{http://www.pdftex.org/}. -\OnCD{texmf-dist/doc/pdftex/manual/pdftex-a.pdf} for the manual, and -\OnCD{texmf-dist/doc/pdftex/manual/samplepdf/samplepdf.tex} for example usage -of some of its features. - -\item [Lua\TeX] is the designated successor of pdf\TeX, with which it -is intended to be backward-compatible. It should also supersede Aleph, -see below. The incorporated Lua interpreter (see -\url{http://www.lua.org/}) enables elegant solutions for many thorny -\TeX{} problems. When called as \filename{texlua}, it functions as a -standalone Lua interpreter, and is already used as such within \TL. See -\url{http://www.luatex.org/} and -\OnCD{texmf-dist/doc/luatex/luatexref-t.pdf}. - -\item [\XeTeX] adds support for Unicode input and OpenType- and system -fonts, implemented using standard third-party libraries. See -\url{http://scripts.sil.org/xetex}. - -\item [\OMEGA\ (Omega)] is based on Unicode (16-bit characters), thus -supports working with almost all the world's scripts simultaneously. It -also supports so-called `\OMEGA{} Translation Processes' (\acro{OTP}s), -for performing complex transformations on arbitrary input. See -\OnCD{texmf-dist/doc/omega/base/doc-1.8.tex} (not completely up-to-date). - -\item [Aleph] combines the \OMEGA\ and \eTeX\ extensions. -See \OnCD{texmf-dist/doc/aleph/base} for some minimal documentation. - -\end{description} - - -\subsection{Other notable programs in \protect\TL} - -Here are a few other commonly-used programs included in \TL{}: - -\begin{cmddescription} - -\item [bibtex] bibliography support. - -\item [makeindex] index support. - -\item [dvips] convert \dvi{} to \PS{}. - -\item [xdvi] \dvi{} previewer for the X Window System. - -\item [dvilj] \dvi{} drive for the HP LaserJet family. - -\item [dv2dt, dt2dv] convert \dvi{} to/from plain text. - -\item [dviconcat, dviselect] cut and paste pages -from \dvi{} files. - -\item [dvipdfmx] convert \dvi{} to \acro{PDF}, an alternative approach -to pdf\TeX\ (mentioned above). See the \pkgname{ps4pdf} and -\pkgname{pdftricks} packages for still more alternatives. - -\item [psselect, psnup, \ldots] \PS{} -utilities. - -\item [lacheck] \LaTeX{} syntax checker. - -\item [texexec, texmfstart] Con\TeX{}t and \acro{PDF} processor. - -\item [tex4ht] \TeX{} to \acro{HTML} (and \acro{XML} and more) converter. - -\end{cmddescription} - - -\subsection{Fonts in \protect\TL} -\label{sec:tl-fonts} - -\TL{} comes with many high-quality scalable fonts. See -\url{http://tug.org/fonts} and -\OnCD{texmf-doc/doc/english/free-math-font-survey}. - - - -\section{Installation} -\label{sec:install} - -\subsection{Starting the installer} -\label{sec:inst-start} - -To start with, get the \TK{} \DVD{} or download the \TL{} net installer, -and locate the installer script: \filename{install-tl} for Unix, -\filename{install-tl.bat} for Windows. - -\begin{description} -\item [Net installer:] Download from \CTAN, under -\dirname{systems/texlive/tlnet}; the url -\url{http://mirror.ctan.org/systems/texlive/tlnet} will automatically -redirect to a nearby, up-to-date, mirror. You can retrieve either -\filename{install-tl.zip} which can be used under Unix and Windows and -\filename{install-unx.tar.gz} which is considerably smaller, for Unix -only. After unpacking, \filename{install-tl} and -\filename{install-tl.bat} will be in the \dirname{install-tl} -subdirectory. - -\item [\TeX{} Collection \DVD:] go to its \dirname{texlive} -subdirectory. Under Windows, the installer should start automatically -when you insert the \DVD. You can get the \DVD\ by becoming a member of -a \TeX\ user group (highly recommended, -\url{http://tug.org/usergroups.html}), or purchasing it separately -(\url{http://tug.org/store}), or burning your own from the \ISO\ -image (\url{http://tug.org/texlive/acquire.html}). - -\end{description} -The following sections explain in more detail. - -\subsubsection{Unix} - -\begin{figure}[tb] -\begin{boxedverbatim} -======================> TeX Live installation procedure <===================== - -=======> Note: Letters/digits in indicate menu items <======= -=======> for commands or configurable options <======= - - - Detected platform: Intel x86 with GNU/Linux - - binary systems: 1 out of 16 - - Installation scheme (scheme-full) - - Customizing installation scheme: - standard collections - language collections - 83 collections out of 84, disk space required: 1666 MB - - directories: - TEXDIR (the main TeX directory): - !! default location: /usr/local/texlive/2008 - !! is not writable, please select a different one! - TEXMFLOCAL (directory for site-wide local files): - /usr/local/texlive/texmf-local - TEXMFSYSVAR (directory for variable and automatically generated data): - /usr/local/texlive/2008/texmf-var - TEXMFSYSCONFIG (directory for local config): - /usr/local/texlive/2008/texmf-config - TEXMFHOME (directory for user-specific files): - ~/texmf - - options: - [ ] use letter size instead of A4 by default - [X] create all format files - [X] install macro/font doc tree - [X] install macro/font source tree - [ ] create symlinks in standard directories - - Install for running from DVD - -Other actions: - start installation to HD - help - quit - -Enter command: -\end{boxedverbatim} -\caption{Main text installer screen (\GNU/Linux)}\label{fig:text-main} -\end{figure} - -\begin{figure}[tb] -\tlpng{install-w32-main}{\linewidth} -\caption{Main \GUI{} installer screen (Windows)}\label{fig:gui-main} -\end{figure} - -\noindent -Below, \texttt{>} denotes the shell prompt; user input is -\Ucom{\texttt{bold}}. -Starting in a terminal window on a Unix-compatible system, the simplest -way: -\begin{alltt} -> \Ucom{cd /path/to/installer} -> \Ucom{perl install-tl} -\end{alltt} -(Or you can invoke \Ucom{perl /path/to/installer/install-tl}, or -\Ucom{./install-tl} if it stayed executable, etc.; we won't repeat all -these variations.) - -To install in \GUI\ mode (you'll need the \dirname{Perl/TK} module), use: -\begin{alltt} -> \Ucom{perl install-tl -gui} -\end{alltt} - -For a complete listing of the various options: -\begin{alltt} -> \Ucom{perl install-tl -help} -\end{alltt} - -\textbf{Warning about Unix permissions:} Your \code{umask} at the time -of installation will be respected by the \TL{} installer. Therefore, if -you want your installation to be usable by users other than you, make -sure your setting is sufficiently permissive, for instance, \code{umask -002}. For more information about \code{umask}, consult your system -documentation. - - -\subsubsection{Mac\,OS\,X} - -As mentioned in section~\ref{sec:tl-coll-dists}, a separate distribution -is prepared for \MacOSX, named Mac\TeX\ (\url{http://tug.org/mactex}). -We recommend using the native Mac\TeX\ installer instead of the \TL\ -installer on \MacOSX, because the native installer can make a few -Mac-specific adjustments, in particular to allow easily switching -between the various \TeX\ distributions for \MacOSX\ (Mac\TeX, gw\TeX, -Fink, MacPorts, \ldots). - -Mac\TeX\ is firmly based on \TL, and the main \TeX\ trees are precisely -the same. It does add a few extra folders with Mac-specific -documentation and applications. - - -\subsubsection{Windows} - -If you are using the net installer, or the \DVD\ installer failed to -start automatically, double-click \filename{install-tl.bat}. - -You can also start the installer from the command-prompt. Below, -\texttt{>} denotes the prompt; user input is \Ucom{\texttt{bold}}. If -you are in the installer directory, run just: -\begin{alltt} -> \Ucom{install-tl} -\end{alltt} - -Or you can invoke it with an absolute location, such as: -\begin{alltt} -> \Ucom{D:\bs{}texlive\bs{}install-tl} -\end{alltt} -for the \TK\ \DVD, supposing that \dirname{D:} is the optical drive. - -To install in text mode, use: -\begin{alltt} -> \Ucom{install-tl -no-gui} -\end{alltt} - -For a complete listing of the various options: -\begin{alltt} -> \Ucom{install-tl -help} -\end{alltt} - -\subsubsection{The text installer} - -Figure~\ref{fig:text-main} displays the main text mode screen under -Unix. - -This is only a command-line installer; there is no cursor support at -all. For instance, you cannot tab around checkboxes or input fields. -You just type something (case-sensitive) at the prompt and press the -Enter key, and then the entire terminal screen will be rewritten, with -adjusted content. - -The text installer interface is this primitive for a reason: it -is designed to run on as many platforms as possible, even with a -very barebones Perl (for Windows, a Perl subset is included). - -\subsubsection{The graphical installer} - -Figure~\ref{fig:gui-main} displays the graphical installer under -Windows. Most differences in available options are due to this -screenshot being from Windows, and the previous text screen being -from \GNU/Linux. - -\subsection{Running the installer} -\label{sec:runinstall} - -The installer is intended to be mostly self-explanatory. Still, a few -quick notes about the various options and submenus: - -\subsubsection{Binary systems menu (Unix only)} -\label{sec:binary} - -\begin{figure}[tbh] -\begin{boxedverbatim} -Available sets of binaries: -=============================================================================== - - a [ ] alpha-linux DEC Alpha with GNU/Linux - b [ ] amd64-freebsd x86_64 with FreeBSD - c [ ] hppa-hpux HP-UX - d [ ] i386-freebsd Intel x86 with FreeBSD - e [X] i386-linux Intel x86 with GNU/Linux - f [ ] i386-openbsd Intel x86 with OpenBSD - g [ ] i386-solaris Intel x86 with Sun Solaris - h [ ] mips-irix SGI IRIX - i [ ] powerpc-aix PowerPC with AIX - j [ ] powerpc-linux PowerPC with GNU/Linux - k [ ] sparc-linux Sparc with GNU/Linux - l [ ] sparc-solaris Sparc with Solaris - m [ ] universal-darwin universal binaries for MacOSX/Darwin - o [ ] win32 Windows - p [ ] x86_64-linux x86_64 with GNU/Linux -\end{boxedverbatim} -\caption{Binaries menu}\label{fig:bin-text} -\end{figure} - -Figure~\ref{fig:bin-text} displays the text mode binaries menu. By -default, only the binaries for your current platform will be installed. -From this menu, you can select installation of binaries for other -architectures as well. This can be useful if you are sharing a \TeX\ -tree across a network of heterogenous machines, or for a dual-boot -system. - -\subsubsection{Selecting what is going to be installed} -\label{sec:components} - -\begin{figure}[tbh] -\begin{boxedverbatim} -Select a scheme: -=============================================================================== - - a [ ] TeX Live basic scheme - b [ ] TeX Live scheme for ConTeXt - c [X] TeX Live full scheme - d [ ] GUST TeX Live scheme - e [ ] GUTenberg TeX Live scheme - f [ ] TeX Live medium scheme - g [ ] TeX Live minimal scheme - h [ ] TeX Live for Omega users - i [ ] teTeX scheme - j [ ] XML typesetting scheme -\end{boxedverbatim} -\caption{Scheme menu}\label{fig:scheme-text} -\end{figure} - -Figure~\ref{fig:scheme-text} displays the \TL\ scheme menu; from here, -you choose a ``scheme'', which is an overall set of package collections. -The default \optname{full} scheme installs everything available, but you -can also choose the \optname{basic} scheme for a small system, -\optname{minimal} for testing purposes, and \optname{medium} or -\optname{teTeX} to get something in between. There are also various -specialized and country-specific schemes. - -\begin{figure}[tbh] -\tlpng{stdcoll}{.7\linewidth} -\caption{Collections menu (Linux)}\label{fig:collections-gui} -\end{figure} - -You can refine your scheme selection with the `standard collections' and -`language collections' menus (figure~\ref{fig:collections-gui}, shown in -\GUI\ mode for a change). - -Collections are one level more detailed than schemes\Dash in essence, a -scheme consists of several collections, a collection consists of one or -more packages, and a package (the lowest level grouping in \TL) contains -the actual \TeX\ macro files, font files, and so on. - -If you want more control than the collection menus provide, you can use -the \prog{tlmgr} program after installation (see -section~\ref{sec:tlmgr}); using that, you can control the installation -at the package level. - -\subsubsection{Directories} -\label{sec:directories} - -The default layout is described in section~\ref{sec:texmftrees}, -\p.\pageref{sec:texmftrees}. The default location of -\dirname{TEXDIR} is different between Windows -(|%PROGRAMFILES%\texlive\2008|) and Unix -(\dirname{/usr/local/texlive/2008}). - -The main reason to change this default is if you lack write permission -for the default location. You don't have to be root or adminstrator to -install \TL, but you do need write access to the target directory. - -A logical alternate choice is a directory under your home directory, -especially if you will be the sole user. Use -`|~|' to indicate this, as in `|~/texlive/2008|'. - -We recommend including the year in the name, to enable keeping different -releases of \TL{} side by side. (You may wish to make a -version-independent name such as \dirname{/usr/local/texlive-cur} via a -symbolic link, which you can then update after testing the new release.) - -Changing \dirname{TEXDIR} in the installer will also change -\dirname{TEXMFLOCAL}, \dirname{TEXMFSYSVAR} and -\dirname{TEXMFSYSCONFIG}. - -\dirname{TEXMFHOME} is the recommended location for personal -macro files or packages. The default value is |~/texmf|. In -contrast to \dirname{TEXDIR}, here a |~| is preserved in the -newly-written configuration files, since it usefully refers to the home -directory of each individual running \TeX. It expands to -\dirname{$HOME} on Unix and \verb|%USERPROFILE%| on Windows. - -\subsubsection{Options} -\label{sec:options} - -\begin{figure}[tbh] -\begin{boxedverbatim} -

use letter size instead of A4 by default: [ ] - create all format files: [X] - install font/macro doc tree: [X] - install font/macro source tree: [X] - create symlinks in standard directories: [ ] - binaries to: - manpages to: - info to: -\end{boxedverbatim} -\caption{Options menu (Unix)}\label{fig:options-text} -\end{figure} - -Figure~\ref{fig:options-text} displays the text mode options menu. -Three of the options here need mentioning: - -\begin{description} -\item[use letter size instead of A4 by default:] The usual default paper - size selection. Of course, individual documents can specify a specific - paper size, if desired. - -\item[create all format files:] Although unnecessary format files - take time to generate and disk space to store, it is still recommended - to leave this option checked: if you don't, then format files will be - generated in people's private \dirname{TEXMFVAR} tree as they are - needed. In that location, they will not be updated automatically if - (say) binaries or hyphenation patterns are updated in the - installation, and thus could end up with incompatible format files. - -\item[create symlinks in standard directories] (Unix only): - This option bypasses the need to change environment - variables. Without this option, \TL{} directories have to be added - to \envname{PATH}, \envname{MANPATH} and \envname{INFOPATH}. You will - need write permissions to the target directories. It is not - advisable to overwrite a \TeX\ system that came with your system - with this option. It is intended primarily for creating the links - in standard directories that are known to users, such as - \dirname{/usr/local/bin}, which don't already contain any - \TeX\ files. -\end{description} - -Now when all these settings are to your liking, you can type `I' to -start the installation process. When it is done, skip to -section~\ref{sec:postinstall} to read what else needs to be done, if -anything. - -\htmlanchor{runfromdvd} -\subsubsection{Set up for running from DVD{} (text mode only)} -\label{sec:fromdvd} - -Type `|V|' to select this option. This changes the main menu into something -like figure~\ref{fig:main-fromdvd}. -\begin{figure}[tbh] -\begin{boxedverbatim} -======================> TeX Live installation procedure <===================== - -=======> Note: Letters/digits in indicate menu items <======= -=======> for commands or configurable options <======= - - directories: - TEXDIRW (Writable root): - !! default location: /usr/local/texlive/2008 - !! is not writable, please select a different one! - TEXMFLOCAL (directory for site-wide local files): - /usr/local/texlive/texmf-local - TEXMFSYSVAR (directory for variable and automatically generated data): - /usr/local/texlive/2008/texmf-var - TEXMFSYSCONFIG (directory for local config): - /usr/local/texlive/2008/texmf-config - TEXMFHOME (directory for user-specific files): - ~/texmf - - options: - [ ] use letter size instead of A4 by default - [X] create all format files - - set up for installing to hard disk - -Other actions: - start installation for running from DVD - help - quit -\end{boxedverbatim} -\caption{The main menu with \optname{from DVD} - set}\label{fig:main-fromdvd} -\end{figure} - -Note the changes: all options about what to install have -disappeared, and the directories section now talks about -\dirname{TEXDIRW} or writable root. The symlinks option has also -disappeared. - -The installer will still create various directories and -configuration files, but won't copy \dirname{texmf}, -\dirname{texmf-dist} or \dirname{texmf-doc} to hard disk. - -Post-install configuration for Unix will be slightly more complicated, -because now the directory layout deviates from the default; see -section~\ref{sec:postinstall}. - -Due to time constraints, this option didn't make it into the \GUI{} -installer, but it is available both for Unix and for -Windows. Windows users have to start the installer from a command -prompt, see section~\ref{sec:cmdline}. - -Section \ref{sec:portable-unix} describes a more strictly portable -way to run \TL, which doesn't make or require changes in the -system's configuration, but doesn't allow any configuration either. - -\subsection{Command-line install options} -\label{sec:cmdline} - -Type -\begin{alltt} -> \Ucom{install-tl -help} -\end{alltt} -for a listing of command-line options. Either |-| or |--| can be used -to introduce option names. These are the more -interesting ones: - -\begin{ttdescription} -\item[-gui] If possible, use the \GUI{} installer. This requires the - Perl/Tk module (\url{http://tug.org/texlive/distro.html#perltk}); - if Perl/Tk is not available, installation continues in text mode. -\item[-no-gui] Force using the text mode installer, even under - Windows; you'll need this if you want a `from \DVD' installation, - since that is not available in \GUI{} mode. -\item[-lang {\sl LL}] Specify the installer interface - language as its standard two-letter code \textsl{LL}. Currently - supported languages: English (\texttt{en}, default), German - (\texttt{de}), French (\texttt{fr}), Dutch (\texttt{nl}), Polish - (\texttt{pl}), Slovenian (\texttt{sl}) and Vietnamese - (\texttt{vi}). The installer tries to determine the right language - itself but if it fails, or if the right language is not available, - then it uses English as a fallback. -\item[-profile {\sl profile}] The installer always writes a file - \filename{texlive.profile} to the \dirname{2008/tlpkg}- or - \dirname{tlpkg} subdirectory of your installation. This option tells - the installer to re-use such a profile file. Here's an excerpt: - \begin{fverbatim} -# texlive.profile written on Wed Jul 9 16:13:44 2008 UTC -# It will NOT be updated and reflects only the -# installation profile at installation time. -selected_scheme scheme-basic -TEXDIR /usr/local/texlive/2008 -TEXDIRW /usr/local/texlive/2008 -... -TEXMFSYSVAR /usr/local/texlive/2008/texmf-var -collection-basic 1 -... -option_symlinks 0 - \end{fverbatim} - Thus, using this option you can install in batch mode on - subsequent systems, reproducing the choices you made for the - original installation. -\item [-location {\sl url/path}] Specify a non-default source for - packages; see below. -\end{ttdescription} - -\subsubsection{The \optname{location} parameter} -\label{sec:location} - -The location value can be a url starting with \texttt{ftp:}, -\texttt{http:}, or \texttt{file:/} url, or a plain path. If the given -argument is on a local drive (either a path or a \texttt{file:/} url), -the installation type (compressed or live) is automatically determined: -if an \dirname{archive} subdirectory with \filename{.tar.lzma} files is -found then it will be used, even if uncompressed files are available as -well. - -When giving an \texttt{http:} or \texttt{ftp:} location, trailing -`\texttt{/}' characters and/or a trailing `\texttt{/tlpkg}' component -are ignored. For example, you could choose a particular \CTAN\ mirror -with something like: -\url{http://ctan.example.org/tex-archive/texlive/tlnet/2008}, -substituting of course a proper hostname and its particular top-level -\CTAN\ path (the list of \CTAN\ mirrors is maintained at -\url{http://ctan.org/mirrors}) for |ctan.example.org/tex-archive|. The -default is to pick a mirror automatically, using -\url{http://mirror.ctan.org}; in any case, the chosen host is used for -the entire download. - - -\subsection{Post-install actions} -\label{sec:postinstall} - -Some post-install may be required. - -\subsubsection{Windows} - -But on Windows, the installer takes care of everything. - -\subsubsection{If symlinks were created} - -If you elected to create symlinks in standard directories (mentioned in -section~\ref{sec:options}), then there is no need to edit environment -variables. - -\subsubsection{Environment variables for Unix} -\label{sec:env} - -The directory of the binaries for your platform must be added to -the search path. Each supported platform has its own subdirectory -under \dirname{TEXDIR/bin}. See figure~\ref{fig:bin-text} for the -list of subdirectories and corresponding platforms. - -You can also add the documentation man and Info directories to their -respective search paths, if you want the system tools to find them. - -For Bourne-compatible shells such as \prog{bash}, and using Intel x86 -GNU/Linux and a default directory setup as an example, the file to edit -might be \filename{$HOME/.profile} (or another file sourced by -\filename{.profile}, and the lines to add would look like this: - -\begin{sverbatim} -PATH=/usr/local/texlive/2008/bin/i386-linux:$PATH; export PATH -MANPATH=/usr/local/texlive/2008/texmf/doc/man:$MANPATH; export MANPATH -INFOPATH=/usr/local/texlive/2008/texmf/doc/info:$INFOPATH; export INFOPATH -\end{sverbatim} - -For csh or tcsh, the file to edit is typically \filename{$HOME/.cshrc}, and -the lines to add might look like: - -\begin{sverbatim} -setenv PATH /usr/local/texlive/2008/bin/i386-linux:$PATH -setenv MANPATH /usr/local/texlive/2008/texmf/doc/man:$MANPATH -setenv INFOPATH /usr/local/texlive/2008/texmf/doc/info:$INFOPATH -\end{sverbatim} - -Of course, you may well already have settings somewhere in your ``dot'' -files, and so then the \TL\ directories should simply be merged in as -appropriate. - -\subsubsection{Environment variables: global configuration} -\label{sec:envglobal} - -If you want to make these changes globally, or for a user newly added to -the system, then you are on your own; there is just too much variation -between systems in how and where these things are configured. - -Our two hints are: 1)~you may want to check for a file -\filename{/etc/manpath.config} and, if present, add lines such as - -\begin{sverbatim} -MANPATH_MAP /usr/local/texlive/2008/bin/i386-linux \ - /usr/local/texlive/2008/texmf/doc/man -\end{sverbatim} - -And 2)~check for a file \filename{/etc/environment} which may define the -search path and other default environment variables. - - -\subsubsection{When running from DVD} - -Normally, a \TL{} program consults a file \filename{texmf.cnf} for the -location of the various trees. It looks for this file in a series of -locations relative to its own location. However, this scheme breaks down -when a program is run from \DVD{}: the \DVD{} is read-only. Some of the -paths to be recorded in \filename{texmf.cnf} are only known at -installation time, so this file cannot be on the \DVD{} and must be -placed somewhere else. This makes it necessary to define an environment -\envname{TEXMFCNF} variable which tells \TL{} programs in what directory -to find this \filename{texmf.cnf}. It is also still necessary to modify -the \envname{PATH} environment variable, as described before. - -At the end of the installation, the installer should have printed a -message giving the value to which \envname{TEXMFCNF} should be set. In -case you missed it: this value is \dirname{$TEXMFSYSVAR/web2c}. For the -default, \dirname{/usr/local/texlive/2008/texmf-var/web2c}, you need the -lines -\begin{sverbatim} -TEXMFCNF=/usr/local/texlive/2008/texmf-var/web2c; export TEXMFCNF -\end{sverbatim} -or, for [t]csh: -\begin{sverbatim} -setenv TEXMFCNF /usr/local/texlive/2008/texmf-var/web2c -\end{sverbatim} - - -\subsubsection{\ConTeXt{} Mark IV} - -The `old' \ConTeXt{} should run out of the box. The new `Mark IV' -\ConTeXt{} will require manual setup; see -\url{http://wiki.contextgarden.net/Running_Mark_IV}. - - -\subsubsection{Integrating local and personal macros} -\label{sec:local-personal-macros} - -This is already mentioned implicitly in section~\ref{sec:texmftrees}: -\dirname{TEXMFLOCAL} (by default, -\dirname{/usr/local/texlive/texmf-local} or -\verb|C:\Program Files\texlive\texmf-local|) - -is intended for system-wide local fonts and macros; and -\dirname{TEXMFHOME} (by default, \dirname{$HOME/texmf} or -\verb|%USERPROFILE%\texmf|), is for personal fonts and macros. These -directories are intended to stick around from release to release, and -have their content seen automatically by a new \TL{} release. -Therefore, it is best to refrain from changing the definition of -\dirname{TEXMFLOCAL} to be too far away from the main \TL{} directory, -or you will need to manually change future releases. - -For both trees, files should be placed in their proper subdirectories; -see \url{http://tug.org/tds} or consult -\filename{texmf/web2c/texmf.cnf}. For instance, a \LaTeX{} class file or -package should be placed in \dirname{TEXMFLOCAL/tex/latex} or -\dirname{TEXMFHOME/tex/latex}, or a subdirectory thereof. - -\dirname{TEXMFLOCAL} requires an up-to-date filename database, or files -will not be found. You can update it with the command -\cmdname{mktexlsr} or use the `Reinit file database' button on the -configuration tab of \prog{tlmgr} in \GUI\ mode. - -\subsubsection{Integrating third-party fonts} - -This is unfortunately a very complicated and messy topic. Forget -about it unless you really know your way around blindfolded in a -\TeX{} installation. Don't forget to check first what you get for -free: see section~\ref{sec:tl-fonts}. - -A possible alternative is to use \XeTeX (see -section~\ref{sec:tex-extensions}), which lets you use operating system -fonts without any installation in \TeX. - - -\subsection{Testing the installation} -\label{sec:test-install} - -After installing \TL{} as best you can, you naturally want to test -it out, so you can start creating beautiful documents and\slash or fonts. - -This section gives some basic procedures for testing that the new system -is functional. We give Unix commands here; under \MacOSX{} and Windows, -you're more likely to run the tests through a graphical interface, but -the principles are the same. - -\begin{enumerate} - -\item Make sure that you can run the \cmdname{tex} program in the first -place: - -\begin{alltt} -> \Ucom{tex -{}-version} -TeX 3.1415926 (Web2C 7.5.7) -kpathsea version 3.5.7 -... -\end{alltt} -If this comes back with `command not found' instead of version and -copyright information, or with an older version, most likely you don't -have the correct \dirname{bin} subdirectory in your \envname{PATH}. See -the environment-setting information on \p.\pageref{sec:env}. - -\item Process a basic \LaTeX{} file: -\begin{alltt} -> \Ucom{latex sample2e.tex} -This is pdfeTeXk, Version 3.1415926... -... -Output written on sample2e.dvi (3 pages, 7484 bytes). -Transcript written on sample2e.log. -\end{alltt} -If this fails to find \filename{sample2e.tex} or other files, most -likely you have interference from old environment variables or -configuration files; we recommend unsetting all \TeX-related environment -variables for a start. (For a deep analysis, you can ask \TeX{} to -report on exactly what it is searching for, and finding; see ``Debugging -actions'' on page~\pageref{sec:debugging}.) - -\item Preview the result online: -\begin{alltt} -> \Ucom{xdvi sample2e.dvi} -\end{alltt} -(Under Windows, the analogous command is \cmdname{dviout}.) You should -see a new window with a nice document explaining some of the basics of -\LaTeX{}. (Well worth reading, by the way if you're new to the system.) -You do have to be running under X for \cmdname{xdvi} to work; if you're -not, or your \envname{DISPLAY} environment variable is set incorrectly, -you'll get an error \samp{Can't open display}. - -\item Create a \PS{} file for printing or display: -\begin{alltt} -> \Ucom{dvips sample2e.dvi -o sample2e.ps} -\end{alltt} - -\item Create a \acro{PDF} file instead of \dvi{}; this processes the -\filename{.tex} file and writes \acro{PDF} directly: -\begin{alltt} -> \Ucom{pdflatex sample2e.tex} -\end{alltt} - -\item Preview the \acro{PDF} file: -\begin{alltt} -> \Ucom{gv sample2e.pdf} -\textrm{or:} -> \Ucom{xpdf sample2e.pdf} -\end{alltt} -Unfortunately neither \cmdname{gv} nor \cmdname{xpdf} are currently -included in \TL{}, so you must install them separately. See -\url{http://www.gnu.org/software/gv} and -\url{http://www.foolabs.com/xpdf}, respectively. (There are plenty of -other \acro{PDF} viewers, too.) - -\item Standard test files you may find useful in addition to -\filename{sample2e.tex}: - -\begin{ttdescription} -\item [small2e.tex] A simpler document than \filename{sample2e}, to -reduce the input size if you're having troubles. -\item [testpage.tex] Test if your printer introduces any offsets. -\item [nfssfont.tex] For printing font tables and tests. -\item [testfont.tex] Also for font tables, but using plain \TeX{}. -\item [story.tex] The most canonical (plain) \TeX{} test file of all. -You must type \samp{\bs bye} to the \code{*} prompt after \samp{tex -story.tex}. -\end{ttdescription} - -\end{enumerate} - -If you are new to \TeX{}, or otherwise need help with actually writing -\TeX{} or \LaTeX{} documents, please visit -\url{http://tug.org/begin.html} for some introductory resources. - - -\section{Network installations} -\label{sec:netinstall} - -\TL{} has been designed to be shared between different users, and even -different systems on a network. With a standard directory layout, no -hard paths are configured: the locations for files needed by \TL{} -programs are defined relative to the places of those programs. You can -see this at work in the configuration file -\filename{$TEXMFMAIN/web2c/texmf.cnf}, which contains lines such as -\begin{sverbatim} -TEXMFMAIN = $SELFAUTOPARENT/texmf -... -TEXMFLOCAL = $SELFAUTOPARENT/../texmf-local -\end{sverbatim} -This means that other systems or other users merely need to add the -directory for \TL{} binaries for their platform to their search path. - -By the same token, you can also install \TL{} locally and then move -the entire hierarchy afterwards to a network location. - -Of course, Windows users have different expectations. The directory -\dirname{texmf-doc/source/texlive/texlive-common/w32client} contains a -sample script \filename{install-w32client} which creates settings and -menu shortcuts for using an existing \TL{} installation on a -\acro{LAN}. It is to be invoked through a batch file -\filename{install-w32client.bat} in the same directory. - -You can read more about \TL{} configuration and path searching in -section~\ref{sec:kpathsea}. - -\section{Maximally portable \protect\TL{} on DVD and USB} -\label{sec:portable-unix} - -The `running from \DVD{}' option described in -section~\ref{sec:fromdvd} is fine for your own system, but if you -are a guest on somebody else's system then you would probably like -something with minimal side effects. - -In the root of the \TL{} \DVD, or the \dirname{texlive} subdirectory of -the \TK{} \DVD, are a \filename{tl-portable} script (Unix) and a -\filename{tl-portable.bat} batchfile (Windows) which start up a -secondary shell\slash command prompt with environment settings suitable -for directly accessing the \TL{} on the \DVD. - -When it runs for the first time, some files will be generated in a -directory \dirname{~/.tlportable2008}, which will take a little time. -On subsequent runs, though, it will start almost instantaneously. - -The rest of the system will be unaware of \TL. If you want your editor -to be aware of this \TL, then you can start it from a second, parallel, -such \filename{tl-portable} session. - -You can also use \filename{tl-portable} to run \TL{} on a -\acro{USB} stick. In this case, copy all the top-level files and -the contents of the \dirname{bin}, \dirname{texmf}, -\dirname{texmf-dist}, and \dirname{tlpkg} directories (at least) to -the stick. This may take quite a while! If you are copying to a -\acro{FAT}32-formatted \acro{USB} stick, make sure to dereference -symbolic links (\code{cp -L}). A \dirname{texmf-local} directory on -the stick will also be found and used. - -Then run \filename{tl-portable} from the root of the stick, as above. -In this case, the script will notice that the stick is writable and use -it for generated files. You could burn the resulting contents of the -stick back to \DVD{} if that is more convenient to (for example) give to -others. - - -\section{\cmdname{tlmgr}: Managing your installation} -\label{sec:tlmgr} - -\begin{figure}[tb] -\tlpng{tlmgr-gui}{\linewidth} -\caption{\prog{tlmgr} in \GUI\ mode. The list of - packages/collections/schemes only shows up after clicking the - `Load' button.}\label{fig:tlmgr-gui} -\end{figure} - -\begin{figure}[tb] -\tlpng{tlmgr-config}{\linewidth} -\caption{\texttt{tlmgr} in GUI mode: Configuration tab}\label{fig:tlmgr-config} -\end{figure} - -The installer installs a program named \prog{tlmgr} for managing \TL{} -after the initial installation. The programs \prog{updmap}, -\prog{fmtutil} and \prog{texconfig} are still included and will be -retained in the future, but \prog{tlmgr} is now the preferred interface. -Its capabilities include: - -\begin{itemize*} -\item listing schemes, collections and packages; -\item installing, updating, backing up, restoring and uninstalling - individual packages, optionally taking dependencies into account; -\item searching for packages; -\item listing and adding architectures; -\item changing installation options such as paper size and source - location (see section~\ref{sec:location}). -\end{itemize*} -\textit{Warning:} \prog{tlmgr} has not been designed for or tested -with installations which run from \DVD. - -\subsection{\cmdname{tlmgr} GUI mode} -\prog{tlmgr} can be started in \GUI{} mode with -\begin{alltt} -> \Ucom{tlmgr -gui} -\end{alltt} -or in Windows via the Start menu: \texttt{Start}, \texttt{Programs}, -\texttt{TeX Live 2008}, \texttt{TeX Live Manager}. After clicking `Load' -it displays a list of available and installed packages\Dash the latter -prepended with `(i)'. This assumes of course that the installation -source is valid and reachable. - -Figure~\ref{fig:tlmgr-config} shows the configuration tab. - -\subsection{Sample \cmdname{tlmgr} command-line invocations} - -This example adds several packages, including a new `engine', from a -non-default location: - -\begin{alltt} -> \Ucom{tlmgr -location http://172.16.18.1/tldev install collection-xetex xkeyval} -\end{alltt} -It generates the following output: -\begin{fverbatim} -install: collection-xetex -install: arabxetex -install: euenc -install: bidi -install: fontspec -install: fontwrap -install: ifxetex -install: philokalia -install: polyglossia -install: xecyr -install: xecyr.i386-linux -install: xepersian -install: xetex -install: xetexconfig -install: xetex.i386-linux -running post install action for xetex -install: xetex-def -install: xetex-pstricks -install: xetexfontinfo -install: xltxtra -install: xunicode -install: xkeyval -running mktexlsr -mktexlsr: Updating /usr/local/texlive/2008/texmf/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-config/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-dist/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-doc/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/../texmf-local/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-var/ls-R... -mktexlsr: Done. -regenerating fmtutil.cnf -running fmtutil-sys --missing -... -Transcript written on xelatex.log. -fmtutil: /usr/local/texlive/2008/texmf-var/web2c/xetex/xelatex.fmt installed. -\end{fverbatim} -As you see, \prog{tlmgr} installs dependencies, and takes care of any -necessary post-install actions, including updating the filename database -and (re)generating formats. (Here we generated new formats for \XeTeX.) - -This example installs a new language. This also triggers format -regeneration: -\begin{alltt} -> \Ucom{tlmgr install collection-langdutch} -\end{alltt} -To describe a package: -\begin{alltt} -> \Ucom{tlmgr show collection-wintools} -\end{alltt} -which produces -\begin{fverbatim} -Package: collection-wintools -Category: Collection -ShortDesc: Windows support programs -LongDesc: Utilities for Windows, since they are not readily available there: - gzip, chktex, jpeg2ps, unzip, wget, xpdf. -Installed: Yes -\end{fverbatim} -Updating your entire installation to the latest versions available: -\begin{alltt} -> \Ucom{tlmgr update -all} -\end{alltt} -If this makes you nervous, first try -\begin{alltt} -> \Ucom{tlmgr update -all -dry-run} -\end{alltt} -or -\begin{alltt} -> \Ucom{tlmgr update -list} -\end{alltt} -For full documentation: -\begin{alltt} -> \Ucom{tlmgr -help} -\end{alltt} - - -\section{Notes on Windows} -\label{sec:windows} - -\TL\ has a single installer which runs on both Windows and Unix. This -was only possible by dropping support for older Windows versions, so -\TL\ can now be installed only on Windows 2000 and later. - - -\subsection{Windows-specific features} -\label{sec:winfeatures} - -Under Windows, the installer does some extra things: -\begin{description} -\item[Menus and shortcuts.] A new `\TL{}' submenu of the - Start menu is installed, which contains entries for some \GUI{} programs - (\prog{tlmgr}, \prog{texdoctk}, the PS\_View PostScript previewer) - and some documentation. PS\_View also gets a shortcut on the - desktop as a drag-and-drop target for PostScript files. -\item[Automatic setting of environment variables.] No manual - configuration steps are required. -\item[Uninstaller.] The installer creates an entry under `Add/Remove - Programs' for \TL. The uninstall tab of\prog{tlmgr} refers to - this. -\end{description} - -\subsection{Additional included software} - -\begin{figure}[tb] -\tlpng{psview}{.6\linewidth} -\caption{PS\_View: very high magnifications available!}\label{fig:psview} -\end{figure} - -To be complete, a \TL installation needs support packages that are not -commonly found on a Windows machine. \TL{} provides the missing -pieces: -\begin{description} -\item[Perl and Ghostscript.] Because of the importance of Perl and - Ghostscript, \TL{} includes `hidden' copies of these - programs. \TL{} programs that need them know where to find them, - but they don't betray their presence through environment variables - or registry settings. They aren't full-scale distributions, and - shouldn't interfere with any system installations of Perl or - Ghostscript. -\item[Command-line tools.] A number of Windows ports of common Unix - command-line programs are installed along with the usual \TL{} - binaries. These include \cmdname{gzip}, \cmdname{chktex}, - \cmdname{jpeg2ps}, \cmdname{unzip}, \cmdname{wget} and the - command-line utilities from the \cmdname{xpdf} suite. (The - \cmdname{xpdf} viewer itself is not available for Windows, but the - Sumatra \acro{PDF} viewer is based on it: - \url{http://blog.kowalczyk.info/software/sumatrapdf}.) -\item[\texttt{fc-cache}] helps \XeTeX{} to handle fonts more - efficiently. -\item[PS\_View.] Also installed is PS\_View, a new PostScript viewer - with a free license; see figure~\ref{fig:psview}. -\end{description} -\begin{description} -\item[The \texttt{support} directory,] already mentioned in - section~\ref{sec:tld}. This directory contains various programs - which can be useful in connection with \TeX, in particular a - number of \TeX-aware editors and \TeX{} frontends. The software in - this directory isn't covered by the installer. This directory also - contains the \cmdname{dviout} \dvi{} previewer; see the next section. -\end{description} - -\subsection{The Dviout previewer} - -This \TL{} release unfortunately doesn't offer a preinstalled \dvi{} -previewer for Windows. However, you can install \prog{dviout} by -Toshio Oshima from the \path{support/dviout/} directory, which -contains also a short \filename{README} describing how to install -and configure \prog{dviout} for \TL. Please read this carefully -before installation. - -At first, when you preview files with \cmdname{dviout}, it will create fonts, -because screen fonts were not installed. After a while, you will have created -most of the fonts you use, and you will rarely see the font-creation window. -More information can be found in the (very good) on-line help. - -\subsection{Links for additional downloadable software} - -Urls for some other tools you may consider installing: -\begin{description} -\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} -\item[Perl] \url{http://www.perl.org/} with - supplementary packages from \acro{CPAN}, \url{http://www.cpan.org/} -\item[ImageMagick] \url{http://www.imagemagick.com}, for graphics - processing and conversion -\item[NetPBM] \url{http://netpbm.sourceforge.net/}, also for graphics. - -\item[\TeX-oriented editors] There is a wide choice, and it is a matter of the - user's taste. Here is a selection, in no particular order: - \begin{itemize*} - \item \cmdname{GNU Emacs} is available natively under Windows, see - \url{http://www.gnu.org/software/emacs/windows/ntemacs.html}. - \item \cmdname{Emacs} with Auc\TeX\ for Windows is available in \TL's - \path{support} directory; its home page is - \url{http://www.gnu.org/software/auctex}. - \item \cmdname{WinShell} is available in \TL's \path|support| - directory; its home page is \url{http://www.winshell.de}. - \item \cmdname{WinEdt} is shareware available from - \url{http://www.winedt.com}. - \item \cmdname{Vim} is free software, available from - \url{http://www.vim.org}. - \item TeXnicCenter is free software, available from - \url{http://www.toolscenter.org} and in the pro\TeX{}t distribution. - \item \cmdname{LEd} is available from \url{http://www.ctan.org/support/LEd}. - \item \cmdname{SciTE} is available from - \url{http://www.scintilla.org/SciTE.html}. - \end{itemize*} -\end{description} - - -\subsection{User Profile is Home} -\label{sec:winhome} - -The Windows counterpart of a Unix home directory is the -\verb|%USERPROFILE%| directory. Under Windows XP and Windows 2000, this -is usually \verb|C:\Documents and Settings\|, and under -Windows Vista \verb|C:\Users\|. In the -\filename{texmf.cnf} file, and \KPS{} in general, \verb|~| will expand -appropriately on both Windows and Unix. - - -\subsection{The Windows registry} -\label{sec:registry} - -Windows stores nearly all configuration data in its registry. The -registry contains a set of hierarchically organized keys, with several -root keys. The most important ones for installation programs are -\path{HKEY_CURRENT_USER} and \path{HKEY_LOCAL_MACHINE}, \path{HKCU} and -\path{HKLM} in short. The \path{HKCU} part of the registry is in the -user's home directory (see section~\ref{sec:winhome}). \path{HKLM} is -normally in a subdirectory of the Windows directory. - -In some cases, system information could be obtained from environment -variables but for other information, for example the location of -shortcuts, it is necessary to consult the registry. Setting environment -variables permanently also requires registry access. - - -\subsection{Windows permissions} -\label{sec:winpermissions} - -In later versions of Windows, a distinction is made between regular -users and administrators, where only the latter have free access to the -entire operating system. In practice, though, you could better describe -these classes of users as unprivileged users and normal users: being an -administrator is the rule, not the exception. Nevertheless, we have made -an effort to make \TL{} installable without administrative privileges. - -If the user is an administrator, shortcuts are created for all users, -and the system environment is modified. Otherwise, shortcuts and menu -entries are created for the current user, and the user environment is -modified. Use the \optname{non-admin} option to \prog{install-tl} if -you prefer per-user settings even as an administrator. - -Regardless of administrator status, the default root of \TL{} proposed -by the installer is always under \verb|%PROGRAMFILES%|. The installer -always tests whether the root is writable for the current user. - -A problem may arise if the user is not an administrator and \TeX{} -already exists in the search path. Since the effective path consists of -the system path followed by the user path, the new \TL{} will never get -precedence. As a workaround, in this case the installer creates -shortcuts to the command-prompt in which the new \TL{} binary directory -is prepended to the local searchpath. The new \TL{} will be usable when -run in a command-line session started from such a shortcut. - - -\section{A user's guide to Web2C} - -\Webc{} is an integrated collection of \TeX-related programs: \TeX{} -itself, \MF{}, \MP, \BibTeX{}, etc. It is the heart of \TL{}. The home -page for \Webc{}, with the current manual and more, is -\url{http://tug.org/web2c}. - -A bit of history: The original implementation was by Tomas Rokicki who, -in 1987, developed a first \TeX{}-to-C system based on change files -under Unix, which were primarily the original work of Howard Trickey and -Pavel Curtis. Tim Morgan became the maintainer of the system, and -during this period the name changed to Web-to-C\@. In 1990, Karl Berry -took over the work, assisted by dozens of additional contributors, and -in 1997 he handed the baton to Olaf Weber, who returned it to Karl in -2006. - -The \Webc{} system runs on Unix, 32-bit Windows systems, \MacOSX{}, and -other operating systems. It uses Knuth's original sources for \TeX{} and -other basic programs written in the \web{} literate programming system -and translates them into C source code. The core \TeX{} programs -handled in this way are: - -\begin{cmddescription} -\item[bibtex] Maintaining bibliographies. -\item[dmp] \cmdname{troff} to MPX (\MP{} pictures). -\item[dvicopy] Expands virtual font references in \dvi{} files. -\item[dvitomp] \dvi{} to MPX (MetaPost pictures). -\item[dvitype] \dvi{} to human-readable text. -\item[gftodvi] Generic font proofsheets. -\item[gftopk] Generic to packed fonts. -\item[gftype] GF to human-readable text. -\item[makempx] \MP{} label typesetting. -\item[mf] Creating typeface families. -\item[mft] Prettyprinting \MF{} source. -\item[mpost] Creating technical diagrams. -\item[mpto] MetaPost label extraction. -\item[newer] Compare modification times. -\item[patgen] Creating hyphenation patterns. -\item[pktogf] Packed to generic fonts. -\item[pktype] PK to human-readable text. -\item[pltotf] Plain text property list to TFM. -\item[pooltype] Display \web{} pool files. -\item[tangle] \web{} to Pascal. -\item[tex] Typesetting. -\item[tftopl] TFM to plain text property list. -\item[vftovp] Virtual font to virtual property list. -\item[vptovf] Virtual property list to virtual font. -\item[weave] \web{} to \TeX. -\end{cmddescription} - -\noindent The precise functions and syntax of these programs are -described in the documentation of the individual packages and of \Webc{} -itself. However, knowing a few principles governing the whole family of -programs will help you take advantage of your \Webc{} installation. - -All programs honor these standard \GNU options: -\begin{ttdescription} -\item[-{}-help] print basic usage summary. -\item[-{}-verbose] print detailed progress report. -\item[-{}-version] print version information, then exit. -\end{ttdescription} - -For locating files the \Webc{} programs use the path searching library -\KPS{} (\url{http://tug.org/kpathsea}). This library uses a combination -of environment variables and a configuration files to optimize searching -the (huge) collection of \TeX{} files. \Webc{} can look at many -directory trees simultaneously, which is useful in maintaining \TeX's -standard distribution and local and personal extensions in distinct -trees. To speed up file searches, the root of each tree has a file -\file{ls-R}, containing an entry showing the name and relative pathname -for all files under that root. - - -\subsection{Kpathsea path searching} -\label{sec:kpathsea} - -Let us first describe the generic path searching mechanism of the \KPS{} -library. - -We call a \emph{search path} a colon- or semicolon\hyph sepa\-rated list -of \emph{path elements}, which are basically directory names. A -search path can come from (a combination of) many sources. To look up -a file \samp{my-file} along a path \samp{.:/dir}, \KPS{} checks each -element of the path in turn: first \file{./my-file}, then -\file{/dir/my-file}, returning the first match (or possibly all -matches). - -In order to adapt optimally to all operating systems' conventions, on -non-Unix systems \KPS{} can use filename separators different from -colon (\samp{:}) and slash (\samp{/}). - -To check a particular path element \var{p}, \KPS{} first checks if a -prebuilt database (see ``Filename data\-base'' on -page~\pageref{sec:filename-database}) applies to \var{p}, i.e., if the -database is in a directory that is a prefix of \var{p}. If so, the path -specification is matched against the contents of the database. - -If the database does not exist, or does not apply to this path -element, or contains no matches, the filesystem is searched (if this -was not forbidden by a specification starting with \samp{!!}\ and if -the file being searched for must exist). \KPS{} constructs the list -of directories that correspond to this path element, and then checks -in each for the file being sought. - -The ``file must exist'' condition comes into play with \samp{.vf} files and -input files read by \TeX's \cs{openin} command. Such files may not -exist (e.g., \file{cmr10.vf}), and so it would be wrong to search the -disk for them. Therefore, if you fail to update \file{ls-R} when you -install a new \samp{.vf} file, it will never be found. -Each path element is checked in turn: first the database, then the -disk. If a match is found, the search stops and the result is -returned. - -Although the simplest and most common path element is a directory -name, \KPS{} supports additional features in search paths: layered -default values, environment variable names, config file values, users' -home directories, and recursive subdirectory searching. Thus, we say -that \KPS{} \emph{expands} a path element, meaning it transforms all -the specifications into basic directory name or names. This is -described in the following sections in the same order as it takes -place. - -Note that if the filename being searched for is absolute or explicitly -relative, i.e., starts with \samp{/} or \samp{./} or \samp{../}, -\KPS{} simply checks if that file exists. - -\ifSingleColumn -\else -\begin{figure*} -\verbatiminput{examples/ex5.tex} -\setlength{\abovecaptionskip}{0pt} - \caption{An illustrative configuration file sample} - \label{fig:config-sample} -\end{figure*} -\fi - -\subsubsection{Path sources} -\label{sec:path-sources} - -A search path can come from many sources. In the order in which -\KPS{} uses them: - -\begin{enumerate} -\item - A user-set environment variable, for instance, \envname{TEXINPUTS}\@. - Environment variables with a period and a program name appended - override; e.g., if \samp{latex} is the name of the program being run, - then \envname{TEXINPUTS.latex} will override \envname{TEXINPUTS}. -\item - A program-specific configuration file, for exam\-ple, a line - \samp{S /a:/b} in \cmdname{dvips}'s \file{config.ps}. -\item A \KPS{} configuration file \file{texmf.cnf}, containing a line like - \samp{TEXINPUTS=/c:/d} (see below). -\item The compile-time default. -\end{enumerate} -\noindent You can see each of these values for a given search path by -using the debugging options (see ``Debugging actions'' on -page~\pageref{sec:debugging}). - -\subsubsection{Config files} - -\begingroup\tolerance=3500 -\KPS{} reads \emph{runtime configuration files} named \file{texmf.cnf} -for search path and other definitions. The search path used to look -for these files is named \envname{TEXMFCNF} (by default such a file lives -in the \file{texmf/web2c} subdirectory). \emph{All} -\file{texmf.cnf} files in the search path will be read and definitions -in earlier files override those in later files. Thus, with a search -path of \verb|.:$TEXMF|, values from \file{./texmf.cnf} override those -from \verb|$TEXMF/texmf.cnf|. -\endgroup - -\begin{itemize} -\item - Comments start with \code{\%} and continue to the end of the line. -\item - Blank lines are ignored. -\item - A \bs{} at the end of a line acts as a continuation character, - i.e., the next line is appended. Whitespace at the beginning of - continuation lines is not ignored. -\item - Each remaining line has the form: -\begin{alltt} - \var{variable}[.\var{progname}] [=] \var{value} -\end{alltt}% - where the \samp{=} and surrounding whitespace are optional. -\item - The \ttvar{variable} name may contain any character other - than whitespace, \samp{=}, or \samp{.}, but sticking to - \samp{A-Za-z\_} is safest. -\item - If \samp{.\var{progname}} is present, the definition only - applies if the program that is running is named - \texttt{\var{progname}} or \texttt{\var{progname}.exe}. This allows - different flavors of \TeX{} to have different search paths, for - example. -\item \var{value} may contain any characters except - \code{\%} and \samp{@}. The - \code{\$\var{var}.\var{prog}} feature is not available on the - right-hand side; instead, you must use an additional variable. A - \samp{;}\ in \var{value} is translated to \samp{:}\ if - running under Unix; this is useful to be able to have a single - \file{texmf.cnf} for Unix, \acro{MS-DOS} and Windows systems. -\item - All definitions are read before anything is expanded, so - variables can be referenced before they are defined. -\end{itemize} -A configuration file fragment illustrating most of these points is -\ifSingleColumn -shown below: - -\verbatiminput{examples/ex5.tex} -\else -shown in Figure~\ref{fig:config-sample}. -\fi - -\subsubsection{Path expansion} -\label{sec:path-expansion} - - -\KPS{} recognizes certain special characters and constructions in -search paths, similar to those available in Unix shells. As a -general example, the complex path, -\verb+~$USER/{foo,bar}//baz+, expands to all subdirectories under -directories \file{foo} and \file{bar} in \texttt{\$USER}'s home -directory that contain a directory or file \file{baz}. These -expansions are explained in the sections below. -%$ -\subsubsection{Default expansion} -\label{sec:default-expansion} - -\tolerance=2500 -If the highest-priority search path (see ``Path sources'' on -page~\pageref{sec:path-sources}) contains an \emph{extra colon} (i.e., -leading, trailing, or doubled), \KPS{} inserts at that point the -next-highest-prio\-rity search path that is defined. If that inserted -path has an extra colon, the same happens with the next highest. For -example, given an environment variable setting - -\tolerance=1500 - -\begin{alltt} -> \Ucom{setenv TEXINPUTS /home/karl:} -\end{alltt} -and a \code{TEXINPUTS} value from \file{texmf.cnf} of - -\begin{alltt} - .:\$TEXMF//tex -\end{alltt} -then the final value used for searching will be: - -\begin{alltt} - /home/karl:.:\$TEXMF//tex -\end{alltt} - -Since it would be useless to insert the default value in more than one -place, \KPS{} changes only one extra \samp{:}\ and leaves any others in -place. It checks first for a leading \samp{:}, then a trailing -\samp{:}, then a doubled \samp{:}. - -\subsubsection{Brace expansion} - -A useful feature is brace expansion, which means that, for instance, -\verb+v{a,b}w+ expands to \verb+vaw:vbw+. Nesting is allowed. -This is used to implement multiple \TeX{} hierarchies, by -assigning a brace list to \code{\$TEXMF}. -For example, in \file{texmf.cnf}, the following definition -(appproximately; there are actually even more trees) is made: -\begin{verbatim} - TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN} -\end{verbatim} -Using this you can then write something like -\begin{verbatim} - TEXINPUTS = .;$TEXMF/tex// -\end{verbatim} -%$ -which means that, after looking in the current directory, the -\code{\$TEXMFHOME/tex}, \code{\$TEXMFLOCAL/tex}, \code{\$TEXMFVAR/tex} -and \code{\$TEXMFMAIN/tex} trees \emph{only}) will be searched (the -last two use using \file{ls-R} data base files). It is a convenient -way for running two parallel \TeX{} structures, one ``frozen'' (on a -\CD, for instance) and the other being continuously updated with new -versions as they become available. By using the \code{\$TEXMF} -variable in all definitions, one is sure to always search the -up-to-date tree first. - -\subsubsection{Subdirectory expansion} -\label{sec:subdirectory-expansion} - -Two or more consecutive slashes in a path element following a directory -\var{d} is replaced by all subdirectories of \var{d}: first those -subdirectories directly under \var{d}, then the subsubdirectories under -those, and so on. At each level, the order in which the directories are -searched is \emph{unspecified}. - -If you specify any filename components after the \samp{//}, only -subdirectories with matching components are included. For example, -\samp{/a//b} expands into directories \file{/a/1/b}, \file{/a/2/b}, -\file{/a/1/1/b}, and so on, but not \file{/a/b/c} or \file{/a/1}. - -Multiple \samp{//} constructs in a path are possible, but -\samp{//} at the beginning of a path is ignored. - -\subsubsection{List of special characters and their meaning: a summary} - -The following list summarizes the special characters in \KPS{} -configuration files. - -% need a wider space for the item labels here. -\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} -\begin{ttdescription} -\item[\CODE{:}] Separator in path specification; at the beginning or - the end of a path it substitutes the default path expansion.\par -\item[\CODE{;}] Separator on non-Unix systems (acts like \code{:}). -\item[\CODE{\$}] Variable expansion. -\item[\CODE{\string~}] Represents the user's home directory. -\item[\CODE{\char`\{...\char`\}}] Brace expansion. -\item[\CODE{//}] Subdirectory expansion (can occur anywhere in - a path, except at its beginning). -\item[\CODE{\%}] Start of comment. -\item[\CODE{\bs}] Continuation character (allows multi-line entries). -\item[\CODE{!!}] Search \emph{only} database to locate file, \emph{do - not} search the disk. -\end{ttdescription} - - -\subsection{Filename databases} -\label{sec:filename-database} - -\KPS{} goes to some lengths to minimize disk accesses for searches. -Nevertheless, at installations with enough directories, searching each -possible directory for a given file can take an excessively long time -(this is especially true if many hundreds of font directories have to -be traversed.) Therefore, \KPS{} can use an externally-built plain text -``database'' file named \file{ls-R} that maps files to directories, -thus avoiding the need to exhaustively search the disk. - -A second database file \file{aliases} allows you to give additional -names to the files listed in \file{ls-R}. This can be helpful to -confirm to \acro{DOS} 8.3 filename conventions in source files. - -\subsubsection{The filename database} -\label{sec:ls-R} - -As explained above, the name of the main filename database must be -\file{ls-R}. You can put one at the root of each \TeX{} hierarchy in -your installation that you wish to be searched (\code{\$TEXMF} by -default); most sites have only one hierarchy. \KPS{} looks for -\file{ls-R} files along the \code{TEXMFDBS} path. - -The recommended way to create and maintain \samp{ls-R} is to run the -\code{mktexlsr} script included with the distribution. It is invoked -by the various \samp{mktex}\dots\ scripts. In principle, this script -just runs the command -\begin{alltt} -cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R -\end{alltt} -presuming your system's \code{ls} produces the right output format -(\GNU \code{ls} is all right). To ensure that the database is -always up-to-date, it is easiest to rebuild it regularly via -\code{cron}, so that it is automatically updated when the installed -files change, such as after installing or updating a \LaTeX{} package. - -If a file is not found in the database, by default \KPS{} goes ahead -and searches the disk. If a particular path element begins with -\samp{!!}, however, \emph{only} the database will be searched for that -element, never the disk. - - -\subsubsection{kpsewhich: Standalone path searching} -\label{sec:invoking-kpsewhich} - -The \texttt{kpsewhich} program exercises path searching independent of any -particular application. This can be useful as a sort of \code{find} -program to locate files in \TeX{} hierarchies (this is used heavily in -the distributed \samp{mktex}\dots\ scripts). - -\begin{alltt} -> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} -\end{alltt} -The options specified in \ttvar{option} start with either \samp{-} -or \samp{-{}-}, and any unambiguous abbreviation is accepted. - -\KPS{} looks up each non-option argument on the command line as a -filename, and returns the first file found. There is no option to -return all the files with a particular name (you can run the Unix -\samp{find} utility for that). - -The most common options are described next. - -\begin{ttdescription} -\item[\texttt{-{}-dpi=\var{num}}]\mbox{} - Set the resolution to \ttvar{num}; this only affects \samp{gf} - and \samp{pk} lookups. \samp{-D} is a synonym, for compatibility - with \cmdname{dvips}. Default is 600. - -\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ - Set the format for lookup to \ttvar{name}. By default, the - format is guessed from the filename. For formats which do not have - an associated unambiguous suffix, such as \MP{} support files and - \cmdname{dvips} configuration files, you have to specify the name as - known to \KPS{}, such as \texttt{tex} or \texttt{enc files}. Run - \texttt{kpsewhich -{}-help} for a list. - -\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ - Set the mode name to \ttvar{string}; this only affects \samp{gf} - and \samp{pk} lookups. No default: any mode will be found. -\item[\texttt{-{}-must-exist}]\mbox{}\\ - Do everything possible to find the files, notably including - searching the disk. By default, only the \file{ls-R} database is - checked, in the interest of efficiency. -\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ - Search along the path \ttvar{string} (colon-separated as usual), - instead of guessing the search path from the filename. \samp{//} and - all the usual expansions are supported. The options \samp{-{}-path} - and \samp{-{}-format} are mutually exclusive. -\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ - Set the program name to \texttt{\var{name}}. - This can affect the search paths via the \texttt{.\var{progname}} - feature. - The default is \cmdname{kpsewhich}. -\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ - shows the path used for file lookups of file type \texttt{\var{name}}. - Either a filename extension (\code{.pk}, \code{.vf}, etc.) or a - name can be used, just as with \samp{-{}-format} option. -\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ - sets the debugging options to \texttt{\var{num}}. -\end{ttdescription} - - -\subsubsection{Examples of use} -\label{sec:examples-of-use} - -Let us now have a look at \KPS{} in action. Here's a straightforward search: - -\begin{alltt} -> \Ucom{kpsewhich article.cls} - /usr/local/texmf-dist/tex/latex/base/article.cls -\end{alltt} -We are looking for the file \file{article.cls}. Since the \samp{.cls} -suffix is unambiguous we do not need to specify that we want to look for a -file of type \optname{tex} (\TeX{} source file directories). We find it in -the subdirectory \file{tex/latex/base} below the \samp{texmf-dist} \TL\ -directory. Similarly, all of the following are found without problems -thanks to their unambiguous suffix. -\begin{alltt} -> \Ucom{kpsewhich array.sty} - /usr/local/texmf-dist/tex/latex/tools/array.sty -> \Ucom{kpsewhich latin1.def} - /usr/local/texmf-dist/tex/latex/base/latin1.def -> \Ucom{kpsewhich size10.clo} - /usr/local/texmf-dist/tex/latex/base/size10.clo -> \Ucom{kpsewhich small2e.tex} - /usr/local/texmf-dist/tex/latex/base/small2e.tex -> \Ucom{kpsewhich tugboat.bib} - /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib -\end{alltt} - -By the way, that last is a \BibTeX{} bibliography database for \textsl{TUGBoat} articles. - -\begin{alltt} -> \Ucom{kpsewhich cmr10.pk} -\end{alltt} -Font bitmap glyph files of type \file{.pk} are used by display -programs like \cmdname{dvips} and \cmdname{xdvi}. Nothing is returned in -this case since there are no pre-generated Computer Modern \samp{.pk} -files in \TL{}\Dash the Type~1 variants are used by default. -\begin{alltt} -> \Ucom{kpsewhich wsuipa10.pk} -\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk -\else /usr/local/texmf-var/fonts/pk/ljfour/public/ -... wsuipa/wsuipa10.600pk -\fi\end{alltt} -For these fonts (a phonetic alphabet from the University of Washington) -we had to generate \samp{.pk} files, and since the default \MF{} mode on -our installation is \texttt{ljfour} with a base resolution of 600\dpi{} -(dots per inch), this instantiation is returned. -\begin{alltt} -> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} -\end{alltt} -In this case, when specifying that we are interested in a resolution -of 300\dpi{} (\texttt{-dpi=300}) we see that no such font is available on -the system. A program like \cmdname{dvips} or \cmdname{xdvi} would -go off and actually build the required \texttt{.pk} files -using the script \cmdname{mktexpk}. - -Next we turn our attention to \cmdname{dvips}'s header and configuration -files. We first look at one of the commonly used files, the general -prologue \file{tex.pro} for \TeX{} support, before turning our attention -to the generic configuration file (\file{config.ps}) and the \PS{} font -map \file{psfonts.map}\Dash as of 2004, map and encoding files have -their own search paths and new location in \dirname{texmf} trees. As -the \samp{.ps} suffix is ambiguous we have to specify explicitly which -type we are considering (\optname{dvips config}) for the file -\texttt{config.ps}. -\begin{alltt} -> \Ucom{kpsewhich tex.pro} - /usr/local/texmf/dvips/base/tex.pro -> \Ucom{kpsewhich --format="dvips config" config.ps} - /usr/local/texmf/dvips/config/config.ps -> \Ucom{kpsewhich psfonts.map} - /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map -\end{alltt} - -We now take a closer look at the \acro{URW} Times \PS{} support -files. The prefix for these in the standard font naming scheme is -\samp{utm}. The first file we look at is the configuration file, -which contains the name of the map file: -\begin{alltt} -> \Ucom{kpsewhich --format="dvips config" config.utm} - /usr/local/texmf-dist/dvips/psnfss/config.utm -\end{alltt} -The contents of that file is -\begin{alltt} - p +utm.map -\end{alltt} -which points to the file \file{utm.map}, which we want to -locate next. -\begin{alltt} -> \Ucom{kpsewhich utm.map} - /usr/local/texmf-dist/fonts/map/dvips/times/utm.map -\end{alltt} -This map file defines the file names of the Type~1 \PS{} fonts in -the URW collection. Its contents look like (we only show part of the -lines): -\begin{alltt} -utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} -\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb -\else /usr/local/texmf-dist/fonts/type1/ -... urw/utm/utmr8a.pfb -\fi\end{alltt} - -It should be evident from these examples how you can easily locate the -whereabouts of a given file. This is especially important if you suspect -that the wrong version of a file is picked up somehow, since -\cmdname{kpsewhich} will show you the first file encountered. - -\subsubsection{Debugging actions} -\label{sec:debugging} - -Sometimes it is necessary to investigate how a program resolves file -references. To make this practical, \KPS{} offers various levels of -debugging output: - -\begin{ttdescription} -\item[\texttt{\ 1}] \texttt{stat} calls (disk lookups). When running - with an up-to-date \file{ls-R} database this should almost give no - output. -\item[\texttt{\ 2}] References to hash tables (such as \file{ls-R} - databases, map files, configuration files). -\item[\texttt{\ 4}] File open and close operations. -\item[\texttt{\ 8}] General path information for file types - searched by \KPS. This is useful to find out where a particular - path for the file was defined. -\item[\texttt{16}] Directory list for each path element (only relevant - for searches on disk). -\item[\texttt{32}] File searches. -\item[\texttt{64}] Variable values. -\end{ttdescription} -A value of \texttt{-1} will set all the above options; in practice, -this is usually the most convenient. - -Similarly, with the \cmdname{dvips} program, by setting a combination of -debug switches, one can follow in detail where files are being picked up -from. Alternatively, when a file is not found, the debug trace shows in -which directories the program looks for the given file, so that one can -get an indication what the problem~is. - -Generally speaking, as most programs call the \KPS{} library -internally, one can select a debug option by using the -\envname{KPATHSEA\_DEBUG} environment variable, and setting it to (a -combination of) values as described in the above list. - -(Note for Windows users: it is not easy to redirect -all messages to a file in this system. For diagnostic purposes -you can temporarily \texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log}). - -Let us consider, as an example, a small \LaTeX{} source file, -\file{hello-world.tex}, which contains the following input. -\begin{verbatim} - \documentclass{article} - \begin{document} - Hello World! - \end{document} -\end{verbatim} -This little file only uses the font \file{cmr10}, so let us look at -how \cmdname{dvips} prepares the \PS{} file (we want to use the Type~1 -version of the Computer Modern fonts, hence the option \texttt{-Pcms}). -\begin{alltt} -> \Ucom{dvips -d4100 hello-world -Pcms -o} -\end{alltt} -In this case we have combined \cmdname{dvips}'s debug class 4 (font -paths) with \KPS's path element expansion (see \cmdname{dvips} Reference -Manual, \OnCD{texmf/doc/dvips/dvips.pdf}). -The output (slightly rearranged) appears in -Figure~\ref{fig:dvipsdbga}. -\begin{figure*}[tp] -\centering -\input{examples/ex6a.tex} -\caption{Finding configuration files}\label{fig:dvipsdbga} - -\bigskip - -\input{examples/ex6b.tex} -\caption{Finding the prolog file}\label{fig:dvipsdbgb} - -\bigskip - -\input{examples/ex6c.tex} -\caption{Finding the font file}\label{fig:dvipsdbgc} -\end{figure*} - -\cmdname{dvips} starts by locating its working files. First, -\file{texmf.cnf} is found, which gives the definitions of the search -paths for the other files, then the file database \file{ls-R} (to -optimize file searching) and the file \file{aliases}, which makes it -possible to declare several names (e.g., a short \acro{DOS}-like 8.3 and -a more natural longer version) for the same file. Then \cmdname{dvips} -goes on to find the generic configuration file \file{config.ps} -before looking for the customization file \file{.dvipsrc} (which, in -this case is \emph{not found}). Finally, \cmdname{dvips} locates the -config file for the Computer Modern \PS{} fonts \file{config.cms} -(this was initiated with the \texttt{-Pcms} option on the \cmdname{dvips} -command). This file contains the list of the map files which -define the relation between the \TeX{}, \PS{} and file system -names of the fonts. -\begin{alltt} -> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} - p +ams.map - p +cms.map - p +cmbkm.map - p +amsbkm.map -\end{alltt} -\cmdname{dvips} thus goes on to find all these files, plus the generic -map file \file{psfonts.map}, which is always loaded (it contains -declarations for commonly used \PS{} fonts; see the last part of -Section \ref{sec:examples-of-use} for more details about \PS{} map -file handling). - -At this point \cmdname{dvips} identifies itself to the user: -\begin{alltt} -This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) -\end{alltt} -\ifSingleColumn -Then it goes on to look for the prolog file \file{texc.pro}: -\begin{alltt}\small -kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro -\end{alltt} -\else -Then it goes on to look for the prolog file \file{texc.pro} (see -Figure~\ref{fig:dvipsdbgb}). -\fi - -After having found the file in question, \cmdname{dvips} outputs -the date and time, and informs us that it will generate the -file \file{hello-world.ps}, then that it needs the font file -\file{cmr10}, and that the latter is declared as ``resident'' (no -bitmaps needed): -\begin{alltt}\small -TeX output 1998.02.26:1204' -> hello-world.ps -Defining font () cmr10 at 10.0pt -Font cmr10 is resident. -\end{alltt} -Now the search is on for the file \file{cmr10.tfm}, which is found, -then a few more prolog files (not shown) are referenced, and finally -the Type~1 instance \file{cmr10.pfb} of the font is located and -included in the output file (see last line). -\begin{alltt}\small -kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, - path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: - /var/tex/fonts/tfm//). -kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm -kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, - ... - -kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb -[1] -\end{alltt} - -\subsection{Runtime options} - -Another useful feature of \Webc{} is its possibility to control a number -of memory parameters (in particular, array sizes) via the runtime file -\file{texmf.cnf} read by \KPS{}. The memory settings can be found in -Part 3 of that file in the \TL{} distribution. The more important -are: - -\begin{ttdescription} -\item[\texttt{main\_memory}] - Total words of memory available, for - \TeX{}, \MF{} and \MP. You must make a new format file for each - different setting. For instance, you could generate a ``huge'' - version of \TeX{}, and call the format file \texttt{hugetex.fmt}. - Using the standard way of specifying the program name used by \KPS{}, - the particular value of the \texttt{main\_memory} variable will then - be read from \file{texmf.cnf}. -\item[\texttt{extra\_mem\_bot}] - Extra space for ``large'' \TeX{} data structures: - boxes, glue, breakpoints, etc. Especially useful if you use - \PiCTeX{}. -\item[\texttt{font\_mem\_size}] - Number of words for font information available for \TeX. This - is more or less the total size of all \acro{TFM} files read. -\item[\texttt{hash\_extra}] - Additional space for the hash table of control sequence names. - Only $\approx$10,000 control sequences can be stored in the main - hash table; if you have a large book with numerous cross-references, - this might not be enough. The default value of - \texttt{hash\_extra} is \texttt{50000}. -\end{ttdescription} - -\noindent Of course, this facility is no substitute for truly dynamic -arrays and memory allocation, but since these are extremely difficult to -implement in the present \TeX{} source, these runtime parameters provide -a practical compromise allowing some flexibility. - - -\begin{comment} -\section{Building on a new Unix platform} - -If you have a platform for which executables are not included, you will -need to compile \TeX{} and friends. This is not as hard as it -sounds. What you need is all in the directory \texttt{source} in the -distribution. - -\subsection{Prerequisites} - -You will need at least 100 megabytes of disk space to compile all of -\TeX{} and its support programs. You'll also need an \acro{ANSI} C -compiler, a \cmdname{make} utility, a lexical scanner, and a parser -generator. We recommend the \GNU version of these programs -(\cmdname{gcc}, \GNU \cmdname{make}, \cmdname{m4}, \cmdname{flex}, -\cmdname{bison}). You may be able to work with other C compilers and -\cmdname{make} programs, but you will need a good understanding of -building Unix programs to sort out problems. - -Also, the command \texttt{uname} must return a sensible value. - - -\subsection{Configuration} - -To begin, perform a normal installation of \TL{} to your disk (see -section~\ref{sec:install-disk} on -\p.\pageref{sec:install-disk}). You may wish to skip installing -all of the prebuilt binaries. - -Then, unpack the source from the compressed \texttt{tar} file in the -directory \dirname{source} to your disk and change directory to where -you placed it. - -Next, run \cmdname{configure} with a command line like this: -\begin{alltt} -> \Ucom{sh configure -prefix=/usr/local/TeX} -\end{alltt} - -The \optname{-prefix} directory is the one where you installed the -support tree; the directory layout will be as follows (where \$TEXDIR -stands for the directory you chose): - -\noindent -\begin{tabular}{>{\ttfamily}ll@{}} - \dirname{$TEXDIR/share/texmf} & main tree with fonts,\\ - & \qquad macros, etc\\ - \dirname{$TEXDIR/man} & Unix manual pages\\ - \dirname{$TEXDIR/info} & \GNU style Info manuals\\ - \dirname{$TEXDIR/bin/$PLATFORM} & binaries\\ -\end{tabular} -%$ - -If you want to leave out the \dirname{$PLATFORM} directory level, -i.e., put the binaries directly into \dirname{$TEXDIR/bin}, specify -the \verb|--disable-multiplatform| option to \cmdname{configure}. - -Have a look at the output of \verb|./configure --help| for more -options you can use. For example, you can skip building of \OMEGA{} and -\eTeX{}. - - -\subsection{Running \cmdname{make}} - -Make sure the shell variable or option \texttt{noclobber} is not set. -Then, run the main \cmdname{make} like this: -\begin{alltt} -> \Ucom{make world} -\end{alltt} -and relax\ldots - -Alternatively, you want to log all the output, as in: -\begin{alltt} -> \Ucom{sh -c "make world >world.log 2>\&1" \&} -\end{alltt} - -Before you believe that everything went ok, please check the log file -for errors: \GNU \cmdname{make} always uses the string \samp{***} -whenever a command fails. Also, check if all the programs were built: - -\begin{alltt} -> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} -> \Ucom{ls | wc} -\end{alltt} -The result should be over 200 (you can check the exact number with the -\dirname{bin} directory contents in the distribution). - -If you need special privileges for \texttt{make install}, you can -separate the \samp{make world} into two different runs, like this: -\begin{alltt} -> \Ucom{make all} -> \Ucom{su} -> \Ucom{make install strip} -\end{alltt} - -After you've installed your new binaries, you should follow the normal -post-installation procedures, given in section~\ref{sec:postinstall} -(\p.\pageref{sec:postinstall}). - -Also, if you'd like to make your binaries available to others, please -contact us. We'll be happy to put them on the \TL\ web pages. -\end{comment} - -\htmlanchor{ack} -\section{Acknowledgements} - -\TL{} is a joint effort by virtually all of the \TeX{} user groups. -This edition of \TL{} was overseen by Karl Berry. The other principal -contributors, past and present, are listed below. - -\begin{itemize*} - -\item The English, German, Dutch, and Polish \TeX{} user groups -(\acro{TUG}, \acro{DANTE} e.V., \acro{NTG}, and \acro{GUST}, -respectively), which provide the necessary technical and administrative -infrastructure. Please join the \TeX\ user group near you! (See -\url{http://tug.org/usergroups.html}.) - -\item The \acro{CTAN} team, most notably Robin Fairbairns, Jim Hef{}feron, -and Rainer Sch\"opf, which distributes the \TL{} images and provides the -common infrastructure for package updates, upon which \TL{} depends. - -\item Peter Breitenlohner (and the \eTeX\ team) for the stable foundation -of future \TeX's, and Peter specifically for stellar help with the GNU -autotools usage throughout \TL. - -\item Thomas Esser, without whose marvelous \teTeX{} package \TL{} -would have never existed. - -\item Michel Goossens, who co-authored the original documentation. - -\item Eitan Gurari, whose \TeX4ht was used to create the \HTML{} -version of this documentation, and who worked tirelessly to improve -it at short notice. - -\item \Thanh, Martin Schr\"oder, and the pdf\TeX\ team -(\url{http://pdftex.org}) for continuing enhancements of \TeX's -abilities. - -\item Hans Hagen, for much testing and making his \ConTeXt\ format -(\url{http://pragma-ade.com}) work within \TL's framework. - -\item Hartmut Henkel, for significant development contributions to -pdf\TeX\, Lua\TeX, and more. - -\item Taco Hoekwater, for renewed development efforts on MetaPost and -(Lua)\TeX\ (\url{http://luatex.org}) itself, and for incorporating -\ConTeXt\ into \TL. - -\item Pawe{\l} Jackowski, for the Windows installer \cmdname{tlpm}, -and Tomasz {\L}uczak, for \cmdname{tlpmgui}, used in past releases. - -\item Akira Kakuto, for providing the Windows -binaries from his \acro{W32TEX} distribution for Japanese \TeX\ -(\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}), and many -other contributions. - -\item Jonathan Kew and \acro{SIL}, for the major new development of -\XeTeX{} and taking the time and trouble to integrate it in \TL{}, as -well as the initial version of the Mac\TeX\ installer. - -\item Dick Koch, for maintaining Mac\TeX\ (\url{http://tug.org/mactex}) -in very close tandem with \TL{}, and for his great good cheer in doing -so. - -\item Reinhard Kotucha, for major contributions to the \TL{} 2008 -infrastructure and installer, as well as Windows research efforts, the -\texttt{getnonfreefonts} script, and more. - -\item Siep Kroonenberg, also for major contributions to the \TL{} 2008 -infrastructure and installer, especially on Windows, and for the bulk of -work updating this manual describing the new features. - -\item Petr Ol\v{s}ak, who coordinated and checked all the Czech and Slovak -material very carefully. - -\item Toshio Oshima, for his \cmdname{dviout} previewer for Windows. - -\item Manuel P\'egouri\'e-Gonnard, for helping with package updates, -documentation improvements, and \cmdname{tldoc} development. - -\item Fabrice Popineau, for the original Windows support in \TL{} and -work on the French documentation. - -\item Norbert Preining, the principal architect of the \TL{} 2008 -infrastructure and installer, and also for coordinating the Debian -version of \TL{} (together with Frank K\"uster), making many suggestions -along the way. - -\item Sebastian Rahtz, for originally creating \TL{} and maintaining it -for many years. - -\item Phil Taylor, for setting up the BitTorrent downloads. - -\item Vladimir Volovich, for substantial help with porting and other -maintenance issues, and especially for making it feasible to include -\cmdname{xindy}. - -\item Staszek Wawrykiewicz, the principal tester for all of \TL{}, -and coordinator of the many major Polish contributions: fonts, Windows -installation, and more. - -\item Olaf Weber, for his patient maintenance of \Webc. - -\item Gerben Wierda, for creating and maintaining the \MacOSX\ support, -and much integration and testing. - -\item Graham Williams, on whose work the \TeX\ Catalogue of packages depends. - -\end{itemize*} - -Builders of the binaries: -Reinhard Kotucha (\pkgname{x86\_64-linux}), -Tim Arnold (\pkgname{hppa-hpux}), -Randy Au (\pkgname{amd64-freebsd}), -Edd Barrett (\pkgname{i386-openbsd}), -Karl Berry (\pkgname{i386-linux}), -Akira Kakuto (\pkgname{win32}), -Dick Koch (\pkgname{universal-darwin}), -Manfred Lotz (\pkgname{i386-freebsd}), -Norbert Preining (\pkgname{alpha-linux}), -Arthur Reutenauer (\pkgname{sparc-linux}), -Thomas Schmitz (\pkgname{powerpc-linux}), -Apostolos Syropoulos (\pkgname{i386-solaris}), -Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-solaris}), -Olaf Weber (\pkgname{mips-irix}). -For information on the \TL{} build process, see -\url{http://tug.org/texlive/build.html}. - -Documentation and translation updates: -Karl Berry (English), -Daniel Flipo (French), -Klaus H\"oppner (German), -Petr Sojka \& Jan Busa (Czech\slash Slovak), -Boris Veytsman (Russian), -Staszek Wawrykiewicz (Polish). The \TL{} documentation web page -is \url{http://tug.org/texlive/doc.html}. - -Of course the most important acknowledgement must go to Donald Knuth, -first for inventing \TeX, and then for giving it to the world. - - - -\section{Release history} -\label{sec:history} - -\subsection{Past} - -Discussion began in late 1993 when the Dutch \TeX{} Users Group was -starting work on its 4All\TeX{} \CD{} for \acro{MS-DOS} users, and it -was hoped at that time to issue a single, rational, \CD{} for all -systems. This was too ambitious a target for the time, but it did spawn -not only the very successful 4All\TeX{} \CD{}, but also the \acro{TUG} -Technical Council working group on a \emph{\TeX{} Directory Structure} -(\url{http://tug.org/tds}), which specified how to create consistent and -manageable collections of \TeX{} support files. A complete draft of the -\TDS{} was published in the December 1995 issue of \textsl{TUGboat}, and -it was clear from an early stage that one desirable product would be a -model structure on \CD{}. The distribution you now have is a very direct -result of the working group's deliberations. It was also clear that the -success of the 4All\TeX{} \CD{} showed that Unix users would benefit -from a similarly easy system, and this is the other main strand of -\TL. - -We first undertook to make a new Unix-based \TDS{} \CD{} in the autumn -of 1995, and quickly identified Thomas Esser's \teTeX{} as the ideal -setup, as it already had multi-platform support and was built with -portability across file systems in mind. Thomas agreed to help, and work -began seriously at the start of 1996. The first edition was released in -May 1996. At the start of 1997, Karl Berry completed a major new release -of Web2c, which included nearly all the features which Thomas Esser had -added in \teTeX, and we decided to base the 2nd edition of the \CD{} on -the standard \Webc, with the addition of \teTeX's \texttt{texconfig} -script. The 3rd edition of the \CD{} was based on a major revision of -\Webc, 7.2, by Olaf Weber; at the same time, a new revision of \teTeX -was being made, and \TL{} included almost all of its features. The -4th edition followed the same pattern, using a new version of \teTeX, -and a new release of \Webc{} (7.3). The system now included a complete -Windows setup. - -For the 5th edition (March 2000) many parts of the \CD{} were revised -and checked, updating hundreds of packages. Package details were stored -in XML files. But the major change for \TeX\ Live 5 was that all -non-free software was removed. Everything in \TL{} is now intended -to be compatible with the Debian Free Software Guidelines -(\url{http://www.debian.org/intro/free}); we have done our best to check -the license conditions of all packages, but we would very much -appreciate hearing of any mistakes. - -The 6th edition (July 2001) had much more material updated. The major -change was a new install concept: the user could select a more exact set -of needed collections. Language-related collections were completely -reorganized, so selecting any of them installs not only macros, fonts, -etc., but also prepares an appropriate \texttt{language.dat}. - -The 7th edition of 2002 had the notable addition of \MacOSX{} support, -and the usual myriad of updates to all sorts of packages and -programs. An important goal was integration of the source back with -\teTeX, to correct the drift apart in versions~5 and~6. - -\subsubsection{2003} - -In 2003, with the continuing flood of updates and additions, we found -that \TL{} had grown so large it could no longer be contained on a -single \CD, so we split it into three different distributions (see -section~\ref{sec:tl-coll-dists}, \p.\pageref{sec:tl-coll-dists}). In -addition: - -\begin{itemize*} -\item At the request of the \LaTeX{} team, we changed the standard - \cmdname{latex} and \cmdname{pdflatex} commands to now use \eTeX{} (see - \p.\pageref{text:etex}). -\item The new Latin Modern fonts were included (and are recommended). -\item Support for Alpha \acro{OSF} was removed - (\acro{HPUX} support was removed previously), since no one had (or - volunteered) hardware available on which to compile new binaries. -\item Windows setup was substantially changed; for the first time - an integrated environment based on XEmacs was introduced. -\item Important supplementary programs for Windows - (Perl, Ghost\-script, Image\-Magick, Ispell) are now installed - in the \TL{} installation directory. -\item Font map files used by \cmdname{dvips}, \cmdname{dvipdfm} - and \cmdname{pdftex} are now generated by the new program - \cmdname{updmap} and installed into \dirname{texmf/fonts/map}. -\item \TeX{}, \MF{}, and \MP{} now, by default, output most input - characters (32 and above) as themselves in output (e.g., - \verb|\write|) files, - log files, and the terminal, i.e., \emph{not} translated using the - \verb|^^| notation. In \TL{}~7, this translation was - dependent on the system locale settings; now, locale settings do - not influence the \TeX{} programs' behavior. If for some reason - you need the \verb|^^| output, rename the file - \verb|texmf/web2c/cp8bit.tcx|. (Future releases will have cleaner - ways to control this.) -\item This documentation was substantially revised. -\item Finally, since the edition numbers had grown unwieldy, - the version is now simply identified by the year: \TL{} 2003. -\end{itemize*} - - -\subsubsection{2004} - -2004 saw many changes: - -\begin{itemize} - -\item If you have locally-installed fonts which use their own -\filename{.map} or (much less likely) \filename{.enc} support files, you -may need to move those support files. - -\filename{.map} files are now searched for in subdirectories of -\dirname{fonts/map} only (in each \filename{texmf} tree), along the -\envname{TEXFONTMAPS} path. Similarly, \filename{.enc} files are now -searched for in subdirectories of \dirname{fonts/enc} only, along the -\envname{ENCFONTS} path. \cmdname{updmap} will attempt to warn about -problematic files. - -For methods of handling this and other information, please see -\url{http://tug.org/texlive/mapenc.html}. - -\item The \TK\ has been expanded with the addition of a \MIKTEX-based -installable \CD, for those who prefer that implementation to Web2C. -See section~\ref{sec:overview-tl} (\p.\pageref{sec:overview-tl}). - -\item Within \TL, the single large \dirname{texmf} tree of previous -releases has been replaced by three: \dirname{texmf}, -\dirname{texmf-dist}, and \dirname{texmf-doc}. See -section~\ref{sec:tld} (\p.\pageref{sec:tld}), and the \filename{README} -files for each. - -\item All \TeX-related input files are now collected in -the \dirname{tex} subdirectory of \dirname{texmf*} trees, rather than -having separate sibling directories \dirname{tex}, \dirname{etex}, -\dirname{pdftex}, \dirname{pdfetex}, etc. See -\CDref{texmf-doc/doc/english/tds/tds.html\#Extensions} -{\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}. - -\item Helper scripts (not meant to be invoked by users) are now located -in a new \dirname{scripts} directory of \dirname{texmf*} trees, and -searched for via \verb|kpsewhich -format=texmfscripts|. So if you have -programs which call such scripts, they'll need to be adjusted. See -\CDref{texmf-doc/doc/english/tds/tds.html\#Scripts} -{\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}. - -\item Almost all formats leave most characters printable as -themselves via the ``translation file'' \filename{cp227.tcx}, instead of -translating them with the \verb|^^| notation. Specifically, characters -at positions 32--256, plus tab, vertical tab, and form feed are -considered printable and not translated. The exceptions are plain \TeX\ -(only 32--126 printable), \ConTeXt\ (0--255 printable), and the -\OMEGA-related formats. This default behavior is almost the same as in -\TL\,2003, but it's implemented more cleanly, with more possibilities -for customization. See \CDref{texmf/doc/web2c/web2c.html\#TCX-files} -{\texttt{texmf/doc/web2c/web2c.html\#TCX-files}}. -(By the way, with Unicode input, \TeX\ may output partial character -sequences when showing error contexts, since it is byte-oriented.) - -\item \textsf{pdfetex} is now the default engine for all formats -except (plain) \textsf{tex} itself. (Of course it generates \acro{DVI} -when run as \textsf{latex}, etc.) This means, among other things, that -the microtypographic features of \textsf{pdftex} are available in -\LaTeX, \ConTeXt, etc., as well as the \eTeX\ features -(\OnCD{texmf-dist/doc/etex/base/}). - -It also means it's \emph{more important than ever} to use the -\pkgname{ifpdf} package (works with both plain and \LaTeX) or equivalent -code, because simply testing whether \cs{pdfoutput} or some other -primitive is defined is not a reliable way to determine if \acro{PDF} -output is being generated. We made this backward compatible as best we -could this year, but next year, \cs{pdfoutput} may be defined even when -\acro{DVI} is being written. - -\item pdf\TeX\ (\url{http://pdftex.org}) has many new features: - - \begin{itemize*} - - \item \cs{pdfmapfile} and \cs{pdfmapline} provide font map support - from within a document. - - \item Microtypographic font expansion can be used more easily.\\ - \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} - - \item All parameters previously set through the special configuration - file \filename{pdftex.cfg} must now be set through primitives, - typically in \filename{pdftexconfig.tex}; \filename{pdftex.cfg} is no - longer supported. Any extant \filename{.fmt} files must be redumped - when \filename{pdftexconfig.tex} is changed. - - \item See the pdf\TeX\ manual for more: \OnCD{texmf-dist/doc/pdftex/manual/pdftex-a.pdf}. - - \end{itemize*} - -\item The \cs{input} primitive in \cmdname{tex} (and \cmdname{mf} and -\cmdname{mpost}) now accepts double quotes containing spaces and other -special characters. Typical examples: -\begin{verbatim} -\input "filename with spaces" % plain -\input{"filename with spaces"} % latex -\end{verbatim} -See the Web2C manual for more: \OnCD{texmf/doc/web2c}. - -\item enc\TeX\ support is now included within Web2C and consequently all -\TeX\ programs, via the \optname{-enc} option\Dash \emph{only when -formats are built}. enc\TeX\ supports general re-encoding of input and -output, enabling full support of Unicode (in \acro{UTF}-8). See -\OnCD{texmf-dist/doc/generic/enctex/} and -\url{http://www.olsak.net/enctex.html}. - -\item Aleph, a new engine combining \eTeX\ and \OMEGA, is available. -A little information is available in \OnCD{texmf-dist/doc/aleph/base} -and \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph}. The -\LaTeX-based format for Aleph is named \textsf{lamed}. - -\item The latest \LaTeX\ release has a new version of the -\acro{LPPL}\Dash now officially a Debian-approved license. Assorted -other updates, see the \filename{ltnews} files in -\OnCD{texmf-dist/doc/latex/base}. - -\item \cmdname{dvipng}, a new program for converting \acro{DVI} to -\acro{PNG} image files, is included. See \OnCD{texmf/doc/man/man1/dvipng.1}. - -\item We reduced the \pkgname{cbgreek} package to a ``medium'' sized set -of fonts, with the assent and advice of the author (Claudio Beccari). -The excised fonts are the invisible, outline, and transparency ones, -which are relatively rarely used, and we needed the space. The full set -is of course available from \acro{CTAN} -(\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). - -\item \cmdname{oxdvi} has been removed; just use \cmdname{xdvi}. - -\item The \cmdname{ini} and \cmdname{vir} commands (links) for -\cmdname{tex}, \cmdname{mf}, and \cmdname{mpost} are no longer created, -such as \cmdname{initex}. The \cmdname{ini} functionality has been -available through the command-line option \optname{-ini} for years now. - -\item \textsf{i386-openbsd} platform support was removed. Since the -\pkgname{tetex} package in the \acro{BSD} Ports system is available, and -\acro{GNU/}Linux and Free\acro{BSD} binaries were available, it seemed -volunteer time could be better spent elsewhere. - -\item On \textsf{sparc-solaris} (at least), you may have to set the -\envname{LD\_LIBRARY\_PATH} environment variable to run the -\pkgname{t1utils} programs. This is because they are compiled with C++, -and there is no standard location for the runtime libraries. (This is -not new in 2004, but wasn't previously documented.) Similarly, on -\textsf{mips-irix}, the \acro{MIPS}pro 7.4 runtimes are required. - -\end{itemize} - -\subsubsection{2005} - -2005 saw the usual huge number of updates to packages and programs. -The infrastructure stayed relatively stable from 2004, but inevitably -there were some changes there as well: - -\begin{itemize} - -\item New scripts \cmdname{texconfig-sys}, \cmdname{updmap-sys}, and - \cmdname{fmtutil-sys} were introduced, which modify the - configuration in the system trees. The \cmdname{texconfig}, - \cmdname{updmap}, and \cmdname{fmtutil} scripts now modify - user-specific files, under \dirname{$HOME/.texlive2005}. - -\item Corresponding new variables \envname{TEXMFCONFIG} and - \envname{TEXMFSYSCONFIG} to specify the trees where configuration - files (user or system, respectively) are found. Thus, you may - need to move personal versions of \filename{fmtutil.cnf} and - \filename{updmap.cfg} to these places; another option is to - redefine \envname{TEXMFCONFIG} or \envname{TEXMFSYSCONFIG} in - \filename{texmf.cnf}. In any case the real location of these files - and the values of \envname{TEXMFCONFIG} and \envname{TEXMFSYSCONFIG} - must agree. - See section~\ref{sec:texmftrees}, \p.\pageref{sec:texmftrees}. - -\item Last year, we kept \verb|\pdfoutput| and other primitives undefined - for \dvi\ output, even though the \cmdname{pdfetex} program was - being used. This year, as promised, we undid that compatibility - measure. So if your document uses \verb|\ifx\pdfoutput\undefined| - to test if PDF is being output, it will need to be changed. You - can use the package \pkgname{ifpdf.sty} (which works under both - plain \TeX\ and \LaTeX) to do this, or steal its logic. - -\item Last year, we changed most formats to output (8-bit) characters as - themselves (see previous section). The new TCX file - \filename{empty.tcx} now provides an easier way to get the - original \verb|^^| notation if you so desire, as in: -\begin{verbatim} -latex --translate-file=empty.tcx yourfile.tex -\end{verbatim} - -\item The new program \cmdname{dvipdfmx} is included for translation of - DVI to PDF; this is an actively maintained update of - \cmdname{dvipdfm} (which is also still available for now, though - no longer recommended). - -\item The new programs \cmdname{pdfopen} and \cmdname{pdfclose} are included - to allow reloading of pdf files in the Adobe Acrobat Reader without - restarting the program. (Other pdf readers, notably \cmdname{xpdf}, - \cmdname{gv}, and \cmdname{gsview}, have never suffered from this - problem.) - -\item For consistency, the variables \envname{HOMETEXMF} and - \envname{VARTEXMF} have been renamed to \envname{TEXMFHOME} and - \envname{TEXMFSYSVAR}, respectively. There is also - \envname{TEXMFVAR}, which is by default user-specific. See the - first point above. - -\end{itemize} - - -\subsubsection{2006--2007} - -In 2006--2007, the major new addition to \TL{} was the \XeTeX{} program, -available as the \texttt{xetex} and \texttt{xelatex} programs; see -\url{http://scripts.sil.org/xetex}. - -MetaPost also received a notable update, with more planned for the -future (\url{http://tug.org/metapost/articles}), likewise pdf\TeX{} -(\url{http://tug.org/applications/pdftex}). - -The \TeX\ \filename{.fmt} (high-speed format) and the similar files for -MetaPost and \MF\ are now stored in subdirectories of \dirname{texmf/web2c}, -instead of in the directory itself (although the directory is still -searched, for the sake of existing \filename{.fmt}'s). The -subdirectories are named for the `engine' in use, such as \filename{tex} -or \filename{pdftex} or \filename{xetex}. This change should be -invisible in normal use. - -The (plain) \texttt{tex} program no longer reads \texttt{\%\&} first -lines to determine what format to run; it is the pure Knuthian \TeX. -(\LaTeX\ and everything else do still read \texttt{\%\&} lines). - -Of course the year also saw (the usual) hundreds of other updates to -packages and programs. As usual, please check \acro{CTAN} -(\url{http://www.ctan.org}) for updates. - -Internally, the source tree is now stored in Subversion, with a standard -web interface for viewing the tree, as linked from our home page. -Although not visible in the final distribution, we expect this will -provide a stable development foundation for future years. - -Finally, in May 2006 Thomas Esser announced that he would no longer be -updating te\TeX{} (\url{http://tug.org/tetex}). As a result, there was -been a surge of interest in \TL{}, especially among \GNU/Linux -distributors. (There is a new \texttt{tetex} installation scheme in -\TL{}, which provides an approximate equivalent.) We hope this will -eventually translate to improvements in the \TeX\ environment for -everyone. - -\medskip \noindent -Final note on the past: all releases of \TL{}, along with ancillary -material such as \CD\ labels, are available at -\url{ftp://tug.org/historic/systems/texlive}. - -\htmlanchor{news} -\subsection{Present} -\label{sec:tlcurrent} - -In 2008, the entire \TL{} infrastructure was redesigned and -reimplemented. Complete information about an installation is now stored -in a plain text file \filename{tlpkg/texlive.tlpdb}. - -Among other things, this finally makes possible upgrading a \TL{} -installation over the Internet after the initial installation, a feature -MiK\TeX\ has provided for many years. We expect to regularly update new -packages as they are released to \CTAN. - -The major new engine Lua\TeX\ (\url{http://luatex.org}) is included; -besides a new level of flexibility in typesetting, this provides an -excellent scripting language for use both inside and outside of \TeX\ -documents. - -Support among Windows and the Unix-based platforms is now much more -uniform. In particular, most Perl and Lua scripts are now available on -Windows, using the Perl internally distributed with \TL. - -The new \cmdname{tlmgr} script (section~\ref{sec:tlmgr}) is the -general interface for managing \TL{} after the initial installation. -It handles package updates and consequent regeneration of formats, map -files, and language files, optionally including local additions. - -With the advent of \cmdname{tlmgr}, the \cmdname{texconfig} actions to -edit the format and hyphenation configuration files are now disabled. - -The \cmdname{xindy} indexing program -(\url{http://xindy.sourceforge.net/}) is now included on most platforms. - -The \cmdname{kpsewhich} tool can now report all matches for a given file -(option \optname{--all}) and limit matches to a given subdirectory -(option \optname{--subdir}). - -The \cmdname{dvipdfmx} program now includes functionality to extract -bounding box information, via the command name \cmdname{extractbb}; this -was one of the last features provided by \cmdname{dvipdfm} not in -\cmdname{dvipdfmx}. - -The font aliases \filename{Times-Roman}, \filename{Helvetica}, and so on -have been removed. Different packages expected them to behave -differently (in particular, to have different encodings), and there was -no good way to resolve this. - -The \pkgname{platex} format has been removed, to resolve a name conflict -with a completely different Japanese \pkgname{platex}; the -\pkgname{polski} package is now the main Polish support. - -Internally, the \web\ string pool files are now compiled into the -binaries, to ease upgrades. - -Finally, the changes made by Donald Knuth in his `\TeX\ tuneup of 2008' -are included in this release. See -\url{http://tug.org/TUGboat/Articles/tb29-2/tb92knut.pdf}. - - -\subsection{Future} - -\emph{\TL{} is not perfect!} (And never will be.) We intend to -continue to release new versions, and would like to provide more help -material, more utilities, more installation programs, and (of course) an -ever-improved and better-checked tree of macros and fonts. This work is -all done by hard-pressed volunteers in their limited spare time, and a -great deal remains to be done. Please see -\url{http://tug.org/texlive/contribute.html}. - -Please send corrections, suggestions, and offers of help to: -\begin{quote} -\email{tex-live@tug.org} \\ -\url{http://tug.org/texlive} -\end{quote} - -\medskip -\noindent \textsl{Happy \TeX ing!} - -\end{document} diff --git a/Master/texmf-doc/source/texlive/texlive-fr/Makefile b/Master/texmf-doc/source/texlive/texlive-fr/Makefile deleted file mode 100644 index 519abf8798a..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-fr/Makefile +++ /dev/null @@ -1,5 +0,0 @@ -include ../texlive-en/Makefile -doc = texlive-fr -lang = french - - diff --git a/Master/texmf-doc/source/texlive/texlive-fr/live.tex b/Master/texmf-doc/source/texlive/texlive-fr/live.tex deleted file mode 100644 index ccb25a86f0b..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-fr/live.tex +++ /dev/null @@ -1,3945 +0,0 @@ -%Format: pdf - -% $Id: //depot/Master/texmf-doc/source/english/texlive-en/live.tex#31 $ -% $Author: staw $ $Date: 2005/10/31 $ -% -% Change history (started May 18th 2002) -% 2007/01/18: synced with 2007 English version, by Daniel Flipo -% 2005/11/01: synced with 2005 English version, by Daniel Flipo -% 2005/05/05: re-added section on building binaries (Daniel Flipo) -% 2004/10/28: synced with 2004 English version, by Daniel Flipo -% 2003/08/28: synced with 2003 English version, by Éric Picheral and Jacques André -% 2002/05/25: proof-reading and corrections, by Daniel Flipo -% 2002/05/18: synced with English version, by Fabrice -% -\documentclass{article} -%\let\tldocenglish=1 % *NOT* for French - -\usepackage[latin1]{inputenc} - -\usepackage{caption} -\DeclareCaptionLabelSeparator{endash}{\space\textendash\space} -\captionsetup{labelsep=endash} - -\usepackage[frenchb]{babel} -\usepackage{xspace} -\addto\captionsfrench{\def\figurename{{\scshape Figure}}} -\addto\captionsfrench{\def\tablename{{\scshape Table}}} -\AddThinSpaceBeforeFootnotes -\FrenchFootnotes -\NoAutoSpaceBeforeFDP - -\newcommand{\THANH}{Hàn Th\'{ê} Thanh} - -\usepackage{comment} - -\usepackage{ifpdf} -% tex-live.sty suppose \hyper@linkurl défini... -\ifpdf - \def\Status{1} % (df) Pour faire charger hyperref dans tex-live.sty -\else - \makeatletter - \def\hyper@linkurl#1#2{#2} % undefined if hyperref.sty not loaded - \makeatother -\fi - -\usepackage{tex-live} -%%%% Ajout J.A. à garder -\newcommand{\CDdemo}{\acro{CD} \pkgname{demo}\xspace} -\newcommand{\CDinst}{\acro{CD} \pkgname{inst}\xspace} -\newcommand{\DVDlive}{\acro{DVD} \pkgname{live}\xspace} -\renewcommand{\samp}[1]{\og \texttt{#1}\fg{}} - -%%%% Ajout (df) -% Alias -\let\XemTeX\XEmTeX -% (df) La commande \TeXLive n'est pas utilisée en v.f. -\renewcommand{\TL}{\TeX{} Live\xspace}% Robuste (pas besoin de \protect)... -% tex-live.sty fait précéder les no de page d'une fine... si on veut -% une insécable normale, décommenter la ligne suivante : -\def\p.{p.~} -% Chez Karl, la commande \url{} ne protège pas les caractères actifs (:?), -% d'où ceci (essai provisoire... erreurs avec le car. #) : -%\let\urlORI\url -%\renewcommand*{\url}[1]{\foreignlanguage{english}{\urlORI{#1}}} -%\renewcommand*{\url}[1]{{\shorthandoff{:?!;}\urlORI{#1}}} -% La commande \path de url.sty ajoute des espaces parasites, pas \url, d'où -\let\path\url -% mais ceci impose de remplacer \path|...| par \path{...}, et les \$ inclus -% par des $. - -\setlength{\parindent}{0mm} -\addtolength{\parskip}{.25\baselineskip} - -\begin{document} - -\title{{\huge Guide pratique de \TL{}} \\ \strut - {\LARGE\textsf{\TK{} 2007}} - } - -\author{Karl Berry \\[3mm] - \url{http://tug.org/texlive/}\\[5mm] - \textit{Version française}\\[3mm] - Daniel Flipo (GUTenberg) - } - -\date{Janvier 2007} - -\maketitle -\thispagestyle{empty} % no need for page number - -\newpage -\begin{multicols}{2} -\tableofcontents -\listoftables -\end{multicols} - -\section{Introduction} -\label{sec:intro} - -Ce document décrit les principales caractéristiques de la -distribution \TL{}, une distribution de \TeX{} et \LaTeX{} -pour Linux et autres Unix, \MacOSX{} et systèmes Windows 32 bits -(attention, cette distribution n'est pas vraiment utilisable avec -les anciens systèmes Mac ou \acro{MS-DOS}). Elle comprend les binaires -pré-compilés de \TeX{}, \LaTeXe{}, \MF, \MP, \BibTeX{} et de nombreux -autres programmes ainsi qu'une bibliothèque étendue de macros, de -fontes et de documentations. Elle traite aussi la composition de textes -qui utilisent plusieurs systèmes d'écritures différentes venant de toute -la surface du globe. -La distribution \TL{} est en fait un sous-ensemble de \TK{} (décrit brièvement -à la section ~\ref{sec:struct-tl}, \p.\pageref{sec:struct-tl}) -produit grâce aux efforts combinés des différents groupes d'utilisateurs -de \TeX. - -L'édition 2007 a été figée en janvier 2007. -Les futures mises à jour des composants de la distribution 2007 -seront disponibles au fur et à mesure de leur parution sur le site -\acro{CTAN}, \url{http://www.ctan.org}. - -On trouvera à la fin du document, section~\ref{sec:history} -(\p.\pageref{sec:history}), un bref historique des principales modifications -apportées au fil du temps à la distribution \TL. - -Les utilisateurs des éditions précédentes de \TL{} sont invités -à lire, \emph{avant toute mise à jour}, la section~\ref{tlcurrent} -\p.\pageref{tlcurrent} qui présente les principaux changements intervenus -cette année. - - -\subsection{Utilisation élémentaire de \TL{}} -\label{sec:basic} - -Vous pouvez utiliser \TL{} de trois façons différentes : -\begin{enumerate} -\item Vous pouvez exécuter \TL{} directement depuis le - \DVDlive{} (toutes plates-formes). - Cela prend très peu d'espace disque et - donne un accès immédiat à tout le contenu de - \TL. C'est une solution parfaitement acceptable même si les - performances obtenues sont moins bonnes que si \TL{} était - lancé depuis un disque local. -\item Vous pouvez installer tout ou partie de \TL{} sur un disque - local. C'est l'utilisation la plus fréquente de \TL{}. - Ceci peut se faire à partir du \DVDlive{} ou de l'un des \CD de la - distribution (voir section~\ref{sec:multiple-dist}, - \p.\pageref{sec:multiple-dist}). - Il faut disposer d'un minimum de 120\,Mo, mais on recommande au moins -%(df) un peu mensonger... schéma GUT = 800 Mo chez moi ! - 400\,Mo pour un système standard ou 800\,Mo pour un système complet. -\item Vous pouvez incorporer un jeu de composants particulier ou une - collection dans un système \TeX{} déjà présent, soit un - système \TL{} installé précédemment, soit un système \TeX{} différent. -\end{enumerate} - -Ces trois utilisations sont décrites en détail dans les sections -concernant l'installation spécifique à chaque système. -Quelques remarques générales : - -\begin{itemize} - -\item Le script d'installation globale pour Unix et pour \MacOSX{} s'appelle -\texttt{install-tl.sh}. -Les utilisateurs de Linux peuvent aussi essayer le nouvel installeur -\texttt{setuptl/tlpmgui} développé au départ pour Windows et adapté à Linux. -Consulter la section \ref{sec:win-install} p.~\pageref{sec:win-install} pour -plus d'informations. - -\item Pour installer une extension ou une collection, on utilise le script - d'installation \texttt{install-pkg.sh}. -Après une installation faite à l'aide de \texttt{tlpmgui}, il est possible -d'utiliser \texttt{tlpmgui} pour ajouter ou supprimer des extensions ou des -collections. - -\item Le programme d'installation pour Windows s'appelle - \cmdname{tlpmgui.exe}, il sert aussi à ajouter ou supprimer des composants - dans une installation existante (voir section~\ref{sec:win-install}). - -\end{itemize} - -\subsection{Obtenir de l'aide} -\label{sec:help} - -La communauté \TeX{} est à la fois active et conviviale ; pratiquement -toute question sérieuse finit par obtenir une réponse. Le support est -pourtant informel, assuré par des volontaires et des lecteurs -occasionnels, aussi est-il particulièrement important que vous fassiez -votre propre travail de recherche avant de poser la question (si vous -préférez un support commercial, vous pouvez renoncer à \TL{} et -acheter un système payant ; voir une liste à -\url{http://tug.org/interest.html#vendors}). - -Voici une liste de ressources, classées selon l'ordre dans lequel nous -recommandons de les utiliser : - -\begin{description} -\item [Getting Started] Pour ceux qui débutent en \TeX, la page web -\url{http://tug.org/begin.html} contient une courte description -du système. - -\item [\acro{FAQ} \TeX{}] La \acro{FAQ} \TeX{} est un vaste recueil - de réponses à toutes sortes de questions, de la plus élémentaire à la - plus complexe. Elle est enregistrée sur le \DVDlive{} dans - \OnCD{texmf-doc/doc/english/FAQ-en} - et elle est disponible sur Internet à - l'adresse \url{http://www.tex.ac.uk/faq}. - Merci de consulter cette FAQ avant toute question. - -\item [Catalogue \TeX{}] Si vous recherchez une extension, une fonte, - un programme, ... particuliers, il faut examiner le catalogue - \TeX{}. C'est une importante liste de tous les éléments relatifs à - \TeX{}. Voir \OnCD{texmf-doc/doc/english/catalogue} sur le \DVDlive{}, - ou \url{http://www.ctan.org/tex-archive/help/Catalogue}. - -\item [Ressources \TeX{} sur le Web ] La page web - \url{http://tug.org/interest.html} propose - beaucoup de liens relatifs à \TeX{}, en particulier concernant des - livres, manuels et articles portant sur tous les aspects du système. - -\item [Archives des forums d'aide] Les principaux forums dédiés - au support de \TeX{} sont les groupes de news Usenet - \url{news:comp.text.tex} (en anglais) et \url{news:fr.comp.text.tex} - (en français) ainsi que les listes de diffusion - \email{texhax@tug.org} (en anglais) et \email{gut@ens.fr} (en français). - Les archives correspondantes contiennent des - milliers de questions et réponses déjà traitées et permettent - une recherche fructueuse. Voir - \url{http://groups.google.com/groups?group=comp.text.tex} - et \url{http://tug.org/mail-archives/texhax}, respectivement. Une - question posée sur un moteur de recherche, tel que - \url{http://google.com}, peut aussi fournir des réponses pertinentes. - -\item [Poster une question] Si vous n'obtenez pas de réponse, vous - pouvez poster la question à \dirname{comp.text.tex} via Google ou - votre lecteur de news, ou encore par messagerie à - \email{texhax@tug.org}. Mais avant de le faire, merci de lire - l'introduction de la \acro{FAQ} donnant les conseils sur la façon de - rédiger la question pour avoir des chances d'obtenir une réponse : - \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. - -\item [Support de \TL{}] Si vous voulez faire un rapport - d'anomalie, émettre des suggestions ou des commentaires sur la - distribution \TL{}, l'installation ou la documentation, utilisez - la liste de diffusion \email{tex-live@tug.org}. Mais attention, si - la question concerne l'utilisation d'un programme particulier inclus - dans \TL{}, il vaut mieux que vous écriviez directement à la - personne ou à la liste de diffusion qui maintient le programme. - -\end{description} - -L'autre aspect du sujet concerne l'aide à apporter aux personnes -soumettant des questions. Les forums \dirname{comp.text.tex}, -\dirname{fr.comp.text.tex} ainsi que les listes de diffusion \code{texhax} -et \code{gut} -sont ouverts à tous, aussi n'hésitez pas à vous y joindre, à commencer -la lecture et à fournir de l'aide là où cela vous est possible. -Bienvenue dans le monde \TeX{} ! - -% No \protect needed as \TL is defined in French with \newcommand (robust). -\section{Structure de \TL} -\label{sec:struct-tl} - -Nous décrivons ici la structure et le contenu de \TL{} et -de \TK{} qui est un sur-ensemble de \TL. - -\subsection {Distributions multiples : \protect\pkgname{live}, - \protect\pkgname{inst}, \protect\pkgname{protext}} -\label{sec:multiple-dist} - -Des limitations d'espace liées au format des \acro{CD-ROM} nous ont contraint -à diviser \TK{} en plusieurs distributions : - -\begin{description} - -\item [live] Un système exécutable complet sur \acro{DVD} ; il est - trop volumineux pour tenir sur \acro{CD-ROM}. Le \DVD{} contient - aussi une image du système \CTAN{}, totalement indépendant de - \TL{}, la distribution Mac\TeX{} pour \MacOSX, la distribution \ProTeXt{} - pour Windows, ainsi que d'autres extensions - réunies dans un répertoire \texttt{texmf-extra}. - - Les droits d'utilisation des fichiers présents dans \CTAN, \ProTeXt, - Mac\TeX{} et \texttt{texmf-extra} diffèrent de ceux de \TL{}, pensez à lire - les licences si vous envisagez de modifier ou de redistribuer certains de - ces fichiers. - -\item [inst\textrm{(allable)}] Un système complet sur \CD{} pour les Unix - (dont Linux et \MacOSX{}) ; pour le faire - tenir sur le \CD, il a fallu compresser tout ce que nous avons - pu. Du coup, il n'est pas possible d'exécuter directement \TeX\ - depuis le \CD\ d'installation, il vous faut l'installer sur disque - (d'où le nom). L'installation est décrite dans les sections - concernées (\ref{sec:unix-install-disk} et \ref{sec:osx-unix-inst} - pour \MacOSX). - -\item [protext] Une extension du système \MIKTEX\ sur \CD{} pour - Windows. Cette distribution est totalement indépendante du \TL{}, - elle nécessite un mode d'installation spécifique. - Elle peut être installée sur disque ou exécutée directement - depuis le \CD. Le site de \ProTeXt\ se trouve ici : - \url{http://tug.org/protext}. - - \pkgname{protext} est fourni à la fois sur le \DVDlive{} et - sur un \CD{} spécifique pour ceux qui n'ont pas de lecteur de \DVD. - -\end{description} - -\noindent On peut déterminer la nature de la distribution -utilisée en recherchant le fichier \texttt{00\var{type}.TL} dans le -répertoire racine du médium utilisé (\CD{} ou \DVD{}). -Ce fichier contient aussi la date de dernière mise à jour du \TL. - -%(df) Que fait GUT ? -%Naturally, each user group chooses what to distribute, at its own -%discretion. - -\subsection{Répertoires situés à la racine} -\label{sec:tld} - -Les répertoires les plus importants situés à la racine -% (df) bin et source ne sont pas sur \CDinst -du \DVDlive{} -sont énumérés ci-dessous. Cette année, la distribution \TL{} -est dans un sous-répertoire \dirname{texlive2007} et non à la racine. -%%% (df) confus : on parle du CD ou du DVD -\smallskip -\begingroup - \renewcommand{\arraystretch}{1.3} % open up interrow spacing -\begin{tabular}{>{\ttfamily}lp{.78\hsize}} -% (df) bin pas présent sur \CDinst : les .zip des binaires sont dans 'archive' -bin & Programmes de la famille \TeX{}, rangés dans des - sous-répertoires selon les plates-formes. \\ -% pas sur \CDinst -source & Le code source de tous les programmes, incluant la - distribution \Webc{} de \TeX{} et \MF{}. Il s'agit d'une archive au - format \texttt{tar}, compressée par bzip2. - % Ajout (df) - Faute de place, le répertoire \texttt{source} - n'est pas sur le \CDinst{} (seulement sur le \DVDlive{}).\\ -setuptl & Programmes d'installation pour Windows et Linux. \\ -support & Ensemble d'extensions et programmes auxiliaires. Ils ne - sont \emph{pas} installés par défaut. -% Faux (df) -% On y trouve \cmdname{Ghostscript}, \cmdname{netpbm} et un ensemble -% d'éditeurs orientés \TeX{}. -\\ -texmf & Répertoire contenant les programmes et leur documentation. - Ne contient ni les formats ni les extensions - (appelé \envname{TEXMFMAIN} dans la section suivante.) \\ -texmf-dist & Répertoire principal où se trouvent les extensions, - les fontes, etc., avec leur documentation - (appelé \envname{TEXMFDIST} dans la section suivante.) \\ -texmf-doc & Répertoire contenant le reste de la documentation, - le sous-répertoire doc est organisé par langue. \\ -texmf-var & Répertoire contenant les fichiers générés automatiquement - (appelé \envname{TEXMFSYSVAR} dans la section suivante.) \\ -\end{tabular} -\endgroup - -\smallskip - -Le répertoire \dirname{texmf-doc} ne contient que de la documentation -mais pas toute la documentation. Celle concernant les programmes (manuels, -pages \textit{man} et fichiers de type \textit{info} est dans -\dirname{texmf/doc} car les programmes correspondants sont dans -\dirname{texmf}. De même, la documentation des extensions et formats -est dans \dirname{texmf-dist/doc}. Les commandes \cmdname{texdoc} ou -\cmdname{texdoctk} trouveront pour vous les documentations où quelles soient -sur le disque. % Bof... pas vrai chez moi (df) ? -Le fichier \OnCD{doc.html} du \DVDlive{} contient une liste de liens bien -utiles pour localiser les fichiers de documentation. - -On trouve également, au même niveau que les répertoires mentionnés ci-dessus, -les scripts d'installation et les fichiers \filename{README} (dans -différentes langues). - -\subsection{Description des arborescences texmf utilisées} -\label{sec:texmftrees} - -Nous donnons ici la liste complète des variables prédéfinies qui contiennent -les noms des différentes arborescences de type texmf et l'usage qui en est -fait. La commande \cmdname{texconfig conf} retourne les valeurs de ces -variables, ce qui permet de savoir où se trouvent ces différentes -arborescences dans une installation donnée. - -\begin{ttdescription} -\item [TEXMFMAIN] contient les éléments essentiels du système, comme les - scripts (\cmdname{web2c/mktexdir}, etc.), les fichiers \file{.pool}, - etc. -\item [TEXMFDIST] contient les fichiers de macro (Plain, \LaTeX, \ConTeXt, - etc.,), les fontes, etc., de la distribution \TL. Rien ne devrait être - ni ajouté ni supprimé dans cette arborescence. -\item [TEXMFLOCAL] c'est là que l'administrateur de la machine - place les classes et extensions locales, les fontes non disponibles - dans \TL, etc. -\item [TEXMFHOME] contient les fichiers personnels (extensions, classes, - fontes) de l'utilisateur ; ce répertoire est sous \verb+$HOME+ % $ - par défaut. La variable \envname{TEXINPUTS} ne devrait plus être utilisée. -\item [TEXMFCONFIG] c'est là que les scripts \cmdname{updmap} et - \cmdname{fmtutil} recherchent leurs fichiers de configuration en priorité. - \cmdname{texconfig} y place les versions modifiées des fichiers de - configuration. Sous \verb+$HOME+ par défaut. %$ -\item [TEXMFSYSCONFIG] c'est là que les scripts \cmdname{updmap-sys} et - \cmdname{fmtutil-sys} recherchent leurs fichiers de configuration en - priorité. \cmdname{texconfig-sys} y place les versions modifiées des - fichiers de configuration. -\item [TEXMFVAR] c'est là que les scripts \cmdname{texconfig}, - \cmdname{updmap} et \cmdname{fmtutil} rangent les formats et les fichiers - \file{.map} qu'ils produisent. Sous \verb+$HOME+ par défaut. %$ -\item [TEXMFSYSVAR] c'est là que les scripts \cmdname{texconfig-sys}, - \cmdname{updmap-sys} et \cmdname{fmtutil-sys} rangent les formats et les - fichiers \file{.map} qu'ils produisent. -\end{ttdescription} - -Les possibilités offertes par \cmdname{texconfig} sont décrites à la - section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig}. - - -\subsection{Les extensions de \TeX} -\label{sec:tex-extensions} - -\TL{} contient plusieurs extensions de \TeX{}. - -\begin{description} - -\item [\eTeX{}] \label{text:etex} ajoute un jeu, petit mais puissant, - de nouvelles - primitives et les extensions \TeXXeT{} pour l'écriture de droite - à gauche ; \eTeX{} est, en mode normal, 100\% compatible avec - \TeX{} standard. Pour plus de détails consulter le - fichier \OnCD{texmf-dist/doc/etex/base/etex_man.pdf} du \DVDlive{}. - -\item [pdf\TeX{}] inclut les extensions \eTeX{} et produit, au choix, - des fichiers au format Acrobat \acro{PDF} ou au format \dvi{}. - Le manuel d'utilisation se trouve sur le \DVDlive{} - dans \OnCD{texmf/doc/pdftex/manual/}. Le fichier - \OnCD{texmf/doc/pdftex/pdftex/manual/samplepdf/samplepdf.tex}\relax{} - donne un exemple d'utilisation. pdf\TeX{} est le moteur de base - sur lequel sont construits tous les formats autres que plain\TeX. - -\item [Xe\TeX] ajoute la possibilité d'utiliser le codage Unicode en entrée - et les fontes OpenType en sortie, ceci grâce à des bibliothèques - externes : voir \url{http://scripts.sil.org/xetex}. - -\item [\OMEGA{} (Omega)] fonctionne en utilisant Unicode et des - caractères 16 bits, ce qui lui permet de travailler directement et - simultanément avec presque toutes les écritures du monde entier. - L'extension supporte aussi le chargement dynamique d'\acro{OTP} - (\OMEGA{} \emph{Translation Processes}) qui permet à l'utilisateur - d'appliquer sur des flux d'entrée quelconques des transformations - complexes qu'il aura lui-même définies. Voir la documentation - (pas vraiment à jour) dans \OnCD{texmf-dist/doc/omega/base/doc-1.8.tex}. - -\item [Aleph] combine les fonctionnalités de \OMEGA\ et de \eTeX. - \OnCD{texmf-dist/doc/aleph/base} contient une documentation de base. - -\end{description} - -\subsection{Quelques autres programmes intéressants - dans \TL} - -Voici quelques autres programmes couramment utilisés et présents dans -\TL{} : - -\begin{cmddescription} - -\item [bibtex] Traitement de la bibliographie. - -\item [makeindex] Traitement des index. - -\item [dvips] Conversion \dvi{} vers \PS{}. - -\item [xdvi] Visualisation \dvi{} pour le système X Window. - -\item [dvilj] Pilote \dvi{} pour les imprimantes HP LaserJet. - -\item [dv2dt, dt2dv] Conversion \dvi{} vers ou depuis du texte simple. - -\item [dviconcat, dviselect] Couper/Coller de pages à partir de fichiers - \dvi{}. - -\item [dvipdfmx] Conversion \dvi{} vers \acro{PDF}, une autre approche que - celle de pdf\TeX\ (mentionné ci-dessus). Voir les extensions - \pkgname{ps4pdf} et \pkgname{pdftricks} pour d'autres alternatives. - -\item [psselect, psnup, \ldots] Utilitaires \PS{}. - -\item [lacheck] Vérification de syntaxe \LaTeX{}. - -\item [texexec] Processeur Con\TeX{}t et \acro{PDF}. - -\item [tex4ht] Conversion \TeX{} vers \acro{HTML}. - -\end{cmddescription} - - -\section{Utilisation sous Unix} -\label{sec:unix-install} - -Comme on l'a vu en section~\ref{sec:basic} \p.\pageref{sec:basic}, -le \TL{} peut être utilisé de trois façons principales : - -\begin{enumerate} -\item Exécution directe depuis le \DVDlive. -\item Installation sur le disque dur. -\item Intégration d'un jeu de composants ou collections dans un système -\TeX{} déjà installé. -\end{enumerate} - -\noindent -Les procédures spécifiques à Unix sont décrites pour chacun de ces cas -dans les sections qui suivent. - -\ifSingleColumn \begin{figure}[ht]\noindent \fi -\begin{warningbox} - \textbf{ATTENTION : } Les \CD{} et le \DVD{} sont au format ISO~9660 - (High Sierra), avec les extensions \og Rock Ridge\fg{} (et \og Joliet\fg{} - pour Windows). Votre système doit pouvoir reconnaître les - extensions \og Rock Ridge\fg{} pour une utilisation optimale de - \TL{}. Consultez votre documentation concernant la commande - \cmdname{mount} pour voir si c'est le cas. Si votre réseau local est - constitué de machines différentes, regardez - si vous pouvez monter les \CD{} sur une machine qui supporte - Rock Ridge et utiliser ce point de montage pour les autres machines. - -\leavevmode\quad -L'utilisation des \CD{} sur les systèmes modernes -ne devrait pas poser de problèmes. S'il y en avait, n'hésitez pas à -nous le faire savoir. -La suite de ce document suppose que vous avez installé et monté les - \CD{} avec une compatibilité Rock Ridge parfaite. -\end{warningbox} - -\ifSingleColumn\end{figure}\fi - -N.B. : les droits de \og root \fg{} sont souvent requis pour monter le \CD{}. -D'autre part, selon le type d'Unix utilisé, il vous faudra probablement -connaître le mot de passe de \og root \fg{} ou tout au moins utiliser la -commande \cmdname{sudo} pour effectuer l'installation (le droit -d'écriture sur le(s) répertoire(s) d'installation est évidemment -indispensable). Cette remarque concerne particulièrement les utilisateurs de -\MacOSX{} à qui nous recommandons de prendre d'abord connaissance de la -section~\ref{sec:mac-install} avant toute installation. - - -\subsection{Utiliser \TL{} à partir du \DVDlive} - -La liste des architectures sur lesquelles fonctionne \TL{} est donnée -page~\pageref{tab:archlist} (table~\ref{tab:archlist}). - -\def\runlive{% text repeated in windows section -On peut utiliser le système \TeX{} directement depuis \DVDlive, -sans l'installer sur le disque dur (d'où en fait le nom \TL). -Il \emph{n'est pas possible} de faire tourner \TeX{} directement -depuis le \CDinst{} (voir section~\ref{sec:multiple-dist}, -page~\pageref{sec:multiple-dist}). -}% fin \runlive - -\def\startinst{% repeated in other subsections -Pour démarrer, il faut d'abord \og monter \fg{} le médium avec les -extensions Rock Ridge. -La commande exacte varie d'un système à l'autre ; la commande suivante -fonctionne sous Linux, mais les noms du périphérique (ici -\filename{/dev/cdrom}) et du point de montage (ici \dirname{/mnt/cdrom}) -peuvent changer. -\\ N.B. Tous nos exemples utilisent \texttt{>} pour les lignes de -commandes \textit{(shell prompt)} ; les commandes de l'utilisateur sont -\underline{soulignées}. -\begin{alltt} -> \Ucom{mount -t iso9660 /dev/cdrom /mnt/cdrom} -\end{alltt} - -\noindent Se placer au point de montage du lecteur : -\begin{alltt} -> \Ucom{cd /mnt/cdrom} -\end{alltt} -}% fin startinst - -\def\installtlsh{% repeated in other subsections -Lancer le script \filename{install-tl.sh} : -\begin{alltt} -> \Ucom{sh install-tl.sh}\\ -Welcome to TeX Live... -\end{alltt} - -\noindent Après l'affichage de divers messages de bienvenue et une liste des -options du menu principal, l'installation réclame l'entrée d'une commande. -Taper alors le caractère voulu suivi d'un retour-chariot. Ne pas taper les -chevrons (ni \texttt{<} ni \texttt{>}) ; on peut utiliser des majuscules ou -des minuscules ; ici, les exemples utilisent des minuscules. -}% fin \installtlsh - -\runlive -\startinst -\installtlsh - -Pour exécuter \pkgname{live}, la première commande est \Ucom{d} -suivie de la sous-commande \Ucom{1} pour choisir le répertoire du disque -local où seront placés les fichiers (tels que les fontes et les formats) que -le système \TeX{} génère lui-même ainsi que les fichiers de configuration si -besoin est. On utilisera \dirname{/opt/texlive2007} dans cet exemple, -mais un utilisateur non privilégié peut très bien choisir un -sous-répertoire non-existant de son répertoire personnel (il sera créé -et ne contiendra donc que du matériel \TL{}). -Étant donné que les fichiers créés ne sont pas toujours compatibles d'une -année sur l'autre, il est recommandé d'inclure l'année dans le nom du -répertoire. -Si la valeur par défaut \dirname{/usr/local/texlive/2007} vous convient -(c.-à-d. que \dirname{/usr/local/texlive/2007} n'est pas un répertoire -existant et que vous avez les droits pour écrire sous \dirname{/usr/local}), -vous pouvez sauter cette étape. -\begin{alltt} -Enter command: \Ucom{d} -Current directories setup: -<1> TEXDIR: /usr/local/texlive/2007 -... -Enter command: \Ucom{1} -New value for TEXDIR [/usr/local/texlive/2007]: \Ucom{/opt/texlive2007} -... -Enter command: \Ucom{r} -\end{alltt} - -Retour au menu principal. La seconde (et dernière) commande est -\Ucom{r} -pour faire tourner \pkgname{live} à partir du \DVD{} sans pour autant -l'installer sur le disque dur : - -\begin{alltt} -Enter command: \Ucom{r} -Preparing destination directories... -... -Welcome to the TeX Live! -> -\end{alltt} - -On se retrouve au niveau de la ligne de commande -comme on vient de le voir. - -Il faut maintenant modifier les deux variables -d'environnement \envname{PATH} et \envname{TEXMFSYSVAR} comme indiqué -à l'écran quelques lignes au dessus de \og Welcome to TeX Live!\fg. -La syntaxe dépend du \textit{shell} utilisé. Les syntaxes -précises sont affichées pour les \textit{shell} de type Bourne ou compatible -(\cmdname{bash}, \cmdname{sh} \cmdname{ksh}, etc.) et pour les -\textit{C~shells} (\cmdname{csh}, \cmdname{tcsh}). -Rappelons qu'il suffit de taper la commande \verb+echo $SHELL+ %$ -pour connaître le nom du \textit{shell} utilisé. -Le plus simple est de recopier par copier-coller, soit les deux lignes -commençant par \og\cmdname{setenv}\fg{} pour les \textit{C~shells}, -soit les trois lignes \og\envname{PATH=}\fg, \og\envname{TEXMFSYSVAR=}\fg, -\og\envname{export ...}\fg{} pour les \textit{shell} de type Bourne -(suivies d'un retour-chariot) dans le terminal de commandes. - -Ceci suffit pour pouvoir utiliser la distribution \TL{} -pendant toute la session. -Pour ne pas avoir à redéfinir \envname{PATH} et \envname{TEXMFSYSVAR} -à chaque nouvelle connexion, il suffit d'entrer les mêmes commandes -à l'aide d'un éditeur dans le fichier d'initialisation du \textit{shell} -(\file{.bash\_profile}, \file{.profile} ou \file{.cshrc} -selon le cas). -L'initialisation se fera ensuite automatiquement au début de chaque nouvelle -session. - -\def\textruntexconfig{% - Une fois l'installation terminée et les variables d'environnement - initialisées, la dernière étape consiste à exécuter \cmdname{texconfig} ou - \cmdname{texconfig-sys} pour éventuellement modifier certains paramètres. - Ceci est expliqué à la section~\ref{sec:texconfig}, - \p.\pageref{sec:texconfig}.% -} -\textruntexconfig - -\def\textifindoubt{% -Passez maintenant à la section~\ref{sec:test-install} pour effectuer -quelques tests de bon fonctionnement. - -En cas de doute, n'hésitez pas à contacter un gourou système pour -vous aider à résoudre vos problèmes, tels que la façon de monter le - médium \TL{}, le choix des répertoires à utiliser ou les modifications -à apporter dans vos fichiers d'initialisation. -}%fin textifindoubt -\textifindoubt - -\subsection{Installer \TL{} sur le disque} -\label{sec:unix-install-disk} - -Il est possible, et même habituel, d'installer le système \TeX{} à -partir du \TL{} sur le disque (\og dur\fg{}). -Ceci peut se faire en utilisant soit le \DVDlive, soit le \CDinst -(voir section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist} -pour des explications sur les différentes distributions). - -\startinst -\installtlsh - -La table~\ref{tab:main-menu-options} donne la liste des options du menu -principal. On peut choisir les options dans n'importe quel ordre, mais -\Ucom{i} doit être la dernière choisie. Il est cependant raisonnable de -procéder dans l'ordre où elles apparaissent ici ! - -% apparently here.sty [H] doesn't support table*. -\begin{table}[H] -\caption{Options d'installation du menu principal} -\label{tab:main-menu-options} -\begin{tabular}{>{\ttfamily}ll} -p & plate-forme que vous utilisez\\ -b & choix des binaires à installer (architectures multiples)\\ -s & \emph{schéma d'installation} de base - (complet, recommandé, GUTenberg, etc.).\\ -c & modifier le choix des collections individuelles\\ -l & modifier le choix des langues à installer\\ -d & répertoire où faire l'installation\\ -o & autres options\\ -i & lancer l'installation\\ -\end{tabular} -\end{table} - -Voici quelques précisions sur chaque option. - -\begin{description} - -\item[\optname{p} -- Platform (current).] Plate-forme utilisée.\\ -Le script d'installation détecte automatiquement la plate-forme -sur laquelle il tourne, il est en général inutile de modifier cette option, -sauf en cas d'erreur. - -\item[\optname{b} -- Binary architectures.] Binaires pour d'autres -architectures.\\ -Par défaut, seuls les binaires pour votre plate-forme seront installés. À -l'aide de ce menu-ci, il est possible de choisir d'installer aussi les -binaires pour d'autres plates-formes (ou de ne pas installer pour la -plate-forme courante). C'est utile si on partage un arbre \TeX\ -au travers d'un réseau de machines hétérogènes. -La table~\ref{tab:archlist} ci-dessous donne la liste des architectures -pour lesquelles des binaires sont disponibles. - -\begin{table*}[!ht] -%\captionsetup{margin=5mm,justification=centerfirst} -\caption{Les binaires sont disponibles pour les architectures suivantes.} -\label{tab:archlist} -%(df) vérifier la liste finale -\begin{tabular}{>{\hspace*{15mm}\ttfamily}lll} -alpha-linux & HP Alpha GNU/Linux \\ -%alphaev5-osf4.0d & HP Alphaev5 OSF \\ -%hppa2.0-hpux10.20 & HP9000 HPUX 10.20 \\ -i386-darwin & Intel x86 \MacOSX \\ -i386-freebsd & Intel x86 FreeBSD \\ -i386-linux & Intel x86 GNU/Linux \\ -%i386-openbsd3.3 & Intel x86 OpenBSD \\ -%i386-solaris2.8 & Intel x86 Solaris \\ -mips-irix & SGI IRIX \\ -powerpc-aix & IBM RS/6000 AIX \\ -powerpc-darwin & PowerPC \MacOSX \\ -sparc-linux & Sun Sparc GNU/Linux \\ -sparc-solaris & Sun Sparc Solaris \\ -win32 & Windows (32-bit) \\ -x86\_64-linux & Intel x86 64-bit GNU/Linux \\ -% \\ \hline -\end{tabular} -\end{table*} - -\item[\optname{s} -- Base Installation scheme.] -Schéma d'installation de base.\\ -Ce menu permet de choisir un type d'installation plus ou moins complet. -L'option par défaut (\optname{full}) installe tout, c'est un bon choix si -l'espace disque n'est pas limité. Les francophones préféreront peut-être -le schéma \acro{GUT}enberg, mais on peut choisir un ensemble minimal -(\optname{basic}) pour économiser de la place sur le disque. On trouve -aussi des ensembles spécifiques pour Omega ou pour les utilisateurs -d'\acro{XML}. - -\item[\optname{c} -- Individual collections.] Collections individuelles.\\ -Ce menu permet d'ajouter ou de supprimer des collections -parmi celles retenues par le schéma choisi ci-dessus. -Chaque collection\Dash fichiers de macros TeX, familles de fontes Metafont, -etc.\Dash{} est formée de plusieurs composants. -Attention, le programme différencie les lettres minuscules -des lettres capitales pour les touches de sélection. - -\item[\optname{l} -- Language collections.] Collections de langues.\\ -Ce menu fonctionne comme celui de \Ucom{c} pour modifier -le choix des langues à installer. -Attention, le programme différencie les lettres minuscules -des lettres capitales pour les touches de sélection. - -Voici la liste des collections de langues du \TL{} -(on garde ici les noms anglais des options qui sont ceux du système !) : - -% xx really should generate list from texmf/tpm/collection/tex-lang* -% a la install-tl.sh. -\begin{tabbing} -\hspace{.25\linewidth} \= -\hspace{.20\linewidth} \= -\hspace{.20\linewidth} \= -\hspace{.35\linewidth} \kill -African \textit{(qq scripts)} \> -Arabic \> -Armenian \> -Chinese\,Japanese\,Korean \\ -Croatian \> -Cyrillic \> -Czech/Slovak \> -Danish \\ -Dutch \> -Finnish \> -French \> -German \\ -Greek \> -Hebrew \> -Hungarian \> -Indic \\ -Italian \> -Latin \> -Manju \> -Mongolian \\ -Norwegian \> -Polish \> -Portuguese \> -Spanish \\ -Swedish \> -Tibetan \> -\acro{UK} English \> -Vietnamese \\ -\end{tabbing} - -\noindent Les collections de langues comprennent normalement des fontes, -macros, motifs de césure et autres fichiers. Par exemple, -\pkgname{frenchle.sty} est installé lorsqu'on sélectionne la collection -\optname{French}. Par ailleurs, l'installation d'une langue de la collection -modifie le fichier de configuration \filename{language.dat} qui contrôle -quelles divisions (ou coupures de mots) sont chargées. - -\item[\optname{d} -- Installation directories] Choix des -répertoires d'installation.\\ \label{text:instdir} -Ceci concerne les trois répertoires suivants : - -\begin{ttdescription} -\item [TEXDIR] -Répertoire de plus haut niveau sous lequel tout le reste sera installé, -la valeur par défaut est \dirname{/usr/local/texlive/2007}. -Il est conseillé de faire figurer l'année dans le nom choisi, de façon à -pouvoir conserver séparément plusieurs versions de \TL. -L'ajout d'un lien symbolique -\dirname{/usr/local/texlive/current} qui pointe vers la version à utiliser -facilitera grandement le basculement d'une version -à l'autre et le retour à l'ancienne version en cas de problème. - -Sous \MacOSX, les interfaces utilisateurs recherchent \TeX{} -dans \dirname{/usr/local/teTeX} ; plutôt que d'installer la distribution \TL{} -dans ce répertoire, on pourra faire l'installation par défaut -(dans \dirname{/usr/local/texlive/2007} donc) et ajouter deux liens -symboliques : \dirname{current} qui pointe vers \dirname{2007} et -\dirname{teTeX} qui pointe vers \dirname{current}. Pour cela il suffit de -taper les deux commandes suivantes dans un terminal : -\begin{alltt} -> \Ucom{(cd /usr/local/texlive ; ln -s ./2007 ./current)} -> \Ucom{(cd /usr/local ; ln -s ./texlive/current teTeX)} -\end{alltt} - -\item [TEXMFLOCAL] -C'est dans cette arborescence que doivent être placés les fichiers -non fournis par \TL{}. -La valeur par défaut est \dirname{/usr/local/texlive/texmf-local}. -C'est l'endroit recommandé pour y mettre les classes et les fichiers de style -locaux, les fontes (par exemple commerciales) non disponibles -sur \TL{} ainsi que les paramètres de configuration locaux. - -\item [TEXMFSYSVAR] -C'est dans cette arborescence que les scripts \cmdname{texconfig-sys}, -\cmdname{fmtutil-sys}, \cmdname{updmap-sys} installent les fichiers qui -sont spécifiques à la version, notamment les fichiers de format. -La valeur par défaut est \dirname{TEXDIR/texmf-var}, il n'y a en -général aucune raison de la changer. -Les fichiers configuration modifiables par \cmdname{texconfig-sys} (voir -section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig}), comme -\filename{fmtutil.cnf} et \filename{updmap.cfg}, sont eux dans -\envname{TEXMFSYSCONFIG}. -\end{ttdescription} - -\item[\optname{o} -- Other Options.] -Ce menu permet de choisir les options suivantes : - -\begin{ttdescription} -\item [a] Pour spécifier un autre répertoire pour les fontes générées. -La valeur par défaut utilise l'arborescence \envname{TEXMFVAR}, comme on -l'a dit plus haut. -Si vous voulez que l'arborescence principale soit accessible en lecture -uniquement, cette option permet de choisir une autre localisation -(qui doit bien sûr être accessible en lecture-écriture pour tous) -pour ranger les fontes créées dynamiquement. - -\item [l] Pour créer des liens symboliques pour les binaires, -la documentation \textit{(man pages)} ou les fichiers Info \acro{GNU}. -Par exemple, on peut désirer rendre la documentation de type \textit{man} -accessible depuis \dirname{/usr/local/man} et les fichiers Info -depuis \dirname{/usr/local/info} (il faut alors bien sûr avoir les droits -d'écriture dans les répertoires spécifiés). - -En revanche, il est déconseillé d'utiliser cette option pour les binaires. -Rendre les binaires \TL{} accessibles depuis \dirname{/usr/local/bin} -risque de masquer définitivement, y compris pour \textit{root}, les -binaires \TeX\ fournis en standard sur la plate-forme. -Sous Linux par exemple, \textit{root} doit utiliser par défaut les binaires -\teTeX{} fournis avec la distribution installée (Debian, Mandrake, RedHat, -etc.) et non ceux fournis par \TL. - -\item [d] Pour ne pas installer l'arborescence de la documentation -sur les fontes et les macros. Utile pour économiser de l'espace -disque ou bien si la documentation a été installée auparavant à un -autre emplacement. - -\item [s] Pour ne pas installer l'arborescence des fichiers source. -Ceci peut être utile si cette arborescence est commune à -différentes machines ou architectures, (partage par \acro{NFS} ou -\cmdname{automount} par exemple). - -\end{ttdescription} - -\item[\optname{i} -- Perform Installation.] Installer.\\ -Quand les options de configuration sont satisfaisantes, on peut taper -\Ucom{i} pour lancer effectivement l'installation. - -\end{description} - -Lorsque l'installation est terminée, l'étape suivante consiste à inclure dans -la variable \envname{PATH} des usagers (autres que \textit{root} -cf. ci-dessus) le sous-répertoire de \dirname{TEXDIR/bin} spécifique à -l'architecture de façon que les programmes nouvellement installés puissent -être trouvés. Le tableau~\ref{tab:archlist} (page~\pageref{tab:archlist}) -donne la liste des noms des architectures ; on peut aussi lister le contenu de -\dirname{TEXDIR/bin} pour déterminer le nom du sous-répertoire de -\dirname{TEXDIR/bin} à inclure en tête de \envname{PATH}. - -\label{text:path} -La syntaxe de cette commande et le fichier d'initialisation à utiliser -dépendent du système utilisé. Pour un \textit{shell} Bourne ou -compatible (\cmdname{sh}, \cmdname{bash}, \cmdname{ksh}, etc.), il -faut mettre dans le fichier \filename{$HOME/.profile}% %$ -\footnote{Pour les utilisateurs qui possèdent un fichier - \filename{$HOME/.bash_profile}, c'est dans ce dernier qu'il faut redéfinir - la variable \envname{PATH}, car pour eux, \filename{$HOME/.profile} est - sans effet.} -des futurs utilisateurs de \TL{} : -\begin{alltt} -PATH=/\Ucom{\emph{TEXDIR}}/bin/\Ucom{\emph{archname}}:$PATH; export PATH -\end{alltt} - -\noindent -et pour un \textit{C~shell} (\cmdname{csh}, \cmdname{tcsh}), -mettre dans le fichier \filename{$HOME/.cshrc} : -\begin{alltt} -setenv PATH /\Ucom{\emph{TEXDIR}}/bin/\Ucom{\emph{archname}}:$PATH -\end{alltt} %$ - -Sous \MacOSX{} ceci se peut se faire de la manière suivante, qui évite d'avoir -à ouvrir un éditeur sur un fichier caché : -on redevient utilisateur de base, on se place dans son répertoire personnel, -en tapant dans le Terminal -\begin{alltt} -> \Ucom{exit ; cd} -\end{alltt} -On vérifie quel est le \textit{shell} utilisé en tapant -\begin{alltt} -> \Ucom{echo $SHELL} -\end{alltt} %$ -Si la réponse est \filename{bash} (ou \filename{sh}) le fichier à modifier est -\file{.profile}, si c'est \filename{tcsh} (ou \filename{csh}) -le fichier à modifier est \file{.cshrc}.\\ -Cas de \filename{bash} : on tape dans le terminal\footnotemark{} -\addtocounter{footnote}{-1} -\begin{alltt} -> \Ucom{touch .profile} -> \Ucom{echo "export PATH=/usr/local/texlive/2007/bin/powerpc-darwin:$PATH" >> .profile} -> \Ucom{source .profile} -\end{alltt} %$ -Cas de \filename{tcsh} : on tape dans le terminal% -\footnote{Cet exemple suppose qu'on a fait l'installation dans -\dirname{/usr/local/texlive/2007} et que processeur est un Motorola, sinon il -faut adapter \envname{PATH} en conséquence (changer \dirname{powerpc-darwin} -en \dirname{i386-darwin} pour les Mac à base de processeur Intel).} -\begin{alltt} -> \Ucom{touch .cshrc} -> \Ucom{echo "setenv PATH /usr/local/texlive/2007/bin/powerpc-darwin:$PATH" >> .cshrc} -> \Ucom{source .cshrc} -\end{alltt} %$ -La mise à jour de la variable \envname{PATH} est terminée. - -\medskip -Voici un court exemple qui sélectionne une installation complète avec -les binaires du système actuel seulement (on accepte tous les choix par -défaut). Les \acro{RETURN} sont omis ici. - -% Respecter les espaces pour aligner les # !!! -\begin{alltt} -> \Ucom{sh install-tl.sh} -\Ucom{i} # lancer l'installation -# Redevenir utilisateur de base (non root) -> \Ucom{exit ; cd} -# Nouveau PATH (sous Linux, SHELL=bash, compte avec fichier \file{.bash_profile}) : -> \Ucom{echo "export PATH=/usr/local/texlive/2007/bin/i386-linux:$PATH" >> .bash_profile} -> \Ucom{source .bash_profile} # faire prendre en compte le nouveau PATH -\end{alltt} %$ - -Si votre système Unix connaît la commande \cmdname{manpath} (essayez en tapant -\code{man manpath} dans un terminal), vous pourrez accéder à la documentation -de \TL{} grâce à la commande \cmdname{man} en ajoutant la ligne suivante -(en adaptant les chemins éventuellement) dans -le fichier \filename{/etc/manpath.config} (ceci nécessite les droits de -\textit{root}) : -\begin{alltt} -MANPATH_MAP /usr/local/texlive/2007/bin/i386-linux /usr/local/texlive/2007/texmf/doc/man -\end{alltt} - - -\textruntexconfig - -\medskip %J.A. - -\textifindoubt - - -\subsubsection{Installation non interactive } -\label{sec:noninteractive-install} - -Lorsqu'on doit dupliquer la même installation sur plusieurs machines, il -peut être fastidieux de devoir répondre à chaque fois à la même liste de -questions. Une installation personnalisée automatique est possible. - -Exemple : pour réaliser une installation standard de \TL{} sous -\dirname{/opt/texlive} plutôt que sous \dirname{/usr/local/texlive}, -il suffit d'exécuter les trois commandes suivantes : -\begin{alltt} -> \Ucom{TEXLIVE_INSTALL_PREFIX=/opt/texlive} -> \Ucom{export TEXLIVE_INSTALL_PREFIX} -> \Ucom{echo i | sh install-tl.sh} -\end{alltt} - -L'argument \og\texttt{i}\fg{} passé au script d'installation sert à lancer -l'installation (en mode interactif, on taperait \texttt{i} au clavier). - -Cinq variables d'environnement permettent de choisir où aura lieu -l'installation : -\begin{ttdescription} -\item [TEXLIVE\_INSTALL\_PREFIX] - remplace \dirname{/usr/local/texlive}. -\item [TEXLIVE\_INSTALL\_TEXDIR] - remplace \dirname{/usr/local/texlive/2007}. -\item [TEXLIVE\_INSTALL\_TEXMFLOCAL] - remplace \dirname{/usr/local/texlive/texmf-local}. -\item [TEXLIVE\_INSTALL\_TEXMFSYSVAR] - remplace \dirname{/usr/local/texlive/2007/texmf-var}. -\item [TEXLIVE\_INSTALL\_TEXMFHOME] - remplace \dirname{$HOME/texmf}. %$ -\end{ttdescription} - -\enlargethispage*{\baselineskip} -Pour réaliser une installation personnalisée, il est facile d'écrire un petit -script qui passe les arguments adéquats à la commande \cmdname{install-tl.sh} ; -par exemple pour une installation selon le schéma Gutenberg, avec comme langues -supplémentaires l'espagnol et l'anglais britannique, à placer sous -\dirname{/opt/texlive}, on pourrait lancer (sous root, en supposant que -le SHELL est \cmdname{sh} ou \cmdname{bash} le script suivant : -\begin{verbatim} -TEXLIVE_INSTALL_PREFIX=/opt/texlive -export TEXLIVE_INSTALL_PREFIX -sh install-tl.sh <} pour les lignes de -commandes \textit{(shell prompt)} ; les commandes de l'utilisateur sont -\underline{soulignées}. -\begin{alltt} -> \Ucom{mount -t iso9660 /dev/cdrom /mnt/cdrom} -\end{alltt} - -\noindent Se placer au point de montage du lecteur : -\begin{alltt} -> \Ucom{cd /mnt/cdrom} -\end{alltt} - -Lancer le script \filename{install-pkg.sh} (et non -\filename{install-tl.sh} qui n'est destiné qu'à l'installation complète) : - -\begin{alltt} -> \Ucom{sh install-pkg.sh \var{options}} -\end{alltt} - -Le premier jeu d'options permet de choisir ce qui sera installé : - -\begin{ttdescription} -\item [-{}-package=\var{pkgname}] Le composant individuel à installer. - -\item [-{}-collection=\var{colname}] La collection individuelle à installer. - -\item [-{}-nodoc] Ne pas installer les fichiers de documentation pour -cette opération. - -\item [-{}-nosrc] Ne pas installer les fichiers source pour cette opération. - -\item [-{}-cddir=\var{dir}] Répertoire source d'où on lit ; -par défaut le répertoire courant. Si on a suivi les instructions ci-dessus, -il n'a pas besoin d'être modifié. - -\item [-{}-listdir=\var{dir}] -Ce qu'on appelle \og répertoire des listes\fg{} dans \var{cddir} -d'où on lira l'information sur le composant. -Si on a suivi les instructions ci-dessus, il n'y a pas besoin de le modifier. - -\end{ttdescription} - -La suite des opérations est contrôlée par les options décrites ci-dessous. -Si aucune n'est spécifiée, par défaut on installe les fichiers spécifiés. -L'arborescence principale de destination est -le répertoire père du répertoire \dirname{bin} affiché par la commande -\cmdname{which tex}. -On peut la modifier en changeant les variables d'environnement -\envname{TEXMFMAIN} ou \envname{TEXMF}. - -\begin{ttdescription} - -\item [-{}-listonly] Liste les fichiers à installer mais n'installe - rien du tout ! - -\item [-{}-archive=\var{tarfile}] Au lieu d'installer les fichiers - dans le système \TeX{}, crée une archive \cmdname{tar}. - -\end{ttdescription} - -Options additionnelles : - -\begin{ttdescription} - -\item [-{}-config] Après l'installation, exécuter \code{texconfig init}. - -\item [-{}-nohash] Après installation, ne pas lancer \cmdname{mktexlsr} -pour reconstruire la base de données des noms de fichiers. -\item [-{}-verbose] Donner plus d'informations durant l'exécution des scripts. -\end{ttdescription} - -Voici quelques exemples d'utilisation : - -\begin{enumerate} - -\item Voir les fichiers du composant \pkgname{fancyhdr} sans l'installer : - -\begin{alltt} -\ifSingleColumn> \Ucom{sh install-pkg.sh --package=fancyhdr --listonly} -\else> \Ucom{sh install-pkg.sh --package=fancyhdr \bs} -> \Ucom{--listonly} -\fi{} -texmf-dist/doc/latex/fancyhdr/README -texmf-dist/doc/latex/fancyhdr/fancyhdr.pdf -... -\end{alltt} - -\item Installer le composant \LaTeX{} \pkgname{natbib}: -\begin{alltt} -> \Ucom{sh install-pkg.sh --package=natbib} -\end{alltt} - -\item Installer le composant - \LaTeX{} \pkgname{alg} sans les sources ni la documentation : - -\begin{alltt} -\ifSingleColumn> \Ucom{sh install-pkg.sh --package=alg --nosrc --nodoc} -\else> \Ucom{sh install-pkg.sh -{}-package=alg \bs} -> \Ucom{-{}-nosrc -{}-nodoc} -\fi\end{alltt} - -\item Installer tous les composants dans la collection de macros - additionnelles de plain \TeX\ : -\begin{alltt} -> \Ucom{sh install-pkg.sh --collection=tex-plainextra} -\end{alltt} - -\item -Faire une archive \cmdname{tar} dans \path{/tmp} contenant tous les -composants -de \pkgname{pstricks} : -\begin{alltt} -\ifSingleColumn> \Ucom{sh install-pkg.sh --package=pstricks --archive=/tmp/pstricks.tar} -\else -> \Ucom{sh install-pkg.sh -{}-package=pstricks \bs} -> \Ucom{-{}-archive=/tmp/pstricks.tar} -\fi\end{alltt} - -\end{enumerate} - -\textifindoubt - -% -\section{À faire après l'installation} -\label{sec:postinstall} - -Une fois l'installation terminée il faut, quel que soit le système, -configurer le système pour certains besoins locaux et -faire des tests de base. - -Cette phase de post-installation comprend éventuellement la prise en compte de -composants, fontes ou de programmes qui n'étaient pas inclus dans \TL{}. -L'idée de base est de faire les ajouts dans l'arborescence -\envname{TEXMFLOCAL} (si vous avez installé depuis le disque) -ou dans \envname{TEXMFSYSVAR} (si vous exécutez depuis le disque) ; -voir \og répertoires d'installation\fg{} en page~\pageref{text:instdir}. - -Bien sûr, les détails varient d'un cas à l'autre et nous n'essayerons -donc pas de les traiter ici. Voici quelques pointeurs à consulter : -\begin{itemize} -\item -\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instpackages} -\item -\url{http://www.ctan.org/installationadvice} -\item -\url{http://www.ctan.org/tex-archive/info/beginlatex/html/chapter5.html#pkginst} -\item -\url{http://www.ctan.org/tex-archive/info/Type1fonts} sur l'installation -de fontes. -\end{itemize} - -\subsection{Le programme \protect\cmdname{texconfig}} -\label{sec:texconfig} - -Vous pouvez utiliser le programme \cmdname{texconfig} n'importe quand après -votre installation pour reconfigurer votre système -de façon à satisfaire les besoins locaux. -Il peut être nécessaire de l'exécuter au moins une fois juste après -l'installation si les valeurs par défaut de certains paramètres ne vous -conviennent pas. -Ce programme est installé avec les autres sous le répertoire propre à -votre architecture \texttt{TEXDIR/bin/\var{archname}}, si vous n'avez pas -modifié le \envname{PATH} de \textit{root}, il faudra le lancer -(sous \textit{root}) avec son chemin complet. - -Si on le lance sans arguments, il entre en mode plein-écran et on peut -alors voir et modifier interactivement les paramètres. - -On peut aussi le lancer avec diverses options. Voici les plus courantes -(la distribution \TL{} est configurée pour utiliser du papier~A4 par défaut) : - -\begin{ttdescription} - -\item [texconfig paper letter] -Mettre la taille par défaut du papier à \textit{letter} pour les pilotes -\cmdname{pdftex}, \cmdname{dvips}, \cmdname{dvipdfm}, \cmdname{xdvi}, etc. - -\item [texconfig rehash] Mettre à jour toutes les bases de données des -fichiers du système \TeX{} (à faire après tout ajout ou suppression de -fichier). - -\item [texconfig faq] Afficher la \acro{FAQ} sur \teTeX{}. -(voir aussi la \acro{FAQ} principale de \TeX{} dans -\OnCD{texmf-doc/doc/english/FAQ-en} sur le \DVDlive{}). - -\item [texconfig help] Obtenir de l'aide sur la commande \cmdname{texconfig}. - -\end{ttdescription} - -Bien sûr, \cmdname{texconfig} ne permet de changer que certaines des -nombreuses options et paramètres de configuration d'un système \TeX{}. -Le fichier principal de configuration pour les programmes de la base -\Webc{} s'appelle \filename{texmf.cnf}. ; on peut trouver son emplacement -en exécutant \samp{kpsewhich texmf.cnf}. Ce fichier contient de nombreux -commentaires expliquant les options par défaut et la signification des -paramètres, sa lecture est recommandée. - -Depuis 2005, la commande \cmdname{texconfig} \emph{ne modifie plus les -fichiers de configuration de la machine}, mais ceux de l'utilisateur qui la -lance ; ces fichiers sont dans le répertoire \dirname{$HOME/.texlive2007} %$ -de l'utilisateur. - -De même, les commandes \cmdname{updmap} et \cmdname{fmtutil} -opèrent maintenant au niveau de l'utilisateur dans le répertoire -\dirname{$HOME/.texlive2007} %$ - -\textbf{Important : machines multi-utilisateurs}. Les administrateurs -installant \TL{} sur une machine multi-utilisateurs devront dorénavant -utiliser les commandes \cmdname{texconfig-sys}, \cmdname{updmap-sys} et -\cmdname{fmtutil-sys} pour respectivement modifier la configuration, mettre à -jour les fichiers \file{.map} et créer les formats \emph{au niveau de la - machine}. Noter qu'aucun format n'est créé à l'installation, ils sont -fabriqués à la demande ; depuis cette année, le format créé par un utilisateur -l'est uniquement pour lui (il est mis dans \dirname{$HOME/.texlive2007}). %$ -Afin d'éviter la multiplication de fichiers de formats, il y a donc lieu créer -au moins les formats les plus utilisés au niveau du système à la fin de -l'installation par la commande \cmdname{fmtutil-sys}. Le plus simple est de -les créer tous (c.-à-d. ceux qui figurent dans le fichier fmtutil.conf) par -\begin{alltt} -> \Ucom{fmtutil-sys --all} -\end{alltt} -De plus, ceux qui ont des fichiers de configuration spécifiques -\filename{fmtutil.cnf} ou \filename{updmap.cfg} devront les placer -dans l'arborescence pointée par la nouvelle variable -\envname{TEXMFSYSCONFIG}, -faute de quoi ces fichiers ne seront pas trouvés par les scripts -\cmdname{fmtutil-sys} et \cmdname{updmap-sys}. -Si les fichiers \filename{fmtutil.cnf} et \filename{updmap.cfg} propres à la -machine sont, par exemple, dans \envname{\$TEXMFLOCAL}, -rien n'empêche de définir \envname{TEXMFSYSCONFIG} comme -\envname{\$TEXMFLOCAL}, -mais il faut le faire explicitement dans le fichier \filename{texmf.cnf}. - -Rappelons que la commande \cmdname{texconfig conf} retourne les valeurs des -variables \envname{TEXMFSYSCONFIG}, \envname{TEXMFLOCAL}, etc., et que -l'utilisation des différentes arborescences texmf a été décrite à la -section~\ref{sec:texmftrees} \p.\pageref{sec:texmftrees}. - - -\subsection{Tester l'installation} -\label{sec:test-install} - -Une fois l'installation de \TL{} terminée, il faut -la tester avant de créer des documents ou des fontes. -Les tests doivent être faits par un utilisateur non privilégié -(autre que \textit{root}). - -On donne ici quelques procédures de base pour vérifier que le nouveau -système est opérationnel. On les décrit pour Unix ; pour \MacOSX{} ou -Windows, il vaut mieux tester au travers d'une interface graphique, -mais les principes sont les mêmes. - -\begin{enumerate} - -\item -S'assurer en premier lieu que le programme \cmdname{tex} fonctionne : - -\begin{alltt} -> \Ucom{tex -{}-version} -TeX 3.141592 (Web2C 7.5.5) -kpathsea version 3.5.5 -... -\end{alltt} - -Si on récupère un \textit{command not found} au lieu d'informations -comme le numéro de version et le copyright, il est fort probable que -vous n'avez pas le bon répertoire \dirname{bin} dans votre -\envname{PATH}. -Voir les informations sur l'environnement page~\pageref{text:path}. - -\item Traiter un fichier \LaTeX{} simple : - -\begin{alltt} -> \Ucom{latex sample2e.tex} -This is pdfeTeXk, Version 3.141592... -... -Output written on sample2e.dvi (3 pages, 7496 bytes). -Transcript written on sample2e.log. -\end{alltt} -Si ça échoue en cherchant \filename{sample2e.tex} ou d'autres fichiers, -il y a peut-être des interférences entre vos anciennes variables -d'environnement ou fichiers de configuration. Pour analyser en détail -votre problème, vous pouvez demander à \TeX{} de dire exactement ce -qu'il cherche et trouve ; voir \og Actions de débogage \fg{} -page~\pageref{Debugging}. - -\item Prévisualiser les résultats en ligne : -\begin{alltt} -> \Ucom{xdvi sample2e.dvi} -\end{alltt} -Sous Windows, la commande équivalente est \cmdname{dviout}. -Une nouvelle fenêtre doit s'ouvrir et montrer un document expliquant les -bases de \LaTeX{} (document à lire d'ailleurs si vous êtes débutant !). -Vous devez tourner sous X pour que \cmdname{xdvi} fonctionne. Sinon, votre -variable d'environnement \envname{DISPLAY} n'est pas correcte et vous -aurez une erreur \samp{Can't open display}. - -\item Créer un fichier \PS{} pour l'imprimer ou l'afficher : - -\begin{alltt} -> \Ucom{dvips sample2e.dvi -o sample2e.ps} -\end{alltt} - -\item Créer un fichier \acro{PDF} au lieu de \dvi{} ; -cet exemple traite le fichier \filename{sample2e.tex} et crée directement -du \acro{PDF} : - -\begin{alltt} -> \Ucom{pdflatex sample2e.tex} -\end{alltt} - -\item Prévisualiser le fichier \acro{PDF} : - -\begin{alltt} -> \Ucom{gv sample2e.pdf} -\textrm{ou} -> \Ucom{xpdf sample2e.pdf} -\end{alltt} - -Hélas, ni \cmdname{gv} ni \cmdname{xpdf} ne sont actuellement inclus dans -\TL{}, aussi devez-vous les installer séparément si ce n'est déjà fait. -Voir respectivement -\url{http://www.gnu.org/software/gv} et -\url{http://www.foolabs.com/xpdf}. - -\item Autres fichiers de tests utiles : - -\begin{ttdescription} - -\item [small2e.tex] Un document plus simple à compiler que -\filename{sample2e} si celui-ci pose des problèmes. - -\item [testpage.tex] Teste que l'imprimante n'introduit pas de décalages. - -\item [nfssfont.tex] Imprime des tables de fontes et des tests. -\item [testfont.tex] Aussi pour les tables de fontes, mais en (plain) \TeX. -\item [story.tex] Le fichier de test de (plain) \TeX{} le plus canonique -de tous. Il faut taper \samp{\bs bye} à la commande \code{*} après -\samp{tex story.tex}. - -\end{ttdescription} -Pour exécuter ces tests procéder comme on l'a fait pour -\filename{sample2e.tex}. - -\end{enumerate} - -Si vous êtes débutant ou si vous avez besoin d'aide pour réaliser des -documents \TeX{} ou \LaTeX{}, n'hésitez pas à consulter -\url{http://tug.org/begin.html}. -On vous recommande également l'introduction à \LaTeX{} de Tobias Oetiker -dans sa version anglaise (la version française n'est plus à jour) -disponible après installation sous -\url{texmf-doc/doc/english/lshort-english/lshort.pdf}. - - -\section{Installation pour \MacOSX} -\label{sec:mac-install} - -\TL{} traite \MacOSX, mais pas les versions antérieures des Macintosh. - -On peut installer \TeX{} sous \MacOSX{} de deux façons : - -\begin{enumerate} - -\item Utiliser la nouvelle distribution, appellée Mac\TeX{}, disponible - depuis l'édition 2005 sur le \DVDlive ; elle se trouve dans le répertoire - \dirname{mactex/}, voir section~\ref{sec:mactex}. C'est la méthode - \emph{vivement recommandée}, car l'installation est très simple. - -\item Utiliser les commandes \filename{install*} comme pour Unix (lire d'abord - la section~\ref{sec:osx-unix-inst} ci-dessous pour les spécificités \MacOSX{} -puis la section~\ref{sec:unix-install}). Cette méthode offre plus de choix -quant à ce qui sera installé mais déroute bien des utilisateurs de Macintosh -(ceux qui répugnent à taper des commandes dans un Terminal). - -\end{enumerate} - -\noindent Par ailleurs, l'utilisation de \TeX{} sous \MacOSX{} se fait -normalement par le biais d'une interface graphique (\emph{frontend}), -comme expliqué ci-dessous à la section~\ref{sec:interf-graph-macosx}. - -\subsection{Installation de Mac\TeX} -\label{sec:mactex} - -La distribution Mac\TeX{} est une variante de \TL{} complétée par de -nombreuses applications et de la documentation spécifique. -Elle dispose de son propre installeur intégré. - -Le site de référence pour Mac\TeX{} est \url{http://tug.org/mactex}. - -\subsection{\protect\cmdname{install*.sh} : installation depuis \TL{}} -\label{sec:osx-unix-inst} - -Le système \MacOSX{} est un Unix (presque) comme les autres, mais Apple -cache soigneusement ce fait, ce qui ne facilite pas l'installation de -logiciels comme \TL{}. - -Nous allons essayer de décrire en détail la procédure d'installation. -La première chose à faire est d'ouvrir une fenêtre \og Terminal \fg{}. -L'application \og Terminal\fg{} se trouve dans le répertoire -/Applications/Utilitaires, elle est accessible à partir du menu -principal en haut de l'écran. - -Ensuite, nous allons vérifier si l'interpréteur de commandes -(ou \textit{shell} en anglais) \cmdname{bash} est présent ou non. -Pour cela, taper dans la fenêtre \og Terminal \fg{} la commande suivante : -\begin{alltt} -> \Ucom{which bash} -\end{alltt} -Si le \textit{shell} \cmdname{bash} est présent (cas des versions -de 10.2 et suivantes de \MacOSX) la réponse sera un chemin, par exemple -\filename{/bin/bash}. -Si la réponse est \texttt{command not found}, vous avez une version -antérieure à 10.2, sur laquelle \cmdname{bash} n'est pas installé par défaut. -Vous devrez alors récupérer le \textit{shell} \cmdname{bash} sur internet -(par exemple ici : \url{http://tug.org/texlive/bash.dmg}) -et l'installer\dots{} ou mieux, mettre à jour votre version de \MacOSX. - -Supposons désormais le \textit{shell} \cmdname{bash} présent. -Il faut maintenant \og passer \textit{root} \fg{}, c'est-à-dire -se donner le pouvoir d'effectuer des opérations normalement interdites -aux utilisateurs de base. Ceci se fait en tapant dans le \og Terminal\fg{} -la commande : -\begin{alltt} -> \Ucom{sudo su -} -\end{alltt} - -Mettre le \CDinst{} ou le \DVDlive{} dans le lecteur, son contenu -devient automatiquement accessible sous le répertoire \dirname{/Volumes}. -On tape ensuite dans le \og Terminal\fg{} les commandes : -\begin{alltt} -> \Ucom{cd /Volumes/texlive2007} -> \Ucom{sh install-tl.sh} -\end{alltt} -pour se placer à la racine de l'image disque montée et y lancer le script -d'installation. Il suffit ensuite de suivre la documentation -d'installation de la section~\ref{sec:unix-install-disk} -\p.\pageref{sec:unix-install-disk} où des notes spécifiques pour \MacOSX{} -ont été incluses si nécessaire. - -\subsection{Interfaces graphiques pour \MacOSX{}} -\label{sec:interf-graph-macosx} - -Normalement, l'utilisation de \TeX{} sur un Macintosh se fait à travers -une interface graphique, comprenant un \textit{shell} d'exécution, un -éditeur, un prévisualiseur et d'autres outils (on échappe toutefois -difficilement à l'utilisation de \og Terminal \fg{} dès que l'on veut -réaliser des tâches un tant soit peu évoluées\ldots). - -Voici les principales interfaces disponibles : - -\begin{cmddescription} -\item [TeXShop] Inclus dans \TL{} sous -\filename{./MacOSX/texshop.dmg}.\\ -Voir \url{http://www.uoregon.edu/~koch/texshop/texshop.html}. - -\item [ITeXMac] Inclus dans \TL{} sous \filename{./MacOSX/iTM-*.dmg}.\\ -Voir \url{http://itexmac.sourceforge.net}. - -\item [Mac-emacs] Une adaptation d'Emacs à \MacOSX{}, avec -\pkgname{AucTeX} inclus.\\ -Voir \url{http://www.cs.man.ac.uk/~franconi/mac-emacs}. - -\end{cmddescription} - -Si vous choisissez d'utiliser \cmdname{TeXShop} ou \cmdname{ITeXMac}, -il sera nécessaire de donner à ces logiciels les informations concernant -le PATH : - -\begin{cmddescription} - -\item [TeXshop] Lancer l'application et ouvrir le panneau préférences (menu - TeXShop). Sélectionner l'onglet \og Moteur\fg{} et modifier la première - ligne en saisissant votre PATH, par exemple : - \dirname{/usr/local/texlive/2007/bin/powerpc-darwin}. - -\item [ITeXMac] Lancer l'application et ouvrir le panneau préférences (menu - ITeXMac). Sélectionner le bouton \og Assistant teTeX\fg{}, puis l'onglet - \og TeX\fg{} et cliquer sur le bouton radio \og{} Autre\fg{}. Saisir alors - votre PATH, par exemple : - \dirname{/usr/local/texlive/2007/bin/powerpc-darwin}. - -\end{cmddescription} - - -\section{Installation sous Windows} -\label{sec:win-install} - -La distribution \TL{} inclut un -installeur pour Windows qui s'appelle \cmdname{tlpmgui}. - -%%%%%%%%%%%%%%%%%%%% Ajout (df) %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% -\begin{quote} -\textbf{Note du traducteur :} à titre personnel, je ne recommande pas -l'installation sous Windows à partir de \cmdname{tlpmgui}, sauf aux -utilisateurs qui connaissent bien \TL{} sous Unix et veulent avoir sous -Windows une distribution aussi proche que possible de celle-ci. - -Une autre piste, non basée sur la distribution \TL{}, me semble nettement plus -adaptée : il s'agit installer la distribution \ProTeXt{} à partir du -\DVDlive{} ou du \CD{} spécifique, elle est basée sur \MIKTEX{} distribution -très appréciée sous Windows ; - -Si vous décidez d'opter pour \ProTeXt{} la suite de toute cette -section ainsi que la suivante (Maintenance sous Windows) ne vous -concernent pas. -\end{quote} -%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% - -\cmdname{tlpmgui} propose essentiellement les mêmes options que le script -\cmdname{install-tl.sh} sous Unix mais dans une interface graphique : - sélection des schémas, choix des collections, etc., se reporter -à la section~\ref{sec:unix-install-disk} \p.\pageref{sec:unix-install-disk}. -Certaines manipulations telles que l'ajout ou la suppression -de composants, la mise à jour des bases de données -et la constructions de formats sont également possibles. -De plus, \cmdname{tlpmgui} offre la possibilité d'utiliser \TL{} depuis -le \DVDlive{} (sans l'installer sur le disque dur). - -Pour les connaisseurs, \cmdname{tlpmgui} repose sur le programme -\cmdname{tlpm} accessible en ligne de commande Windows. - -Les binaires pour Windows sont empruntés à la distribution \acro{W32TEX}, -fournie par Akira Kakuto. -Certains outils de l'ancienne distribution \fpTeX{} de Fabrice Popineau ont -été conservés, le nouveau visualiseur \cmdname{dviout} de Toshio Oshima -a remplacé celui de Fabrice (\cmdname{Windvi}). - -\TL{} peut être installé sur les systèmes Windows~9x, \acro{ME}, -\acro{NT}, \acro{2K} or \acro{XP}. Il ne fonctionne pas avec les versions -plus anciennes Windows (3.1x) et \acro{MS-DOS}. - -\textbf{Attention :} Les utilisateurs de Windows~9x - doit vérifier qu'il disposent d'assez d'espace pour les variables - d'environnement. Le programme \cmdname{tlpmgui.exe} crée un certain - nombre de variables d'environnement, si l'espace manque ajouter - \texttt{SHELL=COMMAND.COM /E:4096 /P} dans le fichier - \filename{config.sys}. - -\subsection{Installation sous Windows depuis le \CDinst} - -Le programme \cmdname{tlpmgui} devrait démarrer automatiquement -dès l'insertion du \CDinst{} dans le lecteur de \acro{CD}. -Si ce n'est pas le cas, cliquer sur \guiseq{Start\arw Run} puis -taper \path{:\string\setuptl\string\tplmgui.exe} ---- resp. -\path{:\string\texlive\string\setuptl\string\tplmgui.exe} -si vous installez à partir du \DVDlive{} --- où \path{} -désigne la lettre correspondant au lecteur de \acro{CD} ; cliquer ensuite -sur OK. - -La fenêtre intitulée \guiseq{TeX Live installation and maintenance utility} -devrait s'ouvrir. Elle propose les options suivantes : -\guiseq{Main customization}, \guiseq{Install}, \guiseq{Select a scheme}, -\guiseq{Select systems}, \guiseq{Directories} et \guiseq{Options}. - -Dans la section \guiseq{Directories}, le nom du lecteur de \acro{CD/DVD} -(par exemple \texttt{F:/}) devrait apparaître à côté du bouton -\acro{CD/DVD}. S'il n'est pas affiché utiliser ce bouton pour -sélectionner le lecteur de \acro{CD/DVD} contenant \TL. - -Il est possible de choisir le répertoire devant contenir la distribution \TL{} -en cliquant sur le bouton \guiseq{TLroot}(la variable \path{TLroot} contiendra -le nom de ce répertoire). -% Le contenu des variables d'environnement -% \path{TEXMFTEMP} et \path{TEXMFCNF} est affiché à côté des boutons -% \guiseq{TEXMFTEMP} et \guiseq{TEXMFCNF}, il sera mis à jour automatiquement -% pendant l'installation (il est possible de le modifier en cas de besoin -% particulier). - -La section \guiseq{Select a scheme} permet, comme sous Unix, de choisir le -schéma de base souhaité pour l'installation (complète, GUTenberg, etc.) : -utiliser le bouton radio pour faire ce choix et le bouton \guiseq{Info} -pour une description du schéma sélectionné. - -Il est possible de personnaliser le schéma choisi en lui ajoutant ou en -supprimant certaines de ses composantes (appelées \guiseq{collections}). -Ceci se fait en utilisant les boutons \guiseq{Standard collections} -et \guiseq{Language collections} (choix des langues utilisables) -dans \guiseq{Main customization}. - -La collection \guiseq{Wintools} est sélectionnée par défaut car elle contient -beaucoup de petits utilitaires non fournis avec Windows, comme des -convertisseurs tels que \cmdname{sam2p}, \cmdname{jpeg2ps}, \cmdname{tiff2png}, -des prgramme de compression tels que \cmdname{bzip2}, \cmdname{gzip}, -\cmdname{unzip} et \cmdname{wget} qui est requis par le nouvel utilitaire -\cmdname{getnonfreefonts}. - -\textbf{Remarque :} Les collections \guiseq{Ghostscript}, \guiseq{Perl} -sont sélectionnées par défaut. Elles \emph{doivent être -installées}\dots{} sauf si elles l'ont été par ailleurs. -Les variables d'environnement \envname{PERL5LIB} et \verb|GS_LIB| doivent -aussi être initialisées et le chemin complet des binaires \guiseq{Ghostscript} -doit être ajouté à la variable \verb|PATH|. - -Finalement, cliquer sur le bouton \guiseq{Install} dans la section -\guiseq{Install} pour lancer le processus d'installation. - -Laisser le processus se poursuivre jusqu'à l'affichage du message annonçant -que l'installation a réussi (un certain nombre d'étapes sont nécessaires, -comme la création des formats, la mise à jour des bases de données, etc. ce -qui peut prendre un certain temps). - -Un raccourci pour \cmdname{tlpmgui} (et pour \cmdname{dviout} s'il est -installé), sera ajouté dans le menu \guiseq{Start\arw Programs\arw -TeXLive2007}. - -Si nécessaire (Windows~9x/WinME), il vous sera demandé de -redémarrer l'ordinateur. - - -\subsection{Programmes auxiliaires pour Windows} -\label{sec:win-xemtex} - -Pour être complète, une installation \TL{} a besoin de programmes -auxiliaires qu'on ne trouve pas fréquemment sur une machine Windows. -De nombreux scripts sont écrits en Perl. Certains outils importants utilisent -l'interpréteur \PS{} Ghostscript pour afficher ou convertir les fichiers. -Il faut aussi dans certains cas une boîte à outils graphique. -Enfin, un éditeur orienté \TeX{} facilite la saisie de fichiers \TeX{}. - -Tous ces outils sont assez faciles à trouver pour \TeX{}, mais pour essayer -de vous rendre la vie plus facile, nous avons incorporé des outils de ce type -dans \TL{} : -\begin{itemize} -\item GNU \cmdname{GhostScript} 8.54 ; -\item un \cmdname{Perl} 5.8 minimum, suffisant pour exécuter tous les scripts -Perl du \TL{} ; -\item quelques utilitaires comme bzip2, gzip, jpeg2ps et tiff2png. -\end{itemize} - -Perl et Ghostscript sont installés par défaut ; vous pouvez empêcher -leur installation en les déselectionant explicitement lors de -l'installation si vous les avez déjà. - -Si vous préférez ne pas installer les outils inclus dans \TL{}, vous êtes -libre d'installer les outils nécessaires pour compléter votre système \TL{} ; -voici une liste des adresses où les obtenir : -\begin{description} -\item[GhostScript] \url{http://www.cs.wisc.edu/~ghost/} -\item[Perl] \url{http://www.activestate.com/} (mais il vous faudra peut-être - chercher des bibliothèques supplémentaires sur CPAN, - \url{http://www.cpan.org/}) -\item[ImageMagick] \url{http://www.imagemagick.com} -\item[NetPBM] Vous pouvez aussi utiliser NetPBM à la place de ImageMagick - pour traiter ou convertir vos fichiers graphiques. La page d'accueil - de NetPBM est - \url{http://netpbm.sourceforge.net/} -\item[Éditeurs orientés \TeX] Il y a un large choix, et cela dépend des - préférences de l'utilisateur. En voici une sélection : - \begin{itemize} - \item \cmdname{GNU Emacs} avec l'extension AucTeX existe nativement - sous Windows, l'url de référence est - \url{ftp://alpha.gnu.org/gnu/auctex} ; - \item \cmdname{WinShell} se trouve sur \TL{} dans le répertoire - \path{support}, l'url de référence est \url{http://www.winshell.de} ; - \item \cmdname{WinEdt} est un partagiciel disponible à l'adresse - \url{http://www.winedt.com} ; - \item TeXnicCenter est libre et se trouve à l'adresse - \url{http://www.toolscenter.org/products/texniccenter/} et aussi dans - la distribution \ProTeXt{} ; - \item \cmdname{Vim} peut être téléchargé sur le site - \url{http://www.vim.org} ; - \item \cmdname{LEd} se trouve à l'adresse - \url{http://www.ctan.org/support/LEd} ; - \item \cmdname{SciTE} se trouve à l'adresse - \url{http://www.scintilla.org/SciTE.html}. - \end{itemize} -\end{description} - -Il est aussi possible d'installer d'autres outils qui ne sont pas -libres\footnote{Pas libres en fait dans le sens de la liberté de les - modifier et les redistribuer, selon les -\emph{Debian's guidelines}. Cela ne signifie pas qu'on ne peut pas les -acquérir gratuitement.} -comme \cmdname{GSView}, le programme compagnon de \cmdname{GhostScript} -pour afficher plus facilement les fichiers PS/PDF. -\cmdname{GSView} est disponible à l'url -\url{http://www.cs.wisc.edu/~ghost/gsview/} -ou sur tout site \acro{CTAN}. - -\section{Maintenance sous Windows} - -Une fois la distribution \TL{} installée, vous pouvez vous servir du programme -\cmdname{tlpmgui} pour modifier ou compléter votre installation. - -\subsection{Ajouter ou supprimer des composants} - -Le raccourci \cmdname{tlpmgui} du menu -\guiseq{Start\arw Programs\arw TeXLive2007} permet de lancer le programme -et affiche la fenêtre \guiseq{TeX Live installation and maintenance utility}. -Les sections à utiliser sont \guiseq{Add Packages} (ajout de composants), -\guiseq{Remove packages} (suppression de composants), -\guiseq{Manage installation} (maintenace), \guiseq{Remove installation} -(suppression totale de \TL). - -Cliquer sur \guiseq{Add packages} ou \guiseq{Remove packages}, puis - -\begin{itemize} -\item Choisir le lecteur de \acro{CD} (ou le répertoire \texttt{texlive} - du lecteur de \acro{DVD}) grâce au bouton \guiseq{CD/DVD}. - -\item Cliquer sur le bouton \guiseq{Search} dans la section \guiseq{Buttons} -pour afficher la liste de composants à installer ou à supprimer -dans \guiseq{Select packages to\dots}. - -Lors de l'ajout de composants, la liste des composants installés est comparée -à la liste des composants disponibles sur le \acro{CD/DVD}. -Seuls les composants non installés sont affichés, à vous de choisir ceux que -vous souhaitez ajouter. - -Inversement, lors de la suppression de composants, seuls les composants -installés sont affichés. - -Noter que les collections sont en tête de liste. - -\item Sélectionner un composant en cliquant sur son nom dans la liste. -Un clic sur le bouton \guiseq{Info} donne une courte description du contenu. -Il est possible de sélectionner plusieurs composants à la fois à l'aide des -touches \og Ctrl \fg{} et \og Shift \fg{} (majuscules). - -\item Cliquer sur \guiseq{Install} ou \guiseq{Remove} pour terminer -l'opération. -\end{itemize} - -\subsection{Configuration et maintenance} - -La section \guiseq{Manage the installation} permet d'effectuer les opérations -courantes de configuration et de maintenance. - -Voici la liste des actions possibles : -\begin{itemize} - \item mettre à jour la base \filename{ls-R}, - \item créer les formats, - \item modifier le fichier \filename{language.dat}, - \item modifier le fichier \filename{fmtutil.cnf}, - \item modifier le fichier \filename{updmap.cfg}. - \end{itemize} - -Il faut sortir de la fenêtre d'édition en cliquant sur le bouton \guiseq{Done} -pour que les mises à jour des formats, fichiers \file{.map}, base -\filename{ls-R} soient effectuées. - -Les autres possibilités de configuration sont décrites à la -section~\ref{sec:persconf}, \p.\pageref{sec:persconf}. - -\subsection{Désinstallation complète de \TL{}} - -L'option \guiseq{Remove the TeX Live installation} permet de supprimer toute -la distribution \TL{}. - -Attention, ce que vous avez éventuellement installé dans le répertoire -\path{texmf-local} ne sera pas supprimé ; le répertoire \path{setuptl} -contenant \cmdname{tlpmgui} doit être également nettoyé à la main si -nécessaire. - -\subsection{Ajouter des composants à votre système} - -Tout d'abord, quelles que soient les modifications faites, -\emph{n'oubliez pas de reconstruire les fichiers ls-R de bases de - données}, sinon les nouveaux fichiers ne seront jamais retrouvés. -Pour cela, vous pouvez soit utiliser le programme \cmdname{tlpmgui}, option -\guiseq{Manage the installation}, soit lancer manuellement la commande -\file{mktexlsr}. - -Si vous choisissez d'ajouter des fichiers qui ne proviennent pas de la -distribution \TL{} (ou fp\TeX{}), il est fortement -recommandé de les mettre dans le répertoire \path{$TEXMFLOCAL}. %$ -De cette manière, vous serez certain qu'il n'y aura pas de problème -lors d'une mise à jour de \TL. - -L'arborescence pointée par \path{$TEXMFLOCAL} est initialement %$ -vide. Si vous souhaitez y ajouter par exemple les fichiers de style -pour le logiciel de calcul formel Maple, vous devrez mettre ces -fichiers dans le répertoire -\path{C:\string\TeXLive2007\string\texmf-local\string\tex\string\latex\string\maple} -et les fichiers de documentation dans -\path{C:\string\TeXLive2007\string\texmf-local\string\doc\string\latex\string\maple} - - -\subsection{Exécution de \texttt{tlmp.exe} en ligne de commande} - -Le programme \cmdname{tlpm.exe} utilisé par \cmdname{tlpmgui} -possède de nombreuses options utiles dont la liste est donnée par -\begin{verbatim} -tlpm --help -\end{verbatim} - -Consulter le fichier \filename{tlpm.readme} pour plus de renseignements et des -exemples. - -\subsection{Installation en réseau} - -\KPS{} est compatible avec les noms UNC, ceux-ci peuvent donc être utilisés -pour récupérer l'arborescence TEXMF depuis le réseau. Mais -encore mieux, tous les fichiers, y compris ceux de -configuration et excepté les binaires dans \path{bin/win32}, sont -compatibles et partageables avec \teTeX{} ou le \TL{} Unix. Cela -signifie que vous pouvez utiliser Samba, soit pour monter la -distribution Unix sur un client Windows, ou un client Unix -depuis un serveur NT. Plusieurs stratégies sont possibles : -\begin{itemize} - -\item tout mettre sur le serveur. Il faut simplement être certain de mettre dans \path{bin/} les binaires pour tous les couples systèmes d'exploitation / architectures nécessaires. Par exemple, ajouter \path{bin/win32} et - \path{bin/i386-linux}. Ensuite configurer les variables principales ; vous - pouvez utiliser des noms UNC pour pointer sur les répertoires appropriés - sous Win32. - -\item Installer une copie locale pour les binaires et les fichiers de - format. Dans ce cas, assigner \path{$TEXMFMAIN} au répertoire - principal \path{texmf} qui sera pris sur le réseau. Faire pointer - \path{$VARTEXMF} vers un répertoire local qui contiendra les fichiers - de configuration locaux et les fichiers générés au vol. %$ - -\end{itemize} - -\subsection{Différences entre la version Windows et la version - Unix de \TL} - -La version Windows de \Webc{} possède quelques spécificités qui méritent -d'être notées. - -\begin{description} -\item [\cmdname{kpsecheck}] Cette commande fournit des fonctionnalités - qui ne rentraient pas bien dans \cmdname{kpsewhich}. En particulier, - elle permet de lister tous les fichiers qui apparaissent plusieurs - fois à travers les multiples arborescences \path{texmf/}. Ceci à - l'air pratique, sauf qu'en réalité, la sortie est polluée par des - occurrences multiples de fichiers qui ne sont pas utiles à \TeX{} à - proprement parler (commes des dizaines de fichiers - \filename{README})\footnote{Tous ces fichiers - sont susceptibles de produire des collisions lors de l'accès à la - table de hachage ; heureusement \TeX{} ne les utilise pas, ils ne - sont donc pas pris en compte !}. Pour cette raison, vous pouvez combiner - l'option \path{-multiple-occurences} avec deux autres options pour - inclure ou exclure de la recherche tout fichier conforme à un - certain motif (plusieurs motifs d'inclusion ou d'exclusion peuvent - être spécifiés). - - La commande \cmdname{kpsecheck} peut aussi indiquer le statut - d'utilisation de la mémoire partagée : en utilisation ou - non-utilisée. Cette information peut être très utile, car si le - statut rapporté est \og en utilisation\fg{}, cela signifie qu'un - ou plusieurs processus tournent et utilisent le bloc de mémoire - partagée. Dans ce cas, une réinitialisation des tables de hachage - basée sur les fichiers \filename{ls-R}, comme la commande - \cmdname{mktexlsr} l'effectue, sera automatiquement repoussée - jusqu'à ce que tous les processus utilisant la version courante en - mémoire partagée soient terminés. Il est prévu d'enlever cette - limitation dans une version future, mais la version actuelle de - \KPS{} ne permet pas de faire facilement cette réinitialisation. - - Enfin, la même commande \cmdname{kpsecheck} peut indiquer l'endroit - où \KPS{} pense pouvoir trouver la Dll de Ghostscript. En effet, - sous Win32, il est souvent plus simple de travailler directement - avec la Dll de Ghostscript, et de la trouver en utilisant la clé - appropriée dans la base de registre, que d'utiliser \path{gswin32c.exe} et - de modifier le \path{PATH} qui a une longueur limitée. - -\item [\Webc] Les moteurs \TeX{} ont une option supplémentaire - par rapport à la version standard : - \path{-proctimes} affiche des statistiques à propos du - temps d'exécution. Il est à noter que Windows~9x n'étant pas un - système multi-tâche préemptif, il ne possède pas d'horloge - interne suffisamment précise pour mesurer ces temps d'exécution - et donc la valeur affichée n'est qu'une approximation. Sous - NT/2K/XP, le résultat est assez précis et comprend le temps - utilisateur et le temps système alloués à la compilation. Pour - les utilisateurs d'Unix : la commande \path{time} n'existe pas - sous Windows. -\end{description} - -\subsection{Personnalisation de l'installation} -\label{sec:persconf} - -\subsubsection{Dvips} - -Le fichier de configuration de \texttt{dvips} se trouve par défaut en -\path{C:\string\TeXLive2007\string\texmf-var\string\dvips\string\config\string\config.ps}. Il peut être ouvert avec n'importe quel éditeur de texte -% (comme \cmdname{WinShell}) -pour modifier certains paramètres : -\begin{description} -\item[fontes] vous pouvez changer la résolution et le mode de - l'imprimante à laquelle sont destinés vos fichiers dans le cas où - \texttt{dvips} aurait besoin de générer des fontes bitmap. Par défaut, - les fontes Type1 CM interpolées sont utilisées, et donc - \path{mktexpk} ne devrait pas être appelé trop souvent. -\item[imprimante] vous pouvez spécifier où se fera l'impression par - défaut. Si l'option `o' n'est pas suivie d'un nom d'imprimante, un - fichier est créé avec l'extension \file{.ps}. Sinon, vous pouvez - spécifier un nom d'imprimante tel que : -\begin{verbatim} -o lpt1: -% o | lpr -S server -P myprinter -% o \\server\myprinter -\end{verbatim} -\item[papier] vous pouvez changer le format de papier retenu par - défaut (A4), par exemple en format US letter, le premier format - mentionné. Allez vers les lignes débutant par \path{@}. Déplacez les - lignes adéquates, ainsi le fichier commencera par les lignes qui suivent. -\begin{verbatim} -@ letterSize 8.5in 11in - -@ letter 8.5in 11in -@+ %%BeginPaperSize: Letter -@+ letter -@+ %%EndPaperSize -\end{verbatim} -\end{description} - -La distribution \TL{} actuelle intègre un programme \og \cmdname{updmap} \fg{} -facilitant la mise à jour des fichiers \file{psfonts.map} pour Dvips et -\file{pdftex.map} pour PdfTeX. -\cmdname{updmap} est lancé automatiquement durant l'installation. -Si vous ajoutez de nouvelles fontes à la main, -éditez le fichier \verb+updmap.cfg+ dans \path{$TEXMFVAR/web2c}. %$ -et relancez \cmdname{updmap}. - -\subsubsection{PdfTeX} - -Si le programme \cmdname{pdflatex} est utilisé pour écrire directement en -format -\acro{PDF} et qu'on utilise du papier au format \acro{US} letter-size, -éditer le fichier -\path{C:\string\TeXLive2007\string\texmf-var\string\tex\string\generic\string\config\string\pdftexconfig.tex} -et modifier \samp{\bs page\_width} et \samp{\bs page\_height}. -Ces entrées doivent être : -\begin{alltt} -\bs{}pdfpagewidth=8.5 true in -\bs{}pdfpageheight=11 true in -\end{alltt} - -Sauvegarder le fichier et sortir de l'éditeur. - -\subsubsection{Xe\TeX} - -Xe\TeX{} pour Windows est lié statiquement à la bibliothèque fontconfig 2.4.2. -Le fichier de configuration pour les fontes s'appelle \verb+fonts.conf+. -Ce fichier se trouve dans le répertoire indiqué par la commande -\texttt{kpsewhich --var-value=FONTCONFIG\_PATH}. - -\subsubsection{Gsview} - -\cmdname{GSView} est maintenant distribué sous licence Aladdin et n'est donc -plus inclus dans \TL{}. - -Si vous voulez changer le format du papier, ouvrez \cmdname{GSView} à -partir du menu \guiseq{Démarrer} et sélectionnez \guiseq{Media\arw Letter}. -Le sous menu Display Settings vous permet -également d'améliorer la netteté du rendu en positionnant les -deux valeurs \textbf{Text Alpha} et \textbf{Graphics Alpha} à 4 bits. - -Pour ce qui est de l'impression, consulter la -sous-section~\ref{sub:printing}. - -Les fichiers \file{.ps} et \file{.eps} seront automatiquement ouverts -par \cmdname{GSView}. - -\subsection{Tests} - -Pour des procédures génériques de vérification, voir -section~\ref{sec:test-install}, page~\pageref{sec:test-install}. -Cette section décrit les tests spécifiques à Windows. - -Vous pouvez tester l'installation -en ouvrant le fichier -\verb+sample2e.tex+ dans votre éditeur (\cmdname{XEmacs}, -\cmdname{WinShell}) qui se trouve dans -\path{C:\string\TeXLive2007\string\texmf-dist\string\tex\string\latex\string\base}. -Le source \LaTeX{} doit apparaître à l'écran. Compilez-le en cliquant -sur le menu (XEmacs) \guiseq{Command\arw LaTeX} ou sur l'icône \LaTeX{} -(WinShell) dans la barre d'outils, ensuite affichez-le en -cliquant sur le menu (XEmacs) \guiseq{Command\arw View DVI} -ou sur l'icône Preview (dviout). - -La première fois que vous afficherez un document avec \cmdname{dviout}, il va -créer les fichiers de fontes bitmaps qui ne sont pas installées. -Après avoir visualisé quelques fichiers, vous aurez créé la plupart de ces -fichiers et vous ne verrez plus souvent apparaître la fenêtre de création de -fontes. - -En cas de problèmes, reportez-vous à la -sous-section~\ref{sec:troubleshooting}. - -\subsection{Impression} -\label{sub:printing} - -Il est possible d'imprimer depuis \cmdname{dviout}. Dans ce cas, l'impression -utilise le pilote unifié d'impression de Windows, il est donc par -définition compatible avec toutes les imprimantes. Cependant, il y a -un inconvénient : cette impression génère des fichiers (spool) très -importants, quelques versions anciennes de Windows le supportent mal. -L'avantage est que vous pouvez tirer -parti de l'impression d'images BMP ou WMF par exemple. Il faut -également faire bien attention à ce que les paramètres de l'imprimante -soient correctement définis sous peine -d'avoir un effet d'échelle -(imprimer à 600\,dpi sur une imprimante qui fait réellement 300\,dpi -aboutit à n'avoir qu'un seul quart de la page visible). - -L'impression est souvent plus rapide en utilisant \cmdname{dvips}, puis en -imprimant le fichier \file{.ps} depuis \cmdname{GSView}. Pour imprimer -depuis \cmdname{GSView}, sélectionner \textbf{Print\dots{}} dans le menu -\textbf{File}. Une fenêtre de dialogue pour l'impression apparaît. - -Si vous utilisez une imprimante PostScript, \emph{soyez sûr de - sélectionner \textbf{PostScript Printer}} en choisissant cette -option dans \textbf{Print Method} en bas à gauche de la boîte de -dialogue, faute de quoi l'impression échouera. Vous -pouvez ensuite sélectionner une imprimante quelconque parmi celles -installées. - -Si vous utilisez une imprimante qui ne supporte pas PostScript, -sélectionnez \textbf{Ghostscript Device} dans \textbf{Print - Method}. Ensuite cliquez sur le bouton \textbf{djet500} et -sélectionnez votre imprimante. - -\subsection{Trucs et astuces à propos de la plate-forme Win32} - -\subsubsection{Différentes déclinaisons de Win32} - -Ce que recouvre la dénomination Win32 n'est pas un système -d'exploitation. C'est un ensemble de fonctions très -vaste (environ 12000 fonctions dans les fichiers d'en-tête du - SDK Microsoft) que vous pouvez utiliser pour écrire des programmes -pour différentes versions des systèmes d'exploitation de la famille -Windows. - -Windows se décline en plusieurs versions : -\begin{itemize} -\item Win95, Win98 et WinME, qui \emph{ne sont pas de vrais systèmes - d'exploitation multitâches et multithreads}. Ils sont en fait les - dernières incarnations de DOS. On peut s'en apercevoir, car en - lançant le PC, l'interpréteur de commandes \path{command.com} est - chargé et si vous arrêtez le processus à ce moment, vous pouvez - demander la version courante (de DOS) et il vous est répondu quelque - chose du style "MS-DOS 7.0", au moins pour les versions anciennes de - Windows~9x ; -\item Windows \acro{NT} est un système d'exploitation écrit à partir - de zéro, avec un - vrai multitâche préemptif et des fonctionnalités de très haut niveau ; -\item Windows 2000 est écrit sur une base \acro{NT}, il est doté de toutes les - facilités offertes par Win98 ; -\item Windows \acro{XP} existe en versions Personnelle et - Professionnelle. C'est la dernière étape dans la fusion entre les - deux lignes de produits (basée sur Windows~9x et basée sur NT). \acro{XP} est - écrit sur une base NT. -\end{itemize} - -Windows~9x peut faire tourner des programmes 32~bits et des -programmes 16~bits en même temps. Mais le système d'exploitation -lui-même n'est pas entièrement écrit en mode 32~bits et ne fournit pas -une protection mémoire entre les applications : les applications -16~bits peuvent écraser des parties du système d'exploitation en -mémoire ! Des parties du système telles que le \acro{GDI} -(\emph{Graphical Device Interface}) ne se voient allouer que des -ressources de taille très -limitée pour gérer les bitmaps, les pinceaux et les polices, et ces -ressources sont allouées de manière globale pour tous les programmes -qui tournent de manière concurrente. Par exemple, toutes les entêtes de -bitmaps utilisés par tous les programmes qui tournent simultanément ne -doivent pas requérir plus de 64~ko de mémoire. Ceci explique le -comportement du moniteur de performance et le fait que vous pouvez -mettre votre système à genoux en utilisant de manière intensive les -objets graphiques. - -NT, 2K et XP ne souffrent pas de ces limitations, ni d'aucune autre -limitation de Windows~9x. Ce sont de vrais environnements multitâches, avec -une vraie mémoire protégée. Ils répondent de manière plus fluide que -Windows~9x de par leur meilleure gestion de la mémoire, leur système de -gestion de fichiers plus performant, etc. - -\subsubsection{La ligne de commande} - -Vous allez demander : mais pourquoi diable devrais-je me -préoccuper d'une ligne de commande alors que j'ai Windows ? - -Bonne question. Le problème est de nature très générale. Toutes les -opérations ne peuvent pas être accomplies très facilement à l'aide de -la seule interface graphique. La ligne de commande vous donne la -puissance de la programmation -- si vous avez un bon interpréteur de -commandes. - -Mais le problème est plus fondamental : \TeX{} est un outil qui -fonctionne \emph{en batch}, de manière non interactive. \TeX{} a -besoin de calculer la meilleure mise en page pour chaque page, de -résoudre les références croisées, etc. Ceci ne peut être réalisé -que par un traitement global du document. Ce n'est pas encore une tâche -qui peut être réalisée interactivement. - -Ceci implique que vous devriez utiliser \TeX{} depuis la ligne de -commande. En fait la situation n'est pas si catastrophique. Il y a un -avantage à écrire des outils en ligne de commande pour des tâches -complexes : ils sont bien plus fiables, parce qu'ils n'héritent pas de -la complexité inhérente aux interfaces graphiques. -Il est ensuite possible de -concevoir des outils graphiques qui servent d'interface aux outils en -ligne de commande. C'est le cas de \TeX{} : vous interagirez avec lui -la plupart du temps au travers d'un éditeur de textes qui possède une -interface graphique. - -Cependant, il se peut que vous ayez besoin d'utiliser la ligne de -commande dans certaines situations. Par exemple en cas de -problèmes, parce que vous avez besoin de trouver une erreur dans votre -installation -- voir la section~\ref{sec:troubleshooting}. - -\begin{description} -\item[Windows~9x, WinME] Vous ouvrirez une ligne de commande soit en cherchant - l'icône \acro{MS-DOS} dans le menu \og \guiseq{Démarrer\arw Programmes}\fg{}, - soit en choisissant \og \guiseq{Démarrer\arw Exécuter}\fg{}, puis en tapant - \path{command.com} . -\item[NT, 2K, XP] Vous ouvrirez une ligne de commande en cherchant - \og \guiseq{Invite de commandes}\fg{} dans le menu \og \guiseq{Démarrer\arw - Accessoires}\fg{} (ces emplacements peuvent changer d'une version de Windows à - l'autre). Vous pouvez aussi choisir le menu - \og Démarrer -> Exécuter\fg{} et taper \path{cmd.exe}, qui est le nom - du nouvel interpréteur de commandes pour NT. -\end{description} - -\subsubsection{Les séparateurs de chemins} - -L'API Win32 admet les deux caractères \verb+/+ et \verb+\+ comme -séparateurs pour les noms de fichiers. Mais pas les interpréteurs -de commande ! Donc, chaque fois qu'un nom de fichier est utilisé par -un programme, vous pouvez utiliser l'un ou l'autre séparateur, mais -sur la ligne de commande, vous devez utiliser \verb+\+ comme unique -séparateur. Ce qui explique que vous pouvez taper : -\begin{verbatim} - C:\>set TEXMFCNF=C:/Program Files/TeXLive/texmf-var/web2c -\end{verbatim} -mais pas : -\begin{verbatim} -C:\>dir "C:/Program Files/TeXLive" -\end{verbatim} -Dans le premier cas, seuls des programmes utiliseront le chemin que -vous avez fourni, dans le deuxième cas, c'est l'interpréteur de commandes -qui va vouloir s'en servir directement. - -Tout ceci pour dire, ne soyez pas surpris de voir des noms de -fichiers écrits avec des \path{/} en guise de séparateurs, à la mode Unix ; -Windows-\TL{} est un portage de \Webc, dont l'objectif est d'être -compatible avec toutes les plates-formes. Pour cette raison, les -fichiers de configuration utilisent la convention Unix des séparateurs -dans les noms de fichiers. - -\subsubsection{Les systèmes de gestion de fichiers} - -Une des plus mauvaises caractéristiques de Windows~9x vis-à-vis de \TeX{} -est probablement ce qu'on appelle le système de fichiers FAT. -\TeX{} utilise une myriade de petits fichiers dont la taille varie -entre 1~ko et 5~ko. Le système FAT est ancien et date d'une époque bien -antérieure à l'apparition des disques de plusieurs Go qui sont monnaie -courante aujourd'hui. Tout ceci pour dire qu'il n'est pas possible de -gérer efficacement les dizaines de fichiers de \TL{} sur un disque dur -formaté en FAT. Les fichiers se voient allouer chacun 32~ko au -minimum, donc l'installation de \TL{} utilise beaucoup plus de -place que nécessaire. - -Le seul moyen d'éviter ce problème consiste à -passer en FAT32 ou NTFS. Ces systèmes sont plus récents et n'ont pas -l'inconvénient de FAT. La taille des clusters par défaut y est de 4~ko, -leur accès est plus performant. NTFS est protégé, redondant et on peut -même ajuster la taille des clusters jusqu'à un minimum de 512 octets -à la création. - -\subsubsection{Comment ajouter un répertoire à votre PATH} - -Il existe dans votre système des variables qui -agissent un peu comme des variables globales à tous vos programmes. On -appelle cet ensemble de variables \emph{l'environnement}. Chaque -programme hérite à son démarrage d'une copie de l'environnement. Il peut -modifier les valeurs des variables, ajouter ou enlever des variables, -mais les modifications ne sont effectives que pour sa propre copie et -ne sont pas propagées aux autres programmes, sauf à ceux qu'il lance -lui-même. - -Votre variable PATH est une variable spéciale de l'environnement -utilisée pour chercher les programmes lorsque vous en demandez -l'exécution. Il y a une procédure différente pour modifier cette -variable selon que vous êtes sous Windows~9x, \acro{ME} ou -\acro{NT}/\acro{2K}/\acro{XP}. - -\begin{description} -\item[Windows 95/98] -Éditez votre fichier \path{autoexec.bat}. Dans ce fichier, vous -trouverez une ligne commençant par \path{PATH=} et suivie par une -liste de répertoires séparés par des points-virgules. Ajoutez le répertoire -contenant les programmes exécutables au bout de cette ligne. Cette -ligne ressemble alors à la suivante : -\begin{verbatim} -PATH=C:\windows;C:\windows\system;C:\TeXLive2007\bin\win32 -\end{verbatim} -Les modifications ne prendront effet qu'après redémarrage de la machine. -\item[Windows ME] - Vous devez utiliser le programme - \path{C:\string\windows\string\system\string\msconfig.exe} pour pouvoir - modifier une des - variables d'environnement. Dans ce programme, choisissez l'onglet - Environnement, ensuite ajoutez ou modifiez la variable de votre - choix. Il faut alors redémarrer la machine pour que les modifications - prennent effet. -\item[Windows NT/2K/XP] - Ouvrez le \guiseq{Panneau~de~Contrôle}, accessible depuis le menu - \guiseq{Démarrer\arw} \guiseq{Paramètres\arw Panneau~de~Contrôle}. - Ouvrez l'icône Système, la fenêtre des \guiseq{Propriétés système} - s'ouvre. Choisissez l'onglet \textsf{Environnement} ou cherchez un - bouton \guiseq{Variables d'environnement} -parmi les différentes boîtes de dialogue offertes. -Vous pouvez maintenant modifier vos propres variables d'environnement. -Il est à noter que les variables d'environnement système communes à -tous les utilisateurs sont également affichées. Vous ne pouvez les -modifier que si vous avez les droits d'administrateur. Si c'est le -cas, vous pouvez modifier la variable \path{PATH} pour tous les -utilisateurs du système -- mais vous devez savoir précisément ce que -vous faites. - -S'il y a déjà un \path{PATH} défini pour votre compte utilisateur, cliquez -dessus. Dans le champ \textsf{Variable} apparaît \path{PATH} et dans le champ -\textsf{Valeur}, la liste courante de répertoires séparés par des -points-virgules. Ajoutez les répertoires où se trouvent vos exécutables (i.e. -\path{C:\string\TeXLive2007\string\bin\string\win32}). Si la variable -\path{PATH} n'est pas encore définie, il suffit de taper son nom dans le champ -\textsf{Variable} et la valeur initiale que vous souhaitez lui donner dans le -champ \textsf{Valeur}. Important : cliquez sur le bouton \textsf{Appliquer} -avant de cliquer sur \textsf{Ok}, de cette façon, les modifications seront -propagées immédiatement à la session courante. Soyez prudent quand vous -modifiez les variables d'environnement. -\end{description} - -Le meilleur moyen de savoir si une variable a été correctement définie -consiste à ouvrir une console et à taper -\begin{verbatim} -set VARIABLE -\end{verbatim} -la valeur correspondante doit alors être affichée.. - -\subsubsection{Les moteurs \TeX{}} - -En lisant la documentation de \Webc{}, on voit -que les différents programmes dérivés de \TeX{} -utilisent le même moteur de base. Par exemple, \path{tex.exe} et -\path{latex.exe} sont des copies exactes du même programme, mais -chacun utilise un fichier de format différent, en se basant sur le nom -par lequel il a été invoqué. - -Sous Unix, ce mode de fonctionnement est réalisé en faisant appel aux -\emph{liens symboliques}. On peut ainsi économiser un peu d'espace disque, -car plusieurs moteurs de base sont utilisés avec différents fichiers -de format. - -L'API Win32 ne connaît pas les liens symboliques. Dans le but -d'économiser presqu'autant d'espace disque, tous les moteurs -\TeX{} de base ont été mis dans des DLL (\emph{Dynamic Linked - Library}). Ceci se traduit par l'aspect suivant pour les fichiers : -\begin{alltt} - 2006-11-23 07:06 2 560 latex.exe - 2007-01-06 23:54 1 073 664 pdftex.dll - 2006-01-28 08:05 2 560 pdftex.exe -\end{alltt} -\noindent et le fichier \path{latex.exe} n'est ni plus ni moins qu'une copie -presqu'identique du fichier \path{pdfetex.exe}, utilisant le même moteur -\path{pdftex.dll}. La même astuce a été utilisée pour la famille de -programmes \path{mktex*.exe} qui utilisent tous la bibliothèque -\path{mktex.dll}. - -Il existe même un outil générique appelé \path{irun.exe} qui permet -de simuler les liens durs de Unix sous Win32, mais uniquement pour les -fichiers \file{.exe}. - -\subsection{En cas de problème} -\label{sec:troubleshooting} - -\subsubsection{Que faire si \texttt{latex} ne trouve pas vos fichiers ?} - -\begin{itemize} -\item \cmdname{kpsewhich} est l'outil de choix pour trouver la source - de n'importe quel problème. Malheureusement, \cmdname{kpsewhich} - écrit le résultat de ses recherches sur le flux \path{stderr}, et - les anciennes versions de la console de Windows ne savaient pas - rediriger ce flux vers un fichier\footnote{En fait, les systèmes - Windows NT/2K/XP savent le faire, grâce à leur nouvel interpréteur - de commandes, mais l'astuce spécifique à \KPS{}-Win32 fonctionne - sur toutes les consoles.}. Pour des besoins de diagnostic, vous - pouvez positionner temporairement une variable d'environnement en tapant - dans une console : -\begin{verbatim} -SET KPATHSEA_DEBUG_OUTPUT=err.log -\end{verbatim} -Vous pouvez également définir un niveau de trace : -\begin{verbatim} -SET KPATHSEA_DEBUG=-1 -\end{verbatim} - -La trace de l'exécution des commandes suivantes sera conservée dans le -fichier \filename{err.log}. Si vous voulez rediriger le flux stderr sur le -flux stdout, ce qui n'est normalement possible sous aucune version de Windows, -il vous suffit de faire : -\begin{verbatim} -SET KPATHSEA_DEBUG_OUTPUT=con: -\end{verbatim} -De cette manière, vous pourrez rediriger à la fois stdout et stderr -dans le même fichier. - -\item En supposant que l'installation a été faite dans - \texttt{C:/TeX}, vérifiez les valeurs suivantes :\\ - \begin{tabular}{ll} - \texttt{kpsewhich -expand-path \$SELFAUTOPARENT} & \texttt{C:/TeX} \\ - \texttt{kpsewhich -expand-path \$TEXMF} & \texttt{C:/TeX/texmf....} \\ - \texttt{kpsewhich -expand-path \$TEXMFCNF} & - \texttt{.;C:/TeX/texmf-var/web2c;} \\ - \texttt{kpsewhich -expand-var \$TEXINPUTS} & \texttt{.;C:/TeX/texmf/tex//} - \end{tabular} - -\item Si des variables d'environnement liées à TeX sont - positionnées dans votre environnement, enlevez-les, car elles - masquent les valeurs existant dans le fichier \filename{texmf.cnf}. - -\item Vérifiez les valeurs de :\\ - \begin{tabular}{ll} - \texttt{kpsewhich cmr10.tfm} & \texttt{C:/TeX/texmf-dist/fonts/tfm/public/cm/cmr10.tfm}\\ - \texttt{kpsewhich latex.fmt}& \texttt{C:/TeX/texmf-var/web2c/latex.fmt} - \end{tabular} - -\item à ce point, si tout est correct, \TeX{} et tous les - programmes associés doivent fonctionner. Si ce n'est pas le cas, - vous devez poursuivre vos investigations avec l'option \path{-debug=n} de - \path{kpsewhich} et contrôler toutes les valeurs. Essayez - d'identifier et de signaler le problème. -\end{itemize} - -\subsubsection{Que faire si votre installation ne fonctionne toujours - pas selon vos attentes ?} - -Il faut se poser plusieurs questions : -\begin{enumerate} -\item Est-ce que \path{tex.exe} est bien dans mon \path{PATH} ? - -\item Est-ce que la variable d'environnement \path{TEXMFCNF} est bien - positionnée à \\ - \path{C:/TeXLive2007/texmf-var/web2c} (valeur par défaut) ? - -\item Est-ce qu'il y a des erreurs dans le fichier de log \file{tlmpgui.log} - généré lors de l'installation par \filename{tlmpgui} ? Ce fichier est dans - le répertoire \file{TEMP}, les erreurs sont repérées par la séquence - \samp{Error}. - -\item Y a-t-il des correctifs de bogues correspondant au problème à - \url{http://www.tug.org/tex-live.html} (improbable, mais il vaut - mieux le vérifier). - -\end{enumerate} - -Le logiciel \TL{} est composé de centaines de -programmes et de milliers de fichiers d'origines très diverses. Il -est pratiquement impossible de prédire toutes les causes possibles de -problèmes. Néanmoins, nous ferons notre possible pour vous aider dans -tous les cas (voir section~\ref{sec:help}, \p.\pageref{sec:help}). - -% don't use \Webc so the \uppercase in the headline works. -%\section{Guide d'utilisation du système \protect\Webc{}} -\section{Guide d'utilisation du système Web2C} - -\Webc{}est une collection intégrée de programmes relatifs à \TeX, -c.-à-d. \TeX{} lui-même, \MF{}, \MP, \BibTeX{}, etc. -C'est le c\oe ur de \TL{}. - -Un peu d'histoire : la première implémentation a été réalisée par Tomas -Rokicki qui, en 1987, a développé un premier système \TeX{}-to-C en adaptant -les \textit{change files} pour Unix (travail de Howard Trickey et Pavel Curtis -principalement). Tim Morgan assura la maintenance du système, dont le nom fut -remplacé durant cette période par Web-to-C. En 1990, Karl Berry reprit le -travail, assisté par des dizaines de contributeurs, et en 1997 il passa le -relais à Olaf Weber. - -Le système \Webc{} fonctionne sur Unix, les systèmes Windows 32 bits, -\MacOSX{} et de nombreux autres systèmes d'exploitation. Il utilise les -sources originales de D.E.~Knuth pour \TeX{} et les autres programmes de base -écrits en \web{} qui sont tous traduits en langage C. Les composants du noyau -de \TeX{} sont : - -\begin{description} -%\renewcommand{\makelabel}[1]{\descriptionlabel{\makebox[0.6in][l]{#1}}} -\item[bibtex] Gère les bibliographies. -\item[dmp] \cmdname{troff} vers MPX (dessins \MP{}). -\item[dvicopy] Copie le fichier \dvi{} en supprimant les fontes -virtuelles. -\item[dvitomp] Convertit le fichier \dvi{} en MPX (dessins \MP{}). -\item[dvitype] Convertit le fichier \dvi{} en un texte lisible. -\item[gftodvi] Visualisation de fontes génériques GF. -\item[gftopk] Convertit les fontes génériques GF en fontes bitmap PK. -\item[gftype] Convertit le fichier GF en un texte lisible. -\item[makempx] Typographie des étiquettes \MP{}. -\item[mf] Création de fontes. -\item[mft] Mise en page de code source \MF{}. -\item[mpost] Création de diagrammes techniques. -\item[mpto] Extraction d'étiquettes \MP{}. -\item[newer] Comparaison de dates de modification (fichiers). -\item[patgen] Création de motifs de césure. -\item[pktogf] Convertit les fontes bitmap PK en fontes génériques GF. -\item[pktype] Convertit les fontes PK en un texte lisible. -\item[pltotf] Convertit les fichiers PL (lisibles) en TFM. -\item[pooltype] Affiche les fichiers \web{} pool. -\item[tangle] \web{} vers Pascal. -\item[tex] Composition de textes. -\item[tftopl] Convertit les fichiers TFM en PL (lisibles). -\item[vftovp] Convertit les fontes virtuelles VF en VPL (lisibles). -\item[vptovf] Convertit les fontes VPL en fontes virtuelles VF. -\item[weave] \web{} vers \TeX. -\end{description} - -La syntaxe et les fonctions précises de ces programmes sont décrites -dans -la documentation des composants individuels et dans le manuel \Webc{} -lui-même. Toutefois, connaître un certain nombre de principes -régissant -l'ensemble de la famille de programmes peut aider à exploiter de -façon -optimale votre installation \Webc{}. - - Presque tous ces programmes suivent les -options standard de \acro{GNU} : -\begin{description} -%\renewcommand{\descriptionlabel}[1]{\makebox[1.4in][l]{#1}} - \item[\texttt{-{}-help}] imprime le sommaire de l'utilisation, - \item[\texttt{-{}-verbose}] imprime le rapport détaillé du processus, - \item[\texttt{-{}-version}] imprime seulement le numéro de version. -\end{description} - -Pour localiser les fichiers, les programmes \Webc{} utilisent la -bibliothèque de recherche \KPS{}. Cette bibliothèque utilise une -combinaison de -variables d'environnement et un certain nombre de fichiers de -paramètres pour optimiser la recherche dans l'énorme arborescence -\TeX{}. -\Webc{} peut exécuter une recherche dans plusieurs arborescences -simultanément, ce qui est utile si l'on souhaite maintenir la -distribution standard de \TeX{} et les extensions locales dans deux -arborescences distinctes. Afin d'accélérer la recherche de fichiers, la -racine de chaque arborescence possède un fichier \file{ls-R} contenant -une -entrée donnant le nom et le chemin de chaque fichier situé sous la -racine. - -\subsection{Kpathsea et la recherche de fichiers} - -Décrivons en premier lieu le mécanisme de recherche de la bibliothèque -\KPS{}. - -Nous appelons \emph{chemin de recherche} une liste, séparée par -\og deux-points\fg{} ou \og point-virgule\fg{}, d'éléments, appelés -\emph{éléments de chemin}, qui sont des noms de répertoires. -Un chemin de recherche peut provenir de plusieurs sources. -Pour rechercher un fichier \samp{my-file} le long -d'un chemin \samp{.:/dir}, \KPS{} vérifie chaque élément du -chemin : -d'abord \filename{./my-file}, puis \filename{/dir/my-file}, et renvoie la -première occurrence (voire toutes). - -Afin d'optimiser l'adaptation à tous les systèmes d'exploitation, -\KPS{} peut utiliser dans les noms de fichiers des séparateurs -différents -de deux-points (\samp{:}) et barre oblique (\samp{/}) - pour les systèmes non-Unix. - -Pour vérifier un élément de chemin particulier \var{p}, \KPS{} -vérifie d'abord si une base de données existante (voir -page~\pageref{Filename-database}) contient \var{p}, -c.-à-d. si la base de données se trouve dans un -répertoire qui est un préfixe de \var{p}. Si oui, la spécification -du chemin est comparée avec le contenu de la base de données. - -Si la base de données n'existe pas, si elle ne s'applique pas à cet -élément de chemin ou si elle ne contient aucune correspondance, -la recherche est lancée sur tout le système de fichiers (si cela -n'a -pas été interdit -par une commande commençant par \samp{!!} - et si le fichier cherché est censé exister). -\KPS{} construit la liste de répertoires qui correspondent -à cet élément de chemin, puis cherche le fichier dans chaque -élément -de cette liste. - -La condition \og le fichier est censé exister\fg{} est liée aux -fichiers~\samp{.vf} et aux fichiers d'entrée lus par la commande \TeX\ -\cs{openin}. -De tels fichiers peuvent ne pas exister (par exemple \file{cmr10.vf}), -il -est donc inutile de les rechercher sur le disque. De plus, si vous -n'actualisez pas le fichier \file{ls-R} lors de l'installation d'un -nouveau fichier -\samp{.vf}, -il ne sera jamais trouvé. -Chaque élément de chemin est alors vérifié : d'abord dans -la base de données puis sur le disque. Si une occurrence est -trouvée, la recherche s'arrête et le résultat est obtenu. - -Bien que l'élément de chemin le plus simple et le plus fréquent -soit un -nom de répertoire, \KPS{} supporte d'autres types d'éléments dans -les -chemins de recherche : des valeurs par défaut différentes pour chaque -programme, des noms de variables d'environnement, des valeurs de -fichiers de -configuration, les répertoires de l'utilisateur et la recherche -récursive -de sous-répertoires. Nous disons alors que \KPS{} \emph{étend} un -élément, c'est-à-dire que \KPS{} transforme toutes ces -spécifications -en noms de répertoires de base. Cette opération est décrite dans les sections -suivantes. - -Notons que si le nom de fichier cherché est absolu ou explicitement -relatif, c'est-à-dire commençant par \samp{/}, \samp{./} ou -\samp{../}, \KPS{} ne vérifie que l'existence de ce fichier. -\ifSingleColumn -\else -\begin{figure*} -\verbatiminput{examples/ex5.tex} -\setlength{\abovecaptionskip}{0pt} - \caption{Un exemple de fichier de configuration} - \label{fig:config-sample} -\end{figure*} -\fi - -\subsubsection{Les différentes sources} -\label{Path-sources} - -Un chemin de recherche peut provenir de plusieurs sources. Voici l'ordre -dans lequel \KPS\ les utilise. - -\begin{enumerate} -\item - Une variable d'environnement définie par l'utilisateur, par exemple - \envname{TEXINPUTS}. Les variables d'environnement avec une - extension attachée (nom de programme) sont d'abord prises en compte : - par exemple, si \samp{latex} est le nom du programme exécuté, - \envname{TEXINPUTS.latex} passera avant \envname{TEXINPUTS}. -\item - Un fichier de configuration de programme spécifique, par exemple une -ligne - \og \texttt{S /a:/b}\fg{} dans le fichier \file{config.ps} de \cmdname{dvips}. -\item - Un fichier de configuration \file{texmf.cnf} de \KPS{} contenant une - ligne telle que \\ \samp{TEXINPUTS=/c:/d} (voir ci-dessous). -\item La valeur par défaut obtenue à la compilation. -\end{enumerate} -\noindent On peut voir chacune de ces valeurs pour un chemin de -recherche -donné en utilisant l'option de débogage (voir page~\pageref{Debugging}). - -\subsubsection{Fichiers de configuration} - -\begingroup\tolerance=3500 -\KPS{} lit dans les \emph{fichiers de configuration à - l'exécution} appelés \file{texmf.cnf} les chemins de recherche et -d'autres définitions. Le chemin pour accéder à ces fichiers dans -l'arborescence est stocké dans la variable \envname{TEXMFCNF} -(par défaut ces -fichiers se trouvent dans le sous-répertoire \file{texmf/web2c}). -\emph{Tous} les fichiers \file{texmf.cnf} se trouvant dans le chemin -de recherche vont être lus et les définitions provenant -de fichiers précédents écraseront celles des fichiers suivants. Par -exemple, avec un chemin tel que \verb|.:$TEXMF|, les définitions du -fichier \filename{./texmf.cnf} écrasent celles de -\verb|$TEXMF/texmf.cnf|. -\endgroup - -\begin{itemize} -\item - Les commentaires sont signalés par un \texttt{\%} et - se terminent à la fin de la ligne. -\item - Les lignes vides sont ignorées. -\item - Un \bs{} à la fin d'une ligne joue le rôle d'un lien entre deux - lignes, c'est-à-dire que la ligne courante se poursuit à la ligne - suivante. Dans ce cas, les espaces présents au début de la ligne - suivante ne sont pas ignorés. -\item - Toutes les autres lignes sont de la forme : -\begin{alltt} - \emph{variable}[.\emph{progname}] [=] \emph{value} -\end{alltt}% - où le \samp{=} et les espaces autour sont optionnels. -\item - Le nom de la \ttvar{variable} peut contenir n'importe - quel caractère autre que les espaces, \samp{=}, ou \samp{.}, mais - on recommande d'utiliser \samp{A-Za-z\_} pour éviter les - problèmes. -\item - Si \samp{.\var{progname}} est présent, sa définition - s'applique seulement si le programme exécuté se nomme - \texttt{\var{progname}} ou \texttt{\var{progname}.exe}. Ceci permet - par exemple à différentes variantes de \TeX{} d'avoir des chemins de - recherche différents. -\item - \var{value} peut contenir n'importe quel caractère - excepté \code{\%} et \samp{@}. - L'option - \code{\$\var{var}.\var{prog}} - n'est pas disponible à droite du signe \samp{=} ; - à la place, on doit utiliser une variable supplémentaire. Un -\samp{;}\ dans \var{value} -est compris comme un - \samp{:}\ si on travaille sous Unix ; ceci est très utile et - permet d'avoir un seul \file{texmf.cnf} pour les systèmes Unix, - \acro{MS-DOS} et Windows. -\item - Toutes les définitions sont lues avant tout désarchivage ou - décompactage, de telle façon que les variables peuvent être - référencées avant d'être définies. -\end{itemize} -Voici un fichier de configuration illustrant les points -précédents -\ifSingleColumn - -%\verbatiminput{examples/ex5.tex} % trop petit (df) -\begin{verbatim} -TEXMF = {$TEXMFLOCAL,!!$TEXMFMAIN} -TEXINPUTS.latex = .;$TEXMF/tex/{latex,generic;}// -TEXINPUTS.fontinst = .;$TEXMF/tex//;$TEXMF/fonts/afm// -% e-TeX related files -TEXINPUTS.elatex = .;$TEXMF/{etex,tex}/{latex,generic;}// -TEXINPUTS.etex = .;$TEXMF/{etex,tex}/{eplain,plain,generic;}// -\end{verbatim} - -\else -dans la figure~\ref{fig:config-sample}. -\fi - -\subsubsection{Expansion d'un chemin de recherche} -\label{Path-expansion} - -\KPS{} reconnaît certains caractères et constructions spéciales dans -les chemins de recherche, semblables à ceux disponibles dans les -\textit{shells} Unix. Ainsi, le chemin complexe, -\verb+~$USER/{foo,bar}//baz+ %$ -étend la recherche vers tous les sous-répertoires situés sous les -répertoires \file{foo} et \file{bar} dans le répertoire utilisateur -\texttt{\$USER} contenant un répertoire ou un fichier appelé %$ -\file{baz}. Ces expansions sont explicitées dans les sections -suivantes. - -\subsubsection{Expansion par défaut} -\label{Default-expansion} - -\tolerance=2500 -Si le chemin de recherche le plus prioritaire (voir -section~\ref{Path-sources}) contient un \samp{:} -\emph{supplémentaire} (c.-à-d. en début ou fin de ligne ou -double), \KPS{} insère à cet endroit le chemin suivant dont la -priorité définie est immédiatement inférieure. Si ce chemin inséré -possède un \samp{:} supplémentaire, le même processus se -répète pour le chemin prioritaire suivant. -Par exemple, étant donné une variable d'environnement définie ainsi - -\tolerance=1500 - -\begin{alltt} -> \Ucom{setenv TEXINPUTS /home/karl:} -\end{alltt} -la valeur de \code{TEXINPUTS} d'après le fichier \file{texmf.cnf} étant - -\begin{alltt} - .:\$TEXMF//tex -\end{alltt} -alors la valeur finale utilisée pour la recherche sera - -\begin{alltt} - /home/karl:.:\$TEXMF//tex -\end{alltt} - -Comme il est inutile d'insérer la valeur par défaut en plusieurs -endroits, \KPS{} applique la substitution à seulement un \samp{:} -supplémentaire et laisse les autres inchangés : il cherche d'abord un -\samp{:} en début de ligne, puis en fin de ligne et enfin un double -\samp{:}. - -\subsubsection{Expansion spécifiée par les accolades} - -Option utile, l'expansion par le biais des accolades -signifie, par exemple, que \verb+v{a,b}w+ va permettre la recherche -dans \verb+vaw:vbw+. Les définitions emboîtées sont autorisées. Ceci -peut être utilisé pour établir des hiérarchies \TeX{} multiples en -attribuant une liste entre accolades à \code{\$TEXMF}. Par exemple, -dans \file{texmf.cnf}, on trouve une définition du type suivant -(il y a en fait plus de répertoires) : -\begin{verbatim} - TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFSYSVAR,!!$TEXMFMAIN} -\end{verbatim} -Avec ceci, on peut écrire quelque chose comme -\begin{verbatim} - TEXINPUTS = .;$TEXMF/tex// -\end{verbatim} -%$ -ce qui signifie que, après avoir cherché dans le répertoire courant, les -arborescences complètes \code{\$TEXMFHOME/tex} suivie de -\code{\$TEXMFLOCAL/tex} (sur le disque) et ensuite les arborescences -\code{!!\$TEXMFVAR/tex} et \code{!!\$TEXMFMAIN/tex} -(définies dans le fichier de référence \file{ls-R} \emph{seulement}) seront -inspectées. C'est un moyen pratique permettant d'utiliser en parallèle deux -distributions \TeX{}, une \og gelée\fg{} (sur un \CD, par exemple) et une -autre régulièrement mise à jour avec de nouvelles versions quand elles -deviennent disponibles. En utilisant la variable \code{\$TEXMF} dans toutes -les définitions, on est toujours sûr d'inspecter d'abord l'arborescence la -plus récente. - -\subsubsection{Expansion des sous-répertoires} -\label{Subdirectory-expansion} - -Deux barres \samp{//} ou plus consécutives dans une partie d'un chemin suivant -un répertoire \var{d} sont remplacées par tous les sous-répertoires de -\var{d} : d'abord les sous-répertoires directement présents dans -\var{d}, ensuite les sous-répertoires de ceux-ci, et ainsi de suite. À -chaque niveau, l'ordre dans lequel les répertoires sont inspectés est -\emph{non-déterminé}. - -Dans le cas où l'on spécifie une partie de nom de fichier après le -\samp{//}, seuls sont inclus les sous-répertoires auxquels le nom -correspond. Par exemple, \samp{/a//b} va correspondre aux répertoires -\file{/a/1/b}, \file{/a/2/b}, -\file{/a/1/1/b}, et ainsi de suite, mais pas à \file{/a/b/c} ni -\file{/a/1}. - -Des \samp{//} multiples et successifs dans un chemin sont possibles, -mais \samp{//} au début d'un chemin est ignoré. - -\subsubsection{Liste des caractères spéciaux et de leur signification : - récapitulatif} - -La liste suivante récapitule la signification des caractères spéciaux -dans les fichiers de configuration de \KPS{}. - -\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} - -\begin{ttdescription} - -\item[\CODE{:}] Séparateur dans un chemin de recherche ; au début - ou à la fin d'un chemin, il remplace le chemin par défaut. - -\item[\CODE{;}] Séparateur dans les systèmes non-Unix - (joue le rôle de \code{:}). - -\item[\CODE{\$}] Substitue le contenu d'une variable. - -\item[\CODE{\string~}] Représente le répertoire racine de - l'utilisateur. - -\item[\CODE{\char`\{...\char`\}}] Expansion par les accolades, - par exemple \verb+a{1,2}b+ devient \verb+a1b:a2b+. - -\item[\CODE{//}] La recherche concernera aussi les sous-répertoires - (peut être inséré n'importe où dans un chemin sauf au début). - -\item[\CODE{\%}] Début d'un commentaire. - -\item[\CODE{\bs}] Caractère de continuation de ligne (permet les - entrées sur plusieurs lignes). - -\item[\CODE{!!}] Cherche \emph{seulement} dans la base de - données pour localiser le fichier et \emph{ne cherche pas} sur le disque. - -\end{ttdescription} - -\subsection{Les bases de données} -\label{Filename-database} - -\KPS{} a une certaine profondeur d'investigation pour minimiser les -accès disque durant les recherches. Néanmoins, dans le cas de -distributions comprenant beaucoup de répertoires, inspecter chaque -répertoire possible pour un fichier donné peut durer excessivement -longtemps (ceci est typiquement le cas quand plusieurs centaines de -répertoires de polices de caractères doivent être parcourus). En -conséquence, \KPS{} peut utiliser un fichier texte appelé \file{ls-R} --- en -fait une base de données -construite au préalable --- qui fait correspondre -les fichiers à leur répertoire, ce qui permet d'éviter une recherche -exhaustive sur le disque. - -Un deuxième fichier appelé \file{aliases} (qui est également une base de -données) permet de donner -des noms différents aux fichiers listés dans \mbox{\file{ls-R}}. Ceci peut -aider à adapter ses fichiers source aux conventions de \acro{DOS}~8.3 pour les -noms de fichiers. - -\subsubsection{Le fichier base de données} -\label{ls-R} - -Comme nous l'avons expliqué ci-dessus, le nom du principal fichier-base de -données doit être \mbox{\file{ls-R}}. -Dans votre installation, vous pouvez en mettre un à la racine de chaque -arborescence \TeX{} que vous désirez voir -inspecter (\code{\$TEXMF} par défaut) ; la plupart des sites ont -une seule arborescence \TeX{}. \KPS{} cherche les fichiers \file{ls-R} -dans le chemin spécifié dans la variable \code{TEXMFDBS}. - -La meilleure façon de créer et mettre à jour le fichier \file{ls-R} -est d'exécuter le script \cmdname{mktexlsr} inclus dans la -distribution. Il est appelé par les divers scripts \cmdname{mktex}\dots\ -En principe, ce script exécute uniquement la commande -%cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R| -% Remplacé (df) car \path|...| plante à cause de \let\path\url. -\begin{alltt} -cd \var{/your/texmf/root} && \boi{}ls -1LAR ./ >ls-R -\end{alltt} -en supposant que la commande \code{ls} de votre système produise le bon -format de sortie (le \code{ls} de \acro{GNU} convient -parfaitement). Pour s'assurer que la base de données est toujours à -jour, le meilleur moyen est de la reconstruire en utilisant la table -des \code{cron}, de telle façon que le fichier \file{ls-R} prenne -automatiquement en compte les changements dans les fichiers -installés, par exemple après une installation ou une -mise à jour d'un composant \LaTeX{}. - -Si un fichier n'est pas trouvé dans la base de données, par défaut -\KPS{} décide de le chercher sur le disque. Par contre, si un élément du -chemin commence par \samp{!!}, \emph{seule} la base de données -sera inspectée pour cet élément, jamais le disque. - -\subsubsection{kpsewhich : programme de recherche dans une arborescence} -\label{Invoking-kpsewhich} - -Le programme \texttt{kpsewhich} effectue une recherche dans une -arborescence indépendamment de toute application. On peut le -considérer comme une sorte de \code{find} pour localiser des fichiers -dans les arborescences \TeX{} (ceci est largement utilisé dans les -scripts \cmdname{mktex}\dots\ de la distribution). - -\begin{alltt} -> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} -\end{alltt} -Les options spécifiées dans \ttvar{option} peuvent -commencer soit par \samp{-} soit par \samp{-{}-} ; n'importe quelle -abréviation claire est acceptée. - -\KPS{} considère tout argument non optionnel dans la ligne de commande -comme un nom de fichier et renvoie la première occurrence trouvée. Il -n'y a pas d'option pour renvoyer tous les fichiers ayant un nom -particulier (vous pouvez utiliser le \cmdname{find} d'Unix pour cela). - -Les options les plus importantes sont décrites ci-après. - -\begin{ttdescription} -%\renewcommand{\makelabel}[1]{\descriptionlabel{\makebox[1.2in]{#1}}} -\item[\texttt{-{}-dpi=\var{num}}]\mbox{} \\ - Définit la résolution à \ttvar{num} ; ceci affecte - seulement la recherche des fichiers \samp{gf} et \samp{pk}. \samp{-D} est un - synonyme pour assurer la compatibilité avec \cmdname{dvips}. Le défaut - est 600. -\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ - Définit le format pour la recherche à \ttvar{name}. - Par défaut, le format est estimé en fonction du nom de fichier. - Pour les formats qui n'ont pas de suffixe clair associé, comme les - fichiers de support \MP{} et les fichiers de configuration - \cmdname{dvips}, vous devez spécifier le nom connu de \KPS, comme - \texttt{tex} ou \texttt{enc files}. Exécutez la commande - \texttt{kpsewhich -{}-help} pour obtenir la liste précise. - -\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ - Définit le nom du mode comme étant \ttvar{string} ; -ceci affecte seulement la recherche des \samp{gf} et des \samp{pk}. -Pas d'option par défaut, n'importe quel mode sera trouvé. -\item[\texttt{-{}-must-exist}]\mbox{}\\ - Fait tout ce qui est possible pour trouver les fichiers, ce qui -inclut une recherche sur le disque. Par défaut, seule la base de -données \file{ls-R} est inspectée, dans un souci d'efficacité. -\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ - Recherche dans le chemin \ttvar{string} (séparé par -deux-points comme d'habitude), au lieu de prendre le chemin à partir -du nom de fichier. \samp{//} et toutes les expansions habituelles sont -supportées. - Les options \samp{-{}-path} et \samp{-{}-format} s'excluent mutuellement. -\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ - Définit le nom de programme comme étant \ttvar{name}. - Ceci peut affecter les chemins de recherche via l'option - \texttt{.\var{progname}} dans les fichiers de configuration. - Le défaut est \cmdname{kpsewhich}. -\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ - Montre le chemin utilisé pour la recherche des fichiers de type -\ttvar{name}. - On peut utiliser soit une extension de fichier (\code{.pk}, \code{.vf}, - etc.), soit un nom de fichier, comme avec l'option \samp{-{}-format}. -\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ - Définit les options de débogage comme étant - \ttvar{num}. -\end{ttdescription} - -\subsubsection{Exemples d'utilisation} -\label{SExamplesofuse} - -Jetons un coup d'{\oe}il à \KPS{} en action ; voici une recherche -toute simple : - -\begin{alltt} -> \Ucom{kpsewhich article.cls} -/usr/local/texmf-dist/tex/latex/base/article.cls -\end{alltt} -Nous recherchons le fichier \file{article.cls}. Puisque le suffixe -\file{.cls} est non-ambigu, nous n'avons pas besoin de spécifier que -nous voulons rechercher un fichier de type \optname{tex} (répertoires des -fichiers sources de \TeX{}). Nous le trouvons dans le sous-répertoire -\filename{tex/latex/base} du répertoire racine \samp{TEXMF}. De même, - le suffixe non-ambigu permet de trouver facilement les autres fichiers. -\begin{alltt} -> \Ucom{kpsewhich array.sty} - /usr/local/texmf-dist/tex/latex/tools/array.sty -> \Ucom{kpsewhich latin1.def} - /usr/local/texmf-dist/tex/latex/base/latin1.def -> \Ucom{kpsewhich size10.clo} - /usr/local/texmf-dist/tex/latex/base/size10.clo -> \Ucom{kpsewhich small2e.tex} - /usr/local/texmf-dist/tex/latex/base/small2e.tex -> \Ucom{kpsewhich tugboat.bib} - /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib -\end{alltt} - -Le dernier exemple est une base de données bibliographiques pour \BibTeX{} -servant aux articles de \textsl{TUGBoat}. - -\begin{alltt} -> \Ucom{kpsewhich cmr10.pk} -\end{alltt} -Les fichiers de glyphes de fontes bitmaps, de type -\file{.pk}, sont -utilisés pour l'affichage par des programmes comme \cmdname{dvips} et -\cmdname{xdvi}. Rien n'est renvoyé dans ce cas puisque il n'y a pas -de fichiers Computer Modern \file{.pk} pré-créés sur nos systèmes -(nous utilisons les versions type~1 du \TL{}). -\begin{alltt} -> \Ucom{kpsewhich wsuipa10.pk} -\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk -\else /usr/local/texmf-var/fonts/pk/ljfour/public/ -... wsuipa/wsuipa10.600pk -\fi\end{alltt} -Pour ces fontes (alphabet phonétique de l'université Washington), -nous avons dû créer les fichiers \file{.pk} et, puisque le mode \MF{} par -défaut sur notre installation est \texttt{ljfour} avec une résolution de -base de 600\dpi{} \textit{(dots per inch)}, cette instance est trouvée. -\begin{alltt} -> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} -\end{alltt} -Dans ce cas, lorsque l'on spécifie que nous recherchons une -résolution de 300\dpi{} (\texttt{-dpi=300}) nous voyons qu'aucune fonte -pour cette résolution n'est disponible dans le système. En fait, un -programme comme \cmdname{dvips} ou \cmdname{xdvi} ne s'en -préoccuperait pas et créerait les fichiers \file{.pk} à la -résolution demandée en utilisant le script \cmdname{mktexpk}. - -Intéressons-nous à présent aux fichiers d'en-tête et de configuration -pour \cmdname{dvips}. -Regardons en premier le fichier \file{tex.pro} communément utilisé -pour le support de \TeX{} avant de regarder le fichier -de configuration générique (\file{config.ps}) et la liste des fontes -\PS{} \file{psfonts.map}. Depuis l'édition 2004, les fichiers -\file{.map} et les fichiers de codage ont changé de place dans -l'arborescence \dirname{texmf}. Comme le suffixe \file{.ps} est -ambigu, nous devons spécifier quel type particulier du fichier -\texttt{config.ps} nous considérons (\optname{dvips config}). -\begin{alltt} -> \Ucom{kpsewhich tex.pro} - /usr/local/texmf/dvips/base/tex.pro -> \Ucom{kpsewhich -{}-format="dvips config" config.ps} - /usr/local/texmf-var/dvips/config/config.ps -> \Ucom{kpsewhich psfonts.map} - /usr/local/texmf-var/fonts/map/dvips/updmap/psfonts.map -\end{alltt} - -Regardons plus en détail les fichiers de support Times -\PS{} d'\acro{URW}. Leur nom standard dans le schéma de nommage des fontes -est \samp{utm}. Le premier fichier que nous voyons est le -fichier de configuration, qui contient le nom du fichier -de la liste : -\begin{alltt} -> \Ucom{kpsewhich -{}-format="dvips config" config.utm} - /usr/local/texmf-dist/dvips/psnfss/config.utm -\end{alltt} -Le contenu de ce fichier est -\begin{alltt} - p +utm.map -\end{alltt} -qui pointe vers le fichier \file{utm.map}, que nous cherchons à -localiser ensuite. -\begin{alltt} -> \Ucom{kpsewhich utm.map} - /usr/local/texmf-dist/fonts/map/dvips/times/utm.map -\end{alltt} -Ce fichier liste les noms des fichiers des -fontes \PS{} de type~1 dans la collection URW. Son contenu -ressemble à (nous ne montrons qu'une partie des lignes) : -\begin{alltt} -utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} -\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb -\else /usr/local/texmf-dist/fonts/type1/ -... urw/utm/utmr8a.pfb -\fi\end{alltt} - -Il devrait être clair, d'après ces quelques exemples, qu'il est facile -de trouver l'endroit où se cache un fichier donné. C'est -particulièrement important si vous suspectez que c'est, pour une -raison quelconque, une mauvaise version du fichier qui est utilisée, -puisque \cmdname{kpsewhich} va vous montrer le premier fichier -trouvé. - -\subsubsection{Opérations de débogage} -\label{Debugging} - -Il est quelquefois nécessaire de savoir comment un programme référence -les fichiers. Pour permettre cela, \KPS{} offre -plusieurs niveaux de débogage : -\begin{ttdescription} -\item[\texttt{\ 1}] Appels à \texttt{stat} (test d'existence de fichier). Lors d'une - exécution utilisant une base de données \file{ls-R} à jour, ce niveau - ne devrait donner presque aucune information en sortie. -\item[\texttt{\ 2}] Références aux différentes tables (comme la base - de données \file{ls-R}, les fichiers de correspondance de fontes, les fichiers de - configuration). -\item[\texttt{\ 4}] Opérations d'ouverture et de fermeture des - fichiers. -\item[\texttt{\ 8}] Information globale sur la localisation des types - de fichiers recherchés par \KPS. Ceci est utile pour trouver où a été - défini le chemin particulier pour un fichier. -\item[\texttt{16}] Liste des répertoires pour chaque élément du - chemin (utilisé uniquement en cas de recherche sur le disque). -\item[\texttt{32}] Recherche de fichiers. -\end{ttdescription} -Une valeur de \texttt{-1} activera toutes les options ci-dessus ; en -pratique, c'est habituellement la valeur la plus adaptée. - -De la même façon, avec le programme \cmdname{dvips}, en utilisant une -combinaison d'options de débogage, on peut suivre en détail la -localisation des -différents fichiers. De plus, lorsqu'un fichier n'est -pas trouvé, la trace du débogage montre les différents répertoires dans -lesquels le programme va chercher tel ou tel fichier, donnant ainsi -des indices sur le problème. - -Généralement, comme la plupart des programmes appellent la -bibliothèque \KPS{} en interne, on peut sélectionner une option de -débogage en utilisant la variable d'environnement -\envname{KPATHSEA\_DEBUG}, et en la définissant égale à la valeur (ou -à une combinaison de valeurs) décrite(s) dans la liste ci-dessus. - -Note à l'intention des utilisateurs de Windows : il n'est pas facile -de rediriger les messages d'erreur vers un fichier sur ces -systèmes. À des fins de diagnostic, vous pouvez temporairement -affecter \texttt{KPATHSEA\_DEBUG\_OUTPUT=err.log} pour capturer le flux -standard d'erreur dans le fichier \texttt{err.log}. - -Considérons comme exemple un petit fichier source \LaTeX{}, -\file{hello-world.tex}, dont le contenu est le suivant. -\begin{verbatim} - \documentclass{article} - \begin{document} - Hello World! - \end{document} -\end{verbatim} -Ce petit fichier utilise simplement la fonte \file{cmr10}, aussi -allons voir comment \cmdname{dvips} prépare le fichier \PS{} -(nous voulons utiliser la version type~1 -des fontes Computer Modern, d'où l'option \texttt{-Pcms}). -\begin{alltt} -> \Ucom{dvips -d4100 hello-world -Pcms -o} -\end{alltt} -Dans ce cas, nous avons combiné le niveau 4 de débogage de -\cmdname{dvips} (chemins des fontes) avec l'option d'expansion des -éléments du chemin de \KPS\ (voir \cmdname{dvips} Reference Manual, -\OnCD{texmf/doc/html/dvips/dvips_toc.html} sur le \DVDlive{}). -La sortie (légèrement formatée) apparaît dans la -figure~\ref{fig:dvipsdbga}. -\begin{figure*}[tp] -\centering -\input{examples/ex6a.tex} -\caption{Recherche des fichiers de configuration}\label{fig:dvipsdbga} - -\bigskip - -\input{examples/ex6b.tex} -\caption{Recherche du fichier prolog}\label{fig:dvipsdbgb} - -\bigskip - -\input{examples/ex6c.tex} -\caption{Recherche du fichier de fontes}\label{fig:dvipsdbgc} -\end{figure*} - -\cmdname{dvips} commence par localiser ses fichiers de -fonctionnement. D'abord, \file{texmf.cnf} est trouvé, ce qui donne les -définitions pour les chemins de recherche servant à localiser les -autres fichiers, ensuite le fichier base de données \file{ls-R} (pour -optimiser la recherche des fichiers) et le fichier \file{aliases}, qui -permet de déclarer plusieurs noms (\p.ex., un nom \acro{DOS} de type -8.3 court et une version longue plus naturelle) pour le même -fichier. Ensuite \cmdname{dvips} continue en cherchant le fichier de -configuration générique \file{config.ps} avant de rechercher le fichier -de paramétrisation \file{.dvipsrc} (qui, dans notre cas, \emph{n'est -pas trouvé}). Enfin, \cmdname{dvips} localise le fichier de -configuration pour les fontes \PS{} Computer Modern -\file{config.cms} (ceci est lancé par l'option \mbox{\texttt{-Pcms}} de la -commande \cmdname{dvips}). Ce fichier contient la liste des fichiers - qui définissent la relation entre les noms des fontes -selon \TeX{}, selon \PS{} et dans le système de fichiers. -\begin{alltt} -> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} - p +ams.map - p +cms.map - p +cmbkm.map - p +amsbkm.map -\end{alltt} -\cmdname{dvips} veut chercher tous ces fichiers, y compris le -fichier générique d'association \file{psfonts.map}, qui est toujours -chargé (il contient des déclarations pour les fontes \PS{} les -plus communément utilisées ; voir la dernière partie de la Section -\ref{SExamplesofuse} pour plus de détails sur la gestion du fichier -d'association \PS{}). - -Arrivé là, \cmdname{dvips} s'identifie à l'utilisateur : - \begin{alltt} - This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) - \end{alltt} - -\ifSingleColumn -pour continuer ensuite en cherchant le fichier prologue \file{texc.pro}, -\begin{alltt}\small -kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro -\end{alltt} -\else -pour continuer ensuite en cherchant le fichier prologue \file{texc.pro} -(voir la figure~\ref{fig:dvipsdbgb}). -\fi - -Après avoir trouvé ce fichier, \cmdname{dvips} affiche la date et -l'heure, et nous informe qu'il va générer le fichier -\file{hello-world.ps}, puis qu'il a besoin du fichier de fonte -\file{cmr10}, et que ce dernier est déclaré comme \og résident\fg{} -(pas besoin de bitmaps) : -\begin{alltt}\small -TeX output 1998.02.26:1204' -> hello-world.ps -Defining font () cmr10 at 10.0pt -Font cmr10 is resident. -\end{alltt} -Maintenant la recherche concerne le fichier \file{cmr10.tfm}, qui est -trouvé, puis quelques fichiers de prologue de plus (non montrés) sont -référencés ; finalement le fichier de la fonte type~1 \file{cmr10.pfb} -est localisé et inclus dans le fichier de sortie (voir la dernière ligne). -\begin{alltt}\small -kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, - path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: - /var/tex/fonts/tfm//). -kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm -kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, - ... - -kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb -[1] -\end{alltt} - -\subsection{Options à l'exécution} - -\Webc{} offre la possibilité de contrôler à l'exécution bon nombre de -paramètres concernant la mémoire (en particulier la taille des -tableaux utilisés) à partir du fichier -\file{texmf.cnf} qui est lu par \KPS. -Les paramètres en question se trouvent -dans la troisième partie du fichier inclus dans la distribution \TL{}. - Les variables les plus importantes sont : -\begin{ttdescription} -\item[\texttt{main\_memory}] - Nombre total de mots mémoire disponibles pour - \TeX{}, \MF{} et \MP. Vous devez générer un nouveau fichier de - format pour chaque nouveau paramétrage. Par exemple, vous pouvez - générer une version large de \TeX{} et appeler le fichier de format - \texttt{hugetex.fmt}. En utilisant la méthode supportée par \KPS{} - qui consiste à suffixer la variable par le nom du programme, la valeur - particulière de la variable \texttt{main\_memory} destinée à ce - fichier de format sera lue dans le fichier \file{texmf.cnf}. -\item[\texttt{extra\_mem\_bot}] - Espace supplémentaire pour certaines structures de données de \TeX{} : - boîtes, \textit{glue}, points d'arrêt\dots{} Surtout utile si vous utilisez - \PiCTeX{} par exemple. -\item[\texttt{font\_mem\_size}] - Nombre de mots mémoire disponibles pour décrire les polices. C'est - plus ou moins l'espace occupé par les fichiers TFM lus. -\item[\texttt{hash\_extra}] - Espace supplémentaire pour la table de hachage des noms de séquences - de contrôle. Environ 10~000 de ces noms peuvent être stockés dans la - table principale ; si vous avez un document très volumineux avec - beaucoup de références croisées, il se peut que ce ne soit pas - suffisant. La valeur par défaut \texttt{hash\_extra} est \texttt{50000}. -\end{ttdescription} - -\noindent Évidemment, cette possibilité ne remplace pas une véritable -allocation dynamique des tableaux et de la mémoire, mais puisque c'est -complexe à implémenter dans le présent source \TeX{}, ces paramètres lus -à l'exécution fournissent un compromis pratique qui procure une certaine -souplesse. - -%\begin{comment} (supprimé (df) 5/5/2006, mail à K.B. - -\section{Installation sur un nouveau système Unix} - -Si vous avez un système Unix ne correspondant à aucun des exécutables -fournis, il faut compiler vous-même \TeX{} et tous ses programmes -satellites à partir des sources. Cela n'est pas aussi difficile qu'il -y paraît. Tout ce dont vous aurez besoin est contenu dans le -répertoire \texttt{source} qui se trouve sur le \DVDlive. - -\subsection{Prérequis} - -Il faut au moins 400\,Mo d'espace sur disque pour compiler la -totalité de \TeX{} et des programmes associés. -Vous aurez aussi besoin d'un -compilateur C \acro{ANSI}, de l'utilitaire \cmdname{make}, -d'un générateur d'analyseur lexical et d'un générateur d'analyseur -syntaxique. Nous recommandons les versions \acro{GNU} des programmes suivants -(\cmdname{gcc}, \acro{GNU}\cmdname{make}, \cmdname{m4}, -\cmdname{flex}, \cmdname{bison}). Vous pouvez utiliser d'autres compilateurs C -et d'autres programmes \cmdname{make} si vous maîtrisez -correctement la programmation sous Unix pour résoudre les -problèmes éventuels. La commande \texttt{uname} doit renvoyer une valeur -raisonnable. - -\subsection{Configuration} - -Tout d'abord, effectuez l'installation normale de \TL{} sur le disque -dur (voir section~\ref{sec:unix-install-disk}, -\p.\pageref{sec:unix-install-disk}). Vous pouvez sauter l'installation de -tous les binaires précompilés. -Décompactez ensuite sur le disque le fichier -\file{source.tar.bz2} (archive compressée) trouvé dans -le répertoire \dirname{source} et placez-vous dans -le répertoire où vous avez transféré l'ensemble. -\begin{alltt} -> \Ucom{cd /tmp/tl-source} -> \Ucom{bunzip2 source.tar.bz2} -> \Ucom{tar xf source.tar} -\end{alltt} - -Lancez maintenant \textsf{configure} de la façon suivante : -\begin{alltt} -> \Ucom{sh configure -prefix=/usr/local/texlive/2007} -\end{alltt} - -Le répertoire \optname{-prefix} est le répertoire de base de -l'arborescence \TL{}, il est désigné par \var{TEXDIR} dans la suite. -\begin{comment} -Les répertoires utilisés sont les suivants : - -\noindent -\begin{tabular}{>{\ttfamily}ll@{}} - \dirname{$TEXDIR/texmf-dist} & répertoire de base pour les fontes, - macros, etc\\ - \dirname{$TEXDIR/man} & pages du manuel Unix\\ - \dirname{$TEXDIR/info} & manuels \acro{GNU} en format Info\\ - \dirname{$TEXDIR/bin/$archname} & exécutables.\\ -\end{tabular}\\ -\end{comment} -%$ - -Si vous ne voulez pas créer de répertoire \dirname{$archname} spécifique %$ -au système choisi pour stocker les exécutables (c.-à-d. les -copier directement dans \dirname{$TEXDIR/bin}), %$ -il faut exécuter \textsf{configure} avec l'option \\ -\verb|--disable-multiplatform|. - -Tapez \verb|./configure --help|, le programme affichera -les options supplémentaires disponibles (telles que supprimer l'installation -des extensions optionnelles comme \OMEGA\ ou \eTeX). - -\subsection{Exécuter \textsf{make}} -S'assurer que la variable ou l'option \texttt{noclobber} n'est pas définie. - et lancer le \cmdname{make} à la racine de l'arborescence de la façon -suivante : -\begin{alltt} ->> \Ucom{make world} -\end{alltt} -et aller prendre un café\dots - -Il peut être utile de garder une trace complète dans un fichier log en tapant : -\begin{alltt} ->> \Ucom{sh -c "make world >world.log 2>\&1" \&} -\end{alltt} -Avant de conclure que tout va bien, vérifier que le fichier log ne contient -pas de message d'erreur : le \cmdname{make} de \acro{GNU} renvoie toujours -le message \samp{***} à chaque erreur d'exécution. Vérifier aussi que -tous les exécutables ont été créés. -\begin{alltt} ->> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} ->> \Ucom{ls | wc} -\end{alltt} -Le résultat doit être supérieur à 200 (on peut tester le nombre exact -dans le répertoire \dirname{bin} de la distribution). - -Si vous avez besoin de droits spéciaux pour exécuter \texttt{make install}, -vous pouvez séparer \samp{make world} en deux processus différents : -\begin{alltt} ->> \Ucom{make all} ->> \Ucom{su} ->> \Ucom{make install strip} -\end{alltt} - -Après avoir installé vos nouveaux binaires, il faut suivre les procédures -normales de la post-installation, indiquées dans la -section~\ref{sec:postinstall}, \p.\pageref{sec:postinstall}. - -%\end{comment} supprimé (df) 5/5/2006 - -\section{Remerciements} - -\TL{} est le résultat des efforts -collectifs de pratiquement tous les groupes d'utilisateurs de \TeX. -La présente édition de \TL{} a été coordonnée par -Sebastian Rahtz et Karl Berry. -Voici la liste des principaux contributeurs : - -\begin{itemize} - -\item Les associations d'utilisateurs anglais, allemands, néerlandais et - polonais (\acro{TUG}, \acro{DANTE} e.V., \acro{NTG}, and \acro{GUST}, - respectivement) qui contribuent ensemble à l'infrastructure technique et - administrative. Soutenez votre association locale (\acro{GUTenberg} pour - les francophones) ! - -\item L'équipe du \acro{CTAN} qui distribue les images des distributions \TL{} - et fournit les sites d'hébergement pour le stockage et la mise à jour des - extensions qui sont la base de \TL. - -\item Peter Breitenlohner et toute l'équipe \eTeX{} qui construisent - les bases des successeurs de \TeX. - -\item Thomas Esser, car, sans lui, sa merveilleuse distribution \teTeX{} et - son aide continuelle, \TL{} n'existerait probablement pas. - -\item Michel Goossens, en tant que co-auteur de la documentation initiale. - -\item Eitan Gurari, dont le programme \TeX4ht a été utilisé pour créer la - version \HTML{} de cette documentation et qui travailla inlassablement à - l'améliorer, avec des délais très brefs. - -\item Hans Hagen qui, outre sa participation active aux tests, - a adapté le format \ConTeXt\ aux besoins de \TL{}. - -\item \Thanh, Martin Schr\"oder et toute l'équipe pdf\TeX\ qui continuent - inlassablement à étendre les performances de \TeX. - -\item Taco Hoekwater, pour ses efforts sans cesse renouvelés à l'amélioration - de MetaPost et de \TeX\ lui-même. - -\item Pawe{\l} Jackowski, pour l'installeur Windows \cmdname{tlpm}, -et Tomasz {\L}uczak, pour la version graphique \cmdname{tlpmgui}. - -\item Akira Kakuto, pour son aide précieuse qui nous a permis - d'intégrer dans \TL{} les binaires Windows de sa distribution \acro{W32TEX} - (\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}). - -\item Jonathan Kew et son employeur \acro{SIL}, pour avoir produit - Xe\TeX{} et pour avoir pris la peine de l'intégrer dans \TL{}. - -\item Reinhard Kotucha, pour son aide dans la lourde tâche consistant à -mettre à jour les innombrables extensions incluses dans \TL{} et pour ses -contributions sous Windows en particulier le script \texttt{getnonfreefonts}. - -\item Petr Ol\v{s}ak, qui coordonna et vérifia minutieusement toute la - partie tchèque et slovaque. - -\item Toshio Oshima, pour le visualisateur \cmdname{dviout} pour Windows. - -\item Fabrice Popineau, pionnier du développement de \TL{} sous Windows. - -\item Norbert Preining, pour son aide à la mise à jour de \TL, ses nombreuses - suggestions d'amélioration et pour avoir coordonné (avec Frank K\"uster) la - version Debian de \TL. - -\item Staszek Wawrykiewicz, principal testeur de \TL{} et - coordinateur des contributions polonaises - (fontes, installation Windows, etc.). - -\item Olaf Weber, pour son patient assemblage et la maintenance de \Webc{} - sur laquelle tout repose. - -\item Gerben Wierda, qui a créé et maintient la partie \MacOSX{} - et qui participe activement aux tests. - -\item Graham Williams, du travail duquel dépend le catalogue des -composants. -\end{itemize} - -Les binaires ont été compilés par : -Hartmut Henkel (\pkgname{x86\_64-linux}), -Akira Kakuto et Fabrice Popineau (\pkgname{win32}), -Manfred Lotz (\pkgname{i386-freebsd}), -Norbert Preining (\pkgname{alpha-linux}), -Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-linux} - et \pkgname{sparc-solaris}), -Karl Berry (\pkgname{i386-linux}), -Olaf Weber (\pkgname{mips-irix}), -Gerben Wierda (\pkgname{i386-darwin}, \pkgname{powerpc-darwin}). - -Documentation et mises à jour des traductions : -Karl Berry (anglais), -G\"unter Partosch, Hartmut Henkel \& Klaus H\"oppner (allemand), -Daniel Flipo (français), -Petr Sojka \& Janka Chleb\'\i kov\'a (tchèque et slovaque), -Boris Veytsman (russe), -Staszek Wawrykiewicz (polonais). - -Bien sûr, notre gratitude va en premier lieu à Donald Knuth pour avoir -inventé \TeX{} et l'avoir offert au monde entier. - -\section{Historique des versions successives} -\label{sec:history} - -\subsection{Les éditions précédentes} - -La discussion commença à la fin de 1993 quand le Groupe des Utilisateurs -Néerlandais de \TeX{} commençait à travailler à son \CD{} 4All\TeX{} pour les -utilisateurs de \acro{MS-DOS}, et on espérait à ce moment sortir un \CD{} -unique pour tous les systèmes. C'était un objectif beaucoup trop ambitieux, -mais il permit la naissance du \CD{} 4All\TeX{}, projet couronné de succès, -mais aussi d'un groupe de travail \og \acro{TUG} Technical Council\fg{} pour -mettre en place TDS (\emph{\TeX{} Directory Structure} : -\url{http://tug.org/tds}), qui spécifiait la gestion des fichiers \TeX{} sous -une forme logique. La mouture finale de \TDS{} fut publiée dans le numéro de -décembre 1995 de \textsl{TUGboat}, et il était clair depuis un certain temps -qu'il fallait proposer un produit contenant une structure modèle sur \CD{}. -La distribution que vous possédez est le résultat direct des délibérations de -ce groupe de travail. Il était également clair que le succès des \CD{} -4All\TeX{} démontrait que les utilisateurs d'Unix trouveraient leur bonheur -avec une distribution aussi simple, et ceci a été l'autre objectif de -\TL. - -Nous avons d'abord entrepris de créer un nouveau \CD{} \TDS{} Unix à l'automne -1995, et nous avons rapidement choisi \teTeX{} de Thomas Esser comme étant la -configuration idéale, car il supportait déjà plusieurs plates-formes et avait -été construit en gardant à l'esprit la portabilité entre systèmes. Thomas -accepta de nous aider et commença à travailler sérieusement au début de 1996. -La première édition sortit en mai 1996. Au début de 1997, Karl Berry acheva -une nouvelle distribution de \Webc{}, qui incluait presque toutes les -caractéristiques que Thomas Esser avait ajoutées dans \teTeX, et il fut décidé -de baser la deuxième édition du \CD{} sur le standard \Webc, en y ajoutant le -script \texttt{texconfig} de \teTeX. La troisième édition du \CD{} était -basée sur une version majeure de \Webc, 7.2, par Olaf Weber ; en même temps, -une nouvelle version révisée de \teTeX{} était achevée dont \TL{} partageait -presque toutes les caractéristiques. La quatrième édition a suivi le même -schéma, en utilisant une nouvelle version de \teTeX{} et une nouvelle version -de \Webc{} (7.3). Le système incluait dorénavant un programme complet -d'installation pour Windows. - -Pour la cinquième édition (mars 2000), de nombreuses parties du \CD{} -ont été vérifiées et révisées, des centaines de composants -mis à jour. -Le contenu détaillé des composants était décrit par des -fichiers XML. Mais le changement majeur de cette cinquième édition a -été la suppression de tout logiciel non libre de droits. -Tout ce qui se trouve dans \TL{} devait être compatible avec la licence -Debian (\emph{Debian Free Software Guidelines} : -\url{http://www.debian.org/intro/free}) ; nous avons -fait de notre mieux pour vérifier les termes des licences de chaque -composant, et nous souhaiterions que toute erreur nous soit signalée. - -La sixième édition (juillet 2001) contient un grand nombre de mises à jour. -Le changement majeur de cette version réside dans la refonte du -processus d'installation : l'utilisateur peut désormais choisir -les collections de manière plus précise. Les collections concernant -les langues ont été entièrement réorganisées, aussi le choix d'une -langue installe non seulement les macros, les fontes, etc. mais -prépare également un fichier \file{language.dat} adéquat. - -La septième édition (mai 2002) a comme ajout majeur une installation -pour \MacOSX{} et l'habituelle myriade de mises à jour de composants et -de programmes. Un objectif important a été de fusionner à -nouveau les sources avec ceux de \teTeX{}, alors que les versions -5 et 6 s'en étaient éloignées. - -\subsubsection{2003} - -En 2003, le flot de mises à jour et d'additions a continué, mais nous -avons constaté que \TL{} était devenu si volumineux qu'il ne -pouvait plus tenir sur un seul \CD, aussi l'avons-nous divisé en trois -distributions distinctes (voir section~\ref{sec:multiple-dist}, -\p.\pageref{sec:multiple-dist}). Par ailleurs : -\begin{itemize} -\item À la demande de l'équipe \LaTeX{}, nous avons modifié les - commandes standard \cmdname{latex} et \cmdname{pdflatex} pour - qu'elles utilisent \eTeX{} (voir \p.\pageref{text:etex}). -\item Les nouvelles fontes Latin Modern sont disponibles (et - recommandées). -\item Le support pour Alpha \acro{OSF} a été supprimé - (celui pour \acro{HPUX} l'avait été auparavant), car personne - disposant des machines nécessaires ne s'est - proposé pour compiler les nouveaux binaires. -\item L'installation pour Windows a été largement modifiée ; un environnement - de travail intégré basé sur \cmdname{XEmacs} a été introduit. -\item Des programmes supplémentaires importants pour Windows (Perl, - Ghost\-script, Image\-Magick, Ispell) sont maintenant installés dans le - répertoire d'installation de \TL{}. -\item Les fichiers \emph{font map} utilisés par \cmdname{dvips}, - \cmdname{dvipdfm} et \cmdname{pdftex} sont maintenant générés par le - nouveau programme \cmdname{updmap} et installés dans - \dirname{texmf/fonts/map}. -\item Dorénavant, \TeX{}, \MF{} et \MP{} écrivent les caractères 8-bit - présentés en entrée sans modification, et non pas avec la notation - \verb|^^|, que ce soit dans des fichiers (par la commande - \verb|write|), dans les fichiers de trace (\verb|.log|) ou sur le - terminal. Dans le \TL{}~7, l'écriture de ces caractères - 8-bit était influencée par les paramètres de localisation du - système; maintenant ces paramètres n'influent plus du tout sur le - comportement des programmes \TeX{}. Si pour quelque raison que ce - soit, vous avez besoin de la notation \verb|^^| en sortie, - renommez le fichier \verb|texmf/web2c/cp8bit.tcx|. Les prochaines - versions disposeront d'un moyen plus propre pour contrôler cette - sortie. -\item La documentation de \TL{} a été largement révisée. -\item Enfin, comme la numérotation séquentielle des versions - devenait peu maniable, il a été décidé d'identifier désormais la version - de \TL{} par l'année : \TL{}~2003 au lieu de \TL{}~8. -\end{itemize} - - -\subsubsection{2004} - -2004 a apporté beaucoup de changements (et quelques incompatibilités avec les -versions précédentes) : - -\begin{itemize} - -\item Si vous avez installé des fontes supplémentaires qui ont leur propre -fichier \file{.map} ou des fichiers \file{.enc} spécifiques, vous -devrez vraisemblablement déplacer ces fichiers. - -Les fichiers \file{.map} sont désormais recherchés uniquement dans les -sous-répertoires \dirname{fonts/map} (dans chaque arborescence -\filename{texmf}), leur chemin de recherche est donné par la variable -\envname{TEXFONTMAPS} de \filename{texmf.cnf}. -De même, les fichiers \file{.enc} sont désormais recherchés uniquement -dans les sous-répertoires \dirname{fonts/enc}, leur chemin de recherche est -donné par la variable \envname{ENCFONTS} de \filename{texmf.cnf}. -Le script \cmdname{updmap} devrait émettre des messages d'avertissement -pour les fichiers \file{.map} et \file{.enc} mal placés. - -Sur les différentes façons de traiter le problème, consulter -\url{http://tug.org/texlive/mapenc.html}. - -\item La distribution pour Windows a changé cette année : -l'installation de la distribution \fpTeX{} (basée sur \Webc{}) de Fabrice -Popineau n'est provisoirement plus proposée dans l'attente -d'un nouvel installeur. À la place, vous pouvez tester et installer -la distribution \MIKTEX{} (indépendante de \Webc{}), -voir section~\ref{sec:struct-tl}, \p.\pageref{sec:struct-tl}. -Le \CDdemo{} diffusé en 2003 a été supprimé. - -\item L'ancien répertoire \dirname{texmf} a été éclaté en trois parties : -\dirname{texmf}, \dirname{texmf-dist} et \dirname{texmf-doc}. Voir -section~\ref{sec:tld}, \p.\pageref{sec:tld}. -% et les fichiers \filename{README} à la racine de ces répertoires. -% (df) Y'en a pas !!! - -\item Tous les fichiers relatifs aux différents avatars de \TeX{} sont -désormais regroupés dans le même sous-répertoire \dirname{tex} des -arborescences \dirname{texmf*} (ils étaient jusqu'ici placés dans des -sous-répertoires spécifiques \dirname{tex}, \dirname{etex}, -\dirname{pdftex}, \dirname{pdfetex}, etc.). Voir -\CDref{texmf-doc/doc/english/tds/tds.html\#Extensions} -{\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}. - -\item Les scripts auxiliaires, normalement pas exécutés directement -par les utilisateurs, sont regroupés dans un répertoire \dirname{scripts} -des arborescences \dirname{texmf*}. On les localise grâce à la -commande \verb|kpsewhich -format=texmfscripts|. Au cas où vous en auriez, -les programmes utilisant ces scripts nécessiteront une adaptation. Voir -\OnCD{texmf-doc/doc/english/tds/tds.html\#Scripts}. - -\item La plupart des formats affichent en clair (dans les fichiers -\file{.log} en particulier) les caractères imprimables au lieu -de les transcrire en notation hexadécimale \verb|^^|. Ceci se fait -grâce au fichier \filename{cp227.tcx}, qui considère comme imprimables -les caractères 32 à 256, ainsi que les tabulations et les changements -de page (caractères 9 à 11). Les formats faisant exception sont -plain \TeX\ (seuls les caractères 32 à 127 sont déclarés imprimables), -\ConTeXt{} (0 à 255 imprimables) et les formats basés sur \OMEGA. -Il y a peu de différence avec le comportement de \TL\,2003 -mais la mise en {\oe}uvre est plus propre et plus facilement configurable. -Voir \OnCD{texmf/doc/web2c/web2c.html\#TCX-files}. -Noter que l'utilisation du codage Unicode en entrée peut provoquer -des affichages défectueux en sortie (TeX code sur un seul octet). - -\item Tous les formats, sauf plain \TeX, font appel au moteur -\textsf{pdfetex} (qui produit bien sûr par défaut des fichiers \acro{DVI} -lorsque le format choisi est \LaTeX). Ceci permet aux formats -\LaTeX, \ConTeXt, etc., d'avoir accès aux fonctionnalités -micro-typographiques de pdf\TeX{} (alignement optique des marges par exemple) -et aux fonctionnalités de \eTeX{} (\OnCD{texmf-dist/doc/etex/base/}). - -Ceci rend \emph{indispensable} le recours à l'extension \pkgname{ifpdf} -(qui fonctionne aussi bien avec plain que \LaTeX) pour déterminer si -le format de sortie est \acro{DVI} ou \acro{PDF}. Tester si la commande -\cs{pdfoutput} est définie ou non \emph{n'est pas} un moyen fiable -de le faire. - -\item pdf\TeX\ (\url{http://pdftex.org}) offre de nouvelles fonctionnalités : - - \begin{itemize} - - \item Les commandes \cs{pdfmapfile} et \cs{pdfmapline} permettent - de spécifier le choix des fichiers \file{.map} à utiliser - pour le document en cours. - - \item L'amélioration du gris typographique par variation (infime) de la - largeur des caractères (\textit{font expansion}) est plus facile à - mettre en {\oe}uvre, voir - \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} - - \item Le fichier \filename{pdftex.cfg} n'est plus utilisé. - Toutes les affectations de paramètres doivent désormais être - faites dans le préambule en utilisant les primitives ad~hoc. - - \item Pour plus d'informations, consulter le manuel de pdf\TeX\ : - \OnCD{texmf/doc/pdftex/manual}. - - \end{itemize} - -\item La primitive \cs{input} de \cmdname{tex}, \cmdname{mf} et -\cmdname{mpost}, accepte désormais les espaces et autres caractères -spéciaux dans les noms de fichiers à condition d'utiliser des -\textit{double quotes}, en voici deux exemples typiques : -\begin{verbatim} -\input "filename with spaces" % plain -\input{"filename with spaces"} % latex -\end{verbatim} -Consulter le manuel \Webc{} pour plus d'informations : \OnCD{texmf/doc/web2c}. - -\item Les fonctionnalités de enc\TeX\ sont désormais incluses dans \Webc{}. -Ainsi, tous les formats \emph{construits avec l'option \optname{-enc}} y ont -accès. enc\TeX\ permet le transcodage en entrée et en sortie et -l'utilisation transparente du codage Unicode \acro{UTF}-8. Voir -\OnCD{texmf-dist/doc/generic/enctex/} et -\url{http://www.olsak.net/enctex.html}. - -\item Un nouveau moteur combinant les fonctionnalités de \eTeX\ -et d'\OMEGA, appelé Aleph, est disponible. \OnCD{texmf-dist/doc/aleph/base} -et \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph} -fournissent une information succincte. Le format \LaTeX{} utilisant -Aleph s'appelle \textsf{lamed}. - -\item La licence \acro{LPPL} de \LaTeX\ (version décembre 2003) a changé, -elle est désormais compatible avec les prescriptions Debian. -Les autres changements sont décrits dans le fichier \filename{ltnews}, voir -\OnCD{texmf-dist/doc/latex/base}. - -\item Un nouveau programme, \cmdname{dvipng}, qui convertit les fichiers -\acro{DVI} en images \acro{PNG} a été ajouté. Voir -\OnCD{texmf/doc/man/man1/dvipng.1}. - -\item Nous avons dû réduire le nombre de fontes incluses dans l'extension -\pkgname{cbgreek}, ceci a été fait avec l'accord et l'aide de l'auteur -(Claudio Beccari). Les fontes exclues (invisibles, transparentes, contours) -sont rarement utilisées et la place nous manquait. La collection complète -des fontes \pkgname{cbgreek} est disponible sur \acro{CTAN} -(\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). - -\item La commande \cmdname{oxdvi} a été supprimée, il suffit utiliser -\cmdname{xdvi} à la place. - -\item Les commandes \cmdname{initex}, \cmdname{virtex} et leurs -homologues pour \cmdname{mf} et \cmdname{mpost} ont disparu. -Vous pouvez les recréer si nécessaire mais elles sont avantageusement -remplacées, depuis des années maintenant, par l'option \optname{-ini} -(\cmdname{tex} \optname{-ini} pour \cmdname{initex} et \cmdname{virtex}). - -\item Les binaires pour l'architecture \textsf{i386-openbsd} ont été - supprimés par manque de volontaires pour les compiler. - -Sur \textsf{sparc-solaris} (au moins) il sera probablement -nécessaire de positionner la variable d'environnement -\envname{LD\_LIBRARY\_PATH} pour utiliser les programmes de la famille -\pkgname{t1utils}. Ceci vient du fait qu'ils sont compilés en C++, -et que l'emplacement des bibliothèques dynamiques est variable. -Ce n'est pas une nouveauté 2004 mais ce point n'était pas documenté -précédemment. De même, sur \textsf{mips-irix}, les bibliothèques dynamiques -\acro{MIPS}pro 7.4 sont nécessaires. - -\end{itemize} - -\subsubsection{2005} - -2005 a apporté son lot habituel d'innombrables mises à jour d'extensions -et de programmes. L'infrastructure est restée relativement stable par rapport -à 2004, à quelques changements inévitables près : - -\begin{itemize} - -\item Trois nouveaux scripts \cmdname{texconfig-sys}, \cmdname{updmap-sys} et - \cmdname{fmtutil-sys} ont été introduits ; ils agissent sur la - configuration générale de la machine, comme le faisaient les - scripts \cmdname{texconfig}, \cmdname{updmap} et \cmdname{fmtutil} - jusqu'à l'an dernier. Les nouveaux scripts \cmdname{texconfig}, - \cmdname{updmap} et \cmdname{fmtutil} modifient maintenant - la configuration \emph{personnelle} de l'utilisateur qui les lance ; - le résultat est placé dans le répertoire personnel de l'utilisateur - (sous \dirname{$HOME/.texlive2005}), voir %$ - section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig}. - -\item De nouvelles variables, \envname{TEXMFCONFIG} (resp. - \envname{TEXMFSYSCONFIG}) ont été introduites ; elles définissent - les répertoires où doivent se trouver les fichiers de configuration de - l'utilisateur (resp. de la machine), comme \filename{fmtutil.cnf} et - \filename{updmap.cfg}. Les utilisateurs de fichiers de configuration - locaux \filename{fmtutil.cnf} ou \filename{updmap.cfg} devront - probablement les déplacer ; une autre possibilité est de modifier la - définition des variables \envname{TEXMFCONFIG} ou - \envname{TEXMFSYSCONFIG} dans \filename{texmf.cnf}. L'important est - de s'assurer de la cohérence entre les définitions de ces variables - dans \filename{texmf.cnf} et l'emplacement réel de ces fichiers. - Voir section~\ref{sec:texmftrees}, \p.\pageref{sec:texmftrees} pour - la description des différentes arborescences texmf utilisées. - -\item L'an dernier nous avions rendu \og \texttt{undefined} \fg certaines - primitives propres à \cmdname{pdftex} (comme \verb|\pdfoutput|) - dans les formats créés à partir de \cmdname{pdfetex} (\cmdname{latex} - \cmdname{amstex}, \cmdname{context} par exemple)). - C'était à titre transitoire, aussi cette année, ces primitives sont de - nouveau définies dans tous les formats à base \cmdname{pdf(e)tex}, - \emph{même lorsqu'ils sont utilisés pour produire des fichiers - \file{.dvi}}. Ceci implique qu'il vous faudra modifier vos - documents qui utilisent le test \verb|\ifx\pdfoutput\undefined| - pour déterminer si la sortie est en DVI ou en PDF. Le mieux est - d'utiliser l'extension \pkgname{ifpdf.sty} et son test - \verb|\ifpdf| qui fonctionne même en plain \TeX. - -\item L'an dernier nous avions fait en sorte que la plupart des formats - impriment dans les sorties \file{.log} des caractères 8-bit - lisibles à la place des notations hexadécimales \verb|^^| - (voir section précédente). - Le nouveau fichier TCX \filename{empty.tcx} permet - de revenir facilement à la notation traditionnelle \verb|^^|, il suffit - de coder : -\begin{verbatim} -latex --translate-file=empty.tcx fichier.tex -\end{verbatim} - -\item Le nouveau programme \cmdname{dvipdfmx} est disponible pour convertir - des fichier DVI en PDF ; ce programme remplace \cmdname{dvipdfm}, - toujours disponible mais dont l'usage est maintenant déconseillé. - -\item Les variables \envname{HOMETEXMF} et \envname{VARTEXMF} ont été renommées - en \envname{TEXMFHOME} et \envname{TEXMFSYSVAR} respectivement pour - raisons de cohérence avec les autres noms de variables. Il y a aussi - \envname{TEXMFVAR} qui désigne maintenant un répertoire personnel - de l'utilisateur (cf. le premier point de la présente liste). - -\end{itemize} - -\subsection{L'édition 2006--2007} -\label{tlcurrent} - -En 2006--2007, la nouveauté majeure a été l'arrivée dans \TL{} de Xe\TeX{} -disponible sous forme de deux programmes \texttt{xetex} et \texttt{xelatex}, -voir \url{http://scripts.sil.org/xetex}. - -MetaPost a subi une mise à jour importante et d'autres améliorations -sont prévues, voir \url{http://tug.org/metapost/articles}. Il en va de même -pour pdf\TeX{}, voir \url{http://tug.org/applications/pdftex}. - -Le format \filename{tex.fmt} et les formats pour MetaPost and \MF\ ne -se trouvent plus dans \dirname{texmf/web2c} mais dans des -sous-répertoires de \dirname{texmf/web2c} (la recherche de fichiers -\filename{.fmt} est néanmoins faite aussi dans \dirname{texmf/web2c}). -Ces sous-répertoires portent le nom du moteur utilisé pour construire -le format, par exemple \filename{tex}, \filename{pdftex} ou -\filename{xetex}. Ce changement ne devrait pas avoir d'effet visible -pour les utilisateurs. - -Le programme (plain) \texttt{tex} ignore désormais les lignes commençant -par \texttt{\%\&} qui permettent de déterminer le format à utiliser ; -c'est un vrai \TeX{} \og à la Knuth \fg ! -\LaTeX\ et tous les autres prennent toujours en compte les lignes commençant -par \texttt{\%\&}. - -Les scripts d'installation peuvent maintenant être utilisés de manière -non interactive (voir section~\ref{sec:noninteractive-install}) en -positionnant des variables d'environnement. - -Comme chaque année des centaines d'extensions et de programmes ont été mis à -jour, voir les sites \acro{CTAN} (\url{http://www.ctan.org}). - -L'arborescence utilisée en interne a été réorganisée avec de nouveaux outils -qui devraient fournir une meilleure base de travail pour les développements -futurs. - -Enfin, en mai 2006 Thomas Esser a annoncé qu'il renonçait à poursuivre -le développement de te\TeX{} (\url{http://tug.org/tetex}). Sa décision a -relancé l'intérêt pour \TL, en particulier chez les distributeurs de solutions - \acro{GNU}/Linux (un nouveau schéma d'installation \texttt{tetex} a été - ajouté dans le script d'installation de \TL{} pour produire une - distribution proche de l'ancienne te\TeX). La distribution \TL{} existe -déjà sous forme de paquets Debian, espérons que les autres acteurs du monde -Linux (RedHat, SuSe, etc.) suivront et que les utilisateurs -se verront proposer à l'avenir des distributions \TeX{} riches et plus -faciles à installer. - - - -\subsection{Versions futures} - -\emph{\TL{} n'est pas un produit parfait !} -(et ne le sera jamais). Nous prévoyons de continuer à produire de -nouvelles versions, et aimerions fournir plus d'aide, de -fonctionnalités, de programmes d'installation, et (bien sûr) une -arborescence améliorée et vérifiée de macros et de fontes. Ce travail -est effectué par des volontaires débordés, dans la limite de leur temps -libre, et beaucoup reste à faire. Si vous pouvez nous aider, n'hésitez pas -à vous proposer ! - -Corrections, suggestions et propositions d'aide doivent -être envoyées à :\hfill\null -\begin{quote} -\email{tex-live@tug.org} \\ -\url{http://tug.org/texlive} -\end{quote} - -\medskip -\noindent \textsl{Bon travail avec \TeX{} !} - -\end{document} - -%%% Local Variables: -%%% mode: latex -%%% mode: flyspell -%%% ispell-local-dictionary: "francais" -%%% TeX-master: t -%%% coding: latin-1 -%%% End: diff --git a/Master/texmf-doc/source/texlive/texlive-fr/live4ht.cfg b/Master/texmf-doc/source/texlive/texlive-fr/live4ht.cfg deleted file mode 100644 index 4da18b3c746..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-fr/live4ht.cfg +++ /dev/null @@ -1,47 +0,0 @@ -% tex4ht configuration file for the TeX Live documentation. -% Accumulated over many years. Public domain. -% -% html specifies the main output format. -% info for extra debugging info in the log files. - -% better approach is to have html in one piece (including footnotes). -% charset=utf-8 fails for French, all accented letters get lost. -\Preamble{html,info,fn-in} - -% add extra stylesheet -\Configure{@HEAD}{\HCode{% -\Hnewline -\Hnewline -}} - -% or LaTeX complains it is missing. -\begin{document} - -\EndPreamble - -% simplify output for HTML. We leave TeX and LaTeX alone, since tex4ht -% actually does the lowered E (and raised A) in CSS. -\def\OMEGA{Omega} -\def\LaTeXe{LaTeX2e} -\def\eTeX{e-\TeX} -\def\acro#1{#1} -\def\MF{Metafont} -\def\BibTeX{BibTeX} -\def\warningbox{} -\def\endwarningbox{} - -\newif\ifhackliterals -\ifx\tldocenglish\undefined \else \hackliteralstrue \fi -\ifx\tldocrussian\undefined \else \hackliteralstrue \fi -\ifx\tldocgerman\undefined \else \hackliteralstrue \fi -% -\ifhackliterals - % these definitions cause "missing } inserted" at \end{tabularx} in - % French and Czech. don't know why. - % - % don't make these into links, as happens with \path. We only have a couple - % special characters that actually occur. - \def\dirname{\texttt\bgroup\catcode`\$=12 \catcode`\_=12 \finishliteral} - \def\finishliteral#1{#1\egroup} - \let\filename=\dirname -\fi diff --git a/Master/texmf-doc/source/texlive/texlive-fr/tex-live.css b/Master/texmf-doc/source/texlive/texlive-fr/tex-live.css deleted file mode 100644 index 5062bc0d229..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-fr/tex-live.css +++ /dev/null @@ -1,44 +0,0 @@ -/* $Id$ - Simple CSS for TeX Live that adds margins and a little color. - original by Bzyl Wlodzimierz, edited by Karl Berry, 2005. - Public domain. */ - -html { - // top left bottom right - margin: 15pt 15pt 15pt 15pt; - background: rgb(255,255,224); -} - -body { - margin: 0 5pt 0 5pt; - padding: 0; - //matw: background: rgb(224,255,224); - // (It looks better to me to have a consistent background --karl) -// fonts in browser are low resolution; -// therefore generated serif are poor quality, -// so they disturb reading (that is my opinion) - font-family: sans-serif; - font-style: normal; -} - -/* (It looks better to me to not vary colors at every level --karl) */ - -h3.sectionHead { - padding: 12pt 10pt 12pt 20pt; - //matw: background: rgb(192,224,255); - background: rgb(224,224,255); - color: rgb(0,0,32); -} - -h4.subsectionHead { - padding: 7pt 10pt 7pt 40pt; - background: rgb(224,224,255); - color: rgb(0,0,32); -} - -h5.subsubsectionHead { - padding: 3pt 10pt 3pt 40pt; - //matw: background: rgb(224,255,255); - background: rgb(224,224,255); - color: rgb(0,0,32); -} diff --git a/Master/texmf-doc/source/texlive/texlive-fr/texlive-fr.tex b/Master/texmf-doc/source/texlive/texlive-fr/texlive-fr.tex deleted file mode 100644 index 6b74bc3bd13..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-fr/texlive-fr.tex +++ /dev/null @@ -1,3148 +0,0 @@ -%Format: pdf -% -% Change history (started May 18th 2002) -% 2008/07/26: synced with 2008 English version, by Daniel Flipo -% 2007/01/18: synced with 2007 English version, by Daniel Flipo -% 2005/11/01: synced with 2005 English version, by Daniel Flipo -% 2005/05/05: re-added section on building binaries (Daniel Flipo) -% 2004/10/28: synced with 2004 English version, by Daniel Flipo -% 2003/08/28: synced with 2003 English version, by Éric Picheral & Jacques André -% 2002/05/25: proof-reading and corrections, by Daniel Flipo -% 2002/05/18: synced with English version, by Fabrice -% -\documentclass{article} -\let\tldocfrench=1 % NOT used... - -\usepackage[utf8]{inputenc} -\usepackage[T1]{fontenc} - -\usepackage[frenchb]{babel} -\usepackage{xspace} -\frenchbsetup{AutoSpacePunctuation=false, og=», fg=»} - -\usepackage{ifpdf} -% tex-live.sty suppose \hyper@linkurl défini... -\ifpdf - \def\Status{1} % (df) Pour faire charger hyperref dans tex-live.sty -\else - \makeatletter - \def\hyper@linkurl#1#2{#2} % undefined if hyperref.sty not loaded - \makeatother -\fi - -\usepackage{tex-live} -% Correctifs à tex-live.sty (df) -\renewcommand{\samp}[1]{\og \texttt{#1}\fg{}} -% (df) La commande \TeXLive n'est pas utilisée en v.f. -\renewcommand{\TL}{\TeX{} Live\xspace}% Robuste (pas besoin de \protect)... -\renewcommand{\TK}{\TeX{} Collection\xspace}% idem. -% tex-live.sty fait précéder les no de page d'une fine... si on veut -% une insécable normale, décommenter la ligne suivante : -\def\p.{page~} -% Chez Karl, la commande \url{} ne protège pas les caractères actifs (:?), -% d'où ceci (essai provisoire... erreurs avec le car. #) : -%\let\urlORI\url -%\renewcommand*{\url}[1]{\foreignlanguage{english}{\urlORI{#1}}} -%\renewcommand*{\url}[1]{{\shorthandoff{:?!;}\urlORI{#1}}} -% La commande \path de url.sty ajoute des espaces parasites, pas \url, d'où -\let\path\url -% mais ceci impose de remplacer \path|...| par \path{...}, et les \$ inclus -% par des $. - -\newcommand{\THANH}{Hàn Th\'{ê} Thanh} - -\setlength{\parindent}{0mm} -\addtolength{\parskip}{.25\baselineskip} - -\begin{document} - -\title{{\huge Guide pratique de \TL{} \\\smallskip} - {\LARGE\textsf{\TL{} 2008}}% - } - -\author{Karl Berry \\[3mm] - \url{http://tug.org/texlive/}\\[5mm] - \textit{Version française}\\[3mm] - Daniel Flipo (GUTenberg) - } - -\date{Juillet 2008} - -\maketitle -\thispagestyle{empty} % no need for page number - -\begin{multicols}{2} -\tableofcontents -%\listoftables -\end{multicols} - -\section{Introduction} -\label{sec:intro} - -\subsection{\TeX\ Live et \TeX\ Collection} - -Ce document décrit les principales caractéristiques de la -distribution \TL{}, une distribution complète de \TeX{} -pour Linux et autres Unix, \MacOSX{} et systèmes Windows. - -Cette distribution peut être obtenue par téléchargement ou sur le \DVD{} \TK{} -distribué par les groupes d'utilisateurs de \TeX{} à leurs membres. -La section \ref{sec:tl-coll-dists} décrit brièvement le contenu de ce \DVD. -\TL{} comme \TK{} sont produits grâce au travail des groupes d'utilisateurs de -\TeX. La description qui suit porte essentiellement sur \TL. - -La distribution \TL{} comprend les binaires -pré-compilés de \TeX{}, \LaTeXe{}, \MF, \MP, \BibTeX{} et de nombreux -autres programmes ainsi qu'une bibliothèque étendue de macros, de -fontes et de documentations. Elle traite aussi de la composition de textes -dans la plupart des langues utilisées dans le monde. - -Les composants de la distribution \TL{} sont régulièrement mis à jour -sur le site \acro{CTAN}, \url{http://www.ctan.org}. - -On trouvera à la fin du document, section~\ref{sec:history} -(page~\pageref{sec:history}), un bref historique des principales modifications -apportées au fil du temps à la distribution \TL. - -% Ajout (df) -Les utilisateurs des éditions précédentes de \TL{} sont invités -à lire, \emph{avant toute mise à jour}, la section~\ref{tlcurrent} -page~\pageref{tlcurrent} qui présente les principaux changements intervenus -cette année. - -\subsection{Support pour différents systèmes d'exploitation} -\label{sec:os-support} - -\TL{} contient les exécutables pour les principales architectures Unix, en -particulier Linux et \MacOSX. Les sources inclus dans la distribution -devraient permettre de compiler les exécutables nécessaires aux autres -systèmes d'exploitation. - -En ce qui concerne Windows, seuls Windows 2000 et ses successeurs (XP, Vista) -sont supportés ; les architectures antérieures (Windows 9\textit{x}, ME et NT) -ne le sont plus. Il n'y a pas d'exécutables 64-bit mais les versions 32-bit -devraient fonctionner aussi sur les systèmes 64-bit. - -Consulter la section~\ref{sec:tl-coll-dists} pour des solutions alternatives -sous Windows et \MacOSX. - -\subsection{Utilisation élémentaire de \TL{}} -\label{sec:basic} - -Vous pouvez installer \TL{} de deux façons différentes : soit en utilisant -l'installeur qui télécharge toute la distribution sur Internet, soit à partir -du \DVD{} ce qui ne nécessite pas de connexion au réseau. - -Vous pouvez aussi exécuter \TL{} directement depuis le -\DVD{} (ou depuis une image iso du \DVD{} si votre système le permet) sans -(presque) rien installer sur le disque dur. - -Ces trois utilisations sont décrites en détail dans les sections suivantes, -voici quelques remarques générales pour débuter : - -\begin{itemize} - -\item Le script d'installation globale s'appelle -\filename{install-tl}. Il fonctionne en mode graphique (mode par défaut sous -Windows) et en mode texte (mode par défaut pour les autres systèmes). -Ajouter l'option \code{-gui} ou \code{-no-gui} pour imposer le mode graphique -ou le mode texte. - -\item Ce script installe en particulier un nouveau programme, le -« \TL\ Manager » appelé \prog{tlmgr}. Comme l'installeur, il peut être -utilisé en mode graphique ou en mode texte. Il permet d'ajouter ou de -supprimer des composants et de procéder à différents réglages de -configuration. - -\end{itemize} - -\subsection{Obtenir de l'aide} -\label{sec:help} - -La communauté \TeX{} est à la fois active et conviviale ; la plupart des -questions finissent par obtenir une réponse. Le support est -pourtant informel, assuré par des volontaires et des lecteurs -occasionnels, aussi est-il particulièrement important que vous fassiez -votre propre travail de recherche avant de poser la question (si vous -préférez un support commercial, vous pouvez renoncer à \TL{} et -acheter un système payant ; voir une liste à -\url{http://tug.org/interest.html#vendors}). - -Voici une liste de ressources, classées selon l'ordre dans lequel nous -recommandons de les utiliser : - -\begin{description} -\item [Getting Started] -- pour ceux qui débutent en \TeX, la page web -\url{http://tug.org/begin.html} contient une courte description -du système. - -\item [\acro{FAQ} \TeX{}] -- la \acro{FAQ} \TeX{} est un vaste recueil - de réponses à toutes sortes de questions, de la plus élémentaire à la - plus complexe. Elle est enregistrée sur le \DVD{} dans - \OnCD{texmf-doc/doc/english/FAQ-en/html/index.html} - et elle est disponible sur Internet à - l'adresse \url{http://www.tex.ac.uk/faq}. - Merci de consulter cette FAQ avant toute question. - -\item [Catalogue \TeX{}] -- si vous recherchez une extension, une fonte, - un programme, etc., le mieux est de consulter le catalogue - \TeX{} ici : \url{http://www.ctan.org/help/Catalogue/}. - -\item [Ressources \TeX{} sur le Web] -- la page web - \url{http://tug.org/interest.html} propose - beaucoup de liens relatifs à \TeX{}, en particulier concernant des - livres, manuels et articles portant sur tous les aspects du système. - -\item [Archives des forums d'aide] -- les principaux forums dédiés - au support de \TeX{} sont les groupes de news Usenet - \url{news:comp.text.tex} (en anglais) et \url{news:fr.comp.text.tex} - (en français) ainsi que les listes de diffusion - \email{texhax@tug.org} (en anglais) et \email{gut@ens.fr} (en français). - Les archives correspondantes contiennent des - milliers de questions et réponses déjà traitées et permettent - une recherche fructueuse. Voir - \url{http://groups.google.com/groups?group=fr.comp.text.tex} - et \url{http://tug.org/mail-archives/texhax}, respectivement. Une - question posée sur un moteur de recherche, tel que - \url{http://google.com}, peut aussi fournir des réponses pertinentes. - -\item [Poster une question] -- si vous ne trouvez pas de réponse, vous - pouvez poster la question à \dirname{fr.comp.text.tex} via Google ou - votre lecteur de news, ou encore par messagerie à - \email{texhax@tug.org}. Mais avant de le faire, merci de lire - l'introduction de la \acro{FAQ} donnant les conseils sur la façon de - rédiger la question pour avoir des chances d'obtenir une réponse pertinente : - \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. - -\item [Support de \TL{}] -- si vous voulez faire un rapport - d'anomalie, émettre des suggestions ou des commentaires sur la - distribution \TL{}, son installation ou sa documentation, utilisez - la liste de diffusion \email{tex-live@tug.org}. Mais attention, si - la question concerne l'utilisation d'un programme particulier inclus - dans \TL{}, il vaut mieux que vous vous adressiez directement à la - personne ou à la liste de diffusion qui maintient le programme. Il suffit - souvent d'ajouter l'option \code{-{}-help} lors de l'exécution du programme - pour trouver à qui adresser le rapport. - -\end{description} - -L'autre aspect du sujet concerne l'aide à apporter aux personnes -soumettant des questions. Les forums \dirname{comp.text.tex}, -\dirname{fr.comp.text.tex} ainsi que les listes de diffusion \code{texhax} -et \code{gut} -sont ouverts à tous, aussi n'hésitez pas à vous y joindre, à commencer -la lecture et à fournir de l'aide là où cela vous est possible. - -% No \protect needed as \TL is defined in French with \newcommand (robust). -\section{Structure de \TK} -\label{sec:overview-tl} - -Nous décrivons ici le contenu de \TK{} qui est un sur-ensemble de \TL. - -\subsection {\TK{} : \TL, pro\TeX{}t, Mac\TeX} -\label{sec:tl-coll-dists} - -Le \DVD{} \TK{} contient les éléments suivants : - -\begin{description} - -\item [\TL{}] -- un système \TeX{} complet (\TL) qui peut au choix, être lancé à - partir du \DVD{} (sans installation) ou être installé sur le disque dur. - -\item [CTAN] -- une image du site d'archives \CTAN. - -\item [pro\TeX{}t] -- une extension du système \MIKTEX\ pour Windows qui en - facilite l'installation. Cette distribution est totalement indépendante de - \TL{}, elle nécessite un mode d'installation spécifique. Le site de - \ProTeXt\ se trouve ici : \url{http://tug.org/protext}. - -\item [Mac\TeX] -- un programme d'installation spécifique de \TL{} pour - \MacOSX{} et quelques applications propres au système Mac. - Le site de Mac\TeX{} se trouve ici : \url{http://www.tug.org/mactex/}. - -\item [\texttt{texmf-extra}] -- un répertoire contenant quelques extensions - supplémentaires. - -\end{description} - -Les droits d'utilisation des fichiers présents dans \CTAN, \ProTeXt{} -et \texttt{texmf-extra} diffèrent de ceux de \TL{}, pensez à lire -les licences si vous envisagez de modifier ou de redistribuer certains de -ces fichiers. - -\subsection{Répertoires situés à la racine de \TL{}} -\label{sec:tld} - -La distribution \TL{} est dans le sous-répertoire \dirname{texlive} -du \DVD{} \TK{}. Les répertoires les plus importants -situés à la racine de la distribution \TL{} sont énumérés ci-dessous : - -\begin{ttdescription} -\item[bin] -- programmes de la famille \TeX{}, rangés dans des - sous-répertoires selon les plates-formes. -% -\item[readme.html] -- une brève introduction et quelques liens utiles sous forme - de pages \textsc{html} dans différentes langues. -% -\item[source] -- le code source de tous les programmes, incluant la - distribution \Webc{} de \TeX{} et \MF{}. -% -\item[support] -- ensemble d'extensions et programmes auxiliaires (en - particulier des éditeurs et des \textit{shells} dédiés à \TeX) ; ils ne sont - \emph{pas} installés par défaut. -% -\item[texmf] -- répertoire contenant les programmes et leur documentation ; ne - contient ni les formats ni les extensions (la variable \envname{TEXMFMAIN} - de la section suivante pointe sur ce répertoire). -% -\item[texmf-dist] -- répertoire principal où se trouvent les extensions, - les fontes, etc., avec leur documentation (la variable \envname{TEXMFDIST} - de la section suivante pointe sur ce répertoire). -% -\item[texmf-doc] -- répertoire contenant le reste de la documentation, le - sous-répertoire doc est organisé par langue. -% -\item[tlpkg] -- scripts et programmes d'installation ; des versions de - Perl et de Ghostscript (inaccessibles en dehors de \TL) ainsi qu'un - nouveau visualiseur de fichiers PostScript ont été ajoutés pour - Windows. -\end{ttdescription} - -On trouve également, au même niveau que les répertoires mentionnés ci-dessus, -les scripts d'installation et les fichiers \filename{README} (disponibles dans -différentes langues). - -Le répertoire \dirname{texmf-doc} ne contient que de la documentation -mais pas toute la documentation. Celle concernant les programmes (manuels, -pages \textit{man} et fichiers de type \textit{info} est dans -\dirname{texmf/doc} car les programmes correspondants sont dans -\dirname{texmf}. De même, la documentation des extensions et formats -est dans \dirname{texmf-dist/doc}. Les commandes \cmdname{texdoc} ou -\cmdname{texdoctk} trouveront pour vous les documentations où qu'elles soient -sur le disque. -Le fichier \OnCD{doc.html} du \DVD{} contient une liste de liens bien -utiles pour localiser les fichiers de documentation. - -La documentation de \TL\ proprement dite est disponible dans le répertoire -\dirname{texmf-doc} en plusieurs langues, - -\begin{itemize} -\item{anglais :} \OnCD{texmf-doc/doc/english/texlive-en}, -\item{allemand :} \OnCD{texmf-doc/doc/german/texlive-de}, -\item{chinois (simplifié) :} \OnCD{texmf-doc/doc/chinese/texlive-zh-cn}, -\item{français :} \OnCD{texmf-doc/doc/french/texlive-fr}, -\item{polonais :} \OnCD{texmf-doc/doc/polish/texlive-pl}, -\item{russe :} \OnCD{texmf-doc/doc/russian/texlive-ru}, -\item{tchèque \& slovaque :} \OnCD{texmf-doc/doc/czechslovak/texlive-cz}. -\end{itemize} - -\subsection{Description des arborescences « texmf » de \TL} -\label{sec:texmftrees} - -Nous donnons ici la liste complète des variables prédéfinies qui contiennent -les noms des différentes arborescences de type « texmf » et l'usage qui -en est fait. La commande \cmdname{texconfig conf} retourne les valeurs de ces -variables, ce qui permet de savoir où se trouvent ces différentes -arborescences dans une installation donnée. - -\begin{ttdescription} -\item [TEXMFMAIN] -- contient les éléments essentiels du système, comme les - scripts (\cmdname{web2c/mktexdir}, etc.), leur documentation mais pas les - formats ni les fichiers de macros.-- -\item [TEXMFDIST] -- contient les fichiers de macros (Plain, \LaTeX, \ConTeXt, - etc.,), les fontes, etc., de la distribution \TL{} ; rien ne devrait être - ni ajouté ni supprimé dans cette arborescence. -\item [TEXMFLOCAL] -- c'est là que l'administrateur de la machine doit - placer les classes et extensions locales, les fontes non disponibles - dans \TL, etc. -\item [TEXMFHOME] -- contient les fichiers personnels (extensions, classes, - fontes) de l'utilisateur ; ce répertoire est installé automatiquement dans - le répertoire personnel de l'utilisateur. -\item [TEXMFCONFIG] -- c'est là que les scripts \cmdname{updmap} et - \cmdname{fmtutil} recherchent leurs fichiers de configuration en priorité. - \cmdname{texconfig} y place les versions modifiées des fichiers de - configuration. Sous \envname{TEXMFHOME} par défaut. -\item [TEXMFSYSCONFIG] -- c'est là que les scripts \cmdname{updmap-sys} et - \cmdname{fmtutil-sys} recherchent leurs fichiers de configuration en - priorité. \cmdname{texconfig-sys} y place les versions modifiées des - fichiers de configuration. -\item [TEXMFVAR] -- c'est là que les scripts \cmdname{texconfig}, - \cmdname{updmap} et \cmdname{fmtutil} rangent les formats et les fichiers - \file{.map} qu'ils produisent. Sous \verb+$HOME+ par défaut. %$ -\item [TEXMFSYSVAR] -- c'est là que les scripts \cmdname{texconfig-sys}, - \cmdname{updmap-sys} et \cmdname{fmtutil-sys} rangent les formats et les - fichiers \file{.map} qu'ils produisent. -\end{ttdescription} - -La structure de l'arborescence \TL{} est par défaut la suivante : -\begin{description} -\item[racine multi-utilisateurs] (par exemple \verb|/usr/local/texlive|, - \verb|D:\texlive|,\dots) qui contient éventuellement plusieurs - distributions : - \begin{ttdescription} - \item[2007] -- la distribution précédente, - \begin{ttdescription} - \item [...] - \end{ttdescription} - \item[2008] -- la distribution actuelle, - \begin{ttdescription} - \item [bin] ~ - \begin{ttdescription} - \item [i386-linux] -- exécutables Linux, - \item [...] - \item [universal-darwin] -- exécutables \MacOSX, - \item [win32] -- exécutables Windows, - \end{ttdescription} - \item [texmf] -- correspond à \envname{TEXMFMAIN}, - \item [texmf-dist] -- correspond à \envname{TEXMFDIST}, - \item [texmf-doc] -- correspond à \envname{TEXMFDOC}, - \item [texmf-var] -- correspond à \envname{TEXMFSYSVAR}, - \item [texmf-config] -- correspond à \envname{TEXMFSYSCONFIG}, - \end{ttdescription} - \item [texmf-local] -- correspond à \envname{TEXMFLOCAL}, normalement - commun à plusieurs distributions \TL{} (2007, 2008, etc.), - \end{ttdescription} - \item[répertoire personnel de l'utilisateur] \texttt{\$HOME} ou - \texttt{\%USERPROFILE\%} : - \begin{ttdescription} - \item[.texlive2007] -- fichiers générés automatiquement par la - distribution \TL{} précédente, - \item[.texlive2008] -- fichiers générés automatiquement par la - distribution \TL{} actuelle, - \begin{ttdescription} - \item [texmf-var] -- correspond à \envname{TEXMFVAR}, - \item [texmf-config] -- correspond à \envname{TEXMFCONFIG}, - \end{ttdescription} - \item[texmf] -- correspond à \envname{TEXMFHOME}, répertoire regroupant - tous les répertoires de macros personnelles : \dirname{texmf/tex/latex} - par exemple pour les fichiers de macros LaTeX, etc. - \end{ttdescription} -\end{description} - -\subsection{Les extensions de \TeX} -\label{sec:tex-extensions} - -\TL{} contient, à part \TeX{} lui-même (le programme \prog{tex}) qui est figé -sauf rares corrections de bogues, plusieurs extensions de \TeX{}. - -\begin{description} - -\item [\eTeX{}] \label{text:etex} ajoute un jeu de nouvelles - primitives et les extensions \TeXXeT{} pour l'écriture de droite - à gauche ; \eTeX{} est, en mode normal, 100\% compatible avec - \TeX{} standard. Pour plus de détails consulter le - fichier \OnCD{texmf-dist/doc/etex/base/etex_man.pdf} du \DVD{}. - -\item [pdf\TeX{}] inclut les extensions \eTeX{} et produit, au choix, - des fichiers au format Acrobat \acro{PDF} ou au format \dvi{}. - C'est le moteur de base sur lequel sont construits tous les formats autres - que plain\TeX{} (voir \url{http://www.pdftex.org/}). - Le manuel d'utilisation se trouve sur le \DVD{} - dans \OnCD{texmf/doc/pdftex/manual/}. Le fichier - \OnCD{texmf/doc/pdftex/pdftex/manual/samplepdf/samplepdf.tex} - donne des exemples d'utilisation. - -\item [Lua\TeX] est le successeur de pdf\TeX{} - avec lequel il reste compatible. Il devrait également remplacer Aleph, voir - ci-dessous. Lua\TeX{} fait appel à l'interpréteur de commande Lua (voir - \url{http://www.lua.org/}) qui apporte des solutions élégantes - à beaucoup de problèmes épineux en \TeX{} pur. - La commande \filename{texlua}, qui fonctionne comme un interpréteur Lua - indépendant, est déjà utilisée en tant que telle dans \TL. - Voir \url{http://www.luatex.org/} et - \OnCD{texmf-dist/doc/luatex/luatexref-t.pdf}. - -\item [Xe\TeX] ajoute la possibilité d'utiliser en entrée le codage Unicode - et en sortie les fontes OpenType et les fontes système de la machine, ceci - grâce à des bibliothèques externes : voir \url{http://scripts.sil.org/xetex}. - -\item [\OMEGA{} (Omega)] fonctionne en utilisant Unicode et des - caractères 16 bits, ce qui lui permet de travailler directement et - simultanément avec presque toutes les écritures du monde. - L'extension supporte aussi le chargement dynamique d'\acro{OTP} - (\OMEGA{} \emph{Translation Processes}) qui permet à l'utilisateur - d'appliquer sur des flux d'entrée quelconques des transformations - complexes qu'il aura lui-même définies. Voir la documentation - (pas vraiment à jour) dans \OnCD{texmf-dist/doc/omega/base/doc-1.8.tex}. - -\item [Aleph] combine les fonctionnalités de \OMEGA\ et de \eTeX. - \OnCD{texmf-dist/doc/aleph/base} contient une documentation de base. - -\end{description} - -% Fin MAJ 15/07/2008 -\subsection{Quelques autres programmes intéressants - dans \TL} - -Voici quelques autres programmes couramment utilisés et présents dans -\TL{} : - -\begin{cmddescription} - -\item [bibtex] -- traitement de la bibliographie. - -\item [makeindex] -- traitement des index. - -\item [dvips] -- conversion \dvi{} vers \PS{}. - -\item [xdvi] -- visualisation \dvi{} pour le système X Window. - -\item [dvilj] -- pilote \dvi{} pour les imprimantes HP LaserJet. - -\item [dv2dt, dt2dv] -- conversion \dvi{} vers ou depuis du texte simple. - -\item [dviconcat, dviselect] -- couper/Coller de pages à partir de fichiers - \dvi{}. - -\item [dvipdfmx] -- conversion \dvi{} vers \acro{PDF}, une autre façon de - produire des fichiers \acro{PDF}, concurrente de pdf\TeX\ mentionné - ci-dessus ; voir aussi les extensions \pkgname{ps4pdf} et - \pkgname{pdftricks} pour d'autres alternatives. - -\item [psselect, psnup, \ldots] -- utilitaires \PS{}. - -\item [lacheck] -- vérification de syntaxe \LaTeX{}. - -\item [texexec, texmfstart] -- processeurs Con\TeX{}t et \acro{PDF}. - -\item [tex4ht] -- conversion \TeX{} vers \acro{HTML} et \acro{XML}. - -\end{cmddescription} - -\subsection{Fontes incluses dans \TL} -\label{sec:tl-fonts} - -La distribution \TL{} contient un grand nombre de fontes vectorielles de haute -qualité : voir \url{http://tug.org/fonts} et -\OnCD{texmf-doc/english/free-math-fonts-survey}. - - -\section{Installation} -\label{sec:install} - -\subsection{Démarrage de l'installation} -\label{sec:inst_start} - -La première chose à faire est de récupérer le \DVD{} \TK ou de -télécharger le programme d'installation par le réseau. -Le programme d'installation s'appelle \filename{install-tl} pour Unix -et \filename{install-tl.bat} pour Windows. - -\begin{description} -\item [Installeur réseau] -- à télécharger sur CTAN dans - \dirname{systems/texlive/tlnet}; l'url - \url{http://mirror.ctan.org/systems/texlive/tlnet} vous redirigera - automatiquement vers le serveur d'archive le plus proche de chez vous. - Deux versions sont disponibles, \filename{install-tl.zip} utilisable sous - Unix et sous Windows et \filename{install-unx.tar.gz} pour Unix seulement - (y compris \MacOSX). Après décompression de l'un de ces deux fichiers, les - scripts \filename{install-tl} et \filename{install-tl.bat} se trouveront - dans le sous-répertoire \dirname{install-tl}. - -\item [\DVD \TK{}] -- aller dans le répertoire \dirname{texlive}. - Sous Windows, l'installation démarrera probablement - automatiquement quand vous insérerez le \DVD, sinon, il faudra lancer le - script d'installation \filename{install-tl} ou \filename{install-tl.bat}. - Le \DVD \TK{} est distribué gratuitement aux membres des groupes - d'utilisateurs de \TeX{} (Gutenberg par exemple en France, voir la liste - des groupes sur \url{http://tug.org/usergroups.html}). Il est également - possible de l'acheter séparément (\url{http://tug.org/store}) ou de graver - l'image \ISO{} (\url{http://tug.org/texlive/acquire.html}). -\end{description} -Les sections suivantes détaillent le processus d'installation. - - -\begin{figure}[tb] -\centering -\begin{boxedverbatim} -======================> TeX Live installation procedure <===================== - -=======> Note: Letters/digits in indicate menu items <======= -=======> for commands or configurable options <======= - - - Detected platform: Intel x86 with GNU/Linux - - binary systems: 1 out of 16 - - Installation scheme (scheme-full) - - Customizing installation scheme: - standard collections - language collections - 83 collections out of 84, disk space required: 1666 MB - - directories: - TEXDIR (the main TeX directory): - !! default location: /usr/local/texlive/2008 - !! is not writable, please select a different one! - TEXMFLOCAL (directory for site-wide local files): - /usr/local/texlive/texmf-local - TEXMFSYSVAR (directory for variable and automatically generated data): - /usr/local/texlive/2008/texmf-var - TEXMFSYSCONFIG (directory for local config): - /usr/local/texlive/2008/texmf-config - TEXMFHOME (directory for user-specific files): - ~/texmf - - options: - [ ] use letter size instead of A4 by default - [X] create all format files - [X] install macro/font doc tree - [X] install macro/font source tree - [ ] create symlinks in standard directories - - Install for running from DVD - -Other actions: - start installation to HD - help - quit - -Enter command: -\end{boxedverbatim} -\caption{Écran principal de configuration (\GNU/Linux)}\label{fig:text-main} -\end{figure} - -\begin{figure}[tb] -\centering -\tlpng{install-w32-main}{\linewidth} -\caption{Écran principal de configuration (Windows)}\label{fig:gui-main} -\end{figure} - -\subsubsection{Installation sous Unix} - -Dans ce qui suit l'invite du \textit{shell} est notée \texttt{>} ; les -commandes de l'utilisateur sont en \Ucom{\texttt{gras}}.\linebreak -Commandes à lancer dans un terminal sur tout système Unix pour travailler en -mode texte : -\begin{alltt} -> \Ucom{cd /chemin/de/installeur} -> \Ucom{perl install-tl} -\end{alltt} - -Pour travailler en mode graphique : -\begin{alltt} -> \Ucom{cd /chemin/de/installeur} -> \Ucom{./install-tl -gui} -\end{alltt} - -La liste complète des options est donnée par -\begin{alltt} -> \Ucom{perl install-tl -help} -\end{alltt} - -\textbf{Attention} : le matériel installé doit normalement être accessible à -tous les utilisateurs de la machine ; si celui qui installe n'est pas -\textit{root}, il devra s'assurer que son \code{umask} est adapté, par -exemple \code{umask 022} ou \code{umask 002}. -Consulter la documentation système pour plus de précisions. - -\subsubsection{Installation sous Mac\,OS\,X} - -Une distribution spécifique, Mac\TeX\ (\url{http://tug.org/mactex}), a été -mise au point pour \MacOSX. Nous recommandons de l'utiliser plutôt que -d'installer la distribution \TL{} en suivant la procédure indiquée pour Unix. - -En effet, Mac\TeX{} permet des ajustements spécifiques pour le système -\MacOSX{} et facilite la cohabitation entre plusieurs distributions \TeX{} -(Mac\TeX, gw\TeX, Fink, MacPorts, \ldots). - -Mac\TeX\ est très proche de \TL, les arborescences principales sont en tous -points identiques, quelques répertoires contenant de la documentation et des -applications spécifiques au Mac sont ajoutés. - -\subsubsection{Installation sous Windows} - -Si vous utilisez l'installeur réseau ou si l'insertion du \DVD{} ne lance pas -l'installation automatiquement, double-cliquez sur \filename{install-tl.bat}. - -Il est également possible de travailler en ligne de commande ; -dans ce qui suit l'invite du \textit{shell} est notée \texttt{>}, les -commandes de l'utilisateur sont notées \Ucom{\texttt{en gras}}. Voici les -commandes à lancer : -\begin{alltt} -> \Ucom{install-tl} -\end{alltt} -à condition d'être dans répertoire du script d'installation, sinon -\begin{alltt} -> \Ucom{D:\bs{}texlive\bs{}install-tl} -\end{alltt} -où \texttt{D:} désigne le lecteur de \DVD. - -Pour travailler en mode texte : -\begin{alltt} -> \Ucom{install-tl -no-gui} -\end{alltt} -La liste complète des options est donnée par -\begin{alltt} -> \Ucom{install-tl -help} -\end{alltt} - -\subsubsection{Installation en mode texte} - -La figure~\ref{fig:text-main} page~\pageref{fig:text-main} présente l'écran -principal de configuration en mode texte sous Unix/Linux. - -Taper une des lettres proposées (en respectant la casse) suivie de -« Entrée » (retour-chariot), l'écran se mettra automatiquement à jour. - -L'interface est volontairement rudimentaire afin de permettre son utilisation -sur le plus grand nombre possible de systèmes même avec des versions très -dépouillées de Perl (un sous-ensemble de commande Perl est fourni pour Windows). - -\subsubsection{Installation en mode graphique} - -La figure~\ref{fig:gui-main} page~\pageref{fig:gui-main} présente l'écran -principal de configuration en mode graphique sous Windows. Les différences -entre les options disponibles en mode texte et en mode graphique s'expliquent -par le changement de système (\GNU/Linux pour le premier, Windows pour le -second). - -\subsection{Choix des options d'installation} -\label{sec:runinstall} - -Les options proposées sont censées être assez explicites, voici cependant -quelques précisions. - -\subsubsection{Choix des binaires (Unix seulement)} -\label{sec:binary} - -\begin{figure}[tbh] -\centering -\begin{boxedverbatim} -Available sets of binaries: -=============================================================================== - - a [ ] alpha-linux DEC Alpha with GNU/Linux - b [ ] amd64-freebsd x86_64 with FreeBSD - c [ ] hppa-hpux HP-UX - d [ ] i386-freebsd Intel x86 with FreeBSD - e [X] i386-linux Intel x86 with GNU/Linux - f [ ] i386-openbsd Intel x86 with OpenBSD - g [ ] i386-solaris Intel x86 with Sun Solaris - h [ ] mips-irix SGI IRIX - i [ ] powerpc-aix PowerPC with AIX - j [ ] powerpc-linux PowerPC with GNU/Linux - k [ ] sparc-linux Sparc with GNU/Linux - l [ ] sparc-solaris Sparc with Solaris - m [ ] universal-darwin universal binaries for MacOSX/Darwin - o [ ] win32 Windows - p [ ] x86_64-linux x86_64 with GNU/Linux -\end{boxedverbatim} -\caption{Menu pour le choix des binaires}\label{fig:bin-text} -\end{figure} - -La figure~\ref{fig:bin-text} présente les choix de binaires possibles en mode -texte. Seuls les binaires correspondant à l'architecture détectée seront -installés par défaut. Rien n'empêche d'en sélectionner d'autres si nécessaire, -ce qui peut être intéressant dans le cas de serveurs en réseau ou sur des -machines en « double boot ». - -\subsubsection{Choix des composants de l'installation} -\label{sec:components} - -\begin{figure}[tbh] -\centering -\begin{boxedverbatim} -Select a scheme: -=============================================================================== - - a [ ] TeX Live basic scheme - b [ ] TeX Live scheme for ConTeXt - c [X] TeX Live full scheme - d [ ] GUST TeX Live scheme - e [ ] GUTenberg TeX Live scheme - f [ ] TeX Live medium scheme - g [ ] TeX Live minimal scheme - h [ ] TeX Live for Omega users - i [ ] teTeX scheme - j [ ] XML typesetting scheme -\end{boxedverbatim} -\caption{Menu « Scheme »}\label{fig:scheme-text} -\end{figure} - -Dans le menu « Scheme » (voir figure~\ref{fig:scheme-text}) on choisit -un schéma général de configuration qui détermine un ensemble de collections à -installer. Par défaut, on procède à l'installation de tout ce qui est -disponible (option \optname{scheme-full}). Des installations plus ou moins -complètes sont proposées : \optname{minimal} pour effectuer des tests -uniquement, \optname{basic} pour un système de base, \optname{medium} ou -\optname{teTeX} pour des systèmes intermédiaires. -Pour les francophones, l'option \optname{GUTenberg} est une bonne base de -départ. Le choix pourra être affiné à l'étape suivante. - -\begin{figure}[tbh] -\centering -\tlpng{stdcoll}{.7\linewidth} -\caption{Menu « Collections » (Linux)}\label{fig:collections-gui} -\end{figure} - -Une fois choisi le schéma général, il est possible de d'ajouter ou de -supprimer des composants, appelés -ici collections. Il y a deux types de collections : les -« Standard Collections » qui concernent les fontes, les extensions, les -formats, etc. (voir figure~\ref{fig:collections-gui}) et les -« Language Collections » qui permettent de préciser la liste des langues -qui seront utilisables sur le système (indispensable !). Attention, si vous -travaillez en mode texte, dans ces menus la casse des lettres est importante. -En mode graphique, il suffit de cocher ou de décocher les cases en cliquant. - -Il est possible de raffiner encore les choix mais il faudra alors utiliser -le programme \prog{tlmgr} ultérieurement, voir la section~\ref{sec:tlmgr}. - -\subsubsection{Répertoires d'installation} -\label{sec:directories} - -La racine de l'installation principale est donnée par \dirname{TEXDIR} qui -vaut par défaut \dirname{/usr/local/texlive/2008} sous Unix et -|%PROGRAMFILES%\texlive\2008| sous Windows. -La liste des sous-répertoires de \dirname{TEXDIR} choisis par défaut est -donnée à la section~\ref{sec:texmftrees}, page~\pageref{sec:texmftrees}. - -Il peut être nécessaire de changer la valeur de \dirname{TEXDIR} -lorsque celui qui procède à l'installation n'a pas les droits d'écriture -sur le répertoire \dirname{TEXDIR} (l'installation n'est pas réservée au -super-utilisateur « root » ou « Administrateur »). -Il est possible d'installer \TL{} dans le répertoire personnel d'un -utilisateur, dans ce cas on peut choisir par exemple |~/texlive/2008|. - -Dans tous les cas, il est recommandé d'inclure l'année dans le chemin afin de -pouvoir conserver plusieurs versions de \TL{} en parallèle. -Rien n'empêche d'ajouter un lien symbolique (par exemple -\dirname{/usr/local/texlive-current}) qui pointe sur la version actuellement -utilisée. Ceci facilite les basculements d'une version à une autre. - -Le répertoire \envname{TEXMFHOME} (|~/texmf| par défaut) est destiné à -regrouper les répertoires de macros personnelles. Le caractère |~| désignant -le répertoire personnel est traité différemment, selon qu'il est utilisé dans -\dirname{TEXDIR} --~il s'agit alors du répertoire de \emph{l'installateur}~-- -ou dans \envname{TEXMFHOME}, là |~| est traité dynamiquement utilisateur par -utilisateur est vaut \envname{\$HOME} %$ -sous Unix et |%USERPROFILE%| sous Windows. - -\subsubsection{Options} -\label{sec:options} - -\begin{figure}[tbh] -\centering -\begin{boxedverbatim} -

use letter size instead of A4 by default: [ ] - create all format files: [X] - install font/macro doc tree: [X] - install font/macro source tree: [X] - create symlinks in standard directories: [ ] - binaries to: - manpages to: - info to: -\end{boxedverbatim} -\caption{menu « Options » (Unix)}\label{fig:options-text} -\end{figure} - -La figure~\ref{fig:options-text} présente le menu « Options » en mode -texte. Normalement il n'y a pas lieu de modifier les choix par défaut. -Voici quelques précisions cependant. - -\begin{description} -\item[use letter size instead of A4 by default] -- la taille du papier pour - l'impression est A4, il est possible de la changer ici, en \textit{letter} - par exemple. - -\item[create all format files] -- création de tous les formats à l'installation. - Bien que cette opération prenne un peu de temps, il est conseillé de ne pas - la supprimer, sinon les formats seront créés au coup par coup dans les - répertoires personnels des utilisateurs (sous \envname{TEXMFVAR}). Les - formats personnels ainsi créés ne bénéficieront pas des mises à jour - éventuelles effectuées ultérieurement sur l'installation \TL{}, ce qui - peut engendrer des incompatibilités. - -\item[create symlinks in standard directories] (Unix seulement) -- - cette option permet d'éviter de modifier les variables d'environnement - \envname{PATH}, \envname{MANPATH} et \envname{INFOPATH}. En revanche, - elle peut perturber une installation \TeX{} incluse dans votre distribution - (Debian, RedHat, etc.). La modification des trois variables d'environnement - ci-dessus est préférable. -\end{description} - -Lorsque vous êtes satisfait des réglages faits, il vous reste à taper -\code{I} pour lancer le processus d'installation. Lorsque celui-ci sera -terminé, sautez à la section~\ref{sec:postinstall} pour voir s'il y a -d'autres choses à faire. - -\subsubsection{Utilisation de \TL{} à partir du DVD{} (mode texte uniquement)} -\label{sec:fromdvd} - -Taper `|V|' pour choisir ce mode de fonctionnement, le menu qui s'affiche -alors est présenté figure~\ref{fig:main-fromdvd}. -\begin{figure}[tbh] -\centering -\begin{boxedverbatim} -======================> TeX Live installation procedure <===================== - -=======> Note: Letters/digits in indicate menu items <======= -=======> for commands or configurable options <======= - - directories: - TEXDIRW (Writable root): - !! default location: /usr/local/texlive/2008 - !! is not writable, please select a different one! - TEXMFLOCAL (directory for site-wide local files): - /usr/local/texlive/texmf-local - TEXMFSYSVAR (directory for variable and automatically generated data): - /usr/local/texlive/2008/texmf-var - TEXMFSYSCONFIG (directory for local config): - /usr/local/texlive/2008/texmf-config - TEXMFHOME (directory for user-specific files): - ~/texmf - - options: - [ ] use letter size instead of A4 by default - [X] create all format files - - set up for installing to hard disk - -Other actions: - start installation for running from DVD - help - quit -\end{boxedverbatim} -\caption{Menu principal après choix de l'option « \optname{running from DVD} »}% -\label{fig:main-fromdvd} -\end{figure} -Noter les changements : toutes les options concernant le choix du matériel à -installer, les liens symboliques, ont disparu. Le menu « Directories » -parle maintenant de \dirname{TEXDIRW} (racine accessible en écriture). - -L'exécution de \TL{} à partir du \DVD{} nécessite la création de quelques -répertoires mais un minimum de fichiers sont installés sur le disque dur. - -La configuration après installation pour Unix est un peu plus complexe, voir -section~\ref{sec:postinstall}. - -Faute de temps, cette option n'a pu être intégrée à l'interface graphique. -Elle reste utilisable en mode texte y compris sous Windows, voir -section~\ref{sec:cmdline}. - -La section \ref{sec:portable-unix} décrit une autre façon d'utiliser \TL{} à -partir du \DVD{}. Elle ne nécessite aucune modification du système mais ne -permet aucune personnalisation. - -\subsection{Options en ligne de commande} -\label{sec:cmdline} - -Taper -\begin{alltt} -> \Ucom{install-tl -help} -\end{alltt} -pour obtenir la liste de toutes les options disponibles. -Voici les principales : - -\begin{ttdescription} -\item[-gui] -- exécution en mode graphique (si possible). Ceci nécessite le - module Perl/Tk (\url{http://tug.org/texlive/distro.html#perltk}) ; si - Perl/Tk n'est pas disponible, l'installation se poursuit en mode texte. -\item[-no-gui] -- exécution en mode texte, même sous Windows ; - ceci est utile pour exécuter \TL{} à partir du \DVD{} (option non disponible - en mode graphique). -\item[-lang {\sl LL}] -- impose la langue utilisée dans les menus lors de - l'installation. Le code de langue comporte deux lettres. Sont actuellement - disponibles les langues suivantes : : anglais (\texttt{en}, langue par - défaut), allemand (\texttt{de}), français (\texttt{fr}), néerlandais - (\texttt{nl}), polonais (\texttt{pl}), Slovène (\texttt{sl}) et vietnamien - (\texttt{vi}). Le programme s'efforce de déterminer automatiquement - la langue à utiliser et se rabat sur l'anglais en cas d'échec. -\item[-profile {\sl profile}] -- à chaque exécution, le script d'installation - écrit un compte-rendu dans le fichier - \filename{texlive.profile} du répertoire \dirname{2008/tlpkg} ou - \dirname{tlpkg}. L'option \texttt{-profile} demande au script de réutiliser - le fichier \filename{texlive.profile}. En voici un extrait : - \begin{fverbatim} -# texlive.profile written on Wed Jul 9 16:13:44 2008 UTC -# It will NOT be updated and reflects only the -# installation profile at installation time. -selected_scheme scheme-basic -TEXDIR /usr/local/texlive/2008 -TEXDIRW /usr/local/texlive/2008 -... -TEXMFSYSVAR /usr/local/texlive/2008/texmf-var -collection-basic 1 -... -option_symlinks 0 - \end{fverbatim} - Il est ainsi facile de reproduire un même scéma d'installation sur plusieurs - machines. -\item [-location {\slshape url/path}] -- choix d'une source où récupérer le - matériel à installer. \label{item:location} - -L'argument de l'option \texttt{{\slshape url/path}} peut être une url -commençant par \texttt{ftp:}, \texttt{http:}, ou \texttt{file:/} ou bien un -chemin local. - -Si l'argument correspond à un chemin local (ou une url de type -\texttt{file:/}), le script recherche un sous-répertoire -\dirname{archive} contenant des fichiers compressés \filename{.tar.lzma}, -ceux-ci seront utilisés en priorité. - -Si l'argument est une url distante (\texttt{http:} ou \texttt{ftp:}) -le `\texttt{/}' final ainsi que la chaîne `\texttt{/tlpkg}' sont ignorés. -Par exemple, le choix du miroir \CTAN{} -\url{http://mirrors.ircam.fr/pub/CTAN/systems/texlive/tlnet/2008/} -est valide. La liste des miroirs \CTAN{} est ici : -\url{http://ctan.org/mirrors}. - -Lorsqu'aucune option \texttt{-location} n'est spécifiée, le script -d'installation choisit un miroir automatiquement, celui-ci servira -pour tout le téléchargement. -\end{ttdescription} - -\subsection{Terminer l'installation} -\label{sec:postinstall} - -Selon les cas quelques opérations supplémentaires peuvent être nécessaires. - -\subsubsection{Windows} - -Sous Windows, le programme d'installation s'occupe de tout (normalement). - -\subsubsection{Cas où des liens symboliques sont créés} - -Si vous avez opté pour l'option créant des liens symboliques (voir -section~\ref{sec:options}), il n'est pas nécessaire d'ajuster les variables -d'environnement. - -\subsubsection{Variables d'environnement Unix} -\label{sec:env} - -Le chemin des binaires correspondant à votre machine doit être ajouté à la -variable \envname{PATH}. À chaque architecture correspond un sous-répertoire -de \dirname{TEXDIR/bin}, voir la liste à la figure~\ref{fig:bin-text} -\pageref{fig:bin-text}. - -Si vous voulez que votre système trouve les fichiers de documentation -concernant \TL{}, il faut également ajuster les variables \envname{MANPATH} -et \envname{INFOPATH}. - -Pour les \textit{shells} dits « Bourne-compatible » tels que -\prog{bash} sous GNU/Linux, le fichier à éditer peut être -\filename{$HOME/.bash\_profile} ou \filename{$HOME/.profile} et les lignes à -ajouter sont de la forme suivante : - -\begin{sverbatim} -PATH=/usr/local/texlive/2008/bin/i386-linux:$PATH; export PATH -MANPATH=/usr/local/texlive/2008/texmf/doc/man:$MANPATH; export MANPATH -INFOPATH=/usr/local/texlive/2008/texmf/doc/info:$INFOPATH; export INFOPATH -\end{sverbatim} - -Pour les \textit{shells} \prog{csh} ou \prog{tcsh}, le fichier à éditer -est en principe \filename{$HOME/.cshrc} %$ -et les lignes à ajouter sont de la forme suivante : -\begin{sverbatim} -setenv PATH /usr/local/texlive/2008/bin/i386-linux:$PATH -setenv MANPATH /usr/local/texlive/2008/texmf/doc/man:$MANPATH -setenv INFOPATH /usr/local/texlive/2008/texmf/doc/info:$INFOPATH -\end{sverbatim} - -%$ - -\subsubsection{Variables d'environnement : configuration multi-utilisateur} -\label{sec:envglobal} - -Il est possible d'ajuster les variables \envname{PATH}, \envname{MANPATH} -et \envname{INFOPATH} globalement pour tous les utilisateurs présents et -futurs sans avoir à éditer les fichiers personnels de chacun mais les façons -de le faire sont trop différentes d'un système à l'autre pour être présentées -ici. - -Voici quelques pistes : pour \envname{MANPATH} chercher un fichier -\filename{/etc/manpath.config}, s'il est présent lui ajouter -des lignes du genre -\begin{sverbatim} -MANPATH_MAP /usr/local/texlive/2008/bin/i386-linux \ - /usr/local/texlive/2008/texmf/doc/man -\end{sverbatim} -Pour les deux autres, chercher un fichier\filename{/etc/environment}, il est -éventuellement possible d'y définir les valeurs des variables d'environnement -telles que \envname{PATH} et \envname{INFOPATH}. - -\subsubsection{Exécution à partir du DVD} - -Les programmes de \TL{} consultent le fichier \filename{texmf.cnf} pour savoir -dans quelles arborescences se trouvent les fichiers dont ils ont besoin. -Malheureusement, ceci ne fonctionne pas lorsque les programmes sont lancés à -partir d'un \DVD{} ; en effet certains chemins ne sont connus qu'à -l'installation et ne peuvent être inscrits sur le \DVD{} puisqu'il est -accessible uniquement en lecture. Il faut donc créer un fichier -\filename{texmf.cnf} sur le disque et préciser où il se trouve grâce à la -variable d'environnement \envname{TEXMFCNF}. Ceci ne dispense pas de -modifier la variable d'environnement \envname{PATH} comme indiqué ci-dessus. - -Le script d'installation affiche en fin de traitement, un message indiquant la -valeur à donner à la variable \envname{TEXMFCNF}. Si ce message vous a -échappé, cette valeur est \dirname{$TEXMFSYSVAR/web2c}, %$ -qui vaut par défaut \dirname{/usr/local/texlive/2008/texmf-var/web2c}. - -Voici les lignes à taper dans ce cas : -\begin{sverbatim} -TEXMFCNF=/usr/local/texlive/2008/texmf-var/web2c; export TEXMFCNF -\end{sverbatim} -ou pour [t]csh: -\begin{sverbatim} -setenv TEXMFCNF /usr/local/texlive/2008/texmf-var/web2c -\end{sverbatim} - -\subsubsection{\ConTeXt{} Mark IV} - -L'ancien \ConTeXt{} devrait fonctionner sans problème. La nouvelle version, -appelée « Mark IV » demande un peu de configuration spécifique, voir -\url{http://wiki.contextgarden.net/Running_Mark_IV}. - -\subsubsection{Ajout de fichiers locaux ou personnels} - -Comme cela a déjà été indiqué à la section~\ref{sec:texmftrees}, -\envname{TEXMFLOCAL} (par défaut \dirname{/usr/local/texlive/texmf-local} ou -\verb|C:\Program Files\texlive\texmf-local|) est la racine de -l'arborescence prévue pour regrouper les fichiers de macros, les fontes et le -matériel utilisable par l'ensemble des utilisateurs du système. -D'autre part \envname{TEXMFHOME} (par défaut \dirname{$HOME/texmf} %$ -(ou |%USERPROFILE%\texmf|) regroupe le matériel personnel de chaque -utilisateur. - -Dans les deux cas, les fichiers ajoutés doivent être placés, non pas en vrac à -la racine de \envname{TEXMFLOCAL} ou \envname{TEXMFHOME} mais dans des -sous-répertoires bien choisis (voir \url{http://tug.org/tds} ou lire le -fichier \filename{texmf.cnf}). Par exemple, une classe ou une extension -\LaTeX{} ne sera trouvée que si elle est dans \dirname{TEXMFLOCAL/tex/latex} ou -\dirname{TEXMFHOME/tex/latex} ou dans un sous-répertoire de ceux-ci. - -Enfin, si les ajouts ont été faits sous \envname{TEXMFLOCAL}, il y a lieu de -régénérer les bases de données \filename{ls-R} (commande \cmdname{mktexlsr} -ou bouton « Reinit file database » du programme \prog{tlmgr} -en mode graphique). - -L'emplacement des répertoires \envname{TEXMFLOCAL} et \envname{TEXMFHOME} est -fixe (il ne change pas d'une version à l'autre de \TL{}). Leur contenu est -pris en compte par toutes les versions de \TL{} aussi est-il préférable de ne -pas changer la valeur des variables \envname{TEXMFLOCAL} et \envname{TEXMFHOME} -à l'installation. - - -\subsubsection{Ajout de fontes externes à \TL{}} - -Cette question est malheureusement trop complexe pour être abordée ici. -Renoncez-y sauf si connaissez bien les arcanes d'une installation \TeX. -Vérifiez en premier lieu ce qui existe déjà en libre : voir la -section~\ref{sec:tl-fonts}. - -Une alternative possible est d'utiliser \XeTeX (voir -section~\ref{sec:tex-extensions}) qui permet l'accès aux fontes disponibles -sur le système sans aucune installation supplémentaire. - - -\subsection{Tester l'installation} -\label{sec:test-install} - -Une fois l'installation de \TL{} terminée, il faut la tester avant de créer -des documents ou des fontes. Les tests doivent être faits par un utilisateur -non privilégié (autre que \textit{root}). - -On donne ici quelques procédures de base pour vérifier que le nouveau -système est opérationnel. On les décrit pour Unix ; pour \MacOSX{} ou -Windows, il vaut mieux tester au travers d'une interface graphique -mais les principes sont les mêmes. - -\begin{enumerate} - -\item S'assurer en premier lieu que le programme \cmdname{tex} fonctionne : - -\begin{alltt} -> \Ucom{tex -{}-version} -TeX 3.1415926 (Web2C 7.5.7) -kpathsea version 3.5.7 -... -\end{alltt} - -Si la réponse est \texttt{command not found} ou si le numéro de version est -différent, il est fort probable que vous n'avez pas le bon répertoire -de binaires dans votre \envname{PATH}. -Voir les informations sur l'environnement page~\pageref{sec:env}. - -\item Traiter un fichier \LaTeX{} simple : - -\begin{alltt} -> \Ucom{latex sample2e.tex} -This is pdfeTeXk, Version 3.1415926... -... -Output written on sample2e.dvi (3 pages, 7484 bytes). -Transcript written on sample2e.log. -\end{alltt} -Si le fichier \filename{sample2e.tex} ou d'autres ne sont pas trouvés, -il y a probablement des interférences avec vos anciennes variables -d'environnement ou fichiers de configuration. Pour analyser en détail -votre problème, vous pouvez demander à \TeX{} de dire exactement ce -qu'il cherche et trouve ; voir la section~\ref{sec:debugging} -page~\pageref{sec:debugging}. - -\item Prévisualiser les résultats en ligne : -\begin{alltt} -> \Ucom{xdvi sample2e.dvi} -\end{alltt} -Sous Windows, la commande équivalente est \cmdname{dviout}. -Une nouvelle fenêtre doit s'ouvrir et montrer un joli document expliquant les -bases de \LaTeX{} (document dont la lecture attentive est recommandée si vous -êtes débutant !). -Vous devez travailler sous X pour que \cmdname{xdvi} fonctionne. Sinon, votre -variable d'environnement \envname{DISPLAY} n'est pas correcte et vous -aurez une erreur \samp{Can't open display}. - -\item Créer un fichier \PS{} pour l'imprimer ou l'afficher : - -\begin{alltt} -> \Ucom{dvips sample2e.dvi -o sample2e.ps} -\end{alltt} - -\item Créer un fichier \acro{PDF} au lieu de \dvi{} ; -cet exemple traite le fichier \filename{sample2e.tex} et crée directement -du \acro{PDF} : - -\begin{alltt} -> \Ucom{pdflatex sample2e.tex} -\end{alltt} - -\item Prévisualiser le fichier \acro{PDF} : - -\begin{alltt} -> \Ucom{gv sample2e.pdf} -\textrm{ou} -> \Ucom{xpdf sample2e.pdf} -\end{alltt} - -Hélas, ni \cmdname{gv} ni \cmdname{xpdf} ne sont actuellement inclus dans -\TL{}, aussi devez-vous les installer séparément si ce n'est déjà fait. -Voir respectivement -\url{http://www.gnu.org/software/gv} et -\url{http://www.foolabs.com/xpdf} (il y a bien d'autres lecteurs de -fichiers \acro{PDF}). - -\item Autres fichiers de tests utiles en plus de \filename{sample2e.tex} : - -\begin{ttdescription} - -\item [small2e.tex] à compiler avant \filename{sample2e} si celui-ci pose des - problèmes. - -\item [testpage.tex] teste que l'imprimante n'introduit pas de décalages. - -\item [nfssfont.tex] imprime des tables des fontes et des tests. -\item [testfont.tex] aussi pour les tables de fontes mais en (plain)\TeX. -\item [story.tex] le fichier de test de (plain)\TeX{} le plus canonique -de tous. Il faut taper \samp{\bs bye} à la commande \code{*} après -\samp{tex story.tex}. - -\end{ttdescription} -Pour exécuter ces tests procéder comme pour \filename{sample2e.tex}. - -\end{enumerate} - -Si vous êtes débutant ou si vous avez besoin d'aide pour réaliser des -documents \TeX{} ou \LaTeX{}, n'hésitez pas à consulter -\url{http://tug.org/begin.html}. -On vous recommande également l'introduction à \LaTeX{} de Tobias Oetiker -dans sa version anglaise (la version française n'est plus à jour) -disponible après installation sous -\url{texmf-doc/doc/english/lshort-english/lshort.pdf}. - -\section{Utilisation de \TL{} en réseau} -\label{sec:netinstall} - -\TL{} a été conçu comme un système multi-utilisateurs capable de fonctionner -en réseau. Un même serveur peut proposer la distribution \TL{} à différentes -machines, éventuellement d'architectures différentes, il suffit que le serveur -possède les répertoires de binaires adéquats. - -La seule chose à faire par chaque utilisateur local ou distant est d'ajouter -le chemin des exécutables correspondant à son architecture dans son -\envname{PATH}% -\footnote{Plus précisément \emph{en tête} du \envname{PATH} s'il y a d'autres - binaires \TeX{} en concurrence.}. - -Ceci fonctionne parce que les répertoires de recherche des fichiers utilisés -par \TL{} (\envname{TEXMFMAIN}, \envname{TEXMFDIST}, \envname{TEXMFSYSVAR}, -\envname{TEXMFSYSCONFIG} et \envname{TEXMFLOCAL} sont définis -\emph{relativement aux exécutables} lors de l'installation (voir dans le fichier -\filename{TEXMFMAIN/web2c/texmf.cnf} le rôle de la variable -\envname{\$SELFAUTOPARENT}). %$ - -Cette disposition permet aussi de faire une installation sur une machine et -de la déplacer après coup sur un serveur, la seule chose à changer est le -contenu de la variable \envname{PATH}. - -Ce qui précède vaut pour les utilisateurs d'Unix. -Pour ceux qui sont sous Windows, le répertoire -\dirname{texmf-doc/source/texlive/texlive-common/w32client} -contient un exemple de script \filename{install-w32client} qui permet -de partager une installation \TL{} à travers un réseau local. Il se lance -par l'intermédiaire du fichier « batch » -\filename{install-w32client.bat} qui se trouve dans le même répertoire. - -De plus amples informations sur la configuration de \TL{} et sur la recherche -de fichiers sont disponibles à la section~\ref{sec:kpathsea}. - -\section{\TL{} sur une machine hôte (DVD ou USB)} -\label{sec:portable-unix} - -L'utilisation de \TL{} à partir du \DVD{} décrite à la -section~\ref{sec:fromdvd} impose la création de quelques répertoires sur le -disque dur, ce qui n'est pas gênant sur une machine personnelle. En revanche, -lorsqu'on travaille sur une machine hôte, il est préférable de limiter les -ajouts et modifications à faire sur le disque dur. - -Les scripts \filename{tl-portable} (pour Unix) et \filename{tl-portable.bat} -pour Windows, présents à la racine de \TL{} (ou dans le répertoire -\dirname{texlive} du \DVD \TK) facilitent l'utilisation de \TL{} sur des -machines hôtes. Lors de leur première exécution, ces scripts créent un -répertoire \dirname{~/.tlportable2008} contenant divers fichiers de -configuration qui permettront l'accès à la distribution \TL{} du \DVD. -Ceci peut prendre un peu de temps mais lors des exécutions -suivantes le démarrage est presque immédiat. Rien n'est modifié sur la machine -en dehors du répertoire \dirname{~/.tlportable2008}. - -Pour qu'un éditeur prenne en compte la distribution \TL{} du \DVD, il suffit -de le lancer par l'intermédiaire du script \filename{tl-portable}. - -Le script \filename{tl-portable} est utile aussi pour créer une distribution -\TL{} sur une clé \acro{USB}. Pour ce faire, copier sur la clé les fichiers -et les répertoires situés à la racine de \TL{} (au moins \dirname{bin}, -\dirname{texmf}, \dirname{texmf-dist} et \dirname{tlpkg}). Si la clé est -formatée en \acro{FAT32}, attention aux liens symboliques (utiliser \code{cp - -L} pour copier). Il est possible d'ajouter un répertoire -\dirname{texmf-local} sur la clé, il sera pris en compte à l'exécution. Il -reste à lancer le script \filename{tl-portable} à la racine de la clé comme -ci-dessus ; celle-ci étant accessible en écriture, lors des exécutions de \TL{} -tous les fichiers seront créés sur elle et rien ne sera écrit sur le -disque dur. - -\section{Maintenance de l'installation avec \cmdname{tlmgr}} -\label{sec:tlmgr} - -\begin{figure}[tb] -\centering -\tlpng{tlmgr-gui}{\linewidth} -\caption{\prog{tlmgr} en mode graphique (après clic sur le bouton « Load »).}% -\label{fig:tlmgr-gui} -\end{figure} - -\begin{figure}[tb] -\centering -\tlpng{tlmgr-config}{\linewidth} -\caption{\texttt{tlmgr} en mode graphique, onglet « configuration »}% -\label{fig:tlmgr-config} -\end{figure} - -Un nouveau programme appelé \prog{tlmgr} est installé avec la -distribution \TL. Il fournit une interface conviviale pour la -maintenance de la distribution. Les programmes \prog{updmap}, -\prog{fmtutil} et \prog{texconfig} ont été conservés et le seront à -l'avenir bien que \prog{tlmgr} soit appelé à devenir l'interface -standard de configuration. -\prog{tlmgr} permet en particulier -\begin{itemize} -\item de voir la liste de toutes les collections et extensions - disponibles, avec la mention \texttt{(i)} pour celles qui sont installées ; -\item d'installer, de mettre à jour ou de désinstaller tel ou tel composant, - en respectant les dépendances (sauf si l'utilisateur le refuse) ; -\item de rechercher des extensions ; -\item de voir la liste des binaires disponibles et d'en installer ; -\item de modifier la configuration (taille du papier, choix du - répertoire source pour le téléchargement voir option \texttt{-location} - page~\pageref{item:location}, etc.). -\end{itemize} -\textit{Attention :} \prog{tlmgr} ne doit pas être utilisé lorsque \TL{} est -exécuté à partir du \DVD{} (sans installation sur le disque dur). - -\subsection{\cmdname{tlmgr} en mode graphique} - -\prog{tlmgr} est lancé en mode graphique par la commande -\begin{alltt} -> \Ucom{tlmgr -gui} -\end{alltt} -ou sous Windows dans le menu « Démarrer » : \texttt{Démarrer} $\rightarrow$ -\texttt{Programmes} $\rightarrow$ \texttt{TeX Live 2008} $\rightarrow$ -\texttt{TeX Live Manager}. - -La première chose à faire est de cliquer sur le bouton « Load% -\footnote{Dans la description qui suit, le nom des boutons est celui de la - version anglaise par souci de cohérence avec les figures. L'affichage se - fait normalement dans la langue de l'utilisateur (variable \envname{LANG} - sous Unix).} » ce qui affiche la liste des collections, extensions, etc. ; -le préfixe \texttt{(i)} indique celles qui sont déjà installées. - -La figure~\ref{fig:tlmgr-config} présente l'onglet « configuration ». - -\subsection{Exemples d'utilisation de \cmdname{tlmgr} - en ligne de commande} - -Premier exemple : ajout de la collection « xetex » et de l'extension « xkeyval » -qui devront être téléchargées à partir d'un site spécifié. La commande - -\begin{alltt} -> \Ucom{tlmgr -location http://172.16.18.1/tldev install collection-xetex xkeyval} -\end{alltt} -retourne -\begin{fverbatim} -install: collection-xetex -install: arabxetex -install: euenc -install: bidi -install: fontspec -install: fontwrap -install: ifxetex -install: philokalia -install: polyglossia -install: xecyr -install: xecyr.i386-linux -install: xepersian -install: xetex -install: xetexconfig -install: xetex.i386-linux -running post install action for xetex -install: xetex-def -install: xetex-pstricks -install: xetexfontinfo -install: xltxtra -install: xunicode -install: xkeyval -running mktexlsr -mktexlsr: Updating /usr/local/texlive/2008/texmf/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-config/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-dist/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-doc/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/../texmf-local/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-var/ls-R... -mktexlsr: Done. -regenerating fmtutil.cnf -running fmtutil-sys --missing -... -Transcript written on xelatex.log. -fmtutil: /usr/local/texlive/2008/texmf-var/web2c/xetex/xelatex.fmt installed. -\end{fverbatim} -Le programme \prog{tlmgr} prend en compte les dépendances et effectue -automatiquement toutes les opérations nécessaires comme la mise à jour des -bases de données et la génération de formats (ici un nouveau format a été créé -pour \XeTeX). - -Deuxième exemple : ajout d'une langue de travail (néerlandais) ; ceci provoque -la régénération de plusieurs formats. -\begin{alltt} -> \Ucom{tlmgr install collection-langdutch} -\end{alltt} - -La demande de description de l'extension « collection-wintools » -\begin{alltt} -> \Ucom{tlmgr show collection-wintools} -\end{alltt} -retourne -\begin{fverbatim} -Package: collection-wintools -Category: Collection -ShortDesc: Windows support programs -LongDesc: Utilities for Windows, since they are not readily available there: - gzip, chktex, jpeg2ps, unzip, wget, xpdf. -Installed: Yes -\end{fverbatim} - -Mise à jour complète de l'installation avec les dernières versions disponibles : -\begin{alltt} -> \Ucom{tlmgr update -all} -\end{alltt} -ou juste pour voir ce qui se passerait en cas de mise à jour complète : -\begin{alltt} -> \Ucom{tlmgr update -all -dry-run} -\end{alltt} -ou bien -\begin{alltt} -> \Ucom{tlmgr update -list} -\end{alltt} - -Documentation complète de \prog{tlmgr} : -\begin{alltt} -> \Ucom{tlmgr -help} -\end{alltt} - -\section{Spécificités Windows} -\label{sec:windows} - -Le nouveau programme d'installation de \TL{} est conçu pour -fonctionner aussi bien sous Unix que sous Windows. Ceci nous a -obligés à nous limiter à Windows 2000 et à ses successeurs (XP, Vista), -au détriment des anciennes versions (9\textit{x}, ME et NT). - -\subsection{Installation} -\label{sec:winfeatures} - -Sous Windows le programme d'installation effectue quelques tâches -supplémentaires : -\begin{description} -\item[Menus et raccourcis] -- un sous-menu «\TL{}» est ajouté au menu - « Démarrer », il contient des entrées pour les programmes \prog{tlmgr}, - \prog{texdoctk}, PS\_View et pour de la documentation. - Une icône PS\_View est ajoutée sur le bureau, il suffit d'y déposer un - fichier PostScript pour provoquer son affichage. -\item[Variables d'environnement] -- leurs valeurs sont préremplies - automatiquement sans intervention de l'utilisateur. -\item[Désinstallation] -- une entrée est ajoutée pour \TL{} dans le menu - « Ajout et suppression de programmes ». -\end{description} - -\subsection{Programmes supplémentaires} - -\begin{figure}[tb] -\centering -\tlpng{psview}{.6\linewidth} -\caption{PS\_View: de très forts grossissements sont possibles !}% -\label{fig:psview} -\end{figure} - -L'installation de \TL{} ajoute quelques utilitaires non fournis en standard -avec Windows : -\begin{description} -\item[Perl et Ghostscript] -- \TL{} installe des copies « cachées » de ces - programmes : ce sont des versions spécifiques adaptées à \TL{}, elles - sont invisibles hors de \TL{} et n'interfèrent donc en aucune façon avec - d'autres versions éventuellement présentes sur la machine. -\item[Outils en ligne de commande] -- des versions pour Windows de programmes - Unix sont installées, en particulier \cmdname{gzip}, \cmdname{chktex}, - \cmdname{jpeg2ps}, \cmdname{unzip}, \cmdname{wget} et quelques utilitaires - de la suite \cmdname{xpdf} (\cmdname{xpdf} lui-même n'est pas disponible - sous Windows mais le visualiseur \acro{PDF} Sumatra en est dérivé, voir - \url{http://blog.kowalczyk.info/software/sumatrapdf}). -\item[\texttt{fc-cache}] -- facilite l'accès aux fontes système pour \XeTeX. -\item[PS\_View] -- nouveau visualiseur PostScript sous licence libre, - voir figure~\ref{fig:psview}. -\item[Répertoire \texttt{support}] -- ce répertoire, déjà mentionné à la - section~\ref{sec:tld}, contient divers programmes éventuellement utiles - comme des éditeurs adaptés aux fichiers \TeX{} ou le visualiseur Dviout - présenté à la section suivante. Ces programmes ne sont - pas installés automatiquement par la commande \prog{install-tl}. -\end{description} - -\subsection{Visualiseur Dviout} - -Cette année, la distribution \TL{} ne contient malheureusement pas de -visualiseur \dvi{} pour Windows. Le programme \prog{dviout} de -Toshio Oshima est disponible dans le répertoire \path{support/dviout/}, il est -accompagné d'un fichier \filename{README} (à lire attentivement) décrivant -l'installation et la configuration de \prog{dviout} pour \TL. - -Lors des premières exécutions de \cmdname{dviout}, de nombreuses fontes sont -créées à la volée pour l'écran utilisé. Ceci prend un peu de temps mais se -produit de plus en plus rarement au fur et à mesure des utilisations. -Une bonne aide en ligne est disponible. - -\subsection{Téléchargement de logiciels supplémentaires} - -Voici quelques liens vers des sites proposant des outils intéressants : -\begin{description} -\item[Ghostscript] -- \url{http://www.cs.wisc.edu/~ghost/} ; -\item[Perl] -- \url{http://www.activestate.com/} et \acro{CPAN} - \url{http://www.cpan.org/} ; -\item[ImageMagick] -- \url{http://www.imagemagick.com} pour l'affichage et la - conversion d'images ; -\item[NetPBM] -- \url{http://netpbm.sourceforge.net/} un concurrent du - précédent ; -\item[Éditeurs orientés \TeX] -- le choix est large, en voici une sélection : - \begin{itemize} -% \item \cmdname{GNU Emacs} disponible sous Windows, see -% \url{http://www.gnu.org/software/emacs/windows/ntemacs.html} ; - \item \cmdname{Emacs} avec Auc\TeX\ pour Windows disponible dans le - répertoire \path{support} de \TL{} ; le site de référence est - \url{http://www.gnu.org/software/auctex} ; - \item \cmdname{WinShell} disponible également dans le répertoire - \path{support} ; le site de référence est \url{http://www.winshell.de} ; - \item \cmdname{WinEdt} est un \textit{shareware}, voir - \url{http://www.winedt.com} ; - \item TeXnicCenter est libre, il est disponible sur - \url{http://www.toolscenter.org} et dans la distribution \ProTeXt{} ; - \item \cmdname{Vim} est libre, voir \url{http://www.vim.org} ; - \item \cmdname{LEd} voir \url{http://www.ctan.org/support/LEd} ; - \item \cmdname{SciTE} voir - \url{http://www.scintilla.org/SciTE.html}. - \end{itemize} -\end{description} - - -\subsection{Répertoire personnel} -\label{sec:winhome} - -L'équivalent du répertoire personnel noté \envname{\$HOME} sous -Unix s'appelle \verb|%USERPROFILE%| sous Windows. % -Cette variable vaut en général -\verb|C:\Documents and Settings\| sous Windows XP et 2000 -et \verb|C:\Utilisateurs\| sous Vista. -La notation \verb|~|, utilisée dans \filename{texmf.cnf} et dans \KPS{} en -général pour désigner un répertoire personnel, est correctement interprétée -sous Windows comme sous Unix. - - -\subsection{Base de registre Windows} -\label{sec:registry} - -% (df) Je ne vois pas bien l'utilité de cette section... - -Windows stocke pratiquement tous les paramètres de configuration dans sa base -de registres. Celle-ci contient un ensemble de clés organisées par niveau. -Les clés les plus importantes pour l'installation de programmes sont -\path{HKEY_CURRENT_USER} et \path{HKEY_LOCAL_MACHINE}, \path{HKCU} et -\path{HKLM} en abrégé. La partie \path{HKCU} de la base de registres -se trouve dans le répertoire personnel de l'utilisateur (voir -section~\ref{sec:winhome}). La partie \path{HKLM} est normalement dans un -sous-répertoire du répertoire Windows. - -Certaines informations système peuvent s'obtenir à partir des variables -d'environnement mais pour d'autres, la localisation des raccourcis par -exemple, la consultation de la base de registre est indispensable. -La modification des variables d'environnement nécessite l'accès à la base de -registre. - - -\subsection{Droits d'accès sous Windows} -\label{sec:winpermissions} - -Dans les versions récentes de Windows, la distinction est faite entre -« utilisateurs » et « administrateurs », ces derniers ayant accès en écriture -à la totalité du système. En pratique on devrait plutôt parler d'utilisateurs -« non privilégiés » et d'utilisateurs « normaux » car être « administrateur » -est la règle et non l'exception. - -Nous nous sommes efforcés de rendre l'installation de \TL{} possible aux -utilisateurs non privilégiés. - -Si celui qui fait l'installation est « administrateur », les raccourcis -et les entrées des menus sont créés pour tous les utilisateurs ; -sinon, seul celui qui a fait l'installation aura accès à ces éléments. -L'option \optname{non-admin} du programme \prog{install-tl} permet à un -« administrateur » de faire une installation comme utilisateur non privilégié. - -Dans tous les cas, le répertoire proposé comme racine de l'installation est -\verb|%PROGRAMFILES%|. % -Le programme \prog{install-tl} vérifie si le répertoire choisi comme racine -est accessible en écriture pour celui qui procède à l'installation. - -Lorsqu'une installation \TeX{} est présente sur la machine, l'installation -de \TL{} par un utilisateur non privilégié est problématique : -cet utilisateur n'aura jamais accès aux exécutables \TL{} car la recherche -s'effectue d'abord dans les répertoires système, puis dans les répertoires de -l'utilisateur. Une parade sommaire a été prévue : les raccourcis intègrent -dans ce cas le chemin complet des exécutables qu'ils représentent. La -distribution \TL{} est ainsi utilisable en ligne de commande à partir de ces -raccourcis. - - -\section{Guide d'utilisation du système Web2C} - -\Webc{} est une collection intégrée de programmes relatifs à \TeX, -c.-à-d. \TeX{} lui-même, \MF{}, \MP, \BibTeX{}, etc. -C'est le cÅ“ur de \TL{}. Le site de référence est \url{http://tug.org/web2c}. - -Un peu d'histoire : la première implémentation a été réalisée par Tomas -Rokicki qui, en 1987, a développé un premier système \TeX{}-to-C en adaptant -les \textit{change files} pour Unix (travail de Howard Trickey et Pavel Curtis -principalement). Tim Morgan assura la maintenance du système, dont le nom fut -remplacé durant cette période par Web-to-C. En 1990, Karl Berry reprit le -travail, assisté par des dizaines de contributeurs et en 1997 il passa le -relais à Olaf Weber qui le rendit à Karl en 2006. - -Le système \Webc{} fonctionne sur Unix, sur les systèmes Windows 32 bits, -sur \MacOSX{} et sur de nombreux autres systèmes d'exploitation. Il utilise les -sources originales de Knuth pour \TeX{} et les autres programmes de base -écrits en \web{} (système de programmation documentée) qui sont tous traduits -en langage C. Les composants du noyau de \TeX{} issus de ce processus sont : - -\begin{description} -\item[bibtex] -- gère les bibliographies. -\item[dmp] -- \cmdname{troff} vers MPX (dessins \MP{}). -\item[dvicopy] -- copie le fichier \dvi{} en supprimant les fontes virtuelles. -\item[dvitomp] -- convertit le fichier \dvi{} en MPX (dessins \MP{}). -\item[dvitype] -- convertit le fichier \dvi{} en un texte lisible. -\item[gftodvi] -- visualisation de fontes génériques GF. -\item[gftopk] -- convertit les fontes génériques GF en fontes bitmap PK. -\item[gftype] -- convertit le fichier GF en un texte lisible. -\item[makempx] -- typographie des étiquettes \MP{}. -\item[mf] -- création de fontes. -\item[mft] -- mise en page de code source \MF{}. -\item[mpost] -- création de diagrammes techniques. -\item[mpto] -- extraction d'étiquettes \MP{}. -\item[newer] -- comparaison de dates de modification (fichiers). -\item[patgen] -- création de motifs de césure. -\item[pktogf] -- convertit les fontes bitmap PK en fontes génériques GF. -\item[pktype] -- convertit les fontes PK en un texte lisible. -\item[pltotf] -- convertit les fichiers PL (lisibles) en TFM. -\item[pooltype] -- affiche les fichiers \web{} pool. -\item[tangle] -- \web{} vers Pascal. -\item[tex] -- composition de textes. -\item[tftopl] -- convertit les fichiers TFM en PL (lisibles). -\item[vftovp] -- convertit les fontes virtuelles VF en VPL (lisibles). -\item[vptovf] -- convertit les fontes VPL en fontes virtuelles VF. -\item[weave] -- \web{} vers \TeX. -\end{description} - -La syntaxe et les fonctions précises de ces programmes sont décrites dans -la documentation des composants individuels et dans le manuel \Webc{} -lui-même. Toutefois, connaître un certain nombre de principes régissant -l'ensemble de la famille de programmes peut aider à exploiter de façon -optimale votre installation \Webc{}. - - Presque tous ces programmes suivent les options standard de \GNU : -\begin{description} - \item[\texttt{-{}-help}] imprime le sommaire de l'utilisation, - \item[\texttt{-{}-verbose}] imprime le rapport détaillé du processus, - \item[\texttt{-{}-version}] imprime seulement le numéro de version. -\end{description} - -Pour localiser les fichiers, les programmes \Webc{} utilisent la bibliothèque -de recherche \KPS{} (\url{http://tug.org/kpathsea}). Cette bibliothèque -utilise une combinaison de variables d'environnement et un certain nombre de -fichiers de paramètres pour optimiser la recherche dans l'énorme arborescence -\TeX{}. \Webc{} peut exécuter une recherche dans plusieurs arborescences -simultanément, ce qui est utile si l'on souhaite maintenir la distribution -standard de \TeX{} et les extensions locales dans deux arborescences -distinctes. Afin d'accélérer la recherche de fichiers, la racine de chaque -arborescence possède un fichier \file{ls-R} contenant une entrée donnant le -nom et le chemin de chaque fichier situé sous la racine. - -\subsection{Kpathsea et la recherche de fichiers} -\label{sec:kpathsea} - -Décrivons en premier lieu le mécanisme de recherche de la bibliothèque \KPS{}. - -Nous appelons \emph{chemin de recherche} une liste, séparée par -« deux-points» ou « point-virgule», d'éléments, appelés -\emph{éléments de chemin}, qui sont des noms de répertoires. -Un chemin de recherche peut provenir de plusieurs sources. -Pour rechercher un fichier \samp{my-file} le long -d'un chemin \samp{.:/dir}, \KPS{} vérifie chaque élément du chemin : -d'abord \filename{./my-file}, puis \filename{/dir/my-file} et renvoie la -première occurrence (voire toutes). - -Afin d'optimiser l'adaptation à tous les systèmes d'exploitation, \KPS{} peut -utiliser dans les noms de fichiers des séparateurs différents de deux-points -(\samp{:}) et barre oblique (\samp{/}) pour les systèmes non-Unix. - -Pour vérifier un élément de chemin particulier \var{p}, \KPS{} -vérifie d'abord si une base de données existante (voir -page~\pageref{sec:filename-database}) contient \var{p}, -c.-à-d. si la base de données se trouve dans un -répertoire qui est un préfixe de \var{p}. Si oui, la spécification -du chemin est comparée avec le contenu de la base de données. - -Si la base de données n'existe pas, si elle ne s'applique pas à cet élément de -chemin ou si elle ne contient aucune correspondance, la recherche est lancée -sur tout le système de fichiers (si cela n'a pas été interdit par une commande -commençant par \samp{!!} et si le fichier cherché est censé exister). \KPS{} -construit la liste de répertoires qui correspondent à cet élément de chemin, -puis cherche le fichier dans chaque élément de cette liste. - -La condition « le fichier est censé exister » est liée aux fichiers~\samp{.vf} -et aux fichiers d'entrée lus par la commande \TeX\ \cs{openin}. De tels -fichiers peuvent ne pas exister (par exemple \file{cmr10.vf}), il est donc -inutile de les rechercher sur le disque. De plus, si vous n'actualisez pas le -fichier \file{ls-R} lors de l'installation d'un nouveau fichier \samp{.vf}, il -ne sera jamais trouvé. Chaque élément de chemin est alors vérifié : d'abord -dans la base de données puis sur le disque. Si une occurrence est trouvée, la -recherche s'arrête et le résultat est obtenu. - -Bien que l'élément de chemin le plus simple et le plus fréquent soit un nom de -répertoire, \KPS{} supporte d'autres types d'éléments dans les chemins de -recherche : des valeurs par défaut différentes pour chaque programme, des noms -de variables d'environnement, des valeurs de fichiers de configuration, les -répertoires de l'utilisateur et la recherche récursive de -sous-répertoires. Nous disons alors que \KPS{} \emph{étend} un élément, -c'est-à-dire que \KPS{} transforme toutes ces spécifications en noms de -répertoires de base. Cette opération est décrite dans les sections suivantes. - -Notons que si le nom de fichier cherché est absolu ou explicitement -relatif, c'est-à-dire commençant par \samp{/}, \samp{./} ou -\samp{../}, \KPS{} ne vérifie que l'existence de ce fichier. -\ifSingleColumn -\else -\begin{figure*} -\centering -\verbatiminput{examples/ex5.tex} -\setlength{\abovecaptionskip}{0pt} - \caption{Un exemple de fichier de configuration} - \label{fig:config-sample} -\end{figure*} -\fi - -\subsubsection{Les différentes sources} -\label{sec:path-sources} - -Un chemin de recherche peut provenir de plusieurs sources. Voici l'ordre -dans lequel \KPS\ les utilise. - -\begin{enumerate} -\item Une variable d'environnement définie par l'utilisateur, par exemple - \envname{TEXINPUTS}. Les variables d'environnement avec une extension - attachée (nom de programme) sont d'abord prises en compte : par exemple, si - \samp{latex} est le nom du programme exécuté, \envname{TEXINPUTS.latex} - passera avant \envname{TEXINPUTS}. -\item Un fichier de configuration de programme spécifique, par exemple une - ligne « \texttt{S /a:/b} » dans le fichier \file{config.ps} de - \cmdname{dvips}. -\item Un fichier de configuration \file{texmf.cnf} de \KPS{} contenant une - ligne telle que \\ \samp{TEXINPUTS=/c:/d} (voir ci-dessous). -\item La valeur par défaut obtenue à la compilation. -\end{enumerate} -\noindent On peut voir chacune de ces valeurs pour un chemin de recherche -donné en utilisant l'option de débogage (voir page~\pageref{sec:debugging}). - -\subsubsection{Fichiers de configuration} - -\begingroup\tolerance=3500 -\KPS{} lit dans les \emph{fichiers de configuration à - l'exécution} appelés \file{texmf.cnf} les chemins de recherche et -d'autres définitions. Le chemin pour accéder à ces fichiers dans -l'arborescence est stocké dans la variable \envname{TEXMFCNF} -(par défaut ces -fichiers se trouvent dans le sous-répertoire \file{texmf/web2c}). -\emph{Tous} les fichiers \file{texmf.cnf} se trouvant dans le chemin -de recherche vont être lus et les définitions provenant -de fichiers précédents écraseront celles des fichiers suivants. Par -exemple, avec un chemin tel que \verb|.:$TEXMF|, les définitions du -fichier \filename{./texmf.cnf} écrasent celles de -\verb|$TEXMF/texmf.cnf|. -\endgroup - -\begin{itemize} -\item Les commentaires sont signalés par un \texttt{\%} et se terminent à la - fin de la ligne. -\item Les lignes vides sont ignorées. -\item Un \bs{} à la fin d'une ligne joue le rôle d'un lien entre deux lignes, - c'est-à-dire que la ligne courante se poursuit à la ligne suivante. Dans ce - cas, les espaces présents au début de la ligne suivante ne sont pas ignorés. -\item Toutes les autres lignes sont de la forme : -\begin{alltt} - \emph{variable}[.\emph{progname}] [=] \emph{value} -\end{alltt}% - où le \samp{=} et les espaces autour sont optionnels. -\item Le nom de la \ttvar{variable} peut contenir n'importe quel caractère - autre que les espaces, \samp{=}, ou \samp{.} mais on recommande d'utiliser - \samp{A-Za-z\_} pour éviter les problèmes. -\item Si \samp{.\var{progname}} est présent, sa définition s'applique - seulement si le programme exécuté se nomme \texttt{\var{progname}} ou - \texttt{\var{progname}.exe}. Ceci permet par exemple à différentes variantes - de \TeX{} d'avoir des chemins de recherche différents. -\item \var{value} peut contenir n'importe quel caractère excepté \code{\%} et - \samp{@}. L'option \code{\$\var{var}.\var{prog}} n'est pas disponible à - droite du signe \samp{=} ; à la place, on doit utiliser une variable - supplémentaire. Un \samp{;}\ dans \var{value} est compris comme un \samp{:}\ - si on travaille sous Unix ; ceci est très utile et permet d'avoir un seul - \file{texmf.cnf} pour les systèmes Unix, \acro{MS-DOS} et Windows. -\item Toutes les définitions sont lues avant tout désarchivage ou - décompactage, de telle façon que les variables peuvent être référencées - avant d'être définies. -\end{itemize} -Voici un fichier de configuration illustrant les points précédents -\ifSingleColumn - -%\verbatiminput{examples/ex5.tex} % trop petit (df) -\begin{verbatim} -TEXMF = {$TEXMFLOCAL,!!$TEXMFMAIN} -TEXINPUTS.latex = .;$TEXMF/tex/{latex,generic;}// -TEXINPUTS.fontinst = .;$TEXMF/tex//;$TEXMF/fonts/afm// -% e-TeX related files -TEXINPUTS.elatex = .;$TEXMF/{etex,tex}/{latex,generic;}// -TEXINPUTS.etex = .;$TEXMF/{etex,tex}/{eplain,plain,generic;}// -\end{verbatim} - -\else -dans la figure~\ref{fig:config-sample}. -\fi - -\subsubsection{Expansion d'un chemin de recherche} -\label{sec:path-expansion} - -\KPS{} reconnaît certains caractères et constructions spéciales dans -les chemins de recherche, semblables à ceux disponibles dans les -\textit{shells} Unix. Ainsi, le chemin complexe, -\verb+~$USER/{foo,bar}//baz+ %$ -étend la recherche vers tous les sous-répertoires situés sous les -répertoires \file{foo} et \file{bar} dans le répertoire utilisateur -\texttt{\$USER} contenant un répertoire ou un fichier appelé %$ -\file{baz}. Ces expansions sont explicitées dans les sections -suivantes. - -\subsubsection{Expansion par défaut} -\label{sec:default-expansion} - -\tolerance=2500 -Si le chemin de recherche le plus prioritaire (voir -section~\ref{sec:path-sources}) contient un \samp{:} -\emph{supplémentaire} (c.-à-d. en début ou fin de ligne ou -double), \KPS{} insère à cet endroit le chemin suivant dont la -priorité définie est immédiatement inférieure. Si ce chemin inséré -possède un \samp{:} supplémentaire, le même processus se -répète pour le chemin prioritaire suivant. -Par exemple, étant donné une variable d'environnement définie ainsi - -\tolerance=1500 - -\begin{alltt} -> \Ucom{setenv TEXINPUTS /home/karl:} -\end{alltt} -la valeur de \code{TEXINPUTS} d'après le fichier \file{texmf.cnf} étant - -\begin{alltt} - .:\$TEXMF//tex -\end{alltt} -alors la valeur finale utilisée pour la recherche sera - -\begin{alltt} - /home/karl:.:\$TEXMF//tex -\end{alltt} - -Comme il est inutile d'insérer la valeur par défaut en plusieurs -endroits, \KPS{} applique la substitution à seulement un \samp{:} -supplémentaire et laisse les autres inchangés : il cherche d'abord un -\samp{:} en début de ligne, puis en fin de ligne et enfin un double -\samp{:}. - -\subsubsection{Expansion spécifiée par les accolades} - -Option utile, l'expansion par le biais des accolades -signifie, par exemple, que \verb+v{a,b}w+ va permettre la recherche -dans \verb+vaw:vbw+. Les définitions emboîtées sont autorisées. Ceci -peut être utilisé pour établir des hiérarchies \TeX{} multiples en -attribuant une liste entre accolades à \code{\$TEXMF}. Par exemple, -dans \file{texmf.cnf}, on trouve une définition du type suivant -(il y a en fait plus de répertoires) : -\begin{verbatim} - TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFSYSVAR,!!$TEXMFMAIN} -\end{verbatim} -Avec ceci, on peut écrire quelque chose comme -\begin{verbatim} - TEXINPUTS = .;$TEXMF/tex// -\end{verbatim} -%$ -ce qui signifie que, après avoir cherché dans le répertoire courant, les -arborescences complètes \code{\$TEXMFHOME/tex} suivie de -\code{\$TEXMFLOCAL/tex} (sur le disque) et ensuite les arborescences -\code{!!\$TEXMFVAR/tex} et \code{!!\$TEXMFMAIN/tex} -(définies dans le fichier de référence \file{ls-R} \emph{seulement}) seront -inspectées. C'est un moyen pratique permettant d'utiliser en parallèle deux -distributions \TeX{}, une « figée » (sur un \CD, par exemple) et une -autre régulièrement mise à jour avec de nouvelles versions quand elles -deviennent disponibles. En utilisant la variable \code{\$TEXMF} dans toutes -les définitions, on est toujours sûr d'inspecter d'abord l'arborescence la -plus récente. - -\subsubsection{Expansion des sous-répertoires} -\label{sec:subdirectory-expansion} - -Deux barres \samp{//} ou plus consécutives dans une partie d'un chemin suivant -un répertoire \var{d} sont remplacées par tous les sous-répertoires de -\var{d} : d'abord les sous-répertoires directement présents dans -\var{d}, ensuite les sous-répertoires de ceux-ci et ainsi de suite. À -chaque niveau, l'ordre dans lequel les répertoires sont inspectés est -\emph{non-déterminé}. - -Dans le cas où l'on spécifie une partie de nom de fichier après le -\samp{//}, seuls sont inclus les sous-répertoires auxquels le nom -correspond. Par exemple, \samp{/a//b} va correspondre aux répertoires -\file{/a/1/b}, \file{/a/2/b}, \file{/a/1/1/b} et ainsi de suite, -mais pas à \file{/a/b/c} ni \file{/a/1}. - -Des \samp{//} multiples et successifs dans un chemin sont possibles, -mais \samp{//} au début d'un chemin est ignoré. - -\subsubsection{Liste des caractères spéciaux et de leur signification : - récapitulatif} - -La liste suivante récapitule la signification des caractères spéciaux -dans les fichiers de configuration de \KPS{}. - -\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} - -\begin{ttdescription} - -\item[\CODE{:}] Séparateur dans un chemin de recherche ; au début - ou à la fin d'un chemin, il remplace le chemin par défaut. - -\item[\CODE{;}] Séparateur dans les systèmes non-Unix - (joue le rôle de \code{:}). - -\item[\CODE{\$}] Substitue le contenu d'une variable. - -\item[\CODE{\string~}] Représente le répertoire racine de - l'utilisateur. - -\item[\CODE{\char`\{...\char`\}}] Expansion par les accolades, - par exemple \verb+a{1,2}b+ devient \verb+a1b:a2b+. - -\item[\CODE{//}] La recherche concernera aussi les sous-répertoires - (peut être inséré n'importe où dans un chemin sauf au début). - -\item[\CODE{\%}] Début d'un commentaire. - -\item[\CODE{\bs}] Caractère de continuation de ligne (permet les - entrées sur plusieurs lignes). - -\item[\CODE{!!}] Cherche \emph{seulement} dans la base de - données pour localiser le fichier et \emph{ne cherche pas} sur le disque. - -\end{ttdescription} - -\subsection{Les bases de données} -\label{sec:filename-database} - -\KPS{} a une certaine profondeur d'investigation pour minimiser les -accès disque durant les recherches. Néanmoins, dans le cas de -distributions comprenant beaucoup de répertoires, inspecter chaque -répertoire possible pour un fichier donné peut durer excessivement -longtemps (ceci est typiquement le cas quand plusieurs centaines de -répertoires de polices de caractères doivent être parcourus). En -conséquence, \KPS{} peut utiliser un fichier texte appelé \file{ls-R} --- en -fait une base de données construite au préalable --- qui fait correspondre -les fichiers à leur répertoire, ce qui permet d'éviter une recherche -exhaustive sur le disque. - -Un deuxième fichier appelé \file{aliases} (qui est également une base de -données) permet de donner des noms différents aux fichiers listés dans -\mbox{\file{ls-R}}. Ceci peut aider à adapter ses fichiers source aux -conventions de \acro{DOS}~8.3 pour les noms de fichiers. - -\subsubsection{Le fichier base de données} -\label{sec:ls-R} - -Comme nous l'avons expliqué ci-dessus, le nom du principal fichier-base de -données doit être \mbox{\file{ls-R}}. -Dans votre installation, vous pouvez en mettre un à la racine de chaque -arborescence \TeX{} que vous désirez voir -inspecter (\code{\$TEXMF} par défaut) ; la plupart des sites ont -une seule arborescence \TeX{}. \KPS{} cherche les fichiers \file{ls-R} -dans le chemin spécifié dans la variable \code{TEXMFDBS}. - -La meilleure façon de créer et mettre à jour le fichier \file{ls-R} -est d'exécuter le script \cmdname{mktexlsr} inclus dans la -distribution. Il est appelé par les divers scripts \cmdname{mktex}\dots\ -En principe, ce script exécute uniquement la commande -%cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R| -% Remplacé (df) car \path|...| plante à cause de \let\path\url. -\begin{alltt} -cd \var{/your/texmf/root} && \boi{}ls -1LAR ./ >ls-R -\end{alltt} -en supposant que la commande \code{ls} de votre système produise le bon -format de sortie (le \code{ls} de \GNU convient -parfaitement). Pour s'assurer que la base de données est toujours à -jour, le meilleur moyen est de la reconstruire en utilisant la table -des \code{cron}, de telle façon que le fichier \file{ls-R} prenne -automatiquement en compte les changements dans les fichiers -installés, par exemple après une installation ou une -mise à jour d'un composant \LaTeX{}. - -Si un fichier n'est pas trouvé dans la base de données, par défaut -\KPS{} décide de le chercher sur le disque. Par contre, si un élément du -chemin commence par \samp{!!}, \emph{seule} la base de données -sera inspectée pour cet élément, jamais le disque. - -\subsubsection{kpsewhich : programme de recherche dans une arborescence} -\label{sec:invoking-kpsewhich} - -Le programme \texttt{kpsewhich} effectue une recherche dans une -arborescence indépendamment de toute application. On peut le -considérer comme une sorte de \code{find} pour localiser des fichiers -dans les arborescences \TeX{} (ceci est largement utilisé dans les -scripts \cmdname{mktex}\dots\ de la distribution). - -\begin{alltt} -> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} -\end{alltt} -Les options spécifiées dans \ttvar{option} peuvent -commencer soit par \samp{-} soit par \samp{-{}-} ; n'importe quelle -abréviation claire est acceptée. - -\KPS{} considère tout argument non optionnel dans la ligne de commande -comme un nom de fichier et renvoie la première occurrence trouvée. Il -n'y a pas d'option pour renvoyer tous les fichiers ayant un nom -particulier (vous pouvez utiliser le \cmdname{find} d'Unix pour cela). - -Les options les plus importantes sont décrites ci-après. - -\begin{ttdescription} -\item[\texttt{-{}-dpi=\var{num}}]\mbox{} \\ - Définit la résolution à \ttvar{num} ; ceci affecte - seulement la recherche des fichiers \samp{gf} et \samp{pk}. \samp{-D} est un - synonyme pour assurer la compatibilité avec \cmdname{dvips}. Le défaut - est 600. -\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ - Définit le format pour la recherche à \ttvar{name}. - Par défaut, le format est estimé en fonction du nom de fichier. - Pour les formats qui n'ont pas de suffixe clair associé, comme les - fichiers de support \MP{} et les fichiers de configuration - \cmdname{dvips}, vous devez spécifier le nom connu de \KPS, comme - \texttt{tex} ou \texttt{enc files}. Exécutez la commande - \texttt{kpsewhich -{}-help} pour obtenir la liste précise. - -\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ - Définit le nom du mode comme étant \ttvar{string} ; -ceci affecte seulement la recherche des \samp{gf} et des \samp{pk}. -Pas d'option par défaut, n'importe quel mode sera trouvé. -\item[\texttt{-{}-must-exist}]\mbox{}\\ - Fait tout ce qui est possible pour trouver les fichiers, ce qui -inclut une recherche sur le disque. Par défaut, seule la base de -données \file{ls-R} est inspectée, dans un souci d'efficacité. -\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ - Recherche dans le chemin \ttvar{string} (séparé par -deux-points comme d'habitude), au lieu de prendre le chemin à partir -du nom de fichier. \samp{//} et toutes les expansions habituelles sont -supportées. - Les options \samp{-{}-path} et \samp{-{}-format} s'excluent mutuellement. -\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ - Définit le nom de programme comme étant \ttvar{name}. - Ceci peut affecter les chemins de recherche via l'option - \texttt{.\var{progname}} dans les fichiers de configuration. - Le défaut est \cmdname{kpsewhich}. -\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ - Montre le chemin utilisé pour la recherche des fichiers de type -\ttvar{name}. - On peut utiliser soit une extension de fichier (\code{.pk}, \code{.vf}, - etc.), soit un nom de fichier, comme avec l'option \samp{-{}-format}. -\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ - Définit les options de débogage comme étant - \ttvar{num}. -\end{ttdescription} - -\subsubsection{Exemples d'utilisation} -\label{sec:examples-of-use} - -Jetons un coup d'Å“il à \KPS{} en action ; voici une recherche -toute simple : - -\begin{alltt} -> \Ucom{kpsewhich article.cls} -/usr/local/texmf-dist/tex/latex/base/article.cls -\end{alltt} -Nous recherchons le fichier \file{article.cls}. Puisque le suffixe -\file{.cls} est non-ambigu, nous n'avons pas besoin de spécifier que -nous voulons rechercher un fichier de type \optname{tex} (répertoires des -fichiers sources de \TeX{}). Nous le trouvons dans le sous-répertoire -\filename{tex/latex/base} du répertoire racine \samp{TEXMF}. De même, - le suffixe non-ambigu permet de trouver facilement les autres fichiers. -\begin{alltt} -> \Ucom{kpsewhich array.sty} - /usr/local/texmf-dist/tex/latex/tools/array.sty -> \Ucom{kpsewhich latin1.def} - /usr/local/texmf-dist/tex/latex/base/latin1.def -> \Ucom{kpsewhich size10.clo} - /usr/local/texmf-dist/tex/latex/base/size10.clo -> \Ucom{kpsewhich small2e.tex} - /usr/local/texmf-dist/tex/latex/base/small2e.tex -> \Ucom{kpsewhich tugboat.bib} - /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib -\end{alltt} - -Le dernier exemple est une base de données bibliographiques pour \BibTeX{} -servant aux articles de \textsl{TUGBoat}. - -\begin{alltt} -> \Ucom{kpsewhich cmr10.pk} -\end{alltt} -Les fichiers de glyphes de fontes bitmaps, de type -\file{.pk}, sont -utilisés pour l'affichage par des programmes comme \cmdname{dvips} et -\cmdname{xdvi}. Rien n'est renvoyé dans ce cas puisque il n'y a pas -de fichiers Computer Modern \file{.pk} pré-créés sur nos systèmes -(nous utilisons les versions type~1 du \TL{}). -\begin{alltt} -> \Ucom{kpsewhich wsuipa10.pk} -\ifSingleColumn - /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk -\else /usr/local/texmf-var/fonts/pk/ljfour/public/ -... wsuipa/wsuipa10.600pk -\fi\end{alltt} -Pour ces fontes (alphabet phonétique de l'université Washington), -nous avons dû créer les fichiers \file{.pk} et, puisque le mode \MF{} par -défaut sur notre installation est \texttt{ljfour} avec une résolution de -base de 600\dpi{} \textit{(dots per inch)}, cette instance est trouvée. -\begin{alltt} -> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} -\end{alltt} -Dans ce cas, lorsque l'on spécifie que nous recherchons une -résolution de 300\dpi{} (\texttt{-dpi=300}) nous voyons qu'aucune fonte -pour cette résolution n'est disponible dans le système. En fait, un -programme comme \cmdname{dvips} ou \cmdname{xdvi} ne s'en -préoccuperait pas et créerait les fichiers \file{.pk} à la -résolution demandée en utilisant le script \cmdname{mktexpk}. - -Intéressons-nous à présent aux fichiers d'en-tête et de configuration -pour \cmdname{dvips}. -Regardons en premier le fichier \file{tex.pro} communément utilisé -pour le support de \TeX{} avant de regarder le fichier -de configuration générique (\file{config.ps}) et la liste des fontes -\PS{} \file{psfonts.map}. Depuis l'édition 2004, les fichiers -\file{.map} et les fichiers de codage ont changé de place dans -l'arborescence \dirname{texmf}. Comme le suffixe \file{.ps} est -ambigu, nous devons spécifier quel type particulier du fichier -\texttt{config.ps} nous considérons (\optname{dvips config}). -\begin{alltt} -> \Ucom{kpsewhich tex.pro} - /usr/local/texmf/dvips/base/tex.pro -> \Ucom{kpsewhich -{}-format="dvips config" config.ps} - /usr/local/texmf-var/dvips/config/config.ps -> \Ucom{kpsewhich psfonts.map} - /usr/local/texmf-var/fonts/map/dvips/updmap/psfonts.map -\end{alltt} - -Regardons plus en détail les fichiers de support Times -\PS{} d'\acro{URW}. Leur nom standard dans le schéma de nommage des fontes -est \samp{utm}. Le premier fichier que nous voyons est le -fichier de configuration, qui contient le nom du fichier -de la liste : -\begin{alltt} -> \Ucom{kpsewhich -{}-format="dvips config" config.utm} - /usr/local/texmf-dist/dvips/psnfss/config.utm -\end{alltt} -Le contenu de ce fichier est -\begin{alltt} - p +utm.map -\end{alltt} -qui pointe vers le fichier \file{utm.map}, que nous cherchons à -localiser ensuite. -\begin{alltt} -> \Ucom{kpsewhich utm.map} - /usr/local/texmf-dist/fonts/map/dvips/times/utm.map -\end{alltt} -Ce fichier liste les noms des fichiers des -fontes \PS{} de type~1 dans la collection URW. Son contenu -ressemble à (nous ne montrons qu'une partie des lignes) : -\begin{alltt} -utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} -\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb -\else /usr/local/texmf-dist/fonts/type1/ -... urw/utm/utmr8a.pfb -\fi\end{alltt} - -Il devrait être clair, d'après ces quelques exemples, qu'il est facile -de trouver l'endroit où se cache un fichier donné. C'est -particulièrement important si vous suspectez que c'est, pour une -raison quelconque, une mauvaise version du fichier qui est utilisée, -puisque \cmdname{kpsewhich} va vous montrer le premier fichier -trouvé. - -\subsubsection{Opérations de débogage} -\label{sec:debugging} - -Il est quelquefois nécessaire de savoir comment un programme référence -les fichiers. Pour permettre cela, \KPS{} offre -plusieurs niveaux de débogage : -\begin{ttdescription} -\item[\texttt{\ 1}] Appels à \texttt{stat} (test d'existence de fichier). Lors d'une - exécution utilisant une base de données \file{ls-R} à jour, ce niveau - ne devrait donner presque aucune information en sortie. -\item[\texttt{\ 2}] Références aux différentes tables (comme la base - de données \file{ls-R}, les fichiers de correspondance de fontes, les fichiers de - configuration). -\item[\texttt{\ 4}] Opérations d'ouverture et de fermeture des - fichiers. -\item[\texttt{\ 8}] Information globale sur la localisation des types - de fichiers recherchés par \KPS. Ceci est utile pour trouver où a été - défini le chemin particulier pour un fichier. -\item[\texttt{16}] Liste des répertoires pour chaque élément du - chemin (utilisé uniquement en cas de recherche sur le disque). -\item[\texttt{32}] Recherche de fichiers. -\item[\texttt{64}] Valeur des variables. -\end{ttdescription} -Une valeur de \texttt{-1} activera toutes les options ci-dessus ; en -pratique, c'est habituellement la valeur la plus adaptée. - -De la même façon, avec le programme \cmdname{dvips}, en utilisant une -combinaison d'options de débogage, on peut suivre en détail la -localisation des -différents fichiers. De plus, lorsqu'un fichier n'est -pas trouvé, la trace du débogage montre les différents répertoires dans -lesquels le programme va chercher tel ou tel fichier, donnant ainsi -des indices sur le problème. - -Généralement, comme la plupart des programmes appellent la -bibliothèque \KPS{} en interne, on peut sélectionner une option de -débogage en utilisant la variable d'environnement -\envname{KPATHSEA\_DEBUG} et en la définissant égale à la valeur (ou -à une combinaison de valeurs) décrite(s) dans la liste ci-dessus. - -Note à l'intention des utilisateurs de Windows : il n'est pas facile -de rediriger les messages d'erreur vers un fichier sur ces -systèmes. À des fins de diagnostic, vous pouvez temporairement -affecter \texttt{KPATHSEA\_DEBUG\_OUTPUT=err.log} pour capturer le flux -standard d'erreur dans le fichier \texttt{err.log}. - -Considérons comme exemple un petit fichier source \LaTeX{}, -\file{hello-world.tex}, dont le contenu est le suivant. -\begin{verbatim} - \documentclass{article} - \begin{document} - Hello World! - \end{document} -\end{verbatim} -Ce petit fichier utilise simplement la fonte \file{cmr10}, aussi -allons voir comment \cmdname{dvips} prépare le fichier \PS{} -(nous voulons utiliser la version type~1 -des fontes Computer Modern, d'où l'option \texttt{-Pcms}). -\begin{alltt} -> \Ucom{dvips -d4100 hello-world -Pcms -o} -\end{alltt} -Dans ce cas, nous avons combiné le niveau 4 de débogage de -\cmdname{dvips} (chemins des fontes) avec l'option d'expansion des -éléments du chemin de \KPS\ (voir \cmdname{dvips} Reference Manual, -\OnCD{texmf/doc/html/dvips/dvips_toc.html} sur le \DVD{}). -La sortie (légèrement formatée) apparaît dans la -figure~\ref{fig:dvipsdbga}. -\begin{figure*}[tp] -\centering -\input{examples/ex6a.tex} -\caption{Recherche des fichiers de configuration}\label{fig:dvipsdbga} - -\bigskip - -\input{examples/ex6b.tex} -\caption{Recherche du fichier prolog}\label{fig:dvipsdbgb} - -\bigskip - -\input{examples/ex6c.tex} -\caption{Recherche du fichier de fontes}\label{fig:dvipsdbgc} -\end{figure*} - -\cmdname{dvips} commence par localiser ses fichiers de -fonctionnement. D'abord, \file{texmf.cnf} est trouvé, ce qui donne les -définitions pour les chemins de recherche servant à localiser les -autres fichiers, ensuite le fichier base de données \file{ls-R} (pour -optimiser la recherche des fichiers) et le fichier \file{aliases}, qui -permet de déclarer plusieurs noms (par exemple un nom \acro{DOS} de type -8.3 court et une version longue plus naturelle) pour le même -fichier. Ensuite \cmdname{dvips} continue en cherchant le fichier de -configuration générique \file{config.ps} avant de rechercher le fichier -de paramétrisation \file{.dvipsrc} (qui, dans notre cas, \emph{n'est -pas trouvé}). Enfin, \cmdname{dvips} localise le fichier de -configuration pour les fontes \PS{} Computer Modern -\file{config.cms} (ceci est lancé par l'option \mbox{\texttt{-Pcms}} de la -commande \cmdname{dvips}). Ce fichier contient la liste des fichiers - qui définissent la relation entre les noms des fontes -selon \TeX{}, selon \PS{} et dans le système de fichiers. -\begin{alltt} -> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} - p +ams.map - p +cms.map - p +cmbkm.map - p +amsbkm.map -\end{alltt} -\cmdname{dvips} veut chercher tous ces fichiers, y compris le -fichier générique d'association \file{psfonts.map}, qui est toujours -chargé (il contient des déclarations pour les fontes \PS{} les -plus communément utilisées ; voir la dernière partie de la Section -\ref{sec:examples-of-use} pour plus de détails sur la gestion du fichier -d'association \PS{}). - -Arrivé là, \cmdname{dvips} s'identifie à l'utilisateur : - \begin{alltt} - This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) - \end{alltt} - -\ifSingleColumn -pour continuer ensuite en cherchant le fichier prologue \file{texc.pro}, -\begin{alltt}\small -kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro -\end{alltt} -\else -pour continuer ensuite en cherchant le fichier prologue \file{texc.pro} -(voir la figure~\ref{fig:dvipsdbgb}). -\fi - -Après avoir trouvé ce fichier, \cmdname{dvips} affiche la date et -l'heure, nous informe qu'il va générer le fichier -\file{hello-world.ps} puis qu'il a besoin du fichier de fonte -\file{cmr10} et que ce dernier est déclaré comme « résident» -(pas besoin de bitmaps) : -\begin{alltt}\small -TeX output 1998.02.26:1204' -> hello-world.ps -Defining font () cmr10 at 10.0pt -Font cmr10 is resident. -\end{alltt} -Maintenant la recherche concerne le fichier \file{cmr10.tfm}, qui est -trouvé, puis quelques fichiers de prologue de plus (non montrés) sont -référencés ; finalement le fichier de la fonte type~1 \file{cmr10.pfb} -est localisé et inclus dans le fichier de sortie (voir la dernière ligne). -\begin{alltt}\small -kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, - path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: - /var/tex/fonts/tfm//). -kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm -kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, - ... - -kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb -[1] -\end{alltt} - -\subsection{Options à l'exécution} - -\Webc{} offre la possibilité de contrôler à l'exécution bon nombre de -paramètres concernant la mémoire (en particulier la taille des -tableaux utilisés) à partir du fichier -\file{texmf.cnf} qui est lu par \KPS. -Les paramètres en question se trouvent -dans la troisième partie du fichier inclus dans la distribution \TL{}. - Les variables les plus importantes sont : -\begin{ttdescription} -\item[\texttt{main\_memory}] - Nombre total de mots mémoire disponibles pour - \TeX{}, \MF{} et \MP. Vous devez générer un nouveau fichier de - format pour chaque nouveau paramétrage. Par exemple, vous pouvez - générer une version large de \TeX{} et appeler le fichier de format - \texttt{hugetex.fmt}. En utilisant la méthode supportée par \KPS{} - qui consiste à suffixer la variable par le nom du programme, la valeur - particulière de la variable \texttt{main\_memory} destinée à ce - fichier de format sera lue dans le fichier \file{texmf.cnf}. -\item[\texttt{extra\_mem\_bot}] - Espace supplémentaire pour certaines structures de données de \TeX{} : - boîtes, \textit{glue}, points d'arrêt\dots{} Surtout utile si vous utilisez - \PiCTeX{} par exemple. -\item[\texttt{font\_mem\_size}] - Nombre de mots mémoire disponibles pour décrire les polices. C'est - plus ou moins l'espace occupé par les fichiers \acro{TFM} lus. -\item[\texttt{hash\_extra}] - Espace supplémentaire pour la table de hachage des noms de séquences - de contrôle. Environ 10~000 de ces noms peuvent être stockés dans la - table principale ; si vous avez un document très volumineux avec - beaucoup de références croisées, il se peut que ce ne soit pas - suffisant. La valeur par défaut \texttt{hash\_extra} est \texttt{50000}. -\end{ttdescription} - -\noindent Évidemment, cette possibilité ne remplace pas une véritable -allocation dynamique des tableaux et de la mémoire mais puisque c'est -complexe à implémenter dans le présent source \TeX{}, ces paramètres lus -à l'exécution fournissent un compromis pratique qui procure une certaine -souplesse. - -\section{Installation sur un nouveau système Unix} - -Si vous avez un système Unix ne correspondant à aucun des exécutables -fournis, il faut compiler vous-même \TeX{} et tous ses programmes -satellites à partir des sources. Cela n'est pas aussi difficile qu'il -y paraît. Tout ce dont vous aurez besoin est contenu dans le -répertoire \texttt{source} qui se trouve sur le \DVD. - -\subsection{Prérequis} - -Il faut au moins 400\,Mo d'espace sur disque pour compiler la -totalité de \TeX{} et des programmes associés. -Vous aurez aussi besoin d'un -compilateur C \acro{ANSI}, de l'utilitaire \cmdname{make}, -d'un générateur d'analyseur lexical et d'un générateur d'analyseur -syntaxique. Nous recommandons les versions \GNU des programmes suivants -(\cmdname{gcc}, \GNU{}\cmdname{make}, \cmdname{m4}, -\cmdname{flex}, \cmdname{bison}). Vous pouvez utiliser d'autres compilateurs C -et d'autres programmes \cmdname{make} si vous maîtrisez -correctement la programmation sous Unix pour résoudre les -problèmes éventuels. La commande \texttt{uname} doit renvoyer une valeur -raisonnable. - -\subsection{Configuration} - -Tout d'abord, effectuez l'installation normale de \TL{} sur le disque -dur (voir section~\ref{sec:install}, -page~\pageref{sec:install}). Vous pouvez sauter l'installation de -tous les binaires précompilés. -Décompactez ensuite sur le disque le fichier -\file{source.tar.bz2} (archive compressée) trouvé dans -le répertoire \dirname{source} et placez-vous dans -le répertoire où vous avez transféré l'ensemble. -\begin{alltt} -> \Ucom{cd /tmp/tl-source} -> \Ucom{bunzip2 source.tar.bz2} -> \Ucom{tar xf source.tar} -\end{alltt} - -Lancez maintenant \textsf{configure} de la façon suivante : -\begin{alltt} -> \Ucom{sh configure -prefix=/usr/local/texlive/2007} -\end{alltt} - -Le répertoire \optname{-prefix} est le répertoire de base de -l'arborescence \TL{}, il est désigné par \var{TEXDIR} dans la suite. -\begin{comment} -Les répertoires utilisés sont les suivants : - -\noindent -\begin{tabular}{>{\ttfamily}ll@{}} - \dirname{$TEXDIR/texmf-dist} & répertoire de base pour les fontes, - macros, etc\\ - \dirname{$TEXDIR/man} & pages du manuel Unix\\ - \dirname{$TEXDIR/info} & manuels \GNU en format Info\\ - \dirname{$TEXDIR/bin/$archname} & exécutables.\\ -\end{tabular}\\ -\end{comment} -%$ - -Si vous ne voulez pas créer de répertoire \dirname{$archname} spécifique %$ -au système choisi pour stocker les exécutables (c.-à-d. les -copier directement dans \dirname{$TEXDIR/bin}), %$ -il faut exécuter \textsf{configure} avec l'option \\ -\verb|--disable-multiplatform|. - -Tapez \verb|./configure --help|, le programme affichera -les options supplémentaires disponibles (telles que supprimer l'installation -des extensions optionnelles comme \OMEGA\ ou \eTeX). - -\subsection{Exécuter \textsf{make}} -S'assurer que la variable ou l'option \texttt{noclobber} n'est pas définie. - et lancer le \cmdname{make} à la racine de l'arborescence de la façon -suivante : -\begin{alltt} ->> \Ucom{make world} -\end{alltt} -et aller prendre un café\dots - -Il peut être utile de garder une trace complète dans un fichier log en tapant : -\begin{alltt} ->> \Ucom{sh -c "make world >world.log 2>\&1" \&} -\end{alltt} -Avant de conclure que tout va bien, vérifier que le fichier log ne contient -pas de message d'erreur : le \cmdname{make} de \GNU renvoie toujours -le message \samp{***} à chaque erreur d'exécution. Vérifier aussi que -tous les exécutables ont été créés. -\begin{alltt} ->> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} ->> \Ucom{ls | wc} -\end{alltt} -Le résultat doit être supérieur à 200 (on peut tester le nombre exact -dans le répertoire \dirname{bin} de la distribution). - -Si vous avez besoin de droits spéciaux pour exécuter \texttt{make install}, -vous pouvez séparer \samp{make world} en deux processus différents : -\begin{alltt} ->> \Ucom{make all} ->> \Ucom{su} ->> \Ucom{make install strip} -\end{alltt} - -Après avoir installé vos nouveaux binaires, il faut suivre les procédures -normales de la post-installation, indiquées dans la -section~\ref{sec:postinstall}, page~\pageref{sec:postinstall}. - -\section{Remerciements} - -\TL{} est le résultat des efforts -collectifs de pratiquement tous les groupes d'utilisateurs de \TeX. -La présente édition de \TL{} a été coordonnée par Karl Berry. -Voici la liste des principaux contributeurs : - -\begin{itemize} - -\item Les associations d'utilisateurs anglais, allemands, néerlandais et - polonais (\acro{TUG}, \acro{DANTE} e.V., \acro{NTG}, and \acro{GUST}, - respectivement) qui contribuent ensemble à l'infrastructure technique et - administrative. Soutenez votre association locale (voir la liste - \url{http://tug.org/usergroups.html}) ! - -\item L'équipe du \acro{CTAN}, en particulier Robin Fairbairns, Jim Hef{}feron - et Rainer Schöpf, qui distribue les images des distributions \TL{} et - fournit les sites d'hébergement pour le stockage et la mise à jour des - extensions qui sont la base de \TL. - -\item Peter Breitenlohner et toute l'équipe \eTeX{} qui construisent - les bases des successeurs de \TeX. - -\item Thomas Esser et sa merveilleuse distribution \teTeX{} sans laquelle - \TL{} n'aurait jamais vu le jour. - -\item Michel Goossens, en tant que co-auteur de la documentation initiale. - -\item Eitan Gurari, dont le programme \TeX4ht a été utilisé pour créer la - version \HTML{} de cette documentation et qui travaille inlassablement à - l'améliorer, ce dans des délais très courts. - -\item \Thanh, Martin Schr\"oder et toute l'équipe pdf\TeX\ qui continuent - inlassablement à étendre les performances de \TeX. - -\item Hans Hagen qui, outre sa participation active aux tests, a adapté le - format \ConTeXt\ (\url{http://pragma-ade.com}) aux besoins de \TL{}. - -\item Hartmut Henkel, pour ses contributions au développement - de pdf\TeX{} et Lua\TeX{} entre autres. - -\item Taco Hoekwater, pour ses efforts sans cesse renouvelés à l'amélioration - de MetaPost et de (Lua)\TeX\ (\url{http://luatex.org}). - -\item Pawe{\l} Jackowski pour l'installeur Windows \cmdname{tlpm} et Tomasz - {\L}uczak pour la version graphique \cmdname{tlpmgui} utilisée dans - l'édition précédente. - -\item Akira Kakuto, pour son aide précieuse qui nous a permis - d'intégrer dans \TL{} les binaires Windows de sa distribution \acro{W32TEX} - (\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}). - -\item Jonathan Kew et \acro{SIL}, pour avoir produit - Xe\TeX{}, pour l'avoir intégré dans \TL{} et pour avoir - créé la première version de l'installeur Mac\TeX. - -\item Dick Koch, pour la maintenance de Mac\TeX\ (\url{http://tug.org/mactex}) - faite en symbiose avec \TL. - -\item Reinhard Kotucha, pour ses contributions majeures à l'infrastructure de - \TL{} 2008 et à son programme d'installation, pour ses contributions sous - Windows et pour son script \texttt{getnonfreefonts} en particulier. - -\item Siep Kroonenberg, également pour ses contributions majeures à - l'infrastructure de \TL{} 2008 et à son programme d'installation ainsi que - pour la réécriture de cette documentation. - -\item Petr Ol\v{s}ak, qui coordonna et vérifia minutieusement toute la - partie tchèque et slovaque. - -\item Toshio Oshima, pour le visualisateur \cmdname{dviout} pour Windows. - -\item Manuel Pégourié-Gonnard, pour son aide concernant le programme de mise à - jour de la distribution, la documentation et pour le développement de - \cmdname{tldoc}. - -\item Fabrice Popineau, pionnier du développement de \TL{} sous Windows et - pour son travail sur la documentation française. - -\item Norbert Preining, principal architecte de la distribution \TL{} 2008 et - de son installeur et coordinateur (avec Frank K\"uster) de la - version Debian de \TL. - -\item Sebastian Rahtz, qui a créé la distribution \TL{} et en a assuré la - maintenance pendant de nombreuses années. - -\item Vladimir Volovich, pour son aide substantielle, en particulier pour - avoir rendu possible l'intégration de \cmdname{xindy} dans \TL. - -\item Staszek Wawrykiewicz, principal testeur de \TL{} et coordinateur des - contributions polonaises (fontes, installation Windows, etc.). - -\item Olaf Weber, pour son patient assemblage de \Webc. - -\item Gerben Wierda, qui a créé et maintient la partie \MacOSX{} - et qui participe activement aux tests. - -\item Graham Williams, pour son travail sur le catalogue \TeX\ des - composants. - -\end{itemize} - -Les binaires ont été compilés par : -Tigran Aivazian (\pkgname{x86\_64-linux}), -Tim Arnold (\pkgname{hppa-hpux}), -Randy Au (\pkgname{amd64-freebsd}), -Edd Barrett (\pkgname{i386-openbsd}), -Karl Berry (\pkgname{i386-linux}), -Akira Kakuto (\pkgname{win32}), -Dick Koch (\pkgname{universal-darwin}), -Manfred Lotz (\pkgname{i386-freebsd}), -Norbert Preining (\pkgname{alpha-linux}), -Arthur Reutenauer (\pkgname{sparc-linux}), -Thomas Schmitz (\pkgname{powerpc-linux}), -Apostolos Syropoulos (\pkgname{i386-solaris}), -Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-solaris}), -Olaf Weber (\pkgname{mips-irix}). - -Documentation et mises à jour des traductions : -Karl Berry (anglais), -Daniel Flipo (français), -Klaus H\"oppner (allemand), -Petr Sojka \& Jan Busa (tchèque et slovaque), -Boris Veytsman (russe), -Staszek Wawrykiewicz (polonais). - -La page d'accueil de la documentation \TL{} est -\url{http://tug.org/texlive/doc.html}. - -Bien sûr, notre gratitude va en premier lieu à Donald Knuth pour avoir -inventé \TeX{} et l'avoir offert au monde entier. - -\section{Historique des versions successives} -\label{sec:history} - -\subsection{Les éditions précédentes} - -La discussion commença à la fin de 1993 quand le Groupe des Utilisateurs -Néerlandais de \TeX{} commençait à travailler à son \CD{} 4All\TeX{} pour les -utilisateurs de \acro{MS-DOS} et on espérait à ce moment sortir un \CD{} -unique pour tous les systèmes. C'était un objectif beaucoup trop ambitieux -mais il permit la naissance du \CD{} 4All\TeX{}, projet couronné de succès et -aussi d'un groupe de travail « \acro{TUG} Technical Council » pour -mettre en place TDS (\emph{\TeX{} Directory Structure} : -\url{http://tug.org/tds}), qui spécifiait la gestion des fichiers \TeX{} sous -une forme logique. La mouture finale de \TDS{} fut publiée dans le numéro de -décembre 1995 de \textsl{TUGboat} et il était clair depuis un certain temps -qu'il fallait proposer un produit contenant une structure modèle sur \CD{}. -La distribution que vous possédez est le résultat direct des délibérations de -ce groupe de travail. Il était également clair que le succès des \CD{} -4All\TeX{} démontrait que les utilisateurs d'Unix trouveraient leur bonheur -avec une distribution aussi simple et ceci a été l'autre objectif de -\TL. - -Nous avons d'abord entrepris de créer un nouveau \CD{} \TDS{} Unix à l'automne -1995 et nous avons rapidement choisi \teTeX{} de Thomas Esser comme étant la -configuration idéale, car il supportait déjà plusieurs plates-formes et avait -été construit en gardant à l'esprit la portabilité entre systèmes. Thomas -accepta de nous aider et commença à travailler sérieusement au début de 1996. -La première édition sortit en mai 1996. Au début de 1997, Karl Berry acheva -une nouvelle distribution de \Webc{}, qui incluait presque toutes les -caractéristiques que Thomas Esser avait ajoutées dans \teTeX{} et il fut décidé -de baser la deuxième édition du \CD{} sur le standard \Webc, en y ajoutant le -script \texttt{texconfig} de \teTeX. La troisième édition du \CD{} était -basée sur une version majeure de \Webc, 7.2, par Olaf Weber ; en même temps, -une nouvelle version révisée de \teTeX{} était achevée dont \TL{} partageait -presque toutes les caractéristiques. La quatrième édition a suivi le même -schéma, en utilisant une nouvelle version de \teTeX{} et une nouvelle version -de \Webc{} (7.3). Le système incluait dorénavant un programme complet -d'installation pour Windows. - -Pour la cinquième édition (mars 2000), de nombreuses parties du \CD{} -ont été vérifiées et révisées, des centaines de composants -mis à jour. -Le contenu détaillé des composants était décrit par des -fichiers XML. Mais le changement majeur de cette cinquième édition a -été la suppression de tout logiciel non libre de droits. -Tout ce qui se trouve dans \TL{} devait être compatible avec la licence -Debian (\emph{Debian Free Software Guidelines} : -\url{http://www.debian.org/intro/free}) ; nous avons -fait de notre mieux pour vérifier les termes des licences de chaque -composant et nous souhaiterions que toute erreur nous soit signalée. - -La sixième édition (juillet 2001) contient un grand nombre de mises à jour. -Le changement majeur de cette version réside dans la refonte du -processus d'installation : l'utilisateur peut désormais choisir -les collections de manière plus précise. Les collections concernant -les langues ont été entièrement réorganisées, aussi le choix d'une -langue installe non seulement les macros, les fontes, etc. mais -prépare également un fichier \file{language.dat} adéquat. - -La septième édition (mai 2002) a comme ajout majeur une installation -pour \MacOSX{} et l'habituelle myriade de mises à jour de composants et -de programmes. Un objectif important a été de fusionner à -nouveau les sources avec ceux de \teTeX{}, alors que les versions -5 et 6 s'en étaient éloignées. - -\subsubsection{2003} - -En 2003, le flot de mises à jour et d'additions a continué mais nous -avons constaté que \TL{} était devenu si volumineux qu'il ne -pouvait plus tenir sur un seul \CD, aussi l'avons-nous divisé en trois -distributions distinctes (voir section~\ref{sec:tl-coll-dists}, -page~\pageref{sec:tl-coll-dists}). Par ailleurs : -\begin{itemize} -\item À la demande de l'équipe \LaTeX{}, nous avons modifié les - commandes standard \cmdname{latex} et \cmdname{pdflatex} pour - qu'elles utilisent \eTeX{} (voir page~\pageref{text:etex}). -\item Les nouvelles fontes Latin Modern sont disponibles (et - recommandées). -\item Le support pour Alpha \acro{OSF} a été supprimé - (celui pour \acro{HPUX} l'avait été auparavant), car personne - disposant des machines nécessaires ne s'est - proposé pour compiler les nouveaux binaires. -\item L'installation pour Windows a été largement modifiée ; un environnement - de travail intégré basé sur \cmdname{XEmacs} a été introduit. -\item Des programmes supplémentaires importants pour Windows (Perl, - Ghost\-script, Image\-Magick, Ispell) sont maintenant installés dans le - répertoire d'installation de \TL{}. -\item Les fichiers \emph{font map} utilisés par \cmdname{dvips}, - \cmdname{dvipdfm} et \cmdname{pdftex} sont maintenant générés par le - nouveau programme \cmdname{updmap} et installés dans - \dirname{texmf/fonts/map}. -\item Dorénavant, \TeX{}, \MF{} et \MP{} écrivent les caractères 8-bit - présentés en entrée sans modification et non pas avec la notation - \verb|^^|, que ce soit dans des fichiers (par la commande - \verb|write|), dans les fichiers de trace (\verb|.log|) ou sur le - terminal. Dans le \TL{}~7, l'écriture de ces caractères - 8-bit était influencée par les paramètres de localisation du - système; maintenant ces paramètres n'influent plus du tout sur le - comportement des programmes \TeX{}. Si pour quelque raison que ce - soit, vous avez besoin de la notation \verb|^^| en sortie, - renommez le fichier \verb|texmf/web2c/cp8bit.tcx|. Les prochaines - versions disposeront d'un moyen plus propre pour contrôler cette - sortie. -\item La documentation de \TL{} a été largement révisée. -\item Enfin, comme la numérotation séquentielle des versions - devenait peu maniable, il a été décidé d'identifier désormais la version - de \TL{} par l'année : \TL{}~2003 au lieu de \TL{}~8. -\end{itemize} - - -\subsubsection{2004} - -2004 a apporté beaucoup de changements (et quelques incompatibilités avec les -versions précédentes) : - -\begin{itemize} - -\item Si vous avez installé des fontes supplémentaires qui ont leur propre -fichier \file{.map} ou des fichiers \file{.enc} spécifiques, vous -devrez vraisemblablement déplacer ces fichiers. - -Les fichiers \file{.map} sont désormais recherchés uniquement dans les -sous-répertoires \dirname{fonts/map} (dans chaque arborescence -\filename{texmf}), leur chemin de recherche est donné par la variable -\envname{TEXFONTMAPS} de \filename{texmf.cnf}. -De même, les fichiers \file{.enc} sont désormais recherchés uniquement -dans les sous-répertoires \dirname{fonts/enc}, leur chemin de recherche est -donné par la variable \envname{ENCFONTS} de \filename{texmf.cnf}. -Le script \cmdname{updmap} devrait émettre des messages d'avertissement -pour les fichiers \file{.map} et \file{.enc} mal placés. - -Sur les différentes façons de traiter le problème, consulter -\url{http://tug.org/texlive/mapenc.html}. - -\item La distribution pour Windows a changé cette année : -l'installation de la distribution \fpTeX{} (basée sur \Webc{}) de Fabrice -Popineau n'est plus proposée. À la place, vous pouvez tester et installer -la distribution \ProTeXt{} basée sur \MIKTEX{} (indépendante de \Webc{}), -voir section~\ref{sec:overview-tl}, page~\pageref{sec:overview-tl}. - -\item L'ancien répertoire \dirname{texmf} a été éclaté en trois parties : -\dirname{texmf}, \dirname{texmf-dist} et \dirname{texmf-doc}. Voir -section~\ref{sec:tld}, page~\pageref{sec:tld}. - -\item Tous les fichiers relatifs aux différents avatars de \TeX{} sont -désormais regroupés dans le même sous-répertoire \dirname{tex} des -arborescences \dirname{texmf*} (ils étaient jusqu'ici placés dans des -sous-répertoires spécifiques \dirname{tex}, \dirname{etex}, -\dirname{pdftex}, \dirname{pdfetex}, etc.). Voir -\OnCD{texmf-doc/doc/english/tds/tds.html\#Extensions}. - -\item Les scripts auxiliaires, normalement pas exécutés directement -par les utilisateurs, sont regroupés dans un répertoire \dirname{scripts} -des arborescences \dirname{texmf*}. On les localise grâce à la -commande \verb|kpsewhich -format=texmfscripts|. Au cas où vous en -auriez, les programmes utilisant ces scripts nécessiteront une adaptation. -Voir \OnCD{texmf-doc/doc/english/tds/tds.html\#Scripts}. - -\item La plupart des formats affichent en clair (dans les fichiers -\file{.log} en particulier) les caractères imprimables au lieu -de les transcrire en notation hexadécimale \verb|^^|. Ceci se fait -grâce au fichier \filename{cp227.tcx}, qui considère comme imprimables -les caractères 32 à 256, ainsi que les tabulations et les changements -de page (caractères 9 à 11). Les formats faisant exception sont -plain \TeX\ (seuls les caractères 32 à 127 sont déclarés imprimables), -\ConTeXt{} (0 à 255 imprimables) et les formats basés sur \OMEGA. -Il y a peu de différence avec le comportement de \TL\,2003 -mais la mise en Å“uvre est plus propre et plus facilement configurable. -Voir \OnCD{texmf/doc/web2c/web2c.html\#TCX-files}. -Noter que l'utilisation du codage Unicode en entrée peut provoquer -des affichages défectueux en sortie (TeX code sur un seul octet). - -\item Tous les formats, sauf plain \TeX, font appel au moteur -\textsf{pdfetex} (qui produit bien sûr par défaut des fichiers \acro{DVI} -lorsque le format choisi est \LaTeX). Ceci permet aux formats -\LaTeX, \ConTeXt, etc., d'avoir accès aux fonctionnalités -micro-typographiques de pdf\TeX{} (alignement optique des marges par exemple) -et aux fonctionnalités de \eTeX{} (\OnCD{texmf-dist/doc/etex/base/}). - -Ceci rend \emph{indispensable} le recours à l'extension \pkgname{ifpdf} -(qui fonctionne aussi bien avec plain que \LaTeX) pour déterminer si -le format de sortie est \acro{DVI} ou \acro{PDF}. Tester si la commande -\cs{pdfoutput} est définie ou non \emph{n'est pas} un moyen fiable -de le faire. - -\item pdf\TeX\ (\url{http://pdftex.org}) offre de nouvelles fonctionnalités : - - \begin{itemize} - - \item Les commandes \cs{pdfmapfile} et \cs{pdfmapline} permettent - de spécifier le choix des fichiers \file{.map} à utiliser - pour le document en cours. - - \item L'amélioration du gris typographique par variation (infime) de la - largeur des caractères (\textit{font expansion}) est plus facile à - mettre en Å“uvre, voir - \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} - - \item Le fichier \filename{pdftex.cfg} n'est plus utilisé. - Toutes les affectations de paramètres doivent désormais être - faites dans le préambule en utilisant les primitives ad~hoc. - - \item Pour plus d'informations, consulter le manuel de pdf\TeX\ : - \OnCD{texmf/doc/pdftex/manual}. - - \end{itemize} - -\item La primitive \cs{input} de \cmdname{tex}, \cmdname{mf} et -\cmdname{mpost}, accepte désormais les espaces et autres caractères -spéciaux dans les noms de fichiers à condition d'utiliser des -\textit{double quotes}, en voici deux exemples typiques : -\begin{verbatim} -\input "filename with spaces" % plain -\input{"filename with spaces"} % latex -\end{verbatim} -Consulter le manuel \Webc{} pour plus d'informations : \OnCD{texmf/doc/web2c}. - -\item Les fonctionnalités de enc\TeX\ sont désormais incluses dans \Webc{}. -Ainsi, tous les formats \emph{construits avec l'option \optname{-enc}} y ont -accès. enc\TeX\ permet le transcodage en entrée et en sortie et -l'utilisation transparente du codage Unicode \acro{UTF}-8. Voir -\OnCD{texmf-dist/doc/generic/enctex/} et -\url{http://www.olsak.net/enctex.html}. - -\item Un nouveau moteur combinant les fonctionnalités de \eTeX\ -et d'\OMEGA, appelé Aleph, est disponible. \OnCD{texmf-dist/doc/aleph/base} -et \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph} -fournissent une information succincte. Le format \LaTeX{} utilisant -Aleph s'appelle \textsf{lamed}. - -\item La licence \acro{LPPL} de \LaTeX\ (version décembre 2003) a changé, -elle est désormais compatible avec les prescriptions Debian. -Les autres changements sont décrits dans le fichier \filename{ltnews}, voir -\OnCD{texmf-dist/doc/latex/base}. - -\item Un nouveau programme, \cmdname{dvipng}, qui convertit les fichiers -\acro{DVI} en images \acro{PNG} a été ajouté. Voir -\OnCD{texmf/doc/man/man1/dvipng.1}. - -\item Nous avons dû réduire le nombre de fontes incluses dans l'extension -\pkgname{cbgreek}, ceci a été fait avec l'accord et l'aide de l'auteur -(Claudio Beccari). Les fontes exclues (invisibles, transparentes, contours) -sont rarement utilisées et la place nous manquait. La collection complète -des fontes \pkgname{cbgreek} est disponible sur \acro{CTAN} -(\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). - -\item La commande \cmdname{oxdvi} a été supprimée, il suffit utiliser -\cmdname{xdvi} à la place. - -\item Les commandes \cmdname{initex}, \cmdname{virtex} et leurs -homologues pour \cmdname{mf} et \cmdname{mpost} ont disparu. -Vous pouvez les recréer si nécessaire mais elles sont avantageusement -remplacées, depuis des années maintenant, par l'option \optname{-ini} -(\cmdname{tex} \optname{-ini} pour \cmdname{initex} et \cmdname{virtex}). - -\item Les binaires pour l'architecture \textsf{i386-openbsd} ont été - supprimés par manque de volontaires pour les compiler. - -Sur \textsf{sparc-solaris} (au moins) il sera probablement -nécessaire de positionner la variable d'environnement -\envname{LD\_LIBRARY\_PATH} pour utiliser les programmes de la famille -\pkgname{t1utils}. Ceci vient du fait qu'ils sont compilés en C++ et -que l'emplacement des bibliothèques dynamiques est variable. -Ce n'est pas une nouveauté 2004 mais ce point n'était pas documenté -précédemment. De même, sur \textsf{mips-irix}, les bibliothèques dynamiques -\acro{MIPS}pro 7.4 sont nécessaires. - -\end{itemize} - -\subsubsection{2005} - -2005 a apporté son lot habituel d'innombrables mises à jour d'extensions -et de programmes. L'infrastructure est restée relativement stable par rapport -à 2004, à quelques changements inévitables près : - -\begin{itemize} - -\item Trois nouveaux scripts \cmdname{texconfig-sys}, \cmdname{updmap-sys} et - \cmdname{fmtutil-sys} ont été introduits ; ils agissent sur la - configuration générale de la machine, comme le faisaient les - scripts \cmdname{texconfig}, \cmdname{updmap} et \cmdname{fmtutil} - jusqu'à l'an dernier. Les nouveaux scripts \cmdname{texconfig}, - \cmdname{updmap} et \cmdname{fmtutil} modifient maintenant - la configuration \emph{personnelle} de l'utilisateur qui les lance ; - le résultat est placé dans le répertoire personnel de l'utilisateur - (sous \dirname{$HOME/.texlive2005}). %$ - -\item De nouvelles variables, \envname{TEXMFCONFIG} (resp. - \envname{TEXMFSYSCONFIG}) ont été introduites ; elles définissent - les répertoires où doivent se trouver les fichiers de configuration de - l'utilisateur (resp. de la machine), comme \filename{fmtutil.cnf} et - \filename{updmap.cfg}. Les utilisateurs de fichiers de configuration - locaux \filename{fmtutil.cnf} ou \filename{updmap.cfg} devront - probablement les déplacer ; une autre possibilité est de modifier la - définition des variables \envname{TEXMFCONFIG} ou - \envname{TEXMFSYSCONFIG} dans \filename{texmf.cnf}. L'important est - de s'assurer de la cohérence entre les définitions de ces variables - dans \filename{texmf.cnf} et l'emplacement réel de ces fichiers. - Voir section~\ref{sec:texmftrees}, page~\pageref{sec:texmftrees} pour - la description des différentes arborescences texmf utilisées. - -\item L'an dernier nous avions rendu « \texttt{undefined} » certaines - primitives propres à \cmdname{pdftex} (comme \verb|\pdfoutput|) - dans les formats créés à partir de \cmdname{pdfetex} (\cmdname{latex} - \cmdname{amstex}, \cmdname{context} par exemple)). - C'était à titre transitoire, aussi cette année, ces primitives sont de - nouveau définies dans tous les formats à base \cmdname{pdf(e)tex}, - \emph{même lorsqu'ils sont utilisés pour produire des fichiers - \file{.dvi}}. Ceci implique qu'il vous faudra modifier vos - documents qui utilisent le test \verb|\ifx\pdfoutput\undefined| - pour déterminer si la sortie est en DVI ou en PDF. Le mieux est - d'utiliser l'extension \pkgname{ifpdf.sty} et son test - \verb|\ifpdf| qui fonctionne même en plain \TeX. - -\item L'an dernier nous avions fait en sorte que la plupart des formats - impriment dans les sorties \file{.log} des caractères 8-bit - lisibles à la place des notations hexadécimales \verb|^^| - (voir section précédente). - Le nouveau fichier TCX \filename{empty.tcx} permet - de revenir facilement à la notation traditionnelle \verb|^^|, il suffit - de coder : -\begin{verbatim} -latex --translate-file=empty.tcx fichier.tex -\end{verbatim} - -\item Le nouveau programme \cmdname{dvipdfmx} est disponible pour convertir - des fichier DVI en PDF ; ce programme remplace \cmdname{dvipdfm}, - toujours disponible mais dont l'usage est maintenant déconseillé. - -\item Les variables \envname{HOMETEXMF} et \envname{VARTEXMF} ont été renommées - en \envname{TEXMFHOME} et \envname{TEXMFSYSVAR} respectivement pour - raisons de cohérence avec les autres noms de variables. Il y a aussi - \envname{TEXMFVAR} qui désigne maintenant un répertoire personnel - de l'utilisateur (cf. le premier point de la présente liste). - -\end{itemize} - -\subsubsection{2006--2007} - -En 2006--2007, la nouveauté majeure a été l'arrivée dans \TL{} de Xe\TeX{} -disponible sous forme de deux programmes \texttt{xetex} et \texttt{xelatex}, -voir \url{http://scripts.sil.org/xetex}. - -MetaPost a subi une mise à jour importante et d'autres améliorations -sont prévues, voir \url{http://tug.org/metapost/articles}. Il en va de même -pour pdf\TeX{}, voir \url{http://tug.org/applications/pdftex}. - -Le format \filename{tex.fmt} et les formats pour MetaPost and \MF\ ne -se trouvent plus dans \dirname{texmf/web2c} mais dans des -sous-répertoires de \dirname{texmf/web2c} (la recherche de fichiers -\filename{.fmt} est néanmoins faite aussi dans \dirname{texmf/web2c}). -Ces sous-répertoires portent le nom du moteur utilisé pour construire -le format, par exemple \filename{tex}, \filename{pdftex} ou -\filename{xetex}. Ce changement ne devrait pas avoir d'effet visible -pour les utilisateurs. - -Le programme (plain) \texttt{tex} ignore désormais les lignes commençant -par \texttt{\%\&} qui permettent de déterminer le format à utiliser ; -c'est un vrai \TeX{} « à la Knuth » ! -\LaTeX\ et tous les autres prennent toujours en compte les lignes commençant -par \texttt{\%\&}. - -Comme chaque année des centaines d'extensions et de programmes ont été mis à -jour, voir les sites \acro{CTAN} (\url{http://www.ctan.org}). - -L'arborescence utilisée en interne a été réorganisée avec de nouveaux outils -qui devraient fournir une meilleure base de travail pour les développements -futurs. - -Enfin, en mai 2006 Thomas Esser a annoncé qu'il renonçait à poursuivre le -développement de te\TeX{} (\url{http://tug.org/tetex}). Sa décision a relancé -l'intérêt pour \TL, en particulier chez les distributeurs de solutions -\GNU/Linux (un nouveau schéma d'installation \texttt{tetex} a été ajouté dans -le script d'installation de \TL{} pour produire une distribution proche de -l'ancienne te\TeX). La distribution \TL{} existe déjà sous forme de paquets -Debian, espérons que les autres acteurs du monde Linux (RedHat, SuSe, etc.) -suivront et que les utilisateurs se verront proposer à l'avenir des -distributions \TeX{} riches et plus faciles à installer. - -Remarque finale : toutes les anciennes distributions \TL{} ainsi que les -jaquettes des \CD{} correspondants sont disponibles ici : -\url{ftp://tug.org/historic/systems/texlive}. - -\subsection{L'édition 2008} -\label{tlcurrent} - -En 2008, l'infrastructure de la distribution \TL{} a été entièrement remaniée. -Un nouveau fichier texte, \filename{tlpkg/texlive.tlpdb}, regroupe toutes les -informations concernant la configuration \TL{} de la machine. - -Ce fichier permet entre autres choses de procéder à des mises à jour par le -réseau après l'installation initiale. Cette possibilité était offerte depuis -des années par MiK\TeX. Nous espérons pouvoir fournir des mises à jour -régulières du contenu des archives \CTAN. - -Le nouveau moteur Lua\TeX\ (\url{http://luatex.org}) a été intégré ; -il offre de nouvelles fonctionnalités typographiques et repose -sur l'excellent langage de commande Lua qui peut aussi être utilisé -en dehors de \TeX. - -Les versions Windows et Unix sont beaucoup plus proches que par le passé. -En particulier les scripts en Perl et en Lua sont communs aux deux -architectures. - -\TL{} dispose d'une nouvelle interface pour la maintenance (\cmdname{tlmgr} -voir section~\ref{sec:tlmgr}), elle permet les ajouts, mises à jour et -suppressions de composants et prend en charge la régénération des bases -\texttt{ls-R}, des formats et des fichiers \filename{.map} lorsque c'est -nécessaire. - -Les fonctionnalités de \cmdname{tlmgr} englobent toutes les tâches dévolues -auparavant à \cmdname{texconfig} qui ne devrait plus être utilisé (il est -conservé mais avec un champ d'action réduit). - -Le programme d'indexation \cmdname{xindy} (\url{http://xindy.sourceforge.net/}) -est maintenant disponible pour la plupart des plates-formes. - -L'utilitaire \cmdname{kpsewhich} dispose de deux options nouvelles : -\optname{--all} qui retourne toutes les occurrences du fichier recherché -et \optname{--subdir} qui limite la recherche à un sous-répertoire donné. - -Le programme \cmdname{dvipdfmx} permet maintenant d'extraire les informations -concernant la \textit{bounding box} par le biais de la commande -\cmdname{extractbb}; c'était une des dernières fonctionnalités de -\cmdname{dvipdfm} qui manquaient à \cmdname{dvipdfmx}. - -Les alias de polices \filename{Times-Roman}, \filename{Helvetica}, etc. -ont été supprimés, les conflits de codage qu'ils induisaient n'ayant pas pu -être résolus. - -Le format \pkgname{platex} a été supprimé afin de résoudre un conflit de nom -avec son homonyme japonais ; le support pour le polonais est assuré -maintenant par l'extension \pkgname{polski}. - -Les fichiers \web{} d'extension \filename{.pool} sont maintenant inclus dans -les binaires afin de faciliter les mises à jour. - -Enfin, les changements décrits par Donald Knuth dans « \TeX\ tuneup of 2008 » -(voir \url{http://tug.org/TUGboat/Articles/tb29-2/tb92knut.pdf}) sont inclus -dans la présente édition. - -\subsection{Versions futures} - -\emph{\TL{} n'est pas un produit parfait !} (et ne le sera jamais). -Nous prévoyons de continuer à produire de nouvelles versions et aimerions -fournir plus d'aide, de fonctionnalités, de programmes d'installation et -(bien sûr) une arborescence améliorée et vérifiée de macros et de fontes. Ce -travail est effectué par des volontaires débordés, dans la limite de leur -temps libre et beaucoup reste à faire. Si vous pouvez nous aider, n'hésitez -pas à nous contacter, voir \url{http://tug.org/texlive/contribute.html}. - -Corrections, suggestions et propositions d'aide doivent être envoyées à : -\begin{quote} -\email{tex-live@tug.org} \\ -\url{http://tug.org/texlive} -\end{quote} - -\medskip -\noindent \textsl{Bon travail avec \TeX{} !} - -\end{document} - -%%% Local Variables: -%%% mode: latex -%%% mode: flyspell -%%% ispell-local-dictionary: "francais" -%%% TeX-master: t -%%% coding: utf-8 -%%% End: diff --git a/Master/texmf-doc/source/texlive/texlive-pl/Makefile b/Master/texmf-doc/source/texlive/texlive-pl/Makefile deleted file mode 100644 index 4f0d8cc9985..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-pl/Makefile +++ /dev/null @@ -1,3 +0,0 @@ -include ../texlive-en/Makefile -doc = texlive-pl -lang = polish diff --git a/Master/texmf-doc/source/texlive/texlive-pl/live4ht.cfg b/Master/texmf-doc/source/texlive/texlive-pl/live4ht.cfg deleted file mode 100644 index 2927d07cb93..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-pl/live4ht.cfg +++ /dev/null @@ -1,52 +0,0 @@ -% tex4ht configuration file for the TeX Live documentation. -% Accumulated over many years. Public domain. -% -% html specifies the main output format. -% info for extra debugging info in the log files. - -% have html in one piece (including footnotes). -%\Preamble{charset=iso-8559-2,html,info,fn-in} -\Preamble{html,info,fn-in} - -% add extra stylesheet -\Configure{@HEAD}{\HCode{% -\Hnewline -\Hnewline -}} -% use png graphics as-is -\Configure{graphics*} - {png} - {\Needs{""}% - \Picture[pict]{\csname Gin@base\endcsname.png}% - } -% or LaTeX complains it is missing. -\begin{document} - -\EndPreamble - -% simplify output for HTML. We leave TeX and LaTeX alone, since tex4ht -% actually does the lowered E (and raised A) in CSS. -%\def\OMEGA{Omega} -\def\LaTeXe{LaTeX2e} -\def\eTeX{e-\TeX} -\def\acro#1{#1} -\def\MF{Metafont} -\def\BibTeX{BibTeX} -\def\warningbox{} -\def\endwarningbox{} -\def\Thanh{H\`an Th\^e Th\`anh} - -\Configure{crosslinks}{[}{] - }{nastêpny}{poprzedni}{wstecz} - {pocz±tek}{koniec}{spis} - -\ifx\tldocenglish\undefined \else - % these definitions cause "missing } inserted" at \end{tabularx} in - % other langs. don't know why. - % - % don't make these into links, as happens with \path. We only have a couple - % special characters that actually occur. - \def\dirname{\texttt\bgroup\catcode`\$=12 \catcode`\_=12 \finishliteral} - \def\finishliteral#1{#1\egroup} - \let\filename=\dirname -\fi diff --git a/Master/texmf-doc/source/texlive/texlive-pl/tex-livep.sty b/Master/texmf-doc/source/texlive/texlive-pl/tex-livep.sty deleted file mode 100644 index e81908a5d47..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-pl/tex-livep.sty +++ /dev/null @@ -1,446 +0,0 @@ -% TeX Live documentation style. Written by many people over many years. -% Public domain. -% -\NeedsTeXFormat{LaTeX2e}[1995/12/01] -\ProvidesPackage{tex-livep}[2008/07/31 v1.6 TeX Live documentation style] -% -\RequirePackage{alltt} -\RequirePackage{array} -\RequirePackage{colortbl} -\RequirePackage{comment} -\RequirePackage{float} -\RequirePackage{graphicx} -\RequirePackage{longtable} -\RequirePackage{shortvrb} -\RequirePackage[normalem]{ulem} -\RequirePackage[obeyspaces]{url} -\RequirePackage{xspace} -% -\RequirePackage{lmodern} -\usepackage{textcomp}% including \textbullet -\usepackage[T1]{fontenc} -%\usepackage[latin1]{inputenc} -% -% for a proper \acro command (even in the context of the definition in -% ltugboat -- \DRC overrides without checking) -\RequirePackage{relsize} -%\DeclareRobustCommand{\acro}[1]{\textsmaller{#1}\@} -\def\acro#1{\textscale{.9}{#1}\@} -% -\RequirePackage{fancyvrb} -\DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=\normalsize} -\DefineVerbatimEnvironment{fverbatim}{Verbatim}{fontsize=\footnotesize} -\DefineVerbatimEnvironment{sverbatim}{Verbatim}{fontsize=\small} -\DefineVerbatimEnvironment{boxedverbatim} - {Verbatim}{fontsize=\scriptsize,frame=single} -\DefineVerbatimEnvironment{Verbatim}{Verbatim}{fontsize=\normalsize} -\def\verbatiminput#1{\VerbatimInput[fontsize=\scriptsize]{#1}} -\def\boxedverbatiminput#1{\VerbatimInput[frame=single,fontsize=\scriptsize]{#1}} -\def\listinginput#1#2{\VerbatimInput[fontsize=\scriptsize,firstnumber=#1,numbers=left]{#2}} -\MakeShortVerb\| -% -% -% Done with packages. -% -% Page layout. -\advance\textwidth by 1.1in -\advance\oddsidemargin by -.55in -\advance\evensidemargin by -.55in -% -\advance\textheight by 1in -\advance\topmargin by -.5in -\advance\footskip by -.5in -\pagestyle{headings} -% -% LaTeX parameters. -\renewcommand{\topfraction}{0.85} -\renewcommand{\floatpagefraction}{0.86} -\renewcommand{\textfraction}{0.1} -\renewcommand{\abovecaptionskip}{4pt} -\renewcommand{\belowcaptionskip}{4pt} -\setcounter{tocdepth}{3} -\setcounter{secnumdepth}{3} -\setcounter{topnumber}{5} -\setcounter{totalnumber}{5} -% -% linebreaking, etc. -\hbadness=4000 -\vbadness=4000 -\emergencystretch=.1\hsize -\relpenalty=500 -% -\def\slash{/\penalty\z@\hskip\z@skip } -% -% various sorts of names -\newcommand*{\pkgname}[1]{\textsf{#1}}% package name -\newcommand*{\optname}[1]{\texttt{#1}}% (package,class) option name -\newcommand*{\cmdname}[1]{\textsf{#1}}% command name -\newcommand*{\colname}[1]{\emph{#1}}% collection name -\newcommand*{\dirname}[1]{\path{#1}}% directory name -\newcommand*{\filename}[1]{\path{#1}}% file name -\newcommand*{\envname}[1]{\texttt{#1}}% environment variable name -\newcommand{\code}[1]{\texttt{#1}} -\newcommand{\file}[1]{\texttt{#1}} -\newcommand{\prog}[1]{\textsf{#1}}% same as \cmdname -\newcommand{\samp}[1]{`\texttt{#1}'} -\newcommand{\var}[1]{{\sl #1}}% not \textsl, for roman not typewriter slanted. -\newcommand{\ttvar}[1]{\texttt{\var{#1}}} -% -% underlined command input. -%\def\Ucom#1{% -% \uline{\rule[-.2\baselineskip]{0pt}{.9\baselineskip}\ttfamily #1}} -% bold command input -\def\Ucom#1{{\bfseries\ttfamily #1}} - -% \CDref is for url's with a #, where we need to write the target url and -% displayed url separately in the input, due to catcode madness. -% (We could simplify/remove this next time, I think.) -\def\CDref#1#2{\texttt{#1}} -% -% \OnCD is currently for any other reference to a file or directory in -% the distribution. PDF readers only open .pdf files, though, so we -% should change this to only use \href for those. Or more likely use -% different macros in the source. -\def\OnCD#1{\href{../../../../#1}{\path{#1}}} -% -% \href incorrectly appends .pdf to anything without an extension; these -% definitions using \hyper@linkurl do not, but they fail for .pdf -% references -- which are the only ones that work anyway. So this is -% useless, in practice. -%\def\CDref#1#2{\hyper@linkurl{#2}{../../../../#1}} -%\def\OnCD#1{\hyper@linkurl{\path{#1}}{../../../../#1}} - -% GUI menu/button/tab sequence: -\def\guiseq#1{\textsf{#1}} -\def\arw{\unskip$\rightarrow$\ignorespaces} -% -% Special names. -\def\dpi{$\,$dpi\xspace} -\def\bs{{\protect\normalfont\ttfamily\char'134}} -\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} -\def\Q#1{\par\vskip6pt\leftline{#1}\par} -\def\hyph{-} -% -% many abbreviations. -\newcommand{\CS}{$\mathcal{C}\kern-.1667em\lower.5ex% - \hbox{$\mathcal{S}$}\kern-.075em $} -\def\AFMtoTFM{\cmdname{AFM2TFM}\null} -\def\bv{\emph{Baskerville}} -\let\BV=\bv -\def\Dash{\unskip\nobreak\thinspace---\thinspace\ignorespaces} -\def\dvicopy{\cmdname{dvicopy}} -\def\dvidvi{\cmdname{dvidvi}} -\def\dvips{\cmdname{dvips}} -\def\eTeX{$\varepsilon$-\TeX} -\def\fpTeX{\textrm{fp}\TeX\xspace} -\def\GFtoDVI{\cmdname{GFtoDVI}\null} -\def\GFtoPK{\cmdname{GFtoPK}\null} -\def\GFtype{\cmdname{GFtype}} -\def\GUI{\acro{GUI}\xspace} -\def\KPS{Kpathsea} -\def\La{La} -\def\OMEGA{$\Omega$} -\def\OzMF{OzMF} -\def\OzMP{OzMP} -\def\OzTeX{O\kern-.03em z\kern-.15em\TeX} -\def\p.{p.\,} -\def\PKtype{\cmdname{PKtype}} -\def\PLtoTF{\cmdname{PLtoTF}\null} -\def\ProTeXt{Pro\TeX t} -\def\teTeX{\textrm{te}\TeX\xspace} -\def\TeXLive{\TeX{} Live\xspace} -\def\TFtoPL{\cmdname{TFtoPL}\null} -\def\TK{\TeX\ Collection} -\let\TL=\TeXLive -\def\TypeI{Type~1} -\def\VFtoVP{\cmdname{VFtoVP}\null} -\def\VPtoVF{\cmdname{VPtoVF}\null} -\def\Thanh{H\`an~Th\ifx % get Unicode char in tex4ht's HTML output - \HCode\UnDef\^e\llap{\raise 0.5ex\hbox{\'{}}}\else - \HCode{\string&\#x1EBF;}\fi~Th\`anh} -\def\XEmTeX{\textrm{XEm}\TeX\xspace} -\def\XEmacs{\textrm{XEmacs}\xspace} -\def\XeTeX{Xe\TeX\xspace} -\def\Webc{Web2C} -\providecommand*{\CD}{\acro{CD}\xspace} -\providecommand*{\CTAN}{\acro{CTAN}\xspace} -\providecommand*{\DVD}{\acro{DVD}\xspace} -\providecommand*{\GNU}{\acro{GNU}\xspace} -\providecommand*{\HTML}{\acro{HTML}\xspace} -\providecommand*{\MacOSX}{Mac\,\acro{OS\,X}\xspace} -\providecommand*{\PS}{Post\-Script\xspace} -\providecommand*{\TDS}{\acro{TDS}\xspace} -\providecommand*{\dvi}{\acro{DVI}\xspace} -\providecommand*{\web}{\texttt{WEB}\xspace} - -% Include an image. -% #1 - name of image (pictures/#1.jpg, always .jpg please) -% #2 - bb for html -% #3 - width for TeX -% -\def\tlimage#1#2#3{% - \ifnum \Status=2 % html, want relative path in output - \includegraphics[#2]{../../general/texlive-common/pictures/#1.jpg} - \else % not html, handled by TEXINPUTS in Makefile - \includegraphics[width=#3]{pictures/#1.jpg} - \fi - \\[5mm] -} - -\def\tlpng#1#2{% - \ifnum \Status=2 % html, want relative path in output - \includegraphics[bb=0 0 1 1]{#1.png}% - \else % not html, handled by TEXINPUTS in Makefile - \includegraphics[width=#2]{#1.png}% - \fi -} - -% -% description-like environment that uses tt instead of bf, and doesn't -% go to the left margin. Without the \hfil, get an underfull box. -% Don't know why \descriptionlabel doesn't. -% -\newenvironment{ttdescription} - {\begin{list}{label must be supplied}{% - \itemsep=0pt % these lists tend to have short descriptions - \parindent=0pt - \let\makelabel=\ttdescriptionlabel}}% - {\end{list}} -\newcommand*\ttdescriptionlabel[1]{\hspace\labelsep - \normalfont\ttfamily #1\hfil} -% -% Likewise, for commands using sans serif. -\newenvironment{cmddescription} - {\begin{list}{label must be supplied}{% - \itemsep=0pt - \let\makelabel=\cmddescriptionlabel}}% - {\end{list}} -\newcommand*\cmddescriptionlabel[1]{\hspace\labelsep - \normalfont\sffamily #1\hfil} - -% General squeezed itemize. -\newenvironment{itemize*}% - {\begin{itemize}% - \setlength{\itemsep}{0pt}% - \setlength{\parskip}{0pt}}% - {\end{itemize}} - -\newsavebox{\wbox} -\newenvironment{warningbox} - {\begin{lrbox}{\wbox} - \begin{minipage}{.95\textwidth}} - {\end{minipage}\end{lrbox}\fbox{\usebox{\wbox}}} -% -% lrbox is used as a representation marking. I changed it to -% lrBox in tne source file, to get closer to logical marking -\newsavebox{\mylrbox} -\newenvironment{lrBox} - {\begin{lrbox}{\mylrbox}} - {\end{lrbox}} - - -% emacs-page output setup -% -\ifx \HCode\UnDef - \providecommand{\Status}{0}% running TeX -\else - \providecommand{\Status}{2}% running TeX4ht -\fi -%\typeout{Status is \Status} -% -\newif\ifSingleColumn -% -% By default, we won't be creating hyperlinks. -\def\href#1#2{#2} -\def\hypertarget#1#2{} -\def\email#1{\href{mailto:#1}{\path{#1}}} % \path comes from url -% -\definecolor{hypercolor}{rgb}{0.5,0.0,0.5} % purplish external links. -% -% -\ifcase\Status - % \Status = 0 - \typeout{TeX Live documentation in DVI format} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - \or - % \Status = 1 - \typeout{TeX Live documentation in PDF format} - \RequirePackage[breaklinks, - colorlinks,linkcolor=hypercolor,citecolor=hypercolor, - urlcolor=hypercolor,filecolor=hypercolor, - bookmarksopen, - %pdfstartview={FitBH -320000}, % fails with acrobat7 - hyperindex] - {hyperref} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - \or - % \Status = 2 - \typeout{TeX Live documentation in HTML format} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - % read our config file, live4ht.cfg; q.v., for more definitions. - % hyperref load must come after the tex4ht load. - \RequirePackage[live4ht]{tex4ht} - \RequirePackage[tex4ht]{hyperref} \hyperlinkfileprefix{} - % definitions need simplifying for TeX4ht to make relative paths work. - \def\CDref#1#2{\href{../../../../#1}{#2}} - \def\OnCD#1{\href{../../../../#1}{#1}} - \or - % \Status = 3 - \typeout{TeX Live documentation as a Baskerville issue} - \@ifundefined{Fonts}% - {\RequirePackage{ae}}% - {\RequirePackage[T1]{\Fonts}} - \RequirePackage{bvoutln}% outline of baskerville - \SingleColumnfalse - \RequirePackage{multicol} - \or - % \Status = 4 - \typeout{TeX Live documentation as a TUB article} - \@ifundefined{Fonts}% - {\RequirePackage{ae}}% - {\RequirePackage[T1]{\Fonts}} - \SingleColumnfalse - \newenvironment{multicols}[1]{}{} -\fi -% -\ifnum \Status=4 -\else - \RequirePackage{texnames} - \providecommand\TeXXeT{\TeX-{}-% - \kern-.1emX\kern-.125em\lower.5ex\hbox{E}\kern-.1667emT\@} - \def\MP{MetaPost} - \let\mf\MF - \newcommand\ConTeXt{C\kern-.0333emon\-\kern-.0667em\TeX\kern-.0333emt} - \newcommand\MIKTEX{MiK\kern-.025em \TeX}% per www.miktex.org - % from pictex.tex: - \ifx\PiC\undefined \def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC} \fi - \ifx\PiCTeX\undefined \def\PiCTeX{\PiC\kern-.11em\TeX} \fi -\fi -% -% hacking at sections etc., to pay attention to baskerville status -\newcommand{\@condend@multicols}{% - \ifSingleColumn - \else - \def\@tempa{multicols}% - \ifx\@tempa\@currenvir - \end{multicols}% - \fi - \fi -} -\let\Section\section -\renewcommand{\section}{% - \@ifstar - {\Section*}% - {% - \@condend@multicols - \@dblarg\@full@section - }% -} -\def\@full@section[#1]#2{% - \Section[#1]{#2}% - \ifSingleColumn\else\begin{multicols}{2}\fi -} -\let\SubSection\subsection -\renewcommand{\subsection}{% - \@ifstar{\SubSection*}% - {% - \@condend@multicols - \@dblarg\@full@subsection - } -} -\def\@full@subsection[#1]#2{% - \SubSection[#1]{#2}% - \ifSingleColumn\else\begin{multicols}{2}\fi -} - -% calm things down a bit if we're in a multiple-column version -\ifSingleColumn -\else - \def\@listI{\leftmargin\leftmargini - \parsep \z@ - \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ - \itemsep \z@ \@plus .1\p@ - } - \let\@listi\@listI - \@listi - \def\@listii{\leftmargin\leftmarginii - \labelwidth\leftmarginii\advance\labelwidth-\labelsep - \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ - \parsep \z@ - \itemsep \z@ \@plus .1\p@ - } - \def\@listiii{\leftmargin\leftmarginiii - \labelwidth\leftmarginiii\advance\labelwidth-\labelsep - \topsep 1\p@ \@plus 1\p@ \@minus 1\p@ - \parsep \z@ - \partopsep \z@ - \itemsep \topsep - } - \def\@listiv{\leftmargin\leftmarginiv - \labelwidth\leftmarginiv\advance\labelwidth-\labelsep - } - \def\@listv{\leftmargin\leftmarginv - \labelwidth\leftmarginv\advance\labelwidth-\labelsep - } - \def\@listvi{\leftmargin\leftmarginvi - \labelwidth\leftmarginvi\advance\labelwidth-\labelsep - } -\fi -% -% array package stuff -\def\arraybackslash{\let\\=\@arraycr} -\newcolumntype{P}[1]{>{\raggedright\arraybackslash}p{#1}} -% -% shaded rows (using facilities of colortbl) -% -\definecolor{pale}{gray}{.9} -\newcount\colrow -\gdef\RowColor{pale} -\def\SetRowColor{% - \rowcolor{\RowColor}% - \global\advance\colrow by1\relax - \ifodd\colrow - \gdef\RowColor{pale}% - \else - \gdef\RowColor{white}% - \fi -} -% redefine to hack up a reference even though we don't need it... -\renewcommand\@bibitem[1]{\if@filesw \immediate\write\@auxout - {\string\bibcite{#1}{?}}\fi\ignorespaces} -% -% \unknownTeXlive is a dummy texlive entry for the biblio -\newcommand\unknownTeXlive[2][\relax]{\textbf{\textsc{unknown}}% - \global\@all@unknown\expandafter{\the\@all@unknown{#2}}% -} -\newtoks\@all@unknown -\global\@all@unknown{} -\AtEndDocument{\@message@unknowns} -\def\@message@unknowns{\edef\@tempa{\the\@all@unknown}% - \ifx\@tempa\@empty - \else - \def\@tempa{*** TeX live package location of }% - \expandafter\@output@unknowns\the\@all@unknown\@empty - \fi -} -\def\@output@unknowns#1{\edef\@tempb{#1}% - \ifx\@tempb\@empty - \typeout{ unknown}% - \else - \message{\@tempa#1,}% - \def\@tempa{}% - \expandafter\@output@unknowns - \fi -} - - -% Silence font warnings about no bold typewriter in LM. -\def\@font@warning#1{}% - -% Silence hyperref warnings about \kern. -\def\HyPsd@Warning#1{}% - -\endinput diff --git a/Master/texmf-doc/source/texlive/texlive-pl/texlive-pl.tex b/Master/texmf-doc/source/texlive/texlive-pl/texlive-pl.tex deleted file mode 100644 index 0378da6518b..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-pl/texlive-pl.tex +++ /dev/null @@ -1,3335 +0,0 @@ -% iso8859-2 -% $Id: live.tex, v. 36 2008/08/17 -% TeX Live documentation. -% Originally written by Sebastian Rahtz and Michel Goossens, -% now maintained by Karl Berry and others. -% Polish translation and additions by Staszek Wawrykiewicz et al. -% Public domain. -% ---- -% UWAGA dla recenzentów/t³umaczy: %%! to moje komentarze (StaW) -\documentclass{article} -\let\tldocenglish=0 % for live4ht.cfg -\def\La{La} -\let\textsl\textit -\usepackage{tex-livep} -\usepackage{polski} %% for PL -\usepackage[latin2]{inputenc} %% for PL -\exhyphenpenalty=10000 %% for PL -\def\Dash{---} -\widowpenalty=10000 -\clubpenalty=10000 -%% redefined MF logo! %% for PL -%\def\MF{\textlogo{META}\-\textlogo{FONT}} %% for PL -%\def\MP{\textlogo{META}\-\textlogo{POST}} %% *** TP *** -\def\shac{\char178} % for PL + qtmr (HTML) -\def\aac{\char225} % for PL + qtmr (HTML) -\def\iac{\char237} % for PL + qtmr (HTML) -\renewcommand{\samp}[1]{,,\texttt{#1}''} %% for PL -%% Polish style for sections -\makeatletter -\renewcommand{\@seccntformat}[1]{% - \csname the#1\endcsname.\hspace{.5em}} %% -\def\numberline#1{\hb@xt@\@tempdima{#1.\hfill}} -\makeatother -\hyphenation{tex-basic la-tex pdf-tex} -%% ----- -\begin{document} - -\title{{\huge \textit{Przewodnik po \protect\TL}\\[1ex]} - {\LARGE \textsf\TL{} 2008} -} - -\author{Redakcja: Karl Berry \\[3mm] - \url{http://tug.org/texlive/} -} - -\date{Sierpieñ 2008} - -\maketitle - -\begin{multicols}{2} -\tableofcontents -%\listoftables -\end{multicols} -%-------------------------- -\section{Wstêp}\label{sec:intro} - -\subsection{\TeX\ Live i \TeX\ Collection} -Niniejsza dokumentacja opisuje oprogramowanie \TL{} -- -dystrybucjê \TeX-a wraz z~programami pomocniczymi, dostêpn± dla -systemów \acro{GNU}/Linux, ró¿nych wersji Unix (w~tym \MacOSX{}) -oraz Windows. - -\TL{} mo¿na ¶ci±gn±æ z~sieci b±d¼ otrzymaæ na p³ytce \DVD \TK{}, dostarczanej -swoim cz³onkom przez Grupy U¿ytkowników Systemu \TeX{} . -Czê¶æ \ref{sec:tl-coll-dists} omawia pokrótce zawarto¶æ tej p³ytki. -Zarówno \TL{}, jak i \TK{} powsta³y dziêki zbiorowemu wysi³kowi Grup. -W~tym dokumencie omówimy g³ównie sam± dystrybucjê \TL. - -\TL{} zawiera skompilowane programy: \TeX{}, \LaTeXe{}, \mbox{\MF}, \MP, -\BibTeX{} i~wiele innych oraz bogaty zestaw pakietów makr o~wielorakim -zastosowaniu, a tak¿e fonty i~dokumentacje. Wszystko to umo¿liwia sk³ad -publikacji w~wielu jêzykach. - -Pakiety zawarte w~\TL{} s± regularnie aktualizowane z serwerów \acro{CTAN}: -\url{http://www.ctan.org}. - -Lista najwa¿niejszych zmian dokonanych w~tej edycji \TL{} -znajduje siê w~czê¶ci~\ref{sec:tlcurrent}, na str.~\pageref{sec:tlcurrent}. - %w~czê¶ci~\ref{sec:history}, na str.~\pageref{sec:history}. - -Nie opisujemy tu, czym jest system \TeX{}, a~jedynie kwestiê instalacji -i~konfiguracji oprogramowania \TL. -Pocz±tkuj±cy u¿ytkownicy mog± siê zapoznaæ z~podstawowymi pojêciami -np. w~artykule {\it Przewodnik po systemie \TeX\/}: -\OnCD{texmf-doc/doc/polish/tex-virtual-academy-pl/cototex.html}. - -\subsection{Obs³ugiwane systemy operacyjne} -\label{sec:os_support} - -\TL{} zawiera oprogramowanie dla wielu platform linuksowych i uniksowych, -w~tym \MacOSX. Za³±czone pliki ¼ród³owe pozwalaj± te¿ na instalacjê -na dodatkowych platformach. - -Spo¶ród systemów Windows obs³ugiwane s± tylko wersje 2000 i nowsze. -Zaniechano wsparcia dla Windows~9x, ME oraz NT, których obs³uga by³a bardzo -pracoch³onna (w~porównaniu z~Linux/Unix). Wprawdzie brak jest -oprogramowania na wersje 64-bitowe, ale aplikacje 32-bitowe powinny na nich -dzia³aæ. - -W czê¶ci \ref{sec:tl-coll-dists} omówiono alternatywne dystrybucje, -przeznaczone dla Windows oraz \MacOSX. - -\subsection{Podstawy instalacji \protect\TL{}} -\label{sec:basic} - -\TL{} mo¿na zainstalowaæ z~p³ytki \DVD{} lub internetu. Program instalacyjny -jest niewielki i~pozwala pobraæ z sieci wszystkie potrzebne pakiety. -Jest to wygodne, gdy potrzebujemy jedynie czê¶ci oprogramowania \TL. - -Posiadaj±c p³ytkê \DVD{}, mo¿emy nie tylko zaistalowaæ \TL{} na twardym dysku, -ale i~uruchomiæ programy bezpo¶rednio z~niej (a~nawet z~obrazu -\DVD{}, je¶li nasz system pozwala na jego zamontowanie). - -Szczegó³owy opis instalacji \TL{} znajduje siê w dalszych rozdzia³ach -tego dokumentu, tu podamy jedynie skrócony przepis: - -\begin{itemize*} - \item program instalacyjny \filename{install-tl} mo¿e dzia³aæ w~dwóch -trybach: tekstowym (domy¶lnym dla Unix/Linux) i~graficznym (tzw. \GUI, -domy¶lnym dla Windows); tryb mo¿na wymusiæ podaj±c parametr \code{-gui} -b±d¼ \code{-no-gui}; - -\item jednym z~instalowanych programów jest \prog{tlmgr} (mened¿er \TL{}), -który równie¿ mo¿na uruchomiæ w~trybie tekstowym b±d¼ graficznym; pozwala -on doinstalowaæ lub usun±æ pakiety, aktualizowaæ je z~sieci, a tak¿e -wykonaæ ró¿ne czynno¶ci konfiguracyjne. - -\end{itemize*} - -\subsection{Dostêpna pomoc} -\label{sec:help} - -Spo³eczno¶æ \TeX-owa jest bardzo aktywna i~pomocna, st±d te¿ wiêkszo¶æ -powa¿nych zapytañ nie pozostaje bez odpowiedzi. Przed zadaniem -pytania warto je uprzednio dobrze przemy¶leæ i~sformu³owaæ, poniewa¿ -respondenci to wolontariusze, w¶ród których znale¼æ siê mog± mniej lub -bardziej do¶wiadczeni u¿ytkownicy. -(Je¶li preferujemy komercyjne wsparcie techniczne, mo¿emy zamiast -\TL{} zakupiæ system u~jednego z~dostawców, których listê mo¿na znale¼æ -na \url{http://tug.org/interest.html#vendors}.) - -Oto lista ¼róde³ pomocy, w~kolejno¶ci przez nas rekomendowanej: - -\begin{description} -\item [\TeX{} \acro{FAQ}] \TeX-owy \acro{FAQ} jest obszernym zbiorem -odpowiedzi na wszelkie rodzaje pytañ, od najprostszych do najbardziej -zaawansowanych. Jest on za³±czony na \TL{} w~katalogu -\OnCD{texmf-doc/doc/english/FAQ-en}, -a~tak¿e dostêpny w~sieci: \url{http://www.tex.ac.uk/faq}. Proponujemy -zajrzeæ najpierw tam. Uruchomiono te¿ serwis \acro{FAQ} -w~jêzyku polskim: \url{http://faq.gust.org.pl}. - -\item [\TeX{} Catalogue] Je¶li poszukujemy konkretnego pakietu, fontu, -programu itp., to polecamy \TeX{} Catalogue. Jest to obszerne zestawienie -wszelkich pakietów dotycz±cych \TeX-a. Patrz: - %\OnCD{texmf-doc/doc/english/catalogue} lub - \url{http://www.ctan.org/help/Catalogue/}. - -\item [\TeX{} Web Resources] Strona \url{http://tug.org/interest.html} -zawiera wiele odsy³aczy, w~szczególno¶ci do ksi±¿ek, podrêczników -i~artyku³ów po¶wiêconych wszelkim aspektom pracy z~systemem \TeX. - -\item [archiwa pomocy] Dwa g³ówne fora pomocy to grupa -Usenet \url{news:comp.text.tex} oraz lista dyskusyjna -\email{texhax@tug.org}. Warto przeszukaæ archiwa list dyskusyjnych, -zawieraj±ce mnóstwo pytañ i odpowiedzi zbieranych przez wiele lat: -\url{http://groups.google.com/group/comp.text.tex/topics} oraz -\url{http://tug.org/mail-archives/texhax}. Nie zaszkodzi -skorzystanie z~wyszukiwarki, np. \url{http://www.google.com}. - -\item [wysy³anie pytañ] Je¶li nadal nie znajdujemy rozwi±zania problemu, -to mo¿emy wys³aæ pytanie do \dirname{comp.text.tex}, korzystaj±c z~Google, -czytnika wiadomo¶ci b±d¼ pisz±c list na adres \email{texhax@tug.org}. -Przedtem jednak \emph{nale¿y} siê zapoznaæ z~poradami dotycz±cymi sposobu -zadawania pytañ, zawartymi w~\acro{FAQ}: -\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. -Polscy u¿ytkownicy maj± do dyspozycji listê dyskusyjn± GUST (polskiej Grupy -U¿ytkowników Systemu \TeX); informacje o niej -znajdziemy na stronie \url{http://www.gust.org.pl}. - -\item [wsparcie \TL{}] Gdy chcemy zg³osiæ b³±d b±d¼ sugestie -i~komentarze dotycz±ce dystrybucji \TL{}, instalacji lub dokumentacji, -mamy do dyspozycji listê dyskusyjn± \email{tex-live@tug.org}. Je¶li kwestia -dotyczy konkretnego programu (pakietu makr itp.) z~\TL{}, -to lepiej jednak skierowaæ pytanie do osoby opiekuj±cej siê danym programem -lub na specjalistyczn± listê dyskusyjn±. - -\end{description} - -Druga strona medalu to pomaganie tym, którzy maj± problemy. Zarówno -\dirname{comp.text.tex}, jak i~\code{texhax} (oraz lista dyskusyjna GUST) -s± otwarte dla ka¿dego, -tak wiêc zapraszamy do w³±czenia siê, czytania wiadomo¶ci i~pomagania -innym w~miarê w³asnych mo¿liwo¶ci. Witamy w¶ród u¿ytkowników -systemu \TeX! - -%-------------------------- -\section{Struktura \protect\TeX\protect\ Live}\label{sec:struct-tl} - -Omówimy tutaj strukturê i~zawarto¶æ dystrybucji \TL{}, a~tak¿e \TK{} -- -p³ytki \DVD, w~sk³ad której wchodzi \TL. - -\subsection{The \protect\TeX\protect\ Collection: \TL, pro\TeX{}t, Mac\TeX} -\label{sec:tl-coll-dists} - -The \TK{} \DVD{} zawiera: - -\begin{description} - -\item [\TL] kompletny system na \acro{DVD}, z mo¿liwo¶ci± uruchamiania -bezpo¶rednio z~p³yty b±d¼ instalacji na twardym dysku; - -\item [Mac\TeX] dla systemu \MacOSX; posiada on w³asny program instalacyjny -i~dodatkowe programy dla tego systemu; strona domowa projektu: -\url{http://www.tug.org/mactex/}; - -\item [pro\TeX{}t] dystrybucja dla Windows, oparta na dystrybucji \MIKTEX{}, -rozszerzonej o~dodatkowe narzêdzia; ca³kowicie niezale¿na od \TL; -\ProTeXt\ posiada w³asny, ³atwy w~obs³udze program instalacyjny; - %i~równie¿ mo¿e byæ uruchamiany bezpo¶rednio z~p³ytki. - strona domowa projektu: \url{http://tug.org/protext}; - -\item [CTAN] zrzut zawarto¶ci archiwów \CTAN{}; - -\item [\texttt{texmf-extra}] katalog z wybranymi pakietami dodatkowymi. - -\end{description} - -\CTAN, \pkgname{protext}, i~\texttt{texmf-extra} nie spe³niaj± przyjêtych dla -\TL{} wymogów dotycz±cych swobody kopiowania, wobec tego nale¿y ten fakt -uwzglêdniæ przy redystrybucji b±d¼ modyfikacji zawarto¶ci wymienionych -katalogów. - -\subsection{G³ówne katalogi \TL} -\label{sec:tld} - -Poni¿ej wymieniono wa¿niejsze podkatalogi g³ównego katalogu dystrybucji \TL. -Na p³ytce \pkgname{live} \DVD ca³a dystrybucja \TL{} zosta³a -umieszczona w katalogu \dirname{texlive}, nie za¶ w~katalogu g³ównym -(poni¿ej traktujemy go jako katalog g³ówny we wszystkich odniesieniach -do \TL). - -\begin{ttdescription} -\item[bin] skompilowane programy \TeX-owe, zorganizowane w~podkatalogach - wed³ug platform systemowych; - -\item[readme.html] krótki wstêp z~u¿ytecznymi odno¶nikami; - -\item[source] ¼ród³a wszystkich programów, w³±cznie z~g³ównymi dystrybucjami - \Webc{} \TeX-a i~\MF{}-a; - -\item[support] ró¿ne programy pomocnicze zwi±zane z~\TeX-em, które \emph{nie} - s± domy¶lnie instalowane; - dla u¿ytkowników systemów Windows do³±czono ponadto szereg programów - (edytory, ,,shelle TeX-owe''), których zwykle brak w~typowej instalacji - Windows (programy te mog± byæ szczególnie przydatne dla pocz±tkuj±cych); - -\item[texmf] drzewo katalogów plików pomocniczych i~dokumentacji dla - \emph{programów} (patrz: \texttt{TEXMFMAIN} w~nastêpnej czê¶ci); - -\item[texmf-dist] g³ówne drzewo katalogów formatów i~pakietów (zawiera makra, - fonty i~dokumentacje; patrz: \texttt{TEXMDIST} w~nastêpnej czê¶ci); - -\item[texmf-doc] drzewo samodzielnych dokumentacji (m.in. podrêczniki itp.), - niezwi±zane z~konkretnymi pakietami, zorganizowane wed³ug jêzyków. - -\item[tlpkg] skrypty, programy i~inne dane potrzebne do instalacji; - katalog zawiera tak¿e ,,prywatne'' dla \TL{} kopie systemów Perl i~Ghostscript - dla Windows (nie koliduj± one z~posiadanymi przez u¿ytkownika podobnymi - programami i~dzia³aj± tylko w~ramach instalacji); poza tym do³±czono - szybki i~wygodny program do podgl±du plików postscriptowych (a~tak¿e PDF) - -- PS\_View dla Windows. -\end{ttdescription} - -Prócz podkatalogów wymienionych powy¿ej, katalog g³ówny zawiera skrypty -instalacyjne oraz pliki \filename{README}, w~formacie tekstowym lub HTML, -w~kilku jêzykach (równie¿ polskim). - -Katalog \dirname{texmf-doc} zawiera, jak wspomniano wy¿ej, dokumentacje -ogólne, np. podrêczniki (tak¿e po polsku). Dokumentacje programów (man, info, -tak¿e w~formacie PDF) znajduj± siê w~katalogu -\dirname{texmf/doc}, za¶ dokumentacje pakietów makr, fontów i~formatów -w~katalogu \dirname{texmf-dist/doc}. W~odszukaniu konkretnej -dokumentacji w~dowolnym z~wymienionych katalogów mog± pomóc -programy \cmdname{texdoc} lub \cmdname{texdoctk}. Pomocnym mo¿e te¿ byæ -plik \OnCD{doc.html}, który znajdziemy w~g³ównym katalogu. - -Niniejsza dokumentacja w~kilku jêzykach znajduje siê w katalogu -\dirname{texmf-doc}: - -\begin{itemize*} -\item{uproszczony chiñski:} \OnCD{texmf-doc/doc/chinese/texlive-zh-cn} -\item{czeski/s³owacki:} \OnCD{texmf-doc/doc/czechslovak/texlive-cz} -\item{angielski:} \OnCD{texmf-doc/doc/english/texlive-en} -\item{francuski:} \OnCD{texmf-doc/doc/french/texlive-fr} -\item{niemiecki:} \OnCD{texmf-doc/doc/german/texlive-de} -\item{polski:} \OnCD{texmf-doc/doc/polish/texlive-pl} -\item{rosyjski:} \OnCD{texmf-doc/doc/russian/texlive-ru} -\end{itemize*} - -\subsection{Predefiniowane drzewa katalogów texmf} -\label{sec:texmftrees} - -W tej czê¶ci wymieniono wszystkie u¿ywane przez system, predefiniowane zmienne -specyfikuj±ce drzewa katalogów texmf, omówiono te¿ ich przeznaczenie. -Uruchomiaj±c polecenie \texttt{texconfig conf}, zobaczymy warto¶ci tych -zmiennych, dziêki czemu ³atwo ustalimy, które katalogi w~naszej instalacji s± -przypisane do konkretnych zmiennych. - -\begin{ttdescription} -\item [TEXMFMAIN] Drzewo katalogów zawieraj±ce podstawowe dla - dystrybucji elementy systemu, jak skrypty (np. \verb+web2c/mktexdir+), - i~inne pliki pomocnicze oraz ich dokumentacjê (nie zawiera zatem - pakietów makr ani formatów). -\item [TEXMFDIST] Drzewo katalogów zawieraj±ce pakiety makr, fontów itp., - tak jak s± one oryginalnie dystrybuowane; drzewo to mo¿e byæ - wspó³dzielone z~dowoln± dystybucj±. -\item [TEXMFLOCAL] Drzewo katalogów, które administratorzy mog± wykorzystaæ - do przechowywania lokalnych makr, fontów itp., dostêpnych dla wszystkich - u¿ytkowników serwera. -\item [TEXMFHOME] Drzewo katalogów dla prywatnych makr, fontów itp. - u¿ytkownika. Rozwiniêcie tej zmiennej zale¿y domy¶lnie od warto¶ci przypisanej - zmiennej systemowej \verb+$HOME+ (w~Windows \verb+%USERPROFILE%+). -\item [TEXMFCONFIG] Drzewo katalogów wykorzystywane przez narzêdzia - \verb+texconfig+, \verb+updmap+ oraz \verb+fmtutil+ do przechowywania - danych konfiguracyjnych (domy¶lnie w~ramach \envname{TEXMFHOME}). -\item [TEXMFSYSCONFIG] Drzewo katalogów wykorzystywane przez narzêdzia - \verb+texconfig-sys+, \verb+updmap-sys+ oraz \verb+fmtutil-sys+ - do przechowywania danych konfiguracyjnych dla ca³ej instalacji. -\item [TEXMFVAR] Drzewo katalogów wykorzystywane przez \verb+texconfig+, - \verb+updmap+ i~\verb+fmtutil+ do przechowywania wygenerowanych plików - formatów i~map fontowych (domy¶lnie w~ramach \envname{TEXMFHOME}). -\item [TEXMFSYSVAR] Drzewo katalogów wykorzystywane przez - \verb+texconfig-sys+, \verb+updmap-sys+ oraz \verb+fmtutil-sys+, a~tak¿e - przez program \verb+tlmgr+ do przechowywania wygenerowanych plików - formatów i~map fontowych dla ca³ej instalacji. -\end{ttdescription} - - %Wiêcej informacji na temat \texttt{texconfig} znajdziemy - %w~czê¶ci~\ref{sec:texconfig}, na str.~\pageref{sec:texconfig}. - -\noindent -Domy¶lny uk³ad katalogów: -\begin{description} - \item[ogólnosystemowy katalog instalacji] mo¿e zawieraæ kilka wydañ \TL{}: - \begin{ttdescription} - \item[2007] poprzednie wydanie, - \begin{ttdescription} - \item [...] - \end{ttdescription} - \item[2008] wydanie aktualne: - \begin{ttdescription} - \item [bin] ~ - \begin{ttdescription} - \item [i386-linux] programy dla \GNU/Linux - \item [...] - \item [universal-darwin] programy dla \MacOSX - \item [win32] programy dla Windows - \end{ttdescription} - \item [texmf] okre¶lany zmienn± \envname{TEXMFMAIN} - \item [texmf-dist] \envname{TEXMFDIST} - \item [texmf-doc] \envname{TEXMFDOC} - \item [texmf-var] \envname{TEXMFSYSVAR} - \item [texmf-config] \envname{TEXMFSYSCONFIG} - \end{ttdescription} - \item [texmf-local] \envname{TEXMFLOCAL}, katalog zachowywany - od wydania do wydania, - \end{ttdescription} - \item[katalog domowy u¿ytkownika] (\texttt{\$HOME} lub - \texttt{\%USERPROFILE\%}) - \begin{ttdescription} - \item[.texlive2007] prywatne pliki konfiguracyjne - poprzedniego wydania: - \item[.texlive2008] prywatne pliki konfiguracyjne - dla bie¿±cego wydania: - \begin{ttdescription} - \item [texmf-var] \envname{TEXMFVAR} - \item [texmf-config] \envname{TEXMFCONFIG} - \end{ttdescription} - \item[texmf] \envname{TEXMFHOME} prywatne makra, fonty itp. - \end{ttdescription} -\end{description} - -\subsection{Rozszerzenia \protect\TeX-a} -\label{sec:tex-extensions} - -Standardowy \TeX{} zosta³ zamro¿ony, ale jest i~bêdzie w~przysz³o¶ci dostêpny -w~dystrybucji. \TL{} zawiera ponadto kilka wersji rozszerzonych -standardowego \TeX-a: - -\begin{description} -\item [\eTeX] wersja \label{text:etex} programu \TeX{}, w~której dodano - po¿yteczny zestaw nowych poleceñ wbudowanych - (dotycz±cych g³ównie rozwijania makr, leksemów znakowych, interpretacji - znaczników itp.) oraz rozszerzenie \TeXXeT{} dla sk³adu - od prawej do lewej. W~trybie domy¶lnym \eTeX{} jest w~100\% zgodny ze - standardowym programem \TeX. Wiêcej szczegó³ów mo¿na znale¼æ - w~\OnCD{texmf-dist/doc/etex/base/etex_man.pdf}. - -\item [pdf\TeX] program zawieraj±cy silnik \eTeX, umo¿liwiaj±cy -tworzenie plików zarówno w~formacie PDF, jak i~\dvi{}. Jest on domy¶lnym -programem dla wiêkszo¶ci formatów (prócz plain \TeX), nie ma wiêc obecnie -rozró¿nienia na ,,maszyny'' \textsf{pdftex} i \textsf{pdfetex}, jak to mia³o -miejsce w~poprzednich wersjach programów i~w~poprzednich dystrybucjach \TL. -Podrêczniki znajdziemy w~katalogu -\OnCD{texmf-dist/doc/pdftex/manual/pdftex-a.pdf}, -za¶ przyk³ad wykorzystania -- w~pliku -\OnCD{texmf-dist/doc/pdftex/manual/samplepdf/samplepdf.tex}. - -\item [Lua\TeX] docelowo sukcesor pdf\TeX-a, z~którym ma byæ zgodny wstecz. - Powinien tak¿e zast±piæ Aleph (patrz ni¿ej). Za³±czony -interpreter Lua (patrz strona domowa \url{http://www.lua.org/}) -pozwala na eleganckie rozwi±zanie wielu trudnych problemów \TeX-a. -Program \filename{texlua} ma funkcjonalno¶æ samodzielnego -interpretera Lua, co sprawia, ¿e jest u¿ywany w~\TL{} do wielu zadañ. -Patrz \url{http://www.luatex.org/} i~na \DVD{} -\OnCD{texmf-dist/doc/luatex/luatexref-t.pdf}. - -\item [Xe\TeX] umo¿liwia kodowanie tekstów w~Unicode oraz korzystanie -z~fontów OpenType (tak¿e tych dostêpnych w~systemie operacyjnym), -przy czym stosuje biblioteki obce, patrz -\OnCD{texmf-dist/doc/xetex/XeTeX-reference.pdf} lub -\url{http://scripts.sil.org/xetex}. - -\item [\OMEGA{} (Omega)] program, który pracuje wewnêtrznie ze znakami -kodowanymi 16-bitowo (Unicode), pozwalaj±c sk³adaæ jednocze¶nie -wiêkszo¶æ tekstów spotykanych na ¶wiecie. Wspomaga dynamicznie -³adowane tzw. ,,procesy t³umaczenia \OMEGA'' (\acro{OTP}), co pozwala -u¿ytkownikowi definiowaæ z³o¿one transformacje, wykonywane na dowolnych -strumieniach wej¶ciowych. Wiêcej szczegó³ów znale¼æ mo¿na na \DVD: -\OnCD{texmf-dist/doc/omega/base/doc-1.8.tex} (dokumentacja niezbyt aktualna; -sam program te¿ od dawna nie jest aktualizowany). - -\item [Aleph] ³±czy rozszerzenia \OMEGA\ i~\eTeX; powsta³ jako niezale¿ny -projekt z~potrzeby stabilnej ,,u¿ywalno¶ci'' programu Omega, w~sytuacji -gdy ten jest ci±gle w~fazie eksperymentalnej. Minimalna dokumentacja: -\OnCD{texmf-dist/doc/aleph/base}. - -\end{description} - -\subsection{Inne wa¿niejsze programy \protect\TL} - -Poni¿ej zestawiono inne najczê¶ciej u¿ywane programy dostêpne -w~dystrybucji \TL{}: - -\begin{cmddescription} - -\item[bibtex] tworzenie spisów bibliograficznych; - -\item[makeindex] tworzenie posortowanych skorowidzów; - -\item[dvips] konwersja \dvi{} do \PS{}; - -\item[xdvi] przegl±darka plików \dvi{} dla X~Window; - -\item[dvilj] sterownik dla drukarek HP LaserJet; - -\item [dv2dt, dt2dv] konwerter \dvi{} do/z tekstu ASCII; - -\item [dviconcat, dviselect] programy do manipulacji stronami w~plikach - \dvi{}; - -\item [dvipdfmx] konwersja \dvi{} do PDF, metoda alternatywna w~stosunku - do wspomnianego wy¿ej programu pdf\TeX{} (pakiety - \pkgname{ps4pdf} i~\pkgname{pdftricks} dostarczaj± kolejnych mo¿liwo¶ci); - -\item [psselect, psnup, \ldots] narzêdzia do manipulacji na plikach -postscriptowych; - -\item [lacheck] kontrola syntaktyki plików \LaTeX-owych; - -\item [texexec, texmfstart] programy uruchamiaj±ce dla Con\TeX{}t; - -\item [tex4ht] postprocesor dla \TeX-a konwersji do HTML i XML. - -\end{cmddescription} - -%%! zostawiam tê czê¶æ, choæ wylecia³a z wersji oryginalnej!!! 27.08.2003 - -\subsection[Pakiety i ich zestawy]{Pakiety i ich zestawy} -\label{packages} -Zawarto¶æ drzew \texttt{texmf} na \TL{} zosta³a do celów instalacji -zorganizowana w~szereg ,,zestawów'' (\emph{collections}), -z~których ka¿dy posiada zbiór ,,pakietów'' (\emph{packages}; jest ich obecnie -ponad 2500). Normalna instalacja pozwala u¿ytkownikowi skopiowaæ -z~\DVD{} na twardy dysk jeden lub wiêcej zestawów, mo¿na te¿ -zainstalowaæ jedynie pojedynczy pakiet. - -Zestawy pozwalaj± lepiej dobraæ instalowane sk³adniki, a~tak¿e okre¶liæ, -jakie jêzyki bêd± obs³ugiwane po instalacji. Najwa¿niejszy zestaw, wymagany -dla wiêkszo¶ci zastosowañ, to ,,basic''. Zestawy ,,latex'' -i~,,pdftex'' s± rekomendowane dla wiêkszo¶ci u¿ytkowników. Pozosta³e -zestawy s± opcjonalne. - -Oto dostêpne zestawy i~krótki opis ich zawarto¶ci: - -\begin{description} -\item[basic] podstawowe programy, pakiety makr i~fontów systemu \TeX{}, - pliki konfiguracyjne dla podstawowych sterowników; -\item[bibtexextra] dodatkowa, obszerna biblioteka stylów Bib\TeX-owych - i~bazy danych bibliograficznych (podstawowe style znajduj± siê w~zestawie - ,,basic''); -\item[chemistry] pakiety makr do sk³adu wzorów chemicznych; -\item[context] pakiet makr do Con\TeX{}t -- ,,dialektu'' \TeX-a - autorstwa Hansa Hagena; -\item[documentation] dodatkowe, u¿yteczne dokumentacje; -\item[etex] pliki pomocnicze dla programu e-\TeX; -\item[extrabin] ró¿ne programy pomocnicze; zestaw zawiera m.in. - programy i~makra dla systemu texinfo, programy do manipulacji na plikach - DVI itp.; -\item[fontbin] programy do konwersji plików fontowych oraz testowania - i~instalacji fontów (zestaw do tworzenia fontów wirtualnych, manipulacji - plikami .gf i~.pk, programy \texttt{mft}, \texttt{fontinst} itp.); -\item[fontsrecommended] obszerna biblioteka czê¶ciej u¿ywanych fontów - w~postaci ¼ród³owej (.mf) b±d¼ fontów obwiedniowych oraz pliki z~definicjami - i~stylami \LaTeX-a dla tych fontów; -\item[fontsextra] biblioteka ró¿nych rzadziej u¿ywanych fontów; -\item[formatsextra] pliki pomocnicze do generowania dodatkowych - ,,formatów'' (tj. obszerne zestawy makr s³u¿±ce do wstêpnego przetworzenia - i~utworzenia pliku \texttt{.fmt}); -\item[games] pakiety do prezentacji zapisu ró¿nych gier (szachy, - bryd¿ itp.); -\item[genericextra] obszerna biblioteka makr, trudnych do sklasyfikowania, - dzia³aj±cych z~ró¿nymi formatami (Plain, \LaTeX{} itp.); -\item[htmlxml] pakiety konwersji \LaTeX-a do XML/HTML oraz do sk³adu - dokumentów XML/SGML; -\item[lang\dots] wsparcie poszczególnych jêzyków; zestawy zawieraj± - wzorce przenoszenia wyrazów i~makra obs³ugi danych jêzyków, czasem te¿ - specyficzne fonty itp., przyk³adowo: - %\item[langarmenian] armeñski; -%\item[langcjk] pakiety CJK (obs³uga chiñskiego, japoñskiego i~koreañskiego); -%\item[langcroatian] chorwacki; -%\item[langcyrillic] fonty i makra do sk³adu cyrylic±; -%\item[langczechslovak] fonty i pakiety makr dla czeskiego i~s³owackiego; -%\item[langdanish] duñski; -%\item[langdutch] holenderski; -%\item[langfinnish] fiñski; -%\item[langfrench] francuski; -%\item[langgerman] niemiecki; -%\item[langgreek] grecki; -%\item[langhungarian] wêgierski; -%\item[langindic] wsparcie dla jêzyków indyjskich; -%\item[langitalian] w³oski; -%\item[langlatin] ³acina; -%\item[langmanju] jêzyk Manju; -%\item[langmongolian] mongolski; -%\item[langnorwegian] norweski; -%\item[langother] wzorce przenoszenia wyrazów dla innych jêzyków; -\item[langpolish] zawiera polskie pakiety: makra do tworzenia formatu MeX, - pakiety \texttt{polski}, \texttt{mwcls}, fonty i~makra dodatkowe, - przydatne dla polskich u¿ytkowników, dokumentacje w~jêzyku polskim; -%\item[langportuguese] portugalski; -%\item[langspanish] hiszpañski; -%\item[langswedish] szwedzki; -%\item[langtibetan] fonty i~wsparcie do sk³adu tybetañskiego; -%\item[langukenglish] angielski (brytyjski); -%\item[langvietnamese] wietnamski; -\item[latex] podstawowe pakiety \LaTeX-a; -\item[latexrecommended] rekomendowany zestaw czêsto u¿ywanych pakietów - dodatkowych; -\item[latex3] pakiety-,,zwiastuny'' \LaTeX3, dzia³aj±ce z~\LaTeXe; -\item[latexextra] bogaty wybór dodatkowych pakietów dla \LaTeX-a; -\item[mathextra] dodatkowe pakiety do sk³adu zaawansowanej matematyki; -\item[metapost] MetaPost i~pakiety do tworzenia rysunków z~u¿yciem - MetaFonta; -\item[music] makra do sk³adu nutowego; -\item[omega] rozszerzenie \TeX{}a autorstwa Johna Plaice'a i~Yannisa Haralambousa, dzia³aj±ce ze znakami kodowanymi 16-bitowo; -\item[pdftex] pliki pomocnicze dla pdf\TeX{}-a, wersji programu \TeX{} - tworz±cej pliki w~formacie PDF; -\item[pictures] pakiety do tworzenia diagramów i~innych obiektów graficznych; -\item[plainextra] dodatkowe biblioteki makr dla Plain \TeX; -\item[psutils] narzêdzia do manipulacji plikami \PS-owymi; -\item[publishers] pakiety makr pochodz±ce od ró¿nych wydawnictw; -\item[t1utils] narzêdzia do obs³ugi fontów w~formacie Type~1; -\item[texbooks] przyk³ady i~inne materia³y autorstwa D.E.~Knutha; -\item[ttfutils] narzêdzia do konwersji fontów True Type. -\end{description} -%-------------------------- -%%! koniec pozostawionej sekcji 27.08.2003 - -Plik \texttt{tlpdb/texlive.tlpdb} (wykorzystywany podczas instalacji) -zawiera spis wszystkich plików w~ka¿dym pakiecie. - -\subsection{Fonty w \protect\TL} -\label{sec:tl-fonts} - -\TL{} zawiera wiele wysokiej jako¶ci fontów skalowanych. Patrz -\url{http://tug.org/fonts} oraz -\OnCD{texmf-doc/doc/english/free-math-fonts-survey}. - -%==== - -\section{Instalacja} -\label{sec:install} - -\subsection{Start instalacji} -\label{sec:inst-start} - -Instalacjê \TL{} uruchamiamy skryptem \filename{install-tl} -(\filename{install-tl.bat} dla Windows) z~p³ytki \TK{} \DVD{} -b±d¼ dostêpnym w~pobranym z~sieci pakiecie instalacyjnym. - -\begin{description} -\item [Instalator z sieci:] z~archiwum \CTAN, z~katalogu -\dirname{systems/texlive/tlnet} -(\url{http://mirror.ctan.org/systems/texlive/tlnet} automatycznie -przekierowuje do najbli¿szej kopii \CTAN) nale¿y pobraæ plik -\filename{install-tl.zip} (dla Unix i Windows) lub znacznie mniejszy -\filename{install-unx.tar.gz} (tylko dla Unix). Po rozpakowaniu, -w~katalogu \dirname{install-tl/} znajdziemy skrypty instalacyjne -\filename{install-tl} i~\filename{install-tl.bat}. - -\item [\TeX{} Collection \DVD:] po zamontowaniu p³ytki nale¿y -zmieniæ katalog bie¿±cy na \dirname{texlive} (w~Windows program -instalacyjny powinien uruchomiæ siê automatycznie). \DVD{} otrzymamy -w ramach cz³onkowstwa w~dowolnej Grupie U¿ytkowników Systemu \TeX{} -(kontakt w Polsce \url{http://www.gust.org.pl}). -\end{description} - -Dalsze kroki omówiono dok³adniej w~nastêpnych czê¶ciach. - -\subsubsection{Unix} - -\noindent -Poni¿ej \texttt{>} oznacza prompt systemu; to, co wpisuje u¿ytkownik, -zaznaczono \Ucom{\texttt{pogrubieniem}}. W~systemach zgodnych z~Unix -nale¿y wykonaæ w~oknie terminala: -\begin{alltt} -> \Ucom{cd /path/to/installer} -> \Ucom{perl install-tl} -\end{alltt} -(mo¿na tak¿e uruchomiæ \Ucom{perl /path/to/installer/install-tl} lub -\Ucom{./install-tl}; w dalszej czê¶ci nie bêdziemy powtarzaæ wszelkich -mo¿liwych kombinacji). - -Do uruchomienia w~trybie graficznym (\GUI) wymagany jest w~systemie modu³ -\dirname{Perl/TK}: -\begin{alltt} -> \Ucom{perl install-tl -gui} -\end{alltt} - -Kompletny wykaz dostêpnych opcji otrzymamy, uruchamiaj±c: -\begin{alltt} -> \Ucom{perl install-tl -help} -\end{alltt} - -\textbf{Uwaga dotycz±ca uprawnieñ w Unix:} program instalacyjny -bêdzie respektowa³ aktualn± warto¶æ \code{umask}. -Je¶li wiêc chcemy, aby instalacja by³a dostêpna dla innych, to musimy -ustawiæ warto¶æ np. \code{umask 002}. Wiêcej informacji na temat -\code{umask} znajdziemy w~podrêcznikach systemu operacyjnego. - -\begin{figure}[tb] -\begin{boxedverbatim} -======================> TeX Live installation procedure <===================== - -=======> Note: Letters/digits in indicate menu items <======= -=======> for commands or configurable options <======= - - - Detected platform: Intel x86 with GNU/Linux - - binary systems: 1 out of 16 - - Installation scheme (scheme-full) - - Customizing installation scheme: - standard collections - language collections - 83 collections out of 84, disk space required: 1666 MB - - directories: - TEXDIR (the main TeX directory): - !! default location: /usr/local/texlive/2008 - !! is not writable, please select a different one! - TEXMFLOCAL (directory for site-wide local files): - /usr/local/texlive/texmf-local - TEXMFSYSVAR (directory for variable and automatically generated data): - /usr/local/texlive/2008/texmf-var - TEXMFSYSCONFIG (directory for local config): - /usr/local/texlive/2008/texmf-config - TEXMFHOME (directory for user-specific files): - ~/texmf - - options: - [ ] use letter size instead of A4 by default - [X] create all format files - [X] install macro/font doc tree - [X] install macro/font source tree - [ ] create symlinks in standard directories - - Install for running from DVD - -Other actions: - start installation to HD - help - quit - -Enter command: -\end{boxedverbatim} -\caption{G³ówny ekran instalatora w~trybie tekstowym (\GNU/Linux)}\label{fig:text-main} -\end{figure} - -\begin{figure}[tb] -\tlpng{install-w32-main}{\linewidth} -\caption{G³ówny ekran instalatora \GUI{} (Windows)}\label{fig:gui-main} -\end{figure} - -\subsubsection{Mac\,OS\,X} - -Jak wspomniano w czê¶ci \ref{sec:tl-coll-dists}, dla \MacOSX{} -przygotowano odrêbn± dystrybucjê Mac\TeX\ (\url{http://tug.org/mactex}), -w~tym wypadku nale¿y u¿yæ dedykowanego programu instalacyjnego, gdy¿ -zmienia on w~specyficzny sposób ustawienia systemu, w~szczególno¶ci pozwala -na ³atwe prze³±czanie pomiêdzy ró¿nymi dystrybucjami \TeX-a dla -\MacOSX: Mac\TeX, gw\TeX, Fink, MacPorts,\ldots - -Mac\TeX\ jest oparty na \TL{} i g³ówne drzewa katalogów s± dok³adnie te -same, jedynie dodawane s± katalogi ze specyficznymi dla systemu -\MacOSX\ dokumentacjami i~aplikacjami. - -\subsubsection{Windows} - -Gdy u¿ywamy instalatora pobranego z~sieci (b±d¼ program ten nie uruchamia siê -automatycznie po w³o¿eniu \DVD{} do napêdu), nale¿y uruchomiæ -\filename{install-tl.bat} (np. podwójnym klikniêciem myszy). -Mo¿na to uczyniæ tak¿e z~linii poleceñ -- gdy katalog zawieraj±cy ten plik -jest bie¿±cym, wystarczy uruchomiæ: -\begin{alltt} -> \Ucom{install-tl} -\end{alltt} - -W linii poleceñ mo¿na te¿ podaæ ¶cie¿kê do programu, np.: -\begin{alltt} -> \Ucom{D:\bs{}texlive\bs{}install-tl} -\end{alltt} -dla \TK\ \DVD, zak³adaj±c, ¿e \dirname{D:} jest napêdem \DVD. - -Instalacja w~trybie tekstowym wymaga podania: -\begin{alltt} -> \Ucom{install-tl -no-gui} -\end{alltt} - -Wszystkie dostêpne opcje wy¶wietlimy uruchamiaj±c: -\begin{alltt} -> \Ucom{install-tl -help} -\end{alltt} - -\subsubsection{Instalator w trybie tekstowym} - -Rysunek \ref{fig:text-main} przedstawia g³ówny ekran programu -\filename{install-tl} w~trybie tekstowym w~systemie Unix. -W tym trybie nie u¿ywamy ani klawiszy kursora, ani myszy, -tylko wy³±cznie klawiszy cyfr i~liter (uwaga: du¿e i ma³e litery s± -rozró¿niane!). Wybran± opcjê zatwierdzamy klawiszem Enter. -Instalator w~trybie tekstowym jest dlatego tak prosty, by dzia³a³ na -mo¿liwie wielu platformach, nawet wyposa¿onych w~ubogie biblioteki Perla -(dla Windows za³±czono taki w³a¶nie podzbiór dystrybucji Perla). - -\subsubsection{Instalator w trybie graficznym} - -Rysunek \ref{fig:gui-main} pokazuje instalator w~trybie graficznym -(zrzut ekranu w systemie Windows). - -\subsection{Podczas instalacji} -\label{sec:runinstall} - -Program instalacyjny jest z~za³o¿enia na tyle prosty, ¿e szczegó³owe -wyja¶nienia s± zbêdne. Podamy jednak kilka uwag dotycz±cych ró¿nych opcji -i~dostêpnych podmenu. - -\subsubsection{Menu: binary systems (tylko Unix)} -\label{sec:binary} - -\begin{figure}[tbh] -\begin{boxedverbatim} -Available sets of binaries: (Dostêpne zestawy programów dla:) -=============================================================================== - - a [ ] alpha-linux DEC Alpha with GNU/Linux - b [ ] amd64-freebsd x86_64 with FreeBSD - c [ ] hppa-hpux HP-UX - d [ ] i386-freebsd Intel x86 with FreeBSD - e [X] i386-linux Intel x86 with GNU/Linux - f [ ] i386-openbsd Intel x86 with OpenBSD - g [ ] i386-solaris Intel x86 with Sun Solaris - h [ ] mips-irix SGI IRIX - i [ ] powerpc-aix PowerPC with AIX - j [ ] powerpc-linux PowerPC with GNU/Linux - k [ ] sparc-linux Sparc with GNU/Linux - l [ ] sparc-solaris Sparc with Solaris - m [ ] universal-darwin universal binaries for MacOSX/Darwin - o [ ] win32 Windows - p [ ] x86_64-linux x86_64 with GNU/Linux -\end{boxedverbatim} -\caption{Wybór platformy (systemu operacyjnego)}\label{fig:bin-text} -\end{figure} - -Rysunek \ref{fig:bin-text} pokazuje (w~trybie tekstowym) wybór platformy -(systemu operacyjnego). -Domy¶lnie instalowane s± tylko programy dla bie¿±cej platformy, -ale menu to pozwala wybraæ tak¿e zestaw dla innych platform. Mo¿e byæ to -przydatne do instalacji na serwerze i~wspó³dzielenia zasobów w~sieci -dla ró¿nych systemów operacyjnych b±d¼ dla instalacji - %\textit{dual-boot} - dla kilku systemów na tej samej maszynie. - -\subsubsection{Wybór tego, co ma byæ zainstalowane} -\label{sec:components} - -\begin{figure}[tbh] -\begin{boxedverbatim} -Select a scheme: (Wybór schematu do instalacji:) -=============================================================================== - - a [ ] TeX Live basic scheme - b [ ] TeX Live scheme for ConTeXt - c [X] TeX Live full scheme - d [ ] GUST TeX Live scheme - e [ ] GUTenberg TeX Live scheme - f [ ] TeX Live medium scheme - g [ ] TeX Live minimal scheme - h [ ] TeX Live for Omega users - i [ ] teTeX scheme - j [ ] XML typesetting scheme -\end{boxedverbatim} -\caption{Menu: wybór schematów}\label{fig:scheme-text} -\end{figure} - -Rysunek \ref{fig:scheme-text} pokazuje menu ,,Wybór schematów''. Schematy to -obszerne zestawy pakietów, przeznaczone do wstêpnego wyboru instalowanych -komponentów. Mamy tu schematy do instalacji: podstawowej (\optname{basic}), -typowej (\optname{medium}) i~pe³nej (\optname{full}; jest ona -domy¶lna), pozosta³e przygotowano z~my¶l± o~wybranych grupach -u¿ytkowników (np.~GUST i~GUTenberg przygotowa³y schematy dla swoich -cz³onków) lub zastosowaniach (np.~XML lub Omega). - -\begin{figure}[tbh] -\begin{center} -\tlpng{stdcoll}{.7\linewidth} -\caption{Menu Standard Collections (Kolekcje standardowe) (Linux)}\label{fig:collections-gui} -\end{center} -\end{figure} - -Wstêpnie wybrane schematy mo¿na modyfikowaæ. W sk³ad ,schematów'' wchodz± -tzw. ,,kolekcje'', które mo¿na wybraæ w~kolejnych menu o~nazwach: ,,Kolekcje -standardowe'' i~,,Kolekcje jêzykowe'' (rysunek \ref{fig:collections-gui}). -Kolekcje stanowi± ni¿szy poziom ni¿ schematy, a~same sk³adaj± siê z -,,pakietów''. Dopiero pakiety zawieraj± w³a¶ciwe pliki makr, fontów itp. -Je¶li chcemy dodaæ lub usun±æ pakiet, to po instalacji w³a¶ciwej u¿yjemy -programu \prog{tlmgr} (patrz czê¶æ~\ref{sec:tlmgr}). - -\subsubsection{Katalogi} -\label{sec:directories} - -Domy¶lny uk³ad katalogów opisano w czê¶ci~\ref{sec:texmftrees} na -str.~\pageref{sec:texmftrees}. Po³o¿enie domy¶lne ca³ej instalacji -(\dirname{TEXDIR}) ró¿ni siê w~Windows (|%PROGRAMFILES%\texlive\2008|) -i~w~Unix (\dirname{/usr/local/texlive/2008}). - -G³ównym powodem, dla którego zmieniamy domy¶lne po³o¿enie \dirname{TEXDIR}, -mo¿e byæ brak uprawnieñ. Aby zainstalowaæ \TL{}, nie musimy byæ -administratorem systemu, musimy jednak posiadaæ uprawnienia do zapisu -w~docelowym katalogu. Logiczn± alternatyw± mo¿e byæ wtedy instalacja -w~katalogu domowym, szczególnie wtedy, gdy bêdziemy jedynym u¿ytkownikiem. -Stosujemy tu zapis ,,|~|'' do zaznaczenia takiego wyboru, np. -|~/texlive/2008|. Zalecamy stosowanie katalogu z~nazw± odzwierciedlaj±c± -rok wydania, co pozwoli na zainstalowanie obok siebie ró¿nych wydañ \TL{}. - %%! przegadane, na razie olewam (SW) - %(You may wish to make a - %version-independent name such as \dirname{/usr/local/texlive-cur} via a - %symbolic link, which you can then update after testing the new release.) - -Zmiana \dirname{TEXDIR} w programie instalacyjnym zmieni tak¿e ¶cie¿ki -katalogów okre¶lone przez zmienne \dirname{TEXMFLOCAL}, \dirname{TEXMFSYSVAR} -i~\dirname{TEXMFSYSCONFIG}. - -\dirname{TEXMFHOME} jest zalecanym po³o¿eniem dla prywatnych makr i~fontów -u¿ytkownika. Domy¶lnym katalogiem jest |~/texmf|. W odró¿nieniu od -\dirname{TEXDIR}, znak |~| jest zachowywany w generowanych plikach -konfiguracyjnych, poniewa¿ w~wygodny sposób odnosi siê do katalogu domowego -podczas ka¿dego uruchamiania programów. Znak ten rozwijany jest do zmiennej -\dirname{$HOME} w~Unix i~\verb|%USERPROFILE%| w~Windows. - -\subsubsection{Opcje} -\label{sec:options} - -\begin{figure}[tbh] -\begin{boxedverbatim} -

use letter size instead of A4 by default: [ ] - create all format files: [X] - install font/macro doc tree: [X] - install font/macro source tree: [X] - create symlinks in standard directories: [ ] - binaries to: - manpages to: - info to: -\end{boxedverbatim} -\caption{Menu: Options (Opcje) w Unix}\label{fig:options-text} -\end{figure} - -Rysunek \ref{fig:options-text} pokazuje menu (w~trybie tekstowym) -z~dodatkowymi opcjami. Warto tu wspomnieæ o~trzech z nich: - -\begin{description} -\item[use letter size instead of A4 by default] (u¿yj domy¶lnego formatu -papieru letter zamiast A4): pozwala okre¶liæ domy¶lny format papieru -dla wielu programów. Oczywi¶cie format papieru mo¿na specyfikowaæ potem -dla ka¿dego dokumentu. - -\item[create all format files] (generuj wszystkie pliki formatów): -chocia¿ zbêdne formaty zajmuj± miejsce na dysku, to zaleca siê -pozostawiæ tê opcjê w³±czon±; je¶li tego nie zrobimy, formaty bêd± -generowane automatycznie (w~razie potrzeby) w~prywatnych katalogach -\dirname{TEXMFVAR} u¿ytkowników, nie bêd± jednak od¶wie¿ane, gdy w~instalacji -zostan± zaktualizowane np. programy b±d¼ wzorce przenoszenia; wskutek tego -formaty mog± utraciæ zgodno¶æ ze ¶rodowiskiem, w~którym s± u¿ywane. - -\item[create symlinks in standard directories] (utwórz dowi±zania - w~standardowych katalogach, tylko Unix): opcja ta pozwala unikn±æ ustawiania - zmiennych ¶rodowiska po instalacji (\envname{PATH}, \envname{MANPATH} - i~\envname{INFOPATH}), ale jej u¿ycie nie jest zalecane, bo mo¿e powodowaæ kolizje - z ju¿ zainstalowanym w~systemie ¶rodowiskiem \TeX; mo¿e byæ ona przydatna - jedynie wtedy, gdy w~standardowych katalogach (np. \dirname{/usr/local/bin}) -nie ma jakichkolwiek programów \TeX-owych. -\end{description} - -Po wszystkich potrzebnych ustawieniach mo¿na rozpocz±æ instalacjê -(klawisz ,,I''). Po instalacji zaleca siê zajrzeæ do czê¶ci -\ref{sec:postinstall}, bo byæ mo¿e potrzebne oka¿± siê jeszcze -dodatkowe kroki. - -\subsubsection{Uruchamianie bezpo¶rednio z DVD{} (tylko w trybie tekstowym)} -\label{sec:fromdvd} - -Aby uruchomiæ programy bezpo¶rednio z~p³ytki \DVD{} nale¿y wybraæ -opcjê ,,|V|'', co zmienia menu na przedstawione na -rys.~~\ref{fig:main-fromdvd}. -\begin{figure}[tbh] -\begin{boxedverbatim} -======================> TeX Live installation procedure <===================== - -=======> Note: Letters/digits in indicate menu items <======= -=======> for commands or configurable options <======= - - directories: - TEXDIRW (Writable root): - !! default location: /usr/local/texlive/2008 - !! is not writable, please select a different one! - TEXMFLOCAL (directory for site-wide local files): - /usr/local/texlive/texmf-local - TEXMFSYSVAR (directory for variable and automatically generated data): - /usr/local/texlive/2008/texmf-var - TEXMFSYSCONFIG (directory for local config): - /usr/local/texlive/2008/texmf-config - TEXMFHOME (directory for user-specific files): - ~/texmf - - options: - [ ] use letter size instead of A4 by default - [X] create all format files - - set up for installing to hard disk - -Other actions: - start installation for running from DVD - help - quit -\end{boxedverbatim} -\caption{Menu g³ówne dla uruchamiania z~\optname{DVD}}% -\label{fig:main-fromdvd} -\end{figure} - -Zwróæmy uwagê na nastêpuj±ce zmiany: zniknê³y wszystkie opcje dotycz±ce wyboru -pakietów, sekcja dotycz±ca katalogów pokazuje teraz \dirname{TEXDIRW} -- -katalog z~prawami do zapisu. Pozwoli to uruchamiaæ dowolny program -bezpo¶rednio z~p³ytki; na dysku twardym znajd± siê (w odpowiednich -katalogach) jedynie niezbêdne pliki konfiguracyjne. - -Poniewa¿ struktura katalogów ró¿ni siê nieco od domy¶lnej, niezbêdne bêd± -pewne czynno¶ci konfiguracyjne, omówione w~czê¶ci~\ref{sec:postinstall}. - - %Z powodu pilniejszych prac i braku czasu - Instalator \GUI nie posiada opcji ,,V'', dlatego - %ale jest dostêpna dla wszystkich systemów. - u¿ytkownicy Windows mog± uruchomiæ program jedynie -z~linii poleceñ, jak opisano to w~czê¶ci~\ref{sec:cmdline}. - -W~rozdziale \ref{sec:portable-unix} opisano jeszcze inny, przeno¶ny sposób -uruchamiania \TL, który nie wymaga zmian w~konfiguracji systemu -(a~nawet nie pozwala na nie). - -\subsection{Parametry instalacji z linii poleceñ} -\label{sec:cmdline} - -Uruchom -\begin{alltt} -> \Ucom{install-tl -help} -\end{alltt} -aby wy¶wietliæ wszystkie dostêpne parametry. - % Either |-| or |--| can be used to introduce option names. - Najbardziej interesuj±ce to: - -\begin{ttdescription} -\item[-gui] u¿yj programu w~wersji graficznej (\GUI), je¶li to mo¿liwe; - wymagane jest posiadanie modu³u Perl/Tk - (\url{http://tug.org/texlive/distro.html#perltk}); - gdy jest on niedostêpny, program instalacyjny uruchomiony zostanie - w trybie tekstowym; -\item[-no-gui] wymusza tryb tekstowy, np. w~Windows potrzebny jest on - dla przygotowania do uruchamiania bezpo¶rednio z~\DVD; -\item[-lang {\sl LL}] pozwala wybraæ jêzyk komunikatów, - \textsl{LL} oznacza tu dwuliterowy kod jêzyka; aktualnie dostêpne s±: - angielski (\texttt{en}, domy¶lny), niemiecki (\texttt{de}), francuski - (\texttt{fr}), holenderski (\texttt{nl}), polski (\texttt{pl}), - s³oweñski (\texttt{sl}) i~wietnamski (\texttt{vi}); program samoczynnie - w³±cza jêzyk, ale je¶li jest to niemo¿liwe, komunikaty i menu bêd± - wy¶wietlane w jêzyku angielskim; -\item[-profile {\sl profile}] program instalacyjny zapisuje plik - \filename{texlive.profile} w~katalogu \dirname{2008/tlpkg}, co pozwala - wykorzystaæ go dla powielenia wszystkich wyborów i~ustawieñ w~kolejnych - instalacjach; - %%! zbêdny przyk³ad, patrz wer. oryg. (SW) -\item [-location {\sl url/path}] pozwala okre¶liæ inne ni¿ domy¶lne ¼ród³o - instalacji (patrz poni¿ej). -\end{ttdescription} - -\subsubsection{Parametr \optname{location}} -\label{sec:location} - -Parametrowi \optname{location} mo¿na przypisaæ adres w sieci -(rozpoczynaj±cy siê od \texttt{ftp:}, \texttt{http:} lub \texttt{file:/}), -lub pe³n± ¶cie¿kê. Je¶li podany argument wskazuje na lokalny dysk -(¶cie¿ka b±d¼ adres \texttt{file:/}), to automatycznie zostanie dostosowany -typ instalacji (ze skompresowanych plików b±d¼ nie): gdy dostêpny bêdzie -katalog \dirname{archive}, zawieraj±cy pliki \filename{.tar.lzma}, wybrana -zostanie instalacja z~tych¿e plików, nawet je¶li dostêpne bêd± równolegle -katalogi z~plikami nieskompresowanymi. - -%%! póki co, brak czasu na takie szczegó³y (SW) -%%! When giving an \texttt{http:} or \texttt{ftp:} location, trailing -%%! `\texttt{/}' characters and/or a trailing `\texttt{/tlpkg}' component -%%! are ignored. For example, you could choose a particular \CTAN\ mirror -%%! with something like: -%%! \url{http://ctan.example.org/tex-archive/texlive/tlnet/2008}, -%%! substituting of course a proper hostname and its particular top-level -%%! \CTAN\ path (the list of \CTAN\ mirrors is maintained at -%%! \url{http://ctan.org/mirrors}) for |ctan.example.org/tex-archive|. The -%%! default is to pick a mirror automatically, using -%%! \url{http://mirror.ctan.org}; in any case, the chosen host is used for -%%! the entire download. - -\subsection{Czynno¶ci poinstalacyjne} -\label{sec:postinstall} - -Czê¶æ ta nie dotyczy systemu Windows, dla którego program instalacyjny -przeprowadza ca³± konfiguracjê, w³±cznie z~menu systemowym i~ikonami na -pulpicie. Poni¿sze uwagi mog± byæ przydatne dla u¿ytkowników innych systemów. - -\subsubsection{Gdy zastosujemy dowi±zania symboliczne} - -U¿ycie opisanej w~czê¶ci~\ref{sec:options} opcji tworzenia dowi±zañ -symbolicznych w~standardowych katalogach nie wymaga zmian w zmiennych -¶rodowiska systemowego. - -\subsubsection{Zmienne ¶rodowiska dla Unix} -\label{sec:env} - -Po instalacji trzeba do zmiennej \envname{PATH} dodaæ ¶cie¿kê do -programów \TL. Ka¿da z~obs³ugiwanych platform ma w³asny podkatalog -w~ramach \dirname{TEXDIR/bin}. Listê platform i odpowiadaj±cych im katalogów -przedstawiono na rys.~\ref{fig:bin-text}. - -Równie¿ korzystanie z~systemowych przegl±darek dokumentacji \prog{man} -i~\prog{info} staje siê mo¿liwe dopiero -po dodaniu odpowiednich katalogów do ich ¶cie¿ek przeszukiwania. - -Dla pow³oki zgodnej z~Bourne shell (\cmdname{sh}, \cmdname{bash}, -\cmdname{ksh}) mo¿emy dopisaæ do pliku \filename{$HOME/.profile}: - -\begin{sverbatim} -PATH=/usr/local/texlive/2008/bin/i386-linux:$PATH; export PATH -MANPATH=/usr/local/texlive/2008/texmf/doc/man:$MANPATH; export MANPATH -INFOPATH=/usr/local/texlive/2008/texmf/doc/info:$INFOPATH; export INFOPATH -\end{sverbatim} - -W~wypadku csh lub tcsh nale¿y zmodyfikowaæ plik \filename{$HOME/.cshrc}, np: - -\begin{sverbatim} -setenv PATH /usr/local/texlive/2008/bin/i386-linux:$PATH -setenv MANPATH /usr/local/texlive/2008/texmf/doc/man:$MANPATH -setenv INFOPATH /usr/local/texlive/2008/texmf/doc/info:$INFOPATH -\end{sverbatim} - -%%! ??? (SW) -%%! Of course, you may well already have settings somewhere in your ``dot'' -%%! files, and so then the \TL\ directories should simply be merged in as -%%! appropriate. - -%%! ??? (SW) -%%! \subsubsection{Environment variables: global configuration} -%%! \label{sec:envglobal} -%%! -%%! If you want to make these changes globally, or for a user newly added to -%%! the system, then you are on your own; there is just too much variation -%%! between systems in how and where these things are configured. -%%! -%%! Our two hints are: 1)~you may want to check for a file -%%! \filename{/etc/manpath.config} and, if present, add lines such as -%%! -%%! \begin{sverbatim} -%%! MANPATH_MAP /usr/local/texlive/2008/bin/i386-linux \ -%%! /usr/local/texlive/2008/texmf/doc/man -%%! \end{sverbatim} -%%! -%%! And 2)~check for a file \filename{/etc/environment} which may define the -%%! search path and other default environment variables. - -\subsubsection{Gdy uruchamiamy programy z~DVD} - -Programy \TL{} wyszukuj± potrzebne dane w~ró¿nych drzewach katalogów -korzystaj±c z~pliku \filename{texmf.cnf}. Plik ten znajdowany jest w ca³ej -serii po³o¿eñ wzglêdem po³o¿enia samych programów, ale zasada ta nie dzia³a, -gdy uruchamiamy programy bezpo¶rednio z~\DVD. Wynika to z faktu, ¿e niektóre -pliki s± zapisywane na twardym dysku (\DVD{} jest medium tylko do odczytu) -i~trac± tym samym predefiniowane wzglêdne po³o¿enie. Wymagane jest zatem -zdefiowanie w~¶rodowisku zmiennej \envname{TEXMFCNF}, która wska¿e po³o¿enie -\filename{texmf.cnf}. Nadal jest potrzebna modyfikacja zmiennej -\envname{PATH}, jak opisano wy¿ej. - -Na zakoñczenie instalacji program powinien pokazaæ komunikat informuj±cy, -jak± warto¶æ nale¿y przypisaæ zmiennej \envname{TEXMFCNF}. Gdyby¶my -to przeoczyli -- warto¶ci± t± jest \dirname{$TEXMFSYSVAR/web2c}, czyli dla -domy¶lnych ustawieñ (\dirname{/usr/local/texlive/2008/texmf-var/web2c}) -potrzebujemy deklaracji: -\begin{sverbatim} -TEXMFCNF=/usr/local/texlive/2008/texmf-var/web2c; export TEXMFCNF -\end{sverbatim} -lub, dla [t]csh: -\begin{sverbatim} -setenv TEXMFCNF /usr/local/texlive/2008/texmf-var/web2c -\end{sverbatim} - -\subsubsection{\ConTeXt{} Mark IV} - -Tak zwany ,,stary'' \ConTeXt{} dzia³a jak dotychczas. Nowy \ConTeXt{} -,,Mark~IV'' wymaga rêcznego dostrojenia -- patrz: -\url{http://wiki.contextgarden.net/Running_Mark_IV}. - -\subsubsection{Integracja lokalnych i prywatnych pakietów makr} -\label{sec:local-personal-macros} - -Jak ju¿ wspomniano w~czê¶ci~\ref{sec:texmftrees}, katalog \dirname{TEXMFLOCAL} -(domy¶lnie \dirname{/usr/local/texlive/texmf-local} lub -\verb|C:\Program Files\texlive\texmf-local|) przeznaczony jest na lokalne -(np. w~danej sieci komputerowej) fonty oraz pakiety makr. Z~kolei -\dirname{TEXMFHOME} (domy¶lnie \dirname{$HOME/texmf} lub -\verb|%USERPROFILE%\texmf|) jest przeznaczony na prywatne makra i~fonty -u¿ytkownika. W zamierzeniu oba te katalogi powinny byæ zachowywane przy -instalacji nowszych wersji \TL{}, a~ich zawarto¶æ ma byæ automatycznie -dostêpna w~kolejnych wydaniach. Zalecamy zatem, by nie -przedefiniowywaæ \dirname{TEXMFLOCAL}, co pozwoli unikn±æ rêcznego -konfigurowania w~przysz³o¶ci. - -W~obu drzewach katalogów pliki powinny byæ umieszczane w~odpowiednich -podkatalogach, zgodnie z~zaleceniami TDS (patrz: \url{http://tug.org/tds}, -tak¿e plik \filename{texmf/web2c/texmf.cnf}). Przyk³adowo pliki klas lub -makr \LaTeX-a powinny byæ umieszczane w~katalogu -\dirname{TEXMFLOCAL/tex/latex/} lub \dirname{TEXMFHOME/tex/latex/} -(lub ich podkatalogach). - -\dirname{TEXMFLOCAL} po zmianie zawarto¶ci wymaga od¶wie¿enia bazy danych -- -poleceniem \cmdname{mktexlsr} lub poprzez u¿ycie przycisku ,,Od¶wie¿ bazy -danych'' w~graficznym trybie programu \prog{tlmgr}. - -\subsubsection{Integracja fontów z innych ¼róde³} - -Jest to, niestety, - %mocno zagmatwany temat, - bardzo skomplikowane zagadnienie, wymagaj±ce sporej wiedzy -u¿ytkownika. Warto najpierw siê dowiedzieæ, jakie fonty mamy dostêpne -bezp³atnie (patrz czê¶æ~~\ref{sec:tl-fonts}). - -Alternatyw± jest \XeTeX{} (patrz -czê¶c~\ref{sec:tex-extensions}), który umo¿liwia u¿ycie fontów systemowych -bez potrzeby instalowania ich dla programów \TeX-owych. - -\subsection{Testowanie instalacji} -\label{sec:test-install} - -Po zainstalowaniu \TL{} warto sprawdziæ, czy programy dzia³aj± -poprawnie. Opiszemy tu podstawowe procedury testuj±ce funkcjonowanie -systemu w~systemach Unix. W~\MacOSX{} i~Windows najczê¶ciej u¿yjemy -¶rodowiska graficznego (\GUI), regu³y jednak bêd± podobne. - -\begin{enumerate} -\item Sprawdzamy najpierw, czy uruchamia siê program \cmdname{tex}: - -\begin{alltt} -> \Ucom{tex -{}-version} -TeX 3.1415926 (Web2C 7.5.7) -kpathsea version 3.5.7 -... -\end{alltt} -Je¶li uruchomienie koñczy siê komunikatem \emph{command not found} -(\emph{Nie znaleziono pelecenia}), oznacza to, ¿e niepoprawnie -zadeklarowano zmienn± \envname{PATH} (patrz deklaracje zmiennych -¶rodowiska na str.~\pageref{sec:env}). - -\item Nastêpnie przetwarzamy prosty plik \LaTeX-owy: -\begin{alltt} -> \Ucom{latex sample2e.tex} -This is pdfeTeXk, Version 3.1415926... -..... -Output written on sample2e.dvi (3 pages, 7484 bytes). -Transcript written on sample2e.log. -\end{alltt} -Gdy program nie znajduje \filename{sample2e.tex} (b±d¼ innych wymaganych -plików), mo¿e to oznaczaæ, ¿e nadal dzia³aj± ustawienia zmiennych ¶rodowiska -b±d¼ pliki konfiguracyjne z~poprzedniej instalacji. -Szczegó³ow± analizê, gdzie pliki s± szukane i~znajdowane, -umo¿liwia diagnostyka opisana w~czê¶ci \ref{sec:debugging} na -str.~\pageref{sec:debugging}. - -\item Podgl±d wyniku sk³adu: -\begin{alltt} -> \Ucom{xdvi sample2e.dvi} -\end{alltt} -Polecenie to wymaga uruchomionego ¶rodowiska graficznego X~Window. -Dla MS Windows analogicznym poleceniem jest \cmdname{dviout} (o~ile -samodzielnie zainstalowali¶my ten program). - %%! - %%! You should see a new window with a nice document explaining some of the - %%! basics of \LaTeX{}. (Well worth reading, by the way if you're new to the - %%! system.) You do have to be running under X for \cmdname{xdvi} to work; if - %%! you're not, or your \envname{DISPLAY} environment variable is set - %%! incorrectly, you'll get an error \samp{Can't open display}. - -\item Przetwarzanie wyniku sk³adu do \PS{} w~celu wy¶wietlenia lub wydruku: -\begin{alltt} -> \Ucom{dvips sample2e.dvi -o sample2e.ps} -\end{alltt} - -\item Tworzenie dokumentu bezpo¶rednio w~formacie \acro{PDF}: -\begin{alltt} -> \Ucom{pdflatex sample2e.tex} -\end{alltt} - -\item Podgl±d dokumentu \acro{PDF}: -\begin{alltt} -> \Ucom{gv sample2e.pdf} -\textrm{lub:} -> \Ucom{xpdf sample2e.pdf} -\end{alltt} -Programy \cmdname{gv} i~\cmdname{xpdf} s± zwykle dostarczane -w~ramach systemu operacyjnego, wobec tego nie zamieszczono ich -na \TL. Przed samodzieln± instalacj± warto odwiedziæ strony, -odpowiednio: \url{http://www.gnu.org/software/gv} -i~\url{http://www.foolabs.com/xpdf}. W~sieci dostêpny jest tak¿e -bezp³atny program Adobe Reader (\url{http://www.adobe.com}). -W~systemie Windows domy¶lnie instalowany jest dla \TL{} program -\cmdname{psv} -(PS\_View), pozwalaj±cy przegl±daæ pliki \cmdname{.ps} i~\cmdname{.pdf}. -Program ten mo¿na te¿ zainstalowaæ samodzielnie w~systemach Linux -(w~katalogu \dirname{support/} znajdziemy plik \filename{psview-5.09t.zip}). - -\item Inne przydatne pliki testowe: - -\begin{ttdescription} -\item [small2e.tex] przyk³ad prostszy ni¿ \filename{sample2e}; -\item [testpage.tex] test po³o¿enia wydruku na kartce papieru, przydatny - do sprawdzenia, czy nasza drukarka nie wprowadza przesuniêæ; -\item [nfssfont.tex] s³u¿y do wydruku tablic fontowych; -\item [testfont.tex] jak wy¿ej, z~tym ¿e zamiast \LaTeX-a trzeba u¿yæ plain - \TeX{}; -\item [story.tex] najbardziej kanoniczny przyk³ad dla plain \TeX{}; - na zakoñczenie przetwarzania uruchomionego poleceniem \samp{tex story}, - po ukazaniu siê \code{*}, nale¿y wpisaæ \samp{\bs bye}. -\end{ttdescription} - -\end{enumerate} - -Pocz±tkuj±cym u¿ytkownikom polecamy stronê -\url{http://tug.org/begin.html} oraz podrêcznik -Petera Flynna \textsl{Formatting Information}, dostêpny pod adresem -\url{http://www.ctan.org/tex-archive/documentation/beginlatex}. - -\section{Instalacje sieciowe} -\label{sec:netinstall} - -\TL{} zaprojektowano tak, by mog³o z~niego korzystaæ wielu -u¿ytkowników, nawet w~ró¿nych systemach operacyjnych w~sieci komputerowej. -Dziêki standardowej strukturze katalogów nie ma potrzeby konfiguracji -i~okre¶lania konkretnych ¶cie¿ek: po³o¿enie plików wymaganych przez programy -\TL{} jest zdefiniowane jako wzglêdne wobec samych programów. Mo¿na to -zobaczyæ w~pliku \filename{$TEXMFMAIN/web2c/texmf.cnf}, który zawiera np. -takie wiersze: -\begin{sverbatim} -TEXMFMAIN = $SELFAUTOPARENT/texmf -... -TEXMFLOCAL = $SELFAUTOPARENT/../texmf-local -\end{sverbatim} -W konsekwencji oznacza to, ¿e dla ró¿nych systemów operacyjnych b±d¼ -u¿ytkowników wystarczy dodaæ do ich ¶cie¿ek przeszukiwania tylko ¶cie¿kê -do programów \TL{}. - -Mo¿liwa jest zatem np. instalacja lokalna \TL{}, po czym przeniesienie -ca³ej struktury w~inne miejsce w~sieci. - -U¿ytkownicy Windows mog± mieæ tak¿e inne wymagania. -W~katalogu \dirname{texmf-doc/source/texlive/texlive-common/w32client} -znajdziemy przyk³adowy skrypt \filename{install-w32client}, który -pozwala dostosowaæ istniej±c± instalacjê \TL{} dla potrzeb sieci -(w³±cznie z~utworzeniem skrótów w~menu systemowym). Wystarczy -w~tym katalogu uruchomiæ \filename{install-w32client.bat}. - -W czê¶ci~\ref{sec:kpathsea} dowiemy siê wiêcej o~konfigurowaniu \TL{} -i~zasadach przeszukiwania ¶cie¿ek. - -%%! 2 sekcje t³umaczy³ Kocio (Andrzej Borzyszkowski), przeredagowa³ StaW -\section{Maksymalnie przeno¶ny \protect\TL{} na DVD i~USB} -\label{sec:portable-unix} - -Opcja ,,uruchom z~\DVD{}'', opisana w~rozdziale~\ref{sec:fromdvd}, jest -wprzydatna, je¶li dzia³amy na swoim w³asnym komputerze. Gdy go¶cimy na -cudzym, to prawdopodobnie woleliby¶my wybraæ inn± mo¿liwo¶æ, bez zbêdnych -skutków ubocznych. - -W~g³ównym katalogu \TL{} \DVD (w~podkatalogu \dirname{texlive} \TK{} \DVD) -znajdziemy skrypt uniksowy \filename{tl-portable} oraz widowsowy -\filename{tl-portable.bat}, które uruchamiaj± terminal z~ustawieniami -odpowiednimi do bezpo¶redniego dostêpu do \TL{} na \DVD. - -Gdy skrypt ten jest wykonywany po raz pierwszy, generowane s± pewne pliki -w~podkatalogu \dirname{~/.tlportable2008}, co trwa kilka chwil. -W~kolejnych wywo³aniach skrypt rozpoczyna dzia³anie niemal natychmiast. - -Reszta systemu nie jest ¶wiadoma istnienia \TL. Je¶li chcemy, by nasz edytor -móg³ wspó³pracowaæ z~\TL, to musimy uruchomiæ go z~innej, -równoleg³ej sesji \filename{tl-portable}. - -Mo¿na równie¿ u¿yæ \filename{tl-portable} do wywo³ania \TL{} z~pendrive'a -\acro(USB). W~tym wypadku nale¿y skopiowaæ wszystkie pliki najwy¿szego -poziomu oraz zawarto¶æ (co najmniej) katalogów \dirname{bin}, -\dirname{texmf}, \dirname{texmf-dist} i~\dirname{tlpkg} na pendrive. Zajmie -to trochê czasu! Je¶li kopiujemy na pendrive \acro{USB} sformatowany -z~systemem plików \acro{FAT}32, to nale¿y siê upewniæ, ¿e dowi±zania -symboliczne s± zastêpowane plikami (polecenie \code{cp -L}). U¿ywany te¿ -bêdzie katalog \dirname{texmf-local} na pendrive. - -Nastêpnie wywo³ajmy \filename{tl-portable} z~katalogu g³ównego pendrive'a. -W~tym wypadku skrypt zauwa¿y, ¿e pendrive mo¿na zapisywaæ i~u¿yje go do -zapisania wygenerowanych plików. Zawarto¶æ tê mo¿na z~powrotem zapisaæ na -\DVD{} (np. do przekazania innym). - -\section{\cmdname{tlmgr}: zarz±dzanie instalacj±} -\label{sec:tlmgr} - -\begin{figure}[tb] -\tlpng{tlmgr-gui}{\linewidth} -\caption{\prog{tlmgr} w~trybie graficznym. Lista pokietów\slash -kolekcji\slash schematów poka¿e siê dopiero po naci¶niêciu klawisza -,,£aduj'' (Load).}\label{fig:tlmgr-gui} -\end{figure} - -\begin{figure}[tb] -\tlpng{tlmgr-config}{\linewidth} -\caption{\texttt{tlmgr} w~trybie graficznym: zak³adka -konfiguracji}\label{fig:tlmgr-config} -\end{figure} - -Instalator instaluje program o~nazwie \prog{tlmgr}, s³u¿±cy do dalszego -zarz±dzania \TL{} po pierwotnej instalacji. Programy \prog{updmap}, -\prog{fmtutil} oraz \prog{texconfig} s± nadal dostêpne i~bêd± utrzymywane -w~przysz³o¶ci, jednak¿e obecnie polecanym interfejsem jest \prog{tlmgr}. Jego -mo¿liwo¶ci obejmuj±: - -\begin{itemize*} -\item pokazanie listy schematów, kolekcji i~pakietów; -\item instalowanie, aktualizacjê, tworzenie kopii zapasowych, odtwarzanie - oraz usuwanie pojedynczych pakietów (opcjonalnie~-- z~uwzglêdnieniem - zale¿no¶ci pomiêdzy pakietami); -\item wyszczególnianie oraz dodawanie architektur (platform systemowych); -\item zmianê opcji instalacji, takich jak rozmiar papieru czy zmiana - po³o¿enia ¼ród³a instalacji (patrz czê¶æ~\ref{sec:location}). -\end{itemize*} -\textit{Ostrze¿enie:} \prog{tlmgr} nie zosta³ zaprojektowany ani - przetestowany z~instalacjami, które s± wywo³ywane bezpo¶rednio z~\DVD. - -\subsection{\cmdname{tlmgr} -- tryb graficzny (GUI)} -\prog{tlmgr} mo¿e byæ uruchomiony w~trybie graficznym za pomoc± polecenia -\begin{alltt} -> \Ucom{tlmgr -gui} -\end{alltt} -za¶ w~systemie Windows poprzez wybór menu: \texttt{Start} \verb+->+ -\texttt{Programy} \verb+->+ \texttt{TeX Live 2008} \verb+->+ \texttt{TeX Live -Manager}. Po klikniêciu przycisku ,,£aduj'' wy¶wietla listê dostêpnych -oraz listê zainstalowanych pakietów (te ostatnie poprzedzone s± ,,(i)''). -Zak³adamy oczywi¶cie, ¿e ¼ród³a instalacji s± poprawne i~s± dostêpne. - -Rysunek~\ref{fig:tlmgr-config} przedstawia zak³adkê konfiguracji. - -\subsection{Przyk³adowe wywo³ania \cmdname{tlmgr} z~linii poleceñ} - -Poni¿szy przyk³ad dodaje kilka pakietów, w³±cznie z nowym ,,silnikiem'', -z~innego ni¿ domy¶lne po³o¿enia ¼ród³a instalacji: - -\begin{alltt} -> \Ucom{tlmgr -location http://172.16.18.1/tldev install collection-xetex xkeyval} -\end{alltt} -Generuje on poni¿szy wynik: -\begin{fverbatim} -install: collection-xetex -install: arabxetex -install: euenc -install: bidi -install: fontspec -install: fontwrap -install: ifxetex -install: philokalia -install: polyglossia -install: xecyr -install: xecyr.i386-linux -install: xepersian -install: xetex -install: xetexconfig -install: xetex.i386-linux -running post install action for xetex -install: xetex-def -install: xetex-pstricks -install: xetexfontinfo -install: xltxtra -install: xunicode -install: xkeyval -running mktexlsr -mktexlsr: Updating /usr/local/texlive/2008/texmf/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-config/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-dist/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-doc/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/../texmf-local/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-var/ls-R... -mktexlsr: Done. -regenerating fmtutil.cnf -running fmtutil-sys --missing -... -Transcript written on xelatex.log. -fmtutil: /usr/local/texlive/2008/texmf-var/web2c/xetex/xelatex.fmt installed. -\end{fverbatim} -Jak widaæ, \prog{tlmgr} instaluje zale¿ne pakiety i~dba o~niezbêdne czynno¶ci -poinstalacyjne, w³±cznie z~aktualizacj± bazy danych nazw plików i~powtórnym -wygenerowaniem formatów (w przyk³adzie wygenerowali¶my nowy format dla -\XeTeX). - -Poni¿szy przyk³ad prezentuje instalacjê nowego jêzyka oraz uruchamia powtórne -wygenerowanie formatów: -\begin{alltt} -> \Ucom{tlmgr install collection-langdutch} -\end{alltt} -Aby wy¶wietliæ informacjê o~pakiecie, nale¿y uruchomiæ np.: -\begin{alltt} -> \Ucom{tlmgr show collection-wintools} -\end{alltt} -co daje w~wyniku -\begin{fverbatim} -Package: collection-wintools -Category: Collection -ShortDesc: Windows support programs -LongDesc: Utilities for Windows, since they are not readily available there: - gzip, chktex, jpeg2ps, unzip, wget, xpdf. -Installed: Yes -\end{fverbatim} -Aktualizacja ca³ej instalacji do najnowszej dostêpnej wersji: -\begin{alltt} -> \Ucom{tlmgr update -all} -\end{alltt} -Aby unikn±æ zdenerwowania, proponujemy zacz±æ od: -\begin{alltt} -> \Ucom{tlmgr update -all -dry-run} -\end{alltt} -albo -\begin{alltt} -> \Ucom{tlmgr update -list} -\end{alltt} -Pe³n± dokumentacjê programu poka¿e polecenie: -\begin{alltt} -> \Ucom{tlmgr -help} -\end{alltt} - -\section{Uwagi dotycz±ce Windows} -\label{sec:windows} - -\TL\ ma tylko jeden program instalacyjny, dzia³aj±cy zarówno w~Unix, -jak i~w~Windows. Stworzenie takiego programu by³o mo¿liwe dopiero -po zaniechaniu wsparcia dla starszych wersji Windows. Obecnie -\TL\ mo¿na instalowaæ tylko w~Windows 2000 i~nowszych. - -\subsection{Cechy specyficzne w~systemie Windows} -\label{sec:winfeatures} - -W systemie Windows program instalacyjny wykonuje kilka dodatkowych czynno¶ci: -\begin{description} -\item[Menu i skróty.] W~menu systemowym instalowane jest podmenu ,,\TL'', -które zawiera kilka pozycji dla programów dzia³aj±cych w~trybie graficznym -(\prog{tlmgr}, \prog{texdoctk}, PS\_View -- przegl±darka plików -postscriptowych) oraz dokumentacji. Dla PS\_View tworzony jest tak¿e -skrót (ikona) na pulpicie, umo¿liwiaj±cy ,,przeci±ganie\dywiz upuszczanie'' -na ikonie plików postscriptowych. -\item[Automatyczne ustawienie zmiennych ¶rodowiska.] -Po instalacji nie s± wymagane ¿adne ,,rêczne'' zmiany ustawieñ. -\item[Odinstalowanie.] Program instalacyjny rejestruje instalacjê -w~menu ,,Dodaj/Usuñ programy'' w~Panelu sterowania; odinstalowanie -odbywa siê zatem w~standardowy dla Windows sposób. -\end{description} - -\subsection{Programy pomocnicze dla Windows} - -Aby instalacja by³a kompletna, \TL{} wymaga kilku pomocniczych -programów, które nie s± dostarczane z~systemem Windows. -Wiele skryptów napisano w~jêzyku Perl, ponadto wiele narzêdzi wymaga -programu Ghostscript (interpretera jêzyka PostScript) do -rasteryzacji b±d¼ konwersji plików. Przydatne s± tak¿e w~wielu wypadkach -ró¿ne programy do obróbki grafiki. Ponadto posiadanie edytora -zorientowanego na ¶rodowisko \TeX{} znacznie u³atwi pracê. - -Wszystkie te programy dla Windows mo¿na dosyæ ³atwo znale¼æ w~sieci, -poniewa¿ jednak jest ich spory wybór, postanowili¶my te najbardziej istotne -umie¶ciæ w~dystrybucji \TL: -\begin{description} -\item[Perl i Ghostscript.] Oba te programy s± niezbêdne do -poprawnego dzia³ania \TL, do³±czyli¶my zatem \cmdname{Ghostscript} 8.62 -i~minimaln± dystrybucjê \cmdname{Perl} 5.8, wystarczaj±c± do -uruchomienia wszystkich, zawartych w~\TL{} skryptów perlowych; -oba programy zosta³y ,,ukryte'', to znaczy tylko programy \TL, które -z~nich korzystaj±, ,,wiedz±'' gdzie je znale¼æ; tym samym nie powinny -kolidowaæ z~ewentualnie zainstalowanymi w~systemie programami Perl -i~Ghostscript; -\item[narzêdzia uruchamiane z~linii poleceñ] -- zestaw kilku przydatnych - programów - %(\texttt{bzip2}, %% NIE MA!! (SW) - (\texttt{gzip}, \texttt{unzip}, \texttt{jpeg2ps} i~\texttt{tiff2png}) - a~tak¿e kilka narzêdzi z~zestawu \cmdname{xpdf}, uruchamianych z~linii - poleceñ (sam \cmdname{xpdf} nie jest dostêpny dla Windows, - mo¿na jednak pobraæ z~internetu opart± na nim przegl±darkê \acro{PDF}: - \url{http://blog.kowalczyk.info/software/sumatrapdf}); -\item[\texttt{fc-cache}] -- program rejestruj±cy dla \XeTeX-a fonty - systemowe lub dostarczane w~dystrybucji \TL{} fonty OpenType; -\item[PS\_View] -- nowy program podgl±du plików postscriptowych (a~tak¿e - plików \acro{PDF}), patrz rys.~\ref{fig:psview}. -\end{description} -\begin{description} -\item[katalog \texttt{support,}] wspomniany ju¿ w~czê¶ci~\ref{sec:tld}, - zawiera ró¿ne programy, które mog± byæ u¿yteczne w~¶rodowisku \TeX-owym - (np. edytory/¶rodowiska dla \TeX-a); programy te \emph{nie s±} uwzglêdniane - podczas instalacji samego \TL, nale¿y je wiêc zainstalowaæ samodzielnie. -\end{description} - -\begin{figure}[h] -\begin{center} -\tlpng{psview}{.6\linewidth} -\caption{PS\_View: umo¿liwia bardzo du¿e powiêkszenia!}\label{fig:psview} -\end{center} -\end{figure} - -Poni¿ej zamieszczono listê miejsc, z~których mo¿na pobraæ programy -pomocnicze: - -\begin{description} -\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} -\item[Perl] \url{http://www.perl.org} (uzupe³niaj±ce, przydatne - pakiety nale¿y pobraæ z~zasobów CPAN \url{http://cpan.org}) -\item[ImageMagick] -- bogaty zestaw narzêdzi do wsadowego przetwarzania - plików graficznych (\url{http://www.imagemagick.com}) -\item[NetPBM] -- do przetwarzania i~konwersji plików graficznych mo¿emy - u¿yæ alternatywnego dla \textsf{ImageMagick} programu NetPBM - (\url{http://netpbm.sourceforge.net/}) -\item[Edytory dla systemu \TeX{}] -- spory wybór programów, uwzglêdniaj±cy - indywidualne preferencje u¿ytkownika: - \begin{itemize*} - \item \cmdname{GNU Emacs} -- w~wersji zintegrowanej z~\textsf{AucTeX} - dostêpny jest w~\TL{} w~katalogu \path{support/} - (\url{ftp://alpha.gnu.org/gnu/auctex}) -% http://www.gnu.org/software/emacs/windows/ntemacs.html}) -% \item \cmdname{XEmacs} -- bardziej przyjazna wersja dla Windows -% (\url{http://www.xemacs.org/}) - \item \cmdname{WinShell} -- prosty edytor/shell, dostêpny na \TL - w~katalogu \dirname{support/WinShell} (\url{http://www.winshell.de}) - \item \cmdname{WinEdt} -- bogaty w~funkcje edytor dla \TeX-a, dostêpny jako - \emph{shareware} (\url{http://www.winedt.com}) - \item TeXnicCenter -- kolejny, dosyæ bogaty w~funkcje edytor - (\url{http://www.toolscenter.org/products/texniccenter/}) - \item \cmdname{Vim} -- rozbudowany i~bardzo funkcjonalny edytor, wywodz±cy siê - z~klasycznego dla systemów Unix edytora \cmdname{vi} - %, dostêpny na \TL{} w~katalogu \dirname{support/vim} - (\url{http://www.vim.org}) - \item \cmdname{LEd} -- polski edytor, dostêpny - z~\url{http://www.ctan.org/support/LEd} - \item \cmdname{SciTE} -- edytor dostêpny - z \url{http://www.scintilla.org/SciTE.html} - \end{itemize*} -\end{description} - -%Mo¿emy zainstalowaæ z~sieci tak¿e inne narzêdzia, których zabrak³o na -%\TL{} z~powodów licencyjnych. Przyk³adem jest tu \cmdname{GSView}, -%wygodny program wykorzystuj±cy \cmdname{Ghostscript} do wy¶wietlania -%i~drukowania plików PS/PDF. Dostêpny jest on m.in. -%na \url{http://www.cs.wisc.edu/~ghost/gsview/}, a~tak¿e na ka¿dym serwerze -%\acro{CTAN}. - -\subsection{Program Dviout} - -Obecne wydanie \TL{} nie oferuje niestety preinstalowanego programu do -podgl±du plików \acro{DVI} dla Windows, mo¿na jednak samodzielnie -zainstalowaæ doskona³y \prog{dviout}, autorstwa Toshio Oshimy. Znajdziemy go -w~katalogu \path{support/dviout/}, zawieraj±cym równie¿ krótki plik -\filename{README} omawiaj±cy, jak zaistalowaæ i~skonfigurowaæ \prog{dviout} -dla \TL. Przed instalacj± zalecamy przeczytaæ informacje tam zawarte. - -Pierwsze uruchomienie \verb+dviout+ zazwyczaj automatycznie generuje wymagane -fonty ekranowe. Po kilku sesjach komunikaty dotycz±ce generowania fontów -stan± siê rzadsze. Wiêcej informacji mo¿na znale¼æ w~bardzo dobrym -poradniku \emph{on-line} tego programu. - -\subsection{User Profile to inaczej Home (katalog domowy)} -\label{sec:winhome} - -Odpowiednikiem uniksowego katalogu domowego u¿ytkownika (HOME) jest -w~Windows katalog okre¶lany zmienn± \verb|%USERPROFILE%|. W~Windows -2000 i~XP jest to zazwyczaj katalog -\verb|C:\Documents and Settings\|, za¶ w~Windows Vista -\verb|C:\Users\|. W~pliku konfiguracyjnym -\filename{texmf.cnf} i~bibliotekach \KPS{} znak \verb|~| -jest poprawnie rozwijany do odpowiedniej zmiennej zarówno w~Windows, jak -i~w~Unix. - -\subsection{Rejestr Windows} -\label{sec:registry} - -W systemie Windows prawie wszystkie dane konfiguracyjne przechowywane s± -w~tzw. rejestrze. Zawiera on hierachicznie zorganizowane klucze, w~ramach -kilku kluczy g³ównych. Najbardziej istotne dla programów instalacyjnych -s± klucze \path{HKEY_CURRENT_USER} oraz \path{HKEY_LOCAL_MACHINE} -(w~skrócie \path{HKCU} i \path{HKLM}). Czê¶æ \path{HKCU} dotyczy katalogów -domowych u¿ytkowników (patrz~\ref{sec:winhome}), za¶ \path{HKLM} -- podkatalogów -systemowych (w~katalogu Windows). - -Informacje o~ustawieniach systemu mo¿na czasem uzyskaæ ze zmiennych -¶rodowiska, ale po inne informacje, np. po³o¿enie tzw. skrótów, trzeba -odwo³aæ siê do rejestru. Tak¿e zapis zmiennych ¶rodowiska na sta³e wymaga -dostêpu do rejestru. - -\subsection{Uprawnienia w Windows} -\label{sec:winpermissions} - -%%! UWAGA SW: ca³a ta czê¶æ jest mocno niejasna w oryginale. T³umaczy³em -%%! j± maj±c na uwadze ogólny sens, w niektórych miejscach doprecyzowuj±c -%%! sformu³owania. Ale i tak jest, wg mnie, do bani :-) - -W nowszych wersjach Windows istnieje wyra¼ne rozró¿nienie miêdzy -zwyk³ymi u¿ytkownikami i~administratorami, przy czym tylko ci ostatni maj± -pe³n± swobodê dostêpu do ca³o¶ci systemu. - %%! ??? - %In practice, though, you could better describe - %these classes of users as unprivileged users and normal users: being an - %administrator is the rule, not the exception. - Do³o¿ono wielu starañ, aby umo¿liwiæ instalacjê \TL{} tak¿e osobom bez - uprawnieñ administratora. - -Je¶li osoba instaluj±ca jest administratorem, to skróty s± tworzone dla -wszystkich u¿ytkowników, tak¿e zmienne ¶rodowiska s± ustawiane dla ca³ego -systemu. W~przeciwnym wypadku skróty i~menu s± tworzone jedynie dla konkretnego -u¿ytkownika, tak¿e definiowane zmienne ¶rodowiska dotycz± zwyk³ych -u¿ytkowników. Maj±c uprawnienia admistratora mo¿emy zainstalowaæ \TL{} tylko -dla u¿ytkowników; nale¿y wtedy uruchomiæ \prog{install-tl} z~parametrem -\optname{-non-admin}. - -Bez wzglêdu na status u¿ytkownika domy¶lnym katalogiem g³ównym instalacji -jest katalog w~ramach \verb|%PROGRAMFILES%|. Program instalacyjny zawsze -sprawdza, czy ten katalog jest dostêpny do zapisu dla aktualnego u¿ytkownika. - -Problem mo¿e siê pojawiæ wtedy, gdy u¿ytkownik instaluj±cy \TL{} nie jest -administratorem, a~programy \TeX-owe ju¿ s± w~¶cie¿ce przeszukiwania. -Wynikowa ¶cie¿ka zawiera wtedy ¶cie¿kê systemow±, do której dodano ¶cie¿kê do -programów u¿ytkownika. W~konsekwencji nie bêd± znajdowane nowo instalowane -programy. W~celu obej¶cia tego problemu program instalacyjny tworzy skrót do -okna z~wierszem poleceñ, w~którym ¶cie¿ka do nowych programów \TL{} ma -priorytet. W~ten sposób, po uruchomieniu tego skrótu, bêdzie mo¿na korzystaæ -z~\TL. - -%%% Zostawione z poprzedniej wersji tylko w polskim t³umaczeniu! - -\subsection{\cmdname{WinShell}}\label{sec:winshell} - -Je¶li nie decydujemy siê na instalowanie rozbudowanego (ale i~bardzo -bogatego w~funkcje) edytora Emacs, mo¿emy samodzielnie zainstalowaæ prosty -i~³atwy w~obs³udze edytor WinShell. Znajdziemy go na p³ytce w~katalogu -\dirname{support/winshell}. Wystarczy dwukrotnie klikn±æ klawiszem myszy -na znajduj±cym siê tam pliku \texttt{.exe}. -Program uruchamiamy z~menu Start b±d¼ z~ikony/skrótu na pulpicie. -Dostosowanie do polskiej wersji Windows wymaga, prócz okre¶lenia jêzyka -dla menu i~komunikatów, u¿ycia menu -\verb+Opcje+ (Options) \verb+->+ \verb+Font+ \verb+->+ \verb+Zmieñ+ -i~wyboru w~wy¶wietlonym oknie \texttt{Skrypt} -napisu \texttt{Europa ¦rodkowa}. -Dziêki temu poprawnie bêd± wy¶wietlane polskie znaki diakrytyczne, -wpisywane za pomoc± prawego klawisza Alt. - -Aby skonfigurowaæ uruchamianie programów, otwieramy menu -\texttt{Options} \verb+->+ \texttt{Program Calls}. - -\begin{itemize}\itemsep 0pt -\item W zak³adce DVIWin, w~polu ,,exe-file'', wpisujemy -\texttt{dviout.exe} (o~ile go wcze¶niej zaistalowali¶my). -\item W zak³adce Ghostview wpisujemy psv.bat. - %sprawdziæ, czy prawid³owo podano - %¶cie¿kê dla gsview32.exe:\\ - %\hspace*{1em} \verb+C:\ghostgum\gsview\gsview32.exe+ (dla wersji 3.6 - %i~nowszych). -\end{itemize} -Po wci¶niêciu przycisku \texttt{OK} zatwierdzamy zmiany. - -Instalacja programu ustawia w~Windows skojarzenie plików \texttt{.tex} -z~uruchamianiem \cmdname{WinShell}. O~ile nie zamierzamy korzystaæ -z~innego edytora (jak WinEdt lub Emacs), jest to poprawne. - -\cmdname{WinShell} jest wyposa¿ony w~modu³ pomocy, dostêpnej po -naci¶niêciu symbolu $\textbf{\underbar{?}}$ na pasku z~narzêdziami. - -\subsubsection{U¿ycie plików ,,projektu''} - Wielokrotnie mamy do czynienia z~dokumentami sk³adaj±cymi siê z~wielu -czê¶ci. Najwygodniej gdy s± one zapisane w~odrêbnych plikach. -\cmdname{WinShell} umo¿liwia utworzenie pliku projektu (\textit{Project -file}), w~którym deklarujemy poszczególne czê¶ci wiêkszego dokumentu. Nazwy -plików projektu: traktowanego jako g³ówny (\textit{Main file}) oraz plików -czê¶ci s± wy¶wietlane w~lewym oknie edytora. Dwukrotne klikniêcie mysz± na -nazwie pliku powoduje jego wy¶wietlenie w~g³ównym oknie edytora. Naci¶niêcie -ikony LaTeX na belce narzêdziowej uruchamia zawsze przetwarzanie g³ównego -pliku, bez wzglêdu na to, który plik jest aktualnie wy¶wietlany. - -Na belce narzêdziowej mamy dodatkowe przyciski, pozwalaj±ce wy³±czyæ lub -w³±czyæ wy¶wietlanie okna projektu (po lewej stronie) i~okna zapisu sesji -(log) -- u~do³u. Gdy plik projektu nie jest u¿ywany, lew± czê¶æ okna mo¿na -zamkn±æ, zyskuj±c w~ten sposób ca³± szeroko¶æ ekranu dla edytowanego pliku. - -\subsubsection{Drukowanie z~\cmdname{WinShell} na drukarce PostScriptowej} -\label{winshell:print} - Ikona Dvips belki narzêdziowej uruchamia program, który wynik pracy -zapisuje zwykle w~pliku \verb+.ps+. Ogl±danie i/lub drukowanie takiego pliku -wymaga uruchomienia - %GSView. - PS\_View. - \cmdname{WinShell} pozwala zdefiniowaæ -wygodne wywo³anie polecenia dvips, które wynik przetwarzania wy¶le od razu -do drukarki wyposa¿onej w~interpreter PostScript. Przyk³adowo, dla drukarki -o~nazwie \texttt{vclw}, postêpowanie bêdzie nastêpuj±ce: -\begin{enumerate} -\item Deklaracja danej drukarki w programie: -\begin{itemize} -\item otworzyæ \cmdname{WinShell}, wybraæ menu \texttt{Opcje} \verb+->+ - \texttt{Programy u¿ytkownika}. -\item wybraæ \texttt{Tool 1} w~spisie po prawej stronie i~wype³niæ pola - po stronie lewej, np.:\vspace{-3pt} - \begin{quote} - Name: \verb+Drukuj+\\ - exe file: \verb+dvips+\\ - cmd-line: \verb+ -D600 %c.dvi -o vclw+\\ - skasowaæ zaznaczenie okienka ,,najpierw DVIPS'' -\end{quote}%\vspace{-12pt} -\item nacisn±æ \texttt{OK}. -\end{itemize} -\item Dodanie polecenia ,,Drukuj'' do belki narzêdziowej: -\begin{itemize} -\item wybraæ menu \texttt{Opcje} \verb+->+ \texttt{Przegl±daj} \verb+->+ - \texttt{Dostosuj paski}; -\item w~okienku \verb+Kategoria+ wybraæ \texttt{Programy u¿ytkownika}; -\item wskazaæ \texttt{Drukuj} i~przeci±gn±æ go mysz± na belkê narzêdziow±, - umieszczaj±c w~dowolnym miejscu obok innych poleceñ; -\item w kolejno wy¶wietlanym oknie dokonaæ wyboru: ,,Tylko obrazek'' - (\textit{Image only}), ,,Tylko tekst'' lub ,,Tekst i~obrazek''; najpro¶ciej - wybraæ ,,Tylko tekst'' i~zatwierdziæ guzikiem \texttt{OK}. - Napis \texttt{Drukuj} uka¿e siê na belce. (Bardziej wymagaj±cy u¿ytkownicy - mog± wybraæ opcjê ,,Tylko obrazek'', nastêpnie ,,Edytuj'' i~skonstruowaæ - sobie w³asn± ikonkê.) -\end{itemize} -\end{enumerate} -Uruchamianie polecenia zosta³o zdefiniowane. Aby drukowaæ bezpo¶rednio na -drukarce, wystarczy teraz nacisn±æ guzik z~napisem ,,Drukuj''. - -\subsection{W razie problemów} -\label{troubleshooting} - -\subsubsection{Co zrobiæ gdy \texttt{latex} nie mo¿e znale¼æ potrzebnych -plików?} - -\begin{itemize} -\item Program \cmdname{kpsewhich} jest podstawowym narzêdziem do diagnozowania - problemów. Wyprowadza on informacje diagnostyczne na wyj¶cie stderr, przy -czym konsole (okienka wierszy poleceñ) starszych systemów Windows nie -potrafi± przekierowaæ stderr do pliku. Umo¿liwia to dopiero system Windows -NT i~pó¼niejsze, ale rozwi±zanie przedstawione poni¿ej dzia³a dla ka¿dej -konsoli (okienka wierszy poleceñ). Otó¿ dla celów diagnostycznych mo¿na -tymczasowo zdefiniowaæ zmienn± ¶rodowiska (w~oknie poleceñ): -\begin{verbatim} -SET KPATHSEA_DEBUG_OUTPUT=err.log -\end{verbatim} -Mo¿na równie¿ zadaæ zakres diagnostyki: -\begin{verbatim} -SET KPATHSEA_DEBUG=-1 -\end{verbatim} - -Podobnie, aby przekierowaæ wyj¶cie stderr na stdout: -\begin{verbatim} -SET KPATHSEA_DEBUG_OUTPUT=con: -\end{verbatim} -W ten sposób mo¿na skierowaæ zarówno stderr, jak i stdout do tego samego pliku. -\item Przy za³o¿eniu, ¿e instalacjê wykonano w \path|c:/TeX|, nale¿y - sprawdziæ (porównaæ) nastêpuj±ce warto¶ci:\\ - {\small - \begin{tabular}{ll} - \path|kpsewhich -expand-path $SELFAUTOPARENT| & \path|c:/TeX| \\ - \path|kpsewhich -expand-path $TEXMF| & \path|c:/TeX/texmf....| \\ - \path|kpsewhich -expand-var $TEXINPUTS| & \path|.;c:/TeX/texmf/tex//| - \end{tabular} -} - -Je¶li w otoczeniu systemowym s± zdefiniowane zmienne zwi±zane z~\TeX-em, -nale¿y je usun±æ, maj± bowiem pierwszeñstwo przed tymi, -które okre¶lono w~pliku \filename{texmf.cnf}. -\item Nastêpnie nale¿y sprawdziæ (porównaæ) warto¶ci:\\ -{\small - \begin{tabular}{ll} - \texttt{kpsewhich cmr10.tfm} & \path|c:/TeX/texmf-dist/fonts/tfm/public/cm/cmr10.tfm|\\ - \texttt{kpsewhich latex.fmt}& \path|c:/TeX/texmf-var/web2c/pdftex/latex.fmt| - \end{tabular} -} - -Je¶li sprawdzenia nie wykaza³y odstêpstw, to \TeX{} i~programy towarzysz±ce -powinny dzia³aæ. Je¶li tak nie jest, nale¿y poeksperymentowaæ z opcj± -\path|-debug=n| programu \path|kpsewhich| i~zweryfikowaæ wszystkie uzyskane -warto¶ci. Po zidentyfikowaniu problemu warto go zg³osiæ. -\end{itemize} - -%-------------------------- -% don't use \Webc so the \uppercase in the headline works. -\section{Instrukcja obs³ugi systemu Web2C} - -\Webc{} to zestaw programów zwi±zanych z~\TeX-em, tj. sam \TeX{}, \MF{}, -\MP, \BibTeX{} itd. Stanowi± one rdzeñ dystrybucji \TL. - -Oryginalna implementacja wykonana zosta³a przez Tomasa Rokickiego, który -w~roku 1987 stworzy³ pierwszy system \TeX{}-to-C, adaptuj±c pliki wymiany -(\emph{change files}) pod Unix-em (pierwotnie by³y one dzie³em Howarda -Trickey'a oraz Pavela Curtisa). W~czasie, gdy Tim Morgan zajmowa³ siê -systemem, jego nazwa zosta³a zmieniona na Web-to-C\@. W~1990 roku prace nad -projektem przej±³ Karl Berry wraz z~dziesi±tkami wspó³pracowników, a~w~roku -1997 pa³eczkê przej±³ Olaf Weber. - -\Webc{} dzia³a na platformach systemowych, takich jak Unix (w~tym \MacOSX), -Windows 9x/\acro{NT/2K/XP} i~innych. -System wykorzystuje oryginalne ¼ród³a \TeX-owe autorstwa Donalda Knutha -oraz inne programy napisane w~\web{} i~t³umaczy je na kod ¼ród³owy~C. -Ponadto system udostêpnia spory zestaw makr i~funkcji stworzonych dla -zwiêkszenia funkcjonalno¶ci oryginalnych zasobów oprogramowania -zwi±zanego z~\TeX-em. Podstawowymi sk³adnikami systemu s±: - -\begin{cmddescription} -\item[bibtex] tworzenie spisów bibliograficznych; -\item[dmp] konwersja \cmdname{troff} do MPX (rysunki \MP{}-owe); -\item[dvicopy] modyfikowanie pliku \dvi; -\item[dvitomp] konwersja \dvi{} do MPX (rysunki \MP{}-owe); -\item[dvitype] konwersja \dvi{} na plik tekstowy (ASCII); -\item[gftodvi] zamiana fontu GF na plik \dvi; -\item[gftopk] zamiana fontu w~formacie GF na font spakowany (PK); -\item[gftype] zamiana fontu GF na plik tekstowy (ASCII); -\item[makempx] sk³ad etykiet \MP{}-owych; -\item[mf] generowanie fontów bitmapowych w formacie GF; -\item[mft] sk³ad plików ¼ród³owych \MF{}-a; -\item[mpost] tworzenie rysunków oraz diagramów technicznych; -\item[mpto] ekstrakcja etykiet \MP{}-owych; -\item[newer] porównywanie czasów modyfikacji; -\item[patgen] tworzenie wzorców przenoszenia wyrazów; -\item[pktogf] zamiana fontów w formacie PK na fonty GF; -\item[pktype] zamiana fontu PK na plik tekstowy (ASCII); -\item[pltotf] konwersja tekstowej listy w³a¶ciwo¶ci do TFM; -\item[pooltype] wy¶wietlanie \web-owych plików pool; -\item[tangle] konwersja \web{} do jêzyka Pascal; -\item[tex] sk³ad tekstu; -\item[tftopl] konwersja TFM do tekstowej listy w³a¶ciwo¶ci (PL); -\item[vftovp] konwersja fontów wirtualnych do wirtualnej listy - w³a¶ciwo¶ci (VPL); -\item[vptovf] konwersja wirtualnej listy w³a¶ciwo¶ci do fontów wirtualnych; -\item[weave] konwersja \web{} do \TeX-a. -\end{cmddescription} - -\noindent -Dok³adny opis funkcji oraz sk³adni tych programów zawarty jest -w~dokumentacji poszczególnych pakietów samego \Webc{}. -Do optymalnego korzystania z~instalacji \Webc{} -przyda siê znajomo¶æ kilku zasad rz±dz±cych ca³± rodzin± programów. - -Wszystkie programy obs³uguj± standardowe opcje \acro{GNU}: -\begin{description} -\item[\texttt{-{}-help\ \ \ }] podaje podstawowe zasady u¿ytkowania; -\item[\texttt{-{}-verbose}] podaje dok³adny raport z~dzia³ania programu; -\item[\texttt{-{}-version}] podaje informacjê o~wersji, po czym koñczy - dzia³anie programu. -\end{description} - -Do lokalizowania plików programy oparte na \Webc{} u¿ywaj± biblioteki do -przeszukiwania ¶cie¿ek zwanej \KPS{}. -Dla optymalizacji przeszukiwania \TeX-owego drzewa podkatalogów biblioteka ta -u¿ywa kombinacji zmiennych ¶rodowiskowych oraz kilku plików konfiguracyjnych. -\Webc{} potrafi obs³ugiwaæ jednocze¶nie wiêcej ni¿ jedno drzewo -podkatalogów, co jest u¿yteczne w~wypadku, gdy chce siê przechowywaæ -standardow± dystrybucjê \TeX-a jak i~lokalne rozszerzenia w~dwóch ró¿nych -drzewach katalogów. -Aby przyspieszyæ poszukiwanie plików, katalog g³ówny ka¿dego drzewa ma swój -plik \file{ls-R}, zawieraj±cy pozycje okre¶laj±ce nazwê i~wzglêdn± ¶cie¿kê -dla wszystkich plików zawartych w~tym katalogu. - -\subsection{Przeszukiwanie ¶cie¿ek przez Kpathsea} -\label{sec:kpathsea} - -Opiszemy najpierw ogólny mechanizm przeszukiwania ¶cie¿ek przez bibliotekê -\KPS{}. - -Tym, co nazywamy \emph{¶cie¿k± przeszukiwania}, jest rozdzielona dwukropkami -lub ¶rednikami lista \emph{elementów ¶cie¿ki}, które zasadniczo s± nazwami -podkatalogów. ¦cie¿ka przeszukiwania mo¿e pochodziæ z~(kombinacji) wielu -¼róde³. Przyk³adowo, aby odnale¼æ plik \samp{my-file} w~¶cie¿ce -\samp{.:/dir}, \KPS{} sprawdza istnienie danego elementu ¶cie¿ki -w~nastêpuj±cej kolejno¶ci: najpierw \file{./my-file}, potem -\file{/dir/my-file}, zwracaj±c pierwszy odnaleziony (lub mo¿liwie wszystkie). - -Aby optymalnie zaadaptowaæ siê do konwencji wszystkich systemów operacyjnych, -na systemach nieunixowych \KPS{} mo¿e u¿ywaæ -jako separatorów nazw ¶cie¿ek znaków innych -ni¿ dwukropek (\samp{:}) oraz ,,ciach'' (\samp{/}). - -W~celu sprawdzenia konkretnego elementu \var{p} ¶cie¿ki, \KPS{} najpierw -sprawdza, czy zbudowana wcze¶niej baza danych (patrz ,,Baza nazw plików'' na -stronie~\pageref{Filename-database}) odnosi sie do \var{p}, tj. -czy baza danych znajduje siê w~podkatalogu z~prefiksem~\var{p}. -Je¿eli tak, to specyfikacja ¶cie¿ki jest porównywana z~zawarto¶ci± bazy. - -Je¶li baza danych nie istnieje b±d¼ nie odnosi siê do danego elementu -¶cie¿ki albo te¿ nie zawiera elementów zgodnych, to przeszukiwany jest system -plików (je¿eli nie zosta³o to zabronione przez specyfikacjê rozpoczynaj±c± -siê od~\samp{!!}\ oraz je¿eli poszukiwany plik musi istnieæ). -\KPS{} konstruuje listê podkatalogów, które koresponduj± z~danym elementem -¶cie¿ki, a~nastêpnie sprawdza w~ka¿dym z~nich, czy nie ma tam poszukiwanego -pliku. - -Warunek mówi±cy, ¿e ,,plik musi istnieæ'' dotyczy np. plików \samp{.vf} -i~plików do³±czanych \TeX-owym poleceniem \cs{openin}. -Takiego pliku mo¿e nie byæ (np. \file{cmr10.vf}), b³êdne by³oby zatem -poszukiwanie go na dysku. -Je¶li wiêc zapomnisz o~aktualizacji \file{ls-R} po instalacji nowego -pliku \samp{.vf}, to nie zostanie on odnaleziony. -Ka¿dy element ¶cie¿ki sprawdzany jest w~nastêpuj±cej kolejno¶ci: najpierw -w~bazie danych, potem na dysku. -Je¿eli plik siê znajdzie, to przeszukiwanie zostanie zatrzymane i~zwrócony -zostanie wynik. - -Poniewa¿ najprostszym i~najbardziej powszechnym elementem ¶cie¿ki jest -nazwa katalogu, \KPS{} korzysta z~dodatkowych mo¿liwo¶ci w~przeszukiwaniu -¶cie¿ek: -wielowarstwowych warto¶ci domy¶lnych, zmiennych ¶rodowiskowych, warto¶ci -pliku konfiguracyjnego, lokalnych -podkatalogów u¿ytkownika oraz rekursywnego przeszukiwania podkatalogów. -Mo¿na wiêc powiedzieæ, ¿e \KPS{} \emph{rozwija} element ¶cie¿ki, tzn. -transformuje wszystkie specyfikacje do podstawowej nazwy lub nazw katalogów. -Jest to opisane w~kolejnych akapitach, w~kolejno¶ci w~jakiej ma to miejsce. - -Trzeba zauwa¿yæ, ¿e je¿eli nazwa poszukiwanego pliku jest -absolutna lub jawnie wzglêdna, tj. zaczyna siê od \samp{/} lub \samp{./} -lub \samp{../}, to \KPS{} ogranicza siê do sprawdzenia, czy ten plik istnieje. - -\ifSingleColumn -\else -\begin{figure*} -\verbatiminput{examples/ex5.tex} -\setlength{\abovecaptionskip}{0pt} - \caption{Przyk³ad pliku konfiguracyjnego} - \label{fig:config-sample} -\end{figure*} -\fi - -\subsubsection{¬ród³a ¶cie¿ek} -\label{Path-sources} - -Nazwa przeszukiwanej ¶cie¿ki mo¿e pochodziæ z~wielu ¼róde³. -Oto kolejno¶æ, w~jakiej \KPS{} ich u¿ywa: - -\begin{enumerate} -\item - Zmienna ¶rodowiskowa ustawiana przez u¿ytkownika, np. - \envname{TEXINPUTS}. - Zmienne ¶rodowiskowe z~do³±czon± kropk± i~nazw± programu zastêpuj± inne, - np. je¿eli \samp{latex} jest nazw± uruchomionego programu, wtedy zamiast - \envname{TEXINPUTS} wykorzystana zostanie zmienna \envname{TEXINPUTS.latex}. -\item - Plik konfiguracyjny konkretnego programu, np. linia ,,\texttt{S /a:/b}'' - w~pliku \file{config.ps} programu \cmdname{dvips}. -\item Plik konfiguracyjny \KPS{} \file{texmf.cnf}, zawieraj±cy tak± liniê, - jak \samp{TEXINPUTS=/c:/d} (patrz poni¿ej). -\item Warto¶ci domy¶lne dla uruchamianych programów. -\end{enumerate} -\noindent Ka¿d± z~tych warto¶ci dla danej ¶cie¿ki przeszukiwania mo¿na -zobaczyæ, u¿ywaj±c opcji diagnostyki b³êdów (patrz ,,Diagnostyka b³êdów'' na -stronie~\pageref{sec:debugging}). - -\subsubsection{Pliki konfiguracyjne} - -\tolerance=3500 - \KPS{} szuka ¶cie¿ek przeszukiwania i~innych definicji w~\emph{plikach -konfiguracyjnych} o~nazwach \file{texmf.cnf}. -¦cie¿ka przeszukiwania u¿ywana do znajdowania tych plików okre¶lana jest -przez zmienn± \envname{TEXMFCNF} (domy¶lnie taki plik znajduje siê w~podkatalogu -\file{texmf/web2c}). -Czytane bêd± \emph{wszystkie} pliki \file{texmf.cnf} w~¶cie¿ce -przeszukiwania, -a~definicje we wcze¶niejszych plikach zast±pi± te w~pó¼niejszych. -Tak wiêc w~¶cie¿ce \verb|.:$TEXMF| warto¶ci pochodz±ce z~\file{./texmf.cnf} -zast±pi± te z~\verb|$TEXMF/texmf.cnf|. - -%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% - -Dociekliwy czytelnik mo¿e byæ zainteresowany sposobem, w~jaki programy -znajduj± plik \file{texmf.cnf}, skoro nie ma konieczno¶ci deklarowania -specyficznej zmiennej ¶rodowiskowej systemu. Otó¿ po³o¿enie domy¶lne jest -wkompilowane w~programy jako wzglêdne do ich po³o¿enia (okre¶lanego, jak -wiemy, w~¶cie¿ce specyfikowanej przez \texttt{\$PATH}): -\path{../../texmf/web2c/} b±d¼ \path{../texmf/web2c/}. Je¶li jawnie -deklarujemy zmienn± \envname{TEXMFCNF}, wymagane jest podanie bezwzglêdnej -¶cie¿ki. - -Czytaj±c zamieszczony poni¿ej opis formatu pliku \file{texmf.cnf}, -warto przegl±daæ jego zawarto¶æ. Po³o¿enie \emph{aktywnego} pliku -znajdziemy za pomoc± polecenia \texttt{kpsewhich texmf.cnf}. - -\begin{itemize} -\item - Komentarze zaczynaj± siê od ,,\texttt{\%}'', a~koñcz± na koñcu wiersza. -\item - Puste wiersze nie s± brane pod uwagê. -\item - Znak \bs{} na koñcu wiersza dzia³a jako znak kontynuacji, tzn. - oznacza, ¿e kolejny wiersz jest kontynuacj± bie¿±cego. - Spacja na pocz±tku kolejnego wiersza nie jest ignorowana. -\item - Pozosta³e wiersze maj± postaæ: -\begin{alltt} - \emph{zmienna}[.\emph{program}] [=] \emph{warto¶æ} -\end{alltt}% - gdzie \samp{=} i~otaczaj±ce spacje s± opcjonalne. -\item - ,,\texttt{\var{zmienna}}'' zawieraæ mo¿e dowolne znaki poza spacj±, - \samp{=}, lub \samp{.} (kropk±), najbezpieczniej jednak u¿ywaæ znaków - z~zakresu \samp{A-Za-z\_}. -\item - Napis ,,\texttt{.\var{program}}'' ma zastosowanie w~wypadku, gdy - uruchamiany program nosi nazwê \texttt{\var{program}} lub - \texttt{\var{program}.exe}. Pozwala to ró¿nym odmianom \TeX-a stosowaæ - ró¿ne ¶cie¿ki przeszukiwania. -\item ,,\texttt{\var{warto¶æ}}'' zawieraæ mo¿e dowolne znaki poza - ,,\texttt{\%}'' i \samp{@}. - Nie mo¿na u¿ywaæ konstrukcji ,,\texttt{\$\var{zmienna}.\var{program}}'' - po prawej stronie. Zamiast tego trzeba zastosowaæ zmienn± pomocnicz±. - ¦rednik \samp{;}\ u¿yty w~,,\texttt{\var{warto¶æ}}'' zamieniany jest na - \samp{:}\ je¿eli systemem operacyjnym jest Unix; umo¿liwia to istnienie - wspólnego pliku \file{texmf.cnf} dla systemów Unix oraz Windows. -\item - Wszystkie definicje czytane s± zanim cokolwiek zostanie rozwiniête, tak - wiêc do zmiennych mo¿na siê odwo³ywaæ przed ich zdefiniowaniem. -\end{itemize} -Oto fragment pliku konfiguracyjnego, ilustruj±cy wiêkszo¶æ opisanych powy¿ej -regu³ notacji: -\ifSingleColumn -\verbatiminput{examples/ex5.tex} -\else -jest pokazany na rys.~\ref{fig:config-sample}. -\fi - -\subsubsection{Rozwijanie ¶cie¿ek} -\label{Path-expansion} - -\KPS{} rozpoznaje w~¶cie¿kach przeszukiwania pewne specjalne znaki oraz -konstrukcje, podobne do tych dostêpnych w~pow³okach Unix. -Jako ogólny przyk³ad: z³o¿ona ¶cie¿ka -\verb+~$USER/{foo,bar}//baz+ rozwija siê do wszystkich podkatalogów pod -katalogami \file{foo} i~\file{bar} w~katalogu g³ównym \texttt{\$USER}, -które zawieraj± katalog lub plik \file{baz}. -Rozwiniêcia te opisane s± w~poni¿szych podrozdzia³ach. - -\subsubsection{Rozwijanie domy¶lne} -\label{Default-expansion} - -\tolerance=2500 -Je¿eli ¶cie¿ka przeszukiwania najwiêkszego uprzywilejowania (patrz ,,¬ród³a -¶cie¿ek'' na stronie~\pageref{Path-sources}) zawiera -\emph{dodatkowy dwukropek} (np. na pocz±tku, na koñcu lub podwójny) to \KPS{} -wstawia w~tym miejscu nastêpn± zdefiniowan± w~hierarchii uprzywilejowania -¶cie¿kê przeszukiwania. -Je¿eli ta wstawiona ¶cie¿ka ma dodatkowy dwukropek, to dzieje siê dalej to samo. -Przyk³adowo, je¿eli ustawiæ zmienn± ¶rodowiskow± -\tolerance=1500 - -\begin{alltt} -> \Ucom{setenv TEXINPUTS /home/karl:} -\end{alltt} -oraz warto¶æ \code{TEXINPUTS} pobran± z~\file{texmf.cnf} - -\begin{alltt} - .:\$TEXMF//tex -\end{alltt} -koñcow± warto¶ci± u¿yt± w~przeszukiwaniu bêdzie: - -\begin{alltt} - /home/karl:.:\$TEXMF//tex -\end{alltt} - -Poniewa¿ nieu¿ytecznym by³oby wstawiaæ warto¶æ domy¶ln± w~wiêcej ni¿ jednym -miejscu, \KPS{} zmienia tylko jeden dodatkowy \samp{:}\ i~pozostawia -inne bez zmian. \KPS{} najpierw szuka dwukropków na pocz±tku linii, potem na koñcu, -a~nastêpnie podwójnych. - -\subsubsection{Rozwijanie nawiasów} - -U¿yteczna jest mo¿liwo¶æ rozwijania nawiasów, co oznacza, ¿e np. -\verb+v{a,b}w+ rozwija siê do \verb+vaw:vbw+. -Nawiasy mo¿na te¿ zagnie¿d¿aæ. -Funkcji tej mo¿na u¿yæ do zaimplementowania ró¿nych hierarchii \TeX-owych -przez przypisanie listy nawiasów do \code{\$TEXMF}. Przyk³adowo, -w~pliku \file{texmf.cnf} mo¿na znale¼æ nastêpuj±c± definicjê: -\begin{verbatim} - TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN} -\end{verbatim} -U¿ywaj±c jej, mo¿na nastêpnie napisaæ co¶ w~rodzaju: -\begin{verbatim} - TEXINPUTS = .;$TEXMF/tex// -\end{verbatim} -co oznacza, ¿e po szukaniu w~katalogu bie¿±cym bêd± przeszukane kolejno -\code{\$TEXMFHOME/tex}, \code{\$TEXMFLOCAL/tex}, \code{\$TEXMFVAR/tex} -i~\code{\$TEXMFMAIN/tex} (wszystkie wraz z~katalogami ni¿szego poziomu; -dwie ostatnie ¶cie¿ki \emph{wy³±cznie} na podstawie zawarto¶ci -pliku \file{ls-R}). -Jest to wygodny sposób na uruchamianie dwóch równoleg³ych struktur \TeX-owych, -jednej ,,zamro¿onej'' (np. na \CD), a~drugiej ci±gle uaktualnianej nowo -pojawiaj±cymi siê wersjami. -U¿ywaj±c zmiennej \code{\$TEXMF} we wszystkich definicjach daje pewno¶æ, -¿e najpierw przeszukiwane jest drzewo uaktualnione. - -\subsubsection{Rozwijanie podkatalogów} -\label{Subdirectory-expansion} - -Dwa lub wiêcej kolejnych ,,ciachów'' (,,/'') w~elemencie ¶cie¿ki, -wystêpuj±cych po nazwie katalogu~\var{d}, zastêpowanych jest przez wszystkie -podkatalogi~\var{d}, najpierw podkatalogi znajduj±ce siê bezpo¶rednio -pod~\var{d}, potem te pod powy¿szymi i~tak dalej. Na ka¿dym etapie -kolejno¶æ, w~jakiej przeszukiwane s± katalogi, jest \emph{nieokre¶lona}. - -Je¶li wyszczególni siê cz³ony nazwy pliku po \samp{//}, to uwzglêdnione zostan± -tylko te podkatalogi, które zawieraj± powy¿sze cz³ony. -Na przyk³ad \samp{/a//b} rozwija siê do katalogów \file{/a/1/b}, -\file{/a/2/b}, \file{/a/1/1/b} itd., ale nie do \file{/a/b/c} czy \file{/a/1}. - -Mo¿liwe jest wielokrotne u¿ycie \samp{//} w~¶cie¿ce, jednak¿e \samp{//} -wystêpuj±ce na pocz±tku ¶cie¿ki nie jest brane pod uwagê. - -\subsubsection{Lista znaków specjalnych i~ich znaczeñ -- podsumowanie} - -Poni¿sza lista podsumowuje znaczenie znaków specjalnych w~plikach -konfiguracyjnych. - -\newcommand{\CODE}[1]{\makebox[2.2em][l]{\code{#1}}} -\begin{description} -\item[\CODE{:}] znak rozdzielaj±cy w~specyfikacji ¶cie¿ki; umieszczony na -pocz±tku lub na koñcu ¶cie¿ki zastêpuje domy¶lne rozwiniêcie ¶cie¿ki; -\item[\CODE{;}] znak rozdzielaj±cy dla systemów nieuniksowych - (dzia³a tak jak ,,\code{:}''); -\item[\CODE{\$}] rozwijanie zmiennej; -\item[\CODE{\string~}] oznacza katalog g³ówny u¿ytkownika; -\item[\CODE{\char`\{\dots\char`\}}] rozwijanie nawiasów, np. - \verb+a{1,2}b+ zmieni siê w~\verb+a1b:a2b+; -\item[\CODE{//}] rozwijanie podkatalogów (mo¿e wyst±piæ gdziekolwiek - w~¶cie¿ce, poza jej pocz±tkiem); -\item[\CODE{\%}] pocz±tek komentarza, obejmuj±cego wszystkie znaki do koñca - linii; -\item[\CODE{\bs}] znak kontynuacji (pozwala na prze³amanie wiersza - z~wyra¿eniem); -\item[\CODE{!!}] przeszukiwanie \emph{tylko} bazy danych, - a~\emph{nie} dysku. -\end{description} - - -\subsection{Bazy nazw plików} -\label{Filename-database} - -Podczas przeszukiwania \KPS{} stara siê zminimalizowaæ dostêp do dysku. -Niemniej, w~przypadku instalacji ze zbyt du¿± liczb± katalogów -przegl±danie ka¿dego dopuszczalnego katalogu w~poszukiwaniu pliku mo¿e -zabieraæ sporo czasu (ma to miejsce zw³aszcza, je¿eli przeszukaæ trzeba setki -katalogów z~fontami). -Dlatego te¿ \KPS{} mo¿e u¿ywaæ zewnêtrznego pliku z~,,baz± danych'' -o~nazwie \file{ls-R}, który zawiera przypisania plików do katalogów. -Unika siê w~ten sposób czasoch³onnego przeszukiwania dysku. - -Drugi plik z~baz± danych -- \file{aliases} -- pozwala na nadawanie -dodatkowych nazw plikom zawartym w~\file{ls-R}. -Mo¿e to byæ pomocne do adaptacji do DOS-owej konwencji ,,8.3'' nazewnictwa -plików w~plikach ¼ród³owych. - -\subsubsection{Baza nazw plików} -\label{ls-R} - -Jak ju¿ wspomniano powy¿ej, plik zawieraj±cy g³ówn± bazê nazw -plików musi nosiæ nazwê \file{ls-R}. -W~katalogu podstawowym ka¿dej hierarchii \TeX-owej (domy¶lnie \code{\$TEXMF}), -któr± chcemy w³±czyæ w~mechanizm przeszukiwania, umieszczaæ mo¿na po jednym -pliku \file{ls-R}; w~wiêkszo¶ci przypadków istnieje tylko jedna hierarchia. -\KPS{} szuka pliku \file{ls-R} w~¶cie¿ce \code{TEXMFDBS}. - -Najlepszym sposobem stworzenia i~utrzymywania pliku \file{ls-R} jest -uruchomienie skryptu \code{mktexlsr}, bêd±cego sk³adnikiem dystrybucji. -Jest on wywo³ywany przez ró¿ne skrypty typu \samp{mktex...}. -W~zasadzie skrypt ten jedynie wykonuje polecenie -\begin{alltt} -cd \var{/your/texmf/root} && ls -LAR ./ >ls-R -\end{alltt} -zak³adaj±c, ¿e polecenie \code{ls} danego systemu utworzy w³a¶ciwy format -strumienia wyj¶ciowego (\acro{GNU} \code{ls} dzia³a prawid³owo). -Aby mieæ pewno¶æ, ¿e baza danych jest zawsze aktualna, wygodnie jest - przebudowywaæ j± regularnie za pomoc± demona \code{cron}. - %tak ¿e wraz ze zmianami - %w~instalowanych plikach -- np. po instalacji lub uaktualnianiu pakietu - %\LaTeX{} -- plik \file{ls-R} jest uaktualniany automatycznie. - -Je¶li pliku nie ma w~bazie danych, \KPS{} domy¶lnie przechodzi do -przeszukiwania dysku. Je¿eli jednak dany element ¶cie¿ki zaczyna sie od -\samp{!!}, w~poszukiwaniu tego elementu sprawdzona zostanie \emph{jedynie} -baza danych, a~nigdy dysk. - -\subsubsection{kpsewhich -- program do przeszukiwania ¶cie¿ek} -\label{Invoking-kpsewhich} - -Przeszukiwanie ¶cie¿ek przez program \texttt{kpsewhich} jest niezale¿ne od -jakiejkolwiek aplikacji. -Mo¿e on byæ przydatny jako rodzaj programu \code{find}, za pomoc± którego -lokalizowaæ mo¿na pliki w~hierarchiach \TeX-owych (jest on u¿ywany -intensywnie w~skryptach \samp{mktex...} tej dystrybucji). - -\begin{alltt} -> \Ucom{kpsewhich \var{opcje}\dots{} \var{nazwa-pliku}\dots{}} -\end{alltt} -Parametry wyszczególnione w~,,\texttt{\var{opcje}}'' mog± zaczynaæ siê zarówno od -\samp{-}, jak i~od \samp{-{}-}, a~dozwolony jest ka¿dy jednoznaczny skrót. - -\KPS{} traktuje ka¿dy argument nie bêd±cy parametrem jako nazwê pliku -i~zwraca pierwsz± odnalezion± nazwê. -Nie ma parametru nakazuj±cego zwracanie wszystkich nazw plików o~okre¶lonej -nazwie (w~tym celu mo¿na wykorzystaæ Unix-owy program \samp{find}). - -Wa¿niejsze parametry opisane s± poni¿ej. - -\begin{ttdescription} -\item[\texttt{-{}-dpi=\var{num}}]\mbox{}\\* - Ustaw rozdzielczo¶æ na ,,\texttt{\var{num}}''; ma to tylko wp³yw na - przeszukiwanie fontów \samp{gf} i~\samp{pk}. Dla zgodno¶ci - z~\cmdname{dvips} parametr - \samp{-D} dzia³a identycznie. Domy¶ln± warto¶ci± jest 600. -\item[\texttt{-{}-format=\var{nazwa}}]\mbox{}\\ - Ustawienie formatu (typu pliku) przeszukiwania na ,,\texttt{\var{nazwa}}''. - Domy¶lnie format odgadywany jest z~nazwy pliku. - Dla formatów, które nie maj± przydzielonego jednoznacznego rozszerzenia, - takich jak niektóre pliki \MP{}-owe czy pliki konfiguracyjne - \cmdname{dvips}-a, nale¿y wyszczególniæ nazwê, których listê wy¶wietli - uruchomienie \texttt{kpsewhich -{}-help}. - -\item[\texttt{-{}-mode=\var{napis}}]\mbox{}\\* - Ustaw nazwê trybu na ,,\texttt{\var{napis}}''; dotyczy to jedynie szukania - fontów \samp{gf} oraz \samp{pk}. - Brakuje warto¶ci domy¶lnej -- odnaleziony zostanie dowolny - wyszczególniony tryb. -\item[\texttt{-{}-must-exist}]\mbox{}\\ - Zrób wszystko co mo¿liwe, aby odnale¼æ pliki, w³±czaj±c w~to przede wszystkim - przeszukanie dysku. - Domy¶lnie, w~celu zwiêkszeniu efektywno¶ci dzia³ania, sprawdzana jest - tylko baza \file{ls-R}. -\item[\texttt{-{}-path=\var{napis}}]\mbox{}\\ - Szukaj w~¶cie¿ce ,,\texttt{\var{napis}}'' (rozdzielonej, jak - zwykle, dwukropkami), zamiast zgadywaæ ¶cie¿kê przeszukiwania z~nazwy - pliku. - \samp{//} i~wszystkie zwyk³e rozszerzenia s± mo¿liwe. - Parametry \samp{-{}-path} oraz \samp{-{}-format} wzajemnie siê wykluczaj±. -\item[\texttt{-{}-progname=\var{nazwa}}]\mbox{}\\ - Ustaw nazwê programu na ,,\texttt{\var{nazwa}}''. - Mo¿e to mieæ wp³yw na ¶cie¿kê przeszukiwania poprzez - ,,\texttt{.\var{program}}'' w~plikach konfiguracyjnych. - Ustawieniem domy¶lnym jest \samp{kpsewhich}. -\item[\texttt{-{}-show-path=\var{nazwa}}]\mbox{}\\ - Pokazuje ¶cie¿kê u¿ywan± do poszukiwania plików typu - ,,\texttt{\var{nazwa}}''. - U¿yte mo¿e byæ zarówno rozszerzenie (\samp{.pk}, \samp{.vf}, etc.), jak - i~nazwa pliku, tak jak w~wypadku parametru \samp{-{}-format}. -\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ - ustawia parametry wykrywania b³êdów na ,,\texttt{\var{num}}''. -\end{ttdescription} - -%Zmienne ¶rodowiskowe domy¶lnie ustawiane s± w~pliku konfiguracyjnym -%\file{texmf.cnf}. W~wypadku gdy chce siê uniewa¿niæ warto¶ci zmiennych -%wyszczególnione w~tym pliku, mo¿na narzuciæ ich ustawienie w~¶rodowisku, -%w~którym uruchamiane s± programy. - -\subsubsection{Przyk³ady u¿ycia} -\label{SExamplesofuse} - -Przyjrzyjmy sie teraz, jak dzia³a \KPS{}. - -\begin{alltt} -> \Ucom{kpsewhich article.cls} -/usr/local/texmf-dist/tex/latex/base/article.cls -\end{alltt} -Szukamy pliku \file{article.cls}. -Poniewa¿ rozszerzenie \samp{.cls} jest jednoznaczne, nie musimy zaznaczaæ, ¿e -poszukujemy pliku typu ,,tex'' (katalogi plików ¼ród³owych \TeX-a). -Znajdujemy go w~podkatalogu \file{tex/latex/base}, pod katalogiem nadrzêdnym -\samp{texmf-dist}. -Podobnie wszystkie poni¿sze pliki odnajdowane s± bez\-pro\-ble\-mo\-wo -dziêki swoim jednoznacznym rozszerzeniom: -\begin{alltt} -> \Ucom{kpsewhich array.sty} -/usr/local/texmf-dist/tex/latex/tools/array.sty -> \Ucom{kpsewhich latin1.def} -/usr/local/texmf-dist/tex/latex/base/latin1.def -> \Ucom{kpsewhich size10.clo} -/usr/local/texmf-dist/tex/latex/base/size10.clo -> \Ucom{kpsewhich small2e.tex} -/usr/local/texmf-dist/tex/latex/base/small2e.tex -> \Ucom{kpsewhich tugboat.bib} -/usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib -\end{alltt} - -\noindent (ostatni plik to \BibTeX-owa baza bibliograficzna dla artyku³ów -\textsl{TUGBoat}). - -\begin{alltt} -> \Ucom{kpsewhich cmr10.pk} -\end{alltt} -Pliki czcionek bitmapowych typu \file{.pk} u¿ywane s± przez sterowniki, -takie jak \cmdname{dvips} % ??? dvips to chyba nie przegl±darka --- -czy \cmdname{xdvi}. % w oryg. by³o display programs like dvips... -W~tym wypadku wynik przeszukiwania oka¿e siê pusty, poniewa¿ -w~systemie brak gotowych wygenerowanych czcionek \samp{.pk} Computer Modern -(wynika to z~faktu u¿ywania w~\TL{} fontów PostScript-owych Type1). -\begin{alltt} -> \Ucom{kpsewhich wsuipa10.pk} -\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk -\else /usr/local/texmf-var/fonts/pk/ljfour/public/ -..... wsuipa/wsuipa10.600pk -\fi\end{alltt} -Dla tych fontów (alfabetu fonetycznego) musieli¶my wygenerowaæ pliki -\samp{.pk}, a~poniewa¿ domy¶lnym \MF{}-owym trybem naszej instalacji jest -\texttt{ljfour} z~podstawow± rozdzielczo¶ci± 600dpi, zwracany jest taki -w³a¶nie wynik. -\begin{alltt} -> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} -\end{alltt} -W~tym wypadku, kiedy zaznaczamy, ¿e interesuje nas rozdzielczo¶æ -300dpi (\texttt{-dpi=300}), to widzimy, ¿e w~naszej instalacji taka -czcionka nie jest dostêpna. -Program taki jak \cmdname{dvips} czy \cmdname{xdvi} zatrzyma³by siê, aby -utworzyæ pliki \texttt{.pk} w~wymaganej rozdzielczo¶ci (u¿ywaj±c skryptu -\cmdname{mktexpk}). - -Zwrócimy teraz nasz± uwagê na pliki nag³ówkowe i~konfiguracyjne -programu \cmdname{dvips}. -Najpierw szukamy pliku PostScript-owego prologu \file{tex.pro}, -wykorzystywanego dla potrzeb \TeX-a. Drugi przyk³ad pokazuje -poszukiwanie pliku konfiguracyjnego \file{config.ps}, za¶ trzeci -- -szukanie pliku mapy czcionek PostScriptowych \file{psfonts.map} -(pocz±wszy od obecnej edycji, pliki \file{.map} i~\file{.enc} -maj± w³asne regu³y przeszukiwania ¶cie¿ek i~zmienione po³o¿enie w~ramach -drzew \dirname{texmf}). -Poniewa¿ rozszerzenie \samp{.ps} nie jest jednoznaczne, musimy zaznaczyæ -wyra¼nie jaki typ jest wymagany dla pliku -\texttt{config.ps} (,,\texttt{dvips config}''). -\begin{alltt} -> \Ucom{kpsewhich tex.pro} -/usr/local/texmf/dvips/base/tex.pro -> \Ucom{kpsewhich --format="dvips config" config.ps} -/usr/local/texmf-var/dvips/config/config.ps -> \Ucom{kpsewhich psfonts.map} -/usr/local/texmf-var/fonts/map/dvips/updmap/psfonts.map -\end{alltt} - -Nastêpnie przyjrzymy siê bli¿ej plikom pomocniczym fontów Times z~kolekcji -URW. W~standardzie nazewnictwa fontów maj± one prefiks \samp{utm}. -Pierwszy plik którego szukamy, to plik konfiguracyjny, zawieraj±cy nazwê -pliku z~przemapowaniem fontów: -\begin{alltt} -> \Ucom{kpsewhich --format="dvips config" config.utm} - /usr/local/texmf-dist/dvips/psnfss/config.utm -\end{alltt} -W~pliku tym znajduje siê wiersz: -\begin{alltt} - p +utm.map -\end{alltt} -wskazuj±cy na plik \file{utm.map}, który chcemy zlokalizowaæ w~nastêpnej -kolejno¶ci: -\begin{alltt} -> \Ucom{kpsewhich utm.map} - /usr/local/texmf-dist/fonts/map/dvips/times/utm.map -\end{alltt} -Plik z~przemapowaniem definiuje nazwy czcionek PostScriptowych Type~1 -w~zestawie fontów URW, za¶ jego zawarto¶æ wygl±da nastêpuj±co -(pokazane s± tylko fragmenty wierszy): -\begin{alltt} -utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} -\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb -\else /usr/local/texmf-dist/fonts/type1/ -... urw/utm/utmr8a.pfb -\fi\end{alltt} - -Powy¿sze przyk³ady pokazuj±, jak ³atwo mo¿na znajdowaæ lokalizacjê danego -pliku. Jest to wa¿ne zw³aszcza wówczas, gdy istnieje podejrzenie, ¿e gdzie¶ -zawieruszy³a siê b³êdna wersja jakiego¶ pliku; \cmdname{kpsewhich} poka¿e tylko -pierwszy napotkany plik. - -\subsubsection{Diagnostyka b³êdów} -\label{sec:debugging} - -Czasami niezbêdne s± informacje o~tym, jak program sobie radzi -z~odniesieniami do plików. Aby da³o siê je uzyskaæ w~wygodny sposób, -\KPS{} oferuje ró¿ne poziomy diagnostyki b³êdów: -\begin{itemize} -\item[\texttt{\ 1}] wywo³ania \texttt{stat} (testy pliku). Podczas - uruchamiania z~uaktualnion± baz± danych \file{ls-R} nie powinno to - przewa¿nie dawaæ ¿adnego wyniku. -\item[\texttt{\ 2}] Zapis odwo³añ do tablic asocjacyjnych (\emph{hash - tables}), takich jak baza \file{ls-R}, pliki przemapowañ, pliki konfiguracyjne. -\item[\texttt{\ 4}] Operacje otwarcia i~zamkniêcia pliku. -\item[\texttt{\ 8}] Ogólne informacje o~¶cie¿kach dla typów - plików szukanych przez \KPS; u¿yteczne dla znalezienia ¶cie¿ki - zdefiniowanej dla danego pliku. -\item[\texttt{16}] Lista katalogów dla ka¿dego z~elementów ¶cie¿ki - (odnosi siê tylko do poszukiwañ na dysku). -\item[\texttt{32}] Poszukiwania plików. -\end{itemize} -Warto¶æ \texttt{-1} ustawia wszystkie powy¿sze opcje -- w~praktyce, -poszukuj±c przyczyny b³êdów, prawdopodobnie bêdziesz zawsze u¿ywaæ -tych poziomów. - -Podobnie, w~przypadku programu \cmdname{dvips}, ustawiaj±c kombinacjê -prze³±czników wykrywania b³êdów, mo¿na dok³adnie ¶ledziæ, sk±d pochodz± pliki. -W~sytuacji, gdy plik nie zostanie odnaleziony, widaæ, w~których katalogach -program szuka³ danego pliku, dziêki czemu mo¿na siê zorientowaæ, w~czym -problem. - -Ogólnie mówi±c, poniewa¿ programy odwo³uj± siê wewnêtrznie do -biblioteki \KPS{}, opcje wykrywania b³êdów mo¿na wybraæ przy u¿yciu -zmiennej ¶rodowiskowej \envname{KPATHSEA\_DEBUG}, ustawiaj±c j± -na opisan± powy¿ej warto¶æ (kombinacjê warto¶ci). - -\noindent -\textbf{Uwaga dla u¿ytkowników Windows:} w~systemie tym nie³atwo -przekierowaæ komunikaty programu do pliku. Do celów diagnostycznych -mo¿na chwilowo ustawiæ zmienne (w~oknie CMD): -\begin{verbatim} -SET KPATHSEA_DEBUG_OUTPUT=err.log -SET KPATHSEA_DEBUG=-1 -\end{verbatim} - -Rozwa¿my na przyk³ad ma³y \LaTeX-owy plik ¼ród³owy \file{hello-world.tex}, -który zawiera: -\begin{verbatim} - \documentclass{article} - \begin{document} - Hello World! - \end{document} -\end{verbatim} -Ten ma³y plik korzysta jedynie z~fontu \file{cmr10}. Przyjrzyjmy siê, jak -\cmdname{dvips} przygotowuje plik PostScript-owy (chcemy u¿yæ wersji Type1 -fontu Computer Modern, st±d opcja \texttt{-Pcms}). -\begin{alltt} -> \Ucom{dvips -d4100 hello-world -Pcms -o} -\end{alltt} -Mamy tu do czynienia jednocze¶nie z~czwart± klas± wykrywania b³êdów -programu \cmdname{dvips} (¶cie¿ki fontowe) oraz z~rozwijaniem elementu -¶cie¿ki przez \KPS{} (patrz: \emph{Dvips Reference Manual}, -\OnCD{texmf/doc/dvips/dvips.pdf}). - %Komunikaty z~uruchomienia programu (lekko zmodyfikowane) znajduj± siê - %na~rys.~\ref{fig:dvipsdbga}. - %\begin{figure*}[tp] - %\centering - %\input{examples/ex6a.tex} - %\caption{Szukanie pliku konfiguracyjnego}\label{fig:dvipsdbga} - % - %\bigskip - % - %\input{examples/ex6b.tex} - %\caption{Szukanie pliku prologu}\label{fig:dvipsdbgb} - % - %\bigskip - % - %\input{examples/ex6c.tex} - %\caption{Szukanie pliku fontu}\label{fig:dvipsdbgc} - %\end{figure*} - Program \cmdname{dvips} zaczyna pracê od zlokalizowania potrzebnych mu plików. -Najpierw znajduje plik \file{texmf.cnf}, który zawiera ¶cie¿ki -przeszukiwania dla innych plików. Potem znajduje bazê danych \file{ls-R} -(w~celu optymalizacji szukania plików), nastêpnie plik \file{aliases}, -który umo¿liwia deklarowanie ró¿nych nazw (np. krótkie \acro{DOS}-owe ,,8.3'' -i~bardziej naturalne d³u¿sze wersje) dla tych samych plików. -Nastêpnie \cmdname{dvips} znajduje podstawowy plik konfiguracyjny -\file{config.ps}, zanim poszuka pliku z~ustawieniami u¿ytkownika -\file{.dvipsrc} (który w~tym wypadku \emph{nie} zostaje odnaleziony). -W~koñcu \cmdname{dvips} lokalizuje plik konfiguracyjny \file{config.cms} -dla fontów PostScript-owych Computer Modern (jest to inicjowane przez -dodanie parametru \texttt{-Pcms} przy uruchamianiu programu). -Plik ten zawiera listê plików z~,,mapami'', które definiuj± relacje -pomiêdzy \TeX-owymi, PostScript-owymi i~systemowymi nazwami fontów. -\begin{alltt} -> \Ucom{more /usr/local/texmf/dvips/config/config.cms} -p +bsr.map -p +bakomaextra.map -\end{alltt} -W~ten sposób \cmdname{dvips} wyszukuje wszystkie te pliki oraz g³ówny plik -z~przemapowaniem -\file{psfonts.map}, który ³adowany jest domy¶lnie (zawiera on deklaracje -czêsto u¿ywanych fontów postscriptowych; wiêcej szczegó³ów na temat -postscriptowych plików przemapowañ fontów mo¿na znale¼æ w~ostatniej czê¶ci -rozdzia³u \ref{SExamplesofuse}). - -W~tym miejscu \cmdname{dvips} zg³asza siê u¿ytkownikowi: -\begin{alltt}\ifSingleColumn -This is dvips 5.86 Copyright 1999 Radical Eye Software (www.radicaleye.com) -\else\small{}This is dvips 5.86 Copyright 1999 Radical Eye... -\fi\end{alltt}% decided to accept slight overrun in tub case -\ifSingleColumn -\ldots potem szuka pliku prologu \file{texc.pro}: -\begin{alltt}\small -kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro -\end{alltt} -\else -potem szuka pliku prologu \file{texc.pro}. - %(patrz rys.~\ref{fig:dvipsdbgb}). - -\fi -Po znalezieniu szukanego pliku \cmdname{dvips} podaje datê i~czas -oraz informuje o~generowaniu pliku \file{hello-world.ps}. -Poniewa¿ potrzebuje pliku z~fontem \file{cmr10}, a~jest on -zadeklarowany jako dostêpny, wy¶wietla komunikat: -\begin{alltt}\small -TeX output 1998.02.26:1204' -> hello-world.ps -Defining font () cmr10 at 10.0pt -Font cmr10 is resident. -\end{alltt} -Teraz trwa poszukiwanie pliku \file{cmr10.tfm}, który zostaje znaleziony, -po czym \cmdname{dvips} powo³uje siê na kilka innych plików startowych -(nie pokazanych). W~koñcu przyk³adowy font Type1 \file{cmr10.pfb} -zostaje zlokalizowany i~do³±czony do pliku wynikowego (patrz ostatnia linia): -\begin{alltt}\small -kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, - path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: - /var/tex/fonts/tfm//). -kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm -kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, - ... - -kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb -[1] -\end{alltt} - -\subsection{Parametry kontroluj±ce dzia³anie programów} -Inn± u¿yteczn± cech± \Webc{} jest mo¿liwo¶æ ustalania wielu parametrów -okre¶laj±cych wielko¶æ pamiêci za pomoc± pliku \texttt{texmf.cnf}. - %Za³±cznik~\ref{app:texmf.cnf} zaczynaj±cy siê na - %stronie~\pageref{app:texmf.cnf} zawiera listing pliku \texttt{texmf.cnf}. - Ustawienia wszystkich parametrów znajduj± siê w~czê¶ci trzeciej pliku. -Najwa¿niejszymi zmiennymi s±: -\begin{description} -\item[\code{main\_memory}] Ca³kowita wielko¶æ pamiêci dostêpnej dla - \TeX-a, \MF{}-a i~\MP{}-a. Dla ka¿dego nowego ustawienia tej zmiennej - nale¿y wykonaæ nowy format. - %Przyk³adowo, mo¿esz wygenerowaæ ,,ogromn±'' wersjê formatu \TeX{} i~nazwaæ - %taki plik \texttt{hugetex.fmt}. - %Dziêki standardowemu sposobowi nazywania programów przez - %\KPS{}, okre¶lona warto¶æ zmiennej \verb|main_memory| bêdzie - %przeczytana z~pliku \texttt{texmf.cnf} (por. warto¶æ standardow± - %oraz warto¶æ ,,ogromn±'', wykorzystywan± przez program \texttt{hugetex}, - %itd.). - % -\item[\code{extra\_mem\_bot}] Dodatkowa wielko¶æ pamiêci przeznaczonej - na ,,du¿e'' struktury danych \TeX-a, takie jak: pude³ka, kleje itd.; - przydatna zw³aszcza w~wypadku korzystania z~pakietu \PiCTeX{}. - % -\item[\code{font\_mem\_size}] Wielko¶æ pamiêci przeznaczonej przez - \TeX-a na informacje o~fontach. Jest to mniej wiêcej ogólna - wielko¶æ wczytywanych przez \TeX-a plików TFM. - % -\item[\code{hash\_extra}] Dodatkowa wielko¶æ pamiêci przeznaczonej - na tablicê zawieraj±c± nazwy instrukcji. Tablica g³ówna - mo¿e zmie¶ciæ w~przybli¿eniu 10000 nazw; wielko¶æ ta mo¿e siê okazaæ - zbyt ma³a, np. w~wypadku obszernej ksi±¿ki zawieraj±cej liczne - odsy³acze. Domy¶lna warto¶æ \texttt{hash\_extra} to \texttt{50000}. -\end{description} - % -Oczywi¶cie powy¿sza mo¿liwo¶æ nie zast±pi prawdziwej, dynamicznej -alokacji pamiêci. Jest to jednak niezwykle trudne -do zaimplementowania w~obecnej wersji \TeX-a i~dlatego -powy¿sze parametry stanowi± praktyczny kompromis, pozwalaj±c -na pewn± elastyczno¶æ. - -Nale¿y tu jednak nadmieniæ, i¿ nie wszystkie programy korzystaj± -z tych zmiennych. Np. Lua\TeX\ posiada nowoczesn±, -w~pe³ni dynamiczn± alokacjê pamiêci, a zatem powy¿sze zmienne s± -w tym przypadku po prostu ignorowane. - -%%==== -%\begin{comment} %% nie wiem czemu rezygnowaæ z tej czê¶ci (SW) -\section{Budowa systemu na nowej platformie uniksowej}\label{sec:build} -Je¿eli mamy do czynienia z~platform±, dla której nie s± dostarczone binaria, -trzeba bêdzie skompilowaæ \TeX-a oraz towarzysz±ce mu programy. -Nie jest to takie trudne, jak siê wydaje. -Wszystko czego potrzebujemy, znajduje siê na \DVD{} w~katalogu -\texttt{source}. - -Najpierw nale¿y zainstalowaæ g³ówne drzewo plików \TeX-owych z~\CD{} -\TL{} (najlepiej wykonaæ instalacjê podstawow±, bez wybierania -binariów systemowych). - -\subsection{Warunki wstêpne} -Do skompilowania ca³ego \TeX-a i~jego programów pomocniczych potrzeba -oko³o 100 megabajtów wolnego miejsca na dysku. -Potrzebny jest tak¿e kompilator \acro{ANSI}~C, oprogramowanie \cmdname{make}, -skaner leksykalny oraz generator parserów. -Programy u¿ytkowe \acro{GNU} (\cmdname{gcc}, \acro{GNU} -\cmdname{make}, \cmdname{m4}, \cmdname{flex}, \cmdname{bison}) -s± najlepiej przetestowanymi na ró¿nych platformach. -Poprawnie powinny pracowaæ \cmdname{gcc}-2.7.*, \cmdname{flex}-2.4.7 -i~\acro{GNU}\,\cmdname{make}-3.72.1 lub nowszy. -Mo¿na te¿ korzystaæ z~innych kompilatorów C i~programów -\cmdname{make}, wymaga to jednak dobrego zrozumienia zasad tworzenia -programów uniksowych, aby móc poradziæ sobie z~ewentualnymi problemami. - %W~wyniku wykonania polecenia \texttt{uname} powinni¶my - %otrzymaæ jak±¶ rozs±dn± warto¶æ. - -\subsection{Konfiguracja} -Nale¿y rozpakowaæ ¼ród³a ze skompresowanego pliku \texttt{tar} -z~katalogu \dirname{source} na twardy dysk, a~potem przej¶æ do katalogu, -do którego zosta³y one skopiowane. -Teraz trzeba siê zdecydowaæ, gdzie bêdzie g³ówny katalog instalacji, -np.\ \path|/usr/TeX| lub \path|/usr/local/TeX|. -Naturalnie, nale¿y u¿yæ tej samej lokalizacji, która zosta³a u¿yta -podczas instalacji g³ównego drzewa \TeX-owego. - -Uruchomiæ \textsf{configure} z~linii poleceñ: -\begin{alltt} -> \Ucom{./configure --prefix=/usr/local/TeX} -\end{alltt} - -Katalog ,,prefix'' to ten, w~którym zainstalowane zosta³o g³ówne drzewo -\TeX-owe. Zostanie u¿yty nastêpuj±cy uk³ad katalogów - (\verb|$TEXDIR| oznacza wybrany powy¿ej katalog): - -\noindent -\begin{tabular}{>{\ttfamily}ll@{}} - \dirname{$TEXDIR/man} & strony manuala uniksowego,\\ - \dirname{$TEXDIR/share/texmf} & g³ówne drzewo \TeX-owe, - zawieraj±ce makra itp.,\\ - \dirname{$TEXDIR/info} & podrêczniki w formacie \acro{GNU} - info,\\ - \dirname{$TEXDIR/bin/$PLATFORM} & binaria\\ -\end{tabular} -%$ - -Mo¿na unikn±æ stosowania ,,\dirname{share/}'' przed katalogiem -\dirname{texmf}, poniewa¿ \dirname{$TEXDIR/share/texmf} -i~\dirname{$TEXDIR/texmf} s± wykrywane automatycznie przez skrypt \cmdname{configure}. -W~razie wybrania innego katalogu, trzeba ten katalog wyszczególniæ -parametrem \verb|--datadir| skryptu \cmdname{configure}. - -Je¿eli nie chcemy u¿ywaæ katalogu \dirname{$PLATFORM} -(a~wiêc umie¶ciæ binaria bezpo¶rednio w~\dirname{$TEXDIR/bin}), to -w~wywo³aniu skryptu \cmdname{configure} nale¿y u¿yæ parametru -\verb|--disable-multiplatform|. - -Wiêcej dostêpnych parametrów (np. pomijanie pakietów opcjonalnych, takich -jak \OMEGA) mo¿na zobaczyæ, uruchamiaj±c -\texttt{./configure -{}-help}. - -\subsection{Uruchamianie \textsf{make}} -Po upewnieniu siê, ¿e nie jest ustawiona zmienna pow³oki \texttt{noclobber}, -nale¿y napisaæ: -\begin{alltt} -> \Ucom{make world} -\end{alltt} -i~\ldots zaparzyæ sobie kawê. - -Mo¿e siê te¿ przydaæ zapisanie ca³ego procesu -kompilacji w~pliku \texttt{.log}: -\begin{alltt} -> \Ucom{sh -c "make world >world.log 2>\&1" \&} -\end{alltt} -Zanim stwierdzimy, ¿e wszystko jest w~porz±dku, warto sprawdziæ, czy w~pliku -\texttt{.log} nie ma komunikatów b³êdów (kiedy polecenie zwraca kod b³êdu, -\acro{GNU} \cmdname{make} zawsze u¿ywa sekwencji \samp{***}), -i~czy utworzone zosta³y wszystkie binaria: -\begin{alltt} -> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} -> \Ucom{ls | wc} -\end{alltt} -Oczekiwanym rezultatem jest ponad 200. Polecenie \texttt{make world} jest -równowa¿ne z~\texttt{make all install strip}. -Je¶li do uruchamiania \texttt{make install} potrzebne s± specjalne -uprawnienia, mo¿na uruchomiæ dwie oddzielne sesje \cmdname{make}: -\begin{alltt} -> \Ucom{make all} -> \Ucom{su} -> \Ucom{make install strip} -\end{alltt} - -\subsection{Koñcowe kroki konfiguracyjne} -Nale¿y uaktualniæ zmienn± \envname{PATH} o~nazwê katalogu zawieraj±cego -w³a¶nie zainstalowane binaria (np.\ -\dirname{/usr/local/TeX/bin/mips-sgi-irix6.3}); podobnie post±piæ trzeba -z~\envname{MANPATH} i~\envname{INFOPATH} i~do³±czyæ do nich -odpowiednie nazwy podkatalogów, tj.\ -\dirname{$TEXDIR/man} oraz \dirname{$TEXDIR/info}. -Patrz czê¶æ~\ref{sec:postinstall} (str.~\pageref{sec:postinstall}). - -Je¶li zechcesz udostêpniæ skompilowane przez siebie programy, skontaktuj -siê z~nami (\url{tex-live@tug.org}); chêtnie umie¶cimy je na stronie \TL. -%\end{comment} - -%-------------------------- -\section{Podziêkowania} %\label{sec:acknowl} - -\TL{} jest wspólnym dzie³em prawie wszystkich grup \TeX-owych. -Niniejsza edycja \TL{} zosta³a opracowana pod kierownictwem Karla Berry'ego, -przy g³ównym wspó³udziale: - -\begin{itemize*} -\item grup \TeX-owych: miêdzynarodowej, niemieckiej, holenderskiej i~polskiej - (odpowiednio: \acro{TUG}, \acro{DANTE} e.V., \acro{NTG}, i~\acro{GUST}), - które wspólnie zapewniaj± potrzebn± infrastrukturê techniczn± - i~organizacyjn±. Do³±cz do swojej grupy \TeX-owej!; -\item zespo³u \acro{CTAN} (w~szczególno¶ci Robina Fairbairnsa, Jima - Hef{}ferona i~Rainera Sch\"opfa), który dystrybuuje obrazy \TL{} i~udostêpnia - wspóln± infrastrukturê s³u¿±c± aktualizacji pakietów, od której zale¿y \TL{}; -\item Petera Breitenlohnera i~zespo³u \eTeX, którzy stworzyli stabiln± - podstawê przysz³ych wersji \TeX-a (Peter dodatkowo s³u¿y nieustann± pomoc± - w~wykorzystaniu narzêdzi autotools w~\TL); -\item Thomasa Essera, autora wspania³ego \teTeX-a, bez którego - \TL{} z~ca³± pewno¶ci± by nie powsta³, i~którego sta³a - pomoc umo¿liwi³a doskonalenie tej dystrybucji; -\item Michaela Goossensa, który by³ wspó³autorem pierwotnej dokumentacji; -\item Eitana Gurari, autora programu \TeX4ht{} (wykorzystanego do - tworzenia niniejszej dokumentacji w~wersji \HTML), który niezmordowanie - pracowa³ nad jego ulepszaniem i~b³yskawicznie dostarcza³ poprawki; -\item Hansa Hagena, który dostosowywa³ \ConTeXt\ do potrzeb \TL; -\item \Thanh{}a, Martina Schr\"odera i~zespo³u pdf\TeX-a, którzy ci±gle - ulepszali mo¿liwo¶ci \TeX-a; -\item Hartmuta Henkela, maj±cego istotny udzia³ w~rozwoju pdf\TeX-a, - Lua\TeX-a i~innych programów; -\item Taco Hoekwatera, który wznowi³ rozwój MetaPosta i~pracowa³ nad - Lua\TeX-em, jak te¿ pomóg³ w~integracji \ConTeXt\ w~\TL; -\item Paw³a Jackowskiego, który wykona³ instalator dla Windows \cmdname{tlpm} - i~Tomka £uczaka, twórcy \cmdname{tlpmgui} (programy te by³y wykorzystane - w~poprzednich edycjach); -\item Akira Kakuto, który dostarczy³ programy dla Windows, pochodz±ce - z~dystrybucji \acro{W32TEX} - (\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}), - stale dostosowywane i~aktualizowane dla potrzeb \TL; -\item Jonathana Kew z firmy \acro{SIL}, który zainicjowa³ now± ¶cie¿kê - rozwojow± -- Xe\TeX{}, i~który w³o¿y³ sporo wysi³ku w~zintegrowanie - tego programu z~\TL, jak równie¿ zapocz±tkowa³ prace nad instalatorem dla - Mac\TeX; -\item Dicka Kocha, który pielêgnuje Mac\TeX-a (\url{http://tug.org/mactex}) - w~¶cis³ym po³±czeniu z~\TL i~bardzo sympatycznie wspó³pracuje; -\item Reinharda Kotuchy, maj±cego istotny udzia³ w~stworzeniu nowej infrastruktury - i~programu instalacyjnego dla \TL{} 2008, uparcie d±¿±cego do ujednolicenia - dzia³ania \TL{} w~Windows i~Unix, który równie¿ opracowa³ skrypt - \texttt{getnonfreefonts} i~wykona³ wiele innych prac; -\item Siep Kroonenberg, która równie¿ wziê³a udzia³ w~stworzeniu nowej - infrastruktury i~programu instalacyjnego dla \TL{} 2008 (szczególnie dla - Windows) oraz w³o¿y³a ogrom pracy aktualizuj±c tê dokumentacjê; -\item Petra Ol\shac{}\aac{}ka, który koordynowa³ i~sprawdza³ - przygotowanie czeskich i~s³owackich pakietów; -\item Toshio Oshimy, który opracowa³ przegl±darkê \cmdname{dviout} dla Windows; -\item Manuela P\'egouri\'e-Gonnarda, który pomóg³ w~aktualizacji pakietów - i~pracowa³ nad \cmdname{tldoc}. -\item Fabrice'a Popineau, który pierwszy stworzy³ wersje oprogramowania - dla Windows; -\item Norberta Preininga, g³ównego architekta infrastruktury i~programu - instalacyjnego \TL{} 2008, a~przyczyni³ siê te¿ do aktualizacji pakietów, - koordynowania (wraz z~Frankiem K\"usterem) debianowej wersji \TL{}, - i~przedstawi³ wiele sugestii ulepszeñ; -\item Sebastiana Rahtza, który stworzy³ \TL{} i~kierowa³ projektem przez - wiele lat; -\item Vladimira Volovicha, który wydatnie pomóg³ w~rozwi±zywaniu problemów - przeno¶no¶ci, szczególnie za¶ umo¿liwi³ do³±czenia \cmdname{xindy}; -\item Staszka Wawrykiewicza, g³ównego testuj±cego \TL{} w~ró¿nych systemach, - który ponadto koordynowa³ przygotowanie wszystkich polskich dodatków (fontów, - programów instalacyjnych i~wielu innych); -\item Olafa Webera, który cierpliwie pielêgnowa³ Web2C, od którego wszystko zale¿y; -\item Gerbena Wierda, który przygotowa³ oprogramowanie i~wsparcie dla - \MacOSX{}; -\item Grahama Williamsa, którego prace nad katalogiem pakietów bardzo - pomog³y w~przygotowaniu dystrybucji. -\end{itemize*} - -Binaria dla ró¿nych platform skompilowali: -Reinhard Kotucha (\pkgname{x86\_64-linux}), -Tim Arnold (\pkgname{hppa-hpux}), -Randy Au (\pkgname{amd64-freebsd}), -Edd Barrett (\pkgname{i386-openbsd}), -Karl Berry (\pkgname{i386-linux}), -Akira Kakuto (\pkgname{win32}), -Dick Koch (\pkgname{universal-darwin}), -Manfred Lotz (\pkgname{i386-freebsd}), -Norbert Preining (\pkgname{alpha-linux}), -Arthur Reutenauer (\pkgname{sparc-linux}), -Thomas Schmitz (\pkgname{powerpc-linux}), -Apostolos Syropoulos (\pkgname{i386-solaris}), -Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-solaris}), -Olaf Weber (\pkgname{mips-irix}). -Informacje na temat procesu budowy \TL{} mo¿na znale¼æ na stonie: -\url{http://tug.org/texlive/build.html}. - -Aktualizacje i~t³umaczenia dokumentacji wykonali: -Siep Kroonenberg i~Karl Berry (angielski), -Daniel Flipo (francuski), -Klaus H\"oppner (niemiecki), -Petr Sojka i~Jan Busa (czeski\slash s³owacki), -Boris Veytsman (rosyjski), -Staszek Wawrykiewicz (polski). -Na stronie \url{http://tug.org/texlive/doc.html} bêd± umieszczane ewentualne -aktualizacje tej dokumentacji. - -Oczywi¶cie, najwa¿niejsze podziêkowania nale¿± siê Donaldowi Knuthowi -za stworzenie systemu \TeX{} i~ofiarowanie go nam wszystkim. - -%%% -\section{Historia} -\label{sec:history} - -\subsection{Poprzednie wersje} - -Dystrybucja \TL{} jest wspólnym przedsiêwziêciem -grup U¿ytkowników Systemu \TeX{} z Niemiec, Holandii, Wielkiej -Brytanii, Francji, Czech, S³owacji, Polski, Indii i~Rosji oraz grupy -miêdzynarodowej TUG (\emph{\TeX{} Users Group}). -Dyskusje nad projektem rozpoczê³y siê pod koniec 1993 roku, kiedy holenderska -Grupa U¿ytkowników \TeX-a rozpoczê³a prace nad swoim -4All\TeX{} \CD{} dla u¿ytkowników \acro{MS-DOS}. W~tym te¿ -czasie pojawi³y siê nadzieje na opracowanie jednego \CD{} dla -wszystkich systemów. -Projekt ten by³ wprawdzie zbyt ambitny, zrodzi³ jednak nie tylko bardzo -popularny i~uwieñczony du¿ym powodzeniem projekt 4All\TeX{} \CD{}, -lecz równie¿ spowodowa³ powstanie Grupy Roboczej TUG ds. Standardu Katalogów -\TeX-owych (\emph{\TeX{} Directory Structure}), okre¶laj±cego, w~jaki -sposób tworzyæ zgodne i~³atwe do zarz±dzania zestawy pakietów \TeX-owych. -Koñcowy raport \TDS{} zosta³ opublikowany w~grudniowym numerze -\textsl{TUGboat}-a, i~jasnym siê sta³o, ¿e -jednym z~oczekiwanych wyników wprowadzenia tego standardu mog³aby -byæ modelowa struktura na p³ytce \CD. -Wydana wówczas p³ytka \CD{} by³a bezpo¶rednim rezultatem rozwa¿añ i~zaleceñ -Grupy Roboczej ds. \TDS. -Jasne tak¿e by³o, ¿e sukces 4All\TeX{} \CD{} pokaza³, ¿e -u¿ytkownicy Unixa tak¿e wiele by zyskali, mog±c korzystaæ -z~podobnie ³atwego w~instalacji/pielêgnacji i~u¿ytkowaniu systemu. -By³o to jednym z~celów projektu \TL. - -Projekt przygotowania p³ytki \CD, opartej na standardzie \TDS i~zorientowanej -na systemy uniksowe, rozpocz±³ siê jesieni± 1995 roku. Szybko -zdecydowali¶my siê na wykorzystanie \teTeX-a autorstwa Thomasa Essera, poniewa¿ -dzia³a³ na wielu platformach i~zosta³ zaprojektowany z~my¶l± -o~przeno¶no¶ci pomiêdzy ró¿nymi systemami plików. Thomas zgodzi³ siê pomóc -i~prace rozpoczê³y siê na dobre na pocz±tku 1996 roku. Pierwsze wydanie -ukaza³o siê w~maju 1996 roku. Na pocz±tku 1997 roku Karl Berry udostêpni³ -now±, istotnie zmienion± wersjê swojego pakietu \Webc, zawieraj±c± prawie -wszystkie funkcje wprowadzone do \teTeX-a przez Thomasa Essera. W~zwi±zku -z~tym zdecydowali¶my siê oprzeæ drugie wydanie \CD{} na standardowej -bibliotece \Webc, z~dodaniem skryptu \texttt{texconfig} z~pakietu \teTeX. -Trzecie wydanie \CD{} by³o oparte na \Webc{} wersji 7.2, przygotowanej przez -Olafa Webera. W~tym samym czasie zosta³a przygotowana nowa wersja \teTeX-a -i~\TL{} udostêpnia³ prawie wszystkie jego nowe funkcje. -Czwarta edycja by³a przygotowana podobnie, -z~u¿yciem nowej wersji te\TeX-a i~nowej wersji \Webc{} (7.3). -Wtedy to te¿ zapocz±tkowano kompletn± dystrybucjê dla Windows. - -Edycja pi±ta (marzec 2000) zawiera³a wiele poprawek i~uzupe³nieñ; -zaktualizowano setki pakietów. Szczegó³ow± zawarto¶æ pakietów -zapisano w~plikach XML. -G³ówn± zmian± w~\TeX\ Live~5 by³o usuniêcie programów, które nie mia³y -statusu {\it public domain}. Zawarto¶æ ca³ej p³ytki powinna odpowiadaæ ustaleniom -Debian Free Software Guidelines (\url{http://www.debian.org/intro/free}). -Do³o¿yli¶my wszelkich starañ, aby sprawdziæ warunki licencyjne pakietów, -nadal jednak bardzo prosimy o~zg³aszanie zauwa¿onych pomy³ek. - -Szósta edycja (lipiec 2001) zawiera³a aktualizacje ca³ego materia³u. G³ówn± -zmian± by³o wprowadzenie nowej koncepcji programów instalacyjnych -- u¿ytkownik -mia³ odt±d mo¿liwo¶æ dok³adniejszego wyboru potrzebnych zestawów i~pakietów. -Zestawy dotycz±ce obs³ugi poszczególnych jêzyków zosta³y ca³kowicie -zreorganizowane, dziêki czemu wybór jednego z~nich nie tylko instalowa³ -potrzebne makra i~fonty, ale te¿ przygotowywa³ odpowiedni plik -\texttt{language.dat}. - -\TL~7 (rok 2002) zawiera³ po raz pierwszy oprogramowanie dla \MacOSX{} -i -- jak zwykle -- aktualizacjê wszelkich programów i~pakietów. -Wa¿nym zadaniem, które wykonano, by³o ujednolicenie plików ¼ród³owych -programów z~dystrybucj± te\TeX. W~programach instalacyjnych wprowadzono -mo¿liwo¶æ wyboru bardziej ogólnych, predefiniowanych zestawów pakietów -(m.in. dla u¿ytkowników francuskojêzycznych oraz polskich). Nowo¶ci± -by³o tak¿e wprowadzenie procedury aktualizacji map fontowych dla Dvips -i~PDFTeX podczas instalacji oraz doinstalowywania pakietów fontowych. - -W~2003~r., wraz z~nap³ywem aktualizacji i~dodatkowych nowych pakietów, -okaza³o siê, ¿e \TL{} nie mie¶ci siê na pojedynczym \CD. -Zmuszeni byli¶my podzieliæ \TL{} na trzy dystrybucje, które wydano -na \DVD{} i~dwóch p³ytkach \CD. Ponadto: - -\begin{itemize*} -\item na ¿yczenie ,,\LaTeX{} team'' zmieniono standardowe u¿ycie - programów \cmdname{latex} i~\cmdname{pdflatex}~-- by korzysta³y - one z~\eTeX{} (patrz str.~\pageref{text:etex}); -\item za³±czono nowe fonty obwiedniowe Latin Modern, które zastêpuj± - m.in. fonty EC (zawieraj±c komplet znaków europejskich), szczególnie - do tworzenia poprawnych plików PDF; -\item usuniêto binaria dla platformy Alpha \acro{OSF} (poprzednio - usuniêto tak¿e binaria dla \acro{HPUX}), niestety nie uda³o siê znale¼æ - osób chêtnych do wykonania kompilacji; -\item zmieniono instalacjê w~systemach Windows, wprowadzaj±c po raz pierwszy - zintegrowane ¶rodowisko pracy, oparte na edytorze XEmacs; -\item potrzebne programy pomocnicze dla Windows (Perl, Ghost\-script, - Image\-Magick, Ispell) instalowano w~strukturze katalogów - instalacji \TL; -\item mapy fontowe, z~których korzystaj± programy \cmdname{dvips}, - \cmdname{dvipdfm} oraz \cmdname{pdftex}, generowano odt±d w~katalogu - \dirname{texmf/fonts/map}; -\item \TeX{}, \MF{} oraz \MP{} domy¶lnie pozwala³y wypisywaæ komunikaty - na ekranie i~w~pliku .log, a~tak¿e w~operacjach \verb|\write| w~ich - reprezentacji 8-bitowej, zamiast tradycyjnej notacji \verb|^^|; - w~\TL{}~7 eksperymentalnie wprowadzono zale¿no¶æ przekodowania - wyj¶cia programów od systemowej strony kodowej, potem ten pomys³ - zarzucono; -\item znacznie zmieniono niniejsz± dokumentacjê; -\item wreszcie, poniewa¿ numery wersji kolejnych edycji mog³y wprowadzaæ - w~b³±d, postanowiono identyfikowaæ edycje \TL{} zgodnie z~rokiem - wydania. -\end{itemize*} - -\subsection{Edycja 2004} - -Jak w~ka¿dej kolejnej wersji, w~2004 roku uaktualniono wiele pakietów -i~programów. Poni¿ej wymieniamy najbardziej istotne zmiany. - -\begin{itemize} -\item Gdy mieli¶my ju¿ lokalnie zainstalowane fonty, które korzysta³y -z~w³asnych plików \filename{.map} i/lub \filename{.enc}, \emph{nale¿a³o} -przenie¶æ te pliki w~nowe miejsce w~strukturze \filename{texmf/}. - -Pliki \filename{.map} (map fontowych) s± odt±d wyszukiwane w~podkatalogach -\dirname{fonts/map} (w~ka¿dym drzewie \filename{texmf}), zgodnie ze ¶cie¿k± -okre¶lon± przez zmienn± \envname{TEXFONTMAPS}. Analogicznie, pliki -\filename{.enc} (przekodowañ fontów) s± odt±d wyszukiwane w~podkatalogach -\dirname{fonts/enc}, zgodnie ze ¶cie¿k± okre¶lon± przez zmienn± -\envname{ENCFONTS}. O~niew³a¶ciwie umieszczonych plikach tego typu -zostaniemy ostrze¿eni podczas uruchomienia programu \cmdname{updmap}. -Zmiany te wprowadzono w~celu uporz±dkowania struktury katalogów: wszystkie -pliki dotycz±ce fontów znajduj± siê odt±d w~ramach jednego podkatalogu -\dirname{fonts/}. - -Metody radzenia sobie z~sytuacjami zwi±zanymi z~przej¶ciem na nowy uk³ad -katalogów omawia³ artyku³ \url{http://tug.org/texlive/mapenc.html}. - -\item Do \TK\ \DVD{} dodano now± dystrybucjê dla Windows o~nazwie -pro\TeX{}t (opart± na \MIKTEX-u). By³a ona dostêpna tak¿e na odrêbnym \CD. -Choæ pro\TeX{}t nie bazuje na implementacji Web2C, stosuje uk³ad katalogów -zgodny z~\TDS (patrz czê¶æ~\ref{sec:struct-tl} na -str.~\pageref{sec:struct-tl}). - -\item W ramach \TL{} dotychczasowe pojedyncze drzewo katalogów -\dirname{texmf} zosta³o rozdzielone na trzy mniejsze: \dirname{texmf}, -\dirname{texmf-dist} i~\dirname{texmf-doc} (patrz -czê¶æ~\ref{sec:tld}, str.~\pageref{sec:tld}) oraz pliki \filename{README} -w~ka¿dym z~tych katalogów). - -\item Wszystkie pliki makr wczytywane przez \TeX-a zosta³y -umieszczone wy³±cznie w~podkalogu \dirname{tex} w~ramach -\dirname{texmf*}. Tym samym usuniêto zbêdne katalogi -\dirname{etex}, \dirname{pdftex}, \dirname{pdfetex} itp. i~uproszczono -metody wyszukiwania plików. - -\item Pomocnicze skrypty wykonywalne, niezale¿ne od platformy -i~zwykle uruchamiane w~sposób automatyczny, by³y odt±d -umieszczone w~nowym podkatalogu \dirname{scripts} w~ramach \dirname{texmf*}. -Znajdowane s± poleceniem \verb|kpsewhich -format=texmfscripts|. -Programy korzystaj±ce z tych skryptów mog³y wymagaæ modyfikacji. -Patrz \CDref{texmf-doc/doc/english/tds/tds.html\#Scripts} -{\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}. - -\item Prawie wszystkie formaty traktuj± od tego wydania wiêkszo¶æ znaków jako -jawnie ,,wy¶wietlalne'' (\emph{printable}), nie za¶, jak by³o dotychczas, -konwertowane na \TeX-ow± notacjê \verb|^^|. By³o to mo¿liwe dziêki domy¶lnemu -wczytywaniu tablicy przekodowañ \filename{cp227.tcx}. Dok³adniej, znaki -o~kodach 32--256, HT, VT oraz FF zosta³y potraktowane dos³ownie podczas -wy¶wietlania komunikatów. Wyj±tkiem jest plain \TeX{} (tylko znaki z~zakresu -32--127 s± nie zmieniane), \ConTeXt{} (znaki z zakresu 0--255) oraz formaty -bazuj±ce na Omedze. Podobna domy¶lna w³a¶ciwo¶æ wystêpowa³a w~\TL\,2003, ale -w~tej edycji zosta³a zaimplementowana w~bardziej elegancki sposób -i~z~wiêkszymi mo¿liwo¶ciami indywidualnego dostosowania (patrz -\CDref{texmf/doc/web2c/web2c.html\#TCX-files} {\texttt{texmf/doc/web2c/web2c. -tml\#TCX-files}}. (Warto wspomnieæ, ¿e wczytuj±c Unicode, \TeX{} mo¿e -w~komunikatach b³êdów pokazywaæ niekompletne sekwencje znaków, poniewa¿ -zosta³ zaprojektowany ,,bajtowo''.) - %%! hmmm, ca³y akapit by o strumieniach we-wy? - -\item Program \textsf{pdfetex} zosta³ domy¶ln± ,,maszyn±'' dla -wiêkszo¶ci formatów (nie dotyczy to samego Plain \textsf{tex}). -Domy¶lnie, gdy uruchamiamy polecenie \textsf{latex}, \textsf{mex} -itp., generowane s± pliki \acro{DVI}. Mo¿liwe jest jednak wykorzystanie -w~\LaTeX, \ConTeXt{} itp. m.in. w³a¶ciwo¶ci mikrotypograficznych -zaimplementowanych w~\textsf{pdftex}, a~tak¿e rozszerzonych cech \eTeX-a -(\OnCD{texmf-dist/doc/etex/base/}). - -Oznacza to tak¿e, co warto podkre¶liæ, ¿e \emph{zalecane} jest odt±d u¿ycie -pakietu \pkgname{ifpdf} (który dzia³a zarówno z~plain, jak i~\LaTeX) -lub analogicznych makr. Zwyk³e sprawdzanie czy zdefiniowano \cs{pdfoutput} -b±d¼ kilka innych poleceñ pierwotnych mo¿e nie wystarczyæ do rozstrzygniêcia -czy nie jest generowany plik \acro{PDF}. W~2004 roku podjêli¶my -wysi³ek by zachowaæ, najlepiej jak to mo¿liwe, kompatybilno¶æ -z~dotychczasowymi przyzwyczajeniami u¿ytkowników. Brano wówczas pod uwagê, -¿e \cs{pdfoutput} mo¿e byæ zdefiniowany nawet wtedy, -gdy generowany jest plik \acro{DVI}. - -\item pdf\TeX\ (\url{http://pdftex.org}) zyska³ wówczas wiele nowych -cech: - - \begin{itemize*} - \item \cs{pdfmapfile} i~\cs{pdfmapline} pozwalaj± okre¶liæ - z~poziomu dokumentu u¿yte mapy fontowe, a~tak¿e pojedyncze - dodatkowe wpisy w~tych mapach. - - \item mikrotypograficzne operacje z~fontami s± ³atwiejsze w u¿yciu;\\ - \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} - - \item wszystkie parametry pracy pdf\TeX-a, dotychczas okre¶lane - w~specjalnym pliku konfiguracyjnym \filename{pdftex.cfg}, musz± byæ - odt±d ustawiane poleceniami wbudowanymi, jak w~pliku - \filename{pdftexconfig.tex}; plik \filename{pdftex.cfg} - nie jest ju¿ w~ogóle wykorzystywany. Po zmianie \filename{pdftexconfig.tex} - nale¿a³o na nowo wygenerowaæ pliki formatów (wci±¿ jednak u¿ytkownik mia³ - pe³n± swobodê okre¶lania parametrów w~redagowanym dokumencie); - - \item wiêcej informacji zawarto w~podrêczniku pdf\TeX-a: - \OnCD{texmf-dist/doc/pdftex/manual/pdftex-a.pdf}. - - \end{itemize*} - -\item Polecenie \cs{input} w~programach \cmdname{tex}, - \cmdname{mf} oraz \cmdname{mpost} akceptowa³o odt±d nazwy - plików ograniczone podwójnymi apostrofami, zawieraj±ce spacje i~inne - znaki, np.: -\begin{verbatim} -\input "nazwa_pliku ze spacjami" % plain -\input{"nazwa_pliku ze spacjami"} % latex -\end{verbatim} -Wiêcej informacji zawarto w~podrêczniku Web2C: \OnCD{texmf/doc/web2c}. - -\item \texttt{-output-directory} -- nowa opcja programów \cmdname{tex}, - \cmdname{mf} oraz \cmdname{mpost} -- pozwala³a na zapisanie wyniku pracy - w~wyspecyfikowanym katalogu (np. mo¿na uruchomiæ program \texttt{tex} - z~plikiem znajduj±cym siê na dysku tylko do odczytu, za¶ wynik zapisaæ - na dysku pozwalaj±cym na~to); - -\item Rozszerzenie enc\TeX\ zosta³o szczê¶liwie w³±czone do Web2C. - Aby uaktywniæ to rozszerzenie, nale¿a³o podczas generowania formatu - u¿yæ opcji \optname{-enc}. Ogólnie mówi±c, enc\TeX\ obs³uguje - przekodowanie wej¶cia i~wyj¶cia, w³±czaj±c tak¿e Unicode (\acro{UTF}-8) - (patrz \OnCD{texmf-dist/doc/generic/enctex/} oraz - \url{http://www.olsak.net/enctex.html}). - -\item Udostêpniono nowy program Aleph, który ³±czy³ cechy \eTeX\ i~\OMEGA. - Skromna dokumentacja jest dostêpna na \OnCD{texmf-dist/doc/aleph/base} - oraz \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph}. - Format oparty na \LaTeX-u dla programu Aleph nazwano \textsf{lamed}. - -\item Dystrybucja \LaTeX-a zosta³a po raz pierwszy zaopatrzona w~now± - licencjê \acro{LPPL}, odt±d w~pe³ni zgodn± i~aprobowan± przez zalecenia - okre¶lone w~licencji Debiana. O~nowo¶ciach i~uaktualnieniach mo¿na siê - dowiedzieæ przegl±daj±c pliki \filename{ltnews} - w~\OnCD{texmf-dist/doc/latex/base}. - -\item Do³±czono tak¿e program \cmdname{dvipng} konwertuj±cy pliki \acro{DVI} -do formatu graficznego \acro{PNG} (\OnCD{texmf/doc/man/man1/dvipng.1}). - -\item W~porozumieniu i~z~pomoc± autora, Claudio Beccariego, ograniczono - pakiet \pkgname{cbgreek} do zestawu fontów rozs±dnego rozmiaru. Usuniêto - sporadycznie u¿ywane fonty konturowe i~s³u¿±ce do prezentacji. Pe³en - zestaw by³ oczywi¶cie nadal dostêpny z~serwerów \acro{CTAN} - (\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). - -\item Usuniêto program \cmdname{oxdvi}; jego funkcje przej±³ - \cmdname{xdvi}. - -\item Programy z~przedrostkiem \cmdname{ini} oraz \cmdname{vir} - (np. \cmdname{initex}), które zwykle by³y dowi±zaniami do programów - \cmdname{tex}, \cmdname{mf} i~\cmdname{mpost}, nie by³y od tej pory dostêpne - -- w~zupe³no¶ci wystarcza u¿ycie w~wierszu poleceñ opcji \optname{-ini}. - -\item Dystrybucja nie zawiera³a binariów dla platformy \textsf{i386-openbsd} - (g³ównie z~powodu braku chêtnych do wykonania kompilacji). - -\item W~systemie \textsf{sparc-solaris} nale¿a³o ustawiæ zmienn± systemow± - \envname{LD\_LIBRARY\_PATH}, aby uruchomiæ programy \pkgname{t1utils}. - Binaria by³y kompilowane w~C++, ale w~tym systemie brakowa³o standardowego - po³o¿enia bibliotek uruchomieniowych. Wiedziano o~tym ju¿ wcze¶niej, - nie by³o to jednak dotychczas udokumentowane. Z~kolei dla systemu - \textsf{mips-irix} wymagana by³a obecno¶æ bibliotek \acro{MIPS}pro 7.4. - -\end{itemize} - -\subsection{Edycja 2005} - -Kolejna edycja przynios³a, jak zwykle, mnóstwo aktualizacji pakietów -i~programów. Struktura dystrybucji ustabilizowa³a siê, niemniej -pojawi³o siê nieco zmian w~konfiguracji: - -\begin{itemize} - -\item Wprowadzono nowe skrypty \cmdname{texconfig-sys}, \cmdname{updmap-sys} - i~\cmdname{fmtutil-sys}, których zadaniem jest modyfikowanie plików - konfiguracyjnych w~g³ównych drzewach katalogów systemu. Dotychczasowe - skrypty \cmdname{texconfig}, \cmdname{updmap} i~\cmdname{fmtutil} - modyfikuj± odt±d pliki u¿ytkownika w~katalogu \dirname{$HOME/.texlive2005}. - %(Patrz czê¶æ~\ref{sec:texconfig}, str.~\pageref{sec:texconfig}). - -\item Dodano nowe zmienne ¶rodowiskowe \envname{TEXMFCONFIG} - i~\envname{TEXMFSYSCONFIG}, które wskazuj± po³o¿enie drzew katalogów - z~plikami konfiguracyjnymi, odpowiednio: u¿ytkownika i~systemu. Tak wiêc - mog³o okazaæ siê koniecznym przeniesienie w³asnych wersji - \filename{fmtutil.cnf} i~\filename{updmap.cfg} w~odpowiednie miejsca. - Inn± mo¿liwo¶ci± by³o przedefiniowanie \envname{TEXMFCONFIG} lub - \envname{TEXMFSYSCONFIG} w~pliku \file{texmf.cnf}. W~ka¿dym z~przypadków - po³o¿enie tych plików i~przypisania - \envname{TEXMFCONFIG} i~\envname{TEXMFSYSCONFIG} musz± byæ zgodne. - (Patrz czê¶æ~\ref{sec:texmftrees}, str.~\pageref{sec:texmftrees}.) - -\item W~wydaniu z~poprzedniego roku podczas tworzenia wynikowego pliku - DVI \verb|\pdfoutput| i~podobne polecenia pozostawa³y niezdefiniowane, mimo - ¿e u¿ywany by³ program \cmdname{pdfetex}. Zgodnie z~obietnic±, - w~2005 roku zarzucono to rozwi±zanie (jego celem by³o zapewnienie - kompatybilno¶ci). Z~tego powodu u¿ytkownik by³ zmuszony zmieniæ te dokumenty, - które u¿ywa³y \verb|\ifx\pdfoutput\undefined| do sprawdzania, czy plik - wynikowy ma byæ w~formacie PDF. Zamiast tego nale¿a³o zastosowaæ pakiet - \pkgname{ifpdf.sty}, który dzia³a zarówno z~plain \TeX-em jak i~\LaTeX-em, - albo zapo¿yczyæ zastosowane w~nim rozwi±zania. - -\item W~wydaniu z~2004 roku zmieniono wiêkszo¶æ formatów tak, by - na wyj¶ciu 8-bitowe znaki by³y reprezentowane przez same siebie (por. - poprzednia czê¶æ). Nowy plik TCX o~nazwie \filename{empty.tcx} pozwala³ - w~³atwy sposób uzyskaæ w~razie potrzeby oryginaln± notacjê (\verb|^^|), - np.: - -\begin{verbatim} -latex --translate-file=empty.tcx twojplik.tex -\end{verbatim} - -\item Do³±czono nowy program \cmdname{dvipdfmx}, s³u¿±cy do konwersji DVI - do PDF. Program jest aktywnie pielêgnowan± wersj± programu - \cmdname{dvipdfm}, który wci±¿ jest dostêpny, ale nie jest ju¿ jednak - polecany. - -\item Nowe programy \cmdname{pdfopen} i~\cmdname{pdfclose} pozwala³y na - prze³adowanie plików PDF w~Adobe Acrobat Reader, bez konieczno¶ci ponownego - uruchamiania programu. (Inne przegl±darki formatu PDF, jak \cmdname{xpdf}, - \cmdname{gv} i~\cmdname{gsview}, nigdy na tê przypad³o¶æ nie cierpia³y.) - -\item Dla spójno¶ci, zmienne \envname{HOMETEXMF} i~\envname{VARTEXMF} zosta³y - przemianowane odpowiednio na \envname{TEXMFHOME} i~\envname{TEXMFSYSVAR}. - Zachowano zmienn± \envname{TEXMFVAR}, przeznaczon± domy¶lnie dla - u¿ytkownika. Patrz te¿ punkt pierwszy, powy¿ej. - -\end{itemize} - -\subsection{Edycja 2007} - -Najwiêksz± nowo¶ci± edycji lat 2006 i~2007 by³ Xe\TeX{}, -w~postaci programów \texttt{xetex} i~\texttt{xelatex}; patrz -\OnCD{texmf-dist/doc/xetex/XeTeX-reference.pdf} lub -\url{http://scripts.sil.org/xetex}. - -W istotny sposób zosta³ zaktualizowany MetaPost, zaplanowano tak¿e jego -dalszy rozwój (\url{http://tug.org/metapost/articles}); to samo dotyczy -pdf\TeX-a (\url{http://tug.org/applications/pdftex}). - -Pliki formatów (pdf)TeX-a (\filename{.fmt}) oraz analogiczne dla MetaPosta -i~Meta\-Fonta s± od tej edycji zapisywane w~podkatalogach -\dirname{texmf/web2c}, choæ sam ten katalog jest nadal przeszukiwany. -Podkatalogi te maj± nazwê zgodn± z~zastosowanym podczas generowania -,,silnikiem'', np. \filename{tex}, \filename{pdftex} lub \filename{xetex}. -Zmiana ta nie powinna byæ zauwa¿alna w~typowym u¿yciu. - -Program \texttt{tex} (plain) od tej edycji ju¿ nie analizowa³ pierwszego -wiersza rozpoczynaj±cego siê znakami \texttt{\%\&}, aby ustaliæ jaki ma -wczytaæ format. Pozosta³ zatem czysty, Knuthowy \TeX. \LaTeX\ i~wszystkie -pozosta³e formaty nadal analizuj± pierwszy wiersz z~\texttt{\%\&}. - -Oczywi¶cie, jak zwykle, w~okresie od poprzedniego wydania opracowano setki -innych aktualizacji pakietów i programów. Kolejne aktualizacje mo¿na znale¼æ -tradycyjnie na \acro{CTAN} (\url{http://www.ctan.org}). - -Drzewo ¼ród³owe \TL{} jest odt±d przechowywane w~Subversion. Przegl±danie -umo¿liwia standardowy interfejs www, a~jego adres zamieszczono na stronie -\url{http://tug.org.pl/texlive}. -Mimo i¿ nie widaæ efektów tej zmiany w koñcowej dystrybucji, mamy nadziejê, -¿e w~nadchodz±cych latach bêdzie to stabilne repozytorium oprogramowania -dla rozwoju \TL{}. - -W~maju 2006~r. Thomas Esser og³osi³, ¿e zaprzestaje aktualizowania -dystrybucji te\TeX{} (\url{http://tug.org/tetex}). Spowodowa³o to znaczny -wzrost zainteresowanie \TL, szczególnie w¶ród dystrybutorów -\acro{GNU}/Linuksa. (W~\TL{} zdefiniowano w przybli¿eniu równowa¿ny, nowy -schemat instalacyjny pod nazw± \texttt{tetex}.) Mamy nadziejê, ¿e -w~przysz³o¶ci doprowadzi to do takich ulepszeñ w~otoczeniu \TeX-owym, na -których skorzystaj± wszyscy. - -\medskip \noindent - %%!Koñcowa uwaga, dotycz±ca przesz³o¶ci: - Wszystkie wydania \TL{}, wraz z~dodatkowymi materia³ami (np. ok³adkami -p³ytek), s± dostêpne na stronie: -\url{ftp://tug.org/historic/systems/texlive}. - -\subsection{Wydanie obecne} -\label{sec:tlcurrent} - -W 2008 roku ca³a infrastruktura \TL{} zosta³a przeprojektowana -i~przeprogramowana. Informacja dotycz±ca instalacji jest przechowywana -obecnie w~zwyk³ym pliku tekstowym \filename{tlpkg/texlive.tlpdb}. - -Po zainstalowaniu \TL{} wreszcie jest mo¿liwa jego aktualizacja z~internetu, -podobnie jak od paru lat umo¿liwia to dystrybucja MiK\TeX. Zamierzamy -regularnie aktualizowaæ pakiety, w~miarê jak bêd± siê pojawiaæ na serwerach -\CTAN. - -W~tym wydaniu pojawi³ siê nowy ,,silnik'', Lua\TeX\ -(\url{http://luatex.org}). Prócz nowych, elastycznych mo¿liwo¶ci -dotycz±cych sk³adu, udostêpnia on doskona³y jêzyk skryptowy do -zastosowania zarówno w~dokumentach \TeX-owych, jak i~poza nimi. - -Obs³uga dla Windows i~platform opartych na Unix zosta³a obecnie znacznie -bardziej zunifikowana. W~szczególno¶ci wiêkszo¶æ skryptów w~Perlu i~Lua -dostêpna jest teraz tak¿e dla Windows (zastosowano ,,wewnêtrzny'' Perl, -dostarczany wraz z~\TL). - -Pojawi³ siê nowy skrypt \cmdname{tlmgr} (patrz czê¶æ~\ref{sec:tlmgr}), który -staje siê g³ównym narzêdziem do zarz±dzania \TL{} po jego instalacji. -Umo¿liwia on aktualizacjê pakietów wraz z~niezbêdnymi wtedy czynno¶ciami, -jak regenerowanie formatów, aktualizacja map fontowych itp. - -Wraz z pojawieniem siê \cmdname{tlmgr} niektóre funkcje \cmdname{texconfig} -zosta³y zablokowane (edycja plików konfiguracyjnych formatów i~wzorców -przenoszenia). - -Program \cmdname{xindy} do tworzenia skorowidzów -(\url{http://xindy.sourceforge.net/}) jest obecnie dostêpny dla wiêkszo¶ci -platform. - -Narzêdzie \cmdname{kpsewhich} mo¿e obecnie raportowaæ wszystkie wyniki -przeszukiwania danego pliku (parametr \optname{--all}), jak równie¿ -ograniczyæ wyszukiwanie do jednego katalogu (parametr \optname{--subdir}). - -Program \cmdname{dvipdfmx} posiada obecnie funkcjê \cmdname{extractbb} -uzyskania informacji o~prostok±cie ograniczaj±cym (\textit{bounding box}); -jest to jedna z~ostatnich cech przejêtych od dawniej u¿ywanego programu -\cmdname{dvipdfm} (który jest nadal dostêpny). - -Usuniêto aliasy fontów \filename{Times-Roman}, \filename{Helvetica}, itd. -Ró¿ne pakiety korzysta³y z~nich w~nieoczekiwany sposób (np. spodziewaj±c -siê, ¿e fonty te bêd± mia³y ró¿ne kodowanie). Nie ma obecnie dobrego sposobu -na rozwi±zanie tych sprzeczno¶ci. - -Usuniêto format \pkgname{platex}, by unikn±æ konfliktu nazwy z~u¿ywanym od -wielu lat japoñskim pakietem \pkgname{platex}; pakiet \pkgname{polski} (czyli -dawny \pkgname{platex}) jest obecnie wystarczaj±cym sposobem na polonizacjê -dla \LaTeX-a. - -Usuniêto pliki \filename{.pool}, które s± obecnie wkompilowane w~programy, -co u³atwia ich aktualizacjê. - -Do tego wydania w³±czono tak¿e ostatnie zmiany dokonane przez -Donalda Knutha (tzw. \textit{\TeX\ tuneup of 2008}); patrz: -\url{http://tug.org/TUGboat/Articles/tb29-2/tb92knut.pdf}. - -\subsection{Przysz³e wersje} - -\emph{Niniejsza dystrybucja nie jest doskona³a!} Planujemy kontynuowaæ -wydawanie nowych wersji i~chcieliby¶my, ¿eby zawiera³y one jeszcze wiêcej -pomocnej dokumentacji, wiêcej programów u¿ytkowych, lepsze programy -instalacyjne oraz stale ulepszany i~poprawiany katalog makr -i~fontów. Zadanie to jest wykonywane przez ciê¿ko pracuj±cych ochotników, -po¶wiêcaj±cych na to wiele swojego wolnego czasu. Wiele jeszcze zosta³o do -zrobienia. Je¿eli mo¿esz pomóc, nie zastanawiaj siê i~przy³±cz siê do nas. -Patrz: \url{http://tug.org/texlive/contribute.html}. - -Prosimy o~przesy³anie poprawek, sugestii i~uzupe³nieñ oraz deklaracji -pomocy w~opracowywaniu kolejnych edycji pod adres: -%\begin{quote} -\email{tex-live@tug.org} -%\url{http://tug.org/texlive} -%\end{quote} - -%Uaktualnienia, og³oszenia i~wskazówki bêd± dostêpne na stronie -%\url{http://tug.org/texlive.html}. - -\end{document} - diff --git a/Master/texmf-doc/source/texlive/texlive-ru/Makefile b/Master/texmf-doc/source/texlive/texlive-ru/Makefile deleted file mode 100644 index 93708128b74..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-ru/Makefile +++ /dev/null @@ -1,3 +0,0 @@ -include ../texlive-en/Makefile -doc = texlive-ru -lang = russian diff --git a/Master/texmf-doc/source/texlive/texlive-ru/live4ht.cfg b/Master/texmf-doc/source/texlive/texlive-ru/live4ht.cfg deleted file mode 100644 index 508ccca27c8..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-ru/live4ht.cfg +++ /dev/null @@ -1,47 +0,0 @@ -% tex4ht configuration file for the TeX Live documentation. -% Accumulated over many years. Public domain. -% -% html specifies the main output format. -% info for extra debugging info in the log files. - -% better approach is to have html in one piece (including footnotes). -% also the newest TeX4ht could produce UTF-8 output (-utf8 option) -\Preamble{charset=iso-8859-5,html,info,fn-in} - -% add extra stylesheet -\Configure{@HEAD}{\HCode{% -\Hnewline -\Hnewline -}} - -% or LaTeX complains it is missing. -\begin{document} - -\EndPreamble - -% simplify output for HTML. We leave TeX and LaTeX alone, since tex4ht -% actually does the lowered E (and raised A) in CSS. -\def\OMEGA{Omega} -\def\LaTeXe{LaTeX2e} -\def\eTeX{e-\TeX} -\def\acro#1{#1} -\def\MF{Metafont} -\def\BibTeX{BibTeX} -\def\warningbox{} -\def\endwarningbox{} - -\newif\ifhackliterals -\ifx\tldocenglish\undefined \else \hackliteralstrue \fi -\ifx\tldocrussian\undefined \else \hackliteralstrue \fi -\ifx\tldocgerman\undefined \else \hackliteralstrue \fi -% -\ifhackliterals - % these definitions cause "missing } inserted" at \end{tabularx} in - % French and Czech. don't know why. - % - % don't make these into links, as happens with \path. We only have a couple - % special characters that actually occur. - \def\dirname{\texttt\bgroup\catcode`\$=12 \catcode`\_=12 \finishliteral} - \def\finishliteral#1{#1\egroup} - \let\filename=\dirname -\fi diff --git a/Master/texmf-doc/source/texlive/texlive-ru/texlive-ru.tex b/Master/texmf-doc/source/texlive/texlive-ru/texlive-ru.tex deleted file mode 100644 index 9184449b75c..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-ru/texlive-ru.tex +++ /dev/null @@ -1,2998 +0,0 @@ -% $Id$ -% -%\def\Status{1} -\documentclass{article} -\let\tldocrussian=1 % for live4ht.cfg -\usepackage{tex-live} -\usepackage[koi8-r]{inputenc} -\usepackage[russian]{babel} -\newcommand\Unix{Unix} -\newcommand\Windows{Windows} -\usepackage{indentfirst, cmap} -\def\p.{ÓÔÒ.~}% -\renewcommand{\samp}[1]{<<\texttt{#1}>>} -% -\begin{document} - -\title{% - {\huge \textit{òÕËÏ×ÏÄÓÔ×Ï ÐÏÌØÚÏ×ÁÔÅÌÑ \protect\TL{}}\\\strut} - {\LARGE \textsf{\TL{} 2008}} -} - -\author{òÅÄÁËÔÏÒ: ëÁÒÌ âÅÒÒÉ\\[3mm] - \url{http://tug.org/texlive/}} -\date{éÀÌØ 2008} - -\maketitle - - -\begin{multicols}{2} -\tableofcontents -\listoftables -\end{multicols} - -\section{÷×ÅÄÅÎÉÅ} -\label{sec:intro} - -\subsection{\TeX\ Live É \TeX\ Collection} - - -÷ ÜÔÏÍ ÄÏËÕÍÅÎÔÅ ÏÐÉÓÁÎÙ ÏÓÎÏ×ÎÙÅ ×ÏÚÍÏÖÎÏÓÔÉ ÐÒÏÇÒÁÍÍÎÏÇÏ ÐÒÏÄÕËÔÁ -\TL{} "--- ÄÉÓÔÒÉÂÕÔÉ×Á \TeX{}Á É ÄÒÕÇÉÈ ÐÒÏÇÒÁÍÍ ÄÌÑ -\acro{GNU}/ìÉÎÕËÓÁ É ÄÒÕÇÉÈ àÎÉËÓÏ×, \MacOSX É (32-ÂÉÔÎÙÈ) Windows. - -\TL{} ÍÏÖÎÏ ÓËÁÞÁÔØ Ó éÎÔÅÒÎÅÔÁ, Á ÍÏÖÎÏ ÐÏÌÕÞÉÔØ ÎÁ \DVD{} <<\TK{}>>. üÔÉ -\DVD{} ÒÁÓÐÒÏÓÔÒÁÎÑÀÔÓÑ ÇÒÕÐÐÁÍÉ ÐÏÌØÚÏ×ÁÔÅÌÅÊ \TeX Á. ÷ ÒÁÚÄÅÌÅ -\ref{sec:tl-coll-dists} ËÒÁÔËÏ ÏÐÉÓÁÎÏ ÓÏÄÅÒÖÁÎÉÅ ÔÁËÏÇÏ \DVD{}. é -\TL{}, É \TK{} ÐÏÄÄÅÒÖÉ×ÁÀÔÓÑ ÇÒÕÐÐÁÍÉ ÐÏÌØÚÏ×ÁÔÅÌÅÊ \TeX Á. ÷ ÜÔÏÍ -ÄÏËÕÍÅÎÔÅ × ÏÓÎÏ×ÎÏÍ ÏÐÉÓÁÎ \TL{}. - -÷ \TL{} ×ËÌÀÞÅÎÙ ÐÒÏÇÒÁÍÍÙ \TeX{}, \LaTeXe{}, \ConTeXt, \MF, \MP, -\BibTeX{} É ÍÎÏÇÉÅ ÄÒÕÇÉÅ; ÏÂÛÉÒÎÁÑ ËÏÌÌÅËÃÉÑ ÍÁËÒÏÓÏ×, ÛÒÉÆÔÏ× É -ÄÏËÕÍÅÎÔÁÃÉÉ; Á ÔÁËÖÅ ÐÏÄÄÅÒÖËÁ ×£ÒÓÔËÉ ÎÁ ÍÎÏÇÉÈ ÑÚÙËÁÈ ÍÉÒÁ. - - -âÏÌÅÅ ÎÏ×ÙÅ ×ÅÒÓÉÉ ÐÁËÅÔÏ×, ×ËÌÀÞ£ÎÎÙÈ × ÄÉÓÔÒÉÂÕÔÉ×, ÍÏÖÎÏ ÎÁÊÔÉ × -ÁÒÈÉ×Å \acro{CTAN}, \url{http://www.ctan.org}. - -ëÒÁÔËÉÊ ÓÐÉÓÏË ÏÓÎÏ×ÎÙÈ ÉÚÍÅÎÅÎÉÊ × ÜÔÏÍ ÉÚÄÁÎÉÉ \TeXLive{} ÍÏÖÎÏ -ÎÁÊÔÉ × ÒÁÚÄÅÌÅ~\ref{sec:history}, \p.\pageref{sec:history}. - - -\subsection{ðÏÄÄÅÒÖÉ×ÁÅÍÙÅ ÏÐÅÒÁÃÉÏÎÎÙÅ ÓÉÓÔÅÍÙ} -\label{sec:os-support} - -÷ \TL{} ×ËÌÀÞÅÎÙ ÓËÏÍÐÉÌÉÒÏ×ÁÎÎÙÅ ÐÒÏÇÒÁÍÍÙ ÄÌÑ ÍÎÏÇÉÈ ÀÎÉËÓÏÐÏÄÏÂÎÙÈ -ÓÉÓÔÅÍ, ×ËÌÀÞÁÑ \MacOSX. éÓÈÏÄÎÙÊ ËÏÄ ÔÁËÖÅ ×ËÌÀÞÅÎ × ÄÉÓÔÒÉÂÕÔÉ×, -ÞÔÏ ÐÏÚ×ÏÌÑÅÔ ÕÓÔÁÎÏ×ÉÔØ \TL{} ÎÁ ÍÁÛÉÎÁÈ, ÄÌÑ ÁÒÈÉÔÅËÔÕÒ ËÏÔÏÒÙÈ ÍÙ ÎÅ -ÓÏÂÒÁÌÉ ÐÒÏÇÒÁÍÍÙ. - -þÔÏ ËÁÓÁÅÔÓÑ Windows: ÐÏÄÄÅÒÖÉ×ÁÀÔÓÑ ÔÏÌØËÏ ×ÅÒÓÉÉ Windows 2000 É -ÍÌÁÄÛÅ. íÙ ÐÒÅËÒÁÔÉÌÉ ÐÏÄÄÅÒÖÉ×ÁÔØ Windows 9\textit{x}, ME É NT. üÔÏ -ÐÏÚ×ÏÌÉÌÏ ÚÎÁÞÉÔÅÌØÎÏ ÓÏËÒÁÔÉÔØ ÚÁÔÒÁÔÙ ÔÒÕÄÁ ÎÁ ÜÔÕ ÐÌÁÔÆÏÒÍÕ. íÙ ÎÅ -ÓÏÂÒÁÌÉ 64-ÂÉÔÏ×ÙÅ ÐÒÏÇÒÁÍÍÙ ÄÌÑ Windows, ÎÏ 32-ÂÉÔÏ×ÙÅ ×ÁÒÉÁÎÔÙ -ÄÏÌÖÎÙ ÒÁÂÏÔÁÔØ ÎÁ 64-ÂÉÔÏ×ÙÈ ÓÉÓÔÅÍ. - -áÌØÔÅÒÎÁÔÉ×ÎÙÅ ×ÁÒÉÁÎÔÙ ÄÌÑ Windows É \MacOSX{} ÏÐÉÓÁÎÙ × -ÒÁÚÄÅÌÅ~\ref{sec:tl-coll-dists}. - -\subsection{ïÓÎÏ×Ù ÕÓÔÁÎÏ×ËÉ \protect\TL{}} -\label{sec:basic} - -\TL{} ÍÏÖÎÏ ÕÓÔÁÎÏ×ÉÔØ Ó \DVD{} ÉÌÉ Ó éÎÔÅÒÎÅÔÁ. ðÒÏÇÒÁÍÍÁ ÄÌÑ -ÕÓÔÁÎÏ×ËÉ Ó ÓÅÔÉ ÓÁÍÁ ÐÏ ÓÅÂÅ ÍÁÌÁ "--- ÏÎÁ ÓËÁÞÉ×ÁÅÔ ×ÓÅ ÎÕÖÎÏÅ Ó -éÎÔÅÒÎÅÔÁ. üÔÏ ÕÄÏÂÎÏ, ÅÓÌÉ ×ÁÍ ÎÕÖÎÁ ÔÏÌØËÏ ÞÁÓÔØ ÐÁËÅÔÏ× \TL{}. - -ðÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ Ó \DVD{} ÐÏÚ×ÏÌÑÅÔ ÕÓÔÁÎÏ×ÉÔØ \TL{} ÎÁ ÄÉÓË -ËÏÍÐØÀÔÅÒÁ, ÎÏ ÍÏÖÎÏ ÔÁËÖÅ ÚÁÐÕÓËÁÔØ \TL{} ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ Ó \DVD{} -(ÉÌÉ Ó ÏÂÒÁÚÁ \DVD{}, ÅÓÌÉ ×ÁÛÁ ÓÉÓÔÅÍÁ ÐÏÄÄÅÒÖÉ×ÁÅÔ ÍÏÎÔÉÒÏ×ÁÎÉÅ -ÏÂÒÁÚÁ ÄÉÓËÁ). - - -\noindent ÷Ó£ ÜÔÏ ÐÏÄÒÏÂÎÏ ÏÐÉÓÁÎÏ × ÓÌÅÄÕÀÝÉÈ ÒÁÚÄÅÌÁÈ. ÷ËÒÁÔÃÅ: -\begin{itemize*} -\item óËÒÉÐÔ ÄÌÑ ÕÓÔÁÎÏ×ËÉ ÓÉÓÔÅÍÙ ÎÁÚÙ×ÁÅÔÓÑ \texttt{install-tl}. ïÎ - ÍÏÖÅÔ ÒÁÂÏÔÁÔØ × Ä×ÕÈ ×ÁÒÉÁÎÔÁÈ: ÇÒÁÆÉÞÅÓËÏÍ (ÒÅÖÉÍ ÐÏ ÕÍÏÌÞÁÎÉÀ ÄÌÑ - Windows) ÉÌÉ × ÔÅËÓÔÏ×ÏÍ (ÒÅÖÉÍ ÐÏ ÕÍÏÌÞÁÎÉÀ ÄÌÑ ÏÓÔÁÌØÎÙÈ - ÁÒÈÉÔÅËÔÕÒ). îÕÖÎÙÊ ×ÁÒÉÁÎÔ ÍÏÖÎÏ ×ÙÂÒÁÔØ ÐÒÉ ÐÏÍÏÝÉ ÏÐÃÉÊ - \code{-gui} É \code{-no-gui}. - -\item óÒÅÄÉ ÕÓÔÁÎÏ×ÌÅÎÎÙÈ ÐÒÏÇÒÁÍÍ ÅÓÔØ <<íÅÎÅÄÖÅÒ \TL{}>>, - \prog{tlmgr}. ëÁË É ÐÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ, ÏÎ ÍÏÖÅÔ ÒÁÂÏÔÁÔØ ËÁË × - ÇÒÁÆÉÞÅÓËÏÍ, ÔÁË É × ÔÅËÓÔÏ×ÏÍ ÒÅÖÉÍÁÈ. üÔÁ ÐÒÏÇÒÁÍÍÁ ÐÏÚ×ÏÌÑÅÔ - ÕÓÔÁÎÁ×ÌÉ×ÁÔØ É ÕÄÁÌÑÔØ ÐÁËÅÔÙ, Á ÔÁËÖÅ ÎÁÓÔÒÁÉ×ÁÔØ ÓÉÓÔÅÍÕ. -\end{itemize*} - - -\subsection{çÄÅ ÍÏÖÎÏ ÐÏÌÕÞÉÔØ ÐÏÄÄÅÒÖËÕ} -\label{sec:help} - -óÏÏÂÝÅÓÔ×Ï ÐÏÌØÚÏ×ÁÔÅÌÅÊ \TeX{}Á ÁËÔÉ×ÎÏ É ÄÒÕÖÅÌÀÂÎÏ, É ÐÒÁËÔÉÞÅÓËÉ -ÎÁ ËÁÖÄÙÊ ÓÅÒØ£ÚÎÙÊ ×ÏÐÒÏÓ ÎÁÊÄ£ÔÓÑ ÏÔ×ÅÔ. ïÄÎÁËÏ ÜÔÁ ÐÏÄÄÅÒÖËÁ -ÎÅÆÏÒÍÁÌØÎÁ, ×ÙÐÏÌÎÑÅÔÓÑ ÄÏÂÒÏ×ÏÌØÃÁÍÉ, É ÐÏÜÔÏÍÕ ÏÞÅÎØ ×ÁÖÎÏ, ÞÔÏÂÙ -×Ù ÓÁÍÉ ÐÏÐÒÏÂÏ×ÁÌÉ ÎÁÊÔÉ ÏÔ×ÅÔ ÐÅÒÅÄ ÔÅÍ, ËÁË ÚÁÄÁ×ÁÔØ ×ÏÐÒÏÓ. (åÓÌÉ -×Ù ÐÒÅÄÐÏÞÉÔÁÅÔÅ ËÏÍÍÅÒÞÅÓËÕÀ ÐÏÄÄÅÒÖËÕ, ×ÏÚÍÏÖÎÏ ×ÁÍ ÓÔ\'ÏÉÔ ×ÍÅÓÔÏ -\TL{} ËÕÐÉÔØ ÏÄÎÕ ÉÚ ËÏÍÍÅÒÞÅÓËÉÈ ×ÅÒÓÉÊ \TeX{}Á, ÓÍ. ÓÐÉÓÏË ÐÏ -ÁÄÒÅÓÕ \url{http://tug.org/interest.html#vendors}). - -÷ÏÔ ÓÐÉÓÏË ÉÓÔÏÞÎÉËÏ× ÐÏÄÄÅÒÖËÉ, ÐÒÉÂÌÉÚÉÔÅÌØÎÏ × ÔÏÍ ÐÏÒÑÄËÅ, × -ËÏÔÏÒÏÍ ÍÙ ÒÅËÏÍÅÎÄÕÅÍ Ë ÎÉÍ ÏÂÒÁÝÁÔØÓÑ: - -\begin{description} - -\item[óÔÒÁÎÉÃÁ ÄÌÑ ÎÏ×ÉÞËÏ×:] åÓÌÉ ×Ù "--- ÎÏ×ÉÞÏË, ÔÏ ÓÔÒÁÎÉÃÁ - \url{http://tug.org/begin.html} ÍÏÖÅÔ ÐÏÓÌÕÖÉÔØ ÄÌÑ ÎÁÞÁÌÁ. - -\item [\TeX{} \acro{FAQ}:] \TeX{} \acro{FAQ} (þÁ÷Ï, ÞÁÓÔÏ ÚÁÄÁ×ÁÅÍÙÅ - ×ÏÐÒÏÓÙ) "--- ÏÇÒÏÍÎÁÑ ËÏÌÌÅËÃÉÑ ÏÔ×ÅÔÏ× ÎÁ ×ÓÅ×ÏÚÍÏÖÎÙÅ ×ÏÐÒÏÓÙ, ÏÔ - ÓÁÍÙÈ ÐÒÏÓÔÙÈ ÄÏ ÓÁÍÙÈ ÓÌÏÖÎÙÈ. áÎÇÌÉÊÓËÁÑ ×ÅÒÓÉÑ þÁ÷Ï ÎÁÈÏÄÉÔÓÑ ÎÁ - \TL{} × ÒÁÚÄÅÌÅ \OnCD{texmf-doc/doc/english/FAQ-en/html/index.html} - É ÄÏÓÔÕÐÎÁ × éÎÔÅÒÎÅÔÅ ÐÏ ÁÄÒÅÓÕ \url{http://www.tex.ac.uk/faq}. - ðÏÖÁÌÕÊÓÔÁ, ÎÁÞÉÎÁÊÔÅ ÐÏÉÓË ÏÔ×ÅÔÁ ÎÁ ×ÁÛÉ ×ÏÐÒÏÓÙ ÏÔÓÀÄÁ. - -\item [\TeX{} Catalogue:] åÓÌÉ ×Ù ÉÝÅÔÅ ËÁËÏÊ-ÌÉÂÏ ÐÁËÅÔ, ÛÒÉÆÔ, - ÐÒÏÇÒÁÍÍÕ É Ô.Ð., ÔÏ ×ÁÍ ÓÔÏÉÔ ÚÁÇÌÑÎÕÔØ × \TeX{} Catalogue. üÔÏ - ÏÇÒÏÍÎÙÊ ËÁÔÁÌÏÇ ×ÓÅÇÏ, ÞÔÏ ÏÔÎÏÓÉÔÓÑ Ë \TeX{}Õ. óÍ. - \url{http://www.ctan.org/help/Catalogue}. - -\item [\TeX{} ×Ï ×ÓÅÍÉÒÎÏÊ ÐÁÕÔÉÎÅ:] ÷ÏÔ ÓÔÒÁÎÉÞËÁ, ÎÁ ËÏÔÏÒÏÊ ÍÎÏÇÏ - ÓÓÙÌÏË ÐÏ \TeX{}Õ, ×ËÌÀÞÁÑ ÍÎÏÇÏÞÉÓÌÅÎÎÙÅ ËÎÉÇÉ, ÒÕËÏ×ÏÄÓÔ×Á É - ÓÔÁÔØÉ: \url{http://tug.org/interest.html}. - -\item [áÒÈÉ×Ù ÓÐÉÓËÏ× ÒÁÓÓÙÌËÉ É ÇÒÕÐÐ:] ä×Á ÏÓÎÏ×ÎÙÈ ÆÏÒÕÍÁ - ÔÅÈÎÉÞÅÓËÏÊ ÐÏÄÄÅÒÖËÉ "--- ÇÒÕÐÐÁ \url{news:comp.text.tex} É ÓÐÉÓÏË - ÒÁÓÓÙÌËÉ \email{texhax@tug.org}. ÷ ÉÈ ÁÒÈÉ×ÁÈ ÔÙÓÑÞÉ ×ÏÐÒÏÓÏ× É - ÏÔ×ÅÔÏ× ÎÁ ×ÓÅ ÓÌÕÞÁÉ ÖÉÚÎÉ. óÍ. - \url{http://groups.google.com/groups?group=comp.text.tex} É - \url{http://tug.org/mail-archives/texhax}. ðÏÉÓË, ÎÁÐÒÉÍÅÒ, × çÕÇÌÅ - (\url{http://google.com}) ÔÏÖÅ ÞÁÓÔÏ ÐÏÍÏÇÁÅÔ ÎÁÊÔÉ ÏÔ×ÅÔ. - -\item [÷ÏÐÒÏÓÙ ÎÁ ÆÏÒÕÍÁÈ] åÓÌÉ ×Ù ÎÅ ÍÏÖÅÔÅ ÎÁÊÔÉ ÏÔ×ÅÔÁ ÎÁ ×ÁÛ - ×ÏÐÒÏÓ, ×Ù ÍÏÖÅÔÅ ÌÉÂÏ ÏÐÕÂÌÉËÏ×ÁÔØ ×ÏÐÒÏÓ × \dirname{comp.text.tex} - ÐÒÉ ÐÏÍÏÝÉ Google ÉÌÉ ×ÁÛÅÊ ÌÀÂÉÍÏÊ ÎÏ×ÏÓÔÎÏÊ ÐÒÏÇÒÁÍÍÙ, ÌÉÂÏ - ÐÏÓÌÁÔØ ÐÉÓØÍÏ ÎÁ ÌÉÓÔ ÒÁÓÓÙÌËÉ \email{texhax@tug.org}. îÏ ÐÅÒÅÄ - ÜÔÉÍ \emph{ÐÏÖÁÌÕÊÓÔÁ} ÐÒÏÞÔÉÔÅ × þÁ÷Ï ÓÏ×ÅÔ Ï ÔÏÍ, ËÁË ÐÒÁ×ÉÌØÎÏ - ÚÁÄÁ×ÁÔØ ×ÏÐÒÏÓÙ ÎÁ ÜÔÉÈ ÆÏÒÕÍÁÈ: - \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. - -\item [ðÏÄÄÅÒÖËÁ \TL{}] åÓÌÉ ×Ù ÈÏÔÉÔÅ ÓÏÏÂÝÉÔØ Ï ÂÁÇÅ ÉÌÉ - ×ÙÓËÁÚÁÔØ ÎÁÍ Ó×ÏÉ ÐÒÅÄÌÏÖÅÎÉÑ É ÚÁÍÅÞÁÎÉÑ Ï ÄÉÓÔÒÉÂÕÔÉ×Å \TL{}, - ÅÇÏ ÕÓÔÁÎÏ×ËÅ ÉÌÉ ÄÏËÕÍÅÎÔÁÃÉÉ, ÐÉÛÉÔÅ ÎÁ ÌÉÓÔ ÒÁÓÓÙÌËÉ - \email{tex-live@tug.org}. ïÄÎÁËÏ ÅÓÌÉ ×ÁÛ ×ÏÐÒÏÓ ËÁÓÁÅÔÓÑ - ËÏÎËÒÅÔÎÏÊ ÐÒÏÇÒÁÍÍÙ, ×ÈÏÄÑÝÅÊ × \TL{}, ×ÁÍ ÌÕÞÛÅ ÚÁÄÁ×ÁÔØ - ×ÏÐÒÏÓ٠ţ Á×ÔÏÒÕ ÉÌÉ ÐÏÓÙÌÁÔØ ÉÈ ÎÁ ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÊ ÓÐÉÓÏË - ÒÁÓÓÙÌËÉ. þÁÓÔÏ ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÊ ÁÄÒÅÓ ÍÏÖÎÏ ÐÏÌÕÞÉÔØ ÐÒÉ ÐÏÍÏÝÉ - ÏÐÃÉÉ \code{-{}-help} ÎÕÖÎÏÊ ÐÒÏÇÒÁÍÍÙ. - -\item[òÕÓÓËÏÑÚÙÞÎÙÅ ÒÅÓÕÒÓÙ] \emph{(ÄÏÂÁ×ÌÅÎÏ ÐÅÒÅ×ÏÄÞÉËÏÍ)} - üÈÏËÏÎÆÅÒÅÎÃÉÑ \dirname{ru.tex} ÄÏÓÔÕÐÎÁ ËÁË × ÓÅÔÉ æéäï, ÔÁË É × - éÎÔÅÒÎÅÔÅ (ËÁË \url{news:fido7.ru.tex}). òÕÓÓËÉÅ ÇÒÕÐÐÙ æéäï ÍÏÖÎÏ - ÎÁÊÔÉ ÎÁ ÍÎÏÇÉÈ ÓÅÒ×ÅÒÁÈ, ÎÁÐÒÉÍÅÒ \code{demos.ddt.su}. ÷ FAQ - ÜÔÏÊ ÇÒÕÐÐÙ (Á×ÔÏÒ "--- íÉÈÁÉÌ ëÏÌÏÄÉÎ) ÐÒÉ×ÏÄÉÔÓÑ ÍÎÏÇÏ ÓÓÙÌÏË ÎÁ - ÒÕÓÓËÏÑÚÙÞÎÙÅ ÒÅÓÕÒÓÙ. - -\end{description} - -ó ÄÒÕÇÏÊ ÓÔÏÒÏÎÙ, ×Ù ÓÁÍÉ ÔÏÖÅ ÍÏÖÅÔÅ ÐÏÍÏÞØ ÔÅÍ, Õ ËÏÇÏ ÅÓÔØ ×ÏÐÒÏÓÙ. -é \dirname{comp.text.tex}, É \code{texhax}, É \dirname{fido7.ru.tex} -ÏÔËÒÙÔÙ ÄÌÑ ×ÓÅÈ, ÐÏÜÔÏÍÕ ×Ù ÔÏÖÅ ÍÏÖÅÔÅ ÐÒÉÓÏÅÄÉÎÉÔØÓÑ, ÞÉÔÁÔØ É -ÐÏÍÏÇÁÔØ ÄÒÕÇÉÍ. - - -% don't use \TL so the \uppercase in the headline works. Also so -% tex4ht ends up with the right TeX. Likewise the \protect's. - -\section{óÔÒÕËÔÕÒÁ \protect\TeX\protect\ Live} -\label{sec:overview-tl} - -üÔÏÔ ÒÁÚÄÅÌ ÏÐÉÓÙ×ÁÅÔ ÓÔÒÕËÔÕÒÕ É ÓÏÄÅÒÖÁÎÉÅ \TK{} É ÅÇÏ ÓÏÓÔÁ×ÎÏÊ -ÞÁÓÔÉ \TL{}. - - -\subsection{\protect\TeX\protect\ Collection: \TL, pro\TeX{}t, Mac\TeX} -\label{sec:tl-coll-dists} - -\DVD{} \TK{} ÓÏÄÅÒÖÉÔ ÓÌÅÄÕÀÝÉÅ ÐÁËÅÔÙ: - -\begin{description} - -\item [\TL:] ÐÏÌÎÁÑ ÓÉÓÔÅÍÁ, ËÏÔÏÒÏÊ ÍÏÖÎÏ ÐÏÌØÚÏ×ÁÔØÓÑ - ÌÉÂÏ ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ Ó \DVD{}, ÌÉÂÏ ÕÓÔÁÎÏ×É× ÎÁ ÄÉÓË ËÏÍÐØÀÔÅÒÁ. - -\item [Mac\TeX:] ×ÁÒÉÁÎÔ ÄÌÑ \MacOSX{}. üÔÏÔ ÐÁËÅÔ ÄÏÂÁ×ÌÑÅÔ Ë \TL{} - ÐÒÏÇÒÁÍÍÕ ÕÓÔÁÎÏ×ËÉ ÄÌÑ \MacOSX{} É ÄÒÕÇÉÅ ÐÒÏÇÒÁÍÍÙ ÄÌÑ íÁËÉÎÔÏÛÅÊ. - óÔÒÁÎÉÃÁ ÐÒÏÅËÔÁ "--- \url{http://www.tug.org/mactex/}. - - -\item[pro\TeX{}t:] ÕÌÕÞÛÅÎÎÙÊ ×ÁÒÉÁÎÔ ÄÉÓÔÒÉÂÕÔÉ×Á \MIKTEX\ ÄÌÑ Windows. - \ProTeXt\ ×ËÌÀÞÁÅÔ × ÓÅÂÑ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ÐÒÏÇÒÁÍÍÙ É ÕÐÒÏÝ£ÎÎÕÀ - ÕÓÔÁÎÏ×ËÕ. ïÎ ÎÅ ÚÁ×ÉÓÉÔ ÏÔ \TL{} É ×ËÌÀÞÁÅÔ ÓÏÂÓÔ×ÅÎÎÙÅ ÉÎÓÔÒÕËÃÉÉ - ÐÏ ÕÓÔÁÎÏ×ËÅ. óÔÒÁÎÉÃÁ \ProTeXt{} "--- - \url{http://tug.org/protext}. - -\item [CTAN:] úÅÒËÁÌÏ ÁÒÈÉ×Á \CTAN. - -\item[\texttt{texmf-extra}:] ÄÉÒÅËÔÏÒÉÑ Ó ÒÁÚÎÏÏÂÒÁÚÎÙÍÉ - ÄÏÐÏÌÎÉÔÅÌØÎÙÍÉ ÐÁËÅÔÁÍÉ. - - -\end{description} - -ìÉÃÅÎÚÉÉ ÎÁ ÉÓÐÏÌØÚÏ×ÁÎÉÅ \CTAN{}, \pkgname{protext} É -\texttt{texmf-extra} ÏÔÌÉÞÁÀÔÓÑ ÏÔ ÌÉÃÅÎÚÉÉ \TL{}, ÐÏÜÔÏÍÕ ÂÕÄØÔÅ -×ÎÉÍÁÔÅÌØÎÙ ÐÒÉ ÒÁÓÐÒÏÓÔÒÁÎÅÎÉÉ ÉÌÉ ÍÏÄÉÆÉËÁÃÉÉ ÐÒÏÇÒÁÍÍ, ×ÈÏÄÑÝÉÈ × -ÜÔÉ ÄÉÓÔÒÉÂÕÔÉ×Ù. - - -\subsection{ëÏÒÎÅ×ÙÅ ÄÉÒÅËÔÏÒÉÉ} -\label{sec:tld} - -÷ÏÔ ËÒÁÔËÏÅ ÏÐÉÓÁÎÉÅ ËÏÒÎÅ×ÙÈ ÄÉÒÅËÔÏÒÉÊ × ÄÉÓÔÒÉÂÕÔÉ×Å \TL{}. îÁ - \DVD \TK{} ×ÓÑ ÉÅÒÁÒÈÉÑ \TL{} ÐÏÍÅÝÅÎÁ × ÐÏÄÄÉÒÅËÔÏÒÉÀ -\dirname{texlive}, Á ÎÅ × ËÏÒÅÎØ ÄÉÓËÁ. - -\begin{ttdescription} -\item[bin:] ðÒÏÇÒÁÍÍÙ ÓÉÓÔÅÍÙ \TeX{}, ÓÇÒÕÐÐÉÒÏ×ÁÎÎÙÅ ÐÏ ÐÌÁÔÆÏÒÍÁÍ. -% -\item[readme.html:] óÔÒÁÎÉÞËÉ WWW Ó ËÒÁÔËÉÍ ÒÕËÏ×ÏÄÓÔ×ÏÍ ÄÌÑ - ÐÏÌØÚÏ×ÁÔÅÌÑ É ÒÁÚÌÉÞÎÙÍÉ ÓÓÙÌËÁÍÉ, ÎÁ ÒÁÚÎÙÈ ÑÚÙËÁÈ. -% -\item[source:] éÓÈÏÄÎÙÊ ËÏÄ ×ÓÅÈ ÐÒÏÇÒÁÍÍ, ×ËÌÀÞÁÑ ÄÉÓÔÒÉÂÕÔÉ×Ù \Webc{} - \TeX{} É \MF{}. -% -\item[support:] òÁÚÎÙÅ ×ÓÐÏÍÏÇÁÔÅÌØÎÙÅ ÐÁËÅÔÙ É ÐÒÏÇÒÁÍÍÙ. ïÎÉ - \emph{ÎÅ} ÕÓÔÁÎÁ×ÌÉ×ÁÀÔÓÑ ÐÏ ÕÍÏÌÞÁÎÉÀ. óÀÄÁ ÏÔÎÏÓÑÔÓÑ - ÒÁÚÎÏÏÂÒÁÚÎÙÅ ÒÅÄÁËÔÏÒÙ É ÏÂÏÌÏÞËÉ ÄÌÑ \TeX{}Á. -% -\item[texmf:] óÍ. \dirname{TEXMFMAIN} ÎÉÖÅ. -% -\item[texmf-dist:] óÍ. \dirname{TEXMFDIST} ÎÉÖÅ. -% -\item[texmf-doc:] äÅÒÅ×Ï ÓÁÍÏÓÔÏÑÔÅÌØÎÏÊ ÄÏËÕÍÅÎÔÁÃÉÉ, ÓÇÒÕÐÐÉÒÏ×ÁÎÎÏÊ - ÐÏ ÑÚÙËÁÍ. -% -\item[tlpkg:] óËÒÉÐÔÙ, ÐÒÏÇÒÁÍÍÙ É ÄÒÕÇÉÅ ÆÁÊÌÙ ÄÌÑ ÐÏÄÄÅÒÖËÉ ÓÉÓÔÅÍÙ. - üÔÏ ÄÅÒÅ×Ï ÔÁËÖÅ ÓÏÄÅÒÖÉÔ ÓÏÂÓÔ×ÅÎÎÙÅ ËÏÐÉÉ ÐÒÏÇÒÁÍÍ Perl É - Ghostscript, ÎÅ×ÉÄÉÍÙÅ ×ÎÅ \TL{}, Á ÔÁËÖÅ ÎÏ×ÕÀ ÏÂÏÌÏÞËÕ ÄÌÑ - ÐÒÏÓÍÏÔÒÁ ÐÏÓÔÓËÒÉÐÔÏ×ÓËÉÈ ÆÁÊÌÏ× ÐÏÄ Windows, PSView. -\end{ttdescription} - - -ëÒÏÍÅ ÜÔÉÈ ÄÉÒÅËÔÏÒÉÊ, × ËÏÒÎÅ×ÏÊ ÄÉÒÅËÔÏÒÉÉ ÎÁÈÏÄÑÔÓÑ ÓËÒÉÐÔÙ -ÕÓÔÁÎÏ×ËÉ É ÆÁÊÌÙ \filename{README} (ÎÁ ÒÁÚÎÙÈ ÑÚÙËÁÈ). - -äÉÒÅËÔÏÒÉÑ \dirname{texmf-doc} ÓÏÄÅÒÖÉÔ ÄÏËÕÍÅÎÔÁÃÉÀ, ËÏÔÏÒÁÑ ÎÅ -ÏÔÎÏÓÉÔÓÑ Ë ÏÔÄÅÌØÎÙÍ ÐÁËÅÔÁÍ ÉÌÉ ÐÒÏÇÒÁÍÍÁÍ. äÏËÕÍÅÎÔÁÃÉÑ Ë -ÐÒÏÇÒÁÍÍÁÍ (ÒÕËÏ×ÏÄÓÔ×Á, man, info) ÎÁÈÏÄÉÔÓÑ × ÄÉÒÅËÔÏÒÉÉ -\dirname{texmf/doc}. äÏËÕÍÅÎÔÁÃÉÑ ÍÁËÒÏÐÁËÅÔÏ× É ÆÏÒÍÁÔÏ× -ÎÁÈÏÄÉÔÓÑ × ÄÉÒÅËÔÏÒÉÉ \dirname{texmf-dist/doc}. äÌÑ ÐÏÉÓËÁ -ÄÏËÕÍÅÎÔÁÃÉÉ ÍÏÖÎÏ ×ÏÓÐÏÌØÚÏ×ÁÔØÓÑ ÐÒÏÇÒÁÍÍÁÍÉ \cmdname{texdoc} ÉÌÉ -\cmdname{texdoctk}. íÏÖÎÏ ÔÁËÖÅ ×ÏÓÐÏÌØÚÏ×ÁÔØÓÑ ÓÓÙÌËÁÍÉ × ÆÁÊÌÅ -\OnCD{doc.html} × ËÏÒÎÅ×ÏÊ ÄÉÒÅËÔÏÒÉÉ. - -äÏËÕÍÅÎÔÁÃÉÑ Ë ÓÁÍÏÍÕ ÄÉÓÔÒÉÂÕÔÉ×Õ \TL{} ÎÁÈÏÄÉÔÓÑ × ÄÉÒÅËÔÏÒÉÉ -\dirname{texmf-doc} É ÄÏÓÔÕÐÎÁ ÎÁ ÎÅÓËÏÌØËÉÈ ÑÚÙËÁÈ: -\begin{itemize*} -\item{áÎÇÌÉÊÓËÉÊ:} \OnCD{texmf-doc/doc/english/texlive-en} -\item{õÐÒÏÝÅÎÎÙÊ ËÉÔÁÊÓËÉÊ:} \OnCD{texmf-doc/doc/chinese/texlive-zh-cn} -\item{îÅÍÅÃËÉÊ:} \OnCD{texmf-doc/doc/german/texlive-de} -\item{ðÏÌØÓËÉÊ:} \OnCD{texmf-doc/doc/polish/texlive-pl} -\item{òÕÓÓËÉÊ:} \OnCD{texmf-doc/doc/russian/texlive-ru} -\item{æÒÁÎÃÕÚÓËÉÊ:} \OnCD{texmf-doc/doc/french/texlive-fr} -\item{þÅÛÓËÉÊ É ÓÌÏ×ÁÃËÉÊ:} \OnCD{texmf-doc/doc/czechslovak/texlive-cz} -\end{itemize*} - -\subsection{ïÐÉÓÁÎÉÅ ÄÉÒÅËÔÏÒÉÊ texmf} -\label{sec:texmftrees} - -÷ ÜÔÏÍ ÒÁÚÄÅÌÅ ÏÐÉÓÁÎÙ ×ÓÅ ÐÅÒÅÍÅÎÎÙÅ, ÚÁÄÁÀÝÉÅ ÐÏÌÏÖÅÎÉÅ ÄÅÒÅ×ØÅ× -ÄÉÒÅËÔÏÒÉÊ texmf É ÉÈ ÚÎÁÞÅÎÉÑ ÐÏ ÕÍÏÌÞÁÎÉÀ. ëÏÍÁÎÄÁ -\texttt{texconfig conf} ÐÏËÁÚÙ×ÁÅÔ ÔÅËÕÝÉÅ ÚÎÁÞÅÎÉÑ ÜÔÉÈ ÐÅÒÅÍÅÎÎÙÈ, -ÔÁË ÞÔÏ ×Ù ÍÏÖÅÔÅ ÌÅÇËÏ ÐÒÏ×ÅÒÉÔØ, ÇÄÅ ÜÔÉ ÄÉÒÅËÔÏÒÉÉ ÎÁÈÏÄÑÔÓÑ × -×ÁÛÅÊ ÓÉÓÔÅÍÅ. - -\begin{ttdescription} -\item [TEXMFMAIN] äÅÒÅ×Ï, ÇÄÅ ÎÁÈÏÄÑÔÓÑ ÏÓÎÏ×ÎÙÅ ÞÁÓÔÉ ÓÉÓÔÅÍÙ, - ÔÁËÉÅ, ËÁË ×ÓÐÏÍÏÇÁÔÅÌØÎÙÅ ÓËÒÉÐÔÙ (ÎÁÐÒÉÍÅÒ, - \verb+web2c/mktexdir+), ÄÒÕÇÉÅ ×ÓÐÏÍÏÇÁÔÅÌØÎÙÅ ÆÁÊÌÙ É ÄÏËÕÍÅÎÔÁÃÉÑ - Ë ÎÉÍ. üÔÏ ÄÅÒÅ×Ï ÎÅ ÓÏÄÅÒÖÉÔ ÆÏÒÍÁÔÏ× \TeX Á É ÐÁËÅÔÏ×. -\item [TEXMFDIST] äÅÒÅ×Ï Ó ÏÓÎÏ×ÎÙÍ ÎÁÂÏÒÏÍ ÍÁËÒÏÐÁËÅÔÏ×, ÛÒÉÆÔÏ× É - Ô.Ä. × ÐÅÒ×ÏÎÁÞÁÌØÎÏÊ ËÏÎÆÉÇÕÒÁÃÉÉ. -\item [TEXMFLOCAL] äÅÒÅ×Ï, ËÏÔÏÒÏÅ ÍÏÖÅÔ ÂÙÔØ ÉÓÐÏÌØÚÏ×ÁÎÏ - ÁÄÍÉÎÉÓÔÒÁÔÏÒÁÍÉ ÓÉÓÔÅÍÙ ÄÌÑ ÄÏÐÏÌÎÉÔÅÌØÎÙÈ ÐÁËÅÔÏ×, - ÛÒÉÆÔÏ× É Ô.Ä., ÉÌÉ ÕÓÔÁÎÏ×ËÉ ÏÂÎÏ×ÌÅÎÉÊ. -\item [TEXMFHOME] äÅÒÅ×Ï, ËÏÔÏÒÏÅ ÐÏÌØÚÏ×ÁÔÅÌÉ ÍÏÇÕÔ ÉÓÐÏÌØÚÏ×ÁÔØ ÄÌÑ - ÕÓÔÁÎÏ×ËÉ ÓÏÂÓÔ×ÅÎÎÙÈ ÐÁËÅÔÏ×, ÛÒÉÆÔÏ× É Ô.Ä., ÉÌÉ ÄÌÑ ÏÂÎÏ×Ì£ÎÎÙÈ - ×ÅÒÓÉÊ ÓÉÓÔÅÍÎÙÈ ÐÁËÅÔÏ×. üÔÁ ÐÅÒÅÍÅÎÎÁÑ Ñ×ÌÑÅÔÓÑ - Ó×ÏÅÊ ÄÌÑ ËÁÖÄÏÇÏ ÐÏÌØÚÏ×ÁÔÅÌÑ. -\item [TEXMFCONFIG] üÔÏ ÄÅÒÅ×Ï ÉÓÐÏÌØÚÕÅÔÓÑ ÕÔÉÌÉÔÁÍÉ - \verb+texconfig+, \verb+updmap+ É \verb+fmtutil+ - ÄÌÑ ÈÒÁÎÅÎÉÑ ÍÏÄÉÆÉÃÉÒÏ×ÁÎÎÙÈ ÆÁÊÌÏ× ËÏÎÆÉÇÕÒÁÃÉÉ. ðÏ ÕÍÏÌÞÁÎÉÀ - ÎÁÈÏÄÉÔÓÑ × ÄÉÒÅËÔÏÒÉÉ \envname{TEXMFHOME}. -\item [TEXMFSYSCONFIG] üÔÏ ÄÅÒÅ×Ï ÉÓÐÏÌØÚÕÅÔÓÑ ÕÔÉÌÉÔÁÍÉ - \verb+texconfig-sys+, \verb+updmap-sys+ É \verb+fmtutil-sys+ - ÄÌÑ ÈÒÁÎÅÎÉÑ ÍÏÄÉÆÉÃÉÒÏ×ÁÎÎÙÈ ÆÁÊÌÏ× - ËÏÎÆÉÇÕÒÁÃÉÉ, ÏÂÝÉÈ ÄÌÑ ×ÓÅÈ ÐÏÌØÚÏ×ÁÔÅÌÅÊ. -\item [TEXMFVAR] üÔÏ ÄÅÒÅ×Ï ÉÓÐÏÌØÚÕÅÔÓÑ ÕÔÉÌÉÔÁÍÉ \verb+texconfig+, - \verb+updmap+ É \verb+fmtutil+ ÄÌÑ ÈÒÁÎÅÎÉÑ - ÓÏÚÄÁ×ÁÅÍÙÈ Á×ÔÏÍÁÔÉÞÅÓËÉ ÆÁÊÌÏ×: ÆÏÒÍÁÔÏ×, ËÁÒÔ ÛÒÉÆÔÏ×. ðÏ - ÕÍÏÌÞÁÎÉÀ ÎÁÈÏÄÉÔÓÑ × ÄÉÒÅËÔÏÒÉÉ \envname{TEXMFHOME}. -\item [TEXMFSYSVAR] üÔÏ ÄÅÒÅ×Ï ÉÓÐÏÌØÚÕÅÔÓÑ ÕÔÉÌÉÔÁÍÉ - \verb+texconfig-sys+, \verb+updmap-sys+, \verb+fmtutil-sys+, Á ÔÁËÖÅ - \verb+tlmgr+ - ÄÌÑ ÈÒÁÎÅÎÉÑ ÓÏÚÄÁ×ÁÅÍÙÈ Á×ÔÏÍÁÔÉÞÅÓËÉ ÆÁÊÌÏ×: - ÆÏÒÍÁÔÏ×, ËÁÒÔ ÛÒÉÆÔÏ×, "--- ÏÂÝÉÈ ÄÌÑ ×ÓÅÈ ÐÏÌØÚÏ×ÁÔÅÌÅÊ. -\end{ttdescription} - -\noindent -ðÏ ÕÍÏÌÞÁÎÉÀ ÓÔÒÕËÔÕÒÁ ÄÉÒÅËÔÏÒÉÊ ×ÙÇÌÑÄÉÔ ÔÁË: -\begin{description} - \item[ËÏÒÎÅ×ÁÑ ÄÉÒÅËÔÏÒÉÑ] ÍÏÖÅÔ ÓÏÄÅÒÖÁÔØ ÎÅÓËÏÌØËÏ ×ÅÒÓÉÊ \TL{}: - \begin{ttdescription} - \item[2007] ðÒÅÄÙÄÕÝÁÑ ×ÅÒÓÉÑ. - \begin{ttdescription} - \item [...] - \end{ttdescription} - \item[2008] ôÅËÕÝÁÑ ×ÅÒÓÉÑ. - \begin{ttdescription} - \item [bin] ~ - \begin{ttdescription} - \item [i386-linux] ðÒÏÇÒÁÍÍÙ ÄÌÑ \GNU/Linux - \item [...] - \item [universal-darwin] ðÒÏÇÒÁÍÍÙ ÄÌÑ \MacOSX - \item [win32] ðÒÏÇÒÁÍÍÙ ÄÌÑ Windows - \end{ttdescription} - \item [texmf] \envname{TEXMFMAIN}. - \item [texmf-dist] \envname{TEXMFDIST} - \item [texmf-doc] \envname{TEXMFDOC} - \item [texmf-var] \envname{TEXMFSYSVAR} - \item [texmf-config] \envname{TEXMFSYSCONFIG} - \end{ttdescription} - \item [texmf-local] \envname{TEXMFLOCAL}, ÏÂÝÁÑ ÄÌÑ ×ÓÅÈ ×ÅÒÓÉÊ - \TL{}. - \end{ttdescription} - \item[ÄÏÍÁÛÎÑÑ ÄÉÒÅËÔÏÒÉÑ ÐÏÌØÚÏ×ÁÔÅÌÑ] (\texttt{\$HOME} ÉÌÉ - \texttt{\%USERPROFILE\%}) - \begin{ttdescription} - \item[.texlive2007] äÁÎÎÙÅ É ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÆÁÊÌÙ ÐÒÅÄÙÄÕÝÅÊ - ×ÅÒÓÉÉ. - \item[.texlive2008] äÁÎÎÙÅ É ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÆÁÊÌÙ ÔÅËÕÝÅÊ - ×ÅÒÓÉÉ. - \begin{ttdescription} - \item [texmf-var] \envname{TEXMFVAR} - \item [texmf-config] \envname{TEXMFCONFIG} - \end{ttdescription} - \item[texmf] \envname{TEXMFHOME} ìÉÞÎÙÅ ÍÁËÒÏÐÁËÅÔÙ. - \textit{etc.} - \end{ttdescription} -\end{description} - -\subsection{òÁÓÛÉÒÅÎÉÑ \protect\TeX{}Á} -\label{sec:tex-extensions} - -ëÎÕÔÏ×ÓËÉÊ ×ÁÒÉÁÎÔ \TeX Á ÚÁÍÏÒÏÖÅÎ "--- ÚÁ ÉÓËÌÀÞÅÎÉÅÍ ÒÅÄËÉÈ -ÉÓÐÒÁ×ÌÅÎÉÊ ÂÁÇÏ×, × ÎÅÇÏ ÎÅ ×ÎÏÓÉÔÓÑ ÎÉËÁËÉÈ ÉÚÍÅÎÅÎÉÊ. ïÎ ×ÓÅ ÅÝ£ -ÒÁÓÐÒÏÓÔÒÁÎÑÅÔÓÑ × \TL{} ËÁË \prog{tex} É ÂÕÄÅÔ ÒÁÓÐÒÏÓÔÒÁÎÑÔØÓÑ × -ÏÂÏÚÒÉÍÏÍ ÂÕÄÕÝÅÍ. ÷ ÓÏÓÔÁ× \TL{} ×ÈÏÄÉÔ ÎÅÓËÏÌØËÏ ÒÁÓÛÉÒÅÎÉÊ \TeX{}Á: - -\begin{description} - -\item [\eTeX] ÄÏÂÁ×ÌÑÅÔ ÎÁÂÏÒ ÎÏ×ÙÈ ÐÒÉÍÉÔÉ×Ï× -\label{text:etex} -(ÏÔÎÏÓÑÝÉÊÓÑ Ë ÍÁËÒÏÐÏÄÓÔÁÎÏ×ËÁÍ, ÞÔÅÎÉÀ ÓÉÍ×ÏÌÏ×, ÄÏÐÏÌÎÉÔÅÌØÎÙÍ -×ÏÚÍÏÖÎÏÓÔÑÍ ÏÔÌÁÄËÉ É ÍÎÏÇÏÍÕ ÄÒÕÇÏÍÕ) É ÒÁÓÛÉÒÅÎÉÑ \TeXXeT{} ÄÌÑ -×£ÒÓÔËÉ ÓÐÒÁ×Á ÎÁÌÅ×Ï É ÓÌÅ×Á ÎÁÐÒÁ×Ï. ÷ ÏÂÙÞÎÏÍ ÒÅÖÉÍÅ \eTeX{} ÎÁ -100\% ÓÏ×ÍÅÓÔÉÍ ÓÏ ÓÔÁÎÄÁÒÔÎÙÍ\TeX{}ÏÍ. óÍ. -\OnCD{texmf-dist/doc/etex/base/etex_man.pdf}. - -\item [pdf\TeX] ×ËÌÀÞÁÅÔ × ÓÅÂÑ ÒÁÓÛÉÒÅÎÉÑ \eTeX Á, ÄÏÂÁ×ÌÑÑ ÐÏÄÄÅÒÖËÕ - ÆÏÒÍÁÔÁ \acro{PDF}, ÐÏÍÉÍÏ ÓÔÁÎÄÁÒÔÎÏÇÏ \dvi{}. üÔÁ ÐÒÏÇÒÁÍÍÁ - ÉÓÐÏÌØÚÕÅÔÓÑ ÂÏÌØÛÉÎÓÔ×ÏÍ ÆÏÒÍÁÔÏ×, ÎÁÐÒÉÍÅÒ, \prog{etex}, - \prog{latex}, \prog{pdflatex}. óÍ. \url{http://www.pdftex.org/}. - ÷ ÒÕËÏ×ÏÄÓÔ×Å ÐÏÌØÚÏ×ÁÔÅÌÑ \OnCD{texmf/doc/pdftex/manual/} É ÐÒÉÍÅÒÅ - \OnCD{texmf/doc/pdftex/manual/samplepdf/samplepdf.tex} ÏÐÉÓÁÎÙ - ×ÏÚÍÏÖÎÏÓÔÉ ÐÒÏÇÒÁÍÍÙ. - -\item[Lua\TeX] ÐÒÅÄÎÁÚÎÁÞÅÎ ÚÁÍÅÎÉÔØ pdf\TeX{} × ÂÕÄÕÝÅÍ. - ðÒÅÄÐÏÌÁÇÁÅÔÓÑ, ÞÔÏ ÏÎ ÂÕÄÅÔ ÓÏ×ÍÅÓÔÉÍ Ó ÐÏÓÌÅÄÎÉÍ. ïÎ ÔÁËÖÅ - ÚÁÍÅÎÉÔ Aleph, ÓÍ. ÎÉÖÅ. ÷ÓÔÒÏÅÎÎÙÊ ÉÎÔÅÒÐÒÅÔÁÔÏÒ ÑÚÙËÁ Lua (ÓÍ. - \url{http://www.lua.org/}) ÐÏÚ×ÏÌÑÅÔ ÜÌÅÇÁÎÔÎÏ ÒÅÛÉÔØ ÍÎÏÇÉÅ ÓÌÏÖÎÙÅ - ÐÒÏÂÌÅÍÙ \TeX Á. ëÏÇÄÁ ÜÔÁ ÐÒÏÇÒÁÍÍÁ ÚÁÐÕÓËÁÅÔÓÑ ËÁË - \filename{texlua}, ÏÎÁ ÒÁÂÏÔÁÅÔ ËÁË ÉÎÔÅÒÐÒÅÔÁÔÏÒ Lua, É × ÜÔÏÍ - ËÁÞÅÓÔ×Å ÉÓÐÏÌØÚÕÅÔÓÑ × \TL{}. óÍ. \url{http://www.luatex.org/} É - \OnCD{texmf-dist/doc/luatex/luatexref-t.pdf}. - -\item [Xe\TeX] ÄÏÂÁ×ÌÑÅÔ ÐÏÄÄÅÒÖËÕ Unicode É ÛÒÉÆÔÏ× × ÆÏÒÍÁÔÅ - OpenType, ÓÄÅÌÁÎÎÕÀ ÞÅÒÅÚ ÓÔÁÎÄÁÒÔÎÙÅ ÂÉÂÌÉÏÔÅËÉ. óÍ. - \url{http://scripts.sil.org/xetex}. - -\item [\OMEGA\ (ïÍÅÇÁ)] ÏÓÎÏ×ÁÎÁ ÎÁ Unicode (ÓÉÓÔÅÍÁ 16-ÂÉÔÏ×ÙÈ - ÓÉÍ×ÏÌÏ×), ÞÔÏ ÐÏÚ×ÏÌÑÅÔ ÒÁÂÏÔÁÔØ ÏÄÎÏ×ÒÅÍÅÎÎÏ ÐÏÞÔÉ ÓÏ ×ÓÅÍÉ - ÐÉÓØÍÅÎÎÏÓÔÑÍÉ ÍÉÒÁ. ïÎÁ ÔÁËÖÅ ÐÏÄÄÅÒÖÉ×ÁÅÔ ÔÁË ÎÁÚÙ×ÁÅÍÙÊ <<ÐÒÏÃÅÓÓ - ÔÒÁÎÓÌÑÃÉÉ \OMEGA{}>> (\acro{OTP}s) ÄÌÑ ÓÌÏÖÎÙÈ ÐÒÅÏÂÒÁÚÏ×ÁÎÉÊ - ÐÒÏÉÚ×ÏÌØÎÏÇÏ ×ÈÏÄÎÏÇÏ ÐÏÔÏËÁ. óÍ. - \OnCD{texmf-dist/doc/omega/base/doc-1.8.tex} (ÔÅËÓÔ ÎÅÓËÏÌØËÏ ÕÓÔÁÒÅÌ). - - -\item[Aleph] ÏÂßÅÄÉÎÑÅÔ \OMEGA\ É \eTeX. óÍ. ËÒÁÔËÕÀ ÄÏËÕÍÅÎÔÁÃÉÀ × - \OnCD{texmf-dist/doc/aleph/base}. - -\end{description} - - -\subsection{äÒÕÇÉÅ ÉÎÔÅÒÅÓÎÙÅ ÐÒÏÇÒÁÍÍÙ × ÄÉÓÔÒÉÂÕÔÉ×Å \protect\TL} - -÷ÏÔ ÎÅÓËÏÌØËÏ ÄÒÕÇÉÈ ÞÁÓÔÏ ÉÓÐÏÌØÚÕÅÍÙÈ ÐÒÏÇÒÁÍÍ × ÄÉÓÔÒÉÂÕÔÉ×Å \TL{}: - -\begin{cmddescription} - -\item [bibtex] ÐÏÄÄÅÒÖËÁ ÂÉÂÌÉÏÇÒÁÆÉÊ. - -\item [makeindex] ÐÏÄÄÅÒÖËÁ ÁÌÆÁ×ÉÔÎÙÈ ÕËÁÚÁÔÅÌÅÊ. - -\item [dvips] ÐÒÅÏÂÒÁÚÏ×ÁÎÉÅ \dvi{} × \PS{}. - -\item [xdvi] ÐÒÏÇÒÁÍÍÁ ÄÌÑ ÐÒÏÓÍÏÔÒÁ \dvi{} ÄÌÑ X Window System. - -\item [dvilj] ÄÒÁÊ×ÅÒ ÄÌÑ ÌÁÚÅÒÎÙÈ ÐÒÉÎÔÅÒÏ× ÓÅÍÅÊÓÔ×Á HP LaserJet. - -\item [dv2dt, dt2dv] ÐÒÅÏÂÒÁÚÏ×ÁÎÉÅ \dvi{} × ÔÅËÓÔ É ÏÂÒÁÔÎÏ. - -\item [dviconcat, dviselect] ÐÅÒÅÓÔÁÎÏ×ËÁ ÓÔÒÁÎÉÃ × ÆÁÊÌÁÈ \dvi{}. - -\item [dvipdfmx] ÐÒÅÏÂÒÁÚÏ×ÁÎÉÅ \dvi{} × \acro{PDF}, ÁÌØÔÅÒÎÁÔÉ×Á - pdf\TeX{}Õ, ÕÐÏÍÑÎÕÔÏÍÕ ×ÙÛÅ. ðÁËÅÔÙ \pkgname{ps4pdf} É -\pkgname{pdftricks} ÐÒÅÄÌÁÇÁÀÔ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ×ÏÚÍÏÖÎÏÓÔÉ. - -\item [psselect, psnup, \ldots] ÕÔÉÌÉÔÙ ÄÌÑ ÆÏÒÍÁÔÁ \PS{}. - -\item [lacheck] ÐÒÏ×ÅÒËÁ ÓÉÎÔÁËÓÉÓÁ \LaTeX{}Á. - -\item [texexec, texmfstart] ÐÒÏÃÅÓÓÏÒ ÄÌÑ Con\TeX{}tÁ É \acro{PDF}. - -\item [tex4ht] ËÏÎ×ÅÒÔÅÒ ÉÚ \TeX{}Á × \acro{HTML}, \acro{XML} É ÍÎÏÇÉÅ - ÄÒÕÇÉÅ ÆÏÒÍÁÔÙ. - -\end{cmddescription} - -\subsection{ûÒÉÆÔÙ × \protect\TL{}} -\label{sec:tl-fonts} - -÷ \TL{} ×ËÌÀÞÅÎÏ ÍÎÏÇÏ ×ÅËÔÏÒÎÙÈ ÛÒÉÆÔÏ× ×ÙÓÏËÏÇÏ ËÁÞÅÓÔ×Á. -óÍ. \url{http://tug.org/fonts} É -\OnCD{texmf-doc/english/free-math-fonts-survey}. - -\section{õÓÔÁÎÏ×ËÁ} -\label{sec:install} - -\subsection{úÁÐÕÓË ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ} -\label{sec:inst-start} - -äÌÑ ÎÁÞÁÌÁ ×ÁÍ ÐÏÔÒÅÂÕÅÔÓÑ \DVD{} \TK{} ÉÌÉ ÐÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ \TL{} -Ó éÎÔÅÒÎÅÔÁ. îÁÊÄÉÔÅ ÓËÒÉÐÔ ÕÓÔÁÎÏ×ËÉ: \filename{install-tl} ÄÌÑ -àÎÉËÓÁ, \filename{install-tl.bat} ÄÌÑ Windows. - -\begin{description} -\item [õÓÔÁÎÏ×ËÁ Ó ÓÅÔÉ:] ÓËÁÞÁÊÔÅ ÐÒÏÇÒÁÍÍÕ ÉÚ ÁÒÈÉ×Á \CTAN, ÄÉÒÅËÔÏÒÉÑ -\dirname{systems/texlive/tlnet}; ÁÄÒÅÓ -\url{http://mirror.ctan.org/systems/texlive/tlnet} Á×ÔÏÍÁÔÉÞÅÓËÉ -ÐÒÉ×ÏÄÉÔ Ë ÂÌÉÖÁÊÛÅÍÕ ÚÅÒËÁÌÕ ÁÒÈÉ×Á. ÷Ù ÍÏÖÅÔÅ ÓËÁÞÁÔØ ÌÉÂÏ -\filename{install-tl.zip} (ÕÓÔÁÎÏ×ËÁ ÐÏÄ àÎÉËÓÏÍ É Windows), ÌÉÂÏ ÆÁÊÌ -ÓÕÝÅÓÔ×ÅÎÎÏ ÍÅÎØÛÅÇÏ ÒÁÚÍÅÒÁ -\filename{install-unx.tar.gz} (ÔÏÌØËÏ ÄÌÑ àÎÉËÓÁ). ðÏÓÌÅ ÒÁÓÐÁËÏ×ËÉ -ÆÁÊÌÙ \filename{install-tl} É -\filename{install-tl.bat} ÏËÁÖÕÔÓÑ × ÄÉÒÅËÔÏÒÉÉ \dirname{install-tl}. - -\item [\TeX{} Collection \DVD:] ðÅÒÅÊÄÉÔÅ × ÐÏÄÄÉÒÅËÔÏÒÉÀ - \dirname{texlive}. ðÏÄ Windows ÐÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ ÚÁÐÕÓËÁÅÔÓÑ - Á×ÔÏÍÁÔÉÞÅÓËÉ, ËÏÇÄÁ ×Ù ×ÓÔÁ×ÌÑÅÔÅ \DVD{} × ËÏÍÐØÀÔÅÒ. ÷Ù ÍÏÖÅÔÅ - ÐÏÌÕÞÉÔØ \DVD, ×ÓÔÕÐÉ× × ÇÒÕÐÐÕ ÐÏÌØÚÏ×ÁÔÅÌÅÊ \TeX Á (ÍÙ - ÎÁÓÔÏÑÔÅÌØÎÏ ÒÅËÏÍÅÎÄÕÅÍ ÜÔÏ ÓÄÅÌÁÔØ, - \url{http://tug.org/usergroups.html}), ÌÉÂÏ ËÕÐÉ× ÅÇÏ ÏÔÄÅÌØÎÏ - (\url{http://tug.org/store}), ÌÉÂÏ ÓÄÅÌÁ× ÅÇÏ ÓÁÍÏÓÔÏÑÔÅÌØÎÏ, ÓËÁÞÁ× - \ISO\ ÏÂÒÁÚ ÄÉÓËÁ (\url{http://tug.org/texlive/acquire.html}). - -\end{description} - - -÷ ÓÌÅÄÕÀÝÉÈ ÒÁÚÄÅÌÁÈ ÕÓÔÁÎÏ×ËÁ ÏÐÉÓÙ×ÁÅÔÓÑ ÂÏÌÅÅ ÐÏÄÒÏÂÎÏ. - -\subsubsection{àÎÉËÓ} - -\begin{figure}[tb] -\begin{boxedverbatim} -======================> TeX Live installation procedure <===================== - -=======> Note: Letters/digits in indicate menu items <======= -=======> for commands or configurable options <======= - - - Detected platform: Intel x86 with GNU/Linux - - binary systems: 1 out of 16 - - Installation scheme (scheme-full) - - Customizing installation scheme: - standard collections - language collections - 83 collections out of 84, disk space required: 1666 MB - - directories: - TEXDIR (the main TeX directory): - !! default location: /usr/local/texlive/2008 - !! is not writable, please select a different one! - TEXMFLOCAL (directory for site-wide local files): - /usr/local/texlive/texmf-local - TEXMFSYSVAR (directory for variable and automatically generated data): - /usr/local/texlive/2008/texmf-var - TEXMFSYSCONFIG (directory for local config): - /usr/local/texlive/2008/texmf-config - TEXMFHOME (directory for user-specific files): - ~/texmf - - options: - [ ] use letter size instead of A4 by default - [X] create all format files - [X] install macro/font doc tree - [X] install macro/font source tree - [ ] create symlinks in standard directories - - Install for running from DVD - -Other actions: - start installation to HD - help - quit - -Enter command: -\end{boxedverbatim} -\caption{çÌÁ×ÎÏÅ ÍÅÎÀ ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ × ÔÅËÓÔÏ×ÏÍ ÒÅÖÉÍÅ - (\GNU/Linux)}\label{fig:text-main} -\end{figure} - - -\begin{figure}[tb] -\tlpng{install-w32-main}{\linewidth} -\caption{çÌÁ×ÎÏÅ ÍÅÎÀ ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ × ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ - (Windows)}\label{fig:gui-main} -\end{figure} - -\noindent -îÉÖÅ \texttt{>} ÕËÁÚÙ×ÁÅÔ ÓÉÓÔÅÍÎÙÊ ÐÒÏÍÐÔ; ÔÏ, ÞÔÏ ××ÏÄÉÔ -ÐÏÌØÚÏ×ÁÔÅÌØ, ÐÏËÁÚÁÎÏ \Ucom{\texttt{ÖÉÒÎÙÍ ÛÒÉÆÔÏÍ}}. -ïÔËÒÙ× ÔÅÒÍÉÎÁÌØÎÏÅ ÏËÎÏ × àÎÉËÓÅ, ÚÁÐÕÓÔÉÔÅ ÐÒÏÇÒÁÍÍÕ ÕÓÔÁÎÏ×ËÉ: -\begin{alltt} -> \Ucom{cd /path/to/installer} -> \Ucom{perl install-tl} -\end{alltt} -(áÌØÔÅÒÎÁÔÉ×ÎÏ, ×Ù ÍÏÖÅÔÅ ÚÁÐÕÓÔÉÔØ \Ucom{perl - /path/to/installer/install-tl}, ÉÌÉ -\Ucom{./install-tl}, ÅÓÌÉ Õ ÜÔÏÇÏ ÓËÒÉÐÔÁ ÅÓÔØ ÐÒÁ×Á ÎÁ ×ÙÐÏÌÎÅÎÉÅ, É -Ô.Ä. íÙ ÎÅ ÂÕÄÅÍ ÕËÁÚÙ×ÁÔØ ×ÓÅ ÜÔÉ ×ÁÒÉÁÎÔÙ.) - - -äÌÑ ÕÓÔÁÎÏ×ËÉ × ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ (×ÁÍ ÐÏÔÒÅÂÕÅÔÓÑ ÍÏÄÕÌØ -\dirname{Perl/TK}) ÉÓÐÏÌØÚÕÊÔÅ -\begin{alltt} -> \Ucom{perl install-tl -gui} -\end{alltt} - -ðÏÌÎÙÊ ÓÐÉÓÏË ×ÏÚÍÏÖÎÙÈ ÏÐÃÉÊ ÄÁÅÔ ËÏÍÁÎÄÁ -\begin{alltt} -> \Ucom{perl install-tl -help} -\end{alltt} - -\textbf{ðÒÅÄÕÐÒÅÖÄÅÎÉÅ Ï ÐÒÁ×ÁÈ ÄÏÓÔÕÐÁ × àÎÉËÓÅ:} ÓÉÓÔÅÍÁ ÕÓÔÁÎÏ×ËÉ -\TL{} ÉÓÐÏÌØÚÕÅÔ ÔÅËÕÝÅÅ ÚÎÁÞÅÎÉÅ ÐÁÒÁÍÅÔÒÁ \code{umask}. ðÏÜÔÏÍÕ -ÅÓÌÉ ×Ù ÈÏÔÉÔÅ, ÞÔÏÂÙ ÐÏÌÕÞÅÎÎÏÊ ÓÉÓÔÅÍÙ ÍÏÇÌÉ ÐÏÌØÚÏ×ÁÔØÓÑ ÎÅ ÔÏÌØËÏ -×Ù, ÎÏ É ÄÒÕÇÉÅ ÐÏÌØÚÏ×ÁÔÅÌÉ, ×Ù ÄÏÌÖÎÙ ÕÓÔÁÎÏ×ÉÔØ, ÎÁÐÒÉÍÅÒ, \code{ - umask 022}. âÏÌÅÅ ÐÏÄÒÏÂÎÏ \code{umask} ÏÂÓÕÖÄÁÅÔÓÑ × ÄÏËÕÍÅÎÔÁÃÉÉ -Ë ×ÁÛÅÊ ÓÉÓÔÅÍÅ. - -\subsubsection{Mac\,OS\,X} - -ëÁË ÏÔÍÅÞÁÅÔÓÑ × ÒÁÚÄÅÌÅ~\ref{sec:tl-coll-dists}, ÄÌÑ \MacOSX{} -ÓÕÝÅÓÔ×ÕÅÔ ÓÐÅÃÉÁÌØÎÙÊ ÄÉÓÔÒÉÂÕÔÉ×, Mac\TeX{} -(\url{http://tug.org/mactex}). íÙ ÒÅËÏÍÅÎÄÕÅÍ ÐÏÌØÚÏ×ÁÔØÓÑ ÅÇÏ -ÓÉÓÔÅÍÏÊ ÕÓÔÁÎÏ×ËÉ, Á ÎÅ ÏÂÝÉÍ ÓËÒÉÐÔÏÍ \TL{}, ÐÏÓËÏÌØËÕ Õ ÎÅÇÏ ÅÓÔØ -ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ×ÏÚÍÏÖÎÏÓÔÉ, ÓÐÅÃÉÆÉÞÅÓËÉÅ ÄÌÑ íÁËÏ×, ÎÁÐÒÉÍÅÒ, ÕÄÏÂÎÏÅ -ÐÅÒÅËÌÀÞÅÎÉÅ ÍÅÖÄÕ ÒÁÚÌÉÞÎÙÍÉ ÄÉÓÔÒÉÂÕÔÉ×ÁÍÉ \TeX Á ÄÌÑ \MacOSX{} -(Mac\TeX, gw\TeX, Fink, MacPorts, \ldots). - -Mac\TeX{} ÏÓÎÏ×ÁÎ ÎÁ \TL{}, É ÏÓÎÏ×ÎÙÅ ÄÅÒÅ×ØÑ ÄÉÒÅËÔÏÒÉÊ Õ ÎÉÈ -ÓÏ×ÐÁÄÁÀÔ. ïÎ ÄÏÂÁ×ÌÑÅÔ ÎÅÓËÏÌØËÏ ÐÏÄÄÉÒÅËÔÏÒÉÊ Ó ÐÒÏÇÒÁÍÍÁÍÉ É -ÄÏËÕÍÅÎÔÁÃÉÅÊ, ÏÔÎÏÓÑÝÉÍÉÓÑ ÔÏÌØËÏ Ë íÁËÁÍ. - -\subsubsection{Windows} - -åÓÌÉ ×Ù ÕÓÔÁÎÁ×ÌÉ×ÁÅÔÅ ÓÉÓÔÅÍÕ Ó ÓÅÔÉ, ÉÌÉ ÅÓÌÉ ÐÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ Ó -\DVD{} ÎÅ ÓÔÁÒÔÏ×ÁÌÁ Á×ÔÏÍÁÔÉÞÅÓËÉ, Ä×ÁÖÄÙ ÝÅÌËÎÉÔÅ ÐÏ -\filename{install-tl.bat}. - -íÏÖÎÏ ÔÁËÖÅ ÚÁÐÕÓÔÉÔØ ÐÒÏÇÒÁÍÍÕ ÉÚ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ. îÉÖÅ \texttt{>} -ÏÚÎÁÞÁÅÔ ÓÉÓÔÅÍÎÙÊ ÐÒÏÍÐÔ; ÔÏ, ÞÔÏ ××ÏÄÉÔ ÐÏÌØÚÏ×ÁÔÅÌØ, ÕËÁÚÁÎÏ -\Ucom{\texttt{ÖÉÒÎÙÍ ÛÒÉÆÔÏÍ}}. åÓÌÉ ×Ù ÎÁÈÏÄÉÔÅÓØ × ÄÉÒÅËÔÏÒÉÉ -ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ, ÎÁÐÅÞÁÔÁÊÔÅ: -\begin{alltt} -> \Ucom{install-tl} -\end{alltt} - -ðÒÏÇÒÁÍÍÕ ÍÏÖÎÏ ×ÙÚ×ÁÔØ É ÉÚ ÄÒÕÇÏÊ ÄÉÒÅËÔÏÒÉÉ, ÎÁÐÒÉÍÅÒ, -\begin{alltt} -> \Ucom{D:\bs{}texlive\bs{}install-tl} -\end{alltt} -(ÐÒÅÄÐÏÌÁÇÁÅÔÓÑ, ÞÔÏ × \dirname{D:} ÎÁÈÏÄÉÔÓÑ \DVD{} \TK{}). - -äÌÑ ÕÓÔÁÎÏ×ËÉ × ÔÅËÓÔÏ×ÏÍ ÒÅÖÉÍÅ ÉÓÐÏÌØÚÕÊÔÅ -\begin{alltt} -> \Ucom{install-tl -no-gui} -\end{alltt} - - -÷ÓÅ ÏÐÃÉÉ ÐÒÏÇÒÁÍÍÙ ÍÏÖÎÏ ÐÏÌÕÞÉÔØ ÐÒÉ ÐÏÍÏÝÉ ËÏÍÁÎÄÙ -\begin{alltt} -> \Ucom{install-tl -help} -\end{alltt} - -\subsubsection{õÓÔÁÎÏ×ËÁ × ÔÅËÓÔÏ×ÏÍ ÒÅÖÉÍÅ} - -îÁ ÒÉÓÕÎËÅ~\ref{fig:text-main} ÐÏËÁÚÁÎÏ ÏÓÎÏ×ÎÏÅ ÍÅÎÀ ÐÒÏÇÒÁÍÍÙ -ÕÓÔÁÎÏ×ËÉ × ÔÅËÓÔÏ×ÏÍ ÒÅÖÉÍÅ ÄÌÑ àÎÉËÓÁ. - -éÎÔÅÒÆÅÊÓ ÐÒÏÇÒÁÍÍÙ ÄÏ×ÏÌØÎÏ ÐÒÉÍÉÔÉ×ÅÎ: ÐÏÄÄÅÒÖËÉ ËÕÒÓÏÒÁ × ÎÅÍ -ÎÅÔ. îÁÐÒÉÍÅÒ, ÎÅÌØÚÑ ÐÅÒÅÄ×ÉÇÁÔØÓÑ ÐÏ ÐÏÌÑÍ ÐÒÉ ÐÏÍÏÝÉ ËÌÁ×ÉÛÉ -<>. ÷Ù ÐÒÏÓÔÏ ÐÅÞÁÔÁÅÔÅ ÞÔÏ-ÔÏ (ÒÅÇÉÓÔÒ ÕÞÉÔÙ×ÁÅÔÓÑ!) É -ÎÁÖÉÍÁÅÔÅ ËÌÁ×ÉÛÕ <>, ÐÏÓÌÅ ÞÅÇÏ ÐÅÒÅÒÉÓÏ×Ù×ÁÅÔÓÑ ×ÅÓØ ÜËÒÁÎ. - -üÔÏÔ ÉÎÔÅÒÆÅÊÓ ÐÒÉÍÉÔÉ×ÅÎ ÐÏ ÓÌÅÄÕÀÝÅÊ ÐÒÉÞÉÎÅ: ÏÎ ÄÏÌÖÅÎ ÒÁÂÏÔÁÔØ ÎÁ -ËÁË ÍÏÖÎÏ ÂÏÌØÛÅÍ ËÏÌÉÞÅÓÔ×Å ÐÌÁÔÆÏÒÍ, ×ËÌÀÞÁÑ ÔÁËÉÅ, ÇÄÅ ÅÓÔØ ÔÏÌØËÏ -ÕÓÅÞÅÎÎÙÊ ×ÁÒÉÁÎÔ PerlÁ (ÄÌÑ Windows ÔÁËÏÊ ×ÁÒÉÁÎÔ -PerlÁ ×ËÌÀÞÅÎ × ÄÉÓÔÒÉÂÕÔÉ×). - -\subsubsection{õÓÔÁÎÏ×ËÁ × ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ} - -îÁ ÒÉÓÕÎËÅ~\ref{fig:gui-main} ÉÚÏÂÒÁÖÅÎÏ ÍÅÎÀ ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ × -ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ. ïÓÎÏ×ÎÙÅ ÒÁÚÌÉÞÉÑ Ó ÒÉÓÕÎËÏÍ~\ref{fig:text-main} -Ó×ÑÚÁÎÙ Ó ÔÅÍ, ÞÔÏ ÜÔÁ ÐÒÏÇÒÁÍÍÁ ÒÁÂÏÔÁÅÔ ÐÏÄ Windows, Á ÐÒÅÄÙÄÕÝÁÑ -"--- ÐÏÄ GNU/Linux. - -\subsection{òÁÂÏÔÁ ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ} -\label{sec:runinstall} - -íÅÎÀ ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ ÄÏÌÖÎÏ ÂÙÔØ ÐÏÎÑÔÎÏ ÂÅÚ ÏÂßÑÓÎÅÎÉÊ. íÙ ×ÓÅ -ÖÅ ÐÒÉ×ÅÄÅÍ ÎÅÓËÏÌØËÏ ËÒÁÔËÉÈ ÚÁÍÅÞÁÎÉÊ. - -\subsubsection{íÅÎÀ ×ÙÂÏÒÁ ÐÌÁÔÆÏÒÍÙ (ÔÏÌØËÏ ÄÌÑ àÎÉËÓÁ)} -\label{sec:binary} - -\begin{figure}[tbh] -\begin{boxedverbatim} -Available sets of binaries: -==================================================================== - - a [ ] alpha-linux DEC Alpha with GNU/Linux - b [ ] amd64-freebsd x86_64 with FreeBSD - c [ ] hppa-hpux HP-UX - d [ ] i386-freebsd Intel x86 with FreeBSD - e [X] i386-linux Intel x86 with GNU/Linux - f [ ] i386-openbsd Intel x86 with OpenBSD - g [ ] i386-solaris Intel x86 with Sun Solaris - h [ ] mips-irix SGI IRIX - i [ ] powerpc-aix PowerPC with AIX - j [ ] powerpc-linux PowerPC with GNU/Linux - k [ ] sparc-linux Sparc with GNU/Linux - l [ ] sparc-solaris Sparc with Solaris - m [ ] universal-darwin universal binaries for MacOSX/Darwin - o [ ] win32 Windows - p [ ] x86_64-linux x86_64 with GNU/Linux -\end{boxedverbatim} -\caption{íÅÎÀ ×ÙÂÏÒÁ ÐÌÁÔÆÏÒÍÙ}\label{fig:bin-text} -\end{figure} - -îÁ ÒÉÓÕÎËÅ~\ref{fig:bin-text} ÉÚÏÂÒÁÖÅÎÏ ÍÅÎÀ ×ÙÂÏÒÁ ÐÌÁÔÆÏÒÍÙ. ðÏ -ÕÍÏÌÞÁÎÉÀ ÕÓÔÁÎÁ×ÌÉ×ÁÀÔÓÑ ÔÏÌØËÏ ÐÒÏÇÒÁÍÍÙ ÄÌÑ ×ÁÛÅÊ ÔÅËÕÝÅÊ -ÁÒÈÉÔÅËÔÕÒÙ. ÷ ÜÔÏÍ ÍÅÎÀ ×Ù ÍÏÖÅÔÅ ×ÙÂÒÁÔØ ÔÁËÖÅ ÕÓÔÁÎÏ×ËÕ ÐÒÏÇÒÁÍÍ -ÄÌÑ ÄÒÕÇÉÈ ÐÌÁÔÆÏÒÍ. üÔÏ ÍÏÖÅÔ ÂÙÔØ ÐÏÌÅÚÎÏ, ÅÓÌÉ ×Ù ÉÓÐÏÌØÚÕÅÔÅ ÏÄÎÏ -É ÔÏ ÖÅ ÄÅÒÅ×Ï \TeX{}Á ÄÌÑ ÒÁÚÎÙÈ ÍÁÛÉÎ É ÒÁÚÄÁ£ÔÅ ÅÇÏ ÐÏ ÌÏËÁÌØÎÏÊ -ÓÅÔÉ, ÌÉÂÏ ÅÓÌÉ ÎÁ ×ÁÛÅÊ ÍÁÛÉÎÅ ÕÓÔÁÎÏ×ÌÅÎÏ ÎÅÓËÏÌØËÏ ÏÐÅÒÁÃÉÏÎÎÙÈ -ÓÉÓÔÅÍ. - -\subsubsection{÷ÙÂÏÒ ÏÓÎÏ×ÎÙÈ ËÏÍÐÏÎÅÎÔÏ×} -\label{sec:components} - -\begin{figure}[tbh] -\begin{boxedverbatim} -Select a scheme: -==================================================================== - - a [ ] TeX Live basic scheme - b [ ] TeX Live scheme for ConTeXt - c [X] TeX Live full scheme - d [ ] GUST TeX Live scheme - e [ ] GUTenberg TeX Live scheme - f [ ] TeX Live medium scheme - g [ ] TeX Live minimal scheme - h [ ] TeX Live for Omega users - i [ ] teTeX scheme - j [ ] XML typesetting scheme -\end{boxedverbatim} -\caption{÷ÙÂÏÒ ÏÓÎÏ×ÎÙÈ ËÏÍÐÏÎÅÎÔÏ×}\label{fig:scheme-text} -\end{figure} - -îÁ ÒÉÓÕÎËÅ~\ref{fig:scheme-text} ÐÏËÁÚÁÎÏ ÍÅÎÀ ×ÙÂÏÒÁ ÏÓÎÏ×ÎÙÈ -ËÏÍÐÏÎÅÎÔÏ× (ÓÈÅÍ) \TL{}. ÷ ÜÔÏÍ ÍÅÎÀ ×Ù ÍÏÖÅÔÅ ×ÙÂÒÁÔØ <<ÓÈÅÍÕ>>, -Ô.Å. ÎÁÂÏÒ ËÏÌÌÅËÃÉÊ ÐÁËÅÔÏ×. ðÏ ÕÍÏÌÞÁÎÉÀ ÉÓÐÏÌØÚÕÅÔÓÑ ÓÈÅÍÁ -\optname{full}, Ô.Å. ×ÓÅ ÐÁËÅÔÙ \TL{}, ÎÏ ×Ù ÍÏÖÅÔÅ ×ÙÂÒÁÔØ ÓÈÅÍÕ -\optname{basic} ÄÌÑ ÎÅÂÏÌØÛÏÊ ÓÉÓÔÅÍÙ, ÓÈÅÍÕ \optname{minimal} ÄÌÑ -ÔÅÓÔÉÒÏ×ÁÎÉÑ ÉÌÉ ÓÈÅÍÙ \optname{medium} ÉÌÉ \optname{teTeX}. åÓÔØ -ÔÁËÖÅ ÒÑÄ ÓÐÅÃÉÁÌØÎÙÈ ÓÈÅÍ, × ÔÏÍ ÞÉÓÌÅ É ÐÒÅÄÎÁÚÎÁÞÅÎÎÙÈ ÄÌÑ -ÒÁÚÌÉÞÎÙÈ ÓÔÒÁÎ. - -\begin{figure}[tbh] -\tlpng{stdcoll}{.7\linewidth} -\caption{íÅÎÀ ËÏÌÌÅËÃÉÊ (ìÉÎÕËÓ)}\label{fig:collections-gui} -\end{figure} - -÷Ù ÍÏÖÅÔÅ ÕÔÏÞÎÉÔØ ×ÁÛ ×ÙÂÏÒ ÐÒÉ ÐÏÍÏÝÉ ÍÅÎÀ <<ËÏÌÌÅËÃÉÊ>> -(ÒÉÓÕÎÏË~\ref{fig:collections-gui}, ÄÌÑ ÒÁÚÎÏÏÂÒÁÚÉÑ ÓÄÅÌÁÎÎÙÊ × -ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ). - -ëÏÌÌÅËÃÉÉ ÐÒÅÄÓÔÁ×ÌÑÀÔ ÓÏÂÏÊ ÓÌÅÄÕÀÝÉÊ ÐÏÓÌÅ ÓÈÅÍ ÕÒÏ×ÅÎØ -ÉÅÒÁÒÈÉÉ \TL{}. çÒÕÂÏ ÇÏ×ÏÒÑ, ÓÈÅÍÙ ÓÏÓÔÏÑÔ ÉÚ ËÏÌÌÅËÃÉÊ, ËÏÌÌÅËÃÉÉ -ÓÏÓÔÏÑÔ ÉÚ ÐÁËÅÔÏ×, Á ÐÁËÅÔÙ (ÎÉÖÎÉÊ ÕÒÏ×ÅÎØ ÉÅÒÁÒÈÉÉ \TL{}) ÓÏÄÅÒÖÁÔ -ÍÁËÒÏÓÙ, ÛÒÉÆÔÙ É Ô.Ä. - -åÓÌÉ ×Ù ÈÏÔÉÔÅ ÂÏÌÅÅ ÔÏÎËÏÊ ÎÁÓÔÒÏÊËÉ, ÞÅÍ ×ÏÚÍÏÖÎÁ × ÍÅÎÀ ËÏÌÌÅËÃÉÊ, -×Ù ÍÏÖÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ ÐÒÏÇÒÁÍÍÕ \prog{tlmgr} ÐÏÓÌÅ ÕÓÔÁÎÏ×ËÉ -(ÓÍ. ÒÁÚÄÅÌ~\ref{sec:tlmgr}). üÔÁ ÐÒÏÇÒÁÍÍÁ ÐÏÚ×ÏÌÑÅÔ ÕÓÔÁÎÁ×ÌÉ×ÁÔØ -ÉÌÉ ÕÄÁÌÑÔØ ÏÔÄÅÌØÎÙÅ ÐÁËÅÔÙ. - -\subsubsection{äÉÒÅËÔÏÒÉÉ} -\label{sec:directories} - -óÈÅÍÁ ÄÉÒÅËÔÏÒÉÊ ÐÏ ÕÍÏÌÞÁÎÉÀ ÏÐÉÓÁÎÁ × ÒÁÚÄÅÌÅ~\ref{sec:texmftrees}, -\p.\pageref{sec:texmftrees}. ðÏÌÏÖÅÎÉÅ ÄÅÒÅ×Á -\dirname{TEXDIR} ÏÔÌÉÞÁÅÔÓÑ ÄÌÑ Windows -(|%PROGRAMFILES%\texlive\2008|) É àÎÉËÓÁ -(\dirname{/usr/local/texlive/2008}). - -ïÓÎÏ×ÎÁÑ ÐÒÉÞÉÎÁ, ÐÏ ËÏÔÏÒÏÊ ÂÙ×ÁÅÔ ÎÅÏÂÈÏÄÉÍÏ ÉÚÍÅÎÉÔØ ÜÔÕ ÓÈÅÍÕ -"--- ÏÔÓÕÔÓÔ×ÉÅ Õ ×ÁÓ ÐÒÁ× ÎÁ ÚÁÐÉÓØ × ÎÕÖÎÙÅ ÄÉÒÅËÔÏÒÉÉ. ÷ÁÍ ÎÅ -ÎÁÄÏ ÉÍÅÔØ ÐÒÁ×Á ÁÄÍÉÎÉÓÔÒÁÔÏÒÁ ÄÌÑ ÕÓÔÁÎÏ×ËÉ \TL{}, ÏÄÎÁËÏ ×ÁÍ ÎÁÄÏ -ÉÍÅÔØ ÐÒÁ×Ï ÐÉÓÁÔØ × ÄÉÒÅËÔÏÒÉÀ, ËÕÄÁ ÕÓÔÁÎÁ×ÌÉ×ÁÅÔÓÑ ÓÉÓÔÅÍÁ. - -åÓÌÉ Õ ×ÁÓ ÎÅÔ ÐÒÁ×Á ÎÁ ÚÁÐÉÓØ × ÓÉÓÔÅÍÎÙÅ ÄÉÒÅËÔÏÒÉÉ, ÅÓÔÅÓÔ×ÅÎÎÏÊ -ÁÌØÔÅÒÎÁÔÉ×ÏÊ Ñ×ÌÑÅÔÓÑ ÕÓÔÁÎÏ×ËÁ × ×ÁÛÕ ÄÏÍÁÛÎÀÀ ÄÉÒÅËÔÏÒÉÀ, ÏÓÏÂÅÎÎÏ -ÅÓÌÉ ×Ù ÂÕÄÅÔÅ ÅÄÉÎÓÔ×ÅÎÎÙÍ ÐÏÌØÚÏ×ÁÔÅÌÅÍ ÓÉÓÔÅÍÙ. äÌÑ ÜÔÏÇÏ -ÉÓÐÏÌØÚÕÊÔÅ `|~|' ÎÁÐÒÉÍÅÒ `|~/texlive/2008|'. - -íÙ ÒÅËÏÍÅÎÄÕÅÍ ×ËÌÀÞÁÔØ ÎÏÍÅÒ ÇÏÄÁ × ÎÁÚ×ÁÎÉÅ ÄÉÒÅËÔÏÒÉÉ, ÞÔÏÂÙ ÍÏÖÎÏ -ÂÙÌÏ ÄÅÒÖÁÔØ ÏÔÄÅÌØÎÏ ÒÁÚÎÙÅ ×ÅÒÓÉÉ \TL{}. ðÏÓÌÅ ÔÅÓÔÉÒÏ×ÁÎÉÑ ÎÏ×ÏÊ -×ÅÒÓÉÉ ×Ù ÓÍÏÖÅÔÅ ÓÄÅÌÁÔØ \dirname{/usr/local/texlive-cur} ÓÓÙÌËÏÊ ÎÁ -ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÕÀ ÄÉÒÅËÔÏÒÉÀ. - -éÚÍÅÎÅÎÉÅ \dirname{TEXDIR} ÉÚÍÅÎÉÔ ÔÁËÖÅ \dirname{TEXMFLOCAL}, -\dirname{TEXMFSYSVAR} É \dirname{TEXMFSYSCONFIG}. - -ìÉÞÎÙÅ ÐÁËÅÔÙ É ÆÁÊÌÙ ÒÅËÏÍÅÎÄÕÅÔÓÑ ÄÅÒÖÁÔØ × ÄÉÒÅËÔÏÒÉÉ -\dirname{TEXMFHOME}. ðÏ ÕÍÏÌÞÁÎÉÀ ÜÔÏ |~/texmf|. ÷ ÏÔÌÉÞÉÅ ÏÔ -\dirname{TEXDIR}, ÚÄÅÓØ |~| ÂÕÄÅÔ Ó×ÏÉÍ ÄÌÑ ËÁÖÄÏÇÏ ÐÏÌØÚÏ×ÁÔÅÌÑ. -üÔÁ ÐÅÒÅÍÅÎÎÁÑ ÓÔÁÎÏ×ÉÔÓÑ \dirname{$HOME} ÐÏÄ àÎÉËÓÏÍ É -\verb|%USERPROFILE%| ÐÏÄ Windows. - -\subsubsection{ïÐÃÉÉ} -\label{sec:options} - -\begin{figure}[tbh] -\begin{boxedverbatim} -

use letter size instead of A4 by default: [ ] - create all format files: [X] - install font/macro doc tree: [X] - install font/macro source tree: [X] - create symlinks in standard directories: [ ] - binaries to: - manpages to: - info to: -\end{boxedverbatim} -\caption{íÅÎÀ ÏÐÃÉÊ (Unix)}\label{fig:options-text} -\end{figure} - -îÁ ÒÉÓÕÎËÅ~\ref{fig:options-text} ÐÒÉ×ÅÄÅÎÏ ÍÅÎÀ ÏÐÃÉÊ (ÔÅËÓÔÏ×ÙÊ -ÒÅÖÉÍ). óÔÏÉÔ ÕÐÏÍÑÎÕÔØ ÔÒÉ ÉÚ ÎÉÈ: -\begin{description} -\item[use letter size instead of A4 by default (ÉÓÐÏÌØÚÏ×ÁÔØ ÐÏ - ÕÍÏÌÏÞÁÎÉÀ ÒÁÚÍÅÒ letter ×ÍÅÓÔÏ A4):] ×ÙÂÏÒ ÒÁÚÍÅÒÁ ÂÕÍÁÇÉ - ÐÏ ÕÍÏÌÞÁÎÉÀ. òÁÚÕÍÅÅÔÓÑ, ÏÔÄÅÌØÎÙÅ ÄÏËÕÍÅÎÔÙ ÍÏÇÕÔ ÐÒÉ - ÎÅÏÂÈÏÄÉÏÓÔÉ ÕËÁÚÁÔØ ÓÏÂÓÔ×ÅÎÎÙÊ ÒÁÚÍÅÒ ÂÕÍÁÇÉ. - -\item[create all format files (ÓÏÚÁÔØ ×ÓÅ ÆÏÒÍÁÔÙ):] èÏÔÑ ÎÅÎÕÖÎÙÅ ÆÏÒÍÁÔÙ ÚÁÎÉÍÁÀÔ ÍÅÓÔÏ - ÎÁ ÄÉÓËÅ É ÔÒÅÂÕÀÔ ×ÒÅÍÅÎÉ ÄÌÑ ÓÏÚÄÁÎÉÑ, ÍÙ ×ÓÅ ÖÅ ÒÅËÏÍÅÎÄÕÅÍ ÎÅ - ÉÚÍÅÎÑÔØ ÜÔÕ ÏÐÃÉÀ. ÷ ÐÒÏÔÉ×ÎÏÍ ÓÌÕÞÁÅ ÏÔÓÕÔÓÔ×ÕÀÝÉÅ ÆÏÒÍÁÔÙ ÂÕÄÕÔ ÇÅÎÒÉÒÏ×ÁÔØÓÑ - × ÄÉÒÅËÔÏÒÉÑÈ \dirname{TEXMFVAR} ÄÌÑ ËÁÖÄÏÇÏ ÐÏÌØÚÏ×ÁÔÅÌÑ. ïÎÉ ÎÅ - ÂÕÄÕÔ Á×ÔÏÍÁÔÉÞÅÓËÉ ÐÅÒÅÇÅÎÅÒÉÒÏ×ÁÔØÓÑ ÐÒÉ ÉÚÍÅÎÅÎÉÉ ÐÒÏÇÒÁÍÍ É ÓÈÅÍ - ÐÅÒÅÎÏÓÁ, É × ÉÔÏÇÅ ÍÏÇÕÔ ÏËÁÚÁÔØÓÑ ÎÅÓÏ×ÍÅÓÔÉÍÙÍÉ Ó ÎÏ×ÏÊ - ÓÉÓÔÅÍÏÊ. - -\item[create symlinks in standard directories (ÓÏÚÄÁÔØ ÓÉÍÌÉÎËÉ × - ÓÔÁÎÄÁÒÔÎÙÈ ÄÉÒÅËÔÏÒÉÑÈ)] (ÔÏÌØËÏ ÄÌÑ àÎÉËÓÁ): üÔÁ ÏÐÃÉÑ ÄÅÌÁÅÔ - ÎÅÎÕÖÎÏÊ ÓÍÅÎÕ ÐÅÒÅÍÅÎÎÙÈ ÏËÒÕÖÅÎÉÑ. âÅÚ ÎÅ£ ÄÉÒÅËÔÏÒÉÉ \TL{} ÎÕÖÎÏ - ÄÏÂÁ×ÉÔØ Ë \envname{PATH}, \envname{MANPATH} É \envname{INFOPATH}. - äÌÑ ÜÔÏÊ ÏÐÃÉÉ ×ÁÍ ÎÕÖÎÙ ÐÒÁ×Á ÎÁ ÚÁÐÉÓØ × ÓÔÁÎÄÁÒÔÎÙÅ ÄÉÒÅËÔÏÒÉÉ. - íÙ ÎÅ ÓÏ×ÅÔÕÅÍ ×ÁÍ ÐÏÄÍÅÎÑÔØ \TeX{} ÉÚ ÄÉÓÔÒÉÂÕÔÉ×Á ×ÁÛÅÊ ÓÉÓÔÅÍÙ - ÐÒÉ ÐÏÍÏÝÉ ÜÔÏÊ ÏÐÃÉÉ. ïÎÁ ÎÕÖÎÁ ÄÌÑ ÓÏÚÄÁÎÉÑ ÓÉÍÌÉÎËÏ× × - ÄÉÒÅËÔÏÒÉÑÈ ÔÉÐÁ \dirname{/usr/local/bin}, ËÏÔÏÒÙÅ ÎÅ ÓÏÄÅÒÖÁÔ - ÆÁÊÌÏ× \TeX Á ÉÚ ÓÉÓÔÅÍÎÏÇÏ ÄÉÓÔÒÉÂÕÔÉ×Á. -\end{description} - -úÁÄÁ× ÎÕÖÎÙÅ ÎÁÓÔÒÏÊËÉ, ×Ù ÍÏÖÅÔÅ ÎÁÞÁÔØ ÕÓÔÁÎÏ×ËÕ ÓÉÓÔÅÍÙ, ÎÁÖÁ× -ËÌÁ×ÉÛÕ <<|I|>>. ëÏÇÄÁ ÕÓÔÁÎÏ×ËÁ ÚÁËÏÎÞÅÎÁ, ÐÅÒÅÊÄÉÔÅ Ë -ÒÁÚÄÅÌÕ~\ref{sec:postinstall}. - -\subsubsection{îÁÓÔÒÏÊËÁ ÄÌÑ ÒÁÂÏÔÙ Ó DVD{} (ÔÏÌØËÏ ÔÅËÓÔÏ×ÙÊ ÒÅÖÉÍ)} -\label{sec:fromdvd} - -äÌÑ ×ÙÂÏÒÁ ÜÔÏÊ ÏÐÃÉÉ ÎÁÖÍÉÔÅ ËÌÁ×ÉÛÕ <<|V|>>. ïÓÎÏ×ÎÏÅ ÍÅÎÀ ÓÔÁÎÅÔ -ÔÁËÉÍ, ËÁË ÎÁ ÒÉÓÕÎËÅ~\ref{fig:main-fromdvd}. -\begin{figure}[tbh] -\begin{boxedverbatim} -======================> TeX Live installation procedure <===================== - -=======> Note: Letters/digits in indicate menu items <======= -=======> for commands or configurable options <======= - - directories: - TEXDIRW (Writable root): - !! default location: /usr/local/texlive/2008 - !! is not writable, please select a different one! - TEXMFLOCAL (directory for site-wide local files): - /usr/local/texlive/texmf-local - TEXMFSYSVAR (directory for variable and automatically generated data): - /usr/local/texlive/2008/texmf-var - TEXMFSYSCONFIG (directory for local config): - /usr/local/texlive/2008/texmf-config - TEXMFHOME (directory for user-specific files): - ~/texmf - - options: - [ ] use letter size instead of A4 by default - [X] create all format files - - set up for installing to hard disk - -Other actions: - start installation for running from DVD - help - quit -\end{boxedverbatim} -\caption{ïÓÎÏ×ÎÏÅ ÍÅÎÀ ÐÏÓÌÅ ×ÙÂÏÒÁ ÏÐÃÉÉ \optname{from - DVD}}\label{fig:main-fromdvd} -\end{figure} - -ïÂÒÁÔÉÔÅ ×ÎÉÍÁÎÉÅ ÎÁ ÉÚÍÅÎÅÎÉÑ: ÉÓÞÅÚÌÉ ×ÓÅ ÏÐÃÉÉ ×ÙÂÏÒÁ, ÞÔÏ -ÕÓÔÁÎÁ×ÌÉ×ÁÔØ, Á ÍÅÎÀ ÄÉÒÅËÔÏÒÉÊ ÇÏ×ÏÒÉÔ ÔÅÐÅÒØ Ï \dirname{TEXDIRW}, -Ô.Å. ÞÁÓÔÉ ÄÅÒÅ×Á ÎÁ ÌÏËÁÌØÎÏÍ ÄÉÓËÅ. ïÐÃÉÑ ÓÏÚÄÁÎÉÑ ÓÉÍÌÉÎËÏ× ÔÁËÖÅ -ÉÓÞÅÚÌÁ. - -ðÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ ÓÏÚÄÁÓÔ ÒÁÚÌÉÞÎÙÅ ÄÉÒÅËÔÏÒÉÉ É ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ -ÆÁÊÌÙ, ÎÏ ÎÅ ÂÕÄÅÔ ËÏÐÉÒÏ×ÁÔØ ÎÁ ÄÉÓË ËÏÍÐØÀÔÅÒÁ \dirname{texmf}, -\dirname{texmf-dist} ÉÌÉ \dirname{texmf-doc}. - -äÅÊÓÔ×ÉÑ ÐÏÓÌÅ ÕÓÔÁÎÏ×ËÉ ÄÌÑ àÎÉËÓÁ ÂÕÄÕÔ ÞÕÔØ ÓÌÏÖÎÅÅ, ÞÅÍ × -ÐÒÅÄÙÄÕÝÅÍ ÓÌÕÞÁÅ, ÐÏÓËÏÌØËÕ ÒÁÓÐÏÌÏÖÅÎÉÅ ÄÉÒÅËÔÏÒÉÊ ÔÅÐÅÒØ ÏÔÌÉÞÁÅÔÓÑ -ÏÔ ÓÔÁÎÄÁÒÔÎÏÇÏ; ÓÍ. ÒÁÚÄÅÌ~\ref{sec:postinstall}. - -éÚ-ÚÁ ÎÅÄÏÓÔÁÔËÁ ×ÒÅÍÅÎÉ ÜÔÏÊ ÏÐÃÉÉ ÐÏËÁ ÎÅÔ × ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ, ÎÏ -ÏÎÁ ÄÏÓÔÕÐÎÁ É ÄÌÑ àÎÉËÓÁ, É ÄÌÑ Wiindows. ðÏÌØÚÏ×ÁÔÅÌÑÍ Windows -ÐÒÉÄÅÔÓÑ ÚÁÐÕÓÔÉÔØ ÐÒÏÇÒÁÍÍÕ ÕÓÔÁÎÏ×ËÉ ÉÚ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ, -ÓÍ. ÒÁÚÄÅÌ~\ref{sec:cmdline}. - -÷ ÒÁÚÄÅÌÅ~\ref{sec:portable-unix} ÏÐÉÓÁÎ ÄÒÕÇÏÊ ÓÐÏÓÏ ÚÁÐÕÓËÁ \TL{} Ó -ÄÉÓËÁ, ËÏÔÏÒÙÊ ÎÅ ÔÒÅÂÕÅÔ ÉÚÍÅÎÅÎÉÊ × ËÏÎÆÉÇÕÒÁÃÉÉ ÓÉÓÔÅÍÙ "--- ÎÏ É -ÎÅ ÐÏÚ×ÏÌÑÅÔ ÎÁÓÔÒÁÉ×ÁÔØ \TL{}. - -\subsection{ïÐÃÉÉ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ} -\label{sec:cmdline} - -îÁÐÅÞÁÔÁÊÔÅ -\begin{alltt} -> \Ucom{install-tl -help} -\end{alltt} -ÞÔÏÂÙ ÐÏÌÕÞÉÔØ ÓÐÉÓÏË ÏÐÃÉÊ ËÏÍÁÄÎÏÊ ÓÔÒÏËÉ. ÷ ÏÐÃÉÑÈ ÍÏÖÎÏ -ÉÓÐÏÌØÚÏ×ÁÔØ ËÁË |-|, ÔÁË É |--|. ÷ÏÔ ÓÁÍÙÅ ÉÎÔÅÒÅÓÎÙÅ ÏÐÃÉÉ: - -\begin{ttdescription} -\item[-gui] åÓÌÉ ×ÏÚÍÏÖÎÏ, ÉÓÐÏÌØÚÏ×ÁÔØ ÇÒÁÇÉÞÅÓËÉÊ ÒÅÖÉÍ. äÌÑ ÜÔÏÇÏ - ÎÕÖÅÎ ÍÏÄÕÌØ Perl/Tk (\url{http://tug.org/texlive/distro.html#perltk}); - ÅÓÌÉ ÜÔÏÇÏ ÍÏÄÕÌÑ × ÓÉÓÔÅÍÅ ÎÅÔ, ÕÓÔÁÎÏ×ËÁ ÐÒÏÉÓÈÏÄÉÔ × ÔÅËÓÔÏ×ÏÍ - ÒÅÖÉÍÅ. -\item[-no-gui] éÓÐÏÌØÚÏ×ÁÔØ ÔÅËÓÔÏ×ÙÊ ÒÅÖÉÍ, ÄÁÖÅ ÐÏÄ Windows. ÷ÁÍ - ÐÏÎÁÄÏÂÉÔÓÑ ÜÔÁ ÏÐÃÉÑ, ÅÓÌÉ ×Ù ÈÏÔÉÔÅ ÚÁÐÕÓËÁÔØ \TL{} Ó \DVD{}, - ÐÏÓËÏÌØËÕ ÜÔÏ ÐÏËÁ ÎÅ×ÏÚÍÏÖÎÏ × ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ. -\item[-lang {\sl LL}] úÁÄÁÔØ ÑÚÙË ÉÎÔÅÒÆÅÊÓÁ ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ - (ÓÔÁÎÄÁÒÔÎÙÍ ËÏÄÏÍ ÓÔÒÁÎÙ \textsl{LL}). óÅÊÞÁÓ ÄÏÓÔÕÐÎÙ ÓÌÅÄÕÀÝÉÅ ÑÚÙËÉ: - ÁÎÇÌÉÊÓËÉÊ (\texttt{en}, ÚÎÁÞÅÎÉÅ ÐÏ ÕÍÏÌÞÁÎÉÀ), ÎÅÍÅÃËÉÊ - (\texttt{de}), ÆÒÁÎÃÕÚÓËÉÊ (\texttt{fr}), ÇÏÌÌÁÎÄÓËÉÊ (\texttt{nl}), ÐÏÌØÓËÉÊ - (\texttt{pl}), ÓÌÏ×ÅÎÓËÉÊ (\texttt{sl}) É ×ØÅÔÎÁÍÓËÉÊ - (\texttt{vi}). ðÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ ÐÙÔÁÅÔÓÑ ÏÐÒÅÄÅÌÅÔØ ÎÕÖÎÙÊ ÑÚÙË - Á×ÔÏÍÁÔÉÞÅÓËÉ, ÎÏ ÅÓÌÉ ÜÔÏ ÎÅ ÐÏÌÕÞÁÅÔÓÑ ÉÌÉ ÅÓÌÉ ÎÕÖÎÙÊ ÑÚÙË ÎÅ - ÐÏÄÄÅÒÖÉ×ÁÅÔÓÑ, ÏÎÁ ÐÅÒÅÈÏÄÉÔ ÎÁ ÁÎÇÌÉÊÓËÉÊ. -\item[-profile {\sl profile}] ðÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ ×ÓÅÇÄÁ ÚÁÐÉÓÙ×ÁÅÔ ÆÁÊÌ - \filename{texlive.profile} × ÐÏÄÄÉÒÅËÔÏÒÉÀ \dirname{2008/tlpkg} ÉÌÉ - \dirname{tlpkg}. üÔÁ ÏÐÃÉÑ ÚÁÓÔÁ×ÌÑÅÔ ÐÒÏÇÒÁÍÍÕ ÉÓÐÏÌØÚÏ×ÁÔØ ÜÔÏÔ - ÆÁÊÌ. ÷ÏÔ ÐÒÉÍÅÒ ÔÁËÏÇÏ ÆÁÊÌÁ: - \begin{fverbatim} -# texlive.profile written on Wed Jul 9 16:13:44 2008 UTC -# It will NOT be updated and reflects only the -# installation profile at installation time. -selected_scheme scheme-basic -TEXDIR /usr/local/texlive/2008 -TEXDIRW /usr/local/texlive/2008 -... -TEXMFSYSVAR /usr/local/texlive/2008/texmf-var -collection-basic 1 -... -option_symlinks 0 - \end{fverbatim} - ðÒÉ ÐÏÍÏÝÉ ÜÔÏÊ ÏÐÃÉÉ ×Ù ÍÏÖÅÔÅ ÕÓÔÁÎÁ×ÌÉ×ÁÔØ \TL{} ÎÁ ÎÅÓËÏÌØËÉÈ - ÍÁÛÉÎÁÈ Ó ÏÄÎÉÍÉ É ÔÅÍÉ ÖÅ ÐÁÒÁÍÅÔÒÁÍÉ. -\item [-location {\sl url/path}] õËÁÚÁÔØ ÁÌØÔÅÒÎÁÔÉ×ÎÙÊ ÉÓÔÏÞÎÉË - ÐÁËÅÔÏ×; ÓÍ. ÎÉÖÅ. -\end{ttdescription} - -\subsubsection{ðÁÒÁÍÅÔÒ \optname{location}} -\label{sec:location} - -úÎÁÞÅÎÉÅ ÜÔÏÇÏ ÐÁÒÁÍÅÔÒÁ ÍÏÖÅÔ ÂÙÔØ URL, ÎÁÞÉÎÁÀÝÉÓÑ Ó \texttt{ftp:}, -\texttt{http:}, \texttt{file:/} ÉÌÉ ÄÉÒÅËÔÏÒÉÑ ÎÁ ÄÉÓËÅ. åÓÌÉ -ÁÒÇÕÍÅÎÔ ÚÁÄÁÅÔ ÄÉÒÅËÔÏÒÉÀ ÎÁ ÄÉÓËÉ (ÐÒÑÍÏ ÉÌÉ ÐÒÉ ÐÏÍÏÝÉ -\texttt{file:/}), ÓÉÓÔÅÍÁ Á×ÔÏÍÁÔÉÞÅÓËÉ ÏÐÒÅÄÅÌÑÅÔ, Ñ×ÌÑÅÔÓÑ ÌÉ -ÉÓÔÏÞÎÉË ÁÒÈÉ×ÏÍ: ÅÓÌÉ ÎÁÊÄÅÎÁ ÐÏÄÄÉÒÅËÔÏÒÉÑ \dirname{archive} Ó -ÆÁÊÌÁÍÉ \filename{.tar.lzma}, ÔÏ ÏÎÁ ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÎÁ, ÄÁÖÅ ÅÓÌÉ -ÒÑÄÏÍ ÎÁÈÏÄÑÔÓÑ ÎÅÚÁÁÒÈÉ×ÉÒÏ×ÁÎÎÙÅ ÆÁÊÌÙ. - -åÓÌÉ ÐÁÒÁÍÅÔÒ ÎÁÞÉÎÁÅÔÓÑ Ó \texttt{http:} ÉÌÉ \texttt{ftp:}, ÔÏ ÓÉÍ×ÏÌ -\texttt{/} ÉÌÉ ÄÉÒÅËÔÏÒÉÑ \texttt{/tlpkg} × ËÏÎÃÅ ÐÁÒÁÍÅÔÒÁ -ÉÇÎÏÒÉÒÕÀÔÓÑ. îÁÐÒÉÍÅÒ, ×Ù ÍÏÖÅÔÅ ÚÁÄÁÔØ × ËÁÞÅÓÔ×Å ÐÁÒÁÍÅÔÒÁ ÚÅÒËÁÌÏ -\CTAN{}: -\url{http://ctan.example.org/tex-archive/texlive/tlnet/2008}. -òÁÚÕÍÅÅÔÓÑ, ×ÁÍ ÓÌÅÄÕÅÔ ÐÏÄÓÔÁ×ÉÔØ ×ÍÅÓÔÏ \dirname{example.ctan.org} -ÎÕÖÎÏÅ ÚÅÒËÁÌÏ É ÐÕÔØ Ë ÁÒÈÉ×Õ ÎÁ ÜÔÏÍ ÚÅÒËÁÌÅ (ÓÐÉÓÏË ÚÅÒËÁÌ -ÎÁÈÏÄÉÔÓÑ ÎÁ \url{http://mirror.ctan.org}). ðÏ ÕÍÏÌÞÁÎÉÀ ÚÅÒËÁÌÏ -ÏÐÒÅÄÅÌÑÅÔÓÑ Á×ÔÏÍÁÔÉÞÅÓËÉ ÉÚ ÓÐÉÓËÁ ÎÁ \url{http://mirror.ctan.org}; -× ÌÀÂÏÍ ÓÌÕÞÁÅ ×ÙÂÒÁÎÎÏÅ ÚÅÒËÁÌÏ ÉÓÐÏÌØÚÕÅÔÓÑ ÄÌÑ ×ÓÅÊ ÕÓÔÁÎÏ×ËÉ. - - -\subsection{äÅÊÓÔ×ÉÑ ÐÏÓÌÅ ÕÓÔÁÎÏ×ËÉ} -\label{sec:postinstall} - -éÎÏÇÄÁ ÐÏÓÌÅ ÕÓÔÁÎÏ×ËÉ ÓÉÓÔÅÍÙ ÔÒÅÂÕÀÔÓÑ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ÄÅÊÓÔ×ÉÑ. - -\subsubsection{Windows} - -ðÏÄ Windows ÐÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ ÓÁÍÁ ÄÅÌÁÅÔ ×ÓÅ ÎÅÏÂÈÏÄÉÍÏÅ. - -\subsubsection{åÓÌÉ ÓÏÚÄÁÎÙ ÓÉÍÌÉÎËÉ} - -åÓÌÉ ×Ù ÒÅÛÉÌÉ ÓÏÚÄÁÔØ ÓÉÍÌÉÎËÉ × ÓÔÁÎÄÁÒÔÎÙÈ ÄÉÒÅËÔÏÒÉÑÈ -(ÓÍ. ÒÁÚÄÅÌ~\ref{sec:options}), ÔÏ ÍÅÎÑÔØ ÐÅÒÅÍÅÎÎÙÅ ÏËÒÕÖÅÎÉÑ ÎÅ -ÎÕÖÎÏ. - -\subsubsection{ðÅÒÅÍÅÎÎÙÅ ÏËÒÕÖÅÎÉÑ ÄÌÑ àÎÉËÓÁ} -\label{sec:env} - -äÉÒÅËÔÏÒÉÑ Ó ÐÒÏÇÒÁÍÍÁÍÉ ÄÌÑ ×ÁÛÅÊ ÐÌÁÔÆÏÒÍÙ ÄÏÌÖÎÁ ÂÙÔØ ÄÏÂÁ×ÌÅÎÁ Ë -ÐÕÔÉ ÐÏÉÓËÁ. ðÒÏÇÒÁÍÍÙ ÄÌÑ ËÁÖÄÏÊ ÁÒÈÉÔÅËÔÕÒÙ ÐÏÍÅÝÁÀÔÓÑ × -ÓÏÂÓÔ×ÅÎÎÕÀ ÐÏÄÄÉÒÅËÔÏÒÉÀ ÐÏÄ \dirname{TEXDIR/bin}. óÍ. ÓÐÉÓÏË -ÐÏÄÄÉÒÅËÔÏÒÉÊ É ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÈ ÐÌÁÔÆÏÒÍ ÎÁ -ÒÉÓÕÎËÅ~\ref{fig:bin-text}. - -÷Ù ÍÏÖÅÔÅ ÔÁËÖÅ ÄÏÂÁ×ÉÔØ ÄÉÒÅËÔÏÒÉÉ Ó ÄÏËÕÍÅÎÔÁÃÉÅÊ × ÆÏÒÍÁÔÅ man É -info Ë ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÍ ÐÕÔÑÍ ÐÏÉÓËÁ, ÅÓÌÉ ×Ù ÈÏÔÉÔÅ, ÞÔÏÂÙ ×ÁÛÁ -ÏÐÅÒÁÃÉÏÎÎÁÑ ÓÉÓÔÅÍÁ ÚÎÁÌÁ Ï ÎÉÈ. - -îÉÖÅ ÍÙ ÉÓÐÏÌØÚÕÅÍ ÄÌÑ ÐÒÉÍÅÒÁ ÓÔÁÎÄÁÒÔÎÕÀ ÓÉÓÔÅÍÕ ÄÉÒÅËÔÏÒÉÊ × ÓÉÓÔÅÍÅ -Intel86 GNU/Linux. - -äÌÑ ÏÂÏÌÏÞÅË ÔÉÐÁ Bourne (\prog{bash} É Ô.Ð.) ×Ù ÍÏÖÅÔÅ ÄÏÂÁ×ÉÔØ × -ÆÁÊÌ \filename{$HOME/.profile} (ÉÌÉ × ÆÁÊÌ, ËÏÔÏÒÙÊ ×ÙÚÙ×ÁÅÔÓÑ ÉÚ -\filename{.profile}) ÓÌÅÄÕÀÝÅÅ: - -\begin{sverbatim} -PATH=/usr/local/texlive/2008/bin/i386-linux:$PATH; export PATH -MANPATH=/usr/local/texlive/2008/texmf/doc/man:$MANPATH; export MANPATH -INFOPATH=/usr/local/texlive/2008/texmf/doc/info:$INFOPATH; export INFOPATH -\end{sverbatim} - -äÌÑ \prog{csh} ÉÌÉ \prog{tcsh} ÓÌÅÄÕÅÔ ÒÅÄÁËÔÉÒÏ×ÁÔØ ÆÁÊÌ -\filename{$HOME/.cshrc}, É ÓÌÅÄÕÅÔ ÄÏÂÁ×ÉÔØ ÞÔÏ-ÔÏ ×ÒÏÄÅ - -\begin{sverbatim} -setenv PATH /usr/local/texlive/2008/bin/i386-linux:$PATH -setenv MANPATH /usr/local/texlive/2008/texmf/doc/man:$MANPATH -setenv INFOPATH /usr/local/texlive/2008/texmf/doc/info:$INFOPATH -\end{sverbatim} - -òÁÚÕÍÅÅÔÓÑ, × ×ÁÛÉÈ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÈ ÆÁÊÌÁÈ ÕÖÅ ÍÏÇÕÔ ÂÙÔØ ÏÐÒÅÄÅÌÅÎÙ -ÜÔÉ ÐÅÒÅÍÅÎÎÙÅ; ÆÒÁÇÍÅÎÔÙ ×ÙÛÅ ÄÏÂÁ×ÌÑÀÔ Ë ÎÉÍ ÄÉÒÅËÔÏÒÉÉ \TL{}. - -\subsubsection{ðÅÒÅÍÅÎÎÙÅ ÏËÒÕÖÅÎÉÑ: ÇÌÏÂÁÌØÎÁÑ ËÏÎÆÉÇÕÒÁÃÉÑ} -\label{sec:envglobal} - -åÓÌÉ ×Ù ÈÏÔÉÔÅ ×ÎÅÓÔÉ ÜÔÉ ÉÚÍÅÎÅÎÉÑ ÄÌÑ ×ÓÅÈ ÐÏÌØÚÏ×ÁÔÅÌÅÊ, ÉÌÉ -ÄÏÂÁ×ÌÑÔØ ÉÈ Á×ÔÏÍÁÔÉÞÅÓËÉ ÄÌÑ ÎÏ×ÙÈ ÐÏÌØÚÏ×ÁÔÅÌÅÊ, ÔÏ ×ÁÍ ÓÌÅÄÕÅÔ -ÒÁÚÏÂÒÁÔØÓÑ ÓÁÍÏÍÕ: × ÒÁÚÎÙÈ ÓÉÓÔÅÍÁÈ ÜÔÏ ÄÅÌÁÅÔÓÑ ÓÌÉÛËÏÍ -ÐÏ-ÒÁÚÎÏÍÕ. - -ä×Á ÓÏ×ÅÔÁ: 1)~×ÏÚÍÏÖÎÏ, ×ÁÍ ÓÌÅÄÕÅÔ ÄÏÂÁ×ÉÔØ × ÆÁÊÌ -\filename{/etc/manpath.config} ÓÔÒÏÞËÉ ×ÒÏÄÅ: - -\begin{sverbatim} -MANPATH_MAP /usr/local/texlive/2008/bin/i386-linux \ - /usr/local/texlive/2008/texmf/doc/man -\end{sverbatim} - -é 2)~ÉÎÏÇÄÁ ÐÕÔÉ ÐÏÉÓËÁ É ÄÒÕÇÉÅ ÇÌÏÂÁÌØÎÙÅ ÐÅÒÅÍÅÎÎÙÅ ÏËÒÕÖÅÎÉÑ -ÚÁÄÁÀÔÓÑ × ÆÁÊÌÅ \filename{/etc/environment}. - -\subsubsection{òÁÂÏÔÁ Ó DVD} - -ïÂÙÞÎÏ ÐÒÏÇÒÁÍÍÙ \TL{} ÕÚÎÁÀÔ, ÇÄÅ ÎÁÈÏÄÑÔÓÑ ÎÕÖÎÙÅ ÄÉÒÅËÔÏÒÉÉ, ÉÚ -ÆÁÊÌÁ \filename{texmf.cnf}. ïÎÉ ÉÝÕÔ ÜÔÏÔ ÆÁÊÌ, ÉÓÈÏÄÑ ÉÚ ÔÏÇÏ, ÇÄÅ -ÎÁÈÏÄÑÔÓÑ ÓÁÍÉ. ïÄÎÁËÏ ÜÔÁ ÓÈÅÍÁ ÎÅ ÒÁÂÏÔÁÅÔ, ËÏÇÄÁ ÐÒÏÇÒÁÍÍÁ -ÚÁÐÕÓËÁÅÔÓÑ Ó \DVD{}. îÁ \DVD{} ÎÅÌØÚÑ ÐÉÓÁÔØ, ÎÏ ÎÅËÏÔÏÒÙÅ ÐÕÔÉ, -ËÏÔÏÒÙÅ ÄÏÌÖÎÙ ÂÙÔØ × \filename{texmf.cnf}, ÉÚ×ÅÓÔÎÙ ÔÏÌØËÏ ÐÏÓÌÅ -ÕÓÔÁÎÏ×ËÉ, ÐÏÜÔÏÍÕ ÜÔÏÔ ÆÁÊÌ ÎÅ ÍÏÖÅÔ ÎÁÈÏÄÉÔØÓÑ ÎÁ \DVD{}, É ÄÏÌÖÅÎ -ÂÙÔØ × ÄÒÕÇÏÍ ÍÅÓÔÅ. üÔÏ ÏÚÎÁÞÁÅÔ, ÞÔÏ ÎÅÏÂÈÏÄÉÍÏ ÏÐÒÅÄÅÌÉÔØ -ÐÅÒÅÍÅÎÎÕÀ ÏËÒÕÖÅÎÉÑ \envname{TEXMFCNF}, ËÏÔÏÒÁÑ ÇÏ×ÏÒÉÔ ÐÒÏÇÒÁÍÍÁÍ -\TL{}, ÇÄÅ ÉÓËÁÔØ ÆÁÊÌ \filename{texmf.cnf}. îÅÏÂÈÏÄÉÍÏ ÔÁËÖÅ -ÉÚÍÅÎÉÔØ ÐÅÒÅÍÅÎÎÕÀ \envname{PATH}, ËÁË ÏÐÓÁÎÏ ×ÙÛÅ. - -÷ ËÏÎÃÅ ÕÓÔÁÎÏ×ËÉ ÐÒÏÇÒÁÍÍÁ ÐÉÛÅÔ ÓÏÏÂÝÅÎÉÅ, ÇÄÅ ÕËÁÚÁÎÏ, ÞÅÍÕ ÄÏÌÖÎÁ -ÒÁ×ÎÑÔØÓÑ ÐÅÒÅÍÅÎÎÁÑ \envname{TEXMFCNF}. îÁ ÓÌÕÞÁÊ, ÅÓÌÉ ×Ù -ÐÒÏÐÕÓÔÉÌÉ ÜÔÏ ÓÏÏÂÝÅÎÉÅ: ÜÔÏ \dirname{$TEXMFSYSVAR/web2c}. ðÏ -ÕÍÏÌÞÁÎÉÀ ÜÔÏ \dirname{/usr/local/texlive/2008/texmf-var/web2c}, É -×ÁÍ ÎÕÖÎÏ ÕÓÔÁÎÏ×ÉÔØ Å£ ÔÁË: -\begin{sverbatim} -TEXMFCNF=/usr/local/texlive/2008/texmf-var/web2c; export TEXMFCNF -\end{sverbatim} -ÉÌÉ, ÄÌÑ [t]csh: -\begin{sverbatim} -setenv TEXMFCNF /usr/local/texlive/2008/texmf-var/web2c -\end{sverbatim} - -\subsubsection{\ConTeXt{} Mark IV} - -<<óÔÁÒÙÊ>> \ConTeXt{} ÄÏÌÖÅÎ ÒÁÂÏÔÁÔØ <<ÉÚ ËÏÒÏÂËÉ>>. îÏ×ÁÑ ÓÉÓÔÅÍÁ -Mark~IV ÔÒÅÂÕÅÔ ÒÕÞÎÏÊ ËÏÎÆÉÇÕÒÁÃÉÉ; -ÓÍ. \url{http://wiki.contextgarden.net/Running_Mark_IV}. - - -\subsubsection{äÏÂÁ×ÌÅÎÉÅ ÌÉÞÎÙÈ É ÌÏËÁÌØÎÙÈ ÐÁËÅÔÏ×} -\label{sec:local-personal-macros} - -üÔÏÔ ×ÏÐÒÏÓ ÕÖÅ ÏÂÓÕÖÄÁÌÓÑ × ÒÁÚÄÅÌÅ~\ref{sec:texmftrees}: ÄÌÑ -ÌÏËÁÌØÎÙÈ ÛÒÉÆÔÏ× É ÐÁËÅÔÏ× ÐÒÅÄÎÁÚÎÁÞÅÎÁ ÄÉÒÅËÔÏÒÉÑ -\dirname{TEXMFLOCAL} (ÐÏ ÕÍÏÌÞÁÎÉÀ, -\dirname{/usr/local/texlive/texmf-local} ÉÌÉ -\verb|C:\Program Files\texlive\texmf-local|), Á ÄÌÑ ÌÉÞÎÙÈ ÛÒÉÆÔÏ× É -ÐÁËÅÔÏ× "--- ÄÉÒÅËÔÏÒÉÑ \dirname{TEXMFHOME} (ÐÏ ÕÍÏÌÞÁÎÉÀ, -\dirname{$HOME/texmf} ÉÌÉ \verb|%USERPROFILE%\texmf|). üÔÉ ÄÉÒÅËÔÏÒÉÉ -ÐÒÅÄÐÏÌÁÇÁÀÔÓÑ ÏÂÝÉÍÉ ÄÌÑ ×ÓÅÈ ×ÅÒÓÉÊ \TL{}, É ËÁÖÄÁÑ ×ÅÒÓÉÑ \TL{} -×ÉÄÉÔ ÉÈ Á×ÔÏÍÁÔÉÞÅÓËÉ. ðÏÜÔÏÍÕ ÍÙ ÎÅ ÒÅËÏÍÅÎÄÕÅÍ ÍÅÎÑÔØ ÚÎÁÞÅÎÉÅ -\dirname{TEXMFLOCAL}, ÉÎÁÞÅ ×ÁÍ ÐÒÉÄÅÔÓÑ ÄÅÌÁÔØ ÜÔÏ ÄÌÑ ËÁÖÄÏÊ ÎÏ×ÏÊ -×ÅÒÓÉÉ. - -æÁÊÌÙ × ÏÂÅÉÈ ÄÉÒÅËÔÏÒÉÑÈ ÄÏÌÖÎÙ ÎÁÈÏÄÉÔØÓÑ × ÐÒÁ×ÉÌØÎÙÈ -ÐÏÄÄÉÒÅËÔÏÒÉÑÈ; ÓÍ. \url{http://tug.org/tds} É -\filename{texmf/web2c/texmf.cnf}. îÁÐÒÉÍÅÒ, \LaTeX Ï×ÓËÉÊ ËÌÁÓÓ ÉÌÉ -ÐÁËÅÔ ÄÏÌÖÅÎ ÎÁÈÏÄÉÔØÓÑ × ÄÉÒÅËÔÏÒÉÉ \dirname{TEXMFLOCAL/tex/latex} ÉÌÉ -\dirname{TEXMFHOME/tex/latex} ÉÌÉ ËÁËÏÊ-ÌÉÂÏ ÉÚ ÉÈ ÐÏÄÄÉÒÅËÔÏÒÉÊ. - -äÌÑ ÄÉÒÅËÔÏÒÉÉ \dirname{TEXMFLOCAL} ÄÏÌÖÎÁ ÐÏÄÄÅÒÖÉ×ÁÔØÓÑ ÂÁÚÁ ÄÁÎÎÙÈ -Ï ÆÁÊÌÁÈ, ÉÎÁÞÅ ÓÉÓÔÅÍÁ ÎÅ ÓÍÏÖÅÔ ÎÁÊÔÉ ÔÁÍ ÎÕÖÎÙÅ ÆÁÊÌÙ. üÔÁ ÂÁÚÁ -ÏÂÎÏ×ÌÑÅÔÓÑ ËÏÍÁÎÄÏÊ \cmdname{mktexlsr} ÉÌÉ ËÎÏÐËÏÊ <> × ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ ÐÒÏÇÒÁÍÍÙ \prog{tlmgr}. - -\subsubsection{äÏÂÁ×ÌÅÎÉÅ ÛÒÉÆÔÏ×} - -ë ÓÏÖÁÌÅÎÉÀ, ÜÔÏ ÏÞÅÎØ ÓÌÏÖÎÁÑ ÚÁÄÁÞÁ. îÅ ÄÅÌÁÊÔÅ ÜÔÏÇÏ, ÅÓÌÉ ×Ù ÎÅ -ÚÎÁÅÔÅ \TeX Á ËÁË Ó×ÏÉ ÐÑÔØ ÐÁÌØÃÅ×. îÅ ÚÁÂÕÄØÔÅ ÓÎÁÞÁÌÁ ÐÒÏ×ÅÒÉÔØ, -ËÁËÉÅ ÛÒÉÆÔÙ Õ ×ÁÓ ÕÖÅ ÅÓÔØ, ÓÍ. ÒÁÚÄÅÌ~\ref{sec:tl-fonts}. - -÷ÏÚÍÏÖÎÁÑ ÁÌØÔÅÒÎÁÔÉ×Á "--- ÐÒÏÇÒÁÍÍÁ \XeTeX{} (ÓÍ. -ÒÁÚÄÅÌ~\ref{sec:tex-extensions}), ËÏÔÏÒÁÑ ÐÏÚ×ÏÌÑÅÔ Á×ÔÏÍÁÔÉÞÅÓËÉ -ÉÓÐÏÌØÚÏ×ÁÔØ × \TeX Å ÛÒÉÆÔÙ ×ÁÛÅÊ ÏÐÅÒÁÃÉÏÎÎÏÊ ÓÉÓÔÅÍÙ. - -\subsection{ôÅÓÔÉÒÏ×ÁÎÉÅ ÓÉÓÔÅÍÙ} -\label{sec:test-install} - - -ðÏÓÌÅ ÕÓÔÁÎÏ×ËÉ \TL{} ×Ù, ÓËÏÒÅÅ ×ÓÅÇÏ, ÚÁÈÏÔÉÔÅ ÐÒÏ×ÅÒÉÔØ ÒÁÂÏÔÕ -ÓÉÓÔÅÍÙ, Á ÕÖÅ ÚÁÔÅÍ ÐÅÒÅÊÔÉ Ë ÓÏÚÄÁÎÉÀ ÐÒÅËÒÁÓÎÙÈ ÄÏËÕÍÅÎÔÏ× É/ÉÌÉ -ÛÒÉÆÔÏ×. - -÷ ÜÔÏÍ ÒÁÚÄÅÌÅ ÏÐÉÓÙ×ÁÀÔÓÑ ÏÓÎÏ×ÎÙÅ ÐÒÏÃÅÄÕÒÙ ÐÏ ÔÅÓÔÉÒÏ×ÁÎÉÀ ÓÉÓÔÅÍÙ. -íÙ ÐÒÉ×ÏÄÉÍ ËÏÍÁÎÄÙ ÄÌÑ ÏÐÅÒÁÃÉÏÎÎÙÈ ÓÉÓÔÅÍ ÔÉÐÁ Unix; ÐÏÄ \MacOSX{} É -Windows ×Ù, ÓËÏÒÅÅ ×ÓÅÇÏ, ÂÕÄÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ ÇÒÁÆÉÞÅÓËÉÊ ÉÎÔÅÒÆÅÊÓ, -ÎÏ ÐÒÉÎÃÉÐ ÔÏÔ ÖÅ. - -\begin{enumerate} - -\item óÎÁÞÁÌÁ ÐÒÏ×ÅÒØÔÅ, ÞÔÏ ×Ù ÍÏÖÅÔÅ ÚÁÐÕÓËÁÔØ ÐÒÏÇÒÁÍÍÕ - \cmdname{tex}: - -\begin{alltt} -> \Ucom{tex -{}-version} -TeX 3.1415926 (Web2C 7.5.7) -kpathsea version 3.5.7 -... -\end{alltt} -åÓÌÉ ×Ù ÐÏÌÕÞÁÅÔÅ × ÏÔ×ÅÔ <> ×ÍÅÓÔÏ ÎÏÍÅÒÁ ×ÅÒÓÉÉ É -ÉÎÆÏÒÍÁÃÉÉ Ï ËÏÐÉÒÁÊÔÅ, Õ ×ÁÓ, ÓËÏÒÅÅ ×ÓÅÇÏ, ÎÅÔ ÄÉÒÅËÔÏÒÉÉ Ó ÎÕÖÎÙÍÉ -ÐÒÏÇÒÁÍÍÁÍÉ × ÐÅÒÅÍÅÎÎÏÊ \envname{PATH}. óÍ. ÏÂÓÕÖÄÅÎÉÅ ÎÁ -ÓÔÒÁÎÉÃÅ~\pageref{sec:env}. - - -\item óËÏÍÐÉÌÉÒÕÊÔÅ ÐÒÏÓÔÏÊ \LaTeX{}Ï×ÓËÉÊ ÆÁÊÌ: -\begin{alltt} -> \Ucom{latex sample2e.tex} -This is pdfeTeXk, Version 3.1415926... -... -Output written on sample2e.dvi (3 pages, 7484 bytes). -Transcript written on sample2e.log. -\end{alltt} -åÓÌÉ ÐÒÏÇÒÁÍÍÁ ÎÅ ÍÏÖÅÔ ÎÁÊÔÉ \filename{sample2e.tex} ÉÌÉ ÄÒÕÇÉÅ -ÆÁÊÌÙ, ×ÏÚÍÏÖÎÏ, Õ ×ÁÓ ÏÓÔÁÌÉÓØ ÓÌÅÄÙ ÏÔ ÓÔÁÒÏÊ ÕÓÔÁÎÏ×ËÉ: ÐÅÒÅÍÅÎÎÙÅ -ÏËÒÕÖÅÎÉÑ ÉÌÉ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÆÁÊÌÙ. íÙ ÒÅËÏÍÅÎÄÕÅÍ ÓÎÁÞÁÌÁ ÕÂÒÁÔØ -×ÓÅ ÐÅÒÅÍÅÎÎÙÅ ÏËÒÕÖÅÎÉÑ, ÏÔÎÏÓÑÝÉÅÓÑ Ë \TeX Õ. (äÌÑ ÏÔÌÁÄËÉ ×Ù ×ÓÅÇÄÁ ÍÏÖÅÔÅ -ÐÏÐÒÏÓÉÔØ \TeX{} ÔÏÞÎÏ ÓËÁÚÁÔØ, ÞÔÏ ÉÍÅÎÎÏ ÏÎ ÉÝÅÔ; ÓÍ. <<ïÔÌÁÄËÁ>> ÎÁ -ÓÔÒ.~\pageref{sec:debugging}.) - -\item ðÏÓÍÏÔÒÉÔÅ ÒÅÚÕÌØÔÁÔ ÎÁ ÜËÒÁÎÅ: -\begin{alltt} -> \Ucom{xdvi sample2e.dvi} -\end{alltt} -(ðÏÄ Windows ÁÎÁÌÏÇÉÞÎÁÑ ËÏÍÁÎÄÁ ÎÁÚÙ×ÁÅÔÓÑ \cmdname{dviout}.) ÷Ù ÄÏÌÖÎÙ -Õ×ÉÄÅÔØ ÎÏ×ÏÅ ÏËÎÏ Ó ËÒÁÓÉ×Ï Ó×£ÒÓÔÁÎÎÙÍ ÄÏËÕÍÅÎÔÏÍ, ÏÂßÑÓÎÑÀÝÉÍ ÏÓÎÏ×Ù -\LaTeX{}Á. (åÓÌÉ ×Ù "--- ÎÏ×ÉÞÏË, ×ÁÍ ÓÔ\'ÏÉÔ ÅÇÏ ÐÒÏÞÅÓÔØ.) þÔÏÂÙ -ÐÒÏÇÒÁÍÍÁ \cmdname{xdvi} ÍÏÇÌÁ ÚÁÐÕÓÔÉÔØÓÑ, ×Ù ÄÏÌÖÎÙ ÂÙÔØ × ÓÒÅÄÅ X Window; -ÅÓÌÉ ÜÔÏ ÎÅ ÔÁË, ÉÌÉ ÅÓÌÉ ÐÅÒÅÍÅÎÎÁÑ \envname{DISPLAY} ÕÓÔÁÎÏ×ÌÅÎÁ -ÎÅÐÒÁ×ÉÌØÎÏ, ×Ù Õ×ÉÄÉÔÅ ÏÛÉÂËÕ \samp{Can't open display}. - -\item óÏÚÄÁÊÔÅ ÆÁÊÌ × ÆÏÒÍÁÔÅ \PS{} ÄÌÑ ÐÅÞÁÔÉ ÉÌÉ ÐÒÏÓÍÏÔÒÁ ÎÁ ÜËÒÁÎÅ: -\begin{alltt} -> \Ucom{dvips sample2e.dvi -o sample2e.ps} -\end{alltt} - -\item óÏÚÄÁÊÔÅ ÆÁÊÌ × ÆÏÒÍÁÔÅ \acro{PDF} ×ÍÅÓÔÏ \dvi{}; ËÏÍÁÎÄÁ ÎÉÖÅ - ËÏÍÐÉÌÉÒÕÅÔ ÆÁÊÌ \filename{.tex} É ÓÏÚÄÁ£Ô \acro{PDF}: -\begin{alltt} -> \Ucom{pdflatex sample2e.tex} -\end{alltt} - -\item ðÏÓÍÏÔÒÉÔÅ ÒÅÚÕÌØÔÁÔ ÎÁ ÜËÒÁÎÅ: -\begin{alltt} -> \Ucom{gv sample2e.pdf} -\textrm{ÉÌÉ:} -> \Ucom{xpdf sample2e.pdf} -\end{alltt} -ë ÓÏÖÁÌÅÎÉÀ, ÎÉ \cmdname{gv}, ÎÉ \cmdname{xpdf} ÎÅ ×ËÌÀÞÅÎÙ × ÔÅËÕÝÕÀ -×ÅÒÓÉÀ \TL{}, ÔÁË ÞÔÏ ×ÁÍ ÐÒÉÄ£ÔÓÑ ÕÓÔÁÎÁ×ÌÉ×ÁÔØ ÉÈ -ÏÔÄÅÌØÎÏ. óÍ. ÓÏÏÔ×ÅÔÓÔ×ÅÎÎÏ -\url{http://www.gnu.org/software/gv} É -\url{http://www.foolabs.com/xpdf}. (òÁÚÕÍÅÅÔÓÑ, ÅÓÔØ É ÍÎÏÇÏ ÄÒÕÇÉÈ -ÐÒÏÇÒÁÍÍ ÄÌÑ ÐÒÏÓÔÍÏÔÒÁ ÆÁÊÌÏ× × ÆÏÒÍÁÔÅ \acro{PDF}). - -\item äÒÕÇÉÅ ÓÔÁÎÄÁÒÔÎÙÅ ÔÅÓÔÏ×ÙÅ ÆÁÊÌÙ, ËÏÔÏÒÙÅ ×ÁÍ ÍÏÇÕÔ ÐÒÉÇÏÄÉÔØÓÑ: - -\begin{ttdescription} -\item [small2e.tex] âÏÌÅÅ ÐÒÏÓÔÏÊ ÄÏËÕÍÅÎÔ, ÞÅÍ \filename{sample2e}, - ÕÄÏÂÎÙÊ, ÅÓÌÉ ÐÏÓÌÅÄÎÉÊ ÓÌÉÛËÏÍ ×ÅÌÉË ÄÌÑ ×ÁÓ. -\item [testpage.tex] ðÒÏ×ÅÒÑÅÔ ÐÏÌÑ É ÐÏÚÉÃÉÏÎÉÒÏ×ÁÎÉÅ ÂÕÍÁÇÉ ÄÌÑ - ×ÁÛÅÇÏ ÐÒÉÎÔÅÒÁ. -\item [nfssfont.tex] éÓÐÏÌØÚÕÅÔÓÑ ÄÌÑ ÐÅÞÁÔÉ ÔÁÂÌÉà ÛÒÉÆÔÏ× É ÔÅÓÔÏ×. -\item [testfont.tex] ðÅÞÁÔØ ÔÁÂÌÉà ÛÒÉÆÔÏ× ÐÏÄ plain \TeX{}. -\item [story.tex] óÁÍÙÊ ËÁÎÏÎÉÞÅÓËÉÊ ÆÁÊÌ × ÆÏÒÍÁÔÅ (plain) \TeX. ÷Ù - ÄÏÌÖÎÙ ÎÁÐÅÞÁÔÁÔØ \samp{\bs bye} × ÏÔ×ÅÔ ÎÁ ÐÒÉÇÌÁÛÅÎÉÅ \code{*} - ÐÏÓÌÅ \samp{tex story.tex}. -\end{ttdescription} -\end{enumerate} - - -åÓÌÉ ×Ù ÎÏ×ÉÞÏË × \TeX{}Å, ÉÌÉ ×ÁÍ ÎÕÖÎÁ ÐÏÍÏÝØ × ÓÏÚÄÁÎÉÉ ÄÏËÕÍÅÎÔÏ× -ÎÁ ÑÚÙËÅ \TeX{} ÉÌÉ \LaTeX{}, ÐÏÓÅÔÉÔÅ -\url{http://tug.org/begin.html}. - -\section{õÓÔÁÎÏ×ËÁ × ÌÏËÁÌØÎÏÊ ÓÅÔÉ} -\label{sec:netinstall} - -\TL{} ÍÏÖÅÔ ÉÓÐÏÌØÚÏ×ÁÔØÓÑ ÏÄÎÏ×ÒÅÍÅÎÎÏ ÒÁÚÎÙÍÉ ÐÏÌØÚÏ×ÁÔÅÌÑÍÉ ÉÌÉ -ÄÁÖÅ ÒÁÚÎÙÍÉ ÍÁÛÉÎÁÍÉ × ÌÏËÁÌØÎÏÊ ÓÅÔÉ. ÷ ÓÔÁÎÄÁÒÔÎÏÊ ÓÈÅÍÅ -ÄÉÒÅËÔÏÒÉÊ ×ÓÅ ÐÕÔÉ Ë ÆÁÊÌÁÍ Ñ×ÌÑÀÔÓÑ ÏÔÎÏÓÉÔÅÌØÎÙÍÉ: ÐÒÏÇÒÁÍÍÙ \TL{} -ÏÐÒÅÄÅÌÑÀÔ, ÇÄÅ ÌÅÖÁÔ ÎÕÖÎÙÅ ÉÍ ÆÁÊÌÙ, ÉÓÈÏÄÑ ÉÚ ÔÏÇÏ, ÇÄÅ ÏÎÉ -ÎÁÈÏÄÑÔÓÑ ÓÁÍÉ. ÷Ù ÍÏÖÅÔÅ Õ×ÉÄÅÔØ, ËÁË ÜÔÏ ÄÅÌÁÅÔÓÑ, ÐÏÓÍÏÔÒÅ× -ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ \filename{$TEXMFMAIN/web2c/texmf.cnf} ÓÏ -ÓÔÒÏÞËÁÍÉ ÔÉÐÁ -\begin{sverbatim} -TEXMFMAIN = $SELFAUTOPARENT/texmf -... -TEXMFLOCAL = $SELFAUTOPARENT/../texmf-local -\end{sverbatim} -üÔÏ ÏÚÎÁÞÁÅÔ, ÞÔÏ ÄÒÕÇÉÅ ÓÉÓÔÅÍÙ ÉÌÉ ÐÏÌØÚÏ×ÁÔÅÌÉ ÄÏÌÖÎÙ ÐÒÏÓÔÏ -ÄÏÂÁ×ÉÔØ ÄÉÒÅËÔÏÒÉÀ Ó ÐÒÏÇÒÁÍÍÁÍÉ \TL{} Ë ÄÉÒÅËÔÏÒÉÑÍ ÐÏÉÓËÁ. - -ôÏÞÎÏ ÔÁË ÖÅ ×Ù ÍÏÖÅÔÅ ÕÓÔÁÎÏ×ÉÔØ \TL{} ÎÁ ÏÄÉÎ ËÏÍÐØÀÔÅÒ, Á ÚÁÔÅÍ -ÐÅÒÅÎÅÓÔÉ ×ÓÀ ÉÅÒÁÒÈÉÀ ÎÁ ÌÏËÁÌØÎÕÀ ÓÅÔØ. - -òÁÚÕÍÅÅÔÓÑ, ÐÏÌØÚÏ×ÁÔÅÌÉ Windows ÐÒÉ×ÙËÌÉ Ë ÄÒÕÇÏÍÕ. ÷ ÄÉÒÅËÔÏÒÉÉ -\dirname{texmf-doc/source/texlive/texlive-common/w32client} ÎÁÈÏÄÉÔÓÑ -ÐÒÉÍÅÒ ÓËÒÉÐÔÁ \filename{install-w32client}, ËÏÔÏÒÙÊ ÓÏÚÄÁÅÔ ÎÁÓÔÒÏÊËÉ -É ÑÒÌÙËÉ ÄÌÑ ÓÕÝÅÓÔ×ÕÀÝÅÊ ÓÉÓÔÅÍÙ \TL{} × ÌÏËÁÌØÎÏÊ ÓÅÔÉ. åÇÏ ÍÏÖÎÏ -ÚÁÐÕÓÔÉÔØ ÉÚ ÆÁÊÌÁ \filename{install-w32client.bat}, ËÏÔÏÒÙÊ ÎÁÈÏÄÉÔÓÑ -× ÔÏÊ ÖÅ ÄÉÒÅËÔÏÒÉÉ. - -äÏÐÏÌÎÉÔÅÌØÎÁÑ ÉÎÆÏÒÍÁÃÉÑ Ï ËÏÎÆÉÇÕÒÁÃÉÉ \TL{} É ÐÏÉÓËÅ ÆÁÊÌÏ× -ÎÁÈÏÄÉÔÓÑ × ÒÁÚÄÅÌÅ~\ref{sec:kpathsea}. - -\section{íÁËÓÉÍÁÌØÎÏ ÐÅÒÅÎÏÓÉÍÁÑ ÓÉÓÔÅÍÁ \protect\TL{} ÎÁ DVD É USB} -\label{sec:portable-unix} - -÷ÁÒÉÁÎÔ <<ÒÁÂÏÔÙ Ó \DVD>>, ÏÐÉÓÁÎÎÙÊ × ÒÁÚÄÅÌÅ~\ref{sec:fromdvd}, -ÐÏÄÈÏÄÉÔ ÄÌÑ ×ÁÛÅÊ ÓÏÂÓÔ×ÅÎÎÏÊ ÓÉÓÔÅÍÙ, ÎÏ ÅÓÌÉ ×Ù "--- ÇÏÓÔØ ÎÁ -ÞØÅÍ-ÎÉÂÕÄØ ÞÕÖÏÍ ËÏÍÐØÀÔÅÒÅ, ×Ù ÚÁÈÏÔÉÔÅ ÓÄÅÌÁÔØ ÔÁË, ÞÔÏÂÙ ÐÏÓÌÅ ×ÁÓ -ÎÅ ÏÓÔÁ×ÁÌÏÓØ ÎÉËÁËÉÈ ÉÚÍÅÎÅÎÉÊ × ÓÉÓÔÅÍÅ. - -÷ ËÏÒÎÅ×ÏÊ ÄÉÒÅËÔÏÒÉÉ \DVD{} \TL{}, ÉÌÉ × ÄÉÒÅËÔÏÒÉÉ \dirname{texlive} -\DVD{} \TK{} ÎÁÈÏÄÉÔÓÑ ÓËÒÉÐÔ \filename{tl-portable} (àÎÉËÓ) É ÆÁÊÌ -\filename{tl-portable.bat} (Windows), ËÏÔÏÒÙÅ ÏÔËÒÙ×ÁÀÔ ÔÅÒÍÉÎÁÌ Ó -ÐÅÒÅÍÅÎÎÙÍÉ ÏËÒÕÖÅÎÉÑ, ÐÏÄÈÏÄÑÝÉÍÉ ÄÌÑ ÒÁÂÏÔÙ Ó \TL{} ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ -Ó \DVD{}. - -ëÏÇÄÁ ÜÔÁ ÐÒÏÇÒÁÍÍÁ ÚÁÐÕÓËÁÅÔÓÑ × ÐÅÒ×ÙÊ ÒÁÚ, ÏÎÁ ÓÏÚÄÁÅÔ ÎÅÓËÏÌØËÏ -ÆÁÊÌÏ× × ÄÉÒÅËÔÏÒÉÉ \dirname{~/.tlportable2008}, ÞÔÏ ÔÒÅÂÕÅÔ -ÎÅËÏÔÏÒÏÇÏ ×ÒÅÍÅÎÉ. ÷ÐÏÓÌÅÄÓÔ×ÉÉ ÏÎÁ ÚÁÐÕÓËÁÅÔÓÑ ÐÒÁËÔÉÞÅÓËÉ -ÍÇÎÏ×ÅÎÎÏ. - -ïÓÔÁÌØÎÁÑ ÓÉÓÔÅÍÁ ÎÅ ÂÕÄÅÔ ÎÉÞÅÇÏ ÚÎÁÔØ Ï \TL{}. åÓÌÉ ×Ù ÈÏÔÉÔÅ, -ÞÔÏÂÙ ×ÁÛ ÒÅÄÁËÔÏÒ ÚÎÁÌ Ï \TL{}, ÚÁÐÕÓÔÉÔÅ ÅÇÏ ÉÚ ÐÁÒÁÌÌÅÌØÎÏÊ ÓÅÓÓÉÉ -\filename{tl-portable}. - -÷Ù ÔÁËÖÅ ÍÏÖÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ \filename{tl-portable}, ÞÔÏÂÙ ÚÁÐÕÓËÁÔØ -\TL{} Ó ÆÌÅÛËÉ \acro{USB}. äÌÑ ÜÔÏÇÏ ÓËÏÐÉÒÕÊÔÅ ×ÓÅ ÆÁÊÌÙ × ËÏÒÎÅ×ÏÊ -ÄÉÒÅËÔÏÒÉÉ, Á ÔÁËÖÅ ÐÏ ËÒÁÊÎÅÊ ÍÅÒÅ ÓÏÄÅÒÖÉÍÏÅ \dirname{bin}, -\dirname{texmf}, \dirname{texmf-dist} É \dirname{tlpkg} ÎÁ ÆÌÅÛËÕ. -üÔÏ ÍÏÖÅÔ ÚÁÎÑÔØ ÍÎÏÇÏ ×ÒÅÍÅÎÉ! åÓÌÉ ×Ù ËÏÐÉÒÕÅÔÅ ÎÁ ÆÌÅÛËÕ × ÆÏÒÍÁÔÅ -\acro{FAT}32, ×Ù ÄÏÌÖÎÙÅ ÒÁÓËÒÙÔØ ÓÉÍÌÉÎËÉ (\code{cp -L}). åÓÌÉ ÎÁ -ÆÌÅÛËÅ ÅÓÔØ ÄÉÒÅËÔÏÒÉÑ \dirname{texmf-local}, ÏÎÁ ÂÕÄÅÔ ÎÁÊÄÅÎÁ É -ÉÓÐÏÌØÚÏ×ÁÎÁ. - -ðÏÓÌÅ ÜÔÏÇÏ ×Ù ÍÏÖÅÔÅ ÚÁÐÕÓËÁÔØ ÓËÒÉÐÔ \filename{tl-portable} ÉÚ -ËÏÒÎÅ×ÏÊ ÄÉÒÅËÔÏÒÉÉ ÆÌÅÛËÉ, ËÁË ÏÐÉÓÁÎÏ ×ÙÛÅ. ÷ ÜÔÏÍ ÓÌÕÞÁÅ ÓËÒÉÐÔ -ÐÏÊÍÅÔ, ÞÔÏ ÎÁ ÆÌÅÛËÕ ÍÏÖÎÏ ÐÉÓÁÔØ, É ÂÕÄÅÔ ÚÁÐÉÓÙ×ÁÔØ Á×ÔÏÍÁÔÉÞÅÓËÉ -ÓÏÚÄÁÎÎÙÅ ÆÁÊÌÙ ÔÕÄÁ. ÷Ù ÍÏÖÅÔÅ ÐÒÏÖÅÞØ \DVD{}, ÅÓÌÉ ÜÔÏ ÂÏÌÅÅ ÕÄÏÂÎÏ -(ÎÁÐÒÉÍÅÒ, ÞÔÏÂÙ ÐÏÄÅÌÉÔØÓÑ Ó ËÅÍ-ÎÉÂÕÄØ \TL{}). - -\section{áÄÍÉÎÉÓÔÒÉÒÏ×ÁÎÉÅ ÓÉÓÔÅÍÙ ÐÒÉ ÐÏÍÏÝÉ \cmdname{tlmgr}} -\label{sec:tlmgr} - -\begin{figure}[tb] -\tlpng{tlmgr-gui}{\linewidth} -\caption{\prog{tlmgr} × ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ. óÐÉÓÏË - ÐÁËÅÔÏ×/ËÏÌÌÅËÃÉÊ/ÓÈÅÍ ×ÉÄÅÎ ÔÏÌØËÏ ÐÏÓÌÅ ÎÁÖÁÔÉÑ ÎÁ ËÌÁ×ÉÛÕ - <>}\label{fig:tlmgr-gui} -\end{figure} - -\begin{figure}[tb] -\tlpng{tlmgr-config}{\linewidth} -\caption{\texttt{tlmgr} × ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ: ÍÅÎÀ - ËÏÎÆÉÇÕÒÁÃÉÉ}\label{fig:tlmgr-config} -\end{figure} - -\TL{} ÓÏÄÅÒÖÉÔ ÐÒÏÇÒÁÍÍÕ \prog{tlmgr} ÄÌÑ ÁÄÍÉÎÉÓÔÒÉÒÏ×ÁÎÉÑ ÓÉÓÔÅÍÙ -ÐÏÓÌÅ ÕÓÔÁÎÏ×ËÉ. ðÒÏÇÒÁÍÍÙ \prog{updmap}, \prog{fmtutil} É -\prog{texconfig} ×ÓÅ ÅÝ£ ÅÓÔØ × ÓÉÓÔÅÍÅ É ÂÕÄÕÔ ÔÁÍ × ÂÕÄÕÝÅÍ, ÎÏ -ÍÙ ÒÅËÏÍÅÎÄÕÅÍ ÔÅÐÅÒØ ÐÒÏÇÒÁÍÍÕ \prog{tlmgr}. óÒÅÄÉ Å£ ×ÏÚÍÏÖÎÏÓÔÅÊ: -\begin{itemize*} -\item ÐÏÄÄÅÒÖËÁ ÓÐÉÓËÏ× ÓÈÅÍ, ËÏÌÌÅËÃÉÊ É ÐÁËÅÔÏ×; -\item ÕÓÔÁÎÏ×ËÁ, ÏÂÎÏ×ÌÅÎÉÅ, ÁÒÈÉ×ÉÒÏ×ÁÎÉÅ, ×ÏÓÓÔÁÎÏ×ÌÅÎÉÅ É ÕÄÁÌÅÎÉÅ - ÏÔÄÅÌØÎÙÈ ÐÁËÅÔÏ×, ÐÒÉ ÖÅÌÁÎÉÉ Ó ÕÞÅÔÏÍ ÚÁ×ÉÓÉÍÏÓÔÅÊ ÍÅÖÄÕ ÎÉÍÉ; -\item ÐÏÉÓË ÐÁËÅÔÏ×; -\item ÄÏÂÁ×ÌÅÎÉÅ ÐÌÁÔÆÏÒÍ; -\item ÉÚÍÅÎÅÎÉÅ ÐÁÒÁÍÅÔÒÏ× ÓÉÓÔÅÍÙ, ÎÁÐÒÉÍÅÒ, ÒÁÚÍÅÒÁ ÂÕÍÁÇÉ É - ÉÓÔÏÞÎÉËÁ ÕÓÔÁÎÏ×ËÉ (ÓÍ. ÒÁÚÄÅÌ~\ref{sec:location}). -\end{itemize*} -\textit{÷ÎÉÍÁÎÉÅ:} \prog{tlmgr} ÎÅ ÐÒÅÄÎÁÚÎÁÞÅÎÁ ÄÌÑ ÚÁÐÕÓËÁ \TL{} Ó -\DVD{}, É ÎÅ ÔÅÓÔÉÒÏ×ÁÌÁÓØ × ÜÔÏÍ ÒÅÖÉÍÅ. - -\subsection{ðÒÏÇÒÁÍÍÁ \cmdname{tlmgr} × ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ} -ðÒÏÇÒÁÍÍÁ \prog{tlmgr} ÍÏÖÅÔ ÂÙÔØ ÚÁÐÕÝÅÎÁ × ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ: -\begin{alltt} -> \Ucom{tlmgr -gui} -\end{alltt} -ÉÌÉ ÎÁ Windows ÉÚ ÍÅÎÀ Start: \texttt{Start}, \texttt{Programs}, -\texttt{TeX Live 2008}, \texttt{TeX Live Manager}. ðÏÓÌÅ ÎÁÖÁÔÉÑ ÎÁ -ËÌÁ×ÉÛÕ <>, ÏÎÁ ÐÏËÁÚÙ×ÁÅÔ ÓÐÉÓÏË ÄÏÓÔÕÐÎÙÈ É ÕÓÔÁÎÏ×ÌÅÎÎÙÈ -ÐÁËÅÔÏ× "--- ÐÅÒÅÄ ÐÏÓÌÅÄÎÉÍÉ ÓÔÏÉÔ ÚÎÁÞÏË <<(i)>>. üÔÏ, ÒÁÚÕÍÅÅÔÓÑ, -ÐÒÏÉÓÈÏÄÉÔ ÐÒÉ ÕÓÌÏ×ÉÉ, ÞÔÏ ÉÓÔÏÞÎÉË ÕÓÔÁÎÏ×ËÉ ÄÏÓÔÕÐÅÎ. - -îÁ ÒÉÓÕÎËÅ~\ref{fig:tlmgr-config} ÐÏËÁÚÁÎÏ ÍÅÎÀ ËÏÎÆÉÇÕÒÁÃÉÉ. - -\subsection{úÁÐÕÓË ÐÒÏÇÒÁÍÍÙ \cmdname{tlmgr} ÉÚ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ} - -÷ ÐÒÉÍÅÒÅ ÎÉÖÅ ÍÙ ÄÏÂÁ×ÌÑÅÍ ÎÅÓËÏÌØËÏ ÐÁËÅÔÏ×, ×ËÌÀÞÁÑ ÎÏ×ÕÀ -ÐÒÏÇÒÁÍÍÕ, ÉÚ ÎÅÓÔÁÎÄÁÒÔÎÏÇÏ ÉÓÔÏÞÎÉËÁ: -\begin{alltt} -> \Ucom{tlmgr -location http://172.16.18.1/tldev install collection-xetex xkeyval} -\end{alltt} -óÉÓÔÅÍÁ ÏÔ×ÅÞÁÅÔ: -\begin{fverbatim} -install: collection-xetex -install: arabxetex -install: euenc -install: bidi -install: fontspec -install: fontwrap -install: ifxetex -install: philokalia -install: polyglossia -install: xecyr -install: xecyr.i386-linux -install: xepersian -install: xetex -install: xetexconfig -install: xetex.i386-linux -running post install action for xetex -install: xetex-def -install: xetex-pstricks -install: xetexfontinfo -install: xltxtra -install: xunicode -install: xkeyval -running mktexlsr -mktexlsr: Updating /usr/local/texlive/2008/texmf/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-config/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-dist/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-doc/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/../texmf-local/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-var/ls-R... -mktexlsr: Done. -regenerating fmtutil.cnf -running fmtutil-sys --missing -... -Transcript written on xelatex.log. -fmtutil: /usr/local/texlive/2008/texmf-var/web2c/xetex/xelatex.fmt installed. -\end{fverbatim} -ëÁË ×ÉÄÎÏ, \prog{tlmgr} ÕÓÔÁÎÁ×ÌÉ×ÁÅÔ ÚÁ×ÉÓÉÍÏÓÔÉ É ÐÒÉÚ×ÏÄÉÔ ×ÓÅ -ÎÕÖÎÙÅ ÐÏÓÌÅ ÕÓÔÁÎÏ×ËÉ ÄÅÊÓÔ×ÉÑ, ×ËÌÀÞÁÑ ÏÂÎÏ×ÌÅÎÉÅ ÂÁÚÙ ÄÁÎÎÙÈ ÆÁÊÌÏ× -É ÓÏÚÄÁÎÉÅ ÆÏÒÍÁÔÏ× (ÚÄÅÓØ ÓÏÚÄÁÎÙ ÆÏÒÍÁÔÙ ÄÌÑ \XeTeX Á). - -÷ ÓÌÅÄÕÀÝÅÍ ÐÒÉÍÅÒÅ ÍÙ ÄÏÂÁ×ÌÑÅÍ ÎÏ×ÙÊ ÑÚÙË. üÔÏ ÔÁËÖÅ ÐÒÉ×ÏÄÉÔ Ë -ÐÅÒÅÇÅÎÅÒÁÃÉÉ ÆÏÒÍÁÔÏ×: -\begin{alltt} -> \Ucom{tlmgr install collection-langdutch} -\end{alltt} -ïÐÉÓÁÎÉÅ ÐÁËÅÔÁ: -\begin{alltt} -> \Ucom{tlmgr show collection-wintools} -\end{alltt} -ÞÔÏ ×ÙÚÙ×ÁÅÔ ÓÌÅÄÕÀÝÉÊ ÏÔ×ÅÔ: -\begin{fverbatim} -Package: collection-wintools -Category: Collection -ShortDesc: Windows support programs -LongDesc: Utilities for Windows, since they are not readily available there: - gzip, chktex, jpeg2ps, unzip, wget, xpdf. -Installed: Yes -\end{fverbatim} -ïÂÎÏ×ÌÅÎÉÅ ×ÓÅÊ ÓÉÓÔÅÍÙ ÄÏ ÐÏÓÌÅÄÎÅÊ ×ÅÒÓÉÉ: -\begin{alltt} -> \Ucom{tlmgr update -all} -\end{alltt} -åÓÌÉ ×ÁÍ ÜÔÏ ËÁÖÅÔÓÑ ÓÔÒÁÛÎÏ×ÁÔÙÍ, ÐÏÐÒÏÂÕÊÔÅ ÓÎÁÞÁÌÁ -\begin{alltt} -> \Ucom{tlmgr update -all -dry-run} -\end{alltt} -ÉÌÉ -\begin{alltt} -> \Ucom{tlmgr update -list} -\end{alltt} -äÏËÕÍÅÎÔÁÃÉÑ: -\begin{alltt} -> \Ucom{tlmgr -help} -\end{alltt} - -\section{äÏÐÏÌÎÉÔÅÌØÎÙÅ ÚÁÍÅÞÁÎÉÑ Ï Windows} -\label{sec:windows} - -õ \TL{} ÏÂÝÁÑ ÐÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ, ËÏÔÏÒÁÑ ÒÁÂÏÔÁÅÔ É ÐÏÄ Windows, É -ÐÏÄ àÎÉËÓÏÍ. üÔÏ ÓÔÁÌÏ ×ÏÚÍÏÖÎÙÍ ÔÏÌØËÏ ÐÏÓÌÅ ÔÏÇÏ, ËÁË ÍÙ ÏÔËÁÚÁÌÉÓØ -ÏÔ ÐÏÄÄÅÒÖËÉ ÓÔÁÒÙÈ ×ÅÒÓÉÊ Windows, ÐÏÜÔÏÍÕ \TL{} ÔÅÐÅÒØ ÍÏÖÎÏ -ÕÓÔÁÎÏ×ÉÔØ ÔÏÌØËÏ ÎÁ Windows 2000 É ÍÌÁÄÛÅ. - -\subsection{äÏÐÏÌÎÉÔÅÌØÎÙÅ ×ÏÚÍÏÖÎÏÓÔÉ Windows} -\label{sec:winfeatures} - -ðÏÄ Windows ÐÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ ÄÅÌÁÅÔ ÎÅÓËÏÌØËÏ ÄÏÐÏÌÎÉÔÅÌØÎÙÈ ×ÅÝÅÊ: -\begin{description} -\item[íÅÎÀ É ÑÒÌÙËÉ.] õÓÔÁÎÁ×ÌÉ×ÁÅÔÓÑ ÐÏÄÍÅÎÀ <<\TL{}>> ÍÅÎÀ - <>, ËÏÔÏÒÏÅ ÓÏÄÅÒÖÉÔ ÎÅËÏÔÏÒÙÅ ÐÒÏÇÒÁÍÍÙ - (\prog{tlmgr}, \prog{texdoctk}, ÐÒÏÇÒÁÍÍÁ PS\_View ÄÌÑ ÐÒÏÓÍÏÔÒÁ - ÆÁÊÌÏ× × ÆÏÒÍÁÔÅ PostScript) É ÄÏËÕÍÅÎÔÁÃÉÀ. äÏÂÁ×ÌÑÅÔÓÑ ÑÒÌÙË - PS\_View ÎÁ ÄÅÓËÔÏÐÅ, ËÕÄÁ ÍÏÖÎÏ ÏÔÐÒÁ×ÌÑÔØ ÐÏÓÔÓËÒÉÐÔÏ×ÓËÉÅ ÆÁÊÌÙ. -\item[á×ÔÏÍÁÔÉÞÅÓËÁÑ ÕÓÔÁÎÏ×ËÁ ÐÅÒÅÍÅÎÎÙÈ ÏËÒÕÖÅÎÉÑ.] ÷ÓÅ ÐÅÒÅÍÅÎÎÙÅ - ÏËÒÕÖÅÎÉÑ ÕÓÔÁÎÁ×ÌÉ×ÁÀÔÓÑ Á×ÔÏÍÁÔÉÞÅÓËÉ. -\item[õÄÁÌÅÎÉÅ ÓÉÓÔÅÍÙ.] ðÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ ÓÏÚÄÁÅÔ × ÍÅÎÀ - <> ÚÁÐÉÓØ <<\TL{}>>. ëÌÁ×ÉÛÁ <<ÕÄÁÌÉÔØ>> × - ÍÅÎÀ \prog{tlmgr} ÏÔÎÏÓÉÔÓÑ Ë ÜÔÏÍÕ. -\end{description} - - - -\subsection{äÏÐÏÌÎÉÔÅÌØÎÙÅ ÐÁËÅÔÙ ÄÌÑ Windows} - -\begin{figure}[tb] -\tlpng{psview}{.6\linewidth} -\caption{PS\_View: ×ÏÚÍÏÖÎÏ ÏÞÅÎØ ÂÏÌØÛÏÅ Õ×ÅÌÉÞÅÎÉÅ!}\label{fig:psview} -\end{figure} - - -äÌÑ ÐÏÌÎÏÔÙ ÄÉÓÔÒÉÂÕÔÉ×Õ \TL ÎÅÏÂÈÏÄÉÍÙ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ÐÁËÅÔÙ, -ËÏÔÏÒÙÅ ÏÂÙÞÎÏ ÎÅ ×ÓÔÒÅÞÁÀÔÓÑ ÎÁ ÍÁÛÉÎÅ ÐÏÄ Windows. ÷ \TL{} ÅÓÔØ -ÎÅÄÏÓÔÁÀÝÉÅ ×ÅÝÉ: -\begin{description} -\item[Perl É Ghostscript.] ÷×ÉÄÕ ×ÁÖÎÏÓÔÉ ÜÔÉÈ ÐÒÏÇÒÁÍÍ, \TL{} - ×ËÌÀÞÁÅÔ ÉÈ <<ÓËÒÙÔÙÅ>> ËÏÐÉÉ. ðÒÏÇÒÁÍÍÙ \TL{}, ËÏÔÏÒÙÍ ÏÎÉ ÎÕÖÎÙ, - ÚÎÁÀÔ, ÇÄÅ ÉÈ ÎÁÊÔÉ, ÎÏ ÏÎÉ ÎÅ ×ÙÄÁÀÔ ÉÈ ÐÒÉÓÕÔÓÔ×ÉÑ ÓÉÓÔÅÍÅ ÞÅÒÅÚ - ÐÅÒÅÍÅÎÎÙÅ ÏËÒÕÖÅÎÉÑ ÉÌÉ ÒÅÇÉÓÔÒ. üÔÏ ÕÓÅÞÅÎÎÙÅ ×ÁÒÉÁÎÔÙ ÐÒÏÇÒÁÍÍ - Perl É Ghostscript, É ÏÎÉ ÎÅ ÄÏÌÖÎÙ ÚÁÍÅÝÁÔØ ÓÉÓÔÅÍÎÙÅ ×ÅÒÓÉÉ. -\item[õÔÉÌÉÔÙ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ.] ÷ÍÅÓÔÅ Ó ÐÒÏÇÒÁÍÍÁÍÉ \TL{} - ÕÓÔÁÎÁ×ÌÉ×ÁÅÔÓÑ ÒÑÄ ÐÏÒÔÉÒÏ×ÁÎÎÙÈ ÐÏÄ Windows ÓÔÁÎÄÁÒÔÎÙÈ - ÀÎÉËÓÏ×ÓËÉÈ ÕÔÉÌÉÔ: \cmdname{gzip}, \cmdname{chktex}, - \cmdname{jpeg2ps}, \cmdname{unzip}, \cmdname{wget} É ÐÒÏÇÒÁÍÍÙ ÉÚ - ÎÁÂÏÒÁ \cmdname{xpdf}. (óÁÍ \cmdname{xpdf} ÐÏÄ Windows ÎÅ ÒÁÂÏÔÁÅÔ, - ÎÏ ÎÁ ÎÅÍ ÏÓÎÏ×ÁÎÁ ÐÒÏÇÒÁÍÍÁ Sumatra: - \url{http://blog.kowalczyk.info/software/sumatrapdf}.) -\item[\texttt{fc-cache}] ÐÏÍÏÇÁÅÔ \XeTeX Õ ÜÆÆÅËÔÉ×ÎÏ ÒÁÂÏÔÁÔØ ÓÏ - ÛÒÉÆÔÁÍÉ. -\item[PS\_View.] ôÁËÖÅ ÕÓÔÁÎÁ×ÌÉ×ÁÅÔÓÑ PS\_View, ÎÏ×ÁÑ ÐÒÏÇÒÁÍÍÁ ÄÌÑ - ÐÒÏÓÍÏÔÒÁ ÆÁÊÌÏ× ÆÏÒÍÁÔÅ PostScript ÐÏÄ Ó×ÏÂÏÄÎÏÊ ÌÉÃÅÎÚÉÅÊ, - ÓÍ. ÒÉÓÕÎÏË~\ref{fig:psview}. -\end{description} -\begin{description} -\item[äÉÒÅËÔÏÒÉÑ \texttt{support},] ÕÖÅ ÕÐÏÍÑÎÕÔÁÑ × - ÒÁÚÄÅÌÅ~\ref{sec:tld}. ÷ ÜÔÏÊ ÄÉÒÅËÔÏÒÉÉ ÎÁÈÏÄÑÔÓÑ ÒÁÚÌÉÞÎÙÅ - ÐÒÏÇÒÁÍÍÙ, ËÏÔÏÒÙÅ ÍÏÇÕÔ ÂÙÔØ ÐÏÌÅÚÎÙ Ó \TeX ÏÍ, × ÞÁÓÔÎÏÓÔÉ, ÒÑÄ - ÕÄÏÂÎÙÈ ÒÅÄÁËÔÏÒÏ× É ÏÂÏÌÏÞÅË. ðÒÏÇÒÁÍÍÙ × ÜÔÏÊ ÄÉÒÅËÔÏÒÉÉ ÎÅ - ÕÓÔÁÎÁ×ÌÉ×ÁÀÔÓÑ Á×ÔÏÍÁÔÉÞÅÓËÉ. ÷ ÜÔÏÊ ÄÉÒÅËÔÏÒÉÉ ÔÁËÖÅ ÎÁÈÏÄÉÔÓÑ - ÐÒÏÇÒÁÍÍÁ ÄÌÑ ÐÒÏÓÍÏÔÒÁ \dvi{} "--- ÐÒÏÇÒÁÍÍÁ \cmdname{dviout}, ÏÐÉÓÁÎÎÁÑ × - ÓÌÅÄÕÀÝÅÍ ÒÁÚÄÅÌÅ. -\end{description} - -\subsection{ðÒÏÇÒÁÍÍÁ Dviout} - -ë ÓÏÖÁÌÅÎÉÀ, × ÜÔÏÊ ×ÅÒÓÉÉ \TL{} ÎÅÔ Á×ÔÏÍÁÔÉÞÅÓËÉ ÕÓÔÁÎÁ×ÌÉ×ÁÅÍÏÊ -ÐÒÏÇÒÁÍÍÙ ÄÌÑ ÐÒÏÓÍÏÔÒÁ \dvi{} ÄÌÑ Windows. ïÄÎÁËÏ ×Ù ÍÏÖÅÔÅ ÕÓÔÁÎÏ×ÉÔØ -ÐÒÏÇÒÁÍÍÕ ôÏÛÉÏ ïÛÉÍÙ \prog{dviout} ÉÚ ÄÉÒÅËÔÏÒÉÉ -\path{support/dviout/}. ÷ ÜÔÏÊ ÄÉÒÅËÔÏÒÉÉ ÅÓÔØ ÔÁËÖÅ ÎÅÂÏÌØÛÏÊ ÆÁÊÌ -\filename{README}, ÏÐÉÓÙ×ÁÀÝÉÊ ÕÓÔÁÎÏ×ËÕ É ËÏÎÆÉÇÕÒÁÃÉÀ \prog{dviout} -ÄÌÑ \TL{}. ÷ÎÉÍÁÔÅÌØÎÏ ÐÒÏÞÔÉÔÅ ÅÇÏ ÐÅÒÅÄ ÕÓÔÁÎÏ×ËÏÊ. - -ðÒÉ ÐÅÒ×ÏÍ ÚÁÐÕÓËÅ ÐÒÏÇÒÁÍÍÙ ÏÎÁ ÓÏÚÄÁÅÔ ÛÒÉÆÔÙ ÄÌÑ ÐÒÏÓÍÏÔÒÁ ÆÁÊÌÏ×. -åÓÌÉ ×Ù ÂÕÄÅÔÅ ÐÏÌØÚÏ×ÁÔØÓÑ ÅÊ ÎÅËÏÔÏÒÏÅ ×ÒÅÍÑ, ÏÎÁ ÓÏÚÄÁÓÔ -ÐÒÁËÔÉÞÅÓËÉ ×ÓÅ ÎÕÖÎÙÅ ×ÁÍ ÛÒÉÆÔÙ, É ÏËÎÏ ÓÏÚÄÁÎÉÑ ÛÒÉÆÔÏ× ÂÕÄÅÔ -ÐÏÑ×ÌÑÔØÓÑ ×ÓÅ ÒÅÖÅ. äÏÐÏÌÎÉÔÅÌØÎÁÑ ÉÎÆÏÒÍÁÃÉÑ Ï ÐÒÏÇÒÁÍÍÅ ÓÏÄÅÒÖÉÔÓÑ -× (ÏÞÅÎØ ÈÏÒÏÛÅÍ) ÍÅÎÀ ÐÏÍÏÝÉ. - -\subsection{óÓÙÌËÉ ÎÁ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ÐÒÏÇÒÁÍÍÙ} - -÷ÏÔ ÓÓÙÌËÉ ÎÁ ÎÅËÏÔÏÒÙÅ ÄÒÕÇÉÅ ÐÒÏÇÒÁÍÍÙ, ËÏÔÏÒÙÅ ×ÁÍ ÍÏÇÕÔ -ÐÏÎÒÁ×ÉÔØÓÑ: -\begin{description} -\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} -\item[Perl] \url{http://www.activestate.com/} Ó ÄÏÐÏÌÎÉÔÅÌØÎÙÍÉ - ÐÁËÅÔÁÍÉ ÉÚ ÁÒÈÉ×Á \acro{CPAN}, \url{http://www.cpan.org/} -\item[ImageMagick] \url{http://www.imagemagick.com}, ÄÌÑ - ËÏÎ×ÅÒÔÉÒÏ×ÁÎÉÑ É ÐÒÅÏÂÒÁÚÏ×ÁÎÉÑ ÇÒÁÆÉËÉ. -\item[NetPBM] \url{http://netpbm.sourceforge.net/}, ÔÏÖÅ ÄÌÑ ÇÒÁÆÉËÉ/ - -\item[òÅÄÁËÔÏÒÙ ÄÌÑ \TeX Á] éÈ ÏÞÅÎØ ÍÎÏÇÏ, É ×ÙÂÏÒ ÉÈ "--- ÄÅÌÏ - ×ËÕÓÁ. ÷ÏÔ ÎÅÓËÏÌØËÏ, × ÐÒÏÉÚ×ÏÌØÎÏÍ ÐÏÒÑÄËÅ: - \begin{itemize*} - \item \cmdname{GNU Emacs} ÅÓÔØ ÄÌÑ Windows, ÓÍ. - \url{http://www.gnu.org/software/emacs/windows/ntemacs.html}. - \item \cmdname{Emacs} Ó Auc\TeX ÏÍ ÄÌÑ Windows ÅÓÔØ × ÄÉÒÅËÔÏÒÉÉ - \path{support} ÎÁ \TL{}; ÅÇÏ ÓÔÒÁÎÉÃÁ ÎÁ ÓÅÔÉ: - \url{http://www.gnu.org/software/auctex}. - \item \cmdname{WinShell} ÅÓÔØ × ÄÉÒÅËÔÏÒÉÉ \path|support| ÎÁ \TL{}; - ÅÇÏ ÓÔÒÁÎÉÃÁ ÎÁ ÓÅÔÉ: \url{http://www.winshell.de}. - \item \cmdname{WinEdt} ÜÔÏ shareware, ËÏÔÏÒÏÅ ÍÏÖÎÏ ÓËÁÞÁÔØ Ó - \url{http://www.winedt.com}. - \item \cmdname{Vim} ÜÔÏ Ó×ÏÂÏÄÎÁÑ ÐÒÏÇÒÁÍÍÁ, ËÏÔÏÒÕÀ ÍÏÖÎÏ ÓËÁÞÁÔØ Ó - \url{http://www.vim.org}. - \item TeXnicCenter ÜÔÏ Ó×ÏÂÏÄÎÁÑ ÐÒÏÇÒÁÍÍÁ, ËÏÔÏÒÕÀ ÍÏÖÎÏ ÓËÁÞÁÔØ Ó - \url{http://www.toolscenter.org} É × ÄÉÓÔÒÉÂÕÔÉ×Å pro\TeX{}t. - \item \cmdname{LEd} ÍÏÖÎÏ ÓËÁÞÁÔØ Ó \url{http://www.ctan.org/support/LEd}. - \item \cmdname{SciTE} ÍÏÖÎÏ ÓËÁÞÁÔØ Ó - \url{http://www.scintilla.org/SciTE.html}. - \end{itemize*} -\end{description} - -\subsection{äÏÍÁÛÎÑÑ ÄÉÒÅËÔÏÒÉÑ ÐÏÄ Windows} -\label{sec:winhome} - -äÏÍÁÛÎÅÊ ÄÉÒÅËÔÏÒÉÉ ÐÏÄ àÎÉËÓÏÍ ÓÏÏÔ×ÅÔÓÔ×ÕÅÔ ÄÉÒÅËÔÏÒÉÑ -\verb|%USERPROFILE%|. ðÏÄ Windows XP É Windows 2000 ÜÔÏ ÏÂÙÞÎÏ -\verb|C:\Documents and Settings\|, Á ÐÏÄ Windows Vista "--- -\verb|C:\Users\|. ÷ ÆÁÊÌÅ \filename{texmf.cnf} É ×ÏÏÂÝÅ ÐÒÉ -ÒÁÂÏÔÅ \KPS{}, \verb|~| ÐÒÁ×ÉÌØÎÏ ÉÎÔÅÒÐÒÅÔÉÒÕÅÔÓÑ É ÐÏÄ Windows, É -ÐÏÄ àÎÉËÓÏÍ. - -\subsection{òÅÇÉÓÔÒ Windows} -\label{sec:registry} - -Windows ÈÒÁÎÉÔ ÐÏÞÔÉ ×ÓÅ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÄÁÎÎÙÅ × ÒÅÇÉÓÔÒÅ. òÅÇÉÓÔÒ -ÓÏÄÅÒÖÉÔ ÎÁÂÏÒ ÉÅÒÁÒÈÉÞÅÓËÉ ÏÒÇÁÎÉÚÏ×ÁÎÎÙÈ ÚÁÐÉÓÅÊ, Ó ÎÅÓËÏÌØËÉÍÉ -ËÏÒÎÅ×ÙÍÉ ÚÁÐÉÓÑÍÉ. îÁÉÂÏÌÅÅ ×ÁÖÎÙ ÄÌÑ ÐÒÏÇÒÁÍÍ ÕÓÔÁÎÏ×ËÉ ÚÁÐÉÓÉ -\path{HKEY_CURRENT_USER} É \path{HKEY_LOCAL_MACHINE}, ÓÏËÒÁÝÅÎÎÏ -\path{HKCU} É \path{HKLM}. ëÁË ÐÒÁ×ÉÌÏ, \path{HKCU} ÎÁÈÏÄÉÔÓÑ × -ÄÏÍÁÛÎÅÊ ÄÉÒÅËÔÏÒÉÉ ÐÏÌØÚÏ×ÁÔÅÌÑ (ÓÍ. ÒÁÚÄÅÌ~\ref{sec:winhome}), Á -\path{HKLM} "--- ÐÏÄÄÉÒÅËÔÏÒÉÑ ÄÉÒÅËÔÏÒÉÉ Windows. - -éÎÏÇÄÁ ËÏÎÆÉÇÕÒÁÃÉÑ ÓÉÓÔÅÍÙ ÏÐÒÅÄÅÌÑÅÔÓÑ ÐÅÒÅÍÅÎÎÙÍÉ ÏËÒÕÖÅÎÉÑ, ÎÏ -ÎÅËÏÔÏÒÙÅ ×ÅÝÉ (ÎÁÐÒÉÍÅÒ, ÐÏÌÏÖÅÎÉÅ ÑÒÌÙËÏ×) ÚÁÄÁÀÔÓÑ × ÒÅÇÉÓÔÒÅ. äÌÑ -ÔÏÇÏ, ÞÔÏÂÙ ÐÅÒÍÁÎÅÎÔÎÏ ÚÁÄÁÔØ ÐÅÒÅÍÅÎÎÙÅ ÏËÒÕÖÅÎÉÑ, ÔÁËÖÅ ÎÕÖÅÎ -ÄÏÓÔÕÐ Ë ÒÅÇÉÓÔÒÕ. - -\subsection{ðÒÁ×Á ÄÏÓÔÕÐÁ ÐÏÄ Windows} -\label{sec:winpermissions} - -÷ ÐÏÚÄÎÉÈ ×ÅÒÓÉÑÈ Windows ÄÅÌÁÅÔÓÑ ÒÁÚÌÉÞÉÅ ÍÅÖÄÕ ÏÂÙÞÎÙÍÉ -ÐÏÌØÚÏ×ÁÔÅÌÑÍÉ É ÁÄÍÉÎÉÓÔÒÁÔÏÒÁÍÉ, ÐÒÉÞÅÍ ÔÏÌØËÏ ÐÏÓÌÅÄÎÉÅ ÉÍÅÀÔ ÐÒÁ×Ï -ÄÏÓÔÕÐÁ ËÏ ×ÓÅÊ ÏÐÅÒÁÃÉÏÎÎÏÊ ÓÉÓÔÅÍÅ. îÁ ÐÒÁËÔÉËÅ ÏÄÎÁËÏ ÂÙÌÏ ÂÙ -ÂÏÌÅÅ ÐÒÁ×ÉÌØÎÏ ÏÐÉÓÙ×ÁÔØ ÜÔÉ ËÌÁÓÓÙ ÐÏÌØÚÏ×ÁÔÅÌÅÊ ËÁË -<<ÎÅÐÒÉ×ÉÌÅÇÉÒÏ×ÁÎÎÙÅ ÐÏÌØÚÏ×ÁÔÅÌÉ>> É <<ÏÂÙÞÎÙÅ ÐÏÌØÚÏ×ÁÔÅÌÉ>>: ÐÒÁ×Á -ÁÄÍÉÎÉÓÔÒÁÔÏÒÁ Ñ×ÌÑÀÔÓÑ ÐÒÁ×ÉÌÏÍ, Á ÎÅ ÉÓËÌÀÞÅÎÉÅÍ. ïÄÎÁËÏ ÍÙ -ÐÏÓÔÁÒÁÌÉÓØ ÓÄÅÌÁÔØ ×ÏÚÍÏÖÎÙÍ ÕÓÔÁÎÏ×ËÕ \TL{} ÂÅÚ ÐÒÁ× -ÁÄÍÉÎÉÓÔÒÁÔÏÒÁ. - -åÓÌÉ ÐÏÌØÚÏ×ÁÔÅÌØ Ñ×ÌÑÅÔÓÑ ÁÄÍÉÎÉÓÔÒÁÔÏÒÏÍ, ÑÒÌÙËÉ ÓÏÚÄÁÀÔÓÑ ÄÌÑ ×ÓÅÈ -ÐÏÌØÚÏ×ÁÔÅÌÅÊ, É ÍÏÄÉÆÉÃÉÒÕÀÔÓÑ ÓÉÓÔÅÍÎÙÅ ÐÁÒÁÍÅÔÒÙ. ÷ ÐÒÏÔÉ×ÎÏÍ -ÓÌÕÞÁÅ ÑÒÌÙËÉ É ÍÅÎÀ ÓÏÚÄÁÀÔÓÑ ÔÏÌØËÏ ÄÌÑ ÔÅËÕÝÅÇÏ ÐÏÌØÚÏ×ÁÔÅÌÑ, É -ÍÏÄÉÆÉÃÉÒÕÀÔÓÑ ÅÇÏ ÐÁÒÁÍÅÔÒÙ. åÓÌÉ ×Ù ÈÏÔÉÔÅ ÕÓÔÁÎÏ×ÉÔØ ÓÉÓÔÅÍÕ -ÔÏÌØËÏ ÄÌÑ ÏÄÎÏÇÏ ÐÏÌØÚÏ×ÁÔÅÌÑ, ÄÁÖÅ ÂÕÄÕÞÉ ÁÄÍÉÎÉÓÔÒÁÔÏÒÏÍ, -ÉÓÐÏÌØÚÕÊÔÅ ÏÐÃÉÀ \optname{non-admin} ÐÒÏÇÒÁÍÍÙ \prog{install-tl}. - -÷ÎÅ ÚÁ×ÉÓÉÍÏÓÔÉ ÏÔ ÓÔÁÔÕÓÁ ÐÏÌØÚÏ×ÁÔÅÌÑ, ËÏÒÅÎØ ÕÓÔÁÎÏ×ËÉ \TL{}, -ÐÒÅÄÌÁÇÁÅÍÙÊ ÐÏ ÕÍÏÌÞÁÎÉÀ, ×ÓÅÇÄÁ ÎÁÈÏÄÉÔÓÑ ÐÏÄ -\verb|%PROGRAMFILES%|. ðÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ ×ÓÅÇÄÁ ÐÒÏ×ÅÒÑÅÔ, ÏÔËÒÙÔÁ -ÌÉ ËÏÒÎÅ×ÁÑ ÄÉÒÅËÔÏÒÉÑ ÄÌÑ ÔÅËÕÝÅÇÏ ÐÏÌØÚÏ×ÁÔÅÌÑ. - -íÏÖÅÔ ×ÏÚÎÉËÎÕÔØ ÐÒÏÂÌÅÍÁ, ÅÓÌÉ Õ ÐÏÌØÚÏ×ÁÔÅÌÑ ÎÅÔ ÐÒÁ× -ÁÄÍÉÎÉÓÔÒÁÔÏÒÁ, Á × ÐÕÔÉ ÐÏÉÓËÁ ÕÖÅ ÅÓÔØ \TeX{}. ðÏÓËÏÌØËÕ × ÐÕÔÉ -ÐÏÉÓËÁ ÓÉÓÔÅÍÎÙÊ ÐÕÔØ ÓÔÏÉÔ ÐÅÒÅÄ ÐÕÔÅÍ ÐÏÌØÚÏ×ÁÔÅÌÑ, \TeX{} ÉÚ \TL{} -ÎÅ ÂÕÄÅÔ ÎÁÊÄÅÎ. þÔÏÂÙ ÏÂÏÊÔÉ ÜÔÕ ÐÒÏÂÌÅÍÕ, ÐÒÏÇÒÁÍÍÁ × ÔÁËÏÍ ÓÌÕÞÁÅ -ÓÏÚÄÁÅÔ ÑÒÌÙË Ó ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÏÊ, × ËÏÔÏÒÏÊ ÄÉÒÅËÔÏÒÉÑ \TL{} ÓÔÏÉÔ -ÐÅÒ×ÏÊ × ÐÕÔÉ ÐÏÉÓËÁ. éÚ ÜÔÏÊ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ ÍÏÖÎÏ ÐÏÌØÚÏ×ÁÔØÓÑ -\TL{}. - -\section{òÕËÏ×ÏÄÓÔ×Ï ÐÏÌØÚÏ×ÁÔÅÌÑ Web2C} - -\Webc{} "--- ÜÔÏ ÉÎÔÅÇÒÉÒÏ×ÁÎÎÁÑ ËÏÌÌÅËÃÉÑ ÐÒÏÇÒÁÍÍ, ÏÔÎÏÓÑÝÉÈÓÑ Ë -\TeX{}Õ: ÓÁÍ \TeX{}, \MF{}, \MP, \BibTeX{}, É Ô.Ä. üÔÏ ÓÅÒÄÃÅ -\TL{}. óÔÒÁÎÉÃÁ \Webc{} Ó ÒÕËÏ×ÏÄÓÔ×ÏÍ ÐÏÌØÚÏ×ÁÔÅÌÑ É ÍÎÏÇÉÍ ÄÒÕÇÉÍ -ÎÁÈÏÄÉÔÓÑ ÎÁ \url{http://tug.org/web2c}. - -îÅÍÎÏÇÏ ÉÓÔÏÒÉÉ. ðÅÒ×ÁÑ ×ÅÒÓÉÑ ÐÒÏÇÒÁÍÍÙ ÂÙÌÁ ÎÁÐÉÓÁÎÁ ôÏÍÁÓÏÍ -òÏËÉËÉ, ËÏÔÏÒÙÊ × 1987 ÇÏÄÕ ÓÏÚÄÁÌ ÓÉÓÔÅÍÕ \TeX{}-to-C, ÁÄÁÐÔÉÒÏ×Á× -ÐÁÔÞÉ ÄÌÑ àÎÉËÓÁ, ÒÁÚÒÁÂÏÔÁÎÎÙÅ × ÏÓÎÏ×ÎÏÍ çÏ×ÁÒÄÏÍ ôÒÉËÉ É ðÁ×ÌÏÍ -ëÕÒÔÉÓÏÍ. ôÉÍ íÏÒÇÁÎ ÓÔÁÌ ÐÏÄÄÅÒÖÉ×ÁÔØ ÓÉÓÔÅÍÕ, É × ÜÔÏÔ ÐÅÒÉÏÄ Å£ -ÎÁÚ×ÁÎÉÅ ÓÍÅÎÉÌÏÓØ ÎÁ Web-to-C\@. ÷ 1990 ÇÏÄÕ ëÁÒÌ âÅÒÒÉ ×ÚÑÌ ÎÁ ÓÅÂÑ -ÜÔÏÔ ÐÒÏÅËÔ, ËÏÏÒÄÉÎÉÒÕÑ ÒÁÂÏÔÕ ÄÅÓÑÔËÏ× ÐÒÏÇÒÁÍÍÉÓÔÏ×, Á × 1997 ÏÎ -ÐÅÒÅÄÁÌ ÒÕËÏ×ÏÄÓÔ×Ï ïÌÁÆÕ ÷ÅÂÅÒÕ. - -óÉÓÔÅÍÁ \Webc{} ÒÁÂÏÔÁÅÔ ÎÁ àÎÉËÓÅ, 32-ÂÉÔÏ×ÙÈ Windows, \MacOSX{}, É -ÄÒÕÇÉÈ ÏÐÅÒÁÃÉÏÎÎÙÈ ÓÉÓÔÅÍÁÈ. ïÎÁ ÉÓÐÏÌØÚÕÅÔ ÏÒÉÇÉÎÁÌØÎÙÅ ÉÓÈÏÄÎÉËÉ -ëÎÕÔÁ ÄÌÑ \TeX{}Á É ÄÒÕÇÉÈ ÐÒÏÇÒÁÍÍ, ÎÁÐÉÓÁÎÎÙÈ ÎÁ ÑÚÙËÅ \web{} É -ÐÅÒÅ×ÅÄ£ÎÎÙÈ ÎÁ C. ïÓÎÏ×ÎÙÅ ÐÒÏÇÒÁÍÍÙ ÓÉÓÔÅÍÙ: - -\begin{cmddescription} -\item[bibtex] ðÏÄÄÅÒÖËÁ ÂÉÂÌÉÏÇÒÁÆÉÊ. -\item[dmp] ðÅÒÅ×ÏÄ \cmdname{troff} × MPX (ËÁÒÔÉÎËÉ × \MP{}). -\item[dvicopy] òÁÓËÒÙÔÉÅ ×ÉÒÔÕÁÌØÎÙÅ ÛÒÉÆÔÙ × ÆÁÊÌÁÈ \dvi{}. -\item[dvitomp] ðÅÒÅ×ÏÄ \dvi{} × MPX (ÒÉÓÕÎËÉ × \MP{}). -\item[dvitype] ðÅÒÅ×ÏÄ \dvi{} × ÔÅËÓÔ. -\item[gftodvi] çÒÁÎËÉ ÛÒÉÆÔÏ×. -\item[gftopk] õÐÁËÏ×ËÁ ÛÒÉÆÔÏ× -\item[gftype] ðÅÒÅ×ÏÄ GF × ÔÅËÓÔ. -\item[makempx] ÷£ÒÓÔËÁ ÍÅÔÏË \MP{}. -\item[mf] óÏÚÄÁÎÉÅ ÛÒÉÆÔÏ×. -\item[mft] ÷£ÒÓÔËÁ ÉÓÈÏÄÎÉËÏ× \MF{}. -\item[mpost] óÏÚÄÁÎÉÅ ÔÅÈÎÉÞÅÓËÉÈ ÄÉÁÇÒÁÍÍ. -\item[mpto] éÚ×ÌÅÞÅÎÉÅ ÍÅÔÏË \MP{}. -\item[newer] óÒÁ×ÎÅÎÉÅ ÄÁÔ ÍÏÄÉÆÉËÁÃÉÉ. -\item[patgen] óÏÚÄÁÎÉÅ ÔÁÂÌÉà ÐÅÒÅÎÏÓÏ×. -\item[pktogf] ðÅÒÅ×ÏÄ PK × GF. -\item[pktype] ðÅÒÅ×ÏÄ PK × ÔÅËÓÔ -\item[pltotf] ðÅÒÅ×ÏÄ ÉÚ ÓÐÉÓËÁ Ó×ÏÊÓÔ× ÛÒÉÆÔÁ × TFM. -\item[pooltype] ðÏËÁÚ ÆÁÊÌÏ× pool × \web{}. -\item[tangle] ðÅÒÅ×ÏÄ \web{} × Pascal. -\item[tex] ÷£ÒÓÔËÁ. -\item[tftopl] ðÅÒÅ×ÏÄ TFM × ÓÐÉÓÏË Ó×ÏÊÓÔ× ÛÒÉÆÔÁ. -\item[vftovp] ðÅÒÅ×ÏÄ ×ÉÒÔÕÁÌØÎÏÇÏ ÛÒÉÆÔÁ × ÓÐÉÓÏË Ó×ÏÊÓÔ× ÛÒÉÆÔÁ. -\item[vptovf] ðÅÒÅ×ÏÄ ÓÐÉÓËÁ Ó×ÏÊÓÔ× ÛÒÉÆÔÁ × ×ÉÒÔÕÁÌØÎÙÊ ÛÒÉÆÔ. -\item[weave] ðÅÒÅ×ÏÄ \web{} × \TeX. -\end{cmddescription} - -\noindent ðÏÌÎÏÓÔØÀ ÜÔÉ ÐÒÏÇÒÁÍÍÙ ÏÐÉÓÁÎÙ × ÄÏËÕÍÅÎÔÁÃÉÉ Ë -ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÍ ÐÁËÅÔÁÍ É ÓÁÍÏÊ \Webc{}. ïÄÎÁËÏ ÚÎÁÎÉÅ ÎÅËÏÔÏÒÙÈ -ÏÂÝÉÈ ÐÒÉÎÃÉÐÏ× ÄÌÑ ×ÓÅÊ ÓÅÍØÉ ÐÒÏÇÒÁÍÍ ÐÏÍÏÖÅÔ ×ÁÍ ÐÏÌÎÅÅ -ÉÓÐÏÌØÚÏ×ÁÔØ ÐÒÏÇÒÁÍÍÙ ÓÉÓÔÅÍÙ \Webc{}. - -÷ÓÅ ÐÒÏÇÒÁÍÍÙ ÐÏÄÄÅÒÖÉ×ÁÀÔ ÓÔÁÎÄÁÒÔÎÙÅ ÏÐÃÉÉ \acro{GNU}: -\begin{ttdescription} -\item[-{}-help] ÎÁÐÅÞÁÔÁÔØ ËÒÁÔËÕÀ ÓÐÒÁ×ËÕ -\item[-{}-verbose] ÐÅÞÁÔÁÔØ ÐÏÄÒÏÂÎÕÀ ÉÎÆÏÒÍÁÃÉÀ ÐÏ ÍÅÒÅ ÒÁÂÏÔÙ -\item[-{}-version] îÁÐÅÞÁÔÁÔØ ×ÅÒÓÉÀ ÐÒÏÇÒÁÍÍÙ É ÚÁ×ÅÒÛÉÔØ ÒÁÂÏÔÕ. -\end{ttdescription} - -äÌÑ ÐÏÉÓËÁ ÆÁÊÌÏ× ÐÒÏÇÒÁÍÍÙ \Webc{} ÉÓÐÏÌØÚÕÀÔ ÂÉÂÌÉÏÔÅËÕ \KPS{} -(\url{http://tug.org/kpathsea}). üÔÁ ÂÉÂÌÉÏÔÅËÁ ÉÓÐÏÌØÚÕÅÔ ËÏÍÂÉÎÁÃÉÀ -ÐÅÒÅÍÅÎÎÙÈ ÏËÒÕÖÅÎÉÑ É ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÈ ÆÁÊÌÏ×, ÞÔÏÂÙ ÎÁÊÔÉ ÎÕÖÎÙÅ -ÆÁÊÌÙ × ÏÇÒÏÍÎÏÊ ÓÉÓÔÅÍÅ \TeX{}. \Webc{} ÍÏÖÅÔ ÐÒÏÓÍÁÔÒÉ×ÁÔØ -ÏÄÎÏ×ÒÅÍÅÎÎÏ ÂÏÌØÛÅ ÏÄÎÏÇÏ ÄÅÒÅ×Á ÄÉÒÅËÔÏÒÉÊ, ÞÔÏ ÐÏÌÅÚÎÏ ÄÌÑ ÒÁÂÏÔÙ -ÓÏ ÓÔÁÎÄÁÒÔÎÙÍ ÄÉÓÔÒÉÂÕÔÉ×ÏÍ \TeX{}Á É ÅÇÏ ÌÏËÁÌØÎÙÍÉ ÒÁÓÛÉÒÅÎÉÑÍÉ. -äÌÑ ÕÓËÏÒÅÎÉÑ ÐÏÉÓËÏ× ÆÁÊÌÏ× ËÁÖÄÏÅ ÄÅÒÅ×Ï ÓÏÄÅÒÖÉÔ ÆÁÊÌ \file{ls-R}, -× ËÏÔÏÒÏÍ ÕËÁÚÁÎÙ ÎÁÚ×ÁÎÉÑ É ÏÔÎÏÓÉÔÅÌØÎÙÅ ÐÕÔÉ ×ÓÅÈ ÆÁÊÌÏ× × ÜÔÏÍ -ÄÅÒÅ×Å. - -\subsection{ðÏÉÓË ÆÁÊÌÏ× × Kpathsea} -\label{sec:kpathsea} - -òÁÓÓÍÏÔÒÉÍ ÓÎÁÞÁÌÁ ÏÂÝÉÊ ÁÌÇÏÒÉÔÍ ÂÉÂÌÉÏÔÅËÉ \KPS. - -âÕÄÅÍ ÎÁÚÙ×ÁÔØ \emph{ÐÕÔ£Í ÐÏÉÓËÁ} ÎÁÂÏÒ ÒÁÚÄÅÌ£ÎÎÙÈ Ä×ÏÅÔÏÞÉÅÍ ÉÌÉ -ÔÏÞËÏÊ Ó ÚÁÐÑÔÏÊ \emph{ÜÌÅÍÅÎÔÏ× ÐÕÔÉ}, ÐÒÅÄÓÔÁ×ÌÑÀÝÉÈ ÉÚ ÓÅÂÑ × -ÏÓÎÏ×ÎÏÍ ÎÁÚ×ÁÎÉÑ ÄÉÒÅËÔÏÒÉÊ. ðÕÔØ ÐÏÉÓËÁ ÍÏÖÅÔ ÉÍÅÔØ ÍÎÏÇÏ -ÉÓÔÏÞÎÉËÏ×. þÔÏÂÙ ÎÁÊÔÉ ÆÁÊÌ \samp{my-file} × ÄÉÒÅËÔÏÒÉÉ -\samp{.:/dir}, \KPS{} ÐÒÏ×ÅÒÑÅÔ ËÁÖÄÙÊ ÜÌÅÍÅÎÔ ÐÕÔÉ ÐÏ ÏÞÅÒÅÄÉ: -ÓÎÁÞÁÌÁ \file{./my-file}, ÚÁÔÅÍ \file{/dir/my-file}, ×ÏÚ×ÒÁÝÁÑ ÐÅÒ×ÙÊ -ÆÁÊÌ (ÉÌÉ, ×ÏÚÍÏÖÎÏ, ×ÓÅ ÆÁÊÌÙ). - -þÔÏÂÙ ÒÁÂÏÔÁÔØ Ó ÒÁÚÎÙÍÉ ÏÐÅÒÁÃÉÏÎÎÙÍÉ ÓÉÓÔÅÍÁÍÉ, \KPS{} ÐÏÄ ÓÉÓÔÅÍÏÊ, -ÏÔÌÉÞÎÏÊ ÏÔ àÎÉËÓÁ ÍÏÖÅÔ ÉÓÐÏÌØÚÏ×ÁÔØ ÒÁÚÄÅÌÉÔÅÌÉ, ÏÔÌÉÞÎÙÅ ÏÔ -\samp{:} É \samp{/}. - -þÔÏÂÙ ÐÒÏ×ÅÒÉÔØ ÏÐÒÅÄÅÌ£ÎÎÙÊ ÜÌÅÍÅÎÔ ÐÕÔÉ \var{p}, \KPS{} ×ÎÁÞÁÌÅ -ÐÒÏ×ÅÒÑÅÔ ÎÁÌÉÞÉÅ ÂÁÚÙ ÄÁÎÎÙÈ (ÓÍ. ÒÁÚÄÅÌ <<âÁÚÁ ÄÁÎÎÙÈ -ÆÁÊÌÏ×>> ÎÁ ÓÔÒ.~\pageref{sec:filename-database}), Ô.Å., ÅÓÔØ ÌÉ ÂÁÚÁ × -ÄÉÒÅËÔÏÒÉÉ, ËÏÔÏÒÁÑ Ñ×ÌÑÅÔÓÑ ÐÒÅÆÉËÓÏÍ ÄÌÑ \var{p}. åÓÌÉ ÜÔÏ ÔÁË, -ÓÐÅÃÉÆÉËÁÃÉÑ ÐÕÔÉ ÓÒÁ×ÎÉ×ÁÅÔÓÑ Ó ÓÏÄÅÒÖÉÍÙÍ ÂÁÚÙ ÄÁÎÎÙÈ. - -åÓÌÉ ÂÁÚÁ ÄÁÎÎÙÈ ÎÅ ÓÕÝÅÓÔ×ÕÅÔ, ÉÌÉ ÎÅ ÏÔÎÏÓÉÔÓÑ Ë ÜÔÏÍÕ ÜÌÅÍÅÎÔÕ -ÐÕÔÉ, ÉÌÉ ÎÅ ÓÏÄÅÒÖÉÔ ÎÕÖÎÏÇÏ ÜÌÅÍÅÎÔÁ, ÐÒÏ×ÅÒÑÅÔÓÑ ÆÁÊÌÏ×ÁÑ ÓÉÓÔÅÍÁ -(ÅÓÌÉ ÜÔÏ ÎÅ ÚÁÐÒÅÝÅÎÏ ÓÐÅÃÉÆÉËÁÃÉÅÊ, ÎÁÞÉÎÁÀÝÅÊÓÑ Ó \samp{!!}, É ÅÓÌÉ -ÆÁÊÌ ÄÏÌÖÅÎ ÓÕÝÅÓÔ×Ï×ÁÔØ). \KPS{} ËÏÎÓÔÒÕÉÒÕÅÔ ÓÐÉÓÏË ÄÉÒÅËÔÏÒÉÊ, -ËÏÔÏÒÙÅ ÓÏÏÔ×ÅÔÓÔ×ÕÀÔ ÜÌÅÍÅÎÔÕ, É × ËÁÖÄÏÊ ÄÉÒÅËÔÏÒÉÉ ÉÝÅÔ ÎÕÖÎÙÊ -ÆÁÊÌ. - -õÓÌÏ×ÉÅ <<ÆÁÊÌ ÄÏÌÖÅÎ ÓÕÝÅÓÔ×Ï×ÁÔØ>> ×ÁÖÎÏ ÄÌÑ ÆÁÊÌÏ× \samp{.vf} É -ÆÁÊÌÏ×, ËÏÔÏÒÙÅ ÏÔËÒÙ×ÁÅÔ \TeX{} ÐÏ ËÏÍÁÎÄÅ \cs{openin}. ôÁËÉÅ ÆÁÊÌÙ -ÍÏÇÕÔ É ÎÅ ÓÕÝÅÓÔ×Ï×ÁÔØ (ÎÁÐÒÉÍÅÒ, ÆÁÊÌ \file{cmr10.vf}), É ÂÙÌÏ ÂÙ -ÎÅÐÒÁ×ÉÌØÎÏ ÉÓËÁÔØ ÉÈ ÎÁ ÄÉÓËÅ. ðÏÜÔÏÍÕ, ÅÓÌÉ ×Ù ÎÅ ÏÂÎÏ×ÉÔÅ -\file{ls-R} ÐÒÉ ÕÓÔÁÎÏ×ËÅ ÎÏ×ÏÇÏ ÆÁÊÌÁ \samp{.vf}, ÏÎ ÎÉËÏÇÄÁ ÎÅ ÂÕÄÅÔ -ÎÁÊÄÅÎ. ëÁÖÄÙÊ ÜÌÅÍÅÎÔ ÐÕÔÉ ÉÝÅÔÓÑ ÐÏ ÏÞÅÒÅÄÉ: ÓÎÁÞÁÌÁ ÂÁÚÁ ÄÁÎÎÙÈ, -ÚÁÔÅÍ ÄÉÓË. åÓÌÉ ÎÕÖÎÙÊ ÆÁÊÌ ÎÁÊÄÅÎ, ÐÏÉÓË ÏÓÔÁÎÁ×ÌÉ×ÁÅÔÓÑ, É -×ÏÚ×ÒÁÝÁÅÔÓÑ ÒÅÚÕÌØÔÁÔ. - -èÏÔÑ ÓÁÍÙÊ ÐÒÏÓÔÏÊ É ÞÁÓÔÏ ×ÓÔÒÅÞÁÀÝÉÊÓÑ ÜÌÅÍÅÎÔ ÐÕÔÉ "--- ÜÔÏ -ÎÁÚ×ÁÎÉÅ ÄÉÒÅËÔÏÒÉÉ, \KPS{} ÐÏÄÄÅÒÖÉ×ÁÅÔ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ×ÏÚÍÏÖÎÏÓÔÉ: -ÒÁÚÎÏÏÂÒÁÚÎÙÅ ÚÎÁÞÅÎÉÑ ÐÏ ÕÍÏÌÞÁÎÉÀ, ÉÍÅÎÁ ÐÅÒÅÍÅÎÎÙÈ ÏËÒÕÖÅÎÉÑ, -ÚÎÁÞÅÎÉÑ ÉÚ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÈ ÆÁÊÌÏ×, ÄÏÍÁÛÎÉÅ ÄÉÒÅËÔÏÒÉÉ -ÐÏÌØÚÏ×ÁÔÅÌÅÊ, ÒÅËÕÒÓÉ×ÎÙÊ ÐÏÉÓË ÐÏÄÄÉÒÅËÔÏÒÉÊ. ðÏÜÔÏÍÕ ÍÙ ÇÏ×ÏÒÉÍ, -ÞÔÏ \KPS{} \emph{×ÙÞÉÓÌÑÅÔ} ÜÌÅÍÅÎÔ ÐÕÔÉ, Ô.Å., ÞÔÏ ÂÉÂÌÉÏÔÅËÁ -ÐÒÅÏÂÒÁÚÕÅÔ ÓÐÅÃÉÆÉËÁÃÉÉ × ÉÍÑ ÉÌÉ ÉÍÅÎÁ ÄÉÒÅËÔÏÒÉÉ. üÔÏ ÏÐÉÓÁÎÏ × -ÓÌÅÄÕÀÝÉÈ ÒÁÚÄÅÌÁÈ × ÔÏÍ ÖÅ ÐÏÒÑÄËÅ, × ËÏÔÏÒÏÍ ÐÒÏÉÓÈÏÄÉÔ ÐÏÉÓË. - -úÁÍÅÔØÔÅ, ÞÔÏ ÉÍÑ ÆÁÊÌÁ ÐÒÉ ÐÏÉÓËÅ ÍÏÖÅÔ ÂÙÔØ ÁÂÓÏÌÀÔÎÙÍ ÉÌÉ -ÏÔÎÏÓÉÔÅÌØÎÙÍ, Ô.Å. ÎÁÞÉÎÁÔØÓÑ Ó \samp{/}, ÉÌÉ \samp{./}, ÉÌÉ -\samp{../}, \KPS{} ÐÒÏÓÔÏ ÐÒÏ×ÅÒÑÅÔ, ÓÕÝÅÓÔ×ÕÅÔ ÌÉ ÆÁÊÌ. - -\ifSingleColumn -\else -\begin{figure*} -\verbatiminput{examples/ex5.tex} -\setlength{\abovecaptionskip}{0pt} - \caption{ðÒÉÍÅÒ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÏÇÏ ÆÁÊÌÁ} - \label{fig:config-sample} -\end{figure*} -\fi - -\subsubsection{éÓÔÏÞÎÉËÉ ÐÕÔÅÊ ÐÏÉÓËÁ} -\label{sec:path-sources} - -ðÕÔØ ÐÏÉÓËÁ ÍÏÖÅÔ ÉÍÅÔØ ÒÁÚÎÙÅ ÉÓÔÏÞÎÉËÉ. \KPS{} ÉÓÐÏÌØÚÕÅÔ ÉÈ × -ÓÌÅÄÕÀÝÅÍ ÐÏÒÑÄËÅ: - -\begin{enumerate} -\item õÓÔÁÎÏ×ÌÅÎÎÙÅ ÐÏÌØÚÏ×ÁÔÅÌÅÍ ÐÅÒÅÍÅÎÎÙÅ ÏËÒÕÖÅÎÉÑ, ÎÁÐÒÉÍÅÒ - \envname{TEXINPUTS}\@. ðÅÒÅÍÅÎÎÙÅ ÏËÒÕÖÅÎÉÑ Ó ÔÏÞËÏÊ É ÎÁÚ×ÁÎÉÅÍ - ÐÒÏÇÒÁÍÍÙ ÉÍÅÀÔ ÐÒÅÉÍÕÝÅÓÔ×Ï; ÎÁÐÒÉÍÅÒ ÅÓÌÉ \samp{latex} "--- ÉÍÑ - ÐÒÏÇÒÁÍÍÙ. ÔÏ \envname{TEXINPUTS.latex} ÉÍÅÅÔ ÐÒÅÉÍÕÝÅÓÔ×Ï ÐÅÒÅÄ - \envname{TEXINPUTS}. -\item - ëÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ, ÓÐÅÃÉÆÉÞÅÓËÉÊ ÄÌÑ ÄÁÎÎÏÊ ÐÒÏÇÒÁÍÍÙ, ÎÁÐÒÉÍÅÒ, - ÓÔÒÏËÁ - \samp{S /a:/b} × \file{config.ps} ÄÌÑ \cmdname{dvips}. -\item - ëÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ \KPS{} \file{texmf.cnf}, ÓÏÄÅÒÖÁÝÉÊ ÓÔÒÏËÕ - ÔÉÐÁ - \samp{TEXINPUTS=/c:/d} (ÓÍ. ÎÉÖÅ). -\item úÎÁÞÅÎÉÅ, ÚÁÄÁÎÎÏÅ ÐÒÉ ËÏÍÐÉÌÑÃÉÉ. -\end{enumerate} -\noindent ÷Ù ÍÏÖÅÔÅ Õ×ÉÄÅÔØ ËÁÖÄÏÅ ÉÚ ÜÔÉÈ ÚÎÁÞÅÎÉÊ ÄÌÑ ÄÁÎÎÏÇÏ ÐÕÔÉ -ÐÏÉÓËÁ, ÚÁÄÁ× ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÊ ÕÒÏ×ÅÎØ ÏÔÌÁÄËÉ (ÓÍ. <<ïÔÌÁÄËÁ>> -ÎÁ ÓÔÒ.~\pageref{sec:debugging}). - -\subsubsection{ëÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÆÁÊÌÙ} - -\begingroup\tolerance=3500 -\KPS{} ÞÉÔÁÅÔ \emph{ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÆÁÊÌÙ} -\file{texmf.cnf} ÄÌÑ ÚÁÄÁÎÉÑ Ó×ÏÉÈ ÐÁÒÁÍÅÔÒÏ×. ðÕÔØ ÐÏÉÓËÁ ÄÌÑ ÜÔÉÈ -ÆÁÊÌÏ× ÎÁÚÙ×ÁÅÔÓÑ \envname{TEXMFCNF} (ÐÏ ÕÍÏÌÞÁÎÉÀ, ÔÁËÏÊ ÆÁÊÌ -ÎÁÈÏÄÉÔÓÑ × ÐÏÄÄÉÒÅËÔÏÒÉÉ \file{texmf/web2c}). \emph{÷ÓÅ} ÎÁÊÄÅÎÎÙÅ -ÆÁÊÌÙ \file{texmf.cnf} ÂÕÄÕÔ ÐÒÏÞÉÔÁÎÙ, É ÏÐÒÅÄÅÌÅÎÉÑ × ÂÏÌÅÅ ÒÁÎÎÉÈ -ÆÁÊÌÁÈ ÉÍÅÀÔ ÐÒÅÉÍÕÝÅÓÔ×Ï ÐÅÒÅÄ ÏÐÒÅÄÅÌÅÎÉÑÍÉ × ÂÏÌÅÅ ÐÏÚÄÎÉÈ. ôÁËÉÍ -ÏÂÒÁÚÏÍ, ÅÓÌÉ ÐÕÔØ ÐÏÉÓËÁ ÚÁÄÁÎ ËÁË \verb|.:$TEXMF|, ÚÎÁÞÅÎÉÑ × -\file{./texmf.cnf} ÉÍÅÀÔ ÐÒÅÉÍÕÝÅÓÔ×Ï ÐÅÒÅÄ ÚÎÁÞÅÎÉÑÍÉ × -\verb|$TEXMF/texmf.cnf|. -\endgroup - -\begin{itemize} -\item - ëÏÍÍÅÎÔÁÒÉÉ ÎÁÞÉÎÁÀÔÓÑ Ó \code{\%} É ÐÒÏÄÏÌÖÁÀÔÓÑ ÄÏ ËÏÎÃÁ ÓÔÒÏËÉ. -\item - ðÕÓÔÙÅ ÓÔÒÏËÉ ÉÇÎÏÒÉÒÕÀÔÓÑ -\item - \bs{} × ËÏÎÃÅ ÓÔÒÏËÉ ÏÚÎÁÞÁÅÔ ÐÒÏÄÏÌÖÅÎÉÅ, Ô.Å. ÄÏÂÁ×ÌÑÅÔÓÑ - ÓÌÅÄÕÀÝÁÑ ÓÔÒÏËÁ. ðÒÏÂÅÌÙ × ÎÁÞÁÌÅ ÓÌÅÄÕÀÝÅÊ ÓÔÒÏËÉ ÎÅ - ÉÇÎÏÒÉÒÕÀÔÓÑ. -\item - ïÓÔÁ×ÛÉÅÓÑ ÓÔÒÏËÉ ÉÍÅÀÔ ×ÉÄ -\begin{alltt} - \emph{variable}[.\emph{progname}] [=] \emph{value} -\end{alltt}% - ÇÄÅ \samp{=} É ÐÒÏÂÅÌÙ ×ÏËÒÕÇ ÍÏÇÕÔ ÏÐÕÓËÁÔØÓÑ. -\item - \ttvar{variable} ÍÏÖÅÔ ÓÏÄÅÒÖÁÔØ ÌÀÂÙÅ ÓÉÍ×ÏÌÙ, ËÒÏÍÅ ÐÒÏÂÅÌÁ, - \samp{=} ÉÌÉ \samp{.}, ÎÏ ÎÁÄ£ÖÎÅÅ ×ÓÅÇÏ ÐÒÉÄÅÒÖÉ×ÁÔØÓÑ ÎÁÂÏÒÁ - \samp{A-Za-z\_}. -\item - åÓÌÉ ÅÓÔØ \samp{.\var{progname}}, ÏÐÒÅÄÅÌÅÎÉÅ ÏÔÎÏÓÉÔÓÑ ÔÏÌØËÏ Ë - ÐÒÏÇÒÁÍÍÅ, ËÏÔÏÒÁÑ ÎÁÚÙ×ÁÅÔÓÑ - \texttt{\var{progname}} ÉÌÉ \texttt{\var{progname}.exe}. üÔÏ - ÐÏÚ×ÏÌÑÅÔ, ÎÁÐÒÉÍÅÒ ÒÁÚÎÙÍ ×ÉÄÁÍ \TeX{}Á ÉÍÅÔØ ÒÁÚÎÙÅ ÐÕÔÉ ÐÏÉÓËÁ. -\item \var{value} ÍÏÖÅÔ ÓÏÄÅÒÖÁÔØ ÌÀÂÙÅ ÓÉÍ×ÏÌÙ, ËÒÏÍÅ - \code{\%} É \samp{@}. îÅÌØÚÑ ÉÓÐÏÌØÚÏ×ÁÔØ - \code{\$\var{var}.\var{prog}} × ÐÒÁ×ÏÊ ÞÁÓÔÉ; ×ÍÅÓÔÏ ÜÔÏÇÏ ×Ù ÄÏÌÖÎÙ - ÚÁÄÁÔØ ÄÏÐÏÌÎÉÔÅÌØÎÕÀ ÐÅÒÅÍÅÎÎÕÀ. - \samp{;} × \samp{:} ÐÏÄ àÎÉËÓÏÍ ÜË×É×ÁÌÅÎÔÎÏ \samp{:}; ÜÔÏ - ÐÏÌÅÚÎÏ, ÞÔÏÂÙ ÐÏÄÄÅÒÖÉ×ÁÔØ ÏÂÝÉÊ ÆÁÊÌ ÄÌÑ àÎÉËÓÁ, \acro{MS-DOS} É - Windows. -\item - ÷ÓÅ ÏÐÒÅÄÅÌÅÎÉÑ ÞÉÔÁÀÔÓÑ ÄÏ ÐÏÄÓÔÁÎÏ×ÏË, ÐÏÜÔÏÍÕ Ë ÐÅÒÅÍÅÎÎÙÍ ÍÏÖÎÏ - ÏÂÒÁÝÁÔØÓÑ ÄÏ ÔÏÇÏ, ËÁË ÏÎÉ ÏÐÒÅÄÅÌÅÎÙ. -\end{itemize} -æÒÁÇÍÅÎÔ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÏÇÏ ÆÁÊÌÁ, ÉÌÌÀÓÔÒÉÒÕÀÝÉÊ ÜÔÉ ÐÒÁ×ÉÌÁ, ÐÒÉ×ÅÄeÎ -\ifSingleColumn -ÎÉÖÅ: - -\verbatiminput{examples/ex5.tex} -\else -ÐÒÉ×ÅÄeÎ ÎÁ òÉÓ.~\ref{fig:config-sample}. -\fi - -\subsubsection{ðÏÄÓÔÁÎÏ×ËÁ ÐÕÔÅÊ} -\label{sec:path-expansion} - - -\KPS{} ÒÁÓÐÏÚÎÁ£Ô ÏÐÒÅÄÅÌ£ÎÎÙÅ ÓÐÅÃÉÁÌØÎÙÅ ÓÉÍ×ÏÌÙ É ËÏÎÓÔÒÕËÃÉÉ × -ÐÕÔÑÈ ÐÏÉÓËÁ, ÁÎÁÌÏÇÉÞÎÙÅ ËÏÎÓÔÒÕËÃÉÑÍ × ÓÔÁÎÄÁÒÔÎÙÈ ÏÂÏÌÏÞËÁÈ -àÎÉËÓÁ. îÁÐÒÉÍÅÒ, ÓÌÏÖÎÙÊ ÐÕÔØ -\verb+~$USER/{foo,bar}//baz+, ÏÚÎÁÞÁÅÔ ×ÓÅ ÐÏÄÄÉÒÅËÔÏÒÉÉ ÄÉÒÅËÔÏÒÉÊ -\file{foo} É \file{bar} × ÄÏÍÁÛÎÅÊ ÄÉÒÅËÔÏÒÉÉ ÐÏÌØÚÏ×ÁÔÅÌÑ -\texttt{\$USER}, ËÏÔÏÒÙÅ ÓÏÄÅÒÖÁÔ ÆÁÊÌ ÉÌÉ ÐÏÄÄÉÒÅËÔÏÒÉÀ \file{baz}. -üÔÏ ÏÂßÑÓÎÅÎÏ × ÓÌÅÄÕÀÝÉÈ ÒÁÚÄÅÌÁÈ. - -%$ -\subsubsection{ðÏÄÓÔÁÎÏ×ËÁ ÐÏ ÕÍÏÌÞÁÎÉÀ} -\label{sec:default-expansion} - -\tolerance=2500 - -åÓÌÉ ÐÕÔØ ÐÏÉÓËÁ Ó ÎÁÉÂÏÌØÛÉÍ ÐÒÉÏÒÉÔÅÔÏÍ (ÓÍ. ÒÁÚÄÅÌ <<éÓÔÏÞÎÉËÉ ÐÕÔÅÊ -ÐÏÉÓËÁ>> ÎÁ ÓÔÒ.~\pageref{sec:path-sources}) ÓÏÄÅÒÖÉÔ \emph{ÄÏÐÏÌÎÉÔÅÌØÎÏÅ - Ä×ÏÅÔÏÞÉÅ} (× ÎÁÞÁÌÅ, × ËÏÎÃÅ, Ä×ÏÊÎÏÅ), \KPS{} ÚÁÍÅÎÑÅÔ ÅÇÏ -ÓÌÅÄÕÀÝÉÍ ÐÏ ÐÒÉÏÒÉÔÅÔÕ ÐÕÔ£Í. åÓÌÉ ÜÔÏÔ ×ÓÔÁ×ÌÅÎÎÙÊ ÐÕÔØ ÓÏÄÅÒÖÉÔ -ÄÏÐÏÌÎÉÔÅÌØÎÏÅ Ä×ÏÅÔÏÞÉÅ, ÔÏ ÖÅ ÐÒÏÉÓÈÏÄÉÔ ÓÏ ÓÌÅÄÕÀÝÉÍ ÐÕÔ£Í. -îÁÐÒÉÍÅÒ, ÅÓÌÉ ÐÅÒÅÍÅÎÎÁÑ ÏËÒÕÖÅÎÉÑ ÚÁÄÁÎÁ ËÁË - -\tolerance=1500 - -\begin{alltt} -> \Ucom{setenv TEXINPUTS /home/karl:} -\end{alltt} -É \code{TEXINPUTS} × ÆÁÊÌÅ \file{texmf.cnf} ÓÏÄÅÒÖÉÔ - -\begin{alltt} - .:\$TEXMF//tex -\end{alltt} -ÔÏ ÐÏÉÓË ÂÕÄÅÔ ÐÒÏÉÓÈÏÄÉÔØ Ó ÐÕÔ£Í - -\begin{alltt} - /home/karl:.:\$TEXMF//tex -\end{alltt} - -ðÏÓËÏÌØËÕ ÂÙÌÏ ÂÙ ÂÅÓÐÏÌÅÚÎÏ ×ÓÔÁ×ÌÑÔØ ÚÎÁÞÅÎÉÅ ÐÏ ÕÍÏÌÞÁÎÉÀ ÂÏÌÅÅ ÞÅÍ -ÏÄÉÎ ÒÁÚ, \KPS{} ÉÚÍÅÎÑÅÔ ÔÏÌØËÏ ÏÄÎÏ ÌÉÛÎÅÅ Ä×ÏÅÔÏÞÉÅ, É ÏÓÔÁ×ÌÑÅÔ -ÏÓÔÁÌØÎÙÅ: ÏÎÁ ÐÒÏ×ÅÒÑÅÔ ÓÎÁÞÁÌÁ Ä×ÏÅÔÏÞÉÅ × ÎÁÞÁÌÅ, ÐÏÔÏÍ × ËÏÎÃÅ, -ÐÏÔÏÍ Ä×ÏÊÎÙÅ Ä×ÏÅÔÏÞÉÑ. - -\subsubsection{ðÏÄÓÔÁÎÏ×ËÁ ÓËÏÂÏË} - -ðÏÌÅÚÎÁ ÔÁËÖÅ ÐÏÄÓÔÁÎÏ×ËÁ ÓËÏÂÏË, ÉÚ-ÚÁ ËÏÔÏÒÏÊ, ÎÁÐÒÉÍÅÒ, -\verb+v{a,b}w+ ÏÚÎÁÞÁÅÔ \verb+vaw:vbw+. ÷ÌÏÖÅÎÎÏÓÔØ ÔÕÔ ÄÏÐÕÓËÁÅÔÓÑ. -âÌÁÇÏÄÁÒÑ ÜÔÏÍÕ ÍÏÖÎÏ ÉÍÅÔØ ÎÅÓËÏÌØËÏ ÉÅÒÁÒÈÉÊ ÄÉÒÅËÔÏÒÉÊ, ÐÕÔ£Í -ÐÒÉÓ×ÏÅÎÉÑ ÚÎÁÞÅÎÉÑ ÓÏ ÓËÏÂËÁÍÉ \code{\$TEXMF}. -îÁÐÒÉÍÅÒ, × ÆÁÊÌÅ \file{texmf.cnf}, ÍÏÖÎÏ ÎÁÊÔÉ ÓÌÅÄÕÀÝÅÅ ÏÐÒÅÄÅÌÅÎÉÅ -(ÜÔÏ ÕÐÒÏÝÅÎÉÅ, ÎÁ ÓÁÍÏÍ ÄÅÌÅ ÔÁÍ ÅÝ£ ÂÏÌØÛÅ ÄÅÒÅ×ØÅ×): -\begin{verbatim} - TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN} -\end{verbatim} -âÌÁÇÏÄÁÒÑ ÜÔÏÍÕ ÍÏÖÎÏ ÐÉÓÁÔØ ÔÁËÏÅ: -\begin{verbatim} - TEXINPUTS = .;$TEXMF/tex// -\end{verbatim} -%$ -ÞÔÏ ÏÚÎÁÞÁÅÔ, ÞÔÏ ËÒÏÍÅ ÔÅËÕÝÅÊ ÄÉÒÅËÔÏÒÉÉ ÂÕÄÅÔ ÐÒÏÉÓÈÏÄÉÔØ ÐÏÉÓË -\emph{ÔÏÌØËÏ} × \code{\$TEXMFHOME/tex}, \code{\$TEXMFLOCAL/tex}, -\code{\$TEXMFVAR/tex} É \code{\$TEXMFMAIN/tex} (ÐÏÓÌÅÄÎÉÅ Ä×Á ÄÅÒÅ×Á -ÉÓÐÏÌØÚÕÀÔ ÆÁÊÌÙ \file{ls-R}). üÔÏ ÕÄÏÂÎÏ ÄÌÑ ÐÏÄÄÅÒÖËÉ Ä×ÕÈ -ÐÁÒÁÌÌÅÌØÎÙÈ ÓÔÒÕËÔÕÒ, <<ÚÁÍÏÒÏÖÅÎÎÏÊ>> (ÎÁÐÒÉÍÅÒ, ÎÁ \CD) É -ÏÂÎÏ×ÌÑÅÍÏÊ ÐÏ ÍÅÒÅ ÐÏÑ×ÌÅÎÉÑ ÎÏ×ÙÈ ×ÅÒÓÉÊ. éÓÐÏÌØÚÕÑ ÐÅÒÅÍÅÎÎÕÀ -\code{\$TEXMF} ×Ï ×ÓÅÈ ÏÐÒÅÄÅÌÅÎÉÑÈ, ÍÏÖÎÏ ÚÁÄÁÔØ ÐÏÉÓË × ÏÂÎÏ×ÌÑÅÍÏÍ -ÄÅÒÅ×Å ÐÅÒ×ÙÍ. - -\subsubsection{ðÏÄÓÔÁÎÏ×ËÁ ÐÏÄÄÉÒÅËÔÏÒÉÊ} -\label{sec:subdirectory-expansion} - -ä×Á ÉÌÉ ÂÏÌÅÅ ÓÌÜÛÁ \samp{/} × ÜÌÅÍÅÎÔÅ ÐÕÔÉ ×ÓÌÅÄ ÚÁ ÉÍÅÎÅÍ ÄÉÒÅËÔÏÒÉÉ -\var{d} ÚÁÍÅÎÑÀÔÓÑ ×ÓÅÍÉ ÐÏÄÄÉÒÅËÔÏÒÉÑÍÉ \var{d} ÒÅËÕÒÓÉ×ÎÏ. îÁ ËÁÖÄÏÍ -ÕÒÏ×ÎÅ ÐÏÒÑÄÏË ÐÏÉÓËÁ ÐÏ ÄÉÒÅËÔÏÒÉÑÍ \emph{ÎÅ ÏÐÒÅÄÅÌ£Î}. - -åÓÌÉ ×Ù ÏÐÒÅÄÅÌÉÔÅ ËÏÍÐÏÎÅÎÔÙ ÉÍÅÎÉ ÆÁÊÌÁ ÐÏÓÌÅ \samp{//}, ÔÏÌØËÏ -ÐÏÄÄÉÒÅËÔÏÒÉÉ Ó ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÍÉ ËÏÍÐÏÎÅÎÔÁÍÉ ÂÕÄÕÔ ×ËÌÀÞÅÎÙ. -îÁÐÒÉÍÅÒ, \samp{/a//b} ÄÁ£Ô ÐÏÄÄÉÒÅËÔÏÒÉÉ \file{/a/1/b}, -\file{/a/2/b}, \file{/a/1/1/b}, É Ô.Ä., ÎÏ ÎÅ \file{/a/b/c} ÉÌÉ -\file{/a/1}. - -÷ÏÚÍÏÖÎÙ ÎÅÓËÏÌØËÏ ËÏÎÓÔÒÕËÃÉÊ \samp{//} × ÏÄÎÏÍ ÐÕÔÉ, ÎÏ -\samp{//} × ÎÁÞÁÌÅ ÐÕÔÉ ÉÇÎÏÒÉÒÕÀÔÓÑ. - -\subsubsection{óÐÉÓÏË ÓÐÅÃÉÁÌØÎÙÈ ÓÉÍ×ÏÌÏ× É ÉÈ ÚÎÁÞÅÎÉÊ} - -÷ ÓÌÅÄÕÀÝÅÍ ÓÐÉÓËÅ ÐÒÉ×ÏÄÑÔÓÑ ÓÐÅÃÉÁÌØÎÙÅ ÓÉÍ×ÏÌÙ × ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÈ -ÆÁÊÌÁÈ \KPS{}. - -\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} -\begin{ttdescription} -\item[\CODE{:}] òÁÚÄÅÌÉÔÅÌØ × ÓÐÅÃÉÆÉËÁÃÉÑÈ ÐÕÔÅÊ; × ÎÁÞÁÌÅ ÉÌÉ ËÏÎÃÅ - ÏÚÎÁÞÁÅÔ ÐÏÄÓÔÁÎÏ×ËÕ ÐÏ ÕÍÏÌÞÁÎÉÀ. -\item[\CODE{;}] òÁÚÄÅÌÉÔÅÌØ ÄÌÑ ÎÅ-àÎÉËÓÁ (ÔÏ ÖÅ, ÞÔÏ \code{:}). -\item[\CODE{\$}] ðÏÄÓÔÁÎÏ×ËÁ ÐÅÒÅÍÅÎÎÙÈ. -\item[\CODE{\string~}] ïÚÎÁÞÁÅÔ ÄÏÍÁÛÎÀÀ ÄÉÒÅËÔÏÒÉÀ ÐÏÌØÚÏ×ÁÔÅÌÑ. -\item[\CODE{\char`\{...\char`\}}] ðÏÄÓÔÁÎÏ×ËÁ ÓËÏÂÏË. -\item[\CODE{//}] ðÏÄÓÔÁÎÏ×ËÁ ÐÏÄÄÉÒÅËÔÏÒÉÊ (ÍÏÖÅÔ ×ÓÔÒÅÔÉÔØÓÑ ÇÄÅ - ÕÇÏÄÎÏ, ËÒÏÍÅ ÎÁÞÁÌÁ ÐÕÔÉ). -\item[\CODE{\%}] îÁÞÁÌÏ ËÏÍÍÅÎÔÁÒÉÑ. -\item[\CODE{\bs}] óÉÍ×ÏÌ ÐÒÏÄÏÌÖÅÎÉÑ (ÄÌÑ ËÏÍÁÎÄ ÉÚ ÎÅÓËÏÌØËÉÈ ÓÔÒÏË). -\item[\CODE{!!}] ðÏÉÓË \emph{ÔÏÌØËÏ} × ÂÁÚÅ ÄÁÎÎÙÈ, ÎÏ \emph{ÎÅ} ÎÁ - ÄÉÓËÅ. -\end{ttdescription} - - -\subsection{âÁÚÙ ÄÁÎÎÙÈ} -\label{sec:filename-database} - -\KPS{} ÓÔÁÒÁÅÔÓÑ ÍÉÎÉÍÉÚÉÒÏ×ÁÔØ ÏÂÒÁÝÅÎÉÅ Ë ÄÉÓËÕ ÐÒÉ ÐÏÉÓËÅ. ôÅÍ ÎÅ -ÍÅÎÅÅ × ÓÉÓÔÅÍÁÈ Ó ÂÏÌØÛÉÍ ËÏÌÉÞÅÓÔ×ÏÍ ÄÉÒÅËÔÏÒÉÊ ÐÏÉÓË × ËÁÖÄÏÊ -×ÏÚÍÏÖÎÏÊ ÄÉÒÅËÔÏÒÉÉ ÍÏÖÅÔ ÚÁÎÑÔØ ÄÏÌÇÏÅ ×ÒÅÍÑ (ÜÔÏ ÏÓÏÂÅÎÎÏ ×ÅÒÎÏ, -ÅÓÌÉ ÎÁÄÏ ÐÒÏ×ÅÒÉÔØ ÓÏÔÎÉ ÄÉÒÅËÔÏÒÉÊ ÓÏ ÛÒÉÆÔÁÍÉ). ðÏÜÔÏÍÕ \KPS{} -ÕÍÅÅÔ ÉÓÐÏÌØÚÏ×ÁÔØ ×ÎÅÛÎÉÊ ÔÅËÓÔÏ×ÙÊ ÆÁÊÌ, -<<ÂÁÚÕ ÄÁÎÎÙÈ>> \file{ls-R}, ËÏÔÏÒÙÊ ÚÎÁÅÔ, ÇÄÅ ÎÁÈÏÄÑÔÓÑ ÆÁÊÌÙ × -ÄÉÒÅËÔÏÒÉÑÈ, ÞÔÏ ÄÁ£Ô ×ÏÚÍÏÖÎÏÓÔØ ÉÚÂÅÖÁÔØ ÞÁÓÔÙÈ ÏÂÒÁÝÅÎÉÊ Ë ÄÉÓËÕ. - -åÝ£ ÏÄÎÁ ÂÁÚÁ ÄÁÎÎÙÈ, ÆÁÊÌ \file{aliases} ÐÏÚ×ÏÌÑÅÔ ×ÁÍ ÄÁ×ÁÔØ -ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ÎÁÚ×ÁÎÉÑ ÆÁÊÌÁÍ × \file{ls-R}. üÔÏ ÐÏÌÅÚÎÏ, ÅÓÌÉ ×ÁÍ -ÎÕÖÎÏ ÓÏÂÌÀÄÁÔØ ÐÒÁ×ÉÌÏ \acro{DOS} <<8.3>>. - -\subsubsection{âÁÚÙ ÄÁÎÎÙÈ \texttt{ls-R}} -\label{sec:ls-R} - -ëÁË ÏÂßÑÓÎÅÎÏ ×ÙÛÅ, ÏÓÎÏ×ÎÁÑ ÂÁÚÁ ÄÁÎÎÙÈ ÎÁÚÙ×ÁÅÔÓÑ \file{ls-R}. ÷Ù -ÍÏÖÅÔÅ ÓÏÚÄÁÔØ Å£ × ËÏÒÎÅ ËÁÖÄÏÇÏ ÄÅÒÅ×Á \TeX{}Á, ËÏÔÏÒÏÅ -ÐÒÏÓÍÁÔÒÉ×ÁÅÔÓÑ \KPS{} (ÐÏ ÕÍÏÌÞÁÎÉÀ, \code{\$TEXMF}); × ÂÏÌØÛÉÎÓÔ×Å -ÓÌÕÞÁÅ× ÉÅÒÁÒÈÉÑ ÔÏÌØËÏ ÏÄÎÁ. \KPS{} ÉÝÅÔ ÆÁÊÌÙ \file{ls-R} × ÐÕÔÉ -\code{TEXMFDBS}. - -òÅËÏÍÅÎÄÕÅÍÙÊ ÓÐÏÓÏ ÓÏÚÄÁÎÉÑ É ÐÏÄÄÅÒÖËÉ \samp{ls-R} "--- ÓËÒÉÐÔ -\code{mktexlsr}, ×ËÌÀÞ£ÎÎÙÊ × ÄÉÓÔÒÉÂÕÔÉ×. ïÎ ×ÙÚÙ×ÁÅÔÓÑ ÒÁÚÎÙÍÉ -ÓËÒÉÐÔÁÍÉ \samp{mktex}\dots. ÷ ÐÒÉÎÃÉÐÅ ÜÔÏÔ ÓËÒÉÐÔ ×ÙÐÏÌÎÑÅÔ ËÏÍÁÎÄÙ -ÔÉÐÁ -\begin{alltt} -cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R -\end{alltt} -ÐÒÉ ÕÓÌÏ×ÉÉ, ÞÔÏ × ×ÁÛÅÊ ÓÉÓÔÅÍÅ \code{ls} ÄÁ£Ô ×Ù×ÏÄ × ÎÕÖÎÏÍ ÆÏÒÍÁÔÅ -(\acro{GNU} \code{ls} ÇÏÄÉÔÓÑ). þÔÏÂÙ ÐÏÄÄÅÒÖÉ×ÁÔØ ÂÁÚÕ ÄÁÎÎÙÈ × -ÔÅËÕÝÅÍ ÓÏÓÔÏÑÎÉÉ, ÐÒÏÝÅ ×ÓÅÇÏ ÐÅÒÅÇÅÎÅÒÉÒÏ×ÁÔØ Å£ ÒÅÇÕÌÑÒÎÏ ÉÚ -\code{cron}Á, ÔÁË ÞÔÏ ÏÎÁ Á×ÔÏÍÁÔÉÞÅÓËÉ ÏÂÎÏ×ÌÑÅÔÓÑ ÐÏÓÌÅ ÕÓÔÁÎÏ×ËÉ -ÎÏ×ÏÇÏ ÐÁËÅÔÁ. - -åÓÌÉ ÆÁÊÌ ÎÅ ÎÁÊÄÅÎ × ÂÁÚÅ ÄÁÎÎÙÈ, ÐÏ ÕÍÏÌÞÁÎÉÀ \KPS{} ÉÝÅÔ ÅÇÏ ÎÁ ÄÉÓËÅ. -åÓÌÉ ÜÌÅÍÅÎÔ ÐÕÔÉ ÎÁÞÉÎÁÅÔÓÑ Ó \samp{!!}, ÔÏ ÐÏÉÓË ÐÒÏÉÓÈÏÄÉÔ -\emph{ÔÏÌØËÏ} × ÂÁÚÅ ÄÁÎÎÙÈ. - - -\subsubsection{kpsewhich: ÐÏÉÓË ÆÁÊÌÏ×} -\label{sec:invoking-kpsewhich} - -ðÒÏÇÒÁÍÍÁ \texttt{kpsewhich} ×ÙÐÏÌÎÑÅÔ ÐÏÉÓË × ÓÏÏÔ×ÅÔÓÔ×ÉÉ Ó -ÁÌÇÏÒÉÔÍÏÍ, ÏÐÉÓÁÎÎÙÍ ×ÙÛÅ. üÔÏ ÍÏÖÅÔ ÂÙÔØ ÐÏÌÅÚÎÏ × ËÁÞÅÓÔ×Å -×ÁÒÉÁÎÔÁ ËÏÍÁÎÄÙ \code{find} ÄÌÑ ÐÏÉÓËÁ ÆÁÊÌÏ× × ÉÅÒÁÒÈÉÑÈ \TeX{}Á -(ÜÔÏ ÛÉÒÏËÏ ÉÓÐÏÌØÚÕÅÔÓÑ × ÓËÒÉÐÔÁÈ \samp{mktex}\dots). - -\begin{alltt} -> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} -\end{alltt} -ïÐÃÉÉ, ÕËÁÚÁÎÎÙÅ × \ttvar{option}, ÎÁÞÉÎÁÀÔÓÑ ÌÉÂÏ Ó \samp{-} -ÌÉÂÏ \samp{-{}-}, É ÌÀÂÙÅ ÏÄÎÏÚÎÁÞÎÙÅ ÓÏËÒÁÝÅÎÉÑ ÄÏÐÕÓÔÉÍÙ. - -\KPS{} ÒÁÓÓÍÁÔÒÉ×ÁÅÔ ËÁÖÄÙÊ ÁÒÇÕÍÅÎÔ, ÎÅ Ñ×ÌÑÀÝÉÊÓÑ ÏÐÃÉÅÊ, ËÁË ÉÍÑ -ÆÁÊÌÁ, É ×ÏÚ×ÒÁÝÁÅÔ ÐÅÒ×ÙÊ ÎÁÊÄÅÎÎÙÊ ÆÁÊÌ. îÅÔ ÏÐÃÉÉ ×ÅÒÎÕÔØ ×ÓÅ -ÎÁÊÄÅÎÎÙÅ ÆÁÊÌÙ (ÄÌÑ ÜÔÏÇÏ ÍÏÖÎÏ ÉÓÐÏÌØÚÏ×ÁÔØ ÐÒÏÇÒÁÍÍÕ \samp{find}). - -îÁÉÂÏÌÅÅ ×ÁÖÎÙÅ ÏÐÃÉÉ ÏÐÉÓÁÎÙ ÎÉÖÅ. - -\begin{ttdescription} -\item[\texttt{-{}-dpi=\var{num}}]\mbox{}\\ - õÓÔÁÎÏ×ÉÔØ ÒÁÚÒÅÛÅÎÉÅ \ttvar{num}; ÜÔÏ ×ÌÉÑÅÔ ÔÏÌØËÏ ÎÁ ÐÏÉÓË ÆÁÊÌÏ× - \samp{gf} É \samp{pk}. óÉÎÏÎÉÍ \samp{-D}, ÄÌÑ - ÓÏ×ÍÅÓÔÉÍÏÓÔÉ Ó \cmdname{dvips}. ðÏ ÕÍÏÌÞÁÎÉÀ 600. - -\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ - õÓÔÁÎÏ×ÉÔØ ÆÏÒÍÁÔ ÄÌÑ ÐÏÉÓËÁ \ttvar{name}. ðÏ ÕÍÏÌÞÁÎÉÀ, ÆÏÒÍÁÔ - ÏÐÒÅÄÅÌÑÅÔÓÑ ÉÚ ÉÍÅÎÉ ÆÁÊÌÁ. äÌÑ ÆÏÒÍÁÔÏ×, ÄÌÑ ËÏÔÏÒÙÈ ÎÅÔ - ÏÄÎÏÚÎÁÞÎÏÇÏ ÓÕÆÆÉËÓÁ, ÎÁÐÒÉÍÅÒ, ÆÁÊÌÏ× \MP{} É ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÈ - ÆÁÊÌÏ× - \cmdname{dvips}, ×Ù ÄÏÌÖÎÙ ÕËÁÚÁÔØ ÎÁÚ×ÁÎÉÅ, ÉÚ×ÅÓÔÎÏÅ \KPS{}, - ÎÁÐÒÉÍÅÒ, \texttt{tex} ÉÌÉ \texttt{enc files}. óÐÉÓÏË ÍÏÖÎÏ - ÐÏÌÕÞÉÔØ ËÏÍÁÎÄÏÊ \texttt{kpsewhich -{}-help}. - -\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ - õÓÔÁÎÏ×ÉÔØ ÚÎÁÞÅÎÉÅ ÒÅÖÉÍÁ \ttvar{string}; ÜÔÏ ×ÉÌÑÅÔ ÔÏÌØËÏ ÎÁ - ÐÏÉÓË ÆÁÊÌÏ× \samp{gf} É \samp{pk}. úÎÁÞÅÎÉÑ ÐÏ ÕÍÏÌÞÁÎÉÀ ÎÅÔ: - ÉÝÕÔÓÑ ÆÁÊÌÙ ÄÌÑ ×ÓÅÈ ÒÅÖÉÍÏ×. - -\item[\texttt{-{}-must-exist}]\mbox{}\\ - óÄÅÌÁÔØ ×Ó£ ×ÏÚÍÏÖÎÏÅ, ÞÔÏÂÙ ÎÁÊÔÉ ÆÁÊÌ ×ËÌÀÞÁÑ ÐÏÉÓË ÎÁ ÄÉÓËÅ. ðÏ - ÕÍÏÌÞÁÎÉÀ ÄÌÑ ÐÏ×ÙÛÅÎÉÑ ÜÆÆÅËÔÉ×ÎÏÓÔÉ ÐÒÏÓÍÁÔÒÉ×ÁÅÔÓÑ ÔÏÌØËÏ ÂÁÚÁ - ÄÁÎÎÙÈ \file{ls-R}. - -\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ - éÓËÁÔØ × ÎÁÂÏÒÅ ÄÉÒÅËÔÏÒÉÊ \ttvar{string} (ËÁË ÏÂÙÞÎÏ, ÒÁÚÄÅÌ£ÎÎÙÈ - Ä×ÏÅÔÏÞÉÑÍÉ), ×ÍÅÓÔÏ ÔÏÇÏ, ÞÔÏÂÙ ×ÙÞÉÓÌÑÔØ ÐÕÔØ ÐÏÉÓËÁ ÐÏ ÉÍÅÎÉ - ÆÁÊÌÁ. \samp{//} É ÏÂÙÞÎÙÅ ÐÏÄÓÔÁÎÏ×ËÉ ÒÁÂÏÔÁÀÔ. ïÐÃÉÉ - \samp{-{}-path} É \samp{-{}-format} ÎÅÓÏ×ÍÅÓÔÉÍÙ. - -\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ - õÓÔÁÎÏ×ÉÔØ ÉÍÑ ÐÒÏÇÒÁÍÍÙ ÒÁ×ÎÙÍ \texttt{\var{name}}. üÔÏ ×ÌÉÑÅÔ ÎÁ - ÐÕÔØ ÐÏÉÓËÁ ÉÚ-ÚÁ ÐÒÅÆÉËÓÁ \texttt{.\var{progname}}. ðÏ ÕÍÏÌÞÁÎÉÀ - \cmdname{kpsewhich}. - -\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ - ðÏËÁÚÁÔØ ÐÕÔØ, ÉÓÐÏÌØÚÕÅÍÙÊ ÐÒÉ ÐÏÉÓËÁÈ ÆÁÊÌÏ× ÔÉÐÁ - \texttt{\var{name}}. íÏÖÎÏ ÉÓÐÏÌØÚÏ×ÁÔØ ÒÁÓÛÉÒÅÎÉÅ (\code{.pk}, - \code{.vf} É Ô.Ä.) ÉÌÉ ÎÁÚ×ÁÎÉÅ, ËÁË ÄÌÑ ÏÐÃÉÉ \samp{-{}-format}. - -\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ - õÓÔÁÎÏ×ÉÔØ ÕÒÏ×ÅÎØ ÏÔÌÁÄËÉ \texttt{\var{num}}. -\end{ttdescription} - - - -\subsubsection{ðÒÉÍÅÒÙ ÉÓÐÏÌØÚÏ×ÁÎÉÑ} -\label{sec:examples-of-use} - -äÁ×ÁÊÔÅ ÐÏÓÍÏÔÒÉÍ ÎÁ \KPS{} × ÄÅÊÓÔ×ÉÉ. ÷ÏÔ ÐÒÏÓÔÏÊ ÐÏÉÓË: - -\begin{alltt} -> \Ucom{kpsewhich article.cls} - /usr/local/texmf-dist/tex/latex/base/article.cls -\end{alltt} -íÙ ÉÝÅÍ ÆÁÊÌ \file{article.cls}. ôÁË ËÁË ÓÕÆÆÉËÓ \samp{.cls} -ÏÄÎÏÚÎÁÞÅÎ, ÎÁÍ ÎÅ ÎÕÖÎÏ ÕËÁÚÙ×ÁÔØ, ÞÔÏ ÍÙ ÉÝÅÍ ÆÁÊÌ ÔÉÐÁ -\optname{tex} (ÉÓÈÏÄÎÉËÉ \TeX{}Á). íÙ ÎÁÈÏÄÉÍ ÅÇÏ × ÐÏÄÄÉÒÅËÔÏÒÉÉ -\file{tex/latex/base} ÄÉÒÅËÔÏÒÉÉ \samp{temf-dist} \TL. áÎÁÌÏÇÉÞÎÏ, -×Ó£ ÐÏÓÌÅÄÕÀÝÅÅ ÎÁÈÏÄÉÔÓÑ ÂÅÚ ÐÒÏÂÌÅÍ ÂÌÁÇÏÄÁÒÑ ÏÄÎÏÚÎÁÞÎÏÍÕ ÓÕÆÆÉËÓÕ: -\begin{alltt} -> \Ucom{kpsewhich array.sty} - /usr/local/texmf-dist/tex/latex/tools/array.sty -> \Ucom{kpsewhich latin1.def} - /usr/local/texmf-dist/tex/latex/base/latin1.def -> \Ucom{kpsewhich size10.clo} - /usr/local/texmf-dist/tex/latex/base/size10.clo -> \Ucom{kpsewhich small2e.tex} - /usr/local/texmf-dist/tex/latex/base/small2e.tex -> \Ucom{kpsewhich tugboat.bib} - /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib -\end{alltt} - -ëÓÔÁÔÉ, ÐÏÓÌÅÄÎÅÅ "--- ÂÉÂÌÉÏÇÒÁÆÉÞÅÓËÁÑ ÂÁÚÁ ÄÁÎÎÙÈ ÄÌÑ ÓÔÁÔÅÊ ÖÕÒÎÁÌÁ -\textsl{TUGBoat}. - -\begin{alltt} -> \Ucom{kpsewhich cmr10.pk} -\end{alltt} -âÉÔÍÁÐÙ ÛÒÉÆÔÏ× ÔÉÐÁ \file{.pk} ÉÓÐÏÌØÚÕÀÔÓÑ ÐÒÏÇÒÁÍÍÁÍÉ -\cmdname{dvips} Ï \cmdname{xdvi}. îÉÞÅÇÏ ÎÅ ÎÁÊÄÅÎÏ, ÔÁË ËÁË Õ ÎÁÓ -ÎÅÔ ÇÏÔÏ×ÙÈ ÆÁÊÌÏ× ÛÒÉÆÔÏ× Computer Modern × ÆÏÒÍÁÔÅ \samp{.pk} (ÔÁË -ËÁË ÍÙ ÉÓÐÏÌØÚÕÅÍ ×ÅÒÓÉÉ × ÆÏÒÍÁÔÅ Type~1 ÉÚ ÄÉÓÔÒÉÂÕÔÉ×Á \TL{}). -\begin{alltt} -> \Ucom{kpsewhich wsiupa10.pk} -\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk -\else /usr/local/texmf-var/fonts/pk/ljfour/public/ -... wsuipa/wsuipa10.600pk -\fi\end{alltt} -äÌÑ ÜÔÉÈ ÛÒÉÆÔÏ× (ÆÏÎÅÔÉÞÅÓËÉÊ ÁÌÆÁ×ÉÔ, ÓÏÚÄÁÎÎÙÊ × ÕÎÉ×ÅÒÓÉÔÅÔÅ -ÛÔÁÔÁ ÷ÁÛÉÎÇÔÏÎ) ÍÙ ÄÏÌÖÎÙ ÓÇÅÎÅÒÉÒÏ×ÁÔØ -\samp{.pk}, É ÔÁË ËÁË ÒÅÖÉÍ \MF{} [Ï ÕÍÏÌÞÁÎÉÀ × ÎÁÛÅÊ ÓÉÓÔÅÍÅ -\texttt{ljfour} Ó ÒÁÚÒÅÛÅÎÉÅÍ of 600\dpi{} (ÔÏÞÅË ÎÁ ÄÀÊÍ), ÜÔÏÔ ÛÒÉÆÔ -É ÎÁÊÄÅÎ. -\begin{alltt} -> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} -\end{alltt} -÷ ÜÔÏÍ ÓÌÕÞÁÅ ÎÁÍ ÎÕÖÎÏ ÒÁÚÒÅÛÅÎÉÅ 300\dpi{} (\texttt{-dpi=300}); ÍÙ -×ÉÄÉÍ, ÞÔÏ ÔÁËÏÇÏ ÛÒÉÆÔÁ × ÓÉÓÔÅÍÅ ÎÅÔ. îÁ ÓÁÍÏÍ ÄÅÌÅ ÐÒÏÇÒÁÍÍÁ -\cmdname{dvips} ÉÌÉ \cmdname{xdvi} ÐÏÓÔÒÏÉÌÁ ÂÙ ÎÕÖÎÙÊ ÆÁÊÌ -\texttt{.pk} ÐÒÉ ÐÏÍÏÝÉ ÓËÒÉÐÔÁ \cmdname{mktexpk}. - -ôÅÐÅÒØ ÏÂÒÁÔÉÍÓÑ Ë ÚÁÇÏÌÏ×ËÁÍ É ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÍ ÆÁÊÌÁÍ -\cmdname{dvips}. ÷ÎÁÞÁÌÅ ÒÁÓÓÍÏÔÒÉÍ ÏÄÉÎ ÉÚ ÎÁÉÂÏÌÅÅ ÞÁÓÔÏ -ÉÓÐÏÌØÚÕÅÍÙÈ ÆÁÊÌÏ×, ÐÒÏÌÏÇ \file{tex.pro} ÄÌÑ ÐÏÄÄÅÒÖËÉ \TeX{}Á, Á -ÚÁÔÅÍ ÒÁÓÓÍÏÔÒÉÍ ÏÂÝÉÊ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ \file{config.ps} É ËÁÒÔÕ -ÛÒÉÆÔÏ× \file{psfonts.map} (Ó 2004 ÇÏÄÁ ËÁÒÔÙ É ÆÁÊÌÙ ËÏÄÉÒÏ×ÏË ÉÍÅÀÔ -ÓÏÂÓÔ×ÅÎÎÙÅ ÐÕÔÉ ÐÏÉÓËÁ × ÄÅÒÅ×ØÑÈ \dirname{texmf}). ôÁË ËÁË ÓÕÆÆÉËÓ -\samp{.ps} ÎÅÏÄÎÏÚÎÁÞÅÎ, ÍÙ ÄÏÌÖÎÙÅ Ñ×ÎÏ ÕËÁÚÁÔØ ÔÉÐ ÆÁÊÌÁ, ËÏÔÏÒÙÊ ÍÙ -ÉÝÅÍ: (\optname{dvips config}) ÄÌÑ ÆÁÊÌÁ \texttt{config.ps}. -\begin{alltt} -> \Ucom{kpsewhich tex.pro} - /usr/local/texmf/dvips/base/tex.pro -> \Ucom{kpsewhich --format="dvips config" config.ps} - /usr/local/texmf/dvips/config/config.ps -> \Ucom{kpsewhich psfonts.map} - /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map -\end{alltt} - -òÁÓÓÍÏÔÒÉÍ ÔÅÐÅÒØ ÆÁÊÌÙ ÐÏÄÄÅÒÖËÉ \acro{URW} Times (\PS{}). ðÒÅÆÉËÓ -ÄÌÑ ÜÔÉÈ ÆÁÊÌÏ× × ÓÔÁÎÄÁÒÔÎÏÊ ÓÈÅÍÅ ÏÂÏÚÎÁÞÅÎÉÑ ÛÒÉÆÔÏ× \samp{utm}. -÷ÎÁÞÁÌÅ ÍÙ ÒÁÓÓÍÏÔÒÉÍ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ, ËÏÔÏÒÙÊ ÓÏÄÅÒÖÉÔ ÎÁÚ×ÁÎÉÅ -ËÁÒÔÙ ÛÒÉÆÔÏ×: -\begin{alltt} -> \Ucom{kpsewhich --format="dvips config" config.utm} -/usr/local/texmf-dist/dvips/psnfss/config.utm -\end{alltt} -óÏÄÅÒÖÁÎÉÅ ÜÔÏÇÏ ÆÁÊÌÁ: -\begin{alltt} - p +utm.map -\end{alltt} -ÞÔÏ ÕËÁÚÙ×ÁÅÔ ÎÁ ÆÁÊÌ \file{utm.map}, ËÏÔÏÒÙÊ ÍÙ ÈÏÔÉÍ ÔÅÐÅÒØ ÎÁÊÔÉ. -\begin{alltt} -> \Ucom{kpsewhich --format="dvips config" utm.map} - /usr/local/texmf-dist/fonts/map/dvips/times/utm.map -\end{alltt} -üÔÁ ËÁÒÔÁ ÏÐÒÅÄÅÌÑÅÔ ÎÁÚ×ÁÎÉÑ ÛÒÉÆÔÏ× ÆÏÒÍÁÔÁ Type~1 (\PS{}) × -ËÏÌÌÅËÃÉÉ URW. ïÎÁ ×ÙÇÌÑÄÉÔ ÔÁË (ÍÙ ÐÏËÁÚÙ×ÁÅÍ ÔÏÌØËÏ ÞÁÓÔØ ÆÁÊÌÁ): -\begin{alltt} -utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} -\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb -\else /usr/local/texmf-dist/fonts/type1/ -... urw/utm/utmr8a.pfb -\fi\end{alltt} - -éÚ ÜÔÉÈ ÐÒÉÍÅÒÏ× ×ÉÄÎÏ, ÞÔÏ ×Ù ÍÏÖÅÔÅ ÌÅÇËÏ ÎÁÊÔÉ ÚÁÄÁÎÎÙÊ ÆÁÊÌ. -üÔÏ ÏÓÏÂÅÎÎÏ ×ÁÖÎÏ, ÅÓÌÉ ×Ù ÐÏÄÏÚÒÅ×ÁÅÔÅ, ÞÔÏ ÐÒÏÇÒÁÍÍÙ ÎÁÈÏÄÑÔ -ÎÅÐÒÁ×ÉÌØÎÕÀ ×ÅÒÓÉÀ ÆÁÊÌÁ, ÐÏÓËÏÌØËÕ \cmdname{kpsewhich} ÐÏËÁÚÙ×ÁÅÔ -ÐÅÒ×ÙÊ ÎÁÊÄÅÎÎÙÊ ÆÁÊÌ. - -\subsubsection{ïÔÌÁÄËÁ} -\label{sec:debugging} - -éÎÏÇÄÁ ÎÅÏÂÈÏÄÉÍÏ ÐÒÏ×ÅÒÉÔØ, ËÁË ÐÒÏÇÒÁÍÍÁ ÉÝÅÔ ÆÁÊÌÙ. ó ÜÔÏÊ ÃÅÌØÀ -\KPS{} ÐÒÅÄÌÁÇÁÅÔ ÒÁÚÎÙÅ ÕÒÏ×ÎÉ ÏÔÌÁÄËÉ: - -\begin{ttdescription} -\item[\texttt{\ 1}] ÓÔÁÔÉÓÔÉËÁ ÏÂÒÁÝÅÎÉÊ Ë ÄÉÓËÕ. ðÒÉ ÒÁÂÏÔÅ Ó ÂÁÚÁÍÉ - \file{ls-R} ÜÔÏ ÐÏÞÔÉ ÎÅ ÄÏÌÖÎÏ ÄÁ×ÁÔØ ÚÁÐÉÓÅÊ × ÌÏÇ. -\item[\texttt{\ 2}] óÓÙÌËÉ ÎÁ ÈÅÛÉ (ÎÁÐÒÉÍÅÒ, ÂÁÚÙ ÄÁÎÎÙÈ \file{ls-R}, - ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÆÁÊÌÙ É Ô.Ä.). -\item[\texttt{\ 4}] ïÐÅÒÁÃÉÉ ÏÔËÒÙÔÉÑ É ÚÁËÒÙÔÉÑ ÆÁÊÌÏ×. -\item[\texttt{\ 8}] ïÂÝÁÑ ÉÎÆÏÒÍÁÃÉÑ Ï ÔÉÐÁÈ ÆÁÊÌÏ×, ËÏÔÏÒÙÅ ÉÝÅÔ - \KPS. üÔÏ ÐÏÌÅÚÎÏ ÄÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÎÁÊÔÉ, ÇÄÅ ÏÐÒÅÄÅÌÑÅÔÓÑ ÔÉÐ ÐÕÔÉ - ÐÏÉÓËÁ ÄÌÑ ÄÁÎÎÏÇÏ ÆÁÊÌÁ. -\item[\texttt{16}] óÐÉÓÏË ÄÉÒÅËÔÏÒÉÊ ÄÌÑ ËÁÖÄÏÇÏ ÜÌÅÍÅÎÔÁ ÐÕÔÉ (ÐÒÉ - ÐÏÉÓËÁÈ ÎÁ ÄÉÓËÅ). -\item[\texttt{32}] ðÏÉÓËÉ ÆÁÊÌÏ×. -\item[\texttt{64}] úÎÁÞÅÎÉÑ ÐÅÒÅÍÅÎÎÙÈ. -\end{ttdescription} -úÎÁÞÅÎÉÅ \texttt{-1} ÚÁÄÁÓÔ ×ÓÅ ÏÐÃÉÉ ×ÙÛÅ; ÉÍÅÎÎÏ ÜÔÏ ÚÎÁÞÅÎÉÅ ÞÁÝÅ -×ÓÅÇÏ ÉÓÐÏÌØÚÕÅÔÓÑ ÎÁ ÐÒÁËÔÉËÅ. - -áÎÁÌÏÇÉÞÎÏ, ÚÁÐÕÓÔÉ× ÐÒÏÇÒÁÍÍÕ \cmdname{dvips} É ÉÓÐÏÌØÚÕÑ ÓÏÞÅÔÁÎÉÅ -ÜÔÉÈ ÏÐÃÉÊ, ÍÏÖÎÏ ÐÒÏÓÌÅÄÉÔØ ÐÏÄÒÏÂÎÏ, ËÁË ÉÝÕÔÓÑ ÆÁÊÌÙ. ó ÄÒÕÇÏÊ -ÓÔÏÒÏÎÙ, ÅÓÌÉ ÆÁÊÌ ÎÅ ÎÁÊÄÅÎ, ÔÒÁÓÓÉÒÏ×ËÁ ÐÏËÁÚÙ×ÁÅÔ, ÇÄÅ ÅÇÏ ÉÓËÁÌÉ, -ÔÁË ÞÔÏ ÍÏÖÎÏ ÐÏÎÑÔØ, × Þ£Í ÓÏÓÔÏÉÔ ÐÒÏÂÌÅÍÁ. - -÷ÏÏÂÝÅ ÇÏ×ÏÒÑ, ÐÏÓËÏÌØËÕ ÂÏÌØÛÉÎÓÔ×Ï ÐÒÏÇÒÁÍÍ ÐÏÌØÚÕÀÔÓÑ ÂÉÂÌÉÏÔÅËÏÊ -\KPS{}, ×Ù ÍÏÖÅÔÅ ÕÓÔÁÎÏ×ÉÔØ ÏÐÃÉÀ ÏÔÌÁÄËÉ ÉÓÐÏÌØÚÕÑ ÐÅÒÅÍÅÎÎÕÀ -ÏËÒÕÖÅÎÉÑ \envname{KPATHSEA\_DEBUG}, É ÕÓÔÁÎÏ×É× Å£ ÎÁ ËÏÍÂÉÎÁÃÉÀ -ÏÐÉÓÁÎÎÙÈ ×ÙÛÅ ÚÎÁÞÅÎÉÊ. - -(ðÒÉÍÅÞÁÎÉÅ ÄÌÑ ÐÏÌØÚÏ×ÁÔÅÌÅÊ Windows: × ÜÔÏÊ ÓÉÓÔÅÍÅ ÔÒÕÄÎÏ -ÐÅÒÅÎÁÐÒÁ×ÉÔØ ×ÓÅ ÓÏÏÂÝÅÎÉÑ × ÆÁÊÌ. äÌÑ ÄÉÁÇÎÏÓÔÉËÉ ×Ù ÍÏÖÅÔÅ ×ÒÅÍÅÎÎÏ -ÕÓÔÁÎÏ×ÉÔØ \texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log}). - - -òÁÓÓÍÏÔÒÉÍ × ËÁÞÅÓÔ×Å ÐÒÉÍÅÒÁ ÐÒÏÓÔÏÊ ÆÁÊÌ × ÆÏÒÍÁÔÅ \LaTeX{}, -\file{hello-world.tex}, ÓÏ ÓÌÅÄÕÀÝÉÍ ÓÏÄÅÒÖÁÎÉÅÍ: -\begin{verbatim} - \documentclass{article} - \begin{document} - Hello World! - \end{document} -\end{verbatim} -üÔÏÔ ÍÁÌÅÎØËÉÊ ÆÁÊÌ ÉÓÐÏÌØÚÕÅÔ ÔÏÌØËÏ ÛÒÉÆÔ \file{cmr10}, ÔÁË ÞÔÏ -ÄÁ×ÁÊÔÅ ÐÏÓÍÏÔÒÉÍ, ËÁË \cmdname{dvips} ÓÏÚÄÁ£Ô ÆÁÊÌ × ÆÏÒÍÁÔÅ \PS{} -(ÍÙ ÈÏÔÉÍ ÉÓÐÏÌØÚÏ×ÁÔØ ×ÅÒÓÉÀ ÛÒÉÆÔÏ× × ÆÏÒÍÁÔÅ Type~1, ÏÔÓÀÄÁ ÏÐÃÉÑ -\texttt{-Pcms}). -\begin{alltt} -> \Ucom{dvips -d4100 hello-world -Pcms -o} -\end{alltt} -÷ ÜÔÏÍ ÓÌÕÞÁÅ ÍÙ ÏÂßÅÄÉÎÉÌÉ ÏÔÌÁÄÏÞÎÙÊ ÕÒÏ×ÅÎØ 4 ÄÌÑ \cmdname{dvips} -(ÄÉÒÅËÔÏÒÉÉ ÛÒÉÆÔÏ×) Ó ÐÏÄÓÔÁÎÏ×ËÏÊ ÜÌÅÍÅÎÔÏ× ÐÕÔÅÊ × \KPS (ÓÍ. -òÕËÏ×ÏÄÓÔ×Ï ÐÏÌØÚÏ×ÁÔÅÌÑ \cmdname{dvips}, -\OnCD{texmf/doc/html/dvips/dvips_toc.html}). òÅÚÕÌØÔÁÔ (ÓÌÅÇËÁ -ÏÔÒÅÄÁËÔÉÒÏ×ÁÎÎÙÊ) ÐÏËÁÚÁÎ ÎÁ ÒÉÓÕÎËÅ~\ref{fig:dvipsdbga}. -\begin{figure*}[tp] -\centering -\input{examples/ex6a.tex} -\caption{ðÏÉÓË ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÈ ÆÁÊÌÏ×}\label{fig:dvipsdbga} - -\bigskip - -\input{examples/ex6b.tex} -\caption{ðÏÉÓË ÆÁÊÌÁ ÐÒÏÌÏÇÁ}\label{fig:dvipsdbgb} - -\bigskip - -\input{examples/ex6c.tex} -\caption{ðÏÉÓË ÆÁÊÌÁ ÛÒÉÆÔÁ}\label{fig:dvipsdbgc} -\end{figure*} - -ðÒÏÇÒÁÍÍÁ \cmdname{dvips} ×ÎÁÞÁÌÅ ÉÝÅÔ Ó×ÏÉ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÆÁÊÌÙ. -óÎÁÞÁÌÁ ÎÁÈÏÄÉÔÓÑ \file{texmf.cnf}, ËÏÔÏÒÙÊ ÓÏÄÅÒÖÉÔ ÏÐÒÅÄÅÌÅÎÉÑ ÄÌÑ -ÐÕÔÅÊ ÐÏÉÓËÁ ÏÓÔÁÌØÎÙÈ ÆÁÊÌÏ×, ÚÁÔÅÍ ÂÁÚÁ ÄÁÎÎÙÈ \file{ls-R} (ÄÌÑ -ÏÐÔÉÍÉÚÁÃÉÉ ÐÏÉÓËÁ ÆÁÊÌÏ×) É ÆÁÊÌ \file{aliases}, ËÏÔÏÒÙÊ ÐÏÚ×ÏÌÑÅÔ -ÏÂßÑ×ÉÔØ ÎÅÓËÏÌØËÏ ÉͣΠ(ÎÁÐÒÉÍÅÒ, ËÏÒÏÔËÉÅ 8.3 É ÂÏÌÅÅ ÄÌÉÎÎÙÅ) ÄÌÑ -ÏÄÎÏÇÏ ÆÁÊÌÁ. úÁÔÅÍ \cmdname{dvips} ÉÝÅÔ Ó×ÏÊ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ -\file{config.ps} É ÆÁÊÌ -\file{.dvipsrc} (ËÏÔÏÒÙÊ × ÄÁÎÎÏÍ ÓÌÕÞÁÅ \emph{ÎÅ ÎÁÊÄÅÎ}). îÁËÏÎÅÃ, -\cmdname{dvips} ÎÁÈÏÄÉÔ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ ÄÌÑ ÛÒÉÆÔÏ× Computer -Modern \PS{} \file{config.cms} (ÜÔÏ ÂÙÌÏ ÚÁÄÁÎÏ ÏÐÃÉÅÊ \texttt{-Pcms} -× ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÅ). üÔÏÔ ÆÁÊÌ ÓÏÄÅÒÖÉÔ ÓÐÉÓÏË ËÁÒÔ, ËÏÔÏÒÙÅ -ÏÐÒÅÄÅÌÑÀÔ ÓÏÏÔÎÏÛÅÎÉÑ ÍÅÖÄÕ ÆÁÊÌÁÍÉ × ÆÏÒÍÁÔÁÈ \TeX{}, \PS{} -É ÎÁÚ×ÁÎÉÑÍÉ ÛÒÉÆÔÏ×: -\begin{alltt} -> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} - p +ams.map - p +cms.map - p +cmbkm.map - p +amsbkm.map -\end{alltt} -\cmdname{dvips} ÎÁÈÏÄÉÔ ×ÓÅ ÜÔÉ ÆÁÊÌÙ ÐÌÀÓ ÏÂÝÕÀ ËÁÒÔÕ ÛÒÉÆÔÏ× -\file{psfonts.map}, ËÏÔÏÒÁÑ ×ÓÅÇÄÁ ÚÁÇÒÕÖÁÅÔÓÑ (ÏÎÁ ÓÏÄÅÒÖÉÔ ÏÂÙÞÎÙÅ -ÛÒÉÆÔÙ × ÆÏÒÍÁÔÅ \PS{}; ÓÍ. ÐÏÓÌÅÄÎÀÀ ÞÁÓÔØ -ÒÁÚÄÅÌÁ~\ref{sec:examples-of-use}). - -÷ ÜÔÏÔ ÍÏÍÅÎÔ \cmdname{dvips} ÓÏÏÂÝÁÅÔ Ï ÓÅÂÅ ÐÏÌØÚÏ×ÁÔÅÌÀ: -\begin{alltt} -This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) -\end{alltt} -\ifSingleColumn -úÁÔÅÍ ÏÎÁ ÉÝÅÔ ÐÒÏÌÏÇ \file{texc.pro}: -\begin{alltt}\small -kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro -\end{alltt} -\else -úÁÔÅÍ ÏÎÁ ÉÝÅÔ ÐÒÏÌÏÇ \file{texc.pro} (ÓÍ. -ÒÉÓÕÎÏË~\ref{fig:dvipsdbgb}). -\fi - -îÁÊÄÑ ÜÔÏÔ ÆÁÊÌ, \cmdname{dvips} ÐÅÞÁÔÁÅÔ ÄÁÔÕ É ×ÒÅÍÑ, É ÉÎÆÏÒÍÉÒÕÅÔ -ÎÁÓ, ÞÔÏ ÓÏÂÉÒÁÅÔÓÑ ÇÅÎÅÒÉÒÏ×ÁÔØ ÆÁÊÌ \file{hello-world.ps}, ÞÔÏ ÅÊ -ÎÕÖÅÎ ÆÁÊÌ \file{cmr10}, É ÞÔÏ ÐÏÓÌÅÄÎÉÊ Ñ×ÌÑÅÔÓÑ <<ÒÅÚÉÄÅÎÔÎÙÍ>> -(ÂÉÔÍÁÐÙ ÎÅ ÎÕÖÎÙ): -\begin{alltt}\small -TeX output 1998.02.26:1204' -> hello-world.ps -Defining font () cmr10 at 10.0pt -Font cmr10 is resident. -\end{alltt} -ôÅÐÅÒØ ÏÎÁ ÉÝÅÔ ÆÁÊÌ \file{cmr10.tfm}, ËÏÔÏÒÙÊ ÏÎÁ ÎÁÈÏÄÉÔ, ÚÁÔÅÍ ÅÝ£ -ÎÅÓËÏÌØËÏ ÐÒÏÌÏÇÏ× (ÚÄÅÓØ ÏÎÉ ÏÐÕÝÅÎÙ), É ÎÁËÏÎÅà ÆÁÊÌ ÆÏÒÍÁÔÁ Type~1 -\file{cmr10.pfb} ÎÁÊÄÅÎ É ×ËÌÀÞ£Î × ×ÙÈÏÄÎÏÊ ÆÁÊÌ (ÓÍ, ÐÏÓÌÅÄÎÀÀ -ÓÔÒÏËÕ): -\begin{alltt}\small -kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, - path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: - /var/tex/fonts/tfm//). -kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm -kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, - ... - -kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb -[1] -\end{alltt} - -\subsection{ïÐÃÉÉ ÚÁÐÕÓËÁ} - -åÝ£ ÏÄÎÁ ÐÏÌÅÚÎÁÑ ×ÏÚÍÏÖÎÏÓÔØ \Webc{} "--- ËÏÎÔÒÏÌØ ÐÁÒÁÍÅÔÒÏ× ÐÁÍÑÔÉ -(× ÏÓÏÂÅÎÎÏÓÔÉ ÒÁÚÍÅÒ ÍÁÓÓÉ×Ï×) ÐÒÉ ÚÁÐÕÓËÅ, ×Ï ×ÒÅÍÑ ÞÔÅÎÉÑ ÆÁÊÌÁ -\file{texmf.cnf} ÂÉÂÌÉÏÔÅËÏÊ \KPS{}. ðÁÒÁÍÅÔÒÙ ÐÁÍÑÔÉ ÎÁÈÏÄÑÔÓÑ × -ÞÁÓÔÉ~3 ÜÔÏÇÏ ÆÁÊÌÁ × ÄÉÓÔÒÉÂÕÔÉ×Å \TL{}. ÷ÏÔ ÓÁÍÙÅ ×ÁÖÎÙÅ: - -\begin{ttdescription} -\item[\texttt{main\_memory}] ïÂÝÅÅ ËÏÌÉÞÅÓÔ×Ï ÓÌÏ× × ÐÁÍÑÔÉ ÄÌÑ - ÐÒÏÇÒÁÍÍ \TeX{}, \MF{} É \MP. ðÏÓÌÅ ÉÚÍÅÎÅÎÉÑ ÜÔÏÇÏ ÐÁÒÁÍÅÔÒÁ ÎÁÄÏ - ÐÅÒÅÇÅÎÅÒÉÒÏ×ÁÔØ ÆÏÒÍÁÔ. îÁÐÒÉÍÅÒ, ×Ù ÍÏÖÅÔÅ ÓÏÚÄÁÔØ <<ÏÇÒÏÍÎÕÀ>> - ×ÅÒÓÉÀ \TeX{}Á, É ÎÁÚ×ÁÔØ ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÊ ÆÏÒÍÁÔ - \texttt{hugetex.fmt}. ðÏ ÏÂÝÉÍ ÐÒÁ×ÉÌÁÍ \KPS{}, ÚÎÁÞÅÎÉÅ ÐÅÒÅÍÅÎÎÏÊ - \texttt{main\_memory} ÂÕÄÅÔ ÞÉÔÁÔØÓÑ ÉÚ ÆÁÊÌÁ \file{texmf.cnf}. -\item[\texttt{extra\_mem\_bot}] äÏÐÏÌÎÉÔÅÌØÎÁÑ ÐÁÍÑÔØ ÄÌÑ <<ÂÏÌØÛÉÈ>> - ÓÔÒÕËÔÕÒ, ËÏÔÏÒÙÅ ÓÏÚÄÁ£Ô \TeX{}: ÂÏËÓÏ×, ËÌÅÑ É Ô.Ä. ïÓÏÂÅÎÎÏ - ÐÏÌÅÚÎÏ ÐÒÉ ÉÓÐÏÌØÚÏ×ÁÎÉÉ \PiCTeX{}Á. -\item[\texttt{font\_mem\_size}] ëÏÌÉÞÅÓÔ×Ï ÓÌÏ× ÉÎÆÏÒÍÁÃÉÉ Ï ÛÒÉÆÔÁÈ - ÄÌÑ \TeX{}Á. üÔÏ ÐÒÉÍÅÒÎÏ ÓÕÍÍÁÒÎÙÊ ÒÁÚÍÅÒ ×ÓÅÈ ÆÁÊÌÏ× TFM, ËÏÔÏÒÙÅ - ÞÉÔÁÅÔ \TeX. -\item[\texttt{hash\_extra}] - äÏÐÏÌÎÉÔÅÌØÎÙÊ ÒÁÚÍÅÒ ÈÅÛÁ ÄÌÑ ÉͣΠËÏÍÁÎÄ. ðÒÉÍÅÒÎÏ 10\,000 ËÏÍÁÎÄ - ÍÏÖÅÔ ÂÙÔØ ÐÏÍÅÝÅÎÏ × ÏÓÎÏ×ÎÏÊ ÈÅÛ. åÓÌÉ ×Ù ÄÅÌÁÅÔÅ ÂÏÌØÛÕÀ ËÎÉÇÕ ÓÏ - ÍÎÏÇÉÍÉ ÐÅÒÅËÒ£ÓÔÎÙÍÉ ÓÓÙÌËÁÍÉ, ÜÔÏÇÏ ÍÏÖÅÔ ÎÅ È×ÁÔÉÔØ. ðÏ ÕÍÏÌÞÁÎÉÀ - \texttt{hash\_extra} ÒÁ×ÅÎ \texttt{50000}. -\end{ttdescription} - -òÁÚÕÍÅÅÔÓÑ, ÜÔÏ ÎÅ ÚÁÍÅÎÁ ÎÁÓÔÏÑÝÉÈ ÄÉÎÁÍÉÞÅÓËÉÈ ÍÁÓÓÉ×Ï× É -ÒÁÓÐÒÅÄÅÌÅÎÉÑ ÐÁÍÑÔÉ, ÎÏ ÐÏÓËÏÌØËÕ ÜÔÉ ÞÅÒÔÙ ÉÓËÌÀÞÉÔÅÌØÎÏ ÓÌÏÖÎÏ -ÏÓÕÝÅÓÔ×ÉÔØ × ÔÅËÕÝÅÍ \TeX{}Å, ÉÓÐÏÌØÚÏ×ÁÎÉÅ ÜÔÉÈ ÐÁÒÁÍÅÔÒÏ× -ÐÒÅÄÓÔÁ×ÌÑÅÔ ÓÏÂÏÊ ÐÏÌÅÚÎÙÊ ËÏÍÐÒÏÍÉÓÓ É ÏÂÅÓÐÅÞÉ×ÁÅÔ ÎÅËÏÔÏÒÕÀ -ÇÉÂËÏÓÔØ. - - -\begin{comment} -\section{ëÏÍÐÉÌÉÒÏ×ÁÎÉÅ ÄÌÑ ÎÏ×ÏÊ ÐÌÁÔÆÏÒÍÙ ÔÉÐÁ Unix} - - -åÓÌÉ Õ ×ÁÓ ÐÌÁÔÆÏÒÍÁ, ÄÌÑ ËÏÔÏÒÏÊ ÍÙ ÎÅ ÓËÏÍÐÉÌÉÒÏ×ÁÌÉ ÐÒÏÇÒÁÍÍ, ×ÁÍ -ÐÒÉÄ£ÔÓÑ ÜÔÏ ÓÄÅÌÁÔØ ÓÁÍÉÍ. üÔÏ ÎÅ ÔÁË ÕÖ ÓÌÏÖÎÏ. ÷Ó£, ÞÔÏ ×ÁÍ ÍÏÖÅÔ -ÐÏÎÁÄÏÂÉÔØÓÑ, ÅÓÔØ × ÄÉÓÔÒÉÂÕÔÉ×Å × ÄÉÒÅËÔÏÒÉÉ \texttt{source}. - -\subsection{îÅÏÂÈÏÄÉÍÙÅ ÉÎÓÔÒÕÍÅÎÔÙ} - -÷ÁÍ ÎÕÖÎÏ ÐÏ ËÒÁÊÎÅÊ ÍÅÒÅ 100\,Mb ÎÁ ÄÉÓËÅ ÄÌÑ ËÏÍÐÉÌÉÒÏ×ÁÎÉÑ \TeX{}Á É -ÄÒÕÇÉÈ ÐÒÏÇÒÁÍÍ. ÷ÁÍ ÐÏÔÒÅÂÕÅÔÓÑ ËÏÍÐÉÌÑÔÏÒ \acro{ANSI} C, ÐÒÏÇÒÁÍÍÁ -\cmdname{make}, ÌÅËÓÉÞÅÓËÉÊ ÓËÁÎÅÒ É ÇÅÎÅÒÁÔÏÒ ÐÁÒÓÅÒÏ×. íÙ -ÒÅËÏÍÅÎÄÕÅÍ ×ÅÒÓÉÉ ÜÔÉÈ ÐÒÏÇÒÁÍÍ ÏÔ \acro{GNU} -(\cmdname{gcc}, \acro{GNU} \cmdname{make}, \cmdname{m4}, \cmdname{flex}, -\cmdname{bison}). ÷Ù ÍÏÖÅÔÅ ÒÁÂÏÔÁÔØ É Ó ÄÒÕÇÉÍÉ ËÏÍÐÉÌÑÔÏÒÁÍÉ É -×ÅÒÓÉÑÍÉ \cmdname{make}, ÎÏ ×ÁÍ ÐÏÔÒÅÂÕÅÔÓÑ ÇÌÕÂÏËÏÅ ÐÏÎÉÍÁÎÉÅ àÎÉËÓÁ, -ÞÔÏÂÙ ÒÁÚÏÂÒÁÔØÓÑ × ×ÏÚÍÏÖÎÙÈ ÐÒÏÂÌÅÍÁÈ. - -ëÒÏÍÅ ÔÏÇÏ, ËÏÍÁÎÄÁ \texttt{uname} ÄÏÌÖÎÁ ÄÁ×ÁÔØ ÒÁÚÕÍÎÙÊ ÒÅÚÕÌØÔÁÔ. - - -\subsection{ëÏÎÆÉÇÕÒÁÃÉÑ} - -óÎÁÞÁÌÁ ÐÒÏÉÚ×ÅÄÉÔÅ ÎÏÒÍÁÌØÎÕÀ ÕÓÔÁÎÏ×ËÕ \TL{} ÎÁ ×ÁÛ ÄÉÓË (ÓÍ. -ÒÁÚÄÅÌ~\ref{sec:unix-install-disk} -\p.~\pageref{sec:unix-install-disk}). ÷Ù ÍÏÖÅÔÅ ÐÒÏÐÕÓÔÉÔØ ÕÓÔÁÎÏ×ËÕ -ÓËÏÍÐÉÌÉÒÏ×ÁÎÎÙÈ ÐÒÏÇÒÁÍÍ. - -úÁÔÅÍ ÒÁÓÐÁËÕÊÔÅ ÉÓÈÏÄÎÉËÉ ÉÚ ÆÁÊÌÁ × ÄÉÒÅËÔÏÒÉÉ \dirname{source} ÎÁ -×ÁÛ ÄÉÓË É ÓÍÅÎÉÔÅ ÄÉÒÅËÔÏÒÉÀ ÔÕÄÁ, ÇÄÅ ×Ù ÒÁÓËÒÙÌÉ ÜÔÏÔ ÆÁÊÌ. - -úÁÔÅÍ ÚÁÐÕÓÔÉÔÅ \cmdname{configure}, ÎÁÐÒÉÍÅÒ, ÔÁË: -\begin{alltt} -> \Ucom{sh configure -prefix=/usr/local/TeX} -\end{alltt} - -äÉÒÅËÔÏÒÉÑ \optname{-prefix} "--- ÜÔÏ ÍÅÓÔÏ, ËÕÄÁ ×Ù ÕÓÔÁÎÏ×ÉÌÉ -ÏÓÎÏ×ÎÏÅ ÄÅÒÅ×Ï ÐÏÄÄÅÒÖËÉ. óÔÒÕËÔÕÒÁ ÄÉÒÅËÔÏÒÉÊ ÂÕÄÅÔ ÔÁËÏ×Á -(\$TEXDIR ÏÚÎÁÞÁÅÔ ×ÙÂÒÁÎÎÕÀ ÄÉÒÅËÔÏÒÉÀ): - -\noindent -\begin{tabular}{>{\ttfamily}ll@{}} - \dirname{$TEXDIR/share/texmf} & ÏÓÎÏ×ÎÏÅ ÄÅÒÅ×Ï ÓÏ ÛÒÉÆÔÁÍÉ,\\ - & \qquad ÍÁËÒÏÓÙ É Ô.Ä.\\ - \dirname{$TEXDIR/man} & ÒÕËÏ×ÏÄÓÔ×Á × ÆÏÒÍÁÔÅ Unix man\\ - \dirname{$TEXDIR/info} & ÒÕËÏ×ÏÄÓÔ×Á × ÆÏÒÍÁÔÅ \acro{GNU} Info \\ - \dirname{$TEXDIR/bin/$PLATFORM} & ÐÒÏÇÒÁÍÍÙ\\ -\end{tabular} -%$ - -åÓÌÉ ×Ù ÈÏÔÉÔÅ ÕÂÒÁÔØ ÕÒÏ×ÅÎØ ÄÉÒÅËÔÏÒÉÊ \dirname{$PLATFORM}, -Ô.Å. ÐÏÍÅÓÔÉÔØ ÐÒÏÇÒÁÍÍÙ ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ × \dirname{$TEXDIR/bin}, -ÄÏÂÁ×ØÔÅ Ë ÏÐÃÉÑÍ \verb|--disable-multiplatform|. - -ðÏÓÍÏÔÒÉÔÅ ÎÁ ÒÅÚÕÌØÔÁÔ \verb|./configure --help| ÄÌÑ ÏÓÔÁÌØÎÙÈ -ÏÐÃÉÊ. îÁÐÒÉÍÅÒ, ×Ù ÍÏÖÅÔÅ ÎÅ ËÏÍÐÉÌÉÒÏ×ÁÔØ \OMEGA{} É -\eTeX{}. - - -\subsection{úÁÐÕÓË \cmdname{make}} - -õÂÅÄÉÔÅÓØ, ÞÔÏ ÐÅÒÅÍÅÎÎÁÑ ÏÂÏÌÏÞËÉ ÉÌÉ ÏÐÃÉÑ \texttt{noclobber} ÎÅ -ÚÁÄÁÎÁ. úÁÔÅÍ ÚÁÐÕÓÔÉÔÅ \cmdname{make}: -\begin{alltt} -> \Ucom{make world} -\end{alltt} -É ÒÁÓÓÌÁÂØÔÅÓØ\ldots - -åÓÌÉ ×Ù ÈÏÔÉÔÅ ÚÁÐÉÓÁÔØ × ÌÏÇ ×ÓÅ ÐÒÏÉÓÈÏÄÑÝÅÅ, ÉÓÐÏÌØÚÕÊÔÅ: -\begin{alltt} -> \Ucom{sh -c "make world >world.log 2>\&1" \&} -\end{alltt} - -ðÅÒÅÄ ÔÅÍ, ËÁË ×Ù ÒÅÛÉÔÅ, ÞÔÏ ×Ó£ ÐÒÏÛÌÏ ÎÏÒÍÁÌØÎÏ, ÐÒÏ×ÅÒØÔÅ ÌÏÇ ÎÁ -ÏÛÉÂËÉ; \acro{GNU} \cmdname{make} ×ÓÅÇÄÁ ÉÓÐÏÌØÚÕÅÔ ÓÔÒÏËÕ \samp{***} -ÐÒÉ ÏÛÉÂËÅ. ëÒÏÍÅ ÔÏÇÏ, ÐÒÏ×ÅÒØÔÅ, ÞÔÏ ×ÓÅ ÐÒÏÇÒÁÍÍÙ -ÓËÏÍÐÉÌÉÒÏ×ÁÌÉÓØ: -\begin{alltt} -> \Ucom{cd \emph{TEXDIR}/bin/\emph{archname}} -> \Ucom{ls | wc} -\end{alltt} -òÅÚÕÌØÔÁÔ ÄÏÌÖÅÎ ÂÙÔØ ÂÏÌØÛÅ 200 (×Ù ÍÏÖÅÔÅ ÐÏÌÕÞÉÔØ ÔÏÞÎÏÅ ÞÉÓÌÏ, -ÐÒÏ×ÅÒÉ× ÓÏÄÅÒÖÉÍÏÅ ÄÉÒÅËÔÏÒÉÉ -\dirname{bin} × ÄÉÓÔÒÉÂÕÔÉ×Å). - -åÓÌÉ ×ÁÍ ÎÕÖÎÙ ÓÐÅÃÉÁÌØÎÙÅ ÐÒÉ×ÉÌÅÇÉÉ ÄÌÑ \texttt{make install}, ×Ù -ÍÏÖÅÔÅ ÒÁÚÄÅÌÉÔØ \samp{make world} ÎÁ Ä×Á ÐÒÉ£ÍÁ: -\begin{alltt} -> \Ucom{make all} -> \Ucom{su} -> \Ucom{make install strip} -\end{alltt} - -ðÏÓÌÅ ÕÓÔÁÎÏ×ËÉ ×ÁÛÉÈ ÎÏ×ÙÈ ÐÒÏÇÒÁÍÍ, ×ÙÐÏÌÎÉÔÅ ÏÂÙÞÎÙÅ ÐÒÏÃÅÄÕÒÙ -ÎÁÓÔÒÏÊËÉ, ÏÐÉÓÁÎÎÙÅ × ÒÁÚÄÅÌÅ~\ref{sec:postinstall}, -\p.~\pageref{sec:postinstall}. - -ëÒÏÍÅ ÔÏÇÏ, ÅÓÌÉ ×Ù ÈÏÔÉÔÅ, ÞÔÏÂÙ ×ÁÛÉÍÉ ÐÒÏÇÒÁÍÍÁÍÉ ÐÏÌØÚÏ×ÁÌÉÓØ -ÄÒÕÇÉÅ ÌÀÄÉ, ÎÁÐÉÛÉÔÅ ÎÁÍ. íÙ ÂÕÄÅÍ ÒÁÄÙ ÐÏÍÅÓÔÉÔØ ÉÈ ÎÁ ÓÔÒÁÎÉÃÙ -\TL{} × ÓÅÔÉ. - -\end{comment} - -\section{âÌÁÇÏÄÁÒÎÏÓÔÉ} - -\TL{} "--- ÒÅÚÕÌØÔÁÔ ÏÂßÅÄÉΣÎÎÙÈ ÕÓÉÌÉÊ ÐÒÁËÔÉÞÅÓËÉ ×ÓÅÈ ÇÒÕÐÐ -ÐÏÌØÚÏ×ÁÔÅÌÅÊ \TeX Á. üÔÏ ÉÚÄÁÎÉÅ \TL{} ×ÙÈÏÄÉÔ ÐÏÄ ÒÅÄÁËÃÉÅÊ ëÁÒÌÁ -âÅÒÒÉ. äÒÕÇÉÅ ÏÓÎÏ×ÎÙÅ Á×ÔÏÒÙ, ÐÒÏÛÌÙÅ É ÎÁÓÔÏÑÝÉÅ, ÐÅÒÅÞÉÓÌÅÎÙ ÎÉÖÅ. -íÙ ÂÌÁÇÏÄÁÒÉÍ: - -\begin{itemize*} - -\item áÎÇÌÏÑÚÙÞÎÕÀ, ÎÅÍÅÃËÕÀ, ÇÏÌÌÁÎÄÓËÕÀ É ÐÏÌØÓËÕÀ ÇÒÕÐÐÙ - ÐÏÌØÚÏ×ÁÔÅÌÅÊ \TeX{}Á (\acro{TUG}, \acro{DANTE} e.V., \acro{NTG} É - \acro{GUST}) ÚÁ ÎÅÏÂÈÏÄÉÍÕÀ ÔÅÈÎÉÞÅÓËÕÀ É ÁÄÍÉÎÉÓÔÒÁÔÉ×ÎÕÀ - ÉÎÆÒÁÓÔÒÕËÔÕÒÕ. ðÏÖÁÌÕÊÓÔÁ, ×ÓÔÕÐÁÊÔÅ × ÇÒÕÐÐÙ ÐÏÌØÚÏ×ÁÔÅÌÅÊ \TeX - Á (ÓÍ. \url{http://tug.org/usergroups.html}). - -\item çÒÕÐÐÕ ÐÏÄÄÅÒÖËÉ \acro{CTAN}, × ÏÓÏÂÅÎÎÏÓÔÉ òÏÂÉÎÁ æÜÊÒÂÜÊÒÎÓÁ, - äÖÉÍÁ èÅÆÆÅÒÏÎÁ É òÁÊÎÅÒÁ ûÏÐÆÁ ÚÁ ÒÁÚÍÅÝÅÎÉÅ ÄÉÓËÏ× \TL{} É - ÐÏÄÄÅÒÖËÕ ÉÎÆÒÁÓÔÒÕËÔÕÒÙ ÏÂÎÏ×ÌÅÎÉÑ ÐÁËÅÔÏ×, ÏÔ ËÏÔÏÒÏÊ ÚÁ×ÉÓÉÔ - \TL. - -\item ðÉÔÅÒÁ âÒÅÊÔÅÎÌÏÈÎÅÒÁ É ËÏÍÁÎÄÕ ÒÁÚÒÁÂÏÔÞÉËÏ× \eTeX Á ÚÁ - ÂÕÄÕÝÉÊ \TeX Ï×, É × ÏÓÏÂÅÎÎÏÓÔÉ ðÉÔÅÒÁ ÚÁ ÂÌÅÓÔÑÝÕÀ ÒÁÂÏÔÕ Ó - ÓÉÓÔÅÍÏÊ GNU autoools ÄÌÑ \TL{}. - - -\item ôÏÍÁÓÁ üÓÓÅÒÁ, ÂÅÚ ÚÁÍÅÞÁÔÅÌØÎÏÇÏ ÐÁËÅÔÁ \teTeX{} ËÏÔÏÒÏÇÏ \TL{} - ÎÅ ÓÕÝÅÓÔ×Ï×ÁÌ ÂÙ, É ËÏÔÏÒÙÊ ÍÎÏÇÏ ÐÏÍÏÇÁÌ ÎÁÍ × ÒÁÂÏÔÅ ÎÁÄ \TL. - -\item íÁÊËÌÁ çÕÓÅÎÓÁ, ËÏÔÏÒÙÊ ÂÙÌ ÓÏÁ×ÔÏÒÏÍ ÐÅÒ×ÏÊ ×ÅÒÓÉÉ ÄÏËÕÍÅÎÔÁÃÉÉ. - - -\item üÊÔÁÎÁ çÕÒÁÒÉ, ÞÅÊ \TeX4ht{} ÉÓÐÏÌØÚÏ×ÁÌÓÑ ÄÌÑ ÓÏÚÄÁÎÉÑ ÆÁÊÌÏ× × - ÆÏÒÍÁÔÅ \HTML{}, É ËÏÔÏÒÙÊ ÎÅÕÓÔÁÎÎÏ ÒÁÂÏÔÁÌ, ÐÏ ÐÅÒ×ÏÍÕ ÔÒÅÂÏ×ÁÎÉÀ - ÄÏÂÁ×ÌÑÑ ÎÕÖÎÙÅ ÎÁÍ ×ÏÚÍÏÖÎÏÓÔÉ. - -\item èÁÎ ôÅ ôÁÎÁ, íÁÒÔÉÎÁ ûÒ£ÄÅÒÁ É ËÏÍÁÎÄÕ pdf\TeX a - (\url{http://pdftex.org}) ÚÁ ÎÅÕÓÔÁÎÎÏÅ ÒÁÓÛÉÒÅÎÉÅ ×ÏÚÍÏÖÎÏÓÔÅÊ \TeX - Á. - - -\item çÁÎÓÁ èÁÇÅÎÁ ÚÁ ÐÏÍÏÝØ × ÔÅÓÔÉÒÏ×ÁÎÉÉ É ÐÒÉÓÐÏÓÏÂÌÅÎÉÉ ÆÏÒÍÁÔÁ - \ConTeXt\ (\url{http://pragma-ade.com}) Ë ÎÁÛÉÍ ÎÕÖÄÁÍ. - -\item èÁÒÔÍÕÔÁ èÅÎËÅÌÑ ÚÁ ÓÕÝÅÓÔ×ÅÎÎÙÊ ×ËÌÁÄ × pdf\TeX\, Lua\TeX{} É - ÄÒÕÇÉÅ ÐÒÏÇÒÁÍÍÙ. - - -\item ôÁËÏ èÏË×ÁÔÅÒÁ ÚÁ ×ÏÚÏÂÎÏ×ÌÅÎÉÅ ÒÁÂÏÔÙ ÎÁÄ \MP{} É (Lua)\TeX ÏÍ - (\url{http://luatex.org}) É ÚÁ ÉÎÔÅÇÒÉÒÏ×ÁÎÉÅ \ConTeXt Á × \TL. - -\item ðÁ×ÌÁ ñËÏ×ÓËÏÇÏ ÚÁ ÉÎÓÔÁÌÌÑÔÏÒ ÄÌÑ Windows \cmdname{tlpm}, É - ôÏÍÁÛÁ ìÕÖÁËÁ ÚÁ \cmdname{tlpmgui}, ÉÓÐÏÌØÚÏ×ÁÎÎÙÅ × ÐÒÏÛÌÙÈ ×ÅÒÓÉÑÈ - \TL{}. - -\item áËÉÒÕ ëÁËÕÔÏ ÚÁ ÂÏÌØÛÕÀ ÐÏÍÏÝØ × ÉÎÔÅÇÒÉÒÏ×ÁÎÉÉ × ÓÉÓÔÅÍÕ - ÐÒÏÇÒÁÍÍ ÄÌÑ Windows ÉÚ ÅÇÏ ÄÉÓÔÒÉÂÕÔÉ×Á \acro{W32TEX} - (\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}) É ÍÎÏÇÏÅ - ÄÒÕÇÏÅ. - -\item äÖÏÎÁÔÁÎÁ ëØÀ É ÅÇÏ ÒÁÂÏÔÏÄÁÔÅÌÑ \acro{SIL} ÚÁ ÓÏÚÄÁÎÉÅ ×ÁÖÎÏÊ - ÎÏ×ÏÊ ÓÉÓÔÅÍÙ Xe\TeX{}, ÚÁ ÕÓÉÌÉÑ ÐÏ Å£ ÉÎÔÅÇÒÉÒÏ×ÁÎÉÀ × \TL{} É ÚÁ - ÉÓÈÏÄÎÕÀ ×ÅÒÓÉÀ ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ Mac\TeX. - -\item äÉËÁ ëÏÞÁ ÚÁ ÐÏÄÄÅÒÖËÕ Mac\TeX Á (\url{http://tug.org/mactex}) × - ÔÅÓÎÏÍ ÓÏÔÒÕÄÎÉÞÅÓÔ×Å Ó \TL{}, É ÚÁ ÅÇÏ ÎÅÉÓÔÏÝÉÍÙÈ ÜÎÔÕÚÉÁÚÍ. - -\item òÅÊÎÈÁÒÄÁ ëÏÔÕÞÕ ÚÁ ÏÇÒÏÍÎÕÀ ÒÁÂÏÔÕ ÐÏ ÉÎÆÒÁÓÔÒÕËÔÕÒÅ - \TL{} 2008, ÚÁ ÉÓÓÌÅÄÏ×ÁÔÅÌØÓËÕÀ ÒÁÂÏÔÕ × ÏÂÌÁÓÔÉ Windows, ÚÁ - ÓËÒÉÐÔ \texttt{getnonfreefonts} É ÍÎÏÇÏÅ ÄÒÕÇÏÅ. - - -\item óÉÐÁ ëÒÏÎÅÎÂÅÒÇÁ, ÔÁËÖÅ ÚÁ ÂÏÌØÛÏÊ ×ÌÁÄ × ÉÎÆÒÁÓÔÒÕËÔÕÒÕ \TL{} - 2008 É ÐÒÏÇÒÁÍÍÕ ÕÓÔÁÎÏ×ËÉ, ÏÓÏÂÅÎÎÏ ÄÌÑ Windows, Á ÔÁËÖÅ ÚÁ - ÏÓÎÏ×ÎÕÀ ÒÁÂÏÔÕ ÐÏ ÄÏËÕÍÅÎÔÁÃÉÉ ÎÏ×ÙÈ ×ÏÚÍÏÖÎÏÓÔÅÊ. - -\item ðÅÔÒÁ ïÌÛÁËÁ ÚÁ ËÏÏÒÄÉÎÁÃÉÀ É ÔÝÁÔÅÌØÎÕÀ ÐÒÏ×ÅÒËÕ ÞÅÛÓËÏÇÏ É - ÓÌÏ×ÁÃËÏÇÏ ÍÁÔÅÒÉÁÌÁ. - -\item ôÏÛÉÏ ïÛÉÍÕ ÚÁ ÅÇÏ ÐÒÏÓÍÏÔÒÝÉË \cmdname{dviout} ÄÌÑ Windows. - - -\item íÁÎÕÜÌÑ ðØÅÇÏÒØÅ-çÏÎÎÁÒÁ ÚÁ ÐÏÍÏÝØ × ÏÂÎÏ×ÌÅÎÉÉ ÐÁËÅÔÏ×, - ÄÏËÕÍÅÎÔÁÃÉÉ É ÒÁÚÒÁÂÏÔËÕ ÐÒÏÇÒÁÍÍÙ \cmdname{tldoc}. - -\item æÁÂÒÉÃÉÑ ðÏÐÉÎØÅ, ÚÁ ÐÏÄÄÅÒÖËÕ Windows × ÐÅÒ×ÙÈ ×ÅÒÓÉÑÈ \TL{} É - ÚÁ ÒÁÂÏÔÕ ÎÁÄ ÆÒÁÎÃÕÚÓËÏÊ ÄÏËÕÍÅÎÔÁÃÉÅÊ. - -\item îÏÒÂÅÒÔÁ ðÒÅÊÎÉÎÇÁ, ËÏÔÏÒÙÊ ÂÙÌ ÇÌÁ×ÎÙÍ ÁÒÈÉÔÅËÔÏÒÏÍ - ÉÎÆÒÁÓÔÒÕËÔÕÒÙ É ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ \TL{} 2008, Á ÔÁËÖÅ - ËÏÏÒÄÉÎÉÒÏ×ÁÌ ÄÅÂÉÁÎÏ×ÓËÕÀ ×ÅÒÓÉÀ \TL{} (ÓÏ×ÍÅÓÔÎÏ Ó æÒÁÎËÏÍ - ëÀÓÔÅÒÏÍ), ×ÙÄ×ÉÎÕ× ÍÎÏÇÏ ÃÅÎÎÙÈ ÐÒÅÄÌÏÖÅÎÉÊ. - - -\item óÅÂÁÓÔØÑÎÁ òÁÔÃÁ, ÓÏÚÄÁ×ÛÅÇÏ ÐÒÏÅËÔ \TL{} É ÍÎÏÇÏ ÌÅÔ - ÐÏÄÄÅÒÖÉ×ÁÀÝÅÇÏ ÅÇÏ. - - -\item ÷ÌÁÄÉÍÉÒÁ ÷ÏÌÏ×ÉÞÁ ÚÁ ÐÏÍÏÝØ × ÐÏÒÔÉÒÏ×ÁÎÉÉ É ÐÏÄÄÅÒÖËÅ - ÐÒÏÇÒÁÍÍ, × ÏÓÏÂÅÎÎÏÓÔÉ ÚÁ ÒÁÂÏÔÕ ÎÁÄ \cmdname{xindy}, ËÏÔÏÒÁÑ ÄÁÌÁ - ×ÏÚÍÏÖÎÏÓÔØ ×ËÌÀÞÉÔØ ÜÔÕ ÐÒÏÇÒÁÍÍÕ × ÄÉÓÔÒÉÂÕÔÉ×. - -\item óÔÁÛÅËa ÷Á×ÒÉËÅ×ÉÞÁ, ËÏÔÏÒÙÊ ÂÙÌ ÇÌÁ×ÎÙÍ ÔÅÓÔÅÒÏÍ \TL{} É - ËÏÏÒÄÉÎÉÒÏ×ÁÌ ÍÎÏÇÉÅ ÐÏÌØÓËÉÅ ÐÒÏÅËÔÙ: ÛÒÉÆÔÙ, ÕÓÔÁÎÏ×ËÕ ÐÏÄ - Windows É ÍÎÏÇÏÅ ÄÒÕÇÏÅ. - -\item ïÌÁÆÁ ÷ÅÂÅÒÁ ÚÁ ÔÅÒÐÅÌÉ×ÕÀ ÒÁÂÏÔÕ ÎÁÄ \Webc. - -\item çÅÒÂÅÎÁ ÷ÉÅÒÄÕ ÚÁ ÒÁÚÒÁÂÏÔËÕ É ÐÏÄÄÅÒÖËÕ \MacOSX, ÕÞÁÓÔÉÅ × - ÉÎÔÅÇÒÁÃÉÉ É ÔÅÓÔÉÒÏ×ÁÎÉÉ. - -\item çÒÜÍÁ ÷ÉÌÌÉÁÍÓÁ, ÓÏÚÄÁ×ÛÅÇÏ ËÁÔÁÌÏÇ ÐÁËÅÔÏ× \TeX\ Catalogue. - -\end{itemize*} - -ðÒÏÇÒÁÍÍÙ ËÏÍÐÉÌÉÒÏ×ÁÌÉ: -ôÉÇÒÁÎ áÊ×ÁÚÑÎ (\pkgname{x86\_64-linux}), -ôÉÍ áÒÎÏÌØÄ (\pkgname{hppa-hpux}), -òÜÎÄÉ áÕ (\pkgname{amd64-freebsd}), -üÄÄ âÁÒÒÅÔÔ (\pkgname{i386-openbsd}), -ëÁÒÌ âÅÒÒÉ (\pkgname{i386-linux}), -áËÉÒÁ ëÁËÕÔÏ (\pkgname{win32}), -äÉË ëÏÞ (\pkgname{universal-darwin}), -íÁÎÆÒÅÄ ìÏÔà (\pkgname{i386-freebsd}), -îÅÒÂÅÒÔ ðÒÅÊÎÉÎÇ (\pkgname{alpha-linux}), -áÒÔÕÒ òÅÊÔÅÎÁÕÜÒ (\pkgname{sparc-linux}), -ôÏÍÁÓ ûÍÉÔà (\pkgname{powerpc-linux}), -áÐÏÓÔÏÌÏÓ óÉÒÏÐÕÌÏÓ (\pkgname{i386-solaris}), -÷ÌÁÄÉÍÉÒ ×ÏÌÏ×ÉÞ (\pkgname{powerpc-aix}, \pkgname{sparc-solaris}), -ïÌÁÆ ÷ÅÂÅÒ (\pkgname{mips-irix}). -éÎÆÏÒÍÁÃÉÑ Ï ÐÒÏÃÅÓÓÅ ËÏÍÐÉÌÉÒÏ×ÁÎÉÑ \TL{} ÎÁÈÏÄÉÔÓÑ ÎÁ -\url{http://tug.org/texlive/build.html}. - - -äÏËÕÍÅÎÔÁÃÉÑ É ÐÅÒÅ×ÏÄÙ: ëÁÒÌ âÅÒÒÉ (ÁÎÇÌÉÊÓËÉÊ), -äÁÎÉÜÌØ æÌÉÐÏ (ÆÒÁÎÃÕÚÓËÉÊ), -ëÌÁÕÓ è£ÐÐÎÅÒ (ÎÅÍÅÃËÉÊ), -ðÅÔÒ óÏÊËÁ É ñÎ âÕÓÁ (ÞÅÛÓËÉÊ É ÓÌÏ×ÁÃËÉÊ), -âÏÒÉÓ ÷ÅÊÃÍÁÎ (ÒÕÓÓËÉÊ), -óÔÁÛÅË ÷Á×ÒÉËÅ×ÉÞ (ÐÏÌØÓËÉÊ). -óÔÒÁÎÉÃÁ ÄÏËÕÍÅÎÔÁÃÉÉ \TL{}: \url{http://tug.org/texlive/doc.html}. - -òÁÚÕÍÅÅÔÓÑ, ÎÁÛÁ ÇÌÁ×ÎÁÑ ÂÌÁÇÏÄÁÒÎÏÓÔØ "--- äÏÎÁÌØÄÕ ëÎÕÔÕ, ×Ï-ÐÅÒ×ÙÈ, -ÚÁ ÒÁÚÒÁÂÏÔËÕ \TeX Á, É ×Ï-×ÔÏÒÙÈ, ÚÁ ÔÏ, ÞÔÏ ÏÎ ÐÏÄÁÒÉÌ ÅÇÏ ÍÉÒÕ. - -\section{éÓÔÏÒÉÑ ÉÚÄÁÎÉÑ} -\label{sec:history} - -\subsection{ðÒÏÛÌÏÅ} - -÷ ËÏÎÃÅ 1993 ÇÏÄÁ × ÇÏÌÌÁÎÄÓËÏÊ ÇÒÕÐÐÅ ÐÏÌØÚÏ×ÁÔÅÌÅÊ \TeX{}Á ×Ï ×ÒÅÍÑ -ÒÁÂÏÔÙ ÎÁÄ ÄÉÓÔÒÉÂÕÔÉ×ÏÍ 4All\TeX{} \CD{} ÄÌÑ ÐÏÌØÚÏ×ÁÔÅÌÅÊ -\acro{MS-DOS} ×ÏÚÎÉËÌÁ ÎÏ×ÁÑ ÉÄÅÑ. âÙÌÁ ÐÏÓÔÁ×ÌÅÎÁ ÃÅÌØ ÓÏÚÄÁÔØ -ÅÄÉÎÙÊ \CD{} ÄÌÑ ×ÓÅÈ ÓÉÓÔÅÍ. üÔÁ ÃÅÌØ ÂÙÌÁ ÞÅÒÅÞÕÒ ÓÌÏÖÎÁ ÄÌÑ ÔÏÇÏ -×ÒÅÍÅÎÉ, ÏÄÎÁËÏ ÏÎÁ ÐÒÉ×ÅÌÁ ÎÅ ÔÏÌØËÏ Ë ÐÏÑ×ÌÅÎÉÀ ÏÞÅÎØ ÕÓÐÅÛÎÏÇÏ \CD{} -4All\TeX{}, ÎÏ É Ë ÓÏÚÄÁÎÉÀ ÒÁÂÏÞÅÊ ÇÒÕÐÐÙ ôÅÈÎÉÞÅÓËÏÇÏ óÏ×ÅÔÁ -\acro{TUG} ÐÏ ÓÔÒÕËÔÕÒÅ ÄÉÒÅËÔÏÒÉÊ ÄÌÑ \TeX{}Á -(\url{http://tug.org/tds}), ËÏÔÏÒÁÑ ÒÁÚÒÁÂÏÔÁÌÁ ÓÔÁÎÄÁÒÔ ÓÔÒÕËÔÕÒÙ -ÄÉÒÅËÔÏÒÉÊ ÄÌÑ ÓÉÓÔÅÍÙ \TeX{} É ÕËÁÚÁÌÁ, ËÁË ÓÏÚÄÁÔØ ÌÏÇÉÞÎÕÀ ÅÄÉÎÕÀ -ÓÉÓÔÅÍÕ ÆÁÊÌÏ× ÄÌÑ \TeX Á. îÅÓËÏÌØËÏ ×ÅÒÓÉÊ \TDS{} ÂÙÌÏ ÏÐÕÂÌÉËÏ×ÁÎÏ -× ÄÅËÁÂÒØÓËÏÍ ×ÙÐÕÓËÅ \textsl{TUGboat} × 1995 ÇÏÄÕ, É Ó ÓÁÍÏÇÏ ÎÁÞÁÌÁ -ÓÔÁÌÏ ÑÓÎÏ, ÞÔÏ ÓÌÅÄÕÅÔ ÓÏÚÄÁÔØ ÐÒÉÍÅÒ ÓÔÒÕËÔÕÒÙ ÎÁ \CD{}. äÉÓÔÒÉÂÕÔÉ×, -ËÏÔÏÒÙÊ ×Ù ÄÅÒÖÉÔÅ × ÒÕËÁÈ, "--- ÐÒÑÍÏÊ ÒÅÚÕÌØÔÁÔ ÒÁÂÏÔÙ ÜÔÏÊ ÇÒÕÐÐÙ. -éÚ ÕÓÐÅÈÁ 4All\TeX{} ÂÙÌ ÓÄÅÌÁÎ ×Ù×ÏÄ, ÞÔÏ ÐÏÌØÚÏ×ÁÔÅÌÑÍ àÎÉËÓÁ ÔÁËÖÅ -ÐÏÄÏÊÄ£Ô ÔÁËÁÑ ÕÄÏÂÎÁÑ ÓÉÓÔÅÍÁ, É ÔÁË ÒÏÄÉÌÁÓØ ÄÒÕÇÁÑ ×ÁÖÎÁÑ ÞÁÓÔØ -\TL. - -íÙ ÎÁÞÁÌÉ ÄÅÌÁÔØ \CD{} Ó àÎÉËÓÏÍ É ÓÔÒÕËÔÕÒÏÊ ÄÉÒÅËÔÏÒÉÊ \TDS{} ÏÓÅÎØÀ -1995 ÇÏÄÁ, É ÂÙÓÔÒÏ ÐÏÎÑÌÉ, ÞÔÏ Õ \teTeX{}Á ôÏÍÁÓÁ üÓÓÅÒÁ ÉÄÅÁÌØÎÙÊ -ÓÏÓÔÁ× ÄÉÓÔÒÉÂÕÔÉ×Á É ÐÏÄÄÅÒÖËÁ ÍÎÏÇÉÈ ÐÌÁÔÆÏÒÍ. ôÏÍÁÓ ÓÏÇÌÁÓÉÌÓÑ ÎÁÍ -ÐÏÍÏÞØ, É ÍÙ × ÎÁÞÁÌÅ 1996 ÇÏÄÁ ÓÔÁÌÉ ÓÅÒØ£ÚÎÏ ÒÁÂÏÔÁÔØ ÎÁÄ -ÄÉÓÔÒÉÂÕÔÉ×ÏÍ. ðÅÒ×ÏÅ ÉÚÄÁÎÉÅ ×ÙÛÌÏ × ÍÁÅ 1996 ÇÏÄÁ. ÷ ÎÁÞÁÌÅ 1997 -ÇÏÄÁ ëÁÒÌ âÅÒÒÉ ÚÁ×ÅÒÛÉÌ ÎÏ×ÕÀ ×ÅÒÓÉÀ Web2C, ËÏÔÏÒÁÑ ×ËÌÀÞÉÌÁ -ÐÒÁËÔÉÞÅÓËÉ ×ÓÅ ÎÏ×ÙÅ ×ÏÚÍÏÖÎÏÓÔÉ, ÄÏÂÁ×ÌÅÎÎÙÅ ôÏÍÁÓÏÍ üÓÓÅÒÏÍ × -\teTeX, É ÍÙ ÒÅÛÉÌÉ ÏÓÎÏ×ÁÔØ ×ÔÏÒÏÅ ÉÚÄÁÎÉÅ ÎÁ ÓÔÁÎÄÁÒÔÎÏÍ \Webc, Ó -ÄÏÂÁ×ÌÅÎÉÅÍ ÓËÒÉÐÔÁ \texttt{texconfig} ÉÚ \teTeX{}Á. ôÒÅÔØÅ ÉÚÄÁÎÉÅ -\CD{} ÏÓÎÏ×Ù×ÁÌÏÓØ ÎÁ ÎÏ×ÏÊ ×ÅÒÓÉÉ \Webc{} 7.2, ïÌÁÆÁ ÷ÅÂÅÒÁ; × ÔÏ ÖÅ -×ÒÅÍÑ ÂÙÌÁ ×ÙÐÕÝÅÎÁ ÎÏ×ÁÑ ×ÅÒÓÉÑ \teTeX{}Á, É \TL{} ×ËÌÀÞÉÌ ÐÏÞÔÉ ×ÓÅ -ÅÇÏ ÎÏ×ÙÅ ×ÏÚÍÏÖÎÏÓÔÉ. þÅÔ×ÅÒÔÏÅ ÉÚÄÁÎÉÅ ÓÌÅÄÏ×ÁÌÏ ÔÏÊ ÖÅ ÔÒÁÄÉÃÉÉ, -ÉÓÐÏÌØÚÕÑ ÎÏ×ÕÀ ×ÅÒÓÉÀ \teTeX{}Á É \Webc{} (7.3). ôÅÐÅÒØ × Î£Í ÂÙÌÁ -ÐÏÌÎÁÑ ÓÉÓÔÅÍÁ ÄÌÑ Windows. - -äÌÑ ÐÑÔÏÇÏ ÉÚÄÁÎÉÑ (ÍÁÒÔ 2000 ÇÏÄÁ) ÍÎÏÇÉÅ ÐÁËÅÔÙ ÎÁ \CD{} ÂÙÌÉ -ÐÅÒÅÓÍÏÔÒÅÎÙ É ÐÒÏ×ÅÒÅÎÙ. éÎÆÏÒÍÁÃÉÑ Ï ÐÁËÅÔÁÈ ÂÙÌÁ ÓÏÂÒÁÎÁ × ÆÁÊÌÙ -XML. îÏ ÇÌÁ×ÎÙÍ ÉÚÍÅÎÅÎÉÅÍ × \TeX\ Live 5 ÂÙÌÏ ÕÄÁÌÅÎÉÅ ×ÓÅÈ -ÎÅÓ×ÏÂÏÄÎÙÈ ÐÒÏÇÒÁÍÍ. ÷Ó£ ÎÁ \TL{} ÐÒÅÐÏÌÁÇÁÅÔÓÑ ÓÏ×ÍÅÓÔÉÍÙÍ Ó -ðÒÁ×ÉÌÁÍÉ äÅÂÉÁÎÁ ÄÌÑ ó×ÏÂÏÄÎÙÈ ðÒÏÇÒÁÍÍ -(\url{http://www.debian.org/intro/free}); ÍÙ ÓÄÅÌÁÌÉ ×Ó£, ÞÔÏ ÍÏÇÌÉ, -ÞÔÏÂÙ ÐÒÏ×ÅÒÉÔØ ÌÉÃÅÎÚÉÉ ×ÓÅÈ ÐÁËÅÔÏ×, É ÍÙ ÂÕÄÅÍ ÂÌÁÇÏÄÁÒÎÙ ÚÁ ÌÀÂÏÅ -ÕËÁÚÁÎÉÅ ÎÁ ÏÛÉÂËÉ. - -÷ ÛÅÓÔÏÍ ÉÚÄÁÎÉÉ (ÉÀÌØ 2001 ÇÏÄÁ) ÂÙÌÏ ÍÎÏÇÏ ÎÏ×ÏÇÏ ÍÁÔÅÒÉÁÌÁ. -çÌÁ×ÎÙÍ ÂÙÌÁ ÎÏ×ÁÑ ËÏÎÃÅÐÃÉÑ ÕÓÔÁÎÏ×ËÉ: ÐÏÌØÚÏ×ÁÔÅÌØ ×ÙÂÉÒÁÌ ÎÕÖÎÙÊ -ÎÁÂÏÒ ËÏÌÌÅËÃÉÊ. ñÚÙËÏ×ÙÅ ËÏÌÌÅËÃÉÉ ÂÙÌÉ ÐÏÌÎÏÓÔØÀ ÒÅÏÒÇÁÎÉÚÏ×ÁÎÙ, -ÔÁË ÞÔÏ ×ÙÂÏÒ ÌÀÂÏÊ ÉÚ ÎÉÈ ÕÓÔÁÎÁ×ÌÉ×ÁÌ ÎÅ ÔÏÌØËÏ ÍÁËÒÏÓÙ, ÛÒÉÆÔÙ É É -Ô.Ä., ÎÏ É ×ÎÏÓÉÌ ÉÚÍÅÎÅÎÉÑ × \texttt{language.dat}. - -óÅÄØÍÏÅ ÉÚÄÁÎÉÅ 2002 ÇÏÄÁ ÄÏÂÁ×ÉÌÏ ÐÏÄÄÅÒÖËÕ \MacOSX{}, É ÂÏÌØÛÏÅ -ËÏÌÉÞÅÓÔ×Ï ÏÂÎÏ×ÌÅÎÉÊ ÄÌÑ ÐÁËÅÔÏ× É ÐÒÏÇÒÁÍÍ. ÷ÁÖÎÏÊ ÃÅÌØÀ ÂÙÌÁ -ÉÎÔÅÇÒÁÃÉÑ Ó \teTeX{}ÏÍ, ÞÔÏÂÙ ÉÓÐÒÁ×ÉÔØ ÒÁÓÈÏÖÄÅÎÉÅ, ÎÁÍÅÔÉ×ÛÅÅÓÑ × -×ÅÒÓÉÑÈ~5 É~6. - -\subsubsection{2003} - -÷ 2003 ÇÏÄÕ ÍÙ ÐÒÏÄÏÌÖÉÌÉ ÉÚÍÅÎÅÎÉÑ É ÄÏÐÏÌÎÅÎÉÑ, É ÏÂÎÁÒÕÖÉÌÉ, ÞÔÏ -\TL{} ÔÁË ×ÙÒÏÓ, ÞÔÏ ÎÅ ÐÏÍÅÝÁÅÔÓÑ ÎÁ \CD. ðÏÜÔÏÍÕ ÍÙ ÒÁÚÄÅÌÉÌÉ ÅÇÏ ÎÁ -ÔÒÉ ÄÉÓÔÒÉÂÕÔÉ×Á. ëÒÏÍÅ ÔÏÇÏ: - -\begin{itemize*} -\item ðÏ ÐÒÏÓØÂÅ Á×ÔÏÒÏ× \LaTeX{}Á, ÍÙ ÓÍÅÎÉÌÉ ÓÔÁÎÄÁÒÔÎÙÅ ËÏÍÁÎÄÙ - \cmdname{latex} É \cmdname{pdflatex}: ÔÅÐÅÒØ ÏÎÉ ÉÓÐÏÌØÚÕÀÔ \eTeX{} - (ÓÍ. ÓÔÒ.~\pageref{text:etex}). -\item îÏ×ÙÅ ÛÒÉÆÔÙ Latin Modern ×ËÌÀÞÅÎÙ É ÒÅËÏÍÅÎÄÏ×ÁÎÙ ÄÌÑ ÉÓÐÏÌØÚÏ×ÁÎÉÑ. -\item õÂÒÁÎÁ ÐÏÄÄÅÒÖËÁ ÄÌÑ Alpha \acro{OSF} - (ÐÏÄÄÅÒÖËÁ ÄÌÑ \acro{HPUX} ÂÙÌÁ ÕÂÒÁÎÁ ÒÁÎÅÅ), ÐÏÓËÏÌØËÕ ÎÉËÔÏ - ÎÅ ÉÍÅÌ (É ÎÅ ÐÒÅÄÌÏÖÉÌ) ËÏÍÐØÀÔÅÒÏ× ÄÌÑ ËÏÍÐÉÌÉÒÏ×ÁÎÉÑ - ÐÒÏÇÒÁÍÍ. -\item óÉÌØÎÏ ÉÚÍÅÎÉÌÁÓØ ÕÓÔÁÎÏ×ËÁ ÄÌÑ Windows: ×ÐÅÒ×ÙÅ ÂÙÌÁ ÐÒÅÄÌÏÖÅÎÁ - ÉÎÔÅÇÒÉÒÏ×ÁÎÎÁÑ ÓÒÅÄÁ ÎÁ ÏÓÎÏ×Å ÒÅÄÁËÔÏÒÁ XEmacs. -\item äÏÂÁ×ÌÅÎÙ ×ÓÐÏÍÏÇÁÔÅÌÎÙÅ ÐÒÏÇÒÁÍÍÙ ÄÌÑ Windows - (Perl, Ghost\-script, Image\-Magick, Ispell). -\item æÁÊÌÙ Fontmap ÄÌÑ \cmdname{dvips}, \cmdname{dvipdfm} - É \cmdname{pdftex} ÇÅÎÅÒÉÒÕÀÔÒÓÑ ÐÒÏÇÒÁÍÍÏÊ - \cmdname{updmap} É ÕÓÔÁÎ×ÁÌÉ×ÁÀÔÓÑ × \dirname{texmf/fonts/map}. -\item \TeX{}, \MF{}, and \MP{} ÔÅÐÅÒØ ÐÏ ÕÍÏÌÞÁÎÉÀ ×Ù×ÏÄÑÔ ÓÉÍ×ÏÌÙ - ÉÚ ×ÅÒÈÎÅÊ ÐÏÌÏ×ÉÎÙ ÔÁÂÌÉÃÙ ASCII × ÆÁÊÌÙ, ÏÔËÒÙÔÙÅ - ËÏÍÁÎÄÏÊ \verb|\write|, ÌÏÇÉ É ÎÁ ÔÅÒÍÉÎÁÌ ÂÕË×ÁÌØÎÏ, - Ô.Å. \emph{ÎÅ} ÉÓÐÏÌØÚÕÑ ÆÏÒÍÁÔ \verb|^^|. ÷ \TL{}~7 ÜÔÏ ÚÁ×ÉÓÅÌÏ ÏÔ - ÓÉÓÔÅÍÎÏÊ ÌÏËÁÌÉ, ÎÏ ÔÅÐÅÒØ ÜÔÏ ×ÅÒÎÏ ÄÌÑ ×ÓÅÈ ÌÏËÁÌÅÊ. åÓÌÉ - ×ÁÍ ÎÕÖÅÎ ÆÏÒÍÁÔ \verb|^^|, ÐÅÒÅÉÍÅÎÕÊÔÅ ÆÁÊÌ - \verb|texmf/web2c/cp8bit.tcx|. ÷ ÂÕÄÕÝÅÍ ÜÔÁ ÐÒÏÃÅÄÕÒÁ ÂÕÄÅÔ - ÕÐÒÏÝÅÎÁ. -\item äÏËÕÍÅÎÔÁÃÉÑ ÂÙÌÁ ÓÕÝÅÓÔ×ÅÎÎÏ ÏÂÎÏ×ÌÅÎÁ. -\item îÁËÏÎÅÃ, ÉÚ-ÚÁ ÔÏÇÏ, ÞÔÏ ÎÕÍÅÒÁÃÉÑ ÐÏ ÉÚÄÁÎÉÑÍ ÓÔÁÌÁ ÎÅÕÄÏÂÎÏÊ, - ÍÙ ÐÅÒÅÛÌÉ ÎÁ ÎÕÍÅÒÁÃÉÀ ÐÏ ÇÏÄÁÍ: \TL{} 2003. -\end{itemize*} - -\subsubsection{2004} - -÷ 2004 ÇÏÄÕ ÍÙ ×ÎÅÓÌÉ ÍÎÏÇÏ ÉÚÍÅÎÅÎÉÊ. - -\begin{itemize} - -\item åÓÌÉ Õ ×ÁÓ ÅÓÔØ ÌÏËÁÌØÎÙÅ ÛÒÉÆÔÙ Ó ÓÏÂÓÔ×ÅÎÎÙÍÉ ÆÁÊÌÁÍÉ - \filename{.map} ÉÌÉ \filename{.enc}, ×ÁÍ ÍÏÖÅÔ ÐÏÎÁÄÏÂÉÔØÓÑ - ÐÅÒÅÍÅÓÔÉÔØ ÜÔÉ ÆÁÊÌÙ. - - æÁÊÌÙ \filename{.map} ÔÅÐÅÒØ ÉÝÕÔÓÑ ÔÏÌØËÏ × ÐÏÄÄÉÒÅËÔÏÒÉÑÈ - \dirname{fonts/map} (× ËÁÖÄÏÍ ÄÅÒÅ×Å \filename{texmf}) × ÐÕÔÉ - \envname{TEXFONTMAPS}. áÎÁÌÏÇÉÞÎÏ ÆÁÊÌÙ \filename{.enc} ÔÅÐÅÒØ - ÉÝÕÔÓÑ × ÔÏÌØËÏ × ÐÏÄÄÉÒÅËÔÏÒÉÑÈ \dirname{fonts/enc} × ÐÕÔÉ - \envname{ENCFONTS}. ðÒÏÇÒÁÍÍÁ \cmdname{updmap} ÐÒÅÄÕÐÒÅÖÄÁÅÔ, ÅÓÌÉ - ÎÁÈÏÄÉÔ ÜÔÉ ÆÁÊÌÙ ÎÅ ÔÁÍ, ÇÄÅ ÏÎÉ ÄÏÌÖÎÙ ÂÙÔØ. - - óÍ. ÏÐÉÓÁÎÉÅ ÜÔÏÊ ÓÔÒÕËÔÕÒÙ ÎÁ - \url{http://tug.org/texlive/mapenc.html}. - -\item ë ËÏÌÌÅËÃÉÉ \TK{} ÂÙÌ ÄÏÂÁ×ÌÅÎ ÕÓÔÁÎÏ×ÏÞÎÙÊ \CD{} Ó - ÄÉÓÔÒÉÂÕÔÉ×ÏÍ \MIKTEX{} ÄÌÑ ÔÅÈ, ËÔÏ ÐÒÅÄÐÏÞÉÔÁÅÔ \MIKTEX{} - ÐÒÏÇÒÁÍÍÁÍ, ÏÓÎÏ×ÁÎÎÙÍ ÎÁ \Webc. óÍ. ÒÁÚÄÅÌ~\ref{sec:overview-tl} - (\p.\pageref{sec:overview-tl}). - - -\item äÅÒÅ×Ï \dirname{texmf} × \TL{} ÂÙÌÏ ÒÁÚÄÅÌÅÎÏ ÎÁ ÔÒÉ: - \dirname{texmf}, \dirname{texmf-dist} É \dirname{texmf-doc}. - óÍ. ÒÁÚÄÅÌ~\ref{sec:tld} (\p.\pageref{sec:tld}) É ÆÁÊÌÙ - \filename{README} × ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÈ ÄÉÒÅËÔÏÒÉÑÈ. - -\item ÷ÓÅ ÆÁÊÌÙ, ËÏÔÏÒÙÅ ÞÉÔÁÅÔ \TeX, ÓÏÂÒÁÎÙ × ÐÏÄÄÉÒÅËÔÏÒÉÉ - \dirname{tex} ÄÅÒÅ×ØÅ× \dirname{texmf*} ×ÍÅÓÔÏ ÒÁÚÄÅÌÅÎÉÑ ÎÁ - \dirname{tex}, \dirname{etex}, \dirname{pdftex}, \dirname{pdfetex} É - Ô.Ä. óÍ. \CDref{texmf-doc/doc/english/tds/tds.html\#Extensions} - {\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}. - - -\item ÷ÓÐÏÍÏÇÁÔÅÌØÎÙÅ ÓËÒÉÐÔÙ (×ÙÚÙ×ÁÅÍÙÅ ÄÒÕÇÉÍÉ ÐÒÏÇÒÁÍÍÁÍÉ, Á ÎÅ - ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ ÐÏÌØÚÏ×ÁÔÅÌÅÍ) ÔÅÐÅÒØ ÓÏÂÒÁÎÙ × ÄÉÒÅËÔÏÒÉÉ - \dirname{scripts} ÄÅÒÅ×ØÅ× \dirname{texmf*} É ÉÝÕÔÓÑ ËÏÍÁÎÄÏÊ - \verb|kpsewhich -format=texmfscripts|. ðÏÜÔÏÍÕ ÅÓÌÉ Õ ×ÁÓ ÅÓÔØ - ÐÒÏÇÒÁÍÍÙ, ËÏÔÏÒÙÅ ×ÙÚÙ×ÁÀÔ ÔÁËÉÅ ÓËÒÉÐÔÙ, ÉÈ ÎÁÄÏ ÉÚÍÅÎÉÔØ. óÍ. - \CDref{texmf-doc/doc/english/tds/tds.html\#Scripts} - {\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}. - - -\item ðÏÞÔÉ ×ÓÅ ÆÏÒÍÁÔÙ ÔÅÐÅÒØ ÐÅÞÁÔÁÀÔ ÂÏÌØÛÉÎÓÔ×Ï ÓÉÍ×ÏÌÏ× - ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ, ÉÓÐÏÌØÚÕÑ <<ÔÁÂÌÉÃÙ ÐÅÒÅ×ÏÄÁ>> \filename{cp227.tcx} - ×ÍÅÓÔÏ ÆÏÒÍÁÔÁ \verb|^^|. ÷ ÞÁÓÔÎÏÓÔÉ, ÓÉÍ×ÏÌÙ Ó ËÏÄÁÍÉ 32--256 - ÐÌÀÓ ÔÁÂÕÌÑÃÉÑ, ×ÅÒÔÉËÁÌØÎÁÑ ÔÁÂÕÌÑÃÉÑ É ÐÅÒÅ×ÏÄ ÓÔÒÁÎÉÃÙ ÐÅÞÁÔÁÀÔÓÑ - ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ. éÓËÌÀÞÅÎÉÑÍÉ Ñ×ÌÑÀÔÓÑ plain \TeX{} (ÐÅÞÁÔÁÀÔÓÑ - ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ ÓÉÍ×ÏÌÙ 32--127), \ConTeXt{} (0--255) É ÆÏÒÍÁÔÙ, - ÏÔÎÏÓÑÝÉÅÓÑ Ë ÐÒÏÇÒÁÍÍÅ \OMEGA. üÔÏ ÐÏ×ÅÄÅÎÉÅ ÐÏÞÔÉ ÔÁËÏÅ ÖÅ, ËÁË Õ - \TL\,2003, ÎÏ ÒÅÁÌÉÚÏ×ÁÎÏ ÂÏÌÅÅ ÁËËÕÒÁÔÎÏ, Ó Â\'ÏÌØÛÅÊ ×ÏÚÍÏÖÎÏÓÔØÀ - ÎÁÓÔÒÏÊËÉ. óÍ. \CDref{texmf/doc/web2c/web2c.html\#TCX-files} - {\texttt{texmf/doc/web2c/web2c.html\#TCX-files}}. (ëÓÔÁÔÉ, ÐÒÉ ××ÏÄÅ - × Unicode, \TeX\ ÍÏÖÅÔ ×Ù×ÏÄÉÔØ ÐÒÉ ÕËÁÚÁÎÉÉ ÎÁ ÏÛÉÂËÕ ÔÏÌØËÏ ÞÁÓÔØ - ÍÎÏÇÏÂÁÊÔÎÏÇÏ ÓÉÍ×ÏÌÁ, ÔÁË ËÁË ×ÎÕÔÒÉ \TeX\ ÒÁÂÏÔÁÅÔ Ó ÂÁÊÔÁÍÉ). - - -\item \textsf{pdfetex} ÔÅÐÅÒØ ÉÓÐÏÌØÚÕÅÔÓÑ ÄÌÑ ×ÓÅÈ ÆÏÒÍÁÔÏ×, ËÒÏÍÅ - plain \textsf{tex}. (òÁÚÕÍÅÅÔÓÑ, ÏÎ ÄÅÌÁÅÔ ÆÁÊÌÙ × ÆÏÒÍÁÔÅ - \acro{DVI}, ÅÓÌÉ ×ÙÚ×ÁÎ ËÁË \textsf{latex} É Ô.Ð.). üÔÏ ÏÚÎÁÞÁÅÔ, - ÐÏÍÉÍÏ ÐÒÏÞÅÇÏ, ÞÔÏ ×ÏÚÍÏÖÎÏÓÔÉ \textsf{pdftex}a ÄÌÑ ÍÉËÒÏÔÉÐÏÇÒÁÆÉÉ - Á ÔÁËÖÅ ×ÏÚÍÏÖÎÏÓÔÉ \eTeX Á ÄÏÓÔÕÐÎÙ × ÆÏÒÍÁÔÁÈ \LaTeX, \ConTeXt{} É - Ô.Ä. (\OnCD{texmf-dist/doc/etex/base/}). - - üÔÏ ÔÁËÖÅ ÏÚÎÁÞÁÅÔ, ÞÔÏ ÔÅÐÅÒØ \emph{ÏÞÅÎØ ×ÁÖÎÏ} ÉÓÐÏÌØÚÏ×ÁÔØ ÐÁËÅÔ - \pkgname{ifpdf} (ÒÁÂÏÔÁÅÔ É Ó plain, É Ó \LaTeX) ÉÌÉ ÜË×É×ÁÌÅÎÔÎÙÅ - ÓÒÅÄÓÔ×Á, ÐÏÓËÏÌØËÕ ÐÒÏÓÔÏ ÐÒÏ×ÅÒËÁ, ÏÐÒÅÄẠ̊ΠÌÉ \cs{pdfoutput} ÉÌÉ - ÄÒÕÇÏÊ ÐÒÉÍÉÔÉ× ÎÅ ÄÏÓÔÁÔÏÞÎÁ ÄÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÐÏÎÑÔØ, × ËÁËÏÍ - ÆÏÒÍÁÔÅ ÇÅÎÅÒÉÒÕÅÔÓÑ ÒÅÚÕÌØÔÁÔ. íÙ ÓÄÅÌÁÌÉ ×Ó£ ×ÏÚÍÏÖÎÏÅ ÄÌÑ - ÓÏ×ÍÅÓÔÉÍÏÓÔÉ × ÜÔÏÍ ÇÏÄÕ, ÎÏ × ÂÕÄÕÝÅÍ ÇÏÄÕ \cs{pdfoutput} ÍÏÖÅÔ - ÂÙÔØ ÏÐÒÅÄẠ̊ΠÄÁÖÅ ÅÓÌÉ ÇÅÎÅÒÉÒÕÅÔÓÑ \acro{DVI}. - - -\item õ ÐÒÏÇÒÁÍÍÙ pdf\TeX\ (\url{http://pdftex.org}) ÍÎÏÇÏ ÎÏ×ÙÈ - ×ÏÚÍÏÖÎÏÓÔÅÊ: - - \begin{itemize*} - - \item ðÏÄÄÅÒÖËÁ ËÁÒÔ ÛÒÉÆÔÏ× ÉÚÎÕÔÒÉ ÄÏËÕÍÅÎÔÁ ÐÒÉ ÐÏÍÏÝÉ - \cs{pdfmapfile} É \cs{pdfmapline}. - - \item íÉËÒÏÔÉÐÏÇÒÁÆÉÞÅÓËÉÅ ÒÁÓÛÉÒÅÎÉÑ ÍÏÇÕÔ ÂÙÔØ ÉÓÐÏÌØÚÏ×ÁÎÙ - ÎÁÍÎÏÇÏ - ÐÒÏÝÅ.\\ - \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} - - - \item ÷ÓÅ ÐÁÒÁÍÅÔÒÙ, ÒÁÎÅÅ ÚÁÄÁ×Á×ÛÉÅÓÑ × ÓÐÅÃÉÁÌØÎÏÍ - ËÏÎÆÉÇÕÒÁÃÉÏÎÎÏÍ ÆÁÊÌÅ \filename{pdftex.cfg}, ÔÅÐÅÒØ ÄÏÌÖÎÙ ÂÙÔØ - ÕÓÔÁÎÏ×ÌÅÎÙ ÐÒÉÍÉÔÉ×ÁÍÉ, ÎÁÐÒÉÍÅÒ, × ÆÁÊÌÅ - \filename{pdftexconfig.tex}. æÁÊÌ \filename{pdftex.cfg} ÂÏÌØÛÅ ÎÅ - ÐÏÄÄÅÒÖÉ×ÁÅÔÓÑ. ðÒÉ ÉÚÍÅÎÅÎÉÉ ÆÁÊÌÁ \filename{pdftexconfig.tex} - ×ÓÅ ÆÏÒÍÁÔÙ \filename{.fmt} ÄÏÌÖÎÙ ÂÙÔØ ÐÅÒÅÇÅÎÅÒÉÒÏ×ÁÎÙ. - - \item ïÓÔÁÌØÎÙÅ ÉÚÍÅÎÅÎÉÑ ÏÐÉÓÁÎÙ × ÒÕËÏ×ÏÄÓÔ×Å ÐÏÌØÚÏ×ÁÔÅÌÑ - ÐÒÏÇÒÁÍÍÏÊ pdf\TeX: \OnCD{texmf/doc/pdftex/manual}. - - \end{itemize*} - - -\item ðÒÉÍÉÔÉ× \cs{input} × ÐÒÏÇÒÁÍÍÅ \cmdname{tex} (É \cmdname{mf} É - \cmdname{mpost}) ÔÅÐÅÒØ ÐÒÁ×ÉÌØÎÏ ÉÎÔÅÒÐÒÅÔÉÒÕÅÔ ÐÒÏÂÅÌÙ É ÄÒÕÇÉÅ - ÓÐÅÃÉÁÌØÎÙÅ ÓÉÍ×ÏÌÙ × Ä×ÏÊÎÙÈ ËÁ×ÙÞËÁÈ. ÷ÏÔ ÔÉÐÉÞÎÙÅ ÐÒÉÍÅÒÙ: -\begin{verbatim} -\input "filename with spaces" % plain -\input{"filename with spaces"} % latex -\end{verbatim} -óÍ. ÐÏÄÒÏÂÎÏÓÔÉ × ÒÕËÏ×ÏÄÓÔ×Å Ë ÐÒÏÇÒÁÍÍÅ \Webc: \OnCD{texmf/doc/web2c}. - - -\item ðÏÄÄÅÒÖËÁ enc\TeX Á ×ËÌÀÞÅÎÁ × \Webc, É ÐÏÜÔÏÍÕ ×Ï ×ÓÅ - ÐÒÏÇÒÁÍÍÙ \TeX, ËÏÔÏÒÙÅ ÔÅÐÅÒØ ÐÏÄÄÅÒÖÉ×ÁÀÔ ÏÐÃÉÀ \optname{-enc} - (ÔÏÌØËÏ ÐÒÉ ÇÅÎÅÒÉÒÏ×ÁÎÉÉ ÆÏÒÍÁÔÏ×). enc\TeX{} - ÏÂÅÓÐÅÞÉ×ÁÅÔ ÏÂÝÕÀ ÐÅÒÅËÏÄÉÒÏ×ËÕ ×ÈÏÄÎÏÇÏ É ×ÙÈÏÄÎÏÇÏ ÐÏÔÏËÏ×, ÞÔÏ - ÐÏÚ×ÏÌÑÅÔ ÐÏÌÎÕÀ ÐÏÄÄÅÒÖËÕ Unicode (× \acro{UTF}-8). - óÍ. \OnCD{texmf-dist/doc/generic/enctex/} É - \url{http://www.olsak.net/enctex.html}. - -\item ÷ ÄÉÓÔÒÉÂÕÔÉ×Å ÐÏÑ×ÉÌÁÓØ ÎÏ×ÁÑ ÐÒÏÇÒÁÍÍÁ Aleph, ÓÏÞÅÔÁÀÝÁÑ - \eTeX\ É \OMEGA. ëÒÁÔËÁÑ ÉÎÆÏÒÍÁÃÉÑ Ï ÎÅÊ ÎÁÈÏÄÉÔÓÑ × - \OnCD{texmf-dist/doc/aleph/base} É - \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph}. æÏÒÍÁÔ - ÄÌÑ \LaTeX Á ÎÁ ÏÓÎÏ×Å ÜÔÏÊ ÐÒÏÇÒÁÍÍÙ ÎÁÚÙ×ÁÅÔÓÑ \textsf{lamed}. - -\item ðÏÓÌÅÄÎÑÑ ×ÅÒÓÉÑ \LaTeX Á ×ËÌÀÞÁÅÔ ÎÏ×ÕÀ ×ÅÒÓÉÀ ÌÉÃÅÎÚÉÉ - \acro{LPPL} "--- ÔÅÐÅÒØ ÏÆÉÃÉÁÌØÎÏ ÏÄÏÂÒÅÎÎÕÀ DebianÏÍ. îÅËÏÔÏÒÙÅ - ÄÒÕÇÉÅ ÉÚÍÅÎÅÎÉÑ ÐÅÒÅÞÉÓÌÅÎÙ × ÆÁÊÌÁÈ \filename{ltnews} × - \OnCD{texmf-dist/doc/latex/base}. - -\item ÷ ÄÉÓÔÒÉÂÕÔÉ×Å ÐÏÑ×ÉÌÁÓØ \cmdname{dvipng}, ÎÏ×ÁÑ ÐÒÏÇÒÁÍÍÁ ÄÌÑ - ÐÅÒÅ×ÏÄÁ \acro{DVI} × \acro{PNG}. - óÍ. \OnCD{texmf/doc/man/man1/dvipng.1}. - -\item íÙ ÕÍÅÎØÛÉÌÉ ÒÁÚÍÅÒ ÐÁËÅÔÁ \pkgname{cbgreek} ÄÏ ÐÒÉÅÍÌÅÍÏÇÏ - ÎÁÂÏÒÁ ÛÒÉÆÔÏ×, Ó ÓÏÇÌÁÓÉÑ É ÓÏ×ÅÔÁ Á×ÔÏÒÁ (ëÌÁÕÄÉÏ âÅËËÁÒÉ). - éÓËÌÀÞÅÎÙ ÎÅ×ÉÄÉÍÙÅ, ÐÒÏÚÒÁÞÎÙÅ É ÐÏÌÕÐÒÏÚÒÁÞÎÙÅ ÛÒÉÆÔÙ, ËÏÔÏÒÙÅ - ÏÔÎÏÓÉÔÅÌØÎÏ ÒÅÄËÏ ÉÓÐÏÌØÚÕÀÔÓÑ, Á ÎÁÍ ÎÅ È×ÁÔÁÌÏ ÍÅÓÔÁ. ðÏÌÎÙÊ - ÎÁÂÏÒ ÛÒÉÆÔÏ× ÍÏÖÎÏ ÎÁÊÔÉ × ÁÒÈÉ×Å \acro{CTAN} - (\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). - - -\item ðÒÏÇÒÁÍÍÁ \cmdname{oxdvi} ÕÄÁÌÅÎÁ ÉÚ ÄÉÓÔÒÉÂÕÔÉ×Á; ÉÓÐÏÌØÚÕÊÔÅ - \cmdname{xdvi}. - - -\item ìÉÎËÉ \cmdname{ini} É \cmdname{vir} ÄÌÑ ÐÒÏÇÒÁÍÍ \cmdname{tex}, - \cmdname{mf} É \cmdname{mpost} (ÎÁÐÒÉÍÅÒ, \cmdname{initex}) ÂÏÌØÛÅ - ÎÅ ÓÏÚÄÁÀÔÓÑ. õÖÅ ÍÎÏÇÏ ÌÅÔ ÏÐÃÉÑ \optname{-ini} ÉÈ ÕÓÐÅÛÎÏ - ÚÁÍÅÎÑÅÔ. - -\item õÂÒÁÎÁ ÐÏÄÄÅÒÖËÁ ÐÌÁÔÆÏÒÍÙ \textsf{i386-openbsd}. ôÁË ËÁË × - ÐÏÒÔÁÈ BSD ÅÓÔØ ÐÁËÅÔ \pkgname{tetex}, É ÍÏÖÎÏ ÐÏÌØÚÏ×ÁÔØÓÑ - ÐÒÏÇÒÁÍÍÁÍÉ ÄÌÑ \acro{GNU/}Linux É Free\acro{BSD}, ÍÙ ÐÏÓÞÉÔÁÌÉ, ÞÔÏ - ×ÒÅÍÑ ÄÏÂÒÏ×ÏÌØÎÙÈ ÓÏÔÒÕÄÎÉËÏ× ÐÒÏÅËÔÁ ÍÏÖÎÏ ÐÏÔÒÁÔÉÔØ Ó Â\'ÏÌØÛÅÊ - ÐÏÌØÚÏÊ ÐÏ-ÄÒÕÇÏÍÕ. - - -\item ðÏ ËÒÁÊÎÅÊ ÍÅÒÅ ÄÌÑ ÐÌÁÔÆÏÒÍÙ \textsf{sparc-solaris} ÔÒÅÂÕÅÔÓÑ - ÕÓÔÁÎÏ×ÉÔØ ÐÅÒÅÍÅÎÎÕÀ ÏËÒÕÖÅÎÉÑ \envname{LD\_LIBRARY\_PATH} ÄÌÑ - ÒÁÂÏÔÙ ÐÒÏÇÒÁÍÍ \pkgname{t1utils}. üÔÏ ×ÙÚ×ÁÎÏ ÔÅÍ, ÞÔÏ ÏÎÉ - ÎÁÐÉÓÁÎÙ ÎÁ C++, Á ÓÔÁÎÄÁÒÔÎÏÊ ÄÉÒÅËÔÏÒÉÉ ÄÌÑ ÂÉÂÉÌÉÏÔÅË C++ × - ÓÉÓÔÅÍÅ ÎÅÔ (ÜÔÏ ÐÏÑ×ÉÌÏÓØ ÄÏ 2004 ÇÏÄÁ, ÎÏ ÒÁÎÅÅ ÜÔÁ ÏÓÏÂÅÎÎÏÓÔØ ÎÅ - ÂÙÌÁ ÄÏËÕÍÅÎÔÉÒÏ×ÁÎÁ). áÎÁÌÏÇÉÞÎÏ, × \textsf{mips-irix} ÔÒÅÂÕÀÔÓÑ - ÂÉÂÌÉÏÔÅËÉ \acro{MIPS}pro~7.4. - -\end{itemize} - -\subsubsection{2005} - -÷ 2005 ÇÏÄÕ ÂÙÌÏ, ËÁË ×ÓÅÇÄÁ, ÓÄÅÌÁÎÏ ÍÎÏÇÏ ÉÚÍÅÎÅÎÉÊ × ÐÁËÅÔÁÈ É -ÐÒÏÇÒÁÍÍÁÈ. éÎÆÒÁÓÔÒÕËÔÕÒÁ ÐÏÞÔÉ ÎÅ ÉÚÍÅÎÉÌÁÓØ ÐÏ ÓÒÁ×ÎÅÎÅÎÉÀ Ó 2004 -ÇÏÄÏÍ, ÎÏ ÎÅËÏÔÏÒÙÅ ÎÅÉÚÂÅÖÎÙÅ ÉÚÍÅÎÅÎÉÑ ÂÙÌÉ ÓÄÅÌÁÎÙ. - -\begin{itemize} - -\item âÙÌÉ ÄÏÂÁ×ÌÅÎÙ ÎÏ×ÙÅ ÓËÒÉÐÔÙ \cmdname{texconfig-sys}, - \cmdname{updmap-sys} É \cmdname{fmtutil-sys}, ËÏÔÏÒÙÅ ÉÚÍÅÎÑÀÔ - ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÆÁÊÌÙ × ÓÉÓÔÅÍÎÙÈ ÄÅÒÅ×ØÑÈ. óËÒÉÐÔÙ - \cmdname{texconfig}, \cmdname{updmap} É \cmdname{fmtutil} ÔÅÐÅÒØ - ÍÏÄÉÆÉÃÉÒÕÀÔ ÉÎÄÉ×ÉÄÕÁÌØÎÙÅ ÆÁÊÌÙ ÐÏÌØÚÏ×ÁÔÅÌÑ × - \dirname{$HOME/.texlive2005}. - -\item âÙÌÉ ÄÏÂÁ×ÌÅÎÙ ÎÏ×ÙÅ ÐÅÒÅÍÅÎÎÙÅ \envname{TEXMFCONFIG} É - \envname{TEXMFSYSCONFIG} ÄÌÑ ÕËÁÚÁÎÉÑ, ÇÄÅ ÎÁÈÏÄÑÔÓÑ - ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÆÁÊÌÙ (ÐÏÌØÚÏ×ÁÔÅÌØÓËÉÅ É ÓÉÓÔÅÍÎÙÅ). ôÁËÉÍ - ÏÂÒÁÚÏÍ, ×ÁÍ ÎÁÄÏ ÐÅÒÅÍÅÓÔÉÔØ ÔÕÄÁ ×ÁÛÉ ÌÉÞÎÙÅ ËÏÐÉÉ - \filename{fmtutil.cnf} É \filename{texmf.cnf}. ÷ ÌÀÂÏÍ ÓÌÕÞÁÅ - ÐÏÌÏÖÅÎÉÅ ÜÔÉÈ ÆÁÊÌÏ× É ÚÎÁÞÅÎÉÑ ÐÅÒÅÍÅÎÎÙÈ \envname{TEXMFCONFIG} É - \envname{TEXMFSYSCONFIG} ÄÏÌÖÎÙ ÂÙÔØ ÓÏÇÌÁÓÏ×ÁÎÙ. - óÍ. ÒÁÚÄÅÌ~\ref{sec:texmftrees}, \p.\pageref{sec:texmftrees}. - -\item ÷ ÐÒÏÛÌÏÍ ÇÏÄÕ ÍÙ ÏÓÔÁ×ÉÌÉ ÎÅÏÐÒÅÄÅÌ£ÎÎÙÍÉ \verb|\pdfoutput| É - ÄÒÕÇÉÅ ÐÅÒÅÍÅÎÎÙÅ ÐÒÉ ÇÅÎÅÒÉÒÏ×ÁÎÉÉ ÆÁÊÌÏ× × ÆÏÒÍÁÔÅ DVI, ÈÏÔÑ ÄÌÑ - ÜÔÏÇÏ ÉÓÐÏÌØÚÏ×ÁÌÁÓØ ÐÒÏÇÒÁÍÍÁ \cmdname{pdfetex}. ÷ ÜÔÏÍ ÇÏÄÕ, ËÁË - É ÂÙÌÏ ÏÂÅÝÁÎÏ, ÜÔÏ ÕÖÅ ÎÅ ÔÁË. ðÏÜÔÏÍÕ ÅÓÌÉ ×ÁÛ ÄÏËÕÍÅÎÔ - ÉÓÐÏÌØÚÕÅÔ ÄÌÑ ÐÒÏ×ÅÒËÉ ÆÏÒÍÁÔÁ \verb|\ifx\pdfoutput\undefined|, ÅÇÏ - ÎÁÄÏ ÉÚÍÅÎÉÔØ. ÷Ù ÍÏÖÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ ÐÁËÅÔ \pkgname{ifpdf.sty} - (ÒÁÂÏÔÁÅÔ × plain \TeX{} É \LaTeX) ÉÌÉ ÁÎÁÌÏÇÉÞÎÕÀ ÌÏÇÉËÕ. - -\item ÷ ÐÒÏÛÌÏÍ ÇÏÄÕ ÍÙ ÉÚÍÅÎÉÌÉ ÂÏÌØÛÉÎÓÔ×Ï ÆÏÒÍÁÔÏ×, ËÏÔÏÒÙÅ ÓÔÁÌÉ - ×ÙÄÁ×ÁÔØ 8-ÂÉÔÏ×ÙÅ ÓÉÍ×ÏÌÙ. åÓÌÉ ×ÁÍ ×Ó£ ÖÅ ÎÕÖÎÙ ÓÔÁÒÙÊ ×ÁÒÉÁÎÔ Ó - \verb|^^|, ÉÓÐÏÌØÚÕÊÔÅ ÎÏ×ÙÊ ÆÁÊÌ \filename{empty.tcx}: -\begin{verbatim} -latex --translate-file=empty.tcx yourfile.tex -\end{verbatim} - - -\item äÏÂÁ×ÌÅÎÁ ÎÏ×ÁÑ ÐÒÏÇÒÁÍÍÁ \cmdname{dvipdfmx} ÄÌÑ ÐÅÒÅ×ÏÄÁ ÉÚ DVI - × PDF; ÜÔÏ ÁËÔÉ×ÎÏ ÐÏÄÄÅÒÖÉ×ÁÅÍÁÑ ×ÅÒÓÉÑ ÐÒÏÇÒÁÍÍÙ - \cmdname{dvipdfm}, ËÏÔÏÒÁÑ ÐÏËÁ ÅÝ£ ×ËÌÀÞÅÎÁ × ÄÉÓÔÒÉÂÕÔÉ×, ÎÏ ÕÖÅ - ÎÅ ÒÅËÏÍÅÎÄÏ×ÁÎÁ. - -\item äÏÂÁ×ÌÅÎÙ ÎÏ×ÙÅ ÐÒÏÇÒÁÍÍÙ \cmdname{pdfopen} É - \cmdname{pdfclose}, ËÏÔÏÒÙÅ ÐÏÚ×ÏÌÑÀÔ ÐÅÒÅÇÒÕÚÉÔØ ÆÁÊÌ PDF × Adobe - Acrobat Reader, ÎÅ ÐÅÒÅÚÁÐÕÓËÁÑ ÐÒÏÇÒÁÍÍÕ (Õ ÄÒÕÇÉÈ ÐÒÏÇÒÁÍÍ ÄÌÑ - ÞÔÅÎÉÑ ÆÁÊÌÏ× PDF, ×ËÌÀÞÁÑ \cmdname{xpdf}, \cmdname{gv} É - \cmdname{gsview}, ÔÁËÏÊ ÐÒÏÂÌÅÍÙ ÎÉËÏÇÄÁ ÎÅ ÂÙÌÏ). - -\item äÌÑ ÅÄÉÎÏÏÂÒÁÚÉÑ ÍÙ ÐÅÒÅÉÍÅÎÏ×ÁÌÉ ÐÅÒÅÍÅÎÎÙÅ \envname{HOMETEXMF} - É \envname{VARTEXMF} × \envname{TEXMFHOME} É \envname{TEXMFSYSVAR}. - åÓÔØ ÔÁËÖÅ \envname{TEXMFVAR}, ÉÎÄÉ×ÉÄÕÁÌØÎÁÑ ÄÌÑ ËÁÖÄÏÇÏ - ÐÏÌØÚÏ×ÁÔÅÌÑ (ÓÍ. ÐÅÒ×ÙÊ ÐÕÎËÔ ×ÙÛÅ). -\end{itemize} - -\subsubsection{2006--2007} - -÷ 2006--2007 ÇÌÁ×ÎÙÍ ÎÏ×Ï××ÅÄÅÎÉÅÍ ÂÙÌÁ ÐÒÏÇÒÁÍÍÁ Xe\TeX{}, ×ÙÚÙ×ÁÅÍÁÑ -ËÁË \texttt{xetex} ÉÌÉ \texttt{xelatex}; -ÓÍ. \url{http://scripts.sil.org/xetex}. - -úÎÁÞÉÔÅÌØÎÏ ÏÂÎÏ×ÌÅÎÁ ÐÒÏÇÒÁÍÍÁ \MP; ÐÒÅÄÐÏÌÁÇÁÀÔÓÑ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ -ÏÂÎÏ×ÌÅÎÉÑ × ÂÕÄÕÝÅÍ (\url{http://tug.org/metapost/articles}). ôÁËÖÅ -ÏÂÎÏ×̣Πpdf\TeX{} (\url{http://tug.org/applications/pdftex}). - -æÏÒÍÁÔÙ \filename{.fmt} É Ô.Ä. ÔÅÐÅÒØ ÈÒÁÎÑÔÓÑ × ÐÏÄÄÉÒÅËÔÏÒÉÑÈ -\dirname{texmf/web2c}, Á ÎÅ × ÓÁÍÏÊ ÄÉÒÅËÔÏÒÉÉ (ÈÏÔÑ ÄÉÒÅËÔÏÒÉÑ ×Ó£ ÅÝ£ -×ËÌÀÞÅÎÁ × ÐÏÉÓË ÆÏÒÍÁÔÏ×, ÎÁ ÓÌÕÞÁÊ, ÅÓÌÉ ÔÁÍ ÎÁÈÏÄÑÔÓÑ ÓÔÁÒÙÅ -ÆÁÊÌÙ). ðÏÄÄÉÒÅËÔÏÒÉÉ ÎÁÚ×ÁÎÙ ÐÏ ÉÍÅÎÉ ÐÒÏÇÒÁÍÍÙ, ÎÁÐÒÉÍÅÒ, -\filename{tex}, \filename{pdftex}, \filename{xetex}. üÔÏ ÉÚÍÅÎÅÎÉÅ ÎÅ -ÄÏÌÖÎÏ ×ÌÉÑÔØ ÎÁ ÒÁÂÏÔÕ ÐÒÏÇÒÁÍÍ. - -ðÒÏÇÒÁÍÍÁ (plain) \texttt{tex} ÂÏÌØÛÅ ÎÅ ÏÐÒÅÄÅÌÑÅÔ ÐÏ \texttt{\%\&} × -ÐÅÒ×ÏÊ ÓÔÒÏËÅ, ËÁËÏÊ ÆÏÒÍÁÔ ÉÓÐÏÌØÚÏ×ÁÔØ: ÜÔÏ ×ÓÅÇÄÁ ëÎÕÔÏ×ÓËÉÊ -\TeX{} (\LaTeX{} É ÄÒÕÇÉÅ ÅÝ£ ÉÓÐÏÌØÚÕÀÔ \texttt{\%\&}). - -òÁÚÕÍÅÅÔÓÑ, × ÜÔÏÍ ÇÏÄÕ ÂÙÌÉ, ËÁË ÏÂÙÞÎÏ, ÓÏÔÎÉ ÏÂÎÏ×ÌÅÎÉÊ ÐÁËÅÔÏ× É -ÐÒÏÇÒÁÍÍ. ëÁË ÏÂÙÞÎÏ, ÏÂÎÏ×Ì£ÎÎÙÅ ×ÅÒÓÉÉ ÍÏÖÎÏ ÎÁÊÔÉ × ÓÅÔÉ \acro{CTAN} -(\url{http://www.ctan.org}). - -äÅÒÅ×Ï \TL{} ÔÅÐÅÒØ ÈÒÁÎÉÔÓÑ × ÓÉÓÔÅÍÅ Subversion, É Õ ÎÁÓ ÐÏÑ×ÉÌÓÑ -WWW-ÉÎÔÅÒÆÅÊÓ ÄÌÑ ÅÇÏ ÐÒÏÓÍÏÔÒÁ. íÙ ÐÒÅÄÐÏÌÁÇÁÅÍ, ÞÔÏ ÜÔÁ ÓÉÓÔÅÍÁ -ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÎÁ ÄÌÑ ÒÁÚÒÁÂÏÔËÉ × ÂÌÉÖÁÊÛÅÍ ÂÕÄÕÝÅÍ. - -îÁËÏÎÅÃ, × ÍÁÅ 2006 ÇÏÄÁ ôÏÍÁÓ üÓÓÅÒ ÏÂßÑ×ÉÌ Ï ÐÒÅËÒÁÝÅÎÉÉ ÒÁÂÏÔÙ ÎÁÄ -te\TeX ÏÍ (\url{http://tug.org/tetex}). üÔÏ ×ÙÚ×ÁÌÏ ×ÓÐÌÅÓË ÉÎÔÅÒÅÓÁ -Ë \TL, ÏÓÏÂÅÎÎÏ ÓÒÅÄÉ ÒÁÚÒÁÂÏÔÞÉËÏ× ÓÉÓÔÅÍ \acro{GNU}/ìÉÎÕËÓÁ (ÍÙ -ÄÏÂÁ×ÉÌÉ ÓÈÅÍÕ \texttt{tetex}, ËÏÔÏÒÁÑ ÕÓÔÁÎÁ×ÌÉ×ÁÅÔ ÓÉÓÔÅÍÕ, ÐÒÉÍÅÒÎÏ -ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÕÀ te\TeX Õ). íÙ ÎÁÄÅÅÍÓÑ, ÞÔÏ ÜÔÏ ÐÒÉ×ÅÄ£Ô × ËÏÎÅÞÎÏÍ -ÉÔÏÇÅ Ë ÕÌÕÞÛÅÎÉÀ ÒÁÂÏÔÙ × \TeX Å ÄÌÑ ×ÓÅÈ. - -\medskip \noindent -ðÏÓÌÅÄÎÅÅ ÚÁÍÅÞÁÎÉÅ Ï ÐÒÏÛÌÏÍ: ×ÓÅ ×ÙÐÕÓËÉ \TL{} ×ÍÅÓÔÅ Ó -ÄÏÐÏÌÎÉÔÅÌØÎÙÍÉ ÍÁÔÅÒÉÁÌÁÍÉ ×ÒÏÄÅ ÏÂÌÏÖÅË \CD{} ÈÒÁÎÑÔÓÑ ÎÁ -\url{ftp://tug.org/historic/systems/texlive}. -\url{ftp://tug.org/historic/systems/texlive}. - -\subsection{îÁÓÔÏÑÝÅÅ} -\label{sec:tlcurrent} - - -÷ 2008 ÂÙÌÁ ÚÁÎÏ×Ï ÒÁÚÒÁÂÏÔÁÎÁ É ÐÅÒÅÐÉÓÁÎÁ ×ÓÑ ÓÔÒÕËÔÕÒÁ -\TL{}. ðÏÌÎÁÑ ÉÎÆÏÒÍÁÃÉÑ Ï ÕÓÔÁÎÏ×ËÅ ÓÉÓÔÅÍÙ ÔÅÐÅÒØ ÈÒÁÎÉÔÓÑ × -ÔÅËÓÔÏ×ÏÍ ÆÁÊÌÅ \filename{tlpkg/texlive.tlpdb}. - -ðÏÍÉÍÏ ÐÒÏÞÅÇÏ, ÜÔÏ ÎÁËÏÎÅà ÐÏÚ×ÏÌÉÌÏ ÏÂÎÏ×ÌÅÎÉÅ \TL{} ÐÏ ÓÅÔÉ "--- -×ÏÚÍÏÖÎÏÓÔØ, ËÏÔÏÒÁÑ ÍÎÏÇÏ ÌÅÔ ÂÙÌÁ Õ ÐÒÏÇÒÁÍÍÙ MiK\TeX{}. íÙ -ÐÒÅÄÐÏÌÁÇÁÅÍ ÒÅÇÕÌÑÒÎÏ ÏÂÎÏ×ÌÑÔØ ÐÁËÅÔÙ, ÐÏÓÔÕÐÁÀÝÉÅ ÎÁ \CTAN. - -÷ËÌÀÞÅÎ ÎÏ×ÙÊ ×ÁÖÎÙÊ <<Ä×ÉÖÏË>> Lua\TeX\ (\url{http://luatex.org}); -ÐÏÍÉÍÏ ÎÏ×ÏÇÏ ÕÒÏ×ÎÑ ×ÅÒÓÔËÉ, ÜÔÏ ÄÁÅÔ ÐÒÅËÒÁÓÎÙÊ ÓËÒÉÐÔÏ×ÙÊ ÑÚÙË ÄÌÑ -ÉÓÐÏÌØÚÏ×ÁÎÉÑ ËÁË ÉÚÎÕÔÒÉ ÄÏËÕÍÅÎÔÏ× \TeX Á, ÔÁË É ÏÔÄÅÌØÎÏ. - -ðÏÄÄÅÒÖËÁ ÍÎÏÇÉÈ ÐÌÁÔÆÏÒÍ ÎÁ ÏÓÎÏ×Å àÎÉËÓÁ É Windows ÔÅÐÅÒØ ÇÏÒÁÚÄÏ -ÂÏÌÅÅ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÁ. ÷ ÞÁÓÔÎÏÓÔÉ, ÂÏÌØÛÉÎÓÔ×Ï ÓËÒÉÐÔÏ× ÎÁ ÑÚÙËÁÈ -Perl É Lua ÔÅÐÅÒØ ÄÏÓÔÕÐÎÙ ÐÏÄ Windows ÂÌÁÇÏÄÁÒÑ ×ÅÒÓÉÉ PerlÁ, -ÒÁÓÐÒÏÓÔÒÁÎÑÅÍÏÊ Ó \TL{}. - -îÏ×ÙÊ ÓËÒÉÐÔ \cmdname{tlmgr} (ÓÍ. ÒÁÚÄÅÌ~\ref{sec:tlmgr}) ÔÅÐÅÒØ -Ñ×ÌÑÅÔÓÑ ÏÓÎÏ×ÎÙÍ ÉÎÔÅÒÆÅÊÓÏÍ ÄÌÑ ÁÄÍÉÎÉÓÔÒÉÒÏ×ÁÎÉÑ \TL{} ÐÏÓÌÅ -ÕÓÔÁÎÏ×ËÉ. ïÎ ÏÓÕÝÅÓÔ×ÌÑÅÔ ÏÂÎÏ×ÌÅÎÉÅ ÐÁËÅÔÏ× É ÐÅÒÅÇÅÎÅÒÉÒÏ×ÁÎÉÅ -ÆÏÒÍÁÔÏ×, ËÁÒÔ ÛÒÉÆÔÏ× É ÑÚÙËÏ×, ×ËÌÀÞÁÑ ÌÏËÁÌØÎÙÅ ÄÏÂÁ×ÌÅÎÉÑ. - -÷ Ó×ÑÚÉ Ó ÐÏÑ×ÌÅÎÉÅÍ ÐÒÏÇÒÁÍÍÙ \cmdname{tlmgr}, ×ÏÚÍÏÖÎÏÓÔÉ ÐÒÏÇÒÁÍÍÙ -\cmdname{texconfig} ÐÏ ÒÅÄÁËÔÉÒÏ×ÁÎÉÀ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÈ ÆÁÊÌÏ× ÆÏÒÍÁÔÏ× -É ÔÁÂÌÉà ÐÅÒÅÎÏÓÁ ÏÔËÌÀÞÅÎÙ. - -ðÒÏÇÒÁÍÍÁ \cmdname{xindy} (\url{http://xindy.sourceforge.net/}) ÄÌÑ -ÓÏÚÄÁÎÉÑ ÕËÁÚÁÔÅÌÅÊ ÔÅÐÅÒØ ÒÁÂÏÔÁÅÔ ÎÁ ÂÏÌØÛÉÎÓÔ×Å ÐÌÁÔÆÏÒÍ. - -ðÒÏÇÒÁÍÍÁ \cmdname{kpsewhich} ÔÅÐÅÒØ ÍÏÖÅÔ ÓÏÏÂÝÉÔØ ÏÂÏ ×ÓÅÈ ÎÕÖÎÙÈ -ÆÁÊÌÁÈ (ÏÐÃÉÑ \optname{--all}) É ÏÇÒÁÎÉÞÉÔØ ÐÏÉÓË ÏÐÒÅÄÅÌÅÎÎÏÊ -ÐÏÄÄÉÒÅËÔÏÒÉÅÊ (ÏÐÃÉÑ \optname{--subdir}). - -ðÒÏÇÒÁÍÍÁ \cmdname{dvipdfmx} ÔÅÐÅÒØ ÍÏÖÅÔ ÉÚ×ÌÅËÁÔØ ÉÎÆÏÒÍÁÃÉÀ Ï -ÒÁÍËÅ, ÅÓÌÉ ×ÙÚ×ÁÎÁ ËÁË \cmdname{extractbb}; ÜÔÏ ÏÄÎÁ ÉÚ ÐÏÓÌÅÄÎÉÈ -×ÏÚÍÏÖÎÏÓÔÅÊ ÐÒÏÇÒÁÍÍÙ \cmdname{dvipdfm}, ËÏÔÏÒÏÊ ÎÅ ÂÙÌÏ Õ -\cmdname{dvipdfmx}. - -áÌÉÁÓÙ \filename{Times-Roman}, \filename{Helvetica} É Ô.Ä. ÕÂÒÁÎÙ. -òÁÚÎÙÅ ÐÁËÅÔÙ ÏÖÉÄÁÀÔ ÏÔ ÎÉÈ ÒÁÚÎÏÇÏ ÐÏ×ÅÄÅÎÉÑ (ÏÓÏÂÅÎÎÏ ÐÒÉ ÒÁÚÎÙÈ -ËÏÄÉÒÏ×ËÁÈ), É ÍÙ ÎÅ ÎÁÛÌÉ ÓÐÏÓÏÂÁ ÒÅÛÉÔØ ÜÔÕ ÐÒÏÂÌÅÍÕ ÅÄÉÎÏÏÂÒÁÚÎÏ. - -æÏÒÍÁÔ \pkgname{platex} ÕÂÒÁÎ ÉÚ-ÚÁ ËÏÎÆÌÉËÔÁ Ó ÑÐÏÎÓËÉÍ ÐÁËÅÔÏÍ -\pkgname{platex}; ÔÅÐÅÒØ ÏÓÎÏ×ÎÁÑ ÐÏÄÄÅÒÖËÁ ÐÏÌØÓËÏÇÏ ÑÚÙËÁ -ÏÓÕÝÅÓÔ×ÌÑÅÔÓÑ ÞÅÒÅÚ ÐÁËÅÔ \pkgname{polski}. - -ðÕÌÙ ÓÔÒÏËÏ×ÙÈ ËÏÎÓÔÁÎÔ \web\ ÔÅÐÅÒØ ËÏÍÐÉÌÉÒÕÀÔÓÑ × ÓÁÍÉ ÐÒÏÇÒÁÍÍÙ -ÄÌÑ ÕÄÏÂÓÔ×Á ÏÂÎÏ×ÌÅÎÉÊ. - -îÁËÏÎÅÃ, ÄÏÂÁ×ÌÅÎÙ ÉÚÍÅÎÅÎÉÑ, ÓÄÅÌÁÎÎÙÅ äÏÎÁÌØÄÏÍ ëÎÕÔÏÍ × ÅÇÏ -<<îÁÓÔÒÏÊËÅ \TeX Á 2008 ÇÏÄÁ>>, ÓÍ. -\url{http://tug.org/TUGboat/Articles/tb29-2/tb92knut.pdf}. - -\subsection{âÕÄÕÝÅÅ} - -\emph{\TL{} ÎÅ ÓÏ×ÅÒÛÅÎÅÎ!} (é ÎÉËÏÇÄÁ ÎÅ ÂÕÄÅÔ.) íÙ ÐÒÅÄÐÏÌÁÇÁÅÍ -×ÙÐÕÓËÁÔØ ÎÏ×ÙÅ ×ÅÒÓÉÉ, ÄÏÂÁ×ÌÑÑ ÓÐÒÁ×ÏÞÎÙÊ ÍÁÔÅÒÉÁÌ, -ÕÔÉÌÉÔÙ, ÕÓÔÁÎÏ×ÏÞÎÙÅ ÐÒÏÇÒÁÍÍÙ É (ËÏÎÅÞÎÏ) ÎÏ×ÏÅ, ÕÌÕÞÛÅÎÎÏÅ É -ÐÒÏ×ÅÒÅÎÎÏÅ ÄÅÒÅ×Ï ÍÁËÒÏÓÏ× É ÛÒÉÆÔÏ×. üÔÁ ÒÁÂÏÔÁ ÄÅÌÁÅÔÓÑ ÏÞÅÎØ -ÚÁÎÑÔÙÍÉ ÄÏÂÒÏ×ÏÌØÃÁÍÉ × Ó×ÏÂÏÄÎÏÅ ×ÒÅÍÑ, É ÍÎÏÇÏÅ ÏÓÔÁÅÔÓÑ ÓÄÅÌÁÔØ. -åÓÌÉ ×Ù ÍÏÖÅÔÅ ÐÏÍÏÞØ, ÎÅ -ÓÔÅÓÎÑÊÔÅÓØ. óÍ. \url{http://tug.org/texlive/contribute.html}. - -ðÒÉÓÙÌÁÊÔÅ, ÐÏÖÁÌÕÊÓÔÁ, ÚÁÍÅÞÁÎÉÑ É ÐÒÅÄÌÏÖÅÎÉÑ ÐÏ ÁÄÒÅÓÕ:\hfill\null -\begin{quote} -\email{tex-live@tug.org} \\ -\url{http://tug.org/texlive} -\end{quote} - -\medskip -\noindent \textsl{Happy \TeX ing!} - -\end{document} - -%%% Local Variables: -%%% mode: latex -%%% TeX-master: t -%%% LaTeX-command-style: (("." "pdflatex")) -%%% TeX-view-style: (("." "acroread %s.pdf")) -%%% End: diff --git a/Master/texmf-doc/source/texlive/texlive-zh-cn/Makefile b/Master/texmf-doc/source/texlive/texlive-zh-cn/Makefile deleted file mode 100644 index 6541a022547..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-zh-cn/Makefile +++ /dev/null @@ -1,47 +0,0 @@ -# $Id:$ -# Makefile for TeX Live documentation. Public domain. -TEX = xelatex -doc = texlive-zh-cn -source = $(doc).tex -pdf = $(doc).pdf -lang = chinese - -all: $(pdf) - -env = TEXINPUTS=../texlive-common:../texlive-zh-cn:; export TEXINPUTS; - -$(pdf): $(source) - $(env) $(TEX) $< - $(env) $(TEX) $< - -clean: - rm -f *.aux *.log *.blg *.toc *.out *.lot tex4ht.ps *.4* - rm -f *.xref* *.lg *.idv *.out *.otc *.tmp tmp.* - rm -f $(doc).dvi $(doc).ps - -realclean: clean - rm -f $(doc).pdf - rm -f *.html *.htm $(doc).css *.gif *.jpg - - -insttop = ../../../doc -instfiles = $(doc)*html $(doc).css $(doc).pdf -copyfiles = *.png -install: -# lang=`dirname \`pwd\` | sed 's,.*/,,'`; - lang=$(lang); \ - tldir=`pwd | sed 's,.*/,,'`; \ - instdir=$(insttop)/$$lang/$$tldir; \ - echo tldoc install to $$instdir; \ - for f in $(instfiles); do \ - cmp -s $$f $$instdir/$$f && rm -v $$f && continue; \ - mv -v $$f $$instdir/$$f; \ - done; \ - lang=$(lang); \ - tldir=`pwd | sed 's,.*/,,'`; \ - instdir=$(insttop)/$$lang/$$tldir; \ - for f in $(copyfiles); do \ - cmp -s $$f $$instdir/$$f && continue; \ - cp -v $$f $$instdir/$$f; \ - done; echo "$$instdir" - diff --git a/Master/texmf-doc/source/texlive/texlive-zh-cn/README-live.ZH-CN b/Master/texmf-doc/source/texlive/texlive-zh-cn/README-live.ZH-CN deleted file mode 100644 index a308e7daaa1..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-zh-cn/README-live.ZH-CN +++ /dev/null @@ -1,34 +0,0 @@ -TeX Live Guide Translation (Simplified Chinese) -=============================================== - -To compile live.tex, you need: - -1. Xe(La)TeX (and related packages like fontspec) -0.997+ (a recent version is bundled with TeX Live). - -2. xeCJK macro package. - -3. At least one CJK font (with Simpified Chinese -glyphs), preferably two, one for normal text, -another for emphasized text. To change the font, -open tex-live.sty (line 23 - 25): - - \setCJKmainfont[BoldFont=Adobe Heiti Std]{Adobe Song Std} - \setCJKmonofont[Scale=0.9]{Adobe Kaiti Std} - \setCJKfamilyfont{song}[BoldFont=Adobe Heiti Std]{Adobe Song Std} - -Replace "Adobe Heiti Std" and "Adobe Song Std" to -some OpenType/TrueType fonts you already installed. - -4. Type make or simply - - xelatex texlive-zh-cn.tex - -for several times to make sure cross-references are -correctly generated. - -5. If you have any problems, please contact: - gzjjgod at gmail dot com - -jjgod, 2007/01/03. - diff --git a/Master/texmf-doc/source/texlive/texlive-zh-cn/tex-live.sty b/Master/texmf-doc/source/texlive/texlive-zh-cn/tex-live.sty deleted file mode 100644 index 2289ab97ace..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-zh-cn/tex-live.sty +++ /dev/null @@ -1,464 +0,0 @@ -% $Id: tex-live.sty 9758 2008-07-25 00:47:03Z karl $ -% TeX Live documentation style. Written by many people over many years. -% Public domain. -% -\NeedsTeXFormat{LaTeX2e}[1995/12/01] -\ProvidesPackage{tex-live}[2005/09/24 v1.5 TeX Live documentation style] -% -\RequirePackage{alltt} -\RequirePackage{array} -\RequirePackage{colortbl} -\RequirePackage{comment} -\RequirePackage{float} -\RequirePackage{graphicx} -\RequirePackage{longtable} -\RequirePackage{shortvrb} -\RequirePackage[normalem]{ulem} -\RequirePackage[obeyspaces]{url} -\RequirePackage{xspace} - -% Chinese support (with XeTeX 0.997+) -\RequirePackage{xeCJK} -\def\Status{1} -\parindent=20pt -\defaultfontfeatures{Mapping=tex-text} -\setCJKmainfont[BoldFont=Adobe Heiti Std]{Adobe Song Std} -\setCJKmonofont[Scale=0.9]{Adobe Kaiti Std} -\setCJKfamilyfont{song}[BoldFont=Adobe Heiti Std]{Adobe Song Std} - -\renewcommand\contentsname{目录} -\renewcommand\listfigurename{æ’图列表} -\renewcommand\listtablename{表格列表} -\renewcommand\refname{å‚考文献} -\renewcommand\indexname{索引} -\renewcommand\figurename{图} -\renewcommand\tablename{表} -\renewcommand\partname{部分} -\renewcommand\appendixname{附录} -\renewcommand\abstractname{摘è¦} -\setlength{\parskip}{5pt} - -% -%\RequirePackage{lmodern} -%\usepackage{textcomp}% including \textbullet -\def\p.{p.\,} - -% for a proper \acro command. -\RequirePackage{relsize} -%\DeclareRobustCommand{\acro}[1]{\textscale{.9}{#1}\@} -\def\acro#1{\textscale{.9}{#1}\@} -% -\RequirePackage{fancyvrb} -\DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=\normalsize} -\DefineVerbatimEnvironment{fverbatim}{Verbatim}{fontsize=\footnotesize} -\DefineVerbatimEnvironment{sverbatim}{Verbatim}{fontsize=\small} -\DefineVerbatimEnvironment{boxedverbatim} - {Verbatim}{fontsize=\scriptsize,frame=single} -\DefineVerbatimEnvironment{Verbatim}{Verbatim}{fontsize=\normalsize} -\def\verbatiminput#1{\VerbatimInput[fontsize=\scriptsize]{#1}} -\def\boxedverbatiminput#1{\VerbatimInput[frame=single,fontsize=\scriptsize]{#1}} -\def\listinginput#1#2{\VerbatimInput[fontsize=\scriptsize,firstnumber=#1,numbers=left]{#2}} -\MakeShortVerb\| -% -% -% Done with packages. -% -% Page layout. -\advance\textwidth by 1.1in -\advance\oddsidemargin by -.55in -\advance\evensidemargin by -.55in -% -\advance\textheight by 1in -\advance\topmargin by -.5in -\advance\footskip by -.5in -\pagestyle{headings} -% -% LaTeX parameters. -\renewcommand{\topfraction}{0.85} -\renewcommand{\floatpagefraction}{0.86} -\renewcommand{\textfraction}{0.1} -\renewcommand{\abovecaptionskip}{4pt} -\renewcommand{\belowcaptionskip}{4pt} -\setcounter{tocdepth}{3} -\setcounter{secnumdepth}{3} -\setcounter{topnumber}{5} -\setcounter{totalnumber}{5} -% -% linebreaking, etc. -\hbadness=4000 -\vbadness=4000 -\emergencystretch=.1\hsize -\relpenalty=500 -% -\def\slash{/\penalty\z@\hskip\z@skip } -% -% various sorts of names -\newcommand*{\pkgname}[1]{\textsf{#1}}% package name -\newcommand*{\optname}[1]{\texttt{#1}}% (package,class) option name -\newcommand*{\cmdname}[1]{\textsf{#1}}% command name -\newcommand*{\colname}[1]{\emph{#1}}% collection name -\newcommand*{\dirname}[1]{\path{#1}}% directory name -\newcommand*{\filename}[1]{\path{#1}}% file name -\newcommand*{\envname}[1]{\texttt{#1}}% environment variable name -\newcommand{\code}[1]{\texttt{#1}} -\newcommand{\file}[1]{\texttt{#1}} -\newcommand{\prog}[1]{\textsf{#1}}% same as \cmdname -\newcommand{\samp}[1]{`\texttt{#1}'} -\newcommand{\var}[1]{{\sl #1}}% not \textsl, for roman not typewriter slanted. -\newcommand{\ttvar}[1]{\texttt{\var{#1}}} -% -% underlined command input. -%\def\Ucom#1{% -% \uline{\rule[-.2\baselineskip]{0pt}{.9\baselineskip}\ttfamily #1}} -% bold command input -\def\Ucom#1{{\bfseries\ttfamily #1}} -% -% \CDref is for url's with a #, where we need to write the target url and -% displayed url separately in the input, due to catcode madness. -% (We could simplify/remove this next time, I think.) -% \def\CDref#1#2{\texttt{#1}} -% -% \OnCD is currently for any other reference to a file or directory in -% the distribution. PDF readers only open .pdf files, though, so we -% should change this to only use \href for those. Or more likely use -% different macros in the source. -% \def\OnCD#1{\href{../../../../#1}{\path{#1}}} -% -% \href incorrectly appends .pdf to anything without an extension; these -% definitions using \hyper@linkurl do not, but they fail for .pdf -% references -- which are the only ones that work anyway. So this is -% useless, in practice. -\def\CDref#1#2{\hyper@linkurl{#2}{../../../../#1}} -\def\OnCD#1{\hyper@linkurl{\path{#1}}{../../../../#1}} - -% GUI menu/button/tab sequence: -\def\guiseq#1{\textsf{#1}} -\def\arw{\unskip$\rightarrow$\ignorespaces} -% -% Special names. -\def\dpi{$\,$dpi\xspace} -\def\bs{{\protect\normalfont\ttfamily\char'134}} -\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} -\def\Q#1{\par\vskip6pt\leftline{#1}\par} -\def\hyph{-} -% -% many abbreviations. -\newcommand{\CS}{$\mathcal{C}\kern-.1667em\lower.5ex% - \hbox{$\mathcal{S}$}\kern-.075em $} -\def\AFMtoTFM{\cmdname{AFM2TFM}\null} -\def\bv{\emph{Baskerville}} -\let\BV=\bv -\def\Dash{\unskip\nobreak\thinspace---\thinspace\ignorespaces} -\def\dvicopy{\cmdname{dvicopy}} -\def\dvidvi{\cmdname{dvidvi}} -\def\dvips{\cmdname{dvips}} -\def\eTeX{$\varepsilon$-\TeX} -\def\fpTeX{\textrm{fp}\TeX\xspace} -\def\GFtoDVI{\cmdname{GFtoDVI}\null} -\def\GFtoPK{\cmdname{GFtoPK}\null} -\def\GFtype{\cmdname{GFtype}} -\def\GUI{\acro{GUI}\xspace} -\def\KPS{Kpathsea} -\def\La{La} -\def\OMEGA{$\Omega$} -\def\OzMF{OzMF} -\def\OzMP{OzMP} -\def\OzTeX{O\kern-.03em z\kern-.15em\TeX} -\def\PKtype{\cmdname{PKtype}} -\def\PLtoTF{\cmdname{PLtoTF}\null} -\def\ProTeXt{Pro\TeX t} -\def\teTeX{\textrm{te}\TeX\xspace} -\def\TeXLive{\TeX{} Live\xspace} -\def\TFtoPL{\cmdname{TFtoPL}\null} -\def\TK{\TeX\ Collection} -\let\TL=\TeXLive -\def\TypeI{Type~1} -\def\VFtoVP{\cmdname{VFtoVP}\null} -\def\VPtoVF{\cmdname{VPtoVF}\null} -\def\Thanh{H\`an~Th\^e\llap{\raise 0.5ex\hbox{\'{}}}~Th\`anh} -\def\XEmTeX{\textrm{XEm}\TeX\xspace} -\def\XEmacs{\textrm{XEmacs}\xspace} -\def\XeTeX{Xe\TeX\xspace} -\def\Webc{Web2C} -\providecommand*{\CD}{\acro{CD}\xspace} -\providecommand*{\CTAN}{\acro{CTAN}\xspace} -\providecommand*{\DVD}{\acro{DVD}\xspace} -\providecommand*{\GNU}{\acro{GNU}\xspace} -\providecommand*{\ISO}{\acro{ISO}\xspace} -\providecommand*{\HTML}{\acro{HTML}\xspace} -\providecommand*{\MacOSX}{Mac\,\acro{OS\,X}\xspace} -\providecommand*{\PS}{Post\-Script\xspace} -\providecommand*{\TDS}{\acro{TDS}\xspace} -\providecommand*{\dvi}{\acro{DVI}\xspace} -\providecommand*{\web}{\texttt{WEB}\xspace} - -% Include an image. -% #1 - name of image (pictures/#1.jpg, always .jpg please) -% #2 - bb for html -% #3 - width for TeX -% -\def\tlimage#1#2#3{% - \ifnum \Status=2 % html, want relative path in output - \includegraphics[#2]{../../general/texlive-common/pictures/#1.jpg} - \else % not html, handled by TEXINPUTS in Makefile - \includegraphics[width=#3]{pictures/#1.jpg} - \fi - \\[5mm] -} - -\def\tlpng#1#2{% - \ifnum \Status=2 % html, want relative path in output - \includegraphics[bb=0 0 1 1]{#1.png}% - \else % not html, handled by TEXINPUTS in Makefile - \includegraphics[width=#2]{#1.png}% - \fi -} -% -% description-like environment that uses tt instead of bf, and doesn't -% go to the left margin. Without the \hfil, get an underfull box. -% Don't know why \descriptionlabel doesn't. -% -\newenvironment{ttdescription} - {\begin{list}{label must be supplied}{% - \itemsep=0pt % these lists tend to have short descriptions - \parindent=0pt - \let\makelabel=\ttdescriptionlabel}}% - {\end{list}} -\newcommand*\ttdescriptionlabel[1]{\hspace\labelsep - \normalfont\ttfamily #1\hfil} -% -% Likewise, for commands using sans serif. -\newenvironment{cmddescription} - {\begin{list}{label must be supplied}{% - \itemsep=0pt - \let\makelabel=\cmddescriptionlabel}}% - {\end{list}} -\newcommand*\cmddescriptionlabel[1]{\hspace\labelsep - \normalfont\sffamily #1\hfil} - -% General squeezed itemize. -\newenvironment{itemize*}% - {\begin{itemize}% - \setlength{\itemsep}{0pt}% - \setlength{\parskip}{0pt}}% - {\end{itemize}} - -\newsavebox{\wbox} -\newenvironment{warningbox} - {\begin{lrbox}{\wbox} - \begin{minipage}{.95\textwidth}} - {\end{minipage}\end{lrbox}\fbox{\usebox{\wbox}}} -% -% lrbox is used as a representation marking. I changed it to -% lrBox in tne source file, to get closer to logical marking -\newsavebox{\mylrbox} -\newenvironment{lrBox} - {\begin{lrbox}{\mylrbox}} - {\end{lrbox}} - - -% emacs-page output setup -% -\ifx \HCode\UnDef - \providecommand{\Status}{0}% running TeX -\else - \providecommand{\Status}{2}% running TeX4ht -\fi -%\typeout{Status is \Status} -% -\newif\ifSingleColumn -% -% By default, we won't be creating hyperlinks. -\def\href#1#2{#2} -\def\hypertarget#1#2{} -\def\email#1{\href{mailto:#1}{\path{#1}}} % \path comes from url -% -\definecolor{hypercolor}{rgb}{0.5,0.0,0.5} % purplish external links. -% -% -\ifcase\Status - % \Status = 0 - \typeout{TeX Live documentation in DVI format} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - \or - % \Status = 1 - \typeout{TeX Live documentation in PDF format} - \RequirePackage[breaklinks, - colorlinks,linkcolor=hypercolor,citecolor=hypercolor, - urlcolor=hypercolor,filecolor=hypercolor, - bookmarksopen, - %pdfstartview={FitBH -320000}, % fails with acrobat7 - hyperindex] - {hyperref} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - \or - % \Status = 2 - \typeout{TeX Live documentation in HTML format} - \SingleColumntrue - \newenvironment{multicols}[1]{}{} - % read our config file, live4ht.cfg; q.v., for more definitions. - % hyperref load must come after the tex4ht load. - \RequirePackage[live4ht]{tex4ht} - \RequirePackage[tex4ht]{hyperref} \hyperlinkfileprefix{} - % definitions need simplifying for TeX4ht to make relative paths work. - \def\CDref#1#2{\href{../../../../#1}{#2}} - \def\OnCD#1{\href{../../../../#1}{#1}} - \or - % \Status = 3 - \typeout{TeX Live documentation as a Baskerville issue} - \@ifundefined{Fonts}% - {\RequirePackage{ae}}% - {\RequirePackage[T1]{\Fonts}} - \RequirePackage{bvoutln}% outline of baskerville - \SingleColumnfalse - \RequirePackage{multicol} - \or - % \Status = 4 - \typeout{TeX Live documentation as a TUB article} - \@ifundefined{Fonts}% - {\RequirePackage{ae}}% - {\RequirePackage[T1]{\Fonts}} - \SingleColumnfalse - \newenvironment{multicols}[1]{}{} -\fi -% -\ifnum \Status=4 -\else - \RequirePackage{texnames} - \providecommand\TeXXeT{\TeX-{}-% - \kern-.1emX\kern-.125em\lower.5ex\hbox{E}\kern-.1667emT\@} - \def\MP{MetaPost} - \let\mf\MF - \newcommand\ConTeXt{C\kern-.0333emon\-\kern-.0667em\TeX\kern-.0333emt} - \newcommand\MIKTEX{MiK\kern-.025em \TeX}% per www.miktex.org - % from pictex.tex: - \ifx\PiC\undefined \def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC} \fi - \ifx\PiCTeX\undefined \def\PiCTeX{\PiC\kern-.11em\TeX} \fi -\fi -% -% hacking at sections etc., to pay attention to baskerville status -\newcommand{\@condend@multicols}{% - \ifSingleColumn - \else - \def\@tempa{multicols}% - \ifx\@tempa\@currenvir - \end{multicols}% - \fi - \fi -} -\let\Section\section -\renewcommand{\section}{% - \@ifstar - {\Section*}% - {% - \@condend@multicols - \@dblarg\@full@section - }% -} -\def\@full@section[#1]#2{% - \Section[#1]{#2}% - \ifSingleColumn\else\begin{multicols}{2}\fi -} -\let\SubSection\subsection -\renewcommand{\subsection}{% - \@ifstar{\SubSection*}% - {% - \@condend@multicols - \@dblarg\@full@subsection - } -} -\def\@full@subsection[#1]#2{% - \SubSection[#1]{#2}% - \ifSingleColumn\else\begin{multicols}{2}\fi -} - -% calm things down a bit if we're in a multiple-column version -\ifSingleColumn -\else - \def\@listI{\leftmargin\leftmargini - \parsep \z@ - \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ - \itemsep \z@ \@plus .1\p@ - } - \let\@listi\@listI - \@listi - \def\@listii{\leftmargin\leftmarginii - \labelwidth\leftmarginii\advance\labelwidth-\labelsep - \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ - \parsep \z@ - \itemsep \z@ \@plus .1\p@ - } - \def\@listiii{\leftmargin\leftmarginiii - \labelwidth\leftmarginiii\advance\labelwidth-\labelsep - \topsep 1\p@ \@plus 1\p@ \@minus 1\p@ - \parsep \z@ - \partopsep \z@ - \itemsep \topsep - } - \def\@listiv{\leftmargin\leftmarginiv - \labelwidth\leftmarginiv\advance\labelwidth-\labelsep - } - \def\@listv{\leftmargin\leftmarginv - \labelwidth\leftmarginv\advance\labelwidth-\labelsep - } - \def\@listvi{\leftmargin\leftmarginvi - \labelwidth\leftmarginvi\advance\labelwidth-\labelsep - } -\fi -% -% array package stuff -\def\arraybackslash{\let\\=\@arraycr} -\newcolumntype{P}[1]{>{\raggedright\arraybackslash}p{#1}} -% -% shaded rows (using facilities of colortbl) -% -\definecolor{pale}{gray}{.9} -\newcount\colrow -\gdef\RowColor{pale} -\def\SetRowColor{% - \rowcolor{\RowColor}% - \global\advance\colrow by1\relax - \ifodd\colrow - \gdef\RowColor{pale}% - \else - \gdef\RowColor{white}% - \fi -} -% redefine to hack up a reference even though we don't need it... -\renewcommand\@bibitem[1]{\if@filesw \immediate\write\@auxout - {\string\bibcite{#1}{?}}\fi\ignorespaces} -% -% \unknownTeXlive is a dummy texlive entry for the biblio -\newcommand\unknownTeXlive[2][\relax]{\textbf{\textsc{unknown}}% - \global\@all@unknown\expandafter{\the\@all@unknown{#2}}% -} -\newtoks\@all@unknown -\global\@all@unknown{} -\AtEndDocument{\@message@unknowns} -\def\@message@unknowns{\edef\@tempa{\the\@all@unknown}% - \ifx\@tempa\@empty - \else - \def\@tempa{*** TeX live package location of }% - \expandafter\@output@unknowns\the\@all@unknown\@empty - \fi -} -\def\@output@unknowns#1{\edef\@tempb{#1}% - \ifx\@tempb\@empty - \typeout{ unknown}% - \else - \message{\@tempa#1,}% - \def\@tempa{}% - \expandafter\@output@unknowns - \fi -} - - -% Silence font warnings about no bold typewriter in LM. -\def\@font@warning#1{}% - -% Silence hyperref warnings about \kern. -\def\HyPsd@Warning#1{}% - -\endinput diff --git a/Master/texmf-doc/source/texlive/texlive-zh-cn/texlive-zh-cn.tex b/Master/texmf-doc/source/texlive/texlive-zh-cn/texlive-zh-cn.tex deleted file mode 100644 index c444dca64c2..00000000000 --- a/Master/texmf-doc/source/texlive/texlive-zh-cn/texlive-zh-cn.tex +++ /dev/null @@ -1,2576 +0,0 @@ -% $Id$ -% TeX Live documentation. Originally written by Sebastian Rahtz and -% Michel Goossens, now maintained by Karl Berry and others. -% Translated by Jjgod Jiang , -% Jinsong Zhao , -% Yue Wang -% Helin Gai -% Public domain. -% -\documentclass{article} -\let\tldocenglish=1 % for live4ht.cfg - -\usepackage{tex-live, indentfirst} - -\begin{document} - -\title{% - {\huge \textit{\TeX\ Live 指å—}\\\smallskip}% - {\LARGE \textsf{\TL{} 2008}} -} - -\author{Karl Berry 编写 \\[3mm] - \url{http://tug.org/texlive/} - } - -\date{2008 å¹´ 7 月} - -\maketitle - -\begin{multicols}{2} -\tableofcontents -%\listoftables -\end{multicols} - -\section{简介} -\label{sec:intro} - -\subsection{\TeX\ Live 与 \TeX\ Collection} - -本文档æè¿° \TL{} 软件的主è¦åŠŸèƒ½å’Œç‰¹æ€§ï¼Œ\TL{} 是 \TeX{} åŠå…¶ç›¸å…³ç¨‹åºåœ¨ -\acro{GNU}/Linux åŠå…¶ä»–ç±» Unix 系统ã€\MacOSX\ å’Œ Windows -系统下的一套å‘行版。 - -ä½ å¯ä»¥ç›´æŽ¥ä¸‹è½½ \TL{},也å¯ä»¥åœ¨ \TeX{} 用户组织给会员分å‘çš„ \TK{} -\DVD 中找到。第 \ref{sec:tl-coll-dists} 节中,简è¦åœ°ä»‹ç»äº† -\DVD 的内容。这两套å‘行版都是用户组织共åŒå作完æˆçš„。 -这篇文档, 主è¦ä»‹ç» \TL{} 本身。 - -\TL{} 包括了 \TeX{}, \LaTeXe{}, \ConTeXt, \MF, \MP, \BibTeX{} -等许多å¯æ‰§è¡Œç¨‹åºï¼›ç§ç±»ç¹å¤šçš„å®åŒ…ã€å­—体和文档,并支æŒä¸–界上许多 -ä¸åŒçš„语言。 - -\TL{} ä¸­çš„å®‰è£…åŒ…å®šæœŸæ ¹æ® \acro{CTAN}:\url{http://www.ctan.org} -上的内容进行更新。 - -文档末尾的第 \ref{sec:history} 节 (第 \pageref{sec:history} 页) -介ç»äº†è¿™ä¸€ç‰ˆ \TL{} çš„é‡è¦æ”¹å˜ã€‚ - -\subsection{æ“作系统支æŒ} -\label{sec:os-support} - -\TL{} 为包括 \MacOSX 在内的多ç§åŸºäºŽ Unix çš„æ“作系统æ供了å¯æ‰§è¡Œ -文件。它还包å«äº†æºä»£ç ï¼Œå¯ä¾›åœ¨æ²¡æœ‰æä¾›å¯æ‰§è¡Œæ–‡ä»¶çš„å¹³å°ä¸Šç¼–译安装。 - -至于 Windows,\TL{} ä»…æ”¯æŒ Windows 2000 或åŽç»­ç‰ˆæœ¬ã€‚ -ä¸å†æ”¯æŒ Windows 9\textit{x}, ME å’Œ NT。 -因为这一改å˜ï¼ŒWindows 支æŒç›¸å¯¹äºŽ Unix 支æŒç³»ç»Ÿè€Œè¨€ä¸å†éœ€è¦å¾ˆå¤šçš„ -ç‰¹æ®Šå¯¹å¾…ã€‚æˆ‘ä»¬æ²¡æœ‰åŒ…å« 64 ä½çš„ Windows å¯æ‰§è¡Œæ–‡ä»¶ï¼Œä¸è¿‡ 32 ä½çš„å¯ -执行文件也能 64 ä½çš„系统上正常è¿è¡Œã€‚ - -除了 \TL{} 以外,Windows å’Œ \MacOSX 用户还有其它的选择,请å‚考第 -\ref{sec:tl-coll-dists} 节。 - -\subsection{\protect\TL{} 的基本安装} -\label{sec:basic} - -ä½ å¯ä»¥ä½¿ç”¨ \DVD{} æ–¹å¼æˆ–者网络方å¼æ¥å®‰è£… \TL{}。 -通过网络的安装程åºæœ¬èº«éžå¸¸å°ï¼Œå®ƒå¯ä»¥ä»Žç½‘上下载所有的你所è¦æ±‚的软 -件包。网络安装程åºå¯¹ä»…使用 \TL{} 一å°éƒ¨åˆ†çš„用户æ¥è¯´éžå¸¸é€‚宜。 - -\DVD{} 安装程åºå¯ä»¥æŠŠ \TL{} 安装到你的本地ç£ç›˜ä¸Šï¼Œä¹Ÿå¯ä»¥ç›´æŽ¥ä»Ž -\DVD{} 上è¿è¡Œ \TL{} (其实如果你的系统支æŒæŒ‚è½½ DVD é•œåƒï¼Œä½ ä¹Ÿå¯ä»¥ -从 \DVD é•œåƒä¸Šè¿è¡Œ)。 - -\noindent 安装方法将在下é¢çš„章节介ç»ï¼Œè¿™é‡Œæ供一个快速入门: - -\begin{itemize*} - -\item 安装脚本的å称是 \filename{install-tl}。它å¯ä»¥åœ¨ \GUI{} æ¨¡å¼ -(Windows 下的默认模å¼) å’Œæ–‡æœ¬æ¨¡å¼ (其它系统下默认模å¼) ä¸‹å·¥ä½œï¼Œä½ å¯ -以分别使用 \code{-gui} 或 \code{-no-gui} 命令行å‚æ•°æ¥å¼ºåˆ¶ä»¥æŸä¸€æ¨¡å¼ -è¿è¡Œç¨‹åºã€‚ - -\item 安装完æˆåŽå¯ä»¥å¾—到一个å为 \prog{tlmgr} 的程åºï¼š`\TL\ Manager'。 -和安装程åºä¸€æ ·ï¼Œå®ƒå¯ä»¥åœ¨ \GUI{} 模å¼æˆ–文本模å¼ä¸‹è¿è¡Œã€‚ä½ ä¸ä½†å¯ä»¥ç”¨å®ƒ -æ¥å®‰è£…或å¸è½½è½¯ä»¶åŒ…,还å¯ä»¥ç”¨æ¥å®Œæˆå„ç§é…置工作。 - -\end{itemize*} - - -\subsection{获得帮助} -\label{sec:help} - -\TeX{} 社群是活跃而å‹å¥½çš„,几乎所有认真的æ问都能得到回答。尽管如此,这ç§ç”±å¿—愿者 -和业余读者组æˆçš„技术支æŒä»ç„¶æ˜¾å¾—ä¸å¤ªæ­£å¼ï¼Œæ‰€ä»¥ï¼Œåœ¨æé—®å‰æœ€å¥½åšå¥½åŠŸè¯¾ã€‚(如果你更喜欢 -有ä¿éšœçš„商业性技术支æŒï¼Œå¯ä»¥æ”¾å¼ƒ \TL{},改为购买商业 \TeX{} 系统,在 -\url{http://tug.org/interest.html#vendors} 上有一份销售商的列表。) - -按照推è使用的顺åºï¼Œæˆ‘们列出了这样一份资æºåˆ—表: - -\begin{description} -\item [èµ·æ­¥] 如果你刚刚接触 \TeX,\url{http://tug.org/begin.html} -这个网页æ供了这个系统的简短介ç»ã€‚ - -\item [\TeX{} \acro{FAQ}] 这套庞大的 \TeX{} \acro{FAQ} 对å„ç§å„æ ·çš„ -问题——从最基础到最晦涩的——都给予了简明的回答,它在 \TL{} çš„ -\OnCD{texmf-doc/doc/english/FAQ-en/html/index.html},也å¯ä»¥åœ¨ -\url{http://www.tex.ac.uk/faq} 网站上找到。有问题时请先看看这里能å¦æ‰¾ -到解答。 - -\item [\TeX{} Catalogue] 如果你在寻找æŸä¸ªç‰¹å®šçš„å®åŒ…ã€å­—体ã€ç¨‹åºç­‰ç­‰ï¼Œ\TeX{} -Catalogue 就是你首先该找的地方。这里是所有 \TeX{} 相关内容的一个巨大集åˆã€‚å‚è§ -\url{http://www.ctan.org/help/Catalogue/}。 - -\item [\TeX{} 网上资æº] \url{http://tug.org/interest.html} 页é¢ä¸Šæœ‰ -许多和 \TeX{} 相关的链接,包括讨论这个系统方方é¢é¢çš„许多书ç±ã€æ‰‹å†Œå’Œæ–‡ç« ã€‚ - -\item [支æŒä¿¡æ¯çš„å½’æ¡£] 最é‡è¦çš„两个技术支æŒè®ºå›æ˜¯ Usenet 的新闻组 -\url{news:comp.text.tex} 和邮件列表 \email{texhax@tug.org}。它们的内容 -归档中有多年以æ¥çš„æ问和回答供你æœç´¢ã€‚ä½ å¯ä»¥åˆ†åˆ«ä»Ž -\url{http://groups.google.com/groups?group=comp.text.tex} å’Œ -\url{http://tug.org/mail-archives/texhax} 进行查询。当然,一般性的æœç´¢ -æ–¹å¼ï¼Œæ¯”如用 \url{http://google.com} 找找,总没有å处。 - -\item [æé—®] 如果你还是找ä¸åˆ°ç­”案,就å¯ä»¥é€šè¿‡ Google 或者你的新闻组阅读器在 -\dirname{comp.text.tex} 上æ问,或者å‘é€é‚®ä»¶åˆ° \email{texhax@tug.org}。 -ä¸è¿‡ï¼Œåœ¨æ问之å‰\emph{请一定}先阅读 \acro{FAQ} 上的这一æ¡ï¼š -\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}, -它能æ高你获得回答的å¯èƒ½æ€§ã€‚ - -\item [\TL{} 技术支æŒ] 如果你需è¦æŠ¥å‘Š bug,或者æ出对 \TL{} çš„å‘è¡Œã€å®‰è£…或 -文档的建议和æ„è§ï¼Œå¯ä»¥ä½¿ç”¨ \email{tex-live@tug.org} 这个邮件列表。ä¸è¿‡ï¼Œå¦‚果问题 -是针对 \TL{} 中包å«çš„æŸä¸ªç‰¹å®šç¨‹åºï¼Œé‚£æœ€å¥½è¿˜æ˜¯å†™ä¿¡ç»™è¿™ä¸ªç¨‹åºçš„维护者或邮件列表。 -用 \code{-{}-help} å‚æ•°æ¥è¿è¡Œç¨‹åºéƒ½ä¸€èˆ¬èƒ½å¾—到用æ¥æŠ¥å‘Šå…¶ bug 的地å€ã€‚ - -\end{description} - -å¦ä¸€æ–¹é¢ï¼Œä½ ä¹Ÿä¸å¦¨å¸®åŠ©å…¶ä»–有问题的朋å‹ï¼Œ\dirname{comp.text.tex} 与 -\code{texhax} 都是对所有人开放的,请尽管å‚与进去,在你能力所åŠçš„范围内æ供帮助。 - -% don't use \TL so the \uppercase in the headline works. Also so -% tex4ht ends up with the right TeX. Likewise the \protect's. -\section{\protect\TeX\protect\ Live 概览} -\label{sec:overview-tl} - -这个å°èŠ‚æ述的是 \TL{} 的内容,以åŠåŒ…å« \TL{} çš„ \TK{}。 - -\subsection{\TL, pro\TeX{}t, Mac\TeX\ 的大集åˆï¼š\TK} -\label{sec:tl-coll-dists} - -\TK{} çš„ \DVD{} 包å«äº†ä»¥ä¸‹å†…容: - -\begin{description} - -\item [\TL] 是一个完整的 \TeX{} 系统,它å¯ä»¥ç›´æŽ¥åœ¨å…‰ç›˜ä¸Šè¿è¡Œï¼Œä¹Ÿå¯ä»¥å®‰è£…在本 -地ç£ç›˜ä¸Šã€‚ - -\item [Mac\TeX] 在 \TL{} 的基础上增加了原生的 \MacOSX\ 的安装程åºå’Œä¸€äº›å…¶å®ƒçš„ -Mac 应用程åºã€‚它的主页在 \url{http://www.tug.org/mactex/}。 - -\item [pro\TeX{}t] 是 Windows 下的 \MIKTEX\ å‘行版的一个增强版本。\ProTeXt\ 在 -\MIKTEX\ 基础上增加了一些工具,简化了安装。它完全独立于 \TL{},有其 -自己的安装步骤。\ProTeXt\ 的主页在 \url{http://tug.org/protext}。 - -\item [CTAN] 一份 \CTAN{} 仓库的快照。 - -\item[\texttt{texmf-extra}] 一个æä¾›é¢å¤–çš„é…套软件包的目录。 - -\end{description} - -\CTAN{}, \pkgname{protext} å’Œ \dirname{texmf-extra} 并ä¸ä¸€å®šéµå¾ª \TL{} -的版æƒå议,因此在分å‘或修改时è¦æ ¼å¤–地å°å¿ƒã€‚ - -\subsection{\TL{} 的顶层目录} -\label{sec:tld} - -这里是 \TL{} å‘行版顶层目录的一个简短的列表和æ述。注æ„在 \pkgname{live} -\DVD\ 中,整个 \TL{} 目录结构都存放于 \dirname{texlive} å­ç›®å½•ä¸­ï¼Œè€Œéž -光盘的顶层目录下。 - -\begin{ttdescription} -\item[bin] \TeX{} 系统程åºï¼ŒæŒ‰å¹³å°ç»„织。 -% -\item[readme.html] 网页,æ供了多ç§è¯­è¨€çš„简介和有用的链接。 -% -\item[source] 所有程åºçš„æºä»£ç ï¼ŒåŒ…括主è¦çš„ \Webc{} \TeX{} å’Œ \MF{} - å‘行版。 -% -\item[support] å„类辅助性å®åŒ…与程åºã€‚这些内容\emph{ä¸ä¼š}自动安装。 -包括é…套的编辑器和 \TeX\ çš„å‰ç«¯ (外壳) 程åºã€‚ -% -\item[texmf] è§ä¸‹æ–‡çš„ \dirname{TEXMFMAIN}。 -% -\item[texmf-dist] è§ä¸‹æ–‡çš„ \dirname{TEXMFDIST}。 -% -\item[texmf-doc] 这个目录树用于存放和具体程åºã€å®åŒ…关系ä¸å¤§çš„纯粹 -文档,按语言组织。 -% -\item[tlpkg] 用æ¥ç»´æŠ¤å®‰è£…程åºæ‰€ç”¨åˆ°çš„脚本,程åºå’Œæ•°æ®ã€‚还内置了 -Windows 下 Perl å’Œ Ghostscript 的专有版本,它们ä¸èƒ½åœ¨ \TL 外使用。 -还有一个新的 Windows PostScript 阅读器 PSView。 -\end{ttdescription} - -上述目录之外,安装脚本和 (多ç§è¯­è¨€çš„) \filename{README} 文件也存放在å‘行版的顶层目录下。 - -\dirname{texmf-doc} 目录包å«äº†é‚£äº›ä¸éš¶å±žäºŽä»»ä½•ç‰¹å®šå®åŒ…或程åºçš„文档。 -程åºçš„文档 (手册,man page, Info 文件等) 在 \dirname{texmf/doc} -目录下,因为这些程åºæœ¬èº«æ˜¯å±žäºŽ \dirname{texmf} 目录的。\TeX\ å®åŒ…与格å¼æ–‡ä»¶ -的文档则放在 \dirname{texmf-dist/doc} 目录。但ä¸ç®¡æ”¾åœ¨å“ªä¸ªåœ°æ–¹ï¼Œä½ éƒ½å¯ä»¥ä½¿ç”¨ -\cmdname{texdoc} 或 \cmdname{texdoctk} 程åºæ¥å¯»æ‰¾è¿™äº›æ–‡æ¡£ã€‚顶层目录下的 -\OnCD{doc.html} 文件中æ供的完整的链接也会有所帮助。 - -\TL\ 本身的文档在 \dirname{texmf-doc} 目录下,有以下这些语言的版本: - -\begin{itemize*} -\item{简体中文:} \OnCD{texmf-doc/doc/chinese/texlive-zh-cn} -\item{æ·å…‹/斯洛ä¼å…‹è¯­:} \OnCD{texmf-doc/doc/czechslovak/texlive-cz} -\item{英语:} \OnCD{texmf-doc/doc/english/texlive-en} -\item{法语:} \OnCD{texmf-doc/doc/french/texlive-fr} -\item{德语:} \OnCD{texmf-doc/doc/german/texlive-de} -\item{波兰语:} \OnCD{texmf-doc/doc/polish/texlive-pl} -\item{俄语:} \OnCD{texmf-doc/doc/russian/texlive-ru} -\end{itemize*} - - -\subsection{预定义的 texmf 目录树概览} -\label{sec:texmftrees} - -本å°èŠ‚列出了系统中用于指定 texmf 目录的所有预定义å˜é‡åŠå…¶ç”¨é€”, -还有一个 \TL{} 系统的默认布局。\texttt{texconfig conf} å‘½ä»¤å¯ -以列出这些å˜é‡çš„值,这样你å¯ä»¥å¾ˆå®¹æ˜“找到它们和你所安装到的目录 -å称的对应关系。 - -\begin{ttdescription} -\item [TEXMFMAIN] 存储系统核心部件的目录树,包括辅助脚本 (比如 -\verb+web2c/mktexdir+) 和其他支æŒæ–‡ä»¶å’Œæ–‡æ¡£ã€‚ -这个目录ä¸åŒ…å« \TeX\ æ ¼å¼æ–‡ä»¶å’Œå®åŒ…。 -\item [TEXMFDIST] 存储主è¦çš„å®åŒ…ã€å­—体等等,å³ä¸€å¼€å§‹å°±åœ¨å‘行版中包括的而éžè‡ªå·± -åŽç»­æ·»åŠ çš„那些文件。 -\item [TEXMFLOCAL] 系统管ç†å‘˜ç”¨æ¥å®‰è£…供整个系统使用的é¢å¤–的或更新过的å®åŒ…ã€å­—体的目录。 -\item [TEXMFHOME] 给用户存放它们自己独立安装的的å®åŒ…ã€å­—体等等。 -这个å˜é‡æ ¹æ®ä¸åŒçš„用户选择ä¸åŒçš„主目录。 -\item [TEXMFCONFIG] ç»™ \verb+texconfig+ã€\verb+updmap+ã€å’Œ \verb+fmtutil+ -这些程åºå­˜å‚¨ä¿®æ”¹è¿‡çš„é…置文件。默认在 \envname{TEXMFHOME} 目录树下。 -\item [TEXMFSYSCONFIG] ç»™ \verb+texconfig-sys+ã€\verb+updmap-sys+ å’Œ -\verb+fmtutil-sys+ 这些程åºå­˜å‚¨ä¿®æ”¹è¿‡çš„文件. -\item [TEXMFVAR] 这个目录是给 \verb+texconfig+ã€\verb+updmap+ å’Œ - \verb+fmtutil+ 存储 (缓存) æ ¼å¼æ–‡ä»¶ã€ç”Ÿæˆ map 文件这类è¿è¡Œæ—¶æ•°æ®çš„。默认在 - \envname{TEXMFHOME} 目录下。 -\item [TEXMFSYSVAR] ç»™ \verb+texconfig-sys+ã€\verb+updmap-sys+ å’Œ -\verb+fmtutil-sys+ 还有 \verb+tlmgr+ 这几个命令存储ã€ç¼“å­˜è¿è¡Œæ—¶ä½¿ç”¨çš„æ ¼å¼æ–‡ä»¶å’Œ -生æˆçš„ map 文件。 -\end{ttdescription} - -\noindent -默认的目录结构: -\begin{description} - \item[全系统根目录] å¯ä»¥åŒ…å«å¤šä¸ª \TL{} 版本: - \begin{ttdescription} - \item[2007] 上一个版本。 - \begin{ttdescription} - \item [...] - \end{ttdescription} - \item[2008] 当å‰ç‰ˆæœ¬ã€‚ - \begin{ttdescription} - \item [bin] ~ - \begin{ttdescription} - \item [i386-linux] \GNU/Linux 二进制文件 - \item [...] - \item [universal-darwin] \MacOSX 二进制文件 - \item [win32] Windows 二进制文件 - \end{ttdescription} - \item [texmf] 这是 \envname{TEXMFMAIN}。 - \item [texmf-dist] \envname{TEXMFDIST} - \item [texmf-doc] \envname{TEXMFDOC} - \item [texmf-var] \envname{TEXMFSYSVAR} - \item [texmf-config] \envname{TEXMFSYSCONFIG} - \end{ttdescription} - \item [texmf-local] \envname{TEXMFLOCAL} 用æ¥å­˜æ”¾åœ¨ä¸åŒç‰ˆæœ¬é—´å…±äº«çš„æ•°æ®ã€‚ - \end{ttdescription} - \item[用户主 (home) 目录] (\texttt{\$HOME} 或 - \texttt{\%USERPROFILE\%}) - \begin{ttdescription} - \item[.texlive2007] 给上个版本的,个人生æˆå’Œé…置的数æ®ã€‚ - \item[.texlive2008] 给这个版本的,个人生æˆå’Œé…置的数æ®ã€‚ - \begin{ttdescription} - \item [texmf-var] \envname{TEXMFVAR} - \item [texmf-config] \envname{TEXMFCONFIG} - \end{ttdescription} - \item[texmf] \envname{TEXMFHOME} 个人的å®åŒ…文件。 - \textit{等等。} - \end{ttdescription} -\end{description} - - -\subsection{\protect\TeX\ 的扩展版本} -\label{sec:tex-extensions} - -\TeX{} çš„å¼€å‘å·²ç»å†»ç»“了,仅仅修改除去å‘现的æžå…¶å°‘é‡çš„错误。 -在现在以åŠå¯é¢„è§çš„未æ¥ï¼Œ\TL\ 中ä»ç„¶æä¾› \prog{tex} 这个程åºã€‚ -除此以外,\TL{} 包括了一些建立在 \TeX\ 基础上的的扩展程åºã€‚ -\TL{} 包括下列 \TeX\ 扩展版本: - -\begin{description} - -\item [\eTeX] 为 \TeX\ 增加了一套新的原语 (primitive)。 -\label{text:etex} (包括å®å±•å¼€ï¼Œå­—符扫æ,mark 的分类,é¢å¤–的调试功能,等等) -以åŠç”¨äºŽåŒå‘排版的 \TeXXeT{} 扩展模å¼ã€‚在默认模å¼ä¸‹ï¼Œ\eTeX{} 是与原始的 \TeX\ -100\% 兼容的。å‚è§ \OnCD{texmf-dist/doc/etex/base/etex_man.pdf}。 - -\item [pdf\TeX] 在 \eTeX\ 扩展的基础上构建,在 \dvi{} 输出之外增加对 -\acro{PDF} 输出的支æŒã€‚ -这是针对 \prog{etex}, \prog{latex} 或 \prog{pdflatex} 这些格å¼ä½¿ç”¨çš„缺çœç¨‹åºã€‚ -è§ \url{http://www.pdftex.org}。它的手册在 \OnCD{texmf/doc/pdftex/manual}。展 -示其一些功能的例å­å¯ä»¥åœ¨ \OnCD{texmf/doc/pdftex/manual/samplepdf/samplepdf.tex} -中找到。 - -\item [Lua\TeX] 是 pdf\TeX\ 指定的åŽç»§è€…,尽å¯èƒ½å¯¹ pdf\TeX\ ä¿æŒå‘å‰å…¼å®¹ã€‚ -它åŒæ—¶ä¹Ÿæ˜¯ Aleph (è§åŽ) 的继任者。 -它内置的 Lua 语言解释器 (\url{http://www.lua.org}) 为许多 \TeX{} 的棘手问题 -æ供了优雅的解决方案。 -当以 \filename{texlua} 命令执行时,它就åƒä¸€ä¸ªæ ‡å‡†çš„ Lua 解释器一样工作, -所以,Lua\TeX\ 在 \TL\ 中也被作为 Lua 程åºçš„解释器。 -è§ \url{http://www.luatex.org} å’Œ \OnCD{texmf-dist/doc/luatex/luatexref-t.pdf}。 - -\item [Xe\TeX] 通过第三方库,增加对 Unicode 输入文本和 OpenType 字体的支æŒï¼Œ -能够直接使用系统字体。å‚è§ \url{http://scripts.sil.org/xetex}。 - -\item [\OMEGA\ (Omega)] 基于 Unicode (16 ä½å­—符集),因而åŒæ—¶æ”¯æŒå¤„ç†ä¸–界上 -几乎所有的语言。它åŒæ—¶è¿˜æ”¯æŒæ‰€è°“çš„ `\OMEGA{} Translation Processes' (\acro{OTP}), -用于对任æ„输入进行å¤æ‚çš„å˜æ¢æ“作。å‚è§ -\OnCD{texmf-dist/doc/omega/base/doc-1.8.tex} (文档的更新å¯èƒ½ä¸æ˜¯å¾ˆåŠæ—¶)。 - -\item [Aleph] å°† \OMEGA\ 与 \eTeX\ 扩展åˆå¹¶åˆ°ä¸€èµ·å¾—到的。 -在 \OnCD{texmf-dist/doc/aleph/base} å¯ä»¥æ‰¾åˆ°ä¸€äº›ç®€çŸ­çš„文档。 - -\end{description} - - -\subsection{\protect\TL\ 中其他值得一æ的程åº} - -这里是在 \TL{} 中其他的一些常用程åºï¼š - -\begin{cmddescription} - -\item [bibtex] å‚考文献支æŒã€‚ - -\item [makeindex] 索引支æŒã€‚ - -\item [dvips] å°† \dvi{} 转æ¢ä¸º \PS{}。 - -\item [xdvi] X Window System 下的 \dvi{} 阅读器。 - -\item [dvilj] HP LaserJet 系列打å°æœºçš„ \dvi{} 驱动。 - -\item [dv2dt, dt2dv] \dvi{} 和纯文本之间的相互转æ¢ã€‚ - -\item [dviconcat, dviselect] 从 \dvi{} 文件中å¤åˆ¶å’Œç²˜è´´é¡µé¢ã€‚ - -\item [dvipdfmx] å°† \dvi{} 转æ¢ä¸º \acro{PDF},是 (å‰é¢æ到过的) -pdf\TeX\ 的一套替æ¢æ–¹æ¡ˆã€‚å‚è§ \pkgname{ps4pdf} å’Œ -\pkgname{pdftricks} 软件包以了解其他的方案。 - -\item [psselect, psnup, \ldots] \PS{} -实用程åºã€‚ - -\item [lacheck] \LaTeX{} 语法检查器。 - -\item [texexec, texmfstart] Con\TeX{}t å’Œ \acro{PDF} 处ç†å·¥å…·ã€‚ - -\item [tex4ht] \TeX{} 到 \acro{HTML} (还有 \acro{XML} 等其他格å¼) -的转æ¢å™¨ã€‚ - -\end{cmddescription} - - -\subsection{\TL\ 中的字体} -\label{sec:tl-fonts} - -\TL{} 中包括了很多的高质é‡çŸ¢é‡å­—体,å‚è§ \url{http://tug.org/fonts} å’Œ -\OnCD{texmf-doc/english/free-math-fonts-survey}。 - -\section{安装} -\label{sec:install} - -\subsection{å¯åŠ¨å®‰è£…程åº} -\label{sec:inst-start} - -首先请找æ¥ä¸€å¼  \TK{} çš„ \DVD{},或者下载 \TL{} 的网络安装程åºï¼Œç„¶åŽ -找到这个安装脚本:Unix 下是 \filename{install-tl},Windows 下是 -\filename{install-tl.bat}。 - -\begin{description} -\item [网络安装程åºï¼š] 在 \CTAN çš„ \dirname{systems/texlive/tlnet} -目录下å¯ä»¥ä¸‹è½½ï¼Œ\url{http://mirror.ctan.org/systems/texlive/tlnet} 这个地å€èƒ½ -自动将你导å‘一个附近的ã€ä¿æŒæ›´æ–°çš„é•œåƒã€‚ä½ å¯ä»¥ä¸‹è½½åŒæ—¶æ”¯æŒ Unix å’Œ -Windows çš„ \filename{install-tl.zip} 或者å°å¾—多但åªæ”¯æŒ Unix çš„ -\filename{install-unx.tar.gz}。解压åŽï¼Œ\filename{install-tl} å’Œ -\filename{install-tl.bat} 就会出现在 \dirname{install-tl} å­ç›®å½•ä¸­ã€‚ - -\item [\TeX{} Collection \DVD:] 打开 \dirname{texlive} 这个å­ç›®å½•ã€‚ -在 Windows 下安装程åºåº”该在æ’å…¥ \DVD åŽå°±è‡ªåŠ¨å¯åŠ¨äº†ã€‚è¦èŽ·å¾— \DVD çš„ -è¯å¯ä»¥åŠ å…¥ä¸€ä¸ª \TeX\ 用户组织 (推è这么åšï¼Œå‚è§ -\url{http://tug.org/usergroups.html}) 或是å•ç‹¬è´­ä¹° (通过 -\url{http://tug.org/store}),åˆæˆ–者是自己从 \ISO\ é•œåƒåˆ»å½• -(\url{http://tug.org/texlive/acquire.html})。 - -\end{description} - -下é¢çš„章节介ç»å¾—更为详细。 - -\subsubsection{Unix} - -\begin{figure}[tb] -\begin{boxedverbatim} -======================> TeX Live installation procedure <===================== - -=======> Note: Letters/digits in indicate menu items <======= -=======> for commands or configurable options <======= - - - Detected platform: Intel x86 with GNU/Linux - - binary systems: 1 out of 16 - - Installation scheme (scheme-full) - - Customizing installation scheme: - standard collections - language collections - 83 collections out of 84, disk space required: 1666 MB - - directories: - TEXDIR (the main TeX directory): - !! default location: /usr/local/texlive/2008 - !! is not writable, please select a different one! - TEXMFLOCAL (directory for site-wide local files): - /usr/local/texlive/texmf-local - TEXMFSYSVAR (directory for variable and automatically generated data): - /usr/local/texlive/2008/texmf-var - TEXMFSYSCONFIG (directory for local config): - /usr/local/texlive/2008/texmf-config - TEXMFHOME (directory for user-specific files): - ~/texmf - - options: - [ ] use letter size instead of A4 by default - [X] create all format files - [X] install macro/font doc tree - [X] install macro/font source tree - [ ] create symlinks in standard directories - - Install for running from DVD - -Other actions: - start installation to HD - help - quit - -Enter command: -\end{boxedverbatim} -\caption{文本模å¼ä¸»å®‰è£…ç•Œé¢ (\GNU/Linux)}\label{fig:text-main} -\end{figure} - -\begin{figure}[tb] -\tlpng{install-w32-main}{\linewidth} -\caption{\GUI{} 模å¼ä¸»å®‰è£…ç•Œé¢ (Windows)}\label{fig:gui-main} -\end{figure} - -\noindent -下é¢çš„ \texttt{>} 表示 shell æ示符;用户的输入则用 -\Ucom{\texttt{bold}} 体表示。 -在 Unix 兼容的系统的一个终端窗å£ä¸‹ï¼Œæœ€ç®€å•çš„æ–¹å¼æ˜¯: -\begin{alltt} -> \Ucom{cd /path/to/installer} -> \Ucom{perl install-tl} -\end{alltt} -(或者你å¯ä»¥ç›´æŽ¥è¿è¡Œ \Ucom{perl /path/to/installer/install-tl},或者 -\Ucom{./install-tl},如果这个文件有å¯æ‰§è¡Œå±žæ€§ï¼Œæˆ‘们ä¸ä¼šæŠŠæ‰€æœ‰è¿™äº›æ‰§ -行方法列出æ¥ã€‚) - -è¦åœ¨ \GUI\ 模å¼ä¸‹å®‰è£… (ä½ éœ€è¦ \dirname{Perl/TK} 模å—),使用: -\begin{alltt} -> \Ucom{perl install-tl -gui} -\end{alltt} - -è¦åˆ—出所有这些选项: -\begin{alltt} -> \Ucom{perl install-tl -help} -\end{alltt} - -\textbf{关于 Unix 下æƒé™çš„警告:} 在安装过程中,\TL{} 安装程åºå°†ä¼š -éµç…§ä½ çš„ \code{umask} 行事。所以如果你需è¦è®©ä½ çš„安装能给其他用户使 -用,就必须ä¿è¯ä½ è®¾ç½®çš„æƒé™è¶³å¤Ÿï¼Œæ¯”如 \code{umask 002}。更多关于 -\code{umask} çš„ä¿¡æ¯è¯·å‚è§ä½ è‡ªå·±ç³»ç»Ÿçš„文档。 - -\subsubsection{Mac\,OS\,X} - -如第 \ref{sec:tl-coll-dists} 节æ到的,我们给 \MacOSX 准备了一套独立的 -å‘行版,å«åš Mac\TeX\ (\url{http://tug.org/mactex})。我们推è使用原生的 -Mac\TeX\ 安装程åºï¼Œè€Œä¸æ˜¯ \TL\ 自带的那个,因为原生的这个能进行一些专门 -针对 Mac 的调整,尤其方便在多个 \MacOSX 下的 \TeX\ å‘行版 (Mac\TeX, gw\TeX, -Fink, MacPorts, \ldots) 之间切æ¢ã€‚ - -Mac\TeX\ 是严格ä¾èµ– \TL 构建的,所以主 \TeX\ 树也是完全一致的。ä¸è¿‡å®ƒæ·» -加了一些用æ¥å­˜æ”¾ Mac 专有文档和程åºçš„目录。 - -\subsubsection{Windows} - -如果你使用的是网络安装程åºï¼Œåˆæˆ–者 \DVD 安装程åºæ— æ³•è‡ªåŠ¨å¯åŠ¨äº†ï¼Œè¯· -åŒå‡» \filename{install-tl.bat}。 - -你也å¯ä»¥ä»Žå‘½ä»¤è¡Œæ示符下å¯åŠ¨å®‰è£…程åºã€‚ä¸‹é¢ \texttt{>} 表示的就是æ示符, -用户输入用 \Ucom{\texttt{bold}} 体表示。如果你正在安装程åºç›®å½•ä¸‹ï¼Œåªéœ€è¦ -è¿è¡Œï¼š -\begin{alltt} -> \Ucom{install-tl} -\end{alltt} - -或者你也å¯ä»¥é€šè¿‡ç»å¯¹è·¯å¾„æ¥è¿è¡Œï¼Œæ¯”如: -\begin{alltt} -> \Ucom{D:\bs{}texlive\bs{}install-tl} -\end{alltt} -这是对 \TK\ \DVD 而言的,å‡å®š \dirname{D:} 是光驱。 - -è¦åœ¨æ–‡æœ¬æ¨¡å¼ä¸‹å®‰è£…,使用: -\begin{alltt} -> \Ucom{install-tl -no-gui} -\end{alltt} - -è¦åˆ—出所有å¯ç”¨çš„选项: -\begin{alltt} -> \Ucom{install-tl -help} -\end{alltt} - -\subsubsection{文本界é¢å®‰è£…程åº} - -图~\ref{fig:text-main} 展示了 Unix 下文本模å¼çš„主界é¢ã€‚ - -这是一个完全用命令行æ“作的安装程åºï¼Œå®Œå…¨ä¸æ”¯æŒå…‰æ ‡ç§»åŠ¨ã€‚所以你无法 -在多选框或者输入框之间用 Tab 上下切æ¢ï¼Œåªèƒ½åœ¨æ示符下输入特定的字符 -(大å°å†™æ•æ„Ÿçš„) 然åŽæŒ‰ä¸‹ Enter,整个终端窗å£å°±ä¼šæŠŠæ–°çš„内容刷新出æ¥ã€‚ - -文本安装程åºä¹‹æ‰€ä»¥è¿™ä¹ˆç®€é™‹æ˜¯å› ä¸ºå®ƒè¦å°½å¯èƒ½æ”¯æŒæœ€å¤šçš„å¹³å°ï¼Œå°±ç®— -åªæœ‰ä¸€ä¸ª Perl 的系统也能è¿è¡Œå®ƒ (对于 Windows 我们自带了一个 Perl -çš„è£å‰ªç‰ˆæœ¬)。 - -\subsubsection{图形界é¢å®‰è£…程åº} - -图~\ref{fig:gui-main} 展示了 Windows 下的的图形界é¢å®‰è£…程åºã€‚图中 -选项的差别主è¦æ˜¯å› ä¸ºè¿™å¼ å›¾æ˜¯ä»Ž Windows 下截å–的,而上é¢çš„æ–‡æœ¬æ¨¡å¼ -ç•Œé¢æ¥è‡ª \GNU/Linux。 - -\subsection{执行安装程åº} -\label{sec:runinstall} - -安装程åºåº”该ä¸éœ€è¦æ–‡æ¡£å°±è¶³å¤Ÿæ˜Žç¡®ã€‚ä¸è¿‡å¯¹è¿™äº›é€‰é¡¹å’Œå­èœå•è¿˜éœ€è¦ç‚¹å°è¯´æ˜Žã€‚ - -\subsubsection{二进制系统èœå• (åªå¯¹ Unix 适用)} -\label{sec:binary} - -\begin{figure}[tbh] -\begin{boxedverbatim} -Available sets of binaries: -=============================================================================== - - a [ ] alpha-linux DEC Alpha with GNU/Linux - b [ ] amd64-freebsd x86_64 with FreeBSD - c [ ] hppa-hpux HP-UX - d [ ] i386-freebsd Intel x86 with FreeBSD - e [X] i386-linux Intel x86 with GNU/Linux - f [ ] i386-openbsd Intel x86 with OpenBSD - g [ ] i386-solaris Intel x86 with Sun Solaris - h [ ] mips-irix SGI IRIX - i [ ] powerpc-aix PowerPC with AIX - j [ ] powerpc-linux PowerPC with GNU/Linux - k [ ] sparc-linux Sparc with GNU/Linux - l [ ] sparc-solaris Sparc with Solaris - m [ ] universal-darwin universal binaries for MacOSX/Darwin - o [ ] win32 Windows - p [ ] x86_64-linux x86_64 with GNU/Linux -\end{boxedverbatim} -\caption{Binaries (二进制程åº) èœå•}\label{fig:bin-text} -\end{figure} - -图~\ref{fig:bin-text} 展示了文本模å¼ä¸‹çš„ binaries (二进制程åº) -èœå•ã€‚默认情况下åªä¼šå®‰è£…你当å‰å¹³å°ä¸‹çš„二进制程åºã€‚在这个èœå•ä¸‹ï¼Œ -ä½ å¯ä»¥é€‰æ‹©å®‰è£…其他架构的二进制程åºã€‚这对你è¦å°† \TeX\ 树共享在 -异构网络上的情况比较有用,åˆæˆ–者用于åŒå¯åŠ¨çš„系统。 - -\subsubsection{选择è¦å®‰è£…的组件} -\label{sec:components} - -\begin{figure}[tbh] -\begin{boxedverbatim} -Select a scheme: -=============================================================================== - - a [ ] TeX Live basic scheme - b [ ] TeX Live scheme for ConTeXt - c [X] TeX Live full scheme - d [ ] GUST TeX Live scheme - e [ ] GUTenberg TeX Live scheme - f [ ] TeX Live medium scheme - g [ ] TeX Live minimal scheme - h [ ] TeX Live for Omega users - i [ ] teTeX scheme - j [ ] XML typesetting scheme -\end{boxedverbatim} -\caption{Scheme (安装方案) èœå•}\label{fig:scheme-text} -\end{figure} - -图~\ref{fig:scheme-text} 展示了 \TL\ 的安装方案èœå•ï¼›ä»Žè¿™é‡Œä½ é€‰æ‹©çš„是 -一套``安装方案'',也就是对软件包集åˆçš„一个统一划分。默认的 \optname{full} -方案会把所有å¯ç”¨çš„都装上,ä¸è¿‡ä½ ä¹Ÿå¯ä»¥ç»™å°ç‚¹çš„系统选择 \optname{basic} æ–¹ -案,为测试选用 \optname{minimal} 方案,åˆæˆ–者是 \optname{medium} 或 -\optname{teTeX} æ¥é€‰æ‹©ä»‹ä¹Žå…¶é—´çš„方案。还有许多特殊或者专门针对特定国家 -的方案。 - -\begin{figure}[tbh] -\tlpng{stdcoll}{.7\linewidth} -\caption{Collections (集åˆ) èœå• (Linux)}\label{fig:collections-gui} -\end{figure} - -ä½ å¯ä»¥ä½¿ç”¨ `standard collections' 与 `language collections' èœå•æ¥è¯¦ç»† -选择安装方案。(图~\ref{fig:collections-gui} 显示了 \GUI 模å¼ä¸‹ä¿®æ”¹çš„情 -况。) - -Collection (安装集åˆ) 是比 scheme (方案) è¦æ›´ç»†çš„一层 \Dash 实际上一个 -方案包å«äº†å¤šä¸ªé›†åˆï¼Œè€Œä¸€ä¸ªé›†åˆåˆåŒ…å«äº†ä¸€åˆ°å¤šä¸ªè½¯ä»¶åŒ…,然åŽæ¯ä¸ªè½¯ä»¶åŒ… -(\TL 中最å°çš„组织å•ä½) 则包å«äº†å®žé™…çš„ \TeX\ å®æ–‡ä»¶ï¼Œå­—体文件,等等。 - -如果你觉得 collection èœå•å¯¹å®‰è£…控制还ä¸å¤Ÿç»†ï¼Œå¯ä»¥åœ¨å®‰è£…åŽä½¿ç”¨ -\prog{tlmgr} ç¨‹åº (å‚è§ç¬¬~\ref{sec:tlmgr} 节),它能在软件包一层 -控制安装。 - -\subsubsection{目录} -\label{sec:directories} - -缺çœçš„目录布局在第~\ref{sec:texmftrees} 节有过å™è¿°ï¼Œè§ç¬¬ -\pageref{sec:texmftrees} 页。默认的 \dirname{TEXDIR} 路径 -则是 Windows 下的 |%PROGRAMFILES%\texlive\2008| å’Œ Unix -下的 \dirname{/usr/local/texlive/2008}。 - -更改默认值的主è¦åŽŸå› å¤§æ¦‚是你å¯èƒ½æ²¡æœ‰é»˜è®¤ä½ç½®çš„写æƒé™ã€‚虽然è¦å®‰è£… -\TL ä¸éœ€è¦æ˜¯ç®¡ç†å‘˜æˆ–者 root 用户,但你至少得对安装的目的目录有写 -æƒé™ã€‚ - -一个åˆç†çš„选择是你自己主目录下的一个å­ç›®å½•ï¼Œå°¤å…¶åœ¨åªæœ‰ä½ ä¸€ä¸ªäºº -使用的时候。使用 `|~|' æ¥è¡¨ç¤ºä¸»ç›®å½•ï¼Œæ¯”如 `|~/texlive/2008|'。 - -我们建议在目录å称中ä¿ç•™å¹´ä»½ï¼Œè¿™æ ·å¯ä»¥è®©ä½ ä¿ç•™å¤šä¸ªä¸åŒç‰ˆæœ¬çš„ -\TL{}。(ä½ å¯èƒ½å¸Œæœ›ç”¨ä¸€ä¸ªç±»ä¼¼ \dirname{/usr/local/texlive-cur} -这样的å字作为指å‘当å‰ç‰ˆæœ¬çš„符å·é“¾æŽ¥ï¼Œè¿™æ ·çš„目录å就和版本无 -关了,你åªè¦åœ¨æ–°ç‰ˆæœ¬å‡ºæ¥ç›´æŽ¥æ›´æ–°ç¬¦å·é“¾æŽ¥å³å¯ã€‚) - -在安装程åºä¸­ä¿®æ”¹ \dirname{TEXDIR} 之åŽè¿˜ä¼šåŒæ—¶ä¿®æ”¹ -\dirname{TEXMFLOCAL}, \dirname{TEXMFSYSVAR} å’Œ -\dirname{TEXMFSYSCONFIG}。 - -\dirname{TEXMFHOME} 是推è用æ¥å­˜æ”¾ä¸ªäººå®æ–‡ä»¶å’Œè½¯ä»¶åŒ…的目录。 -其缺çœå€¼æ˜¯ |~/texmf|。与 \dirname{TEXDIR} ä¸åŒï¼Œå…¶ä¸­åŒ…å«çš„ -|~| 会被ä¸åŠ è½¬æ¢åœ°å†™è¿›é…置文件,因为它能在 \TeX 系统è¿è¡Œæ—¶ -自动被替æ¢ä¸ºæ¯ä¸ªç”¨æˆ·è‡ªå·±çš„主目录。在 Unix 它会被展开为 -\dirname{$HOME},而 Windows 下展开为 \verb|%USERPROFILE%|。 - -\subsubsection{选项} -\label{sec:options} - -\begin{figure}[tbh] -\begin{boxedverbatim} -

use letter size instead of A4 by default: [ ] - create all format files: [X] - install font/macro doc tree: [X] - install font/macro source tree: [X] - create symlinks in standard directories: [ ] - binaries to: - manpages to: - info to: -\end{boxedverbatim} -\caption{Options èœå• (Unix)}\label{fig:options-text} -\end{figure} - -图~\ref{fig:options-text} 显示了文本模å¼çš„选项èœå•ã€‚其中有 -三个选项值得一æ: - -\begin{description} -\item[use letter size instead of A4 by default:] 常è§çš„缺çœçº¸å¼ å¤§å°é€‰æ‹©ã€‚ -当然如果需è¦ï¼Œæ¯ä»½æ–‡æ¡£éƒ½å¯ä»¥å•ç‹¬è®¾å®šä¸€ä¸ªçº¸å¼ å¤§å°ã€‚ - -\item[create all format files:] 虽然创建ä¸å¿…è¦çš„æ ¼å¼æ–‡ä»¶ä¼šæµªè´¹ä¸€ -点时间,也会多å ä¸€äº›ç£ç›˜ç©ºé—´ï¼Œä½† -我们还是建议现在ä¿æŒè¿™ä¸ªé€‰é¡¹çš„选定状æ€ï¼Œå› ä¸ºå¦‚果这次ä¸ç”Ÿæˆï¼Œä¸‹æ¬¡ -用到的时候格å¼æ–‡ä»¶å°±ä¼šåœ¨ç”¨æˆ·ä¸ªäººçš„ \dirname{TEXMFVAR} 目录树内生 -æˆã€‚这样æ¯æ¬¡äºŒè¿›åˆ¶æ–‡ä»¶æˆ–者断字模å¼æ›´æ–°çš„时候,这些格å¼æ–‡ä»¶ä¹Ÿå¾—ä¸ -到更新,所以å¯èƒ½ä¼šå¯¼è‡´å®ƒä»¬çš„ä¸å…¼å®¹ã€‚ - -\item[create symlinks in standard directories] (åªå¯¹ Unix 有效): -这个选项å¯ä»¥çœä¸‹è®¾å®šçŽ¯å¢ƒå˜é‡çš„步骤。如果没有选择它,就必须把 -\TL{} 的对应目录添加到 \envname{PATH}, \envname{MANPATH} å’Œ -\envname{INFOPATH} 中。如果è¦åˆ›å»ºç¬¦å·é“¾æŽ¥ï¼Œä½ éœ€è¦å¯¹è¿™äº›ç›®æ ‡ -目录的写æƒé™ã€‚我们ä¸å»ºè®®ä½ ç”¨è¿™ä¸ªå‘½ä»¤æ¥è¦†ç›–现有的 \TeX\ 系统, -它主è¦æ˜¯ä¸ºäº†åœ¨ç”¨æˆ·å·²çŸ¥çš„标准目录中创建符å·é“¾æŽ¥è®¾è®¡çš„,这些 -目录并ä¸åŒ…å«ä»»ä½• \TeX\ 文件。 -\end{description} - -如果所有的设置已ç»é½å¤‡ï¼Œä½ å°±å¯ä»¥æŒ‰ä¸‹ `I' æ¥å¼€å§‹å®‰è£…了。安装完æˆåŽï¼Œ -ä½ å¯ä»¥è·³è‡³ç¬¬ \ref{sec:postinstall} 节æ¥äº†è§£è¿˜éœ€è¦åšäº›ä»€ä¹ˆå·¥ä½œã€‚ - -\subsubsection{设置从 DVD{} è¿è¡Œ (åªå¯¹æ–‡æœ¬æ¨¡å¼é€‚用)} -\label{sec:fromdvd} - -按 `|V|' æ¥é€‰æ‹©è¿™ä¸ªé€‰é¡¹ã€‚它将主èœå•æ”¹å˜ä¸ºç±»ä¼¼å›¾~\ref{fig:main-fromdvd} -çš„ç•Œé¢ã€‚ -\begin{figure}[tbh] -\begin{boxedverbatim} -======================> TeX Live installation procedure <===================== - -=======> Note: Letters/digits in indicate menu items <======= -=======> for commands or configurable options <======= - - directories: - TEXDIRW (Writable root): - !! default location: /usr/local/texlive/2008 - !! is not writable, please select a different one! - TEXMFLOCAL (directory for site-wide local files): - /usr/local/texlive/texmf-local - TEXMFSYSVAR (directory for variable and automatically generated data): - /usr/local/texlive/2008/texmf-var - TEXMFSYSCONFIG (directory for local config): - /usr/local/texlive/2008/texmf-config - TEXMFHOME (directory for user-specific files): - ~/texmf - - options: - [ ] use letter size instead of A4 by default - [X] create all format files - - set up for installing to hard disk - -Other actions: - start installation for running from DVD - help - quit -\end{boxedverbatim} -\caption{å¯ç”¨ \optname{from DVD} 集åˆåŽçš„主èœå•}\label{fig:main-fromdvd} -\end{figure} - -注æ„å˜åŒ–之处:所有关于安装内容的选项都消失了,而目录这部分 -çš„è®¾ç½®çŽ°åœ¨æ˜¯æ ¹æ® \dirname{TEXDIRW} (或者一个å¯å†™çš„根目录) -æ¥è®¾ç½®çš„。创建符å·é“¾æŽ¥çš„选项也没有了。 - -这样安装程åºä»ç„¶ä¼šåˆ›å»ºä¸€äº›ç›®å½•å’Œé…置文件,但并ä¸ä¼šæŠŠ \dirname{texmf}, -\dirname{texmf-dist} 或 \dirname{texmf-doc} 目录å¤åˆ¶åˆ°æœ¬åœ°ç¡¬ç›˜ä¸Šã€‚ - -Unix 系统下的安装åŽé…置步骤è¦ç¨å¾®å¤æ‚一些,因为这样目录布局就和缺 -çœæƒ…况有所区别了,å‚è§ç¬¬ \ref{sec:postinstall} 节。 - -因为时间é™åˆ¶ï¼Œè¿™ä¸ªé€‰é¡¹è¿˜æ¥ä¸åŠé›†æˆè¿›å…¥ \GUI{} 安装程åºã€‚ä¸è¿‡å®ƒçš„ç¡® -是åŒæ—¶æ”¯æŒ Unix å’Œ Windows 的。Windows 用户需è¦ä»Žå‘½ä»¤è¡Œé€‰é¡¹æ¥å¯åŠ¨ -这个安装程åºï¼Œå‚è§ç¬¬ \ref{sec:cmdline} 节。 - -第 \ref{sec:portable-unix} 节æ述了一套更具å¯ç§»æ¤æ€§åœ°è¿è¡Œ \TL{} -的方法,它ä¸éœ€è¦å¯¹ç³»ç»Ÿé…ç½®åšä»»ä½•æ”¹åŠ¨ï¼Œä½†ä¹Ÿåšä¸äº†ä»»ä½•é…置。 - -\subsection{命令行安装选项} -\label{sec:cmdline} - -输入 -\begin{alltt} -> \Ucom{install-tl -help} -\end{alltt} -å¯ä»¥åˆ—出所有的命令行å‚数。你既å¯ä»¥ç”¨ |-| 也å¯ä»¥ç”¨ |--| æ¥æŒ‡å®šä¸€ä¸ª -å‚数。这里有些比较有趣的: - -\begin{ttdescription} -\item[-gui] å°½å¯èƒ½ç”¨ \GUI{} 模å¼çš„安装程åºã€‚它需è¦å®‰è£…了 - Perl/Tk æ¨¡å— (\url{http://tug.org/texlive/distro.html#perltk})ï¼› - 如果找ä¸åˆ° Perl/Tk,安装程åºå°±ä¼šåœ¨æ–‡æœ¬æ¨¡å¼ä¸‹å‡ºçŽ°ã€‚ -\item[-no-gui] 强制使用文本模å¼å®‰è£…程åºï¼Œå°±ç®—在 Windows 下也是如此。 -å¦‚æžœä½ éœ€è¦ `from \DVD' 安装方å¼å°±éœ€è¦ç”¨åˆ°è¿™ä¸ªé€‰é¡¹ï¼Œå› ä¸ºè¿™ä¸ªæ–¹å¼åœ¨ -\GUI{} 模å¼ä¸‹æ²¡æœ‰æ供。 -\item[-lang {\sl LL}] 指定安装程åºç•Œé¢çš„语言,使用两个字符的语言 -ä»£ç  \textsl{LL}。目å‰æ”¯æŒçš„语言有:英语 (\texttt{en}, 默认值), -德语 (\texttt{de}), 法语 (\texttt{fr}), è·å…°è¯­ (\texttt{nl}), 波兰语 -(\texttt{pl}), 斯洛文尼亚语 (\texttt{sl}) 和越å—语 (\texttt{vi})。 -安装程åºä¼šå°è¯•è‡ªå·±åˆ¤æ–­å‡ºåˆé€‚的语言,如果判断出的语言没有支æŒå°±ä¼š -使用英语替代。 -\item[-profile {\sl profile}] 安装程åºä¼šåœ¨ \dirname{2008/tlpkg} -目录或者安装到的å­ç›®å½• \dirname{tlpkg} ä¸­åˆ›å»ºä¸€ä¸ªå« -\filename{texlive.profile} 的文件。这个选项å¯ä»¥è®©å®‰è£…程åºé‡ç”¨ -现æˆçš„è¿™ç§æ–‡ä»¶ã€‚这里有个例å­ï¼š - \begin{fverbatim} -# texlive.profile written on Wed Jul 9 16:13:44 2008 UTC -# It will NOT be updated and reflects only the -# installation profile at installation time. -selected_scheme scheme-basic -TEXDIR /usr/local/texlive/2008 -TEXDIRW /usr/local/texlive/2008 -... -TEXMFSYSVAR /usr/local/texlive/2008/texmf-var -collection-basic 1 -... -option_symlinks 0 - \end{fverbatim} -这样一æ¥ï¼Œé€šè¿‡è¿™ä¸ªé€‰é¡¹ä½ å°±å¯ä»¥åœ¨åŽæ¥çš„系统里进行批é‡å®‰è£…了,å¯ä»¥ -ä¿è¯é€‰é¡¹å’Œç¬¬ä¸€æ¬¡å®‰è£…的完全一样。 -\item [-location {\sl url/path}] 为软件包指定一个éžå®˜æ–¹çš„æ¥æºï¼Œå‚è§ä¸‹æ–‡ã€‚ -\end{ttdescription} - -\subsubsection{\optname{location} å‚æ•°} -\label{sec:location} - -location 值å¯ä»¥æ˜¯ä¸€ä¸ªä»¥ \texttt{ftp:}, \texttt{http:}, 或 -\texttt{file:/} 起始的 URL,或者一个本地路径。如果给定的地 -å€åœ¨æœ¬åœ°ç£ç›˜ä¸Š (或者是路径或者是 \texttt{file:/} 开头的 URL), -我们å¯ä»¥ç«‹å³åˆ¤æ–­å‡ºå®‰è£…的类型 (压缩的 CD 还是 live DVD):如果 -èƒ½æ‰¾åˆ°ä¸€ä¸ªå« \dirname{archive} å­ç›®å½•è€Œä¸”它下é¢éƒ½æ˜¯ -\filename{.tar.lzma} æ ¼å¼çš„压缩文件,那就会用它进行安装,就算 -没压缩的文件也存在。 - -如果给定了一个 \texttt{http:} 或 \texttt{ftp:} 地å€ï¼Œå…¶æœ«å°¾çš„ -`\texttt{/}' 字符和末尾的 `\texttt{/tlpkg}' 这段都会被忽略。 -比如你å¯ä»¥é€‰æ‹©è¿™æ ·çš„一个 \CTAN é•œåƒï¼š -\url{http://ctan.example.org/tex-archive/texlive/tlnet/2008}, -当然你应该把 |ctan.example.org/tex-archive| 替æ¢ä¸ºå…·ä½“é•œåƒçš„ -域å和特定的顶层 \CTAN 路径 (\url{http://ctan.org/mirrors}) -维护了一个 \CTAN çš„é•œåƒåˆ—表)。缺çœå€¼æ˜¯ä½¿ç”¨ \url{http://mirror.ctan.org} -æ¥è‡ªåŠ¨åˆ¤æ–­çš„。ä¸ç®¡æ˜¯ä»€ä¹ˆæƒ…况,选定的镜åƒéƒ½ä¼šè¢«ç”¨æ¥ä¸‹è½½æ‰€æœ‰çš„ -内容。 - -\subsection{安装åŽçš„æ“作} -\label{sec:postinstall} - -安装åŽå¯èƒ½éœ€è¦ä¸€äº›é¢å¤–çš„æ“作。 - -\subsubsection{Windows} - -在 Windows 下安装程åºä¼šå®Œæˆæ‰€æœ‰çš„æ“作。 - -\subsubsection{如果创建了符å·é“¾æŽ¥} - -如果你选择了在标准路径下创建符å·è¿žæŽ¥ (在第~\ref{sec:options} 节æ到), -那就ä¸éœ€è¦è®¾ç½®çŽ¯å¢ƒå˜é‡äº†ã€‚ - -\subsubsection{Unix 下的环境å˜é‡} -\label{sec:env} - -你应该将自己使用的平å°ä¸‹äºŒè¿›åˆ¶ç¨‹åºçš„目录加入æœç´¢è·¯å¾„中。æ¯ä¸ªæ”¯ -æŒçš„å¹³å°éƒ½åœ¨ \dirname{TEXDIR/bin} 下有自己的å­ç›®å½•ã€‚å‚è§å›¾~\ref{fig:bin-text} -以了解所有的这些å­ç›®å½•å’Œå®ƒä»¬å¯¹åº”çš„å¹³å°ã€‚ - -如果希望 man å’Œ info 能够找到,你还å¯ä»¥æŠŠæ–‡æ¡£çš„ man å’Œ Info 目录加 -入其对应的æœç´¢è·¯å¾„中。 - -对于 \prog{bash} 这样的 Bourne 兼容 shell 而言,以 Intel x86 下的 -GNU/Linuxã€é»˜è®¤çš„目录设置为例,需è¦ä¿®æ”¹çš„文件是 \filename{$HOME/.profile} -(或者其他由 \filename{.profile} 载入的文件),应该添加的内容应该类似 -这样: - -\begin{sverbatim} -PATH=/usr/local/texlive/2008/bin/i386-linux:$PATH; export PATH -MANPATH=/usr/local/texlive/2008/texmf/doc/man:$MANPATH; export MANPATH -INFOPATH=/usr/local/texlive/2008/texmf/doc/info:$INFOPATH; export INFOPATH -\end{sverbatim} - -对于 csh 或者 tcsh,需è¦ä¿®æ”¹çš„文件通常是 \filename{$HOME/.cshrc},而 -应该添加的内容类似: - -\begin{sverbatim} -setenv PATH /usr/local/texlive/2008/bin/i386-linux:$PATH -setenv MANPATH /usr/local/texlive/2008/texmf/doc/man:$MANPATH -setenv INFOPATH /usr/local/texlive/2008/texmf/doc/info:$INFOPATH -\end{sverbatim} - -当然,你å¯èƒ½å·²ç»åœ¨ä½ çš„é…置文件里写过了这样的路径设置,那就åªéœ€è¦ -把 \TL\ 的这些目录加进去就行了。 - -\subsubsection{环境å˜é‡çš„全局é…ç½®} -\label{sec:envglobal} - -如果你希望在整个系统范围内修改这些å˜é‡ï¼Œæˆ–这样系统新增的用户自动 -继承这些å˜é‡ï¼Œå°±å¾—自寻方法了,因为ä¸åŒçš„系统之间这方é¢çš„é…置差异 -太大。 - -我们的建议是: 1)~ä½ å¯èƒ½åº”该看看 \filename{/etc/manpath.config} -这个文件是å¦å­˜åœ¨ï¼Œå¦‚果有的è¯ï¼Œæ·»åŠ ä¸‹é¢è¿™æ ·çš„内容: - -\begin{sverbatim} -MANPATH_MAP /usr/local/texlive/2008/bin/i386-linux \ - /usr/local/texlive/2008/texmf/doc/man -\end{sverbatim} - -ç„¶åŽ 2)~检查 \filename{/etc/environment} 是å¦å®šä¹‰äº†é»˜è®¤çš„æœç´¢è·¯å¾„ -和其他的默认环境å˜é‡ã€‚ - -\subsubsection{如果从 DVD è¿è¡Œ} - -通常æ¥è¯´ \TL{} 程åºéƒ½ä¼šå¯»æ‰¾ä¸€ä¸ªå«åš \filename{texmf.cnf} 的文件 -æ¥èŽ·çŸ¥æ‰€æœ‰çš„ \TeX æ ‘ä½ç½®ã€‚它会在一系列和其本身ä½ç½®ç›¸å…³çš„地方寻 -找这个文件。ä¸è¿‡å¦‚果直接在 \DVD 上è¿è¡Œï¼Œè¿™å¥—规则就ä¸é€‚用了:因为 -\DVD{} 是åªè¯»çš„,而æŸäº›è·¯å¾„åªèƒ½åœ¨å®‰è£…时确定下æ¥å¹¶å†™å…¥è¿™ä¸ªæ–‡ä»¶ï¼Œ -所以这个文件没法放在 \DVD{} 上,åªèƒ½å¦ç½®ä¸€å¤„。所以å¯èƒ½ä¼šéœ€è¦å®šä¹‰ -\envname{TEXMFCNF} æ¥å‘ŠçŸ¥ \TL{} 程åºè¯¥ä»Žå“ªå„¿æ‰¾åˆ°è¿™ä¸ª \filename{texmf.cnf} -文件。当然,如å‰æ‰€è¿° \envname{} 环境å˜é‡è¿˜æ˜¯è¦æ”¹çš„。 - -在安装结æŸæ—¶ï¼Œå®‰è£…程åºä¼šè¾“出一段告诉你如何设置 \envname{TEXMFCNF} -çš„ä¿¡æ¯ï¼Œå¦‚果你忽略了è¯ï¼Œå®ƒåº”该是 \dirname{$TEXMFSYSVAR/web2c},默认 -情况下就是 \dirname{/usr/local/texlive/2008/texmf-var/web2c}ï¼Œä½ éœ€è¦ -在 bash 下使用: -\begin{sverbatim} -TEXMFCNF=/usr/local/texlive/2008/texmf-var/web2c; export TEXMFCNF -\end{sverbatim} -或者 [t]csh 下使用: -\begin{sverbatim} -setenv TEXMFCNF /usr/local/texlive/2008/texmf-var/web2c -\end{sverbatim} - - -\subsubsection{\ConTeXt{} Mark IV} - -`è€ç‰ˆ'çš„ \ConTeXt{} 正常就应该能工作。新的 `Mark IV' \ConTeXt{} -则需è¦ä¸€äº›æ‰‹åŠ¨è®¾ç½®ã€‚å‚è§ -\url{http://wiki.contextgarden.net/Running_Mark_IV}。 - -\subsubsection{集æˆæœ¬åœ°ä¸Žä¸ªäººå®æ–‡ä»¶} -\label{sec:local-personal-macros} - -这在第~\ref{sec:texmftrees} 节已ç»é¡ºå¸¦æ到过了:\dirname{TEXMFLOCAL} -目录 (它的默认值是 \dirname{/usr/local/texlive/texmf-local} 或者 -\verb|C:\Program Files\texlive\texmf-local|) 这个目录就是为了存储 -é¢å‘整个系统的本地字体和å®æ–‡ä»¶çš„;而 \dirname{TEXMFHOME} 目录 (å…¶ -默认值是 \dirname{$HOME/texmf} 或者 \verb|%USERPROFILE%\texmf|), -则是用æ¥å­˜å‚¨ä¸ªäººçš„字体和å®æ–‡ä»¶çš„。这些目录应该在å„个 \TL{} -版本之间共享,æ¯ä¸ªç‰ˆæœ¬éƒ½èƒ½çœ‹åˆ°å…¶å†…容。因此ä¸åº”该把 -\dirname{TEXMFLOCAL} 改得和主 \TL{} 目录差别太大,å¦åˆ™æ–°çš„ç‰ˆæœ¬å‡ºæ¥ -ä½ åˆå¾—å†æ”¹ã€‚ - -对于这两个目录树而言,文件都应该放到åˆé€‚çš„å­ç›®å½•ä¸­ï¼Œå‚è§ -\url{http://tug.org/tds} 或者 \filename{texmf/web2c/texmf.cnf} -文件。比如一个 \LaTeX{} 文档类或者å®åŒ…应该放在 -\dirname{TEXMFLOCAL/tex/latex} 或者 \dirname{TEXMFHOME/tex/latex} -目录下,è¦ä¸ç„¶å°±æ˜¯å®ƒä»¬çš„一个å­ç›®å½•ä¸‹ã€‚ - -\dirname{TEXMFLOCAL} 目录需è¦ä¸€ä¸ªä¿æŒæ›´æ–°çš„文件åæ•°æ®åº“,å¦åˆ™æ–°å¢ž -的文件就无法找到。你å¯ä»¥ä½¿ç”¨ \cmdname{mktexlsr} 命令或者 -\prog{tlmgr} \GUI\ 模å¼ä¸‹ï¼Œconfiguration 选项å¡ä¸­çš„ -`Reinit file database' 按钮æ¥åˆ·æ–°å®ƒã€‚ - -\subsubsection{集æˆç¬¬ä¸‰æ–¹å­—体} - -ä¸å¹¸çš„是,这是一个éžå¸¸å¤æ‚而混乱的主题。除éžä½ å¯¹ \TeX{} 安装éžå¸¸ -熟悉,å¦åˆ™è¯·ä¸è¦æ¶‰è¶³è¿™ä¸ªé¢†åŸŸã€‚别忘了事先看看我们附带的字体,å‚è§ -第 \ref{sec:tl-fonts} 节。 - -\XeTeX 是一套å¯è¡Œçš„替代方案 (å‚è§ç¬¬ \ref{sec:tex-extensions} 节), -它能让你使用æ“作系统的字体而ä¸å¿…将它安装到 \TeX 中。 - -\subsection{测试安装是å¦æˆåŠŸ} -\label{sec:test-install} - -在完æˆä½ æ‰€éœ€è¦çš„ \TL{} 安装之åŽï¼Œè‡ªç„¶ä½ ä¼šå¸Œæœ›è¯•è¯•çœ‹å®ƒæ˜¯å¦æ­£å¸¸å·¥ä½œï¼Œå¥½è®©ä½ åœ¨ä»¥åŽèƒ½å¤Ÿ -创建优美的文档和字体。 - -这个å°èŠ‚给出了一些测试系统是å¦æ­£å¸¸å·¥ä½œçš„基本步骤。我们这里使用的是 Unix 命令,在 -\MacOSX{} å’Œ Windows 下你更å¯èƒ½æ˜¯ä½¿ç”¨å›¾å½¢ç•Œé¢è¿è¡Œè¿™äº›æµ‹è¯•çš„,ä¸è¿‡å…¶åŽŸç†å¹¶æ— ä¸åŒã€‚ - -\begin{enumerate} - -\item 首先确认你å¯ä»¥æ‰§è¡Œ \cmdname{tex} 程åºï¼š -\begin{alltt} -> \Ucom{tex -{}-version} -TeX 3.1415926 (Web2C 7.5.7) -kpathsea version 3.5.7 -... -\end{alltt} -如果返回的结果是 `command not found' 而éžç‰ˆæœ¬å’Œç‰ˆæƒä¿¡æ¯ï¼Œæˆ–者显示了 -旧版本的信æ¯ï¼Œå¾ˆæœ‰å¯èƒ½æ˜¯å› ä¸ºä½ æ²¡æœ‰æŠŠæ­£ç¡®çš„ \dirname{bin} å­ç›®å½•æ·»åŠ  -到 \envname{PATH} 中。å‚è§ç¬¬ \pageref{sec:env} 页关于设置环境å˜é‡ -的说明。 - -\item 处ç†ä¸€ä¸ªåŸºæœ¬çš„ \LaTeX{} 文件: -\begin{alltt} -> \Ucom{latex sample2e.tex} -This is pdfeTeXk, Version 3.141592... -... -Output written on sample2e.dvi (3 pages, 7484 bytes). -Transcript written on sample2e.log. -\end{alltt} -如果无法找到 \filename{sample2e.tex} 或其他什么文件,很å¯èƒ½æ˜¯å› ä¸ºæ—§çš„环境å˜é‡ -或é…置文件影å“了判断。我们建议你é‡ç½®æ‰€æœ‰ \TeX 相关的环境å˜é‡ç„¶åŽé‡è¯•ã€‚(ä½ å¯ä»¥ -让 \TeX{} 报告具体æœç´¢çš„路径,以便仔细分æžå‡ºé”™çš„原因。å‚è§ç¬¬ \pageref{sec:debugging} -页的``调试æ“作''一节以了解更多信æ¯ã€‚) - -\item å³æ—¶é¢„览结果: -\begin{alltt} -> \Ucom{xdvi sample2e.dvi} -\end{alltt} -(Windows ä¸‹ç±»ä¼¼çš„å‘½ä»¤å« \cmdname{dviout}。) 你应该å¯ä»¥çœ‹åˆ°åœ¨æ–°çª—å£ä¸­å‡ºçŽ°äº†ä¸€ç¯‡ -ä»‹ç» \LaTeX{} 基础的有趣文档。(如果你刚接触 \TeX\ 系统,还是值得一读的。) \cmdname{xdvi} -需è¦è¿è¡Œåœ¨ X 窗å£ç³»ç»Ÿä¸‹æ‰èƒ½å·¥ä½œï¼Œå¦‚果没有è¿è¡Œçª—å£çŽ¯å¢ƒæˆ– \envname{DISPLAY} 环境å˜é‡è®¾ç½® -错误,都会得到 \samp{Can't open display} è¿™å¥é”™è¯¯ä¿¡æ¯ã€‚ - -\item 创建用于打å°æˆ–显示的 \PS{} 文件: -\begin{alltt} -> \Ucom{dvips sample2e.dvi -o sample2e.ps} -\end{alltt} - -\item 创建 \acro{PDF} æ–‡ä»¶è€Œéž \dvi{}ï¼Œè¿™é‡Œé‡‡ç”¨ç›´æŽ¥å¤„ç† \filename{.tex} -文件输出 \acro{PDF} çš„æ–¹å¼ï¼š -\begin{alltt} -> \Ucom{pdflatex sample2e.tex} -\end{alltt} - -\item 预览 \acro{PDF} 文件: -\begin{alltt} -> \Ucom{gv sample2e.pdf} -\textrm{或:} -> \Ucom{xpdf sample2e.pdf} -\end{alltt} -ä¸å¹¸çš„是 \cmdname{gv} å’Œ \cmdname{xpdf} 现在都ä¸åŒ…å«åœ¨ \TL{} 中,你 -å¿…é¡»å•ç‹¬å®‰è£…它们。请分别å‚阅 \url{http://www.gnu.org/software/gv} å’Œ -\url{http://www.foolabs.com/xpdf}。(还有许多其他的 \acro{PDF} 查看器。) - -\item 除 \filename{sample2e.tex} 外å¯èƒ½ä¼šå¯¹ä½ æœ‰ç”¨çš„标准测试文件: - -\begin{ttdescription} -\item [small2e.tex] 比 \filename{sample2e} 更为简å•çš„文档,供你在é‡åˆ°é—®é¢˜ -æ—¶å°è¯•å‡å°‘输入的内容。 -\item [testpage.tex] 测试你的打å°æœºæ˜¯å¦å¸¦æœ‰é¢„设的å移é‡ã€‚ -\item [nfssfont.tex] 打å°ä¸€ä»½å­—体表格 (proofsheet) 以供测试。 -\item [testfont.tex] 用 plain \TeX{} 打å°å­—体表格。 -\item [story.tex] 最ç»å…¸çš„ (plain) \TeX{} 测试文件。在执行 -\samp{tex story.tex} 之åŽï¼Œä½ è¿˜è¦åœ¨ \code{*} æ示符下键入 \samp{\bs bye}。 -\end{ttdescription} -ä½ å¯ä»¥ç”¨ä¸Žæˆ‘ä»¬å¤„ç† \filename{sample2e.tex} 文件时相åŒçš„æ–¹å¼æ¥å¤„ç†è¿™äº›æ–‡ä»¶ã€‚ - -\end{enumerate} - -如果你还是个 \TeX{} 新手,或者在编辑 \TeX{} 或 \LaTeX{} 文档时需è¦å¸®åŠ©ï¼Œ -请访问 \url{http://tug.org/begin.html} 寻找引导性的资æºã€‚ - - -\section{网络安装} -\label{sec:netinstall} - -\TL{} 的设计å¯ä»¥ä½¿å®ƒåœ¨ä¸åŒçš„用户间共享,甚至å¯ä»¥åœ¨ç½‘络上ä¸åŒçš„系统间共 -享。在标准的目录结构下,ä¸éœ€è¦é…置固定的ç»å¯¹è·¯å¾„:\TL{} 程åºæ‰€éœ€è¦çš„æ–‡ -件都能通过都在这些程åºè‡ªèº«çš„相对路径找到。你å¯ä»¥åœ¨ -\filename{$TEXMFMAIN/web2c/texmf.cnf} é…置文件中看到实际的处ç†ï¼Œ -它包å«äº†ç±»ä¼¼ä¸‹é¢çš„内容: -\begin{verbatim} -TEXMFMAIN = $SELFAUTOPARENT/texmf -... -TEXMFLOCAL = $SELFAUTOPARENT/../texmf-local -\end{verbatim} -这就æ„味ç€ï¼Œå…¶å®ƒçš„系统或用户åªéœ€è¦æŠŠ \TL{} çš„å¯æ‰§è¡Œæ–‡ä»¶çš„ä½ç½®æ·»åŠ åˆ°å…¶ -系统的æœç´¢è·¯å¾„中å³å¯ã€‚ - -åŒç†ï¼Œä½ ä¹Ÿå¯ä»¥å…ˆæŠŠ \TL{} 安装在本地,然åŽå†æŠŠæ•´ä¸ªå®‰è£…目录转移到网络上。 - -当然,Windows 用户会有ä¸åŒçš„期望。\dirname{texmf-doc/source/texlive/texlive-common/w32client} -目录包å«äº†ä¸€ä¸ªæ ·ä¾‹è„šæœ¬ \filename{install-w32client},它å¯ä»¥ä¸ºå±€åŸŸç½‘上的 -\TL{} 安装产生é…置文件和èœå•å¿«æ·æ–¹å¼ã€‚它å¯ä»¥é€šè¿‡åœ¨ç›¸åŒç›®å½•çš„ -\filename{install-w32client.bat} 调用。 - -ä½ å¯ä»¥åœ¨ç¬¬~\ref{sec:kpathsea}~节中了解更多有关 \TL{} é…置和 -路径æœç´¢çš„内容。 - -\section{在 DVD 或 USB 上最具å¯ç§»æ¤æ€§åœ°è¿è¡Œ \protect\TL{}} -\label{sec:portable-unix} - -在第 \ref{sec:fromdvd} 节中介ç»çš„``从 \DVD{} è¿è¡Œ''选项å¯ä»¥ä½¿å‘行版在 -你的系统上很好地è¿è¡Œï¼Œä½†æ˜¯å¦‚果你在别人的机器上用éžç®¡ç†å‘˜å¸å·å·¥ä½œï¼Œ -那你就å¯èƒ½å¸Œæœ›ä½¿ç”¨å¯¹ç³»ç»Ÿæœ¬èº«çš„å½±å“最å°çš„è¿è¡Œæ–¹å¼ã€‚ - -在 \TL{} \DVD 的根目录,或者 \TK{} \DVD çš„ \dirname{texlive} å­ç›®å½•ä¸­ï¼Œ -有一个为 Unix 系统æ供的脚本 \filename{tl-portable} 和一个为 Windows -系统æ供的批处ç†æ–‡ä»¶ \filename{tl-portable.bat}。它们能开å¯ä¸€ä¸ªè®¾ç½®å¥½ -环境å˜é‡çš„终端或命令æ示符,在其中就能直接è¿è¡Œ \DVD 上的 \TL{}。 - -头一次执行时它会花点时间在 \dirname{~/.tlportable2008} 目录下生æˆä¸€äº› -文件,此åŽå°±å¯ä»¥åœ¨å¾ˆçŸ­çš„时间内å¯åŠ¨äº†ã€‚ - -而此时系统的其它程åºå¹¶ä¸çŸ¥é“ \TL{} 的存在,如果你需è¦è®©ä½ çš„文本编辑器 -使用这个 \TL,å¯ä»¥å†æ‰“开一个这样的 \filename{tl-portable} 会è¯æ¥ä½¿ç”¨ -该编辑器。 - -你还能通过 \filename{tl-portable} 在 \acro{USB} 驱动器上è¿è¡Œ \TL。 -在这ç§æƒ…况下,请 (至少) 把所有的顶层目录下的所有文件和 \dirname{bin}, -\dirname{texmf}, \dirname{texmf-dist} å’Œ \dirname{tlpkg} 下的所有内容 -å¤åˆ¶åˆ° USB 驱动器上。这会花一定的时间。如果你把它å¤åˆ¶åˆ°ä¸€ä¸ª \acro{FAT}32 -æ ¼å¼çš„ \acro{USB} 驱动上,请ä¿è¯å¤åˆ¶æ“作是跟踪 (dereference) 所有的 -符å·é“¾æŽ¥åˆ°å®žé™…æ•°æ®æ–‡ä»¶çš„ (\code{cp -L})。è¿è¡Œæ—¶éƒ½ä¼šæŸ¥æ‰¾å¹¶ä½¿ç”¨é©±åŠ¨å™¨ä¸Š -çš„ \dirname{texmf-local} 目录。 - -然åŽä½ å°±å¯ä»¥åœ¨é©±åŠ¨å™¨çš„根目录下åƒä¸Šé¢é‚£æ ·è¿è¡Œ \filename{tl-portable} -了。此时脚本能判断出这个驱动是å¯å†™çš„,并把产生的文件写到这里。 -ä¸ºäº†æ–¹ä¾¿èµ·è§ (比如你想把它æ供给别人),你也å¯ä»¥æŠŠé©±åŠ¨å™¨ä¸Šçš„最终内容 -刻录回到 \DVD{} 上。 - -\section{\cmdname{tlmgr}: 管ç†ä½ çš„安装} -\label{sec:tlmgr} - - -\begin{figure}[tb] -\tlpng{tlmgr-gui}{\linewidth} -\caption{图形界é¢æ¨¡å¼è¿è¡Œçš„ \prog{tlmgr} 程åºã€‚ -安装包/集åˆ/方案仅在按下 `Load' 按钮åŽæ˜¾ç¤ºã€‚}\label{fig:tlmgr-gui} -\end{figure} - -\begin{figure}[tb] -\tlpng{tlmgr-config}{\linewidth} -\caption{图形界é¢æ¨¡å¼çš„ \texttt{tlmgr}: Configuration 选项å¡}\label{fig:tlmgr-config} -\end{figure} - -安装程åºä¼šè£…ä¸Šä¸€ä¸ªå« \prog{tlmgr} 的程åºï¼Œå®ƒå¯ä»¥ç”¨æ¥ç®¡ç†å®‰è£…åŽçš„ -ç³»ç»Ÿã€‚åƒ \prog{updmap}, \prog{fmtutil} å’Œ \prog{texconfig} è¿™äº›ç¨‹åº -ä»ç„¶åŒ…å«åœ¨å‘行版中,而且在将æ¥ä¹Ÿä¸ä¼šå‰”除,但是 \prog{tlmgr} 是一个 -优选的界é¢ã€‚它的功能包括: - -\begin{itemize*} -\item 列出方案 (scheme),集åˆå’Œå®‰è£…包; -\item 安装ã€å‡çº§ã€å¤‡ä»½ã€æ¢å¤ã€å¸è½½è½¯ä»¶åŒ…,并且能自动计算ä¾èµ–关系; -\item 查找软件包; -\item 列出和添加å¯æ‰§è¡Œæ–‡ä»¶çš„架构; -\item 改å˜å®‰è£…选项,比如纸张大å°å’Œæºæ–‡ä»¶ä½ç½® (å‚è§ç¬¬~\ref{sec:location}~节)。 -\end{itemize*} -\textit{警告:} \prog{tlmgr} 并ä¸ä¸ºåœ¨ \DVD 中è¿è¡Œè®¾è®¡ï¼Œä¹Ÿä»Žæœªåšè¿‡ç›¸ -关的测试。 - -\subsection{图形界é¢æ¨¡å¼çš„ \cmdname{tlmgr}} -\prog{tlmgr} å¯ä»¥ç”¨ä»¥ä¸‹å‘½ä»¤ä»¥å›¾å½¢æ¨¡å¼å¯åŠ¨ï¼š -\begin{alltt} -> \Ucom{tlmgr -gui} -\end{alltt} -Windows 下å¯ä»¥é€šè¿‡å¼€å§‹èœå•ï¼š\texttt{开始},\texttt{程åº}, -\texttt{TeX Live 2008},\texttt{TeX Live Manager}。 -在å‡å®šå®‰è£…包æºæ˜¯æœ‰æ•ˆä¸”å¯åŠçš„情况下,在点击 `Load' 以åŽï¼Œå®ƒä¼šåˆ—出 -所有å¯èŽ·å–的或已安装 (å‰é¢ç”¨ `(i)' 表示) 的软件包。 - -图~\ref{fig:tlmgr-config} 展示了é…置选项å¡ã€‚ - -\subsection{\cmdname{tlmgr} 命令行使用示例} - -下é¢çš„例å­ä¼šä»Žä¸€ä¸ªéžé»˜è®¤çš„地å€å®‰è£…一些包,其中包括一个新的`引擎'。 - -\begin{alltt} -> \Ucom{tlmgr -location http://172.16.18.1/tldev install collection-xetex xkeyval} -\end{alltt} -它会产生下é¢çš„输出: -\begin{fverbatim} -install: collection-xetex -install: arabxetex -install: euenc -install: bidi -install: fontspec -install: fontwrap -install: ifxetex -install: philokalia -install: polyglossia -install: xecyr -install: xecyr.i386-linux -install: xepersian -install: xetex -install: xetexconfig -install: xetex.i386-linux -running post install action for xetex -install: xetex-def -install: xetex-pstricks -install: xetexfontinfo -install: xltxtra -install: xunicode -install: xkeyval -running mktexlsr -mktexlsr: Updating /usr/local/texlive/2008/texmf/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-config/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-dist/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-doc/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/../texmf-local/ls-R... -mktexlsr: Updating /usr/local/texlive/2008/texmf-var/ls-R... -mktexlsr: Done. -regenerating fmtutil.cnf -running fmtutil-sys --missing -... -Transcript written on xelatex.log. -fmtutil: /usr/local/texlive/2008/texmf-var/web2c/xetex/xelatex.fmt installed. -\end{fverbatim} -如你所è§ï¼Œ\prog{tlmgr} 会安装所有ä¾èµ–的包,也会处ç†æ‰€æœ‰åŒ…括刷新文件å -æ•°æ®åº“å’Œé‡æ–°ç”Ÿæˆæ ¼å¼æ–‡ä»¶åœ¨å†…的所有必è¦çš„安装åŽå·¥ä½œã€‚(åœ¨è¿™é‡Œï¼Œæˆ‘ä»¬ç”Ÿæˆ -了新的 \XeTeX\ æ ¼å¼æ–‡ä»¶)。 - -下é¢è¿™ä¸ªä¾‹å­å®‰è£…了一个新的语言支æŒï¼Œä¹Ÿä¼šè§¦å‘æ ¼å¼æ–‡ä»¶çš„é‡æ–°ç”Ÿæˆã€‚ -\begin{alltt} -> \Ucom{tlmgr install collection-langdutch} -\end{alltt} -如果想得到安装包的说明: -\begin{alltt} -> \Ucom{tlmgr show collection-wintools} -\end{alltt} -会产生 -\begin{fverbatim} -Package: collection-wintools -Category: Collection -ShortDesc: Windows support programs -LongDesc: Utilities for Windows, since they are not readily available there: - gzip, chktex, jpeg2ps, unzip, wget, xpdf. -Installed: Yes -\end{fverbatim} -把你的整个安装更新到最新版本: -\begin{alltt} -> \Ucom{tlmgr update -all} -\end{alltt} -如果你觉得这样太冒险了,å¯ä»¥å…ˆå°è¯• -\begin{alltt} -> \Ucom{tlmgr update -all -dry-run} -\end{alltt} -或 -\begin{alltt} -> \Ucom{tlmgr update -list} -\end{alltt} -程åºçš„完整文档: -\begin{alltt} -> \Ucom{tlmgr -help} -\end{alltt} - -\section{有关 Windows å¹³å°çš„说明} -\label{sec:windows} - -\TL{} 拥有å¯è¿è¡ŒäºŽ Windows å’Œ Unix å¹³å°çš„å•ä¸€å®‰è£…程åºã€‚当然,åªæœ‰åœ¨æ”¾å¼ƒå¯¹ -较è€ç‰ˆæœ¬ Windows 的支æŒçš„情况下,这æ‰æˆä¸ºå¯èƒ½ã€‚因此,现在 \TL{} åªèƒ½å®‰è£… -于 Windows 2000 或更新的版本。 - - -\subsection{针对 Windows 的特å¾} -\label{sec:winfeatures} - -在 Windows 下,安装程åºé¢å¤–地åšäº†ä»¥ä¸‹ä¸€äº›äº‹æƒ…: -\begin{description} -\item[èœå•ä¸Žå¿«æ·æ–¹å¼ã€‚] 在开始èœå•ä¸ŠåŠ å…¥äº†æ–°çš„`\TL{}'程åºèœå•ï¼Œä¸»è¦æ˜¯ä¸€äº› -\GUI{} ç¨‹åº (如 \prog{tlmgr}ã€\prog{texdoctk}ã€PS\_View PostScript 预览程 -åº) 和一些文档的èœå•ã€‚PS\_View 还有一个桌é¢å¿«æ·æ–¹å¼ï¼Œå¯ä»¥ä½œä¸ºæ‹–放 PostScript -文件的目标。 -\item[自动设置环境å˜é‡ã€‚] ä¸å†éœ€è¦æ‰‹åŠ¨çš„é…置步骤。 -\item[å安装程åºã€‚] 安装程åºä¸º \TL{} 创建了`添加/删除程åº'æ¡ç›®ã€‚这与 -\prog{tlmgr} 的删除按钮相对应。 -\end{description} - -\subsection{附加的软件} - -\begin{figure}[tb] -\tlpng{psview}{.6\linewidth} -\caption{PS\_View:å¯ä»¥èŽ·å¾—很高的放大å€æ•°ï¼}\label{fig:psview} -\end{figure} - -为了使安装更加完整,\TL{} 需è¦æ”¯æŒé‚£äº› Windows 机器上ä¸å¸¸è§çš„软件包。 -\TL{} æ供了以下缺失的部分: -\begin{description} -\item[Perl å’Œ Ghostscript。] 由于 Perl å’Œ Ghostscript çš„é‡è¦æ€§ï¼Œ\TL{} -æ供了这些程åºçš„`éšè—'æ‹·è´ã€‚需è¦è¿™äº›è½¯ä»¶æ”¯æŒçš„ \TL{} 程åºçŸ¥é“它们的ä½ç½®ï¼Œ -但它们ä¸ä¼šé€šè¿‡çŽ¯å¢ƒå˜é‡å’Œæ³¨å†Œè¡¨è®¾ç½®æ¥æš´éœ²æ‰€åœ¨çš„ä½ç½®ã€‚它们ä¸æ˜¯å®Œæ•´çš„å‘è¡Œ -版本,也ä¸ä¼šä¸Žä»»ä½• Perl 或 Ghostscript 系统安装程åºå†²çªã€‚ -\item[命令行工具。] 与常è§çš„ \TL{} 二进制文件一起,安装了一些常è§çš„ -Unix 命令行工具的 Windows 移æ¤ç‰ˆæœ¬ã€‚它们包括 \cmdname{gzip}〠-\cmdname{chktex}ã€\cmdname{jpeg2ps}ã€\cmdname{unzip}ã€\cmdname{wget} -å’Œæ¥è‡ªäºŽ \cmdname{xpdf} 套装中的一些命令行工具。(虽然 \cmdname{xpdf} -æµè§ˆå™¨æœ¬èº«æ²¡æœ‰ Windows 版本,但 Sumatra \acro{PDF} æµè§ˆå™¨æ˜¯åŸºäºŽå®ƒçš„: -\url{http://blog.kowalczyk.info/software/sumatrapdf}。) -\item[\texttt{fc-cache}。] 有助于 \XeTeX{} 更有效率地处ç†å­—体。 -\item[PS\_View。] åŒæ—¶å®‰è£…的还有 PS\_View,一个具有自由许å¯è¯çš„全新的 -PostScript æµè§ˆå™¨ï¼›è§å›¾~\ref{fig:psview}。 -\end{description} -\begin{description} - \item[\texttt{support} 目录。] 在 \ref{sec:tld} 节æ到过它。这个目录包括å„ç§åœ¨ - \TeX{} 使用过程中éžå¸¸æœ‰ç”¨çš„软件,主è¦æ˜¯ä¸€äº› \TeX{} 文件编辑器和 \TeX{} - å‰ç«¯ã€‚这具目录中的软件ä¸å—安装程åºå½±å“。åŒæ—¶ï¼Œè¿™ä¸ªç›®å½•ä¸­è¿˜åŒ…括 \dvi{} - 预览器 \cmdname{dviout}ï¼›å‚è§ä¸‹ä¸€èŠ‚的介ç»ã€‚ -\end{description} - -\subsection{Dviout 预览器} - -ä¸å¹¸çš„是,\TL{} å‘行版没有为 Windows 预装 \dvi{} 预览器。ä¸è¿‡ï¼Œä½ å¯ä»¥ä»Ž -\path{support/dviout/} 目录安装 Toshio Oshima æ供的 -\prog{dviout}。这个目录下包括了一份简短的 \filename{README},æ述了如何为 -\TL{} 安装和é…ç½® \prog{dviout}。请在安装å‰ä»”细阅读。 - -当你第一次使用 \cmdname{dviout} 预览文件时,因为没有安装å±å¹•æ˜¾ç¤ºå­—体,它 -将生æˆå­—体。一段时间åŽï¼Œä½ æ‰€ä½¿ç”¨çš„大部分字体都将生æˆï¼ŒéšåŽï¼Œä½ å°†å¾ˆå°‘å†çœ‹ -到生æˆå­—体的窗å£ã€‚ä½ å¯ä»¥ä»Ž (éžå¸¸æ£’çš„) 在线帮助中获得更加详细的信æ¯ã€‚ - -\subsection{å¯ä¸‹è½½çš„附加软件的链接} - -ä½ å¯èƒ½è€ƒè™‘安装的其它工具的下载链接: -\begin{description} -\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} -\item[Perl] \url{http://www.activestate.com/},辅助的包å¯ä»¥ä»Ž \acro{CPAN} -下载,\url{http://www.cpan.org/} -\item[ImageMagick] \url{http://www.imagemagick.com},用于图åƒå¤„ç†åŠè½¬æ¢ -\item[NetPBM] \url{http://netpbm.sourceforge.net/},åŒæ ·ç”¨äºŽå›¾åƒ - -\item[é¢å‘ \TeX 的编辑器] 有很大选择余地,通常是一个用户å好的问题。下 -é¢æ˜¯ä¸€äº›ç²¾é€‰çš„编辑器,当然,没有ä¾ç‰¹å®šé¡ºåºæŽ’列: - \begin{itemize*} - \item \cmdname{GNU Emacs} 有 Windows 下å¯ç”¨çš„原生版本,å‚è§ \url{http://www.gnu.org/software/emacs/windows/ntemacs.html}。 - \item 带 Auc\TeX{} 支æŒçš„ \cmdname{Emacs} çš„ Windows 版本å¯åœ¨ \TL{} 下的 \path{support} 目录下找到;它的主页是 \url{http://www.gnu.org/software/auctex}。 - \item \cmdname{WinShell} å¯ä»¥åœ¨ \TL{} çš„ \path{support} 目录下找到。它的主页在 \url{http://www.winshell.de}。 - \item \cmdname{WinEdt} 是一个共享软件,å¯ä»¥ä»Ž \url{http://www.winedt.com} 获得。 - \item \cmdname{Vim} 是自由软件,å¯ä»¥ä»Ž \url{http://www.vim.org} 获得。 - \item TeXnicCenter 是自由软件,å¯ä»¥ä»Ž \url{http://www.toolscenter.org} å’Œ pro\TeX{}t å‘行版中获得。 - \item \cmdname{LEd} å¯ä»¥ä»Ž \url{http://www.ctan.org/support/LEd} 获得。 - \item \cmdname{SciTE} å¯ä»¥ä»Ž \url{http://www.scintilla.org/SciTE.html} 获得。 - \end{itemize*} -\end{description} - - -\subsection{User Profile 目录相当于主目录} -\label{sec:winhome} - -Windows 下对应于 Unix 下的主目录的是 \verb|%USERPROFILE%|。在 Windows XP -å’Œ Windows 2000 下,它通常ä½äºŽ \verb|C:\Documents and Settings\|ï¼› -在 Windows Vista 下是 \verb|C:\Users\|。通常情况下,在 -\filename{texmf.cnf} 文件和 \KPS{} 中,\verb|~| 在 Windows å’Œ Unix 下å‡å¯ä»¥ -进行åˆé€‚的展开。 - - -\subsection{Windows 注册表} -\label{sec:registry} - -Windows 将几乎所有的é…置数æ®å­˜æ”¾åœ¨æ³¨å†Œè¡¨ä¸­ã€‚注册表是包å«å‡ ä¸ªä¸»æ”¯çš„一系 -列分层组织的分支。对于安装的程åºè€Œè¨€ï¼Œæœ€é‡è¦çš„主支是 \path{HKEY_CURRENT_USER} -å’Œ \path{HKEY_LOCAL_MACHINE},通常简写为 \path{HKCU} å’Œ \path{HKLM}。注册表的 -\path{HKCU} 部分ä½äºŽç”¨æˆ·çš„主目录 (å‚è§ \ref{sec:winhome} 节)。\path{HKLM} -通常ä½äºŽ Windows 目录的å­ç›®å½•ä¸­ã€‚ - -在æŸäº›æƒ…况下,系统信æ¯å¯ä»¥ä»ŽçŽ¯å¢ƒå˜é‡èŽ·å¾—,但对于其它信æ¯ï¼Œå¦‚å¿«æ·æ–¹å¼çš„ä½ç½®ï¼Œ -则需è¦è®¿é—®æ³¨å†Œè¡¨ã€‚设置永久环境å˜é‡ä¹Ÿéœ€è¦è®¿é—®æ³¨å†Œè¡¨ã€‚ - - -\subsection{Windows æƒé™} -\label{sec:winpermissions} - -在较新的 Windows 版本中,普通用户与管ç†å‘˜æ˜¯æœ‰åŒºåˆ«çš„。åªæœ‰ç®¡ç†å‘˜èƒ½è‡ªç”±è®¿é—® -整个æ“作系统。尽管如此,在实际中,作为å—é™ç”¨æˆ·ä¸Žæ™®é€šç”¨æˆ·ï¼Œä½ æœ€èƒ½å¥½èƒ½å¤Ÿæ -述所处的用户类别:作为一个管ç†å‘˜æ˜¯æƒ¯ä¾‹ï¼Œè€Œä¸æ˜¯ç‰¹ä¾‹ã€‚无论如何,我们努力使得 -\TL{} 的安装ä¸éœ€è¦ç®¡ç†å‘˜æƒé™ã€‚ - -如果用户是管ç†å‘˜èº«ä»½ï¼Œå®‰è£…程åºå°†ä¼šä¸ºæ‰€æœ‰ç”¨æˆ·å»ºç«‹å¿«æ·æ–¹å¼ï¼Œå¹¶ä¸”修改 -系统环境å˜é‡ã€‚å¦åˆ™ï¼Œå®‰è£…程åºåªä¸ºå½“å‰ç”¨æˆ·åˆ›å»ºå¿«æ·æ–¹å¼ï¼Œå¹¶æ”¹å˜ç”¨æˆ·çŽ¯å¢ƒå˜é‡ã€‚ -作为管ç†å‘˜ï¼Œå¦‚果倾å‘于使用用户级设置,å¯ä»¥ä½¿ç”¨ \prog{install-tl} çš„ -\optname{non-admin} 选项。 - -无论管ç†å‘˜çŠ¶æ€å¦‚何,\TL{} 预设的默认根目录总是ä½äºŽ \verb|%PROGRAMFILES%| -下。对于当å‰ç”¨æˆ·å®‰è£…程åºæ€»æ˜¯è¦æµ‹è¯•ï¼Œæ ¹ç›®å½•æ˜¯å¦å¯å†™ã€‚ - -如果用户ä¸æ˜¯ç®¡ç†å‘˜ï¼Œå¹¶ä¸” \TeX{} å·²ç»å­˜åœ¨æœç´¢è·¯å¾„中,则å¯èƒ½ä¼šå‡ºçŽ°é—®é¢˜ã€‚因为有效路径是由系统路径åŽæŽ¥ç”¨æˆ·è·¯å¾„组æˆï¼Œæ–°å®‰è£…çš„ \TL{} å¯èƒ½æ°¸è¿œä¸ä¼šä¼˜å…ˆè¿è¡Œã€‚在这ç§æƒ…况下,一个å˜é€šçš„方案是,安装程åºä¸ºå‘½ä»¤æ示符创建快æ·æ–¹å¼ã€‚在这个快æ·æ–¹å¼ä¸­ï¼Œæ–°å®‰è£…çš„ \TL{} çš„å¯æ‰§è¡Œç›®å½•è¢«é¢„设于本地的æœç´¢è·¯å¾„中。当从这个快æ·æ–¹å¼å¯åŠ¨å‘½ä»¤è¡Œä»»åŠ¡æ—¶ï¼Œä¾¿å¯ä»¥ä½¿ç”¨æ–°çš„ \TL{}。 - - -\section{Web2C 用户指å—} - -\Webc{} 是一整套 \TeX{} 相关程åºçš„集åˆï¼š\TeX{} 本身ã€\MF{}ã€\MP{}ã€\BibTeX{}, -等等。它是 \TL{} 的核心。\Webc{} 的主页åŠæœ€æ–°çš„手册等都在 -\url{http://tug.org/web2c}。 - -我们简å•çš„介ç»ä¸€ä¸‹å®ƒçš„历å²ï¼šæœ€æ—©å®ƒæ˜¯ç”± Tomas Rokicki 在 1987 年实现的,他开å‘了第一套 -å°† \TeX{} 系统的代ç è½¬æ¢ä¸º C 语言代ç çš„系统,基于的是 Unix 下 change files -的原ç†ï¼Œchange files çš„ -工作是 Howard Trickey å’Œ Pavel Curtis 完æˆçš„。Tim Morgan åŽæ¥æˆä¸ºäº†è¿™å¥—系统的维护 -者,在这期间,软件的å称改为了 Web-to-C\@。在许多其他贡献者的帮助下,1990 å¹´ Karl Berry -接手了这个工作,到 1997 年,他把这项工作交给了 Olaf Weber。Olaf Weber 在 2006 å¹´åˆ -把这项工作交还给了 Karl。 - -\Webc{} 系统å¯ä»¥åœ¨ Unixã€32 ä½ Windows 系统ã€\MacOSX{} 和其他的一些æ“作系统下è¿è¡Œã€‚ -它使用的是 Knuth 用 \web{} 文学编程语言编写的 \TeX{} 和其他基本程åºçš„原始代ç ï¼Œå°†å…¶è½¬æ¢ä¸º C -æºç ã€‚用这ç§æ–¹æ³•å¤„ç†çš„核心的 \TeX{} 程åºåŒ…括: - -\begin{cmddescription} -\item[bibtex] 维护å‚考文献。 -\item[dmp] 从 \cmdname{troff} æ ¼å¼è½¬æ¢ä¸º MPX (\MP{} 图片)。 -\item[dvicopy] 展开 \dvi{} 中的虚拟字体 (virtual font) 引用。 -\item[dvitomp] å°† \dvi{} 转æ¢ä¸º MPX (MetaPost 图片)。 -\item[dvitype] å°† \dvi{} 转æ¢ä¸ºå¯è¯»æ–‡æœ¬ã€‚ -\item[gftodvi] ç”Ÿæˆ Generic æ ¼å¼å­—体的 proofsheet。 -\item[gftopk] å°† Generic æ ¼å¼å­—体转æ¢ä¸º packed æ ¼å¼å­—体。 -\item[gftype] å°† Generic æ ¼å¼å­—体转æ¢ä¸ºå¯è¯»æ–‡æœ¬ã€‚ -\item[makempx] 排版 \MP{} label。 -\item[mf] 创建字体。 -\item[mft] 以漂亮的方å¼æŽ’版输出 \MF{} 的代ç ã€‚ -\item[mpost] 创建技术性æ’图。 -\item[mpto] 展开 \MP{} çš„ label。 -\item[newer] 比较文件的修改时间。 -\item[patgen] 创建断字规则文件。 -\item[pktogf] å°† Packed æ ¼å¼å­—体转æ¢ä¸º generic æ ¼å¼å­—体。 -\item[pktype] å°† PK æ ¼å¼è½¬æ¢ä¸ºå¯è¯»çš„文本。 -\item[pltotf] 将纯文本的 property list 转æ¢ä¸º TFM æ ¼å¼ã€‚ -\item[pooltype] 显示 \web{} çš„ pool 文件。 -\item[tangle] å°† \web{} 转æ¢ä¸º Pascal 代ç ã€‚ -\item[tex] 排版。 -\item[tftopl] å°† TFM æ ¼å¼è½¬æ¢ä¸ºçº¯æ–‡æœ¬çš„ property list æ ¼å¼ã€‚ -\item[vftovp] 将虚拟字体格å¼è½¬æ¢ä¸º virtual property list æ ¼å¼ã€‚ -\item[vptovf] å°† virtual property list æ ¼å¼è½¬æ¢ä¸ºè™šæ‹Ÿå­—体格å¼ã€‚ -\item[weave] å°† \web{} 转æ¢ä¸º \TeX。 -\end{cmddescription} - -\noindent 这些程åºçš„详细功能和调用语法都在其å„自软件包的文档中有说明,在 \Webc{} çš„æ–‡ -档中也有相关介ç»ã€‚ä¸è¿‡ï¼Œæœ‰äº›è§„则对所有这些程åºéƒ½æ˜¯é€šç”¨çš„,了解这些规则有助于你更好的使用 -\Webc{}。 - -所有的程åºéƒ½æŽ¥å—这些 \GNU 标准的选项: -\begin{ttdescription} -\item[-{}-help] 显示基本使用说明。 -\item[-{}-verbose] 显示详细的执行过程。 -\item[-{}-version] 显示版本信æ¯ï¼Œç„¶åŽé€€å‡ºã€‚ -\end{ttdescription} - -所有的 \Webc{} 程åºå‡ä½¿ç”¨ \KPS{} (\url{http://tug.org/kpathsea}) 路径æœç´¢åº“æ¥æŸ¥æ‰¾æ–‡ä»¶ï¼Œ -这套库结åˆçŽ¯å¢ƒå˜é‡å’Œé…置文件的 -使用æ¥ä¼˜åŒ–å¤§é‡ \TeX{} 文件的æœç´¢ã€‚\Webc{} å¯ä»¥åœ¨å¤šäºŽä¸€å¥—的目录树下执行查找,这å¯ä»¥æ–¹ -便维护类似 \TeX{} 标准å‘行版和本地版本的扩展这样两套目录树。为了优化æœç´¢çš„速度,æ¯ä¸ªç›® -录树的顶层目录下都有一个 \file{ls-R} 文件,这个文件里包å«äº†æ‰€æœ‰æ­¤ç›®å½•ä¸‹æ–‡ä»¶çš„å称和对 -应的相对路径。 - -\subsection{Kpathsea 路径æœç´¢} -\label{sec:kpathsea} - -我们首先介ç»ä¸€ä¸‹ \KPS{} 库的的通用路径æœç´¢æ–¹å¼ã€‚ - -我们将目录å称称作\emph{路径元素},而把用冒å·æˆ–者分å·åˆ†éš”的路径元素列表称 -作\emph{æœç´¢è·¯å¾„}。æœç´¢è·¯å¾„å¯èƒ½æ˜¯è®¸å¤šç§æ¥æºçš„组åˆï¼Œæ¯”如在 \samp{.:/dir} 路径下 -æœç´¢ \samp{my-file} 这个文件,\KPS{} å°†é€ä¸ªå°è¯•è·¯å¾„中的æ¯ä¸ªå…ƒç´ ï¼šé¦–先是 -\file{./my-file},然åŽæ˜¯ \file{/dir/my-file},并返回找到的第一个结果 (或者 -也å¯ä»¥è¿”回所有的结果)。 - -为了符åˆæ‰€æœ‰æ“作系统下的习惯,\KPS{} åœ¨éž Unix 系统下使用的路径分隔符å¯èƒ½ä¸æ˜¯å†’å· -(\samp{:}) å’Œæ–œæ  (\samp{/})。 - -在检查一个具体的路径元素 \var{p} 时,\KPS{} 首先检查是å¦æœ‰ç¬¦åˆ \var{p} 的文件å -æ•°æ®åº“ (è§ç¬¬ \pageref{sec:filename-database} 页的``文件åæ•°æ®åº“'') 存在,也就是说, -是å¦æœ‰æ•°æ®åº“æ­£å¥½å¯¹åº”ç€ \var{p} 的一个å‰ç¼€ã€‚如果存在,就在数æ®åº“中寻找符åˆçš„路径åŽç¼€ã€‚ - -è¦æ˜¯æ²¡æœ‰è¿™ç§æ•°æ®åº“存在ã€åˆæˆ–者所有的数æ®åº“都ä¸èƒ½å’ŒæŒ‡å®šçš„路径å‰ç¼€åŒ¹é…上ã€å†æˆ–者找到的数 -æ®åº“里没有进一步的匹é…,就è¦æœç´¢æ–‡ä»¶ç³»ç»Ÿäº† (å‰æ是我们没在路径å‰åŠ ä¸Š \samp{!!} ï¼Œåˆ -或者æœç´¢æ—¶å°±æŒ‡å®šäº†è¿™æ˜¯ä¸€æ¬¡``必定存在 (must exist)''åž‹çš„æœç´¢æ–¹å¼)。此时 \KPS{} å°† -æ ¹æ®è·¯å¾„元素构建一个需è¦æ£€æŸ¥çš„目录列表,é€ä¸ªå°è¯•è¿™äº›ç›®å½•ï¼Œè¯•å›¾æ‰¾åˆ°æŒ‡å®šçš„文件。 - -æœç´¢ \samp{.vf} 文件和 \TeX{} 用 \cs{openin} 命令读入的文件时,会指定``文件必 -定存在 (must exist)''这个选项。而有些文件 (比如 \file{cmr10.vf}) å¯èƒ½ä¸å­˜åœ¨ï¼Œ -花费时间在ç£ç›˜ä¸Šå¯¹å®ƒè¿›è¡Œæœç´¢æ˜¯ä¸å€¼å¾—的。因此,如果你安装了新的 \samp{.vf} 文件åŽæ²¡æœ‰ -æ›´æ–° \file{ls-R},那这个文件将永远找ä¸åˆ°ã€‚æœç´¢æ—¶ä¼šä¼˜å…ˆåœ¨æ•°æ®åº“寻找,然åŽå†åŽ»æœç´¢ç£ç›˜ã€‚ -一旦找到了就立å³åœæ­¢æœç´¢ï¼Œè¿”回结果。 - -尽管最简å•ä¹Ÿæœ€å¸¸è§çš„路径元素是目录å称,\KPS{} æœç´¢çš„路径里还是å¯ä»¥ä½¿ç”¨å…¶ä»–é¢å¤–功能的: -多层默认值,环境å˜é‡å称ã€é…置文件值ã€ç”¨æˆ·ä¸»ç›®å½•ï¼Œä»¥åŠé€’å½’å¼å­ç›®å½•æŸ¥æ‰¾ã€‚所以我们把 \KPS{} -å°†æœç´¢è·¯å¾„å˜æ¢ä¸ºä¸€ä¸ªæˆ–多个基本目录å的过程称为\emph{展开}è·¯å¾„å…ƒç´ çš„è¿‡ç¨‹ã€‚å±•å¼€çš„æ–¹å¼ -按执行的顺åºåœ¨åŽç»­å°èŠ‚里有å™è¿°ã€‚ - -注æ„,如果æœç´¢çš„文件给出了ç»å¯¹è·¯å¾„或者明确的相对路径,å³ä»¥ \samp{/} 或 \samp{./} 或 -\samp{../} 起始,\KPS{} å°†åªæ£€æŸ¥è¯¥æ–‡ä»¶æ˜¯å¦å­˜åœ¨ã€‚ - -\ifSingleColumn -\else -\begin{figure*} -\verbatiminput{examples/ex5.tex} -\setlength{\abovecaptionskip}{0pt} - \caption{一份示例性的é…置文件的例å­} - \label{fig:config-sample} -\end{figure*} -\fi - -\subsubsection{路径的æ¥æº} -\label{sec:path-sources} - -æœç´¢è·¯å¾„å¯èƒ½æ¥è‡ªè®¸å¤šåœ°æ–¹ï¼Œ\KPS{} 是按照下é¢çš„顺åºæŸ¥æ‰¾çš„: - -\begin{enumerate} -\item - 用户设置的环境å˜é‡ï¼Œä¾‹å¦‚ \envname{TEXINPUTS}\@。以 . 连接æŸä¸ªç¨‹åºå称的环境å˜é‡ -有更高的优先级,比如若正在è¿è¡Œçš„程åºæ˜¯ \samp{latex},那 \envname{TEXINPUTS.latex} -将比 \envname{TEXINPUTS} 优先级更高。 -\item - 专门针对æŸä¸ªç¨‹åºçš„é…置文件,比如 \cmdname{dvips} çš„ \file{config.ps} 里出现 -\samp{S /a:/b} 这样一行。 -\item \KPS{} é…置文件 \file{texmf.cnf},包å«ç±»ä¼¼ - \samp{TEXINPUTS=/c:/d} 这样的一行 (å‚è§ä¸‹é¢çš„解释)。 -\item 编译时的缺çœå€¼ã€‚ -\end{enumerate} -\noindent ä½ å¯ä»¥é€šè¿‡è°ƒè¯•é€‰é¡¹çœ‹åˆ°æ‰€æœ‰çš„这些值 (å‚è§ç¬¬ \pageref{sec:debugging} 页的 -``调试æ“作'')。 - -\subsubsection{é…置文件} - -\begingroup\tolerance=3500 -\KPS{} 读入\emph{è¿è¡Œæ—¶é…置文件} \file{texmf.cnf} æ¥èŽ·å¾—æœç´¢è·¯å¾„和其他定义。 -而这个 \file{texmf.cnf} 存放的路径则是在 \envname{TEXMFCNF} å˜é‡é‡Œå®šä¹‰çš„, -默认是在 \file{texmf/web2c} 目录下。æœç´¢è·¯å¾„里\emph{所有的} \file{texmf.cnf} -文件都会被读入,而先读入的优先级更高。所以,如果æœç´¢è·¯å¾„是 \verb|.:$TEXMF|,那么 -文件 \file{./texmf.cnf} 里é¢çš„值è¦æ¯” \verb|$TEXMF/texmf.cnf| 里边的优先。 -\endgroup - -\begin{itemize} -\item - 以 \code{\%} 表示å•è¡Œæ³¨é‡Šã€‚ -\item - 忽略空行。 -\item - 行末的 \bs{} 作为连接符,å³æŠŠä¸‹ä¸€è¡Œç›´æŽ¥æŽ¥ä¸Šã€‚但ä¿ç•™ä¸‹ä¸€è¡Œè¡Œé¦–的空白。 -\item - 所有剩余的行格å¼å¦‚下: -\begin{alltt} - \var{variable}[.\var{progname}] [=] \var{value} -\end{alltt}% - \samp{=} å·å’Œç©ºç™½éƒ½æ˜¯å¯é€‰çš„。 -\item - \ttvar{variable} (å˜é‡) å…许包å«ä»»ä½•å­—符,除空白ã€\samp{=}ã€\samp{.} - 之外。ä¸è¿‡åªç”¨ \samp{A-Za-z\_} 是最ä¿é™©çš„。 -\item - 如果 \samp{.\var{progname}} (程åºå) 存在,则该定义åªå¯¹æ­£åœ¨è¿è¡Œçš„åå« - \texttt{\var{progname}} 或 \texttt{\var{progname}.exe} - 的程åºèµ·ä½œç”¨ã€‚è¿™å¯ä»¥è®©ç»™ä¸åŒç§ç±»çš„ \TeX{} 程åºè®¾ç½®ä¸åŒçš„æœç´¢è·¯å¾„。 -\item \var{value} (值) å…许任何 \code{\%} 与 \samp{@} 之外的字符出现。 - ä¸æ”¯æŒåœ¨ç­‰å·å³ä¾§ä½¿ç”¨ \code{\$\var{var}.\var{prog}} 这样的写法。 - 如果在 Unix 下,\var{value} 中的 \samp{;}\ 字符会被转æ¢ä¸º - \samp{:}。如果你希望让 Unix, \acro{MS-DOS} å’Œ Windows 里都用åŒä¸€ä¸ª - \file{texmf.cnf},这会很有用。 -\item - 在读入所有定义åŽå†å¼€å§‹å±•å¼€ï¼Œæ‰€ä»¥ä½ å¯ä»¥å¼•ç”¨åŽè¾¹æ‰å®šä¹‰çš„å˜é‡ã€‚ -\end{itemize} -展示上é¢æ‰€æœ‰å†…容的一段é…置文件 -\ifSingleColumn -如下: - -\verbatiminput{examples/ex5.tex} -\else -è§å›¾~\ref{fig:config-sample}. -\fi - -\subsubsection{路径展开} -\label{sec:path-expansion} - -å’Œ Unix shell 类似,\KPS{} 能够识别æœç´¢è·¯å¾„中的特殊字符。比如一个å¤æ‚的路径 -\verb+~$USER/{foo,bar}//baz+,将展开为这样的å­ç›®å½•ï¼šåœ¨ \texttt{\$USER} -的主目录下的 \file{foo} 或 \file{bar} ç›®å½•ä¸­ï¼Œä¸”åŒ…å« \file{baz} -文件或目录。这ç§å±•å¼€å°†åœ¨ä¸‹é¢è§£é‡Šã€‚ -%$ -\subsubsection{默认展开} -\label{sec:default-expansion} - -\tolerance=2500 -如果最高优先级 (å‚è§ç¬¬ \pageref{sec:path-sources} 页的``路径æ¥æº'') -çš„æœç´¢è·¯å¾„中包å«ä¸€ä¸ª\emph{é¢å¤–的冒å·} (å³å‰ç½®ã€åŽç½®æˆ–连续的冒å·),\KPS{} 将在 -此处æ’入次高优先级的æœç´¢è·¯å¾„。如果æ’入的那个路径里也有é¢å¤–的冒å·ï¼ŒåŒæ ·çš„步骤将å‘生 -在更次以åŠä¼˜å…ˆçº§çš„路径上。å‡è®¾çŽ¯å¢ƒå˜é‡è®¾ç½®ä¸º - -\tolerance=1500 - -\begin{alltt} -> \Ucom{setenv TEXINPUTS /home/karl:} -\end{alltt} - -而 \file{texmf.cnf} 里的 \code{TEXINPUTS} 值为 - -\begin{alltt} - .:\$TEXMF//tex -\end{alltt} - -则用于æœç´¢çš„最终值为: - -\begin{alltt} - /home/karl:.:\$TEXMF//tex -\end{alltt} - -因为没必è¦æ’入多个相åŒçš„值,所以 \KPS{} åªä¼šä¿®æ”¹ä¸€ä¸ªé¢å¤–çš„ \samp{:},其他的ä¸å˜ã€‚ -它首先检查å‰ç½®çš„ \samp{:},然åŽæ˜¯æœ«å°¾çš„ \samp{:},最åŽæ˜¯è¿žç»­çš„ \samp{:}。 - -\subsubsection{大括å·å±•å¼€} - -大括å·å±•å¼€æ˜¯ä¸€é¡¹æœ‰ç”¨çš„特性,其作用是把 \verb+v{a,b}w+ 这样的转æ¢ä¸º -\verb+vaw:vbw+,å…许嵌套使用。通过把 \code{\$TEXMF} 赋值为一个括å·åˆ—表, -å¯ä»¥æž„造出多套 \TeX{} 层级结构。例如在 \file{texmf.cnf} 里有下é¢çš„定义 -(è¿™åªæ˜¯ä¸ªè¿‘似的例å­ï¼Œå®žé™…情况定义的目录树还è¦æ›´å¤š): -\begin{verbatim} - TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN} -\end{verbatim} -这样一æ¥ï¼Œå½“你设置 -\begin{verbatim} - TEXINPUTS = .;$TEXMF/tex// -\end{verbatim} -%$ -的时候,检查完当å‰ç›®å½•åŽï¼Œä¾æ¬¡æ£€æŸ¥çš„路径是 -\code{\$TEXMFHOME/tex}, \code{\$TEXMFLOCAL/tex}, \code{\$TEXMFVAR/tex} -å’Œ \code{\$TEXMFMAIN/tex} (åŽä¸¤ä¸ªåªåœ¨ \file{ls-R} æ•°æ®åº“中æœç´¢)。这样维护 -两套并行的 \TeX{} 结构就很方便的,一套是``固定 (frozen)''çš„ (比如放在 \CD\ 上) -而å¦ä¸€å¥—是在新版本出现时就更新的。因为所有的定义里都用到了 \code{\$TEXMF}, -所以你å¯ä»¥ç¡®ä¿¡æ—¶å¸¸æ›´æ–°çš„那个版本肯定是先被找到的。 - -\subsubsection{å­ç›®å½•å±•å¼€} -\label{sec:subdirectory-expansion} - -在路径元素里的目录å称 \var{d} åŽé¢æŽ¥è¿žä½¿ç”¨ä¸¤ä¸ªæˆ–更多连续的斜æ ï¼Œè¡¨ç¤º \var{d} çš„ -所有å­ç›®å½•ï¼šé¦–先是直接处于 \var{d} 下的那些,然åŽæ˜¯è¿™äº›å­ç›®å½•çš„å­ç›®å½•ï¼Œä¾æ­¤ç±»æŽ¨ã€‚ -æ¯å±‚的目录出现的顺åºæ˜¯\emph{ä¸ä¸€å®š}的。 - -如果你在 \samp{//} åŽé¢è¿˜æŒ‡å®šäº†æ–‡ä»¶å,匹é…çš„å°†åªæ˜¯é‚£äº›åŒ…å«äº†æŒ‡å®šæ–‡ä»¶çš„路径。 -比如 \samp{/a//b} 将展开为路径 \file{/a/1/b}, \file{/a/2/b}, -\file{/a/1/1/b} 等等,但ä¸ä¼šå±•å¼€ä¸º \file{/a/b/c} 或 \file{/a/1}。 - -å¯ä»¥åœ¨å•ä¸ªè·¯å¾„元素里使用多个 \samp{//},但出现在路径开头的 \samp{//} -将被忽略。 - -\subsubsection{特殊字符与其æ„义:简è¦è¯´æ˜Ž} - -下é¢çš„列表总结了 \KPS{} é…置文件中出现的特殊字符: - -% need a wider space for the item labels here. -\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} -\begin{ttdescription} -\item[\CODE{:}] 路径分隔符,在路径的å‰è¾¹æˆ–者末尾时表示默认的展开方å¼ã€‚\par -\item[\CODE{;}] éž Unix 系统下的路径分隔符 (å’Œ \code{:} 功能一样)。 -\item[\CODE{\$}] å˜é‡å±•å¼€ã€‚ -\item[\CODE{\string~}] 表示用户的个人主目录。 -\item[\CODE{\char`\{...\char`\}}] Brace expansion. -\item[\CODE{//}] å­ç›®å½•å±•å¼€ (å¯ä»¥å‡ºçŽ°åœ¨é™¤è·¯å¾„开头外的任æ„ä½ç½®)。 -\item[\CODE{\%}] 注释的起始。 -\item[\CODE{\bs}] 连接下一行的字符 (以支æŒè·¨è¡Œçš„设置项)。 -\item[\CODE{!!}] \emph{åª}在数æ®åº“中æœç´¢æ–‡ä»¶ï¼Œ\emph{ä¸}æœå¯»ç£ç›˜ã€‚ -\end{ttdescription} - - -\subsection{文件åæ•°æ®åº“} -\label{sec:filename-database} - -\KPS{} 使用了一些方法æ¥å‡å°‘æœç´¢æ—¶çš„ç£ç›˜è®¿é—®æ¬¡æ•°ã€‚å°½ç®¡å¦‚æ­¤ï¼Œå¦‚æžœå®‰è£…çš„æ–‡ä»¶è¶³å¤Ÿå¤šï¼Œåœ¨å„ -个å¯èƒ½çš„目录下æœç´¢æŸä¸ªæ–‡ä»¶ä»ç„¶å¯èƒ½èŠ±ä¸Šå¾ˆé•¿æ—¶é—´ (尤其是在必须é历数百个字体目录的时候)。 -因此,\KPS{} 使用一个专门构建的纯文本``æ•°æ®åº“''文件,这个文件å«åš \file{ls-R},它将 -文件和目录进行映射,é¿å…对ç£ç›˜çš„大é‡æœç´¢ã€‚ - -第二个数æ®åº“ \file{aliases} å…许你给 \file{ls-R} 中的文件指定其他的å字。有助于 -帮助æºæ–‡ä»¶ç¬¦åˆ \acro{DOS} 8.3 命å规范。 - -\subsubsection{文件åæ•°æ®åº“} -\label{sec:ls-R} - -å‰è¾¹å·²ç»è§£é‡Šè¿‡ï¼Œä¸»æ–‡ä»¶åæ•°æ®åº“çš„å称必须是 \file{ls-R}。你å¯ä»¥åœ¨æ¯ä¸ªéœ€è¦æœç´¢çš„ -\TeX{} 目录树 (缺çœæ˜¯ \code{\$TEXMF}) 下放置一个这样的文件。\KPS{} 在 -\code{TEXMFDBS} 指定的路径中寻找这些 \file{ls-R} 文件。 - -推è使用å‘行版中包å«çš„ \code{mktexlsr} 脚本æ¥åˆ›å»ºå’Œç»´æŠ¤ \samp{ls-R} 文件。å„ç±» -\samp{mktex} 脚本也å¯èƒ½ä¼šé—´æŽ¥è°ƒç”¨è¿™ä¸ªè„šæœ¬ã€‚实际上,这个脚本åªæ˜¯æ‰§è¡Œä¸‹é¢çš„命令: - -\begin{alltt} -cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R -\end{alltt} - -æ„味ç€ä½ çš„系统的 \code{ls} 命令的输出格å¼å¿…须正确 (\GNU \code{ls} 是没 -问题的)。è¦ä¿è¯æ•°æ®åº“åŠæ—¶æ›´æ–°ï¼Œæœ€ç®€å•çš„方法是定期通过 \code{cron} æ¥é‡å»ºã€‚ - -如果文件在数æ®åº“中找ä¸åˆ°ï¼Œç¼ºçœæƒ…况下 \KPS{} 会在ç£ç›˜ä¸Šæœç´¢ã€‚如果æŸä¸ªç‰¹å®šçš„路径元素 -是以 \samp{!!} 起始的,就\emph{åªä¼š}在针对这一元素的数æ®åº“中查找而ä¸æœç´¢ç£ç›˜ã€‚ - - -\subsubsection{kpsewhich: 独立的路径æœç´¢} -\label{sec:invoking-kpsewhich} - -\texttt{kpsewhich} 程åºå°†è·¯å¾„æœç´¢ä»Žå…¶ä»–专用程åºä¸­ç‹¬ç«‹å‡ºæ¥ï¼Œå®ƒå¯ä»¥ä½œä¸ºç±»ä¼¼ \code{find} -一样的程åºï¼Œä¸“门在 \TeX{} 层级结构中定ä½æ–‡ä»¶ (这在å‘行版中的 \samp{mktex}\dots\ -脚本中使用得éžå¸¸å¤š)。 - -\begin{alltt} -> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} -\end{alltt} -\ttvar{option} 处的选项å¯ä»¥ç”¨ \samp{-} 也å¯ä»¥ç”¨ \samp{-{}-} æ¥èµ·å§‹ï¼Œå¹¶æŽ¥å— -任何ä¸é€ æˆç–‘义的缩写。 - -\KPS{} 将第一个éžé€‰é¡¹çš„å‚数作为文件åæ¥æŸ¥æ‰¾ï¼Œå¹¶è¿”回找到的第一个文件。它ä¸æä¾› -寻找所有相åŒå称文件的功能 (ä½ å¯ä»¥ä½¿ç”¨ Unix çš„ \samp{find} 程åºæ¥è¾¾åˆ°è¿™ä¸ªåŠŸèƒ½)。 - -下é¢ä»‹ç»äº†ä¸€äº›æ¯”较常è§çš„选项。 - -\begin{ttdescription} -\item[\texttt{-{}-dpi=\var{num}}]\mbox{} - 将解æžåº¦è®¾ç½®ä¸º \ttvar{num},这个选项åªå½±å“ \samp{gf} 文件和 \samp{pk} - 文件的查找。为了与 \cmdname{dvips} 兼容,æä¾› \samp{-D} - 这个åŒä¹‰çš„å‚数,默认值是 600。 - -\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ - 将查找的文件格å¼è®¾ç½®ä¸º \ttvar{name}。默认情况下是通过文件åæ¥çŒœæµ‹æ ¼å¼çš„。对于扩展å -有二义性的格å¼ï¼Œæ¯”如 \MP{} 支æŒæ–‡ä»¶å’Œ \cmdname{dvips} é…置文件,必须以 \KPS{} 已知 -çš„å称指定格å¼ï¼Œæ¯”如 \texttt{tex} 或 \texttt{enc files}。è¿è¡Œ - \texttt{kpsewhich -{}-help} 会显示格å¼çš„列表。 - -\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ - 设置模å¼ä¸º \ttvar{string},åªå½±å“ \samp{gf} å’Œ \samp{pk} - 文件的查找。默认情况匹é…所有的模å¼ã€‚ -\item[\texttt{-{}-must-exist}]\mbox{}\\ - 尽一切å¯èƒ½æ‰¾åˆ°æ–‡ä»¶ï¼ŒåŒ…括直接在ç£ç›˜ä¸Šæœå¯»ã€‚默认情况下为了效率考虑,åªæ£€æŸ¥ - \file{ls-R} æ•°æ®åº“里的内容。 -\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ - ä¸é€šè¿‡æ–‡ä»¶åæ¥çŒœæµ‹è·¯å¾„,沿 \ttvar{string} 指出的路径æœç´¢ - (也使用冒å·åˆ†éš”)ã€‚æ”¯æŒ \samp{//} 和所有常è§çš„展开方å¼ã€‚\samp{-{}-path} 选项 - å’Œ \samp{-{}-format} 选项是互斥的。 -\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ - 将执行查找的程åºå称设为 \texttt{\var{name}}。 - 这会通过 \texttt{.\var{progname}} 特性影å“æœç´¢è·¯å¾„。 - 缺çœå€¼æ˜¯ \cmdname{kpsewhich}。 -\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ - 显示用于查找 \texttt{\var{name}} 类型文件的路径。和 \samp{-{}-format} - 选项一样,å¯ä»¥ä½¿ç”¨æ‰©å±•å (\code{.pk}, \code{.vf}, 等等) 也å¯ä»¥ä½¿ç”¨å…¨å。 -\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ - 将调试选项 (等级) 设置为 \texttt{\var{num}}。 -\end{ttdescription} - - -\subsubsection{使用举例} -\label{sec:examples-of-use} - -现在我们看看实际使用 \KPS{} 的例å­ã€‚这里是一个简å•çš„æœç´¢ï¼š - -\begin{alltt} -> \Ucom{kpsewhich article.cls} - /usr/local/texmf-dist/tex/latex/base/article.cls -\end{alltt} -我们寻找的是 \file{article.cls} 文件。因为 \samp{.cls} åŽç¼€å·²ç»è¯´æ˜Žäº†æ–‡ä»¶çš„类型,所以 -我们ä¸éœ€è¦ç‰¹åˆ«æŒ‡æ˜ŽæŸ¥æ‰¾çš„是 \optname{tex} 类型的文件 (也就是è¦åœ¨ (\TeX{} æºæ–‡ä»¶ç›®å½•ä¸‹æŸ¥æ‰¾)。 -我们在 \samp{texmf-dist} çš„ \file{tex/latex/base} å­ç›®å½•ä¸‹æ‰¾åˆ°äº†è¿™ä¸ªæ–‡ä»¶ã€‚与之类似, -下列所有文件都顺利找到,因为其扩展å没有二义。 -\begin{alltt} -> \Ucom{kpsewhich array.sty} - /usr/local/texmf-dist/tex/latex/tools/array.sty -> \Ucom{kpsewhich latin1.def} - /usr/local/texmf-dist/tex/latex/base/latin1.def -> \Ucom{kpsewhich size10.clo} - /usr/local/texmf-dist/tex/latex/base/size10.clo -> \Ucom{kpsewhich small2e.tex} - /usr/local/texmf-dist/tex/latex/base/small2e.tex -> \Ucom{kpsewhich tugboat.bib} - /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib -\end{alltt} - -å¦å¤–,最åŽä¸€ä¸ªæ˜¯ \textsl{TUGBoat} 文章的 \BibTeX{} å‚考文献数æ®åº“。 - -\begin{alltt} -> \Ucom{kpsewhich cmr10.pk} -\end{alltt} - -\file{.pk} 类型的字体ä½å›¾æ–‡ä»¶æ˜¯ç»™ \cmdname{dvips} 或者 \cmdname{xdvi} -è¿™ç§æ˜¾ç¤ºç¨‹åºæ供的。因为 \TL{} 里没有预生æˆçš„ Computer Modern \samp{.pk} -字体,所以没有找到任何内容\Dash \TL{} 默认使用 Type~1 版本的。 - -\begin{alltt} -> \Ucom{kpsewhich wsuipa10.pk} -\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk -\else /usr/local/texmf-var/fonts/pk/ljfour/public/ -... wsuipa/wsuipa10.600pk -\fi\end{alltt} - -而这个字体 (Washington 大学的一套注音字æ¯è¡¨) 就需è¦ç”Ÿæˆ \samp{.pk} 文件了。我们默认的 -\MF{} 模å¼æ˜¯ \texttt{ljfour},基础解æžåº¦æ˜¯ 600\dpi{} (dots per inch),所以会得到这样一个文件。 -\begin{alltt} -> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} -\end{alltt} - -一旦指明我们需è¦å¯»æ‰¾çš„åªæ˜¯ 300\dpi{} 的文件时 (\texttt{-dpi=300}),就会å‘现系统里 -没有符åˆè¦æ±‚的文件。这样 \cmdname{dvips} 或 \cmdname{xdvi} 会使用 \cmdname{mktexpk} -脚本去创建所需的 \texttt{.pk} 文件。 - -下é¢æˆ‘们将注æ„åŠ›è½¬å‘ \cmdname{dvips} 的头文件和é…置文件。首先看看最常用的一个,\file{tex.pro} -prologue 文件,然åŽæ£€æŸ¥é€šç”¨é…置文件 \file{config.ps} å’Œ \PS{} 字体映射文件 -\file{psfonts.map}\Dash 从 2004 年开始,映射文件和编ç æ–‡ä»¶éƒ½åœ¨ \dirname{texmf} -目录树下有其自己的æœç´¢è·¯å¾„了。因为 \samp{.ps} åŽç¼€å¯èƒ½ä¼šæœ‰äºŒä¹‰ï¼Œæˆ‘们必须指明æ„æ€æ˜¯ -\optname{dvips config}。 - -\begin{alltt} -> \Ucom{kpsewhich tex.pro} - /usr/local/texmf/dvips/base/tex.pro -> \Ucom{kpsewhich --format="dvips config" config.ps} - /usr/local/texmf/dvips/config/config.ps -> \Ucom{kpsewhich psfonts.map} - /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map -\end{alltt} - -这样我们å¯ä»¥æ›´ä»”细地分æžä¸€ä¸‹ \acro{URW} Times çš„ \PS{} 支æŒæ–‡ä»¶ã€‚ä¾ç…§æ ‡å‡†çš„字体 -命å方案,这些文件的å‰ç¼€æ˜¯ \samp{utm}。首先查询的是é…置文件,其中包å«çš„是 map -文件的å称: - -\begin{alltt} -> \Ucom{kpsewhich --format="dvips config" config.utm} - /usr/local/texmf-dist/dvips/psnfss/config.utm -\end{alltt} - -这个文件的内容是 - -\begin{alltt} - p +utm.map -\end{alltt} - -å³æŒ‡å‘ \file{utm.map} 文件,也就是我们下一步è¦æ‰¾çš„。 - -\begin{alltt} -> \Ucom{kpsewhich utm.map} - /usr/local/texmf-dist/fonts/map/dvips/times/utm.map -\end{alltt} - -这个 map 文件定义了 URW 集åˆä¸­çš„ Type~1 \PS{} 字体文件å。内容差ä¸å¤šæ˜¯ä¸‹è¾¹è¿™æ · -(我们åªåˆ—出了其中一部分): - -\begin{alltt} -utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} -\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb -\else /usr/local/texmf-dist/fonts/type1/ -... urw/utm/utmr8a.pfb -\fi\end{alltt} - -现在你å¯ä»¥å‘现,追寻æŸä¸ªæ–‡ä»¶çš„下è½æ˜¯å¦‚此方便。尤其是在你怀疑找到的文件错了的时候,这些 -功能éžå¸¸é‡è¦ï¼Œå› ä¸º \cmdname{kpsewhich} åªèƒ½å‘Šè¯‰ä½ æ‰¾åˆ°çš„第一个文件。 - -\subsubsection{调试æ“作} -\label{sec:debugging} - -有时你å¯èƒ½ä¼šéœ€è¦åˆ†æžç¨‹åºæ˜¯å¦‚何解æžæ–‡ä»¶å¼•ç”¨çš„。\KPS{} æ供了多层调试输出æ¥å®žçŽ°è¿™ä¸ªåŠŸèƒ½ï¼š - -\begin{ttdescription} -\item[\texttt{\ 1}] \texttt{stat} 调用 (ç£ç›˜ä¸Šçš„查询)。在 \file{ls-R} - æ•°æ®åº“åŠæ—¶æ›´æ–°çš„情况下几乎ä¸ä¼šæœ‰ä»€ä¹ˆè¾“出。 -\item[\texttt{\ 2}] 对散列表的引用 (例如 \file{ls-R} æ•°æ®åº“,映射文件,é…置文件)。 -\item[\texttt{\ 4}] 文件的打开与关闭æ“作。 -\item[\texttt{\ 8}] \KPS{} æœç´¢çš„文件类型的通用路径信æ¯ã€‚有助于寻找针对æŸä¸€æ–‡ä»¶çš„ -特定路径。 -\item[\texttt{16}] æ¯ä¸ªè·¯å¾„元素的目录列表 (åªåœ¨æœ¬åœ°ç£ç›˜ä¸Šæœç´¢æ—¶æœ‰ç”¨)。 -\item[\texttt{32}] 文件æœç´¢ã€‚ -\item[\texttt{64}] å˜é‡çš„值。 -\end{ttdescription} -等级 \texttt{-1} å°†å¯ç”¨ä¸Šè¿°æ‰€æœ‰é€‰é¡¹ï¼Œå®žé™…上这是最方便的设置方法了。 - -类似地,在 \cmdname{dvips} 程åºä¸­è®¾ç½®ä¸Šè¿°è°ƒè¯•é€‰é¡¹çš„组åˆï¼Œä½ å°±å¯ä»¥å‡º \cmdname{dvips} -是从哪里找到它所需的文件的。å¦ä¸€æ–¹é¢ï¼Œå¦‚果找ä¸åˆ°æŸä¸ªæ–‡ä»¶ï¼Œè°ƒè¯•è¾“出也会显示程åºä»Žå“ªäº›ç›®å½•è¿›è¡Œ -了查找,你也å¯ä»¥æ®æ­¤åˆ¤æ–­å‡ºé—®é¢˜å‡ºåœ¨å“ªé‡Œã€‚ - -一般而言,因为所有的程åºéƒ½åœ¨å…¶å†…部调用 \KPS{} 库,你å¯ä»¥è®¾ç½® \envname{KPATHSEA\_DEBUG} -环境å˜é‡æ¥é€‰æ‹©è°ƒè¯•å‚数,将这个å˜é‡è®¾ç½®ä¸ºä¸Šè¿°å‚æ•°çš„ç»„åˆ (加法) 以获得对应的功能。 - -(Windows 用户请注æ„:因为在 Windows 下ä¸å®¹æ˜“把所有信æ¯éƒ½é‡å®šå‘到固定的文件中,为了方便诊断, -ä½ å¯ä»¥ä¸´æ—¶è®¾ç½® \texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log})。 - -让我们以一个简å•çš„ \LaTeX{} æºæ–‡ä»¶ \file{hello-world.tex} 为例,其内容如下: -\begin{verbatim} - \documentclass{article} - \begin{document} - Hello World! - \end{document} -\end{verbatim} -这个å°æ–‡ä»¶åªä½¿ç”¨äº† \file{cmr10} 字体,我们å¯ä»¥çœ‹çœ‹ \cmdname{dvips} æ˜¯å¦‚ä½•ç”Ÿæˆ \PS{} -文件的 (我们希望使用 Type~1 版本的 Computer Modern 字体,所以使用了 \texttt{-Pcms} -å‚æ•°)。 -\begin{alltt} -> \Ucom{dvips -d4100 hello-world -Pcms -o} -\end{alltt} -此时我们将 \cmdname{dvips} 的调试等级 4 (表示字体路径) å’Œ \KPS\ 的路径元素展开组åˆåˆ° -一起 (å‚è§ \cmdname{dvips} å‚考手册,\OnCD{texmf/doc/html/dvips/dvips_toc.html})。 -(ç¨ä½œæ•´ç†çš„) 输出è§å›¾~\ref{fig:dvipsdbga}。 -\begin{figure*}[tp] -\centering -\input{examples/ex6a.tex} -\caption{寻找é…置文件}\label{fig:dvipsdbga} - -\bigskip - -\input{examples/ex6b.tex} -\caption{寻找 prolog 文件}\label{fig:dvipsdbgb} - -\bigskip - -\input{examples/ex6c.tex} -\caption{寻找字体文件}\label{fig:dvipsdbgc} -\end{figure*} - -\cmdname{dvips} å¯åŠ¨åŽå°±å¼€å§‹æœå¯»å…¶éœ€è¦ä½¿ç”¨çš„文件。首先找到的是 \file{texmf.cnf}, -它给出了用于进一步查询其他文件的路径,然åŽæ‰¾åˆ°çš„是 \file{ls-R} 文件åæ•°æ®åº“ (用于 -优化文件æœç´¢é€Ÿåº¦) å’Œ \file{aliases} 文件 (用于创建åŒä¸€æ–‡ä»¶çš„多个别å,比如为较自然 -的长文件å创建 \acro{DOS} 8.3 风格的短别å)ã€‚ç„¶åŽ \cmdname{dvips} 去寻找它的通用 -é…置文件 \file{config.ps},接下æ¥æŸ¥æ‰¾ä¸ªäººå®šåˆ¶æ–‡ä»¶ \file{.dvipsrc} (ä¸è¿‡ä¸Šè¿°ä¾‹å­ä¸­å¹¶ -未找到,显示 \emph{not found})ã€‚æœ€åŽ \cmdname{dvips} 找到了 Computer Modern -\PS{} 字体的é…置文件 \file{config.cms} (因为执行 \cmdname{dvips} 时使用了 -\texttt{-Pcms} 选项)。这个文件里包å«äº†å­—体的 \TeX{} å称, \PS{} å称和文件å的对 -应关系。 - -\begin{alltt} -> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} - p +ams.map - p +cms.map - p +cmbkm.map - p +amsbkm.map -\end{alltt} -于是 \cmdname{dvips} 接下æ¥å¯»æ‰¾è¿™äº›æ–‡ä»¶ï¼Œå†åŠ ä¸Šå›ºå®šè½½å…¥çš„,通用映射文件 -\file{psfonts.map} (这个文件里包å«å¸¸ç”¨ \PS{} 字体的映射,å‚è§ç¬¬ -\ref{sec:examples-of-use} 节的最åŽä¸€éƒ¨åˆ†ï¼Œè®¨è®ºäº† \PS{} 映射文件的处ç†)。 - -这时候 \cmdname{dvips} å‘用户表示它的存在: -\begin{alltt} -This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) -\end{alltt} -\ifSingleColumn -然åŽå¼€å§‹å¯»æ‰¾ prolog 文件 \file{texc.pro}: -\begin{alltt}\small -kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro -\end{alltt} -\else -然åŽå¼€å§‹å¯»æ‰¾ prolog 文件 \file{texc.pro} (è§å›¾~\ref{fig:dvipsdbgb})。 -\fi - -找到所需文件åŽï¼Œ\cmdname{dvips} è¾“å‡ºæ—¥æœŸå’Œæ—¶é—´ï¼Œå¹¶å‘ŠçŸ¥æˆ‘ä»¬å®ƒå°†ç”Ÿæˆ -\file{hello-world.ps} 文件,需è¦ç”¨åˆ° \file{cmr10} 字体文件, -这个字体属于``常驻 (resident) çš„'',也就是ä¸éœ€è¦è½½å…¥ä½å›¾æ–‡ä»¶çš„字体: -\begin{alltt}\small -TeX output 1998.02.26:1204' -> hello-world.ps -Defining font () cmr10 at 10.0pt -Font cmr10 is resident. -\end{alltt} -寻找并找到了 \file{cmr10.tfm} 文件。然åŽå†æ¬¡å¼•ç”¨äº†ä¸€äº› prolog 文件 (此处略去), -最终找到了 \file{cmr10.pfb} 这个 Type~1 字体,并将它包å«åœ¨è¾“出文件中 (è§æœ€åŽ -一行)。 -\begin{alltt}\small -kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, - path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: - /var/tex/fonts/tfm//). -kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm -kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, - ... - -kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, - path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: - ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). -kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb -[1] -\end{alltt} - -\subsection{è¿è¡Œæ—¶é€‰é¡¹} - -\Webc{} å¦ä¸€é¡¹æœ‰ç”¨çš„特性是å¯ä»¥é€šè¿‡ \KPS{} 读入的è¿è¡Œæ—¶æ–‡ä»¶ \file{texmf.cnf} -æ¥æŽ§åˆ¶ä¸€ç³»åˆ—的内存å‚æ•° (具体而言是数组的大å°)。内存的设置å¯ä»¥åœ¨è¿™ä¸ªæ–‡ä»¶çš„第三部分找到。 -比较é‡è¦çš„几个设置是: - -\begin{ttdescription} -\item[\texttt{main\_memory}] - 总的å¯ç”¨å†…存数,以 word 为å•ä½ï¼Œ\TeX{}, \MF{} å’Œ \MP\ å—æ­¤é™åˆ¶ã€‚ - æ¯ä¿®æ”¹ä¸€æ¬¡éƒ½å¿…é¡»é‡æ–°ç”Ÿæˆä¸€ä¸ªæ–°çš„æ ¼å¼æ–‡ä»¶ã€‚比如你å¯ä»¥ç”Ÿæˆä¸€ä¸ª``巨型''版本的 - \TeX{},将其存为 \texttt{hugetex.fmt}。 -\item[\texttt{extra\_mem\_bot}] - 为``大型'' \TeX{} æ•°æ®ç»“构预留的é¢å¤–空间:boxes, glue, breakpoint 等。如果你使用 - \PiCTeX{} 时特别有用。 -\item[\texttt{font\_mem\_size}] - \TeX{} 用于存储字体数æ®çš„ word 数。大致等于载入的所有 \acro{TFM} 文件的总和。 -\item[\texttt{hash\_extra}] - 为存储控制åºåˆ—而设置的散列表的é¢å¤–空间。一般散列表足够存储将近 10,000 - 个控制åºåˆ—。如果你排版的是一本有大é‡äº¤å‰å¼•ç”¨çš„书ç±ï¼Œè¿™ä¸ªå€¼å¯èƒ½ä¸å¤Ÿç”¨ã€‚默认的 - \texttt{hash\_extra} 是 \texttt{50000}。 -\end{ttdescription} - -\noindent 当然,这项功能并éžçœŸæ­£çš„动æ€å†…存和数组分é…的替代,但考虑到动æ€åˆ†é…在现在的 \TeX{} -太难实现,æ‰é€šè¿‡è¿™äº›é€‰é¡¹æ供了一些çµæ´»æ€§ã€‚ - -\begin{comment} -\section{在 Unix å¹³å°ä¸‹ç¼–译} - -If you have a platform for which executables are not included, you will -need to compile \TeX{} and friends. This is not as hard as it -sounds. What you need is all in the directory \texttt{source} in the -distribution. - -\subsection{需求} - -You will need at least 100 megabytes of disk space to compile all of -\TeX{} and its support programs. You'll also need an \acro{ANSI} C -compiler, a \cmdname{make} utility, a lexical scanner, and a parser -generator. We recommend the \GNU version of these programs -(\cmdname{gcc}, \GNU \cmdname{make}, \cmdname{m4}, \cmdname{flex}, -\cmdname{bison}). You may be able to work with other C compilers and -\cmdname{make} programs, but you will need a good understanding of -building Unix programs to sort out problems. - -Also, the command \texttt{uname} must return a sensible value. - - -\subsection{é…ç½®} - -To begin, perform a normal installation of \TL{} to your disk (see -section~\ref{sec:install-disk} on -\p.\pageref{sec:install-disk}). You may wish to skip installing -all of the prebuilt binaries. - -Then, unpack the source from the compressed \texttt{tar} file in the -directory \dirname{source} to your disk and change directory to where -you placed it. - -Next, run \cmdname{configure} with a command line like this: -\begin{alltt} -> \Ucom{sh configure -prefix=/usr/local/TeX} -\end{alltt} - -The \optname{-prefix} directory is the one where you installed the -support tree; the directory layout will be as follows (where \$TEXDIR -stands for the directory you chose): - -\noindent -\begin{tabular}{>{\ttfamily}ll@{}} - \dirname{$TEXDIR/share/texmf} & main tree with fonts,\\ - & \qquad macros, etc\\ - \dirname{$TEXDIR/man} & Unix manual pages\\ - \dirname{$TEXDIR/info} & \GNU style Info manuals\\ - \dirname{$TEXDIR/bin/$PLATFORM} & binaries\\ -\end{tabular} -%$ - -If you want to leave out the \dirname{$PLATFORM} directory level, -i.e., put the binaries directly into \dirname{$TEXDIR/bin}, specify -the \verb|--disable-multiplatform| option to \cmdname{configure}. - -Have a look at the output of \verb|./configure --help| for more -options you can use. For example, you can skip building of \OMEGA{} and -\eTeX{}. - - -\subsection{è¿è¡Œ \cmdname{make}} - -Make sure the shell variable or option \texttt{noclobber} is not set. -Then, run the main \cmdname{make} like this: -\begin{alltt} -> \Ucom{make world} -\end{alltt} -and relax\ldots - -Alternatively, you want to log all the output, as in: -\begin{alltt} -> \Ucom{sh -c "make world >world.log 2>\&1" \&} -\end{alltt} - -Before you believe that everything went ok, please check the log file -for errors: \GNU \cmdname{make} always uses the string \samp{***} -whenever a command fails. Also, check if all the programs were built: - -\begin{alltt} -> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} -> \Ucom{ls | wc} -\end{alltt} -The result should be over 200 (you can check the exact number with the -\dirname{bin} directory contents in the distribution). - -If you need special privileges for \texttt{make install}, you can -separate the \samp{make world} into two different runs, like this: -\begin{alltt} -> \Ucom{make all} -> \Ucom{su} -> \Ucom{make install strip} -\end{alltt} - -After you've installed your new binaries, you should follow the normal -post-installation procedures, given in section~\ref{sec:postinstall} -(\p.\pageref{sec:postinstall}). - -Also, if you'd like to make your binaries available to others, please -contact us. We'll be happy to put them on the \TL\ web pages. -\end{comment} - -\section{致谢} - -\TL{} 是在几乎所有 \TeX{} 用户组织的å力下完æˆçš„。这个版本由 Karl Berry -监制。下é¢åˆ—出了过去和现在主è¦çš„贡献者: - -\begin{itemize*} - -\item 英国ã€å¾·å›½ã€è·å…°å’Œæ³¢å…°çš„ \TeX{} 用户组织 -(分别为 \acro{TUG}, \acro{DANTE} e.V., \acro{NTG}, å’Œ \acro{GUST}),他们为所在 -地区的 \TeX{} 社群æ供了必备的技术和管ç†åŸºç¡€è®¾æ–½ã€‚请加入本地的 \TeX ç”¨æˆ·ç»„ç»‡ï¼ -(å‚è§ \url{http://tug.org/usergroups.html}。) - -\item \acro{CTAN} 团队,特别值得一æ的是 Robin Fairbairns, Jim Hef{}feron, -å’Œ Rainer Sch\"opfã€‚ä»–ä»¬è´Ÿè´£åˆ†å‘ \TL{} 光盘镜åƒï¼Œä¸ºè½¯ä»¶åŒ…æ›´æ–°æ供支撑,\TL{} -正是基于这些软件包构建的。 - -\item Peter Breitenlohner å’Œ \eTeX\ å›¢é˜Ÿï¼Œä»–ä»¬åˆ›é€ äº†æœªæ¥ \TeX\ 的稳定基础。 -åŒæ—¶ç‰¹åˆ«æ„Ÿè°¢ Peter,他为整个 \TL 中 GNU autotools 的使用æ供了主è¦çš„帮助。 - -\item Thomas Esser,如果没有他优秀的 \teTeX{} 套件,\TL{} 根本ä¸å¯èƒ½å­˜åœ¨ã€‚ - -\item Michel Goossens,他一起编写了原始的文档。 - -\item Eitan Gurari,他ä¸çŸ¥ç–²å€¦åœ°æ”¹è¿›ç€çš„ \TeX4ht 程åºç”¨äºŽåˆ›å»ºè¿™ä»½æ–‡æ¡£çš„ \HTML{} -版本。 - -\item \Thanh, Martin Schr\"oder,和 pdf\TeX\ 团队,他们æŒç»­ä¸æ–­åœ°æ”¹è¿› \TeX\ -的功能。 - -\item Hans Hagen,他对 \ConTeXt\ æ ¼å¼ (\url{http://pragma-ade.com}) åšäº† -许多测试和修改,使之能够包å«åœ¨ \TL{} 的框架下。 - -\item Hartmut Henkel,他对 pdf\TeX\, Lua\TeX 等程åºçš„å¼€å‘起到了é‡è¦çš„贡献。 - -\item Taco Hoekwater,他对 \MP{} å’Œ (Lua)\TeX\ (\url{http://luatex.org}) -çš„å¼€å‘使之焕å‘新的活力。他还å‚与了将 \ConTeXt\ èžå…¥ \TL 的工作。 - -\item Pawe{\l} Jackowski,他创建了 Windows ä¸‹çš„å®‰è£…ç¨‹åº \cmdname{tlpm}, -å’Œ Tomasz {\L}uczak,因为他的 \cmdname{tlpmgui} 被用在了以å‰çš„版本。 - -\item Akira Kakuto,以他的 \acro{W32TEX} å‘行版 -(\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}) 为基础æ供了 -Windows 下的二进制文件,以åŠè®¸å¤šå…¶ä»–的贡献。 - -\item Jonathan Kew å’Œ \acro{SIL},因为 Xe\TeX{} 是如此新颖而é‡å¤§ -的改进。他还花了大é‡æ—¶é—´å’Œç²¾åŠ›æ¥å°†å…¶é›†æˆåˆ° \TL{} ä¸­ã€‚ä»¥åŠ Mac\TeX å®‰è£…ç¨‹åº -的早期版本。 - -\item Dick Koch 他维护了 Mac\TeX\ (\url{http://tug.org/mactex}) 这个和 -\TL{} è”ç³»éžå¸¸ç´§å¯†çš„å‘行版本。 - -\item Reinhard Kotucha,他对 \TL{} 2008 的基础架构和安装程åºèµ·åˆ°äº†é‡è¦è´¡çŒ®ï¼Œ -ä»¥åŠ Windows 下的研究性工作,\texttt{getnonfreefonts} 脚本,等等。 - -\item Siep Kroonenberg,也因为他对 \TL{} 2008 基础架构和安装程åºçš„é‡è¦è´¡çŒ®ï¼Œ -尤其是在 Windows 上。他还花了大é‡çš„时间更新手册,介ç»äº†è¿™äº›æ–°çš„特性。 - -\item Petr Ol\v{s}ak,他éžå¸¸è®¤çœŸåœ°å调和检查所有的æ·å…‹è¯­å’Œæ–¯æ´›ä¼å…‹è¯­èµ„料。 - -\item Toshio Oshima,他æ供了 Windows 下的 \cmdname{dviout} 预览工具。 - -\item Manuel P\'egouri\'e-Gonnard,他对å®åŒ…æ›´æ–°ã€æ–‡æ¡£æ”¹è¿›ä»¥åŠ -\cmdname{tldoc} å¼€å‘上的努力。 - -\item Fabrice Popineau,他创建了 \TL{} 最早的 Windows 支æŒã€‚ - -\item Norbert Preining,他是 \TL{} 2008 基础架构和安装程åºçš„总设计师,还 -è´Ÿè´£å调了 Debian 版本的 \TL{} 工作 (å’Œ Frank K\"uster 一起),并æ供了许 -多建议。 - -\item Sebastian Rahtz,他是 \TL{} 的创始者,并维护了它许多年。 - -\item Vladimir Volovich,他很大地帮助解决了许多移æ¤å’Œç»´æŠ¤çš„问题,尤其是令我们能够 -å°† \cmdname{xindy} 包å«è¿›æ¥ã€‚ - -\item Staszek Wawrykiewicz,\TL{} 主è¦çš„测试人员,åŒæ—¶è¿˜æ˜¯è®¸å¤šé‡è¦æ³¢å…°è¯­æ”¯æŒçš„åè°ƒ -人员:字体ã€Windows 安装,和其他许多工作。 - -\item Olaf Weber,他对 \Webc{} è€å¿ƒçš„维护。 - -\item Gerben Wierda,他创建和维护 \MacOSX\ 支æŒï¼Œå¹¶å‚与了大é‡é›†æˆå’Œæµ‹è¯•å·¥ä½œã€‚ - -\item Graham Williams,他整ç†äº†è½¯ä»¶åŒ…çš„ä¾èµ–情况的 \TeX\ Catalogue。 - -\end{itemize*} - -二进制版本的编译者: -Tigran Aivazian (\pkgname{x86\_64-linux}), -Tim Arnold (\pkgname{hppa-hpux}), -Randy Au (\pkgname{amd64-freebsd}), -Edd Barrett (\pkgname{i386-openbsd}), -Karl Berry (\pkgname{i386-linux}), -Akira Kakuto (\pkgname{win32}), -Dick Koch (\pkgname{universal-darwin}), -Manfred Lotz (\pkgname{i386-freebsd}), -Norbert Preining (\pkgname{alpha-linux}), -Arthur Reutenauer (\pkgname{sparc-linux}), -Thomas Schmitz (\pkgname{powerpc-linux}), -Apostolos Syropoulos (\pkgname{i386-solaris}), -Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-solaris}), -Olaf Weber (\pkgname{mips-irix})。 -关于 \TL{} 编译进程的信æ¯ï¼Œè¯·æŸ¥é˜… \url{http://tug.org/texlive/build.html}。 - -文档和翻译的更新: -Karl Berry (英语), -Daniel Flipo (法语), -Klaus H\"oppner (德语), -Petr Sojka \& Jan Busa (æ·å…‹\slash 斯洛ä¼å…‹è¯­), -Boris Veytsman (俄语), -Staszek Wawrykiewicz (波兰语)。\TL{} 文档的主页是 -\url{http://tug.org/texlive/doc.html}。 - -当然,最é‡è¦çš„感谢应该致予 Donald Knuth,感谢他å‘明了 \TeX,也感谢他将 -\TeX\ 赠与全世界。 - -\section{å‘行历å²} -\label{sec:history} - -\subsection{过去} - -1993 年末è·å…° \TeX{} 用户组开始为 \acro{MS-DOS} ç”¨æˆ·å¼€å‘ 4All\TeX{} \CD{} 时, -我们就开始了相关的讨论,并希望在此时为所有的æ“作系统æ供一个å•ä¸€çš„ã€åˆç†çš„ \CD{}。当时 -那是一个过于å®ä¼Ÿçš„目标,但的确滋生了éžå¸¸æˆåŠŸçš„ 4All\TeX{} \CD{},åŒæ—¶ \acro{TUG} -技术委员会工作组也开始设计 \emph{\TeX{} 目录结构} (\url{http://tug.org/tds}), -以指明如何创建一套一致而å¯æŽ§çš„集åˆï¼Œå›Šæ‹¬æ‰€æœ‰ \TeX{} 相关的文件。\TDS{} 的完整è‰æ¡ˆåœ¨ 1995 -å¹´ 12 月的 \textsl{TUGboat} 上出版,并åˆæ­¥ç¡®å®šæœŸæœ›çš„产å“将是在 \CD{} 上出现的范例 -结构。你现在使用的这个å‘行版正是工作组审议的直接结果。4All\TeX{} \CD{} çš„æˆåŠŸä¹Ÿè¯´æ˜Ž -如果有一个类似这样的易于使用的系统,对 Unix 用户肯定很有帮助,这是 \TL{} 最主è¦çš„出å‘点。 - -我们在 1995 年秋天开始å°è¯•æž„建一个新的 \CD{} (基于 \TDS{}),并很快å‘现 Thomas Esser -çš„ \teTeX{} å·²ç»æ˜¯æ¯”较ç†æƒ³çš„é…置,并因为在它构建时就已ç»è€ƒè™‘了跨文件系统的兼容性问题, -也已具有多平å°æ”¯æŒã€‚Thomas åŒæ„帮助我们,并在 1996 å¹´åˆå¼€å§‹äº†æ­£å¼çš„工作。第一版是在 -1996 年五月å‘行的。到 1997 å¹´åˆï¼ŒKarl Berry 完æˆäº† \Webc{} 的一个é‡å¤§çš„更新版本, -将几乎所有 Thomas Esser 加入 \teTeX{} 的特性囊括在内,这样我们决定在 \teTeX{} çš„ -\texttt{texconfig} 脚本的辅助下,基于标准的 \Webc{} æ¥åˆ¶ä½œç¬¬äºŒç‰ˆçš„ \CD{}。 -第 3 版的 \CD{} 基于 Olaf Weber 完æˆçš„ \Webc{} 的一个é‡å¤§ä¿®æ­£ç‰ˆæœ¬ï¼Œ7.2。与此åŒæ—¶ï¼Œ -\teTeX{} 的一个新版本出现了,\TL{} 也包å«äº†å…¶ä¸­ç»å¤§å¤šæ•°ç‰¹æ€§ã€‚第 4 版ä¾ç…§ä¸Šé¢çš„模å¼è¿› -行,使用了新版本的 \teTeX{} 和新版本的 \Webc{} (7.3)。系统此时也包括了完整的 Windows -下的é…置。 - -在第 5 版 (2000 å¹´ 3 月) 中检查并修正了 \CD{} 的许多部分,更新了数百个软件包。软件 -包的详细说明现在存放在 XML 文件中。ä¸è¿‡ \TeX\ Live 5 的首è¦å˜åŒ–还是移除了所有的éžè‡ªç”±è½¯ -件。\TL{} çš„æ‰€æœ‰éƒ¨åˆ†çŽ°åœ¨éƒ½åœ¨å‘ Debian Free Software Guidelines 兼容的方å‘改进, -我们尽最大努力检查了所有软件包的授æƒå议,欢迎为我们指出错误。 - -第 6 版 (2001 å¹´ 7 月) 更新了许多内容。最é‡å¤§çš„一项是新的安装形å¼ï¼Œç”¨æˆ·å¯ä»¥æ›´ç²¾ç¡® -地选择所需的软件集åˆã€‚与语言相关的集åˆä¹Ÿé‡æ–°ç»„织过了,这样一æ¥ï¼Œé€‰å®šæŸä¸ªè¯­è¨€é›†åˆæ—¶ä¼šè‡ª -动安装å®åŒ…ã€å­—体等文件,并自动设置好 \texttt{language.dat}。 - -2002 年出现的第 7 版里显著的更新是添加了 \MacOSX{} 的支æŒï¼Œè¿˜æœ‰å¤§é‡å„ç±»å®åŒ…å’Œç¨‹åº -的更新。这个版本的一个é‡è¦çš„目标是将æºä»£ç é‡æ–°ä¸Ž \teTeX{} 集æˆï¼Œå› ä¸ºåœ¨ç¬¬ 5 和第 6 -版中它们å离得太远了。 - -\subsubsection{2003} - -2003 年,在更新和增添æŒç»­ä¸æ–­åˆ°æ¥çš„情况下,我们å‘现 \TL{} å·²ç»è¿‡äºŽåºžå¤§ï¼Œæ— æ³•åœ¨ä¸€å¼  -\CD\ 中容纳,于是将其切分为三套ä¸åŒçš„å‘行版 (å‚è§ç¬¬~\ref{sec:tl-coll-dists} -节,\p.\pageref{sec:tl-coll-dists})。此外: - -\begin{itemize*} -\item 在 \LaTeX{} 团队的è¦æ±‚下,我们将 \cmdname{latex} å’Œ \cmdname{pdflatex} - 命令改为使用 \eTeX{} 引擎 (å‚è§ \p.\pageref{text:etex})。 -\item 包å«äº†æ–°çš„ Latin Modern 字体 (并推è使用)。 -\item 因为ä¸å†æœ‰äººæ‹¥æœ‰ (或主动æä¾›) 用于编译新的二进制程åºçš„硬件,去除了 - Alpha \acro{OSF} çš„æ”¯æŒ (å…ˆå‰å·²ç»åŽ»é™¤äº† \acro{HPUX} 的支æŒ)。 -\item Windows 下的安装有很大改å˜ï¼Œé¦–次æ供了基于 XEmacs 的集æˆçŽ¯å¢ƒã€‚ -\item Windows 下é‡è¦çš„è¾…åŠ©æ€§ç¨‹åº (Perl, Ghost\-script, Image\-Magick, Ispell) - 现在放在 \TL{} 的安装目录。 -\item \cmdname{dvips}, \cmdname{dvipdfm} å’Œ \cmdname{pdftex} - 使用的字体映射文件现在通过 \cmdname{updmap} 这套新程åºç”Ÿæˆï¼Œå¹¶å®‰è£…到 - \dirname{texmf/fonts/map} 目录下。 -\item \TeX{}, \MF{}, å’Œ \MP{} 现在缺çœç›´æŽ¥è¾“出大多数的输入字符 (ä½ç½® 32 åŠå…¶ä»¥ä¸Š) - (比如通过 \verb|\write|),包括输出到文件ã€æ—¥å¿—和终端上。也就是说,\emph{ä¸å†}使用 - \verb|^^| 标记æ¥è½¬æ¢ã€‚在 \TL{}~7 中是å¦è½¬æ¢æ ¹æ®ç³»ç»ŸåŒºåŸŸ (locale) - 设置而定,而这一版里 locale 设置ä¸å†å½±å“ \TeX{} 程åºçš„è¡Œä¸ºï¼Œæ‰€ä»¥å¦‚æžœä½ éœ€è¦ - \verb|^^| å½¢å¼çš„输出,请将 \verb|texmf/web2c/cp8bit.tcx| - 文件改å。(åŽç»­ç‰ˆæœ¬å°†æ供更简æ´çš„æ–¹å¼æ¥æŽ§åˆ¶ã€‚) -\item 对文档作了大é‡æ›´æ–°ã€‚ -\item 最åŽï¼Œå› ä¸ºç‰ˆæœ¬å·å¢žé•¿å¾—实在太快,现在简å•åœ°ä½¿ç”¨å¹´ä»½æ¥æ ‡è¯†ç‰ˆæœ¬ï¼š\TL{} 2003。 -\end{itemize*} - - -\subsubsection{2004} - -2004 年有许多改å˜ï¼š - -\begin{itemize} - -\item 如果你在本地安装的字体时涉åŠäº† \filename{.map} 或 \filename{.enc} -(附带这ç§æ–‡ä»¶çš„å¯èƒ½æ€§å¾ˆå°) 辅助文件,å¯èƒ½éœ€è¦è½¬ç§»è¿™äº›æ–‡ä»¶çš„ä½ç½®ã€‚ - -çŽ°åœ¨æ ¹æ® \envname{TEXFONTMAPS} å˜é‡ä¸­çš„路径设置,åªåœ¨ (所有 \filename{texmf} -目录树下的) \dirname{fonts/map} å­ç›®å½•ä¸‹æœç´¢ \filename{.map} -文件。与之类似,\filename{.enc} 文件现在åªåœ¨ \dirname{fonts/enc} -目录下æœç´¢ï¼Œæ ¹æ® \envname{ENCFONTS} å˜é‡ä¸­çš„路径设置。如果é‡åˆ°æœ‰é—®é¢˜çš„æ–‡ -件,\cmdname{updmap} 会æ出警告。 - -关于这ç§æœç´¢æ–¹å¼çš„其他信æ¯ï¼Œè¯·å‚è§ \url{http://tug.org/texlive/mapenc.html}。 - -\item 因为有人å¯èƒ½æ›´æ„¿æ„使用 \MIKTEX\ è€Œéž \Webc{} 系统,\TK\ -现在包å«äº†ä¸€å¥—基于 \MIKTEX\ çš„å¯å®‰è£… \CD,å‚è§ç¬¬~\ref{sec:overview-tl} 节 -(\p.\pageref{sec:overview-tl})。 - -\item 在原æ¥æ—§ç‰ˆæœ¬ \TL\ 中å•ä¸€çš„ \dirname{texmf} 目录树被分拆为三 -个:\dirname{texmf}, \dirname{texmf-dist}, å’Œ \dirname{texmf-doc}。å‚è§ -第~\ref{sec:tld} 节 (\p.\pageref{sec:tld}) åŠå„目录下的 \filename{README} -文件。 - -\item 所有 \TeX\ 输入文件现在统一收集到了 \dirname{texmf*} 下的 -\dirname{tex} å­ç›®å½•ä¸­ï¼Œä¸å†åˆ†æ•£åœ¨å„个 \dirname{tex}, \dirname{etex}, -\dirname{pdftex}, \dirname{pdfetex} 目录。è§~ -\CDref{texmf-doc/doc/english/tds/tds.html\#Extensions} -{\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}。 - -\item 辅助性脚本 (并éžç›´æŽ¥æ供给用户调用的) 现在放在 \dirname{texmf*} 目录树下 -æ–°çš„ \dirname{scripts} å­ç›®å½•ä¸­ï¼Œå¹¶å¯ä»¥é€šè¿‡ \verb|kpsewhich -format=texmfscripts| -æ¥æœç´¢ã€‚如果你的程åºè°ƒç”¨äº†è¿™äº›è„šæœ¬ï¼Œå¿…须修改路径。å‚è§ -\CDref{texmf-doc/doc/english/tds/tds.html\#Scripts} -{\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}。 - -\item 几乎所有格å¼ï¼Œéƒ½ç”¨ \filename{cp227.tcx} 这个转æ¢æ–‡ä»¶å°†å¤§å¤šæ•°çš„å¯è§ (printable) -字符ä¿ç•™ä¸‹æ¥ï¼Œè€Œä¸å†ä½¿ç”¨ \verb|^^| 标识æ¥è½¬æ¢è¿™äº›å­—符。具体而言,在ä½ç½® 32--256 çš„ -字符,加上 tab, vertical tab, å’Œ form feed 字符都作为å¯è§å­—符而ä¸å†è½¬æ¢ã€‚例外情况是 -plain \TeX\ (åªå°†ä½ç½® 32--126 的字符视为å¯è§), \ConTeXt\ (0--255 都视为å¯è§) 和与 -\OMEGA\ 相关的格å¼ã€‚缺çœçš„情况几乎与 \TL\,2003 完全一致,但通过更简æ´çš„æ–¹å¼å®žçŽ°ï¼Œå¹¶å…许 -更多定制。å‚è§ \CDref{texmf/doc/web2c/web2c.html\#TCX-files} -{\texttt{texmf/doc/web2c/web2c.html\#TCX-files}}。 -(å¦å¤–,如果é‡åˆ° Unicode 输入,\TeX\ å¯èƒ½ä¼šåœ¨æ˜¾ç¤ºé”™è¯¯ä¸Šä¸‹æ–‡æ—¶è¾“出åŠä¸ªå­—符,因为它是基于 -字节æµæ¥å¤„ç†è¾“入的。) - -\item \textsf{pdfetex} 现在是除 (plain) \textsf{tex} 外所有格å¼çš„默认引擎 (当然 -以 \textsf{latex} è¿™ç§æ–¹å¼è¿è¡Œæ—¶å®ƒè¿˜æ˜¯ç”Ÿæˆ \acro{DVI})。这样一æ¥ï¼Œè‡³å°‘ \textsf{pdftex} -的微调排版 (microtypographic) 技术å¯ä»¥åœ¨ \LaTeX, \ConTeXt 等格å¼ä¸­ä½¿ç”¨ï¼Œå¦å¤– \eTeX\ -的特性也包å«åœ¨å…¶ä¸­ (\OnCD{texmf-dist/doc/etex/base/})。 - -这还说明\emph{比以å‰ä»»ä½•æ—¶å€™éƒ½æ›´æœ‰å¿…è¦}使用 (对 plain å’Œ \LaTeX\ 都适用的) -\pkgname{ifpdf} å®åŒ…或其类似代ç ï¼Œå› ä¸ºåªæ£€æŸ¥ \cs{pdfoutput} 或其他原语是å¦å·²ç»å®šä¹‰ -ä¸å†æ˜¯åˆ¤æ–­æ˜¯å¦å¤„于 \acro{PDF} 输出状æ€çš„å¯é æ–¹æ³•ã€‚我们在这一年尽å¯èƒ½åœ°ä¿æŒå‘ä¸‹å…¼å®¹ï¼Œä½†ä»¥åŽ -å³ä½¿åœ¨è¾“出 \acro{DVI} æ—¶ \cs{pdfoutput} 也å¯èƒ½å·²ç»å®šä¹‰ã€‚ - -\item pdf\TeX\ (\url{http://pdftex.org}) 新增了许多特性: - - \begin{itemize*} - - \item å¯ä»¥ä½¿ç”¨ \cs{pdfmapfile} å’Œ \cs{pdfmapline} æ¥åœ¨å•ç‹¬æ–‡æ¡£å†…指定字体映射文件。 - - \item å¯ä»¥æ›´æ–¹ä¾¿åœ°ä½¿ç”¨æŽ’版微调 (Microtypographic) 和字体延展 (font expansion) - 技术了。\\ - \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} - - \item 原æ¥ä½¿ç”¨ä¸“有格å¼çš„é…置文件 \filename{pdftex.cfg} 里的选项现在都必须改用 - \TeX{} 原语æ¥è®¾ç½®ï¼Œé€šå¸¸æ”¾åœ¨ \filename{pdftexconfig.tex} 里é¢ï¼Œä¸å†æ”¯æŒ - \filename{pdftex.cfg} çš„é…置方å¼ã€‚æ¯æ¬¡ä¿®æ”¹ \filename{pdftexconfig.tex} - 之åŽéƒ½å¿…é¡»é‡æ–°ç”Ÿæˆ \filename{.fmt} 文件。 - - \item å‚è§ pdf\TeX\ 手册以了解更多信æ¯ï¼š\OnCD{texmf/doc/pdftex/manual}。 - - \end{itemize*} - -\item \cmdname{tex} (ä»¥åŠ \cmdname{mf} å’Œ \cmdname{mpost}) 中的 \cs{input} -原语现在支æŒé€šè¿‡åŒå¼•å·æ¥å¼•ç”¨åŒ…å«ç©ºæ ¼å’Œç‰¹æ®Šå­—符的文件。一个典型的例å­å¦‚下: -\begin{verbatim} -\input "filename with spaces" % plain -\input{"filename with spaces"} % latex -\end{verbatim} -å‚阅 \Webc{} 文档以了解更多信æ¯ï¼š\OnCD{texmf/doc/web2c}。 - -\item enc\TeX\ 的支æŒçŽ°åœ¨å·²è¢«åŒ…å«åœ¨ \Webc{} 中,因而所有 \TeX\ 程åºéƒ½å¯ä»¥é€šè¿‡ -\optname{-enc} å‚æ•°å¯ç”¨è¿™ä¸€æ”¯æŒ \Dash \emph{å‰æ是构建好了格å¼æ–‡ä»¶}。enc\TeX\ -æ供了对输入输出通用的é‡æ–°ç¼–ç åŠŸèƒ½ï¼Œå®žçŽ°å¯¹ Unicode (以 \acro{UTF}-8 ç¼–ç çš„å½¢å¼) -的完整支æŒã€‚å‚è§ \OnCD{texmf-dist/doc/generic/enctex/} å’Œ -\url{http://www.olsak.net/enctex.html}。 - -\item æ供了 Aleph 这套新的 \TeX{} 引擎,它将 \eTeX\ å’Œ \OMEGA\ åˆå¹¶åˆ°äº†ä¸€èµ·ã€‚ -关于 Aleph 的部分信æ¯å¯ä»¥åœ¨ \OnCD{texmf-dist/doc/aleph/base} -å’Œ \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph} 找到。Aleph -çš„ \LaTeX æ ¼å¼æ–‡ä»¶ç§°åš \textsf{lamed}。 - -\item 最新å‘布的 \LaTeX\ 包å«äº†æ˜¯æ–°ç‰ˆçš„ \acro{LPPL} 授æƒåè®®\Dash 这一å议已被 -Debian 首肯。\LaTeX\ å…¶ä»–çš„æ›´æ–°è¯·è§ \OnCD{texmf-dist/doc/latex/base} 下的 -\filename{ltnews} 文件。 - -\item 包å«äº†ä¸€ä¸ªå«åš \cmdname{dvipng} 的新程åºï¼Œç”¨äºŽå°† \acro{DVI} 转æ¢ä¸º -\acro{PNG} 图åƒæ–‡ä»¶ã€‚å‚è§ \OnCD{texmf/doc/man/man1/dvipng.1}。 - -\item 我们在作者 (Claudio Beccari) çš„åŒæ„下,将 \pkgname{cbgreek} 包å«çš„ -字体数é‡å‡å°‘到中等。去除了ä¸å¯è§ã€è½®å»“å’Œé€æ˜Žç‰ˆæœ¬çš„字体,这些字体几乎很少用到。而我们 -的光盘镜åƒéœ€è¦ç©ºé—´ã€‚完整版本当然还是在 \acro{CTAN} æä¾› -(\url{http://www.ctan.org/tex-archive/fonts/greek/cb})。 - -\item 去掉了 \cmdname{oxdvi},改为åªä½¿ç”¨ \cmdname{xdvi}。 - -\item ä¸å†ä¸º \cmdname{tex}, \cmdname{mf}, å’Œ \cmdname{mpost} 程åºåˆ›å»º -\cmdname{ini} å’Œ \cmdname{vir} 开头的命令链接,比如 -\cmdname{initex}。\cmdname{ini} 的功能早在几年å‰å°±é€šè¿‡ \optname{-ini} -命令行å‚æ•°æ供了。 - -\item 去掉了 \textsf{i386-openbsd} å¹³å°çš„支æŒã€‚因为在 \acro{BSD} Ports -系统中已ç»åŒ…å«äº† \pkgname{tetex} 软件包,而 \acro{GNU/}Linux å’Œ -Free\acro{BSD} 下的二进制版本都已存在,所以志愿者的时间å¯ä»¥èŠ±åœ¨å…¶ä»–的地方了。 - -\item 至少在 \textsf{sparc-solaris} å¹³å°ä¸‹ï¼Œä½ å¿…须设置好 -\envname{LD\_LIBRARY\_PATH} 环境å˜é‡æ‰èƒ½æ‰§è¡Œ \pkgname{t1utils} 包å«çš„程åºã€‚ -因为这些程åºæ˜¯ä½¿ç”¨ C++ 编写的,其è¿è¡Œæ—¶åº“没有固定的ä½ç½®ã€‚(这一情况并éžåœ¨ 2004 版 -中首次出现,但现在æ‰å†™å…¥æ–‡æ¡£) 与之类似,\textsf{mips-irix} å¹³å°ä¸‹éœ€è¦ç”¨åˆ° -\acro{MIPS}pro 7.4 è¿è¡Œæ—¶åº“。 - -\end{itemize} - -\subsubsection{2005} - -2005 年一如往常,å®åŒ…和程åºéƒ½æœ‰å¤§é‡çš„更新。底层结构和 2004 年相比ä¿æŒäº†ç¨³å®šï¼Œ -ä¸è¿‡ä»ç„¶å­˜åœ¨ä¸€äº›å˜åŒ–。 - -\begin{itemize} - -\item 引入了新的 \cmdname{texconfig-sys}, \cmdname{updmap-sys}, å’Œ - \cmdname{fmtutil-sys} 安装脚本,用于修改系统目录树下的é…置。而原有的 - \cmdname{texconfig}, \cmdname{updmap}, å’Œ \cmdname{fmtutil} - 则用于修改针对å•ä¸ªç”¨æˆ·çš„文件 (放在 \dirname{$HOME/.texlive2005} - 目录下的)。 - -\item 增加了对应的 \envname{TEXMFCONFIG} å’Œ \envname{TEXMFSYSCONFIG} - å˜é‡ï¼Œåˆ†åˆ«ç”¨äºŽè®¾ç½®é’ˆå¯¹ç”¨æˆ·å’Œç³»ç»Ÿçš„,专门存放é…置文件的目录树。所以你需è¦å°†ä¸ªäººä½¿ç”¨çš„ - \filename{fmtutil.cnf} å’Œ \filename{updmap.cfg} - 放到åˆé€‚ä½ç½®ã€‚ä¸è¿‡è¿˜æœ‰ä¸€ç§æ–¹æ³•æ˜¯åœ¨ \filename{texmf.cnf} 里边é‡æ–°å®šä¹‰ - \envname{TEXMFCONFIG} 或 \envname{TEXMFSYSCONFIG} - å˜é‡ã€‚无论如何,这两个值对应的实际目录都必须正确存在。å‚è§ç¬¬ - \pageref{sec:texmftrees} 页的第 \ref{sec:texmftrees} 节。 - -\item 虽然我们在上一年就已ç»ä½¿ç”¨äº† \cmdname{pdfetex} 作为输出程åºï¼Œä½†åœ¨å®ƒè¾“出 \dvi\ - æ ¼å¼æ—¶ä¼šç¦ç”¨ \verb|\pdfoutput| 等原语 - (primitive)。这一年,我们按照预期计划å–消了这一兼容性é™åˆ¶ã€‚所以,如果你的文档里使用了 - \verb|\ifx\pdfoutput\undefined| 这样的语å¥æ¥åˆ¤æ–­æ˜¯å¦æ­£åœ¨ PDF - 输出模å¼ä¸‹ï¼ŒçŽ°åœ¨å°±å¿…须修改了。你å¯ä»¥ä½¿ç”¨ \pkgname{ifpdf.sty} å®åŒ… (对 plain \TeX\ - å’Œ \LaTeX{} 都适用) æ¥åˆ¤æ–­ï¼Œæˆ–者仿照这个文件里的判断原ç†è‡ªå·±å†™ä¸€ä¸ªã€‚ - -\item 上一年,我们将格å¼æ–‡ä»¶çš„输出改æˆäº†å’Œè¿™äº›æ–‡ä»¶æœ¬èº«ä¸€æ ·çš„ 8 - ä½å­—符。在你需è¦çš„情况下,å¯ä»¥ä½¿ç”¨æ–°çš„ TCX 文件 \filename{empty.tcx} æ¥èŽ·å¾—原有的 - \verb|^^| 表示方å¼ã€‚例如: - -\begin{verbatim} -latex --translate-file=empty.tcx yourfile.tex -\end{verbatim} - -\item æ–°å¢žäº†ç”¨äºŽè½¬æ¢ DVI 为 PDF çš„ \cmdname{dvipdfmx} 程åºï¼Œè¿™æ˜¯ - \cmdname{dvipdfm} 的一个比较活跃更新的版本 (我们ä»ç„¶æä¾› - \cmdname{dvipdfm},但ä¸å»ºè®®ä½ ç»§ç»­ä½¿ç”¨)。 - -\item æ–°å¢žäº†å« \cmdname{pdfopen} å’Œ \cmdname{pdfclose} 的两个程åºï¼Œç”¨äºŽæŽ§åˆ¶ - Adobe Acrobat\slash Reader 在ä¸é‡å¯ç¨‹åºçš„情况下é‡æ–°è½½å…¥ pdf 文件。(其他的 - pdf 阅读器,如 \cmdname{xpdf}, \cmdname{gv}, å’Œ - \cmdname{gsview},都ä¸ä¼šé‡åˆ°è¿™ä¸ªé—®é¢˜ã€‚) - -\item 为了ä¿æŒä¸€è‡´æ€§ï¼Œå°† \envname{HOMETEXMF} å’Œ \envname{VARTEXMF} - 环境å˜é‡åˆ†åˆ«æ›´å为 \envname{TEXMFHOME} å’Œ - \envname{TEXMFSYSVAR}。还有一个针对å•ç‹¬ç”¨æˆ·çš„ \envname{TEXMFVAR} - 环境å˜é‡å¯ç”¨ã€‚å‚è§ä¸Šé¢çš„第一点。 - -\end{itemize} - - -\subsubsection{2006--2007} - -2006--2007 年,\TL{} 的一个é‡å¤§å˜åŒ–是增加了 \XeTeX{},以 \texttt{xetex} å’Œ -\texttt{xelatex} 程åºçš„å½¢å¼æ供。请å‚è§ \url{http://scripts.sil.org/xetex}。 - -\MP{} 也有å¯è§‚的更新,并计划在未æ¥å®žçŽ°æ›´å¤šçš„改进 -(\url{http://tug.org/metapost/articles}),pdf\TeX{} åŒæ ·å¦‚æ­¤ -(\url{http://tug.org/applications/pdftex})。 - -\TeX\ \filename{.fmt} (缓存格å¼) 文件和用于 MetaPost å’Œ \MF\ 的类似文件 -现在存储在 \dirname{texmf/web2c} çš„å­ç›®å½•ä¸­è€Œä¸ç›´æŽ¥æ”¾åœ¨ \dirname{texmf/web2c} -目录下 (ä¸è¿‡è€ƒè™‘到现有的 \filename{.fmt} 文件,直接放置在这个目录下的文件ä»ç„¶ -能被æœç´¢åˆ°)。å­ç›®å½•çš„å称是根æ®å½“å‰ä½¿ç”¨çš„``引擎''决定的,比如 \filename{tex} -或 \filename{pdftex} 或 \filename{xetex}。这个å˜åŒ–ä¸ä¼šå¯¹æ—¥å¸¸ä½¿ç”¨å¸¦æ¥ä»»ä½• -å½±å“。 - -(plain) \texttt{tex} 程åºä¸å†é€šè¿‡è¯»å– \texttt{\%\&} 开头的第一行æ¥å†³å®š -执行何ç§æ ¼å¼ï¼Œè€Œéµå¾ªçº¯ç²¹çš„ Knuth 风格 \TeX\ 的传统。(\LaTeX\ å’Œå…¶ä»–æ‰€æœ‰çš„ç¨‹åº -ä»ç„¶è¯»å– \texttt{\%\&} 开头的行。) - -当然,和往常一样,这一年里你能看到æˆç™¾ä¸Šåƒçš„å®åŒ…与程åºå¾—到更新。也和往常一样, -进一步的更新请使用 \acro{CTAN} (\url{http://www.ctan.org})。 - -从内部角度上看,æºä»£ç æ ‘现在改为使用 Subversion 管ç†ï¼Œå¹¶åœ¨æˆ‘们的主页上æ供了 -到 Web ç•Œé¢çš„链接,用于æµè§ˆä»£ç æ ‘。我们希望它能æˆä¸ºæœªæ¥å‡ å¹´ä¸­ç¨³å®šçš„å¼€å‘ -å¹³å°ã€‚ - -末了,2006 年五月 Thomas Esser 宣布他将åœæ­¢ te\TeX{} -(\url{http://tug.org/tetex}) 的更新。这样一æ¥ï¼Œå¤§å®¶å¯¹ \TL{} 的兴趣大增,尤其是在 -\GNU/Linux å‘行版中。(\TL{} æ供了一套新的 \texttt{tetex} 安装方案, -几乎和原有的 te\TeX{} 毫无二致。) 我们希望这些å˜åŒ–将最终转æ¢ä¸ºå¯¹æ•´ä¸ª \TeX\ -环境的改进,从而æ¯ä¸ªäººéƒ½ä¼šå—益。 - -\medskip \noindent -对过去历å²çš„最终一点æ示: 所有版本的 \TL{},包括 \CD\ 标签这些附属æ料,都在 -\url{ftp://tug.org/historic/systems/texlive} æ供。 - - -\subsection{现状} -\label{sec:tlcurrent} - -在 2008 年,整个 \TL{} 的基础架构都é‡æ–°è®¾è®¡è¿‡å¹¶é‡æ–°å®žçŽ°äº†ã€‚安装的完整 -ä¿¡æ¯è¢«å­˜æ”¾åœ¨ \filename{tlpkg/texlive.tlpdb} 这个纯文本文件中。 - -除了许多其他的功能外,我们终于å¯ä»¥é€šè¿‡ Internet 在安装åŽæ›´æ–° \TL{} -了,这是 MiK\TeX\ æ—©å·²æ供了许多年的特性。我们希望能定期更新 \CTAN 上 -æ–°å‘布的软件包。 - -包å«äº†ä¸€ä¸ªé‡è¦çš„新引擎 Lua\TeX\ (\url{http://luatex.org}),除了 -在排版上çµæ´»æ€§æ›´ä¸Šä¸€å±‚楼以外,它还æ供了一个优秀的脚本语言供 \TeX\ -文档内外使用。 - -对 Windows 和基于 Unix 系统的支æŒçŽ°åœ¨è¦ä¸€è‡´å¾—多了。尤其是大部分 Perl å’Œ -Lua 脚本都能在 Windows 下使用,通过 \TL 内部包å«çš„ Perl。 - -æ–°çš„ \cmdname{tlmgr} 脚本 (第 \ref{sec:tlmgr} 节) 是在åˆå§‹å®‰è£…åŽç®¡ç† -\TL{} 的通用界é¢ã€‚它处ç†äº†è½¯ä»¶åŒ…æ›´æ–°å’ŒåŽç»­çš„æ ¼å¼æ–‡ä»¶ã€map 文件和语言文件 -çš„é‡æ–°ç”Ÿæˆï¼Œå¹¶å¯é€‰åœ°åŒ…å«äº†æœ¬åœ°æ·»åŠ çš„内容。 - -éšç€ \cmdname{tlmgr} 到æ¥ï¼Œç¦ç”¨äº† \cmdname{texconfig} 中编辑格å¼å’Œ -æ–­å­—é…置文件的功能。 - -今年还æ供了大多数平å°çš„ \cmdname{xindy} 索引生æˆç¨‹åº -(\url{http://xindy.sourceforge.net})。 - -\cmdname{kpsewhich} 现在å¯ä»¥æŠ¥å‘Šç»™å®šæ–‡ä»¶çš„æ‰€æœ‰åŒ¹é… (\optname{--all} -å‚æ•°) 并é™åˆ¶åˆ—å‡ºç‰¹å®šç›®å½•ä¸‹çš„åŒ¹é… (\optname{--subdir} å‚æ•°)。 - -\cmdname{dvipdfmx} 程åºçŽ°åœ¨æ”¯æŒç”¨ \cmdname{extractbb} 命令æ¥è§£æž -bounding box ä¿¡æ¯ï¼Œè¿™æ˜¯ \cmdname{dvipdfm} 包å«ä½†æœªæ›¾å‡ºçŽ°åœ¨ -\cmdname{dvipdfmx} 中的最åŽä¸€ä¸ªåŠŸèƒ½ã€‚ - -去除了 \filename{Times-Roman}, \filename{Helvetica} 等字体别å。ä¸åŒçš„ -å®åŒ…对它们的ç†è§£ä¸åŒ (尤其是编ç çš„处ç†ä¸ä¸€æ ·),所以没有什么好的办法能解 -决。 - -去除了 \pkgname{platex} æ ¼å¼æ–‡ä»¶ï¼Œä»¥é¿å…与日文 \pkgname{platex} 的命å -冲çªï¼Œ\pkgname{polski} å®åŒ…现在被用作主è¦çš„波兰语支æŒã€‚ - -从内部而言 \web\ 字符串 pool 文件被编译进了二进制文件中,这样å¯ä»¥æ–¹ä¾¿ -å‡çº§ã€‚ - -最终 Donald Knuth 在他的 `\TeX\ tuneup of 2008' 中的更新也被包å«åœ¨è¿™æ¬¡ -å‘布中。å‚è§ \url{http://tug.org/TUGboat/Articles/tb29-2/tb92knut.pdf}。 - -\subsection{未æ¥} - -\emph{\TL{} 并ä¸å®Œç¾Žï¼} (也永远ä¸ä¼šè¾¾åˆ°å®Œç¾Žã€‚) 我们希望继续å‘行新的版本,也希望 -æ供更多的帮助文档ã€æ›´å¤šçš„实用程åºã€æ›´å¤šçš„安装程åºï¼Œå½“然还有更多更新的å®åŒ…与字体。这个 -工作是由压力巨大的志愿者在其空闲时间完æˆçš„,也有很多ä¸å¤Ÿå®Œå–„的地方。请å‚è§ -\url{http://tug.org/texlive/contribute.html}。 - -请把更正ã€å»ºè®®æˆ–者æ供帮助的æ„æ„¿å‘é€åˆ°ï¼š -\begin{quote} -\email{tex-live@tug.org} \\ -\url{http://tug.org/texlive} -\end{quote} - -\medskip -\noindent \textsl{ç¥ä½ ä½¿ç”¨ \TeX\ 愉快ï¼} - -\section{翻译说明} - -这里对简体中文版本《\TL{} 指å—》,å³æœ¬æ–‡æ¡£ä¸­éµå¾ªçš„翻译惯例作一简è¦è¯´æ˜Žï¼š - -\begin{itemize} - -\item package, 视上下文,有时翻译为软件包,有时翻译为å®åŒ…。 -\item format file, å³ \TeX{} 程åºä¸€èˆ¬éƒ½ä¼šé¢„载入的 \texttt{.fmt} -文件。本文档中翻译为格å¼æ–‡ä»¶ã€‚ -\item scheme, 本文档中译为 (安装) 方案。 -\item collection, 本文档中译为 (软件) 集åˆã€‚ -\item 本文档中有时对原文没有采用é€å­—é€å¥çš„对比翻译,而是总括其æ„æ€ï¼Œè½¬æ¢ä¸º -更易为中文 \TeX{} 用户习惯的表达方å¼ã€‚ -\item architecture/platform, 是æ„æ€æ¯”较相近的è¯ï¼ŒåŸºæœ¬ä¸Šæ˜¯åªæŸç§ CPU -和对应这个 CPU çš„æ“作系统。比如 i386-linux。本文里翻译为架构ã€å¹³å°ã€ä½“ç³» -结构等等。 -\item binary, 二进制文件,其实就是说å¯æ‰§è¡Œç¨‹åºæ–‡ä»¶å’Œåº“文件了。 - -\end{itemize} - -2007 年的简体中文版本由 Jiang Jiang, Jinsong Zhao, Yue Wang, -Helin Gai 翻译。其中 Jinsong Zhao è´Ÿè´£ Windows 部分的翻译,Yue Wang -å’Œ Helin Gai 进行了校对,Jiang Jiang 则负责其余的翻译和统稿。 - -2008 年的简体中文版本由 Jiang Jiang, Yue Wang å’Œ Jinsong Zhao 翻译。 - -\end{document} diff --git a/Master/texmf/doc/texlive/source/texlive-common/examples/ex5.tex b/Master/texmf/doc/texlive/source/texlive-common/examples/ex5.tex new file mode 100644 index 00000000000..51a49fb670e --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-common/examples/ex5.tex @@ -0,0 +1,6 @@ +TEXMF = {$TEXMFLOCAL,!!$TEXMFMAIN} +TEXINPUTS.latex = .;$TEXMF/tex/{latex,generic;}// +TEXINPUTS.fontinst = .;$TEXMF/tex//;$TEXMF/fonts/afm// +% e-TeX related files +TEXINPUTS.elatex = .;$TEXMF/{etex,tex}/{latex,generic;}// +TEXINPUTS.etex = .;$TEXMF/{etex,tex}/{eplain,plain,generic;}// diff --git a/Master/texmf/doc/texlive/source/texlive-common/examples/ex6.tex b/Master/texmf/doc/texlive/source/texlive-common/examples/ex6.tex new file mode 100644 index 00000000000..7a56896e61c --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-common/examples/ex6.tex @@ -0,0 +1,56 @@ +\begin{figure*}[tp] +\centering +\begin{BVerbatim}[fontsize=\small] +debug:start search(file=texmf.cnf, must_exist=1, find_all=1, + path=.:/usr/local/bin/texlive:/usr/local/bin: + /usr/local/bin/texmf/web2c:/usr/local: + /usr/local/texmf/web2c:/.:/./teTeX/TeX/texmf/web2c:). +kdebug:start search(file=ls-R, must_exist=1, find_all=1, + path=~/tex:/usr/local/texmf). +kdebug:search(ls-R) =>/usr/local/texmf/ls-R +kdebug:start search(file=aliases, must_exist=1, find_all=1, + path=~/tex:/usr/local/texmf). +kdebug:search(aliases) => /usr/local/texmf/aliases +kdebug:start search(file=config.ps, must_exist=0, find_all=0, + path=.:~/tex:!!/usr/local/texmf/dvips//). +kdebug:search(config.ps) => /usr/local/texmf/dvips/config/config.ps +kdebug:start search(file=/root/.dvipsrc, must_exist=0, find_all=0, + path=.:~/tex:!!/usr/local/texmf/dvips//). +search(file=/home/goossens/.dvipsrc, must_exist=1, find_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//). +kdebug:search($HOME/.dvipsrc) => +kdebug:start search(file=config.cms, must_exist=0, find_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//). +kdebug:search(config.cms) +=>/usr/local/texmf/dvips/cms/config.cms +\end{BVerbatim} +\caption{Finding configuration files}\label{fig:dvipsdbga} + +\bigskip + +\begin{BVerbatim}[fontsize=\small] +kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro +\end{BVerbatim} +\caption{Finding the prolog file}\label{fig:dvipsdbgb} + +\bigskip + +\begin{BVerbatim}[fontsize=\small] +kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, + path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: + /var/tex/fonts/tfm//). +kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm +kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, + ... + +kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb +[1] +\end{BVerbatim} +\caption{Finding the font file}\label{fig:dvipsdbgc} +\end{figure*} diff --git a/Master/texmf/doc/texlive/source/texlive-common/examples/ex6a.tex b/Master/texmf/doc/texlive/source/texlive-common/examples/ex6a.tex new file mode 100644 index 00000000000..bbc9f5b42a7 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-common/examples/ex6a.tex @@ -0,0 +1,24 @@ +\begin{BVerbatim}[fontsize=\small] +debug:start search(file=texmf.cnf, must_exist=1, find_all=1, + path=.:/usr/local/bin/texlive:/usr/local/bin: + /usr/local/bin/texmf/web2c:/usr/local: + /usr/local/texmf/web2c:/.:/./teTeX/TeX/texmf/web2c:). +kdebug:start search(file=ls-R, must_exist=1, find_all=1, + path=~/tex:/usr/local/texmf). +kdebug:search(ls-R) =>/usr/local/texmf/ls-R +kdebug:start search(file=aliases, must_exist=1, find_all=1, + path=~/tex:/usr/local/texmf). +kdebug:search(aliases) => /usr/local/texmf/aliases +kdebug:start search(file=config.ps, must_exist=0, find_all=0, + path=.:~/tex:!!/usr/local/texmf/dvips//). +kdebug:search(config.ps) => /usr/local/texmf/dvips/config/config.ps +kdebug:start search(file=/root/.dvipsrc, must_exist=0, find_all=0, + path=.:~/tex:!!/usr/local/texmf/dvips//). +search(file=/home/goossens/.dvipsrc, must_exist=1, find_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//). +kdebug:search($HOME/.dvipsrc) => +kdebug:start search(file=config.cms, must_exist=0, find_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//). +kdebug:search(config.cms) +=>/usr/local/texmf/dvips/cms/config.cms +\end{BVerbatim} \ No newline at end of file diff --git a/Master/texmf/doc/texlive/source/texlive-common/examples/ex6b.tex b/Master/texmf/doc/texlive/source/texlive-common/examples/ex6b.tex new file mode 100644 index 00000000000..5a5a92f1f22 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-common/examples/ex6b.tex @@ -0,0 +1,6 @@ +\begin{BVerbatim}[fontsize=\small] +kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro +\end{BVerbatim} \ No newline at end of file diff --git a/Master/texmf/doc/texlive/source/texlive-common/examples/ex6c.tex b/Master/texmf/doc/texlive/source/texlive-common/examples/ex6c.tex new file mode 100644 index 00000000000..5daaeaa184b --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-common/examples/ex6c.tex @@ -0,0 +1,14 @@ +\begin{BVerbatim}[fontsize=\small] +kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, + path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: + /var/tex/fonts/tfm//). +kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm +kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, + ... + +kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb +[1] +\end{BVerbatim} \ No newline at end of file diff --git a/Master/texmf/doc/texlive/source/texlive-common/install-w32-main.png b/Master/texmf/doc/texlive/source/texlive-common/install-w32-main.png new file mode 100644 index 00000000000..a8cc55f6070 Binary files /dev/null and b/Master/texmf/doc/texlive/source/texlive-common/install-w32-main.png differ diff --git a/Master/texmf/doc/texlive/source/texlive-common/psview.png b/Master/texmf/doc/texlive/source/texlive-common/psview.png new file mode 100644 index 00000000000..8322bdda693 Binary files /dev/null and b/Master/texmf/doc/texlive/source/texlive-common/psview.png differ diff --git a/Master/texmf/doc/texlive/source/texlive-common/stdcoll.png b/Master/texmf/doc/texlive/source/texlive-common/stdcoll.png new file mode 100644 index 00000000000..16a699ba3c6 Binary files /dev/null and b/Master/texmf/doc/texlive/source/texlive-common/stdcoll.png differ diff --git a/Master/texmf/doc/texlive/source/texlive-common/tlmgr-config.png b/Master/texmf/doc/texlive/source/texlive-common/tlmgr-config.png new file mode 100644 index 00000000000..7f2d3123689 Binary files /dev/null and b/Master/texmf/doc/texlive/source/texlive-common/tlmgr-config.png differ diff --git a/Master/texmf/doc/texlive/source/texlive-common/tlmgr-gui.png b/Master/texmf/doc/texlive/source/texlive-common/tlmgr-gui.png new file mode 100644 index 00000000000..9c45772503d Binary files /dev/null and b/Master/texmf/doc/texlive/source/texlive-common/tlmgr-gui.png differ diff --git a/Master/texmf/doc/texlive/source/texlive-common/w32client/README b/Master/texmf/doc/texlive/source/texlive-common/w32client/README new file mode 100644 index 00000000000..a09ea7cf560 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-common/w32client/README @@ -0,0 +1,26 @@ +The w32client pair of scripts configure a Windows system to make use +of an existing read-only TeX Live installation, typically on a +network drive. + +Copy these scripts to the root of the TeX live installation, +i.e. the same directory as texmf, texmf-dist etc. + +This pair of scripts is intended as a prototype. Normally, it should +work as-is, at least after copying to the right place, but you +should review the following items: + +- check which shortcuts you want to include (add_desktop_shortcut + and add_menu_shortcut) + +- Decide which file associations, if any, you want to create + (register_extension and register_filetype). Although we wrote the + functions for it, we decided in the end not to use them in the + regular installation. + +- You can comment out or remove the xetex stanza if you aren't going +- to use xetex. + +- If the directory layout is non-standard, you may have to edit the + texmf.cnf in the root of the installation. Use relative + directories, using $SELFAUTOPARENT, whenever possible. See + texmf/web2c/texmf.cnf for examples. diff --git a/Master/texmf/doc/texlive/source/texlive-common/w32client/install-w32client b/Master/texmf/doc/texlive/source/texlive-common/w32client/install-w32client new file mode 100755 index 00000000000..0de75a465fa --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-common/w32client/install-w32client @@ -0,0 +1,177 @@ +#!/usr/bin/env perl +# $Id$ +# copy this file and install-w32client.bat to the same directory +# as texmf, texmf-dist etc. + +# sample mini-installer to give Windows systems access to an +# existing TeXLive installation + +# it assumes a standard directory layout, which avoids hard-coded paths. +# if this is not the case, adjustments may be necessary. + +$^W = 1; + +use TeXLive::TLUtils qw(mkdirhier); +use TeXLive::TLWinGoo qw(non_admin add_texbindir_to_path setenv_reg + init_unshortbat add_desktop_shortcut add_menu_shortcut + register_extension register_file_type + update_assocs broadcast_env + create_uninstaller); +use strict; + +# the code below assumes that this script is in $texdir, +# the directory above texmf, texmf-dist etc. + +my $texdir=$0; +$texdir=~s!\\!/!g; +$texdir=~s!(.*)/.*$!$1!; + +# private runtime-generated files +$::texlive_release = '2008'; +my $texdirw = $ENV{'USERPROFILE'}.'/.texlive'.$::texlive_release; +$texdirw=~s!\\!/!g; +my $private_var = $texdirw.'/texmf-var'; +my $private_var_bsl = $private_var; +$private_var_bsl =~ s!/!\\!g; + +# make only per-user modifications +non_admin(); + +# general + +add_texbindir_to_path($texdir.'/bin/win32'); +broadcast_env(); + +my $mainmenu = "TeX Live 2008"; +my $texbindir_bsl = $texdir.'/bin/win32'; +$texbindir_bsl =~ s!/!\\!g; + +mkdirhier("$texdirw/tlpkg/installer"); +create_uninstaller($texdir, $texdirw, $private_var, $texdirw.'/texmf-config'); +init_unshortbat($texdirw); + +# if the path can't be fixed globally add command prompt +# with texbindir prepended to path + +if (uc(TeXLive::TLWinGoo::win_which_dir('tex.exe')) ne + uc($texdir.'/bin/win32') or + uc(TeXLive::TLWinGoo::win_which_dir('pdftex.exe')) ne + uc($texdir.'/bin/win32') or + uc(TeXLive::TLWinGoo::win_which_dir('luatex.exe')) ne + uc($texdir.'/bin/win32')) { + add_menu_shortcut( + $mainmenu, + 'TeX Live Prompt', + '', + $ENV{'COMSPEC'}, + "/k \"path $texbindir_bsl;%path%\"", + '', + ); +} + +# texlive manual + +add_menu_shortcut( + $mainmenu, + 'TeX Live Manual (en)', + '', # default pdf icon + $texdir.'/texmf-doc/doc/english/texlive-en/texlive-en.pdf', + '', + '', +); + +# texdoctk documentation browser + +if (-e $texdir.'/bin/win32/texdoctk.bat') { + add_menu_shortcut( + $mainmenu, + 'TeXdoc GUI', + '', # icon + $texdir.'/bin/win32/texdoctk.bat', + '', # arguments + 'batgui', # any non-null value to hide command-prompt + ) +} + +# psview + +add_desktop_shortcut( + $texdirw, + 'PS_View', + $texdir.'/tlpkg/tlpsv/psv.exe', # icon, not prog! + $texdir.'/bin/win32/psv.bat', + '', # no args + 'batgui', # any non-null value to hide command-prompt +); +add_menu_shortcut( + $mainmenu, + 'PS_View', + $texdir.'/tlpkg/tlpsv/psv.exe', # icon, not prog! + $texdir.'/bin/win32/psv.bat', + '', # no args + 'batgui', # any non-null value to hide command-prompt +); +# comment out if you prefer gsview +register_extension(".ps", "PostScript"); +register_extension(".eps", "PostScript"); +register_file_type("PostScript", + '"'.$texdir.'/tlpkg/tlpsv/gswxlua.exe" -g '. + '"'.$texdir.'/tlpkg/tlgs/bin/gsdll32.dll" -l '. + '"'.$texdir.'/tlpkg/tlpsv/psv.wx.lua" -p '. + '"'.$texdir.'/tlpkg/tlpsv/psv_view.ps" -sINPUT="%1"'); +update_assocs(); + +# dviout + +add_menu_shortcut( + $mainmenu, + 'DVIOUT', + $texdir.'/tlpkg/dviout/dviout.exe', + 'wscript', + $texdir."/bin/win32/dviout.vbs", + '', +); + +# xetex + +if (-e $texdir.'/bin/win32/xetex.exe') { + my $xetexmfcnf = $private_var.'/web2c'; + my $texmfcnf = $xetexmfcnf.';'.$texdir.'/texmf/web2c'; + setenv_reg('TEXMFCNF', $texmfcnf); + broadcast_env(); + mkdirhier($private_var."/fonts"); + system("xcopy", "/e", "/i", "/q", "/y", "\"$texbindir_bsl\\conf\"", + "\"$private_var_bsl\\fonts\\conf\""); + system("xcopy", "/e", "/i", "/q", "/y", "\"$texbindir_bsl\\cache\"", + "\"$private_var_bsl\\fonts\\cache\""); + if (open(FONTSCONF, "<$texdir/bin/win32/conf/fonts.conf")) { + my @lines = ; + close(FONTSCONF); + if (open(FONTSCONF, ">$private_var/fonts/conf/fonts.conf")) { + my $winfontdir; + $winfontdir = $ENV{'SystemRoot'}.'/fonts'; + $winfontdir =~ s!\\!/!g; + foreach (@lines) { + $_ =~ s!c:/Program Files/texlive/2008!$texdir!; + $_ =~ s!c:/windows/fonts!$winfontdir!; + print FONTSCONF; + } + close(FONTSCONF); + } else { + warn("Cannot open $private_var/fonts/conf/fonts.conf for writing\n"); + } + } else { + warn ("Cannot open $texdir/bin/win32/conf/fonts.conf\n"); + } + mkdirhier($xetexmfcnf); + if (open(TMF, ">$xetexmfcnf/texmf.cnf")) { + print TMF "FONTCONFIG_PATH=\$TEXMFVAR/fonts/conf\n"; + print TMF "FC_CACHEDIR=\$TEXMFVAR/fonts/cache\n"; + close TMF; + } else { + warn("Cannot open $xetexmfcnf/texmf.cnf for writing\n"); + } + $ENV{'TEXMFCNF'} = $texmfcnf; + $ENV{'PATH'} = $texbindir_bsl.';'.$ENV{'PATH'}; + system("\"$texbindir_bsl\\fc-cache.exe\"", "-v", "-r"); +} diff --git a/Master/texmf/doc/texlive/source/texlive-common/w32client/install-w32client.bat b/Master/texmf/doc/texlive/source/texlive-common/w32client/install-w32client.bat new file mode 100755 index 00000000000..0d22ada6688 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-common/w32client/install-w32client.bat @@ -0,0 +1,28 @@ +@echo off + +rem copy this file and install-w32client to the same directory +rem as texmf, texmf-dist etc. + +rem TeX Live Root; ends with backslash +rem This may also work with UNC names + +set texdir=%~dp0 +set tldrive=%~d0 + +%tldrive% +cd %texdir% + +rem use provided Perl + +set PERL5SAVE=%PERL5LIB% +set PERL5LIB=%texdir%tlpkg\tlperl\lib;%texdir%tlpkg +"%texdir%tlpkg\tlperl\bin\perl" "%~dpn0" %* +rem pause Done + +rem cleanup in case of start from command-line + +set PERL5LIB=%PERL5SAVE% +set PERL5SAVE= +set tldrive= +set texdir= +pause \ No newline at end of file diff --git a/Master/texmf/doc/texlive/source/texlive-cz/Makefile b/Master/texmf/doc/texlive/source/texlive-cz/Makefile new file mode 100644 index 00000000000..acbed97a89b --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-cz/Makefile @@ -0,0 +1,5 @@ +include ../texlive-en/Makefile +doc = texlive-cz +lang = czechslovak + + diff --git a/Master/texmf/doc/texlive/source/texlive-cz/cs-tex-live.sty b/Master/texmf/doc/texlive/source/texlive-cz/cs-tex-live.sty new file mode 100644 index 00000000000..7e2569d7776 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-cz/cs-tex-live.sty @@ -0,0 +1,458 @@ +\NeedsTeXFormat{LaTeX2e}[1995/12/01] +\ProvidesPackage{cs-tex-live}[2004/11/15 v1.22 TeX Live documentation style] +\RequirePackage{alltt} +\RequirePackage{array} +\RequirePackage{colortbl} +\RequirePackage{graphicx} +%\RequirePackage{here} +\RequirePackage{longtable} +%\iftrue +%\def\Hv@scale{.91} % to match x-height of Palatino +%\RequirePackage{palatino} +%\else +\usepackage{lmodern} +%\fi +\RequirePackage{tabularx} +\RequirePackage{shortvrb} +\RequirePackage[normalem]{ulem} +\RequirePackage[obeyspaces]{url} +\RequirePackage{xspace} +\usepackage[T1]{fontenc} +\usepackage[latin2]{inputenc} +\usepackage[czech]{babel}% +\usepackage{csquote} % do define \uv +\newcommand{\singleuv}[1]{,#1`} +\newcommand{\ctt}{\url{news:comp.text.tex}} +\newcommand{\kB}{KiB} +\newcommand{\MB}{MiB} +\newcommand\TKCS{\textsf{\TeX-kolekce}} +\newcommand\ProTeXt{Pro\TeX t} +\clubpenalty 10000 +\widowpenalty 10000 +\RequirePackage{europs} +\let\euro\EUR +\usepackage{comment} +%\newcommand\ncs{\protect\NN} +%\newcommand\NN[1]{\bgroup\color{red}#1\egroup} +%\def\p.{s.\,} +\def\p.{na stran\v{e}~} +% General squeezed itemize. +\newenvironment{itemize*}% + {\begin{itemize}% + \setlength{\itemsep}{0pt}% + \setlength{\parskip}{0pt}}% + {\end{itemize}} +% +% for a proper \acro command (even in the context of the definition in +% ltugboat -- \DRC overrides without checking) +% +\RequirePackage{relsize} +\DeclareRobustCommand{\acro}[1]{\textsmaller{#1}\@} +% +\RequirePackage{fancyvrb} +\DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=\normalsize} +\DefineVerbatimEnvironment{fverbatim}{Verbatim}{fontsize=\footnotesize} +\DefineVerbatimEnvironment{sverbatim}{Verbatim}{fontsize=\small} +\DefineVerbatimEnvironment{boxedverbatim} + {Verbatim}{fontsize=\scriptsize,frame=single} +\DefineVerbatimEnvironment{Verbatim}{Verbatim}{fontsize=\normalsize} +\def\verbatiminput#1{\VerbatimInput[fontsize=\scriptsize]{#1}} +\def\boxedverbatiminput#1{\VerbatimInput[frame=single,fontsize=\scriptsize]{#1}} +\def\listinginput#1#2{\VerbatimInput[fontsize=\scriptsize,firstnumber=#1,numbers=left]{#2}} +\MakeShortVerb\| +% +% +% Done with packages. +% +% Page layout. +\advance\textwidth by 1.1in +\advance\oddsidemargin by -.55in +\advance\evensidemargin by -.55in +% +\advance\textheight by 1in +\advance\topmargin by -.5in +\advance\footskip by -.5in +\pagestyle{headings} +% +% LaTeX parameters. +\renewcommand{\topfraction}{0.85} +\renewcommand{\floatpagefraction}{0.86} +\renewcommand{\textfraction}{0.1} +\renewcommand{\belowcaptionskip}{4pt} +\setcounter{tocdepth}{2} +\setcounter{topnumber}{5} +\setcounter{totalnumber}{5} +% +% linebreaking, etc. +\pretolerance=1000 +\tolerance=1500 +\hbadness=3000 +\vbadness=3000 +\hyphenpenalty=400 +\emergencystretch=.1\hsize +\relpenalty=500 +% +% fonts +\let\sl\it +\let\slfamily\itfamily +\let\textsl\textit +\def\ttdefault{cmtt} +% +% various sorts of names +\newcommand*{\pkgname}[1]{\textsf{#1}}% package name +\newcommand*{\optname}[1]{\texttt{#1}}% (package,class) option name +\newcommand*{\cmdname}[1]{\textsf{#1}}% command name +\newcommand*{\colname}[1]{\emph{#1}}% collection name +\newcommand*{\dirname}[1]{\path{#1}}% directory name +\newcommand*{\filename}[1]{\path{#1}}% file name +\newcommand*{\envname}[1]{\texttt{#1}}% environment variable name +\newcommand{\code}[1]{\texttt{#1}} +\newcommand{\file}[1]{\texttt{#1}} +\newcommand{\prog}[1]{\texttt{#1}} +\newcommand{\samp}[1]{\singleuv{\texttt{#1}}} +\newcommand{\var}[1]{\emph{#1}} +\newcommand{\ttvar}[1]{\texttt{\var{#1}}} +% Include an image. +% #1 - name of image (pictures/#1.jpg, always .jpg please) +% #2 - bb for html +% #3 - width for TeX +% +\def\tlimage#1#2#3{% + \ifnum \Status=2 % html + \includegraphics[#2]{pictures/#1.jpg} \\[5mm] + \else % not html + \includegraphics[width=#3]{pictures/#1} \\[5mm] + \fi +} + +\def\tlpng#1#2{% + \ifnum \Status=2 % html, want relative path in output + \includegraphics[bb=0 0 1 1]{#1.png}% + \else % not html, handled by TEXINPUTS in Makefile + \includegraphics[width=#2]{#1.png}% + \fi +} + +% underlined command input. +\def\Ucom#1{% + \uline{\rule[-.2\baselineskip]{0pt}{.9\baselineskip}\ttfamily #1}} +\def\CDref#1#2{\href{../../../../#1}{#2}} +\def\OnCD#1{\href{../../../../#1}{\path{#1}}} +%\def\OnCD#1{\hyper@linkurl{\path{#1}}{../../../../#1}} +% GUI menu/button/tab sequence: +\def\guiseq#1{\textsf{#1}} +\def\arw{\unskip\discretionary{\hbox{$\rightarrow$}}{\hbox{$\rightarrow$}}{\hbox{$\rightarrow$}}\ignorespaces} +% +% Special names. +\def\dpi{$\,$dpi\xspace} +\def\bs{{\protect\normalfont\ttfamily\char'134}} +\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} +\def\Q#1{\par\vskip6pt\leftline{#1}\par} +\def\hyph{-} +% +% many abbreviations. +\newcommand{\CS}{$\mathcal{C}\kern-.1667em\lower.5ex% + \hbox{$\mathcal{S}$}\kern-.075em $} +\def\AFMtoTFM{\cmdname{AFM2TFM}\null} +\def\bv{\emph{Baskerville}} +\let\BV=\bv +\def\Dash{\unskip\nobreak\thinspace--\thinspace\ignorespaces} +\def\dvicopy{\cmdname{dvicopy}} +\def\dvidvi{\cmdname{dvidvi}} +\def\dvips{\cmdname{dvips}} +\def\eTeX{$\varepsilon$-\TeX} +\def\fpTeX{\textrm{fp}\TeX\xspace} +\def\GFtoDVI{\cmdname{GFtoDVI}\null} +\def\GFtoPK{\cmdname{GFtoPK}\null} +\def\GFtype{\cmdname{GFtype}} +\def\GUI{\acro{GUI}\xspace} +\def\KPS{Kpathsea} +\def\La{La} +\def\OMEGA{$\Omega$} +\def\OzMF{OzMF} +\def\OzMP{OzMP} +\def\OzTeX{O\kern-.03em z\kern-.15em\TeX} +\def\PKtype{\cmdname{PKtype}} +\def\PLtoTF{\cmdname{PLtoTF}\null} +\def\teTeX{\textrm{te}\TeX\xspace} +\def\TeXLive{\TeX{} Live\xspace} +\let\TL=\TeXLive +\def\TFtoPL{\cmdname{TFtoPL}\null} +\def\TK{\textsf{\TeX-Collection}} +\def\TypeI{Type~1} +\def\VFtoVP{\cmdname{VFtoVP}\null} +\def\VPtoVF{\cmdname{VPtoVF}\null} +\def\Thanh{H\`an~Th\^e\llap{\raise 0.5ex\hbox{\'{}}}~Th\`anh} +\def\XEmTeX{\textrm{XEm}\TeX\xspace} +\def\XEmacs{\textrm{XEmacs}\xspace} +\def\Webc{Web2C} +\providecommand*{\CD}{\acro{CD}\xspace} +\providecommand*{\CTAN}{\acro{CTAN}\xspace} +\providecommand*{\DVD}{\acro{DVD}\xspace} +\providecommand*{\GNU}{\acro{GNU}\xspace} +\providecommand*{\HTML}{\acro{HTML}\xspace} +\providecommand*{\ISO}{\acro{ISO}\xspace} +%\providecommand*{\MacOSX}{Mac\-\acro{OSX}\xspace} +\providecommand*{\MacOSX}{Mac\,\acro{OS\,X}\xspace} +\providecommand*{\PS}{Post\-Script\xspace} +\providecommand*{\GS}{Ghost\-script\xspace} +\providecommand*{\TDS}{\acro{TDS}\xspace} +\providecommand*{\dvi}{\acro{DVI}\xspace} +\providecommand*{\web}{\texttt{web}\xspace} +% +% description-like environment that uses tt instead of bf, and doesn't +% go to the left margin. Without the \hfil, get an underfull box. +% Don't why \descriptionlabel doesn't. +\newenvironment{ttdescription} + {\begin{list}{label must be supplied}{% + \itemsep=0pt % these lists tend to have short descriptions + \let\makelabel=\ttdescriptionlabel}}% + {\end{list}} +\newcommand*\ttdescriptionlabel[1]{\hspace\labelsep + \normalfont\ttfamily #1\hfil} +% +% Likewise, for commands using sans serif. +\newenvironment{cmddescription} + {\begin{list}{label must be supplied}{% + \itemsep=0pt + \let\makelabel=\cmddescriptionlabel}}% + {\end{list}} +\newcommand*\cmddescriptionlabel[1]{%%\hspace\labelsep + \normalfont\sffamily #1\hfil} +% +\newlength\tmplen +\newsavebox{\wbox} +\newenvironment{warningbox}% + {\fboxsep .017\textwidth + \begin{lrbox}{\wbox} + \setlength{\tmplen}{\textwidth}% + \addtolength{\tmplen}{-2\fboxsep}% + \addtolength{\tmplen}{-.8pt}% twolines + \begin{minipage}{\tmplen}} + {\end{minipage}\end{lrbox}% + \bgroup\centering\fbox{\usebox{\wbox}}\egroup} +% +% lrbox is used as a representation marking. I changed it to +% lrBox in tne source file, to get closer to logical marking +\newsavebox{\mylrbox} +\newenvironment{lrBox} + {\begin{lrbox}{\mylrbox}} + {\end{lrbox}} +% +% +% output setup +% +\newif\ifSingleColumn +\providecommand{\Status}{0} +\typeout{Status is \Status, e.g.: } +% +% By default, we won't be creating hyperlinks. +\def\href#1#2{#2} +\def\hypertarget#1#2{} +\def\email#1{\href{mailto:#1}{\path{#1}}} % \path comes from url +\RequirePackage{texnames} +\ifx\PiC\undefined \def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC} \fi +\ifx\PiCTeX\undefined \def\PiCTeX{\PiC\kern-.11em\TeX} \fi +% +% +\ifcase\Status + % \Status = 0 + \typeout{TeX Live documentation for printing} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 1 + \typeout{TeX Live documentation in PDF format} + \RequirePackage[colorlinks,bookmarksopen, + pdfstartview={FitBH -320000},hyperindex]{hyperref} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 2 + \typeout{TeX Live documentation in HTML format} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + % read our config file, live4ht.cfg; q.v., for more definitions. + % hyperref load must come after the tex4ht load. + \RequirePackage[live4ht]{tex4ht} + \RequirePackage[tex4ht]{hyperref} \hyperlinkfileprefix{} + \def\CDref#1#2{\href{../../../../#1}{#2}} + \def\OnCD#1{\href{../../../../#1}{#1}} + \or + % \Status = 3 + \typeout{TeX Live documentation as a Zpravodaj issue!} + \RequirePackage{zpravodaj}% outline of Zpravodaj + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 4 + \typeout{TeX Live documentation as a TUB article} + \@ifundefined{Fonts}% + {\RequirePackage{ae}}% + {\RequirePackage[T1]{\Fonts}} + \SingleColumnfalse + \newenvironment{multicols}[1]{}{} +\fi +% +\ifnum \Status=4 +\else + %\RequirePackage{texnames} + \newcommand\ConTeXt{C\kern-.0333emon\-\kern-.0667em\TeX\kern-.0333emt} + \newcommand\MIKTEX{MiK\kern-.025em \TeX}% per www.miktex.org + \providecommand\TeXXeT{\TeX-{}-% + \kern-.1emX\kern-.125em\lower.5ex\hbox{E}\kern-.1667emT\@} +\fi +% +% hacking at sections etc., to pay attention to baskerville status +\newcommand{\@condend@multicols}{% + \ifSingleColumn + \else + \def\@tempa{multicols}% + \ifx\@tempa\@currenvir + \end{multicols}% + \fi + \fi +} +\let\Section\section +\renewcommand{\section}{% + \@ifstar + {\Section*}% + {% + \@condend@multicols + \@dblarg\@full@section + }% +} +\def\@full@section[#1]#2{% + \Section[#1]{#2}% + \ifSingleColumn\else\begin{multicols}{2}\fi +} +\let\SubSection\subsection +\renewcommand{\subsection}{% + \@ifstar{\SubSection*}% + {% + \@condend@multicols + \@dblarg\@full@subsection + } +} +\def\@full@subsection[#1]#2{% + \SubSection[#1]{#2}% + \ifSingleColumn\else\begin{multicols}{2}\fi +} + +% calm things down a bit if we're in a multiple-column version +\ifSingleColumn +\else + \def\@listI{\leftmargin\leftmargini + \parsep \z@ + \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ + \itemsep \z@ \@plus .1\p@ + } + \let\@listi\@listI + \@listi + \def\@listii{\leftmargin\leftmarginii + \labelwidth\leftmarginii\advance\labelwidth-\labelsep + \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ + \parsep \z@ + \itemsep \z@ \@plus .1\p@ + } + \def\@listiii{\leftmargin\leftmarginiii + \labelwidth\leftmarginiii\advance\labelwidth-\labelsep + \topsep 1\p@ \@plus 1\p@ \@minus 1\p@ + \parsep \z@ + \partopsep \z@ + \itemsep \topsep + } + \def\@listiv{\leftmargin\leftmarginiv + \labelwidth\leftmarginiv\advance\labelwidth-\labelsep + } + \def\@listv{\leftmargin\leftmarginv + \labelwidth\leftmarginv\advance\labelwidth-\labelsep + } + \def\@listvi{\leftmargin\leftmarginvi + \labelwidth\leftmarginvi\advance\labelwidth-\labelsep + } +\fi +% +% array package stuff +\def\arraybackslash{\let\\=\@arraycr} +\newcolumntype{P}[1]{>{\raggedright\arraybackslash}p{#1}} +% +% shaded rows (using facilities of colortbl) +% +\definecolor{pale}{gray}{.9} +\newcount\colrow +\gdef\RowColor{pale} +\def\SetRowColor{% + \rowcolor{\RowColor}% + \global\advance\colrow by1\relax + \ifodd\colrow + \gdef\RowColor{pale}% + \else + \gdef\RowColor{white}% + \fi +} +% redefine to hack up a reference even though we don't need it... +\renewcommand\@bibitem[1]{\if@filesw \immediate\write\@auxout + {\string\bibcite{#1}{?}}\fi\ignorespaces} +% +% \unknownTeXlive is a dummy texlive entry for the biblio +\newcommand\unknownTeXlive[2][\relax]{\textbf{\textsc{unknown}}% + \global\@all@unknown\expandafter{\the\@all@unknown{#2}}% +} +\newtoks\@all@unknown +\global\@all@unknown{} +\AtEndDocument{\@message@unknowns} +\def\@message@unknowns{\edef\@tempa{\the\@all@unknown}% + \ifx\@tempa\@empty + \else + \def\@tempa{*** TeX live package location of }% + \expandafter\@output@unknowns\the\@all@unknown\@empty + \fi +} +\def\@output@unknowns#1{\edef\@tempb{#1}% + \ifx\@tempb\@empty + \typeout{ unknown}% + \else + \message{\@tempa#1,}% + \def\@tempa{}% + \expandafter\@output@unknowns + \fi +} +% +% a hack for the bibliography +\bibliographystyle{tex-live} +\newif\iffirstbibentry +\global\firstbibentrytrue +\let\@@bibitem\bibitem +\renewcommand\bibitem{\iffirstbibentry + \global\firstbibentryfalse + \else + \\\SetRowColor + \fi + \@@bibitem +} + + +% for \Dings +\RequirePackage{pifont} +% available for inter-article dinglines +\def\Dings{\nopagebreak{\footnotesize\dingline{167}}} + +\ifnum \Status=3 +\newfont\fontmanual{logo10} % font used for the METAFONT logo, etc. +\renewcommand\MF{{\fontmanual META}\-{\fontmanual FONT}\spacefactor1000 } +\renewcommand\MP{{\fontmanual META}\-{\fontmanual POST}\spacefactor1000 } +\else +\RequirePackage{mflogo} +%\newfont\fontmanual{logo10} % font used for the METAFONT logo, etc. +%\newcommand\MF{{\fontmanual META}\-{\fontmanual FONT}\spacefactor1000 } +%\newcommand\MP{{\fontmanual META}\-{\fontmanual POST}\spacefactor1000 } +\fi + +% Silence font warnings about no bold typewriter in LM. +\def\@font@warning#1{}% + +% Silence hyperref warnings about \kern. +\def\HyPsd@Warning#1{}% + +\endinput diff --git a/Master/texmf/doc/texlive/source/texlive-cz/csquote.sty b/Master/texmf/doc/texlive/source/texlive-cz/csquote.sty new file mode 100644 index 00000000000..3644143647b --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-cz/csquote.sty @@ -0,0 +1,181 @@ +%%%%%%%%%%%%%%%%%%%%%% cut here %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +% +% File: CSQUOTE.TEX/STY +% Version: 1.1 +% +% Authors: Hunter Goatley +% (parts from QUOTE.TEX/STY) +% Petr Sojka +% +% Warranty: +% +% Copyright (c) 1992 by Hunter Goatley, Petr Sojka +% Permission to copy all or part of this work is granted, provided +% that the copies are not made or distributed for resale, and that +% the copyright notice and this notice are retained. +% +% THIS WORK IS PROVIDED ON AN "AS IS" BASIS. THE AUTHOR PROVIDES NO +% WARRANTY WHATSOEVER, EITHER EXPRESS OR IMPLIED, REGARDING THE WORK, +% INCLUDING WARRANTIES WITH RESPECT TO ITS MERCHANTABILITY OR FITNESS +% FOR ANY PARTICULAR PURPOSE. +% +% If you make any improvements, I'd like to hear about them. +% +% History: +% +% Oct 26, 92 - V1.0 first release +% Dec 14, 92 - V1.1 \uv added +% +% Abstract: +% +% This file defines the macros \csdoublequoteson and \csdoublequotesoff. +% These macros allows switching between standard and following behaviour: +% TeX replace the double-quote character (") with Czech +% left and right double-quotes. For example: +% +% "This is a test." ---> ,,This is a test.'' +% +% The double-quote character is still available via \dq. +% \" is still treated as the umlaut accent. +% +% This macro makes a couple of assumptions about the double-quotes: +% +% 1. Double-quotes are assumed to come in pairs. When replacing +% double-quotes, the macro alternates between ,, and ''. The only +% exception to this is noted in (2) below. +% 2. A double-quote at the beginning of a paragraph is always treated +% as ,,. This correctly handles the case where a quotation is +% continued into a second paragraph: +% +% "This is the first paragraph.\par +% "This is the second paragraph of the same quote." +% +% Normal TeX spacing after ,, and '' is maintained by saving and +% restoring the \spacefactor. +% +% Macros work both with plainTex and LaTeX. +% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +% +% HOW IT WORKS: +% +% The double-quote character (") is made active by \csdoublequoteson. +% The " macro keeps track of left-quote/right-quote pairs and inserts +% the appropriate ,, and '' in its place. +% +% Each character has a \spacefactor associated with it, which specifies +% the amount of stretch or shrink that a space following the character +% can have. Most characters have a factor of 1000, but some punctuation +% marks have higher spacefactors, most notably the period, which has a +% \spacefactor of 3000. This means the space following a period can +% stretch up to 3 times more than the space after a regular character, +% accounting for the increased space at the end of sentences. +% +% The ,, and '' ligatures are assigned \spacefactor's of 0, so that the +% \spacefactor that is applied to the next character is the same as that +% of the character preceding the quotes. Because " has been redefined as +% a macro, any spaces following " are swallowed by TeX. It was necessary +% to have this macro re-insert any needed space so that the following +% cases worked correctly: +% +% "This is a test," she said. --> ,,This is a test,'' she said. +% "This is in a list"; etc. --> ,,This is in a list''; etc. +% +% Without the added space, the first example becomes: +% +% ,,This is a test,''she said. +% +% The solution was to save the current \spacefactor before inserting a +% right double-quote, then resetting the \spacefactor after the +% insertion. The net effect was that the " macro has a \spacefactor +% of 0, which matches the way TeX treats ,, and ''. +% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +{% % Begin a group for which " is active +\catcode`\"=\active % Make " an active character +\catcode`\@=11 % Make @ an active character +% +% \csdoublequoteson +% +% This macro makes " an active character, resets the control sequence +% \dblqu@te to L (left), and defines \dq as a replacement for ". +% +\gdef\csdoublequoteson{% % \csdoublequoteson enables " + \gdef"{\czechquotes}% % Define " as \czechquotes + \global\catcode`\"=\active% % Make " an active character + \global\chardef\dq=`\"% % Double-quote char. via \dq + \global\let\dblqu@te=L% % Always start with a left double-quote + } % End of macro +% +% \bq, \eq +% +% These macros define default characters for czech left and right +% double quotes. Czech opening quote is created from two commas with +% kerning depending on fontdimen four parameter of current font. +% Better solution should be specially designed character with +% proper kernings; if you have such characters in fonts +% (e.g. in DC-fonts), use it instead. (e.g. define +% macros \bq and \eq e.g. \def\bq{\char"130 } +% in your document/style file-- not in csquote.sty!) +% Similar solution is used for czech right quote. +% +% \cs existence test, stolen from TeXbook exercise 7.7 +\def\ifundefined#1{\expandafter\ifx\csname#1\endcsname\relax }% +% +% another macro to be more efficient in time and space +\global\chardef\f@@r=4 +% +\ifundefined{bq}% +\gdef\bq{\kern-.25\fontdimen\f@@r\font,\kern-.8\fontdimen\f@@r\font,% + \kern-.35\fontdimen\f@@r\font}% +\fi +\ifundefined{eq}% +\gdef\eq{\kern-.35\fontdimen\f@@r\font`\kern-.8\fontdimen\f@@r\font`% + \kern-.25\fontdimen\f@@r\font} +\fi +% +% Macro \uv for other usage of \bq and \eq. +% +\ifundefined{uv}% + \gdef\uv#1{\bq #1\eq} +\fi +% +% Define the macro that will be executed whenever " is encountered. +% +\gdef\czechquotes{% + % If the double-quote is the first character in a new paragraph, + % make sure it becomes a left double-quote. This case can be + % detected by checking to see if TeX is currently in vertical mode. + % If so, the double-quote is at the beginning of the paragraph + % (since " hasn't actually generated any horizontal mode tokens + % yet, TeX is still in vertical mode). If the mode is vertical, + % set \dblqu@te equal to L. + % + \ifinner\else\ifvmode\let\dblqu@te=L\fi\fi% + % + % Now insert the appropriate left or right double-quote. + % + % If \dblqu@te is L, insert an opening quote and set \dblqu@te to R. + % + \if L\dblqu@te\bq\global\let\dblqu@te=R% + % + % Otherwise, save the current \spacefactor, insert '', set \dblqu@te + % to L, and reset the original \spacefactor. + % + \else% + \let\xxx=\spacefactor% % Save the \spacefactor + \eq% % Insert ending quote + \global\let\dblqu@te=L% % and reset \dblqu@te + \spacefactor\xxx% % Reset the \spacefactor + \fi% % End of \if L\dblqu@te... + } % End of " macro +} % End of group + +\gdef\csdoublequotesoff{% + \catcode`\"=12% % Set " back to other + } +% +% Czech quotes are default +% +\csdoublequoteson + diff --git a/Master/texmf/doc/texlive/source/texlive-cz/live4ht.cfg b/Master/texmf/doc/texlive/source/texlive-cz/live4ht.cfg new file mode 100644 index 00000000000..3fa6506696b --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-cz/live4ht.cfg @@ -0,0 +1,47 @@ +% tex4ht configuration file for the TeX Live documentation. +% Accumulated over many years. Public domain. +% +% html specifies the main output format. +% info for extra debugging info in the log files. + +% better approach is to have html in one piece (including footnotes). +% also the newest TeX4ht could produce UTF-8 output (-utf8 option) +\Preamble{charset=iso-8859-2,html,info,fn-in} + +% add extra stylesheet +\Configure{@HEAD}{\HCode{% +\Hnewline +\Hnewline +}} + +% or LaTeX complains it is missing. +\begin{document} + +\EndPreamble + +% simplify output for HTML. We leave TeX and LaTeX alone, since tex4ht +% actually does the lowered E (and raised A) in CSS. +\def\OMEGA{Omega} +\def\LaTeXe{LaTeX2e} +\def\eTeX{e-\TeX} +\def\acro#1{#1} +\def\MF{Metafont} +\def\BibTeX{BibTeX} +\def\warningbox{} +\def\endwarningbox{} + +\newif\ifhackliterals +\ifx\tldocenglish\undefined \else \hackliteralstrue \fi +\ifx\tldocrussian\undefined \else \hackliteralstrue \fi +\ifx\tldocgerman\undefined \else \hackliteralstrue \fi +% +\ifhackliterals + % these definitions cause "missing } inserted" at \end{tabularx} in + % French and Czech. don't know why. + % + % don't make these into links, as happens with \path. We only have a couple + % special characters that actually occur. + \def\dirname{\texttt\bgroup\catcode`\$=12 \catcode`\_=12 \finishliteral} + \def\finishliteral#1{#1\egroup} + \let\filename=\dirname +\fi diff --git a/Master/texmf/doc/texlive/source/texlive-cz/texlive-cz.tex b/Master/texmf/doc/texlive/source/texlive-cz/texlive-cz.tex new file mode 100644 index 00000000000..77d8ed9ea5e --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-cz/texlive-cz.tex @@ -0,0 +1,3030 @@ +% +% czechslovak/live.tex - TeXlive 2008 documentation -- Czech/Slovak translation +% +% TeX Live documentation. Originally written by Sebastian Rahtz and +% Michel Goossens, now maintained by Karl Berry and others. +% Public domain. +% +% 2008/08/12: v1.34 prvni korektury prekladu 2008 +% 2008/08/02: v1.33 aktualizacia prekladu 2008 +% 2007/01/24: v1.32 XeTeX URL and HH (config.manpath) change +% 2007/01/22: v1.31 last minute corrections by Staszek (2x) and ZW +% 2007/01/15: v1.30 corrections and typos +% 2007/01/14: v1.29 texlive2007 version (JB&PS) +% 2005/11/01: v1.28 last minute Staszek additions +% 2005/10/31: v1.27 texlive2005 version (JB&PS) +% 2004/11/18: v1.26 final release cleanup, latest changes by Staszek +% 2004/11/17: v1.24,25 typos corrected +% 2004/11/15: v1.21,22,23 corrections by KB, JB and others entered +% 2004/11/14: v1.20 first texlive2004 version (JB&PS) +% 2004/01/30: v1.19 postbulletin version release for CSTUG web +% 2004/01/22: v1.18 minor changes before final-2003 source release +% 2004/01/19: v1.16, v1.17 last-minute corrections before sending +% Bulletin to print +% 2004/01/18: modifications for CS bulletin by Z. Wagner +% 2004/01/07: version 1.15 +% 2003/12/08-10: Slovak and other Czech typos corrected +% 2003/12/06: Czech language typos/errors entered +% 2003/09/23: prepositions checked, v1.03 +% 2003/09/23: some typos, jch's email, v1.02 +% 2003/09/22: further error corrections, v1.01 +% 2003/09/18: final checking and error corrections, v1.0 release +% 2003/09/17: another changes in English version incorporated +% 2003/09/08: changes in English version from 09/04 to 09/06 incorporated +% 2003/09/06: fixes from Staszek +% 2003/09/05: touched by Karl +% 2003/09/04: fixes from Staszek and Fabrice +% 2003/09/05: translation started from english version as of Sep 1st by +% Petra & Petr S. +% 2003/09/01: fixes from Volker. +% 2003/08/12: fixes from Christer Gustafsson . +% 2003/07/07: substantial revisions by karl. +% ... deleted +% +% TODO +% +% -- Priklady ve slovenske casti aktualizovat z~anglicke verze +% (zustaly dosud z verze TeXlive 6). +% +% Translations: +% Copyright (c) 2003--2008 Petr Sojka +% Copyright (c) 2004--2008 Ján Bu¹a +% Copyright (c) 2003 Petra Sojková +% Copyright (c) 2001 Janka Chlebíková +% Permission is granted to copy, distribute and/or modify this document +% under the terms of the GNU Free Documentation License, Version 1.2 +% or any later version published by the Free Software Foundation; +% with no Invariant Sections, no Front-Cover Texts, and no +% Back-Cover Texts. A copy of the license is included in +% the section entitled "GNU Free Documentation License". + +\newif\ifforbulletin +\forbulletinfalse +%\forbulletintrue +\newcommand\cstlversion{1.34} +\newcommand\cstldate{12.\ srpna 2008} +\ifforbulletin + \providecommand\Status{3} % version for CSTUG bulletin Zpravodaj + \else + \providecommand\Status{1} % 2 html alebo 1 pdf +\fi +% +\ifnum\Status=2 % e.g. html generation via tex4ht + \def\classname{article} % need different doc class for html + \def\classoptions{11pt} +\else + \ifnum\Status=3 % Zpravodaj + \def\classname{article} + \def\classoptions{twoside,a5paper} +% \pdfpaperwidth=147.5mm +% \pdfpaperheight=210mm + \else \def\classname{artikel1} + \def\classoptions{11pt} + \fi +\fi + +\listfiles +\documentclass[\classoptions,slovak,english,czech]{\classname} +\usepackage{cs-tex-live} +\makeatletter +\newcommand\tubreflect[1]{% + \@ifundefined{reflectbox}{% + \message{A graphics package must be loaded for \string\XeTeX}% + }{% + \ifdim \fontdimen1\font>0pt + \raise 1.75ex \hbox{\kern.1em\rotatebox{180}{#1}}\kern-.1em + \else + \reflectbox{#1}% + \fi + }% +} +\def\tubhideheight#1{\setbox0=\hbox{#1}\ht0=0pt \dp0=0pt \box0 } +\def\XeTeX{\leavevmode + \tubhideheight{\hbox{X% + \lower.5ex \hbox{\kern-.125em\tubreflect{E}}% + \kern-.1667em \TeX}}} +\makeatother + +\begin{document} +\ifnum\Status=2 + % this ugliness is because the normal definition of ' for tex4ht + % tries to go into math mode. I don't under + \def'{\char`\'} +\fi + +\selectlanguage{czech} +\title{{\huge\textsf{\TL{} 2008}}\\[3mm] + Pøíruèka \protect\TeXLive{}, CS verze \cstlversion} +\date{\cstldate} + +\author{Karl Berry, editor \\[3mm] + \url{http://tug.org/texlive/}\\[3mm] +%B% \ifnum \Status=2 +%B% \includegraphics[bb=0 0 824 741]{../pictures/front} \\[5mm] +%B%\else +%B%\ifnum \Status=3 +%B% \includegraphics[width=.5\linewidth]{../pictures/bw-front2} \\[5mm] +%B%\else +%B% \includegraphics[width=.5\linewidth]{../pictures/front} \\[5mm] +%B%\fi \fi +%B% \small \textit{Kontaktní osoby pro tuto dokumentaci:}\\[3mm] +%B% \small \begin{tabular}{lcr} +%B% Czech/Slovak & Petr Sojka & \email{sojka (at) fi.muni.cz} \\ +%B% & Janka Chlebíková & \email{chlebikj (at) dcs.fmph.uniba.sk} \\ +%B% & Ján Bu¹a & \email{jan.busa (at) tuke.sk} \\ +%B% English & Karl Berry & \email{karl (at) freefriends.org} \\ +%B% French & Fabrice Popineau & \email{fabrice.popineau (at) supelec.fr} \\ +%B% German & Volker R.\,W.\ Schaa & \email{volker (at) dante.de} \\ +%B% Polish & Staszek Wawrykiewicz & \email{staw (at) gust.org.pl} \\ +%B% Russian & Boris Veytsman & \email{borisv (at) lk.net} +%B% \end{tabular} +% \tlimage{front}{bb=0 0 824 741}{.7\linewidth} + } + +% comes out too close to the toc, and we know it's page one anyway. +\thispagestyle{empty} +\maketitle + +\ifnum\Status=3 + \thispagestyle{csbul} + \ifforbulletin \setcounter{page}{113} % valid for 3-4/2003 + \else \raggedbottom + \fi +\fi + + Pøeklad + 2004--2008 J\'an Bu\v{s}a, + 2001 Janka Chleb\'\i kov\'a, + 2003--2008 Petr Sojka a + 2003 Petra Sojkov\'a + je ¹íøen pod GNU FDL licencí. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.2 + or any later version published by the Free Software Foundation; + with no Invariant Sections, no Front-Cover Texts, and no + Back-Cover Texts. + +\begin{multicols}{2} +\tableofcontents +\listoftables +\end{multicols} + +\section{Úvodem} +\label{sec:intro} + +\subsection{\TeX\ Live a kolekce \TeX{}u} + +Tento dokument popisuje základní vlastnosti distribuce \TeXLive{} 2008, +co¾ je instalace \TeX{}u a pøíbuzných programù pro \acro{GNU}/Linux a dal¹í +unixové systémy, \MacOSX{} a (32bitové) systémy Windows. + + +\TL{} mù¾ete získat sta¾ením z~internetu, nebo na \TKCS{} \DVD, +které skupiny u¾ivatelù \TeX{}u distribuují mezi svými èleny. +Obsah tohto \DVD je struènì popsán v~oddíle~\ref{sec:tl-coll.dists}. +\TL{} a \TKCS{} spolu jsou výsledkem spoleèného úsilí +skupin u¾ivatelù \TeX u. Tento dokument popisuje pøevá¾nì samotný +\TL{}. + +\TL{} obsahuje \file{.exe} soubory pro \TeX{}, \LaTeXe{}, \ConTeXt, +\MF, \MP, \BibTeX{} a mnoho dal¹ích programù vèetnì obsáhlého +seznamu maker, fontù a dokumentace spolu s~podporou +sazby v~mnoha rùzných svìtových jazycích. + +Aktuální verze pou¾itého software je v~archívu +\acro{CTAN} na \url{http://www.ctan.org/}. + +Krátký seznam hlavních zmìn v~této verzi \TL{} +najdete na konci tohoto dokumentu, v~oddílu~\ref{sec:history} +na stranì~\pageref{sec:history}. + +\subsection{Podpora operaèních systémù} +\label{sec:os.support} + +\TL{} obsahuje binárky pro èetné architektury na bázi Unixu, +vèetnì \MacOSX. Obsa¾ené zdrojové texty by mìly umo¾nit instalaci +pro platformy, pro které nejsou k~dispozici binárky. + +Co se týèe Windows: podporovány jsou jenom Windows 2000 a pozdìj¹í verze. Upustili jsme +od podpory Windows 9\textit{x}, ME a NT. V~dùsledku této zmìny si Windows +vy¾aduje mnohem ménì zvlá¹tního zacházení ve srovnání s~Unixovými +systémy. Pro Windows nejsou k~dispozici 64bitové \file{.exe} soubory, ale +32bitové binárky by mìly bì¾et na 64bitových systémech. + +Alternativní øe¹ení pro Windows a \MacOSX{} najdete +v~oddíle~\ref{sec:tl-coll.dists}. + +\subsection{Základní instalace \protect\TL{}} +\label{sec:basic} + +\TL{} mù¾ete nainstalovat buï z~\DVD{} nebo z~internetu. Samotný sí»ový +instalaèní program je malý a v¹e po¾adované stáhne z~internetu. Sí»ový +instalaèní program je vhodné pou¾ít, kdy¾ potøebujete jenom èást +z~kompletní instalace \TL. + +Instalaèní program na \DVD{} vám umo¾ní instalaci na lokálním disku, av¹ak \TL{} mù¾ete spustit pøímo z~\DVD{} +(nebo z~obrazu \DVD{}, kdy¾ to vá¹ systém podporuje). + +\noindent Toto je popsané detailnì +v~následujících sekcích, zde jen souhrn: + +\begin{itemize*} +\item Instalaèní dávka se jmenuje \filename{install-tl}\,. +Funguje v~re¾imu \GUI{} (pøedvolba pro Windows) i v~textovém re¾imu (pøedvoleném pro v¹echny ostatní systémy). +Jednotlivé re¾imy dosáhnete volbou \code{-gui} nebo \code{-no-gui}. + +\item Jednou souèástí instalace je nový program, `\TL\ Manager', nazvaný \prog{tlmgr}. + Podobnì jako instalaèní program mù¾e být pou¾it v~re¾imu \GUI{} nebo v~textovém re¾imu. + Mù¾ete ho pou¾ít k~nainstalování nebo odinstalování balíkù a na rùzné konfiguraèní èinnosti. +\end{itemize*} + +\subsection{Nápovìda} +\label{sec:help} + +\TeX{}ovská komunita je aktivní, vstøícná a vìt¹ina +seriózních otázek je obvykle zodpovìzena. Podpora je +neformální, je provádìna pøíle¾itostnými ètenáøi a dobrovolníky, +a proto je dùle¾ité, abyste odpovìï na svùj dotaz hledali nejdøíve sami, +ne¾ ho vznesete na fóru. (Pokud tou¾íte po garantované komerèní podpoøe, +mù¾ete na \TL{} zapomenout a zakoupit komerèní distribuci; viz +seznam prodejc\r u na \url{http://tug.org/interest.html#vendors}.) + +Ní¾e je uveden seznam informaèních zdrojù, pøibli¾nì v~poøadí, ve kterém +ho doporuèujeme k~pou¾ití: + +\begin{description} +\item [první kroky] Pokud jste \TeX ovský nováèek, na stránce +\url{http://tug.org/begin.html} najdete krátký úvod do systému. +\item [\TeX{} \acro{FAQ}] \TeX{} \acro{FAQ} je obrovská studnice + znalostí obsahuj\'ic\'i v¹echny druhy otázek, od tìch základních a¾ po + ty nejobskurnìj¹í. + Dokument najdete na \TL{} v~adresáøi \OnCD{texmf-doc/doc/english/FAQ-en/html/index.html} + nebo na internetu na \url{http://www.tex.ac.uk/faq}. Prosíme, zaènìte + své hledání odpovìdi zde. + +\item [\TeX{} Catalogue] Pokud hledáte konkrétní balík, + font, program ap., \TeX{} Catalogue je místo, kde zaèít. + Je to obsáhlá sbírka \TeX{}ových polo¾ek. Viz + \OnCD{http://www.ctan.org/help/Catalogue/}. + +\item [\TeX{}ov\'e odkazy na Webu] Na \url{http://tug.org/interest.html} + najdete mnoho relevantních odkazù na rùzné pøíruèky, + knihy, manuály a èlánky o v¹ech aspektech systému \TeX{}. + +\item [archívy diskusních skupin] + \sloppypar Dvì základní fóra pro hledání øe¹ení problémù jsou + newsová skupina \ctt{} a emailová diskusní + skupina \email{texhax@tug.org}. V~archívech tìchto zdrojù + najdete tisíce pøedchozích dotazù a odpovìdí èekajících na va¹e + hledání. Nahlédnìte na + \url{http://groups.google.com/groups?group=comp.text.tex}, + res\-pek\-ti\-ve na + \url{http://tug.org/mail-archives/texhax}. Dotazem do obecného + vyhledávacího stroje jako \url{http://google.com/} také nic nepokazíte + a pro specifika èe¹tiny a sloven¹tiny najdete dal¹í zdroje + odkazované na \url{http://www.cstug.cz/}. + +\item [kladení dotazù] Pokud nemù¾ete najít odpovìï na svou otázku, + mù¾ete ji polo¾it na \ctt{} pøes Google nebo + newsového klienta nebo emailem na \email{texhax@tug.org}. + Ale døíve, ne¾ tak uèiníte, \emph{prosím,} pøeètìte + si toto doporuèení, abyste maximalizovali vyhlídky na + získání u¾iteèné odpovìdi: + \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. + +\item [podpora \TL{}] Pokud chcete poslat + chybové hlá¹ení, pøipomínku nebo poznámku k~distribuci + \TL{}, její instalaci nebo dokumentaci, + diskusní skupina k~tomu urèená je \email{tex-live@tug.org}. + Pokud v¹ak je va¹e otázka specifická pro program na + \TL{} umístìný, napi¹te prosím pøímo autorovi nebo do diskusní + skupiny urèené pro tento program. Spu¹tìní programu + s~volbou \code{-{}-help} nezøídka + poskytuje adresu pro chybové hlá¹ení. +\end{description} + +\noindent +Druhou stranou mince je odpovídání na dotazy tìch, kdo kladou otázky. +\ctt{} i~list \code{texhax} jsou otevøeny pro kohokoliv. +Pøihlaste se, naslouchejte a zaènìte odpovídat tam, kde mù¾ete. + +% don't use \TL so the \uppercase in the headline works. Also so +% tex4ht ends up with the right TeX. Likewise the \protect's. +\section{Pøehled \protect\TeX\protect\ Live} +\label{sec:overview.tl} + +Tento oddíl popisuje obsah \TL{} a \TKCS{}, jej\'\i\v z~je èástí. + +%Dvì hlavní instalaèní dávky pro Unix a \MacOSX{} jsou +%\texttt{install-tl.sh} a \texttt{install-pkg.sh}. Jsou +%popsány v~oddíle~\ref{sec:unix.install} na +%stranì~\pageref{sec:unix.install}. +%V~dal¹ím oddíle popí¹eme strukturu a obsah \TL{}. + + +\subsection{Kolekce \protect\TeX{}u: \TL, pro\TeX{}t, Mac\TeX} +\label{sec:tl-coll.dists} + +\DVD{} \TKCS{} zahrnuje následující: + +\begin{description} + +\item [\TL] Úplný systém \TeX{}, který mù¾e být spou¹ten pøímo nebo nainstalován na disk. + +\item [Mac\TeX] pro \MacOSX, pøidává pøirozený \MacOSX\ instalaèní program a jiné aplikace Mac k~\TL{}. Jeho domovská stránka je +\url{http://www.tug.org/mactex/}. + +\item [pro\TeX{}t] Roz¹íøení systému \MIKTEX\ pro Windows. +\ProTeXt\ pøidává k~\MIKTEX u nové doplòkové nástroje +a zjednodu¹uje instalaci. Je plnì nezávislý na \TL{} +a má své vlastní pøíkazy. +Domovská stránka projektu \ProTeXt\ je na \url{http://tug.org/protext}. + +\item [CTAN] Výpis obrazovky skladi¹tì \CTAN{}. + +\item [\texttt{texmf-extra}] Adresáø s~rozmanitými doplòkovými balíky. + +%\item [demo] systém spustitelný pøímo z~\CD. Aby to bylo mo¾né, +%byli jsme nuceni vypustit velké kolekce pro sazbu +%èín¹tiny, japon¹tiny a korej¹tiny \acro{CJK}, +%podporu sazby not, nìkterá ménì èasto pou¾ívaná písma. +%Distribuce funguje jen pod Linuxem, \MacOSX{} a systémy Windows. + +\end{description} + + +\CTAN{}, \pkgname{protext} a \dirname{texmf-extra} nemusí mít stejné podmínky +pro kopírování jako \TL{}, proto buïte pozorní pøi ¹íøení nebo modifikaci. + +\subsection{Popis koøenových adresáøù \TL{}} +\label{sec:tld} + +V~koøenovém adresáøi distribuce \TL{} najdete následující +podadresáøe. Na \pkgname{live} \DVD\ je celá \TL{} hierarchie v~podaresáøi +\dirname{texlive}, a ne v~koøenovém adresáøi disku. + +\begin{ttdescription} +\item[bin] Binárky systému \TeX{}, s~podadresáøi dle platforem. +% +\item[readme.html] Webovské stránky se struènými úvody a u¾iteènými +odkazy, v~rùzných jazycích. +% +\item[source] Zdrojové kódy v¹ech programù, vèetnì distribuce + \Webc{} \TeX{}u a \MF{}u. +% +\item[support] Rùzné pomocné balíky a programy. Automaticky %Implicitnì + \emph{nejsou} instalovány. Toto zahrnuje editory + a \TeX{}ová vývojová prostøedí rùzných druhù. + +% +\item[texmf] Viz \dirname{TEXMFMAIN} ní¾e. +% +\item[texmf-dist] Viz \dirname{TEXMFDIST} ní¾e. +% +\item[texmf-doc] Strom samostatné èisté dokumentace, uspoøádán podle jazykù. +% +\item[tlpkg] Skripty, programy a údaje pro správu instalace. Obsahuje +rovnì¾ neveøejné kopie Perlu a Ghostscriptu pro Windows, které jsou mimo +\TL{} neviditelné, a nový prohlí¾eè PostScriptu pro Windows PSView. +\end{ttdescription} + +\smallskip + +V~koøenovém adresáøi distribuce jsou navíc instalaèní dávky a soubory +\filename{README} (v~rùzných jazycích). + +Adresáø \dirname{texmf-doc} obsahuje dokumentaci, která není +souèástí nìjakého konkrétního balíku nebo programu. +Dokumentace programù (manuály, +man-stránky, info-soubory) jsou v~\dirname{texmf/doc}, +proto¾e programy jsou v~adresáøi \dirname{texmf}. +Dokumentace \TeX ových balíkù a formátù je +v~\dirname{texmf-dist/doc}. +K~vyhledání ve¹keré dokumentace na libovolném místì mù¾ete +pou¾ít programy \cmdname{texdoc} nebo \cmdname{texdoctk}. +Souhrnn\'e odkazy v~koøenovém souboru \OnCD{doc.html} mohou +být také u¾iteèné. + +Samotná tato pøíruèka \TL\ je v~adresáøi \dirname{texmf-doc} +a je k~dispozici v~nìkolika jazycích: + +\begin{itemize*} +\item{zjednodu¹ená èín¹tina:} \OnCD{texmf-doc/doc/chinese/texlive-zh-cn} +\item{èesko-slovenská:} \OnCD{texmf-doc/doc/czechslovak/texlive-cz} +\item{anglická:} \OnCD{texmf-doc/doc/english/texlive-en} +\item{francouzská:} \OnCD{texmf-doc/doc/french/texlive-fr} +\item{nìmecká:} \OnCD{texmf-doc/doc/german/texlive-de} +\item{polská:} \OnCD{texmf-doc/doc/polish/texlive-pl} +\item{ruská:} \OnCD{texmf-doc/doc/russian/texlive-ru} +\end{itemize*} + + +\subsection{Pøehled pøeddefinovaných stromù texmf} +\label{sec:texmftrees} + +Tento oddíl uvádí seznam v¹ech pøeddefinovaných promìnných +urèujících stromy texmf, pou¾ívaných systémem, a jejich zamý¹lený úèel, a standardní uspoøádání systému \TL. +Povel \texttt{texconfig +conf} vám uká¾e hodnoty tìchto promìnných, tedy mù¾ete jednodu¹e zjistit, +jak tyto odpovídají názvùm adresáøù ve va¹í instalaci. + +\begin{ttdescription} +\item [TEXMFMAIN] Strom obsahující ¾ivotnì dùle¾ité èásti systému, jako pomocné skripty +(napø. \verb+web2c/mktexdir+) a jiné podpùrné soubory a jejich dokumentaci. +Neobsahuje \TeX ovské formáty a balíky. +\item [TEXMFDIST] Strom obsahující hlavní sadu balíkù maker, + font\r u, atd. z~pùvodní distribuce. +\item [TEXMFLOCAL] Strom, který mohou pou¾ít administrátoøi na instalaci +doplòkových nebo upravených maker, fontù, atd., pro celý systém. +\item [TEXMFHOME] Strom, který mohou pou¾ít u¾ivatelé na svoje osobní instalace +doplòkových nebo upravených maker, fontù, atd. + Roz¹íøení této promìnné se dynamicky nastaví pro ka¾dého u¾ivatele na jeho vlastní osobní adresáø. +\item [TEXMFCONFIG] +Strom pou¾ívan\'y nástroji + \verb+texconfig+, \verb+updmap+ a \verb+fmtutil+ na ulo¾ení + modifikovaných konfiguraèních údajù. Implicitnì pod \envname{TEXMFHOME}. %$ +\item [TEXMFSYSCONFIG] Strom pou¾ívan\'y nástroji \verb+texconfig-sys+, \verb+updmap-sys+ a \verb+fmtutil-sys+ na ulo¾ení modifikovaných konfiguraèních údajù. +\item [TEXMFVAR] Strom pou¾ívan\'y programy \verb+texconfig+, + \verb+updmap+ a \verb+fmtutil+ na (cache) ulo¾ení runtime + údajù jako jsou soubory formátù a generované map-soubory. + Implicitnì pod \envname{TEXMFHOME}. %$ +\item [TEXMFSYSVAR] Strom pou¾ívan\'y programy \verb+texconfig-sys+, + \verb+updmap-sys+, \verb+fmtutil-sys+ a také \verb+tlmgr+, na (cache) ulo¾ení runtime + údajù jako jsou soubory formátù a generované map-soubory. +\end{ttdescription} + + +\noindent +Standardní struktura je: +\begin{description} + \item[system-wide root] mù¾e obsáhnout vícenásobné vydání \TL{}: + \begin{ttdescription} + \item[2007] Pøedchozí vydání. + \begin{ttdescription} + \item [...] + \end{ttdescription} + \item[2008] Nynìj¹í vydání. + \begin{ttdescription} + \item [bin] ~ + \begin{ttdescription} + \item [i386-linux] binárky systému \GNU/Linux + \item [...] + \item [universal-darwin] binárky systému \MacOSX + \item [win32] binárky systému Windows + \end{ttdescription} + \item [texmf] Toto je \envname{TEXMFMAIN}. + \item [texmf-dist] \envname{TEXMFDIST} + \item [texmf-doc] \envname{TEXMFDOC} + \item [texmf-var] \envname{TEXMFSYSVAR} + \item [texmf-config] \envname{TEXMFSYSCONFIG} + \end{ttdescription} + \item [texmf-local] \envname{TEXMFLOCAL}, zamý¹lený být zachován od vydání k~vydání. + \end{ttdescription} + \item[domovský adresáø u¾ivatele] (\texttt{\$HOME} nebo + \texttt{\%USERPROFILE\%}) + \begin{ttdescription} + \item[.texlive2007] Soukromì generované a konfiguraèní údaje pøedchozího vydání. + \item[.texlive2008] Soukromì generované a konfiguraèní údaje aktuálního vydání. + \begin{ttdescription} + \item [texmf-var] \envname{TEXMFVAR} + \item [texmf-config] \envname{TEXMFCONFIG} + \end{ttdescription} + \item[texmf] \envname{TEXMFHOME} Osobní makra + \textit{atd.} + \end{ttdescription} +\end{description} + + +\subsection{Roz¹íøení \protect\TeX{}u} +\label{sec:tex.extensions} + +Samotný \TeX{} je zmrazený, kromì ojedinìlých oprav chyb. Stále je v~\TL\ pøítomen jako program \prog{tex} a tak to zùstane v~dohledné budoucnosti. \TL{} obsahuje nìkolik roz¹íøených verzí \TeX{}u: + +\begin{description} + +\item [\eTeX] pøidává mno¾inu nových +pøíkazù (nazývaných \TeX{}ové primitivy). +\label{text:etex} +Nové pøíkazy se napøíklad týkají makroexpanze, naèítání znakù, +tøíd znaèek (marks), roz¹íøených ladicích mo¾ností +a roz¹íøení \TeXXeT{} pro obousmìrnou sazbu. Implicitnì +je \eTeX{} 100\% kompatibilní se standardním \TeX{}em. +Viz~\OnCD{texmf-dist/doc/etex/base/etex_man.pdf}. +%B% \eTeX{} je nyní sázecím programem pro \LaTeX{} i pdf\LaTeX{}. + +\item [pdf\TeX] vybudován na roz¹íøeních \eTeX{}u pøidává podporu +zápisu ve formátu \acro{PDF} stejnì jako v~\dvi{}. + +%% This is the program +%% invoked for most formats, e.g., \prog{etex}, \prog{latex}, +%% \prog{pdflatex}. +%% See \url{http://www.pdftex.org/}. +%% \OnCD{texmf/doc/pdftex/manual/} for the manual, and +%% \OnCD{texmf/doc/pdftex/manual/samplepdf/samplepdf.tex} for example usage +%% of some of its features. + +Toto je program pou¾ívaný pro vìt¹inu formátù, napøíklad, \prog{etex}, \prog{latex}, +\prog{pdflatex}. Viz \url{http://www.pdftex.org/}, +návod v~adresáøi \OnCD{texmf/doc/pdftex/manual/} a pøíklady pou¾ití nìkterých jeho vlastností v~adresáøi +\OnCD{texmf/doc/pdftex/manual/samplepdf/samplepdf.tex}. + +\item [Lua\TeX] je oznaèován za nástupce pdf\TeX/{}u, se kterým by mìl být zpìtnì kompatibilní. Mìl by také nahradit Aleph, viz dále. Zabudovaný interpret Lua (viz +\url{http://www.lua.org/}) umo¾òuje elegantn9 øe¹ení mnoha o¾ehavých +\TeX ovských problémù. Volaný povelem \filename{texlua}, funguje jako samostatný interpret Lua, a jako taký je ji¾ pou¾it v~rámci \TL. Viz \url{http://www.luatex.org/} a +\OnCD{texmf-dist/doc/luatex/luatexref-t.pdf}. + +\item [\XeTeX] pøidává podporu vstupního kódování +Unicode a OpenType- a systémových fontù, implementovaných pou¾itím zejména knihoven tøetích stran. +Viz \OnCD{texmf-dist/doc/xetex/XeTeX-reference.pdf}. + +\item [\OMEGA\ (Omega)] je zalo¾ena na Unicode. Umo¾òuje sázet v~témìø v¹ech +svìtových jazycích zároveò. Dociluje toho tzv. +pøekladovými procesy (\OMEGA{} Translation Processes, +\acro{OTP}) pro realizaci slo¾itých transformací na jakémkoliv vstupu. Viz +\OnCD{texmf/doc-dist/omega/base/doc-1.8.tex} +(dokumentace v¹ak není zcela aktuální). + +\item [Aleph] kombinuje roz¹íøení \OMEGA\ a \eTeX. +Pro minimální dokumentaci viz \OnCD{texmf-dist/doc/aleph/base}. +\end{description} + + +\subsection{Dal¹í za zmínku stojící programy na \protect\TeXLive} + +Na \TL{} najdete nìkolik èasto pou¾ívaných programù: + +\begin{cmddescription} + +\item [bibtex] podpora práce se seznamem literatury. + +\item [makeindex] vytváøení rejstøíku. Pro èe¹tinu a sloven¹tinu +v¹ak potøebujete verzi programu s~názvem \texttt{csindex} (není zatím +souèástí distribuce, je potøeba instalovat zvlá¹»). + +\item [dvips] pro konverzi \dvi{} do \PS{}. + +\item [xdvi] prohlí¾eè \dvi{} pro systém X~Window. + +\item [dvilj] \dvi{} ovladaè tiskáren HP Laser\-Jet. + +\item [dv2dt, dt2dv] pro konverzi \dvi{} do/z~ascii textu. + +\item [dviconcat, dviselect] pro kopii a vkládání stránek +do/z \dvi{} souborù. + +\item [dvipdfmx] konvertor \dvi{} do \acro{PDF}, alternativní +pøístup vedle pdf\TeX{}u zmínìného vý¹e. Srovnej balíky +\pkgname{ps4pdf} a \pkgname{pdftricks} pro dal¹í +alternativy. + +\item [psselect, psnup, \ldots] programy pro práci s~\PS{}em. + +\item [lacheck] pro kontrolu syntaxe \LaTeX{}u. + +\item [texexec, texmfstart] wrapper pro Con\TeX{}t a práci s~\acro{PDF}. + +\item [tex4ht] konvertor \TeX{}u do \acro{HTML}. + +\end{cmddescription} + + +\subsection{Fonty v~\protect\TL} +\label{sec:tl.fonts} + +\TL{} pøiná¹í mno¾ství vysoce kvalitních vektorových % ?scalable fonts. +fontù. Viz \url{http://tug.org/fonts} a \OnCD{texmf-doc/english/free-math-fonts-survey}. + + +\section{Instalace} +\label{sec:install} + +\subsection{Spu¹tìní instalaèního programu} +\label{sec:inst.start} + +Pro zaèátek si obstarejte \TK{} \DVD{} nebo si stáhnìte sí»ový instalaèní program \TL{}, +a najdìte instalaèní skript: \filename{install-tl} pro Unix, +\filename{install-tl.bat} pro Windows. + +\begin{description} +\item [Sí»ový instalátor:] stáhnìte z~\CTAN{}u, z~adresáøe \dirname{systems/texlive/tlnet}; url +\url{http://mirror.ctan.org/systems/texlive/tlnet} vás automaticky pøesmìruje na blízký, aktuální mirror. +Mù¾ete získat \filename{install-tl.zip}, který mù¾e být pou¾it pod Unixem a Windows nebo +\filename{install-unx.tar.gz}, který je podstatnì men¹í, jenom pro Unix. Po rozbalení se \filename{install-tl} a +\filename{install-tl.bat} objeví v~podadresáøi \dirname{install-tl}. + +\item [\DVD{} \TeX{} kolekce:] vejdìte do podadresáøe \dirname{texlive}. +Pod Windows by se instalátor mìl spustit automaticky po vlo¾ení \DVD. \DVD\ mù¾ete získat, kdy¾ se stanete èlenem +skupiny u¾ivatelù \TeX u (vøele doporuèujeme, +\url{http://tug.org/usergroups.html}), nebo si ho zvlá¹» zakoupíte +(\url{http://tug.org/store}), anebo si vypálíte svoje vlastní z~\ISO\ +obrazu (\url{http://tug.org/texlive/acquire.html}). + +\end{description} +Následující sekce vysvìtlují v¹echno podrobnìji. + +\subsubsection{Unix} + +\begin{figure}[tb] +\begin{boxedverbatim} +======================> TeX Live installation procedure <===================== + +=======> Note: Letters/digits in indicate menu items <======= +=======> for commands or configurable options <======= + + + Detected platform: Intel x86 with GNU/Linux + + binary systems: 1 out of 16 + + Installation scheme (scheme-full) + + Customizing installation scheme: + standard collections + language collections + 83 collections out of 84, disk space required: 1666 MB + + directories: + TEXDIR (the main TeX directory): + !! default location: /usr/local/texlive/2008 + !! is not writable, please select a different one! + TEXMFLOCAL (directory for site-wide local files): + /usr/local/texlive/texmf-local + TEXMFSYSVAR (directory for variable and automatically generated data): + /usr/local/texlive/2008/texmf-var + TEXMFSYSCONFIG (directory for local config): + /usr/local/texlive/2008/texmf-config + TEXMFHOME (directory for user-specific files): + ~/texmf + + options: + [ ] use letter size instead of A4 by default + [X] create all format files + [X] install macro/font doc tree + [X] install macro/font source tree + [ ] create symlinks in standard directories + + Install for running from DVD + +Other actions: + start installation to HD + help + quit + +Enter command: +\end{boxedverbatim} +\caption{Hlavní obrazovka textového instalaèního programu (\GNU/Linux)}\label{fig:text.main} +\end{figure} + +\begin{figure}[tb] +\tlpng{install-w32-main}{\linewidth} +\caption{Základní obrazovka \GUI{} instalaèního programu (Windows)}\label{fig:gui.main} +\end{figure} + +\noindent +Dále, \texttt{>} oznaèuje výzvu (prompt shellu); vstup u¾ivatele vstup je \Ucom{\texttt{zvýraznìn}}. +Po spu¹tìní terminálu v~Unixovském systému je nejjednodu¹¹í zpùsob: +\begin{alltt} +> \Ucom{cd /path/to/installer} +> \Ucom{perl install-tl} +\end{alltt} +(Nebo mù¾ete vyvolat \Ucom{perl /path/to/installer/install-tl}, nebo +\Ucom{./install-tl} kdy¾ je spustitelný, atd.; nechceme opakovat v¹echny tyto variace.) + +K~instalaci v~re¾imu \GUI\ (budete potøebovat modul \dirname{Perl/TK}), pou¾ijte: +\begin{alltt} +> \Ucom{perl install-tl -gui} +\end{alltt} + +Úplný seznam rùzných voleb získáte povelem: +\begin{alltt} +> \Ucom{perl install-tl -help} +\end{alltt} + +\textbf{Varování o oprávnìních Unixu:} Va¹e nastavení \code{umask} v~èase instalace bude respektováno instalaèním programem \TL{}. Proto, kdy¾ chcete, aby byla va¹e instalace pou¾itelná i jinými u¾ivateli ne¾ vámi, ujistìte se, ¾e jsou va¹e nastavení dostateènì tolerantní, napøíklad, \code{umask +002}. Dal¹í informace o nastavení \code{umask}, hledejte v~dokumentaci k~va¹emu systému. + +\subsubsection{Mac\,OS\,X} + +Jak ji¾ bylo zmínìno v~sekci~\ref{sec:tl-coll.dists}, pro \MacOSX je pøipravena samostatná distribuce, nazvaná Mac\TeX\ (\url{http://tug.org/mactex}). +Doporuèujeme pou¾ít pùvodní instalaèní program Mac\TeX\ u namísto instalátoru \TL\ +pod \MacOSX, proto¾e pùvodní (nativní) instalátor mù¾e provést nìkolik nastavení specifických pro Mac, zejména umo¾òuje snadné pøepínání mezi rùznými distribucemi \TeX u pro \MacOSX\ (Mac\TeX, gw\TeX, +Fink, MacPorts, \ldots). + +Mac\TeX\ je silnì zalo¾en na \TL, a hlavní \TeX ovská stromová struktura je pøesnì stejná. Pøidává nìkolik dal¹ích adresáøù s~dokumentací a aplikacemi specifickými pro Mac. + +\subsubsection{Windows} + +Jestli¾e pou¾íváte sí»ový instalátor, nebo instalaèní program \DVD\ se nespustí automaticky, kliknìte dvakrát na soubor \filename{install-tl.bat}. + +Mù¾ete také spustit instalaèní program z~pøíkazového øádku. Dále \texttt{>} oznaèuje prompt shellu; vstup u¾ivatele je \Ucom{\texttt{polotuèný}}. Pokus jste v~adresáøi instalaèního programu, jenom spus»te: +\begin{alltt} +> \Ucom{install-tl} +\end{alltt} + +Mù¾ete to také vyvolat zadáním absolutní polohy, jako napøíklad: +\begin{alltt} +> \Ucom{D:\bs{}texlive\bs{}install-tl} +\end{alltt} +pro \TKCS\ \DVD, za pøedpokladu, ¾e \dirname{D:} je optický disk. + +Pro instalaci v~textovém re¾imu pou¾ijte: +\begin{alltt} +> \Ucom{install-tl -no-gui} +\end{alltt} + +Pro úplný seznam rùzných voleb zadejte: +\begin{alltt} +> \Ucom{install-tl -help} +\end{alltt} + +\subsubsection{Textový instalaèní program} + +Obrázek~\ref{fig:text.main} ukazuje základní obrazovku textového re¾imu pod Unixem. + +Je to instalátor jenom s~pøíkazovým øádkem; vùbec nemá kurzorovou podporu. Napøíklad, nemù¾ete se pohybovat v~zatrhávacích rámeècích nebo vstupních polích. Jenom napí¹ete nìco (s~rozli¹ováním velikosti písma) na pøíkazovém øádku a stlaèíte klávesu Enter, poté se celá obrazovka pøepí¹e s~pøizpùsobeným obsahem. + +Rozhraní textového instalátoru je tak primitivní z~prostého dùvodu: je +navr¾ené tak, aby se dalo spustit na tolika platformách jak je to jen +mo¾né, dokonce i~v~Perlu (pro Windows je zaøazena +podmo¾ina Perlu). + +\subsubsection{Grafický instalaèní program} + +Obrázek~\ref{fig:gui.main} ukazuje grafický instalátor pod Windows. +Vìt¹ina rozdílù pøípustných voleb je patrná z~obrazovky systému Windows a z~pøedchozí obrazovky systému \GNU/Linux. + +\subsection{Spu¹tìní instalaèního programu} +\label{sec:runinstall} + +Instalátor je zamý¹lený jako co nejvíce samovysvìtlující. Nicménì podáme nìkolik poznámek o jednotlivých volbách a dílèích nabídkách: + +\subsubsection{Nabídka binárních systémù (pouze Unix)} +\label{sec:binary} + +\begin{figure}[tbh] +\begin{boxedverbatim} +Available sets of binaries: +=============================================================================== + + a [ ] alpha-linux DEC Alpha with GNU/Linux + b [ ] amd64-freebsd x86_64 with FreeBSD + c [ ] hppa-hpux HP-UX + d [ ] i386-freebsd Intel x86 with FreeBSD + e [X] i386-linux Intel x86 with GNU/Linux + f [ ] i386-openbsd Intel x86 with OpenBSD + g [ ] i386-solaris Intel x86 with Sun Solaris + h [ ] mips-irix SGI IRIX + i [ ] powerpc-aix PowerPC with AIX + j [ ] powerpc-linux PowerPC with GNU/Linux + k~[ ] sparc-linux Sparc with GNU/Linux + l [ ] sparc-solaris Sparc with Solaris + m [ ] universal-darwin universal binaries for MacOSX/Darwin + o [ ] win32 Windows + p [ ] x86_64-linux x86_64 with GNU/Linux +\end{boxedverbatim} +\caption{Nabídka binárek}\label{fig:bin.text} +\end{figure} + +Obrázek~\ref{fig:bin.text} ukazuje nabídku binárek textového re¾imu. Standardnì budou nainstalovány jenom binárky va¹í aktuální platformy. Z~této nabídky si rovnì¾ mù¾ete vybrat binárky pro jinou architekturu. Toto mù¾e být u¾iteèné, pokud sdílíte \TeX ovský strom v~síti heterogenních strojù, nebo na systému s~dvojitým zavádìcím procesem. + +\subsubsection{Volba obsahu instalace} +\label{sec:components} + +\begin{figure}[tbh] +\begin{boxedverbatim} +Select a scheme: +==================================================================== + + a [ ] TeX Live basic scheme + b [ ] TeX Live scheme for ConTeXt + c [X] TeX Live full scheme + d [ ] GUST TeX Live scheme + e [ ] GUTenberg TeX Live scheme + f [ ] TeX Live medium scheme + g [ ] TeX Live minimal scheme + h [ ] TeX Live for Omega users + i [ ] teTeX scheme + j [ ] XML typesetting scheme +\end{boxedverbatim} +\caption{Nabídka schémat}\label{fig:scheme.text} +\end{figure} + +Obrázek~\ref{fig:scheme.text} ukazuje nabídku schémat \TL; tady +vybíráte ``schéma'', co¾ je souhrn kolekcí balíkù. +Pøedvolené schéma \optname{full} nainstaluje v¹e, co je k~dispozici, av¹ak +mù¾ete také zvolit schéma \optname{basic} pro malý systém, +\optname{minimal} pro úèely testování, a schéma \optname{medium} nebo +\optname{teTeX} pro získání nìèeho mezi tím. K~dispozici jsou také rùzná +specializovaná schémata a schémata specifická pro nìkteré zemì. + +\begin{figure}[tbh] +\tlpng{stdcoll}{.7\linewidth} +\caption{Nabídka kolekcí (Linux)}\label{fig:collections.gui} +\end{figure} + +Svùj výbìr schématu mù¾ete upøesnit pomocí nabídek `standard collections' a +`language collections' (obrázek~\ref{fig:collections.gui}, ukázané pro zmìnu v~re¾imu \GUI). + +Kolekce jsou o jednu úroveò podrobnìj¹í ne¾ schémata\Dash v~podstatì, +schéma je tvoøeno nìkolika kolekcemi, kolekci tvoøí jeden nebo více +balíkù, a balík (nejni¾¹í úroveò seskupvání v~\TL) obsahuje vlastní +soubory \TeX ovských maker, soubory fontù, atd. + +Pokud chcete získat vìt¹í kontrolu ne¾ jakou poskytuje nabídka kolekcí, po instalaci mù¾ete pou¾ít program \prog{tlmgr} (viz sekci~\ref{sec:tlmgr}); jeho pou¾itím mù¾ete øídit instalaci na úrovni balíkù. + +\subsubsection{Adresáøe} +\label{sec:directories} + +Standardní uspoøádání je popsáno v~sekci~\ref{sec:texmftrees}, +\p.\pageref{sec:texmftrees}. Standardní umístìní adresáøe \dirname{TEXDIR} se li¹í pro Windows +(|%PROGRAMFILES%\texlive\2008|) a Unix +(\dirname{/usr/local/texlive/2008}). + +Hlavní dùvod pro zmìnu této pøedvolby je nedostatek práv +na zápis pro standardní umístìní. +Nemusíte být zrovna rootem nebo administrátorem, kdy¾ instalujete \TL, ale potøebujete oprávnìní na zápis do cílového adresáøe. + +Logickou alternativou je adresáø uvnitø va¹eho domovského adresáøe, zvlá¹» kdy¾ chcete být výhradním u¾ivatelem. Na naznaèení tohoto pou¾ijte `|~|', jako napøíklad `|~/texlive/2008|'. + +Doporuèujeme do názvu zaèlenit rok, co umo¾ní zachování rùzných vydání \TL{} vedle sebe. (Mù¾ete chtít vytvoøit název nezávislý na verzi, napøíklad \dirname{/usr/local/texlive-cur} pomocí symbolického odkazu, který mù¾e být pozdìji pøepsán po pøezkou¹ení nového vydání.) + +Zmìna \dirname{TEXDIR} v~instalaèním programu vyvolá také zmìny +\dirname{TEXMFLOCAL}, \dirname{TEXMFSYSVAR} a +\dirname{TEXMFSYSCONFIG}. + +\dirname{TEXMFHOME} je doporuèené umístìní osobních souborù maker nebo balíkù. Pøedvolená hodnota je |~/texmf|. Na rozdíl od \dirname{TEXDIR}, je nyní |~| uchována v~novì vytvoøených konfiguraèních souborech, proto¾e to u¾iteènì odkazuje na domovský adresáø bì¾ícího \TeX u. Expanduje se na \dirname{$HOME} pod Unixem a \verb|%USERPROFILE%| pod Windows. + +\subsubsection{Volby} +\label{sec:options} + +\begin{figure}[tbh] +\begin{boxedverbatim} +

use letter size instead of A4 by default: [ ] + create all format files: [X] + install font/macro doc tree: [X] + install font/macro source tree: [X] + create symlinks in standard directories: [ ] + binaries to: + manpages to: + info to: +\end{boxedverbatim} +\caption{Nabídka voleb (Unix)}\label{fig:options.text} +\end{figure} + +Obrázek~\ref{fig:options.text} ukazuje nabídku voleb textového re¾imu. +Zde musíme pøipomenout tøi volby: + +\begin{description} +\item[use letter size instead of A4 by default:] Obvyklý výbìr standardní velikosti papíru. +Jednotlivé dokumenty mohou deklarovat zvlá¹tní rozmìr papíru, pokud je to ¾ádoucí. + +\item[create all format files:] Pøesto¾e si vytvoøení nepotøebných formátù +vy¾aduje èas a diskový prostor pro ulo¾ení, nicménì doporuèujeme nechat +tuto volbu vyznaèenou: kdy¾ ji nevyznaèíte, budou formátové soubory +vytvoøené v~osobních stromech \dirname{TEXMFVAR} u¾ivatelù, kdy¾ budou +zapotøebí. Na tomto místì nebudou automaticky aktualizované, kdy¾ se budou +napøíklad obnovovat binárky nebo vzory dìlení v~instalaci, co mù¾e +skonèit nekompatibilními soubory formátù. + +\item[create symlinks in standard directories] (pouze Unix): +Tato volba obchází potøebu zmìny promìnných prostøedí. Bez této volby je potøebné pøidat adresáøe \TL{} do promìnnných + \envname{PATH}, \envname{MANPATH} a \envname{INFOPATH}. Budete muset pøidìlit práva na zápis cílovým adresáøùm. Není rozumné pøepsat \TeX ovský systém, který pøi¹el s~va¹ím systémem s~touto volbou. Toto je v~první øadì urèeno k~vytváøení odkazù v~standarndích adresáøích, které u¾ivatelé znají, jako napøíklad \dirname{/usr/local/bin}, které neobsahují ¾ádné \TeX ovské soubory. +\end{description} + +Teï, kdy¾ jsou v¹echna tyto nastavení podle va¹eho vkusu, mù¾ete napsat +`I' a spustit instalaèní proces. Po dokonèení pøeskoète na +sekci~\ref{sec:postinstall}, kde se dozvíte, co se má udìlat, pokud vùbec +nìco. + + +\subsubsection{Nastavení spou¹tìní z~DVD{} (pouze v~textovém re¾imu)} +\label{sec:fromdvd} + +K~výbìru této volby napi¹te `|V|'. Toto zmìní hlavní nabídku na nìco podobného jako ukazuje obrázek~\ref{fig:main.fromdvd}. +\begin{figure}[tbh] +\begin{boxedverbatim} +======================> TeX Live installation procedure <===================== + +=======> Note: Letters/digits in indicate menu items <======= +=======> for commands or configurable options <======= + + directories: + TEXDIRW (Writable root): + !! default location: /usr/local/texlive/2008 + !! is not writable, please select a different one! + TEXMFLOCAL (directory for site-wide local files): + /usr/local/texlive/texmf-local + TEXMFSYSVAR (directory for variable and automatically generated data): + /usr/local/texlive/2008/texmf-var + TEXMFSYSCONFIG (directory for local config): + /usr/local/texlive/2008/texmf-config + TEXMFHOME (directory for user-specific files): + ~/texmf + + options: + [ ] use letter size instead of A4 by default + [X] create all format files + + set up for installing to hard disk + +Other actions: + start installation for running from DVD + help + quit +\end{boxedverbatim} +\caption{Hlavní nabídka s~uspoøádáním pro volbu \optname{from DVD}}\label{fig:main.fromdvd} +\end{figure} + +V¹imnìte si zmìny: v¹echny volby k~instalaci zmizely, a èást pro adresáøe se teï zmiòuje +o~\dirname{TEXDIRW} nebo zapisovatelném koøenu. Volba pro symbolické linky také zmizela. + +Instalaèní program bude poøád vytváøet rùzné adresáøe a konfiguraèní +soubory, ale nezkopíruje \dirname{texmf}, +\dirname{texmf-dist} nebo \dirname{texmf-doc} na pevný disk. + +Poinstalaèní konfigurace pro Unix bude o nìco slo¾itej¹í, +proto¾e teï se struktura adresáøù odchyluje od standardu; viz +sekci~\ref{sec:postinstall}. + +V~dùsledku èasových ohranièení není tato volba zapracována do instalaèního programu \GUI{}, ale je k~dispozici pro oba systémy Unix a Windows. U¾ivatelé pod systémem Windows musí spustit instalátor z~pøíkazového øádku, viz sekci~\ref{sec:cmdline}. + +Oddíl \ref{sec:portable.unix} popisuje schùdnìj¹í cestu spu¹tìní \TL, která nedìlá nebo nepo¾aduje zmìny systémové konfigurace, ale ani ¾ádnou konfiguraci neumo¾òuje. + +\subsection{Instalaèní volby pøíkazového øádku} +\label{sec:cmdline} + +K~zobrazení voleb pøíkazového øádku napi¹te +\begin{alltt} +> \Ucom{install-tl -help} +\end{alltt} +K~uvedení názvu volby mohou být pou¾ity |-| nebo také |--|. +Následují nejzajímavìj¹í volby: + +\begin{ttdescription} +\item[-gui] Podle mo¾ností pou¾ijte \GUI{} instalátor. Toto si vy¾aduje modul + Perl/Tk (\url{http://tug.org/texlive/distro.html#perltk}); + pokud Perl/Tk není k~dispozici, pokraèuje instalace v~textovém re¾imu. +\item[-no-gui] Vynutí si pou¾ití instalátoru v~textovém re¾imu, dokonce i pod Windows; + mù¾ete to potøebovat, pokud chcete spustit instalaci s~volbou `from \DVD', ponìvad¾ tato + není k~dispozici v~re¾imu \GUI{}. +\item[-lang {\sl LL}] Specifikuje jazyk instalaèního rozhraní jako jeho standarní dvoupísmenový kód \textsl{LL}. +V~souèasné dobì jsou podporovány jazyky: angliètina (\texttt{en}, pøedvolený), nìmèina + (\texttt{de}), francouz¹tina (\texttt{fr}), nizozem¹tina (\texttt{nl}), pol¹tina + (\texttt{pl}), slovin¹tina (\texttt{sl}) a vietnam¹tina + (\texttt{vi}). Instalaèní program se sám pokusí urèit vhodný jazyk, ale kdy¾ sel¾e nebo kdy¾ není správný jazyk k~dispozici, pak pou¾ije angliètinu jako nouzové øe¹ení. +\item[-profile {\sl profile}] Instalaèní program v¾dycky ulo¾í soubor + \filename{texlive.profile} do \dirname{2008/tlpkg}- nebo do podadresáøe + \dirname{tlpkg} va¹í instalace. Tato volba zpùsobí, ¾e se pou¾ije + soubor \filename{texlive.profile}. + Tady je výpis: + \begin{fverbatim} +# texlive.profile written on Wed Jul 9 16:13:44 2008 UTC +# It will NOT be updated and reflects only the +# installation profile at installation time. +selected_scheme scheme-basic +TEXDIR /usr/local/texlive/2008 +TEXDIRW /usr/local/texlive/2008 +... +TEXMFSYSVAR /usr/local/texlive/2008/texmf-var +collection-basic 1 +... +option_symlinks 0 + \end{fverbatim} + Takto mù¾ete pou¾itím této volby v~dávkovém re¾imu instalovat \TeX\ na + dal¹í systémy, se stejnými volbami, jaké jste uèinili v~pùvodní instalaci. +\item [-location {\sl url/path}] Specifikuje nestandardní zdroj pro balíky; viz dále. +\end{ttdescription} + +\subsubsection{Promìnná \optname{location}} +\label{sec:location} + +Hondota promìnné \optname{location} mù¾e být adresa url s~\texttt{ftp:}, +\texttt{http:} na zaèátku, nebo \texttt{file:/} url, nebo jednoduchá cesta. +Pokud se daný argument nachází na lokální mechanice (jako cesta nebo \texttt{file:/} url), +automaticky je urèen typ instalace (komprimovaná nebo live): +pokud bude nalezen podadresáø \dirname{archive} obsahující soubory \filename{.tar.lzma}, +tak bude pou¾it, dokonce i kdy¾ budou k~dispozici také nekomprimované soubory. + +Kdy¾ je zadáno \texttt{http:} nebo \texttt{ftp:} umístìní, koncové znaky `\texttt{/}' a/nebo koncová slo¾ka `\texttt{/tlpkg}' jsou ignorovány. Napøíklad, mù¾ete si zvolit urèité zrcadlo \CTAN u nìèím jako: +\url{http://ctan.example.org/tex-archive/texlive/tlnet/2008}, +pochopitelnì s~nahrazením vhodného jména hostitele (hostname) a jeho konkrétní koøenovou cestou +\CTAN u (seznam zrcadel \CTAN u je udr¾ován na \url{http://ctan.org/mirrors}) +namísto |ctan.example.org/tex-archive|. Implicitní je automatický výbìr zrcadla, pou¾itím +\url{http://mirror.ctan.org}; v~ka¾dém pøípadì je zvolený hostitel pou¾it pro ve¹kerý download. + + +\subsection{Poinstalaèní èinnosti} +\label{sec:postinstall} + +Po instalaci se mohou hodit nìkteré dal¹í úpravy. + +\subsubsection{Windows} + +Av¹ak pod Windows se instalaèní program o~v¹e postará. + +\subsubsection{Pokud byly vytvoøeny symbolické odkazy} + +Pokud jste zvolili vytvoøení symbolických odkazù v~standardních adresáøích (zmínìných v~sekci~\ref{sec:options}), pak není potøeba editovat promìnné prostøedí. + + +\subsubsection{Promìnné prostøedí pro Unix} +\label{sec:env} + +Adresáø binárek pro va¹i platformu musí být pøidán k~vyhledávacím cestám. +Ka¾dá podporovaná platforma má svùj vlastní podadresáø pod \dirname{TEXDIR/bin}. Seznam podadresáøù a odpovídajících platforem viz na obrázku~\ref{fig:bin.text}. + +Mù¾ete rovnì¾ pøidat dokumentaèní manuálové stránky (man) a adresáøe Info k~jejich +pøíslu¹ejícím vyhledávacím cestám, kdy¾ chcete, aby je na¹ly systémové nástroje. + +Napøíklad pro Bourne-kompatibilní shell, jako je \prog{bash} a pou¾ívaný Intel x86 +GNU/Linux se standardním nastavením adresáøù, mù¾e být vhodné editovat soubor + \filename{$HOME/.profile}. + +\begin{sverbatim} +PATH=/usr/local/texlive/2008/bin/i386-linux:$PATH; export PATH +MANPATH=/usr/local/texlive/2008/texmf/doc/man:$MANPATH; export MANPATH +INFOPATH=/usr/local/texlive/2008/texmf/doc/info:$INFOPATH; export INFOPATH +\end{sverbatim} + +Pro \prog{csh} nebo \prog{tcsh} je editovaný soubor typicky \filename{$HOME/.cshrc} a +øádky k~pøidání mù¾ou vypadat jako: + +\begin{sverbatim} +setenv PATH /usr/local/texlive/2008/bin/i386-linux:$PATH +setenv MANPATH /usr/local/texlive/2008/texmf/doc/man:$MANPATH +setenv INFOPATH /usr/local/texlive/2008/texmf/doc/info:$INFOPATH +\end{sverbatim} + + +\subsubsection{Promìnné prostøedí: globální konfigurace} +\label{sec:envglobal} + +Volba, zda uèinit tyto zmìny globálnì, anebo pro u¾ivatele právì +pøidaného do systému, je na vás; existuje pøíli¹ mnoho variací mezi +systémy, kde a jak se tato nastavení provádìjí. + +Na¹e dvì rady jsou: 1)~mù¾ete chtít vyhledat soubor +\filename{/etc/manpath.config} a pokud existuje, pøidejte øádky jako + +\begin{sverbatim} +MANPATH_MAP /usr/local/texlive/2008/bin/i386-linux \ + /usr/local/texlive/2008/texmf/doc/man +\end{sverbatim} + +A 2)~vyhledejte soubor \filename{/etc/environment}, který mù¾e definovat vyhledávací cestu a dal¹í standardní promìnné prostøedí. + +\subsubsection{Pøi spu¹tìní \protect\TL{} z~DVD} + +Program \TL{} obyèejnì nahlédne do souboru \filename{texmf.cnf} pro +umístìní rùzných stromù. Hledá tento soubor v~øadì míst vztahujících se +k~jeho vlastnímu umístìní. Nicménì, toto schéma selhává, kdy¾ je program +spou¹tìn z~\DVD{}: \DVD{} je pouze ke ètení. %read-only. +Nìkteré cesty zaznamenané v~\filename{texmf.cnf} jsou známé jen bìhem +instalace, tudí¾ tento soubor nemù¾e být na \DVD{} a musí být umístìn +nìkde jinde. To si vynucuje definovat promìnnou prostøedí +\envname{TEXMFCNF}, která sdìlí programùm \TL{}, v~kterém adresáøi je +mo¾né najít tento soubor \filename{texmf.cnf}. +Pøesto je také nutné upravit promìnnou prostøedí \envname{PATH}, jak bylo +popsáno døíve. + +Na konci instalace by instalaèní program mìl vytisknout hlá¹ení o~hodnotì, +na kterou se má nastavit promìnná \envname{TEXMFCNF}. Jestli¾e jste ji +minuli: tato hodnota je \dirname{$TEXMFSYSVAR/web2c}. Na pøedvolbu +\dirname{/usr/local/texlive/2008/texmf-var/web2c} potøebujete øádky +\begin{sverbatim} +TEXMFCNF=/usr/local/texlive/2008/texmf-var/web2c; export TEXMFCNF +\end{sverbatim} +nebo, pro [t]csh: +\begin{sverbatim} +setenv TEXMFCNF /usr/local/texlive/2008/texmf-var/web2c +\end{sverbatim} + +\subsubsection{\ConTeXt{} Mark IV} + +`Starý' \ConTeXt{} by mìl skonèit. %should run out of the box. +Nový \ConTeXt{} `Mark IV' +si vy¾ádá ruèní nastavení; viz +\url{http://wiki.contextgarden.net/Running_Mark_IV}. + + +\subsubsection{Zaèleòování lokálních a osobních maker} +\label{sec:local-personal.macros} + +Toto je ji¾ implicitnì zmínìno v~sekci~\ref{sec:texmftrees}: +adresáø \dirname{TEXMFLOCAL} (standardnì \dirname{/usr/local/texlive/texmf-local} nebo +\verb|C:\Program Files\texlive\texmf-local|) +je urèen pro rozsáhlé systémové % system-wide +lokální fonty a makra; a adresáø +\dirname{TEXMFHOME} (standardnì \dirname{$HOME/texmf} nebo +\verb|%USERPROFILE%\texmf|), je pro osobní fonty a makra. + +Pro oba stromy musí být soubory umístìné v~patøièných podadresáøích; +viz \url{http://tug.org/tds} nebo nahlédni do souboru +\filename{texmf/web2c/texmf.cnf}. Napøíklad, \LaTeX{}ovský soubor tøídy % class file or +nebo balík by mìl být umístìn v~\dirname{TEXMFLOCAL/tex/latex} nebo +\dirname{TEXMFHOME/tex/latex}, nebo v~jejich podadresáøi. + +\dirname{TEXMFLOCAL} vy¾aduje aktuální databázi jmen souborù, jinak +nebudou soubory nalezeny. +Mù¾ete ji obnovit povelem \cmdname{mktexlsr} nebo pou¾ít tlaèítko +`Reinit file database' na konfiguraèní zálo¾ce \prog{tlmgr} v~re¾imu \GUI. + +\subsubsection{Zaèleòování fontù tøetích stran} + +Toto je nane¹tìstí velice komplikované a delikátní téma. +Vyhnìte se tomu, pokud nejste expert. +Prohlédnìte si nejdøíve fonty, které jsou zadarma souèástí distribuce, +viz sekci~\ref{sec:tl.fonts}. + +Mo¾nou alternativou je pou¾ití \XeTeX u (viz sekci~\ref{sec:tex.extensions}), který vám +umo¾ní pou¾ívat fonty operaèního systému bez jakékoliv instalace v~\TeX u. + + +\subsection{Testování instalace} +\label{sec:test.install} + +Po nainstalování \TL{} pøirozenì chcete +systém otestovat a zaèít vytváøet nádherné dokumenty nebo fonty. + +Tento oddíl popisuje základní postupy testování funkènosti nového +systému pod Unixem. Pod \MacOSX{} a +Windows budete patrnì spou¹tìt testy pøes u¾ivatelské grafické rozhraní +(\acro{GUI}), ale principy jsou stejné. + +\begin{enumerate} +\item Nejprve ovìøte, zda se spustí program \cmdname{tex}: + +\begin{alltt} +> \Ucom{tex -{}-version} +TeX 3.1415926 (Web2C 7.5.7) +kpathsea version 3.5.7 +... +\end{alltt} +Pokud obdr¾íte hlá¹ku s~`command not found' místo vý¹e uvedeného, nebo se +star¹í verzí, patrnì nemáte nastavený správný podadresáø +\dirname{bin} v~promìnné prostøedí \envname{PATH}. Vra»te se +k~informacím o~jejich nastavování na stranì~\pageref{sec:env}. + +\item Pøelo¾te ukázkový soubor \LaTeX{}u: +\begin{alltt} +> \Ucom{latex sample2e.tex} +> This is pdfeTeXk, Version 3.1415926... +Output written on sample2e.dvi (3 pages, 7484 bytes). +Transcript written on sample2e.log. +\end{alltt} +Pokud sel¾e nalezení souboru \filename{sample2e.tex} nebo jiných +souborù, nejspí¹e máte aktivní stará nastavení promìnných prostøedí nebo +konfiguraèních souborù; pro zaèátek doporuèujeme zru¹it nastavení v¹ech promìnných prostøedí souvisejících s~\TeX{}em. +Pro hlub¹í analýzu a dohledání problému mù¾ete kdykoliv po¾ádat +\TeX{} o detaily toho, co a kde hledá: viz \uv{Ladicí èinnosti} +na stranì~\pageref{sec:debugging}. + +\item Prohlédnìte si výsledek na obrazovce: +\begin{alltt} +> \Ucom{xdvi sample2e.dvi} +\end{alltt} +(Pod Windows je analogický pøíkaz \cmdname{dviout}.) Mìlo by se +otevøít nové okno s~pìkným dokumentem popisujícím základy +\LaTeX{}u. (Mimochodem, stojí za pøeètení, pokud zaèínáte.) +Musíte mít spu¹tìny +X~Window, aby \cmdname{xdvi} pracovalo. Pokud tomu tak není nebo máte +¹patnì nastavenou promìnnou prostøedí +\envname{DISPLAY}, dostanete chybovou hlá¹ku `Can't open display'. + +\item Vytvoøte \PS{}ový soubor pro tisk nebo prohlí¾ení: +\begin{alltt} +> \Ucom{dvips sample2e.dvi -o sample2e.ps} +\end{alltt} + +\item Vytvoøte \acro{PDF} soubor místo \dvi{}; tento pøíkaz +ze~souboru \filename{.tex} vytvoøí \acro{PDF} pøímo: +\begin{alltt} +> \Ucom{pdflatex sample2e.tex} +\end{alltt} + +\item Prohlédnìte si \acro{PDF} soubor: +\begin{alltt} +> \Ucom{gv sample2e.pdf} +\textrm{nebo:} +> \Ucom{xpdf sample2e.pdf} +\end{alltt} +Bohu¾el ani \cmdname{gv} ani \cmdname{xpdf} nejsou v~souèasné dobì na +\TL{} a musíte je instalovat separátnì. Viz +\url{http://www.gnu.org/software/gv} a +\url{http://www.foolabs.com/xpdf}. (Existuje také velké mno¾ství jiných prohlí¾eèù \acro{PDF}.) + +\item Standardní testovací soubory, které mohou být u¾iteèné kromì \filename{sample2e.tex}: + +\begin{ttdescription} +%B% \item [docstrip.tex] Vytvoøení \TeX{}ového zdroje èi dokumentace ze +%B% souboru~\samp{.dtx}. +\item [small2e.tex] Ukázkový dokument, je¹tì krat¹í ne¾ +\filename{sample2e}. +\item [testpage.tex] Test, jestli va¹e tiskárna neposunuje tiskové zrcadlo. +\item [nfssfont.tex] Pro tisk tabulek fontù a testù fontù. +\item [testfont.tex] Pro toté¾, ale pro plain \TeX{}. +\item [story.tex] Základní (plain) \TeX{}ový testovací soubor. +Musíte napsat \samp{\bs bye} na výzvu \code{*} po \samp{tex +story.tex}. +\end{ttdescription} +\end{enumerate} + +Pokud jste \TeX{}ový zaèáteèník nebo potøebujete pomoc se psaním +\TeX{}ových, respektive \LaTeX{}ových dokumentù, nav¹tivte +\url{http://tug.org/begin.html}, kde najdete úvodní informace +k~instalaci. + +\section{Sí»ové instalace} +\label{sec:netinstall} + +\TL{} byl navr¾ený pro sdílení mezi rùznými u¾ivateli, nebo dokonce pro rùzné systémy na síti. +Se standardní strukturou adresáøù se nekonfigurují ¾ádné % no hard paths are configured +pevné cesty: umístìní souborù potøebných pro programy \TL{} +je definováno relativnì k~umístìním tìchto programù. Mù¾ete to najít v~èinnosti v~konfiguraèním souboru +\filename{$TEXMFMAIN/web2c/texmf.cnf}, který obsahuje øádky jako jsou +\begin{sverbatim} +TEXMFMAIN = $SELFAUTOPARENT/texmf +... +TEXMFLOCAL = $SELFAUTOPARENT/../texmf-local +\end{sverbatim} +To znamená, ¾e jiné systémy nebo jiní u¾ivatelé potøebují pouze pøidat ke +své vyhledávací cestì adresáø binárek \TL{} pro jejich platformu. + +%By the same token, +Stejným zpùsobem mù¾ete nainstalovat \TL{} lokálnì a pak pøesunout celou hierarchii pozdìji na místo na síti. + +Pochopitelnì, u¾ivatelé pod Windows mají jiné oèekávání. Adresáø +\dirname{texmf-doc/source/texlive/texlive-common/w32client} obsahuje vzorový skript \filename{install-w32client}, +který vytváøí nastavení a nabídkové zkratky k~u¾ívání stávající instalace \TL{} na +\acro{LAN}. Pou¾ívá se to pomocí dávkového souboru +\filename{install-w32client.bat} ve stejném adresáøi. + +Víc o konfiguraci \TL{} a vyhledávání cest si mù¾ete pøeèíst v~sekci~\ref{sec:kpathsea}. + + +\section{Maximálnì mobilní \protect\TL{} na DVD a USB} +\label{sec:portable.unix} + +Volba `running from \DVD{}' (spou¹tìní z~\DVD{}) popsaná v~sekci~\ref{sec:fromdvd} +je skvìlá pro vá¹ systém, ale kdy¾ jste hostem na systému nìkoho jiného, +pak by se vám mo¾ná líbilo nìco s~nejmen¹ími vedlej¹ími úèinky. + +V~koøenovém adresáøi \TL{} \DVD, nebo v~podadresáøi \dirname{texlive} \TKCS{} \DVD, jsou skripty \filename{tl-portable} (Unix) a dávkové soubory +\filename{tl-portable.bat} (Windows), které spou¹tí shell s~nastavením prostøedí odpovídajícím pøímému pøístupu \TL{} na \DVD. + +Pøi prvním spu¹téní budou vygenerovány nìkteré soubory v~adresáøi +\dirname{~/.tlportable2008}, co¾ zabere jistý krátký èas. +Nicménì, pøi následných spou¹tìních zaène témìø okam¾itì. + +Zbytek systému si \TL{} nebude uvìdomovat. Pokud chcete, aby byl vá¹ editor informovaný o~tomto \TL, pak ho mù¾ete spustit z~druhé, paralelní, stejné \filename{tl-portable} relace. + +Skripty \filename{tl-portable} mù¾ete také pou¾ít na spu¹tìní \TL{} z~\acro{USB} klíèe. V~tomto pøípadì zkopírujte (pøinejmen¹ím) v¹echny soubory na nejvy¹¹í urovni a obsah adresáøù \dirname{bin}, \dirname{texmf}, +\dirname{texmf-dist} a \dirname{tlpkg} na klíè. To mù¾e nìjaký èas zabrat! +Pokud kopírujete na \acro{USB} klíè formátovaný jako \acro{FAT}32, nezapomeòte zru¹it %dereference +symbolické odkazy (\code{cp -L}). Adresáø \dirname{texmf-local} na klíèi +bude také nalezen a pou¾it. + +Pak spus»te skript \filename{tl-portable} z~koøenového adresáøe klíèe, jak bylo uvedeno vý¹e. +V~tom pøípadì bude skript vnímat klíè jako zapisovatelný a pou¾ije ho pro vytvoøené soubory. + + + +\section{\cmdname{tlmgr}: správa va¹í instalace} +\label{sec:tlmgr} + +\begin{figure}[tb] +\tlpng{tlmgr-gui}{\linewidth} +\caption{\prog{tlmgr} v~re¾imu \GUI. Seznam balíkù/kolekcí/schémat se uká¾e a¾ po kliknutí na tlaèítko `Load'.}\label{fig:tlmgr.gui} +\end{figure} + +\begin{figure}[tb] +\tlpng{tlmgr-config}{\linewidth} +\caption{\texttt{tlmgr} v~re¾imu GUI: konfiguraèní zálo¾ka}\label{fig:tlmgr.config} % Configuration tab +\end{figure} + +Instalaèní program nainstaluje program nazvaný \prog{tlmgr} pro správu \TL{} +po výchozí instalaci. Programy \prog{updmap}, +\prog{fmtutil} a \prog{texconfig} jsou dosud zahrnuté a zùstanou i v~budoucnosti, av¹ak preferovaným rozhraním je nyní \prog{tlmgr}. +Jeho schopnosti zahrnují: + +\begin{itemize*} +\item výpis seznamù schémat, kolekcí a balíkù; +\item instalaci, aktualizaci, zálohování, obnovení a odinstalování jednotlivých balíkù, volitelnì se zapoèítáním závislostí; % optionally taking dependencies into account; +\item vyhledávání balíkù; +\item výpis seznamu a pøidání architektur; +\item zmìna instalaèních voleb jako napøíklad velikosti papíru a umístìní zdrojù (viz sekci~\ref{sec:location}). +\end{itemize*} +\textit{Varování:} \prog{tlmgr} nebyl urèený pro nebo testovaný s~instalacemi, které jsou spou¹tìné z~\DVD. + +\subsection{GUI re¾im \cmdname{tlmgr}} +\prog{tlmgr} mù¾e být spu¹tìn v~re¾imu \GUI{} povelem +\begin{alltt} +> \Ucom{tlmgr -gui} +\end{alltt} +nebo ve Windows prostøednictvím Start menu: \texttt{Start}, \texttt{Programs}, +\texttt{TeX Live 2008}, \texttt{TeX Live Manager}. Po kliknutí na `Load' +se zobrazí seznam balíkù, které jsou k~dispozici, a nainstalovaných +balíkù\Dash poslednì zmínìné jsou oznaèeny `(i)'. Pochopitelnì se +pøedpokládá, ¾e instalaèní zdroj je platný a dosa¾itelný. +Obrázek~\ref{fig:tlmgr.config} ukazuje konfiguraèní zálo¾ku. + + +\subsection{Vzorové realizace \cmdname{tlmgr} z~pøíkazového øádku} + +Tento pøíklad pøidá nìkolik balíkù, vèetnì nového `motoru' (`engine'), z~nestandardní lokace: + +\begin{alltt} +> \Ucom{tlmgr -location http://172.16.18.1/tldev install collection-xetex xkeyval} +\end{alltt} +Vytvoøí následující výstup: +\begin{fverbatim} +install: collection-xetex +install: arabxetex +install: euenc +install: bidi +install: fontspec +install: fontwrap +install: ifxetex +install: philokalia +install: polyglossia +install: xecyr +install: xecyr.i386-linux +install: xepersian +install: xetex +install: xetexconfig +install: xetex.i386-linux +running post install action for xetex +install: xetex-def +install: xetex-pstricks +install: xetexfontinfo +install: xltxtra +install: xunicode +install: xkeyval +running mktexlsr +mktexlsr: Updating /usr/local/texlive/2008/texmf/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-config/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-dist/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-doc/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/../texmf-local/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-var/ls-R... +mktexlsr: Done. +regenerating fmtutil.cnf +running fmtutil-sys --missing +... +Transcript written on xelatex.log. +fmtutil: /usr/local/texlive/2008/texmf-var/web2c/xetex/xelatex.fmt installed. +\end{fverbatim} +Jak vidíte, \prog{tlmgr} nainstaluje závislosti a postará se o~v¹echny potøebné poinstalaèní èinnosti, vèetnì aktualizace databáze názvù souborù a (znovu)vygenerování formátù. (Tady jsme vytvoøili nové formáty pro \XeTeX.) + +Tento pøíklad instaluje nový jazyk. I toto spustí znovuvytvoøení formátù: +\begin{alltt} +> \Ucom{tlmgr install collection-langdutch} +\end{alltt} +K~popisu balíku zadejte: +\begin{alltt} +> \Ucom{tlmgr show collection-wintools} +\end{alltt} +co vytvoøí +\begin{fverbatim} +Package: collection-wintools +Category: Collection +ShortDesc: Windows support programs +LongDesc: Utilities for Windows, since they are not readily available there: + gzip, chktex, jpeg2ps, unzip, wget, xpdf. +Installed: Yes +\end{fverbatim} +Aktualizace celé va¹i instalace na nejnovìj¹í dostupné verze: +\begin{alltt} +> \Ucom{tlmgr update -all} +\end{alltt} +Pokud vás to znepokojuje, zkuste nejdøíve +\begin{alltt} +> \Ucom{tlmgr update -all -dry-run} +\end{alltt} +nebo +\begin{alltt} +> \Ucom{tlmgr update -list} +\end{alltt} +Pro úplnou dokumentaci: +\begin{alltt} +> \Ucom{tlmgr -help} +\end{alltt} + +\section{Poznámky o Windows} +\label{sec:windows} + +\TL\ má jediný instalaèní program, který bì¾í na obou systémech Windows +a Unix. Toto bylo mo¾né jenom sní¾ením podpory star¹ích verzí Windows, +proto je mo¾né instalovat \TL{} pouze na Windows 2000 a novìj¹í. + + +\subsection{Vlastnosti typické pro Windows} %Windows-specific features +\label{sec:winfeatures} + +Pod Windows dìlá instalaèní program nìkteré dodateèné vìci: +\begin{description} +\item[Nabídky a zkratky.] Je nainstalována nová polo¾ka `\TL{}' nabídky + Start, obsahující vstupy pro nìkteré programy \GUI{} + (\prog{tlmgr}, \prog{texdoctk}, prohlí¾eè PostScriptu PS\_View) + a trochu dokumentace. PS\_View také získává ikonku na pracovní plo¹e jako %a drag-and-drop + cíl pro PostScriptové soubory. +\item[Automatické nastavení promìnných prostøedí.] ®ádné ruèní konfiguraèní kroky nejsou potøebné. +\item[Odinstalátor.] Instalaèní program vytvoøí polo¾ku pro \TL{} pod nabídkou `Add/Remove + Programs'. Vztahuje se k~tomu zálo¾ka `Uninstallation' programu \prog{tlmgr}. +\end{description} + +\subsection{Dodateèný obsa¾ený software} + +\begin{figure}[tb] +\tlpng{psview}{.6\linewidth} +\caption{PS\_View: k~dispozici jsou velmi vysoká zvìt¹ení!}\label{fig:psview} +\end{figure} + + +Pro úplnost, instalace \TL{} potøebuje dal¹í balíky a programy, +které na stroji s~Windows obvykle nenajdete. + +\TL{} poskytuje chybìjící souèásti: +\begin{description} +\item[Perl a Ghostscript.] Kvùli dùle¾itosti Perlu a Ghostscriptu + zahrnuje \TL{} `skryté' kopie tìchto programù. + Programy \TL{}, které je potøebují, vìdí, kde je najdou, ale + neprozrazují jejich pøítomnost nastavením promìnných prostøedí nebo + registrù. Nejsou to úplné distribuce a nemìly by pøeká¾et ¾ádným + systémovým instalacím Perlu nebo Ghostscriptu. +\item[Nástroje pøíkazového øádku.] Øada bì¾ných Unixových programù øízených z~pøíkazového øádku je nainstalovaných pod Windows spolu s~bì¾nými binárkami \TL. Tyto zahrnují programy \cmdname{gzip}, \cmdname{chktex}, + \cmdname{jpeg2ps}, \cmdname{unzip}, \cmdname{wget} a pomùcky pøíkazového øádku %command-line utilities + ze skupiny \cmdname{xpdf}. (Samotný prohlí¾eè \cmdname{xpdf} není k~dispozici pro Windows, ale je na nìm zalo¾en prohlí¾eè \acro{PDF} Sumatra: + \url{http://blog.kowalczyk.info/software/sumatrapdf}.) +\item[\texttt{fc-cache}] pomáhá \XeTeX{}u efektivnìji zacházet s~fonty. +\item[PS\_View.] PS\_View, nový prohlí¾eè PostScriptu s~volnou (free) licencí, je také nainstalován; viz obrázek~\ref{fig:psview}. +\end{description} +\begin{description} +\item[Podpùrný adresáø \texttt{support},] ji¾ zmínìný v~sekci~\ref{sec:tld}. +Tento adresáø obsahuje rozlièné programy, které mù¾ou být u¾iteèné ve spojení s~\TeX{}em, zvlá¹tì nìkolik editorù zamìøených na \TeX{} %\TeX-aware editors +a \TeX{}ovských pomùcek (frontends). % frontends. +Software v~tomto adresáøi není pokrytý instalátorem. Tento adresáø obsahuje té¾ prohlí¾eè \dvi{} \cmdname{dviout}; viz následující sekci. +\end{description} + + +\subsection{The Dviout previewer} + +Bohu¾el toto vydání \TL{} nenabízí nainstalovaný prohlí¾eè \dvi{} souborù pro Windows. Nicménì, mù¾ete si nainstalovat \prog{dviout} od +Toshio Oshimy z~adresáøe \path{support/dviout/}, který obsahuje rovnì¾ malý soubor \filename{README} popisující instalaci a konfiguraci \prog{dviout} pro \TL. Pøeètìte si ho, prosím, peèlivì pøed instalací. + +V~první øadì, kdy¾ si prohlí¾íte soubory pomocí \cmdname{dviout}, vytvoøí tento fonty, proto¾e obrazovkové fonty nebyly nainstalovány. Po chvíli budete mít vytvoøenou vìt¹inu vámi pou¾ívaných fontù a málokdy uvidíte okno s~vytváøením fontù. +Dal¹í informace je mo¾né najít ve (velmi dobré) on-line nápovìdì. + + +\subsection{Odkazy na dodateèný software s~mo¾ností sta¾ení z~internetu} + +Url adresy nìkterých dal¹ích nástrojù, které mù¾ete mít v~úmyslu instalovat: + +\begin{description} +\item[\GS{}] \url{http://www.cs.wisc.edu/~ghost/} +\item[Perl] \url{http://www.activestate.com/} s~pomocnými balíky z~\acro{CPAN}u: \url{http://www.cpan.org/} +\item[ImageMagick] \url{http://www.imagemagick.com/} ke zpracování a konverzi grafiky +\item[NetPBM] \url{http://netpbm.sourceforge.net/} také pro grafiku +\item[\TeX{}ové editory] Máte ¹iroký výbìr a je to + individuální volba. Mo¾nosti jsou napøíklad tyto, bez zvlá¹tního uspoøádání: + \begin{itemize*} + \item \cmdname{GNU Emacs} má pro Windows nativní podporu na + \url{http://www.gnu.org/software/emacs/windows/ntemacs.html} + \item \cmdname{Emacs} s~Auc\TeX{}em pro Windows je k~dispozici na \TL{} v~adresáøi \path{support}; jeho domovská stránka je \url{http://www.gnu.org/software/auctex}. + \item \cmdname{WinShell} je dostupný na \TL{} v~adresáøi + \path|support|, jeho domovská stránka je \url{http://www.winshell.de/} + \item \cmdname{WinEdt} je shareware dostupný na \url{http://www.winedt.com/} + \item \cmdname{Vim} je volný editor do\-stup\-ný z~\url{http://www.vim.org/} + \item TeXnicCenter je volný softvér, který získáte na\\ \url{http://www.toolscenter.org/} a v~distribuci pro\TeX t. \item \cmdname{LEd} je dostupný z~\url{http://www.ctan.org/support/LEd}. + \item \cmdname{SciTE} je dostupný z~\url{http://www.scintilla.org/SciTE.html}. + \end{itemize*} +\end{description} + + +\subsection{User Profile je Home} +\label{sec:winhome} + +Windowsovský protìj¹ek domovského (home) adresáøe Unixu je adresáø +\verb|%USERPROFILE%|. Pod Windows XP a Windows 2000 je to obvykle +\verb|C:\Documents and Settings\| a pod Windows Vista +\verb|C:\Users\|. V~souboru +\filename{texmf.cnf} a obecnì pro \KPS{}, se bude \verb|~| expandovat +pøimìøenì v~obou systémech Windows a Unix. + + +\subsection{Registry Windows} +\label{sec:registry} + +Windows ukládá témìø v¹echny konfiguraèní údaje do svých registrù. Registr +obsahuje soubor hierarchicky uspoøádaných klíèù, s~nìkolika koøenovými klíèi. +Nejdùle¾itìj¹í pro instalaèní programy jsou struènì øeèeno +\path{HKEY_CURRENT_USER} a \path{HKEY_LOCAL_MACHINE}, \path{HKCU} a +\path{HKLM}. Èást \path{HKCU} registra je v~domovském adresáøi u¾ivatele (viz sekci~\ref{sec:winhome}). \path{HKLM} je obvykle v~podadresáøi adresáøe Windows. + +V~nìkterých pøípadech je mo¾né získat systémové informace z~promìnných +prostøedí, ale pro dal¹í informace, kupøíkladu umístìní zkratek, je nutné +nahlédnout do registrù. Trvalé nastavení promìnných prostøedí si rovnì¾ +vy¾aduje pøístup k~registrùm. + + +\subsection{Oprávnìní Windows} +\label{sec:winpermissions} + +V~novìj¹ích verzích Windows se dìlá rozdíl mezi bì¾nými u¾ivateli a +administrátory, kdy¾ pouze poslednì zmínìní mají volný pøístup k~celému +operaènímu systému. Ve skuteènosti mù¾ete tyto tøídy u¾ivatelù radìji +oznaèit jako neprivilegovaní u¾ivatelé a normální u¾ivatelé: být +administrátorem je pravidlo, ne výjimka. Pøesto jsme se sna¾ili uèinit +\TL{} instalovatelným bez administrativních výsad. + +Pokud je u¾ivatel administrátor, odkazy (shortcuts) se vytváøejí pro +v¹echny u¾ivatele a systémové prostøedí se upravuje. Jinak jsou odkazy a +polo¾ky nabídky vytváøeny pro aktuálního u¾ivatele a upravuje se prostøedí +u¾ivatele. Pou¾ijte volbu \optname{non-admin} pro \prog{install-tl}, pokud +upøednostòujete nastavení podle u¾ivatele dokonce jako administrátor. + +Bez ohledu na status administrátora je standardní koøenový adresáø \TL{} +navr¾ený instalaèním programem v¾dycky pod \verb|%PROGRAMFILES%|. +Instalátor stále testuje, zda je root zapisovatelný pro aktuálního +u¾ivatele. + +Problém se mù¾e vyskytnout, pokud u¾ivatel není administrátor a \TeX{} ji¾ +existuje ve vyhledávací cestì. Proto¾e skuteèná cesta se sestává ze +systémové cesty následované u¾ivatelskou cestou, nový \TL{} nikdy nezíská +pøednost. +Jako dùsledek %As a workaround, +Toto instalátor obchází vytvoøením odkazù na pøíkazový øádek +(command-prompt), ve kterém je adresáø binárek nového \TL{} +pøedøazený lokální vyhledávací cestì. Nový \TL{} bude pou¾itelný, kdy¾ +bude bì¾et v~relaci pøíkazového øádku spu¹tìné z~takového odkazu. + +\begin{otherlanguage}{slovak} +\frenchspacing +% don't use \Webc so the \uppercase in the headline works. +\section{Pou¾ívateµská príruèka ku systému Web2C} +\Webc{} obsahuje mno¾inu \TeX-príbuzných programov, t.j.\ samotný \TeX{}, +\MF{}, \MP, \BibTeX{}, atï. Je to srdce systému \TL{}. Domovská stránka \Webc{}, +s~aktuálnou príruèkou a ïal¹ími vecami, je +\url{http://tug.org/web2c}. + +Trochu histórie: originálna implementácia pochádza +od Thomasa Rokického, ktorý v~roku 1987 vyvinul prvý +\TeX{}-to-C systém zalo¾ený na zmenových súboroch systému pre Unix, ktoré +boli v~prvom rade pôvodnou prácou Howarda Trickeya a Pavla Curtisa. +Tim Morgan +sa stal spravovateµom systému a poèas jeho obdobia sa meno zmenilo +na Web-to-C\@. V~roku 1990 Karl Berry prebral túto prácu, +asistoval pri tuctoch dodatoèných príspevkov a v~roku 1997 podal +taktovku Olafovi Weberovi, ktorý ju v~roku 2006 vrátil Karlovi. + +\Webc{} systém be¾í pod Unixom, 32bitovými Windows, +\acro{MacOSX} a inými operaènými systémami. Pou¾íva originálne +\TeX{} zdrojové súbory od Knutha a ostatné základné programy napísané +v~systéme kultivovaného programovania \web{}, ktoré sú prelo¾ené do zdrojového kódu jazyka C. +Základné programy \TeX{}u sú spracované týmto spôsobom: +\begin{description} +\renewcommand{\makelabel}[1]{\descriptionlabel{\mdseries\cmdname{#1}}} +\item[bibtex] Spravovanie bibliografií. +\item[dmp] Konverzia \cmdname{troff} do MPX (\MP{} obrázky). +\item[dvicopy] Vytváranie modifikovanej kópie \dvi{} súboru. +\item[dvitomp] Konverzia \dvi{} do MPX (\MP{} obrázky). +\item[dvitype] Konverzia \dvi{} do µudsky èitateµného textu. +\item[gftodvi] Generovanie fontov pre náhµad. +\item[gftopk] Konverzia gf formátu fontov do pakovaných fontov. +\item[gftype] Konverzia gf formátu fontov do µudsky èitateµného textu. +\item[makempx] \MP{} znaèkové sádzanie. +\item[mf] \MF{} -- vytváranie rodín fontov. +\item[mft] Preddefinované \MF ové zdrojové súbory. +\item[mpost] \MP{} -- tvorba technických diagramov. +\item[mpto] \MP{} -- znaèkový výber. +\item[newer] Porovnanie modifikaèných èasov. +\item[patgen] Vytvaránie vzorov rozdeµovania slov. +\item[pktogf] Konverzia pakovaných formátov fontov do +gf formátov. +\item[pktype] Konverzia pakovaných písiem do µudsky èitateµného textu. +\item[pltotf] Konverzia `Property list' do TFM. +\item[pooltype] Zobrazovanie \singleuv{\web{} pool} súborov. +\item[tangle] Konverzia \web{} súborov do Pascalu. +\item[tex] \TeX{} -- sadzba. +\item[tftopl] Konverzia TFM do `property list'. +\item[vftovp] Konverzia virtuálneho fontu do virtuálneho `property list'. +\item[vptovf] Konverzia virtuálneho `property list' do virtuálneho fontu. +\item[weave] Konverzia \web{} súborov do \TeX u. +\end{description} +\noindent Presné funkcie a syntax týchto programov sú popísané +v~dokumentáciách jednotlivých balíkov alebo v~dokumentácii +\Webc{}. Napriek tomu, poznanie niekoµkých princípov, ktoré +platia pre celý balík programov, vám pomô¾e vy»a¾i» èo najviac +z~va¹ej \Webc{} in¹talácie. + +V¹etky programy dodr¾iavajú ¹tandardné \GNU{} voµby: + +\begin{description} +\item[\texttt{--help}] Vypisuje prehµad základného pou¾ívania. +\item[\texttt{--verbose}] Vypisuje detailnú správu spracovania. +\item[\texttt{--version}] Vypisuje informáciu o~verzii, potom skonèí. +\end{description} + +Na vyhµadávanie súborov pou¾ívajú \Webc{} programy prehµadávaciu +kni¾nicu \KPS{} (\url{http://tug.org/kpathsea}). +Táto kni¾nica pou¾íva kombináciu premenných +prostredia a niekoµkých konfiguraèných súborov na optimalizáciu +prehµadávania adresárového stromu \TeX u{}. \Webc{} zvládne +prácu s~viacerými adresárovými stromami súèasne, èo je +u¾itoèné, ak niekto chce udr¾iava» ¹tandardnú distribúciu \TeX u a jeho +lokálne a osobné roz¹írenia v~rozlièných stromoch. Na urýchlenie +vyhµadávania súborov, koreò ka¾dého stromu obsahuje súbor +\file{ls-R} so záznamom obsahujúcim meno a relatívnu cestu ku +v¹etkým súborom umiestneným pod týmto koreòom. + +\subsection{Vyhµadávanie ciest kni¾nicou Kpathsea} +\label{sec:kpathsea} + +Najprv popí¹eme v¹eobecný mechanizmus vyhµadávania ciest +kni¾nicou \KPS{}. + +\emph{Vyhµadávacou cestou} nazveme zoznam \emph{elementov cesty}, +ktorými sú v~prvom rade mená adresárov +oddelené dvojbodkou alebo bodkoèiarkou. +Vyhµadávacia cesta mô¾e pochádza» z~viacerých zdrojov. +Pri vyhµadávaní súboru \samp{my-file} podµa cesty \samp{.:/dir}, +\KPS{} skontroluje ka¾dý element cesty: najprv \file{./my-file}, +potom \file{/dir/my-file}, vracajúc prvý zodpovedajúci nájdený +prvok (alebo prípadne v¹etky zodpovedajúce prvky). + +Aby bolo dosiahnuté prispôsobenie sa konvenciám èo mo¾no najviac +operaèných systémov, na neunixových systémoch \KPS{} mô¾e pou¾íva» +oddeµovaèe názvov súborov rôzne od dvojbodky (\samp{:}) a +lomítka (\samp{/}). + +Pri kontrolovaní urèitého elementu cesty \var{p} \KPS{} najprv +overí, èi sa na naò nevz»ahuje vopred vybudovaná databáza (pozri +\singleuv{Data\-báza názvov súborov} na +strane~\pageref{sec:filename.database}), t.\,j., èi sa databáza nachádza +v~adresári, ktorý je prefixom \var{p}. Ak to tak je, ¹pecifikácia +cesty sa porovnáva s~obsahom databázy. + +Ak databáza neexistuje, alebo sa nevz»ahuje na tento element cesty, alebo +sa v~nej hµadaný súbor nevyskytuje, celý systém súborov je prehµadaný +(pokiaµ to nebolo zakázané ¹pecifikáciou zaèínajúcou \samp{!!} a +hµadaný súbor musí existova»). \KPS{} zostrojí zoznam adresárov +zodpovedajúcich tomuto elementu cesty a potom skontroluje ka¾dý +z~nich, èi sa v~òom nenachádza hµadaný súbor. + +Podmienka \singleuv{súbor musí existova»\kern1pt} sa týka napr.\ súborov typu +\samp{.vf} a vstupných súborov èítaných príkazom \TeX u \cs{openin}. +Takéto súbory nemusia existova» (napr.\ \file{cmr10.vf}) a nebolo +by dobré prehµadáva» kvôli nim celý disk. Preto, ak zabudnete +aktualizova» \file{ls-R} pri in¹talácii nového \samp{.vf} súboru, +súbor nebude nikdy nájdený. Ka¾dý element cesty sa prekontroluje: najprv +databáza, potom disk. Keï je súbor nájdený, vyhµadávanie sa zastaví +a výsledok je vrátený. + +Hoci najjednoduch¹í a najbe¾nej¹í element cesty je meno adresáru, +\KPS{} podporuje aj iné zdroje vo vyhµadávacích cestách: dedièné +(layered) ¹tandardné hodnoty, mená premenných prostredia, hodnoty +súboru \file{config}, domáce adresáre pou¾ívateµov a rekurzívne +prehµadávanie podadresárov. Preto, ak hovoríme, ¾e \KPS{} +\emph{rozbalí} element cesty, znamená to, ¾e pretransformuje v¹etky +¹pecifikácie do základného mena alebo mien adresárov. Toto je +popísané v~nasledujúcich odsekoch. + +V¹imnite si, ¾e keï je meno hµadaného súboru vyjadrené absolútne +alebo explicitne relatívne, t.\,j.\ zaèína \samp{/} alebo \samp{./} +alebo \samp{../}, \KPS{} jednoducho skontroluje, èi taký súbor +existuje. + +\ifSingleColumn +\else +\begin{figure*} +\verbatiminput{examples/ex5.tex} +\setlength{\abovecaptionskip}{0pt} + \caption{Ilustraèný príklad konfiguraèného súboru} + \label{fig:config.sample} +\end{figure*} +\fi + +\subsubsection{Zdroje cesty} +\label{sec:pathsources} + +Vyhµadávacia cesta mô¾e by» vytvorená z~rôznych zdrojov. +\KPS{} ich pou¾íva v~tomto poradí: +\begin{enumerate} +\item + Pou¾ívateµom nastavená premenná prostredia, napríklad \envname{TEXINPUTS}\@. + Premenné prostredia s~pridanou bodkou a menom programu majú prednos» pred + premennými rovnakého mena, ale bez prípony. + Napríklad, keï \samp{latex} je meno práve be¾iaceho programu, potom + premenná \envname{TEXINPUTS.latex} prepí¹e \envname{TEXINPUTS}. +\item + Programovo-¹pecifický konfiguraèný súbor, napríklad riadok + \singleuv{\texttt{S /a:/b}} v~súbore \file{config.ps} \cmdname{dvips}. +\item Konfiguraèný súbor \KPS{} \Dash{} \file{texmf.cnf}, obsahujúci riadok + ako \samp{TEXINPUTS=/c:/d} (pozri ïalej). +\item Predvolené hodnoty poèas kompilácie. +\end{enumerate} +\noindent V¹etky tieto hodnoty vyhµadávacej cesty mô¾ete prezera» +pou¾itím ladiacích mo¾ností (pozri \singleuv{Ladenie} na +strane~\pageref{sec:debugging}). + +\subsubsection{Konfiguraèné súbory} +\tolerance=3500 +\KPS{} èíta poèas behu z~\emph {konfiguraèných súborov} +s~menom \file{texmf.cnf} vyhµadávaciu cestu a ïal¹ie definície. +Vyhµadávacia cesta pou¾ívaná na hµadanie týchto súborov sa +volá \envname{TEXMFCNF} (v~predvolenom nastavení sa tento súbor +nachádza v~podadresári \file{texmf/web2c}). \emph{V¹etky} súbory +\file{texmf.cnf} vo vyhµadávacej ceste budú preèítané a definície +v~posledných naèítaných súborov majú prednos» pred definíciami +èítanými predtým. Preto pri vyhµadávacej ceste \verb|.:$TEXMF|, hodnoty +z~\file{./texmf.cnf} prepí¹u hodnoty z~\verb|$TEXMF/texmf.cnf|. +\tolerance=1500 + +\begin{itemize} +\item + Komentáre zaèínajú znakom \singleuv{\texttt{\%}} a pokraèujú do konca + riadku. +\item + Prázdne riadky sú ignorované. +\item + Znak \bs{} na konci riadku slú¾i ako pokraèovací znak, t.j.\ + nasledujúci riadok je k~nemu pripojený. Prázdne znaky na zaèiatku + pripájaných riadkov nie sú ignorované. +\item + V¹etky ostatné riadky majú tvar: +\begin{alltt} + \var{variable}[.\var{progname}] [=] \var{value} +\end{alltt}% + kde \samp{=} a prázdne znaky naokolo sú nepovinné. +\item + Meno premennej \singleuv{\texttt{\var{variable}}} mô¾e obsahova» + akékoµvek znaky okrem prázdnych znakov, \samp{=}, alebo \samp{.}, + ale obmedzi» sa na znaky \samp{A-Za-z\_} je najbezpeènej¹ie. +\item + Ak je \singleuv{\texttt{.\var{progname}}} neprázdne, definícia sa + pou¾ije iba vtedy, keï práve be¾iaci program má meno + \texttt{\var{progname}} alebo \texttt{\var{progname}.exe}. + Toto umo¾òuje napríklad ma» pre rôzne nadstavby \TeX u rôzne + vyhµadávacie cesty. +\item Hodnota \singleuv{\texttt{\var{value}}} mô¾e obsahova» akékoµvek + znaky okrem \singleuv{\texttt{\%}} a \samp{@}. Na pravej strane nie je + mo¾né pou¾i» \singleuv{\texttt{\$\var{var}.\var{prog}}}; namiesto toho + musíte pou¾i» ïal¹iu premennú. Znak \samp{;} vo + \singleuv{\texttt{\var{value}}} je prelo¾ený do \samp{:} ak sme pod + operaèným systémom Unix. Toto je u¾itoèné, keï chceme ma» jediný + \file{texmf.cnf} súbor pre systémy Unix, MSDOS a Windows. +\item + V¹etky definície sú preèítané skôr, ako sa expandujú. Preto mô¾u + existova» referencie na premenné skôr, ako sú tieto definované. +\end{itemize} +Uká¾kový úsek konfiguraèného súboru, ilustrujúci väè¹inu +týchto bodov\ifSingleColumn +\ignorespaces: +\verbatiminput{examples/ex5.tex} +\else +\space je na obrázku~\ref{fig:config.sample}. +\fi + +\subsubsection{Expanzia cesty} +\label{sec:pathexpansion} + +\KPS{} rozpoznáva urèité zvlá¹tne znaky a kon¹trukcie vo +vyhµadávacích cestách podobné tým, èo existujú v~prostrediach +unixovských interprétov príkazového riadku (shells). Ako v¹eobecný +príklad uvedieme komplexnú cestu \verb+~$USER/{foo,bar}//baz+, %$ +ktorá sa expanduje do v¹etkých podadresárov pod adresármi \file{foo} a \file{bar} +v~domovskom adresári pou¾ívateµa \texttt{\$USER}, ktorý obsahuje +adresár alebo súbor \file{baz}. Tieto kon¹trukcie sú popísané +v~ïal¹ích odsekoch. + +\subsubsection{Predvolená expanzia} +\label{sec:defaultexpansion} +\tolerance=2500 +Ak vyhµadávacia cesta s~najväè¹ou prioritou (pozri \singleuv{Zdroje cesty} +na strane~\pageref{sec:pathsources}) obsahuje \emph{dvojbodku +navy¹e} (t.j.\ zaèiatoènú, koncovú, alebo zdvojenú), \KPS{} vlo¾í na +toto miesto vyhµadávaciu cestu s~druhou najvy¹¹ou prioritou, ktorá +je definovaná. Ak táto vlo¾ená cesta obsahuje dvojbodku navy¹e, to +isté sa stane s~ïal¹ou najvýznamnej¹ou cestou. Keby sme mali +napríklad dané takéto nastavenie premennej prostredia +\tolerance=1500 +\begin{alltt} +>> \Ucom{setenv TEXINPUTS /home/karl:} +\end{alltt} +a hodnotu \code{TEXINPUTS} v~súbore \file{texmf.cnf} +\begin{alltt} + .:\$TEXMF//tex +\end{alltt} +potom koneèná hodnota pou¾itá na vyhµadávanie by bola: +\begin{alltt} + /home/karl:.:\$TEXMF//tex +\end{alltt} +Keï¾e by bolo zbytoèné vklada» predvolenú hodnotu na viac ako jedno +miesto, \KPS{} mení iba nadbytoènú \samp{:}\ a v¹etko ostatné +ponecháva na mieste. Najprv kontroluje zaèiatoènú \samp{:}, potom +koncovú \samp{:} a potom zdvojenú \samp{:}. + +\subsubsection{Expanzia zátvoriek} +U¾itoèná èrta je expanzia zátvoriek, ktorá funguje tak, ¾e +napríklad \verb+v{a,b}w+ sa expanduje na \verb+vaw:vbw+. Vnáranie je +povolené. Toto sa pou¾íva na implementáciu viacnásobných +\TeX{}ovských hierarchií, priradením hodnoty \code{\$TEXMF} +s~pou¾itím zátvoriek. Napríklad v~súbore \file{texmf.cnf} nájdete +nasledujúcu definíciu (pribli¾ne, +v~skutoènosti je tam e¹te viac stromov): +\begin{verbatim} + TEXMF = {$HOMETEXMF,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN} +\end{verbatim} +Keï potom napí¹ete nieèo podobné ako +\begin{verbatim} + TEXINPUTS = .;$TEXMF/tex// +\end{verbatim} +%$ +bude to znamena», ¾e po hµadaní v~aktuálnom adresári sa najprv +prehµadá celý +strom \code{\$HOMETEXMF/tex}, \code{\$TEXMFLOCAL/tex}, +\code{\$TEXMFVAR/tex} a \code{\$TEXMFMAIN/tex} (posledné dva +s~pou¾itím databázových súborov \file{ls-R}). Je to vhodný spôsob ako +spú¹»a» dve paralelné \TeX{} ¹truktúry, jednu nemennú +(napríklad na \CD) a druhú neustále aktualizovanú novými +verziami, akonáhle sú dostupné. Pou¾itím premennej +\code{\$TEXMF} vo v¹etkých definíciách máme istotu, ¾e sa v¾dy ako +prvý prehµadá aktuálny strom. + +\subsubsection{Expanzia podadresárov} +\label{sec:subdirectory.expansion} + +Dva alebo viac za sebou nasledujúcich znakov \samp{/} +v~elemente cesty nasledujúcom za adresárom \var{d} je nahradených v¹etkými +podadresármi \var{d}: najprv podadresármi priamo pod \var{d}, potom +podadresármi pod nimi, atï. Poradie, v~akom sú prehµadávané +podadresáre na ka¾dej úrovni, \emph{nie je ¹pecifikované}. + +Ak po \samp{//} ¹pecifikujete akékoµvek komponenty mena súboru, +pridajú sa iba pod\-adre\-sáre so zodpovedajúcimi komponentami. +Napríklad, \samp{/a//b} sa expanduje do +adresárov \file{/a/1/b}, \file{/a/2/b}, +\file{/a/1/1/b}, atï, ale nie do \file{/a/b/c} alebo \file{/a/1}. + +Viacnásobné kon¹trukcie \samp{//} v~ceste sú mo¾né, ale +pou¾itie \samp{//} na zaèiatku cesty je ignorované. + +\subsubsection{Typy ¹peciálnych znakov a ich význam: zhrnutie} +Nasledujúci zoznam zahàòa %B% význam +zvlá¹tne znaky v~konfiguraèných +súboroch \KPS{}. + +% need a wider space for the item labels here. 3em instead of 2em +\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} +\begin{description} +\item[\CODE{:}]Oddeµovaè v~¹pecifikácii cesty; na zaèiatku alebo + na konci cesty nahrádza predvolenú expanziu cesty.\par +\item[\CODE{;}]Oddeµovaè v~neunixových systémoch (správa sa ako + \samp{:}). +\item[\CODE{\$}]Expanzia premennej. +\item[\CODE{\string~}] Reprezentuje domovský adresár pou¾ívateµa. +\item[\CODE{\char`\{...\char`\}}] Expanzia zátvoriek, napr.\ + z~\verb+a{1,2}b+ sa stane \verb+a1b:a2b+. +\item[\CODE{//}] Expanzia podadresárov. (Mô¾e sa + vyskytnú» kdekoµvek v~ceste, okrem jej zaèiatku). +\item[\CODE{\%}] Zaèiatok komentáru. +\item[\CODE{\bs}] Znak pokraèovania riadku (umo¾òuje viacriadkové vstupy). +\item[\CODE{!!}] Povel na hµadanie súboru \emph{iba} v~databáze, + neprehµadáva disk. +\end{description} + +\subsection{Databázy názvov súborov} +\label{sec:filename.database} + +\KPS{} minimalizuje prístupy na disk pri vyhµadávaní. Predsa v¹ak +pri in¹taláciách s~dostatoèným mno¾stvom adresárov hµadanie súboru +v~ka¾dom mo¾nom adresári mô¾e zabra» prehnane veµa èasu (toto platí +zvlá¹» vtedy, keï musia by» prejdené stovky adresárov s~fontami). +\KPS{} preto pou¾íva externe vytvorený \singleuv{databázový} súbor +nazývaný \file{ls-R}, ktorý mapuje súbory v~adresároch a pomáha tak +vyhnú» sa vyèerpávajúcemu prehµadávaniu disku. + +Skratky mien (\file{aliases}) v~druhom databázovom súbore vám +umo¾òujú da» dodatoèné mená súborom nachádzajúcim sa +v~zozname \file{ls-R}. Toto mô¾e by» u¾itoèné pri prispôsobovaní sa +súborovým konvenciám 8.3 DOSu v~zdrojových súboroch. + +\subsubsection{Súborová databáza} +\label{sec:ls.R} + +Ako bolo vysvetlené hore, meno hlavnej databázy súborov musí +by» \file{ls-R}. Mô¾ete umiestni» jednu do koreòa ka¾dej hierarchie +\TeX u{} vo svojej in¹talácii, ktorú chcete, aby bola prehµadávaná +(predvolená je \code{\$TEXMF}); väè¹inou sa jedná iba o~jednu +hierarchiu. \KPS{} hµadá \file{ls-R} súbory podµa cesty +v~\code{TEXMFDBS}. + +Odporúèaný spôsob ako vytvori» a udr¾iava» \samp{ls-R} je spusti» +skript \code{mktexlsr} zahrnutý v~distribúcii. Je vyvolávaný +rôznymi \samp{mktex...} skriptami. Tento skript v~princípe iba +spú¹»a príkaz +\begin{alltt} +cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R +\end{alltt} +predpokladajúc, ¾e \code{ls} vá¹ho systému vytvára správny výstup +(výstup \GNU \code{ls} je v~poriadku). Aby ste sa ubezpeèili, +¾e databáza bude v¾dy aktuálna, najjednoduch¹ie je pravidelne ju +prebudováva» cez \code{cron}, +tak¾e po zmenách v~in¹talovaných +súboroch \Dash\ napríklad pri in¹talácii alebo aktualizácii balíka +\LaTeX u{} \Dash\ bude súbor \file{ls-R} automaticky aktualizovaný. + +Ak súbor nie je v~databáze nájdený, podµa predvoleného nastavenia +\KPS{} zaène vyhµadáva» na disku. Ak v¹ak urèitý element cesty +zaèína \samp{!!}, bude prehµadávaná \emph{iba} databáza, nikdy nie +disk. + +\subsubsection{kpsewhich: samostatné prehµadávanie cesty} +\label{sec:invoking.kpsewhich} + +Program \texttt{kpsewhich} vykonáva prehµadávanie cesty nezávislé +od ka¾dej aplikácie. Mô¾e by» u¾itoèný ako vyhµadávací \code{find} +program na nájdenie súborov v~hierarchiách \TeX u{} (veµmi sa +vyu¾íva v~distribuovaných \samp{mktex}\dots\ skriptoch). + +\begin{alltt} +>> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} +\end{alltt} +Voµby ¹pecifikované v~\singleuv{\texttt{\var{option}}} mô¾u zaèína» buï +\samp{-} alebo \samp{-{}-} a ka¾dá skratka, ktorá nie je viacznaèná, je +akceptovaná. + +\KPS{} pova¾uje ka¾dý element vstupného riadku, ktorý nie je +argumentom nejakej voµby, za meno súboru, ktorý hµadá, a +vracia prvý súbor, ktorý nájde. Neexistuje voµba umo¾òujúca +vráti» v¹etky súbory s~urèitým menom (na to mô¾ete pou¾i» +nástroj Unixu \samp{find}). + +Najbe¾nej¹ie voµby sú popísané ni¾¹ie. +\begin{description} +\item[\CODE{--dpi=num}]\hfill\break + Nastav rozlí¹enie na \singleuv{\texttt{\var{num}}}; toto má vplyv iba na + \samp{gf} a \samp{pk} vyhµadávanie. \samp{-D} je synonymom, kvôli + kompatibilite s~\cmdname{dvips}. Predvolená hodnota je~600. +\item[\CODE{--format=name}]\hfill\break + Nastav formát na vyhµadávanie na \singleuv{\texttt{\var{name}}}. Podµa + predvoleného nastavenia je formát uhádnutý z~mena súboru. Pre formáty, + ktoré nemajú asociovanú jednoznaènú príponu, ako napríklad podporné + súbory \MP u a konfiguraèné súbory \cmdname{dvips}, musíte + ¹pecifikova» meno ako známe pre \KPS{}, také ako + \texttt{tex} alebo \texttt{enc files}. Zoznam získate spustením + \texttt{kpsewhich -{}-help}. + +\item[\texttt{--mode=\var{string}}]\mbox{}\\ + Nastav meno módu na \singleuv{\texttt{\var{string}}}; toto má vplyv iba na + \samp{gf} a \samp{pk} vyhµadávanie. ®iadna predvolená hodnota: + ka¾dý mód bude nájdený. +\item[\texttt{--must-exist}]\mbox{}\\ + Urob v¹etko preto, aby si na¹iel súbory. Ak je to potrebné, + vrátane hµadania na disku. Normálne je v~záujme efektívnosti + prehµadávaná iba databáza \file{ls-R}. +\item[\texttt{--path=\var{string}}]\mbox{}\\ + Vyhµadávaj podµa cesty \singleuv{\texttt{\var{string}}} (oddeµovaná dvojbodkou + ako zvyèajne) namiesto hádania vyhµadávacej cesty z~mena súboru. + Podporované sú \samp{//} a v¹etky be¾né expanzie. Voµby \samp{--path} + a \samp{--format} sa vzájomne vyluèujú. +\item[\texttt{--progname=\var{name}}]\mbox{}\\ + Nastav meno programu na \singleuv{\texttt{\var{name}}}. Toto nastavenie ovplyvòuje + pou¾itie vyhµadávacej cesty cez nastavenie \singleuv{\texttt{.\var{progname}}} + v~konfiguraèných súboroch. Predvolená hodnota je \samp{kpsewhich}. +\item[\texttt{--show-path=\var{name}}]\mbox{}\\ + Zobrazí cestu pou¾itú na vyhµadávanie súboru s~typom +\singleuv{\texttt{\var{name}}}. + Mô¾e by» pou¾itá buï súborová prípona (\samp{.pk}, \samp{.vf} a pod.) + alebo meno, podobne ako vo voµbe \samp{--format}. +\item[\texttt{--debug=\var{num}}]\mbox{}\\ + Nastaví masku výberu ladiacích mo¾ností na \singleuv{\texttt{\var{num}}}. +\end{description} + +\subsubsection{Príklady pou¾itia} +\label{sec:examples-of.use} + +Pozrime sa na \KPS{} v~akcii. Za podèiarknutým príkazom nasleduje +výsledok vyhµadávania v~nasledujúcich riadkoch. +\begin{alltt} +> \Ucom{kpsewhich article.cls} +/usr/local/texmf-dist/tex/latex/base/article.cls +\end{alltt} +Hµadáme súbor \file{article.cls}. Keï¾e prípona \samp{.cls} je +jednoznaèná, nemusíme ¹pecifikova», ¾e hµadáme súbor typu \singleuv{tex} +(zdrojový súbor \TeX{}). Nájdeme ho v~podadresári +\file{tex/latex/base} pod koreòovým adresárom +\samp{TEXMF-dist}. Podobne, v¹etky nasledujúce súbory budú nájdené bez +problémov vïaka ich jednoznaènej prípone. +\begin{alltt} +> \Ucom{kpsewhich array.sty} + /usr/local/texmf-dist/tex/latex/tools/array.sty +> \Ucom{kpsewhich latin1.def} + /usr/local/texmf-dist/tex/latex/base/latin1.def +> \Ucom{kpsewhich size10.clo} + /usr/local/texmf-dist/tex/latex/base/size10.clo +> \Ucom{kpsewhich small2e.tex} + /usr/local/texmf-dist/tex/latex/base/small2e.tex +> \Ucom{kpsewhich tugboat.bib} + /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib +\end{alltt} + +Mimochodom, posledným súborom je bibliografická databáza \BibTeX u pre +èlánky \textsl{TUGBoatu}. + +\begin{alltt} +> \Ucom{kpsewhich cmr10.pk} +\end{alltt} +Bitmapové súbory fontov typu \file{.pk} sa pou¾ívajú zobrazovacími +programami ako \cmdname{dvips} a \cmdname{xdvi}. V~tomto prípade +je vrátený prázdny výsledok, keï¾e neexistujú ¾iadne vopred +generované Computer Modern \samp{.pk} súbory v~na¹om systéme +(vzhµadom na to, ¾e v~\TL{} implicitne pou¾ívame verzie Type1 ). +\begin{alltt} +> \Ucom{kpsewhich wsuipa10.pk} +\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk +\else /usr/local/texmf-var/fonts/pk/ljfour/public/ +... wsuipa/wsuipa10.600pk +\fi\end{alltt} + +Pre tieto fonty (fonetickú abecedu z~University of Washington) sme museli vygenerova»\ +\samp{.pk} súbory. Keï¾e predvolený mód \MF u v~na¹ej in¹talácii +je \texttt{ljfour} so základným rozlí¹ením 600~dpi (dots per inch), +je vrátená táto in¹tancia. +\begin{alltt} +> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} +\end{alltt} +V~tomto prípade po ¹pecifikovaní, ¾e nás zaujíma rozlí¹enie 300~dpi +(\texttt{-dpi=300}), vidíme, ¾e taký font nie je v~systéme +k~dispozícii. Programy ako \cmdname{dvips} alebo \cmdname{xdvi} +by v~tomto prípade vytvorili po¾adované \texttt{.pk} súbory, pou¾ijúc skript \cmdname{mktexpk}. + +Teraz obrá»me na¹u pozornos» na hlavièkové a konfiguraèné súbory +\cmdname{dvips}. Najprv sa pozrieme na jeden z~be¾ne pou¾ívaných +súborov, v¹eobecný prológový \file{tex.pro} na pod\-poru \TeX u{}, +potom pohµadáme konfiguraèný súbor (\file{config.ps}) a +PostScriptovú mapu fontov \file{psfonts.map} \Dash %B% as of 2004, +mapové a kódové súbory majú svoje vlastné cesty na vyhµadávanie a nové umiestnenie v~stromoch \dirname{texmf}. + +Keï¾e prípona +\samp{.ps} je ne\-jed\-no\-znaèná, musíme pre súbor \texttt{config.ps} +¹pecifikova» explicitne, o ktorý typ sa zaujímame (\optname{dvips +config}). +\begin{alltt} +> \Ucom{kpsewhich tex.pro} + /usr/local/texmf/dvips/base/tex.pro +> \Ucom{kpsewhich --format=`dvips config' config.ps} + /usr/local/texmf/dvips/config/config.ps +> \Ucom{kpsewhich psfonts.map} + /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map +\end{alltt} + +Teraz sa pozrieme na podporné súbory URW Times PostScript. + V~Berryho schéme meno pre +tieto pomenovania fontov je \uv{\texttt{utm}}. Prvý +súbor, ktorý hµadáme, je konfiguraèný súbor, ktorý obsahuje meno +mapového súboru: +\begin{alltt} +> \Ucom{kpsewhich --format="dvips config" config.utm} + /usr/local/texmf-dist/dvips/psnfss/config.utm +\end{alltt} +Obsah tohoto súboru je +\begin{alltt} + p +utm.map +\end{alltt} +èo odkazuje na súbor \file{utm.map}, ktorý ideme ïalej hµada». +\begin{alltt} +> \Ucom{kpsewhich utm.map} + /usr/local/texmf-dist/fonts/map/dvips/times/utm.map +\end{alltt} +Tento mapový súbor definuje mená súborov fontov typu Type1 +PostScript v~kolekcii URW. Jeho obsah vyzerá takto (zobrazili sme +iba jeho èas»): +\begin{alltt} + utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} +\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb +\else /usr/local/texmf-dist/fonts/type1/ +... urw/utm/utmr8a.pfb +\fi\end{alltt} + +Z~týchto príkladov by malo by» zrejmé, ako µahko mô¾ete nájs» +umiestnenie daného súboru. Toto je zvlá¹» dôle¾ité, keï máte +podozrenie, ¾e ste narazili na zlú verziu súboru, +preto¾e \cmdname{kpsewhich} emuluje vyhµadávanie +úplne rovnakým spôsobom ako skutoèný program (\TeX{}, dvips a pod). + + +\subsubsection{Ladiace èinnosti} +\label{sec:debugging} + +Niekedy je potrebné vy¹etri», ako program rozpoznáva referencie na +súbory. Aby toto bolo mo¾né vhodne uskutoèni», \KPS{} ponúka rôzne +stupne ladenia: +\begin{itemize} +\item[\texttt{\ 1}] Volania \texttt{stat} (testy súborov). Pri behu + s~aktuálnou \file{ls-R} databázou by nemal da» takmer ¾iaden výstup. +\item[\texttt{\ 2}] Referencie do ha¹ovacích tabuliek (ako \file{ls-R} + databázy, mapové súbory, konfiguraèné súbory). +\item[\texttt{\ 4}] Operácie otvárania a zatvárania súboru. +\item[\texttt{\ 8}] V¹eobecná informácia o ceste pre typy súborov + hµadaných \KPS. Toto je u¾itoèné pri zis»ovaní, kde bola definovaná + urèitá cesta pre daný súbor. +\item[\texttt{16}] Adresárový zoznam pre ka¾dý element cesty (vz»ahuje + sa iba na vyhµadávanie na disku). +\item[\texttt{32}] Vyhµadávanie súborov. +\item[\texttt{64}] Premenlivé hodnoty. +\end{itemize} +Hodnota \texttt{-1} nastaví v¹etky horeuvedené voµby, v~praxi +pravdepodobne v¾dy pou¾ijete tieto úrovne, ak budete potrebova» +akékoµvek ladenie. + +Podobne s~programom \cmdname{dvips} nastavením kombinácie +ladiacích prepínaèov mô¾ete detailne sledova», odkiaµ sa berú +pou¾ívané súbory. Aktuálny popis parametrov je mo¾né nájs» +v~\path{../texmf/doc/html/dvips/dvips_2.html}. Alternatívne, +keï súbor nie je nájdený, +ladiaca cesta ukazuje, v~ktorých adresároch program daný súbor +hµadal, èo mô¾e naznaèova», v~èom sa asi vyskytol problém. + +V¹eobecne povedané, keï¾e väè¹ina programov volá kni¾nicu \KPS{} +vnútorne, ladiace voµby je mo¾né nastavi» pomocou premennej +prostredia \envname{KPATHSEA\_DEBUG} na potrebnú kombináciu, ako je +to popísané v~horeuvedenom zozname. + +(Poznámka pre pou¾ívateµov Windows: nie je jednoduché +presmerova» v¹etky hlá¹ky v~tomto systéme do súboru. +Na diagnostick\'e úèely mô¾ete doèasne priradi»\hfill\\ +\texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log}). + + +Uva¾ujme ako príklad malý zdrojový súbor +\LaTeX u{}, \file{hello-world.tex}, ktorý obsahuje nasledujúci vstup. +\begin{verbatim} + \documentclass{article} + \begin{document} + Hello World! + \end{document} +\end{verbatim} +Tento malý súbor pou¾íva iba font \file{cmr10}, tak¾e pozrime sa, +ako \cmdname{dvips} pripravuje PostScriptový súbor (chceme pou¾i» +Type1 verziu písiem Computer Modern, preto je nastavená +voµba \texttt{-Pcms}\footnote{Od verzie \TL{}~7 nie +je nutné túto voµbu nastavova», preto¾e Type~1 fonty sú +naèítané implicitne.}. +\begin{alltt} +> \Ucom{dvips -d4100 hello-world -Pcms -o} +\end{alltt} +V~tomto prípade sme skombinovali \cmdname{dvips} ladiacu +triedu~4 (cesty k~fontom) s~expanziou elementu cesty \KPS\ +(pozri Referenèný Manuál +\cmdname{dvips}, \OnCD{texmf/doc/html/dvips/dvips_toc.html}). +%\ifSingleColumn +%We get something +%like the following (we have rearranged the output for easier display): +%\begin{alltt}\small +%\input{examples/ex6.tex} +%\end{alltt} +%\else +Výstup, trochu preusporiadaný, je zobrazený na +obrázku~\ref{fig:dvipsdbga}. + +\begin{figure*}[tp] +\centering +\input{examples/ex6a.tex} +\caption{Hµadanie konfiguraèných súborov}\label{fig:dvipsdbga} + +\bigskip + +\input{examples/ex6b.tex} +\caption{Hµadanie \singleuv{prolog} súboru}\label{fig:dvipsdbgb} + +\bigskip + +\input{examples/ex6c.tex} +\caption{Hµadanie súboru fontu}\label{fig:dvipsdbgc} +\end{figure*} + + +%\input{examples/ex6skfromtl6.tex} % TODO: Janka -- treba aktualizovat +% z ../examples/ex6*.tex + +\cmdname{dvips} zaène lokáciou svojich pracovných súborov. Najprv je +nájdený \file{texmf.cnf}, ktorý obsahuje definície vyhµadávacích +ciest ostatných súborov, potom databáza súborov \file{ls-R} (na +optimalizáciu vyhµadávania súborov) a skratky mien súborov +(\file{aliases}), èo robí mo¾ným deklarova» viacero mien (napr.\ +krátke meno typu \singleuv{8.3} ako v~\acro{DOS}e a dlh¹iu prirodzenej¹iu +verziu) pre ten istý súbor. Potom \cmdname{dvips} pokraèuje +v~hµadaní v¹eobecného konfiguraèného súboru \file{config.ps} skôr, +ako zaène hµada» súbor nastavení \file{.dvipsrc} (ktorý, v~tomto +prípade, \emph{nie je nájdený}). Nakoniec, \cmdname{dvips} nájde +konfiguraèný súbor pre font Computer Modern PostScript, +\file{config.cms} (toto bolo iniciované voµbou\texttt{-Pcms} +v~príkaze \cmdname{dvips}). Tento súbor obsahuje zoznam \uv{mapových} +súborov, ktoré definujú vz»ah medzi menami fontov v~\TeX u, +PostScripte a systéme súborov. +\begin{alltt} +> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} + p +ams.map + p +cms.map + p +cmbkm.map + p +amsbkm.map +\end{alltt} +\cmdname{dvips} preto pokraèuje v~hµadaní v¹etkých týchto súborov plus +v¹eobecného mapového súboru \file{psfonts.map}, ktorý sa naèíta +v¾dy (obsahuje deklarácie be¾ne pou¾ívaných PostScriptových fontov; +pozri poslednú èas» sekcie~\ref{sec:examples-of.use}, kde sa nachádza +viac detailov o narábaní s~mapovými súbormi PostScriptu). + +V~tomto bode sa \cmdname{dvips} identifikuje +pou¾ívateµovi\,\ldots +\begin{alltt}\ifSingleColumn +This is dvips 5.78 Copyright 1998 Radical Eye Software + (www.radicaleye.com) +\else\small{}This is dvips 5.78 Copyright 1998 Radical Eye ... +\fi\end{alltt}% decided to accept slight overrun in tub case + +\ifSingleColumn +\noindent\ldots potom pokraèuje v~hµadaní prológového súboru +\file{texc.pro}: + +\begin{alltt}\small +kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro +\end{alltt} +\else +potom pokraèuje v~hµadaní prológového súboru +\file{texc.pro} (pozri obrázok~\ref{fig:dvipsdbgb}). +\fi +Po nájdení tohoto súboru, \cmdname{dvips} vypí¹e na výstup dátum a +èas a informuje nás, ¾e vygeneruje súbor \file{hello-world.ps}, ¾e +potrebuje súbor s~fontom \file{cmr10}, ktorý bude deklarovaný ako +\uv{rezidentný}: +\begin{alltt}\small +TeX output 1998.02.26:1204' -> hello-world.ps +Defining font () cmr10 at 10.0pt +Font cmr10 is resident. +\end{alltt} +Teraz sa rozbehne hµadanie súboru \file{cmr10.tfm}, ktorý je +nájdený, potom je referencovaných e¹te niekoµko prológových súborov +(nezobrazené) a nakoniec je nájdená in¹tancia fontu +Type1, \file{cmr10.pfb}, ktorá je pridaná do výstupného súboru +(pozri posledný riadok). +\begin{alltt}\small +kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, + path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: + /var/tex/fonts/tfm//). +kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm +kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, + ... + +kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb +[1] +\end{alltt} + +\subsection{Mo¾nosti nastavenia za behu programu} +Ïal¹ou z~pekných èàt distribúcie \Webc{} je mo¾nos» kontroly +mno¾stva pamä»ových parametrov (najmä veµkosti polí) za behu +prostredníctvom súboru \file{texmf.cnf}, +ktorý èíta kni¾nica \KPS{}. Nastavenia v¹etkých parametrov mô¾ete +nájs» v~èasti~3 tohto súboru. Najdôle¾itej¹ie riadiace +premenné (èísla riadkov sa vz»ahujú na súbor \file{texmf.cnf}): + +\begin{description} +\item[\texttt{main\_memory}] + Celkový poèet dostupných slov v~pamäti pre \TeX{}, \MF{} a \MP. + Musíte vytvori» nový formátový súbor pre ka¾dé odli¹né nastavenie. + Napríklad mô¾ete vygenerova» \uv{obrovskú} verziu \TeX u{} + a zavola» súbor s~formátom \texttt{hugetex.fmt}. S~po\-u¾itím + ¹tandardnej ¹pecifikácie mena programu pou¾ívaného kni¾nicou + \KPS{}, konkrétna hodnota premennej \texttt{main\_memory} sa naèíta zo + súboru \file{texmf.cnf}. + %B% (porovnaj v¹eobecnú hodnotu a \uv{obrovskú} hodnotu, ktorá sa in¹tancuje cez \texttt{hugetex}, atï.). +\item[\texttt{extra\_mem\_bot}] + Dodatoèný priestor pre \uv{veµké} dátové ¹truktúry \TeX u{}: + \uv{boxy}, \uv{glue}, \uv{break\-point(y)} a podobne. + Je to u¾itoèné hlavne ak pou¾ívate \PiCTeX{}. +%%PS (riadok 300). +\item[\texttt{font\_mem\_size}] + Poèet dostupných slov pre informáciu o fontoch v~\TeX u. Toto je + viac-menej celková veµkos» v¹etkých preèítaných \acro{TFM} súborov. +\item[\texttt{hash\_extra}] + Dodatoèný priestor pre ha¹ovaciu tabuµku mien riadiacej sekvencie. + Len $\approx$10\,000 riadiacich sekvencií mô¾e by» ulo¾ených v~hlavnej + ha¹ovacej tabuµke; ak máte veµkú knihu s~mnohými krí¾ovými odkazmi, + toto nemusí staèi». Implicitná hodnota \texttt{hash\_extra} je \texttt{50000}. + %B% Vidíte, ¾e obidve volania programov \cmdname{hugetex} a \cmdname{pdftex} po¾adujú + %B% dodatoèných 15\,000 riadiacich sekvencií (preddefinovaná hodnota + %B% hash\_extra je nula). +\end{description} + +Samozrejme, tento prvok nemô¾e nahradi» naozajstné dynamické polia +a alokácie pamäte, ale keï¾e tieto sa veµmi »a¾ko implementujú +v~súèasnej verzii \TeX u, tieto parametre poèas behu programu +poskytujú praktický kompromis, ktorý dovoµuje aspoò nejakú +flexi\-bilitu. +\end{otherlanguage} + +\begin{comment} +\section{Pøeklad pro novou unixovou platformu} + +Pokud pou¾íváte platformu, pro kterou neposkytujeme binárky, nezbude vám +nic jiného, ne¾ si je vytvoøit ze zdrojákù sami. +Není to tak tì¾ké, jak se traduje èi zdá. V¹e, co je tøeba, najdete +v~adresáøi \texttt{source} distribuce. + +\subsection{Pøedpoklady úspìchu} + +Budete potøebovat alespoò 100~Mebibytù diskového prostoru na kompilaci +celého \TeX{}u a podpùrných programù. Budete také potøebovat kompilátor +\acro{ANSI}~C, program \cmdname{make}, lexikální analyzátor a generátor +pøekladaèe. Doporuèujeme \GNU{} verze tìchto programù +(\cmdname{gcc}, \GNU \cmdname{make}, \cmdname{m4}, \cmdname{flex}, +\cmdname{bison}). Mo¾ná uspìjete i s~jinými verzemi kompilátoru~C, +programu \cmdname{make} a dal¹ích programù, ale budete potøebovat +dobrou znalost kompilace unixových programù pro øe¹ení kolizí. + +Také pøíkaz \texttt{uname} musí vracet rozumné hodnoty. + + +\subsection{Konfigurace} + +Pro zaèátek proveïte normální instalaci \TL{} na vá¹ disk (viz +oddíl~\ref{sec:install.disk} na +stranì~\pageref{sec:install.disk}). Mù¾ete pøeskoèit instalaci +v¹ech pøedkompilovaných binárek. + +Potom rozbalte zdroje z~komprimovaného \texttt{tar} archívu z~adresáøe +\dirname{source} na svùj disk a pøejdìte do adresáøe, kam jste zdroje +rozbalili. + +Potom spus»te program \cmdname{configure} napøíklad takto: +\begin{alltt} +> \Ucom{sh configure -prefix=/usr/local/TeX} +\end{alltt} + +Adresáø udaný pøepínaèem \optname{-prefix} je ten, kam jste instalovali +pomocný texmf strom; struktura adresáøù bude jak je popsáno ní¾e (pøièem¾ +\$TEXDIR je adresáø, který jste zvolili): + +\noindent +\begin{tabularx}{\textwidth}{@{}>{\ttfamily}lX@{}} + \dirname{$TEXDIR/share/texmf} & hlavní strom s~fonty, makry, atp.\\ + \dirname{$TEXDIR/man} & unixové manuálové stránky\\ + \dirname{$TEXDIR/info} & \GNU style Info manuály\\ + \dirname{$TEXDIR/bin/$PLATFORM} & binárky +\end{tabularx} +%$ + +Pokud chcete zru¹it extra úroveò adresáøù \dirname{$PLATFORM} pro ka¾dou +platformu, t.j.\ ulo¾it binárky do adresáøe \dirname{$TEXDIR/bin}, +specifikujte volbu \verb|--disable-multiplatform| pro \cmdname{configure}. + +Podívejte se na výstup pøíkazu \verb|./configure --help| pro popis +dal¹ích pøepínaèù, které mù¾ete chtít pou¾ít. Napøíklad mù¾ete chtít +vynechat pøeklad \OMEGA{}y èi \eTeX{}u. + + +\subsection{Spu¹tìní \cmdname{make}} + +Ovìøte, zda promìnná prostøedí nebo volba \texttt{noclobber} není nastavena. +Potom spus»te hlavní \cmdname{make} takto: +\begin{alltt} +> \Ucom{make world} +\end{alltt} +a dejte si chvíli oddechu\ldots + +Pøípadnì si mù¾ete zaznamenat v¹echen výstup takto: +\begin{alltt} +> \Ucom{sh -c \string"make world >world.log 2>\&1\string" \&} +\end{alltt} + +Pøedtím ne¾ uvìøíte, ¾e v¹echno je v~poøádku, zkontrolujte +logovací soubor na chyby: \GNU \cmdname{make} v¾dy pou¾ívá øetìzec +\samp{***}, kdykoliv pøíkaz sel¾e. Také zkontrolujte, zda v¹echny programy +byly opravdu pøelo¾eny: + +\begin{alltt} +> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} +> \Ucom{ls | wc} +\end{alltt} +Výsledkem by mìlo být pøes 200 programù (mù¾ete zkontrolovat pøesný +poèet s~adresáøi \dirname{bin} na~distribuèním médiu). + +Pro závìreèný \texttt{make install} budete potøebovat rootovské +oprávnìní, tak¾e mù¾ete rozdìlit \samp{make world} na dvì èásti: +\begin{alltt} +> \Ucom{make all} +> \Ucom{su} +> \Ucom{make install strip} +\end{alltt} + +Poté, co instalujete v¹echny binárky, mìli byste provést +normální postinstalaèní proceduru, jak je popsána +v~oddíle~\ref{sec:postinstall} +na stranì~\pageref{sec:postinstall}. + +Kdy¾ budete chtít zpøístupnit svoje binárky ostatním, +prosíme kontaktujte nás. +R\'adi je umístíme na webov\'e stránky \TL. +\end{comment} + +\section{Podìkování} + +\TL{} je výsledkem spoleèného úsilí témìø v¹ech skupin u¾ivatelù \TeX u. +Toto vydání editoval \TL{} Karl Berry. +Seznam ostatních hlavních pøisp\v{e}vatelù, minulých i souèasných, následuje. Dìkujeme: + +%B% Toto vydání \TL{} je editováno Sebastianem Rahtzem, pøièem¾ hlavní +%B% pøispìvatel byl Fabrice Popineau, který tvrdì pracoval na podpoøe +%B% Windows (zvlá¹tì na setupu!) a pøispìl mnoha rùznými zpùsoby a nápady, +%B% radami a kódem. Staszek Wawrykiewicz byl hlavní testér distribuce +%B% a koordinoval pøíspìvky z~Polska. + +%B% Kaja Christiansen provádìla neúnavnì opakované +%B% rekompilace na rùzných unixových platformách. Vladimir Volovich odvedl +%B% vynikající práci na vyèi¹tìní zdrojových textù a provedl mnohá +%B% vylep¹ení, zatímco Gerben Wierda dìlal ve¹kerou práci pro \MacOSX. + +\begin{itemize*} +\item Anglickému, nìmeckému, holandskému a polskému sdru¾ení +u¾ivatelù \TeX{}u (\acro{TUG}, \acro{DANTE} e.V., +\acro{NTG} resp. \acro{GUST}), kte\v r\'i spoleènì zajistily +nezbytnou technickou a administrativní infrastrukturu. +Pøipojte se, prosím, k~\TeX ovskému sdru¾ení ve va¹í blizkosti! +(Viz \url{http://tug.org/usergroups.html}.) + +\item Týmu \acro{CTAN}u, nejpozoruhodnìj¹ím Robinu Fairbairnsovi, Jimu Hef{}feronovi +a Raineru Sch\"opfovi, který distribuuje obrazy \TL{} a +poskytuje spoleènou infrastrukturu pro aktualizaci balíkù, +na kterých je \TL{} závislý. + +\item Peteru Breitenlohnerovi a \eTeX\ týmu, kteøí poskytují +stabilní základ budoucnosti \TeX u, a výslovnì Peteru za hvìzdnou pomoc s~pou¾íváním osobních nástrojù GNU v~celém \TL.. + +%B% \item Karlu Berrymu, který poskytl pùvodní distribuci \Webc{}, a +%B% pokraèoval v~poskytování cenných rad, povzbuzení a pomocí. + +%B% \item Mimi Burbankové, která zajistila na Florida State University +%B% School of Computational Science and Information Technology pøístup +%B% k~øadì rùzných poèítaèù rùzných platforem pro pøeklad +%B% \TeX{}ových binárek a distribuce testovala, kdykoliv to bylo potøeba. + +\item Thomasi Esserovi, za pøekrásný balík \teTeX{}, bez nìho¾ by \TL{} +nikdy neexistovala. + +\item Michelu Goossensovi, který je spoluautorem pùvodní dokumentace. + +\item Eitanu Gurarimu, jeho¾ \TeX{}4ht bylo pou¾ito pro +\HTML{} verzi této dokumentace a který obratem +pracoval neúnavnì na jeho roz¹íøeních. + +\item \Thanh ovi, Martinu Schr\"oderovi a pdf\TeX\ týmu (\url{http://pdftex.org}) +za pokraèující roz¹iøování mo¾ností \TeX u. + +\item Hansi Hagenovi, za mnohá testování a pøípravu jeho formátu \ConTeXt\ +(\url{http://pragma-ade.com}) pracujícího uvnitø systému \TL. + +\item Hartmutu Henkelovi, za významný pøíspìvek k~vývoji +pdf\TeX u, Lua\TeX u a více. + +\item Taco Hoekwaterovi, za úsilí pøi obnovení vývoje \MP u i +samotného (Lua)\TeX{}u (\url{http://luatex.org}) a za zaèlenìní \ConTeXt{}u do systému \TL. + +\item Paw{\l}u Jackowsk\'emu, za windowsový instalátor \cmdname{tlpm}, +a Tomaszi {\L}uczakovi, za \cmdname{tlpmgui}, pou¾ívaný v~pøedchozích vydáních. + +\item Akirovi Kakuto, za poskytnutí windowsovských binárek +z~jeho distribuce \acro{W32TEX} pro japonský \TeX{} +(\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}) a za mno¾ství dal¹ích pøíspìvkù. + +\item Jonathanu Kew a \acro{SIL}, za významný +nový vývoj \XeTeX{}u a za èas a trápení pøi jeho integraci do \TL{}, právì tak jako za výchozí verzi instalaèního programu Mac\TeX. + +\item Dicku Kochovi, za údr¾bu Mac\TeX{}u (\url{http://tug.org/mactex}) +ve velmi blízkém tandemu s~\TL{}, a za jeho skvìlé veselí pøitom. % for his great good cheer in doing so. + +\item Reinhardovi Kotuchovi za dùle¾itý pøíspìvek k~infrastruktuøe a instalaènímu programu \TL{} 2008, rovnì¾ za úsilí pøi výzkumu Windows, za skript \texttt{getnonfreefonts} a dal¹í. + +\item Siepu Kroonenbergovi, rovnì¾ also za dùle¾itý pøíspìvek k~infrastruktuøe a instalaènímu programu \TL{} 2008, zvlá¹tì pod Windows a za mno¾ství práce pøi aktualizaci této pøíruèky, popisující nové vlastnosti. + +\item Petru Ol¹ákovi, který koordinoval a kontroloval velmi peèlivì +èeskou a slovenskou podporu na \TeXLive. + +\item Toshio Oshima za jeho windowsový prohlí¾eè \cmdname{dviout}. + +\item Manueli P\'egouri\'e-Gonnardovi, za pomoc pøi aktualizaci balíkù, +vylep¹ení dokumentace a rozvoj dokumentu \cmdname{tldoc}. + +\item Fabrice Popineau, za pùvodní podporu Windows na \TL{} a za francouzskou dokumentaci. + +\item Norbertovi Preiningovi, pøednímu architektovi infrastruktury a instalaèního programu \TL{} 2008 a také za koordinaci Debian verze \TL{} (spoleènì s~Frankem K\"usterem), +za mnohé prùbì¾né návrhy na zlep¹ení. + +\item Sebastian Rahtz, za pùvodní vytvoøení systému \TL{} a za jeho údr¾bu po mnoho let. + +\item Vladimir Volovich, za významnou pomoc s~portováním % with porting +a jinými problémy údr¾by, obzvlá¹tì za to, ¾e udìlal realizovatelným zahrnutí \cmdname{xindy}. + +\item Staszku Wawrykiewiczovi, hlavnímu testérovi v¹eho na \TL{} a +koordinátorovi mnoha dùle¾itých polských pøíspìvkù: fontù, windowsové instalace a dal¹ích. + +\item Olafu Weberovi, pro jeho peèlivou údr¾bu \Webc. + +\item Gerbenu Wierdovi, za vytvoøení a údr¾bu podpory \MacOSX\ a +za mnohou integraci a testování. + +\item Grahamu Williamsovi, na jeho¾ práci na katalogu \TeX{}ovských balíkù závisíme. + +\end{itemize*} + +Tvùrci binárek: +Tigran Aivazian (\pkgname{x86\_64-linux}), +Tim Arnold (\pkgname{hppa-hpux}), +Randy Au (\pkgname{amd64-freebsd}), +Edd Barrett (\pkgname{i386-openbsd}), +Karl Berry (\pkgname{i386-linux}), +Akira Kakuto (\pkgname{win32}), +Dick Koch (\pkgname{universal-darwin}), +Manfred Lotz (\pkgname{i386-freebsd}), +Norbert Preining (\pkgname{alpha-linux}), +Arthur Reutenauer (\pkgname{sparc-linux}), +Thomas Schmitz (\pkgname{powerpc-linux}), +Apostolos Syropoulos (\pkgname{i386-solaris}), +Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-solaris}), +Olaf Weber (\pkgname{mips-irix}). +Pro informaci o procesu budování \TL{}, viz +\url{http://tug.org/texlive/build.html}. + +Obnova dokumentace a pøekladù: +Karl Berry (anglický), +Daniel Flipo (francouzský), +Klaus H\"oppner (nìmecký), +Petr Sojka \& Ján Bu¹a (èesko\slash slovenský),% +\footnote{Ke korektuøe èeského a slovenského pøekladu pøispìli +v~letech 2003--2007 kromì autorù Jaromír Kuben, Milan Matlák, Tomá¹ Ob¹ívaè, +Tomá¹ Pole¹ovský, Libor ©karvada, Zdenìk Wagner a dal¹í. +Libor \v Skarvada korigoval i leto\v sn\'i verzi.} +Boris Veytsman (ruský), +Staszek Wawrykiewicz (polský). +Webovská stránka dokumentace \TL{} je \url{http://tug.org/texlive/doc.html}. +%B% Dále Gerhard Wilhelms, Volker Schaa, Fabrice Popineau, Janka +%B% Chlebíková, Petra Sojková, Staszek Wawrykiewicz, +%B% Erik Frambach a Ulrik Vieth laskavì pøelo¾ili v~rùzných +%B% obdobích dokumentaci do svých mateøských jazykù a poskytli +%B% vítanou zpìtnou reakci. + +Samozøejmì, nejdùle¾itej¹í podìkování patøí Donaldu Knuthovi, +pøedev¹ím za vymy¹lení \TeX u a také za to, ¾e ho vìnoval svìtu. + +\section{Historie vydání} +\label{sec:history} + +\subsection{Minulost} + +Diskuse zaèala koncem roku 1993, kdy holandská skupina u¾ivatelù \TeX{}u +NTG zaèala práci na \CD{} 4All\TeX{} pro u¾ivatele \acro{MS-DOS}u, doufajíc, +¾e doba nazrála pro vydání jednoho \CD{} pro v¹echny +systémy. Byl to na svou dobu pøíli¹ ambiciózní cíl, ale +nenastartoval jen velmi úspì¹né 4All\TeX{} \CD{}, ale také +pracovní skupinu \acro{TUG}u o \emph{\TeX{} Directory Structure} +(\url{http://tug.org/tds}), která specifikovala, +jak vytvoøit konzistentní a spravovatelnou +kolekci \TeX{}ových souborù. Kompletní draft \TDS{} byl publikován +v~prosincovém èísle èasopisu \textsl{TUGboat} v~roce 1995 a +hned ze zaèátku bylo jasné, ¾e jedním z~¾ádaných produktù bude +vzorová struktura \CD{}. Distribuce, kterou nyní máte, je pøímým +výstupem práce této pracovní skupiny. Evidentní úspìch \CD{} 4All\TeX{} +ukázal, ¾e i unixoví u¾ivatelé by tou¾ili po podobnì jednoduchém +systému, a to je také jedno z~hlavních aktiv~\TeXLive. + +Nejprve jsme vytvoøili unixové \TDS{} \CD{} na podzim +1995 a rychle identifikovali \teTeX{} Thomase Essera +jako ideální systém, jeliko¾ ji¾ mìl multi\-platformní +podporu a byl koncipován s~perspektivou +p\v renositelnosti. Thomas souhlasil s~pomocí a seriózní práce zapoèala +zaèátkem roku 1996. První vydání se uskuteènilo +v~kvìtnu 1996. Zaèátkem 1997 Karl Berry dokonèil nové hlavní +vydání \Webc, které obsahovalo témìø v¹echny vlastnosti, +které Thomas Esser pøidal do \teTeX{}u, a tak jsme se rozhodli +druhé vydání \CD{} postavit na standardním +\Webc, s~pøidáním skriptu \texttt{texconfig} z~\teTeX{}u. +Tøetí vydání \CD{} bylo zalo¾eno na dal¹í revizi +\Webc, 7.2, provedené Olafem Weberem; a jeliko¾ zároveò +byla hotova nová verze \teTeX{}u, \TL{} obsahoval +témìø v¹echna její vylep¹ení. +Podobnì ètvrté vydání pou¾ívalo novou +verzi \teTeX{}u a nové vydání \Webc{} (7.3). +\TL{} nyní obsahuje i kompletní systém pro Windows. + +Pro páté vydání (bøezen 2000) bylo mnoho èástí \CD{} revidováno +a zkontrolováno a byly aktualizovány stovky +balíkù. Detaily o balících byly ulo¾eny v~souborech \acro{XML}. +Ale hlavní zmìnou pro \TeX\ Live~5 bylo vynìtí +softwaru, na kterém byla jakákoliv omezení na ¹íøení +(non-free software). V¹e ulo¾ené na \TL{} je nyní +sluèitelné s~tzv.\ `Debian Free Software Guide\-lines' +(\url{http://www.debian.org/intro/free}); udìlali jsme v¹e mo¾né, +abychom zkontrolovali licenèní podmínky v¹ech balíkù, +ale budeme vdìèni za upozornìní na jakékoli chyby. + +©esté vydání (èervenec 2001) mìlo aktualizovaného materiálu +je¹tì více. Hlavní zmìnou byl nový instalaèní pøístup: +u¾ivatel mù¾e volit instalaèní kolekce. +Byly kompletnì reorganizovány jazykové kolekce, +tak¾e jejich výbìrem se instalují +nejen makra, fonty, ale je také pøipraven odpovídající +soubor \texttt{language.dat}. + +Sedmé vydání v~roce 2002 mìlo podstatné roz¹íøení v~pøidání +podpory \MacOSX{}, kromì mno¾ství aktualizací balíkù a programù. +Dùle¾itým cílem byla opìtná integrace s~\teTeX{}em +a korekce odchylek z~pátého a ¹estého vydání. + +\subsubsection{2003} + +V~roce 2003 se neustálou smr¹tí oprav a roz¹íøení stalo to, ¾e +velikost \TL{} ji¾ neumo¾nila jeho smìstnání +na jedno \CD{}, a tak do¹lo k~rozdìlení na tøi rùzné distribuce +(viz oddíl~\ref{sec:tl-coll.dists} na +stranì~\pageref{sec:tl-coll.dists}). Navíc: + +\begin{itemize*} +\item Na ¾ádost \LaTeX{} týmu jsme zmìnili standardní pøíkazy + \cmdname{latex} a \cmdname{pdflatex} tak, ¾e nyní pou¾ívají + \eTeX{} (viz strana~\pageref{text:etex}). +\item Byly pøidány a jsou nyní doporuèovány k~pou¾ívání + nové fonty Latin Modern. +\item Byla zru¹ena podpora OS Alpha \acro{OSF} + (podpora \acro{HPUX} byla zru¹ena ji¾ døíve), jeliko¾ se + nena¹el nikdo, kdo by na tìchto platformách zkompiloval nové binárky. +\item Instalaèní program Windows byl zmìnìn podstatným zpùsobem; poprvé + bylo integrováno u¾ivatelské prostøedí zalo¾ené na XEmacsu. +\item Dùle¾ité pomocné programy pro Windows + (Perl, \GS{}, Image\-Magick, Ispell) jsou nyní instalovány + do instalaèního adresáøe \TL{}. +\item Mapovací soubory jmen fontù pro \cmdname{dvips}, \cmdname{dvipdfm} + a \cmdname{pdftex} jsou nyní generovány novým programem + \cmdname{updmap} a instalovány do \dirname{texmf/fonts/map}. +%+\item \TeX{}, \MF{}, and \MP{} now output 8-bit input +%+ characters as themselves in output (e.g., \verb|\write|) files, +%+ log files, and the terminal, i.e., \emph{not} translated using the +%+ \verb|^^| notation. In \TL{}~7, this translation was +%+ dependent on the system locale settings; now, locale settings do +%+ not influence the \TeX{} programs' behavior. If for some reason +%+ you need the \verb|^^| output, rename the file +%+ \verb|texmf/web2c/cp8bit.tcx|. (Future releases will have cleaner +%+ ways to control this.) +\item \TeX{}, \MF{} a \MP{} nyní dávají na výstup %B% 8-bitové + vìt¹inu vstupních + znakù (32 a vý¹) bez konverze (napøíklad do souborù + zapisovaných pomocí \verb|\write|, + souborù log, na terminál), a tedy \emph{nejsou pøekládány} do + sedmibitové \verb|^^| notace. V~\TL{}~7 bylo toto mapování + závislé na nastavení systémových locale; nyní ji¾ nastavení locale + \emph{neovlivní} chování \TeX{}u. Pokud z~nìjakých dùvodù + potøebujete výstup s~\verb|^^|, pøejmenujte soubor + \verb|texmf/web2c/cp8bit.tcx|. Pøí¹tí verze bude mít èist¹í øe¹ení. +\item Tato dokumentace byla podstatným zpùsobem pøepracována. +\item Koneènì, jeliko¾ èísla verzí \TL{} ji¾ pøíli¹ narostla, + verze je nyní identifikována rokem vydání: \TL{} 2004. +\end{itemize*} + +\subsubsection{2004} + +Rok 2004 pøinesl mnoho zmìn: + +\begin{itemize} + +\item Pokud máte lokálnì instalovány fonty, které +vyu¾ívají své vlastní podp\r urn\'e soubory +\filename{.map} nebo (mnohem ménì pravdìpodobnì) \filename{.enc}, +mo¾ná budete nuceni tyto soubory pøesunout. + +Soubory \filename{.map} jsou nyní vyhledávány jen v~podaresáøích +\dirname{fonts/map} (v~ka¾dém stromì \filename{texmf}), podél cesty +\envname{TEXFONTMAPS}. Podobnì, soubory \filename{.enc} jsou hledány jen v~podadresáøích \dirname{fonts/enc}, podél cesty \envname{ENCFONTS}. \cmdname{updmap} se pokusí vypsat varování o~problematických souborech. +% +O~metodách zpracování té které informace, prosíme viz +\url{http://tug.org/texlive/mapenc.html}. + +\item \TKCS\ byla roz¹íøena pøidáním instalovatelného \CD, +zalo¾eného na \MIKTEX u, pro ty, kteøí dávají pøednost +této implementaci pøed Web2C. +%Také lo\v{n}sk\'e demo \CD{} bylo nahrazeno instalovatelným \CD{} pro Windows. +Viz oddíl~\ref{sec:overview.tl} (stránka~\pageref{sec:overview.tl}). + +\item Uvnitø \TL byl velký strom \dirname{texmf} pøede¹lých vydání nahrazen tøemi: \dirname{texmf}, +\dirname{texmf-dist} a \dirname{texmf-doc}. Viz oddíl~\ref{sec:tld} (stránka~\pageref{sec:tld}) a soubory \filename{README} pro ka¾dý z~nich. + +\item V¹echny vstupní soubory týkajíci se \TeX u jsou teï soustøedìny v~podadresáøi \dirname{tex} stromù \dirname{texmf*} a nemají oddìlené sourozenecké adresáøe \dirname{tex}, \dirname{etex}, +\dirname{pdftex}, \dirname{pdfetex} atd. Viz +\CDref{texmf.doc/doc/english/tds/tds.html\#Extensions} +{\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}. + +\item Pomocn\'e dávky (nemìly by být volány u¾ivateli) jsou teï +umístìny v~novém adresáøi \dirname{scripts} stromù \dirname{texmf*} a jsou vyhledávány prostøednictvím \verb|kpsewhich -format=texmfscripts|. Kdy¾ tedy máte programy volající tyto dávky, budou muset být nastaveny. Viz +\CDref{texmf.doc/doc/english/tds/tds.html\#Scripts} +{\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}. + +\item Témìø v¹echny formáty umo¾òují vìt¹inu znakù tisknout +bez konverze pomocí p\v{r}ekladov\'eho souboru +\filename{cp227.tcx}, místo jejich konverze pomocí +\verb|^^| notace. Konkrétnì, znaky na pozicích 32--256, +plus \uv{tab}, \uv{vertikální tab} a \uv{form feed} jsou pova¾ovány +za tisknutelné a nejsou konvertovány. Výjimky tvoøí plain \TeX\ +(jen 32--127 jsou tisknutelné), \ConTeXt\ (0--255 tisknutelné) a formáty +systému \OMEGA. Toto implicitní chování je témìø stejn\'e, jak na +\TL\,2003, ale je implementováno èistìji, s~více mo¾nostmi pøizpùsobení. +Viz \CDref{texmf/doc/web2c/web2c.html\#TCX-files} +{\texttt{texmf/doc/web2c/web2c.html\#TCX-files}}. +(Mimochodem, se vstupem Unicode, mù¾e \TeX\ na výstupu vypsat posloupnosti +èásteèných znakù pøi výpisu chybových kontextù, proto¾e je bytovì +orientován.) + +\item \textsf{pdfetex} je teï implicitní stroj pro v¹echny formáty +kromì samotného (plain) \textsf{tex}u. (Ten jistì¾e generuje \acro{DVI}, + kdy¾ je spu¹tìn jako \textsf{latex} atd.) To znamená, kromì jiných + vìcí, ¾e mikrotypografické roz\v{s}\'\i\v{r}en\'\i\ +\textsf{pdftex}u jsou dostupné + v~\LaTeX u, \ConTeXt u atd., stejn\v{e} jako roz\v{s}\'\i\v{r}en\'\i\ +\eTeX u (\OnCD{texmf-dist/doc/etex/base/}). + +To také znamená, ¾e u¾ití balíku \pkgname{ifpdf} (pracuje s~plainem +i \LaTeX em) nebo ekvivalentního kódu je \emph{dùle¾itej¹í +ne¾ kdykoliv pøedtím}, proto¾e jednoduché testování, zda +je \cs{pdfoutput} nebo nìjaký jiný primitiv definován, +není spolehlivý zpùsob urèení, zda je generován \acro{PDF} +výstup. Tento zpìtný krok jsme udìlali co nejvíc kompatibilní +letos, ale v~p\v{r}\'\i\v{s}t\'\i m roce \cs{pdfoutput} mù¾e +být definován, dokonce i kdy¾ se zapisuje do \acro{DVI}. + +\item pdf\TeX\ (\url{http://pdftex.org/}) má mno¾ství nových vlastností: + + \begin{itemize*} + + \item \cs{pdfmapfile} a \cs{pdfmapline} poskytují podporu mapování fontù uvnitø dokumentu. + + \item Mikrotypografické roz¹íøení fontu mù¾e být pou¾ito jednodu¹eji.\\ + \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} + + \item V¹echny parametry, které byly pøedtím nastavovány ve + zvlá¹tním konfiguraèním souboru \filename{pdftex.cfg}, musí + teï být nastaveny pomocí primitivù, obyèejnì + v~\filename{pdftexconfig.tex}; \filename{pdftex.cfg} není + dále podporován. V¹echny existující \filename{.fmt} soubory + musí být znovu vytvoøeny pøi zmìnì souboru \filename{pdftexconfig.tex}. + + \item Dal¹í informace viz manuál pdf\TeX u: \OnCD{texmf/doc/pdftex/manual}. + + \end{itemize*} + +\item Primitiv \cs{input} v~\cmdname{tex}u (a \cmdname{mf} a +\cmdname{mpost}) teï akceptuje dvojité uvozovky se jm\'eny obsahujícími +mezery a s~jin\'ymi zvlá¹tními znaky. Typické pøíklady: +\begin{verbatim} +\input "filename with spaces" % plain +\input{"filename with spaces"} % latex +\end{verbatim} +Pro dal¹í informace viz manuál Web2C: \OnCD{texmf/doc/web2c}. + +\item Podpora enc\TeX u je nyní zahrnuta uvnitø Web2C, +v~dùsledku toho ve v¹ech \TeX ových programech, pou¾itím +volby \optname{-enc} \Dash \emph{jen v~pøípadì, ¾e formáty +jsou vytvoøeny}. enc\TeX\ podporuje obecné pøekódování +vstupu a výstupu, èím\v{z} umo¾òuje plnou podporu kódování +Unicode (v~\acro{UTF}-8). Viz \OnCD{texmf-dist/doc/generic/enctex/} a +\url{http://www.olsak.net/enctex.html}. + +\item Aleph, nový stroj kombinující \eTeX\ a \OMEGA, je nyní k~dispozici. +Trochu informace najdete na \OnCD{texmf-dist/doc/aleph/base} +a \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph}. Formát pro +Aleph, zalo¾ený na \LaTeX u se jmenuje \textsf{lamed}. + +\item Nejnovìj¹í vydání \LaTeX u má novou verzi \acro{LPPL} \Dash teï +oficiálnì schválená Debian licence. Rozmanité dal¹í aktualizace najdete +v~souborech \filename{ltnews} v~\OnCD{texmf-dist/doc/latex/base}. + +\item Je dodán \cmdname{dvipng}, nový program pro konvertování \acro{DVI} na +obrazové soubory \acro{PNG}. Viz \OnCD{texmf/doc/man/man1/dvipng.1}. + +\item Zredukovali jsme balík \pkgname{cbgreek} na \uv{støednì} velkou +sadu fontù, se souhlasem a na radu autora (Claudio Beccari). +Odstranìné fonty jsou neviditelné, obrysové, a prùhledné, +relativnì zøídka se pou¾ívají a my jsme potøebovali místo. +Úplná sada je dostupná z~\acro{CTAN} +(\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). + +\item \cmdname{oxdvi} byl odebrán; pou¾ijte jednodu¹e \cmdname{xdvi}. + +\item Pøíkazy \cmdname{ini} a \cmdname{vir} (linky) pro +\cmdname{tex}, \cmdname{mf} a \cmdname{mpost} se ji¾ nevytváøejí, +napøíklad \cmdname{initex}. Funkènost instrukce \cmdname{ini} byla po +celá léta pøístupna prostøednictvím volby \optname{-ini} na~pøíkazovém øádku. + +\item Podpora platformy \textsf{i386-openbsd} byla zru¹ena. +Jeliko¾ balíèek \pkgname{tetex} v~\acro{BSD} Ports systému +je dostupný a \acro{GNU/}Linux a Free\acro{BSD} binárky byly +dostupné, zdálo se nám, ¾e èas dobrovolníkù mù¾e být vyu¾it +lépe nìkde jinde. + +\item Na \textsf{sparc-solaris} (pøinejmen¹ím) jste mo¾ná +museli nastavovat promìnné prostøedí +\envname{LD\_LIBRARY\_PATH}, aby bì¾ely programy \pkgname{t1utils}. +Je to tím, ¾e jsou kompilovány v~C++, +a neexistuje standardní umístìní \singleuv{runtime} knihoven. +(To není novinka roku 2004, ale nebylo to døív zdokumentováno.) +Podobnì, na \textsf{mips-irix}, `runtime' knihovny pro \acro{MIPS} +7.4 jsou nezbytné. +\end{itemize} + +\subsubsection{2005} + +Rok 2005 pøinesl jako obvykle mno¾ství modernizací balíèkù a programù. +Infrastruktura zùstala relativnì stabilní z~roku 2004, ale nutnì také +nastaly nìjaké zmìny: + +\begin{itemize} + +\item Byly zavedeny nové skripty \cmdname{texconfig-sys}, \cmdname{updmap-sys} a + \cmdname{fmtutil-sys}, které mìní konfiguraci v~systémových stromech. + Skripty \cmdname{texconfig}, + \cmdname{updmap} a \cmdname{fmtutil} teï mìní u¾ivatelské (user-specific) soubory + v~\dirname{$HOME/.texlive2005}. %$ + +\item Na specifikaci stromù obsahujících konfiguraèní soubory (u¾ivatelské resp. systémové) + byly zavedeny odpovídající nové promìnné \envname{TEXMFCONFIG} resp. + \envname{TEXMFSYSCONFIG}. Tedy, mo¾ná budete potøebovat pøesunout osobní verze + souborù \filename{fmtutil.cnf} a \filename{updmap.cfg} na tato místa; jiná volba je + pøedefinování \envname{TEXMFCONFIG} nebo \envname{TEXMFSYSCONFIG} v~souboru + \filename{texmf.cnf}. V~ka¾dém pøípadì skuteèná pozice tìchto souborù a + hodnoty \envname{TEXMFCONFIG} a \envname{TEXMFSYSCONFIG} + se musejí shodovat. Viz oddíl~\ref{sec:texmftrees}, + strana~\pageref{sec:texmftrees}. + +\item Loni jsme ponechali \verb|\pdfoutput| a jiné primitivy nedefinovány + pro výstup \dvi, pøesto¾e byl pou¾íván program \cmdname{pdfetex}. + Letos, jak jsme slíbili, jsme odstranili toto kompatibilitní + opatøení. Tedy kdy¾ vá¹ dokument pou¾ívá + \verb|\ifx\pdfoutput\undefined| + na testován\'i výstupu do formátu \acro{PDF}, je nutné ho zmìnit. Mù¾ete + k~tomu pou¾ít balík \pkgname{ifpdf.sty} (který funguje + v~plain \TeX u i \LaTeX u), nebo pou¾ít jeho logiku. + +\item Loni jsme zmìnili vìt¹inu formátù tak, aby vypisovaly (8bitové) znaky + tak jak jsou (viz pøedcházející sekci). Nový TCX soubor + \filename{empty.tcx} teï poskytuje jednodu¹¹í cestu k~dosa¾ení + pùvodního zápisu \verb|^^| kdy¾ si tak budete pøát, jako v~pøípadì: +\begin{verbatim} +latex --translate-file=empty.tcx yourfile.tex +\end{verbatim} + +\item Nový program \cmdname{dvipdfmx} je zaøazen pro pøevedení z~\acro{DVI} do \acro{PDF}; +ten je platnou aktualizací programu +\cmdname{dvipdfm} (který je té¾ je¹tì k~dispozici, i kdy¾ ho nedoporuèujeme). + +\item Nové programy \cmdname{pdfopen} a \cmdname{pdfclose} byly pøidány, aby +poskytly mo¾nost znovu otevøít \acro{PDF} +soubory v~programe Adobe Acrobat Reader bez jeho restartu. +(Jiné prohlí¾eèe \acro{PDF}, pøedev¹ím \cmdname{xpdf}, +\cmdname{gv} a \cmdname{gsview}, nikdy netrpìly tímto problémem.) + +\item Kvùli dùslednosti promìnné \envname{HOMETEXMF} a + \envname{VARTEXMF} byly pøejmenovány na \envname{TEXMFHOME} resp. na + \envname{TEXMFSYSVAR}. Je tu také \envname{TEXMFVAR}, která je + implicitnì u¾ivatelsky závislá (user-specific). Viz první bod vý¹e. +\end{itemize} + +\subsubsection{2006--2007} + +V~letech 2006--2007 byl rozsáhlým pøírustkem na \TL{} program \XeTeX{}, +pøístupný jako programy \texttt{xetex} a \texttt{xelatex}; viz +\url{http://scripts.sil.org/xetex}. + +\MP\ byl také podstatnì aktualizován, s~mnoha plány do budoucnosti +(\url{http://tug.org/metapost/articles}), podobnì pdf\TeX{} +(\url{http://tug.org/applications/pdftex}). + +Formát \TeX\ \filename{.fmt} (vysokorychlostní formát) a podobnì soubory +\MP\ a \MF\ jsou teï ulo¾eny v~podadresáøích \dirname{texmf/web2c}, +namísto pøímého ulo¾ení v~nìm (aèkoliv je adresáø stále prohledáván, +v~zájmu stávajících formátù \filename{.fmt}). Podadresáøe nesou jména +pou¾ívaných programù, napøíklad \filename{tex} +nebo \filename{pdftex} nebo \filename{xetex}. Tato zmìna by mìla pøi +bì¾ném pou¾ívání zùstat nepostøehnuta. + +Program (plain) \texttt{tex} ji¾ neète první øádky \texttt{\%\&} aby +urèil, jaký formát má spustit; je to èistý knuthovský \TeX. +(\LaTeX\ a v¹echny ostatní programy stále ètou øádky \texttt{\%\&}). + +Pochopitelnì se bìhem roku (jako obvykle) vyskytly stovky jiných +aktualizací balíkù a programù. Jako obyèejnì, zkontrolujte, prosím, +aktualizace na \acro{CTAN}u (\url{http://www.ctan.org}). + +Vnitønì, strom zdrojových textù je nyní ulo¾en v~Subversion, se +standardním webovským rozhran\'\i m pro jeho prohlí¾ení, kam smìruje +odkaz z~na¹í domovské stránky. Tøeba¾e není v~koneèné verzi +viditelný, oèekáváme, ¾e to poskytne základ pro stabilní rozvoj +v~letech následujících. + +Nakonec, v~kvìtnu 2006 Thomas Esser oznámil, ¾e u¾ nebude aktualizovat +te\TeX{} (\url{http://tug.org/tetex}). Výsledkem je nárùst zájmu o~\TL{}, +pøedev¹ím mezi distributory \GNU/Linuxu. +(Na \TL{} se nachází nové instalaèní schéma \texttt{tetex}u, +poskytující pøibli¾ný ekvivalent.) Doufáme, ¾e to mo¾ná povede +ke zlep¹ení prostøedí \TeX{}u pro v¹echny. + +\subsection{Sou\v{c}asnost (2008)} +\label{sec:tlcurrent} + +V~roce 2008 byla celá infrastruktura \TL{} pøebudována a znovu +implementována. Úplná informace o~instalaci je nyní +ulo¾ena v~textovém souboru \filename{tlpkg/texlive.tlpdb}. + +Mezi dal¹ími vìcmi je koneènì mo¾ná aktualizace instalace \TL{} +z~internetu po pøedchozí instalaci. Tuto vlastnost poskytoval +MiK\TeX\ ji¾ øadu let. Pøedpokládáme pravidelnou aktualizaci nových +balíkù po jejich vydání na \CTAN{}u. + +Obsa¾ený je významnìj¹í nový stroj (engine) Lua\TeX\ (\url{http://luatex.org}); +kromì lep¹í pøizpùsobivosti v~sázení je mo¾no tento vynikající skriptovací jazyk +pou¾ít jak uvnitø, tak i~mimo \TeX{}ovské dokumenty. + +Podpora Windows a unixových platforem je nyní jednotnìj¹í. +Zejména, vìt¹ina skriptù Perlu a Lua je teï k~dispozici pod Windows, +s~pou¾itím Perlu distribuovaného na~\TL. + +Nový skript \cmdname{tlmgr} (sekce~\ref{sec:tlmgr}) je v¹eobecné rozhraní +pro správu \TL{} po pøedchozí instalaci. Ovládá aktualizaci balíkù +a následující znovuvytvoøení formátù, mapovacích souborù a jazykových souborù, +volitelnì zahrnující lokální doplòky. + +S~pøíchodem programu \cmdname{tlmgr}, èinnosti programu +\cmdname{texconfig} na editaci formátù a konfiguraèních souborù dìlení +slov jsou nyní blokované. + +Program \cmdname{xindy} pro tvorbu rejstøíkù +(\url{http://xindy.sourceforge.net/}) je nyní zahrnut na vìt¹inì +platforem. + +Nástroj \cmdname{kpsewhich} mù¾e nyní ohlásit v¹echny výskyty +pro daný soubor +(option \optname{--all}) a omezené výskyty pro daný podadresáø +(option \optname{--subdir}). + +Program \cmdname{dvipdfmx} zahrnuje nyní funkènost extrakce informace +o `bounding boxu', pomocí povelu \cmdname{extractbb}; toto +byl jeden z~posledních rysù, které poskytoval \cmdname{dvipdfm}, av¹ak ne +\cmdname{dvipdfmx}. + +Fontové pøezdívky \filename{Times-Roman}, \filename{Helvetica}, atd. +byly odstranìné. Rùzné balíky oèekávaly jejich rùzné chování (pøedev¹ím, +¾e budou mít rùzné kódování) a nenalezlo se vhodné øe¹ení tohoto problému. + +Formát \pkgname{platex} byl odstranìn pro konflikt jmen s~japon¹tinou +\pkgname{platex}; +podporu pol¹tiny nyní zaji¹»uje balík \pkgname{polski}. + +Soubory \web{}ovských øetìzcù (pool) jsou nyní zkompilované do binárek pro +usnadnìní aktualizací. + +A nakonec, v~tomto vydání jsou zahrnuty zmìny provedené Donaldem Knuthem +v~jeho \'Uprav\'ach \TeX u roku 2008 (`\TeX\ tuneup of 2008'). +Viz \url{http://tug.org/TUGboat/Articles/tb29-2/tb92knut.pdf}. + +\subsection{Budoucnost} + +\emph{\TL{} není dokonalý!} A~nikdy nebude. Máme v~úmyslu +pokraèovat v~pravidelných vydáních a rádi bychom poskytovali +více podpùrných materiálù, programù, vèetnì instalaèních a jistì¾e +aktualizovaný a lépe zkontrolovaný strom maker a fontù. Tato práce je +provádìna dobrovolníky v~jejich limitovaném volném èase a mnoho +potøebného je¹tì zbývá udìlat. Viz, prosím, +\url{http://tug.org/texlive/contribute.html}. + +Prosíme, po¹lete opravy, návrhy, námìty a nabídky pomoci na: +\begin{quote} +\email{tex-live@tug.org}\\ +\url{http://tug.org/texlive} +\end{quote} +\smallskip\nobreak +\noindent \textsl{©»\kern-.4ptastné \TeX ování!} + +\end{document} diff --git a/Master/texmf/doc/texlive/source/texlive-de/Makefile b/Master/texmf/doc/texlive/source/texlive-de/Makefile new file mode 100644 index 00000000000..cecbe52710c --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-de/Makefile @@ -0,0 +1,3 @@ +include ../texlive-en/Makefile +doc = texlive-de +lang = german diff --git a/Master/texmf/doc/texlive/source/texlive-de/live4ht.cfg b/Master/texmf/doc/texlive/source/texlive-de/live4ht.cfg new file mode 100644 index 00000000000..4d2aa6b940a --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-de/live4ht.cfg @@ -0,0 +1,47 @@ +% tex4ht configuration file for the TeX Live documentation. +% Accumulated over many years. Public domain. +% +% html specifies the main output format. +% info for extra debugging info in the log files. + +% better approach is to have html in one piece (including footnotes). +% also the newest TeX4ht could produce UTF-8 output (-utf8 option) +\Preamble{charset=iso-8859-1,html,info,fn-in} + +% add extra stylesheet +\Configure{@HEAD}{\HCode{% +\Hnewline +\Hnewline +}} + +% or LaTeX complains it is missing. +\begin{document} + +\EndPreamble + +% simplify output for HTML. We leave TeX and LaTeX alone, since tex4ht +% actually does the lowered E (and raised A) in CSS. +\def\OMEGA{Omega} +\def\LaTeXe{LaTeX2e} +\def\eTeX{e-\TeX} +\def\acro#1{#1} +\def\MF{Metafont} +\def\BibTeX{BibTeX} +\def\warningbox{} +\def\endwarningbox{} + +\newif\ifhackliterals +\ifx\tldocenglish\undefined \else \hackliteralstrue \fi +\ifx\tldocrussian\undefined \else \hackliteralstrue \fi +\ifx\tldocgerman\undefined \else \hackliteralstrue \fi +% +\ifhackliterals + % these definitions cause "missing } inserted" at \end{tabularx} in + % French and Czech. don't know why. + % + % don't make these into links, as happens with \path. We only have a couple + % special characters that actually occur. + \def\dirname{\texttt\bgroup\catcode`\$=12 \catcode`\_=12 \finishliteral} + \def\finishliteral#1{#1\egroup} + \let\filename=\dirname +\fi diff --git a/Master/texmf/doc/texlive/source/texlive-de/lmsy10-40.png b/Master/texmf/doc/texlive/source/texlive-de/lmsy10-40.png new file mode 100644 index 00000000000..55c7772320b Binary files /dev/null and b/Master/texmf/doc/texlive/source/texlive-de/lmsy10-40.png differ diff --git a/Master/texmf/doc/texlive/source/texlive-de/texlive-de.tex b/Master/texmf/doc/texlive/source/texlive-de/texlive-de.tex new file mode 100644 index 00000000000..4291b40950e --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-de/texlive-de.tex @@ -0,0 +1,3091 @@ +% $Id: texlive-de.tex,v 1.81 2008/08/13 20:34:57 hahe Exp hahe $ +% TeX Live documentation. Originally written by Sebastian Rahtz and +% Michel Goossens, now maintained by Karl Berry and others. +% Public domain. +% +\documentclass{article} +\ifnum\Status=1 + % Create A4 pdf + \pdfpageheight297mm + \pdfpagewidth210mm +\fi +\let\tldocgerman=1 % for live4ht.cfg +\usepackage{ngerman} +\usepackage{tex-live} +\usepackage[latin1]{inputenc} % translators: use your preferred encodings. +\usepackage[T1]{fontenc} + +\def\dante{DANTE~e.\,V\kern-0.15em.} +\begin{document} + +\title{% + {\huge \textit{Anleitung zu \TeX\ Live}\\\smallskip}% + {\LARGE \textsf{\TL{} 2008}}% +} + + +\author{Karl Berry (Herausgeber) \\[3mm] + \url{http://tug.org/texlive/}\\[12mm] + \small{\textit{Verantwortlich für die deutsche Ausgabe}}\\[3mm] + \small{Klaus Höppner, \email{klaus@dante.de}} \\ + \small{(\dante)} \\[3mm] + } +\date{August 2008} + + +\maketitle +\thispagestyle{empty} + +\newpage + +\begin{multicols}{2} + \tableofcontents + \listoffigures +\end{multicols} + +%\renewcommand{\Status}{0} +%\typeout{Status is \Status} + +\clearpage + +% ============================================================== +\section{Einleitung}\label{sec:intro} + +Diese Anleitung beschreibt das \TL-System. Die {\TL} Distribution enthält +\TeX/\LaTeX-Systeme für Linux, verschiedene \acro{UNIX}-Plattformen, {\MacOSX} +und (32-Bit)-Windows. + +Wahrscheinlich haben Sie \TL{} auf einem von zwei Wegen bezogen, entweder +per direktem Download von \TL{} oder als Teil der \DVD{} \TK, die von +vielen \TeX-Vereinen (u.\,a. \dante) an ihre Mitglieder verschickt werden +und in Deutschland über die Fachbuchhandlung Lehmanns (\url{http://www.lob.de}) +vertrieben wird. Abschnitt~\ref{sec:tl-coll-dists} beschreibt kurz den +Inhalt der \TK-\DVD. Sowohl \TL{} und die \TK{} sind durch das Engagement +vieler Freiwilliger aus vielen \TeX-Vereinen entstanden. Im Übrigen +beschränkt sich diese Anleitung auf \TL{} an sich. + +{\TL} enthält lauf"|fähige Versionen von \TeX, \LaTeXe, \ConTeXt, \MF, \MP, +{\BibTeX} und vielen anderen Programmen, +sowie eine umfassende Auswahl an Makros, Zeichensätzen und +Beschreibungen, die gemäß der Standard"=\TeX"=Verzeichnisstruktur (\TDS) +abgelegt sind. + +Wenn Sie neuere Versionen der dort aufgeführten Pakete zu suchen wollen, gehen Sie am besten zu \acro{CTAN}: +\url{http://www.ctan.org/}. + +Eine kurze Zusammenfassung der wesentlichen Änderungen der aktuellen \TL-Version +gegenüber der Vorgängerversion finden Sie im Abschnitt~\ref{sec:history} auf +Seite~\pageref{sec:history}. + +\subsection{Unterstützung verschiedener Betriebssysteme} +\label{sec:os-support} +\TL{} enthält direkt ausführbare Programme für viele Unix-basierte +Betriebssysteme, inklusive \MacOSX. Selbst wenn Ihr Unix-System wider +Erwarten nicht unterstützt wird, sollten Sie in der Lage sein, aus +den mitgelieferten Programm-Quellen ein funktionierendes \TeX-System zu +kompilieren. + +Bezüglich Microsoft Windows werden Versionen ab Windows~2000 unterstützt, +während die aktuelle \TL{} unter Windows 95/98, ME und NT nicht +mehr lauffähig ist. Es existieren zwar keine 64-Bit-Versionen der +Programme, allerdings sollten die 32-Bit-Programme problemlos auf +64-Bit-Systemen funktionieren. + +% ------------------------------------------------------------- +\subsection{Einsatzmöglichkeiten des \TL-Systems der \TK}\label{sec:basic} + +Sie können das \TL-System wahlweise von der \DVD{} oder über das +Internet installieren. Der \emph{Net Installer} ist ein kleines Programm, +das die benötigten Teile aus dem Internet nachlädt. Dieser Weg bietet +sich an (eine schnelle und stabile Internetverbindung voraus gesetzt), +wenn Sie kein komplettes \TL{} installieren wollen, sondern Ihr System nur +mit bestimmten Paketen bestehen soll. + +Wenn Sie die \DVD{} besitzen (oder das ISO-Image der \DVD{} herunter +geladen haben -- dieses kann auf einigen Systemen sogar direkt als +virtuelles Medium ">gemountet"< werden), können Sie \TL{} nach +Wunsch auf Ihrer Festplatte installieren oder direkt von der \DVD +benutzen. + +Beide Methoden werden in den Abschnitten zur Installation beschrieben. +Hier daher nur die kurze Zusammenfassung: + +\begin{itemize*} +\item Das Hauptinstallationsskript ist \cmdname{install-tl}. Es existiert +sowohl im Textmodus als auch in Form einer grafischen Benutzeroberfläche (GUI). +Unter Windows ist der grafische Modus der Standard, auf allen anderen +Systemen der Textmodus. Durch die Optionen \code{-gui} bzw.\ \code{-no-gui} +können Sie gezielt einen der beiden Modi auswählen. +\item \TL installiert u.\,a. den neuen ">\TL Manager"< mit dem Namen +\prog{tlmgr}. Auch dieser unterstützt Text- und GUI-Mode. Mit diesem +Programm können Sie einerseits Pakete von \TL installieren oder deinstallieren, +andererseits \TL konfigurieren. +\end{itemize*} + + +% ------------------------------------------------------------- +\subsection{">Wo bekomme ich Hilfe?"< oder ">Hier werden Sie geholfen!"<}\label{sec:help} + +Die \TeX-Gemeinschaft ist ebenso aktiv wie hilfsbereit, und es wird +praktisch jede ernst gemeinte Frage beantwortet. Diese Hilfe ist allerdings +nicht formal organisiert, sondern wird von Freiwilligen in ihrer +Freizeit geleistet. Es ist daher ernst gemeint, dass Sie vor einer +Fragestellung Ihre ">Hausaufgaben"< gemacht haben. Falls Sie auf +eine garantierte kommerzielle Unterstützung angewiesen sind oder eine solche +bevorzugen, sollten Sie die Finger vollständig vom \TL-System lassen und +in der Aufstellung unter \url{http://tug.org/interest.html#vendors} nach +einem geeigneten Händler suchen. + +Die folgende Liste stellt die leicht zugänglichen Quellen in der +empfohlenen Reihenfolge vor: + +\begin{description} +\item [Einführung:]\mbox{}\\ + Wenn Sie \TeX-Anfänger sind und eine englische Einführung in das System benötigen, + sollten Sie das \acro{WWW}-Dokument \url{http://tug.org/begin.html} (Englisch) lesen. + + Für deutschsprachige \LaTeX-Anfänger ist die ">\LaTeXe-Kurzbeschreibung"< von großem Nutzen + (\OnCD{texmf-doc/doc/german/lshort-german/l2kurz.pdf}). +\item [\TeX-\acro{FAQ}s:]\mbox{}\\ + Die \TeX-\acro{FAQ} (im Deutschen + \file{de-tex-faq} ">\emph{Fragen und Antworten [\acro{FAQ}] über + das Textsatzsystem TeX und \acro{DANTE}, Deutschsprachige + Anwendervereinigung TeX e.V.}"<) ist ein riesiges Kompendium + mit Fragen (und Antworten) aller Art, von der einfachsten + Anfängerfrage bis zu Expertenwissen. + % Sie ist Bestandteil + % des \TL-Systems (\OnCD{texmf-doc/doc/german/FAQ-de/}) und umfasst zur + % Zeit 182~Seiten als PDF-Datei (\OnCD{texmf-doc/doc/german/FAQ-de/de-tex-faq.pdf}). + % Darüber hinaus ist die + % \acro{FAQ} als \HTML-Datei (\OnCD{texmf-doc/doc/german/FAQ-de/html/index.html}) + % und als durchsuchbare Textdatei + % (\OnCD{texmf-doc/doc/german/FAQ-de/text/index.html}) enthalten. + % Im Internet finden Sie die \acro{FAQ} unter + Sie finden die deutschsprachige \acro{FAQ} unter + \url{http://www.dante.de/faq/de-tex-faq/}; zudem wird die + Text"-ver"-sion regelmäßig in die News-Gruppe + \url{news:de.comp.text.tex} + verschickt. Die \acro{FAQ} besteht aus mehreren Teilen, wobei + jeder Teil ohne News-Header nicht länger als ca. 32\,KB ist. + + Des Weiteren existiert eine englischsprachige \acro{FAQ}-Sammlung + (\OnCD{texmf-doc/doc/english/FAQ-en/newfaq.pdf}), die auch im Internet verfügbar ist + (\url{http://www.tex.ac.uk/faq}). + + Bitte nutzen Sie bei Problemen zu allererst diese beiden Möglichkeiten. + +\item [\TeX-Catalogue:]\mbox{}\\ + Wenn Sie auf der Suche nach einem bestimmten Paket, + Font, Programm u.\,ä. sind, empfiehlt sich ein Blick in den + \TeX-Catalogue. Dieser Katalog enthält eine Liste aller verfügbaren + \TeX-spezifischen Dinge (siehe + % \OnCD{texmf-doc/doc/english/catalogue} oder + \url{http://www.ctan.org/tex-archive/help/Catalogue/catalogue.html}). + +\item [\TeX-\acro{WWW}-Ressourcen:]\mbox{}\\ + Im \acro{WWW}-Dokument \url{http://tug.org/interest.html} finden Sie eine große Anzahl \TeX-spezifischer + Links zu Büchern, Manuals und Artikeln zu allen Aspekten des \TeX-Systems. + +\item [Archive:]\mbox{}\\ + Ein Forum für die Hilfestellung sind die Usenet-News-Gruppen + \url{news:de.comp.text.tex} (Deutsch), \url{news:comp.text.tex} (Englisch) + und die Mailing-Liste \email{texhax@tug.org}. In deren Archiven finden + sich die Fragen und Antworten vieler Jahre. Ihre Suche können Sie in Google + beispielsweise mit \url{http://groups.google.de/group/de.comp.text.tex/topics} + starten -- oder auch in \url{http://tug.org/mail-archives/texhax/}. + + Im Allgemeinen ist es recht Erfolg versprechend, eine generelle Suche über Google + \url{http://www.google.de/} durchzuführen (entweder im \emph{WWW} allgemein + oder in den \emph{News-Gruppen}); dies insbesondere, wenn es sich um Fragen über + \PS/PDF, \cmdname{Ghostscript} u.\,ä. handelt. + +\item [Fragen stellen:]\mbox{}\\ + Wenn Sie mit den oben aufgezeigten Möglichkeiten immer noch keine + Antwort auf Ihre Frage gefunden haben, können Sie die Frage auch in einer + News-Gruppe stellen (neudeutsch: \emph{posten}). Hier bietet sich für + den deutschsprachigen Raum die News-Gruppe \url{news:de.comp.text.tex} an. + Benutzen Sie am besten für Anfragen Google + (\url{http://groups.google.de/group/de.comp.text.tex/topics}) + oder einen Newsreader. Fragen an die englischsprachige Gruppe + \url{news:comp.text.tex} + (bei Google: \url{http://groups.google.de/group/comp.text.tex/topics}) + sollten Sie bitte nur in Englisch stellen. + + Zusätzlich existieren E-Mail-Diskussionslisten, wobei hier die deutschsprachige Liste + \email{TeX-D-L@listserv.dfn.de} zu nennen ist (das englischsprachige Äquivalent + ist \email{texhax@tug.org}). Darüber hinaus bietet sich für Mitglieder + von \acro{DANTE}~e.V. der Beraterkreis an (\email{beraterkreis@dante.de}). + Wie Sie sich in die E-Mail-Liste \dirname{TeX-D-L} eintragen können, + finden Sie in der \acro{FAQ} unter ">\texttt{1.3.2 Was ist TeX-D-L?}"<. + + Bevor Sie aber eine Frage absenden, lesen Sie \emph{bitte} die entsprechenden + Einträge der \acro{FAQ} zum Thema ">\emph{Wie stelle ich eine Frage in einer + Newsgroup, damit ich mit hoher Wahrscheinlichkeit eine Antwort bekomme?}"<. So + z.\,B. ">\texttt{1.3.1 Was ist `de.comp.text.tex'?}"< und ">\texttt{1.3.7 Was + sollte ich gelesen haben, bevor ich eine Frage in `de.comp.text.tex' oder der + Diskussionsliste TeX-D-L stelle?}"< oder auch + \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. + +\item [Mithilfe:]\mbox{}\\ + Wenn Sie einen Fehler melden wollen oder Empfehlungen und Kommentare + zur \TL-Verteilung, -Installation oder -Dokumentation geben möchten, sollten Sie die + E-Mail-Liste \email{tex-live@tug.org} nutzen. + Korrekturen, Anmerkungen und Erweiterungen für die deutsche Übersetzung können Sie auch + an \email{cdrom@dante.de} oder schriftlich an die Geschäftsstelle von + \acro{DANTE}~e.V. senden. + + Fragen zu Programmen, die Sie in der {\TK} finden, sollten Sie besser auf + einer der oben genannten Mailing-Listen stellen oder direkt an den Programmautor + richten. +\end{description} + +Auf der anderen Seite können auch Sie mit Ihrem Wissen helfen. Die News-Gruppen +\url{news:de.comp.text.tex} (in Deutsch), \url{news:comp.text.tex} (in Englisch) und +die Mailing-Liste \email{TeX-D-L@listserv.dfn.de} (Deutsch) und \email{texhax@tug.org} (Englisch) +stehen allen offen. Wenn Sie also dort mitlesen, scheuen Sie sich nicht, Fragen, +zu denen Sie eine Antwort wissen, zu beantworten und damit anderen zu helfen. + +% ============================================================== +\section[Überblick zum \protect\TeX Live-System]{Überblick zum \TL-System} +\label{sec:overview-tl} +% don't use \TL so the \uppercase in the headline works. Also so +% tex4ht ends up with the right TeX. Likewise the \protect's. + +In diesem Abschnitt beschreiben wir Struktur und Inhalt des \TL-Systems und der übergeordneten \TK-\DVD. + + +% ------------------------------------------------------------- +\subsection[Die \protect\TeX\protect\ Collection: \TL, pro\TeX{}t, Mac\TeX]% +{Die \protect\TeX\protect\ Collection: \TL, pro\TeX{}t, Mac\TeX}\label{sec:tl-coll-dists} + +Die \DVD ">\TK"< besteht aus: +\begin{description} +\item[\TL] Ein komplettes \TeX-System, wahlweise zur Installation auf Festplatte oder zur direkten Benutzung +von der \DVD. +\item[Mac\TeX] für \MacOSX. Dieses enthält das komplette \TL, bietet zusätzlich aber ein Installationsprogramm +für Mac und einige Zusatzprogramme. Nähere Informationen finden Sie auf der Homepage von Mac\TeX{} unter +\url{http://www.tug.org/mactex/}. +\item[pro\TeX{}t] basiert auf der \MIKTEX-Distribution für Windows. Es enthält noch einige Zusatzprogramme und +stellt eine einfache Installationsanleitung bereit, die Schritt für Schritt den Weg zu einem kompletten +\TeX-System beschreibt. Die Homepage von pro\TeX{}t findet sich unter \url{http://tug.org/protext}. +\item[CTAN] Weiterhin ist auf der \DVD{} ein Ausschnitt der \TeX-bezogenen Software enthalten, die sich +in CTAN, dem \emph{Comprehensive \TeX{} Archive Network} befinden. +\item [\texttt{texmf-extra}] In diesem Verzeichnis befinden sich zusätzliche Pakete, die kein Teil von +\TL sind. +\end{description} + +\CTAN{}, \pkgname{protext} und \dirname{texmf-extra} unterliegen nicht den selben Lizenzregeln wie \TL. +Daher können für Teile hieraus andere Lizenzbedingungen bezüglich einer Weiterverteilung oder +Modifikation gelten, die Sie unbedingt beachten sollten! + +% ------------------------------------------------------------- +\subsection{Basisverzeichnisse von \TL}\label{sec:tld} + +In diesem Abschnitt beschreiben wir die Basisverzeichnisse der \TL-Distribution. + +Auf der \pkgname{live}-\DVD befindet sich die gesamte \TL-Hierarchie im Unterverzeichnis \dirname{texlive} +-- nicht im Wurzelverzeichnis der \DVD. + +\begin{center} +%% \begin{longtable}{@{}>{\ttfamily}lp{.63\hsize}@{}} +%% \hline +%% \rm +%% Verzeichnis & Inhalt \\ +%% \hline +%% \endfirsthead +%% \rm +%% Verzeichnis & Inhalt \\ +%% \hline +%% \endhead +%% \hline +%% \endfoot +\begin{tabular}{@{}>{\ttfamily}lp{.75\linewidth}@{}} +bin & ausführbare Programme des \TeX-Systems; + jeweils für die verschiedenen Rechnerplattformen + in Unterverzeichnissen zusammengefasst\\ +readme-html.dir & in diesem Verzeichnis (!) befinden sich HTML-Dateien + in verschiedenen Sprachen, die als schneller + Einstieg in \TL empfehlenswert sind.\\ +readme-txt.dir & in diesem Verzeichnis (!) befinden sich Text-Dateien + mit den gleichen Inhalten wie in {\ttfamily readme-html.dir}.\\ +source & Quelldateien aller Programme inklusive der + \Webc-Quellen für die \TeX- und \MF-Pakete als + komprimierte \file{bzip2}"=Archive\\ +support & verschiedene Programme und Hilfspakete, die \emph{nicht} automatisch + mitinstalliert werden, wie z.\,B. Editoren und \TeX-Shells\\ +texmf & Verzeichnisbaum für Programme und zugehörigen Hilfsdateien und Anleitungen; enthält keine \TeX-Formate + und Pakete (siehe \texttt{TEXMFMAIN} im nächsten Abschnitt)\\ +texmf-dist & Hauptbaum mit Formaten und Paketen (siehe \texttt{TEXMFDIST} im nächsten Abschnitt)\\ +texmf-doc & Verzeichnisbaum mit vollständigen Dokumentationen (ohne andere installierte Dateien); sortiert nach + Sprachen \\ +texmf-var & Verzeichnisbaum für automatisch erzeugte und gespeicherte Dateien + für \TeX, {\MF} und andere (siehe \texttt{TEXMFSYSVAR} im nächsten Abschnitt),\\ +%%\end{longtable} +\end{tabular} +\end{center} +% +Zusätzlich zu den oben aufgeführten Verzeichnissen finden Sie +im Wurzelverzeichnis der Distribution +auch noch die Installationsskripte. + +Das Verzeichnis \OnCD{texmf-doc} enthält zwar nur Anleitungen, bei weitem aber nicht die gesamte Dokumentation: +Die Dokumentation für Programme (Handbücher, ">man~pages"<, \acro{GNU}-\acro{info}-Dateien) beispielsweise finden Sie +im Verzeichnis \OnCD{texmf/doc}, da die Programme selbst sich im Verzeichnis \OnCD{texmf} befinden. Ähnliches +gilt für die Dokumentation der \TeX-Pakete und -Formate im Verzeichnis \OnCD{texmf-dist/doc}. + +Benutzen Sie die Programme \cmdname{texdoc} oder \cmdname{texdoctk}, wenn Sie auf der Suche nach irgendeiner +Dokumentationsdatei sind. Hilfreich in diesem Zusammenhang könnte auch die Link-Sammlung \filename{doc.html} im +Wurzelverzeichnis sein. + +Die Anleitung zu \TL ist in verschiedenen Sprachen verfügbar: +\begin{itemize*} +\item{Chinesisch:} \OnCD{texmf-doc/doc/chinese/texlive-zh-cn/texlive-zh-cn} +\item{Tschechisch/Slowakisch:} \OnCD{texmf-doc/doc/czechslovak/texlive-cz/live} +\item{Englisch:} \OnCD{texmf-doc/doc/english/texlive-en/texlive-en} +\item{Französisch:} \OnCD{texmf-doc/doc/french/texlive-fr/texlive-fr} +\item{Deutsch:} \OnCD{texmf-doc/doc/german/texlive-de/texlive-de} (dieses Dokument) +\item{Polnisch:} \OnCD{texmf-doc/doc/polish/texlive-pl/texlive-pl} +\item{Russisch:} \OnCD{texmf-doc/doc/russian/texlive-ru/texlive-ru} +\end{itemize*} + +% ------------------------------------------------------------- +\subsection{Überblick über die vordefinierten texmf-Bäume} +\label{sec:texmftrees} + +Dieser Abschnitt listet alle vordefinierten texmf-Bäume, die vom System benutzt +werden, und deren Bedeutung auf. Das Kommando \cmdname{texconfig conf} +zeigt Ihnen die aktuellen Einstellungen dieser Variablen an. + +\begin{ttdescription} +\item [TEXMFMAIN] In diesem Baum befinden sich wichtige Teile des Systems, + Hilfsprogramme (wie \verb+web2c/mktexdir+), pool-Dateien und andere + Hilfsdateien. +\item [TEXMFDIST] In diesem Baum befinden sich die wesentlichen Makro-Pakete, + Fonts usw. Dieser Baum enthält systemunabhängige Daten, die prinzipiell + von jedem TDS-kompatiblem \TeX-System nutzbar sein sollten. +\item [TEXMFLOCAL] Dieser Baum ist für Ergänzungen oder Aktualisierungen + von Makros, Fonts etc. gedacht, die Administratoren für alle Nutzer + installieren. +\item [TEXMFHOME] In diesem Baum können einzelne Nutzer Ergänzungen oder + Aktualisierungen von Makros, Fonts etc. ablegen. Standardmäßig befindet + sich dieser Baum unterhalb von \verb+$HOME+, so dass andere Nutzer von + Änderungen hier nicht beeinflusst werden. +\item [TEXMFCONFIG] Dieser Baum wird von den Hilfsprogrammen von te\TeX{} + wie \verb+texconfig+, \verb+updmap+ und \verb+fmtutil+ verwendet. + Standardmäßig befindet sich dieser Baum unterhalb von \verb+$HOME+, + so dass andere Nutzer von Änderungen hier nicht beeinflusst werden. +\item [TEXMFSYSCONFIG] Dieser Baum wird von den Hilfsprogrammen von te\TeX{} + wie \verb+texconfig-sys+, \verb+updmap-sys+ und \verb+fmtutil-sys+ + verwendet, so dass hier das Verhalten des \TL-Systems für alle Nutzer + beeinflusst werden kann. +\item [TEXMFVAR] Dieser Baum wird von Hilfsprogrammen wie \verb+texconfig+, + \verb+updmap+ und \verb+fmtutil+ benutzt, um automatisch generierte + Konfigurations-Dateien abzulegen. +\item [TEXMFSYSVAR] Dieser Baum wird von den systemweiten Hilfsprogrammen + wie \verb+texconfig-sys+, \verb+updmap-sys+ und \verb+fmtutil-sys+ + verwendet, um automatisch generierte Konfigurations-Dateien abzulegen. +\end{ttdescription} + +\noindent +Der Standard der Verzeichnisstruktur von \TL sieht wie folgt aus: +\begin{description} + \item[System-weites Wurzelverzeichnis] kann \TL{}-Versionen aus mehreren Jahren beinhalten: + \begin{ttdescription} + \item[2007] Eine Vorversion von \TL. + \begin{ttdescription} + \item [...] + \end{ttdescription} + \item[2008] Die aktuelle Version. + \begin{ttdescription} + \item [bin] ~ + \begin{ttdescription} + \item [i386-linux] \GNU/Linux binaries + \item [...] + \item [universal-darwin] \MacOSX binaries + \item [win32] Windows binaries + \end{ttdescription} + \item [texmf] Hierauf verweist \envname{TEXMFMAIN}. + \item [texmf-dist] \envname{TEXMFDIST} + \item [texmf-doc] \envname{TEXMFDOC} + \item [texmf-var] \envname{TEXMFSYSVAR} + \item [texmf-config] \envname{TEXMFSYSCONFIG} + \end{ttdescription} + \item [texmf-local] \envname{TEXMFLOCAL}, dieses Verzeichnis gilt für alle installierten \TL-Versionen + (aktuelle Version und Vorgängerversion), so dass hier durchgeführte lokale Änderungen über die + Jahre hinweg erhalten bleiben. + \end{ttdescription} + \item[Home-Verzeichnis des Benutzers] + (\texttt{\$HOME} oder \texttt{\%USERPROFILE\%}): + \begin{ttdescription} + \item[.texlive2007] Vom Nutzer privat erzeugte Dateien and Konfigurationsdaten + der Vorversion. + \item[.texlive2008] Vom Nutzer privat erzeugte Dateien and Konfigurationsdaten + für die aktuelle Version von \TL. + \begin{ttdescription} + \item [texmf-var] \envname{TEXMFVAR} + \item [texmf-config] \envname{TEXMFCONFIG} + \end{ttdescription} + \item[texmf] \envname{TEXMFHOME} Persönliche Makros, Fonts usw. des Nutzers. + \textit{etc.} + \end{ttdescription} +\end{description} + +% ------------------------------------------------------------- +\subsection{\protect\TeX-Erweiterungen}\label{sec:tex-extensions} + +Unter den \TeX-Systemen der {\TL} befinden sich verschiedene +\TeX"=Erweiterungen: + +\begin{description} +\item [\eTeX]\label{text:etex} stellt bei 100\%-iger Kompatibilität zum + normalen {\TeX} einen kleinen, aber mächtigen Satz neuer Befehle + bereit (für Makroexpansion, Character-Scanning, zusätzliche + Klassen für ">marks"<, erweiterte Debug-Möglichkeiten und andere). + Zusätzlich gibt es noch die \TeXXeT-Erweiterungen für den bidirektionalen Textsatz, + wie er beispielsweise im Arabischen gebraucht wird. + Im voreingestellten Modus ist {\eTeX} 100\%-ig kompatibel mit dem ">normalen"< \TeX. + Die Dokumentation zu {\eTeX} finden Sie in der Datei + \OnCD{texmf-dist/doc/etex/base/etex_man.pdf}. +\item [pdf\TeX] enthält die \eTeX\ Erweiterungen und erlaubt zusätzlich + die Ausgabe in PDF-Dateien sowie {\dvi}-Dateien. + Die Dokumentation zu pdf\TeX{} finden Sie unter + \OnCD{texmf-dist/doc/pdftex/manual/pdftex-a.pdf}. + In der Datei + \OnCD{texmf-dist/doc/pdftex/manual/samplepdf/samplepdf.tex} finden + Sie ein Anwendungsbeispiel. Das \LaTeX"=Paket \pkgname{hyperref} + besitzt die Option \optname{pdftex} mit der Möglichkeit + für aktive Querverweise (Hypertext) in PDF-Dateien. +\item [Lua\TeX] befindet sich noch in Entwicklung + und ist als zukünftiger Nachfolger von pdf\TeX\ vorgesehen, + zu dem es abwärtskompatibel bleiben soll. + Weiterhin soll es auch Aleph ersetzen. + Durch den enthaltenen Lua-Interpreter (s.\,\url{http://www.lua.org/}) + können Probleme, die in \TeX{} nur mühsam lösbar sind, + einfach und elegant gelöst werden. + Wird es unter dem Namen \filename{texlua} aufgerufen, + verhält es sich wie ein eigenständiger Lua-Interpreter + -- und wird als solcher in vielen Skripten von \TL bereits benutzt. + Für weitere Informationen siehe \url{http://www.luatex.org/} und + \OnCD{texmf-dist/doc/luatex/luatexref-t.pdf}. +\item [XeTeX] bietet die Unterstützung von Unicode Zeichensätzen und + OpenType Schriften durch diverse zusätzliche Bibliotheken. + Mehr Informationen sind unter \url{http://scripts.sil.org/xetex} + verfügbar. +\item [\OMEGA] (Omega) ist ein \TeX-System, das intern mit Unicode + (16-Bit"=Unicode"=Zeichen) arbeitet und damit das gleichzeitige + Arbeiten mit nahezu allen auf der Welt eingesetzten Schriften + und deren Zeichenkodierungen erlaubt. Außerdem werden über dynamisch + geladene, sogenannte ">{\OMEGA}~Translation~Processes"< (\acro{OTP}s) + Transformationen zur Verfügung gestellt, die beliebige Eingaben + vor der Bearbeitung durch {\TeX} nach bestimmten Regeln + umformen. Die (nicht ganz aktuelle) Anleitung zu {\OMEGA} finden + Sie in dem \TL-System in der Datei \OnCD{texmf-dist/doc/omega/base/doc-1.8.tex}. +\item [$\aleph$] (Aleph) vereinigt die \OMEGA- und \eTeX-Erweiterungen. + Eine Minimaldokumentation finden Sie in \OnCD{texmf-dist/doc/aleph/base}. +\end{description} + +%\clearpage + +% ------------------------------------------------------------- +\subsection{Weitere Programme von \TL} + +{\TL} enthält eine ganze Reihe unterstützender Programme wie + +\smallskip + +\begin{description} +\item[\cmdname{bibtex}] Verwalten von Bibliographien +\item[\cmdname{dv2dt, dt2dv}] \file{dvi} nach ASCII und umgekehrt +\item[\cmdname{dviconcat}] Zusammenfügen von \dvi-Dateien +\item[\cmdname{dvips}] Konversion von {\dvi} in {\PS} +\item[\cmdname{dviselect}] Ausschneiden von Seiten aus \dvi-Dateien +\item[\cmdname{dvipdfmx}] \dvi-nach-PDF-Konverter (erzeugt auch + \acro{CJK}-konformes PDF aus + \dvi-Dateien mit \OMEGA"=Erweiterungen), als Alternative + zu pdf\TeX +\item[\cmdname{dvilj}] Druckertreiber für die HP-LaserJet"=Familie +\item[\cmdname{lacheck}] \LaTeX-Syntax-Überprüfung +\item[\cmdname{makeindex}] Erzeugen eines Stichwortverzeichnisses +\item[\cmdname{mpost}] \MF-ähnliches Grafikprogramm +\item[\cmdname{psnup}] mehrere logische \PS-Seiten auf einem Blatt platzieren +\item[\cmdname{psselect}] Ausschneiden von Seiten aus \PS-Dateien +\item[\cmdname{tex4ht}] \TeX-nach-\HTML-Konvertierung +\item[\cmdname{texexec, texmfstart}] \ConTeXt- und PDF"=Prozessor +\item[\cmdname{xdvi}] \dvi-Bildschirmausgabe im X-Window-System +\end{description} + +\subsection{Fonts in \protect\TL} +\label{sec:tl-fonts} + +\TL{} enthält eine Vielzahl qualitativ hochwertiger Vektorschriften. Weitere Informationen hierzu finden sich unter \url{http://tug.org/fonts} und \OnCD{texmf-doc/doc/english/free-math-font-survey/survey}. + +% ============================================================== +\section[Installation von \TeX Live]{Installation von \protect\TL} +\label{sec:install} + +\subsection{Das Installationsprogramms} +\label{sec:inst-start} + +Zur Installation von \TL benötigen Sie die \TK{}-\DVD{} oer den \emph{\TL{} Net Installer} aus dem Internet. + +\begin{description} +\item [Net Installer:] Verfügbar von \CTAN, unter +\dirname{systems/texlive/tlnet}; die URL +\url{http://mirror.ctan.org/systems/texlive/tlnet} leitet Sie automatisch +an einen nahe gelegenen Server des \CTAN-Netzwerks weiter. +Sie können entweder die Datei \filename{install-tl.zip} herunter laden, +die sowohl für Unix als auch Windows gedacht ist, +oder die deutlich kleinere Datei \filename{install-unx.tar.gz}, +die aber nur den Installer für Unix enthält. +Nach dem Auspacken finden Sie die Dateien \filename{install-tl} (Unix) +bzw.\ \filename{install-tl.bat} (Windows) im Verzeichnis \dirname{install-tl}. + +\item [\TeX{} Collection \DVD:] Hier finden Sie die Dateien \filename{install-tl} (Unix) +bzw.\ \filename{install-tl.bat} (Windows) im Verzeichnis \dirname{texlive} +der \DVD. Unter Windows startet beim Einlegen der DVD i.\,A. automatisch ein Programm, bei dem Sie u.\,a. das +Installationsprogramm von \TL auswählen können. Die \DVD\ erhalten Sie als Mitglied eines \TeX-Vereins +(wie \url{http://www.dante.de} für den deutschsprachigen Raum, weitere Vereine finden Sie unter +\url{http://tug.org/usergroups.html}), oder innerhalb Deutschlands von der Fachbuchhandlung Lehmanns +(\url{http://www.lob.de}) oder international von der \TeX{} Users Group +(\url{http://tug.org/store}). Alternativ können Sie das \ISO-Image der \TL (\url{http://tug.org/texlive/acquire.html}) aus dem Internet laden. + +\end{description} + +Die folgenden Abschnitte beschreiben die Installation für die einzelnen Betriebssysteme. +\subsubsection{Unix} + +\begin{figure}[tb] +\begin{boxedverbatim} +======================> TeX Live installation procedure <===================== + +=======> Note: Letters/digits in indicate menu items <======= +=======> for commands or configurable options <======= + + + Detected platform: Intel x86 with GNU/Linux + + binary systems: 1 out of 16 + + Installation scheme (scheme-full) + + Customizing installation scheme: + standard collections + language collections + 83 collections out of 84, disk space required: 1666 MB + + directories: + TEXDIR (the main TeX directory): + !! default location: /usr/local/texlive/2008 + !! is not writable, please select a different one! + TEXMFLOCAL (directory for site-wide local files): + /usr/local/texlive/texmf-local + TEXMFSYSVAR (directory for variable and automatically generated data): + /usr/local/texlive/2008/texmf-var + TEXMFSYSCONFIG (directory for local config): + /usr/local/texlive/2008/texmf-config + TEXMFHOME (directory for user-specific files): + ~/texmf + + options: + [ ] use letter size instead of A4 by default + [X] create all format files + [X] install macro/font doc tree + [X] install macro/font source tree + [ ] create symlinks in standard directories + + Install for running from DVD + +Other actions: + start installation to HD + help + quit + +Enter command: +\end{boxedverbatim} +\caption{Installationsprogramm im Text-Modus (\GNU/Linux)}\label{fig:text-main} +\end{figure} + +\begin{figure}[tb] +\tlpng{install-w32-main}{\linewidth} +\caption{Grafische Oberfläche des Installationsprogramms (Windows)}\label{fig:gui-main} +\end{figure} + +\noindent +Im Folgenden werden die Eingaben des +Benutzers nach dem Kommando-Prompt \samp{>} \Ucom{fett} dargestellt. + +Öffnen Sie ein Terminalfenster auf Ihrem Unix-System und geben Sie folgende Befehle ein: +\begin{alltt} +> \Ucom{cd /pfad/zum/installer} +> \Ucom{perl install-tl} +\end{alltt} +(Sie können auch direkt \Ucom{perl /pfad/zum/installer/install-tl} eingeben. Wenn Ihre +\DVD so gemountet ist, dass als ausführbar gekennzeichnete Skripte direkt gestartet werden +können, können Sie im Verzeichnis des Installers auch direkt +\Ucom{./install-tl} eingeben.) + +Zum Installieren mit Hilfe einer Benutzeroberfläche verwenden Sie +\begin{alltt} +> \Ucom{perl install-tl -gui} +\end{alltt} + +Alle Optionen des Installationsprogramms werden mit +\begin{alltt} +> \Ucom{perl install-tl -help} +\end{alltt} +angezeigt. + +\textbf{Wichtiger Hinweis zu den Zugriffsrechten unter Unix:} Ihre aktuelle Einstellung von \code{umask} +wird bei der Installation von \TL{} berücksichtigt. Daher müssen Sie darauf achten, dass Sie hierfür +einen sinnvollen Wert einstellen (z.\,B. \code{umask002}), wenn Ihre Installation auch durch andere Nutzer +als Sie benutzt werden soll. Falls Sie unsicher sind, was dies bedeutet, schauen Sie bitte in die Anleitung +zu \code{umask} (indem Sie das Kommando \code{man umask} eingeben). + +\subsubsection{Mac\,OS\,X} + +Wie in Abschnitt~\ref{sec:tl-coll-dists} bereits erwähnt wurde, existiert mit Mac\TeX{} (\url{http://tug.org/mactex}) ein eigenes \TeX-System für \MacOSX. Dieses enthält ein +komplettes \TL mit einem Installationsprogramm, das in Funktionalität und Aussehen der üblichen Installation von Software unter \MacOSX entspricht. Weiterhin sind einige Zusatzprogramme enthalten. + +Wenn Sie die \TK-\DVD besitzen, empfiehlt es sich daher, Mac\TeX{} zu verwenden. + +\subsubsection{Windows} + +Wenn Sie den \emph{Net Installer} verwenden, oder auf Ihrem System beim Einlegen der \DVD das +Installationsprogramm nicht automatisch gestartet wurde, können Sie die Installation von +\TL im Windows-Explorer durch Doppelklick auf \filename{install-tl.bat} (auf der \DVD befindet +sich diese Datei im Verzeichnis \texttt{texlive}) starten. + +Alternativ können Sie eine MS-DOS"=Eingabeaufforderung verwenden, dort in das Verzeichnis wechseln, +in dem sich das Installationsprogramm befindet und dort +\begin{alltt} +D:\bs{}texlive\bs{}> \Ucom{install-tl} +\end{alltt} +eingeben -- \texttt{...>} kennzeichnet hierbei den Eingabeprompt; +Ihre Eingabe ist \Ucom{\texttt{bold/fett}} dargestellt. + +Alternativ können Sie die Installation auch aus einem beliebigen Verzeichnis heraus starten: +\begin{alltt} +> \Ucom{D:\bs{}texlive\bs{}install-tl} +\end{alltt} +wobei wir hier annehmen, dass sich ihre \TK-\DVD im Laufwerk D: befindet. + +Zur Installation im Textmodus verwenden Sie: +\begin{alltt} +> \Ucom{install-tl -no-gui} +\end{alltt} + +Alle vorhandenen Optionen, die beim Starten des Installationsprogramms verwendet werden können, werden +wie folgt angezeigt: +\begin{alltt} +> \Ucom{install-tl -help} +\end{alltt} + +\subsubsection{Installation im Textmodus} + +Abb.~\ref{fig:text-main} zeigt den Eingangsbildschirm des Installationsprogramms im Textmodus. +Dieser ist ein reiner Textmodus, d.\,h., es gibt somit keine Unterstützung zum Wandern durch die +einzelnen Menüpunkte mit den Cursor-Tasten. Alle Befehle wie z.\,B. die Auswahl von Menüpunkten werden +durch Eingabe der entsprechenden Befehle bzw.\ Menükürzel über die Tastatur eingegeben und +dann durch Drücken von \emph{Enter} übernommen. Hierbei wird zwischen Groß- und Kleinschreibung +unterschieden! + +Die Installation im Textmodus ist so spartanisch, weil dieser Modus überall funktionieren soll und daher +auf die Verwendung von Bibliotheken wie \texttt{ncurses} unter Unix verzichtet wurde. + +\subsubsection{Installation mit Benutzeroberfläche} + +Abb.~\ref{fig:gui-main} stellt den Eingangsbildschirm des Installationsprogramms unter +Windows dar. Hier ist die Installation im grafischem Modus voreingestellt. +Der Großteil der Unterschiede in den Menüpunkten +im Vergleich zur Darstellung im Textmodus in Abb.~\ref{fig:text-main} +ergibt sich aus der Tatsache, +dass das hier abgebildete GUI-Fenster unter Windows dargestellt wurde. + +\subsection{Benutzung des Installationsprogramms} +\label{sec:runinstall} + +Das Installationsprogramm sollte (wenn Sie die vorherigen Abschnitte zum Aufbau von \TL und der +verwendeten Verzeichnisstruktur gelesen haben) weitgehend selbsterklärend sein. Trotzdem wollen wir +auf einige Punkte näher eingehen. + +\subsubsection{Auswahl der Binaries (nur für Unix)} +\label{sec:binary} + +\begin{figure}[tbh] +\begin{boxedverbatim} +Available sets of binaries: +=============================================================================== + + a [ ] alpha-linux DEC Alpha with GNU/Linux + b [ ] amd64-freebsd x86_64 with FreeBSD + c [ ] hppa-hpux HP-UX + d [ ] i386-freebsd Intel x86 with FreeBSD + e [X] i386-linux Intel x86 with GNU/Linux + f [ ] i386-openbsd Intel x86 with OpenBSD + g [ ] i386-solaris Intel x86 with Sun Solaris + h [ ] mips-irix SGI IRIX + i [ ] powerpc-aix PowerPC with AIX + j [ ] powerpc-linux PowerPC with GNU/Linux + k [ ] sparc-linux Sparc with GNU/Linux + l [ ] sparc-solaris Sparc with Solaris + m [ ] universal-darwin universal binaries for MacOSX/Darwin + o [ ] win32 Windows + p [ ] x86_64-linux x86_64 with GNU/Linux +\end{boxedverbatim} +\caption{Auswahlmenü für Binaries}\label{fig:bin-text} +\end{figure} + +Abb.~\ref{fig:bin-text} zeigt das Auswahlmenü für die Binaries der einzelnen Betriebssysteme im Textmodus. +Im Allgemeinen sollte hier schon das richtige System ausgewählt sein. Sie können aber problemlos Binaries +für verschiedene Systeme parallel auswählen. Dies bietet sich an, wenn Ihre Installation auf verschiedenen +Rechnern in einem heterogenen Netzwerk sichtbar ist und von dort aus benutzt werden soll. + +\subsubsection{Auswahl der zu installierenden Komponenten} +\label{sec:components} + +\begin{figure}[tbh] +\begin{boxedverbatim} +Select a scheme: +=============================================================================== + + a [ ] TeX Live basic scheme + b [ ] TeX Live scheme for ConTeXt + c [X] TeX Live full scheme + d [ ] GUST TeX Live scheme + e [ ] GUTenberg TeX Live scheme + f [ ] TeX Live medium scheme + g [ ] TeX Live minimal scheme + h [ ] TeX Live for Omega users + i [ ] teTeX scheme + j [ ] XML typesetting scheme +\end{boxedverbatim} +\caption{Menü zur Auswahl des Schemas}\label{fig:scheme-text} +\end{figure} + +Abb.~\ref{fig:scheme-text} zeigt das Auswahlmenü für ein grundsätzliches Installationsschema der +\TL. Durch die Auswahl eines Schemas werden automatisch die Komponenten zur Installation ausgewählt, die +für das gewünschte Schema notwendig bzw.\ sinnvoll sind. Mit einer vollständigen Installation von \TL +(\emph{full scheme}) sind Sie auf der sicheren Seite, da hier einfach alles installiert wird. Sie können +aber auch eines der abgespeckten Schemas wie \emph{basic} (für ein sehr schlankes System), \emph{medium} +oder \emph{minimal} (dies empfiehlt sich aber nur für Testsysteme und weniger zum ernsthaften Arbeiten) +auswählen. Weiter stehen einige Schemas für spezielle Zwecke oder Sprachen zur Verfügung. + +\begin{figure}[tbh] +\tlpng{stdcoll}{.7\linewidth} +\caption{Menü zur Aus- oder Abwahl von Collections (hier unter Linux)}\label{fig:collections-gui} +\end{figure} + +Wenn Sie das Schema ausgewählt haben, können Sie dieses in den Menüpunkten \emph{standard collections} und +\emph{language collections} (s.\,Abb.~\ref{fig:collections-gui}, diesmal zur Abwechslung im GUI-Modus) +individuell nach Ihren Wünschen anpassen. + +Während das Schema nur den grundlegenden Funktionsumfang vorgibt, ist die Auswahl von Komponenten auf der +Ebene der \emph{Collections} viel feiner. Eine Collection besteht dabei aus mehreren Paketen zu einem Thema, +wobei jedes der Pakete aus bestimmten Makrodateien, Fontdateien usw. bestehen kann. + +Noch mehr Kontrolle über die Komponenten Ihres Systems haben Sie nach der Installation mit dem Programm~\prog{tlmgr}, das in Abschnitt~\ref{sec:tlmgr} beschrieben wird. Hier können Sie gezielt einzelne +Pakete installieren oder entfernen. + +\subsubsection{Verzeichnisse} +\label{sec:directories} + +Die Verzeichnisstruktur von \TL wurde bereits im Abschnitt~\ref{sec:texmftrees} auf S.~\pageref{sec:texmftrees} +beschrieben. Als Wurzelverzeichnis für \TL (\dirname{TEXDIR}) wird unter Windows +(|%PROGRAMFILES%\texlive\2008|) und unter Unix (\dirname{/usr/local/texlive/2008}) angenommen. + +Prinzipiell können Sie diesen Pfad problemlos ändern, z.\,B. wenn Sie \TL als normaler Nutzer installieren +wollen und kein Schreibrecht in dem o.\,a. Verzeichnis besitzen. + +Auf Wunsch können Sie \TL also auch in Ihrem Home-Verzeichnis installieren, wenn Sie sowieso der einzige +Verwender von \TL sind. Für Ihr Home-Verzeichnis können Sie den Pfad ">|~|"< verwenden und so +Beispielsweise \TL nach |~/texlive/2008| installieren. + +Wir empfehlen Ihnen, die Jahreszahl im Verzeichnisnamen bei zu behalten. So können Sie von Jahr zu Jahr +einfach die neue Version testen, ohne die alte zu entsorgen. Bei Bedarf können Sie einen symbolischen +Link (z.B. \dirname{/usr/local/texlive-cur}) verwenden, der jeweils auf das Verzeichnis der aktuellen +Version von \TL verweist. + +Wenn Sie die Einstellung \dirname{TEXDIR} im Installationsprogramm ändern, werden die Werte für +\dirname{TEXMFLOCAL}, \dirname{TEXMFSYSVAR} und +\dirname{TEXMFSYSCONFIG} automatisch angepasst. + +Das als \dirname{TEXMFHOME} bezeichnete Verzeichnis ist der Ort, in dem persönliche Makrodateien, +Schriften o.\,ä. abgelegt werden können. Vorgabewert ist |~/texmf|. Im Gegensatz zu \dirname{TEXDIR} +wird |~| hier nicht direkt zum Pfad des Home-Verzeichnisses aufgelöst, sondern unverändert in die +Konfigurationsdateien von \TL übernommen und erst zur Laufzeit aufgelöst. Somit kann jeder Nutzer +des Systems seinen komplett eigenen Pfad haben, der von \TL verwendet wird, und so nach Wunsch auch +eigene Konfigurationsänderungen durchführen. +Zur Laufzeit wird |~| unter Unix durch \dirname{$HOME} und unter Windows durch \verb|%USERPROFILE%| ersetzt. + +\subsubsection{Optionen} +\label{sec:options} + +\begin{figure}[tbh] +\begin{boxedverbatim} +

use letter size instead of A4 by default: [ ] + create all format files: [X] + install font/macro doc tree: [X] + install font/macro source tree: [X] + create symlinks in standard directories: [ ] + binaries to: + manpages to: + info to: +\end{boxedverbatim} +\caption{Auswahlmenü für weitere Optionen (Unix)}\label{fig:options-text} +\end{figure} + +Abb.~\ref{fig:options-text} zeigt das Menü, in dem weitere Einstellungen für die Installation von +\TL möglich sind. Drei dieser Optionen erfordern eine Erläuterung: +\begin{description} +\item[use letter size instead of A4 by default:] Verwendung von Letter statt DIN\,A4 als +Standard\-papier\-größe. Natürlich können Sie später unabhängig davon für einzelne Dokumente eine +beliebige Papiergröße wählen. + +\item[create all format files:] Auch wenn das Erzeugen von Formatdateien für Makropakete, die Sie gar + nicht benötigen, Zeit und Platz kostet, empfehlen wir trotzdem, diese Option ausgewählt zu belassen. + Falls Sie diese Option abwählen, werden Formatdateien jeweils bei Bedarf erzeugt, landen dann aber + im persönlichen \dirname{TEXMFVAR}-Baum des aktuellen Benutzers. Hier liegende Formate werden allerdings + nicht automatisch neu gerneriert, wenn z.\,B. Programme oder Silbentrennmuster aktualisiert werden, so dass + im Extremfall nach einem Update Inkompatibilitäten entstehen können. + +\item[create symlinks in standard directories] (nur unter Unix): + Mit dieser Option können Sie symbolische Links für Programme und Dokumentation in den Standard\-verzeichnissen + Ihres Systems anlegen, so dass Sie Ihre Umgebungsvariablen \envname{PATH}, \envname{MANPATH} und + \envname{INFOPATH} nicht anpassen müssen. Natürlich benötigen Sie für diese Option Schreibrechte in + den entsprechenden Verzeichnissen. Diese Option ist nicht dazu gedacht, ein vorhandenes \TeX-System, das + z.\,B. als Teil Ihrer Linux-Distribution installiert wurde, zu überschreiben. Sie dient vielmehr dazu, + dass die Links in Verzeichnissen angelegt werden, wo die Nutzer sie erwarten -- beispielsweise + \dirname{/usr/local/bin} --, aber sich noch keine \TeX-Programme befinden. +\end{description} + + +\subsubsection[Benutzen von \protect\TL direkt von DVD{}]{Benutzen von \protect\TL direkt von DVD{} (nur im Textmodus verfügbar)} +\label{sec:fromdvd} + +Verwenden Sie die Option ">|V|"<, um die Installation zum Benutzen von \TL direkt von der \DVD einzustellen. +Ihr Installationsbildschirm sollte nun so aussehen wie in Abb.~\ref{fig:main-fromdvd} dargestellt. +Tatsächlich wechselt die Option~|V| jeweils zwischen Installation auf Festplatte und Installation zur +Nutzung von \DVD hin- und her, so dass Sie problemlos zur alten Installations"-einstellung zurück kommen, +wenn Sie diese Option versehentlich ausgewählt haben. + +\begin{figure}[tbh] +\begin{boxedverbatim} +======================> TeX Live installation procedure <===================== + +=======> Note: Letters/digits in indicate menu items <======= +=======> for commands or configurable options <======= + + directories: + TEXDIRW (Writable root): + !! default location: /usr/local/texlive/2008 + !! is not writable, please select a different one! + TEXMFLOCAL (directory for site-wide local files): + /usr/local/texlive/texmf-local + TEXMFSYSVAR (directory for variable and automatically generated data): + /usr/local/texlive/2008/texmf-var + TEXMFSYSCONFIG (directory for local config): + /usr/local/texlive/2008/texmf-config + TEXMFHOME (directory for user-specific files): + ~/texmf + + options: + [ ] use letter size instead of A4 by default + [X] create all format files + + set up for installing to hard disk + +Other actions: + start installation for running from DVD + help + quit +\end{boxedverbatim} +\caption{Haupschirm des Installationsprogrmm, wenn die Option \optname{from DVD} + ausgewählt wurde}\label{fig:main-fromdvd} +\end{figure} + +Wie Sie sehen, hat sich das Hauptmenü an einigen Stellen geändert: Die Menüpunkte zur Auswahl eines +Schemas oder von Collections sowie zum Anlegen symbolischer Links sind verschwunden, und im Abschnitt +\emph{Directories} wird nun die Angabe eines Verzeichnisses für \dirname{TEXDIRW} (writable root) verlangt. + +Auch beim Verwenden von \TL direkt von \DVD müssen einige Verzeichnisse auf der Festplatte angelegt werden, +in denen \TL beispielsweise automatisch generierte Dateien (wie Formate oder Fontmaps) ablegen kann. +Die Verzeichnisse \dirname{texmf}, \dirname{texmf-dist} und \dirname{texmf-doc} werden aber direkt von +\DVD benutzt und daher nicht auf die Festplatte kopiert. + +Die Konfiguration von \TL im Anschluss an die Installation unter Unix ist bei der Verwendung als Live-System +von \DVD etwas komplexer, da hier an einigen Stellen von der normalen Verzeichnisstruktur von \TL abgewichen +werden muss, s.~Abschnitt~\ref{sec:postinstall}. + +Aus Zeitgründen ist die Option für die Benutzung von \TL direkt von \DVD leider nicht im grafischen Modus +des Installationsprogramms enthalten. Daher muss hierfür zwingend der Textmodus verwendet werden. +Zu diesem Zweck muss daher unter Windows die Installation innerhalb einer Eingabeaufforderung mit der +Option~\texttt{-no-gui} gestartet werden (s.\,Abschnitt~\ref{sec:cmdline}). + +Abschnitt~\ref{sec:portable-unix} beschreibt einen portableren Weg um \TL zu benutzen, der keine Änderungen +der Systemkonfiguration erfordert, dafür dann aber keine Konfigurationsänderungen an \TL erlaubt. + + +\subsection{Kommandozeilenoptionen für die Installation} +\label{sec:cmdline} + +Nach Eingabe von +\begin{alltt} +> \Ucom{install-tl -help} +\end{alltt} +erhalten Sie eine Liste der vorhanden Kommando\-zeilen\-optionen. Sie können diese entweder mit |-| oder |--| +verwenden. Die wichtigsten sind: + +\begin{ttdescription} +\item[-gui] Installation im \GUI{}-Modus. Hierfür muss unter Unix Perl/Tk installiert sein + (\url{http://tug.org/texlive/distro.html#perltk}); falls dies nicht der Fall ist, wird die Installation + stattdessen im Textmodus durchgeführt. +\item[-no-gui] Installation im Textmodus. Da dies unter Unix Standard ist, wirkt sich diese Option nur + unter Windows aus. Da die Installation zum Benutzen von \TL direkt von \DVD im grafischen Modus nicht + verfügbar ist, brauchen Sie in diesem Fall unbedingt den Textmodus. +\item[-lang {\sl LL}] Sprache des Installationsprogramms als Sprach-Code in zwei Buchstaben (\textsl{LL}). + Derzeit werden englisch (\texttt{en}, Standard), deutsch (\texttt{de}), französisch (\texttt{fr}), + holländisch (\texttt{nl}), polnisch (\texttt{pl}), slowenisch (\texttt{sl}) und vietnamesisch + (\texttt{vi}) unterstützt. Das Installationsprogramm versucht, die gewünschte Sprache anhand des + Systems herauszufinden. Falls dies scheitert oder die betreffende Sprache nicht verfügbar ist, wird als + Rückfallposition englisch benutzt. +\item[-profile {\sl profile}] Das Installationsprogramm schreibt die ausgewählten Optionen in eine Datei + \filename{texlive.profile} im Unterverzeichnis \dirname{2008/tlpkg}. Mit dieser Option können + Sie eine bereits vorhandene Datei bei der Installation weiter verwenden, z.\,B. wenn Sie äquivalente + Installationen auf mehreren Rechnern realisieren wollen, ohne alle Auswahlschritte der Installation immer + wieder neu durchführen zu müssen. Hier ein Beispiel einer solchen Datei: + \begin{fverbatim} +# texlive.profile written on Wed Jul 9 16:13:44 2008 UTC +# It will NOT be updated and reflects only the +# installation profile at installation time. +selected_scheme scheme-basic +TEXDIR /usr/local/texlive/2008 +TEXDIRW /usr/local/texlive/2008 +... +TEXMFSYSVAR /usr/local/texlive/2008/texmf-var +collection-basic 1 +... +option_symlinks 0 + \end{fverbatim} +\item [-location {\sl url/path}] zur Auswahl eines anderen Verzeichnisses mit den Quellen für Pakete; zur + weiteren Erläuterung siehe den nächsten Abschnitt. +\end{ttdescription} + +\subsubsection{Die Option \optname{location}} +\label{sec:location} + +Der als \optname{location} angegebene Wert kann neben einem ganz normalen Verzeichnispfad auch eine URL sein, +die mit \texttt{ftp:}, \texttt{http:} oder \texttt{file:/} beginnt. Falls sich \optname{location} auf einem +lokalen Laufwerk befindet (Verzeichnispfad oder mit \texttt{file:/} beginnende URL), +wird die Installationsmethode (aus komprimierten Archiven oder einem echten Live-Dateisystem) automatisch +bestimmt: falls bezüglich der angegebenen \optname{location} ein Unterverzeichnis \dirname{archive} existiert, +das Dateien vom Typ \filename{.tar.lzma} enthält, werden diese komprimierte Dateien als Installationsquelle +benutzt, selbst wenn parallel die Pakete ausgepackt in einem Live-Dateisystem vorhanden sind. + +Im Fall einer \optname{location}, die mit \texttt{http:} oder \texttt{ftp:} beginnt, werden +das Zeichen `\texttt{/}' und/oder die Zeichenkette `\texttt{/tlpkg}' am Ende ignoriert. Sie können hier +z.\,B. einen bestimmten \CTAN-Server auswählen, was dann in etwa so aussehen würde: +\url{http://ctan.example.org/tex-archive/texlive/tlnet/2008}. +Hier müssen Sie natürlich einen echten Servernamen und den für diesen Server gültigen Pfad einsetzen +(eine Liste von \CTAN-Servern finden Sie unter \url{http://ctan.org/mirrors}). +Die Standardvorgabe ist, +über \url{http://mirror.ctan.org} einen Server automatisch auszuwählen. +Einmal ausgewählt, wird dieser allerdings zum Herunterladen aller Komponenten verwendet. + +\subsection{Aufgaben im Anschluss an die Installation} +\label{sec:postinstall} + +Je nach System kann es notwendig sein, dass im Anschluss an die Installation noch einige Kleinigkeiten +erledigt werden müssen. + +\subsubsection{Windows} +Benutzer von Windows sind hier in der glücklichen Position, dass das Installationsprogramm alles komplett +erledigt haben sollte. + +\subsubsection{Unix, falls symbolische Links angelegt wurden} + +Wenn Sie bei der Installation angegeben haben, dass und wo symbolische Links angelegt werden sollten +(s.\,Abschnitt~\ref{sec:options}), sollten hier auch keine Nacharbeiten mehr notwendig sein. + +\subsubsection{Umgebungsvariablen für Unix} +\label{sec:env} + +Das Verzeichnis mit den ausführbaren Programmen von \TL muss sich im Suchpfad des Systems befinden. +Jedes unterstützte System besitzt ein eigenes Verzeichnis unterhalb von \dirname{TEXDIR/bin}, deren +Namen Sie in Abb.~\ref{fig:bin-text} finden. + +Weiterhin können Sie die Verzeichnisse mit den Manual-Pages und Info-Dateien zu den entsprechenden +Suchpfaden für Dokumentation hinzu fügen, wenn Sie es wünschen. + +Für Systeme mit einer Bourne-kompatiblen Shell wie \prog{bash} ist hier am Beispiel von GNU/Linux +aufgeführt, wie die Befehle zum Setzen der Umgebungsvariablen (z.\,B. in \filename{$HOME/.profile}) +aussehen könnten: + +\begin{sverbatim} +export PATH=/usr/local/texlive/2008/bin/i386-linux:$PATH +export MANPATH=/usr/local/texlive/2008/texmf/doc/man:$MANPATH +export INFOPATH=/usr/local/texlive/2008/texmf/doc/info:$INFOPATH +\end{sverbatim} + +Für \prog{csh} oder \prog{tcsh} erfolgt die Konfiguration in der Regel in der Datei~\filename{$HOME/.cshrc} +und könnte so aussehen: + +\begin{sverbatim} +setenv PATH /usr/local/texlive/2008/bin/i386-linux:$PATH +setenv MANPATH /usr/local/texlive/2008/texmf/doc/man:$MANPATH +setenv INFOPATH /usr/local/texlive/2008/texmf/doc/info:$INFOPATH +\end{sverbatim} + +\subsubsection{Systemweites Setzen von Umgebungsvariablen} +\label{sec:envglobal} + +Wenn Sie als Administrator die Umgebungsvariablen global für das gesamte System setzen wollen, +gehen wir davon aus, dass Sie sich mit der grundlegenden Systemadministration auskennen. + +Daher hier nur zwei Hinweise: 1)~schauen Sie nach einer Datei +\filename{/etc/manpath.config}. Falls diese vorhanden ist, sollte es reichen, folgende Zeilen +hinzu zu fügen: + +\begin{sverbatim} +MANPATH_MAP /usr/local/texlive/2008/bin/i386-linux \ + /usr/local/texlive/2008/texmf/doc/man +\end{sverbatim} + +Und 2)~prüfen Sie, ob es auf Ihrem System eine Datei \filename{/etc/environment} gibt, in der die +systemweiten Umgebungsvariablen definiert werden. + +\subsubsection{Benutzen von \protect\TL direkt von DVD} +Üblicherweise verwendet \TL eine Datei \filename{texmf.cnf}, um die Verzeichnisbäume, in denen +sich die Komponenten von \TL befinden, zu identifizieren. Diese Methode benutzt relative Pfade, so +dass Ihr \TL-System funktioniert, wo immer Sie es auch hin installieren, solange die Verzeichnisstruktur +erhalten bleibt. + +Diese Methode funktioniert leider nicht mehr, wenn Sie \TL direkt von der \DVD benutzen wollen. +Da die \DVD ein Nur-Lese-Medium ist, einige der Pfade in \filename{texmf.cnf} aber erst nach der +Installation fest stehen, muss sich diese Datei außerhalb der \DVD befinden. +Aus diesem Grund muss eine Umgebungsvariable \envname{TEXMFCNF} gesetzt werden, +die \TL{} mitteilt, in welchem Verzeichnis sich die Datei \filename{texmf.cnf} befindet. +Zusätzlich muss sich natürlich -- wie im vorigen Abschnitt beschrieben -- das +Verzeichnis der \DVD, in dem sich die passenden ausführbaren Programme befinden, innerhalb des +Suchpfads des Systems befinden. + +Beim Abschluss des Installationsprogramms sollten Sie die notwendigen Informationen erhalten haben, +wie Sie \envname{TEXMFCNF} setzen müssen. Falls Sie dies übersehen haben, der Wert ist +\dirname{$TEXMFSYSVAR/web2c}, wobei im Normalfall \dirname{$TEXMFSYSVAR} auf das Verzeichnis +\dirname{/usr/local/texlive/2008/texmf-var/web2c} verweist. In diesem Fall benötigen Sie also für +die \prog{bash} den Befehl +\begin{sverbatim} +TEXMFCNF=/usr/local/texlive/2008/texmf-var/web2c; export TEXMFCNF +\end{sverbatim} +bzw.\ für [t]csh: +\begin{sverbatim} +setenv TEXMFCNF /usr/local/texlive/2008/texmf-var/web2c +\end{sverbatim} + +\subsubsection{\ConTeXt{} Mark IV} +Das ">alte"< \ConTeXt{} sollte direkt lauffähig sein. Falls Sie das neue \ConTeXt{} ">Mark IV"< +verwenden wollen, sind einige manuelle Nacharbeiten notwendig, die unter +\url{http://wiki.contextgarden.net/Running_Mark_IV} beschrieben sind. + +\subsubsection{Integrieren lokaler bzw.\ Nutzer-spezifischer Makros} +\label{sec:local-personal-macros} + +Wie bereits in Abschnitt~\ref{sec:texmftrees} erwähnt, ist der Verzeichnisbaum \dirname{TEXMFLOCAL} (im +Normalfall \dirname{/usr/local/texlive/texmf-local} oder \verb|C:\Program Files\texlive\texmf-local|) +für lokale Ergänzungen wie Makros und Schriften gedacht, die anschließend allen Benutzern des Systems zur +Verfügung stehen. Weiterhin können Benutzer den Verzeichnisbaum \dirname{TEXMFHOME} (im Normalfall +\dirname{$HOME/texmf} oder \verb|%USERPROFILE%\texmf|) für persönliche Ergänzungen verwenden, ohne +dass andere Benutzer davon beeinflusst werden. +Diese Verzeichnisse sollen über verschiedene Versionen von \TL hinweg identisch sein, so dass ein +Update von \TL auf eine neue Version einfach möglich ist, ohne dass Sie Ihre lokalen Ergänzungen +verlieren. Wir empfehlen Ihnen daher, von der vorgegebenen Verzeichnisstruktur nicht abzuweichen. + +Für beide oben genannte Verzeichnisbäume erwartet \TL eine Verzeichnisstruktur innerhalb des Baums, die +dem \emph{\TeX{} Directory Standard} entspricht, wie er in \url{http://tug.org/tds} bzw. +\filename{texmf/web2c/texmf.cnf} definiert ist. +So gehören Dokumentklassen für \LaTeX{} z.\,B. in ein Verzeichnis +unterhalb von \dirname{TEXMFLOCAL/tex/latex} oder \dirname{TEXMFHOME/tex/latex}. + +Der Verzeichnisbaum \dirname{TEXMFLOCAL} wird zur Laufzeit nicht direkt nach Dateien durchsucht. +Stattdessen wird eine Liste von Dateinamen verwendet, sich sich in einer Datei mit dem Namen~\filename{ls-R} +befindet. Denken Sie also daran, nach Änderungen in diesem Baum diese Dateiliste zu aktualisieren, +entweder mit dem Befehl \cmdname{mktexlsr} oder die Schaltfläche \emph{Reinit file database} in +dem Konfigurationsreiter von \prog{tlmgr} im \GUI-Modus. + +\subsubsection{Integrieren von anderen Schriften} +Die Installation von Schriften, die nicht von \TL sind, ist eine recht komplexe Angelegenheit. Sie sollten +sich bereits gut mit dem System auskennen, bevor Sie sich an diese Aufgabe wagen. Schauen Sie vielleicht +vorher in Abschnitt~\ref{sec:tl-fonts} nach, welche Schriften bereits bei \TL mitgeliefert werden. + +Eine Alternative besteht im Benutzen von \XeTeX (s.\,Abschnitt~\ref{sec:tex-extensions}), bei dem +direkt alle vom Betriebssystem installierten Schriften verwendet werden können, ohne dass die Installation +einer \TeX-Unterstützung notwendig ist. + +\subsection{Testen der Installation} +\label{sec:test-install} + +Nach der Installation von \TL wollen Sie es natürlich benutzen, um möglichst schöne Dokumente zu setzen. + +Dieser Abschnitt beschreibt, wie Sie prüfen können, ob Ihr \TL-System funktioniert. +Die folgenden Beispiele sind für Unix, sollten unter Windows und \MacOSX aber sehr ähnlich sein, abgesehen +davon, dass Sie dort eventuell eine grafische Benutzeroberfläche verwenden. + +\begin{enumerate} + +\item Prüfen Sie, ob Sie das Programm \cmdname{tex} ausführen können: + +\begin{alltt} +> \Ucom{tex -{}-version} +TeX 3.1415926 (Web2C 7.5.7) +kpathsea version 3.5.7 +... +\end{alltt} + +Erhalten Sie als Resultat statt der Versionsnummer die Meldung, dass der Befehl nicht gefunden wurde, +so haben Sie wahrscheinlich vergessen, das Verzeichnis mit den ausführbaren Programmen +in Ihren \envname{PATH} aufzunehmen, s.\,Abschnitt~\ref{sec:env} auf S.\,\pageref{sec:env}. + +\item Eine einfache \LaTeX{}-Datei übersetzen: +\begin{alltt} +> \Ucom{latex sample2e.tex} +This is pdfeTeXk, Version 3.1415926... +... +Output written on sample2e.dvi (3 pages, 7484 bytes). +Transcript written on sample2e.log. +\end{alltt} + +Falls dies schief geht, sind wahrscheinlich noch alte Umgebungsvariablen einer vorigen \TeX-Installation +übrig geblieben. Wir empfehlen, die Umgebungsvariablen, die sich auf \TeX{} beziehen, zu entfernen. +Für eine weitere Analyse können Sie \TeX{} anzeigen lassen, wo es bestimmte Dateien sucht, +siehe ">Fehlersuche"< auf Seite~\pageref{sec:debugging}. + +\item Ergebnis auf dem Bildschirm anschauen: +\begin{alltt} +> \Ucom{xdvi sample2e.dvi} +\end{alltt} +(Unter Windows heißt der Befehlt für den Previewer \cmdname{dviout}.) Nun sollte +sich ein Vorschaufenster mit dem soeben gesetzten Beispieldokument öffnen, das die Grundlagen von +\LaTeX{} erläutert (und das Anfänger tatsächlich auch einmal lesen sollten). +Unter Unix muss ein X-Server laufen, damit \cmdname{xdvi} funktioniert; +falls dies nicht der Fall ist oder die Umgebungsvariable \envname{DISPLAY} falsch gesetzt ist, +erhalten Sie die Fehlermeldung \samp{Can't open display}. + +\item Eine \PS{}-Datei erzeugen: +\begin{alltt} +> \Ucom{dvips sample2e.dvi -o sample2e.ps} +\end{alltt} + +\item Direkt eine \acro{PDF}-Datei erzeugen (statt \dvi{}): +\begin{alltt} +> \Ucom{pdflatex sample2e.tex} +\end{alltt} + +\item Eine \acro{PDF}-Datei anschauen: +\begin{alltt} +> \Ucom{gv sample2e.pdf} +\textrm{or:} +> \Ucom{xpdf sample2e.pdf} +\end{alltt} +Leider sind weder \cmdname{gv} noch \cmdname{xpdf} in \TL{} enthalten, daher müssen diese separat installiert +werden, siehe \url{http://www.gnu.org/software/gv} bzw. +\url{http://www.foolabs.com/xpdf}. +(Sie können natürlich auch andere PDF-Viewer verwenden, beispielsweise den Adobe Reader.) + +\item Weitere nützliche Test-Dateien außer +\filename{sample2e.tex}: + +\begin{ttdescription} +\item [small2e.tex] Einfachere Version von \filename{sample2e}, um den Fehler einzugrenzen, wenn Sie +beim Übersetzen von \filename{sample2e} Probleme haben. +\item [testpage.tex] Hiermit können Sie prüfen, ob Ihr Drucker Ihren Ausdruck horizontal oder vertikal verschiebt. +\item [nfssfont.tex] Zum Testen von Fonts und Erzeugen von Schrifttabellen. +\item [testfont.tex] Erzeugen von Schrifttabellen, aber mit plain \TeX. +\item [story.tex] Das einfachste Testdokument von allen (in plain \TeX{}). +Geben Sie am Ende \samp{\bs bye} ein, wenn nach dem Aufruf von \samp{tex +story.tex} der \code{*} erscheint. +\end{ttdescription} + +\end{enumerate} + +\section{Installation im Netzwerk} +\label{sec:netinstall} + +Bei \TL ist nicht nur vorgesehen, dass es von mehreren Benutzern auf einem System verwendet werden kann, +sondern auch in einem Netzwerk. In der normalen Konfiguration von \TL werden nur relative, keine absoluten +Pfade verwendet. Dies erkennt man an Einstellungen in der Datei \filename{$TEXMFMAIN/web2c/texmf.cnf}, +die Zeilen wie die folgenden enthält, +in denen Verzeichnisse relativ zu den Verzeichnissen lokalisiert werden, +in denen sich die Programme befinden: +\begin{sverbatim} +TEXMFMAIN = $SELFAUTOPARENT/texmf +... +TEXMFLOCAL = $SELFAUTOPARENT/../texmf-local +\end{sverbatim} +Daher ist es im Normalfall ausreichend, +das Programm-Verzeichnis in den Suchpfad des Systems aufzunehmen, +alles weitere bestimmt \TL dann automatisch. + +Daher ist es kein Problem, wenn das Grundverzeichnis von \TL als Netzlaufwerk gemountet ist. Tatsächlich +können Sie \TL sogar zunächst lokal installieren und dann auf ein Netzlaufwerk verschieben. + +Für Benutzer von Windows existiert unter \dirname{texmf-doc/source/texlive/texlive-common/w32client} +ein Beispiel-Skript \filename{install-w32client}, das die Einstellungen im Startmenü von Windows +für das Verwenden von \TL über Netzwerk vornimmt. Dieses Skript wird einfach durch Aufruf von +\filename{install-w32client.bat} im selben Verzeichnis gestartet. + +Mehr Informationen zur Konfiguration von \TL und den benutzten Suchpfaden finden Sie im Abschnitt~\ref{sec:kpathsea}. + +\section{Portables \protect\TL{} auf DVD oder USB-Stick} +\label{sec:portable-unix} + +Im Abschnitt~\ref{sec:fromdvd} wurde beschrieben, wie \TL direkt von einer \DVD benutzt werden kann. +Hierbei werden einige Verzeichnisse auf der Festplatte angelegt. Dies ist wahrscheinlich kein Problem, +wenn Sie dies auf Ihrem eigenen Rechner verwenden, aber es kann anders aussehen, wenn Sie auf einem +fremden Rechner ">zu Gast"< sind. + +Sie können die Stellen, an denen beim Benutzen von \TL von \DVD auf der Festplatte Verzeichnisse +angelegt werden, minimieren. Verwenden Sie unter unter Unix das Skript \filename{tl-portable} oder +unter Windows die Batch-Datei \filename{tl-portable.bat}, so werden beim ersten Start die +Konfigurationsdateien für das Verwenden des Live-Modus von \DVD geschrieben. + +Hierzu wird ausschließlich ein Verzeichnis \dirname{~/.tlportable2008} angelegt, in dem diese Dateien +abgelegt werden. Dies kann einen Moment dauern, aber sobald die Dateien einmal da sind, erfolgt +der Start des portablen Modus über die o.\,a. Programme sehr schnell. Die Konfiguration dieses +Modus erfolgt ausschließlich in dem aktuellen Terminalfenster (bzw.\ für die aktuelle Eingabeaufforderung), +der Rest des Systems bleibt davon völlig unberührt. Sie können problemlos in mehreren Sitzungen +parallel den portablen Modus benutzen. + +Wird hier immer ein Verzeichnis auf der Festplatte angelegt, so ist dies komplett überflüssig, wenn +Sie den portablen Modus von USB-Stick verwenden. Kopieren Sie hierfür alle Dateien, die sich direkt im +Verzeichnis \dirname{texlive} der \DVD befinden, sowie (mindestens) die Verzeichnisse \dirname{bin}, +\dirname{texmf}, \dirname{texmf-dist} und \dirname{tlpkg} komplett auf den USB-Stick (dies kann eine +Weile dauern!). Beim Kopieren auf einen mit FAT32 formatierten Stick verwenden Sie unbedingt die Option +zum Auflösen symbolischer Links (\code{cp -L}). Ein auf dem Stick vorhandenes Verzeichnis \dirname{texmf-local} +wird ebenfalls später erkannt und benutzt. + +Wenn Sie nun das Skript \filename{tl-portable} auf dem USB-Stick (wie oben für die \DVD beschrieben) +verwenden, erkennt das Skript, dass der USB-Stick beschreibbar ist und verwendet diesen statt der +Festplatte für die Konfigurationsdateien. + +\section{\cmdname{tlmgr}: Installation verwalten} +\label{sec:tlmgr} + +\begin{figure}[tb] +\tlpng{tlmgr-gui}{\linewidth} +\caption{\prog{tlmgr} im \GUI-Modus. Die Liste der Pakete, Collections und Schemas + wird erst nach Klicken auf ">Load"< angezeigt.}\label{fig:tlmgr-gui} +\end{figure} + +\begin{figure}[tb] +\tlpng{tlmgr-config}{\linewidth} +\caption{\texttt{tlmgr} im \GUI-Modus: Reiter Konfiguration}\label{fig:tlmgr-config} +\end{figure} + +Bei der Installation von \TL wird auch das Programm~\prog{tlmgr} installiert, mit dem Sie anschließend +Ihr \TL-System verwalten können. Die hierfür bisher verwendeten Programme~\prog{updmap}, +\prog{fmtutil} und \prog{texconfig} sind zwar noch vorhanden, werden aber in der Zukunft durch +\prog{tlmgr} ersetzt. Verwenden Sie daher heute schon \prog{tlmgr}. Mit \prog{tlmgr} können Sie +folgende Aufgaben erledigen: +\begin{itemize*} +\item Verfügbare Schemas, Collections und Pakete anzeigen. +\item Installieren, aktualisieren, entfernen, Backup und Restore einzelner Pakete, auf Wunsch mit + Berücksichtigung von Paketabhängigkeiten. +\item Suchen nach Paketen. +\item Anzeigen der Systeme, unter denen \TL läuft; installieren von Binaries für weitere Systeme. +\item Anpassen der Installation, wie Ändern der Papiergröße oder des Quellverzeichnisses für Komponenten + (s.\,Abschnitt~\ref{sec:location}). +\end{itemize*} +\textit{Warning:} \prog{tlmgr} ist für den Live-Modus, bei dem \TL von \DVD genutzt wird, weder gedacht +noch getestet. + +\subsection{\cmdname{tlmgr} im grafischen Modus} +\prog{tlmgr} im \GUI-Modus wird durch +\begin{alltt} +> \Ucom{tlmgr -gui} +\end{alltt} +gestartet. Unter Windows finden Sie das Programm im Start menu: \texttt{Start}, \texttt{Programme}, +\texttt{TeX Live 2008}, \texttt{TeX Live Manager}. Nach Klicken auf ">Load"< +wird eine Liste aller verfügbaren und installierten (letztere durch ">(i)"< gekennzeichnet) angezeigt. Dies +setzt voraus, dass das Verzeichnis, aus dem \TL die Pakete lädt, vorhanden bzw.\ erreichbar ist. + +Abb.~\ref{fig:tlmgr-config} stellt den Reiter zur Konfiguration von \TL dar. + +\subsection{Beispiel zur Verwendung von \cmdname{tlmgr} über Kommandozeile} + +Das folgende Beispiel demonstriert, wie mehrere Pakete +zur Installation hinzu gefügt werden. +Hierbei wird eine andere Adresse zum Herunterladen verwendet. + +\begin{alltt} +> \Ucom{tlmgr -location http://172.16.18.1/tldev install collection-xetex xkeyval} +\end{alltt} +Dies liefert die folgende Ausgabe: +\begin{fverbatim} +install: collection-xetex +install: arabxetex +install: euenc +install: bidi +install: fontspec +install: fontwrap +install: ifxetex +install: philokalia +install: polyglossia +install: xecyr +install: xecyr.i386-linux +install: xepersian +install: xetex +install: xetexconfig +install: xetex.i386-linux +running post install action for xetex +install: xetex-def +install: xetex-pstricks +install: xetexfontinfo +install: xltxtra +install: xunicode +install: xkeyval +running mktexlsr +mktexlsr: Updating /usr/local/texlive/2008/texmf/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-config/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-dist/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-doc/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/../texmf-local/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-var/ls-R... +mktexlsr: Done. +regenerating fmtutil.cnf +running fmtutil-sys --missing +... +Transcript written on xelatex.log. +fmtutil: /usr/local/texlive/2008/texmf-var/web2c/xetex/xelatex.fmt installed. +\end{fverbatim} + +Wie man sieht, beachtet \prog{tlmgr} die Abhängigkeiten von Paketen und installiert im obigen +Beispiel von \XeTeX{} benötigte Komponenten nach. Weiterhin werden automatisch im Anschluss +die Dateilisten der Verzeichnisbäume aktualisiert und fehlende Formate generiert. + +Im folgenden Beispiel wird die Unterstützung für eine weitere Sprache installiert. Im Anschluss +werden automatisch die Formatdateien neu generiert, damit die neuen Trennmuster eingebunden sind. +\begin{alltt} +> \Ucom{tlmgr install collection-langdutch} +\end{alltt} + +Eigenschaften eines Pakets anzeigen: +\begin{alltt} +> \Ucom{tlmgr show collection-wintools} +\end{alltt} + +Hier erhält man folgende Ausgabe: +\begin{fverbatim} +Package: collection-wintools +Category: Collection +ShortDesc: Windows support programs +LongDesc: Utilities for Windows, since they are not readily available there: + gzip, chktex, jpeg2ps, unzip, wget, xpdf. +Installed: Yes +\end{fverbatim} + +Aktualisieren der kompletten Installation: +\begin{alltt} +> \Ucom{tlmgr update -all} +\end{alltt} +Wenn Sie erst wissen wollen, was auf Sie zu kommt, können Sie zunächst folgendes ausprobieren: +\begin{alltt} +> \Ucom{tlmgr update -all -dry-run} +\end{alltt} +oder +\begin{alltt} +> \Ucom{tlmgr update -list} +\end{alltt} + +Zum Anzeigen aller Optionen: +\begin{alltt} +> \Ucom{tlmgr -help} +\end{alltt} + +\section{Hinweise zu Windows} +\label{sec:windows} + +Das Installationsprogramm von \TL\ läuft sowohl unter Windows als auch Unix. Dies war nur dadurch möglich, +dass ältere Versionen von Windows nicht mehr unterstützt werden. Daher kann \TL\ nur noch ab Windows 2000 oder +später installiert werden. + + +\subsection{Windows-spezifische Dinge} +\label{sec:winfeatures} + +Unter Windows kümmert sich das Installationsprogramm auch um folgende Dinge: +\begin{description} +\item[Menüs und Verknüpfungen.] Im Startmenü wird ein Menü ">\TL{}"< hinzu gefügt. Hier sind Einträge für + die grafischen Anwendungen (\prog{tlmgr}, \prog{texdoctk}, den PS\_View PostScript-Previewer) + und einige Verknüpfungen zur Dokumentation vorhanden. Für PS\_View wird eine Verknüpfung auf dem + Desktop angelegt, auf die Sie \PS-Dateien per Drag~\& Drop ziehen können, um diese zu betrachten. +\item[Automatisches Setzen der UmgebungsVariablen.] Hierdurch ist das Setzen dieser Variablen + von Hand überflüssig geworden. +\item[Uninstaller.] Es wird ein Eintrag zum Entfernen von \TL in der Systemsteuerung im Punkt Software angelegt. + Alternativ können Sie \TL über das Programm~\prog{tlmgr} deinstallieren. +\end{description} + +\subsection{Zusätzlich enthaltene Programme} + +\begin{figure}[tb] +\tlpng{psview}{.6\linewidth} +\caption{PS\_View: Anzeige mit hoher Vergrößerung}\label{fig:psview} +\end{figure} + +Zusätzlich werden unter Windows einige Programme installiert, die unter Windows meist noch nicht verfügbar +sind: +\begin{description} +\item[Perl und Ghostscript.] Da Perl und Ghostscript für \TL sehr wichtig ist, werden diese + unter Windows mitgeliefert und werden intern von \TL benutzt. Die in \TL enthaltenen Programme, die + diese Komponenten benötigen, ">wissen"< wo sich diese befinden, ohne dass diese im System durch + Umgebungsvariablen oder Einträge in der Registry sichtbar sind. Es handelt sich um für \TL abgespeckte + Versionen, die zu keinen Konflikten mit eventuell bereits vorhandenen Installationen von Perl und Ghostscript + führen sollten. +\item[Tools für die Kommandozeile.] Für einige unter Unix übliche Programme werden Portierungen für Windows + mitgeliefert. Dies sind z.\,B. \cmdname{gzip}, \cmdname{chktex}, + \cmdname{jpeg2ps}, \cmdname{unzip}, \cmdname{wget} und einige Programme für die Kommandozeile aus der + \cmdname{xpdf}-Suite. (Vom + \cmdname{xpdf}-Viewer selbst gibt es keine Version für Windows, aber der + Sumatra \acro{PDF}-Viewer basiert auf \cmdname{xpdf}: + \url{http://blog.kowalczyk.info/software/sumatrapdf}.) +\item[\texttt{fc-cache}] dient \XeTeX{} zur effizienteren Benutzung von Schriften. +\item[PS\_View.] Weiterhin wird PS\_View installiert, ein neuer PostScript-Viewer, der Freie Software ist, + s.\,Abb.~\ref{fig:psview}. +%\end{description} +% +%\begin{description} +\item[Das Verzeichnis \texttt{support}] wurde bereits in + Abschnitt~\ref{sec:tld} erwähnt. Es enthält einige Programme, die im Zusammenhang mit + \TeX{} nützlich sind, insbesondere einige Editoren mit \TeX-Modus und Benutzeroberflächen für \TeX{}. + Die in diesem Verzeichnis enthaltene Software wird nicht vom Installationsprogramm mit installiert. + Weiterhin findet sich dort der \dvi{}-Previewer \cmdname{dviout}, siehe nächster Abschnitt. +\end{description} + +\subsection{Der Dviout-Previewer} + +Von dieser Version von \TL{} wird leider kein \dvi{}-Previewer für Windows mitinstalliert. +Allerdings können Sie das Programm \prog{dviout} von +Toshio Oshima aus dem Verzeichnis \path{support/dviout/} installieren. Im selben Verzeichnis findet sich +die Datei \filename{README} mit einer kurzen Anleitung zur Installation und Konfiguration von +\prog{dviout} für \TL. Bitte beachten Sie diese Anleitung unbedingt! + +Wenn Sie am Anfang Dokumente mit \cmdname{dviout} anschauen, werden häufig noch Fonts generiert, da +keine fertigen Fontdateien für den Bildschirm mitgeliefert werden. Je mehr Fonts generiert wurden, desto +seltener müssen Schriften nachgeneriert werden, so dass dieser Effekt nach einiger Zeit nur noch selten +auftreten wird. Weitere Informationen finden Sie in der (sehr guten) Online-Hilfe. + +\subsection{Link zu zusätzlicher Software} +Hier einige URLs, hinter denen sich nützliche Software verbirgt: +\begin{description} +\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} +\item[Perl] \url{http://www.perl.org/} mit + Zusatzpaketen von \acro{CPAN}, \url{http://www.cpan.org/}. +\item[ImageMagick] \url{http://www.imagemagick.com}, zum Manipulieren + und Konvertieren von Grafikdateien. +\item[NetPBM] \url{http://netpbm.sourceforge.net/}, ebenfalls zum + Konvertieren von Grafikdateien. +\item[Editoren mit \TeX-Unterstützung] Dies ist lediglich eine grobe Auswahl, + und bekanntlich sind die Geschmäcker verschieden, bei Editoren wie + beim Essen. + \begin{itemize*} + \item \cmdname{GNU Emacs} gibt es auch für Windows, siehe + \url{http://www.gnu.org/software/emacs/windows/ntemacs.html}. + \item \cmdname{Emacs} mit Auc\TeX\ für Windows wird im + \path{support}-Verzeichnis von \TL mitgeliefert. Die Homepage + findet sich unter + \url{http://www.gnu.org/software/auctex}. + \item \cmdname{WinShell} findet sich ebenfalls im \path|support|-Verzeichnis. + Die Homepage lautet \url{http://www.winshell.de}. + \item \cmdname{WinEdt} ist Shareware und verfügbar von + \url{http://www.winedt.com}. + \item \cmdname{Vim} ist freie Software, verfügbar von + \url{http://www.vim.org}. + \item TeXnicCenter ist ebenfalls freie Software, verfügbar von + \url{http://www.toolscenter.org} und Teil von pro\TeX{}t. + \item \cmdname{LEd} ist verfügbar von \url{http://www.ctan.org/support/LEd}. + \item \cmdname{SciTE} ist verfügbar von + \url{http://www.scintilla.org/SciTE.html}. + \end{itemize*} +\end{description} + +\subsection{User Profile unter Windows} +\label{sec:winhome} + +Das Gegenstück von Windows zum HOME-Verzeichnis unter Unix ist das +Verzeichnis \verb|%USERPROFILE%|. Unter Windows XP und Windows 2000 liegt +es meist im Verzeichnis \verb|C:\Documente und Einstellungen\|, unter +Windows Vista \verb|C:\Users\|. In der Datei +\filename{texmf.cnf} und in \KPS{} allgemein wird \verb|~| +sowohl unter Unix und Windows korrekt aufgelöst. + +\subsection{Die Windows-Registry} +\label{sec:registry} + +Windows verwaltet fast all seine Konfigurationseinstellungen in der +Registry. Diese besteht aus einem hierarchisch aufgebauten Baum +von Schlüsseln, wobei mehrere dieser Registry-Bäume existieren. +Die wichtigsten sind \path{HKEY_CURRENT_USER} und \path{HKEY_LOCAL_MACHINE}, +oft abgekürzt als \path{HKCU} bzw.\ \path{HKLM}. +Der \path{HKCU}-Teil der Registry wird im Home-Verzeichnis des Benutzers +gespeichert (s.\,Abschnitt~\ref{sec:winhome}). \path{HKLM} liegt im +Normalfall in einem Unterverzeichnis des Windows-Verzeichnisses. + +In einigen Fällen sind Systeminformationen aus Umgebungsvariablen +ersichtlich, in vielen anderen Fällen liegen diese Informationen +aber in der Registry. + +\subsection{Windows Permissions} +\label{sec:winpermissions} + +In neueren Versionen von Windows wird zwischen normalen Benutzern und +Administratoren unterschieden, wobei nur letztere freien Zugang auf +alle Teile des Betriebsystems haben. Im Gegensatz zu Unix ist es in der +Praxis allerdings häufig so, dass Benutzer zur Klasse der Administratoren +gehören und daher doch alle Freiheiten haben. Trotzdem haben wir einigen +Aufwand getrieben, damit \TL auch unter Windows ohne Administrator-Rechte +installiert werden kann. + +Falls der Benutzer, der \TL installiert, Administrator-Rechte besitzt, +wird \TL für alle Benutzer des Systems installiert, d.\,h. Verknüpfungen, +Menüs und Systemeinträge für alle Nutzer angelegt. Ansonsten werden diese +nur für den aktuellen Benutzer angelegt. Falls Sie Administrator sind, +\TL aber trotzdem nur für sich und nicht für alle installieren wollen, +können Sie dem Programm~\prog{install-tl} die Option~\optname{non-admin} +mit geben. + +Unabhängig davon wird grundsätzlich angenommen, dass das Wurzelverzeichnis +von \TL unter \verb|%PROGRAMFILES%| liegen soll. Allerdings testet das +Installationsprogramm, ob dieses Verzeichnis für den aktuellen Benutzer +schreibbar ist. + +Ein Problem entsteht, wenn \TL ohne Administrator-Rechte installiert +wird und sich bereits ein \TeX{}-System im systemweiten Suchpfad +befindet. Windows benutzt zuerst den Suchpfad des Systems, erst dann +den spezifischen Suchpfad des Nutzers, so dass hier immer zuerst +das alte \TeX-System gefunden wird. Als Workaround wird hier eine +Verknüpfung mit einer Eingabeaufforderung erzeugt, in der das +Programmverzeichnis von \TL im Suchpfad vor den Standard\-such\-pfad +geschrieben wird. Dies bedeutet, dass in diesem Fall nur in einer +Eingabeaufforderung verfügbar ist, die über diese Verknüpfung gestartet +wird. + +% ============================================================== +% don't use \Webc so the \uppercase in the headline works. +\section[Anleitung zum Web2C-System]{Anleitung zum \Webc-System} + +{\Webc} besteht aus einer Reihe von Programmen, die zusammen ein komplettes +\TeX-System darstellen. Dazu gehören natürlich \TeX, +\MF, \MP, {\BibTeX} usw. + +Die erste Implementierung eines \TeX-Systems +in der Programmiersprache C stammt von Tomas~Rokicki und datiert zurück in das +Jahr 1987. Rokicki benutzte als Basis sog. Change-Files unter \acro{UNIX}, die ursprünglich von +Howard~Trickey und Pavel~Curtis entwickelt wurden. Tim~Morgan hat dieses +System, für das der Name Web-to-C\@ eingeführt wurde, gepflegt. +1990 hat Karl~Berry mit Unterstützung vieler Helfer die Weiterentwicklung +übernommen und 1997 an Olaf~Weber weitergegeben, der es 2006 wieder an +Karl zurück gab. + +\Webc{} läuft unter \acro{UNIX}, 32-bit-Versionen von Windows, \MacOSX{} +und auf weiteren Betriebssystemen. Es benutzt die +Original-Quelldateien von Donald E.~Knuth und weitere in der +Sprache {\web} entwickelte Programme als Basis und übersetzt diese +in C-Quell-Code. Darüber hinaus bietet das System viele Makros und +Funktionen zur Nutzung der originalen \TeX-Software. Hier eine +Liste der Basisprogramme eines \TeX-Systems: + +\begin{description} +%\renewcommand{\makelabel}[1]{\descriptionlabel{\mdseries\cmdname{#1}}} +\item[bibtex] Verwalten von Bibliographien +\item[dmp] \cmdname{troff}-nach-MPX-Konverter (\MP-Bilder) +\item[dvicopy] Umwandeln von virtuellen Zeichensätzen in DVI-Dateien +\item[dvitomp] DVI-nach-MPX-Konverter (\MP-Bilder) +\item[dvitype] Textanzeige aus DVI-Dateien +\item[gftodvi] Erzeugen von Prüfausgaben für Zeichensätze +\item[gftopk] Packen von Zeichensätzen +\item[gftype] Anzeige von Zeichensätzen als ASCII-Graphik +\item[makempx] Anzeige von \MP-Beschriftungen +\item[mf] Zeichensatzerzeugung +\item[mft] formatierte Ausgabe von \MF-Quellen +\item[mpost] \MF-ähnliches Grafikprogramm +\item[mpto] Extrahieren von \MP-Beschriftungen +\item[newer] Vergleich von Dateierstellungsdaten +\item[patgen] Erzeugen von Trennmustern +\item[pktogf] Entpacken von Zeichensätzen +\item[pktype] Anzeige gepackter Zeichensätze +\item[pltotf] Umwandeln von Property-Listen in \file{.tfm}-Dateien +\item[pooltype] Anzeige der Bildschirmtexte eines WEB-Programms +\item[tangle] Konverter {\web} nach Pascal +\item[tex] \TeX-Programm +\item[tftopl] Umwandeln einer \file{.tfm}-Datei in eine Property-Liste +\item[vftovp] Umwandeln eines virtuellen Zeichensatzes in eine Property-Liste +\item[vptovf] Umwandeln einer Property-Liste in einen virtuellen Zeichensatz +\item[weave] \web-Code als \TeX-Dokumentation +\end{description} + +Die genaue Funktionsweise und die möglichen Parameter sind der +Beschreibung der jeweiligen Pakete bzw.\ der \Webc-Dokumentation zu entnehmen. +Trotzdem wird ein Überblick über Zusammenspiel und Funktionsweise der +\Webc-Programme Ihnen sicherlich helfen, besser mit dem System zurechtzukommen. + +Zunächst verstehen alle Programme die grundlegenden Parameter der +\acro{GNU}-Software: + +\begin{description} +\item[\texttt{-{}-help}] kurzer Hilfstext +\item[\texttt{-{}-verbose}] ausführliche Ausgaben beim Programmablauf +\item[\texttt{-{}-version}] Ausgabe der Versionsnummer +\end{description} + +Die Programme des \Webc-Systems benutzen zum Lokalisieren der benötigten +Dateien im Dateisystem die \KPS-Bibliothek (\url{http://tug.org/kpathsea}). Diese Bibliothek optimiert und +beschleunigt den Suchprozess im Dateisystem. Ihre Arbeitsweise wird durch +einige Umgebungsvariablen und eine Kon"-fi"-gu"-ra"-tions"-da"-tei gesteuert. +\Webc~7.5 kann mehr als einen Dateibaum gleichzeitig verwalten und ermöglicht +somit die schon beschriebene \TL-Installation unter Verwendung der +\acro{CDROM} oder {\DVD} mit der Ablage modifizierter Konfigurationsdateien +und zusätzlicher Zeichensätze in einem zweiten Dateibaum. Die Suche +nach Dateien wird durch die Analyse der Datei \file{ls-R} beschleunigt, +die in jedem Wurzelverzeichnis eines \TeX-Dateibaums vorhanden ist. +Sie enthält für jede Datei die genaue Position im Dateibaum relativ +zum Wurzelverzeichnis. + +% ------------------------------------------------------------- +\subsection[Dateisuche mit der Kpathsea-Bibliothek]{Dateisuche mit der \protect\KPS-Bibliothek} +\label{sec:kpathsea} + +Wir beschreiben zunächst den grundlegenden Suchmechanismus der \KPS-Bibliothek. + +Ein \emph{Suchpfad} ist eine durch Kommata oder Semikola getrennte Liste von +\emph{Pfadkomponenten}, die üblicherweise Verzeichnisnamen darstellen. +Ein Suchpfad kann sich aus vielen Komponenten zusammensetzen. Die Suche nach +einer Datei \samp{my-file} über den Suchpfad \samp{.:/dir} bewirkt, dass +{\KPS} jede Komponente nacheinander überprüft, also zunächst +\samp{./my-file} und dann \samp{/dir/my-file}. Als Ergebnis wird entweder die +erste gefundene Datei oder eine Liste aller passenden Dateien geliefert. + +Um auf allen Dateisystemen effizient arbeiten zu können, verwendet {\KPS} ggf. andere +Datei-/""Verzeich"-nis-Separatoren als \samp{:} und \samp{/}. + +Beim Überprüfen einer Pfadkomponente \var{p} überprüft {\KPS} zunächst, +ob eine Dateinamen"=Datenbank (siehe auch Dateinamen"=Datenbank auf +Seite~\pageref{sec:filename-database}) für die Pfadkomponente zuständig ist, +d.\,h. beispielsweise steht die Datenbank in einem Verzeichnis, das im Pfad +vor der zu überprüfenden Komponente \var{p} steht. In diesem Fall wird +zur Bestimmung der Position der gesuchten Datei die Datenbank herangezogen. + +Nur wenn keine passende Datenbank existiert oder wenn die Datei nicht +in der Datenbank gefunden wird, durchsucht {\KPS} das Dateisystem. Diese +zeitaufwändige Suche kann über die Spezifikation der Pfadkomponente \var{p} +mit dem Präfix \samp{!!}\ unterbunden werden. Zur Suche erzeugt {\KPS} eine +Liste der Verzeichnisse, die im Pfadelement enthalten sind, und durchsucht +jedes dieser Verzeichnisse nach der gesuchten Datei. + +Für Dateien kann auch ein Schalter \samp{file~must~exist} gesetzt +werden (">Datei muss vorhanden sein"<). Wenn dieser Schalter nicht +gesetzt ist und beispielsweise über das \TeX-Kommando +\cs{openin} eine VF-Datei wie \file{cmr10.vf} gelesen werden +soll, wäre es falsch, nach dieser Datei zu suchen, weil es sie gar +nicht gibt. Speziell für neu installierte VF-Dateien sollten Sie +also unbedingt die Dateinamen"=Datenbank (\cmdname{ls-R}) +aktualisieren, weil die Dateien sonst nicht gelesen werden und +kein Fehler angezeigt wird. Dieser Vorgang wiederholt sich für jede +Komponente eines Suchpfades: zunächst wird die Datenbank +überprüft, danach ggf. das Dateisystem. Wird die Datei gefunden, +stoppt die Suche (normalerweise) und als Ergebnis wird der komplette Pfad zur +gesuchten Datei ausgegeben. + +Außer Verzeichnisnamen dürfen Pfadkomponenten für {\KPS} folgende +Elemente enthalten: (verschachtelte) Vorgaben, Umgebungsvariablen, +Werte aus der Konfigurationsdatei, Home-Verzeich"-nisse von +Benutzern und Startverzeichnisse für eine rekursive Suche. Diese +Elemente werden vor einer Dateisuche von {\KPS} in gewöhnliche +Verzeichnis- oder Dateinamen expandiert. Diese Expansion wird in +den folgenden Abschnitten erklärt, und zwar genau in der +Reihenfolge, wie die Elemente auch von {\KPS} bearbeitet werden. + +Beachten Sie, dass {\KPS} bei absoluten und explizit relativen Komponenten, +d.\,h. wenn die Komponente mit den Zeichen \samp{/}, \samp{./} oder +\samp{../} beginnt, nur überprüft, ob die Datei existiert. + +\ifSingleColumn +\else + +\begin{figure*}[tp] +\verbatiminput{examples/ex5.tex} +\setlength{\abovecaptionskip}{0pt} + \caption{An illustrative configuration file sample} + \label{fig:config-sample} +\end{figure*} +\fi + +% .............................................................. +\subsubsection{Bestandteile von Pfadkomponenten}\label{Path-sources} +\label{sec:path-sources} + +Ein Suchpfad kann aus vielen verschiedenen Bestandteilen aufgebaut werden. +Dies sind in der Reihenfolge, wie {\KPS} sie auswertet: + +\begin{enumerate} +\item + eine benutzerdefinierte Umgebungsvariable, z.\,B. \envname{TEXINPUTS}: + Wird an den Inhalt der Variablen ein Punkt und ein Programmname angehängt, wie + beispielsweise bei \envname{TEXINPUTS.latex}, hat diese Form Vorrang + vor den ">gewöhnlichen"< Variablen. +\item + Einträge aus programmspezifischen Konfigurationsdateien, + beispielsweise zum Programm {\dvips} eine Zeile \samp{S /a:/b} + in der Konfigurationsdatei \file{config.ps} +\item + Einträge aus der \KPS-Konfigurationsdatei \file{texmf.cnf}, + z.\,B. \samp{TEXINPUTS=/c:/d} (siehe folgenden Text) +\item + Einstellung beim Übersetzen der Programme +\end{enumerate} + +Unter Verwendung der Parameter zur Fehlersuche können Sie sich diese +Werte für einen Suchpfad auch anzeigen lassen. (Siehe dazu den Abschnitt +Fehlersuche auf Seite~\pageref{sec:debugging}.) + +% .............................................................. +\subsubsection{Konfigurationsdateien} + +%\tolerance=3500 +Die \KPS-Bibliothek liest zur Laufzeit die \emph{Konfigurationsdateien} mit den Namen +\file{texmf.cnf}. Der zugehörige Suchpfad zum Auf"|finden dieser +Konfigurationsdateien steht in der Umgebungsvariablen \envname{TEXMFCNF} +(die Voreinstellung ist \file{texmf/web2c}). {\KPS} liest \emph{alle} +Dateien mit den Namen \file{texmf.cnf}, die es in diesem Suchpfad findet. +Die zuerst gelesenen Definitionen haben dabei Vorrang vor später gelesenen +Werten. +Wenn der Suchpfad auf \dirname{.:\$TEXMF} steht, überschreiben die Einstellungen +in \file{./texmf.cnf} diejenigen in \dirname{\$TEXMF/texmf.cnf}. + +%\tolerance=1500 + +Im Folgenden wird die Syntax der Datei \file{texmf.cnf} angegeben. +Konsultieren Sie zum besseren Verständnis beim Lesen die auf der +{\acro{CDROM}} oder {\DVD} enthaltene Konfigurationsdatei. +%, die ab Seite~\pageref{app:texmf.cnf} im Anhang dieser Anleitung +% abgedruckt ist. + +\begin{itemize} +\item + Kommentare beginnen mit einem \samp{\%} und erstrecken sich bis zum + Zeilenende. +\item + Leerzeilen werden überlesen. +\item + Ein \samp{\bs} am Zeilenende fasst die aktuelle mit der folgenden Zeile + zusammen. Leerraum in der Folgezeile wird \emph{nicht} überlesen. +\item + Sonstige Zeilen haben den folgenden Aufbau: + +\begin{alltt} + \var{Variable}[.\var{Programmname}] [=] \var{Wert} +\end{alltt}% + + Das Zeichen ">="< und umgebender Leerraum dürfen entfallen. +\item + Der Name von \var{Variable} kann alle Zeichen außer Leerzeichen, + \samp{=} und \samp{.} enthalten. Verwenden Sie am besten nur die Zeichen + \samp{A-Za-z\_}. +\item + Wenn das Suffix ">\code{.\var{Programmname}}"< angegeben wird, gilt die + Variable nur für das entsprechende Programm ">\var{Programmname}"< oder + ">\code{\var{Programmname}.exe}"<. Auf diese Weise können + beispielsweise verschiedene + \TeX-Formate mit unterschiedlichen Suchpfaden arbeiten. +\item + \texttt{\var{Wert}} darf alle Zeichen außer \texttt{\%} und \texttt{@} + enthalten. + Die Einschränkung der Werte auf bestimmte Programme über ein Suffix + ist nicht zulässig. Ein \samp{;} in \texttt{\var{Wert}} wird unter + \acro{UNIX} in \samp{:} umgewandelt. Dadurch ist die Verwendung der gleichen + Konfigurationsdateien für \acro{UNIX} und \acro{DOS}/""Windows"=Systeme möglich. +\item + Die Definitionen werden komplett eingelesen, bevor eine Expansion + stattfindet. Dadurch können Sie die Variable schon vor Ihrer Definition + referieren. +\end{itemize} + +Der Ausschnitt einer Konfigurationsdatei demonstriert diese +Möglichkeiten. +\ifSingleColumn +\verbatiminput{examples/ex5.tex} +\else +Betrachten Sie Abbildung~\ref{fig:config-sample}. +\fi + +% .............................................................. +\subsubsection{Expansion von Pfadkomponenten} +\label{sec:path-expansion} + +{\KPS} verwendet in Suchpfaden ähnliche Zeichen und Konstrukte wie +\acro{UNIX}-Shells. Beispielsweise wird die Definition +\verb|~$USER/{foo,bar}//baz| in alle Unterverzeichnisse von \file{foo} und +\file{bar} unterhalb vom Home-Verzeichnis von \dirname{\$USER} expandiert, +die eine Datei oder ein Unterverzeichnis namens \file{baz} enthalten. Der +Expansionsmechanismus wird im Folgenden erklärt. + +% .............................................................. +\subsubsection{Expansion der Voreinstellungen} +\label{sec:default-expansion} + +Wenn der Suchpfad mit der höchsten Priorität (siehe hierzu ">Bestandteile von +Pfadkomponenten"< auf Seite~\pageref{sec:path-sources}) einen zusätzlichen +(vorangestellten, nachgestellten oder verdoppelten) Doppelpunkt enthält, +wird an dieser Stelle der Suchpfad eingefügt, der als nächstes in der +Hierarchie folgt. Auch bei diesem gilt dieselbe Regel. Wenn beispielsweise +die Umgebungsvariable + +\begin{alltt} +> \Ucom{setenv TEXINPUTS /home/karl:} +\end{alltt} + +gesetzt wird (hier: C-Shell) und in \file{texmf.cnf} die Variable +\code{TEXINPUTS} folgenden Wert erhält + +\begin{alltt} + .:\$TEXMF//tex +\end{alltt} + +dann lautet der Suchpfad schließlich: + +\begin{alltt} + /home/karl:.:\$TEXMF//tex +\end{alltt} + +Da es sinnlos wäre, denselben Pfad mehrfach einzufügen, wird die Ersetzung +nur einmal vorgenommen, und zwar in der Reihenfolge vorne, hinten und +Mitte. Mehrfach verdoppelte Doppelpunkte bleiben unverändert. + +% .............................................................. +\subsubsection{Expansion geschweifter Klammern} + +Die Expansion geschweifter Klammern ist zur Definition mehrerer +\TeX-Hierarchien sehr nützlich. Beispielsweise wird |v{a,b}w| +zu |vaw:vbw|. Verschachtelungen sind dabei erlaubt. +Diese Technik wird dazu benutzt, durch eine Zuweisung an +\code{\$TEXMF} verschiedene \TeX-Hierarchien einzuführen. +Als Beispiel finden Sie in \file{texmf.cnf} folgende Definition +(etwas gekürzt, tatsächlich ist es etwas komplexer): +%(Zeile 75): %%%% to be checked !!!! checked&corrected vrws 01.06.05 + +\begin{verbatim} + TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN} +\end{verbatim} + +Eine Anwendung wie + +\begin{verbatim} + TEXINPUTS = .;$TEXMF/tex// +\end{verbatim} +%$ +führt dann dazu, dass erst im aktuellen Verzeichnis gesucht wird, dann +im gesamten Dateibaum \code{\$TEXMFHOME/tex} und \code{\$TEXMFLOCAL/tex} +(auf der Festplatte) und +schließlich im gesamten Dateibaum \dirname{\$TEXMFVAR/tex} sowie +\code{\$TEXMFMAIN/tex} (nur in der Datenbank \file{ls-R}) +durchsucht wird. Dadurch kann man bequem +zwei parallel installierte \TeX-Hierarchien durchsuchen, +beispielsweise eine unveränderliche auf \acro{CDROM}/{\DVD} und eine dynamisch +angepasste auf Festplatte, in der neue Programmversionen und zusätzliche +Zeichensätze installiert werden. Durch die Verwendung der Variablen +\code{\$TEXMF} in allen Definitionen wird grundsätzlich zuerst der +neuere Dateibaum durchsucht. + +% .............................................................. +\subsubsection{Expansion von Unterverzeichnissen} +\label{sec:subdirectory-expansion} + +Zwei oder mehrere aufeinanderfolgende Schrägstriche (\texttt{//}) in +einer Pfadkomponente, die auf einen Verzeichnisnamen \var{d} folgen, +werden expandiert zu allen Unterverzeichnissen von \var{d}. Dieser +Vorgang findet rekursiv statt, wobei erst alle Verzeichnisse auf +einer Ebene bearbeitet werden, dann deren Unterverzeichnisse, usw. +Auf den jeweiligen Ebenen ist nicht beeinflussbar, in welcher +Reihenfolge die Unterverzeichnisse bearbeitet werden. + +Wenn nach den Schrägstrichen Namen angegeben werden, dann werden nur +Unterverzeichnisse mit passenden Namen in die Suche einbezogen. +Beispielsweise wird \samp{/a//b} in die Pfade \file{/a/1/b}, +\file{/a/2/b}, \file{/a/1/1/b} usw. expandiert, aber nicht +zu \file{/a/b/c} oder \file{/a/1}. +(Jeweils vorausgesetzt, dass die Verzeichnisse existieren.) + +Mehrere \samp{//}-Konstruktionen innerhalb einer Pfadkomponente +sind zulässig, allerdings nicht am Pfadanfang. + +% .............................................................. +\subsubsection{Liste der Sonderzeichen und ihre Bedeutung: eine Zusammenfassung} + +Die folgende Zusammenfassung fasst alle Sonderzeichen zusammen, die in den +\KPS"=Konfigurationsdateien auftreten können: + +% ++++++++++++++++++++++++ +\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} +% ++++++++++++++++++++++++ + +\begin{description} +\item[\CODE{:}] Trennzeichen für Pfadkomponenten; als erstes + oder letztes Zeichen im Pfad bewirkt es die + Expansion der Voreinstellungen. +\item[\CODE{;}] Trennzeichen für Pfadkomponenten für andere + Rechnerplattformen als \acro{UNIX} (Verwendung wie + ">\code{:}"<) +\item[\CODE{\$}] Expansion von Variableninhalten +\item[\CODE{\string~}] Home-Verzeichnis eines Benutzers (Tilde) +\item[\CODE{\char`\{...\char`\}}] Expansion geschweifter Klammern: + beispielsweise wird |a{1,2}b| zu |a1b:a2b|. +\item[\CODE{//}] Expansion von Unterverzeichnissen: tritt niemals + am Anfang einer Pfadkomponente auf. +\item[\CODE{\%}] Kommentar +\item[\CODE{\bs}] Konkatenation mit Folgezeile(n) +\item[\CODE{!!}] Einschränkung der Suche \emph{ausschließlich} auf die + Dateinamen"=Datenbank: Das Dateisystem wird \emph{nicht} + durchsucht! +\end{description} + +% ------------------------------------------------------------- +\subsection{Dateinamen"=Datenbanken} +\label{sec:filename-database} + +{\KPS} unternimmt etliche Anstrengungen, um den Zugriff auf Festplatte und +\acro{CDROM}/{\DVD} zur Suche nach Dateien zu reduzieren. Auf \TeX-Systemen mit +vielen Unterverzeichnissen kann die Suche in jedem möglichen Verzeichnis +nach einer bestimmten Datei eine lange Zeit in Anspruch nehmen, besonders +wenn einige Hundert Zeichensatzverzeichnisse durchforstet werden müssen. +Um dieses Problem abzumildern, benutzt {\KPS} eine Art Datenbankdatei +namens \file{ls-R}, die die Zuordnung von Dateinamen auf Verzeichnisse +enthält. Dadurch muss nicht jedesmal die Festplatte durchsucht werden. + +Eine zweite Datenbank in der Datei \file{aliases} kann eine Zuordnung +zwischen den Namen in \file{ls-R} und weiteren Namen vornehmen und so +beispielsweise hilfreich bei der Umsetzung von \samp{8.3}-\acro{DOS}-Dateinamen +auf die ">echten"<, aussagekräftigen Dateinamen zur Seite stehen. + +% .............................................................. +\subsubsection{Die \texttt{ls-R}-Datenbank} +\label{sec:ls-R} + +Wie schon öfters erwähnt, muss die Dateinamen"=Datenbank in der Datei +\file{ls-R} gespeichert sein. Sie sollten eine solche Datenbank für jede +\TeX-Hierarchie (normalerweise in \code{\$TEXMF}) Ihres Systems anlegen. +Die meisten \TeX-Systeme arbeiten nur mit einer Hierarchie. {\KPS} sucht +die Datenbanken \file{ls-R} über den Pfad \code{TEXMFDBS}. + +Es wird empfohlen, die Pflege der \code{ls-R}-Dateien dem mitgelieferten +Skript \cmdname{mktexlsr} zu überlassen. Dieses Skript wird automatisch von den +verschiedenen \samp{mktex*}-Skripten aufgerufen. Das Skript ruft +grob gesagt den Befehl + +\begin{alltt} +cd /\var{your}/\var{texmf}/\var{root} && ls -LAR ./ >ls-R +\end{alltt} + +auf, falls das Kommando \code{ls} Ihres Rechners eine Ausgabe im richtigen +Format liefert. (So wie das \acro{GNU}-\code{ls}.) Wenn Sie ganz sichergehen +wollen, dass die Datenbank immer auf dem neuesten Stand ist, sollten Sie sie +in regelmäßigen Abständen mit Hilfe eines \cmdname{crontab}-Eintrags +aktualisieren lassen. Dadurch wird nach einer Installation eines +Pakets per Hand trotzdem sichergestellt, dass die Datenbank aktuell ist. + +Wenn eine Datei nicht über die Datenbank gefunden wird, sucht +{\KPS} normalerweise auf der Festplatte weiter. Wenn eine Pfadkomponente +mit \samp{!!} beginnt, wird dagegen niemals die Festplatte durchsucht. + +% .............................................................. +\subsubsection{\cmdname{kpsewhich}: Dateisuche} +\label{sec:invoking-kpsewhich} + +Mit dem Programm \cmdname{kpsewhich} können Sie unabhängig vom Aufruf +irgendeines \TeX-Programms nach Dateien in der \TeX-Hierarchie suchen +(als schnellere Alternative zu dem Befehl \cmdname{find}). Dies +wird von den verschiedenen \samp{mktex\dots}-Skripten bis zum +Exzess vorexerziert. + +\begin{alltt} +> \Ucom{kpsewhich \var{option}{\dots} \var{filename}{\dots}} +\end{alltt} + +Die Optionen werden entweder mit \samp{-} oder mit \samp{-{}-} eingeleitet. +Jede eindeutige Abkürzung ist zulässig. + +Argumente der Kommandozeile, die keine Optionen darstellen, werden als +Dateinamen interpretiert. Für jeden Dateinamen wird der erste passende +Pfad gemeldet. Um eine Liste aller passenden Pfade zu erhalten, müssen Sie +das \acro{UNIX}-Kommando \cmdname{find} aufrufen. + +Im Folgenden werden die häufiger benutzten Optionen beschrieben. + +\begin{description} +\item[\texttt{-{}-dpi=}\var{num}]\mbox{}\\ + Stellt die Auf"|lösung für die Suche nach Zeichensätzen + (nur \file{.gf} oder \file{.pk}) auf \var{num}\,dpi. Alternativ + kann die Option \optname{-D} (kommt von \dvips) benutzt werden. + Voreinstellung ist~600. +\item[\texttt{-{}-format=}\var{name}]\mbox{}\\ + Setzt das Format zur Suche auf \var{name}. Per Voreinstellung + versucht \cmdname{kpsewhich} das Format über den Dateinamen + zu erschließen. Bei Formaten ohne zugeordnete Namens\-endung wie den + zu {\MP} gehörenden Dateien und den Konfigurationsdateien zu + {\dvips} müssen Sie den entsprechenden Namen so eingeben, wie er + \KPS{} bekannt ist. +\item[\texttt{-{}-mode=}\var{string}]\mbox{}\\ + Setzt für die Zeichensatzsuche den Generierungsmodus (betrifft nur + \file{.gf}- oder \file{.pk}-Dateien). Normalerweise werden alle + Zeichensätze gemeldet. +\item[\texttt{-{}-must-exist}]\mbox{}\\ + Es wird versucht, die Dateien notfalls durch eine Suche auf der + Festplatte zu finden. Normalerweise wird nur die \file{ls-R}-Datenbank + konsultiert. +\item[\texttt{-{}-path=}\var{string}]\mbox{}\\ + Sucht entlang des angegebenen Pfads statt des Standardpfads, + der auf Grund der Endung gewählt wird. Alle Expansionen sind + zulässig. Bei Verwendung der Option \texttt{-{}-path} darf nicht + die Option \texttt{-{}-format} angegeben werden. +\item[\texttt{-{}-progname=}\var{name}]\mbox{}\\ + Setzt den Programmnamen für die genauere Variablenspezifikation + über \samp{.\var{Programmname}}. Voreinstellung ist \samp{kpsewhich}. +\item[\texttt{-{}-show-path=}\var{name}]\mbox{}\\ + Zeigt den Suchpfad für die angegebene Namens\-endung. Diese kann entweder + als Namens\-endung (\samp{.pk}, \samp{.vf}, usw.) oder als Name (wie bei der + Option \optname{-{}-format}) spezifiziert werden. +\item[\texttt{-{}-debug=}\var{num}]\mbox{}\\ + Legt den Umfang für die Fehlersuche fest. +\end{description} + +% .............................................................. +\subsubsection{Anwendungsbeispiele} +\label{sec:examples-of-use} + +Wir schauen uns nun die Funktionsweise von {\KPS} anhand einiger Beispiele an. + +\begin{alltt} +> \Ucom{kpsewhich article.cls} + /usr/local/texmf-dist/tex/latex/base/article.cls +\end{alltt} + +Wir suchen unter den \TeX-Quelldateien nach der Datei \file{article.cls}. +Da die Namens\-endung \samp{.cls} eindeutig ist, müssen wir den Typ +\samp{.tex} nicht angeben. Die \samp{texmf-dist}-Hierarchie enthält die +Datei im Unterverzeichnis \dirname{tex/latex/base}. Ähnlich bereiten +die folgenden Beispiele auf Grund eindeutiger Namens\-endungen keine Probleme. + +\begin{alltt} +> \Ucom{kpsewhich array.sty} + /usr/local/texmf-dist/tex/latex/tools/array.sty +> \Ucom{kpsewhich latin1.def} + /usr/local/texmf-dist/tex/latex/base/latin1.def +> \Ucom{kpsewhich size10.clo} + /usr/local/texmf-dist/tex/latex/base/size10.clo +> \Ucom{kpsewhich small2e.tex} + /usr/local/texmf-dist/tex/latex/base/small2e.tex +> \Ucom{kpsewhich tugboat.bib} + /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib +\end{alltt} + +Beim letzten Beispiel handelt es sich übrigens um eine \BibTeX-Literaturdatenbank +für \textsl{TUGBoat}-Artikel. + +\begin{alltt} +> \Ucom{kpsewhich cmr10.pk} +\end{alltt} + +Zeichensatzdateien mit der Namens\-endung \samp{.pk} werden +von Anzeige- oder Druckaufbereitungsprogrammen wie {\dvips} und +\cmdname{xdvi} verwendet. Nachdem wir aufgrund der Voreinstellung keine \file{.pk}-Dateien verwenden, +sondern die \PS-\TypeI-Zeichensätze, die auf der \acro{CDROM}/{\DVD} enthalten +sind, wird auch keine \file{.pk}-Datei angezeigt. + +\begin{alltt} +> \Ucom{kpsewhich wsuipa10.pk} +\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk +\else /usr/local/texmf-var/fonts/pk/ljfour/public/ +... wsuipa/wsuipa10.600pk +\fi\end{alltt} +Für diesen Zeichensatz (Teil der \acro{IPA}-Fonts% +\footnote{\acro{IPA}: International Phonetic Alphabet} +von der Universität von Washington) liegen noch keine +\TypeI-Umsetzungen vor und \samp{.pk}-Dateien müssen generiert werden. Da unser voreingestellter \MF-Modus +\samp{ljfour} eine Auf"|lösung von 600\,dpi besitzt, +finden wir (nachdem er schon einmal gebraucht und automatisch +erzeugt wurde) eine entsprechende Instanz dieses Zeichensatzes. + +\begin{alltt} +> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} +\end{alltt} + +Durch die Angabe ">\optname{-dpi=300}"< interessieren wir uns nur +für Zeichensätze mit der Auf"|lösung 300\,dpi. Es wurde keiner gefunden. +Programme wie {\dvips} oder \cmdname{xdvi} lassen einen solchen fehlenden +Zeichensatz durch den Aufruf des Skripts \cmdname{mktexpk} mit entsprechenden +Parametern automatisch erzeugen. + +Als nächstes wenden wir uns den Header- und Konfigurationsdateien +von {\dvips} zu. +Zunächst suchen wir nach der Konfiguration für die \TeX-Unterstützung, +dem Prolog \file{tex.pro}. Danach suchen wir die allgemeine Konfigurationsdatei +(\file{config.ps}) und schließlich die \PS-Zeichensatzzuordnungsdatei +\file{psfonts.map}. Dateien dieser Art haben seit der 2004er-Version der {\TL} ihre eigenen Suchpfade und einen neuen Aufbewahrungsort im \OnCD{texmf}-Baum. Da die Namens\-endung \samp{.ps} nicht eindeutig ist, +müssen wir den gewünschten Typ (\samp{dvips config}) +für die Datei \file{config.ps} spezifizieren. + +\begin{alltt} +> \Ucom{kpsewhich tex.pro} + /usr/local/texmf/dvips/base/tex.pro +> \Ucom{kpsewhich --format="dvips config" config.ps} + /usr/local/texmf/dvips/config/config.ps +> \Ucom{kpsewhich psfonts.map} + /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map +\end{alltt} + +Jetzt suchen wir nach den Dateien für den \PS-Zeichensatz ">URW Times"<. +Nach dem Namensschema von Karl~Berry beginnen die Namen mit ">\texttt{utm}"<. +Zunächst suchen wir die Konfigurationsdatei, die den Namen der +Zeichensatzzuordnungsdatei enthält. + +\begin{alltt} +> \Ucom{kpsewhich --format="dvips config" config.utm} + /usr/local/texmf-dist/dvips/psnfss/config.utm +\end{alltt} + +Diese Datei enthält folgende Anweisung: + +\begin{alltt} + p +utm.map +\end{alltt} + +Die angegebene Datei \file{utm.map} wollen wir als nächstes suchen: + +\begin{alltt} +> \Ucom{kpsewhich utm.map} + /usr/local/texmf-dist/fonts/map/dvips/times/utm.map +\end{alltt} + +Diese Zuordnungsdatei wird im Unterverzeichnis \file{urw} bei den +Hilfsdateien für {\dvips} gefunden. Sie enthält die Dateinamen der +\TypeI-\PS-Zeichensätze, die für URW Times benutzt werden. Ein +kleiner Auszug aus dieser Datei: + +\begin{alltt} + utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} +\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb +\else /usr/local/texmf-dist/fonts/type1/ +... urw/utm/utmr8a.pfb +\fi\end{alltt} + +Diese Beispiele sollten deutlich gemacht haben, wie leicht bestimmte Dateien +im \TeX-Dateibaum gefunden werden können. Dies ist sehr wichtig, wenn Sie +den Verdacht haben, dass eine falsche Version einer Datei verwendet wird: +Sie lassen sich einfach die verwendete Datei von \cmdname{kpsewhich} +anzeigen. + +% .............................................................. +\subsubsection{Fehlersuche} +\label{sec:debugging} + +Manchmal ist wichtig, bis ins Detail nachzuvollziehen, wie ein Programm eine +bestimmte Datei findet. Zu diesem Zweck bietet die \KPS-Bibliothek verschiedene +Stufen für den Umfang der Fehlersuche an. + +\begin{itemize} +\item[\texttt{\ 1}] \code{stat}-Aufrufe (Überprüfung, ob Datei + existiert); mit einer aktuellen \file{ls-R}-Datenbank sollten Sie fast + keine Meldungen erhalten. +\item[\texttt{\ 2}] Zugriffe auf Suchlisten (wie \file{ls-R}-Datenbanken, + Zuordnungsdateien (\texttt{.map}), Konfigurationsdateien) +\item[\texttt{\ 4}] Öffnen und Schließen von Dateien +\item[\texttt{\ 8}] Auf"|listen der voreingestellten Pfade für Extensionen +\item[\texttt{16}] Verzeichnisliste für jede Pfadkomponente (nur bei Festplattenzugriff) +\item[\texttt{32}] Suchaktionen nach Dateien +\item[\texttt{64}] Werte von Variablen. +\end{itemize} + +Durch die Angabe von \samp{-1} setzen Sie alle Stufen gleichzeitig. +Für eine effiziente Fehlersuche sollten Sie sich auf die wichtigsten +Ausgaben beschränken. + +Für {\dvips} gibt es einen ähnlichen Mechanismus zur Erzeugung +von Analysemeldungen, um herauszufinden, warum bestimmte Dateien geöffnet +wurden bzw.\ wo vielleicht das Problem liegt, wenn Dateien nicht gefunden +werden. + +Da fast alle Programme die \KPS-Bibliothek benutzen, können Sie die +gewünschte Stufe auch über die Umgebungsvariable \envname{KPATHSEA\_DEBUG} +einstellen, indem Sie einen der Werte oder eine additive Kombination +spezifizieren. + +Anmerkung für Windows-Benutzer: Es ist nicht einfach, alle Meldungen in eine Datei umzulenken. Für die Fehlersuche +jedoch ist die folgende (temporäre!) Vereinbarung sinnvoll: + +\indent\texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log} + +Wir betrachten als Beispiel eine kleine \LaTeX-Quelldatei mit dem Namen +\file{hello-world.tex} mit folgendem Inhalt: + +\begin{verbatim} + \documentclass{article} + \begin{document} + Hello World! + \end{document} +\end{verbatim} + +Diese Datei verwendet nur einen Zeichensatz, nämlich \file{cmr10}. Wir sehen uns +jetzt einmal genau an, wie {\dvips} die \PS-Datei erzeugt. +Da wir die \TypeI-Variante der Computer-Modern-Roman-Zeichensätze +verwenden wollen, haben wir die Option \optname{-Pcms} verwendet. + +\begin{alltt} +> \Ucom{dvips -d4100 hello-world -Pcms -o} +\end{alltt} + +Hier haben wir als Stufe zur Fehlersuche eine Kombination der Stufe~\code{4} von +{\dvips} (siehe \dvips-Handbuch, +\dirname{texmf/doc/html/dvips/dvips\_toc.html}?). +%\ifSingleColumn +%We get something +%like the following (we have rearranged the output for easier display): +%\begin{alltt}\small +%\input{examples/ex6.tex} +%\end{alltt} +%\else +Die Ausgabe sieht ungefähr so wie in +Abbildung~\ref{fig:dvipsdbga} dargestellt aus (die Ausgabe wurde für einen besseren Überblick +etwas umgestaltet). + +\begin{figure*}[tp] +\centering +\input{examples/ex6a.tex} +\caption{Suche nach Konfigurationsdateien}\label{fig:dvipsdbga} + +\bigskip + +\input{examples/ex6b.tex} +\caption{Suche nach Prologdateien}\label{fig:dvipsdbgb} + +\bigskip + +\input{examples/ex6c.tex} +\caption{Suche nach Font-Dateien}\label{fig:dvipsdbgc} +\end{figure*} + +Zunächst sucht {\dvips} (bzw.\ \KPS) seine Konfigurationsdateien, +nämlich \file{texmf.cnf} (das die Pfade der anderen Dateien enthält), +dann die Dateinamen"=Datenbank \file{ls-R} (zur Optimierung der Suche) +und die Datei \file{aliases}, mit deren Hilfe für eine Datei +mehrere Namen vereinbart werden können, z.\,B. um die kurzen +\samp{8.3}-\acro{DOS}-Namen mit aussagefähigen, langen Namen zu assoziieren. +Danach wird die allgemeine \dvips-Konfigurationsdatei +\file{config.ps}, anschließend die benutzerspezifische Konfigurationsdatei +\file{.dvipsrc} (wird hier \emph{nicht} gefunden) gesucht. +Als letztes sucht {\dvips} die Zuordnungsdatei für +Computer-Modern-{\PS}"=Zeichensätze \file{config.cms} (bedingt durch die +Option \optname{-Pcms} beim Aufruf von \dvips). Diese +Datei enthält die Dateinamen der Listen, die die Zuordnung zwischen +Dateinamen und Zeichensatznamen herstellen. + +\begin{alltt} +> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} + p +ams.map + p +cms.map + p +cmbkm.map + p +amsbkm.map +\end{alltt} + +{\dvips} versucht, diese Dateien und zusätzlich die +allgemeine Zeichensatzzuordnungstabelle \file{psfonts.map} zu +laden, die immer konsultiert wird; der letzte Teil von +Abschnitt~\ref{sec:examples-of-use} erklärt diese Tabellen genauer. + +Jetzt erfolgt die normale Startmeldung von \dvips: + +\begin{alltt}\ifSingleColumn +dvips(k) 5.94a +kpathsea version +Copyright (C) 2003 Radical Eye Software. +... +\else\small{}dvips(k) 5.94a +kpathsea version +Copyright (C) 2003 Radical Eye Software. +... +\fi\end{alltt}% decided to accept slight overrun in tub case +\ifSingleColumn +Danach wird nach \file{texc.pro} gesucht: + +\begin{alltt}\small +kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro +\end{alltt} +\else +Danach wird nach \file{texc.pro} gesucht (siehe Abbildung~\ref{fig:dvipsdbgb}). +\fi +Dann gibt {\dvips} Datum und Uhrzeit aus und meldet den Dateinamen +der erzeugten \PS-Datei \file{hello-world.ps}. Jetzt wird die +Zeichensatzdatei \file{cmr10} benötigt, die {\dvips} als +">resident"< meldet. + +\enlargethispage{1ex} +\begin{alltt}\small +TeX output 1998.02.26:1204' -> hello-world.ps +Defining font () cmr10 at 10.0pt +Font cmr10 is resident. +\end{alltt} + +Es geht weiter mit \file{cmr10.tfm} und einigen weiteren Prologdateien, +deren Ausgaben wir hier weglassen. Letztlich wird die \TypeI-Zeichensatzdatei +\file{cmr10.pfb} gesucht (und gefunden) und in die Ausgabedatei integriert +(siehe letzte Zeile). + +\begin{alltt}\small +kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, + path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: + /var/tex/fonts/tfm//). +kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm +kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, + ... + +kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb +[1] +\end{alltt} + +% ------------------------------------------------------------- +\subsection{Einstellungen zur Laufzeit} + +Zu den willkommenen Erweiterungen von {\Webc} zählt die Möglichkeit, +zur Laufzeit einige Speicher"-größen über die Datei \file{texmf.cnf} anpassen +zu können (insbesondere die Größe einiger Stacks). Eine ausführliche Liste +der veränderbaren Parameter finden Sie in der Datei \file{texmf.cnf}. +Die wichtigsten Werte sind: + +\begin{description} +\item[\texttt{main\_memory}]\mbox{}\\ + Arbeitsspeicher für \TeX, {\MF} und {\MP} in Worten: Für jede Einstellung + muss eine eigene Format-Datei erstellt werden. Allerdings können Sie + mehrere Versionen von {\TeX} unter verschiedenen Namen erzeugen und + in der Konfigurationsdatei jeweils eigene Einträge vorsehen. Hier gibt + es ein Monster-{\TeX} namens \samp{hugetex} mit der zugehörigen Format-Datei + \file{hugetex.fmt}, wobei der spezielle Wert der + Variablen \texttt{main\_memory} dann + aus der Datei \file{texmf.cnf} gelesen wird. +\item[\texttt{extra\_mem\_bot}]\mbox{}\\ + Extraspeicher für ">große"< \TeX-Datenstrukturen wie Boxen, Glue, + Breakpoints, usw.: Besonders bei Anwendung von {\PiCTeX} sollte dieser + Wert erhöht werden. +\item[\texttt{font\_mem\_size}]\mbox{}\\ + Anzahl der Worte für Speicherung von Zeichensatzinformationen: Entspricht + ungefähr dem Speicherbedarf der gelesenen \acro{TFM}-Dateien. +\item[\texttt{hash\_extra}]\mbox{}\\ + Zusätzlicher Platz für Suchlisten: In der Hauptliste können + ca. 10000~Einträge verwaltet werden. Bei einem Buch mit vielen Querverweisen + reicht dieser Platz unter Umständen nicht aus. + Die Voreinstellung für \texttt{hash\_extra} ist \texttt{50000}. +\end{description} + +Natürlich sind diese Parameter kein Ersatz für eine wirklich dynamische +Speicherverwaltung. Mit der gegenwärtigen Version von {\TeX} ist dieses +Konzept aber nur extrem schwer zu implementieren; darum stellt dieses +Verfahren eine praktikable Lösung dar. + +\begin{comment} +%\clearpage +% ============================================================== +\section{Installation von {\TeX} auf einer neuen \acro{UNIX}-Plattform} + +Wenn Sie eine Rechnerplattform einsetzen, für die wir keine Binärdateien +zur Verfügung gestellt haben, müssen Sie {\TeX} und die zugehörigen +Programme mit Hilfe der Quell-Codes selbst übersetzen. Das ist gar nicht so +schwer, wie es klingt. Alles, was Sie brauchen, finden Sie auf der {\DVD} +im Verzeichnis \texttt{source}. + +Zunächst sollten Sie jedoch die von {\TeX} benötigten Dateien durch +eine Installation ohne Binärdateien auf die Festplatte kopieren bzw. +durch ">Mounten"< der {\DVD} verfügbar machen. + +% ------------------------------------------------------------- +\subsection{Voraussetzungen} + +Zum Übersetzen von {\TeX} und allen weiteren benötigten +Programmen benötigen Sie ca. 100\,MB Festplattenkapazität. +Dazu kommen ein \acro{ANSI}-C-Compiler, \cmdname{make} sowie +ein Scanner- und Parser-Generator. Die \acro{GNU}-Programme +(\cmdname{gcc}, \acro{GNU}-\cmdname{make}, \cmdname{m4}, +\cmdname{flex} und \cmdname{bison}) sind praxiserprobt +und auf den meisten Plattformen verfügbar. Eventuell können +Sie auch andere C-Compiler oder \cmdname{make}-Programme einsetzen, +doch dann sollten Sie sich wirklich gut mit Ihrem System auskennen, +wenn es Schwierigkeiten während des Übersetzungsprozesses gibt. +Der Befehl \cmdname{uname} muss einen gültigen Namen liefern. + +% ------------------------------------------------------------- +\subsection{Konfiguration} + +\begin{itemize} +\item Beginnen Sie mit einer ganz normalen \TL-Installation auf +Festplatte (siehe Abschnitt~\ref{sec:install-disk} auf +Seite~\pageref{sec:install-disk}). Das Installieren der +fertigen Binaries können Sie getrost überspringen. + +\item Dann entpacken Sie das komprimierte Archiv (\cmdname{tar}) in +\dirname{source} auf Ihre Festplatte und wechseln in dieses Verzeichnis. + +\item Legen Sie einen Pfad fest, unter dem das \TeX-System +installiert werden soll. Natürlich sollte das derselbe Pfad sein, +den Sie schon zum Kopieren der Daten verwendet haben +(z.\,B. \dirname{/usr/local} oder \dirname{/usr/local/TeX}). +\end{itemize} + +Die automatische Systemerkennung und -anpassung wird durch +\textsf{configure} mit folgendem Aufruf gestartet: + +\begin{alltt} +> \Ucom{./configure -prefix=/usr/local/TeX} +\end{alltt} + +Bei der Option \optname{prefix} geben Sie das Verzeichnis an, in dem sich die +bereits kopierten \TL-Dateien befinden; +dieses Verzeichnis wird weiter strukturiert (\dirname{\$TEXDIR} +ist dabei das Installationsverzeichnis): + + +\begin{tabular}{>{\ttfamily}ll@{}} + \dirname{\$TEXDIR/man} & Anleitungen im + \acro{UNIX}-\cmdname{man}-Format\\ + \dirname{\$TEXDIR/share/texmf} & \TeX-Daten mit Zeichensätzen, + Makros, usw.\\ + \dirname{\$TEXDIR/info} & Anleitungen im + \acro{GNU}-\cmdname{info}-Format\\ + \dirname{\$TEXDIR/bin/\$PLATFORM} & ausführbare Programme\\ +\end{tabular} +%$ + +Wenn Sie wollen, können Sie ">\dirname{share/}"< als Namensbestandteil +von \OnCD{texmf} weglassen, da sowohl +\dirname{\$TEXDIR/share/texmf} als auch \dirname{\$TEXDIR/texmf} +automatisch von \cmdname{configure} erkannt werden. Sollten Sie ein anderes +Verzeichnis vorziehen, müssen Sie dieses \cmdname{configure} mit dem +Kommandozeilenparameter \optname{-{}-datadir} mitteilen. + +Wenn Sie die erkannte Plattform nicht als \dirname{\$PLATFORM} im +Pfad der ausführbaren Programme haben wollen, sondern z.\,B. +direkt in \dirname{\$TEXDIR/bin} installieren wollen, verwenden Sie +die Option \optname{-{}-disable-multiplatform}. + +Zum Weglassen spezieller \TeX-Systeme wie {\OMEGA} oder {\eTeX} gibt +es eine Reihe von Optionen, die Sie durch die Eingabe von +\samp{./configure --help} angezeigt bekommen. + +% ------------------------------------------------------------- +\subsection{Aufruf von \cmdname{make}} + +Vergewissern Sie sich, dass die Shell-Variable \envname{noclobber} nicht +gesetzt ist und geben + +\begin{alltt} +> \Ucom{make world} +\end{alltt} + +ein. Jetzt können Sie sich entspannt zurücklehnen oder wie ein +{\TeX}ie sagt: |\relax|. + +Eine gute Idee ist auch das Speichern der Meldungen beim +Übersetzen durch das Anlegen eines Protokolls: + +\begin{alltt} +> \Ucom{sh -c "make world >world.log 2>\&1" \&} +\end{alltt} + +Nehmen Sie nicht fälschlicherweise nach dem Durchlauf von \cmdname{make} +an, dass alles gut gegangen ist, sondern vergewissern sich durch eine +Kontrolle des Protokolls. (\acro{GNU} \cmdname{make} zeigt Fehler +z.\,B. immer mit der Zeichenkette ">\texttt{***}"< an.) +Außerdem sollten Sie sich vergewissern, dass alle ausführbaren +Programme auch erzeugt wurden: + +\begin{alltt} +> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} +> \Ucom{ls | wc} +\end{alltt} + +Das Ergebnis sollte über 200 liegen (Sie können die exakte Zahl +mit der Anzahl der lauf"|fähigen Programme [Binaries] im Verzeichnis \OnCD{bin} vergleichen). +Der Aufruf \samp{make~world} ist übrigens äquivalent zu +\samp{make~all~install~strip}. + +Wenn für den Aufruf von \samp{make~install} besondere +Systemverwalterrechte notwendig sein sollten, können Sie die +Anweisung \samp{make~world} auch in zwei Durchgängen absetzen: + +\begin{alltt} +> \Ucom{make all} +> \Ucom{su} +> \Ucom{make install strip} +\end{alltt} + +Nachdem Sie Ihre Binaries installiert haben, sollten Sie die normalen +Installationsnacharbeiten durchführen, die im Abschnitt~\ref{sec:postinstall} +auf Seite~\pageref{sec:postinstall} beschrieben sind. + +Wenn Sie lauf"|fähige Programme erstellt haben und diese Anderen zur Verfügung stellen wollen, sollten Sie uns kontaktieren. Wir würden uns freuen, sie auf den \TL-\acro{WWW}-Seiten anzubieten. +\end{comment} + +% ============================================================== +\section{Danksagungen} + +Die {\TL} ist eine gemeinsame Arbeit faktisch aller {\TeX} Users +Groups. + +Die Entwicklung des vorliegende \TL-Releases wurde Karl~Berry geleitet; +die übrigen Haupt-Mitarbeiter sind im Folgenden aufgelistet. + +\begin{itemize} +\item Den englisch-, deutsch-, niederländisch-, und polnisch-sprachigen + \TeX-Anwendervereinigun\-gen (\acro{TUG}, \acro{DANTE} e.V., + \acro{NTG}, and \acro{GUST}), + die zusammen die technische und administrative Infrastruktur + zur Verfügung stellen. Wir würden uns freuen wenn Sie bei einer der + Anwendervereinigungen Mitglied werden. +\item Dem \acro{CTAN} Team, insbesondere Robin Fairbairns, Jim Hef{}feron, + und Rainer Schöpf, das die \TL{}-CD-Images und die Infrastruktur + für Paketupdates zur Verfügung stellt, von denen \TL{} abhängt. +\item Peter Breitenlohner (und das \eTeX\-Team) für den stabilen Grundstock zu {\TeX}s Zukunft, und Peter speziell für wertvolle Hilfe zum Verwenden + von GNU autotools in \TL; +\item Thomas~Esser, der mit dem exzellenten {\teTeX} die Basis + für dieses {\TL} schuf; +\item Michel~Goossens, als Coautor der englischen Original-Dokumentation; +\item Eitan~Gurari, mit dessen {\TeX4ht} die \HTML-Version dieser + Anleitung erstellt wurde und der unermüdlich daran gearbeitet + hat, es auf Zuruf zu verbessern; +\item \Thanh, Martin~Schröder und das pdf\TeX-Team (\url{http://pdftex.org}), + die die Arbeiten zur Erweiterung der Möglichkeiten von + {\TeX} fortgesetzt haben; +\item Hans Hagen, für zahlreiche Tests und Aktivitäten, damit \ConTeXt{} + (\url{http://pragma-ade.com}) ein Teil von \TL sein kann; +\item Taco Hoekwater, für neue Entwicklungen von MetaPost und (Lua)\TeX\ + (\url{http://luatex.org}), und ebenfalls für die Unterstützung beim + \ConTeXt-Teil von \TL; +\item Pawe{\l} Jackowski für das Installationsprogramm \cmdname{tlpm} für + Windows, + Tomasz {\L}uczak für \cmdname{tlpmgui} in früheren Versionen von \TL; +\item Akira Kakuto, für Windows-Programme im Rahmen seines + \acro{W32TEX} Distribution + (\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}); + +\item Jonathan Kew und \acro{SIL}, für die + Neuentwicklung von Xe\TeX{} und die Zeit und Mühe es in \TL{} zu + integrieren, sowie für die erste Version des Mac\TeX-Installers; + +\item Dick Koch für die Betreuung von Mac\TeX\ (\url{http://tug.org/mactex}); + + +\item Reinhard Kotucha, für die Unterstützung bei der Infrastruktur von + \TL{} und das Installationsprogramm, für seine Windows-Untersuchungen, für das \texttt{getnonfreefonts} + Script, und vieles mehr; + +\item Siep Kroonenberg, für wertvolle Beiträge zur Infrastruktur von + \TL\,2008 und den Installer, insbesondere unter Windows, und für einen + Großteil der Arbeit, die Dokumentation dafür zu schreiben; + +\item Petr~Olsak, der das tschechische und slowakische Material sehr sorgfältig er- und überarbeitet hat; + +\item Toshio Oshima, für den \cmdname{dviout}-Previewer für Windows; + +\item Manuel P\'egouri\'e-Gonnard, für die Mithilfe beim Aktualisieren + von Paketen, der Dokumentation und Arbeit an \cmdname{tldoc}; + +\item Fabrice Popineau für die erste Windows-Version von \TL und Mithilfe + bei der französischen Dokumentation; + +\item Norbert Preining, Hauptkoordinator für \TL{}-Infrastruktur und + den Installer, für die Koordination der Debian Version von \TL{} + (zusammen mit Frank Küster), und die daraus resultierenden + Verbesserungsvorschläge; + +\item Sebastian Rahtz für die Erfindung von \TL und die langjährige + Leitung des Projekts; + +\item Vladimir Volovich für viele substanzielle Mithilfe, und dafür, dass + er es möglich gemacht hat, \cmdname{xindy} in \TL aufzunehmen; + +\item Staszek~Wawrykiewicz, der Haupttester für alles, was mit {\TeX} zusammen hängt, Koordinator der polnischen + Beiträge, Windows-Installation und mehr; + +\item Olaf~Weber für die Geduld beim Pflegen von \Webc; +\item Gerben~Wierda für das Erstellen und Pflegen des \MacOSX-Teils und für viele Integrations- und Testarbeiten; +\item Graham~Williams, dessen Arbeit das Makro- und Paketverzeichnis möglich gemacht hat. +\end{itemize} + +\textbf{Lauf"|fähige Programme:} +Reinhard Kotucha (\pkgname{x86\_64-linux}), +Tim Arnold (\pkgname{hppa-hpux}), +Randy Au (\pkgname{amd64-freebsd}), +Edd Barrett (\pkgname{i386-openbsd}), +Karl Berry (\pkgname{i386-linux}), +Akira Kakuto (\pkgname{win32}), +Dick Koch (\pkgname{universal-darwin}), +Manfred Lotz (\pkgname{i386-freebsd}), +Norbert Preining (\pkgname{alpha-linux}), +Arthur Reutenauer (\pkgname{sparc-linux}), +Thomas Schmitz (\pkgname{powerpc-linux}), +Apostolos Syropoulos (\pkgname{i386-solaris}), +Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-solaris}), +Olaf Weber (\pkgname{mips-irix}). + +Informationen dazu, wie Binaries für \TL{} erzeugt werden, +finden sich unter \url{http://tug.org/texlive/build.html}. + +\textbf{Dokumentation und Anpassung der Übersetzungen:} + +\begin{itemize*} +\item Karl~Berry (Englisch), +\item Daniel~Flipo (Französisch), +\item Klaus Höppner \& Hartmut~Henkel (Deutsch) +\item Petr~Sojka \& Jan~Busa (Tschechisch/""Slowakisch), +\item Boris~Veytsman (Russisch), +\item Staszek~Wawrykiewicz (Polnisch). +\end{itemize*} + +Natürlich haben wir am meisten Donald~Knuth zu danken, einmal dafür, dass er {\TeX} erfand und dann dafür, dass er es +der Welt schenkte. + +% ------------------------------------------------------------- +\section{Geschichtliches}\label{sec:history} + +Diese Ausgabe der {\TL} ist in Zusammenarbeit der \TeX{} Users Group (\acro{TUG}), der +\acro{UKTUG}, der französischen \TeX-Vereinigung GUTenberg +und der deutschsprachigen \TeX-Anwendervereinigung (DANTE e.\,V.) +unter Mithilfe der niederländischen, tschechischen/""slowakischen, +indischen, polnischen und russischen \TeX-Benutzergruppen +entstanden. + +\subsection{Vergangenheit} + +Die niederländische \TeX-Benutzergruppe hatte Ende 1993 mit der +Produktion der 4All\TeX-{\acro{CDROM}} für \acro{MS-DOS} die Diskussion angeregt, +eine einzige {\acro{CDROM}} für alle Rechnersysteme zu entwickeln. Zum +damaligen Zeitpunkt war dieses Ziel zu hoch gesteckt, doch immerhin +entstand aus dieser Diskussion nicht nur die sehr erfolgreiche +4All\TeX-{\acro{CDROM}}, sondern auch die \acro{TUG}-Arbeitsgruppe zur Definition +der {\TeX} Directory Structure \TDS, die die zur Arbeit mit {\TeX} +notwendigen und hilfreichen Dateien in eine konsistente und +handhabbare Verzeichnisstruktur einbettet. Das ">Final~Draft"<-Dokument, +das diese Verzeichnisstruktur festlegt, wurde in der Dezember-Ausgabe +1995 der TUGBoat veröffentlicht. Schon frühzeitig war den Beteiligten +klar, dass eine {\acro{CDROM}} auf der Basis der {\TDS} sehr zu begrüßen wäre. +Die \TL-{\acro{CDROM}} war das direkte Resultat der Beratungen der +\TDS-Arbeitsgruppe. Außerdem hat der Erfolg der 4All\TeX-{\acro{CDROM}} +klargemacht, dass ein ähnliches System auch für \acro{UNIX}-Benutzer eine +Erleichterung darstellen würde. Dies war der zweite Beweggrund für +die \TL-\acro{CDROM}. + +Im Herbst 1995 wurde das Projekt, eine \TDS-basierte \acro{UNIX}-{\acro{CDROM}} +zu entwickeln, in Angriff genommen. Sehr schnell stießen die +Verantwortlichen auf das \teTeX-System von Thomas~Esser als +idealen Ausgangspunkt für diese Arbeit, weil es verschiedene +Rechnerplattformen unterstützte und für die Arbeit mit verschiedenen +Dateisystemen vorgesehen war. Anfang 1996 wurde in Zusammenarbeit +mit Thomas~Esser ernsthaft mit der Arbeit begonnen und im Mai~1996 +die erste Ausgabe der {\acro{CDROM}} veröffentlicht. + +Anfang 1997 stellte +Karl~Berry eine neue Version seines \Webc-\TeX-Systems vor, das +schon nahezu alle Ausstattungsmerkmale aufwies, die Thomas~Esser +mit {\teTeX} verwirklicht hatte. Die \acro{TUG} entschied sich daraufhin, +die zweite Version der {\acro{CDROM}} auf der Basis von {\Webc} unter +Verwendung des Installations-Skripts \cmdname{texconfig} aus dem +\teTeX-Paket zu entwickeln. + +Die dritte Ausgabe basierte auf der +inzwischen von Olaf~Weber gepflegten und weiter entwickelten +{\Webc}~Version~7.2; {\TL} unterstützte fast alle Eigenschaften +der zur selben Zeit entstandenen neuen Version von \teTeX. + +Die vierte Ausgabe folgte demselben Schema, indem ihr neue +Versionen von {\teTeX} und {\Webc}~(7.5) zugrunde lagen. +Fast die gesamte {\acro{CDROM}} wurde einer kritischen Überprüfung +unterzogen, wobei besonders darauf geachtet wurde, dass doppelte +Dateien entfernt wurden und die Einordnung der Pakete konsistent +erfolgte. Zudem enthielt diese Ausgabe ein komplettes Windows-Setup. + +Für die fünfte Ausgabe im März~2000 wurden wiederum große Teile der +{\acro{CDROM}} ersetzt, wobei Hunderte von überarbeiteten Paketen aufgenommen +wurden. {\OMEGA}, {pdf\TeX} und Teile der \TeX-Support-Programme (hier +insbesondere \cmdname{xdvi}, \cmdname{dvips} und \cmdname{tex4ht}) +lagen in neuer Version vor. +Die Hauptänderung bei der \TL\,5 betraf die \samp{non-free}-Software. +Alles auf dieser {\acro{CDROM}} war nun in Übereinstimmung mit den \emph{Debian +Free Software Guidelines} (\url{http://www.debian.org/intro/free}). +Wir haben unser Bestes versucht, die Lizenzbedingungen aller Pakete +zu überprüfen, sind aber dankbar, wenn wir auf Fehler hingewiesen werden. + +Die sechste Ausgabe der {\TL} vom Juli/August~2001 +enthielt die neuesten Versionen aller Pakete und Programme. +Das neue Installationskonzept stellte die größte Änderung dar: +Der Benutzer konnte nun viel genauer +gewünschte bzw.\ nicht erwünschte Sammlungen +und Pakete auswählen. Dabei wurden die sprachspezifischen Sammlungen +komplett überarbeitet, so dass sie jetzt automatisch nicht nur +Makros, Fonts usw. installierten, sondern zusätzlich die notwendigen +Einträge in \file{language.dat} vornahmen. + +Die siebte Ausgabe vom Mai~2002 enthält als größte +Änderungen {\MacOSX} und wieder unzählige Updates aller Pakete und Programme. +Ein wesentliches Ziel war zudem die Wiedererstellung einer gemeinsamen +Quelle mit {\teTeX}, um das Auseinanderlaufen seit \TL\,5 und \TL\,6 +zu korrigieren. + +\subsection{2003} + +Im Jahr 2003 war die Flut von Updates und neuen Paketen so groß geworden, +dass wir feststellen mussten: ">{\TL} passt nicht mehr auf eine einzelne +\acro{CDROM}"<. Und so wurde sie in drei verschiedene Distributionen aufgeteilt +(siehe Abschnitt~\ref{sec:tl-coll-dists} auf Seite~\pageref{sec:tl-coll-dists}). +Des Weiteren: + +\begin{itemize} +\item Auf Wunsch des \LaTeX-Teams wurde der Standard für \cmdname{latex} + und \cmdname{pdflatex} verändert; beide benutzen nun {\eTeX} als Basis + (siehe Seite~\pageref{text:etex}). +\item Die neuen ">Latin Modern Fonts"< wurden aufgenommen (und werden + zur Benutzung empfohlen). +\item Der Support für Alpha-\acro{OSF} wurde aufgegeben (den + \acro{HPUX}-Support hatte es schon zuvor ereilt), da + niemand mehr in der Lage war, neue Binaries zu kompilieren. +\item Das Setup für Windows wurde grundlegend überarbeitet. + Zum ersten Mal wurde eine integrierte Umgebung eingeführt, + die auf \cmdname{XEmacs} basiert. +\item Wichtige Hilfsprogramme für Windows (Perl, Ghost\-script, + Image\-Magick, Ispell) werden nun im \TL-Verzeichnis + installiert. +\item Die von \cmdname{dvips}, \cmdname{dvipdfm} und \cmdname{pdftex} + benutzten Font-Mapfiles werden vom neuen Programm + \cmdname{updmap} generiert und in \dirname{texmf/fonts/map} + installiert. +\item \TeX, {\MF} und {\MP} geben nun die meisten 8"~Bit-Input"~Zeichen (Position 32 und oberhalb) unverändert + aus in (\verb|\write|)-Files, Logfiles und auf dem Terminal. + Das bedeutet, dass sie \emph{nicht} mit der \verb|^^|-Notierung + übersetzt ausgegeben werden. Auf der \TL\,7 war diese + Übersetzung abhängig von der \cmdname{locale}-Einstellung des + Systems; nun beeinflussen \cmdname{locale}-Einstellung nicht + {\TeX}s Programmverhalten. Falls Sie aus irgendwelchen + Gründen die \verb|^^|-Ausgabe benötigen, müssen Sie in Ihrem System + die Datei \file{texmf/web2c/cp8bit.tcx} umbenennen + (zukünftige Versionen werden eine sauberere Schnittstelle zur + Kontrolle dieses Verhaltens anbieten). +\item Die Dokumentation wurde grundlegend überarbeitet. +\item Zum Abschluss einigten wir uns auf eine neue Edition-Nummerierung. + Ab diesem Jahr trägt die {\TL} statt einer fortlaufenden Nummer + die Jahreszahl: \TL~2003. +\end{itemize} + +\subsection{2004} + +\begin{itemize} +\item Wenn Sie lokal installierte Zeichensätze mit ihren eigenen \filename{.map}- oder (weniger wahrscheinlich) + \filename{.enc}-Dateien benutzen, müssen Sie möglicherweise diese Dateien verschieben. + + Nach den \filename{.map}-Dateien wird jetzt in den \dirname{fonts/map}-Unterverzeichnissen im + \envname{TEXFONTMAPS}-Pfad gesucht (in jedem \filename{texmf}-Baum). + Gleichzeitig werden \filename{.enc}-Dateien jetzt in den \dirname{fonts/enc}-Unterverzeichnissen entlang des + \envname{ENCFONTS}-Pfads gesucht. Das Programm \cmdname{updmap} versucht, bei problematischen Dateien zu warnen. + + Informationen darüber, wie das gehandhabt wird, und zusätzliche Informationen finden Sie unter + \url{http://tug.org/texlive/mapenc.html}. + +\item Die \TK\ wurde für all diejenigen, die diese Implementierung {\Webc} vorziehen, um eine \MIKTEX-basierte und + installierbare {\acro{CDROM}} erweitert. Siehe dazu auch Abschnitt~\ref{sec:overview-tl} auf + Seite~\pageref{sec:overview-tl}. + +\item In der {\TL} wurde der umfangreiche \dirname{texmf}-Baum früherer Versionen durch drei Teilbäume ersetzt: + \OnCD{texmf}, \OnCD{texmf-dist} und \OnCD{texmf-doc}. Siehe dazu Abschnitt~\ref{sec:tld} auf + Seite~\pageref{sec:tld} und die \filename{README}-Dateien in den drei Zweigen. + +\item Alle \TeX-relevanten Eingabedateien sind jetzt in den \dirname{tex}-Unterverzeichnissen der + \dirname{texmf*}-Bäume zusammengefasst und nicht mehr in den parallelen Verzeichnissen \dirname{tex}, + \dirname{etex}, \dirname{pdftex}, \dirname{pdfetex}, usw. Siehe dazu + \CDref{texmf-doc/doc/english/tds/tds.html\#Extensions}{\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}. + +\item Hilfs-Skripte, die der Anwender nicht selbst aufruft, werden jetzt in den \mbox{neuen} + \dirname{scripts}-Unterverzeichnissen der \dirname{texmf*}-Bäume aufbewahrt. Nach ihnen wird per + \samp{kpsewhich -format=texmfscripts} gesucht. Wenn Sie Programme einsetzen, die solche Skripte aufrufen, müssen + sie angepasst werden. Siehe dazu \CDref{texmf-doc/doc/english/tds/tds.html\#Scripts} +{\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}. + +\item (Fast) alle Formate interpretieren -- an Stelle einer Übersetzung durch die \verb|^^|-Notation -- mittels + des ">translation files"< \filename{cp227.tcx} die meisten Zeichen als direkt ausgebbar. Insbesondere werden + die Zeichen an den Positionen 32--256, zusätzlich \acro{TAB}, \acro{VT} (vertical tab; vertikaler Tab) und + \acro{FF} (form feed; Seitenvorschub), als druckbar angesehen und daher nicht übersetzt. Ausnahmen sind + plain \TeX, bei dem nur die Zeichen an den Positionen 32--127 druckbar sind, {\ConTeXt} (mit druckbaren Zeichen an + den Positionen 0--255) und die \OMEGA-verwandten Formate. Dieses voreingestellte Verhalten ist (fast) identisch + mit dem in \TL\,2003; es ist aber jetzt klarer und mit umfangreicheren Anpassungsmöglichkeiten implementiert. + Siehe dazu \CDref{texmf/doc/web2c/web2c.html\#TCX-files} +{\texttt{texmf/doc/web2c/web2c.html\#TCX-files}}. + + \textbf{Anmerkung:} Da {\TeX} byte-orientiert ist, können bei einer Unicode-Eingabe (2-Byte-Zeichen) im Kontext + von Fehlermeldungen Folgen von 1-Byte-Zeichen ausgegeben werden. + +\item \cmdname{pdfetex} ist jetzt die voreingestellte ">Engine"< für alle Formate mit Ausnahme von + \mbox{(plain-)\cmdname{tex}} selbst (natürlich generiert es \dvi-Code, wenn es als \cmdname{latex}, usw. + aufgerufen wird.). Das bedeutet unter vielen anderen Dingen, dass die mikrotypographischen Fähigkeiten von + \cmdname{pdftex} + wie auch die Erweiterungen von {\eTeX} in \LaTeX, \ConTeXt usw. zur Verfügung stehen + (\OnCD{texmf-dist/doc/etex/base/}). + + Das bedeutet, dass es \emph{wichtiger denn je} ist, das Paket \pkgname{ifpdf} zu benutzen (es arbeitet sowohl mit + {plain \TeX} als auch mit \LaTeX), da der einfache Test, ob \cs{pdfoutput} oder ein anderer \TeX-Grundbefehl + (primitive) definiert ist, nicht verlässlich genug ist für die Entscheidung, ob eine PDF-Ausgabe erzeugt wird. + Wir haben das rückwärts-kompatibel gemacht, so gut wir das dieses Jahr konnten; nächstes Jahr aber soll + \cs{pdfoutput} so beschaffen sein, dass dieser Befehl auch dann definiert ist, wenn {\dvi}-Code erzeugt wird. + +\item pdf\TeX\ (\url{http://pdftex.org/}) hat viele neue Besonderheiten: + \begin{itemize} + \item Die Befehle \cs{pdfmapfile} und \cs{pdfmapline} ermöglichen einen Font"~Map-Support innerhalb eines + Dokuments. + \item Mikrotypografische Zeichensatz-Expansion (font expansion) kann jetzt viel leichter benutzt werden + \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html}. + \item Alle Parameter, die früher in der speziellen Konfigurationsdatei \filename{pdftex.cfg} definiert wurden, + müssen jetzt mit Hilfe von pdf\TeX-Grundbefehlen gesetzt werden, typischerweise in + \filename{pdftexconfig.tex}; die Konfigurationsdatei \filename{pdftex.cfg} wird nicht länger unterstützt. + Jede schon bestehende Format-Datei (\filename{.fmt}) muss neu erstellt werden, wenn + \filename{pdftexconfig.tex} geändert wird. + \item Für zusätzliche Informationen siehe das pdf\TeX-Handbuch: \OnCD{texmf-dist/doc/pdftex/manual}. + \end{itemize} + +\item Der Grundbefehl \cs{input} in \cmdname{tex} (\cmdname{mf} und \cmdname{mpost}) akzeptiert jetzt doppelte + Anführungszeichen und andere Spezialzeichen. Typische Beispiele: + +\begin{verbatim} +\input "filename with spaces" % plain +\input{"filename with spaces"} % latex +\end{verbatim} + + Für zusätzliche Informationen siehe das \Webc-Handbuch: \OnCD{texmf/doc/web2c}. + +\item enc\TeX\ wird jetzt in {\Webc} und damit auch in allen \TeX-Programmen unterstützt. Dazu wird \emph{beim + Generieren neuer Formate} die Option \optname{-enc} benutzt. enc\TeX\ unterstützt allgemein die Umkodierung der + Ein- und Ausgabe und ermöglicht eine volle Unicode-Unterstützung (in \acro{UTF}-8). + Siehe \OnCD{texmf-dist/doc/generic/enctex/} und \url{http://www.olsak.net/enctex.html}. + +\item Aleph (\ensuremath{\aleph}), eine neue ">Engine"<, die {\eTeX} und {\OMEGA} vereinigt, ist verfügbar. Ein bisschen + Information darüber finden Sie in \OnCD{texmf-dist/doc/aleph/base} und + \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph}. Das \LaTeX-basierte Aleph-Format heißt + \cmdname{lamed}. + +\item Das neueste \LaTeX-Release enthält eine neue Version der \acro{LPPL}% + \footnote{LPPL: LaTeX Project Public License}, + die jetzt eine offiziell von Debian anerkannte Lizenz ist. Zusammen mit anderen Updates finden Sie Informationen + dazu in den \filename{ltnews}-Dateien in \OnCD{texmf-dist/doc/latex/base}. + +\item \cmdname{dvipng} -- ein neues Programm zum Konvertieren von \dvi-Dateien in \acro{PNG}-Bilddateien, ist + Bestandteil von \TL. Siehe \OnCD{texmf/doc/man/man1/dvipng.1}. + +\item Auf Vorschlag des Autors (Claudio~Beccari) haben wir das Paket \pkgname{cbgreek} auf einen ">mittelgroßen"< Satz + von Fonts reduziert. Herausgenommen wurden die ">invisible"<, Outline- und ">Transparency"<-Fonts, + die relativ selten benutzt werden -- denn wir benötigen den Platz. In seinem vollen Umfang ist das Paket natürlich + weiterhin auf \acro{CTAN} verfügbar (\url{http://www.ctan.org/tex-archive/fonts/greek/cb/}). + +\item \cmdname{oxdvi} wurde entfernt; benutzen Sie jetzt \cmdname{xdvi}. + +\item Die \cmdname{ini}- und \cmdname{vir}-Befehle (Links) für \cmdname{tex}, \cmdname{mf} and \cmdname{mpost} sind + nicht mehr länger verfügbar, so auch \cmdname{initex}. Das ist kein richtiger Verlust, da die + \cmdname{ini}-Funktionalität schon seit mehreren Jahren über den Aufrufparameter \optname{-ini} zur Verfügung + steht. + +\item Die Unterstützung der Plattform \cmdname{i386-openbsd} wurde entfernt. Da das Paket \pkgname{tetex} im + \acro{BSD}-Ports-System zur Verfügung steht und Binaries für \acro{GNU}/""Linux and Free\acro{BSD} erhältlich sind, + erschien es sinnvoll, die Zeit der Freiwilligen besser zu nutzen. + +\item Zumindest auf \cmdname{sparc-solaris} müssen Sie ggf. die En"-viron"-ment-Variable \envname{LD\_LIBRARY\_PATH} + setzen, um die \pkgname{t1utils}-Programme laufen lassen zu können. Ursache dafür ist, dass die Programme mit C++ + kompiliert wurden und dass es keinen Standard-Platz für Laufzeit-Bibliotheken gibt (das ist zwar auch im Jahre + 2004 nicht neu, wurde aber bisher nicht dokumentiert.) Unter \cmdname{mips-irix} werden die + \acro{MIPS}pro-7.4-Laufzeit-Bibliotheken benötigt. +\end{itemize} + +\subsection{2005} + +Im Jahr 2005 gab es -- wie üblich -- viele aktualisierte Pakete und +Programme. Die Struktur des Systems blieb weitgehend gleich, mit folgenden +Ausnahmen: + +\begin{itemize} +\item Die neuen Skripte \cmdname{texconfig-sys}, \cmdname{updmap-sys} und + \cmdname{fmtutil-sys} für die systemweite Konfiguration des Systems wurden + hinzugefügt. Die Skripte \cmdname{texconfig}, \cmdname{updmap} und + \cmdname{fmtutil} modifizieren nun die Konfiguration für einen einzelnen + Nutzer unter \dirname{\$HOME/.texlive2005}. +\item Analog spezifizieren die Pfade \envname{TEXMFCONFIG} und + \envname{TEXMFSYSCONFIG} nun, wo die Konfigurationsdateien gefunden + werden (für einen einzelnen Nutzer bzw.\ systemweit). Möglicherweise + müssen Sie daher vorhandene eigene Versionen von + \filename{fmtutil.cnf} oder \filename{updmap.cfg} in die entsprechenden + Pfade verschieben. Alternativ können Sie \envname{TEXMFCONFIG} und + \envname{TEXMFSYSCONFIG} in der Datei \filename{texmf.cnf} umdefinieren, + dass diese auf die Speicherorte Ihrer eigenen Konfigurationsdateien + verweisen. Siehe Abschnitt~\ref{sec:texmftrees} auf Seite~\pageref{sec:texmftrees}. +\item Im letzten Jahr wurden für die Programme, die DVI als Ausgabeformat + erzeugen, die Primitive wie \verb|PDFoutput| auf undefiniert gesetzt, + obwohl immer \cmdname{pdfetex} verwendet wurde. In diesem Jahr wurde dies + wie angekündigt nicht mehr getan. Falls in Dokumenten nun die Abfrage + \verb|\ifxPDFoutput\undefined| zum Test benutzt wird, ob PDF oder DVI + erzeugt wird, müssen diese geändert werden! Benutzen Sie das Paket + \pkgname{ifpdf.sty}, das auch mit dem geänderten Verhalten funktioniert, + oder orientieren Sie sich an dessen Code. +\item Im letzten Jahr wurden die Formate so geändert, dass sie Zeichen + als 8-bit ausgeben. Die neue TCX-Datei \filename{empty.tcx} eröffnet nun + einen einfachen Weg, die originale Ausgabe mit \verb|^^|-Notation zu + erhalten, wenn Sie es wünschen: +\begin{verbatim} +latex --translate-file=empty.tcx yourfile.tex +\end{verbatim} +\item Das Programm \cmdname{dvipdfmx} für die Konvertierung von DVI nach + PDF ist neu hinzugekommen. Dies ist eine aktiv gepflegte Erweiterung von + \cmdname{dvipdfm}, das zwar noch verfügbar ist, aber als obsolet angesehen + werden kann. +\item Ebenso sind die Programme \cmdname{pdfopen} und \cmdname{pdfclose} neu + hinzugekommen. Diese erlauben ein Reload von PDF-Dateien im Acrobat Reader, + ohne diesen neu starten zu müssen (andere PDF-Viewer wie \cmdname{xpdf}, + \cmdname{gv} oder \cmdname{gsview} hatten damit nie Probleme). +\item Aus Konsistenzgründen wurden die Variablen \envname{HOMETEXMF} und + \envname{VARTEXMF} in \envname{TEXMFHOME} bzw.\ \envname{TEXMFSYSVAR} + umbenannt. Weiterhin existiert \envname{TEXMFVAR} für einen Baum, der + spezifisch für einen einzelnen Nutzer ist. +\end{itemize} + +\subsection{2006--2007} +\label{tlcurrent} + +Der wichtigeste Neuzuwachs in der Ausgabe 2006--2007 von \TL{} war das Xe\TeX{} +Programm, verfügbar durch die \texttt{xetex} und \texttt{xelatex} +Programme; siehe \url{http://scripts.sil.org/xetex}. + +Auch MetaPost erhielt ein bemerkenswertes Update, mit weiteren geplannten +Änderungen (\url{http://tug.org/metapost/articles}), ebenso pdf\TeX{} +(\url{http://tug.org/applications/pdftex}). + +Das (plain) \texttt{tex}-Programm liest nicht mehr erste Zeilen mit +\texttt{\%\&} um das Format zu bestimmen. Es ist ein reines Knuth-\TeX. +(\LaTeX\ und alle anderen Formate lesen weiterhin \texttt{\%\&}-Zeilen). + +Weiters wurden wie üblich hunderte von Paketen und Programmen auf einen +neueren Stand gebracht. Für weiter Updates wenden Sie sich bitte an +\acro{CTAN} (\url{http://www.ctan.org}). + +Die Entwicklungsumgebung wurde auf Subversion umgestellt, was ein Webinterface +für den Entwicklungsbaum beisteuerte. Dieses Webinterface ist von der +Homepage verlinkt. Obwohl dieser Umstieg in der Distribution nicht zu +erkennen ist, erwarten wir uns ein stabiles Fundament für die Entwicklung +in den nächsten Jahren. + +Schließlich hat im Mai~2006 Thomas Esser das Ende seiner Entwicklung von +te\TeX{} (\url{http://tug.org/tetex}) angekündigt. Als Konsequenz ist das +Interesse an \TL{}, besonders unter den \acro{GNU}/Linux-Distributoren +angestiegen. (\TL{} bietet nun ein \texttt{tetex}-Installationsschema, dass +annähernd den Umfang von te\TeX{} umfasst.) Wir hoffen dass dies +schlussendlich zu einer Verbesserung der \TeX-Umgebung für jederman führt. + +\medskip\noindent +Abschließende Bemerkung zur Vergangenheit: Alle Versionen von \TL, +inklusive Beimaterial wie CD-Labels, finden sich unter +\url{ftp://tug.org/historic/systems/texlive}. + +\subsection{Gegenwart} +\label{sec:tlcurrent} + +Die komplette Infrastruktur von \TL wurde 2008 neu entwickelt. Die +gesamten Daten, die für die Installation benötigt werden, finden sich +nun in einer einzigen Textdatei mit dem Namen \filename{tlpkg/texlive.tlpdb}. + +Dies ermöglicht es unter anderem, ein Update einer installierten Version +von \TL über das Internet durchzuführen, was für MiK\TeX{} schon seit +Jahren möglich ist. Wir planen regelmäßige Updates bereitzustellen, +wenn Pakete auf \CTAN{} aktualisiert werden oder neu erscheinen. + +Als neues Programm ist Lua\TeX\ (\url{http://luatex.org}) enthalten, +das neben neuen Möglichkeiten innerhalb des Satzsystems eine +hervorragende Skriptsprache zur Verfügung stellt, die inner- und +außerhalb von \TeX{} benutzt werden kann. + +Die Unterstützung von \TL für Windows und Unix ist mittlerweile praktisch +äquivalent. Die meisten Perl- und Lua-Skripte können nun auch unter +Windows verwendet werden, da innerhalb von \TL Perl integriert ist. + +Das neue \cmdname{tlmgr}-Programm (Abschnitt~\ref{sec:tlmgr}) ist +eine komplette Oberfläche zum Verwalten von \TL nach der Installation. +Es ermöglicht das Aktualisieren von Paketen, die Neugenerierung von +Formatdateien, Fontmaps und die Konfiguration der \TeX-Unterstützung +für verschiedene Sprachen. + +Nach der Einführung von \cmdname{tlmgr} sind die Funktionen von +\cmdname{texconfig} zur Konfiguration von Formatdateien und +Trennmustern deaktiviert worden. + +Der Index-Prozessor \cmdname{xindy} (\url{http://xindy.sourceforge.net/}) +ist nun für die meisten Betriebssysteme integriert. + +Das Programm \cmdname{kpsewhich} kann nun alle Fundstellen für eine +gesuchte Datei anzeigen (Option \optname{--all}) oder die Suche +auf ein bestimmtes Verzeichnis einschränken (Option \optname{--subdir}). + +Das Programm \cmdname{dvipdfmx} kann nun Informationen über die +Bounding Box liefern, was über die Kommandozeile mit dem Befehl +\cmdname{extractbb} aufgerufen werden kann; dies war die letzte +Funktion von \cmdname{dvipdfm}, die noch nicht in \cmdname{dvipdfmx} +vorhanden war. + +Die Font-Aliasnamen \filename{Times-Roman}, \filename{Helvetica} usw. +wurden abgeschafft. + +Das Makro-Format \pkgname{platex} wurde entfernt, um den Namenskonflikt +mit dem japanischen \pkgname{platex} auf zu lösen; Unterstützung +für polnisch wird nun vom Paket \pkgname{polski} zur Verfügung gestellt. + +Die \web{} string pool files wurden in die Programme einkompiliert, +um Updates zu vereinfachen. + +Und abschließend sind die Änderungen von Donald Knuth in seinem +\emph{\TeX\ tuneup of 2008} in \TL eingearbeitet, +\url{http://tug.org/TUGboat/Articles/tb29-2/tb92knut.pdf}. +% ------------------------------------------------------------- +\subsection{Zukunft} + +\emph{{\TL} ist nicht perfekt! -- und wird es auch nie sein.} Wir planen +Neuauf"|lagen zu produzieren, die umfangreichere +Hilfstexte, mehr Hilfsprogramme, mehr Installationshilfen und (natürlich) +den ständig verbesserten und überprüften Satz der Makros und Zeichensätze +enthalten. Diese Arbeit wird von Freiwilligen in ihrer knappen Freizeit +geleistet. Viel Arbeit steht noch an. Wenn Sie uns helfen können, +zögern Sie keine Sekunde, sich bei uns zu melden. + +Verbesserungen, Anregungen und Erweiterungen für künftige Ausgaben +der {\TK} senden Sie bitte an:\hfill\null + +\begin{quote} +\email{tex-live@tug.org}\\ +\url{http://tug.org/texlive/} +\end{quote} + +Neue Versionen, Anmerkungen und zusätzliches Material werden über +die \CTAN-Server im Verzeichnis \dirname{info/texlive} zur Verfügung gestellt. +Im \acro{WWW} können Sie sich über die Adresse +\url{http://www.tug.org/tex-live/} informieren und die Bestellformalitäten +einsehen. + +\end{document} diff --git a/Master/texmf/doc/texlive/source/texlive-en/Makefile b/Master/texmf/doc/texlive/source/texlive-en/Makefile new file mode 100644 index 00000000000..170161df9c3 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/Makefile @@ -0,0 +1,69 @@ +# $Id$ +# Makefile for TeX Live documentation. Public domain. +doc = texlive-en +lang = english + +all: pdf html + +env = TEXINPUTS=../texlive-common:../texlive-en:; export TEXINPUTS; + +pdf: + rm -f *.aux *.toc *.lof *.lot *.xref* *.tmp *.out + $(env) pdflatex '\nonstopmode\def\Status{1}\input $(doc)' + $(env) pdflatex '\nonstopmode\def\Status{1}\input $(doc)' + $(env) pdflatex '\nonstopmode\def\Status{1}\input $(doc)' + $(env) pdflatex '\nonstopmode\def\Status{1}\input $(doc)' + +html: + rm -f *.aux *.toc *.lof *.lot *.xref* *.tmp *.out *.4tc +# this sequence is equivalent to running "ht latex $(doc)". We do it +# this way so we can \def\Status for the \ifcase in tex-live.sty. + $(env) latex '\nonstopmode\def\Status{2}\input $(doc)' + $(env) latex '\nonstopmode\def\Status{2}\input $(doc)' + $(env) latex '\nonstopmode\def\Status{2}\input $(doc)' + $(env) latex '\nonstopmode\def\Status{2}\input $(doc)' + $(env) tex4ht $(doc) + $(env) t4ht $(doc) + +clean: + rm -f *.aux *.log *.blg *.toc *.out *.lot tex4ht.ps *.4* + rm -f *.xref* *.lg *.idv *.out *.otc *.tmp tmp.* + rm -f $(doc).dvi $(doc).ps + +realclean: clean + rm -f $(doc).pdf + rm -f *.html *.htm $(doc).css *.gif *.jpg + + +insttop = ../../../doc +instfiles = $(doc)*html $(doc).css $(doc).pdf +install: +# lang=`dirname \`pwd\` | sed 's,.*/,,'`; + lang=$(lang); \ + tldir=`pwd | sed 's,.*/,,'`; \ + instdir=$(insttop)/$$lang/$$tldir; \ + echo tldoc install to $$instdir; \ + for f in $(instfiles); do \ + cmp -s $$f $$instdir/$$f && rm -v $$f && continue; \ + mv -v $$f $$instdir/$$f; \ + done + + +# don't use these, they don't work. +dvi: + rm -f *.aux *.toc + latex '\nonstopmode\def\Status{0}\input $(doc)' + latex '\nonstopmode\def\Status{0}\input $(doc)' + latex '\nonstopmode\def\Status{0}\input $(doc)' + +baskerville: + rm -f *.aux *.toc + latex '\def\Status{3}\input $(doc)' + latex '\def\Status{3}\input $(doc)' + latex '\def\Status{3}\input $(doc)' + +tugboat: + rm -f *.aux *.toc + latex '\def\Status{4}\input $(doc)' + latex '\def\Status{4}\input $(doc)' + latex '\def\Status{4}\input $(doc)' diff --git a/Master/texmf/doc/texlive/source/texlive-en/README b/Master/texmf/doc/texlive/source/texlive-en/README new file mode 100644 index 00000000000..dc5fb6b124d --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/README @@ -0,0 +1,5 @@ +$Id$ +TeX Live documentation. This file is public domain. + +We only generate the documentation in PDF and HTML formats -- see the +Makefile. This saves us having to have the images in EPS format too. diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/bv-live.tex b/Master/texmf/doc/texlive/source/texlive-en/archive/bv-live.tex new file mode 100644 index 00000000000..ad044e568cb --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/bv-live.tex @@ -0,0 +1,84 @@ +% this is the baskerville version of the live documentation +\providecommand{\Status}{3} + +\setcounter{errorcontextlines}{999} +\documentclass{article} +\advance\textwidth by 1in +\advance\oddsidemargin by -1in +\advance\evensidemargin by -1in +\newsavebox{\warnbox} +\def\Q#1{\par\vskip6pt\leftline{#1}\par} +\setcounter{tocdepth}{2} +\pretolerance=1000 +\tolerance=1500 +\hbadness=3000 +\vbadness=3000 +\hyphenpenalty=400 +\renewcommand{\topfraction}{0.85} +\renewcommand{\floatpagefraction}{0.86} +\renewcommand{\textfraction}{0.1} +\setcounter{topnumber}{5} +\setcounter{totalnumber}{5} +\def\eTeX{$\varepsilon$-\TeX} +%\def\CTAN{\textsc{ctan}} +%\def\TUB{\textsc{tub}} +\def\Dash{---} +\def\hyph{-} +%\def\TeXXeT{\TeX-XeT} +\def\OMEGA{$\Omega$} +\def\bs{{\protect\normalfont\ttfamily\char'134}} +\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} +%\def\cs#1{\mbox{\normalfont\ttfamily\bs#1}} +\def\La{La} +\let\textsl\textit +\let\sl\it +\let\slfamily\itfamily +\def\ttdefault{cmtt} +\usepackage{tex-live} +\begin{document} +%\author{Sebastian Rahtz\\ +%\texttt{s.rahtz@elsevier.co.uk}\\ +%Michel Goossens\\ +%\texttt{m.goossens@cern.ch}} +%\title{The \protect\TeX\ Live Guide, 3rd edition} +%\date{March 1998} + +\BASKyear{1998} +\BASKmonth{April} +\BASKvol{8} +\BASKno{2} +\BASKed*{Robin Fairbairns} +\BASKfonts{Y\&Y European Modern} +\makeBSKtitle + +\input editorial +\ifbaskerville +\end{multicols} +%\vfill\Dings\vfill +\fi +\clearpage + +\begin{center} + \LARGE The \TeX\ Live Guide, 3rd edition +\end{center} +\title{\TeX\ Live Guide, 3rd edition} + +\ifbaskerville\begin{multicols}{2}\fi +\tableofcontents +\listoftables +\ifbaskerville +\end{multicols} +\Dings +\fi + +\input tex-live +\appendix + +\Dings + +\input live-app + +\vfill\Dings\vfill +\clearpage +\input sec +\end{document} diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/bvoutln.sty b/Master/texmf/doc/texlive/source/texlive-en/archive/bvoutln.sty new file mode 100644 index 00000000000..92f19fd027b --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/bvoutln.sty @@ -0,0 +1,193 @@ +% extracts of baskerville.cls for use with the tex-live documentation +% when we're producing a bv issue with it. + +% **************************************** +% * PAGE LAYOUT * +% **************************************** +% +% SIDE MARGINS: +\oddsidemargin -2.5pc \evensidemargin -2.5pc +\marginparwidth 4pc % don't use marginal notes... +\marginparsep 0.5pc % ...in the UK TUG newsletter + +% VERTICAL SPACING: +\topmargin -3pc +\headheight 12\p@ +\headsep 15\p@ +\topskip 10\p@ +\footskip 15\p@ + +% DIMENSION OF TEXT: + +\textheight 250mm % height of text on a page (A4 paper) +\textwidth 180mm % total width of a page +\columnseprule 0.5\p@ % width of line in the inter-column gutter +\columnsep 10mm % space between columns +\tolerance 9999 % make those columns justify + +% FOOTNOTES: +\footnotesep 6\p@ +\skip\footins 19.5\p@ plus 12\p@ \@minus 1\p@ + +% FLOATS: +\floatsep 12\p@ plus 5.5\p@ \@minus 1\p@ +\textfloatsep 15\p@ plus 4.5\p@ \@minus 3\p@ +\intextsep 12\p@ plus 5.5\p@ \@minus 2\p@ +\dblfloatsep 12\p@ plus 5.5\p@ \@minus 2\p@ +\dbltextfloatsep 15\p@ plus 4.5\p@ \@minus 3\p@ +\@fptop 0\p@ plus 0fil +\@fpsep 12\p@ plus 0fil +\@fpbot 0\p@ plus 3fil +\@dblfptop 0\p@ plus 0fil +\@dblfpsep 12\p@ plus 0fil +\@dblfpbot 0\p@ plus 3fil +\marginparpush 5\p@ + +% **************************************** +% * TITLES AND ABSTRACT * +% **************************************** +% + +%% Volume Number (ie Year - 1990) +\def\BASKvol#1{\gdef\BASK@vol{#1}} +\BASKvol{?} + +%% Issue Number (ie Month/2, roughly) +\def\BASKno#1{\gdef\BASK@no{#1}} +\BASKno{?} + +% Editor, Star form for Guest editor +\def\BASKed{\@ifstar{\BASK@ed{Guest }}{\BASK@ed{}}} +\def\BASK@ed#1#2{\gdef\BASK@editor{#1Editor: #2}} +\BASKed{????????} + +%% Year (4 digits) +\def\BASKyear#1{\gdef\thisyear{#1}} +\BASKyear{????} + +% Month (as a Word) +\def\BASKmonth#1{\gdef\thismonth{#1}} +\BASKmonth{?????} + +\def\makeBSKtitle{\par + \begingroup + \vspace*{-\headheight}% + \@maketitle + \bigskip\hrule\bigskip + \thispagestyle{plain} + \endgroup + \let\maketitle\relax + \let\@maketitle\relax +} +\newbox\BSKbox +\def\@maketitle{% + \centerline{\BASK@titleline}% + \medskip + \hbox to \textwidth{\bfseries The Annals of the UK \TeX\ Users + Group\hfill \BASK@editor\hfill Vol.~\BASK@vol\ No.~\BASK@no}% + \smallskip\hbox to \textwidth{\bfseries ISSN 1354--5930 + \hfill \thismonth\ \thisyear}% + \medskip + \noindent\ignorespaces + \BASK@headparone} + +% The Journal title command. +% You probably only want to change this if you want to use a design-size +% font rather than let \scaletowidth scale for some special issue. +\def\BASKtitle#1{\gdef\BASK@titleline{#1}} +\let\scaletowidth=\resizebox% added by Sean K. Harbour for Textures +\BASKtitle{% + \fontfamily{mbvx}\bfseries + \scaletowidth{\textwidth}{!}{% modified by Sean K. Harbour + B\,a\,s\,k\,e\,r\,v\,i\,l\,l\,e}} + + +% The first paragraph. Needs to be reset if a special issue used a +% different font set. +\def\BASKheadparone#1{\gdef\BASK@headparone{#1}} +\BASKheadparone{% +This issue of \BV\ is set in \@BASKfonts, and printed on a Xerox Docutech. Production and distribution is +undertaken in Cambridge by Robin Fairbairns. } + + +\def\BASKfonts#1{\gdef\@BASKfonts{#1}} +\BASKfonts{Monotype Baskerville, with Computer Modern Typewriter for + literal text} + +% +% for \Dings +\RequirePackage{pifont} +% +% available for inter-article dinglines +% +\def\Dings{\nopagebreak{\footnotesize\dingline{167}}} + +% +% hack representation of appendices +\let\BV@@appendix\appendix +\renewcommand{\appendix}{\BV@@appendix + \renewcommand\@seccntformat[1]{\@ifundefined{@seccnt@##1}% + {\csname the##1\endcsname\quad}% + {\csname @seccnt@##1\endcsname}} + \newcommand\@seccnt@section{Appendix~\thesection~} +} + +% +% page styles +% +% \ps@empty defined in LATEX.TEX +% +\def\ps@plain{\let\@mkboth\markboth + \def\@oddhead{} + \def\@evenhead{} + \def\@oddfoot{\rm \hfil --\thepage--\hfil} + \def\@evenfoot{\rm \hfil --\thepage--\hfil} +} +\def\ps@headings{\let\@mkboth\markboth + \def\@oddhead{\hfill\emph{\@title}\hfill} + \def\@oddfoot{\rm \hfil --\thepage--\hfil} + \def\@evenhead{\it Baskerville \hfill + Volume \BASK@vol, Number \BASK@no} + \def\@evenfoot{\rm \hfil --\thepage--\hfil} +} + +% +% allow setting of pagehead title +\def\title{\@ifnextchar [{\@titletwo}{\@titleone}} +\def\@titletwo[#1]#2{\gdef\@title{#1}\gdef\@longtitle{#2}} +\def\@titleone#1{\gdef\@title{#1}\gdef\@longtitle{#1}} + +% +% more exciting page parameters +\@twosidetrue +\pagestyle{headings} + +\providecommand{\ukt}{UK \acro{TUG}} + +\newcommand{\standardtitles}{% + \def\section{%\typeout{** section!}% + \@startsection {section}{1}{\z@} + {-12\p@ \@plus -6\p@ \@minus -.1\p@} + {6\p@} + {\raggedright\large\bfseries}} + \def\subsection{\@startsection{subsection}{2}{\z@} + {-4\p@ \@plus -2\p@ \@minus -.1\p@} + {0.1\p@ \@plus 2\p@} + {\raggedright\normalsize\itshape}} + \def\subsubsection{\@startsection{subsubsection}{3}{\z@} + {-6\p@ \@plus -3\p@ \@minus -1\p@} + {0.1\p@ \@plus 2\p@} + {\raggedright\normalsize\it}} + \def\paragraph{\@startsection{paragraph}{4}{\z@} + {12\p@ \@plus 2.25\p@ \@minus -1\p@} + {-0.5em} + {\normalsize\bfseries}} + \def\subparagraph{\@startsection{subparagraph}{5}{\z@} + {12\p@ \@plus 2.25\p@ \@minus 1\p@} + {-0.5em} + {\normalsize\it}} + \setcounter{secnumdepth}{-1} +} + +\endinput + diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/changemail b/Master/texmf/doc/texlive/source/texlive-en/archive/changemail new file mode 100644 index 00000000000..dd792a25f78 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/changemail @@ -0,0 +1,24 @@ +s/J.Smart@ed.ac.uk/??/ +s/gerd@uni-koblenz.de/??/ +s/Meijer@rulfsw.fsw.LeidenUniv.nl/??/ +s/wl@gnu.org/xlwy01@uxp1.hrz.uni-dortmund.de/ +s/weissert@SJUPHIL.SJU.EDU/Tom@Weissert.net/ +s/mehlich@informatik.uni-muenchen.de/mmehlich@semdesigns.com/ +s/eijkhout@math.ucla.edu/victor@eijkhout.net/ +s/ca_rowley@vax.acs.open.ac.uk/c.a.rowley@open.ac.uk/ +s/B.Jackowski@gust.s.org.pl/B.Jackowski@gust.org.pl/ +s/P.Pianowski@gusts.org.pl/P.Pianowski@gust.org.pl/ +s/mittelbach@mzdmza.zdv.uni-mainz.de/Frank.Mittelbach@Uni-Mainz.de/ +s/mcjones@pa.dec.com/paul.mcjones@acm.org/ +s/h.harders@tu-bs.de/Harald.Harders@dlr.de/ +s/pwilson@cme.nist.gov/peter.r.wilson@boeing.com/ +s/wikner@ariel.nac.ac.za/wikner@nac.ac.za/ +s/vitus@agropc.msk.su/vitus@ice.ru/ +s/greg@bic.mni.mcgill.ca/gward@python.net/ +s/mittelbach@mzdmza.zdv.uni-mainz.de/frank.mittelbach@latex-project.org/ +s/fbraun@rz.uni-potsdam.de/fbraun@atdot.org/ +s/david@dcarlisle.demon.co.uk/david.carlisle@latex-project.org/ +s/davidc@nag.co.uk/david.carlisle@latex-project.org/ +s/rf@cl.cam.ac.uk/rf10@cam.ac.uk/ +s/robin.fairbairns@cl.cam.ac.uk/rf10@cam.ac.uk/ +s/robin@lsl.co.uk/rf10@cam.ac.uk/ \ No newline at end of file diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/l.pl b/Master/texmf/doc/texlive/source/texlive-en/archive/l.pl new file mode 100644 index 00000000000..d74f313a5cc --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/l.pl @@ -0,0 +1,44 @@ +require "status.pl"; +require "texlive.pl"; +while (<>) { + chop; + s/,$//; + if (/^\@TeXIndex/) + { + ($nam) = /^\@TeXIndex.(.*)/; + print "\@TeXIndex\{$nam"; + $Status=1; + $Texlive=1; + $Modified=0; + } + elsif (/^ *modified/) { s/, *$//; $mod=$_; } + elsif (/^ *status/) { $Status=0; + if ($L{$nam}) + { print ",\n status\t= \{$L{$nam}\}"; + $Modified=1;} + else { print ",\n$_"; } + } + elsif (/^ *texlive/) { $Texlive=0; + if ($texlive{$nam} ne "") + { print ",\n texlive\t= \{$texlive{$nam}\}"; + $Modified=1;} + } + elsif (/^}/) { + if ($Status) { + print ",\n status\t= \{unknown\}"; + } + if ($Texlive && $texlive{$nam} ne "") + { print ",\n texlive\t= \{$texlive{$nam}\},\n"; } + if ($Modified) + { print ",\n modified\t= {1999/03/26 10:00:00 }\n"; } + elsif ($M{$nam} ne "") + { print ",\n modified\t= \{$M{$nam}\}\n"; } + else + {print ",\n$mod\n"; } + print "}\n"; + } + + elsif (/= {/) { print ",\n$_"; } + else { print "\n$_"; } + } + diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/live-2003.tex b/Master/texmf/doc/texlive/source/texlive-en/archive/live-2003.tex new file mode 100644 index 00000000000..55c1551a628 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/live-2003.tex @@ -0,0 +1,3937 @@ +% $Id$ +% change history (started May 13th 2002) +% 2003/09/06: fixes from Staszek +% 2003/09/05: touched by Karl +% 2003/09/04: fixes from Staszek and Fabrice +% 2003/09/01: fixes from Volker +% 2003/08/24: win32 updates, by Fabrice +% 2003/08/12: fixes from Christer Gustafsson . +% 2003/07/07: substantial revisions by karl. +% 2002/05/25: remove mention of sizes, and bsr-interpolated; add Gutenberg +% 2002/05/18: win32 updates, by Fabrice +% 2002/05/14: corrected example files, other small errors noted by Volker +% 2002/05/13: added tex-langafrican to list of collections +% +\documentclass{article} +\usepackage{tex-live} +% +% +\begin{document} + +\title{{\huge\textsf{\TK{} 2003}}\\[3mm] + The \protect\TeXLive{} Guide} +\date{September 2003} + +\author{Sebastian Rahtz, editor \\[3mm] + \email{tex-live@tug.org}\\ + \url{http://tug.org/texlive/}\\[10mm] +\ifnum \Status=2 + \includegraphics[bb=0 0 824 741]{../pictures/front.jpg} \\[5mm] +\else + \includegraphics[width=.5\linewidth]{../pictures/front} \\[5mm] +\fi + \small \textit{Documentation contacts:}\\[3mm] + \small \begin{tabular}{lcr} + Czech/Slovak & Petr Sojka & \email{sojka@fi.muni.cz} \\ + & Janka Chleb\'\i kov\'a & \email{chlebikj (at) dcs.fmph.uniba.sk} \\ + English & Karl Berry & \email{karl@freefriends.org} \\ + French & Fabrice Popineau & \email{fabrice.popineau@supelec.fr} \\ + German & Volker RW Schaa & \email{volker@dante.de} \\ + Polish & Staszek Wawrykiewicz & \email{staw@gust.org.pl} \\ + Russian & Boris Veytsman & \email{borisv@lk.net} \\ + \end{tabular} + } + +% comes out too close to the toc, and we know it's page one anyway. +\thispagestyle{empty} + +\maketitle +\newpage + +\begin{multicols}{2} +\tableofcontents +\listoftables +\end{multicols} + +\section{Introduction} +\label{sec:intro} + +This document describes the main features of the \TeXLive{} software +distribution\Dash a \TeX{} and \LaTeX{} distribution for Linux and other +Unix flavors, \MacOSX, and (32-bit) Windows systems. (Warning: it is +not especially useful for older Mac or \acro{MS-DOS} systems.) It +includes precompiled binaries for \TeX{}, \LaTeXe{}, \MF, \MP, +\BibTeX{} and many other programs; an extensive collection of +macros, fonts and documentation; and support for typesetting in many +different scripts from around the~world. + +For the 2003 release, the last update of packages and programs was made +on September 3, 2003. For newer versions, please consult \acro{CTAN}, +\url{http://www.ctan.org}. + +For a brief summary of the major changes in this edition of \TeXLive{}, +see section~\ref{sec:history} on p.~\pageref{sec:history}. + + +\subsection{Basic usage of \protect\TeXLive{}} +\label{sec:basic} + +You can use \TeXLive{} in three principal ways: + +\begin{enumerate} + +\item You can run \TeXLive{} directly from the distribution media +(except for the \pkgname{inst} distribution; see +section~\ref{sec:multiple-dist} on p.~\pageref{sec:multiple-dist}). +This takes almost no disk space, as you might expect, and gives you +immediate access to everything in \TeXLive{}. Of course performance +will be worse than running on local disk, but you may well find it +acceptable. + +\item You can install all or part of \TeXLive{} to a local disk. This +is the most common use of \TeXLive. You will need a minimum of 120 +megabytes, 360 megabytes for a recommended system, and 800 megabytes for +a full system. + +\item You can integrate a particular package or collection into your +existing \TeX{} system, either a \TeXLive{} system you installed earlier +or a different system. + +\end{enumerate} + +\noindent All of these are described in detail in the \acro{OS}-specific +installation sections. + + +\subsection{Getting help} +\label{sec:help} + +The \TeX{} community is both active and friendly, and virtually all +serious questions end up getting answered. However, the support is +informal, done by volunteers and casual readers, so it's especially +important that you do your homework before asking. (If you prefer +commercial-style support, you can forego \TeXLive{} completely and +purchase a vendor's system; see +\url{http://tug.org/interest.html#vendors} for a list.) + +Here is a list of resources, approximately in the order we recommend +using them: + +\begin{description} +\item [\TeX{} \acro{FAQ}] The \TeX{} \acro{FAQ} is a huge compendium of +answers to all sorts of questions, from the most basic to the most +arcane. It is included on \TeXLive{} in \OnCD{FAQ/english}, and is +available on the Internet through \url{http://faq.tug.org}. Please +check here first. + +\item [\TeX{} Catalogue] If you are specifically looking for a package, +font, program, etc., the \TeX{} Catalogue is the place to look. It is a +huge list of all \TeX{}-related items. See +\OnCD{texmf/doc/html/catalogue}, or +\url{http://www.ctan.org/tex-archive/help/Catalogue/catalogue.html}. + +\item [\TeX{} Web Resources] This web page has many \TeX{}-related +links, in particular for numerous books, manuals, and articles on all +aspects of the system: \url{http://tug.org/interest.html}. + +\item [support archives] The two principal forums for support are the +Usenet newsgroup \url{news:comp.text.tex} and the mailing list +\email{texhax@tug.org}. So, their archives have thousands of past +questions and answers for your searching pleasure. See +\url{http://groups.google.com/groups?group=comp.text.tex} and +\url{http://tug.org/mail-archives/texhax}, respectively. A query on a +general web search engine, such as \url{http://google.com}, never hurts. + +\item [posting questions] If you cannot find an answer, you can post to +\dirname{comp.text.tex} through Google or your newsreader, or through +email to \email{texhax@tug.org}. But before you post, \emph{please} +read this \acro{FAQ} entry for advice on asking questions in such a way +that you're most likely to get an answer: +\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. + +\item [\TeXLive{} support] If you want to report a bug or have +suggestions or comments on the \TeXLive{} distribution, installation, or +documentation, the mailing list is \email{tex-live@tug.org}. However, +if your question is about how to use a particular program included in +\TeXLive{}, you are better off writing to that program's maintainer or +mailing list. + +\end{description} + +The other side of the coin is helping others who have questions. Both +\dirname{comp.text.tex} and \code{texhax} are open to anyone, so feel +free to join, start reading, and help out where you can. Welcome to +\TeX{}! + + +\section{Structure of \protect\TeXLive} +\label{sec:struct-tl} + +The main two installation scripts for Unix and \MacOSX{} are +\texttt{install-tl.sh} and \texttt{install-pkg.sh}. We discuss them +in section \ref{sec:unix-install} on p.~\pageref{sec:unix-install}. +Here, we describe the structure and contents of \TeXLive{}. + + +\subsection{Multiple distributions: \protect\pkgname{live}, + \protect\pkgname{inst}, \protect\pkgname{demo}} +\label{sec:multiple-dist} + +As of 2003, space limitations of \acro{CD-ROM} format have forced us to +divide \TeXLive{} into three distributions, as follows. + +\begin{description} + +\item [live] a complete, runnable system on \acro{DVD}; it is too large +for \acro{CD-ROM}. (The \DVD{} also includes a snapshot of the \CTAN{} +repository, completely independent of \TeXLive{}.) + +\item [inst(allable)] a complete system on \CD; in order to make it fit, +we had to compress everything we could. Therefore, it is not possible +to run \TeX\ directly from the installable \CD, you have to install it to +disk (hence its name). Installation is described in subsequent sections. + +\item [demo] a live system runnable directly from \CD; in order to make +this fit, we omitted the very large collection of \acro{CJK} (Chinese, +Japanese, Korean) language support, support for typesetting music, some +less-commonly used fonts, and included executables only for Linux, +\MacOSX, and Windows systems. + +\end{description} + +\noindent You can tell which type of distribution you're in by looking +for a \texttt{00\var{type}.TL} file in this top-level directory. + + +\subsection{Top level directories} + +Here is a brief listing and description of the top level directories in +the \TeXLive{} distribution. + +\smallskip +\begin{tabular}{>{\ttfamily}lp{.8\hsize}} +bin & The \TeX{} system programs, arranged by platform. \\ +Books & Examples from some of the books about \TeX\ (see + \filename{Books/README}). \\ +FAQ & Current versions of major FAQ collections. \\ +info & A few manuals in \acro{GNU} Info format, where available. \\ +\MacOSX & Supporting software for \MacOSX (see + section~\ref{sec:mac-install} on p.~\pageref{sec:mac-install}). \\ +man & Unix man pages. \\ +source & The source of all programs, including the main \Webc{} + \TeX{} and \MF{} distributions. These are stored in a + \cmdname{bzip2}-compressed tar archive. \\ +support & assorted auxiliary packages and programs. These are + \emph{not} installed by default. This includes + \cmdname{Ghostscript}, \cmdname{netpbm}, and assorted editors and + \TeX\ shells. \\ +texmf & root of installed packages, fonts, config files, etc. \\ +usergrps & Material about a few of the \TeX\ user groups. (Visit + \url{http://tug.org/usergroups.html} for a current list.) \\ +xemtex & The \cmdname{XEmacs} editor and other support programs for + Windows (see section~\ref{sec:win-xemtex} on p.~\pageref{sec:win-xemtex}). + These programs generally come pre-installed on Unix systems, or are + at least easy to compile. \\ +\end{tabular} + + +\subsection{Extensions to \TeX} +\label{sec:tex-extensions} + +\TeXLive{} contains three extended versions of \TeX: + +\begin{description} + +\item [\eTeX] adds a small but powerful set of new primitives +\label{text:etex} +(related to macro expansion, character scanning, classes of marks, +additional debugging features, and more) and the \TeXXeT{} extensions +for bidirectional typesetting. In default mode, \eTeX{} is 100\% +compatible with ordinary \TeX. See +\OnCD{texmf/doc/etex/base/etex_man.pdf}. \eTeX{} is now the default for +\LaTeX{} and pdf\LaTeX{}. + +\item [pdf\TeX] writes Acrobat PDF format as well as \dvi{}. The +\LaTeX{} \pkgname{hyperref} package has an option `\optname{pdftex}' +which turns on all the program features. See +\OnCD{texmf/doc/pdftex/pdftex-l.pdf} and +\OnCD{texmf/doc/pdftex/base/example.tex}. + +\item [\OMEGA\ (Omega)] based on Unicode (16-bit characters), thus +supports working with almost all the world's scripts simultaneously. It +also supports so-called `\OMEGA{} Translation Processes' (\acro{OTP}s), +for performing complex transformations on arbitrary input. See +\OnCD{texmf/doc/omega/base/doc-1.8.tex} (not completely up-to-date). + +\end{description} + + +\subsection{Other notable programs in \protect\TeXLive} + +Here are a few other commonly-used programs included in \TeXLive{}: + +\begin{cmddescription} + +\item [bibtex] bibliography support. + +\item [makeindex] index support. + +\item [dvips] convert \dvi{} to \PS{}. + +\item [xdvi] \dvi{} previewer for the X Window System. + +\item [dvilj] HP LaserJet driver. + +\item [dv2dt, dt2dv] convert \dvi{} to/from plain text. + +\item [dviconcat, dviselect] cut and paste pages +from \dvi{} files. + +\item [dvipdfm] convert \dvi{} to PDF, an alternative approach +to pdf\TeX\ (mentioned above). See the \pkgname{ps4pdf} and +\pkgname{pdftricks} packages for still more alternatives. + +\item [psselect, psnup, \ldots] \PS{} +utilities. + +\item [lacheck] \LaTeX{} syntax checker. + +\item [texexec] Con\TeX{}t and PDF processor. + +\item [tex4ht] \TeX{} to HTML converter. + +\end{cmddescription} + + +\section{Unix installation} +\label{sec:unix-install} + +As introduced in section~\ref{sec:basic} on p.~\pageref{sec:basic}, +\TeXLive{} has three principal uses: + +\begin{enumerate} +\item Run directly from media. +\item Install to disk. +\item Integrate a particular package or collection into your existing +\TeX{} installation. +\end{enumerate} + +\noindent The following sections describes the Unix-specific procedures +for each of these. + +\ifSingleColumn \begin{figure}[ht]\noindent \fi +\begin{warningbox} +\textbf{Warning: } The \TK{} \CD{}s and \DVD{} are in ISO 9660 (High Sierra) +format, \emph{with} Rock Ridge (and Joliet, for Windows) +extensions. Therefore, in order to take full advantage of the \TK{} +under Unix, your system needs to be able to use the Rock Ridge +extensions. Please consult the documentation for your \cmdname{mount} +command to see how to do this. If you have several different machines +on a local network, you may be able to mount the \CD{}s on one which +does support Rock Ridge, and use this with the others. + +\leavevmode\quad Linux, Free\acro{BSD}, Sun, \acro{SGI} and +Alpha systems should be able to use the \CD{}s without problems. We +would appreciate receiving detailed advice from users on other systems +who succeed, for future versions of this documentation. + +\leavevmode\quad +The discussion below assumes you have been able to mount +the \CD{}s with full Rock Ridge compatibility. +\end{warningbox} +\ifSingleColumn\end{figure}\fi + + +% +\subsection{Running \protect\TeXLive{} directly from media (Unix)} + +\def\runlive{% text repeated in windows section +It is possible to use the \TeX{} system directly from the \pkgname{demo} +\CD{} or the \pkgname{live} \DVD{}, without installing the distribution +to disk. (Thus the name `\TeXLive', in fact.) It is \emph{not} +possible to run \TeX{} directly from the \pkgname{inst} \CD (see +section~\ref{sec:multiple-dist} on p.~\pageref{sec:multiple-dist}). +} + +Only Linux, \MacOSX, and Windows binaries are included on the demo \CD; +if you want to run live on other Unix systems, you'll need to use the +\DVD. + +\def\startinst{% repeated in other subsections +To start, we must mount the \CD{} or \DVD{}, with Rock Ridge extensions +enabled. The exact command to do this varies from system to system; the +following works under Linux, except the name of the device +(\filename{/dev/cdrom}, here) may vary. (All our examples will use +\texttt{>} as the shell prompt; user input is \underline{underlined}.) +\begin{alltt} +> \Ucom{mount -t iso9660 /dev/cdrom /mnt/cdrom} +\end{alltt} + +\noindent Change the current directory to the mount point: +\begin{alltt} +> \Ucom{cd /mnt/cdrom} +\end{alltt} + +\noindent Under \MacOSX, the directory is typically under +\dirname{/Volumes}, and the media will be mounted automatically. +} + +\startinst + +Run the installation script \filename{install-tl.sh}: +\begin{alltt} +> \Ucom{sh install-tl.sh} +Welcome to TeX Live... +\end{alltt} + +\def\firstinstcommand{% +\noindent After various greeting messages and a list of the main menu +options, the installation will ask you to enter a command. Do this by +typing the desired character and hitting return; don't type the angle +brackets. Either uppercase or lowercase is ok; we'll use lowercase in +our examples. +} +\firstinstcommand + +For running live, our first command will be \Ucom{d} and then the +subcommand \Ucom{1} to set directories. Even in this case, we must +choose a directory on the local disk to place files that the \TeX{} +system itself generates, such as fonts and formats, and also to provide +a place for updated configuration files, if need be. We'll use +\dirname{/usr/local/texmf-local} in this example. (If the default value +of \dirname{/usr/TeX} works for you, then you can skip this step.) +\begin{alltt} +Enter command: \Ucom{d} +Current directories setup: +<1> TEXDIR: /usr/TeX +... +Enter command: \Ucom{1} +New value for TEXDIR [/usr/TeX]: \Ucom{/usr/local/texmf-local} +... +Enter command: \Ucom{r} +\end{alltt} + +\noindent Back at the main menu, our second and last command is +\Ucom{r}, to set up for running live off the media without installing +to disk: +\begin{alltt} +Enter command: \Ucom{r} +Preparing destination directories... +... +Welcome to the TeX Live system! +> +\end{alltt} + +\noindent And we are back at the system prompt, as shown. + +Next, it is necessary to alter two environment variables: +\envname{PATH}, to an architecture-dependent value (so that we can run +the programs), and \envname{VARTEXMF}, to the value specified above. See +table~\ref{tab:archlist} for a list of the architecture names for the +different systems, and whether they are available on the \pkgname{demo} +\CD. All systems are available in the \pkgname{inst} and \pkgname{live} +distributions. (In addition to the version-specific names listed here, +there are generic names without the version numbers. For instance, +\dirname{sparc-solaris} links to \dirname{sparc-solaris2.7}. The +generic names can be used to protect against the version numbers +changing in the future, if you wish.) + +\def\runtexconfig{% +After the main installation has completed, and environment variables +have been set, the next step is to run \cmdname{texconfig} to customize +your installation for your needs. This is explained in +section~\ref{sec:texconfig}, p.~\pageref{sec:texconfig}. +} +\runtexconfig + +\begin{table*}[ht] +\caption{Supported system architectures.} +\label{tab:archlist} +\begin{tabular}{>{\ttfamily}lll} +alpha-linux & HP Alpha Linux & \\ +alphaev5-osf4.0d & HP Alphaev5 OSF & \\ +%hppa2.0-hpux10.20 & HP9000 HPUX 10.20 & \\ +i386-freebsd4.8 & Intel x86 FreeBSD & \\ +i386-linux & Intel x86 GNU/Linux & demo \CD\\ +i386-openbsd3.3 & Intel x86 OpenBSD & \\ +i386-solaris2.8 & Intel x86 Solaris & \\ +mips-irix6.5 & SGI IRIX & \\ +powerpc-aix4.3.3.0 & IBM RS/6000 AIX & \\ +powerpc-darwin6.3 & \MacOSX & demo \CD\\ +sparc-solaris2.7 & Sun Sparc Solaris & \\ +sparc64-linux & Sun Sparc Linux & \\ +win32 & Windows (32-bit) & demo \CD\\ +\hline +\end{tabular} +\end{table*} + +\label{text:path} +The syntax for setting the environment variables, and the initialization +file to put them in, depends on the shell you use. If you use a +Bourne-compatible shell (\cmdname{sh}, \cmdname{bash}, \cmdname{ksh}, et +al.), put the following into your \filename{$HOME/.profile} file: +\begin{alltt} +PATH=/mnt/cdrom/bin/\Ucom{\emph{archname}}:$PATH; export PATH +VARTEXMF=/usr/local/texmf-local/texmf-var; export VARTEXMF +\end{alltt} + +\noindent For C shell-compatible shells (csh, tcsh), put the following +into your \filename{$HOME/.cshrc} file: +\begin{alltt} +setenv PATH /mnt/cdrom/bin/\Ucom{\emph{archname}}:$PATH +setenv VARTEXMF /usr/local/texmf-local/texmf-var +\end{alltt} + +\def\donewithinst{% +\noindent Then log out, log back in, and test your installation +(see section~\ref{sec:test-install} on p.~\pageref{sec:test-install}). +} +\donewithinst + +\def\ifindoubt{% +If in doubt, please ask any local system gurus to help you with +problems; for example, the way to mount the \TeXLive{} media, which +directory or directories to use, and precise details of the changes to +your personal initialization files can and do vary from site to site. +} +\ifindoubt + + +% +\subsection{Installing \protect\TeXLive{} to disk} +\label{sec:unix-install-disk} + +It is possible, indeed typical, to install the \TeX{} system from the +\TeXLive{} to disk. This can be done either from the \pkgname{live} +\DVD, or the \pkgname{inst} \CD. It can also be done from the +\pkgname{demo} \CD, if you don't need the omitted packages or systems. +(See section~\ref{sec:multiple-dist} on p.~\pageref{sec:multiple-dist} +for an explanation of the different distributions.) + +\startinst + +Run the installation script \filename{install-tl.sh}: +\begin{alltt} +> \Ucom{sh install-tl.sh} +Welcome to TeX Live... +\end{alltt} + +\firstinstcommand + +Here is an introductory list of the options in the main menu. The order +in which you select the options makes little difference, except that +\Ucom{i} must be last. It's reasonable to go through them in the +order presented~here. + +% apparently here.sty [H] doesn't support table*. +\begin{table}[H] +\caption{Main menu options for the installation.} +\label{tab:main-menu-options} +\begin{tabular}{>{\ttfamily}ll} +p & The system you are running on.\\ +b & The architectures to install binaries for.\\ +s & The base installation scheme to use (minimal, recommended, + full, etc.)\\ +c & Override the installation scheme for individual collections.\\ +l & Override for language collections.\\ +d & Directories in which to install.\\ +o & General options.\\ +i & Perform the installation.\\ +\end{tabular} +\end{table} + +Here are further details on each option. + +\textbf{\optname{p} -- Current platform.} Since the installation script +automatically guesses which platform you're running on, this is +generally unnecessary to override. It's there in case the automatic +detection fails. + +\textbf{\optname{b} -- Binary architectures.} By default, only the +binaries for your current platform will be installed. From this menu, +you can select installation of binaries for other architectures as well +(or not install the current platforms). This is often useful if you +are sharing a \TeX\ tree across a network of heterogenous machines. For +a list of the supported architectures, see table~\ref{tab:archlist}, +p.~\pageref{tab:archlist}. + +\textbf{\optname{s} -- Base installation scheme.} From this menu, you +can choose an overall common set of packages. The default is a +recommended set for typical needs, but you can also choose a basic set +to conserve disk space, or a full set to get absolutely everything. The +\pkgname{Live} scheme is used for creating the \TeXLive{} +\pkgname{demo} distribution itself, and isn't generally useful to select +for a particular site. There are also specific sets for Omega and +\acro{XML} users. + +\textbf{\optname{c} -- Individual collections.} From this menu, you can +override the basic scheme's choice of which collections to install. +Each collection\Dash TeX macro files, Metafont font families, and so +on\Dash consists of several packages. In this menu, selection letters +are case-sensitive. + +\textbf{\optname{l} -- Language collections}. This menu has the same +basic functionality as \Ucom{c}, to override collection choices. In +this case, the collections are specifically for different languages. +Selection letters are case-sensitive here. Here is a list of the +language collections in \TeXLive: + +% xx really should generate list from texmf/tpm/collection/tex-lang* +% a la install-tl.sh. +\begin{tabbing} +\hspace{.25\linewidth} \= +\hspace{.25\linewidth} \= +\hspace{.25\linewidth} \= +\hspace{.25\linewidth} \kill + (some) African scripts \> + Armenian \> + Chinese,Japanese,Korean \> +Croatian \\ + Cyrillic \> + Czech/Slovak \> + Danish \> +Dutch \\ + Finnish \> + French \> + German \> +Greek \\ + Hungarian \> + Indic \> + Italian \> +Latin \\ + Manju \> + Mongolian \> + Norwegian \> +Polish \\ + Portuguese \> + Spanish \> + Swedish \> +Tibetan \\ + \acro{UK} English \> +Vietnamese \\ +\end{tabbing} + +\noindent Language collections typically includes fonts, macros, +hyphenation patterns, and other support files. (For instance, +\pkgname{frenchle.sty} is installed if you select the \optname{French} +collection.) In addition, installing a language collection will alter +the \filename{language.dat} configuration file controlling which +hyphenations are loaded. + +\textbf{\optname{d} -- Installation directories}. Three directories can +be changed here: +\label{text:instdir} + +\begin{ttdescription} +\item [TEXDIR] By default, the top-level directory under which +everything else will be installed. The default value is +\dirname{/usr/TeX}, and is often changed. For example, changing to a +value such as \dirname{/usr/local/texlive2003} would make it possible to +keep different releases of \TeXLive{} separate. You may then wish to +make \dirname{/usr/local/texlive} a symbolic link, after testing the new +release. + +Under \MacOSX, the usual frontends look for \TeX{} in +\dirname{/usr/local/teTeX}, so you may wish to install \TeXLive{} there. + +\item [TEXMFLOCAL] This tree is where the \TeX{} system scripts install +non-version-specific files, primarily fonts. The default value is +\dirname{TEXDIR/texmf-local}. It's also the recommended location to put +any local packages or configuration settings. Therefore, it's desirable +to change it to a location independent of the current \TeXLive{} +release; for example, \dirname{/usr/local/texmf-local}. + +\item [VARTEXMF] This tree is where the scripts install files that +\emph{are} version-specific, primarily format files and the +configuration files which are modified by \cmdname{texconfig} (see +section~\ref{sec:texconfig}, p.~\pageref{sec:texconfig}). The default +value is \dirname{TEXDIR/texmf-var}, and there's generally no reason to +change it. + +\end{ttdescription} + +\textbf{\optname{o} - General options.} From this menu, you can select +three general options affecting the installation: + +\begin{ttdescription} +\item [a] Specify an alternate directory for generated fonts. +The default is to use the \envname{VARTEXMF} tree, as explained above. +Setting this is useful if you plan to mount the main tree read-only, and +therefore another location (perhaps machine-specific) must be used for +dynamically created fonts. + +\item [l] Create symbolic links for the binaries, man pages, +and/or \acro{GNU} Info files in other locations. For example, you may +wish to make the man pages available under \dirname{/usr/local/man} and +the Info files available under \dirname{/usr/local/info}. (Of course +you need appropriate privileges to write in the specified directories.) + +\item [d] Skip installation of the font/macro documentation tree. +This is useful to save space, or if you've previously installed the +documentation elsewhere. + +\item [s] Skip installation of the main font/macro source +tree. This is useful if you are arranging to share that tree between +machines and/or architectures in some other way, such as \acro{NFS} or +\cmdname{automount}. + +\end{ttdescription} + +\textbf{i - Perform installation.} When you're satisfied with your +configuration options, enter \Ucom{i} to actually do the installation +from the media to your chosen locations. + +The last step is to include the architecture-specific subdirectory of +\dirname{TEXDIR/bin} in your +\envname{PATH}, so the newly-installed programs can be found. The +architecture names are listed in table~\ref{tab:archlist}, +p.~\pageref{tab:archlist}, or you can simply list the directory +\dirname{TEXDIR/bin}. + +The syntax for doing this, and the initialization file to put it in, +depends on the shell you use. If you use a Bourne-compatible shell +(\cmdname{sh}, \cmdname{bash}, \cmdname{ksh}, et al.), put the following +into your \filename{$HOME/.profile} file: +\begin{alltt} +PATH=/\Ucom{\emph{TEXDIR}}/bin/\Ucom{\emph{archname}}:$PATH; export PATH +\end{alltt} + +\noindent For C shell-compatible shells (\cmdname{csh}, \cmdname{tcsh}), +put the following into your \filename{$HOME/.cshrc} file: +\begin{alltt} +setenv PATH /\Ucom{\emph{TEXDIR}}/bin/\Ucom{\emph{archname}}:$PATH +\end{alltt} + +\runtexconfig + +Here is a brief annotated example which selects a full installation, +with binaries for the current system only, with directory changes as +recommended above. The prompts and \acro{RETURN} keys are omitted for +brevity. + +\begin{alltt} +> \Ucom{sh install-tl.sh} +\Ucom{s} \Ucom{b} \Ucom{r} # scheme, full, return to main +\Ucom{d} # change directories +\Ucom{1} \Ucom{/usr/local/texlive2003} # top-level dir +\Ucom{2} \Ucom{/usr/local/texmf-local} # TEXMFLOCAL outside TEXDIR +\Ucom{r} # return to main +\Ucom{i} # perform installation +> \Ucom{texconfig} ... +# New PATH, assuming Linux: +> \Ucom{PATH=/usr/local/texlive2003/bin/i386-linux:$PATH; export PATH} +\end{alltt} + +\ifindoubt + + +% +\subsection{Installing individual packages to disk} + +You can add individual packages or collections from the current +distribution to an existing non-\TeXLive{} setup, or an earlier +\TeXLive{} installation. You can do this from the \pkgname{demo} \CD{} +or the \pkgname{live} \DVD{}, but \emph{not} from the \pkgname{inst} +\CD. (See section~\ref{sec:multiple-dist} on +p.~\pageref{sec:multiple-dist}.) + +\startinst + +Run the installation script \filename{install-pkg.sh} (not +\filename{install-tl.sh}, which is intended for complete installations +only): +\begin{alltt} +> \Ucom{sh install-pkg.sh \emph{options}} +\end{alltt} + +This first set of options controls what gets read: + +\begin{ttdescription} +\item [-{}-package=\emph{pkgname}] The individual package to work on. + +\item [-{}-collection=\emph{colname}] The individual collection to work on. + +\item [-{}-nodoc] Exclude documentation files from the operation. + +\item [-{}-nosrc] Exclude source files from the operation. + +\item [-{}-cddir=\emph{dir}] Source directory to read from; defaults +to the current directory. If you followed the instructions above, that +will be the distribution directory, and won't need to be changed. + +\item [-{}-listdir=\emph{dir}] The so-called `lists' directory within +\emph{cddir} from which to read the package information. The default is +\texttt{\emph{cddir}/texmf/tpm/lists}; the only reason to change it is +if you're making changes to \TeXLive{} yourself. + +\end{ttdescription} + +What actually happens is controlled by the following options. If +neither of these are specified, the default action is to install the +selected files. The main destination tree is found by expanding +\envname{\$TEXMFMAIN} with \cmdname{kpsewhich}. You can override it by +setting either the environment variable \envname{TEXMFMAIN} or +\envname{TEXMF}. + +\begin{ttdescription} +\item [-{}-listonly] List the files that would be installed, but don't +actually install anything. + +\item [-{}-archive=\emph{tarfile}] Instead of installing the files into +the \TeX{} system, make a \cmdname{tar} archive. + +\end{ttdescription} + +Additional options: + +\begin{ttdescription} + +\item [-{}-config] After installation, run \code{texconfig init}. + +\item [-{}-nohash] After installation, don't run \cmdname{mktexlsr} to +rebuild the filename database. + +\item [-{}-verbose] Give more information as the script runs. + +\end{ttdescription} + +Here are some usage examples: + +\begin{enumerate} + +\item To see the files in the package \pkgname{fancyhdr} without +installing it: + +\begin{alltt} +\ifSingleColumn> \Ucom{sh install-pkg.sh --package=fancyhdr --listonly} +\else> \Ucom{sh install-pkg.sh --package=fancyhdr \bs} +> \Ucom{--listonly} +\fi{} +texmf/doc/latex/fancyhdr/README +texmf/doc/latex/fancyhdr/fancyhdr.dvi +texmf/doc/latex/fancyhdr/fancyhdr.pdf +... +\end{alltt} + +\item Install the \LaTeX{} package \pkgname{natbib}: +\begin{alltt} +> \Ucom{sh install-pkg.sh --package=natbib} +\end{alltt} + +\item Install the \LaTeX{} package \pkgname{alg} without source files or +documentation: +\begin{alltt} +\ifSingleColumn> \Ucom{sh install-pkg.sh --package=alg --nosrc --nodoc} +\else> \Ucom{sh install-pkg.sh -{}-package=alg \bs} +> \Ucom{-{}-nosrc -{}-nodoc} +\fi\end{alltt} + +\item Install all the packages in the collection of additional +plain \TeX\ macros: +\begin{alltt} +> \Ucom{sh install-pkg.sh --collection=tex-plainextra} +\end{alltt} + +\item Write all files in the \pkgname{pstricks} package to a +\cmdname{tar} file in \path|/tmp|: +\begin{alltt} +\ifSingleColumn> \Ucom{sh install-pkg.sh --package=pstricks --archive=/tmp/pstricks.tar} +\else +> \Ucom{sh install-pkg.sh -{}-package=pstricks \bs} +> \Ucom{-{}-archive=/tmp/pstricks.tar} +\fi\end{alltt} + +\end{enumerate} + +\ifindoubt + + +% +\section{Post-installation} +\label{sec:postinstall} + +After the main installation is done, for any operating system, the +remaining steps are to configure the system for your local needs, and +perform some basic tests. + +Another sort of post-installation is to acquire packages, fonts, or +programs that were not included in \TeXLive{}. The basic idea is to +install such additions in the \envname{TEXMFLOCAL} tree (if you +installed to disk), or \envname{VARTEXMF} (if you are running live). +See ``Installation directories'' on p.~\pageref{text:instdir}. + +Unfortunately, the details can vary widely, and so we do not attempt to +address them here. Please see +\url{http://www.ctan.org/tex-archive/info/beginlatex/html/chapter5.html#pkginst} +for a good description, and +\url{http://www.ctan.org/tex-archive/info/Type1fonts} for font creation +and installation information in particular. + + +\subsection{The \protect\cmdname{texconfig} program} +\label{sec:texconfig} + +At any time after installation, you can and should use the program +\cmdname{texconfig} to configure the system to fit your local needs. It +is installed in the architecture-specific subdirectory +\texttt{TEXDIR/bin/\emph{arch}} along with everything else. + +If you run it without arguments, it will enter full-screen mode and +allow you to view and change options interactively. + +You can also run it with various command-line options. Here are some of +the most commonly used: + +\begin{ttdescription} + +\item [texconfig dvips paper letter] Set default paper size for +\cmdname{dvips} to be letter-size. + +\item [texconfig xdvi us] Likewise, for \cmdname{xdvi}. + +\item [texconfig rehash] Update all the \TeX{} system filename databases. + +\item [texconfig faq] Show the \teTeX{} \acro{FAQ}. +(See also the main \TeX{} \acro{FAQ} in the \dirname{FAQ} subdirectory +of \TeXLive.) + +\item [texconfig help] Output help information. + +\end{ttdescription} + +Of course, \cmdname{texconfig} only supports changing a few of the many +options and configuration parameters in a \TeX{} system. The main +configuration file for the base \Webc{} programs is named +\filename{texmf.cnf}. You can find its location by running +\samp{kpsewhich texmf.cnf}; it contains many comments explaining the +default settings and useful alternatives. + + +\subsection{Testing the installation} +\label{sec:test-install} + +After installing \TeXLive{} as best you can, you naturally want to test +it out, so you can start creating beautiful documents and/or fonts. + +This section gives some basic procedures for testing that the new system +is functional. We described the Unix commands; under \MacOSX{} and +Windows, you're more likely to run the tests through a graphical +interface, but the principles are the same. + +\begin{enumerate} + +\item Make sure that you can run the \cmdname{tex} program in the first +place: + +\begin{alltt} +> \Ucom{tex -{}-version} +TeX (Web2c 7.5.2) 3.141592 +kpathsea version 3.5.2 +Copyright (C) 1997-2003 D.E. Knuth. +... +\end{alltt} +If this comes back with `command not found' instead of version and +copyright information, most likely you don't have the correct +\dirname{bin} subdirectory in your \envname{PATH}. See +the environment-setting information on p.~\pageref{text:path}. + +\item Process a basic \LaTeX{} file: +\begin{alltt} +> \Ucom{latex sample2e.tex} +>TeX (Web2c 7.5.2) 3.141592 +... +Output written on sample2e.dvi (3 pages, 7256 bytes). +Transcript written on sample2e.log. +\end{alltt} +If this fails to find \filename{sample2e.tex} or other files, perhaps +you have interference from old environment variables or configuration +files. For a deep analysis, you can always ask \TeX{} to report on +exactly what it is searching for, and finding; see ``Debugging actions'' +on page~\pageref{Debugging}. + +\item Preview the result online: +\begin{alltt} +> \Ucom{xdvi sample2e.dvi} +\end{alltt} +Under Windows, the analogous command is \cmdname{windvi}. You should +see a new window with a nice document explaining some of the basics of +\LaTeX{}. (Well worth reading, if you're new to the system.) You do +have to be running under X for \cmdname{xdvi} to work; if you're not, or +your \envname{DISPLAY} environment variable is set incorrectly, you'll +get an error \samp{Can't open display}. + +\item Create a \PS{} file for printing or display: +\begin{alltt} +> \Ucom{dvips sample2e.dvi -o sample2e.ps} +\end{alltt} + +\item Create a \acro{PDF} file instead of \dvi{}; this processes the +\filename{.tex} file and writes \acro{PDF} directly: +\begin{alltt} +> \Ucom{pdflatex sample2e.tex} +\end{alltt} + +\item Preview the \acro{PDF} file: +\begin{alltt} +> \Ucom{gv sample2e.pdf} +\textrm{or:} +> \Ucom{xpdf sample2e.pdf} +\end{alltt} +Unfortunately neither \cmdname{gv} nor \cmdname{xpdf} are currently +included in \TeXLive{}, so you must install them separately. See +\url{http://wwwthep.physik.uni-mainz.de/~plass/gv} and +\url{http://www.foolabs.com/xpdf}, respectively. + +\item Other standard test files you may find useful: + +\begin{ttdescription} +\item [docstrip.tex] Produce \TeX{} source or documentation from a +\samp{.dtx} file. +\item [small2e.tex] A simpler document than \filename{sample2e}, to +reduce the input size if you're having troubles. +\item [testpage.tex] Test if your printer introduces any offsets. +\item [nfssfont.tex] For printing font tables and tests. +\item [testfont.tex] Also for font tables, but using plain \TeX{}. +\item [story.tex] The most canonical (plain) \TeX{} test file of all. +You must type \samp{\bs bye} to the \code{*} prompt after \samp{tex +story.tex}. +\end{ttdescription} +You can process these in the same way as we did with +\filename{sample2e.tex}. + +\end{enumerate} + +If you are new to \TeX{}, or otherwise need help with actually +constructing \TeX{} or \LaTeX{} documents, please visit +\url{http://tug.org/begin.html}. We especially recommend the +\textsl{Formatting Information} manual by Peter Flynn, available at +\url{http://www.ctan.org/tex-archive/documentation/beginlatex}. + + +\section{\MacOSX{} installation} +\label{sec:mac-install} + +\TeXLive{} supports \MacOSX, but no prior Macintosh versions. (If you +are running an older Mac version, you can view the files by installing +the Joliet system extension available from +\url{http://www.tempel.org/joliet}; however, the \TeXLive{} binaries +will not run.) + +Installation of \TeX{} under \MacOSX{} can be done in two ways: + +\begin{enumerate} +\item With the \filename{install*} scripts, as with Unix. +\item With the \cmdname{i-Installer} included in +\filename{MacOSX/II2.dmg}. +\end{enumerate} + +\noindent Each of these is described in a following section. + +In addition, typical use of \TeX{} under \MacOSX\ goes through a +\emph{frontend}. This is also described below. + + +\subsection{\protect\cmdname{i-Installer}: Internet installation} +\label{sec:i-Installer} + +The \cmdname{i-Installer} is included in the \TeXLive{} distribution as +an alternative to normal installation. It does not use the contents of +the \TeXLive{} distribution at all; instead, the system (approximately +70 megabytes) is downloaded over the Internet. + +One advantage of \cmdname{i-Installer} is that it makes updates +relatively painless. If you are interested, please see the +\cmdname{i-Installer} \TeX{} home page at \url{http://www.rna.nl/tex.html}. + +To use it, mount \filename{./MacOSX/II2.dmg}. Read the documentation, +launch it, and install at least \emph{TeX Foundation} and \emph{TeX +Programs}. The first will finish without configuration, as soon as the +second is installed you will be presented with a graphical interface to +setting up your \TeX{} system. + +The \cmdname{i-Installer} distribution uses the \teTeX{} \dirname{texmf} +tree with some additions. Due to differences between \TeXLive{} and +\teTeX{} you cannot update a \TeXLive{} installation with an +\cmdname{i-Installer} \emph{TeX Programs} i-Package. + + +\subsection{\protect\cmdname{install*.sh}: \protect\TeXLive{} installation} + +In order to run the installation scripts under \MacOSX, you need to have +the \cmdname{bash} shell installed. If you are running \MacOSX~10.2 +or later, you have \cmdname{bash}, and can proceed. If you're running +an earlier \MacOSX{} version, however, the default shell is +\cmdname{zsh}, which won't work; please see the +subsection~\ref{sec:mac-bash} (p.~\pageref{sec:mac-bash}) below for +instructions on installing bash \cmdname{bash}. + +Once you have \cmdname{bash}, the Unix installation documentation in the +previous section can be followed. See section~\ref{sec:unix-install} on +p.~\pageref{sec:unix-install}; \MacOSX-specific notes are included where +needed. + + +\subsection{\MacOSX{} frontends} + +Using \TeX{} on a Macintosh typically goes through a front end program, +comprising an execution shell, editor, previewer, and other facilities. +Here are the principal frontends: + +\begin{cmddescription} +\item [TeXShop] Included in \TeXLive{} as +\filename{./MacOSX/texshop.dmg}. See +\url{http://www.uoregon.edu/~koch/texshop/texshop.html}. + +\item [ITeXMac] Included in \TeXLive{} as +\filename{./MacOSX/iTeXMac-*.dmg}. See +\url{http://itexmac.sourceforge.net}. + +\item [Mac-emacs] A port of Emacs to \MacOSX{}, integrating +\pkgname{AucTeX}. See \url{http://www.cs.man.ac.uk/~franconi/mac-emacs}. + +\end{cmddescription} + +The frontends use \dirname{/usr/local/teTeX} as the default location; +therefore, you must either install \TeXLive{} there, or change the +configuration of the frontend. + + +\subsection{\cmdname{bash} installation for older \MacOSX{} versions} +\label{sec:mac-bash} + +\MacOSX{} versions 10.1 and earlier do not include \cmdname{bash} by +default, and the default shell does not run the \TeXLive{} installation +scripts properly. This section explains how to install \cmdname{bash}. + +First, check if bash is already installed. `Launch Terminal' +(\filename{/Applications/utilities/Terminal}) and type \code{rehash; +which bash}. If the answer is a filename (for example, +\code{/bin/bash}), then \cmdname{bash} is already installed, and you're done +here; go back to the main installation instructions. +If the answer is \code{bash: command not found}, proceed here. + +There are two ways to install \cmdname{bash} if you need it\Dash via the +\acro{GUI} or via command line. + +To install via \acro{GUI}, double-click the \filename{MacOSX/bash.dmg} +file in \TeXLive{}. The disk image (volume) will be mounted. Then +start the \cmdname{i-Installer} application on that volume. You will be +asked to authenticate; if you have never seen that before, you might not +have enough privileges to install. Just enter your own user name and +password. Hit install. Bash will be installed on your system. + +To install via command line: +\begin{enumerate} +\item ensure you have admin privileges: log in as the +\code{admin} user, the System Administrator, a user with Admin +privileges, using \cmdname{sudo}, etc. + +\item copy \filename{MacOSX/bash.tar.gz} from the \TeXLive{} +distribution to your home directory. + +\item Launch Terminal, and run: +\begin{alltt} +(cd /usr/local/; sudo tar xvzf ~/bash.tar.gz) +\end{alltt} +You'll be asked for your password, and then \cmdname{bash} will be +installed. + +\item Quit Terminal. + +\end{enumerate} + +After using either installation method, be sure to recheck that +\cmdname{bash} is installed with \code{rehash; which bash} in a new +Terminal window. + + +\section{Windows installation} +\label{sec:win-install} + +\TeXLive{} can be installed on systems running Windows 9x, \acro{ME}, +\acro{NT}, \acro{2K} or \acro{XP}. Older versions of Windows (3.1x) +and \acro{MS-DOS} are not supported. + +It is necessary to have your Windows set up so that it uses the +Microsoft Joliet extensions for reading \CD{}s; simply look at the \CD{} +in Explorer and see whether it shows long, mixed-case, file names. If it +does not, you must install the Joliet extensions. + +The Windows \TeX{} system included in \TeXLive{} is no more and no less +than the \fpTeX{} distribution. It includes a \texttt{dvi} previewer, +\textsf{Windvi}, which is similar in usage to the established Unix +\textsf{xdvi}. The documentation can be found in +\OnCD{texmf/doc/html/windvi/windvi.html}. + +\subsection{The \texttt{TeXLive.exe} program} + +\begin{figure*} + \begin{center} + \ifnum \Status=1 + \includegraphics[width=.7\textwidth]{../pictures/Welcome-to-TeXLive} + \else + \ifnum \Status=2 + \includegraphics[bb=0 0 551 534]{../pictures/Welcome-to-TeXLive.jpg} + \else + \includegraphics[width=.7\textwidth]{../pictures/Welcome-to-TeXLive} + \fi + \fi + \end{center} + \caption{``Welcome to \TeXLive'' window}\label{graph:welcome} +\end{figure*} + +If your computer is configured to let the \CD{} autostart, then a dialog +box with a menu bar will popup on the screen, and you will have several +choices from there: + +\begin{itemize} +\item Install \TeX{} on your hard disk +\item Do maintenance on your \TeX{} system. +\item Remove the \TeX{} system. +\item Use \TeX{} off the \TeXLive{} \CD{} or \DVD{}. +\item Browse documentation: \TeXLive{} documentation, TUG web + pages, \fpTeX web pages. +\item Run the \cmdname{TeXdocTK} application to find specific documentation. +\end{itemize} + +If your \CD{} does not autostart, you can explicitly run the program +by double clicking on \path|bin/win32/TeXLive.exe| on the \CD{} from +the explorer window. + +\subsection{Running \protect\TeXLive{} directly from media (Windows)} + +\runlive + +To run live under Windows, from the menu, chose \verb|Explore CD-Rom|, then +\verb|Run TeX off CD-Rom|. This will launch the \cmdname{XEmacs} editor. + +%% To run live under Windows, do the following: + +%% \begin{enumerate} +%% \item from the menu, chose \verb|Explore CD-Rom|, then +%% \verb|Run TeX off CD-Rom|, that will launch the \cmdname{XEmacs} editor. + +%% This program needs to be a \TeX{} oriented editor. It must be able +%% to run the \TeX{} compiler, previewer and any other needed tool. If +%% you don't have one already installed on your system, you can install +%% one from the \CD{}, details section~{\ref{sec:texlive-install}}. + +%% \emph{There is no way we can guess if the program you will +%% select is actually a text editor, so be careful}. +%% Here is a list of frequently used \TeX{} editors: +%% \begin{center} +%% \begin{tabular}[H]{ll} +%% GNU Emacs & \path|c:\Program Files\NTEmacs\bin\runemacs.exe| \\ +%% XEmacs & \path|c:\Program Files\XEmacs\XEmacs-21.2\i586-pc-win32\xemacs.exe| \\ +%% WinShell & \path|c:\Program Files\WinShell\WinShell.exe| \\ +%% WinEdt & \path|c:\Program Files\WinEdt Team\WinEdt\WinEdt.exe|\\ +%% TeXnicCenter & \path|c:\Program Files\TeXnicCenter\TEXCNTR.exe| +%% \end{tabular} +%% \end{center} +%% The program +%% selected will be memorized as the editor to use for future runs. + +%% \item from the menu, chose \verb|Explore CD-Rom|, then +%% \verb|Run TeX off CD-Rom|. The environment will be modified, a small +%% temporary directory created and some configuration files copied +%% there. Then, the selected editor selected will be launched, and you +%% will be able to type in some text, let \TeX{} typeset it and the +%% view it or print it. + +%% If Ghostscript is not detected on your machine, you will be warned +%% that rendering your DVI files might fail. You can install it from +%% the \path|Install|, \path|Support| menu item. See +%% section~\ref{sec:texlive-install} for details. + +%% \item you can select a different text editor any time you want. + +%% \item if you chose \verb|Cleanup CD-Rom setup|, everything \TeX{} +%% needed will be removed, comprised the selection of your text +%% editor, but not the extra packages you may have downloaded and +%% installed. If you installed \cmdname{WinShell} or \cmdname{NTEmacs}, +%% they won't be removed. +%% \end{enumerate} + +XEmacs startup file will set the environment variables needed. XEmacs will also +setup a temporary \acro{TDS} compliant texmf tree in the temporary area of your +computer. It is needed to store files that may be built on the fly, such as +\path|pk| bitmap fonts, or format files. Configuration files are copied from +the \CD{} to this texmf tree, so that you can edit them if needed. The +\path|ls-R| database is computed for this texmf tree. The AUC-\TeX{} mode will +be entered Whenever you will visit or create a \TeX{} file, providing all the +bells and whistles for \TeX{} support XEmacs is capable of. + +If you run 'M-x shell' within XEmacs, then you will have access to all the TeXLive +tools from the command line provided by XEmacs. + +\smallskip {\small\noindent \textbf{[For advanced users:]} You can also + use the small batch file \path|mkloctex.bat| to be called in a + directory \path|bin\win32| of the \CD. From the Start menu select + `Run', then browse the \acro{CD} drive and select + \path|mkloctex.bat|. Before starting it, you should add two parameters + separated by a space: the letter of your \acro{CD} drive and the + letter of the drive where you want to install the \TeX\ directory. + The whole line should read, e.g., \verb+d:\bin\win32\mkloctex.bat d c+. + When installation is complete, please read carefully the information + on screen. If you are running Windows 9x/\acro{ME}, then you will have to + restart Windows.} + +\subsection{Support packages for Windows} +\label{sec:win-xemtex} + +To be complete, a \TeXLive installation needs support packages that are not +commonly found on a Windows machine. +Many scripts are written using the Perl language. Some important tools require +the Ghostscript \PS{} interpreter to render or to convert files. A graphic +file toolbox is also needed in some cases. Last but not least, a \TeX-oriented +editor makes it easy to type in your \TeX{} files. + +All these tools are quite easy to find for Windows, but in order to try to make +your life even easier, we have put such a set of tools on \TeXLive: +\begin{itemize} +\item \cmdname{Ghostscript} 7.07 +\item a minimal \cmdname{Perl} 5.8, sufficient to run all the \TeXLive{} +Perl scripts +\item a subset of \cmdname{ImageMagick} 5.5.6 +\item the \cmdname{ISpell} checker +\item \cmdname{XEmacs} 21.5.14 with a selection of packages to support +\TeX{} typesetting. +\end{itemize} + +These packages should be installed only all at once. The bundle is +known as the \XEmTeX{} bundle. + +If you didn't install \XEmTeX{}, \cmdname{Perl} and \cmdname{Ghostscript} are +installed anyway if they are not detected on your machine. This is because they are +required by many important tools. The \envname{PERL5LIB} and \verb|GS_LIB| +environment variables will be set too. + +When you are under +\cmdname{XEmacs}, the tools provided shadow any other version you might +have installed previously. The point here is that \path|TeXSetup.exe| +will not install anything outside of the \TeXLive location, neither will +it run foreign installers, nor will it try to autodetect installed +products using unreliable rules of thumb. The \XEmTeX{} bundle is +standalone and is meant to evolve in the future. The reference site is +\url{http://www.fptex.org/xemtex/}. + +If you don't want to install this bundle, then you are on your own to +install the required tools to complete your \TeXLive{} system. Here is a +list of places to get those tools: + +\begin{description} +\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} +\item[Perl] \url{http://www.activestate.com/} (but you might need some + supplementary packages from CPAN: \url{http://www.cpan.org/}) +\item[ImageMagick] \url{http://www.imagemagick.com} +\item[NetPBM] alternatively, you could use NetPBM instead of ImageMagick to + process or convert your graphic files. NetPBM home page is + \url{http://netpbm.sourceforge.net/} +\item[\TeX-oriented editors] There is a wide choice, and it is a matter of the + user's taste. Here is a selection: + \begin{itemize} + \item \cmdname{GNU Emacs} is available natively under Windows, the + reference url is + \url{http://www.gnu.org/software/emacs/windows/ntemacs.html} + \item \cmdname{XEmacs} is available natively under Windows, the + reference url is \url{http://www.xemacs.org/} + \item \cmdname{WinShell} is available on \TeXLive in the \path|support| + directory, the reference url is \url{http://www.winshell.de} + \item \cmdname{WinEdt} is shareware available from \url{http://www.winedt.com} + \item TeXnicCenter is available from + \url{http://www.toolscenter.org/products/texniccenter/} + \item \cmdname{Vim} is available on \TeXLive{} in the + \path|support\vim| directory and the + reference site is \url{http://www.vim.org} + \item \cmdname{SciTE} is available from \url{http://www.scintilla.org/SciTE.html} + \end{itemize} +\end{description} + +You might want to install other tools that are not free\footnote{Not +free, that is, in the sense of freedom to modify and redistribute, +following Debian's guidelines. This does not mean you can't acquire +them for no money.} and therefore not included on \TeXLive{}, such as +\cmdname{GSView}, the \cmdname{Ghostscript} companion to more +conveniently view PS/PDF files. \cmdname{GSView} is available from +\url{http://www.cs.wisc.edu/~ghost/gsview/} or any \acro{CTAN} site. + +%% \subsection{Installing editors or support packages} +%% \label{sec:texlive-install} + +%% You can use the \path|TeXSetup.exe| program to install a +%% single (not \TeX{}-dependent) package. This might be an editor +%% such as \cmdname{WinShell} or \cmdname{NTEmacs}, +%% or a support package like \cmdname{NetPBM} +%% (graphics formats conversion) or \cmdname{Ghostscript}. + +%% Some of the packages are not free, or not with the same meaning as for +%% the rest of the \CD{}. These packages have been made available through +%% the Internet. You need to enable an Internet connection in order to +%% install them. Chosing the \path|Enable Internet access| subitem will +%% search your system for an active Internet connection, or start one if +%% possible. \emph{If your computer is not connected to the Internet, +%% then the timeout might be long, 30s or more}. So try to enable it +%% only if you know you have a connection. + +%% Only a few packages are available from the \CD{}, but the most +%% important of them: \cmdname{NTEmacs} and \cmdname{WinShell} for the +%% editors, \cmdname{Ghostscript} and \cmdname{NetPBM} for the other +%% support packages. \cmdname{NetPBM} is needed for running \TeX{}4ht. + +%% The downloadable packages are sometimes huge: \cmdname{Perl} is 10Mb, +%% \cmdname{XEmacs} is 50Mb, so be warned that it can take a lot of time +%% to install such things. \path|TeXSetup.exe| does not yet provide an +%% estimation of the time needed to complete the download. + +%% When installing these packages, \path|TeXSetup| is working in +%% unattended mode. However, the programs that have their own installer +%% like WinEdt or Ghostscript for example will require human interaction. + +%% Those packages who have no specific installer will be unpacked and configured +%% for your system. You will be required to select some directory where +%% they will be installed. The directory to select should be the root +%% directory of the whole installation. Assuming you want to install +%% NTEmacs and NetPBM, the archive files already contain the +%% \path|NTEmacs\| and \path|NetPBM\| part, so the directory you have to +%% select is something like \path|c:\Local| or \path|c:\Program Files|. + +\subsection{Installing \TeXLive{} to disk} + +\textbf{Warning: Win9x users must ensure they have enough environment + space before undertaking installation. The \cmdname{TeXSetup.exe} + program won't change the environment size for them. A few environment + variables will be created and it is possible you run out of + environment space. Add "SHELL=COMMAND.COM /E:4096 /P" in the + config.sys file in order to increase your environment size.} + +Installation is started by letting the media autostart. The program run +is \path|TeXSetup.exe| if you are using the inst disk. If you are using +the live or the demo disk, you will have to select the item +\path|TeXLive Software| from the menu, then the subitem \path|Install on +Hard Disk|. This will invoke \path|TeXSetup.exe|. You can also find it +in the \path|bin/win32| directory and run it, if the autostart fails for +any reason. \path|TeXSetup.exe| is a Windows wizard and it will display +several pages while running. + +\begin{description} +\item[Welcome Page] + You can choose a \emph{quick} installation from + here. In this case, the installation will run without any human + assistance from beginning to end, with all the default settings + (Figure~\ref{graph:setup-src}, + \ifnum \Status = 1 + on the left% + \else\ifnum \Status=2 + at the top% + \else + on the left% + \fi\fi + ). If you have enough privileges (administrator or power user + rights) under a Windows version where this is applicable, then you can + decide to install the \TeXLive{} for all users or for yourself only by + checking the appropriate box. + For installing the whole \XEmTeX{} bundle (XEmacs, Ghost\-script, + Perl, ImageMagick and Ispell) you can check \emph{Install XEmTeX + Support} box. + \begin{figure*}[!htb] + The \cmdname{TeXSetup} Wizard\hfill + Source directories for the \TeXLive{} files + + \begin{center} + \ifnum \Status=1 + \includegraphics[width=.48\textwidth]{../pictures/setup-wizard.jpg}\hfill% + \includegraphics[width=.48\textwidth]{../pictures/source-for-texlive.jpg} + \else + \ifnum \Status=2 +\includegraphics[bb=0 0 506 403]{../pictures/setup-wizard.jpg} +\includegraphics[bb=0 0 506 403]{../pictures/source-for-texlive.jpg} + \else + \includegraphics[width=.48\textwidth]{../pictures/setup-wizard}% + \hfill% + \includegraphics[width=.48\textwidth]{../pictures/source-for-texlive} + \fi + \fi + \caption{The \TeXLive{} setup wizard}\label{graph:setup-src} + \end{center} +\end{figure*} +\item[Source Page] + This page is a bit complex. It will allow you to select two source + directories for your \TeXLive{} system + (Figure~\ref{graph:setup-src}, + \ifnum \Status = 1 + on the right% + \else\ifnum \Status=2 + at the bottom% + \else + on the right% + \fi\fi + ). You will need a \emph{local + source directory} and possibly a \emph{remote source directory}. + +Why do we need both these directories? The files consisting of the +\TeXLive{} system are on the \CD{}, of course, but some other useful +packages are not, either because of space lacking or because their +license was not compatible with \TeXLive{}. You need to enable Internet +downloading if you want to install these packages that are marked with a +specific ``remote'' icon. + + However, don't panic: the default parameters of the setup will allow + you to install a full system using the \CD{} only. Simply, you won't + have \file{WinEdt} (for example), but you will be able to install it + later. + + So you can take your files from: + \begin{itemize} + \item the \CD{} or any similar flat tree of files, available through + some standard directory (this means the \CD{} can be mounted on + some remote machine and be made available through network + sharing), + \item a set of \file{.zip} files (this is the case when you are + installing from the demo \CD{} or the \fpTeX{} distribution), + \item the Internet; in this case, the program takes care of + downloading the \file{.zip} files it needs for you. + \end{itemize} + This option is available only if you enable Internet file + downloading in the right part of the page. You also need to + configure this Internet access by selecting to connect either using + Internet Explorer~5 \file{wininet.dll}, or using a direct connection (\texttt{ftp}, + \texttt{http}). +% or using a proxy server. +% Last, you can be assisted in defining the \emph{local source +% directory} and \emph{remote source directory} which will be used +% to copy the files onto your hard disk. The \texttt{browse} buttons +% allow to select a directory for the former, and an url among a list +% of mirrors for the latter. +\item[Root Page] + On this page, you will tell where you want the files to be + installed (Figure~\ref{graph:root-schm}, + \ifnum \Status = 1 + on the left% + \else\ifnum \Status=2 + at the top% + \else + on the left% + \fi\fi + ). Only the root directory really matters, the other ones + are set according to the root one. You may want to make + \path|$TEXMFEXTRA| point to some TDS compliant directory with other + \TeX{} files or assign a different value to + \path|$HOMETEXMF|, which is set by default to whatever Windows think + is your `HOME' location. +\begin{figure*}[!htb] + Root and directories\hfill% + Scheme selection + \begin{center} + \ifnum \Status=1 + \includegraphics[width=.46\textwidth]{../pictures/root-of-installation.jpg}\hfill% + \includegraphics[width=.46\textwidth]{../pictures/scheme-selection.jpg} + \else + \ifnum \Status=2 +\includegraphics[bb=0 0 506 403]{../pictures/root-of-installation.jpg} +\includegraphics[bb=0 0 506 403]{../pictures/scheme-selection.jpg} + \else + \includegraphics[width=.46\textwidth]{../pictures/root-of-installation}% + \hfill% + \includegraphics[width=.46\textwidth]{../pictures/scheme-selection} + \fi + \fi + \caption{\TeXLive-Setup: Root and directories / Schemes}\label{graph:root-schm} + \end{center} +\end{figure*} +\item[Get TPM Page] + This page does not require any manual intervention. The \file{.tpm} + files which describe collections and packages are retrieved + (possibly from the Internet), unzipped if needed and parsed. +\item[Schemes Page] + On this page, you will select the global scheme of your + installation (Figure~\ref{graph:root-schm}, + \ifnum \Status = 1 + on the right% + \else\ifnum \Status=2 + at the bottom% + \else + on the right% + \fi\fi + ). A scheme is a large set of files targeted at some kind + of usage. There are 3 generic schemes for basic, recommended and + full installation. The other ones are devoted to LUGs (what GUST or + GUTenberg propose for their members) or applications (XML and + \TeX{}). + When a scheme is selected, it is still possible to refine the + selection by checking the appropriate box. If doing so, you will be + presented the packages page to change your selection, else you will + jump to the review page. +\item[Packages Page] + Collections and packages are presented in a tree form + (Figure~\ref{graph:win32-support}, + \ifnum \Status = 1 + on the left% + \else\ifnum \Status=2 + at the top% + \else + on the left% + \fi\fi + ). The links + in the tree are dependency links. Collections \emph{depend on} + packages and maybe other collections, and it is the same for each + package. You can select any package or collection individually, but + your request will be granted only if the object is not requested by + another one which is selected. For example, you can't deselect + \texttt{tex-basic} without deselecting all the collections that + request it. + + The \texttt{tex-xemtex} collection displayed on the picture is Win32 specific. It + holds a number of bonus packages (Figure~\ref{graph:win32-support}, + \ifnum \Status = 1 + on the right% + \else\ifnum \Status=2 + at the bottom% + \else + on the right% + \fi\fi + ) which can be installed + automatically and individually: Ghostscript (the \PS{} + interpreter), XEmacs editor preconfigured for \TeX{}, tools like Perl, + ImageMagick, Ispell. \emph{None of these packages are selected by + default}. + + On this page, you also have the information about disk space + needed, for each object, and for the set of those who are selected, + and also the disk space available on the partition selected for the + installation. Last, you can choose to install or not the + documentation files and source files associated with each package. +\item[Review Page] + You will find there a summary of your choices + (Figure~\ref{graph:review}, + \ifnum \Status = 1 + on the left% + \else\ifnum \Status=2 + at the top% + \else + on the left% + \fi\fi + ). It is still possible to + go back to change them. +\begin{figure*}[!htb] + Packages Page\hfill% + Win32 Support + \begin{center} + \ifnum \Status=1 + \includegraphics[width=.48\textwidth]{../pictures/package-selection}\hfill% + \includegraphics[width=.48\textwidth]{../pictures/win32-support} + \else + \ifnum \Status=2 +\includegraphics[bb=0 0 506 403]{../pictures/package-selection.jpg}\hfill% +\includegraphics[bb=0 0 506 403]{../pictures/win32-support.jpg} + \else + \includegraphics[width=.48\textwidth]{../pictures/package-selection}% + \hfill% + \includegraphics[width=.48\textwidth]{../pictures/win32-support} + \fi + \fi + \end{center} + \caption{Packages Page / Win32 goodies} + \label{graph:win32-support} +\end{figure*} +\item[Files Copy Page] + The selected files are copied on your hard disk (Figure~\ref{graph:file-copy}, + \ifnum \Status = 1 + on the right% + \else\ifnum \Status=2 + at the bottom% + \else + on the right% + \fi\fi + ). All the files not + yet available on your local disk are first downloaded from the + remote source directory on the Internet. Then every package is + unpacked (if \path|.zip| files), or copied from the \CD{}. +\item[Configuration Page] Several packages need some configuration + step to make them usable (Figure~\ref{graph:configuration}, + \ifnum \Status = 1 + on the left% + \else\ifnum \Status=2 + at the top% + \else + on the left% + \fi\fi + ). Also the \TeXLive{} system needs some post-processing step + (format files generation, ls-R databases generation, environment + variables, etc.). All these operations are done there, some of them + can be lengthy. +\begin{figure*}[!htb] + \textbf{Review Page}\hfill% + \textbf{File Copy Page} + \begin{center} + \ifnum \Status=1 + \includegraphics[width=.48\textwidth]{../pictures/review-settings}\hfill% + \includegraphics[width=.48\textwidth]{../pictures/file-copy} + \else + \ifnum \Status=2 + \includegraphics[bb=0 0 506 403]{../pictures/review-settings.jpg}\hfill% + \includegraphics[bb=0 0 506 403]{../pictures/file-copy.jpg} + \else + \includegraphics[width=.48\textwidth]{../pictures/review-settings}\hfill% + \includegraphics[width=.48\textwidth]{../pictures/file-copy}% + \fi + \fi + \end{center} + \caption{Review Page / File Copy Page} + \label{graph:review}\label{graph:file-copy} +\end{figure*} +\item[Final Page] The installation being over, you may want to display + the Windows specific documentation (HTML format) and / or the log + file of the setup process (Figure~\ref{graph:final} + \ifnum \Status = 1 + on the right% + \else\ifnum \Status=2 + at the bottom% + \else + on the right% + \fi\fi + ). If it is needed (Win9x/WinME), you will + be asked to reboot your computer. +\end{description} + +\begin{figure*}[!htb] + \textbf{Configuration Page}\hfill% + \textbf{Final Page} + \begin{center} + \ifnum \Status=1 + \includegraphics[width=.48\textwidth]{../pictures/configuration}\hfill% + \includegraphics[width=.48\textwidth]{../pictures/congratulations} + \else + \ifnum \Status=2 + \includegraphics[bb=0 0 506 403]{../pictures/configuration.jpg}\hfill% + \includegraphics[bb=0 0 506 403]{../pictures/congratulations.jpg} + \else + \includegraphics[width=.48\textwidth]{../pictures/configuration}\hfill% + \includegraphics[width=.48\textwidth]{../pictures/congratulations}% + \fi + \fi + \end{center} + \caption{Configuration Page / Final page} +\label{graph:configuration}\label{graph:final} +\end{figure*} + +Please be aware that the choice of cluster size on DOS disk +partitions can radically affect the size of your \TeX\ +installation. The support tree has hundreds of small files, and it is +not unusual for a complete installation to take up to four times the +amount of space used on the \CD. + + +\section{Windows maintenance and post-installation} + +\subsection{What's different in Windows?} + +The Windows version of \Webc{} has some specific features that should be +pointed out. + +\begin{description} +\item[\KPS{}] The hash-tables that \KPS{} builds are quite large for + the \TeXLive{}. In order to cut down the starting time of any + \KPS{}-enabled program, these hash-tables have been put in shared + memory. This way, when you chain the execution of several such + programs, like \path|tex| calling \path|mpost| calling \path|tex|, + the overhead when starting each of the subprograms is + reduced. This change is hidden to the user, except if you set the + debug flag of kpathsea to the \path|-1| value: you will then trace + access to the shared memory, which is not what you want (it is + accessed very often!). What is useful in a log trace of the shared + memory access is still to be defined, so the situation might evolve + in the future. +\item[\cmdname{kpsecheck}] This command provides some options that did + not fit well into \cmdname{kpsewhich}. It will allow you to list all + the files that occur multiple times across your texmf trees. This + could be handy, but most of the time you will also get unwanted + output (like dozens of \path|README| files)\footnote{It is noticeable + that all these files result in clashes inside the \KPS{}-hashing + mechanism; fortunately, \KPS{} never looks for these files.}. For + this reason, you can combine the \path|-multiple-occurences| with 2 + other options for including or excluding any filename that match + some pattern (you can request for several patterns). + + The \cmdname{kpsecheck} command will also report the status of shared + memory: in use or not used. That might be useful to know because if + the status reported is \samp{in use}, that means one or several + processes are working, and the effect of any \cmdname{mktexlsr} + command will be delayed until the next time where no \KPS{} linked + process will be running. + + Last, this same command will report about the location it thinks + Ghostscript can be found. Under Win32, for many programs, it is + easier to use the Ghostscript dll, and find it by using the + Ghostscript registry key than to change the \path|PATH|, which has a + limited length anyway. +\item[\Webc{}] The engines have a few more options than in Unix + \Webc{}, and one option with a different behaviour: + \begin{itemize} +%% \item the \path|-fmt| option behaves differently. Previously and +%% with the regular \Webc{} distribution, this option has 2 different +%% meanings when you are in ``ini'' or ``vir'' mode. Under Win32, it +%% has the same meaning: preload the format file specified with the +%% argument. The meaning of building a format of such name in ini +%% mode is obtained by the new \path|-job-name| option. +%% \item \path|-job-name| option: allows to set the name of the file +%% resulting from the compilation process. In normal mode, it will +%% change the base name of all files produced (\path|.dvi|, +%% \path|.aux|, etc.), while in ini mode, it will set the name of +%% the format file written. + \item \path|-halt-on-error| stop the compilation at the first error. + \item \path|-job-time| set the job time to the same timestamp as the + file given in argument. +\item \path|-oem| use the DOS codepage for console output. + \item \path|-output-directory| allow to write all the output files in the + specified directory. + \item \path|-time-statistics| print statistics about the job run + time. It is to be noted that Win9x not being a true multitasking + operating system, it has no reliable timer for short periods, so + the value printed is an approximation. Under NT/2K/XP, the result + is quite accurate with user time and system time values allocated + for this run. For Unix + users: the \path|time| command is not usually available to Windows + users. + \end{itemize} +\end{description} + +\subsection{Adding packages to your installation} + +You will find an option in the \guiseq{TeXLive} menu (or go to +\guiseq{Start\arw Programs \arw TeXLive \arw Add TeX package} menu) to +run \file{TeXSetup.exe} in maintenance mode. The steps are almost the +same as in the initial installation. + +We'll discuss differences below, but first, whatever changes you make, +\textbf{do not forget to rebuild the ls-R database files}. Otherwise, +your new files will not be found. You can do this either via the +\acro{GUI} (\guiseq{Start \arw Programs \arw TeXLive \arw Maintenance +\arw Rebuild ls-R}), or manually running the \file{mktexlsr} command. + +The main difference is in the packages selection page. In maintenance +mode, the list of installed packages is compared to the list of packages +available from your source directories. Packages that are not installed +will be displayed in green, out of date packages will be displayed in +red and up-to-date, installed packages are displayed in black. + +This way, you can choose to add or upgrade components, either from +\TeXLive{} or from the Internet, where you are likely to find some more +recent version of your packages. + +It is up to you to select which packages you want to install. The rest +of the process is similar to the first installation. + +If you want to add files that are not provided by the \TeXLive{} (or +\fpTeX{}) distribution, it is recommended to put them in the +\path|$TEXMFLOCAL| directory. This way, you will be safe against +upgrades of the \TeXLive{} software. + +The directory pointed to by \path|$TEXMFLOCAL| is initially empty. If, +for example, you want to add the support file for the Maple symbolic +computation program, you will have to put the style files in:\\ +\path|c:\Program Files\TeXLive\texmf-local\tex\latex\maple\|\\ and the +documentation files in:\\ \path|c:\Program +Files\TeXLive\texmf-local\doc\latex\maple\| + +\subsection{Uninstalling \protect\TeXLive{}} + +The uninstall procedure is available either from the \file{TeXLive.exe} +program, from the \path|TeXLive| menu or from the control panel +(\guiseq{Start \arw Control Panel, Add/Remove Programs}). This procedure +will cleanup your hard disk of most of the \TeXLive{} files. However, +\TeX{} is a system that is creating files and there is no mechanism to +keep track of all of them. Moreover, Win32 support packages have their +own uninstall procedure, which you will have to run separately (provided +you want to get rid of them). Last, the files you may have stored in +\path|$TEXMFLOCAL| won't be removed. So, even if the vast majority of +files are automatically removed by the uninstall procedure, you will +have to do some manual cleanup to actually remove all of them. + +\subsection{Running \texttt{TeXSetup.exe} from the command line} + +The \path|TeXSetup.exe| program has a number of other useful +options. You can get the list by running: +\begin{verbatim} +c:\>TeXSetup --help +\end{verbatim} + +Here is the description: +\begin{description} +\item[\path|--automatic-reboot|] reboot without waiting user + confirmation once installation is over; +\item[\path|--dry-run|] do nothing, just log everything that will be + done without this option; +\item[\path|--quick|] use the recommended installation and default + directories, ask nothing up to rebooting; +\item[\path|--with-xemtex|] selects the \XEmTeX{} bundle; +\item[\path|--net-method (=ie5/direct)|] enable to download components with + restricted licenses from the Internet (either using direct + connection of Internet Explorer 5 DLLs): you need to have an available + network connection and some of the packages are huge; +\item[\path|--remote-source-directory |] this is the base url for the remote packages; +\item[\path|--local-source-directory

|] by default, \path|TeXSetup.exe| + will guess the root directory of the set of files you want it to act on, if you ever + upgrade \path|TeXSetup.exe|, you won't be able to copy the new version + onto your \CD{}, so you will need to use this option to specify the + root of the \CD{}; +\item[\path|--installation-directory |] this is the root of your + installation, all files will be copied under this location. The + default value is \verb+c:\Program Files\TeXLive+; +\item[\path|--texmfmain-directory |] +\item[\path|--texmflocal-directory |] +\item[\path|--texmfextra-directory |] +\item[\path|--texmfhome-directory |] +\item[\path|--vartexmf-directory |] +\item[\path|--vartexfonts-directory |] these are the directories + used to configure the location of your files. They map directly to + the \path|texmf.cnf| variables. +\item[\path|--with-source-files(=yes/no)|] copy the source files + for \TeX{} packages, default value is no; +\item[\path|--with-documentation-files(=yes/no)|] copy documentation files for \TeX{} + packages. Default value is yes. Beware: this is only documentation about specific + packages, general documentation will be installed anyway; +\item[\path|--program-folder |] the name of the folder under + which you will find the menus; +\item[\path|--add-package |] this is used to add or update a specific + package after a first regular installation; +\item[\path|--scheme |] install the named scheme instead of the + default \path|texlive-recommended| scheme; +\item[\path|--maintenance|] mostly the same as \path|--add-package| + without specifying a package to add; +\item[\path|--uninstall|] this option will remove anything \TeX{} related coming from + the \CD{}, which means there can be files left if you added style + files or format files, and also that supplementary tools will not be + removed. This option is still a bit crude in this release; +\item[\path|--help|] this option opens up a box with the list of options. +\end{description} + +\subsection{Network installation} + +\KPS{} knows about UNC names, so you can use them to get your TEXMF +tree from the network. But there is better than this. +All the support files and configuration files, everything except the files in the +\path|bin/win32| are shareable with a \teTeX{} or Unix \TeXLive{} installation. That means +you can use Samba either to mount from an NT server to a Unix +workstation or the converse. Several strategies are possible: +\begin{itemize} +\item Put everything on the server. Just add each set of files for the os and +architecture you want to use in the \path|bin| directory. That means +for example \path|bin/win32| and \path|bin/i386-linux|. Next configure +your main variables. You can use UNC names to +point to the right directories under Win32. +\item Install a local copy for the binaries and format files. In this + case, assign \path|$TEXMFMAIN| to the main \path|texmf| tree that + will be accessed remotely. Set \path|$VARTEXMF| to be a local + directory which will hold local configuration files and on-the-fly + generated files. +\end{itemize} + +\subsection{Personal configurations} + +\subsubsection{Dvips} + +The configuration file for dvips can be found in\\ +\verb+C:\Program Files\TeXLive\texmf-var\dvips\config\config.ps+\\ +You may open it with any editor + %(\cmdname{WinShell} will do fine) + and change some parameters: + +\begin{description} +\item [fonts] you can change the default printer \MF{} mode or printer + resolution in case \cmdname{dvips} needs to generate PK fonts. By default it + is configured to use Type~1 versions of the CM fonts, so it should + not call \cmdname{mktexpk} too often; +\item[printer] you can tell dvips where you want to print by default. If + the \optname{o} option is not followed by a printer name, then a + \file{.ps} \PS{} file is written. You can give dvips a printer + name such as: +\begin{verbatim} +o lpt1: +% o | lpr -S server -P myprinter +% o \\server\myprinter +\end{verbatim} +\item[paper] Next, you might want + to change the paper size from European (A4) to US letter + by making the US letter the first paper size mentioned in the file. + Scroll to the group of lines beginning with \code{@}. Move + the appropriate lines so that this section begins with the lines:\\ +\hspace*{1em} @ letterSize 8.5in 11in\\ +\hspace*{1em} @ letter 8.5in 11in\\ +\hspace*{1em} @+ \%\%BeginPaperSize: Letter\\ +\hspace*{1em} @+ letter\\ +\hspace*{1em} @+ \%\%EndPaperSize +\end{description} + +The current \TeXLive{} distribution implements the procedure of making +always up-to-date fontmaps files for Dvips and Pdftex. This is done by +the \cmdname{updmap} program during installation, as well as during any +font package addition. If you add new packages by hand, edit the file +\verb+updmap.cfg+ in \path|$VARTEXMF/web2c|. + +\subsubsection{Pdftex} + +If you use the program pdf{}latex to write \acro{PDF} format directly, +and you are using \acro{US} letter-size paper, edit the file +\verb+C:\Program Files\TeXLive\texmf-var\pdftex\config\pdftex.cfg+ and +change \samp{page\_width} and \samp{page\_height}. These entries should read: +\begin{alltt} +page_width 8.5 true in +page_height 11 true in +\end{alltt} +Save the file and exit the editor. + +\subsubsection{GSView} +GSView is now distributed under the Aladdin License, and therefore is no longer included in +\TeXLive{}. + +If you may want to change the page size to US letter size. If so, open +GSView from the \guiseq{Start} menu, and select \guiseq{Media\arw Letter}. + +Also, there are menu settings that are supposed to give you the most +readable screen image. On \guiseq{Media \arw Display Settings}, set both +\optname{Text Alpha} and \optname{Graphics Alpha} to 4~bits. + +Note that the installation process has set all \code{.ps} and +\code{.eps} files to automatically open with \cmdname{GSView}. + +For printing instructions, see section~\ref{printing} below. + +\subsubsection{WinDvi} +\label{sub:windvi} + +The \file{TeXSetup.exe} program takes care of associating the files +with the \file{.dvi} extension with \file{Windvi}. + +Open it with \guiseq{Start\arw Programs\arw TeXLive\arw DVI Viewer}. + +You can set it for US letter-size paper by going to \guiseq{View\arw +Options\arw Papertype} and selecting US (8.5\verb+"+ x 11\verb+"+) (and +then \optname{OK}. Exit \cmdname{windvi}. + +You can change other parameters from there as well, such as the ability +to execute system commands specified by the document (disabled by +default for security reasons). Also, the first time you view any .dvi +file, you may find the magnification too large. Zoom out until you get +an appropriate size. + +%There are two important parameters related to printing that can't yet +%be set from the dialog boxes, namely the resolution and the \MF{} mode +%for the printer. You can set them once for all by specifying them on +%the command line: +%\begin{verbatim} +%c:\>windvi -p 360 -mfmode canonbjc foo.dvi +%\end{verbatim} +%When you will exit Windvi, these parameters will be stored in the +%configuration file. The available modes are found in this file:\\ +%\path|c:\Program Files\TeXLive\texmf\metafont\misc\modes.mf| + +All configuration settings for \cmdname{Windvi} are stored in a file +named \path|windvi.cnf| file. You can find it by running this command at +the prompt: +\begin{verbatim} +c:\>kpsewhich --expand-var $HOME/windvi.cnf +\end{verbatim} + +Should you have problems with \cmdname{Windvi}, please remove the configuration +file and test your problem against a vanilla configuration. + +\subsection{Testing} + +For generic verification procedures, see section~\ref{sec:test-install} +on p.~\pageref{sec:test-install}. This section describes +Windows-specific tests. + +Open the file \verb+sample2e.tex+ in your editor (Xemacs, WinShell), +found in \path|C:\Local\TeX\texmf\tex\latex\base|. The \LaTeX\ source +should appear on the screen. Process it by clicking on the +\guiseq{Command\arw LaTeX} menu (XEmacs) or \LaTeX\ icon on the toolbar +(WinShell), then view it by clicking on the \guiseq{Command\arw View DVI} +menu (XEmacs) or Preview (Windvi) icon (WinShell). + +At first, when you preview files with Windvi, it will create fonts because +screen fonts were not installed. After a while, you will have created most +of the fonts you use, and you will rarely see the font-creation window. + +\textbf{Hint for the future:} If a \LaTeX\ run stops because \LaTeX\ +cannot find a file, you can press Ctrl-z to quit. + + +\subsection{Printing} +\label{printing} + +It is possible to print from Windvi. In this case, printing will be done +using the Windows unified printer driver. By definition, it is +compatible with all printers. However, there is some drawback: it can +generate some huge spool files, and some (older) versions of Windows +just don't like them. The advantage is that you can use features like +embedding BMP or WMF images. You also need to make sure that the printer +parameters are correctly set (subsection~\ref{sub:windvi}), else you +will get scaled printing (printing at 600\dpi{} on a 300\dpi{} printer +will give you only one quadrant of your page). + + +Printing is faster and more reliable if you run \cmdname{dvips} to make +a \filename{.ps} file and then print from \cmdname{GSView}. In +\cmdname{GSview}, select \guiseq{File\arw Print\ldots}. A \guiseq{Print} +window will appear. + +If you are using a \PS{} printer, \textit{be sure to select +\guiseq{\PS{} Printer}}. This is done in the \guiseq{Print Method} box +at the bottom left of the \guiseq{Print} window. You can then select any +of the printers that you have previously installed. If you fail to +check the box for \optname{\PS{} Printer}, printing will not work. + +If you will be using your own non-\PS{} printer, select +\guiseq{Ghostscript device} in the \guiseq{Print Method} box, then click +on the button to the right labelled \guiseq{djet500} and select your +printer type from the list that pops up. (In the older version of +\cmdname{GSView}, make sure \optname{\PS{} Printer} is \textit{not} +selected, then select your printer type from the \guiseq{Device} list.) + +%If you use \cmdname{WinShell} and a \PS{} printer, probably the +%most convenient way to print is to add an icon to the \cmdname{WinShell} +%toolbar that invokes dvips in a way that sends the output directly to a +%default printer. For detailed instructions on how to do this, see +%the next section. + +%% \subsection{\cmdname{WinShell}} +%% \label{winshell:more} + +%% \subsubsection{Configuring \cmdname{WinShell}} +%% \label{sec:winshell} + +%% Start this program from the Start menu or from the Desktop shortcut. +%% Go to \guiseq{Options \arw Program Calls}. + +%% \begin{itemize}\itemsep 0pt +%% \item In the DVIWin tab, if the filename is \filename{yap}, replace it +%% with \filename{windvi.exe}. +%% \item In the Ghostview tab, make sure it gives the correct path for +%% gsview32.exe:\\ +%% \hspace*{1em} \verb+C:\ghostgum\gsview\gsview32.exe+ (for 3.6, the +%% current version)\\ +%% or \\ +%% \hspace*{1em} \verb+C:\gstools\gsview\gsview32.exe+ (for the older +%% version) + +%% \end{itemize} + +%% Click \guiseq{OK}. + +%% Note that the install process sets all files with the \texttt{.tex} +%% extension to open with \cmdname{WinShell}. Unless you plan to use another editor +%% (such as WinEdt or Emacs), this is appropriate. + +%% Unfortunately, \cmdname{WinShell} does not have a spell-checking +%% feature. However, if you have installed the \path|tex-extrabin| +%% collection, your installation includes \cmdname{Ispell} (a spell +%% checking program found on most Unix systems). The executable is in your +%% PATH so \verb+ispell.exe+ will be found if you invoke it from a DOS +%% window. If you installed documentation, look at \path|C:\Program +%% Files\TeXLive\texmf\doc\html\manpages\ispell.html|for information on +%% Ispell. (Otherwise, you can find \verb+ispell.html+ on the CD.) If you +%% rely on spell checking, you may want to add an Ispell icon to +%% \cmdname{WinShell}. See subsection~\ref{winshell:ispell} of this +%% document for how to do that. + +%% For an excellent commercial (but inexpensive) spelling checker, +%% see \url{http://www.microspell.com}. + +%% \cmdname{WinShell} also has on-line help, which you can access via the +%% $\textbf{\underbar{?}}$ on the menu bar. + +%% Other information about using \cmdname{WinShell} can be found in +%% section \ref{winshell:more} on p.~\pageref{winshell:more}. + + +%% \subsubsection{Installing Bug Fixes} + +%% \cmdname{WinShell}'s author (\href{mailto:idb@winshell.de}{Ingo de Boer}, +%% thanks to him) sometimes releases beta versions of the next \cmdname{WinShell} +%% version which are also bug fixes. You can grab them from +%% \url{http://www.winshell.de}. Usually they are \file{.zip} files that +%% only require to be unpacked in \cmdname{WinShell} directory (\path|c:\Program +%% Files\WinShell| by default), either using WinZip or a similar tool, or +%% by using \file{unzip} on the command line. If you got some +%% \file{winshellbugfix.zip} file and that you saved it in the \cmdname{WinShell} +%% directory, then you need to run: +%% \begin{verbatim} +%% c:\>cd c:\"Program Files"\WinShell +%% c:\>c:\local\bin\unzip winshellbugfix.zip +%% \end{verbatim} +%% Say \optname{yes} if you are asked if some files should be overwritten. The +%% \path|unzip.exe| programme can be found in the +%% \path|support/gnu-utils| package. If you +%% do not have it on your machine, you can use any archiver tool like +%% WinZip to achieve the same effect. + +%% \subsubsection{The \cmdname{Project} feature: organizing many files} + +%% If your document is split into several files (for example a thesis), +%% look into \cmdname{WinShell}'s \cmdname{Project} feature. From the +%% \guiseq{Project} menu, you give the project a name (e.g., \code{Thesis}), +%% supply the name of the main (or root) file, and then \code{add} other +%% files. These filenames display on the left of the screen where you can +%% double click the names to view and switch between them. Clicking the +%% \guiseq{\LaTeX} icon always processes the main file. + +%% Note the icons on the toolbar for toggling the project space (on the left) +%% and the log space (at the bottom). If you are not using the Project +%% feature, you may want to toggle off the space on the left, using the full +%% screen width to display your file. + +%% \subsubsection{Printing from \cmdname{WinShell} to a \PS{} Printer} +%% \label{winshell:print} + +%% The Dvips icon on the \cmdname{WinShell} toolbar puts the \PS{} output +%% in a file, which you can then view with GSView and print from there if +%% you choose. However, it's convenient to add a \cmdname{WinShell} +%% ``program call'' to dvips which sends the output directly to a +%% designated \PS{} printer. The steps below show how to do this for the +%% printer \optname{vclw}; you should substitute the name of your most +%% frequently-used printer. +%% \begin{enumerate} +%% \item Make the program aware of the printer: +%% \begin{itemize} + +%% \item Open \cmdname{WinShell}, go to \guiseq{Options\arw Program +%% Calls\arw User defined}. + +%% \item Click on \guiseq{Tool 1} in the list on the right and fill in the +%% fields to the left as follows:\vspace{-6pt} +%% \begin{quote} +%% Name: \verb+Print+\\ +%% exe file: \verb+dvips+\\ +%% cmd-line: \verb+ -D600 %m -o vclw+\\ +%% Uncheck the box for \guiseq{DVIPS first} +%% \end{quote}%\vspace{-12pt} +%% \item Click \guiseq{OK} +%% \end{itemize} +%% \item Add \guiseq{Print} to the toolbar: +%% \begin{itemize} +%% \item Go to \guiseq{Options\arw View\arw Customize}. +%% \item In the \guiseq{Category} box, select \guiseq{User-Programs}. +%% \item Select \guiseq{Print} and drag it to the toolbar, placing it just to +%% the right of the \cmdname{GSView} icon. +%% \item You then have a choice of \guiseq{Image only}, \guiseq{Text only}, +%% or \guiseq{Image and Text}. The easiest is to select \guiseq{Text only} +%% and click \guiseq{OK}. You should then see \guiseq{Print} on the +%% toolbar. (If you prefer, you can select \guiseq{Image only\arw Edit}, +%% and edit the displayed picture to your satisfaction.) +%% \end{itemize} +%% \end{enumerate} +%% Now, to print a \LaTeX\ document, just click on the \guiseq{Print} icon +%% to send to your selected printer. To use a different printer, you will +%% need to click on the \guiseq{Dvips} icon to print to a file. Then click +%% on the \cmdname{GSView} icon and use \cmdname{GSView} to send to any +%% printer you have installed on your \acro{PC}. + +%% \subsubsection{Adding Ispell to \cmdname{WinShell}} +%% \label{winshell:ispell} +%% \begin{enumerate} +%% \item Add Ispell to User Tools: +%% \begin{itemize} +%% \item Open \cmdname{WinShell}, go to \guiseq{Options\arw Program +%% Calls\arw User defined}. +%% \item In the list on the right, click on \guiseq{Tool~1} (or +%% \guiseq{Tool~2} if you have already used \guiseq{Tool~1}) and fill in +%% the fields to the left as follows:\vspace{-6pt} +%% \begin{quote} +%% Name: \verb+Ispell+\\ +%% exe file: \verb+ispell+\\ +%% cmd-line: \verb+ -t -d american %c.tex+\\ +%% Uncheck the boxes for \guiseq{LaTeX first} and \guiseq{DVIPS first} +%% \end{quote} +%% \item Click \guiseq{OK}. +%% \end{itemize} + +%% \item Add Ispell to the toolbar: +%% \begin{itemize}\itemsep 0pt +%% \item Go to \guiseq{Options\arw View\arw Customize}. +%% \item In the \guiseq{Category} box, select \guiseq{User-Programs}. +%% \item Select \guiseq{Ispell} and drag it to the toolbar, placing it just to +%% the right of the \cmdname{GSView} icon (or the last icon you added). +%% \item You then have a choice of `\guiseq{mage only}, \guiseq{Text only}, +%% or \guiseq{Image and Text}. The easiest is to select \guiseq{Text only} +%% and click \guiseq{OK}. You should then see \guiseq{Ispell} on the +%% toolbar. (If you prefer, you can select \guiseq{Image only\arw Edit}, +%% and edit the displayed picture to your satisfaction.) +%% \end{itemize} +%% \end{enumerate} +%% Now, when you have a \LaTeX\ document open, you can click on +%% \guiseq{Ispell} to perform spell checking. Ispell will open another +%% window and display the first misspelled word on the left with the +%% filename on the right. Below that you will see the context in which the +%% misspelling appears; often several suggestions for replacements are also +%% displayed. To replace the word, enter the number corresponding to the +%% desired replacement. Other possible responses are listed below; for +%% example, you can press the space bar to ignore the misspelled word. For +%% more information on Ispell, read the manual page: +%% \verb+C:\Program Files\TeXLive\texmf\doc\html\manpages\ispell.html+. + +%% Note that when you replace a word, you will not see the correction in +%% your \cmdname{WinShell} window until you close the file (click the +%% \guiseq{X} in the upper right corner) and then open it again (use the +%% \guiseq{File} menu). + +\subsection{Tips and tricks for Win32} + +\subsubsection{Different flavors of Win32} + +What we call Win32 is not an operating system by itself. It is a large +set of functions (around 12,000 in the header files of the Microsoft +\acro{SDK}) that you can use to write programs for different operating +systems of the Windows family. + +Windows comes in different flavors: +\begin{itemize} +\item Win95, Win98 and Win\acro{ME}, which \emph{are not true multitasking, + multithreading} environments. They are the latest\Dash and hopefully + last\Dash metamorphosis of \acro{DOS}. This can be more or less proven + by the fact that when booting, the PC will load the \path|command.com| + interpreter, and if you stop the boot process at this point, you can + ask for the current (\acro{DOS}) version and it will answer something + like \samp{MS-DOS 7.0} (at least for the old versions of Win9x). +\item Windows \acro{NT}, which is a new operating system written from + scratch, capable of true multitasking behaviour, and including many + high level features. +\item Windows 2000, based on \acro{NT}, with all the bells and + whistles of Win98. +\item Windows \acro{XP}, which comes with Personal and Pro flavors. This is + the last step in merging both lines of products (Win9x based and + \acro{NT} based). \acro{XP} is based on \acro{NT}. +\end{itemize} + +Win9x are able to run 32~bits programs and 16~bits programs +concurrently. But the operating system by itself is not entirely +written in 32~bits mode, and does not support memory protection: 16bits +applications can overwrite parts of the operating system memory! Some +parts of the system like the \acro{GDI} (Graphical Device Interface) +manage limited resources like bitmaps, fonts, pens and so on for the set +of all programs that run concurrently. All the bitmaps headers available +at the same time can't amount for more than 64kB. This explains the +performance tool and the fact that you can put your system on his knees +by making intensive use of graphic objects for example. + +NT, 2K and XP do not suffer from these limitations, and neither from +other Win9x limitations. They are true multitasking environments, with +protected memory. They are much more responsive than Win9x because +of better memory management, better file system and so on. + +\subsubsection{Command line prompt} + +You may wonder, ``Why would I need to use a command line prompt when +I have Windows?'' + +Good question. The problem is of very general nature. Not all operations +can be done easily using only a \acro{GUI}. Command line gives you +programming power\Dash assuming a clever command interpreter. + +But the problem here is more fundamental: \TeX{} is \emph{a batch} +tool. Not an interactive one. \TeX{} needs to compute the best +layout for each page, resolve cross-references and so on. This can be +done only by a global processing of the document. It is not (yet) a +task that can be done interactively. + +This means that you should use \TeX{} from a command line. In fact the +situation is not so bad. There is an advantage to write command line +tools for complex processing: they are better debugged, because they are +independent of any \acro{GUI} problems, and \acro{GUI} tools can be +designed to interface to the command line tools. This is the case for +\TeX{}, where you will mostly interact with it through a \acro{GUI} text +editor. + +However, you may need to use the command line prompt in a number of +situations. One is when you are having difficulties and want to debug +your setup. + +\begin{description} + \item[Win9x] You can open a command line prompt by looking either for + the \acro{MS-DOS} icon in the \guiseq{Start\arw Programs} menu, + or by choosing \guiseq{Start\arw Run} menu typing in + \path|command.com| as the progrm name. + \item[NT, 2K, XP] You can open a command line prompt by looking for + \guiseq{Command Prompt} in the \guiseq{Start\arw Accessories} menu. + You can also choose \guiseq{Start\arw Run} and type in + \path|cmd.exe|, which is the name of the brand new command + interpreter for \acro{NT} (thus, it is untrue to call this a + \emph{DOS} box!). +\end{description} + +These locations may change across different Windows versions. + + +\subsubsection{Path separators} + +The Win32 API understands both \path|/| and \path|\| characters as PATH +separators. But the command interpreters do not! So whenever a path name +is used programmatically, you can use both separators, and even mix them +up in the same path name. But on the command line, you must type +\path|\| as path separator. The reason is compatibility: the command +processor used \samp{/} to introduce arguments to commands. + +All this to say: do not be surprised to read path names written using +the Unix convention; \fpTeX{} is a port of \Webc, and aims to be compatible +across platforms. For this reason, all the configuration files that +need to specify path names use the Unix convention. + +\subsubsection{File systems} +\label{sec:clusters} + +The worst feature of Win9x with regard to \TeX{} is probably the +so-called FAT file system. \TeX{} uses many many small files, with size +around 1--3kB. The \acro{FAT} file system is old, and predates by +decades the multi-gigabytes hard disks we have today. As a result, it +cannot manage efficiently the tens of thousands of \TeX{} files found in +\TeXLive{}. The \acro{FAT} file system allocates a minimum of 32kB for +\emph{any} file on a huge partition. It means that \TeX{} will use much +more disk space than it actually needs. + +The other, more modern, file systems available, \acro{FAT32} and +\acro{NTFS}, do not have this drawback. They manage clusters of 4kB +only. (You can lower the limit to 512 bytes on \acro{NTFS}.) + +\subsubsection{How to add some directory to your PATH} + +There are pairs of variables and values which behave much like global +variables inside your programs. The set of those variables is called the +environment. Each program is initialized with a copy of the +environment when it is run. It can request and change the +value of any variable. The changes happen in the copy of the +environment, and is not at all propagated to the other running +programs. + +Your PATH is a special environment variable used to search for +programs you want to run. +There is a different procedure to change it for Win9x, WinME and NT/2K/XP: + +\begin{description} +\item[Windows 95/98] Edit your \path|autoexec.bat|. In this file should be a line + starting with \texttt{PATH=} and followed by a list of directories separated + by \path|;|. Please add the directory with the executables in this line. + After this, this line could look as follows: +\begin{verbatim} +PATH=c:\windows;c:\windows\system;c:\"Program Files"\TeXLive\bin\win32 +\end{verbatim} +\item[Windows ME] You need to run the special program + \path|c:\windows\system\msconfig.exe| to be able to change any + environment variable. From this program, select the `Environment' + tab, and then add or modify the variable you want. You will be asked to reboot the + machine upon any change. +\item[Windows NT/2K/XP] + Click left on \guiseq{Start \arw Settings \arw Control Panel}. Now the + window with the control panel icons opens. Double click on System. The + System Properties window opens. Click on the tab \textsf{Environment} + or look for a button named \guiseq{Environment Variables} among the + dialog boxes. Now you can change the environment variables for your + user account. Note: There are also displayed the environment settings + for the system. Normally, you can't change the system variables + unless you have administrator rights on your machine. If you want to + change the \texttt{PATH} for all users, you will have to contact your + system administrator or be the system administrator yourself\Dash in + the latter case you should know what you are doing. + + If there is already a \texttt{PATH} setting for your user account, + left click on \texttt{PATH}. In the field \textsf{Variable} appears + \texttt{PATH} while the field Value shows the current setting of + \texttt{PATH} as a list of directories separated by \path|;|. Add + the directory where the executables are located (e.g. + \path|c:\Program Files\TeXLive\bin\win32|). If there isn't a \texttt{PATH} variable + for your user account, simply click in the field Variable and type + in \texttt{PATH}, click in the field \textsf{Value} + and type in the directory with the executables. Important: Click on + the \textsf{Apply} button before clicking \textsf{Ok}, otherwise the + changes to \texttt{PATH} won't apply to your system. Be careful when + changing the environment settings. +\end{description} + +The best way to be sure that a variable has been properly set is to +open a console and type: +\begin{verbatim} +set VARIABLE +\end{verbatim} +which should return the corresponding value. + +\subsubsection{\TeX{} engines} + +If you have a look at the \Webc{} documentation, you will read that all +the various \TeX{} derived programs use the same base engine. For +example, \path|tex.exe| and \path|latex.exe| are exact copies of the +same program, but each one will use a different format file, based on +its calling name. + +Under Unix, this feature is implemented through \emph{symbolic +links}. It saves up a bit of disk space, because some engines are +used with many different format files. + +The Win32 API does not know about file links. So to save up almost +the same amount of memory, all the \TeX{} base engines have been put +in DLLs (\emph{Dynamic Linked Library}). This means that you will have +the following layout: +\begin{alltt} +13/05/2002 17:06 3 584 latex.exe +13/05/2002 17:06 266 240 tex.dll +13/05/2002 17:06 3 584 tex.exe +\end{alltt} +and the \path|latex.exe| file is nothing but a rough copy of +\path|tex.exe| using the same core \path|tex.dll|. +The same trick has been used for the \path|mktex*.exe| family of programs which are +linked to the \path|mktex.dll| library. + +In fact, a generic tool called \path|lnexe.exe| is provided to build the +equivalent of Unix hard links for executable files only under Win32. + +\subsection{In case of problems} +\label{sec:troubleshooting} + +\subsubsection{What to do if \texttt{latex} does not find your files?} + +\begin{itemize} + +\item \cmdname{kpsewhich} is the tool of choice to debug any +problem. Unfortunately, \cmdname{kpsewhich} outputs debug information +to stderr, and the Windows console does not know how to redirect stderr +to a file\footnote{Well, NT and Win2k consoles know how to do that. But +the trick will work for any console.}. For diagnostic purposes you can +temporarily set an environment variable (in a \acro{DOS} box): + +\begin{verbatim} +SET KPATHSEA_DEBUG_OUTPUT=err.log +\end{verbatim} +You can also set the debug level: +\begin{verbatim} +SET KPATHSEA_DEBUG=-1 +\end{verbatim} + +If you want to redirect stderr to stdout, which is not possible +Windows, then do: +\begin{verbatim} +SET KPATHSEA_DEBUG_OUTPUT=con: +\end{verbatim} +This way you can capture both stdout and stderr in the same file. + +\item Assuming the installation has been done in \path|c:/Program Files/TeXLive|, check + the following values: \\ + {\small + \begin{tabular}{ll} + \path|kpsewhich -expand-path $SELFAUTOPARENT| & \path|c:/Program Files/TeXLive| \\ + \path|kpsewhich -expand-path $TEXMF| & \path|c:/Program Files/TeXLive/texmf| \\ + \path|kpsewhich -expand-path $TEXMFCNF| & + \path|.;c:/Program Files/TeXLive/texmf/web2c;| \\ + & \path|c:/Program Files/TeXLive/bin/win32;| \\ + & \path|c:/Program Files/TeXLive/bin;| \\ + & \path|c:/Program Files/TeXLive| \\ + \path|kpsewhich -expand-var $TEXINPUTS| & \path|.;c:/Program Files/TeXLive/texmf/tex//| + \end{tabular} +} +\item If you have other \TeX{}-related values already set in your + environment, please, remove them. They are overriding the ones in + texmf.cnf. +\item Check the values from:\\ +{\small + \begin{tabular}{ll} + \texttt{kpsewhich cmr10.tfm} & \path|c:/Program Files/TeXLive/texmf/fonts/tfm/public/cm/cmr10.tfm|\\ + \texttt{kpsewhich latex.fmt}& \path|c:/Program Files/TeXLive/texmf/web2c/latex.fmt| + \end{tabular} +} +\item At this point, if everything is correct, \TeX{} and friends + should work. If it is not the case, you will need to play with + the \path|-debug=n| option from \path|kpsewhich|, and check back all + the values. Try to identify and report the problem. +\end{itemize} + +\subsubsection{What to do if your setup still does not work as expected?} + +Here are several questions to investigate: + +\begin{enumerate} +\item Is \file{tex.exe} in my \path|PATH|? + +\item Is the \path|TEXMFCNF| variable correctly set to +\path|c:/Program Files/TeXLive/texmf-var/web2c| (default value)? + +\item Are there any errors in the log file generated by the +\file{TeXSetup.exe} program? You can find this by searching for the +string \samp{Error}. + +\item Are there any relevant bug fixes at \url{http://tug.org/texlive/}? +(Unlikely, but it doesn't hurt to check.) + +\item Check the web pages at +\url{http://www.fptex.org/}, or consider subscribing to the \fpTeX{} +mailing list, via \url{http://tug.org/mailman/listinfo/fptex}. + +\end{enumerate} + + +The \TeXLive{} software consists of hundreds and programs and tens of +thousands of files, all from varying sources. So it is quite difficult to +predict all possible causes for problems. Nevertheless, we will do our +best to help you. (see section~\ref{sec:help} on p.~\pageref{sec:help}.) + + +\subsection{Compiling the source files} + +You have the whole set of source files, in the +\path|source/source.tar.bz2| archive available in the distribution together with +a patch file for Win32. To +be able to compile the whole distribution for Windows, you will need: + +\begin{itemize} +\item Windows 2K/XP +\item Microsoft Visual Studio .Net 2003 +\item a set of Unix tools (\texttt{sed}, + \texttt{grep}, \texttt{gawk}, etc.) and also Perl, Flex and Bison, +\item to adjust the paths in the + \path|win32/make/common.mak| file according to your installation +\item to adjust the paths in the Perl script file + \path|win32/perl/build.pl|, +\item run the compilation from the \path|mswin32/| directory using this + command: +\begin{verbatim} +c:\texlive\source\mswin32>perl ./perl/build.pl --install --log=install.log +\end{verbatim} +\end{itemize} + +There is a lot of work to do to make this process easier and cleaner. + +\subsection{Where to get more information} + +The Windows \TeX{} system included on \TeXLive{} is also known as +\fpTeX. The packaging differs, but \fpTeX{} is no more no less than the +current \TeXLive\ release for Windows. + +The \fpTeX{} home page is \url{http://www.fptex.org}. + +The current \fpTeX release is available from any \CTAN site in +\url{htp://www.ctan.org/tex-archive/systems/win32/fptex}. + +The main ftp site for \fpTeX\ is \url{ftp://ftp.dante.de/pub/fptex/} +from where beta versions of \fpTeX\ and additionnal tools are available. +This main site is (partially) mirrored daily by all \CTAN{} sites at +\path|systems/win32/fptex|. + +The \TeX{} Users Group is kindly hosting a mailing list dedicated to +\fpTeX. It is used for announcements, bug reports, enhancement requests, +and general discussion about \fpTeX. To subscribe, visit +\url{http://tug.org/mailman/listinfo/fptex}. The mailing list +address is \email{fptex@tug.org}. + + +\section{A user's guide to \protect\Webc{}} + +\Webc{} is an integrated collection of \TeX-related programs: \TeX{} +itself, \MF{}, \MP, \BibTeX{}, etc. It is the heart of \TeXLive{}. + +A bit of history: The original implementation was by Tomas Rokicki who, +in 1987, developed a first \TeX{}-to-C system adapting change files +under Unix, which were primarily the work of Howard Trickey and Pavel +Curtis. Tim Morgan became the maintainer of the system, and during this +period the name changed to Web-to-C\@. In 1990, Karl Berry took over +the work, assisted by dozens of additional contributors, and in 1997 he +handed the baton to Olaf Weber. + +The \Webc{} system runs on Unix, 32-bit Windows systems, \MacOSX{}, and +other operating systems. It uses Knuth's original sources for \TeX{} and +other basic programs written in \web{} and translates them into C source +code. The core \TeX{} programs are: + +\begin{cmddescription} +\item[bibtex] Maintaining bibliographies. +\item[dmp] \cmdname{troff} to MPX (\MP{} pictures). +\item[dvicopy] Expands virtual font references in \dvi{} files. +\item[dvitomp] \dvi{} to MPX (MetaPost pictures). +\item[dvitype] \dvi{} to human-readable text. +\item[gftodvi] Generic font proofsheets. +\item[gftopk] Generic to packed fonts. +\item[gftype] GF to human-readable text. +\item[makempx] \MP{} label typesetting. +\item[mf] Creating typeface families. +\item[mft] Prettyprinting \MF{} source. +\item[mpost] Creating technical diagrams. +\item[mpto] MetaPost label extraction. +\item[newer] Compare modification times. +\item[patgen] Creating hyphenation patterns. +\item[pktogf] Packed to generic fonts. +\item[pktype] PK to human-readable text. +\item[pltotf] Plain text property list to TFM. +\item[pooltype] Display \web{} pool files. +\item[tangle] \web{} to Pascal. +\item[tex] Typesetting. +\item[tftopl] TFM to plain text property list. +\item[vftovp] Virtual font to virtual property list. +\item[vptovf] Virtual property list to virtual font. +\item[weave] \web{} to \TeX. +\end{cmddescription} + +\noindent The precise functions and syntax of these programs are +described in the documentation of the individual packages and of \Webc{} +itself. However, knowing a few principles governing the whole family of +programs will help you take advantage of your \Webc{} installation. + +All programs honor these standard \acro{GNU} options: +\begin{ttdescription} +\item[-{}-help] print basic usage summary. +\item[-{}-verbose] print detailed progress report. +\item[-{}-version] print version information, then exit. +\end{ttdescription} + +For locating files the \Webc{} programs use the path searching library +\KPS{}. This library uses a combination of environment variables and a +configuration files to optimize searching the (huge) collection of +\TeX{} files. \Webc{} can look at more than one directory tree +simultaneously, which is useful in maintaining \TeX's standard +distribution and local extensions in two distinct trees. To speed up +file searches the root of each tree has a file \file{ls-R}, containing +an entry showing the name and relative pathname for all files under that +root. + +\subsection{\protect\KPS\ path searching} + +Let us first describe the generic path searching mechanism of the \KPS{} +library. + +We call a \emph{search path} a colon- or semicolon\hyph sepa\-rated list +of \emph{path elements}, which are basically directory names. A +search path can come from (a combination of) many sources. To look up +a file \samp{my-file} along a path \samp{.:/dir}, \KPS{} checks each +element of the path in turn: first \file{./my-file}, then +\file{/dir/my-file}, returning the first match (or possibly all +matches). + +In order to adapt optimally to all operating systems' conventions, on +non-Unix systems \KPS{} can use filename separators different from +colon (\samp{:}) and slash (\samp{/}). + +To check a particular path element \var{p}, \KPS{} first checks if a +prebuilt database (see ``Filename data\-base'' on +page~\pageref{Filename-database}) applies to \var{p}, i.e., if the database +is in a directory that is a prefix of \var{p}. If so, the path +specification is matched against the contents of the database. + +If the database does not exist, or does not apply to this path +element, or contains no matches, the filesystem is searched (if this +was not forbidden by a specification starting with \samp{!!}\ and if +the file being searched for must exist). \KPS{} constructs the list +of directories that correspond to this path element, and then checks +in each for the file being sought. + +The ``file must exist'' condition comes into play with \samp{.vf} files and +input files read by \TeX's \cs{openin} command. Such files may not +exist (e.g., \file{cmr10.vf}), and so it would be wrong to search the +disk for them. Therefore, if you fail to update \file{ls-R} when you +install a new \samp{.vf} file, it will never be found. +Each path element is checked in turn: first the database, then the +disk. If a match is found, the search stops and the result is +returned. + +Although the simplest and most common path element is a directory +name, \KPS{} supports additional features in search paths: layered +default values, environment variable names, config file values, users' +home directories, and recursive subdirectory searching. Thus, we say +that \KPS{} \emph{expands} a path element, meaning it transforms all +the specifications into basic directory name or names. This is +described in the following sections in the same order as it takes +place. + +Note that if the filename being searched for is absolute or explicitly +relative, i.e., starts with \samp{/} or \samp{./} or \samp{../}, +\KPS{} simply checks if that file exists. + +\ifSingleColumn +\else +\begin{figure*} +\verbatiminput{../examples/ex5.tex} +\setlength{\abovecaptionskip}{0pt} + \caption{An illustrative configuration file sample} + \label{fig:config-sample} +\end{figure*} +\fi + +\subsubsection{Path sources} +\label{Path-sources} + +A search path can come from many sources. In the order in which +\KPS{} uses them: + +\begin{enumerate} +\item + A user-set environment variable, for instance, \envname{TEXINPUTS}\@. + Environment variables with a period and a program name appended + override; e.g., if \samp{latex} is the name of the program being run, + then \envname{TEXINPUTS.latex} will override \envname{TEXINPUTS}. +\item + A program-specific configuration file, for exam\-ple, a line + \samp{S /a:/b} in \cmdname{dvips}'s \file{config.ps}. +\item A \KPS{} configuration file \file{texmf.cnf}, containing a line like + \samp{TEXINPUTS=/c:/d} (see below). +\item The compile-time default. +\end{enumerate} +\noindent You can see each of these values for a given +search path by using the debugging options (see ``Debugging actions'' +on page~\pageref{Debugging}). + +\subsubsection{Config files} + +\begingroup\tolerance=3500 +\KPS{} reads \emph{runtime configuration files} named \file{texmf.cnf} +for search path and other definitions. The search path used to look +for these files is named \envname{TEXMFCNF} (by default such a file lives +in the \file{texmf/web2c} subdirectory). \emph{All} +\file{texmf.cnf} files in the search path will be read and definitions +in earlier files override those in later files. Thus, with a search +path of \verb|.:$TEXMF|, values from \file{./texmf.cnf} override those +from \verb|$TEXMF/texmf.cnf|. +\endgroup + +\begin{itemize} +\item + Comments start with \code{\%} and continue to the end of the line. +\item + Blank lines are ignored. +\item + A \bs{} at the end of a line acts as a continuation character, + i.e., the next line is appended. Whitespace at the beginning of + continuation lines is not ignored. +\item + Each remaining line has the form: +\begin{alltt} + \emph{variable}[.\emph{progname}] [=] \emph{value} +\end{alltt}% + where the \samp{=} and surrounding whitespace are optional. +\item + The \ttvar{variable} name may contain any character other + than whitespace, \samp{=}, or \samp{.}, but sticking to + \samp{A-Za-z\_} is safest. +\item + If \samp{.\var{progname}} is present, the definition only + applies if the program that is running is named + \texttt{\var{progname}} or \texttt{\var{progname}.exe}. This allows + different flavors of \TeX{} to have different search paths, for + example. +\item \var{value} may contain any characters except + \code{\%} and \samp{@}. The + \code{\$\var{var}.\var{prog}} feature is not available on the + right-hand side; instead, you must use an additional variable. A + \samp{;}\ in \var{value} is translated to \samp{:}\ if + running under Unix; this is useful to be able to have a single + \file{texmf.cnf} for Unix, \acro{MS-DOS} and Windows systems. +\item + All definitions are read before anything is expanded, so + variables can be referenced before they are defined. +\end{itemize} +A configuration file fragment illustrating most of these points is +\ifSingleColumn +shown below: + +\verbatiminput{../examples/ex5.tex} +\else +shown in Figure~\ref{fig:config-sample}. +\fi + +\subsubsection{Path expansion} +\label{Path-expansion} + + +\KPS{} recognizes certain special characters and constructions in +search paths, similar to those available in Unix shells. As a +general example, the complex path, +\verb+~$USER/{foo,bar}//baz+, expands to all subdirectories under +directories \file{foo} and \file{bar} in \texttt{\$USER}'s home +directory that contain a directory or file \file{baz}. These +expansions are explained in the sections below. +%$ +\subsubsection{Default expansion} +\label{Default-expansion} + +\tolerance=2500 +If the highest-priority search path (see ``Path sources'' on +page~\pageref{Path-sources}) contains an \emph{extra colon} (i.e., +leading, trailing, or doubled), \KPS{} inserts at that point the +next-highest-prio\-rity search path that is defined. If that inserted +path has an extra colon, the same happens with the next highest. For +example, given an environment variable setting + +\tolerance=1500 + +\begin{alltt} +> \Ucom{setenv TEXINPUTS /home/karl:} +\end{alltt} +and a \code{TEXINPUTS} value from \file{texmf.cnf} of + +\begin{alltt} + .:\$TEXMF//tex +\end{alltt} +then the final value used for searching will be: + +\begin{alltt} + /home/karl:.:\$TEXMF//tex +\end{alltt} + +Since it would be useless to insert the default value in more than one +place, \KPS{} changes only one extra \samp{:}\ and leaves any others in +place: it checks first for a leading \samp{:}, then a trailing +\samp{:}, then a doubled \samp{:}. + +\subsubsection{Brace expansion} + +A useful feature is brace expansion, which means that, for instance, +\verb+v{a,b}w+ expands to \verb+vaw:vbw+. Nesting is allowed. +This can be used to implement multiple \TeX{} hierarchies, by +assigning a brace list to \code{\$TEXMF}. +For example, in \file{texmf.cnf}, you find +the following definition: +\begin{verbatim} + TEXMF = {$HOMETEXMF,$TEXMFLOCAL,!!$VARTEXMF,!!$TEXMFMAIN} +\end{verbatim} +Using this you can then write something like +\begin{verbatim} + TEXINPUTS = .;$TEXMF/tex// +\end{verbatim} +%$ +which means that, after looking in the current directory, the +\code{\$HOMETEXMF/tex}, \code{\$TEXMFLOCAL/tex}, \code{\$VARTEXMF/tex} +and \code{\$TEXMFMAIN/tex} trees \emph{only}) will be searched (the +last two use using \file{ls-R} data base files). It is a convenient +way for running two parallel \TeX{} structures, one ``frozen'' (on a +\CD, for instance) and the other being continuously updated with new +versions as they become available. By using the \code{\$TEXMF} +variable in all definitions, one is sure to always search the +up-to-date tree first. + +\subsubsection{Subdirectory expansion} +\label{Subdirectory-expansion} + +Two or more consecutive slashes in a path element following a directory +\var{d} is replaced by all subdirectories of \var{d}: first those +subdirectories directly under \var{d}, then the subsubdirectories under +those, and so on. At each level, the order in which the directories are +searched is \emph{unspecified}. + +If you specify any filename components after the \samp{//}, only +subdirectories with matching components are included. For example, +\samp{/a//b} expands into directories \file{/a/1/b}, \file{/a/2/b}, +\file{/a/1/1/b}, and so on, but not \file{/a/b/c} or \file{/a/1}. + +Multiple \samp{//} constructs in a path are possible, but +\samp{//} at the beginning of a path is ignored. + +\subsubsection{List of special characters and their meaning: a summary} + +The following list summarises the meaning of special characters +in \KPS{} configuration files. + +\newcommand{\CODE}[1]{\makebox[2.5em][l]{\code{#1}}} +\begin{ttdescription} +\item[\CODE{:}] Separator in path specification; at the beginning or + the end of a path it substitutes the default path expansion. +\item[\CODE{;}] Separator on non-Unix systems (acts like \code{:}). +\item[\CODE{\$}] Variable expansion. +\item[\CODE{\string~}] Represents the user's home directory. +\item[\CODE{\char`\{\dots\char`\}}] Brace expansion. +\item[\CODE{//}] Subdirectory expansion (can occur anywhere in + a path, except at its beginning). +\item[\CODE{\%}] Start of comment. +\item[\CODE{\bs}] Continuation character (allows multi-line entries). +\item[\CODE{!!}] Search \emph{only} database to locate file, \emph{do + not} search the disk. +\end{ttdescription} + + +\subsection{Filename databases} +\label{Filename-database} + +\KPS{} goes to some lengths to minimize disk accesses for searches. +Nevertheless, at installations with enough directories, searching each +possible directory for a given file can take an excessively long time +(this is especially true if many hundreds of font directories have to +be traversed.) Therefore, \KPS{} can use an externally-built plain text +``database'' file named \file{ls-R} that maps files to directories, +thus avoiding the need to exhaustively search the disk. + +A second database file \file{aliases} allows you to give additional +names to the files listed in \file{ls-R}. This can be helpful to +confirm to \acro{DOS} 8.3 filename conventions in source files. + +\subsubsection{The filename database} +\label{ls-R} + +As explained above, the name of the main filename database must be +\file{ls-R}. You can put one at the root of each \TeX{} hierarchy in +your installation that you wish to be searched (\code{\$TEXMF} by +default); most sites have only one hierarchy. \KPS{} looks for +\file{ls-R} files along the \code{TEXMFDBS} path. + +The recommended way to create and maintain \samp{ls-R} is to run the +\code{mktexlsr} script included with the distribution. It is invoked +by the various \samp{mktex}\dots\ scripts. In principle, this script +just runs the command +\begin{alltt} +cd \var{/your/texmf/root} && ls -LAR ./ >ls-R +\end{alltt} +presuming your system's \code{ls} produces the right output format +(\acro{GNU}'s \code{ls} is all right). To ensure that the database is always +up-to-date, it is easiest to rebuild it regularly via \code{cron}, so +that for changes in the installed files\Dash perhaps after installing or +updating a \LaTeX{} package\Dash the file \file{ls-R} is automatically +updated. + +If a file is not found in the database, by default \KPS{} goes ahead +and searches the disk. If a particular path element begins with +\samp{!!}, however, \emph{only} the database will be searched for that +element, never the disk. + + +\subsubsection{kpsewhich: Standalone path searching} +\label{Invoking-kpsewhich} + +The \texttt{kpsewhich} program exercises path searching independent of any +particular application. This can be useful as a sort of \code{find} +program to locate files in \TeX{} hierarchies (this is used heavily in +the distributed \samp{mktex}\dots\ scripts). + +\begin{alltt} +> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} +\end{alltt} +The options specified in \ttvar{option} start with either \samp{-} +or \samp{-{}-}, and any unambiguous abbreviation is accepted. + +\KPS{} looks up each non-option argument on the command line as a +filename, and returns the first file found. There is no option to +return all the files with a particular name (you can run the Unix +\samp{find} utility for that). + +The more important options are described next. + +\begin{ttdescription} +\item[\texttt{-{}-dpi=\var{num}}]\mbox{} + Set the resolution to \ttvar{num}; this only affects \samp{gf} + and \samp{pk} lookups. \samp{-D} is a synonym, for compatibility + with \cmdname{dvips}. Default is 600. + +\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ + Set the format for lookup to \ttvar{name}. By default, the + format is guessed from the filename. For formats which do not have + an associated unambiguous suffix, such as \MP{} support files and + \cmdname{dvips} configuration files, you have to specify the name as + found in the first column of Table~\ref{tab:kpathsea}, which lists + currently recognized names, a description, possible file extensions, + and associated environment variables. +\end{ttdescription} + + +\def\KpathKey#1#2#3#4#5{% name, number, description, variables, + % suffixes +\SetRowColor#1 & #3 & #4 & #5\\} +\def\HEAD#1{\multicolumn{1}{l}{\emph{#1}}} +% +\begin{small} +% a footnoterule immediately under a bottom-of-page rule looks dead +% silly, so we suppress it +\renewcommand\footnoterule{\relax} +% +\begin{longtable}{@{}% + >{\ttfamily}P{.16\textwidth}% Col.1 + P{.3\textwidth}% Col 2 + >{\ttfamily\footnotesize}P{.29\textwidth}% Col 3 + >{\ttfamily}P{.14\textwidth}% Col 4 +@{}} +\caption{Kpathsea file types.}\label{tab:kpathsea}\\ +\emph{Name} & \HEAD{Description} & \HEAD{Variables} +& \HEAD{Suffixes}\\ +\hline +\endfirsthead +\multicolumn{3}{l}{Kpathsea file types \emph{continued}}\\ +\emph{Name} & \HEAD{Description} & \HEAD{Variables} +& \HEAD{Suffixes}\\ +\hline +\noalign{\vspace{2pt}} +\endhead +\mbox{}\\ +\hline +\endfoot +\KpathKey + {afm} + {4} + {Adobe font metrics} + {AFMFONTS} + {.afm} +\KpathKey + {base} + {5} + {Metafont memory dump} + {MFBASES, TEXMFINI} + {.base} +\KpathKey + {bib} + {6} + {\BibTeX{} bibliography source} + {BIBINPUTS, TEXBIB} + {.bib} +\KpathKey + {} + {2} + {bitmap fonts} + {GLYPHFONTS, TEXFONTS} + {} +\KpathKey + {bst} + {7} + {\BibTeX{} style files} + {BSTINPUTS} + {.bst} +\KpathKey + {cnf} + {8} + {Runtime configuration files} + {TEXMFCNF} + {.cnf} +\KpathKey + {dvips config} + {34} + {\textsf{dvips} configuration files, e.g., \file{config.ps} + and \file{psfonts.map}} + {TEXCONFIG} + {.map} +\KpathKey + {fmt} + {10} + {\TeX{} memory dump} + {TEXFORMATS, TEXMFINI} + {.fmt, .efmt, .efm} +\KpathKey + {gf} + {0} + {generic font bitmap} + {GFFONTS} + {.gf} +\KpathKey + {graphic/figure} + {25} + {Encapsulated \PS{} figures} + {TEXPICTS, TEXINPUTS} + {.eps, .epsi} +\KpathKey + {ist} + {35} + {\textsf{makeindex} style files} + {TEXINDEXSTYLE, INDEXSTYLE} + {.ist} +\KpathKey + {ls-R} + {9} + {Filename databases} + {TEXMFDBS} + {} +\KpathKey + {map} + {11} + {Fontmaps} + {TEXFONTMAPS} + {.map} +\KpathKey + {mem} + {12} + {MetaPost memory dump} + {MPMEMS, TEXMFINI} + {.mem} +\KpathKey + {mf} + {13} + {Metafont source} + {MFINPUTS} + {.mf} +\KpathKey + {mfpool} + {14} + {Metafont program strings} + {MFPOOL, TEXMFINI} + {.pool} +\KpathKey + {mft} + {15} + {MFT style file} + {MFTINPUTS} + {.mft} +\KpathKey + {} + {41} + {miscellaneous fonts} + {MISCFONTS} + {} +\KpathKey + {mp} + {16} + {MetaPost source} + {MPINPUTS} + {.mp} +\KpathKey + {mppool} + {17} + {MetaPost program strings} + {MPPOOL, TEXMFINI} + {.pool} +\KpathKey + {MetaPost support} + {18} + {MetaPost support files, used by DMP} + {MPSUPPORT} + {} +\KpathKey + {ocp} + {19} + {\OMEGA{} compiled process files} + {OCPINPUTS} + {.ocp} +\KpathKey + {ofm} + {20} + {\OMEGA{} font metrics} + {OFMFONTS, TEXFONTS} + {.ofm, .tfm} +\KpathKey + {opl} + {21} + {\OMEGA{} property lists} + {OPLFONTS, TEXFONTS} + {.opl} +\KpathKey + {otp} + {22} + {\OMEGA{} translation process files} + {OTPINPUTS} + {.otp} +\KpathKey + {ovf} + {23} + {\OMEGA{} virtual fonts} + {OVFFONTS, TEXFONTS} + {.ovf} +\KpathKey + {ovp} + {24} + {\OMEGA{} virtual property lists} + {OVPFONTS, TEXFONTS} + {.ovp} +\KpathKey + {pk} + {1} + {packed bitmap fonts} + {\emph{program}FONTS \textrm{(\texttt{\emph{program}} being + \textsmaller{\cmdname{XDVI}}, + etc.)}, PKFONTS, TEXPKS, GLYPHFONTS, TEXFONTS} + {.pk} +\KpathKey + {\PS{} header} + {30} + {downloadable \PS{}} + {TEXPSHEADERS, PSHEADERS} + {.pro, .enc} +\KpathKey + {tex} + {26} + {\TeX{} source} + {TEXINPUTS} + {.tex, .cls, .sty, .clo, .def} +\KpathKey + {TeX system documentation} + {27} + {Documentation files for the \TeX{} system} + {TEXDOCS} + {} +\KpathKey + {TeX system sources} + {29} + {Source files for the \TeX{} system} + {TEXSOURCES} + {} +\KpathKey + {texpool} + {28} + {\TeX{} program strings} + {TEXPOOL, TEXMFINI} + {.pool} +\KpathKey + {tfm} + {3} + {\TeX{} font metrics} + {TFMFONTS, TEXFONTS} + {.tfm} +\KpathKey + {Troff fonts} + {31} + {Troff fonts, used by DMP} + {TRFONTS} + {} +\KpathKey + {truetype fonts} + {36} + {TrueType outline fonts} + {TTFONTS} + {.ttf, .ttc} +\KpathKey + {Type~1 fonts} + {32} + {Type 1 \PS{} outline fonts} + {T1FONTS, T1INPUTS, TEXPSHEADERS, DVIPSHEADERS} + {.pfa, .pfb} +\KpathKey + {type42 fonts} + {37} + {Type 42 \PS{} outline fonts} + {T42FONTS} + {} +\KpathKey + {vf} + {33} + {virtual fonts} + {VFFONTS, TEXFONTS} + {.vf} +\KpathKey + {web2c files} + {38} + {\Webc{} support files} + {WEB2C} + {} +\KpathKey + {other text files} + {39} + {text files used by `\textsf{foo}'} + {FOOINPUTS} + {} +\KpathKey + {other binary files} + {40} + {binary files used by `\textsf{foo}'} + {FOOINPUTS} + {} +\end{longtable} +\end{small} + + +\begin{multicols}{2} + + The last two entries in Table~\ref{tab:kpathsea} are special + cases, where the paths and environment variables depend on the name + of the program: the variable name is constructed by converting the + program name to upper case, and then appending \texttt{INPUTS}. + + The environment variables are set by default in the configuration + file \file{texmf.cnf}. It is only when you want to override one or + more of the values specified in that file that you might want to set + them explicitly in your execution environment. + + The \samp{-{}-format} and \samp{-{}-path} options are mutually + exclusive. + +\begin{ttdescription} + +\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ + Set the mode name to \ttvar{string}; this only affects \samp{gf} + and \samp{pk} lookups. No default: any mode will be found. +\item[\texttt{-{}-must-exist}]\mbox{}\\ + Do everything possible to find the files, notably including + searching the disk. By default, only the \file{ls-R} database is + checked, in the interest of efficiency. +\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ + Search along the path \ttvar{string} (colon-separated as usual), + instead of guessing the search path from the filename. \samp{//} and + all the usual expansions are supported. The options \samp{-{}-path} + and \samp{-{}-format} are mutually exclusive. +\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ + Set the program name to \texttt{\var{name}}. + This can affect the search paths via the \texttt{.\var{progname}} + feature. + The default is \cmdname{kpsewhich}. +\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ + shows the path used for file lookups of file type \texttt{\var{name}}. + Either a filename extension (\code{.pk}, \code{.vf}, etc.) or a + name can be used, just as with \samp{-{}-format} option. +\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ + sets the debugging options to \texttt{\var{num}}. +\end{ttdescription} + + +\subsubsection{Examples of use} +\label{SExamplesofuse} + +Let us now have a look at \KPS{} in action. Here's a straightforward search: + +\begin{alltt} +> \Ucom{kpsewhich article.cls} +/usr/local/texmf/tex/latex/base/article.cls +\end{alltt} +We are looking for the file \file{article.cls}. Since the \samp{.cls} +suffix is unambiguous we do not need to specify that we want to look for a +file of type \optname{tex} (\TeX{} source file directories). We find it in +the subdirectory \file{tex/latex/base} below the \samp{TEXMF} root +directory. Similarly, all of the following are found without problems +thanks to their unambiguous suffix. +\begin{alltt} +> \Ucom{kpsewhich array.sty} + /usr/local/texmf/tex/latex/tools/array.sty +> \Ucom{kpsewhich latin1.def} + /usr/local/texmf/tex/latex/base/latin1.def +> \Ucom{kpsewhich size10.clo} + /usr/local/texmf/tex/latex/base/size10.clo +> \Ucom{kpsewhich small2e.tex} + /usr/local/texmf/tex/latex/base/small2e.tex +> \Ucom{kpsewhich tugboat.bib} + /usr/local/texmf/bibtex/bib/beebe/tugboat.bib +\end{alltt} + +The latter is a \BibTeX{} bibliography database for \textsl{TUGBoat} articles. + +\begin{alltt} +> \Ucom{kpsewhich cmr10.pk} +\end{alltt} +Font bitmap glyph files of type \file{.pk} are used by display +programs like \cmdname{dvips} and \cmdname{xdvi}. Nothing is returned in +this case since there are no pre-generated Computer Modern \samp{.pk} +files on our system (since we use the Type~1 versions included in \TeXLive{}). +\begin{alltt} +> \Ucom{kpsewhich ecrm1000.pk} +\ifSingleColumn /usr/local/texmf/fonts/pk/ljfour/jknappen/ec/ecrm1000.600pk +\else +/usr/local/texmf/fonts/pk/ljfour/jknappen/ +... ec/ecrm1000.600pk +\fi\end{alltt} +For the extended Computer Modern files we had to generate \samp{.pk} +files, and since the default \MF{} mode on our installation is +\texttt{ljfour} with a base resolution of 600\dpi{} (dots per inch), +this instantiation is returned. +\begin{alltt} +> \Ucom{kpsewhich -dpi=300 ecrm1000.pk} +\end{alltt} +In this case, when specifying that we are interested in a resolution +of 300\dpi{} (\texttt{-dpi=300}) we see that no such font is available on +the system. In fact, a program like \cmdname{dvips} or \cmdname{xdvi} would +go off and actually build the \texttt{.pk} files at the required +resolution using the script \cmdname{mktexpk}. + +Next we turn our attention to \cmdname{dvips}'s header and configuration +files. We first look at one of the commonly used files, the general +prolog \file{tex.pro} for \TeX{} support, before turning our attention +to the generic configuration file (\file{config.ps}) and the +\PS{} font map \file{psfonts.map}. As the \samp{.ps} suffix is +ambiguous we have to specify explicitly which type we are considering +(\optname{dvips config}) for the file \texttt{config.ps}. +\begin{alltt} +> \Ucom{kpsewhich tex.pro} + /usr/local/texmf/dvips/base/tex.pro +> \Ucom{kpsewhich --format="dvips config" config.ps} + /usr/local/texmf/config/config.ps +> \Ucom{kpsewhich psfonts.map} + /usr/local/texmf/dvips/base/psfonts.map +\end{alltt} + +We now take a closer look at the \acro{URW} Times \PS{} support +files. The prefix for these in the standard font naming scheme is +\samp{utm}. The first file we look at is the configuration file, +which contains the name of the map file: +\begin{alltt} +> \Ucom{kpsewhich --format="dvips config" config.utm} +/usr/local/texmf/dvips/psnfss/config.utm +\end{alltt} +The contents of that file is +\begin{alltt} + p +utm.map +\end{alltt} +which points to the file \file{utm.map}, which we want to +locate next. +\begin{alltt} +> \Ucom{kpsewhich --format="dvips config" utm.map} +/usr/local/texmf/dvips/psnfss/utm.map +\end{alltt} +This map file defines the file names of the Type~1 \PS{} fonts in +the URW collection. Its contents look like (we only show part of the +lines): +\begin{alltt} +utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} +\ifSingleColumn /usr/local/texmf/fonts/type1/urw/utm/utmr8a.pfb +\else /usr/local/texmf/fonts/type1/ +...urw/utm/utmr8a.pfb +\fi\end{alltt} + +It should be evident from these few examples how you can easily locate +the whereabouts of a given file. This is especially important if you +suspect that the wrong version of a file is picked up somehow, since +\cmdname{kpsewhich} will show you the first file encountered. + +\subsubsection{Debugging actions} +\label{Debugging} + +Sometimes it is necessary to investigate how a program resolves file +references. To make this practical, \KPS{} offers various levels of +debugging output: + +\begin{ttdescription} +\item[\texttt{\ 1}] \texttt{stat} calls (disk lookups). When running + with an up-to-date \file{ls-R} database this should almost give no + output. +\item[\texttt{\ 2}] References to hash tables (such as the \file{ls-R} + database, map files, configuration files). +\item[\texttt{\ 4}] File open and close operations. +\item[\texttt{\ 8}] General path information for file types + searched by \KPS. This is useful to find out where a particular + path for the file was defined. +\item[\texttt{16}] Directory list for each path element (only relevant + for searches on disk). +\item[\texttt{32}] File searches. +\end{ttdescription} +A value of \texttt{-1} will set all the above options; in practice, +this is usually the most convenient value touse. + +Similarly, with the \cmdname{dvips} program, by setting a combination of +debug switches, one can follow in detail where files are being picked up +from. Alternatively, when a file is not found, the debug trace shows in +which directories the program looks for the given file, so that one can +get an indication what the problem~is. + +Generally speaking, as most programs call the \KPS{} library +internally, one can select a debug option by using the +\envname{KPATHSEA\_DEBUG} environment variable, and setting it to (a +combination of) values as described in the above list. + +(Note for Windows users: it is not easy to redirect +all messages to a file in this system. For diagnostic purposes +you can temporarily \texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log}). + +Let us consider, as an example, a small \LaTeX{} source file, +\file{hello-world.tex}, which contains the following input. +\begin{verbatim} + \documentclass{article} + \begin{document} + Hello World! + \end{document} +\end{verbatim} +This little file only uses the font \file{cmr10}, so let us look +how \cmdname{dvips} prepares the \PS{} file (we want to use the Type~1 +version of the Computer Modern fonts, hence the option \texttt{-Pcms}). +\begin{alltt} +> \Ucom{dvips -d4100 hello-world -Pcms -o} +\end{alltt} +In this case we have combined \cmdname{dvips}'s debug class 4 (font +paths) with \KPS's path element expansion (see \cmdname{dvips} Reference +Manual, \OnCD{texmf/doc/html/dvips/dvips_toc.html}). +The output (slightly rearranged) appears in +Figure~\ref{fig:dvipsdbga}. +\begin{figure*}[tp] +\centering +\input{../examples/ex6a.tex} +\caption{Finding configuration files}\label{fig:dvipsdbga} + +\bigskip + +\input{../examples/ex6b.tex} +\caption{Finding the prolog file}\label{fig:dvipsdbgb} + +\bigskip + +\input{../examples/ex6c.tex} +\caption{Finding the font file}\label{fig:dvipsdbgc} +\end{figure*} + +\cmdname{dvips} starts by locating its working files. First, +\file{texmf.cnf} is found, which gives the definitions of the search +paths for the other files, then the file database \file{ls-R} (to +optimize file searching) and the file \file{aliases}, which makes it +possible to declare several names (e.g., a short \acro{DOS}-like 8.3 and +a more natural longer version) for the same file. Then \cmdname{dvips} +goes on to find the generic configuration file \file{config.ps} +before looking for the customization file \file{.dvipsrc} (which, in +this case is \emph{not found}). Finally, \cmdname{dvips} locates the +config file for the Computer Modern \PS{} fonts \file{config.cms} +(this was initiated with the \texttt{-Pcms} option on the \cmdname{dvips} +command). This file contains the list of the map files which +define the relation between the \TeX{}, \PS{} and file system +names of the fonts. +\begin{alltt} +> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} + p +ams.map + p +cms.map + p +cmbkm.map + p +amsbkm.map +\end{alltt} +\cmdname{dvips} thus goes on to find all these files, plus the generic +map file \file{psfonts.map}, which is always loaded (it contains +declarations for commonly used \PS{} fonts; see the last part of +Section \ref{SExamplesofuse} for more details about \PS{} map +file handling). + +At this point \cmdname{dvips} identifies itself to the user: +\begin{alltt} +This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) +\end{alltt} +\ifSingleColumn +Then it goes on to look for the prolog file \file{texc.pro}: +\begin{alltt}\small +kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro +\end{alltt} +\else +Then it goes on to look for the prolog file \file{texc.pro} (see +Figure~\ref{fig:dvipsdbgb}). +\fi + +After having found the file in question, \cmdname{dvips} outputs +date and time, and informs us that it will generate the +file \file{hello-world.ps}, then that it needs the font file +\file{cmr10}, and that the latter is declared as ``resident'' (no +bitmaps needed): +\begin{alltt}\small +TeX output 1998.02.26:1204' -> hello-world.ps +Defining font () cmr10 at 10.0pt +Font cmr10 is resident. +\end{alltt} +Now the search is on for the file \file{cmr10.tfm}, which is found, +then a few more prolog files (not shown) are referenced, and finally +the Type~1 instance \file{cmr10.pfb} of the font is located and +included in the output file (see last line). +\begin{alltt}\small +kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, + path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: + /var/tex/fonts/tfm//). +kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm +kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, + ... + +kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb +[1] +\end{alltt} + +\subsection{Runtime options} + +Another useful feature of \Webc{} is its possibility to control a number +of memory parameters (in particular, array sizes) via the runtime file +\file{texmf.cnf} read by \KPS{}. The memory settings can be found in +Part 3 of that file in the \TeXLive{} distribution. The more important +are: + +\begin{ttdescription} +\item[\texttt{main\_memory}] + Total words of memory available, for + \TeX{}, \MF{} and \MP. You must make a new format file for each + different setting. For instance, you could generate a ``huge'' + version of \TeX{}, and call the format file \texttt{hugetex.fmt}. + Using the standard way of specifying the program name used by \KPS{}, + the particular value of the \texttt{main\_memory} variable will then + be read from \file{texmf.cnf} (compare the generic value + and the huge one instantiated by \texttt{hugetex}, + etc.). +\item[\texttt{extra\_mem\_bot}] + Extra space for ``large'' \TeX{} data structures: + boxes, glue, breakpoints, etc. Especially useful if you use + \PiCTeX{}. +\item[\texttt{font\_mem\_size}] + Number of words for font information available for \TeX. This + is more or less the total size of all TFM files read. +\item[\texttt{hash\_extra}] + Additional space for the hash table of control sequence names. + Approximately 10,000 control sequences can be stored in the main + hash table; if you have a large book with numerous cross-references, + this might not be enough. You can see that both the + \cmdname{hugetex} and \cmdname{pdflatex} program invocations ask for + an extra 15,000 control sequences (the default value of + \texttt{hash\_extra} is zero). +\end{ttdescription} + +\noindent Of course, this facility is no substitute for truly dynamic +arrays and memory allocation, but since this is extremely difficult to +implement in the present \TeX{} source, these runtime parameters provide +a practical compromise allowing some flexibility. + + +\section{Building on a new Unix platform} + +If you have a platform for which we have not created executables, you +will need to compile \TeX{} and friends from scratch. This is not as +hard as it sounds. What you need is all in the directory \texttt{source} +in the distribution. + +\subsection{Prerequisites} + +You will need at least 100 megabytes of disk space to compile all of +\TeX{} and its support programs. You'll also need an \acro{ANSI} C +compiler, a \cmdname{make} utility, a lexical scanner, and a parser +generator. We recommend the \acro{GNU} version of these programs +(\cmdname{gcc}, \acro{GNU} \cmdname{make}, \cmdname{m4}, \cmdname{flex}, +\cmdname{bison}). You may be able to work with other C compilers and +\cmdname{make} programs, but you will need a good understanding of +building Unix programs to sort out problems. + +Also, the command \texttt{uname} must return a sensible value. + + +\subsection{Configuration} + +To begin, perform a normal installation of \TeXLive{} to your disk (see +section~\ref{sec:unix-install-disk} on +p.~\pageref{sec:unix-install-disk}). You may wish to skip installing +any of the prebuilt binaries. + +Then, unpack the source from the compressed \texttt{tar} file in the +directory \dirname{source} to your disk and change directory to where +you placed it. + +Next, run \cmdname{configure} with a command line like this: +\begin{alltt} +> \Ucom{sh configure -prefix=/usr/local/TeX} +\end{alltt} + +The \optname{-prefix} directory is the one where you installed the +support tree; the directory layout will be as follows (where \$TEXDIR +stands for the directory you chose): + +\noindent +\begin{tabular}{>{\ttfamily}ll@{}} + \dirname{$TEXDIR/share/texmf} & main tree with fonts,\\ + & \qquad macros, etc\\ + \dirname{$TEXDIR/man} & Unix manual pages\\ + \dirname{$TEXDIR/info} & \acro{GNU} style Info manuals\\ + \dirname{$TEXDIR/bin/$PLATFORM} & binaries\\ +\end{tabular} +%$ + +If you want to leave out the \dirname{$PLATFORM} directory level, +i.e., put the binaries directly into \dirname{$TEXDIR/bin}, specify +the \verb|--disable-multiplatform| option to \cmdname{configure}. + +Have a look at the output of \verb|./configure --help| for more +options you can use. For example, you can skip building of \OMEGA{} and +\eTeX{}. + + +\subsection{Running \cmdname{make}} + +Make sure the shell variable or option \texttt{noclobber} is not set. +Then, run the main \cmdname{make} like this: +\begin{alltt} +> \Ucom{make world} +\end{alltt} +and relax\ldots + +Alternatively, you want to log all the output, as in: +\begin{alltt} +> \Ucom{sh -c "make world >world.log 2>\&1" \&} +\end{alltt} + +Before you believe that everything went ok, please check the log file +for errors: \acro{GNU} \cmdname{make} always uses the string \samp{***} +whenever a command fails. Also, check if all the programs were built: + +\begin{alltt} +> \Ucom{cd \emph{TEXDIR}/bin/\emph{archname}} +> \Ucom{ls | wc} +\end{alltt} +The result should be over 200 (you can check the exact number with the +\dirname{bin} directory contents in the distribution). + +If you need special privileges for \texttt{make install}, you can +separate the \samp{make world} into two different runs, like this: +\begin{alltt} +> \Ucom{make all} +> \Ucom{su} +> \Ucom{make install strip} +\end{alltt} + +After you've installed your new binaries, you should follow the normal +post-installation procedures, given in section~\ref{sec:postinstall} +on p.~\pageref{sec:postinstall}. + + +\section{Last words} + +This edition of \TeXLive{} is edited by Sebastian Rahtz, with the major +contributors being Fabrice Popineau, who has worked away unceasingly at +the Windows part of the package (especially the setup!)\ and contributed +in many different ways with ideas, advice and code, and Staszek +Wawrykiewicz, who provided great testing feedback, and co-ordinated the +Polish contributions. + +Kaja Christiansen performed a vital role in endless recompilations on +assorted Unix platforms. Vladimir Volovich did great work on cleaning +the source and making other improvements, while Gerben Wierda did all +the work for \MacOSX. + +\subsection{Acknowledgements} + +\TeXLive{} is a joint effort by virtually all \TeX{} Users Groups. In +particular, we are very grateful for past and present help from: + +\begin{itemize} + +\item The German-speaking \TeX{} Users (\acro{DANTE} e.V.), who provide +the hardware the \TeXLive{} source repository; and Rainer Sch\"opf and +Reinhard Zierke who look after it. \acro{DANTE} president Volker Schaa +coordinated production with the Lehmann's Bookstore +(\url{http://www.lob.de}). + +\item The Perforce corporation (\url{http://www.perforce.com}), for providing +a free copy of their excellent change management system, which we use to +manage. + +\item Karl Berry, who provided the original \Webc{} distribution, and +has continued to give invaluable advice, encouragement, and help. + +\item Mimi Burbank, who arranged access at the Florida State University +School of Computational Science and Information Technology to a slew of +different computers to compile \TeX{} on, and acted as an essential +guinea-pig whenever asked. + +\item Thomas Esser, without whose marvellous \teTeX{} package \TeXLive{} +would certainly not exist, and whose continual help makes it a better +product. + +\item Michel Goossens, who co-authored the documentation. + +\item Eitan Gurari, whose \TeX4ht was used to create the \HTML{} +version of this documentation, and who worked tirelessly to improve +it at short notice. + +\item Petr Olsak, who coordinated and checked all the Czech and Slovak +material very carefully. + +\item Olaf Weber, for his patient assembly and maintenance of Web2c. + +\item Graham Williams, on whose work the catalogue of packages depends. + +\end{itemize} + +In addition, Gerhard Wilhelms, Volker Schaa, Fabrice Popineau, Janka +Chleb\'\i{}kov\'a, Staszek Wawrykiewicz, Erik Frambach, and Ulrik Vieth +kindly translated documentation at various times into their respective +languages, checked other documentation, and provided very welcome +feedback. + + +\subsection{Release history} +\label{sec:history} + +Discussion began in late 1993 when the Dutch \TeX{} Users Group was +starting work on its 4All\TeX{} \CD{} for \acro{MS-DOS} users, and it +was hoped at that time to issue a single, rational, \CD{} for all +systems. This was too ambitious a target for the time, but it did spawn +not only the very successful 4All\TeX{} \CD{}, but also the \acro{TUG} +Technical Council working group on a \emph{\TeX{} Directory Structure} +(\url{http://tug.org/tds}), which specified how to create consistent and +manageable collections of \TeX{} support files. A complete draft of the +\TDS{} was published in the December 1995 issue of \textsl{TUGboat}, and +it was clear from an early stage that one desirable product would be a +model structure on \CD{}. The distribution you now have is a very direct +result of the working group's deliberations. It was also clear that the +success of the 4All\TeX{} \CD{} showed that Unix users would benefit +from a similarly easy system, and this is the other main strand of +\TeXLive. + +We first undertook to make a new Unix-based \TDS{} \CD{} in the autumn +of 1995, and quickly identified Thomas Esser's \teTeX{} as the ideal +setup, as it already had multi-platform support and was built with +portability across file systems in mind. Thomas agreed to help, and work +began seriously at the start of 1996. The first edition was released in +May 1996. At the start of 1997, Karl Berry completed a major new release +of Web2c, which included nearly all the features which Thomas Esser had +added in \teTeX, and we decided to base the 2nd edition of the \CD{} on +the standard \Webc, with the addition of \teTeX's \texttt{texconfig} +script. The 3rd edition of the \CD{} was based on a major revision of +\Webc, 7.2, by Olaf Weber; at the same time, a new revision of \teTeX +was being made, and \TeXLive{} included almost all of its features. The +4th edition followed the same pattern, using a new version of \teTeX, +and a new release of \Webc{} (7.3). The system now included a complete +Windows setup. + +For the 5th edition (March 2000) many parts of the \CD{} were revised +and checked, updating hundreds of packages. Package details were stored +in XML files. But the major change for \TeX\ Live 5 was that all +non-free software was removed. Everything in \TeXLive{} is now intended +to be compatible with the Debian Free Software Guidelines +(\url{http://www.debian.org/intro/free}); we have done our best to check +the license conditions of all packages, but we would very much +appreciate hearing of any mistakes. + +The 6th edition (July 2001) had much more material updated. The major +change was a new install concept: the user could select a more exact set +of needed collections. Language-related collections were completely +reorganized, so selecting any of them installs not only macros, fonts, +etc., but also prepares an appropriate \texttt{language.dat}. + +The 7th edition of 2002 had the notable addition of \MacOSX{} support, +and the usual myriad of updates to all sorts of packages and +programs. An important goal was integration of the source back with +\teTeX, to correct the drift apart in versions~5 and~6. + +In 2003, with the continuing flood of updates and additions, we found +that \TeXLive{} had grown so large it could no longer be contained on a +single \CD, so we split it into three different distributions (see +section~\ref{sec:multiple-dist} on p.~\pageref{sec:multiple-dist}). In +addition: + +\begin{itemize} +\item At the request of the \LaTeX{} team, we changed the standard + \cmdname{latex} and \cmdname{pdflatex} commands to now use \eTeX{} (see + p.~\pageref{text:etex}). +\item The new Latin Modern fonts were included (and are recommended). +\item Support for Alpha \acro{OSF} was removed + (\acro{HPUX} support was removed previously), since no one had (or + volunteered) hardware available on which to compile new binaries. +\item Windows setup was substantially changed; for the first time + an integrated environment based on XEmacs was introduced. +\item Important supplementary programs for Windows + (Perl, Ghost\-script, Image\-Magick, Ispell) are now installed + in the \TeXLive{} installation directory. +\item Font map files used by \cmdname{dvips}, \cmdname{dvipdfm} + and \cmdname{pdftex} are now generated by the new program + \cmdname{updmap} and installed into \dirname{texmf/fonts/map}. +\item \TeX{}, \MF{}, and \MP{} now, by default, output 8-bit input + characters as themselves in output (e.g., \verb|\write|) files, + log files, and the terminal, i.e., \emph{not} translated using the + \verb|^^| notation. In \TeXLive{}~7, this translation was + dependent on the system locale settings; now, locale settings do + not influence the \TeX{} programs' behavior. If for some reason + you need the \verb|^^| output, rename the file + \verb|texmf/web2c/cp8bit.tcx|. (Future releases will have cleaner + ways to control this.) +\item This documentation was substantially revised. +\item Finally, since the edition numbers had grown unwieldy, + the version is now simply identified by the year: \TeXLive{} 2003. +\end{itemize} + + +\subsection{Future releases} + +\emph{\TeXLive{} is not perfect!} (And never will be.) We intend to +continue to release new versions yearly, and would like to provide more +help material, more utilities, more installation programs, and (of +course) an ever-improved and checked tree of macros and fonts. This work +is all done by hard-pressed volunteers in their limited spare time, and +a great deal remains to be done. If you can help, don't hesitate to put +your name forward! + +Please send corrections, suggestions, and offers of help to:\hfill\null +\begin{quote} +Sebastian Rahtz \ / \ 7 Stratfield Road \ / \ Oxford OX2 7BG \ / \ UK \\ +\email{tex-live@tug.org} \\ +\url{http://tug.org/texlive} +\end{quote} + +\medskip +\noindent \textsl{Happy \TeX'ing!} + +\end{multicols} +\end{document} diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/live-2004.tex b/Master/texmf/doc/texlive/source/texlive-en/archive/live-2004.tex new file mode 100644 index 00000000000..10e50ee5832 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/live-2004.tex @@ -0,0 +1,3854 @@ +% $Id$ +% TeX Live documentation. Originally written by Sebastian Rahtz and +% Michel Goossens, now maintained by Karl Berry and others. +% Public domain. +% +\documentclass{article} +\let\tldocenglish=1 % for live4ht.cfg +\usepackage{tex-live} +\begin{document} + +\title{% + {\huge \textit{The \protect\TL{} Guide}\\\strut} + {\LARGE \textsf{\TK{} 2004}} +} + +\author{Sebastian Rahtz \& Karl Berry, editors \\[3mm] + \url{http://tug.org/texlive/} + } + +\date{November 2004} + +\maketitle + +\begin{multicols}{2} +\tableofcontents +\listoftables +\end{multicols} + +\section{Introduction} +\label{sec:intro} + +This document describes the main features of the \TL{} software +distribution\Dash a \TeX{} and \LaTeX{} distribution for Linux and other +Unix flavors, \MacOSX, and (32-bit) Windows systems. (Warning: it is +not especially useful for older Mac or \acro{MS-DOS} systems.) + +\TL{} includes precompiled binaries for \TeX{}, \LaTeXe{}, \MF, \MP, +\BibTeX{} and many other programs; an extensive collection of macros, +fonts and documentation; and support for typesetting in many different +scripts from around the world. It is part of the even larger \TK{} +(briefly described below in section~\ref{sec:struct-tl}, +\p.\pageref{sec:struct-tl}), a cooperative effort by the \TeX\ user +groups. + +For newer versions of the packages included here, please check +\acro{CTAN}: \url{http://www.ctan.org} + +For a brief summary of the major changes in this edition of \TL{}, +see section~\ref{sec:history} (\p.\pageref{sec:history}). + + +\subsection{Basic usage of \protect\TL{}} +\label{sec:basic} + +You can use \TL{} in three principal ways: + +\begin{enumerate} + +\item You can run \TL{} directly from the \DVD +(see section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}). +This takes almost no disk space, as you might expect, and gives you +immediate access to everything in \TL{}. Of course performance +will be worse than running on local disk, but you may well find it +acceptable. + +\item You can install all or part of \TL{} to a local disk. This +is the most common use of \TL. You will need (approximately) a +minimum of 100 megabytes, 310 megabytes for a recommended system, and +730 megabytes for a full system. + +\item You can integrate a particular package or collection into your +existing \TeX{} system, either a \TL{} system you installed +earlier, or a different system. + +\end{enumerate} + +\noindent All of these are described in detail in the \acro{OS}-specific +installation sections following, but here is a quick start: + +\begin{itemize*} + +\item The main installation script for Unix and \MacOSX{} is +\texttt{install-tl.sh}; + +\item The single package installation script is \texttt{install-pkg.sh}. + +\item Unfortunately, this version of \TL{} has no Windows installer, due +to technical difficulties. See section~\ref{sec:win-install} below +for more information. + +\end{itemize*} + + +\subsection{Getting help} +\label{sec:help} + +The \TeX{} community is both active and friendly, and virtually all +serious questions end up getting answered. However, the support is +informal, done by volunteers and casual readers, so it's especially +important that you do your homework before asking. (If you prefer +guaranteed commercial support, you can forego \TL{} completely and +purchase a vendor's system; \url{http://tug.org/interest.html#vendors} +has a list.) + +Here is a list of resources, approximately in the order we recommend +using them: + +\begin{description} +\item [Getting Started] If you are new to \TeX, the web page +\url{http://tug.org/begin.html} gives a brief introduction to the system. + +\item [\TeX{} \acro{FAQ}] The \TeX{} \acro{FAQ} is a huge compendium of +answers to all sorts of questions, from the most basic to the most +arcane. It is included on \TL{} in \OnCD{texmf-doc/doc/english/FAQ-en}, and is +available on the Internet through \url{http://www.tex.ac.uk/faq}. +Please check here first. + +\item [\TeX{} Catalogue] If you are looking for a specific package, +font, program, etc., the \TeX{} Catalogue is the place to look. It is a +huge list of all \TeX{}-related items. See +\OnCD{texmf-doc/doc/english/catalogue}, or +\url{http://www.ctan.org/tex-archive/help/Catalogue}. + +\item [\TeX{} Web Resources] The web page +\url{http://tug.org/interest.html} has many \TeX{}-related links, in +particular for numerous books, manuals, and articles on all aspects of +the system. + +\item [support archives] The two principal support forums are the +Usenet newsgroup \url{news:comp.text.tex} and the mailing list +\email{texhax@tug.org}. Their archives have years of past +questions and answers for your searching pleasure, via +\url{http://groups.google.com/groups?group=comp.text.tex} and +\url{http://tug.org/mail-archives/texhax}, respectively. And a general web +search, for example on \url{http://google.com}, never hurts. + +\item [asking questions] If you cannot find an answer, you can post to +\dirname{comp.text.tex} through Google or your newsreader, or to +\email{texhax@tug.org} through email. But before you post, +\emph{please} read this \acro{FAQ} entry for advice on asking questions +in such a way that you're most likely to get an answer: +\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. + +\item [\TL{} support] If you want to report a bug or have +suggestions or comments on the \TL{} distribution, installation, or +documentation, the mailing list is \email{tex-live@tug.org}. However, +if your question is about how to use a particular program included in +\TL{}, you are better off writing to that program's maintainer or +mailing list. + +\end{description} + +The other side of the coin is helping others who have questions. Both +\dirname{comp.text.tex} and \code{texhax} are open to anyone, so feel +free to join, start reading, and help out where you can. Welcome to +\TeX{}! + + +% don't use \TL so the \uppercase in the headline works. Also so +% tex4ht ends up with the right TeX. Likewise the \protect's. +\section{Structure of \protect\TeX\protect\ Live} +\label{sec:struct-tl} + +This section describes the structure and contents of \TL{} and the +\TK{} of which it is a part. + +\subsection{Multiple distributions: \protect\pkgname{live}, + \protect\pkgname{inst}, + \protect\pkgname{protext}} +\label{sec:multiple-dist} + +Space limitations of \acro{CD-ROM} format have forced us to divide +\TK{} into several distributions, as follows. + +\begin{description} + +\item [live] A complete system on \acro{DVD}; it is too large +for \acro{CD}. It can be run live or installed to disk. It also +includes a snapshot of the \CTAN{} repository, entirely independent of +\TL{}, as well as assorted other packages in a +\texttt{texmf-extra} directory. + +Unfortunately, this release of \TL{} does not include a Windows +installer, due to technical difficulties. (We hope there will be an +installer again in a few months.) Therefore, when the \DVD{} is mounted +on Windows, the setup program offers to start the \pkgname{protext} +installation (see below), and also mentions \CTAN{} and \TL{}, which are +in subdirectories of the top level of the \DVD{}. + +\CTAN{} and \texttt{texmf-extra} do not follow the same copying +conditions as \TL{}, so be careful when redistributing or +modifying. + +\item [inst(allable)] A complete system on \CD; in order to make this fit, +the packages and programs are compressed. Therefore, it is not possible +to run \TeX\ directly from the installable \CD, you have to install it +to disk (hence its name). Furthermore, it can only be installed on Unix +(including Linux, \MacOSX, etc.)\ systems, not Windows, although a set +of experimental Windows binaries is included (for sharing across +platforms). Installation is described in subsequent sections. + +\item [protext] An enhancement of the \MIKTEX\ system, for Windows. +\ProTeXt\ adds a few extra tools to \MIKTEX, and simplifies +installation. It is entirely independent of \TL{}, and has its own +installation instructions. It can be run live, or installed to disk. +The \ProTeXt\ home page is \url{http://tug.org/protext}. + +\ProTeXt\ is provided as both the top level of the \pkgname{live} \DVD\ +and on its own \CD\ (for those who cannot use the \DVD). + +\end{description} + +\noindent You can tell which type of distribution you're in by looking +for a \texttt{00\var{type}.TL} file at the top of the \TL{} directory. +This file also contains the \TL{} release date. + +Naturally, each user group chooses what to distribute, at its own +discretion. (\acro{TUG} is sending all three discs above to all of its +members.) + + +\subsection{Top level directories} +\label{sec:tld} + +Here is a brief listing and description of the top level directories in +the \TL{} distribution. This has changed considerably in 2004: the +single \texttt{texmf} tree has been split into several smaller trees. + +Also, on the \pkgname{live} \DVD, the entire \TL{} hierarchy is in a +subdirectory \dirname{texlive2004}, not at the top level of the disc. + +\smallskip +\begingroup + \renewcommand{\arraystretch}{1.3} % open up interrow spacing +\begin{tabular}{>{\ttfamily}lp{.78\hsize}} +bin & The \TeX{} system programs, arranged by platform. \\ +MacOSX & Supporting software for \MacOSX (see + section~\ref{sec:mac-install}, \p.\pageref{sec:mac-install}). \\ +source & The source of all programs, including the main \Webc{} + \TeX{} and \MF{} distributions. These are stored in a + \cmdname{bzip2}-compressed tar archive. \\ +support & Assorted auxiliary packages and programs. These are + \emph{not} installed automatically. This includes + assorted editors and \TeX\ shells. \\ +texmf & Tree for the programs, along with their support files and + documentation. Does not include \TeX\ formats and packages. \\ +texmf-dist & The main tree of formats and packages. \\ +texmf-doc & Tree for self-contained pure documentation, with no other + installed files.\hfil\break Arranged by language. \\ +texmf-var & Tree for files automatically generated and stored. \\ +xemtex & The \cmdname{XEmacs} editor and other support programs for + Windows. + These programs generally come pre-installed on Unix systems, or are + at least easy to compile. \\ +\end{tabular} +\endgroup + +\smallskip + +In addition to the directories above, the installation scripts and +\filename{README} files (in various languages) are at the top level of +the distribution. + +The (new) \dirname{texmf-doc} directory contains only documentation, but +it does not contain all the documentation. The documentation for the +programs (manuals, man pages, Info files) is in \dirname{texmf/doc}, +since the programs are in \dirname{texmf}. Similarly, the documentation +for \TeX\ packages and formats is in \dirname{texmf-dist/doc}. You can +use the \cmdname{texdoc} or \cmdname{texdoctk} programs to find any +documentation wherever it's located. The comprehensive links in the +top-level file \OnCD{doc.html} may also be helpful. + + +\subsection{Extensions to \protect\TeX} +\label{sec:tex-extensions} + +\TL{} contains several extended versions of \TeX: + +\begin{description} + +\item [\eTeX] adds a small but powerful set of new primitives +\label{text:etex} (related to macro expansion, character scanning, +classes of marks, additional debugging features, and more) and the +\TeXXeT{} extensions for bidirectional typesetting. In default mode, +\eTeX{} is 100\% compatible with ordinary \TeX. See +\OnCD{texmf-dist/doc/etex/base/etex_man.pdf}. + +\item [pdf\TeX] writes Acrobat \acro{PDF} format as well as \dvi{}. The +\LaTeX{} \pkgname{hyperref} package has an option `\optname{pdftex}' +which turns on all the program features. See +\OnCD{texmf/doc/pdftex/manual/pdftex-a.pdf} (A4 paper) or +\OnCD{texmf/doc/pdftex/manual/pdftex-l.pdf} (letter paper), and +\OnCD{texmf/doc/pdftex/examples/example.tex}. + +\item [pdfe\TeX] combines the pdf\TeX\ and \eTeX\ extensions. This is +the default program for all formats except plain \TeX. +See above for documentation. + +\item [\OMEGA\ (Omega)] is based on Unicode (16-bit characters), thus +supports working with almost all the world's scripts simultaneously. It +also supports so-called `\OMEGA{} Translation Processes' (\acro{OTP}s), +for performing complex transformations on arbitrary input. See +\OnCD{texmf-dist/doc/omega/base/doc-1.8.tex} (not completely up-to-date). + +\item [Aleph] combines the \OMEGA\ and \eTeX\ extensions. +See \OnCD{texmf-dist/doc/aleph/base} for some minimal documentation. + +\end{description} + + +\subsection{Other notable programs in \protect\TL} + +Here are a few other commonly-used programs included in \TL{}: + +\begin{cmddescription} + +\item [bibtex] bibliography support. + +\item [makeindex] index support. + +\item [dvips] convert \dvi{} to \PS{}. + +\item [xdvi] \dvi{} previewer for the X Window System. + +\item [dvilj] \dvi{} drive for the HP LaserJet family. + +\item [dv2dt, dt2dv] convert \dvi{} to/from plain text. + +\item [dviconcat, dviselect] cut and paste pages +from \dvi{} files. + +\item [dvipdfm] convert \dvi{} to \acro{PDF}, an alternative approach +to pdf\TeX\ (mentioned above). See the \pkgname{ps4pdf} and +\pkgname{pdftricks} packages for still more alternatives. + +\item [psselect, psnup, \ldots] \PS{} +utilities. + +\item [lacheck] \LaTeX{} syntax checker. + +\item [texexec] Con\TeX{}t and \acro{PDF} processor. + +\item [tex4ht] \TeX{} to \acro{HTML} converter. + +\end{cmddescription} + + +\section{Unix installation} +\label{sec:unix-install} + +As introduced in section~\ref{sec:basic} (\p.\pageref{sec:basic}), +\TL{} has three principal uses: + +\begin{enumerate} +\item Run directly from media. +\item Install to disk. +\item Integrate a particular package or collection into your existing +\TeX{} installation. +\end{enumerate} + +\noindent The following sections describes the Unix-specific procedures +for each of these. + +\ifSingleColumn \begin{figure}[ht]\noindent \fi +\begin{warningbox} +\textbf{Warning: } The \TK{} \CD{}s and \DVD{} are in ISO 9660 (High Sierra) +format, \emph{with} Rock Ridge (and Joliet, for Windows) +extensions. Therefore, in order to take full advantage of the \TK{} +under Unix, your system needs to be able to use the Rock Ridge +extensions. Please consult the documentation for your \cmdname{mount} +command to see how to do this. If you have several different machines +on a local network, you may be able to mount the \CD{}s on one which +does support Rock Ridge, and use this with the others. + +\leavevmode\quad Linux, \acro{BSD}, Sun, and \acro{SGI} +systems should be able to use the \CD{}s without problems. We +would appreciate receiving detailed advice from users on other systems +who succeed, for future versions of this documentation. + +\leavevmode\quad +The discussion below assumes you have been able to mount +the \CD{}s with full Rock Ridge compatibility. +\end{warningbox} +\ifSingleColumn\end{figure}\fi + + +% +\subsection{Running \protect\TL{} directly from media (Unix)} + +\def\runlive{% text repeated in windows section +It is possible to use the \TeX{} system directly from the \pkgname{live} +\DVD{}, without installing the distribution to disk. (Thus the name +\TeX\ `Live', in fact.) It is \emph{not} possible to run \TeX{} +directly from the other \CD s (see section~\ref{sec:multiple-dist}, +\p.\pageref{sec:multiple-dist}). +} + +\def\startinst{% repeated in other subsections +To start, you mount the \CD{} or \DVD{}, with Rock Ridge extensions +enabled. The exact command to do this varies from system to system; the +following works under Linux, except the name of the device +(\filename{/dev/cdrom}, here) may vary. (All our examples will use +\texttt{>} as the shell prompt; user input is +\Ucom{\texttt{underlined}}.) +\begin{alltt} +> \Ucom{mount -t iso9660 /dev/cdrom /mnt/cdrom} +\end{alltt} + +\noindent Change the current directory to the mount point: +\begin{alltt} +> \Ucom{cd /mnt/cdrom} +\end{alltt} + +\noindent Under \MacOSX, the directory is typically under +\dirname{/Volumes}, and the media will be mounted automatically. + +Run the installation script \filename{install-tl.sh}: +\begin{alltt} +> \Ucom{sh install-tl.sh}\\ +Welcome to TeX Live... +\end{alltt} + +\noindent After various greeting messages and a list of the main menu +options, the installation will ask you to enter a command. Do this by +typing the desired character and hitting return; don't type the angle +brackets. Either uppercase or lowercase is ok; we'll use lowercase in +our examples. +} + +\runlive +\startinst + +For running live, our first command will be \Ucom{d} and then the +subcommand \Ucom{1} to set directories. Even in this case, we must +choose a directory on the local disk to place files that the \TeX{} +system itself generates, such as fonts and formats, and also to provide +a place for updated configuration files, if need be. We'll use +\dirname{/usr/local/texmf-local} in this example. (If the default value +of \dirname{/usr/TeX} works for you, then you can skip this step.) +\begin{alltt} +Enter command: \Ucom{d} +Current directories setup: +<1> TEXDIR: /usr/TeX +... +Enter command: \Ucom{1} +New value for TEXDIR [/usr/TeX]: \Ucom{/usr/local/texmf-local} +... +Enter command: \Ucom{r} +\end{alltt} + +\noindent Back at the main menu, our second and last command is +\Ucom{r}, to set up for running live off the media without installing +to disk: +\begin{alltt} +Enter command: \Ucom{r} +Preparing destination directories... +... +Welcome to TeX Live! +> +\end{alltt} + +\noindent And we are back at the system prompt, as shown. + +Next, it is necessary to alter two environment variables: +\envname{PATH}, to an architecture-dependent value (so that we can run +the programs), and \envname{VARTEXMF}, to the value specified above. See +table~\ref{tab:archlist} for a list of the architecture names for the +different systems. + + +\def\textruntexconfig{% +After the main installation has completed, and environment variables +have been set, the last step is to run \cmdname{texconfig} to customize +your installation for your needs. This is explained in +section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig}. +} +\textruntexconfig + +\begin{table*}[ht] +\caption[Supported system architectures.]{Supported system +architectures. In addition to the version-specific names listed here, +there are generic names without the version numbers. For instance, +\texttt{sparc-solaris} links to \texttt{sparc-solaris2.7}. The generic +names can be used to protect against the version numbers changing in the +future, if you wish.} +\label{tab:archlist} +\begin{tabular}{>{\ttfamily}ll} +alpha-linux & HP Alpha GNU/Linux \\ +%alphaev5-osf4.0d & HP Alphaev5 OSF \\ +%hppa2.0-hpux10.20 & HP9000 HPUX 10.20 \\ +i386-freebsd4.10 & Intel x86 FreeBSD \\ +i386-linux & Intel x86 GNU/Linux \\ +%i386-openbsd3.3 & Intel x86 OpenBSD \\ +%i386-solaris2.8 & Intel x86 Solaris \\ +mips-irix6.5 & SGI IRIX \\ +powerpc-aix4.3.3.0 & IBM RS/6000 AIX \\ +powerpc-darwin6.8 & \MacOSX \\ +sparc-solaris2.7 & Sun Sparc Solaris \\ +sparc64-linux & Sun Sparc GNU/Linux \\ +win32 & Windows (32-bit) \\ +x86\_64-linux & Intel/AMD 64-bit GNU/Linux \\ +\hline +\end{tabular} +\end{table*} + +\label{text:path} +The syntax for setting the environment variables, and the initialization +file to put them in, depends on the shell you use. If you use a +Bourne-compatible shell (\cmdname{sh}, \cmdname{bash}, \cmdname{ksh}, et +al.), put the following into your \filename{$HOME/.profile} file: +\begin{alltt} +PATH=/mnt/cdrom/bin/\var{archname}:$PATH; export PATH +VARTEXMF=/usr/local/texmf-local/texmf-var; export VARTEXMF +\end{alltt} + +\noindent For C shell-compatible shells (\cmdname{csh}, \cmdname{tcsh}), +put the following into your \filename{$HOME/.cshrc} file: +\begin{alltt} +setenv PATH /mnt/cdrom/bin/\var{archname}:$PATH +setenv VARTEXMF /usr/local/texmf-local/texmf-var +\end{alltt} + +\noindent Then log out, log back in, and test your installation +(see section~\ref{sec:test-install}, \p.\pageref{sec:test-install}). + +\def\textifindoubt{% +If in doubt, please ask any local system gurus to help you with +problems; for example, the way to mount the \TL{} media, which +directory or directories to use, and precise details of the changes to +your personal initialization files can and do vary from site to site. +} +\textifindoubt + + +% +\subsection{Installing \protect\TeX\protect\ Live to disk} +\label{sec:unix-install-disk} + +It is possible, indeed typical, to install the \TeX{} system from the +\TL{} to disk. This can be done either from any of the \TK{} discs. +(See section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}, +for an explanation of the different distributions.) + +\startinst + +Table~\ref{tab:main-menu-options} briefly lists the options in the main +menu. The order in which you select the options makes little +difference, except that \Ucom{i} must be last. It's reasonable to go +through them in the order presented here. + +% apparently here.sty [H] doesn't support table*. +\begin{table}[H] +\caption{Main menu options for the installation.} +\label{tab:main-menu-options} +\begin{tabular}{>{\ttfamily}ll} +p & The platform you are running on.\\ +b & The architectures for which to install binaries.\\ +s & The base installation scheme to use (minimal, recommended, + full, etc.)\\ +c & Override the base scheme for individual collections.\\ +l & Override for language collections.\\ +d & Directories in which to install.\\ +o & Other options.\\ +i & Perform the installation.\\ +\end{tabular} +\end{table} + +Here are further details on each option. + +\textbf{\optname{p} -- Current platform.} Since the installation script +automatically guesses which platform you're running on, it is generally +unnecessary to use this option. It's there in case you need to override +the automatic detection. + +\textbf{\optname{b} -- Binary architectures.} By default, only the +binaries for your current platform will be installed. From this menu, +you can select installation of binaries for other architectures as well +(or not install the current platforms). This can be useful if you are +sharing a \TeX\ tree across a network of heterogenous machines. For a +list of the supported architectures, see table~\ref{tab:archlist}, +\p.\pageref{tab:archlist}. + +\textbf{\optname{s} -- Base installation scheme.} From this menu, you +can choose an overall common set of packages, called a ``scheme''. The +default \optname{recommended} scheme suffices for typical needs, but you +can also choose the \optname{basic} scheme if you are low on disk space, +or \optname{full} to get absolutely everything. There are also specific +sets for Omega and \acro{XML}. + +\textbf{\optname{c} -- Individual collections.} From this menu, you can +override the base scheme's set of collections to install. Collections +are one level lower than schemes\Dash collections consist of +one or more packages, where packages (the lowest level grouping in \TL) +contain the actual \TeX\ macro files, font families, and so on. +In this menu, selection letters are case-sensitive. + +\textbf{\optname{l} -- Language collections}. This menu has the same +basic purpose as \Ucom{c}, to override the base scheme. In this case, +the collections are specifically for different languages. Selection +letters are case-sensitive here. Here is a list of the language +collections in \TL: + +% xx really should generate list from texmf/tpm/collection/tex-lang* +% a la install-tl.sh. +\begin{tabbing} +\hspace{.25\linewidth} \= +\hspace{.25\linewidth} \= +\hspace{.25\linewidth} \= +\hspace{.25\linewidth} \kill +(some) African scripts \> +Arabic \> +Armenian \> +Chinese\,Japanese\,Korean \\ +Croatian \> +Cyrillic \> +Czech/Slovak \> +Danish \\ +Dutch \> +Finnish \> +French \> +German \\ +Greek \> +Hungarian \> +Indic \> +Italian \\ +Latin \> +Manju \> +Mongolian \> +Norwegian \\ +Polish \> +Portuguese \> +Spanish \> +Swedish \\ +Tibetan \> +\acro{UK} English \> +Vietnamese \\ +\end{tabbing} + +\noindent Language collections typically include fonts, macros, +hyphenation patterns, and other support files. (For instance, +\pkgname{frenchle.sty} is installed if you select the \optname{French} +collection.) In addition, installing a language collection will alter +the \filename{language.dat} configuration file controlling which +hyphenation patterns are loaded. + +\textbf{\optname{d} -- Installation directories}. Three directories can +be changed here: +\label{text:instdir} + +\begin{ttdescription} +\item [TEXDIR] The top-level directory under which +everything else will be installed. The default value is +\dirname{/usr/TeX}, and is often changed. For example, changing to a +value such as \dirname{/usr/local/texlive2003} would make it possible to +keep different releases of \TL{} separate. (You may then wish to make +\dirname{/usr/local/texlive} a symbolic link, after testing the new +release.) + +Under \MacOSX, the usual frontends look for \TeX{} in +\dirname{/usr/local/teTeX}, so you may wish to install \TL{} there. + +\item [TEXMFLOCAL] This tree is where the \TeX{} system (not as part of +installation, but rather over time) puts non-version-specific files, +primarily fonts. The default value is \dirname{TEXDIR/texmf-local}. +However, it's also the recommended location to put any local packages or +configuration settings. Therefore, it's desirable to change it to a +location independent of the current \TL{} release; for example, +\dirname{/usr/local/texmf-local}. + +\item [VARTEXMF] This tree is where the system puts files that +\emph{are} version-specific, primarily format files and the +configuration files which are modified by \cmdname{texconfig} (see +section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig}). The default +value is \dirname{TEXDIR/texmf-var}, and there's generally no reason to +change it. + +\end{ttdescription} + +\textbf{\optname{o} -- Other options.} From this menu, you can select +the following general options: + +\begin{ttdescription} +\item [a] Specify an alternate directory for generated fonts. +The default is to use the \envname{VARTEXMF} tree, as explained above. +Setting this is useful if you plan to mount the main tree read-only, and +therefore you need another location (perhaps host-specific) for +dynamically created fonts. + +\item [l] Create symbolic links for the binaries, man pages, +and\slash or \acro{GNU} Info files in other locations. For example, you may +wish to make the man pages available under \dirname{/usr/local/man} and +the Info files available under \dirname{/usr/local/info}. (Of course +you need appropriate privileges to write in the specified directories.) + +It is not advisable to overwrite a \TeX\ system that came with your +system with this option. It's intended more for having the links in +standard directories known to users, such as \dirname{/usr/local/bin}, +which don't already contain any \TeX\ files. + +\item [d] Skip installation of the font/macro documentation tree. +This is useful if you need to save space, or if you've previously +installed the documentation elsewhere. + +\item [s] Skip installation of the main font/macro source +tree. This is useful if you are arranging to share that tree between +machines and\slash or architectures in some other way, such as \acro{NFS}. + +\end{ttdescription} + +\textbf{i -- Perform installation.} When you're satisfied with your +configuration options, enter \Ucom{i} to actually do the installation +from the media to your chosen locations. + +% text is similar to above, but no VARTEXMF, so we have to write out. +After the installation completes, your next step is to include the +architecture-specific subdirectory of \dirname{TEXDIR/bin} in your +\envname{PATH}, so the newly-installed programs can be found. The +architecture names are listed in table~\ref{tab:archlist}, +\p.\pageref{tab:archlist}, or you can simply list the directory +\dirname{TEXDIR/bin}. + +The syntax for doing this, and the initialization file to use, depends +on your shell. If you use a Bourne-compatible shell (\cmdname{sh}, +\cmdname{bash}, \cmdname{ksh}, et al.), put the following into your +\filename{$HOME/.profile} file: + +\begin{alltt} +PATH=/mnt/cdrom/bin/\var{archname}:$PATH; export PATH +\end{alltt} + +\noindent For C shell-compatible shells (\cmdname{csh}, \cmdname{tcsh}), +put the following into your \filename{$HOME/.cshrc} file: +\begin{alltt} +setenv PATH /mnt/cdrom/bin/\var{archname}:$PATH +\end{alltt} + +\textruntexconfig + +Here is a brief annotated example which selects a full installation, +with binaries for the current system only, with directory changes as +recommended above. The prompts and \acro{RETURN}s are omitted for +brevity. + +\begin{alltt} +> \Ucom{sh install-tl.sh} +\Ucom{s} \Ucom{b} \Ucom{r} # scheme, full, return to main +\Ucom{d} # change directories +\Ucom{1} \Ucom{/usr/local/texlive2003} # top-level dir +\Ucom{2} \Ucom{/usr/local/texmf-local} # TEXMFLOCAL outside TEXDIR +\Ucom{r} # return to main +\Ucom{i} # perform installation +> \Ucom{texconfig} ... +# New PATH, with Linux as the example: +> \Ucom{PATH=/usr/local/texlive2003/bin/i386-linux:$PATH; export PATH} +\end{alltt} + +\textifindoubt + + +% +\subsection{Installing individual packages to disk} + +You can add individual packages or collections from the current +distribution to an existing non-\TL{} setup, or an earlier +\TL{} installation. + +\startinst + +Run the installation script \filename{install-pkg.sh} (not +\filename{install-tl.sh}, which is intended for complete installations +only): +\begin{alltt} +> \Ucom{sh install-pkg.sh \var{options}} +\end{alltt} + +The first set of options controls what gets read: + +\begin{ttdescription} +\item [-{}-package=\var{pkgname}] The individual package to work on. + +\item [-{}-collection=\var{colname}] The individual collection to work on. + +\item [-{}-nodoc] Exclude documentation files from the operation. + +\item [-{}-nosrc] Exclude source files from the operation. + +\item [-{}-cddir=\var{dir}] Source directory to read from; defaults +to the current directory. If you followed the instructions above, that +will be the distribution directory, and won't need to be changed. + +\item [-{}-listdir=\var{dir}] The so-called `lists' directory within +\var{cddir} from which to read the package information. The only +reason to change the default is if you're making changes to \TL{} +yourself. + +\end{ttdescription} + +What actually happens is controlled by the following options. If +neither of these are specified, the default action is to install the +selected files. The main destination tree is found by expanding +\envname{\$TEXMFMAIN} with \cmdname{kpsewhich}. You can override it by +setting either the environment variable \envname{TEXMFMAIN} or +\envname{TEXMF}. + +\begin{ttdescription} +\item [-{}-listonly] List the files that would be installed, but don't +actually install anything. + +\item [-{}-archive=\var{tarfile}] Instead of installing the files into +the \TeX{} system, make a \cmdname{tar} archive. + +\end{ttdescription} + +Additional options: + +\begin{ttdescription} + +\item [-{}-config] After installation, run \code{texconfig init}. + +\item [-{}-nohash] After installation, don't run \cmdname{mktexlsr} to +rebuild the filename database. + +\item [-{}-verbose] Give more information as the script runs. + +\end{ttdescription} + +Here are some usage examples: + +\begin{enumerate} + +\item To see the files in the package \pkgname{fancyhdr} without +installing it: + +\begin{alltt} +\ifSingleColumn> \Ucom{sh install-pkg.sh --package=fancyhdr --listonly} +\else> \Ucom{sh install-pkg.sh --package=fancyhdr \bs} +> \Ucom{--listonly} +\fi{} +texmf/doc/latex/fancyhdr/README +texmf/doc/latex/fancyhdr/fancyhdr.dvi +texmf/doc/latex/fancyhdr/fancyhdr.pdf +... +\end{alltt} + +\item Install the \LaTeX{} package \pkgname{natbib}: +\begin{alltt} +> \Ucom{sh install-pkg.sh --package=natbib} +\end{alltt} + +\item Install the \LaTeX{} package \pkgname{alg} without source files or +documentation: +\begin{alltt} +\ifSingleColumn> \Ucom{sh install-pkg.sh --package=alg --nosrc --nodoc} +\else> \Ucom{sh install-pkg.sh -{}-package=alg \bs} +> \Ucom{-{}-nosrc -{}-nodoc} +\fi\end{alltt} + +\item Install all the packages in the collection of additional +plain \TeX\ macros: +\begin{alltt} +> \Ucom{sh install-pkg.sh --collection=tex-plainextra} +\end{alltt} + +\item Write all files in the \pkgname{pstricks} package to a +\cmdname{tar} file in \path|/tmp|: +\begin{alltt} +\ifSingleColumn> \Ucom{sh install-pkg.sh --package=pstricks --archive=/tmp/pstricks.tar} +\else +> \Ucom{sh install-pkg.sh -{}-package=pstricks \bs} +> \Ucom{-{}-archive=/tmp/pstricks.tar} +\fi\end{alltt} + +\end{enumerate} + +\textifindoubt + + +% +\section{Post-installation} +\label{sec:postinstall} + +After the main installation is done, for any operating system, the +remaining steps are to configure the system for your local needs, and +perform some basic tests. + +Another sort of post-installation is to acquire packages, fonts, or +programs that were not included in \TL{}. The basic idea is to +install such additions in the \envname{TEXMFLOCAL} tree (if you +installed to disk), or \envname{VARTEXMF} (if you are running live). +See the ``Installation directories'' option on \p.\pageref{text:instdir}. + +Unfortunately, the details can and do vary widely, and so we do not attempt to +address them here. Here are some external links to descriptions: +\begin{itemize*} +\item +\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instpackages} +\item +\url{http://www.ctan.org/installationadvice} +\item +\url{http://www.ctan.org/tex-archive/info/beginlatex/html/chapter5.html#pkginst} +\item +\url{http://www.ctan.org/tex-archive/info/Type1fonts} for font creation +and installation information in particular. +\end{itemize*} + + +\subsection{The \protect\cmdname{texconfig} program} +\label{sec:texconfig} + +At any time after installation, you can and should use the program +\cmdname{texconfig} to configure the system to fit your local needs. It +is installed in the architecture-specific subdirectory +\texttt{TEXDIR/bin/\var{arch}} along with everything else. + +If you run it without arguments, it will enter full-screen mode and +allow you to view and change options interactively. + +You can also run it with various command-line options. Here are some of +the most common (a \TL{} installation is configured for the A4 paper +size by default): + +\begin{ttdescription} + +\item [texconfig paper letter] Set default paper size for +various programs and drivers (\cmdname{pdftex}, \cmdname{dvips}, +\cmdname{dvipdfm}, \cmdname{xdvi}) to be \acro{US} letter. The other +allowable size is \optname{a4}, which is the default. + +\item [texconfig localsetup] Verify that paths are set ok. + +\item [texconfig rehash] Update all the \TeX{} system filename databases. + +\item [texconfig faq] Show the \teTeX{} \acro{FAQ}. +(See also the main \TeX{} \acro{FAQ} in \OnCD{texmf-doc/doc/english/FAQ-en}.) + +\item [texconfig help] Output help information for \cmdname{texconfig}. + +\end{ttdescription} + +Of course, \cmdname{texconfig} can only support changing a few of the +many options and configuration parameters in a \TeX{} system. The main +configuration file for the base \Webc{} programs is named +\filename{texmf.cnf}. You can find its location by running +\samp{kpsewhich texmf.cnf}; it contains many comments explaining the +default settings and useful alternatives. + + +\subsection{Testing the installation} +\label{sec:test-install} + +After installing \TL{} as best you can, you naturally want to test +it out, so you can start creating beautiful documents and\slash or fonts. + +This section gives some basic procedures for testing that the new system +is functional. We give Unix commands; under \MacOSX{} and Windows, +you're more likely to run the tests through a graphical interface, but +the principles are the same. + +\begin{enumerate} + +\item Make sure that you can run the \cmdname{tex} program in the first +place: + +\begin{alltt} +> \Ucom{tex -{}-version} +TeX 3.141592 (Web2C 7.5.3) +kpathsea version 3.5.3 +Copyright (C) 1997-2004 D.E. Knuth. +... +\end{alltt} +If this comes back with `command not found' instead of version and +copyright information, most likely you don't have the correct +\dirname{bin} subdirectory in your \envname{PATH}. See +the environment-setting information on \p.\pageref{text:path}. + +\item Process a basic \LaTeX{} file: +\begin{alltt} +> \Ucom{latex sample2e.tex} +This is pdfeTeXk, Version 3.141592... +... +Output written on sample2e.dvi (3 pages, 7496 bytes). +Transcript written on sample2e.log. +\end{alltt} +If this fails to find \filename{sample2e.tex} or other files, perhaps +you have interference from old environment variables or configuration +files. For a deep analysis, you can always ask \TeX{} to report on +exactly what it is searching for, and finding; see ``Debugging actions'' +on page~\pageref{Debugging}. + +\item Preview the result online: +\begin{alltt} +> \Ucom{xdvi sample2e.dvi} +\end{alltt} +(Under Windows, the analogous command is \cmdname{windvi}.) You should +see a new window with a nice document explaining some of the basics of +\LaTeX{}. (Well worth reading, by the way if you're new to the system.) +You do have to be running under X for \cmdname{xdvi} to work; if you're +not, or your \envname{DISPLAY} environment variable is set incorrectly, +you'll get an error \samp{Can't open display}. + +\item Create a \PS{} file for printing or display: +\begin{alltt} +> \Ucom{dvips sample2e.dvi -o sample2e.ps} +\end{alltt} + +\item Create a \acro{PDF} file instead of \dvi{}; this processes the +\filename{.tex} file and writes \acro{PDF} directly: +\begin{alltt} +> \Ucom{pdflatex sample2e.tex} +\end{alltt} + +\item Preview the \acro{PDF} file: +\begin{alltt} +> \Ucom{gv sample2e.pdf} +\textrm{or:} +> \Ucom{xpdf sample2e.pdf} +\end{alltt} +Unfortunately neither \cmdname{gv} nor \cmdname{xpdf} are currently +included in \TL{}, so you must install them separately. See +\url{http://wwwthep.physik.uni-mainz.de/~plass/gv} and +\url{http://www.foolabs.com/xpdf}, respectively. + +\item Other standard test files you may find useful: + +\begin{ttdescription} +\item [small2e.tex] A simpler document than \filename{sample2e}, to +reduce the input size if you're having troubles. +\item [testpage.tex] Test if your printer introduces any offsets. +\item [nfssfont.tex] For printing font tables and tests. +\item [testfont.tex] Also for font tables, but using plain \TeX{}. +\item [story.tex] The most canonical (plain) \TeX{} test file of all. +You must type \samp{\bs bye} to the \code{*} prompt after \samp{tex +story.tex}. +\end{ttdescription} +You can process these in the same way as we did with +\filename{sample2e.tex}. + +\end{enumerate} + +If you are new to \TeX{}, or otherwise need help with actually +constructing \TeX{} or \LaTeX{} documents, please visit +\url{http://tug.org/begin.html}. We especially recommend the +\textsl{Formatting Information} manual by Peter Flynn, available at +\url{http://www.ctan.org/tex-archive/documentation/beginlatex}. + + +\section{\MacOSX{} installation} +\label{sec:mac-install} + +\TL{} supports \MacOSX, but no prior Macintosh versions. (If you +are running an older Mac version, you can view the files by installing +the Joliet system extension available from +\url{http://www.tempel.org/joliet}; however, the \TL{} binaries +will not run.) + +Installation of \TeX{} under \MacOSX{} can be done in two ways: + +\begin{enumerate} +\item With the \filename{install*} scripts, as with Unix. +\item With the \cmdname{i-Installer} included in +\filename{MacOSX/II2.dmg}. +\end{enumerate} + +\noindent Each of these is described in a following section. + +In addition, \TeX{} under \MacOSX\ typically uses a ``frontend''. This +is also described below. + + +\subsection{\protect\cmdname{i-Installer}: Internet installation} +\label{sec:i-Installer} + +The \cmdname{i-Installer} is included in the \TL{} distribution as +an alternative to normal installation. It does not use the contents of +the \TL{} distribution at all; instead, the system (approximately +70 megabytes) is downloaded over the Internet. + +One advantage of \cmdname{i-Installer} is that it makes updates +relatively painless. If you are interested, please see the +\cmdname{i-Installer} \TeX{} home page at \url{http://www.rna.nl/tex.html}. + +To use it, mount \filename{./MacOSX/II2.dmg}. Read the documentation, +launch it, and install at least \texttt{TeX Foundation} and \texttt{TeX +Programs}. The first will finish without configuration, as soon as the +second is installed you will be presented with a graphical interface to +setting up your \TeX{} system. + +The \cmdname{i-Installer} distribution uses the \teTeX{} \dirname{texmf} +tree with some additions. Due to differences between \TL{} and +\teTeX{} you cannot update a \TL{} installation with an +\cmdname{i-Installer} \texttt{TeX Programs} i-Package. + + +\subsection{\protect\cmdname{install*.sh}: \protect\TL{} installation} + +In order to run the installation scripts under \MacOSX, you need to have +the \cmdname{bash} shell installed. If you are running \MacOSX~10.2 +or later, you have \cmdname{bash}, and can proceed. If you're running +an earlier \MacOSX{} version, however, the default shell is +\cmdname{zsh}, which won't work; you'll need to get \cmdname{bash} from +the Internet, or more likely upgrade your system. + +Once you have \cmdname{bash}, the Unix installation documentation in the +previous section can be followed. See section~\ref{sec:unix-install} on +\p.\pageref{sec:unix-install}; \MacOSX-specific notes are included there +where needed. + + +\subsection{\MacOSX{} frontends} + +Using \TeX{} on a Macintosh typically goes through a front end program, +comprising an execution shell, editor, previewer, and other facilities, +with a graphical interface. Here are the principal frontends: + +\begin{cmddescription} +\item [TeXShop] Included in \TL{} as \filename{./MacOSX/texshop.dmg}. + \\See \url{http://www.uoregon.edu/~koch/texshop/texshop.html}. + +\item [ITeXMac] Included in \TL{} as \filename{./MacOSX/iTM-*.dmg}. + \\See \url{http://itexmac.sourceforge.net}. + +\item [Mac-emacs] A port of Emacs to \MacOSX{}, integrating \pkgname{AucTeX}. + \\See \url{http://www.cs.man.ac.uk/~franconi/mac-emacs}. + +\end{cmddescription} + +The frontends use \dirname{/usr/local/teTeX} as the default location; +therefore, you must either install \TL{} there, or change the +configuration of the frontend. + + +\section{Windows installation} +\label{sec:win-install} + +Unfortunately, this release of \TL{} does not include a Windows +installer, due to technical difficulties. We hope that an installer +will be available again in a few months. (It is being completely +rewritten to use standard Microsoft libraries, instead of the homegrown +\filename{TeXSetup.exe}.) + +A set of experimental Windows binaries is included, nevertheless. You +can install them with the Unix \filename{install-tl.sh} script: select +the \optname{win32} system from the \optname{S} option of the top-level +menu. The \pkgname{XEmacs} package is not included, however, due to +space. + +(Meanwhile, if you are an experienced Windows programmer and would like +to help with the project, email us!) + + +\begin{comment} +\TL{} can be installed on systems running Windows 9x, \acro{ME}, +\acro{NT}, \acro{2K} or \acro{XP}. Older versions of Windows (3.1x) +and \acro{MS-DOS} are not supported. + +It is necessary to have your Windows set up so that it uses the +Microsoft Joliet extensions for reading \CD{}s; simply look at the \CD{} +in Explorer and see whether it shows long, mixed-case, file names. If it +does not, you must install the Joliet extensions. + +The Windows \TeX{} system included in \TL{} is no more and no less +than the \fpTeX{} distribution. It includes a \texttt{dvi} previewer, +\textsf{Windvi}, which is similar in usage to the established Unix +\textsf{xdvi}. The documentation can be found in +\OnCD{texmf/doc/html/windvi/windvi.html}. + +\subsection{The \texttt{TeXLive.exe} program} + +\begin{figure*} + \begin{center} + \ifnum \Status=1 + \includegraphics[width=.7\textwidth]{pictures/Welcome-to-TeXLive} + \else + \ifnum \Status=2 + \includegraphics[bb=0 0 551 534]{pictures/Welcome-to-TeXLive.jpg} + \else + \includegraphics[width=.7\textwidth]{pictures/Welcome-to-TeXLive} + \fi + \fi + \end{center} + \caption{``Welcome to \TL'' window}\label{graph:welcome} +\end{figure*} + +If your computer is configured to let the \CD{} autostart, then a dialog +box with a menu bar will popup on the screen, and you will have several +choices from there: + +\begin{itemize*} +\item Install \TeX{} on your hard disk +\item Do maintenance on your \TeX{} system. +\item Remove the \TeX{} system. +\item Use \TeX{} off the \TL{} \CD{} or \DVD{}. +\item Browse documentation: \TL{} documentation, TUG web + pages, \fpTeX web pages. +\item Run the \cmdname{TeXdocTK} application to find specific documentation. +\end{itemize*} + +If your \CD{} does not autostart, you can explicitly run the program +by double clicking on \path|bin/win32/TeXLive.exe| on the \CD{} from +the explorer window. + +\subsection{Running \protect\TL{} directly from media (Windows)} + +\runlive + +To run live under Windows, from the menu, chose \verb|Explore CD-Rom|, then +\verb|Run TeX off CD-Rom|. This will launch the \cmdname{XEmacs} editor. + +XEmacs startup file will set the environment variables needed. XEmacs will also +setup a temporary \acro{TDS} compliant texmf tree in the temporary area of your +computer. It is needed to store files that may be built on the fly, such as +\path|pk| bitmap fonts, or format files. Configuration files are copied from +the \CD{} to this texmf tree, so that you can edit them if needed. The +\path|ls-R| database is computed for this texmf tree. The AUC-\TeX{} mode will +be entered Whenever you will visit or create a \TeX{} file, providing all the +bells and whistles for \TeX{} support XEmacs is capable of. + +If you run 'M-x shell' within XEmacs, then you will have access to all the TeXLive +tools from the command line provided by XEmacs. + +\smallskip {\small\noindent \textbf{[For advanced users:]} You can also + use the small batch file \path|mkloctex.bat| to be called in a + directory \path|bin\win32| of the \CD. From the Start menu select + `Run', then browse the \acro{CD} drive and select + \path|mkloctex.bat|. Before starting it, you should add two parameters + separated by a space: the letter of your \acro{CD} drive and the + letter of the drive where you want to install the \TeX\ directory. + The whole line should read, e.g., \verb+d:\bin\win32\mkloctex.bat d c+. + When installation is complete, please read carefully the information + on screen. If you are running Windows 9x/\acro{ME}, then you will have to + restart Windows.} + +\subsection{Support packages for Windows} +\label{sec:win-xemtex} + +To be complete, a \TL installation needs support packages that are not +commonly found on a Windows machine. +Many scripts are written using the Perl language. Some important tools require +the Ghostscript \PS{} interpreter to render or to convert files. A graphic +file toolbox is also needed in some cases. Last but not least, a \TeX-oriented +editor makes it easy to type in your \TeX{} files. + +All these tools are quite easy to find for Windows, but in order to try to make +your life even easier, we have put such a set of tools on \TL: +\begin{itemize*} +\item \cmdname{Ghostscript} 7.07 +\item a minimal \cmdname{Perl} 5.8, sufficient to run all the \TL{} +Perl scripts +\item a subset of \cmdname{ImageMagick} 5.5.6 +\item the \cmdname{ISpell} checker +\item \cmdname{XEmacs} 21.5.14 with a selection of packages to support +\TeX{} typesetting. +\end{itemize*} + +These packages should be installed only all at once. The bundle is +known as the \XEmTeX{} bundle. + +If you didn't install \XEmTeX{}, \cmdname{Perl} and \cmdname{Ghostscript} are +installed anyway if they are not detected on your machine. This is because they are +required by many important tools. The \envname{PERL5LIB} and \verb|GS_LIB| +environment variables will be set too. + +When you are under +\cmdname{XEmacs}, the tools provided shadow any other version you might +have installed previously. The point here is that \path|TeXSetup.exe| +will not install anything outside of the \TL location, neither will +it run foreign installers, nor will it try to autodetect installed +products using unreliable rules of thumb. The \XEmTeX{} bundle is +standalone and is meant to evolve in the future. The reference site is +\url{http://www.fptex.org/xemtex/}. + +If you don't want to install this bundle, then you are on your own to +install the required tools to complete your \TL{} system. Here is a +list of places to get those tools: + +\begin{description} +\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} +\item[Perl] \url{http://www.activestate.com/} (but you might need some + supplementary packages from CPAN: \url{http://www.cpan.org/}) +\item[ImageMagick] \url{http://www.imagemagick.com} +\item[NetPBM] alternatively, you could use NetPBM instead of ImageMagick to + process or convert your graphic files. NetPBM home page is + \url{http://netpbm.sourceforge.net/} +\item[\TeX-oriented editors] There is a wide choice, and it is a matter of the + user's taste. Here is a selection: + \begin{itemize*} + \item \cmdname{GNU Emacs} is available natively under Windows, the + reference url is + \url{http://www.gnu.org/software/emacs/windows/ntemacs.html} + \item \cmdname{XEmacs} is available natively under Windows, the + reference url is \url{http://www.xemacs.org/} + \item \cmdname{WinShell} is available on \TL in the \path|support| + directory, the reference url is \url{http://www.winshell.de} + \item \cmdname{WinEdt} is shareware available from \url{http://www.winedt.com} + \item TeXnicCenter is available from\\ + \url{http://www.toolscenter.org} + \item \cmdname{Vim} is available on \TL{} in the + \path|support\vim| directory and the + reference site is \url{http://www.vim.org} + \item \cmdname{SciTE} is available from \url{http://www.scintilla.org/SciTE.html} + \end{itemize*} +\end{description} + +You might want to install other tools that are not free\footnote{Not +free, that is, in the sense of freedom to modify and redistribute, +following free software guidelines. This does not mean you can't acquire +them for no money.} and therefore not included on \TL{}, such as +\cmdname{GSView}, the \cmdname{Ghostscript} companion to more +conveniently view PS/PDF files. \cmdname{GSView} is available from +\url{http://www.cs.wisc.edu/~ghost/gsview/} or any \acro{CTAN} site. + +\subsection{Installing \protect\TeX\protect\ Live to disk} + +\textbf{Warning: Win9x users must ensure they have enough environment + space before undertaking installation. The \cmdname{TeXSetup.exe} + program won't change the environment size for them. A few environment + variables will be created and it is possible you run out of + environment space. Add \texttt{SHELL=COMMAND.COM /E:4096 /P} in the + config.sys file in order to increase your environment size.} + +Installation is started by letting the media autostart. The program run +is \path|TeXSetup.exe| if you are using the inst disk. If you are using +the live or the demo disk, you will have to select the item +\path|TeXLive Software| from the menu, then the subitem \path|Install on +Hard Disk|. This will invoke \path|TeXSetup.exe|. You can also find it +in the \path|bin/win32| directory and run it, if the autostart fails for +any reason. \path|TeXSetup.exe| is a Windows wizard and it will display +several pages while running. + +\begin{description} +\item[Welcome Page] + You can choose a \emph{quick} installation from + here. In this case, the installation will run without any human + assistance from beginning to end, with all the default settings + (Figure~\ref{graph:setup-src}, + \ifnum \Status = 1 + on the left% + \else\ifnum \Status=2 + at the top% + \else + on the left% + \fi\fi + ). If you have enough privileges (administrator or power user + rights) under a Windows version where this is applicable, then you can + decide to install the \TL{} for all users or for yourself only by + checking the appropriate box. + For installing the whole \XEmTeX{} bundle (XEmacs, Ghost\-script, + Perl, ImageMagick and Ispell) you can check \emph{Install XEmTeX + Support} box. + \begin{figure*}[!htb] + The \cmdname{TeXSetup} Wizard\hfill + Source directories for the \TL{} files + + \begin{center} + \ifnum \Status=1 + \includegraphics[width=.48\textwidth]{pictures/setup-wizard.jpg}\hfill% + \includegraphics[width=.48\textwidth]{pictures/source-for-texlive.jpg} + \else + \ifnum \Status=2 +\includegraphics[bb=0 0 506 403]{pictures/setup-wizard.jpg} +\includegraphics[bb=0 0 506 403]{pictures/source-for-texlive.jpg} + \else + \includegraphics[width=.48\textwidth]{pictures/setup-wizard}% + \hfill% + \includegraphics[width=.48\textwidth]{pictures/source-for-texlive} + \fi + \fi + \caption{The \TL{} setup wizard}\label{graph:setup-src} + \end{center} +\end{figure*} +\item[Source Page] + This page is a bit complex. It will allow you to select two source + directories for your \TL{} system + (Figure~\ref{graph:setup-src}, + \ifnum \Status = 1 + on the right% + \else\ifnum \Status=2 + at the bottom% + \else + on the right% + \fi\fi + ). You will need a \emph{local + source directory} and possibly a \emph{remote source directory}. + +Why do we need both these directories? The files consisting of the +\TL{} system are on the \CD{}, of course, but some other useful +packages are not, either because of space lacking or because their +license was not compatible with \TL{}. You need to enable Internet +downloading if you want to install these packages that are marked with a +specific ``remote'' icon. + + However, don't panic: the default parameters of the setup will allow + you to install a full system using the \CD{} only. Simply, you won't + have \file{WinEdt} (for example), but you will be able to install it + later. + + So you can take your files from: + \begin{itemize} + \item the \CD{} or any similar flat tree of files, available through + some standard directory (this means the \CD{} can be mounted on + some remote machine and be made available through network + sharing), + \item a set of \file{.zip} files (this is the case when you are + installing from the demo \CD{} or the \fpTeX{} distribution), + \item the Internet; in this case, the program takes care of + downloading the \file{.zip} files it needs for you. + \end{itemize} + This option is available only if you enable Internet file + downloading in the right part of the page. You also need to + configure this Internet access by selecting to connect either using + Internet Explorer~5 \file{wininet.dll}, or using a direct connection (\texttt{ftp}, + \texttt{http}). +% or using a proxy server. +% Last, you can be assisted in defining the \emph{local source +% directory} and \emph{remote source directory} which will be used +% to copy the files onto your hard disk. The \texttt{browse} buttons +% allow to select a directory for the former, and an url among a list +% of mirrors for the latter. +\item[Root Page] + On this page, you will tell where you want the files to be + installed (Figure~\ref{graph:root-schm}, + \ifnum \Status = 1 + on the left% + \else\ifnum \Status=2 + at the top% + \else + on the left% + \fi\fi + ). Only the root directory really matters, the other ones + are set according to the root one. You may want to make + \path|$TEXMFEXTRA| point to some TDS compliant directory with other + \TeX{} files or assign a different value to + \path|$HOMETEXMF|, which is set by default to whatever Windows think + is your `HOME' location. +\begin{figure*}[!htb] + Root and directories\hfill% + Scheme selection + \begin{center} + \ifnum \Status=1 + \includegraphics[width=.46\textwidth]{pictures/root-of-installation.jpg}\hfill% + \includegraphics[width=.46\textwidth]{pictures/scheme-selection.jpg} + \else + \ifnum \Status=2 +\includegraphics[bb=0 0 506 403]{pictures/root-of-installation.jpg} +\includegraphics[bb=0 0 506 403]{pictures/scheme-selection.jpg} + \else + \includegraphics[width=.46\textwidth]{pictures/root-of-installation}% + \hfill% + \includegraphics[width=.46\textwidth]{pictures/scheme-selection} + \fi + \fi + \caption{\TL-Setup: Root and directories / Schemes}\label{graph:root-schm} + \end{center} +\end{figure*} +\item[Get TPM Page] + This page does not require any manual intervention. The \file{.tpm} + files which describe collections and packages are retrieved + (possibly from the Internet), unzipped if needed and parsed. +\item[Schemes Page] + On this page, you will select the global scheme of your + installation (Figure~\ref{graph:root-schm}, + \ifnum \Status = 1 + on the right% + \else\ifnum \Status=2 + at the bottom% + \else + on the right% + \fi\fi + ). A scheme is a large set of files targeted at some kind + of usage. There are 3 generic schemes for basic, recommended and + full installation. The other ones are devoted to LUGs (what GUST or + GUTenberg propose for their members) or applications (XML and + \TeX{}). + When a scheme is selected, it is still possible to refine the + selection by checking the appropriate box. If doing so, you will be + presented the packages page to change your selection, else you will + jump to the review page. +\item[Packages Page] + Collections and packages are presented in a tree form + (Figure~\ref{graph:win32-support}, + \ifnum \Status = 1 + on the left% + \else\ifnum \Status=2 + at the top% + \else + on the left% + \fi\fi + ). The links + in the tree are dependency links. Collections \emph{depend on} + packages and maybe other collections, and it is the same for each + package. You can select any package or collection individually, but + your request will be granted only if the object is not requested by + another one which is selected. For example, you can't deselect + \texttt{tex-basic} without deselecting all the collections that + request it. + + The \texttt{tex-xemtex} collection displayed on the picture is Win32 specific. It + holds a number of bonus packages (Figure~\ref{graph:win32-support}, + \ifnum \Status = 1 + on the right% + \else\ifnum \Status=2 + at the bottom% + \else + on the right% + \fi\fi + ) which can be installed + automatically and individually: Ghostscript (the \PS{} + interpreter), XEmacs editor preconfigured for \TeX{}, tools like Perl, + ImageMagick, Ispell. \emph{None of these packages are selected by + default}. + + On this page, you also have the information about disk space + needed, for each object, and for the set of those who are selected, + and also the disk space available on the partition selected for the + installation. Last, you can choose to install or not the + documentation files and source files associated with each package. +\item[Review Page] + You will find there a summary of your choices + (Figure~\ref{graph:review}, + \ifnum \Status = 1 + on the left% + \else\ifnum \Status=2 + at the top% + \else + on the left% + \fi\fi + ). It is still possible to + go back to change them. +\begin{figure*}[!htb] + Packages Page\hfill% + Win32 Support + \begin{center} + \ifnum \Status=1 + \includegraphics[width=.48\textwidth]{pictures/package-selection}\hfill% + \includegraphics[width=.48\textwidth]{pictures/win32-support} + \else + \ifnum \Status=2 +\includegraphics[bb=0 0 506 403]{pictures/package-selection.jpg}\hfill% +\includegraphics[bb=0 0 506 403]{pictures/win32-support.jpg} + \else + \includegraphics[width=.48\textwidth]{pictures/package-selection}% + \hfill% + \includegraphics[width=.48\textwidth]{pictures/win32-support} + \fi + \fi + \end{center} + \caption{Packages Page / Win32 goodies} + \label{graph:win32-support} +\end{figure*} +\item[Files Copy Page] + The selected files are copied on your hard disk (Figure~\ref{graph:file-copy}, + \ifnum \Status = 1 + on the right% + \else\ifnum \Status=2 + at the bottom% + \else + on the right% + \fi\fi + ). All the files not + yet available on your local disk are first downloaded from the + remote source directory on the Internet. Then every package is + unpacked (if \path|.zip| files), or copied from the \CD{}. +\item[Configuration Page] Several packages need some configuration + step to make them usable (Figure~\ref{graph:configuration}, + \ifnum \Status = 1 + on the left% + \else\ifnum \Status=2 + at the top% + \else + on the left% + \fi\fi + ). Also the \TL{} system needs some post-processing step + (format files generation, ls-R databases generation, environment + variables, etc.). All these operations are done there, some of them + can be lengthy. +\begin{figure*}[!htb] + \textbf{Review Page}\hfill% + \textbf{File Copy Page} + \begin{center} + \ifnum \Status=1 + \includegraphics[width=.48\textwidth]{pictures/review-settings}\hfill% + \includegraphics[width=.48\textwidth]{pictures/file-copy} + \else + \ifnum \Status=2 + \includegraphics[bb=0 0 506 403]{pictures/review-settings.jpg}\hfill% + \includegraphics[bb=0 0 506 403]{pictures/file-copy.jpg} + \else + \includegraphics[width=.48\textwidth]{pictures/review-settings}\hfill% + \includegraphics[width=.48\textwidth]{pictures/file-copy}% + \fi + \fi + \end{center} + \caption{Review Page / File Copy Page} + \label{graph:review}\label{graph:file-copy} +\end{figure*} +\item[Final Page] The installation being over, you may want to display + the Windows specific documentation (HTML format) and / or the log + file of the setup process (Figure~\ref{graph:final} + \ifnum \Status = 1 + on the right% + \else\ifnum \Status=2 + at the bottom% + \else + on the right% + \fi\fi + ). If it is needed (Win9x/WinME), you will + be asked to reboot your computer. +\end{description} + +\begin{figure*}[!htb] + \textbf{Configuration Page}\hfill% + \textbf{Final Page} + \begin{center} + \ifnum \Status=1 + \includegraphics[width=.48\textwidth]{pictures/configuration}\hfill% + \includegraphics[width=.48\textwidth]{pictures/congratulations} + \else + \ifnum \Status=2 + \includegraphics[bb=0 0 506 403]{pictures/configuration.jpg}\hfill% + \includegraphics[bb=0 0 506 403]{pictures/congratulations.jpg} + \else + \includegraphics[width=.48\textwidth]{pictures/configuration}\hfill% + \includegraphics[width=.48\textwidth]{pictures/congratulations}% + \fi + \fi + \end{center} + \caption{Configuration Page / Final page} +\label{graph:configuration}\label{graph:final} +\end{figure*} + +Please be aware that the choice of cluster size on DOS disk +partitions can radically affect the size of your \TeX\ +installation. The support tree has hundreds of small files, and it is +not unusual for a complete installation to take up to four times the +amount of space used on the \CD. + +\end{comment} + + +\section{Windows maintenance and post-installation} + +Although this version of \TL{} cannot be installed on Windows, enough of +this section is relevant to existing installations or cross-mounted +installations that it seemed worth leaving in. + +It will be thoroughly updated when a complete \TL{} Windows distribution +is released. For now, please ignore references to +\filename{TeXSetup.exe}, etc. + + +\subsection{What's different in Windows?} + +The Windows version of \Webc{} has some specific features that should be +pointed out. + +\begin{description} +\item[\KPS{}] The hash-tables that \KPS{} builds are quite large for + the \TL{}. In order to cut down the starting time of any + \KPS{}-enabled program, these hash-tables have been put in shared + memory. This way, when you chain the execution of several such + programs, like \path|tex| calling \path|mpost| calling \path|tex|, + the overhead when starting each of the subprograms is + reduced. This change is hidden to the user, except if you set the + debug flag of kpathsea to the \path|-1| value: you will then trace + access to the shared memory, which is not what you want (it is + accessed very often!). What is useful in a log trace of the shared + memory access is still to be defined, so the situation might evolve + in the future. +\item[\cmdname{kpsecheck}] This command provides some options that did + not fit well into \cmdname{kpsewhich}. It will allow you to list all + the files that occur multiple times across your texmf trees. This + could be handy, but most of the time you will also get unwanted + output (like dozens of \path|README| files)\footnote{It is noticeable + that all these files result in clashes inside the \KPS{}-hashing + mechanism; fortunately, \KPS{} never looks for these files.}. For + this reason, you can combine the \path|-multiple-occurrences| with 2 + other options for including or excluding any filename that match + some pattern (you can request for several patterns). + + The \cmdname{kpsecheck} command will also report the status of shared + memory: in use or not used. That might be useful to know because if + the status reported is \samp{in use}, that means one or several + processes are working, and the effect of any \cmdname{mktexlsr} + command will be delayed until the next time where no \KPS{} linked + process will be running. + + Last, this same command will report about the location it thinks + Ghostscript can be found. Under Win32, for many programs, it is + easier to use the Ghostscript dll, and find it by using the + Ghostscript registry key than to change the \path|PATH|, which has a + limited length anyway. +\item[\Webc{}] The engines have a few more options than in Unix + \Webc{}, and one option with a different behavior: + \begin{itemize} + \item \path|-halt-on-error| stop the compilation at the first error. + \item \path|-job-time| set the job time to the same timestamp as the + file given in argument. +\item \path|-oem| use the DOS codepage for console output. + \item \path|-output-directory| allow to write all the output files in the + specified directory. + \item \path|-time-statistics| print statistics about the job run + time. It is to be noted that Win9x not being a true multitasking + operating system, it has no reliable timer for short periods, so + the value printed is an approximation. Under NT/2K/XP, the result + is quite accurate with user time and system time values allocated + for this run. For Unix + users: the \path|time| command is not usually available to Windows + users. + \end{itemize} +\end{description} + +\subsection{Adding packages to your installation} + +You will find an option in the \guiseq{TeXLive} menu (or go to +\guiseq{Start\arw Programs \arw TeXLive \arw Add TeX package} menu) to +run \file{TeXSetup.exe} in maintenance mode. The steps are almost the +same as in the initial installation. + +We'll discuss differences below, but first, whatever changes you make, +\textbf{do not forget to rebuild the ls-R database files}. Otherwise, +your new files will not be found. You can do this either via the +\acro{GUI} (\guiseq{Start \arw Programs \arw TeXLive \arw Maintenance +\arw Rebuild ls-R}), or manually running the \file{mktexlsr} command. + +The main difference is in the packages selection page. In maintenance +mode, the list of installed packages is compared to the list of packages +available from your source directories. Packages that are not installed +will be displayed in green, out of date packages will be displayed in +red and up-to-date, installed packages are displayed in black. + +This way, you can choose to add or upgrade components, either from +\TL{} or from the Internet, where you are likely to find some more +recent version of your packages. + +It is up to you to select which packages you want to install. The rest +of the process is similar to the first installation. + +If you want to add files that are not provided by the \TL{} (or +\fpTeX{}) distribution, it is recommended to put them in the +\path|$TEXMFLOCAL| directory. This way, you will be safe against +upgrades of the \TL{} software. + +The directory pointed to by \path|$TEXMFLOCAL| is initially empty. If, +for example, you want to add the support file for the Maple symbolic +computation program, you will have to put the style files in:\\ +\path|c:\Program Files\TeXLive\texmf-local\tex\latex\maple\|\\ and the +documentation files in:\\ \path|c:\Program +Files\TeXLive\texmf-local\doc\latex\maple\| + +\subsection{Uninstalling \protect\TL{}} + +The uninstall procedure is available either from the \file{TeXLive.exe} +program, from the \path|TeXLive| menu or from the control panel +(\guiseq{Start \arw Control Panel, Add/Remove Programs}). This procedure +will cleanup your hard disk of most of the \TL{} files. However, +\TeX{} is a system that is creating files and there is no mechanism to +keep track of all of them. Moreover, Win32 support packages have their +own uninstall procedure, which you will have to run separately (provided +you want to get rid of them). Last, the files you may have stored in +\path|$TEXMFLOCAL| won't be removed. So, even if the vast majority of +files are automatically removed by the uninstall procedure, you will +have to do some manual cleanup to actually remove all of them. + +\subsection{Running \texttt{TeXSetup.exe} from the command line} + +The \path|TeXSetup.exe| program has a number of other useful +options. You can get the list by running: +\begin{verbatim} +c:\>TeXSetup --help +\end{verbatim} + +Here is the description: +\begin{description} +\item[\path|--automatic-reboot|] reboot without waiting user + confirmation once installation is over; +\item[\path|--dry-run|] do nothing, just log everything that will be + done without this option; +\item[\path|--quick|] use the recommended installation and default + directories, ask nothing up to rebooting; +\item[\path|--with-xemtex|] selects the \XEmTeX{} bundle; +\item[\path|--net-method (=ie5/direct)|] enable to download components with + restricted licenses from the Internet (either using direct + connection of Internet Explorer 5 DLLs): you need to have an available + network connection and some of the packages are huge; +\item[\path|--remote-source-directory |] this is the base url for the remote packages; +\item[\path|--local-source-directory |] by default, \path|TeXSetup.exe| + will guess the root directory of the set of files you want it to act on, if you ever + upgrade \path|TeXSetup.exe|, you won't be able to copy the new version + onto your \CD{}, so you will need to use this option to specify the + root of the \CD{}; +\item[\path|--installation-directory |] this is the root of your + installation, all files will be copied under this location. The + default value is \verb+c:\Program Files\TL+; +\item[\path|--texmfmain-directory |] +\item[\path|--texmflocal-directory |] +\item[\path|--texmfextra-directory |] +\item[\path|--texmfhome-directory |] +\item[\path|--vartexmf-directory |] +\item[\path|--vartexfonts-directory |] these are the directories + used to configure the location of your files. They map directly to + the \path|texmf.cnf| variables. +\item[\path|--with-source-files(=yes/no)|] copy the source files + for \TeX{} packages, default value is no; +\item[\path|--with-documentation-files(=yes/no)|] copy documentation files for \TeX{} + packages. Default value is yes. Beware: this is only documentation about specific + packages, general documentation will be installed anyway; +\item[\path|--program-folder |] the name of the folder under + which you will find the menus; +\item[\path|--add-package |] this is used to add or update a specific + package after a first regular installation; +\item[\path|--scheme |] install the named scheme instead of the + default \path|texlive-recommended| scheme; +\item[\path|--maintenance|] mostly the same as \path|--add-package| + without specifying a package to add; +\item[\path|--uninstall|] this option will remove anything \TeX{} related coming from + the \CD{}, which means there can be files left if you added style + files or format files, and also that supplementary tools will not be + removed. This option is still a bit crude in this release; +\item[\path|--help|] this option opens up a box with the list of options. +\end{description} + +\subsection{Network installation} + +\KPS{} knows about UNC names, so you can use them to get your TEXMF +tree from the network. But there is better than this. +All the support files and configuration files, everything except the files in the +\path|bin/win32| are shareable with a \teTeX{} or Unix \TL{} installation. That means +you can use Samba either to mount from an NT server to a Unix +workstation or the converse. Several strategies are possible: +\begin{itemize} +\item Put everything on the server. Just add each set of files for the os and +architecture you want to use in the \path|bin| directory. That means +for example \path|bin/win32| and \path|bin/i386-linux|. Next configure +your main variables. You can use UNC names to +point to the right directories under Win32. +\item Install a local copy for the binaries and format files. In this + case, assign \path|$TEXMFMAIN| to the main \path|texmf| tree that + will be accessed remotely. Set \path|$VARTEXMF| to be a local + directory which will hold local configuration files and on-the-fly + generated files. +\end{itemize} + +\subsection{Personal configurations} + +\subsubsection{Dvips} + +The configuration file for dvips can be found in\\ +\verb+C:\Program Files\TeXLive\texmf-var\dvips\config\config.ps+\\ +You may open it with any editor + %(\cmdname{WinShell} will do fine) + and change some parameters: + +\begin{description} +\item [fonts] you can change the default printer \MF{} mode or printer + resolution in case \cmdname{dvips} needs to generate PK fonts. By default it + is configured to use Type~1 versions of the CM fonts, so it should + not call \cmdname{mktexpk} too often; +\item[printer] you can tell dvips where you want to print by default. If + the \optname{o} option is not followed by a printer name, then a + \file{.ps} \PS{} file is written. You can give dvips a printer + name such as: +\begin{verbatim} +o lpt1: +% o | lpr -S server -P myprinter +% o \\server\myprinter +\end{verbatim} +\item[paper] Next, you might want + to change the paper size from European (A4) to US letter + by making the US letter the first paper size mentioned in the file. + Scroll to the group of lines beginning with \code{@}. Move + the appropriate lines so that this section begins with the lines:\\ +\hspace*{1em} @ letterSize 8.5in 11in\\ +\hspace*{1em} @ letter 8.5in 11in\\ +\hspace*{1em} @+ \%\%BeginPaperSize: Letter\\ +\hspace*{1em} @+ letter\\ +\hspace*{1em} @+ \%\%EndPaperSize +\end{description} + +The current \TL{} distribution implements the procedure of making +always up-to-date fontmaps files for Dvips and Pdftex. This is done by +the \cmdname{updmap} program during installation, as well as during any +font package addition. If you add new packages by hand, edit the file +\verb+updmap.cfg+ in \path|$VARTEXMF/web2c|. + +\subsubsection{Pdftex} + +If you use the program pdf{}latex to write \acro{PDF} format directly, +and you are using \acro{US} letter-size paper, edit the file +\verb+C:\Program Files\TeXLive\texmf-var\tex\generic\config\pdftexconfig.tex+ and +change \samp{\bs pdfpagewidth} and \samp{\bs pdfpageheight}. These entries should read: +\begin{alltt} +\bs{}pdfpagewidth=8.5 true in +\bs{}pdfpageheight=11 true in +\end{alltt} +Save the file and exit the editor. + +\subsubsection{GSView} +GSView is now distributed under the Aladdin License, and therefore is no longer included in +\TL{}. + +If you may want to change the page size to US letter size. If so, open +GSView from the \guiseq{Start} menu, and select \guiseq{Media\arw Letter}. + +Also, there are menu settings that are supposed to give you the most +readable screen image. On \guiseq{Media \arw Display Settings}, set both +\optname{Text Alpha} and \optname{Graphics Alpha} to 4~bits. + +Note that the installation process has set all \code{.ps} and +\code{.eps} files to automatically open with \cmdname{GSView}. + +For printing instructions, see section~\ref{printing} below. + +\subsubsection{WinDvi} +\label{sub:windvi} + +The \file{TeXSetup.exe} program takes care of associating the files +with the \file{.dvi} extension with \file{Windvi}. + +Open it with \guiseq{Start\arw Programs\arw TeXLive\arw DVI Viewer}. + +You can set it for US letter-size paper by going to \guiseq{View\arw +Options\arw Papertype} and selecting US (8.5\verb+"+ x 11\verb+"+) (and +then \optname{OK}. Exit \cmdname{windvi}. + +You can change other parameters from there as well, such as the ability +to execute system commands specified by the document (disabled by +default for security reasons). Also, the first time you view any .dvi +file, you may find the magnification too large. Zoom out until you get +an appropriate size. + +%There are two important parameters related to printing that can't yet +%be set from the dialog boxes, namely the resolution and the \MF{} mode +%for the printer. You can set them once for all by specifying them on +%the command line: +%\begin{verbatim} +%c:\>windvi -p 360 -mfmode canonbjc foo.dvi +%\end{verbatim} +%When you will exit Windvi, these parameters will be stored in the +%configuration file. The available modes are found in this file:\\ +%\path|c:\Program Files\TeXLive\texmf\metafont\misc\modes.mf| + +All configuration settings for \cmdname{Windvi} are stored in a file +named \path|windvi.cnf| file. You can find it by running this command at +the prompt: +\begin{verbatim} +c:\>kpsewhich --expand-var $HOME/windvi.cnf +\end{verbatim} + +Should you have problems with \cmdname{Windvi}, please remove the configuration +file and test your problem against a vanilla configuration. + +\subsection{Testing} + +For generic verification procedures, see section~\ref{sec:test-install} +(\p.\pageref{sec:test-install}). This section describes +Windows-specific tests. + +Open the file \verb+sample2e.tex+ in your editor (Xemacs, WinShell), +found in \path|C:\Local\TeX\texmf\tex\latex\base|. The \LaTeX\ source +should appear on the screen. Process it by clicking on the +\guiseq{Command\arw LaTeX} menu (XEmacs) or \LaTeX\ icon on the toolbar +(WinShell), then view it by clicking on the \guiseq{Command\arw View DVI} +menu (XEmacs) or Preview (Windvi) icon (WinShell). + +At first, when you preview files with Windvi, it will create fonts because +screen fonts were not installed. After a while, you will have created most +of the fonts you use, and you will rarely see the font-creation window. + +\textbf{Hint for the future:} If a \LaTeX\ run stops because \LaTeX\ +cannot find a file, you can press Ctrl-z to quit. + + +\subsection{Printing} +\label{printing} + +It is possible to print from Windvi. In this case, printing will be done +using the Windows unified printer driver. By definition, it is +compatible with all printers. However, there is some drawback: it can +generate some huge spool files, and some (older) versions of Windows +just don't like them. The advantage is that you can use features like +embedding BMP or WMF images. You also need to make sure that the printer +parameters are correctly set (subsection~\ref{sub:windvi}), else you +will get scaled printing (printing at 600\dpi{} on a 300\dpi{} printer +will give you only one quadrant of your page). + + +Printing is faster and more reliable if you run \cmdname{dvips} to make +a \filename{.ps} file and then print from \cmdname{GSView}. In +\cmdname{GSview}, select \guiseq{File\arw Print\ldots}. A \guiseq{Print} +window will appear. + +If you are using a \PS{} printer, \textit{be sure to select +\guiseq{\PS{} Printer}}. This is done in the \guiseq{Print Method} box +at the bottom left of the \guiseq{Print} window. You can then select any +of the printers that you have previously installed. If you fail to +check the box for \optname{\PS{} Printer}, printing will not work. + +If you will be using your own non-\PS{} printer, select +\guiseq{Ghostscript device} in the \guiseq{Print Method} box, then click +on the button to the right labelled \guiseq{djet500} and select your +printer type from the list that pops up. (In the older version of +\cmdname{GSView}, make sure \optname{\PS{} Printer} is \textit{not} +selected, then select your printer type from the \guiseq{Device} list.) + +\subsection{Tips and tricks for Win32} + +\subsubsection{Different flavors of Win32} + +What we call Win32 is not an operating system by itself. It is a large +set of functions (around 12,000 in the header files of the Microsoft +\acro{SDK}) that you can use to write programs for different operating +systems of the Windows family. + +Windows comes in different flavors: +\begin{itemize} +\item Win95, Win98 and Win\acro{ME}, which \emph{are not true multitasking, + multithreading} environments. They are the latest\Dash and hopefully + last\Dash metamorphosis of \acro{DOS}. This can be more or less proven + by the fact that when booting, the PC will load the \path|command.com| + interpreter, and if you stop the boot process at this point, you can + ask for the current (\acro{DOS}) version and it will answer something + like \samp{MS-DOS 7.0} (at least for the old versions of Win9x). +\item Windows \acro{NT}, which is a new operating system written from + scratch, capable of true multitasking behavior, and including many + high level features. +\item Windows 2000, based on \acro{NT}, with all the bells and + whistles of Win98. +\item Windows \acro{XP}, which comes with Personal and Pro flavors. This is + the last step in merging both lines of products (Win9x based and + \acro{NT} based). \acro{XP} is based on \acro{NT}. +\end{itemize} + +Win9x are able to run 32~bits programs and 16~bits programs +concurrently. But the operating system by itself is not entirely +written in 32~bits mode, and does not support memory protection: 16bits +applications can overwrite parts of the operating system memory! Some +parts of the system like the \acro{GDI} (Graphical Device Interface) +manage limited resources like bitmaps, fonts, pens and so on for the set +of all programs that run concurrently. All the bitmaps headers available +at the same time can't amount for more than 64kB. This explains the +performance tool and the fact that you can put your system on his knees +by making intensive use of graphic objects for example. + +NT, 2K and XP do not suffer from these limitations, and neither from +other Win9x limitations. They are true multitasking environments, with +protected memory. They are much more responsive than Win9x because +of better memory management, better file system and so on. + +\subsubsection{Command line prompt} + +You may wonder, ``Why would I need to use a command line prompt when +I have Windows?'' + +Good question. The problem is of very general nature. Not all operations +can be done easily using only a \acro{GUI}. Command line gives you +programming power\Dash assuming a clever command interpreter. + +But the problem here is more fundamental: \TeX{} is \emph{a batch} +tool. Not an interactive one. \TeX{} needs to compute the best +layout for each page, resolve cross-references and so on. This can be +done only by a global processing of the document. It is not (yet) a +task that can be done interactively. + +This means that you should use \TeX{} from a command line. In fact the +situation is not so bad. There is an advantage to write command line +tools for complex processing: they are better debugged, because they are +independent of any \acro{GUI} problems, and \acro{GUI} tools can be +designed to interface to the command line tools. This is the case for +\TeX{}, where you will mostly interact with it through a \acro{GUI} text +editor. + +However, you may need to use the command line prompt in a number of +situations. One is when you are having difficulties and want to debug +your setup. + +\begin{description} + \item[Win9x] You can open a command line prompt by looking either for + the \acro{MS-DOS} icon in the \guiseq{Start\arw Programs} menu, + or by choosing \guiseq{Start\arw Run} menu typing in + \path|command.com| as the progrm name. + \item[NT, 2K, XP] You can open a command line prompt by looking for + \guiseq{Command Prompt} in the \guiseq{Start\arw Accessories} menu. + You can also choose \guiseq{Start\arw Run} and type in + \path|cmd.exe|, which is the name of the brand new command + interpreter for \acro{NT} (thus, it is untrue to call this a + \emph{DOS} box!). +\end{description} + +These locations may change across different Windows versions. + + +\subsubsection{Path separators} + +The Win32 API understands both \path|/| and \path|\| characters as PATH +separators. But the command interpreters do not! So whenever a path name +is used programmatically, you can use both separators, and even mix them +up in the same path name. But on the command line, you must type +\path|\| as path separator. The reason is compatibility: the command +processor used \samp{/} to introduce arguments to commands. + +All this to say: do not be surprised to read path names written using +the Unix convention; \fpTeX{} is a port of \Webc, and aims to be compatible +across platforms. For this reason, all the configuration files that +need to specify path names use the Unix convention. + +\subsubsection{File systems} +\label{sec:clusters} + +The worst feature of Win9x with regard to \TeX{} is probably the +so-called FAT file system. \TeX{} uses very many small files, with size +around 1--3kB. The \acro{FAT} file system is old, and predates by +decades the multi-gigabytes hard disks we have today. As a result, it +cannot manage efficiently the tens of thousands of \TeX{} files found in +\TL{}. The \acro{FAT} file system allocates a minimum of 32kB for +\emph{any} file on a huge partition. It means that \TeX{} will use much +more disk space than it actually needs. + +The other, more modern, file systems available, \acro{FAT32} and +\acro{NTFS}, do not have this drawback. They manage clusters of 4kB +only. (You can lower the limit to 512 bytes on \acro{NTFS}.) + +\subsubsection{How to add some directory to your PATH} + +There are pairs of variables and values which behave much like global +variables inside your programs. The set of those variables is called the +environment. Each program is initialized with a copy of the +environment when it is run. It can request and change the +value of any variable. The changes happen in the copy of the +environment, and is not at all propagated to the other running +programs. + +Your PATH is a special environment variable used to search for +programs you want to run. +There is a different procedure to change it for Win9x, WinME and NT/2K/XP: + +\begin{description} +\item[Windows 95/98] Edit your \path|autoexec.bat|. In this file should be a line + starting with \texttt{PATH=} and followed by a list of directories separated + by \path|;|. Please add the directory with the executables in this line. + After this, this line could look as follows: +\begin{verbatim} +PATH=c:\windows;c:\windows\system;c:\"Program Files"\TL\bin\win32 +\end{verbatim} +\item[Windows ME] You need to run the special program + \path|c:\windows\system\msconfig.exe| to be able to change any + environment variable. From this program, select the `Environment' + tab, and then add or modify the variable you want. You will be asked to reboot the + machine upon any change. +\item[Windows NT/2K/XP] + Click left on \guiseq{Start \arw Settings \arw Control Panel}. Now the + window with the control panel icons opens. Double click on System. The + System Properties window opens. Click on the tab \textsf{Environment} + or look for a button named \guiseq{Environment Variables} among the + dialog boxes. Now you can change the environment variables for your + user account. Note: There are also displayed the environment settings + for the system. Normally, you can't change the system variables + unless you have administrator rights on your machine. If you want to + change the \texttt{PATH} for all users, you will have to contact your + system administrator or be the system administrator yourself\Dash in + the latter case you should know what you are doing. + + If there is already a \texttt{PATH} setting for your user account, + left click on \texttt{PATH}. In the field \textsf{Variable} appears + \texttt{PATH} while the field Value shows the current setting of + \texttt{PATH} as a list of directories separated by \path|;|. Add + the directory where the executables are located (e.g. + \path|c:\Program Files\TeXLive\bin\win32|). If there isn't a \texttt{PATH} variable + for your user account, simply click in the field Variable and type + in \texttt{PATH}, click in the field \textsf{Value} + and type in the directory with the executables. Important: Click on + the \textsf{Apply} button before clicking \textsf{Ok}, otherwise the + changes to \texttt{PATH} won't apply to your system. Be careful when + changing the environment settings. +\end{description} + +The best way to be sure that a variable has been properly set is to +open a console and type: +\begin{verbatim} +set VARIABLE +\end{verbatim} +which should return the corresponding value. + +\subsubsection{\TeX{} engines} + +If you have a look at the \Webc{} documentation, you will read that all +the various \TeX{} derived programs use the same base engine. For +example, \path|tex.exe| and \path|latex.exe| are exact copies of the +same program, but each one will use a different format file, based on +its calling name. + +Under Unix, this feature is implemented through \emph{symbolic +links}. It saves up a bit of disk space, because some engines are +used with many different format files. + +The Win32 API does not know about file links. So to save up almost +the same amount of memory, all the \TeX{} base engines have been put +in DLLs (\emph{Dynamic Linked Library}). This means that you will have +the following layout: +\begin{alltt} +13/05/2002 17:06 3 584 latex.exe +13/05/2002 17:06 266 240 tex.dll +13/05/2002 17:06 3 584 tex.exe +\end{alltt} +and the \path|latex.exe| file is nothing but a rough copy of +\path|tex.exe| using the same core \path|tex.dll|. +The same trick has been used for the \path|mktex*.exe| family of programs which are +linked to the \path|mktex.dll| library. + +In fact, a generic tool called \path|lnexe.exe| is provided to build the +equivalent of Unix hard links for executable files only under Win32. + +\subsection{In case of problems} +\label{sec:troubleshooting} + +\subsubsection{What to do if \texttt{latex} does not find your files?} + +\begin{itemize} + +\item \cmdname{kpsewhich} is the tool of choice to debug any +problem. Unfortunately, \cmdname{kpsewhich} outputs debug information +to stderr, and the Windows console does not know how to redirect stderr +to a file\footnote{Well, NT and Win2k consoles know how to do that. But +the trick will work for any console.}. For diagnostic purposes you can +temporarily set an environment variable (in a \acro{DOS} box): + +\begin{verbatim} +SET KPATHSEA_DEBUG_OUTPUT=err.log +\end{verbatim} +You can also set the debug level: +\begin{verbatim} +SET KPATHSEA_DEBUG=-1 +\end{verbatim} + +If you want to redirect stderr to stdout, which is not possible +Windows, then do: +\begin{verbatim} +SET KPATHSEA_DEBUG_OUTPUT=con: +\end{verbatim} +This way you can capture both stdout and stderr in the same file. + +\item Assuming the installation has been done in \path|c:/Program Files/TeXLive|, check + the following values: \\ + {\small + \begin{tabular}{ll} + \path|kpsewhich -expand-path $SELFAUTOPARENT| & \path|c:/Program Files/TeXLive| \\ + \path|kpsewhich -expand-path $TEXMF| & \path|c:/Program Files/TeXLive/texmf| \\ + \path|kpsewhich -expand-path $TEXMFCNF| & + \path|.;c:/Program Files/TeXLive/texmf/web2c;| \\ + & \path|c:/Program Files/TeXLive/bin/win32;| \\ + & \path|c:/Program Files/TeXLive/bin;| \\ + & \path|c:/Program Files/TeXLive| \\ + \path|kpsewhich -expand-var $TEXINPUTS| & \path|.;c:/Program Files/TeXLive/texmf/tex//| + \end{tabular} +} +\item If you have other \TeX{}-related values already set in your + environment, please, remove them. They are overriding the ones in + texmf.cnf. +\item Check the values from:\\ +{\small + \begin{tabular}{ll} + \texttt{kpsewhich cmr10.tfm} & \path|c:/Program Files/TeXLive/texmf/fonts/tfm/public/cm/cmr10.tfm|\\ + \texttt{kpsewhich latex.fmt}& \path|c:/Program Files/TeXLive/texmf/web2c/latex.fmt| + \end{tabular} +} +\item At this point, if everything is correct, \TeX{} and friends + should work. If it is not the case, you will need to play with + the \path|-debug=n| option from \path|kpsewhich|, and check back all + the values. Try to identify and report the problem. +\end{itemize} + +\subsubsection{What to do if your setup still does not work as expected?} + +Here are several questions to investigate: + +\begin{enumerate} +\item Is \file{tex.exe} in my \path|PATH|? + +\item Is the \path|TEXMFCNF| variable correctly set to +\path|c:/Program Files/TeXLive/texmf-var/web2c| (default value)? + +\item Are there any errors in the log file generated by the +\file{TeXSetup.exe} program? You can find this by searching for the +string \samp{Error}. + +\item Are there any relevant bug fixes at \url{http://tug.org/texlive/}? +(Unlikely, but it doesn't hurt to check.) + +\item Check the web pages at +\url{http://www.fptex.org/}, or consider subscribing to the \fpTeX{} +mailing list, via \url{http://tug.org/mailman/listinfo/fptex}. + +\end{enumerate} + + +The \TL{} software consists of hundreds of programs and tens of +thousands of files, all from varying sources. So it is quite difficult to +predict all possible causes for problems. Nevertheless, we will do our +best to help you. (See section~\ref{sec:help}, \p.\pageref{sec:help}.) + + +\subsection{Compiling the source files} + +The whole set of source files is available in the distribution as the +\path|source/source.tar.bz2| archive, together with a separate source +archive for Windows. To be able to compile the whole distribution for +Windows, you will need: + +\begin{itemize*} +\item Windows 2K/XP +\item Microsoft Visual Studio .Net 2003 +\item a set of Unix tools (\texttt{sed}, + \texttt{grep}, \texttt{gawk}, etc.) and also Perl, Flex and Bison, +\item to adjust the paths in the + \path|win32/make/common.mak| file according to your installation +\item to adjust the paths in the Perl script file + \path|win32/perl/build.pl|, +\item run the compilation from the \path|mswin32/| directory using this + command: +\begin{verbatim} +c:\texlive\source\mswin32>perl ./perl/build.pl --install --log=install.log +\end{verbatim} +\end{itemize*} + +There is a lot of work to do to make this process easier and cleaner. + +\subsection{Where to get more information} + +The Windows \TeX{} system included on \TL{} is also known as +\fpTeX. The packaging differs, but \fpTeX{} is no more no less than the +current \TL\ release for Windows. + +The \fpTeX{} home page is \url{http://www.fptex.org}. + +The current \fpTeX release is available from any \CTAN site in +\url{htp://www.ctan.org/tex-archive/systems/win32/fptex}. + +The main ftp site for \fpTeX\ is \url{ftp://ftp.dante.de/pub/fptex/} +from where beta versions of \fpTeX\ and additionnal tools are available. +This main site is (partially) mirrored daily by all \CTAN{} sites at +\path|systems/win32/fptex|. + +The \TeX{} Users Group is kindly hosting a mailing list dedicated to +\fpTeX. It is used for announcements, bug reports, enhancement requests, +and general discussion about \fpTeX. To subscribe, visit +\url{http://tug.org/mailman/listinfo/fptex}. The mailing list +address is \email{fptex@tug.org}. + + +% don't use \Webc so the \uppercase in the headline works. +\section{A user's guide to Web2C} + +\Webc{} is an integrated collection of \TeX-related programs: \TeX{} +itself, \MF{}, \MP, \BibTeX{}, etc. It is the heart of \TL{}. + +A bit of history: The original implementation was by Tomas Rokicki who, +in 1987, developed a first \TeX{}-to-C system based on change files +under Unix, which were primarily the original work of Howard Trickey and +Pavel Curtis. Tim Morgan became the maintainer of the system, and +during this period the name changed to Web-to-C\@. In 1990, Karl Berry +took over the work, assisted by dozens of additional contributors, and +in 1997 he handed the baton to Olaf Weber. + +The \Webc{} system runs on Unix, 32-bit Windows systems, \MacOSX{}, and +other operating systems. It uses Knuth's original sources for \TeX{} and +other basic programs written in \web{} and translates them into C source +code. The core \TeX{} programs are: + +\begin{cmddescription} +\item[bibtex] Maintaining bibliographies. +\item[dmp] \cmdname{troff} to MPX (\MP{} pictures). +\item[dvicopy] Expands virtual font references in \dvi{} files. +\item[dvitomp] \dvi{} to MPX (MetaPost pictures). +\item[dvitype] \dvi{} to human-readable text. +\item[gftodvi] Generic font proofsheets. +\item[gftopk] Generic to packed fonts. +\item[gftype] GF to human-readable text. +\item[makempx] \MP{} label typesetting. +\item[mf] Creating typeface families. +\item[mft] Prettyprinting \MF{} source. +\item[mpost] Creating technical diagrams. +\item[mpto] MetaPost label extraction. +\item[newer] Compare modification times. +\item[patgen] Creating hyphenation patterns. +\item[pktogf] Packed to generic fonts. +\item[pktype] PK to human-readable text. +\item[pltotf] Plain text property list to TFM. +\item[pooltype] Display \web{} pool files. +\item[tangle] \web{} to Pascal. +\item[tex] Typesetting. +\item[tftopl] TFM to plain text property list. +\item[vftovp] Virtual font to virtual property list. +\item[vptovf] Virtual property list to virtual font. +\item[weave] \web{} to \TeX. +\end{cmddescription} + +\noindent The precise functions and syntax of these programs are +described in the documentation of the individual packages and of \Webc{} +itself. However, knowing a few principles governing the whole family of +programs will help you take advantage of your \Webc{} installation. + +All programs honor these standard \acro{GNU} options: +\begin{ttdescription} +\item[-{}-help] print basic usage summary. +\item[-{}-verbose] print detailed progress report. +\item[-{}-version] print version information, then exit. +\end{ttdescription} + +For locating files the \Webc{} programs use the path searching library +\KPS{}. This library uses a combination of environment variables and a +configuration files to optimize searching the (huge) collection of +\TeX{} files. \Webc{} can look at more than one directory tree +simultaneously, which is useful in maintaining \TeX's standard +distribution and local extensions in two distinct trees. To speed up +file searches the root of each tree has a file \file{ls-R}, containing +an entry showing the name and relative pathname for all files under that +root. + +\subsection{Kpathsea path searching} + +Let us first describe the generic path searching mechanism of the \KPS{} +library. + +We call a \emph{search path} a colon- or semicolon\hyph sepa\-rated list +of \emph{path elements}, which are basically directory names. A +search path can come from (a combination of) many sources. To look up +a file \samp{my-file} along a path \samp{.:/dir}, \KPS{} checks each +element of the path in turn: first \file{./my-file}, then +\file{/dir/my-file}, returning the first match (or possibly all +matches). + +In order to adapt optimally to all operating systems' conventions, on +non-Unix systems \KPS{} can use filename separators different from +colon (\samp{:}) and slash (\samp{/}). + +To check a particular path element \var{p}, \KPS{} first checks if a +prebuilt database (see ``Filename data\-base'' on +page~\pageref{Filename-database}) applies to \var{p}, i.e., if the database +is in a directory that is a prefix of \var{p}. If so, the path +specification is matched against the contents of the database. + +If the database does not exist, or does not apply to this path +element, or contains no matches, the filesystem is searched (if this +was not forbidden by a specification starting with \samp{!!}\ and if +the file being searched for must exist). \KPS{} constructs the list +of directories that correspond to this path element, and then checks +in each for the file being sought. + +The ``file must exist'' condition comes into play with \samp{.vf} files and +input files read by \TeX's \cs{openin} command. Such files may not +exist (e.g., \file{cmr10.vf}), and so it would be wrong to search the +disk for them. Therefore, if you fail to update \file{ls-R} when you +install a new \samp{.vf} file, it will never be found. +Each path element is checked in turn: first the database, then the +disk. If a match is found, the search stops and the result is +returned. + +Although the simplest and most common path element is a directory +name, \KPS{} supports additional features in search paths: layered +default values, environment variable names, config file values, users' +home directories, and recursive subdirectory searching. Thus, we say +that \KPS{} \emph{expands} a path element, meaning it transforms all +the specifications into basic directory name or names. This is +described in the following sections in the same order as it takes +place. + +Note that if the filename being searched for is absolute or explicitly +relative, i.e., starts with \samp{/} or \samp{./} or \samp{../}, +\KPS{} simply checks if that file exists. + +\ifSingleColumn +\else +\begin{figure*} +\verbatiminput{examples/ex5.tex} +\setlength{\abovecaptionskip}{0pt} + \caption{An illustrative configuration file sample} + \label{fig:config-sample} +\end{figure*} +\fi + +\subsubsection{Path sources} +\label{Path-sources} + +A search path can come from many sources. In the order in which +\KPS{} uses them: + +\begin{enumerate} +\item + A user-set environment variable, for instance, \envname{TEXINPUTS}\@. + Environment variables with a period and a program name appended + override; e.g., if \samp{latex} is the name of the program being run, + then \envname{TEXINPUTS.latex} will override \envname{TEXINPUTS}. +\item + A program-specific configuration file, for exam\-ple, a line + \samp{S /a:/b} in \cmdname{dvips}'s \file{config.ps}. +\item A \KPS{} configuration file \file{texmf.cnf}, containing a line like + \samp{TEXINPUTS=/c:/d} (see below). +\item The compile-time default. +\end{enumerate} +\noindent You can see each of these values for a given +search path by using the debugging options (see ``Debugging actions'' +on page~\pageref{Debugging}). + +\subsubsection{Config files} + +\begingroup\tolerance=3500 +\KPS{} reads \emph{runtime configuration files} named \file{texmf.cnf} +for search path and other definitions. The search path used to look +for these files is named \envname{TEXMFCNF} (by default such a file lives +in the \file{texmf/web2c} subdirectory). \emph{All} +\file{texmf.cnf} files in the search path will be read and definitions +in earlier files override those in later files. Thus, with a search +path of \verb|.:$TEXMF|, values from \file{./texmf.cnf} override those +from \verb|$TEXMF/texmf.cnf|. +\endgroup + +\begin{itemize} +\item + Comments start with \code{\%} and continue to the end of the line. +\item + Blank lines are ignored. +\item + A \bs{} at the end of a line acts as a continuation character, + i.e., the next line is appended. Whitespace at the beginning of + continuation lines is not ignored. +\item + Each remaining line has the form: +\begin{alltt} + \var{variable}[.\var{progname}] [=] \var{value} +\end{alltt}% + where the \samp{=} and surrounding whitespace are optional. +\item + The \ttvar{variable} name may contain any character other + than whitespace, \samp{=}, or \samp{.}, but sticking to + \samp{A-Za-z\_} is safest. +\item + If \samp{.\var{progname}} is present, the definition only + applies if the program that is running is named + \texttt{\var{progname}} or \texttt{\var{progname}.exe}. This allows + different flavors of \TeX{} to have different search paths, for + example. +\item \var{value} may contain any characters except + \code{\%} and \samp{@}. The + \code{\$\var{var}.\var{prog}} feature is not available on the + right-hand side; instead, you must use an additional variable. A + \samp{;}\ in \var{value} is translated to \samp{:}\ if + running under Unix; this is useful to be able to have a single + \file{texmf.cnf} for Unix, \acro{MS-DOS} and Windows systems. +\item + All definitions are read before anything is expanded, so + variables can be referenced before they are defined. +\end{itemize} +A configuration file fragment illustrating most of these points is +\ifSingleColumn +shown below: + +\verbatiminput{examples/ex5.tex} +\else +shown in Figure~\ref{fig:config-sample}. +\fi + +\subsubsection{Path expansion} +\label{Path-expansion} + + +\KPS{} recognizes certain special characters and constructions in +search paths, similar to those available in Unix shells. As a +general example, the complex path, +\verb+~$USER/{foo,bar}//baz+, expands to all subdirectories under +directories \file{foo} and \file{bar} in \texttt{\$USER}'s home +directory that contain a directory or file \file{baz}. These +expansions are explained in the sections below. +%$ +\subsubsection{Default expansion} +\label{Default-expansion} + +\tolerance=2500 +If the highest-priority search path (see ``Path sources'' on +page~\pageref{Path-sources}) contains an \emph{extra colon} (i.e., +leading, trailing, or doubled), \KPS{} inserts at that point the +next-highest-prio\-rity search path that is defined. If that inserted +path has an extra colon, the same happens with the next highest. For +example, given an environment variable setting + +\tolerance=1500 + +\begin{alltt} +> \Ucom{setenv TEXINPUTS /home/karl:} +\end{alltt} +and a \code{TEXINPUTS} value from \file{texmf.cnf} of + +\begin{alltt} + .:\$TEXMF//tex +\end{alltt} +then the final value used for searching will be: + +\begin{alltt} + /home/karl:.:\$TEXMF//tex +\end{alltt} + +Since it would be useless to insert the default value in more than one +place, \KPS{} changes only one extra \samp{:}\ and leaves any others in +place. It checks first for a leading \samp{:}, then a trailing +\samp{:}, then a doubled \samp{:}. + +\subsubsection{Brace expansion} + +A useful feature is brace expansion, which means that, for instance, +\verb+v{a,b}w+ expands to \verb+vaw:vbw+. Nesting is allowed. +This can be used to implement multiple \TeX{} hierarchies, by +assigning a brace list to \code{\$TEXMF}. +For example, in \file{texmf.cnf}, you find +the following definition: +\begin{verbatim} + TEXMF = {$HOMETEXMF,$TEXMFLOCAL,!!$VARTEXMF,!!$TEXMFMAIN} +\end{verbatim} +Using this you can then write something like +\begin{verbatim} + TEXINPUTS = .;$TEXMF/tex// +\end{verbatim} +%$ +which means that, after looking in the current directory, the +\code{\$HOMETEXMF/tex}, \code{\$TEXMFLOCAL/tex}, \code{\$VARTEXMF/tex} +and \code{\$TEXMFMAIN/tex} trees \emph{only}) will be searched (the +last two use using \file{ls-R} data base files). It is a convenient +way for running two parallel \TeX{} structures, one ``frozen'' (on a +\CD, for instance) and the other being continuously updated with new +versions as they become available. By using the \code{\$TEXMF} +variable in all definitions, one is sure to always search the +up-to-date tree first. + +\subsubsection{Subdirectory expansion} +\label{Subdirectory-expansion} + +Two or more consecutive slashes in a path element following a directory +\var{d} is replaced by all subdirectories of \var{d}: first those +subdirectories directly under \var{d}, then the subsubdirectories under +those, and so on. At each level, the order in which the directories are +searched is \emph{unspecified}. + +If you specify any filename components after the \samp{//}, only +subdirectories with matching components are included. For example, +\samp{/a//b} expands into directories \file{/a/1/b}, \file{/a/2/b}, +\file{/a/1/1/b}, and so on, but not \file{/a/b/c} or \file{/a/1}. + +Multiple \samp{//} constructs in a path are possible, but +\samp{//} at the beginning of a path is ignored. + +\subsubsection{List of special characters and their meaning: a summary} + +The following list summarizes the special characters in \KPS{} +configuration files. + +% need a wider space for the item labels here. +\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} +\begin{ttdescription} +\item[\CODE{:}] Separator in path specification; at the beginning or + the end of a path it substitutes the default path expansion.\par +\item[\CODE{;}] Separator on non-Unix systems (acts like \code{:}). +\item[\CODE{\$}] Variable expansion. +\item[\CODE{\string~}] Represents the user's home directory. +\item[\CODE{\char`\{...\char`\}}] Brace expansion. +\item[\CODE{//}] Subdirectory expansion (can occur anywhere in + a path, except at its beginning). +\item[\CODE{\%}] Start of comment. +\item[\CODE{\bs}] Continuation character (allows multi-line entries). +\item[\CODE{!!}] Search \emph{only} database to locate file, \emph{do + not} search the disk. +\end{ttdescription} + + +\subsection{Filename databases} +\label{Filename-database} + +\KPS{} goes to some lengths to minimize disk accesses for searches. +Nevertheless, at installations with enough directories, searching each +possible directory for a given file can take an excessively long time +(this is especially true if many hundreds of font directories have to +be traversed.) Therefore, \KPS{} can use an externally-built plain text +``database'' file named \file{ls-R} that maps files to directories, +thus avoiding the need to exhaustively search the disk. + +A second database file \file{aliases} allows you to give additional +names to the files listed in \file{ls-R}. This can be helpful to +confirm to \acro{DOS} 8.3 filename conventions in source files. + +\subsubsection{The filename database} +\label{ls-R} + +As explained above, the name of the main filename database must be +\file{ls-R}. You can put one at the root of each \TeX{} hierarchy in +your installation that you wish to be searched (\code{\$TEXMF} by +default); most sites have only one hierarchy. \KPS{} looks for +\file{ls-R} files along the \code{TEXMFDBS} path. + +The recommended way to create and maintain \samp{ls-R} is to run the +\code{mktexlsr} script included with the distribution. It is invoked +by the various \samp{mktex}\dots\ scripts. In principle, this script +just runs the command +\begin{alltt} +cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R +\end{alltt} +presuming your system's \code{ls} produces the right output format +(\acro{GNU} \code{ls} is all right). To ensure that the database is +always up-to-date, it is easiest to rebuild it regularly via +\code{cron}, so that it is automatically updated when the installed +files change, such as after installing or updating a \LaTeX{} package. + +If a file is not found in the database, by default \KPS{} goes ahead +and searches the disk. If a particular path element begins with +\samp{!!}, however, \emph{only} the database will be searched for that +element, never the disk. + + +\subsubsection{kpsewhich: Standalone path searching} +\label{Invoking-kpsewhich} + +The \texttt{kpsewhich} program exercises path searching independent of any +particular application. This can be useful as a sort of \code{find} +program to locate files in \TeX{} hierarchies (this is used heavily in +the distributed \samp{mktex}\dots\ scripts). + +\begin{alltt} +> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} +\end{alltt} +The options specified in \ttvar{option} start with either \samp{-} +or \samp{-{}-}, and any unambiguous abbreviation is accepted. + +\KPS{} looks up each non-option argument on the command line as a +filename, and returns the first file found. There is no option to +return all the files with a particular name (you can run the Unix +\samp{find} utility for that). + +The more important options are described next. + +\begin{ttdescription} +\item[\texttt{-{}-dpi=\var{num}}]\mbox{} + Set the resolution to \ttvar{num}; this only affects \samp{gf} + and \samp{pk} lookups. \samp{-D} is a synonym, for compatibility + with \cmdname{dvips}. Default is 600. + +\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ + Set the format for lookup to \ttvar{name}. By default, the + format is guessed from the filename. For formats which do not have + an associated unambiguous suffix, such as \MP{} support files and + \cmdname{dvips} configuration files, you have to specify the name as + found in the first column of table~\ref{tab:kpathsea}, which lists + currently recognized names, a description, possible file extensions, + and associated environment variables. +\end{ttdescription} + + +\def\KpathKey#1#2#3#4#5{% name, number, description, variables, + % suffixes +\SetRowColor#1 & #3 & #4 & #5\\} +\def\HEAD#1{\multicolumn{1}{l}{\emph{#1}}} +% +\begin{small} +% a footnoterule immediately under a bottom-of-page rule looks dead +% silly, so we suppress it +\renewcommand\footnoterule{\relax} +% +\begin{longtable}{@{}% + >{\ttfamily}P{.16\textwidth}% Col.1 + P{.3\textwidth}% Col 2 + >{\ttfamily\footnotesize}P{.29\textwidth}% Col 3 + >{\ttfamily}P{.14\textwidth}% Col 4 +@{}} +\caption{Kpathsea file types.}\label{tab:kpathsea}\\ +\emph{Name} & \HEAD{Description} & \HEAD{Variables} +& \HEAD{Suffixes}\\ +\hline +\endfirsthead +\multicolumn{3}{l}{Kpathsea file types \emph{continued}}\\ +\emph{Name} & \HEAD{Description} & \HEAD{Variables} +& \HEAD{Suffixes}\\ +\hline +\noalign{\vspace{2pt}} +\endhead +\mbox{}\\ +\hline +\endfoot +\KpathKey + {afm} + {4} + {Adobe font metrics} + {AFMFONTS} + {.afm} +\KpathKey + {base} + {5} + {Metafont memory dump} + {MFBASES, TEXMFINI} + {.base} +\KpathKey + {bib} + {6} + {\BibTeX{} bibliography source} + {BIBINPUTS, TEXBIB} + {.bib} +\KpathKey + {} + {2} + {bitmap fonts} + {GLYPHFONTS, TEXFONTS} + {} +\KpathKey + {bst} + {7} + {\BibTeX{} style files} + {BSTINPUTS} + {.bst} +\KpathKey + {cnf} + {8} + {Runtime configuration files} + {TEXMFCNF} + {.cnf} +\KpathKey + {dvips config} + {34} + {\textsf{dvips} configuration files, e.g., \file{config.ps}} + {TEXCONFIG} + {} +\KpathKey + {enc} + {34} + {Font encoding files} + {ENCFONTS} + {.enc} +\KpathKey + {fmt} + {10} + {\TeX{} memory dump} + {TEXFORMATS, TEXMFINI} + {.fmt, .efmt, .efm} +\KpathKey + {gf} + {0} + {generic font bitmap} + {GFFONTS} + {.gf} +\KpathKey + {graphic/figure} + {25} + {Encapsulated \PS{} figures} + {TEXPICTS, TEXINPUTS} + {.eps, .epsi} +\KpathKey + {ist} + {35} + {\textsf{makeindex} style files} + {TEXINDEXSTYLE, INDEXSTYLE} + {.ist} +\KpathKey + {ls-R} + {9} + {Filename databases} + {TEXMFDBS} + {} +\KpathKey + {map} + {11} + {Fontmaps} + {TEXFONTMAPS} + {.map} +\KpathKey + {mem} + {12} + {MetaPost memory dump} + {MPMEMS, TEXMFINI} + {.mem} +\KpathKey + {mf} + {13} + {Metafont source} + {MFINPUTS} + {.mf} +\KpathKey + {mfpool} + {14} + {Metafont program strings} + {MFPOOL, TEXMFINI} + {.pool} +\KpathKey + {mft} + {15} + {MFT style file} + {MFTINPUTS} + {.mft} +\KpathKey + {} + {41} + {miscellaneous fonts} + {MISCFONTS} + {} +\KpathKey + {mp} + {16} + {MetaPost source} + {MPINPUTS} + {.mp} +\KpathKey + {mppool} + {17} + {MetaPost program strings} + {MPPOOL, TEXMFINI} + {.pool} +\KpathKey + {MetaPost support} + {18} + {MetaPost support files, used by DMP} + {MPSUPPORT} + {} +\KpathKey + {ocp} + {19} + {\OMEGA{} compiled process files} + {OCPINPUTS} + {.ocp} +\KpathKey + {ofm} + {20} + {\OMEGA{} font metrics} + {OFMFONTS, TEXFONTS} + {.ofm, .tfm} +\KpathKey + {opl} + {21} + {\OMEGA{} property lists} + {OPLFONTS, TEXFONTS} + {.opl} +\KpathKey + {otp} + {22} + {\OMEGA{} translation process files} + {OTPINPUTS} + {.otp} +\KpathKey + {ovf} + {23} + {\OMEGA{} virtual fonts} + {OVFFONTS, TEXFONTS} + {.ovf} +\KpathKey + {ovp} + {24} + {\OMEGA{} virtual property lists} + {OVPFONTS, TEXFONTS} + {.ovp} +\KpathKey + {pdftex config} + {18} + {\textsf{pdftex} configuration files} + {PDFTEXCONFIG} + {} +\KpathKey + {pk} + {1} + {packed bitmap fonts} + {\var{program}FONTS \textrm{(\texttt{\var{program}} being + \textsmaller{\cmdname{XDVI}}, + etc.)}, PKFONTS, TEXPKS, GLYPHFONTS, TEXFONTS} + {.pk} +\KpathKey + {\PS{} header} + {30} + {downloadable \PS{}} + {TEXPSHEADERS, PSHEADERS} + {.pro, .enc} +\KpathKey + {tex} + {26} + {\TeX{} source} + {TEXINPUTS} + {.tex, .cls, .sty, .clo, .def} +\KpathKey + {texmfscripts} + {20} + {Scripts distributed in the \file{texmf} tree} + {TEXMFSCRIPTS} + {} +\KpathKey + {TeX system documentation} + {27} + {Documentation files for the \TeX{} system} + {TEXDOCS} + {} +\KpathKey + {TeX system sources} + {29} + {Source files for the \TeX{} system} + {TEXSOURCES} + {} +\KpathKey + {texpool} + {28} + {\TeX{} program strings} + {TEXPOOL, TEXMFINI} + {.pool} +\KpathKey + {tfm} + {3} + {\TeX{} font metrics} + {TFMFONTS, TEXFONTS} + {.tfm} +\KpathKey + {Troff fonts} + {31} + {Troff fonts, used by DMP} + {TRFONTS} + {} +\KpathKey + {truetype fonts} + {36} + {TrueType outline fonts} + {TTFONTS} + {.ttf, .ttc} +\KpathKey + {Type~1 fonts} + {32} + {Type 1 \PS{} outline fonts} + {T1FONTS, T1INPUTS, TEXPSHEADERS, DVIPSHEADERS} + {.pfa, .pfb} +\KpathKey + {type42 fonts} + {37} + {Type 42 \PS{} outline fonts} + {T42FONTS} + {} +\KpathKey + {vf} + {33} + {virtual fonts} + {VFFONTS, TEXFONTS} + {.vf} +\KpathKey + {web2c files} + {38} + {\Webc{} support files} + {WEB2C} + {} +\KpathKey + {other text files} + {39} + {text files used by `\textsf{foo}'} + {FOOINPUTS} + {} +\KpathKey + {other binary files} + {40} + {binary files used by `\textsf{foo}'} + {FOOINPUTS} + {} +\end{longtable} +\end{small} + + +\begin{multicols}{2} + + The last two entries in table~\ref{tab:kpathsea} are special + cases, where the paths and environment variables depend on the name + of the program: the variable name is constructed by converting the + program name to upper case, and then appending \texttt{INPUTS}. + + The environment variables are set by default in the configuration + file \file{texmf.cnf}. It is only when you want to override one or + more of the values specified in that file that you might want to set + them explicitly in your execution environment. + + The \samp{-{}-format} and \samp{-{}-path} options are mutually + exclusive. + +\begin{ttdescription} + +\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ + Set the mode name to \ttvar{string}; this only affects \samp{gf} + and \samp{pk} lookups. No default: any mode will be found. +\item[\texttt{-{}-must-exist}]\mbox{}\\ + Do everything possible to find the files, notably including + searching the disk. By default, only the \file{ls-R} database is + checked, in the interest of efficiency. +\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ + Search along the path \ttvar{string} (colon-separated as usual), + instead of guessing the search path from the filename. \samp{//} and + all the usual expansions are supported. The options \samp{-{}-path} + and \samp{-{}-format} are mutually exclusive. +\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ + Set the program name to \texttt{\var{name}}. + This can affect the search paths via the \texttt{.\var{progname}} + feature. + The default is \cmdname{kpsewhich}. +\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ + shows the path used for file lookups of file type \texttt{\var{name}}. + Either a filename extension (\code{.pk}, \code{.vf}, etc.) or a + name can be used, just as with \samp{-{}-format} option. +\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ + sets the debugging options to \texttt{\var{num}}. +\end{ttdescription} + + +\subsubsection{Examples of use} +\label{SExamplesofuse} + +Let us now have a look at \KPS{} in action. Here's a straightforward search: + +\begin{alltt} +> \Ucom{kpsewhich article.cls} + /usr/local/texmf-dist/tex/latex/base/article.cls +\end{alltt} +We are looking for the file \file{article.cls}. Since the \samp{.cls} +suffix is unambiguous we do not need to specify that we want to look for a +file of type \optname{tex} (\TeX{} source file directories). We find it in +the subdirectory \file{tex/latex/base} below the \samp{texmf-dist} \TL\ +directory. Similarly, all of the following are found without problems +thanks to their unambiguous suffix. +\begin{alltt} +> \Ucom{kpsewhich array.sty} + /usr/local/texmf-dist/tex/latex/tools/array.sty +> \Ucom{kpsewhich latin1.def} + /usr/local/texmf-dist/tex/latex/base/latin1.def +> \Ucom{kpsewhich size10.clo} + /usr/local/texmf-dist/tex/latex/base/size10.clo +> \Ucom{kpsewhich small2e.tex} + /usr/local/texmf-dist/tex/latex/base/small2e.tex +> \Ucom{kpsewhich tugboat.bib} + /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib +\end{alltt} + +That last is a \BibTeX{} bibliography database for \textsl{TUGBoat} articles. + +\begin{alltt} +> \Ucom{kpsewhich cmr10.pk} +\end{alltt} +Font bitmap glyph files of type \file{.pk} are used by display +programs like \cmdname{dvips} and \cmdname{xdvi}. Nothing is returned in +this case since there are no pre-generated Computer Modern \samp{.pk} +files in \TL{}\Dash the Type~1 variants are used by default. +\begin{alltt} +> \Ucom{kpsewhich wsuipa10.pk} +\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk +\else /usr/local/texmf-var/fonts/pk/ljfour/public/ +... wsuipa/wsuipa10.600pk +\fi\end{alltt} + +For these fonts (a phonetic alphabet from the University of Washington) +we had to generate \samp{.pk} files, and since the default \MF{} mode on +our installation is \texttt{ljfour} with a base resolution of 600\dpi{} +(dots per inch), this instantiation is returned. +\begin{alltt} +> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} +\end{alltt} +In this case, when specifying that we are interested in a resolution +of 300\dpi{} (\texttt{-dpi=300}) we see that no such font is available on +the system. A program like \cmdname{dvips} or \cmdname{xdvi} would +go off and actually build the required \texttt{.pk} files +using the script \cmdname{mktexpk}. + +Next we turn our attention to \cmdname{dvips}'s header and configuration +files. We first look at one of the commonly used files, the general +prolog \file{tex.pro} for \TeX{} support, before turning our attention +to the generic configuration file (\file{config.ps}) and the \PS{} font +map \file{psfonts.map}\Dash as of 2004, map and encoding files have +their own search paths and new location in \dirname{texmf} trees. As +the \samp{.ps} suffix is ambiguous we have to specify explicitly which +type we are considering (\optname{dvips config}) for the file +\texttt{config.ps}. +\begin{alltt} +> \Ucom{kpsewhich tex.pro} + /usr/local/texmf/dvips/base/tex.pro +> \Ucom{kpsewhich --format="dvips config" config.ps} + /usr/local/texmf/dvips/config/config.ps +> \Ucom{kpsewhich psfonts.map} + /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map +\end{alltt} + +We now take a closer look at the \acro{URW} Times \PS{} support +files. The prefix for these in the standard font naming scheme is +\samp{utm}. The first file we look at is the configuration file, +which contains the name of the map file: +\begin{alltt} +> \Ucom{kpsewhich --format="dvips config" config.utm} + /usr/local/texmf-dist/dvips/psnfss/config.utm +\end{alltt} +The contents of that file is +\begin{alltt} + p +utm.map +\end{alltt} +which points to the file \file{utm.map}, which we want to +locate next. +\begin{alltt} +> \Ucom{kpsewhich utm.map} + /usr/local/texmf-dist/fonts/map/dvips/times/utm.map +\end{alltt} +This map file defines the file names of the Type~1 \PS{} fonts in +the URW collection. Its contents look like (we only show part of the +lines): +\begin{alltt} +utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} +\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb +\else /usr/local/texmf-dist/fonts/type1/ +... urw/utm/utmr8a.pfb +\fi\end{alltt} + +It should be evident from these examples how you can easily locate the +whereabouts of a given file. This is especially important if you suspect +that the wrong version of a file is picked up somehow, since +\cmdname{kpsewhich} will show you the first file encountered. + +\subsubsection{Debugging actions} +\label{Debugging} + +Sometimes it is necessary to investigate how a program resolves file +references. To make this practical, \KPS{} offers various levels of +debugging output: + +\begin{ttdescription} +\item[\texttt{\ 1}] \texttt{stat} calls (disk lookups). When running + with an up-to-date \file{ls-R} database this should almost give no + output. +\item[\texttt{\ 2}] References to hash tables (such as \file{ls-R} + databases, map files, configuration files). +\item[\texttt{\ 4}] File open and close operations. +\item[\texttt{\ 8}] General path information for file types + searched by \KPS. This is useful to find out where a particular + path for the file was defined. +\item[\texttt{16}] Directory list for each path element (only relevant + for searches on disk). +\item[\texttt{32}] File searches. +\end{ttdescription} +A value of \texttt{-1} will set all the above options; in practice, +this is usually the most convenient. + +Similarly, with the \cmdname{dvips} program, by setting a combination of +debug switches, one can follow in detail where files are being picked up +from. Alternatively, when a file is not found, the debug trace shows in +which directories the program looks for the given file, so that one can +get an indication what the problem~is. + +Generally speaking, as most programs call the \KPS{} library +internally, one can select a debug option by using the +\envname{KPATHSEA\_DEBUG} environment variable, and setting it to (a +combination of) values as described in the above list. + +(Note for Windows users: it is not easy to redirect +all messages to a file in this system. For diagnostic purposes +you can temporarily \texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log}). + +Let us consider, as an example, a small \LaTeX{} source file, +\file{hello-world.tex}, which contains the following input. +\begin{verbatim} + \documentclass{article} + \begin{document} + Hello World! + \end{document} +\end{verbatim} +This little file only uses the font \file{cmr10}, so let us look +how \cmdname{dvips} prepares the \PS{} file (we want to use the Type~1 +version of the Computer Modern fonts, hence the option \texttt{-Pcms}). +\begin{alltt} +> \Ucom{dvips -d4100 hello-world -Pcms -o} +\end{alltt} +In this case we have combined \cmdname{dvips}'s debug class 4 (font +paths) with \KPS's path element expansion (see \cmdname{dvips} Reference +Manual, \OnCD{texmf/doc/html/dvips/dvips_toc.html}). +The output (slightly rearranged) appears in +Figure~\ref{fig:dvipsdbga}. +\begin{figure*}[tp] +\centering +\input{examples/ex6a.tex} +\caption{Finding configuration files}\label{fig:dvipsdbga} + +\bigskip + +\input{examples/ex6b.tex} +\caption{Finding the prolog file}\label{fig:dvipsdbgb} + +\bigskip + +\input{examples/ex6c.tex} +\caption{Finding the font file}\label{fig:dvipsdbgc} +\end{figure*} + +\cmdname{dvips} starts by locating its working files. First, +\file{texmf.cnf} is found, which gives the definitions of the search +paths for the other files, then the file database \file{ls-R} (to +optimize file searching) and the file \file{aliases}, which makes it +possible to declare several names (e.g., a short \acro{DOS}-like 8.3 and +a more natural longer version) for the same file. Then \cmdname{dvips} +goes on to find the generic configuration file \file{config.ps} +before looking for the customization file \file{.dvipsrc} (which, in +this case is \emph{not found}). Finally, \cmdname{dvips} locates the +config file for the Computer Modern \PS{} fonts \file{config.cms} +(this was initiated with the \texttt{-Pcms} option on the \cmdname{dvips} +command). This file contains the list of the map files which +define the relation between the \TeX{}, \PS{} and file system +names of the fonts. +\begin{alltt} +> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} + p +ams.map + p +cms.map + p +cmbkm.map + p +amsbkm.map +\end{alltt} +\cmdname{dvips} thus goes on to find all these files, plus the generic +map file \file{psfonts.map}, which is always loaded (it contains +declarations for commonly used \PS{} fonts; see the last part of +Section \ref{SExamplesofuse} for more details about \PS{} map +file handling). + +At this point \cmdname{dvips} identifies itself to the user: +\begin{alltt} +This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) +\end{alltt} +\ifSingleColumn +Then it goes on to look for the prolog file \file{texc.pro}: +\begin{alltt}\small +kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro +\end{alltt} +\else +Then it goes on to look for the prolog file \file{texc.pro} (see +Figure~\ref{fig:dvipsdbgb}). +\fi + +After having found the file in question, \cmdname{dvips} outputs +date and time, and informs us that it will generate the +file \file{hello-world.ps}, then that it needs the font file +\file{cmr10}, and that the latter is declared as ``resident'' (no +bitmaps needed): +\begin{alltt}\small +TeX output 1998.02.26:1204' -> hello-world.ps +Defining font () cmr10 at 10.0pt +Font cmr10 is resident. +\end{alltt} +Now the search is on for the file \file{cmr10.tfm}, which is found, +then a few more prolog files (not shown) are referenced, and finally +the Type~1 instance \file{cmr10.pfb} of the font is located and +included in the output file (see last line). +\begin{alltt}\small +kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, + path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: + /var/tex/fonts/tfm//). +kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm +kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, + ... + +kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb +[1] +\end{alltt} + +\subsection{Runtime options} + +Another useful feature of \Webc{} is its possibility to control a number +of memory parameters (in particular, array sizes) via the runtime file +\file{texmf.cnf} read by \KPS{}. The memory settings can be found in +Part 3 of that file in the \TL{} distribution. The more important +are: + +\begin{ttdescription} +\item[\texttt{main\_memory}] + Total words of memory available, for + \TeX{}, \MF{} and \MP. You must make a new format file for each + different setting. For instance, you could generate a ``huge'' + version of \TeX{}, and call the format file \texttt{hugetex.fmt}. + Using the standard way of specifying the program name used by \KPS{}, + the particular value of the \texttt{main\_memory} variable will then + be read from \file{texmf.cnf}. + etc.). +\item[\texttt{extra\_mem\_bot}] + Extra space for ``large'' \TeX{} data structures: + boxes, glue, breakpoints, etc. Especially useful if you use + \PiCTeX{}. +\item[\texttt{font\_mem\_size}] + Number of words for font information available for \TeX. This + is more or less the total size of all TFM files read. +\item[\texttt{hash\_extra}] + Additional space for the hash table of control sequence names. + Approximately 10,000 control sequences can be stored in the main + hash table; if you have a large book with numerous cross-references, + this might not be enough. The default value of + \texttt{hash\_extra} is \texttt{50000}. +\end{ttdescription} + +\noindent Of course, this facility is no substitute for truly dynamic +arrays and memory allocation, but since these are extremely difficult to +implement in the present \TeX{} source, these runtime parameters provide +a practical compromise allowing some flexibility. + + +\section{Building on a new Unix platform} + +If you have a platform for which executables are not included, you will +need to compile \TeX{} and friends. This is not as hard as it +sounds. What you need is all in the directory \texttt{source} in the +distribution. + +\subsection{Prerequisites} + +You will need at least 100 megabytes of disk space to compile all of +\TeX{} and its support programs. You'll also need an \acro{ANSI} C +compiler, a \cmdname{make} utility, a lexical scanner, and a parser +generator. We recommend the \acro{GNU} version of these programs +(\cmdname{gcc}, \acro{GNU} \cmdname{make}, \cmdname{m4}, \cmdname{flex}, +\cmdname{bison}). You may be able to work with other C compilers and +\cmdname{make} programs, but you will need a good understanding of +building Unix programs to sort out problems. + +Also, the command \texttt{uname} must return a sensible value. + + +\subsection{Configuration} + +To begin, perform a normal installation of \TL{} to your disk (see +section~\ref{sec:unix-install-disk} on +\p.\pageref{sec:unix-install-disk}). You may wish to skip installing +all of the prebuilt binaries. + +Then, unpack the source from the compressed \texttt{tar} file in the +directory \dirname{source} to your disk and change directory to where +you placed it. + +Next, run \cmdname{configure} with a command line like this: +\begin{alltt} +> \Ucom{sh configure -prefix=/usr/local/TeX} +\end{alltt} + +The \optname{-prefix} directory is the one where you installed the +support tree; the directory layout will be as follows (where \$TEXDIR +stands for the directory you chose): + +\noindent +\begin{tabular}{>{\ttfamily}ll@{}} + \dirname{$TEXDIR/share/texmf} & main tree with fonts,\\ + & \qquad macros, etc\\ + \dirname{$TEXDIR/man} & Unix manual pages\\ + \dirname{$TEXDIR/info} & \acro{GNU} style Info manuals\\ + \dirname{$TEXDIR/bin/$PLATFORM} & binaries\\ +\end{tabular} +%$ + +If you want to leave out the \dirname{$PLATFORM} directory level, +i.e., put the binaries directly into \dirname{$TEXDIR/bin}, specify +the \verb|--disable-multiplatform| option to \cmdname{configure}. + +Have a look at the output of \verb|./configure --help| for more +options you can use. For example, you can skip building of \OMEGA{} and +\eTeX{}. + + +\subsection{Running \cmdname{make}} + +Make sure the shell variable or option \texttt{noclobber} is not set. +Then, run the main \cmdname{make} like this: +\begin{alltt} +> \Ucom{make world} +\end{alltt} +and relax\ldots + +Alternatively, you want to log all the output, as in: +\begin{alltt} +> \Ucom{sh -c "make world >world.log 2>\&1" \&} +\end{alltt} + +Before you believe that everything went ok, please check the log file +for errors: \acro{GNU} \cmdname{make} always uses the string \samp{***} +whenever a command fails. Also, check if all the programs were built: + +\begin{alltt} +> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} +> \Ucom{ls | wc} +\end{alltt} +The result should be over 200 (you can check the exact number with the +\dirname{bin} directory contents in the distribution). + +If you need special privileges for \texttt{make install}, you can +separate the \samp{make world} into two different runs, like this: +\begin{alltt} +> \Ucom{make all} +> \Ucom{su} +> \Ucom{make install strip} +\end{alltt} + +After you've installed your new binaries, you should follow the normal +post-installation procedures, given in section~\ref{sec:postinstall} +(\p.\pageref{sec:postinstall}). + +Also, if you'd like to make your binaries available to others, please +contact us. We'll be happy to put them on the \TL\ web pages. + + +\section{Acknowledgements} + +\TL{} is a joint effort by virtually all of the \TeX{} user groups. +This edition of \TL{} was overseen by Sebastian Rahtz and Karl Berry. +The other principal contributors are listed below. + +\begin{itemize*} + +\item The German-speaking \TeX{} Users (\acro{DANTE} e.V.), who provide +the hardware for the \TL{} source repository; and Rainer Sch\"opf and +Reinhard Zierke who look after it. \acro{DANTE} officers Volker Schaa +and Klaus Hoeppner coordinated production with the Lehmann's Bookstore +(\url{http://www.lob.de}). + +\item The Perforce corporation (\url{http://www.perforce.com}), for providing +a free copy of their excellent change management system, which we used +to manage the \TL{} sources. + +\item Peter Breitenlohner and the \eTeX\ team for the stable foundation +of future \TeX's. + +\item Thomas Esser, without whose marvelous \teTeX{} package \TL{} +would certainly not exist, and whose continual help makes it a better +product. + +\item Michel Goossens, who co-authored the original documentation. + +\item Eitan Gurari, whose \TeX4ht was used to create the \HTML{} +version of this documentation, and who worked tirelessly to improve +it at short notice. + +\item Hans Hagen, for major testing and making the \ConTeXt\ format +conform to \TL's needs. + +\item \Thanh, Martin Schr\"oder, and the pdf\TeX\ team for continuing +enhancements of \TeX's abilities. + +\item Petr Olsak, who coordinated and checked all the Czech and Slovak +material very carefully. + +\item Fabrice Popineau, for the Windows side of \TL{} and devising the +new directory layout. + +\item Staszek Wawrykiewicz, the principal tester for all of \TL{}, and +coordinator of the Polish contributions. + +\item Olaf Weber, for his patient assembly and maintenance of Web2C, +upon which all else depends. + +\item Gerben Wierda, for creating and maintaining the \MacOSX\ support, +and much integration and testing. + +\item Graham Williams, on whose work the catalogue of packages depends. + +\end{itemize*} + +Builders of the binaries: +Tigran Aivazian (\pkgname{x86\_64-linux}), +Manfred Lotz (\pkgname{i386-freebsd}), +Maksym Polyakov (\pkgname{sparc-solaris}), +Fabrice Popineau (\pkgname{win32}), +Norbert Preining (\pkgname{alpha-linux}), +Vladimir Volovich (\pkgname{powerpc-aix} and \pkgname{sparc64-linux}), +Staszek Wawrykiewicz (\pkgname{i386-linux}), +Olaf Weber (\pkgname{mips-irix}), +Gerben Wierda (\pkgname{powerpc-darwin}). + +Documentation and translation updates: +Karl Berry (English), +Daniel Flipo \& Fabrice Popineau (French), +G\"unter Partosch \& Hartmut Henkel (German), +Petr Sojka \& Jan Busa (Czech\slash Slovak), +Boris Veytsman (Russian), +Staszek Wawrykiewicz (Polish). + +Of course the most important acknowledgement must go to Donald Knuth, first +for inventing \TeX, and then for giving it to the world. + + +\section{Release history} +\label{sec:history} + +\subsection{Past} + +Discussion began in late 1993 when the Dutch \TeX{} Users Group was +starting work on its 4All\TeX{} \CD{} for \acro{MS-DOS} users, and it +was hoped at that time to issue a single, rational, \CD{} for all +systems. This was too ambitious a target for the time, but it did spawn +not only the very successful 4All\TeX{} \CD{}, but also the \acro{TUG} +Technical Council working group on a \emph{\TeX{} Directory Structure} +(\url{http://tug.org/tds}), which specified how to create consistent and +manageable collections of \TeX{} support files. A complete draft of the +\TDS{} was published in the December 1995 issue of \textsl{TUGboat}, and +it was clear from an early stage that one desirable product would be a +model structure on \CD{}. The distribution you now have is a very direct +result of the working group's deliberations. It was also clear that the +success of the 4All\TeX{} \CD{} showed that Unix users would benefit +from a similarly easy system, and this is the other main strand of +\TL. + +We first undertook to make a new Unix-based \TDS{} \CD{} in the autumn +of 1995, and quickly identified Thomas Esser's \teTeX{} as the ideal +setup, as it already had multi-platform support and was built with +portability across file systems in mind. Thomas agreed to help, and work +began seriously at the start of 1996. The first edition was released in +May 1996. At the start of 1997, Karl Berry completed a major new release +of Web2c, which included nearly all the features which Thomas Esser had +added in \teTeX, and we decided to base the 2nd edition of the \CD{} on +the standard \Webc, with the addition of \teTeX's \texttt{texconfig} +script. The 3rd edition of the \CD{} was based on a major revision of +\Webc, 7.2, by Olaf Weber; at the same time, a new revision of \teTeX +was being made, and \TL{} included almost all of its features. The +4th edition followed the same pattern, using a new version of \teTeX, +and a new release of \Webc{} (7.3). The system now included a complete +Windows setup. + +For the 5th edition (March 2000) many parts of the \CD{} were revised +and checked, updating hundreds of packages. Package details were stored +in XML files. But the major change for \TeX\ Live 5 was that all +non-free software was removed. Everything in \TL{} is now intended +to be compatible with the Debian Free Software Guidelines +(\url{http://www.debian.org/intro/free}); we have done our best to check +the license conditions of all packages, but we would very much +appreciate hearing of any mistakes. + +The 6th edition (July 2001) had much more material updated. The major +change was a new install concept: the user could select a more exact set +of needed collections. Language-related collections were completely +reorganized, so selecting any of them installs not only macros, fonts, +etc., but also prepares an appropriate \texttt{language.dat}. + +The 7th edition of 2002 had the notable addition of \MacOSX{} support, +and the usual myriad of updates to all sorts of packages and +programs. An important goal was integration of the source back with +\teTeX, to correct the drift apart in versions~5 and~6. + +In 2003, with the continuing flood of updates and additions, we found +that \TL{} had grown so large it could no longer be contained on a +single \CD, so we split it into three different distributions (see +section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}). In +addition: + +\begin{itemize*} +\item At the request of the \LaTeX{} team, we changed the standard + \cmdname{latex} and \cmdname{pdflatex} commands to now use \eTeX{} (see + \p.\pageref{text:etex}). +\item The new Latin Modern fonts were included (and are recommended). +\item Support for Alpha \acro{OSF} was removed + (\acro{HPUX} support was removed previously), since no one had (or + volunteered) hardware available on which to compile new binaries. +\item Windows setup was substantially changed; for the first time + an integrated environment based on XEmacs was introduced. +\item Important supplementary programs for Windows + (Perl, Ghost\-script, Image\-Magick, Ispell) are now installed + in the \TL{} installation directory. +\item Font map files used by \cmdname{dvips}, \cmdname{dvipdfm} + and \cmdname{pdftex} are now generated by the new program + \cmdname{updmap} and installed into \dirname{texmf/fonts/map}. +\item \TeX{}, \MF{}, and \MP{} now, by default, output most input + characters (32 and above) as themselves in output (e.g., + \verb|\write|) files, + log files, and the terminal, i.e., \emph{not} translated using the + \verb|^^| notation. In \TL{}~7, this translation was + dependent on the system locale settings; now, locale settings do + not influence the \TeX{} programs' behavior. If for some reason + you need the \verb|^^| output, rename the file + \verb|texmf/web2c/cp8bit.tcx|. (Future releases will have cleaner + ways to control this.) +\item This documentation was substantially revised. +\item Finally, since the edition numbers had grown unwieldy, + the version is now simply identified by the year: \TL{} 2003. +\end{itemize*} + +\subsection{Present} +\label{tlcurrent} + +2004 saw the usual huge number of updates to packages and programs. +Here are the most notable changes, including one important backward +incompatibility: + +\begin{itemize} + +\item If you have locally-installed fonts which use their own +\filename{.map} or (much less likely) \filename{.enc} support files, you +may need to move those support files. + +\filename{.map} files are now searched for in subdirectories of +\dirname{fonts/map} only (in each \filename{texmf} tree), along the +\envname{TEXFONTMAPS} path. Similarly, \filename{.enc} files are now +searched for in subdirectories of \dirname{fonts/enc} only, along the +\envname{ENCFONTS} path. \cmdname{updmap} will attempt to warn about +problematic files. + +For methods of handling this and other information, please see +\url{http://tug.org/texlive/mapenc.html}. + +\item The \TK\ has been expanded with the addition of a \MIKTEX-based +installable \CD, for those who prefer that implementation to Web2C. +See section~\ref{sec:struct-tl} (\p.\pageref{sec:struct-tl}). + +\item Within \TL, the single large \dirname{texmf} tree of previous +releases has been replaced by three: \dirname{texmf}, +\dirname{texmf-dist}, and \dirname{texmf-doc}. See +section~\ref{sec:tld} (\p.\pageref{sec:tld}), and the \filename{README} +files for each. + +\item All \TeX-related input files are now collected in +the \dirname{tex} subdirectory of \dirname{texmf*} trees, rather than +having separate sibling directories \dirname{tex}, \dirname{etex}, +\dirname{pdftex}, \dirname{pdfetex}, etc. See +\CDref{texmf-doc/doc/english/tds/tds.html\#Extensions} +{\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}. + +\item Helper scripts (not meant to be invoked by users) are now located +in a new \dirname{scripts} directory of \dirname{texmf*} trees, and +searched for via \verb|kpsewhich -format=texmfscripts|. So if you have +programs which call such scripts, they'll need to be adjusted. See +\CDref{texmf-doc/doc/english/tds/tds.html\#Scripts} +{\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}. + +\item Almost all formats leave most characters printable as +themselves via the ``translation file'' \filename{cp227.tcx}, instead of +translating them with the \verb|^^| notation. Specifically, characters +at positions 32--256, plus tab, vertical tab, and form feed are +considered printable and not translated. The exceptions are plain \TeX\ +(only 32--126 printable), \ConTeXt\ (0--255 printable), and the +\OMEGA-related formats. This default behavior is almost the same as in +\TL\,2003, but it's implemented more cleanly, with more possibilities +for customization. See \CDref{texmf/doc/web2c/web2c.html\#TCX-files} +{\texttt{texmf/doc/web2c/web2c.html\#TCX-files}}. +(By the way, with Unicode input, \TeX\ may output partial character +sequences when showing error contexts, since it is byte-oriented.) + +\item \textsf{pdfetex} is now the default engine for all formats +except (plain) \textsf{tex} itself. (Of course it generates \acro{DVI} +when run as \textsf{latex}, etc.) This means, among other things, that +the microtypographic features of \textsf{pdftex} are available in +\LaTeX, \ConTeXt, etc., as well as the \eTeX\ features +(\OnCD{texmf-dist/doc/etex/base/}). + +It also means it's \emph{more important than ever} to use the +\pkgname{ifpdf} package (works with both plain and \LaTeX) or equivalent +code, because simply testing whether \cs{pdfoutput} or some other +primitive is defined is not a reliable way to determine if \acro{PDF} +output is being generated. We made this backward compatible as best we +could this year, but next year, \cs{pdfoutput} may be defined even when +\acro{DVI} is being written. + +\item pdf\TeX\ (\url{http://pdftex.org}) has many new features: + + \begin{itemize*} + + \item \cs{pdfmapfile} and \cs{pdfmapline} provide font map support + from within a document. + + \item Microtypographic font expansion can be used more easily.\\ + \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} + + \item All parameters previously set through the special configuration + file \filename{pdftex.cfg} must now be set through primitives, + typically in \filename{pdftexconfig.tex}; \filename{pdftex.cfg} is no + longer supported. Any extant \filename{.fmt} files must be redumped + when \filename{pdftexconfig.tex} is changed. + + \item See the pdf\TeX\ manual for more: \OnCD{texmf/doc/pdftex/manual}. + + \end{itemize*} + +\item The \cs{input} primitive in \cmdname{tex} (and \cmdname{mf} and +\cmdname{mpost}) now accepts double quotes containing spaces and other +special characters. Typical examples: +\begin{verbatim} +\input "filename with spaces" % plain +\input{"filename with spaces"} % latex +\end{verbatim} +See the Web2C manual for more: \OnCD{texmf/doc/web2c}. + +\item enc\TeX\ support is now included within Web2C and consequently all +\TeX\ programs, via the \optname{-enc} option\Dash \emph{only when +formats are built}. enc\TeX\ supports general re-encoding of input and +output, enabling full support of Unicode (in \acro{UTF}-8). See +\OnCD{texmf-dist/doc/generic/enctex/} and +\url{http://www.olsak.net/enctex.html}. + +\item Aleph, a new engine combining \eTeX\ and \OMEGA, is available. +A little information is available in \OnCD{texmf-dist/doc/aleph/base} +and \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph}. The +\LaTeX-based format for Aleph is named \textsf{lamed}. + +\item The latest \LaTeX\ release has a new version of the +\acro{LPPL}\Dash now officially a Debian-approved license. Assorted +other updates, see the \filename{ltnews} files in +\OnCD{texmf-dist/doc/latex/base}. + +\item \cmdname{dvipng}, a new program for converting \acro{DVI} to +\acro{PNG} image files, is included. See \OnCD{texmf/doc/man/man1/dvipng.1}. + +\item We reduced the \pkgname{cbgreek} package to a ``medium'' sized set +of fonts, with the assent and advice of the author (Claudio Beccari). +The excised fonts are the invisible, outline, and transparency ones, +which are relatively rarely used, and we needed the space. The full set +is of course available from \acro{CTAN} +(\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). + +\item \cmdname{oxdvi} has been removed; just use \cmdname{xdvi}. + +\item The \cmdname{ini} and \cmdname{vir} commands (links) for +\cmdname{tex}, \cmdname{mf}, and \cmdname{mpost} are no longer created, +such as \cmdname{initex}. The \cmdname{ini} functionality has been +available through the command-line option \optname{-ini} for years now. + +\item \textsf{i386-openbsd} platform support was removed. Since the +\pkgname{tetex} package in the \acro{BSD} Ports system is available, and +\acro{GNU/}Linux and Free\acro{BSD} binaries were available, it seemed +volunteer time could be better spent elsewhere. + +\item On \textsf{sparc-solaris} (at least), you may have to set the +\envname{LD\_LIBRARY\_PATH} environment variable to run the +\pkgname{t1utils} programs. This is because they are compiled with C++, +and there is no standard location for the runtime libraries. (This is +not new in 2004, but wasn't previously documented.) Similarly, on +\textsf{mips-irix}, the \acro{MIPS}pro 7.4 runtimes are required. + +\end{itemize} + + +\subsection{Future} + +\emph{\TL{} is not perfect!} (And never will be.) We intend to +continue to release new versions yearly, and would like to provide more +help material, more utilities, more installation programs, and (of +course) an ever-improved and checked tree of macros and fonts. This work +is all done by hard-pressed volunteers in their limited spare time, and +a great deal remains to be done. If you can help, don't hesitate to put +your name forward! + +Please send corrections, suggestions, and offers of help to:\hfill\null +\begin{quote} +Sebastian Rahtz \ / \ 7 Stratfield Road \ / \ Oxford OX2 7BG \ / \ UK \\ +\email{tex-live@tug.org} \\ +\url{http://tug.org/texlive} +\end{quote} + +\medskip +\noindent \textsl{Happy \TeX ing!} + +\end{multicols} +\end{document} diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/live-2005.tex b/Master/texmf/doc/texlive/source/texlive-en/archive/live-2005.tex new file mode 100644 index 00000000000..5b525535c63 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/live-2005.tex @@ -0,0 +1,3174 @@ +% $Id: live.tex 1513 2006-02-13 00:22:35Z karl $ +% TeX Live documentation. Originally written by Sebastian Rahtz and +% Michel Goossens, now maintained by Karl Berry and others. +% Public domain. +% +\documentclass{article} +\let\tldocenglish=1 % for live4ht.cfg +\usepackage{tex-live} +\begin{document} + +\title{% + {\huge \textit{The \protect\TL{} Guide}\\\strut} + {\LARGE \textsf{\TK{} 2005}} +} + +\author{Sebastian Rahtz \& Karl Berry, editors \\[3mm] + \url{http://tug.org/texlive/} + } + +\date{October 2005} + +\maketitle + +\begin{multicols}{2} +\tableofcontents +\listoftables +\end{multicols} + +\section{Introduction} +\label{sec:intro} + +This document describes the main features of the \TL{} software +distribution\Dash \TeX{} and friends for \acro{GNU}/Linux and other Unix +flavors, \MacOSX, and (32-bit) Windows systems. (Warning: it is not +especially useful for older Mac or \acro{MS-DOS} systems.) + +\TL{} includes executables for \TeX{}, \LaTeXe{}, \ConTeXt, \MF, \MP, +\BibTeX{} and many other programs; an extensive collection of macros, +fonts and documentation; and support for typesetting in many different +scripts from around the world. It is part of the even larger \TK{} +(briefly described below in section~\ref{sec:struct-tl}, +\p.\pageref{sec:struct-tl}). Both are cooperative efforts by the \TeX\ +user groups. + +For newer versions of the packages included here, please check +\acro{CTAN}: \url{http://www.ctan.org}. + +For a brief summary of the major changes in this edition of \TL{}, +see the end of the document, section~\ref{sec:history} +(\p.\pageref{sec:history}). + + +\subsection{Basic usage of \protect\TL{}} +\label{sec:basic} + +You can use \TL{} in three principal ways: + +\begin{enumerate} + +\item You can run \TL{} directly from the \pkgname{live} \DVD +(see section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}). +This takes almost no disk space, and gives you immediate access to +everything in \TL{}. Of course performance will be worse than running +on local disk, but you may well find it useful. + +\item You can install all or part of \TL{} to a local disk, from either +the \DVD\ or the \pkgname{inst} \acro{CD}. This is the most common use +of \TL. You will need (approximately) 100 megabytes for the most +minimal system, and upwards of 1.3 gigabytes for a full system. + +\item You can integrate a particular package or collection into your +existing \TeX{} system, either a \TL{} system you installed +earlier, or a different system. + +\end{enumerate} + +\noindent All of these are described in detail in the \acro{OS}-specific +installation sections following, but here is a quick start: + +\begin{itemize*} + +\item The main installation script for Unix and \MacOSX{} is +\texttt{install-tl.sh}. + +\item The single package installation script is \texttt{install-pkg.sh}. + +\item The installation program for Windows is \texttt{tlpmgui.exe}. +It can be used also for adding or removing the packages. +See section~\ref{sec:win-install} below for more information. + +\end{itemize*} + + +\subsection{Getting help} +\label{sec:help} + +The \TeX{} community is both active and friendly, and virtually all +serious questions end up getting answered. However, the support is +informal, done by volunteers and casual readers, so it's especially +important that you do your homework before asking. (If you prefer +guaranteed commercial support, you can forego \TL{} completely and +purchase a vendor's system; \url{http://tug.org/interest.html#vendors} +has a list.) + +Here is a list of resources, approximately in the order we recommend +using them: + +\begin{description} +\item [Getting Started] If you are new to \TeX, the web page +\url{http://tug.org/begin.html} gives a brief introduction to the system. + +\item [\TeX{} \acro{FAQ}] The \TeX{} \acro{FAQ} is a huge compendium of +answers to all sorts of questions, from the most basic to the most +arcane. It is included on \TL{} in \OnCD{texmf-doc/doc/english/FAQ-en}, and is +available on the Internet through \url{http://www.tex.ac.uk/faq}. +Please check here first. + +\item [\TeX{} Catalogue] If you are looking for a specific package, +font, program, etc., the \TeX{} Catalogue is the place to look. It is a +huge collection of all \TeX{}-related items. See +\OnCD{texmf-doc/doc/english/catalogue}, or +\url{http://www.ctan.org/tex-archive/help/Catalogue}. + +\item [\TeX{} Web Resources] The web page +\url{http://tug.org/interest.html} has many \TeX{}-related links, in +particular for numerous books, manuals, and articles on all aspects of +the system. + +\item [support archives] The two principal support forums are the +Usenet newsgroup \url{news:comp.text.tex} and the mailing list +\email{texhax@tug.org}. Their archives have years of past +questions and answers for your searching pleasure, via +\url{http://groups.google.com/groups?group=comp.text.tex} and +\url{http://tug.org/mail-archives/texhax}, respectively. And a general web +search, for example on \url{http://google.com}, never hurts. + +\item [asking questions] If you cannot find an answer, you can post to +\dirname{comp.text.tex} through Google or your newsreader, or to +\email{texhax@tug.org} through email. But before you post, +\emph{please} read this \acro{FAQ} entry on asking questions in such a +way that you're most likely to get an answer: +\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. + +\item [\TL{} support] If you want to report a bug or have +suggestions or comments on the \TL{} distribution, installation, or +documentation, the mailing list is \email{tex-live@tug.org}. However, +if your question is about how to use a particular program included in +\TL{}, you are better off writing to that program's maintainer or +mailing list. + +\end{description} + +The other side of the coin is helping others who have questions. Both +\dirname{comp.text.tex} and \code{texhax} are open to anyone, so feel +free to join, start reading, and help out where you can. Welcome to +\TeX{}! + + +% don't use \TL so the \uppercase in the headline works. Also so +% tex4ht ends up with the right TeX. Likewise the \protect's. +\section{Structure of \protect\TeX\protect\ Live} +\label{sec:struct-tl} + +This section describes the structure and contents of \TL{} and the +\TK{} of which it is a part. + +\subsection{Multiple distributions: \protect\pkgname{live}, + \protect\pkgname{inst}, + \protect\pkgname{protext}} +\label{sec:multiple-dist} + +Space limitations of \acro{CD-ROM} format have forced us to divide +\TK{} into several distributions, as follows. + +\begin{description} + +\item [live] A complete system on \acro{DVD}; it is too large +for \acro{CD}. It can be run live or installed to disk. It also +includes a snapshot of the \CTAN{} repository, the \pkgname{protext} +distribution for Windows and the Mac\TeX\ distribution for \MacOSX, entirely +independent of \TL{}, as well as assorted other packages in a +\texttt{texmf-extra} directory. + +\CTAN{}, \pkgname{protext}, Mac\TeX, and \texttt{texmf-extra} do not follow +the same copying conditions as \TL{}, so be careful when redistributing or +modifying. + +\item [inst(allable)] A complete system on \CD; in order to make this fit, +the packages and programs are compressed. Therefore, it is not possible +to run \TeX\ directly from the installable \CD, you have to install it +to disk (hence its name). Installation is described in subsequent sections. + +\item [protext] An enhancement of the \MIKTEX\ distribution for Windows, +\ProTeXt\ adds a few extra tools to \MIKTEX, and simplifies +installation. It is entirely independent of \TL{}, and has its own +installation instructions. It can be run live, or installed to disk. +The \ProTeXt\ home page is \url{http://tug.org/protext}. + +\ProTeXt\ is provided as both the top level of the \pkgname{live} \DVD\ +and on its own \CD\ (for those who cannot use the \DVD). + +\end{description} + +\noindent You can tell which type of distribution you're in by looking +for a \texttt{00\var{type}.TL} file at the top of the \TL{} directory. +This file also contains the \TL{} release date. + +Naturally, each user group chooses what to distribute, at its own +discretion. (\acro{TUG} is sending all three discs above to all of its +members.) + + +\subsection{Top level directories} +\label{sec:tld} + +Here is a brief listing and description of the top level directories in +the \TL{} distribution. On the \pkgname{live} \DVD, the entire \TL{} +hierarchy is in a subdirectory \dirname{texlive2005}, not at the top +level of the disc. + +\smallskip +\begingroup + \renewcommand{\arraystretch}{1.3} % open up interrow spacing +\begin{tabular}{>{\ttfamily}lp{.78\hsize}} +bin & The \TeX{} system programs, arranged by platform. \\ +source & The source of all programs, including the main \Webc{} + \TeX{} and \MF{} distributions. These are stored in a + \cmdname{bzip2}-compressed tar archive. \\ +support & Assorted auxiliary packages and programs. These are + \emph{not} installed automatically. This includes + assorted editors and \TeX\ shells. \\ +texmf & Tree for the programs, along with their support files and + documentation. Does not include \TeX\ formats and packages. + (\texttt{TEXMFMAIN} in the next section.) \\ +texmf-dist & The main tree of formats and packages. + (\texttt{TEXMFDIST} in the next section.) \\ +texmf-doc & Tree for self-contained pure documentation, arranged by + language. \\ +texmf-var & Tree for files automatically generated and stored. + (\texttt{TEXMFSYSVAR} in the next section.) \\ +xemtex & Tree for supporting programs used only in Windows. + These programs generally come pre-installed on Unix systems, or are + at least easy to compile. \\ +\end{tabular} +\endgroup + +\smallskip + +In addition to the directories above, the installation scripts and +\filename{README} files (in various languages) are at the top level of +the distribution. + +The \dirname{texmf-doc} directory contains only documentation, but +it does not contain all the documentation. The documentation for the +programs (manuals, man pages, Info files) is in \dirname{texmf/doc}, +since the programs are in \dirname{texmf}. Similarly, the documentation +for \TeX\ packages and formats is in \dirname{texmf-dist/doc}. You can +use the \cmdname{texdoc} or \cmdname{texdoctk} programs to find any +documentation wherever it's located. The comprehensive links in the +top-level file \OnCD{doc.html} may also be helpful. + + +\subsection{Overview of the predefined texmf trees} +\label{sec:texmftrees} + +This section lists all predefined variables specifying texmf trees used +by the system, and their intended purpose. The command \texttt{texconfig +conf} shows you the values of these variables, so that you can easily +find out how they map to directory names in your installation. + +\begin{ttdescription} +\item [TEXMFMAIN] The tree which holds vital parts of the system + such as helper scripts (e.g., \verb+web2c/mktexdir+), pool files and + other support files. +\item [TEXMFDIST] The tree which holds the main set of macro packages, + fonts, etc., as originally distributed. +\item [TEXMFLOCAL] The tree which administrators can use for system-wide + installation of additional or updated macros, fonts, etc. +\item [TEXMFHOME] The tree which users can use for their own individual + installations of additional or updated macros, fonts, etc. + The expansion of this variable depends on \verb+$HOME+ by default, % $ + which dynamically adjusts for each user to an individual + directory. +\item [TEXMFCONFIG] The tree used by te\TeX's utilities + \verb+texconfig+, \verb+updmap+, and \verb+fmtutil+ to store modified + configuration data. Under \verb+$HOME+ by default. %$ +\item [TEXMFSYSCONFIG] The tree used by te\TeX's utilities + \verb+texconfig-sys+, \verb+updmap-sys+, and \verb+fmtutil-sys+ to + store modified configuration data. +\item [TEXMFVAR] The tree used by \verb+texconfig+, \verb+updmap+ and + \verb+fmtutil+ to store (cached) runtime data such as format files and + generated map files. Under \verb+$HOME+ by default. %$ +\item [TEXMFSYSVAR] The tree used by \verb+texconfig-sys+, + \verb+updmap-sys+ and \verb+fmtutil-sys+ to store (cached) runtime + data such as format files and generated map files. +\end{ttdescription} + +For more discussion of \texttt{texconfig} and related utilities, please +see section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig}. + + +\subsection{Extensions to \protect\TeX} +\label{sec:tex-extensions} + +\TL{} contains several extended versions of \TeX: + +\begin{description} + +\item [\eTeX] adds a small but powerful set of new primitives +\label{text:etex} (related to macro expansion, character scanning, +classes of marks, additional debugging features, and more) and the +\TeXXeT{} extensions for bidirectional typesetting. In default mode, +\eTeX{} is 100\% compatible with ordinary \TeX. See +\OnCD{texmf-dist/doc/etex/base/etex_man.pdf}. + +\item [pdf\TeX] writes Acrobat \acro{PDF} format as well as \dvi{}. The +\LaTeX{} \pkgname{hyperref} package has an option `\optname{pdftex}' +which turns on all the program features. See +\OnCD{texmf/doc/pdftex/manual/} for the manual, and +\OnCD{texmf/doc/pdftex/manual/samplepdf/samplepdf.tex}. + +\item [pdfe\TeX] combines the pdf\TeX\ and \eTeX\ extensions. This is +the default program for all formats except plain \TeX. +See above for documentation. + +\item [\OMEGA\ (Omega)] is based on Unicode (16-bit characters), thus +supports working with almost all the world's scripts simultaneously. It +also supports so-called `\OMEGA{} Translation Processes' (\acro{OTP}s), +for performing complex transformations on arbitrary input. See +\OnCD{texmf-dist/doc/omega/base/doc-1.8.tex} (not completely up-to-date). + +\item [Aleph] combines the \OMEGA\ and \eTeX\ extensions. +See \OnCD{texmf-dist/doc/aleph/base} for some minimal documentation. + +\end{description} + + +\subsection{Other notable programs in \protect\TL} + +Here are a few other commonly-used programs included in \TL{}: + +\begin{cmddescription} + +\item [bibtex] bibliography support. + +\item [makeindex] index support. + +\item [dvips] convert \dvi{} to \PS{}. + +\item [xdvi] \dvi{} previewer for the X Window System. + +\item [dvilj] \dvi{} drive for the HP LaserJet family. + +\item [dv2dt, dt2dv] convert \dvi{} to/from plain text. + +\item [dviconcat, dviselect] cut and paste pages +from \dvi{} files. + +\item [dvipdfmx] convert \dvi{} to \acro{PDF}, an alternative approach +to pdf\TeX\ (mentioned above). See the \pkgname{ps4pdf} and +\pkgname{pdftricks} packages for still more alternatives. + +\item [psselect, psnup, \ldots] \PS{} +utilities. + +\item [lacheck] \LaTeX{} syntax checker. + +\item [texexec] Con\TeX{}t and \acro{PDF} processor. + +\item [tex4ht] \TeX{} to \acro{HTML} converter. + +\end{cmddescription} + + +\section{Unix installation} +\label{sec:unix-install} + +As introduced in section~\ref{sec:basic} (\p.\pageref{sec:basic}), +\TL{} has three principal uses: + +\begin{enumerate} +\item Run directly from media. +\item Install to disk. +\item Integrate a particular package or collection into your existing +\TeX{} installation. +\end{enumerate} + +\noindent The following sections describes the Unix-specific procedures +for each of these. + +\ifSingleColumn \begin{figure}[ht]\noindent \fi +\begin{warningbox} +\textbf{Warning: } The \TK{} \CD{}s and \DVD{} are in ISO 9660 (High Sierra) +format, \emph{with} Rock Ridge (and Joliet, for Windows) +extensions. Therefore, in order to take full advantage of the \TK{} +under Unix, your system needs to be able to use the Rock Ridge +extensions. Please consult the documentation for your \cmdname{mount} +command to see how to do this. If you have several different machines +on a local network, you may be able to mount the discs on one which +does support Rock Ridge, and use this with the others. + +\leavevmode\quad Modern systems should be able to use the discs without +problems. If troubles, let us know. The discussion below assumes you +have been able to mount the \CD{}s with full Rock Ridge compatibility. +\end{warningbox} +\ifSingleColumn\end{figure}\fi + + +% +\subsection{Running \protect\TL{} directly from media (Unix)} + +\def\runlive{% text repeated in windows section +It is possible to use the \TeX{} system directly from the \pkgname{live} +\DVD{}, without installing the distribution to disk. (Thus the name +\TeX\ `Live', in fact.) It is \emph{not} possible to run \TeX{} +directly from the other \CD{}s (see section~\ref{sec:multiple-dist}, +\p.\pageref{sec:multiple-dist}). +} + +\def\startinst{% repeated in other subsections +To start, you mount the \CD{} or \DVD{}, with Rock Ridge extensions +enabled. The exact command to do this varies from system to system; the +following works under Linux, except the name of the device +(\filename{/dev/cdrom}, here) may vary. (All our examples will use +\texttt{>} as the shell prompt; user input is +\Ucom{\texttt{underlined}}.) +\begin{alltt} +> \Ucom{mount -t iso9660 /dev/cdrom /mnt/cdrom} +\end{alltt} + +\noindent Change the current directory to the mount point: +\begin{alltt} +> \Ucom{cd /mnt/cdrom} +\end{alltt} + +\noindent Under \MacOSX, the directory is typically under +\dirname{/Volumes}, and the media will be mounted automatically. +} + +\def\installtlsh{ +Run the installation script \filename{install-tl.sh}: +\begin{alltt} +> \Ucom{sh install-tl.sh}\\ +Welcome to TeX Live... +\end{alltt} + +\noindent After various greeting messages and a list of the main menu +options, the installation will ask you to enter a command. Do this by +typing the desired character and hitting return; don't type the angle +brackets shown. Either uppercase or lowercase is ok; we'll use +lowercase in our examples. +} + +\runlive +\startinst +\installtlsh + +For running live, our first command will be \Ucom{d} and then the +subcommand \Ucom{1} to set directories. Even in this case, we must +choose a directory on the local disk to place files that the \TeX{} +system itself generates, such as fonts and formats, and also to provide +a place for updated configuration files, if need be. + +We'll use \dirname{/opt/texlive2005} in this example. It's good to +include the year in the name, as these generated files are not +compatible from release to release. (If the default value of +\dirname{/usr/local/texlive/2005} works for you, then you can skip this +step.) + +\begin{alltt} +Enter command: \Ucom{d} +Current directories setup: +<1> TEXDIR: /usr/local/texlive/2005 +... +Enter command: \Ucom{1} +New value for TEXDIR [/usr/local/texlive/TeX]: \Ucom{/opt/texlive2005} +... +Enter command: \Ucom{r} +\end{alltt} + +\noindent Back at the main menu, our second and last command is +\Ucom{r}, to set up for running live off the media without installing +to disk: +\begin{alltt} +Enter command: \Ucom{r} +Preparing destination directories... +... +Welcome to TeX Live! +> +\end{alltt} + +\noindent And we are back at the system prompt, as shown. + +Next, it is necessary to alter two environment variables: +\envname{PATH}, to an architecture-dependent value (so that we can run +the programs), and \envname{TEXMFSYSVAR}, to the value specified above. +See table~\ref{tab:archlist} for a list of the architecture names for +the different systems. + + +\def\textruntexconfig{% +After the main installation has completed, and environment variables +have been set, the last step is to run \cmdname{texconfig} or +\cmdname{texconfig-sys} to customize your installation to your needs. +This is explained in section~\ref{sec:texconfig}, +\p.\pageref{sec:texconfig}. +} +\textruntexconfig + +\begin{table*}[ht] +\caption[Supported system architectures.]{Supported system +architectures.} +\label{tab:archlist} +\begin{tabular}{>{\ttfamily}ll} +alpha-linux & HP Alpha GNU/Linux \\ +%alphaev5-osf4.0d & HP Alphaev5 OSF \\ +%hppa2.0-hpux10.20 & HP9000 HPUX 10.20 \\ +i386-darwin & Intel x86 \MacOSX \\ +i386-freebsd & Intel x86 FreeBSD \\ +i386-linux & Intel x86 GNU/Linux \\ +%i386-openbsd3.3 & Intel x86 OpenBSD \\ +%i386-solaris2.8 & Intel x86 Solaris \\ +mips-irix & SGI IRIX \\ +powerpc-aix & IBM RS/6000 AIX \\ +powerpc-darwin & PowerPC \MacOSX \\ +sparc-linux & Sun Sparc GNU/Linux \\ +sparc-solaris & Sun Sparc Solaris \\ +win32 & Windows (32-bit) \\ +x86\_64-linux & Intel x86 64-bit GNU/Linux \\ +\hline +\end{tabular} +\end{table*} + +\label{text:path} +The syntax for setting the environment variables, and the initialization +file to put them in, depends on the shell you use. If you use a +Bourne-compatible shell (\cmdname{sh}, \cmdname{bash}, \cmdname{ksh}, et +al.), put the following into your \filename{$HOME/.profile} file: +\begin{alltt} +PATH=/mnt/cdrom/bin/\var{archname}:$PATH; export PATH +TEXMFSYSVAR=/opt/texlive2005/texmf-var; export TEXMFVAR +\end{alltt} + +\noindent For C shell-compatible shells (\cmdname{csh}, \cmdname{tcsh}), +put the following into your \filename{$HOME/.cshrc} file: +\begin{alltt} +setenv PATH /mnt/cdrom/bin/\var{archname}:$PATH +setenv TEXMFSYSVAR /opt/texlive2005/texmf-var +\end{alltt} + +\noindent Then log out, log back in, and test your installation +(see section~\ref{sec:test-install}, \p.\pageref{sec:test-install}). + +\def\textifindoubt{% +If in doubt, please ask any local system gurus to help you with +problems; for example, the way to mount the \TL{} media, which +directory or directories to use, and precise details of the changes to +your personal initialization files can and do vary from site to site. +} +\textifindoubt + + +% +\subsection{Installing \protect\TeX\protect\ Live to disk} +\label{sec:unix-install-disk} + +It is possible, indeed typical, to install the \TL{} distribution to +hard disk. This can be done from either the \pkgname{live} or +\pkgname{inst} distributions. (See section~\ref{sec:multiple-dist}, +\p.\pageref{sec:multiple-dist}, for an explanation of the different +distributions.) + +\startinst +\installtlsh + +Table~\ref{tab:main-menu-options} briefly lists the options in the main +menu. The order in which you select the options makes little +difference, except that \Ucom{i} must be last. It's reasonable to go +through them in the order presented here. + +% apparently here.sty [H] doesn't support table*. +\begin{table}[H] +\caption{Main menu options for the installation.} +\label{tab:main-menu-options} +\begin{tabular}{>{\ttfamily}ll} +p & The platform you are running on.\\ +b & The architectures for which to install binaries.\\ +s & The base installation scheme to use (minimal, recommended, + full, etc.)\\ +c & Override the base scheme for individual collections.\\ +l & Override for language collections.\\ +d & Directories in which to install.\\ +o & Other options.\\ +i & Perform the installation.\\ +\end{tabular} +\end{table} + +Here are further details on each option. + +\textbf{\optname{p} -- Current platform.} Since the installation script +automatically guesses which platform you're running on, it is usually +unnecessary to use this option. It's there in case you need to override +the automatic detection. + +\textbf{\optname{b} -- Binary architectures.} By default, only the +binaries for your current platform will be installed. From this menu, +you can select installation of binaries for other architectures as well +(or omit installing the current platform). This can be useful if you are +sharing a \TeX\ tree across a network of heterogenous machines. For a +list of the supported architectures, see table~\ref{tab:archlist}, +\p.\pageref{tab:archlist}. + +\textbf{\optname{s} -- Base installation scheme.} From this menu, you +can choose an overall set of package collections, called a ``scheme''. +The default \optname{full} scheme installs everything available, but you +can also choose the \optname{basic} scheme for a minimal system, or +\optname{medium} to get something in between. There are also specific +sets for Omega and \acro{XML}. + +\textbf{\optname{c} -- Individual collections.} From this menu, you can +override the scheme's set of collections to install. Collections are +one level more detailed than schemes\Dash collections consist of one or +more packages, where packages (the lowest level grouping in \TL) contain +the actual \TeX\ macro files, font families, and so on. In this menu, +selection letters are case-sensitive. + +\textbf{\optname{l} -- Language collections}. This menu has the same +basic purpose as \Ucom{c}, to override the collection set in the chosen +scheme. In this case, the collections are specifically for different +languages. Selection letters are case-sensitive here too. Here is a +list of the language collections in \TL: + +% xx really should generate list from texmf/tpm/collection/tex-lang* +% a la install-tl.sh. +\begin{tabbing} +\hspace{.25\linewidth} \= +\hspace{.25\linewidth} \= +\hspace{.25\linewidth} \= +\hspace{.25\linewidth} \kill +(some) African scripts \> +Arabic \> +Armenian \> +Chinese\,Japanese\,Korean \\ +Croatian \> +Cyrillic \> +Czech/Slovak \> +Danish \\ +Dutch \> +Finnish \> +French \> +German \\ +Greek \> +Hebrew \> +Hungarian \> +Indic \\ +Italian \> +Latin \> +Manju \> +Mongolian \\ +Norwegian \> +Polish \> +Portuguese \> +Spanish \\ +Swedish \> +Tibetan \> +\acro{UK} English \> +Vietnamese \\ +\end{tabbing} + +\noindent Language collections typically include fonts, macros, +hyphenation patterns, and other support files. (For instance, +\pkgname{frenchle.sty} is installed if you select the \optname{French} +collection.) In addition, installing a language collection will alter +the \filename{language.dat} configuration file controlling which +hyphenation patterns are loaded. + +\textbf{\optname{d} -- Installation directories}. Three directories can +be changed here: +\label{text:instdir} + +\begin{ttdescription} +\item [TEXDIR] The top-level directory under which +everything else will be installed. The default value is +\dirname{/usr/local/texlive/2005}, and is often changed. We recommend +including the year in the name, to keep different releases of \TL{} +separate. (You may wish to make a version-independent name such +\dirname{/usr/local/texlive} via a symbolic link, which you can then +update after testing the new release.) + +Under \MacOSX, the usual frontends look for \TeX{} in +\dirname{/usr/local/teTeX}, so you may wish to install \TL{} there. + +\item [TEXMFLOCAL] This tree is where the \TeX{} system (not as part of +the initial installation, but rather as time goes by) puts +non-version-specific files, primarily fonts. The default value is +\dirname{/usr/local/texlive/texmf-local}, independent of the current +\TL{} release, because it's also the recommended location to put any +local packages or configuration settings. + +\item [TEXMFSYSVAR] This tree is where \cmdname{texconfig-sys} puts +files that \emph{are} version-specific. The default value is +\dirname{TEXDIR/texmf-var}, and there's generally no reason to change +it. There is also \envname{TEXMFSYSCONFIG}, which is where +\cmdname{texconfig} looks for modified configuration data. See +section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig} for more +information. + +\end{ttdescription} + +\textbf{\optname{o} -- Other options.} From this menu, you can select +the following general options: + +\begin{ttdescription} +\item [a] Specify an alternate directory for generated fonts. +The default is to use the \envname{TEXMFVAR} tree, as explained above. +Setting this is useful if you plan to mount the main tree read-only, and +therefore you need another location (perhaps host-specific) for +dynamically created fonts. + +\item [l] Create symbolic links for the binaries, man pages, +and\slash or \acro{GNU} Info files in other locations. For example, you may +wish to make the man pages available under \dirname{/usr/local/man} and +the Info files available under \dirname{/usr/local/info}. (Of course +you need appropriate privileges to write in the specified directories.) + +It is not advisable to overwrite a \TeX\ system that came with your +system with this option. It's intended primarily for creating the links +in standard directories that are known to users, such as +\dirname{/usr/local/bin}, which don't already contain any \TeX\ files. + +\item [d] Skip installation of the font/macro documentation tree. +This is useful if you need to save space, or if you've previously +installed the documentation elsewhere. + +\item [s] Skip installation of the main font/macro source +tree. This is useful if you are arranging to share that tree between +machines and\slash or architectures in some other way, such as \acro{NFS}. + +\end{ttdescription} + +\textbf{i -- Perform installation.} When you're satisfied with your +configuration options, enter \Ucom{i} to actually do the installation +from the media to your chosen locations. + +% text is similar to above, but no TEXMFSYSVAR, so we have to write out. +After the installation completes, your next step is to include the +architecture-specific subdirectory of \dirname{TEXDIR/bin} in your +\envname{PATH}, so the newly-installed programs can be found. The +architecture names are listed in table~\ref{tab:archlist}, +\p.\pageref{tab:archlist}, or you can simply list the directory +\dirname{TEXDIR/bin}. + +The syntax for doing this, and the initialization file to use, depends +on your shell. If you use a Bourne-compatible shell (\cmdname{sh}, +\cmdname{bash}, \cmdname{ksh}, et al.), put the following into your +\filename{$HOME/.profile} file: + +\begin{alltt} +PATH=/usr/local/texlive/2005/bin/\var{archname}:$PATH; export PATH +\end{alltt} + +\noindent For C shell-compatible shells (\cmdname{csh}, \cmdname{tcsh}), +put the following into your \filename{$HOME/.cshrc} file: +\begin{alltt} +setenv PATH /usr/local/texlive/2005/bin/\var{archname}:$PATH +\end{alltt} + +\textruntexconfig + +Here is a minimal annotated example which accepts the default +directories and installs binaries for the current system only. Thus, +only one command is needed, \Ucom{i} for install. The \texttt{>} is the +shell prompt as usual. + +\begin{alltt} +> \Ucom{sh install-tl.sh} +\Ucom{i} # perform installation +> \Ucom{texconfig} ... # see section \ref{sec:texconfig} +# New PATH element, with Linux as the example: +> \Ucom{PATH=/usr/local/texlive/2005/bin/i386-linux:$PATH; export PATH} +\end{alltt} + +\textifindoubt + + +% +\subsection{Installing individual packages to disk} + +You can add individual packages or collections from the current +distribution to an existing non-\TL{} setup, or an earlier +\TL{} installation. + +\startinst + +Run the installation script \filename{install-pkg.sh} (not +\filename{install-tl.sh}, which is intended for complete installations +only): +\begin{alltt} +> \Ucom{sh install-pkg.sh \var{options}} +\end{alltt} + +The first set of options controls what gets read: + +\begin{ttdescription} +\item [-{}-package=\var{pkgname}] The individual package to work on. + +\item [-{}-collection=\var{colname}] The individual collection to work on. + +\item [-{}-nodoc] Exclude documentation files from the operation. + +\item [-{}-nosrc] Exclude source files from the operation. + +\item [-{}-cddir=\var{dir}] Source directory to read from; defaults +to the current directory. If you followed the instructions above, that +will be the distribution directory, and won't need to be changed. + +\item [-{}-listdir=\var{dir}] The so-called `lists' directory within +\var{cddir} from which to read the package information. The only +reason to change the default is if you're making changes to \TL{} +yourself. + +\end{ttdescription} + +What actually happens is controlled by the following options. If +neither of these are specified, the default action is to install the +selected files. The main destination tree is found by expanding +\envname{\$TEXMFMAIN} with \cmdname{kpsewhich}. You can override it by +setting either the environment variable \envname{TEXMFMAIN} or +\envname{TEXMF}. + +\begin{ttdescription} +\item [-{}-listonly] List the files that would be installed, but don't +actually install anything. + +\item [-{}-archive=\var{tarfile}] Instead of installing the files into +the \TeX{} system, make a \cmdname{tar} archive. + +\end{ttdescription} + +Additional options: + +\begin{ttdescription} + +\item [-{}-config] After installation, run \code{texconfig init}. + +\item [-{}-nohash] After installation, don't run \cmdname{mktexlsr} to +rebuild the filename database. + +\item [-{}-verbose] Give more information as the script runs. + +\end{ttdescription} + +Here are some usage examples: + +\begin{enumerate} + +\item To see the files in the package \pkgname{fancyhdr} without +installing it: + +\begin{alltt} +\ifSingleColumn> \Ucom{sh install-pkg.sh --package=fancyhdr --listonly} +\else> \Ucom{sh install-pkg.sh --package=fancyhdr \bs} +> \Ucom{--listonly} +\fi{} +texmf/doc/latex/fancyhdr/README +texmf/doc/latex/fancyhdr/fancyhdr.pdf +... +\end{alltt} + +\item Install the \LaTeX{} package \pkgname{natbib}: +\begin{alltt} +> \Ucom{sh install-pkg.sh --package=natbib} +\end{alltt} + +\item Install the \LaTeX{} package \pkgname{alg} without source files or +documentation: +\begin{alltt} +\ifSingleColumn> \Ucom{sh install-pkg.sh --package=alg --nosrc --nodoc} +\else> \Ucom{sh install-pkg.sh -{}-package=alg \bs} +> \Ucom{-{}-nosrc -{}-nodoc} +\fi\end{alltt} + +\item Install all the packages in the collection of additional +plain \TeX\ macros: +\begin{alltt} +> \Ucom{sh install-pkg.sh --collection=tex-plainextra} +\end{alltt} + +\item Write all files in the \pkgname{pstricks} package to a +\cmdname{tar} file in \path|/tmp|: +\begin{alltt} +\ifSingleColumn> \Ucom{sh install-pkg.sh --package=pstricks --archive=/tmp/pstricks.tar} +\else +> \Ucom{sh install-pkg.sh -{}-package=pstricks \bs} +> \Ucom{-{}-archive=/tmp/pstricks.tar} +\fi\end{alltt} + +\end{enumerate} + +\textifindoubt + + +% +\section{Post-installation} +\label{sec:postinstall} + +After the main installation is done, for any operating system, the +remaining steps are to configure the system for your local needs, and +perform some basic tests. + +Another sort of post-installation is to acquire packages, fonts, or +programs that were not included in \TL{}. The basic idea is to +install such additions in the \envname{TEXMFLOCAL} tree (if you +installed to disk), or \envname{TEXMFSYSVAR} (if you are running live). +See the ``Installation directories'' option on \p.\pageref{text:instdir}. + +Unfortunately, the details can and do vary widely, and so we do not attempt to +address them here. Here are some external links to descriptions: +\begin{itemize*} +\item +\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instpackages} +\item +\url{http://www.ctan.org/installationadvice} +\item +\url{http://www.ctan.org/tex-archive/info/beginlatex/html/chapter5.html#pkginst} +\item +\url{http://www.ctan.org/tex-archive/info/Type1fonts} for +installation information for fonts in particular. +\end{itemize*} + + +\subsection{The \protect\cmdname{texconfig} program} +\label{sec:texconfig} + +At any time after installation, you can and should use the program +\cmdname{texconfig} to configure the system to fit your local needs. It +is installed in the architecture-specific subdirectory +\texttt{TEXDIR/bin/\var{arch}} along with everything else. + +If you run it without arguments, it will enter full-screen mode and +allow you to view and change options interactively. + +You can also run it with various command-line options. Here are some of +the most common (\TL{} is configured for the A4 paper size by default): + +\begin{ttdescription} + +\item [texconfig paper letter] Set default paper size for +various programs and drivers (\cmdname{pdftex}, \cmdname{dvips}, +\cmdname{dvipdfm}, \cmdname{xdvi}) to be \acro{US} letter. The other +allowable size is \optname{a4}, which is the default. + +\item [texconfig rehash] Update all the \TeX{} ``filename databases'', +after adding or removing files. + +\item [texconfig faq] Show the \teTeX{} \acro{FAQ}. +(See also the main \TeX{} \acro{FAQ} in \OnCD{texmf-doc/doc/english/FAQ-en}.) + +\item [texconfig help] Output help information for \cmdname{texconfig}. + +\end{ttdescription} + +Of course, \cmdname{texconfig} can only support changing a few of the +many options and configuration parameters in a \TeX{} system. The main +configuration file for the base \Webc{} programs is named +\filename{texmf.cnf}. You can find its location by running +\samp{kpsewhich texmf.cnf}; it contains many comments explaining the +default settings and useful alternatives. + +As of 2005, \cmdname{texconfig} alters files in a user-specific +directory, namely \dirname{$HOME/.texlive2005}. If you install \TeX\ +just for yourself, that is unlikely to make a difference. But if you +install \TeX\ on a multi-user system, you will want to change the +configuration for the whole system. In this case, run +\cmdname{texconfig-sys} instead of \cmdname{texconfig}. + +Likewise, the \cmdname{updmap} and \cmdname{fmtutil} scripts were +changed, to work under \dirname{$HOME/.texlive2005}. To alter system +directories, use \cmdname{updmap-sys} and \cmdname{fmtutil-sys}. + +In particular, for multi-user systems, you will probably want to +pregenerate the standard formats with \texttt{fmtutil-sys --missing}. +Otherwise, each user will end up with their own formats. + +Also, if you have a personally-modified copy of \filename{fmtutil.cnf} +or \filename{updmap.cfg}, instead of using the ones generated by +installation, they must be installed in the tree referenced by the +variable \envname{TEXMFSYSCONFIG}. + +The variables specifying the directories altered by these commands are +listed in section~\ref{sec:texmftrees}, \p.\pageref{sec:texmftrees}. +You can see the actual directories by running \texttt{texconfig conf}, +and you can change them by editing \filename{texmf.cnf}. + + +\subsection{Testing the installation} +\label{sec:test-install} + +After installing \TL{} as best you can, you naturally want to test +it out, so you can start creating beautiful documents and\slash or fonts. + +This section gives some basic procedures for testing that the new system +is functional. We give Unix commands; under \MacOSX{} and Windows, +you're more likely to run the tests through a graphical interface, but +the principles are the same. + +\begin{enumerate} + +\item Make sure that you can run the \cmdname{tex} program in the first +place: + +\begin{alltt} +> \Ucom{tex -{}-version} +TeX 3.141592 (Web2C 7.5.5) +kpathsea version 3.5.5 +... +\end{alltt} +If this comes back with `command not found' instead of version and +copyright information, most likely you don't have the correct +\dirname{bin} subdirectory in your \envname{PATH}. See +the environment-setting information on \p.\pageref{text:path}. + +\item Process a basic \LaTeX{} file: +\begin{alltt} +> \Ucom{latex sample2e.tex} +This is pdfeTeXk, Version 3.141592... +... +Output written on sample2e.dvi (3 pages, 7496 bytes). +Transcript written on sample2e.log. +\end{alltt} +If this fails to find \filename{sample2e.tex} or other files, perhaps +you have interference from old environment variables or configuration +files. For a deep analysis, you can always ask \TeX{} to report on +exactly what it is searching for, and finding; see ``Debugging actions'' +on page~\pageref{Debugging}. + +\item Preview the result online: +\begin{alltt} +> \Ucom{xdvi sample2e.dvi} +\end{alltt} +(Under Windows, the analogous command is \cmdname{windvi}.) You should +see a new window with a nice document explaining some of the basics of +\LaTeX{}. (Well worth reading, by the way if you're new to the system.) +You do have to be running under X for \cmdname{xdvi} to work; if you're +not, or your \envname{DISPLAY} environment variable is set incorrectly, +you'll get an error \samp{Can't open display}. + +\item Create a \PS{} file for printing or display: +\begin{alltt} +> \Ucom{dvips sample2e.dvi -o sample2e.ps} +\end{alltt} + +\item Create a \acro{PDF} file instead of \dvi{}; this processes the +\filename{.tex} file and writes \acro{PDF} directly: +\begin{alltt} +> \Ucom{pdflatex sample2e.tex} +\end{alltt} + +\item Preview the \acro{PDF} file: +\begin{alltt} +> \Ucom{gv sample2e.pdf} +\textrm{or:} +> \Ucom{xpdf sample2e.pdf} +\end{alltt} +Unfortunately neither \cmdname{gv} nor \cmdname{xpdf} are currently +included in \TL{}, so you must install them separately. See +\url{http://www.gnu.org/software/gv} and +\url{http://www.foolabs.com/xpdf}, respectively. + +\item Other standard test files you may find useful: + +\begin{ttdescription} +\item [small2e.tex] A simpler document than \filename{sample2e}, to +reduce the input size if you're having troubles. +\item [testpage.tex] Test if your printer introduces any offsets. +\item [nfssfont.tex] For printing font tables and tests. +\item [testfont.tex] Also for font tables, but using plain \TeX{}. +\item [story.tex] The most canonical (plain) \TeX{} test file of all. +You must type \samp{\bs bye} to the \code{*} prompt after \samp{tex +story.tex}. +\end{ttdescription} +You can process these in the same way as we did with +\filename{sample2e.tex}. + +\end{enumerate} + +If you are new to \TeX{}, or otherwise need help with actually +constructing \TeX{} or \LaTeX{} documents, please visit +\url{http://tug.org/begin.html} for some introductory resources. + + +\section{\MacOSX{} installation} +\label{sec:mac-install} + +The recommended way to install \TeX\ on \MacOSX\ is from the Mac\TeX\ +distribution, new in 2005. This is provided on the \pkgname{live} +\DVD{} in the top-level \dirname{mactex/} directory. It contains its +own (native) installer for a full \TeX\ distribution, based on a +combination of te\TeX\ and \TL, along with many additional applications +and documentation. The project web page is \url{http://tug.org/mactex}. + +If you prefer, installation of \TeX{} under \MacOSX{} can also be done +directly from \TL, using the \filename{install*} scripts, as follows. + +In order to run the installation scripts under \MacOSX, you need to have +the \cmdname{bash} shell installed. If you are running \MacOSX~10.2 +or later, you have \cmdname{bash}, and can proceed. If you're running +an earlier \MacOSX{} version, however, the default shell is +\cmdname{zsh}, which won't work; you'll need to get \cmdname{bash} from +the Internet, or more likely upgrade your system. + +Once you have \cmdname{bash}, the Unix installation documentation in the +previous section can be followed. See section~\ref{sec:unix-install} on +\p.\pageref{sec:unix-install}; \MacOSX-specific notes are included there +where needed. + +\section{Windows installation} +\label{sec:win-install} + +In this release of \TL{}, happily, the distribution once +again has a native Windows installer, named \cmdname{tlpmgui.exe}. (See +section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}, for an +explanation of the different distributions.) + +\cmdname{tlpmgui} has essentially the same options as the Unix +installer, only done through a GUI interface: selecting schemes, +individual collections, installation directories, and so on. +Section~\ref{sec:unix-install-disk} on +\p.\pageref{sec:unix-install-disk} describes the basic elements. It +also allows some post-installation activities such as adding/removing +packages, updating the filename database and building formats. +Moreover, \cmdname{tlpmgui} can setup the system for running +programs directly from the \DVD. + +For those who like to look underneath the hood, \cmdname{tlpmgui} uses +as its ``engine'' a command-line Windows program named \cmdname{tlpm}. + +The Windows \TeX{} system included in \TL{} is based on new binaries +borrowed from the \XEmTeX{} project, formerly known as \fpTeX{} (see +\url{http://www.metz.supelec.fr/~popineau/xemtex-1.html}). +It also includes some older (but still working) tools, notably +a \texttt{dvi} previewer, \textsf{Windvi}, which is similar in usage to +the established Unix \textsf{xdvi}. The documentation can be found in +\OnCD{texmf/doc/html/windvi/windvi.html}. + +\TL{} can be installed on systems running Windows 98, \acro{ME}, +\acro{NT}, \acro{2K} or \acro{XP}. Older versions of Windows (3.1x) +and \acro{MS-DOS} are not supported. + +\textbf{Warning:} Win9.x users must ensure they have enough environment + space before undertaking installation. The \cmdname{tlpmgui.exe} + program won't change the environment size for them. A few environment + variables will be created and it is possible you run out of + environment space. Add \texttt{SHELL=COMMAND.COM /E:4096 /P} in the + config.sys file in order to increase your environment size. + +\subsection{Installing \protect\TeX\protect\ Live to disk} + +After inserting the \TL{} CD into the \acro{CD} drive, autostart should +activate \cmdname{tlpmgui}. If it does not, click \guiseq{Start\arw Run}, +then type \verb|:\setup-win32\tplmgui.exe| (or +\verb|:\texlive\setup-win32\tplmgui.exe| if you are +installing from the TeX Collection DVD), where \verb|| +is the drive letter with the TeX Live CD (or TeX Collection DVD), and +then click OK. + +The installation window titled \guiseq{TeX Live installation and maintenance +utility} should open. It contains the following sections: \guiseq{Main +customization}, \guiseq{Install}, \guiseq{Select a scheme}, \guiseq{Select +systems}, \guiseq{Directories} and \guiseq{Options}. + +In the \guiseq{Directories} section the installation drive (directory) next +to the \guiseq{CD/DVD} button should be displayed (e.g., \texttt{F:/} or \texttt{F:/texlive/} for the DVD), but +if it is not, then click the \guiseq{CD/DVD} button and select the \acro{CD/DVD} +drive, with the \TL{} CD (or TeX Collection DVD). + +The directory in which you wish to install the software can be set by +clicking the \guiseq{TLroot} button. This directory will be set as +\path|TLroot| environment variable for later usage. The \path|TEXMFTEMP| and +\path|TEXMFCNF| environment variables as displayed next to the +\guiseq{TEXMFTEMP} and \guiseq{TEXMFCNF} buttons will be adjusted +automatically and set during installation, but they can also be adjusted +manually now to suit special needs. + +In the \guiseq{Select a scheme} section the desired \TL{} installation scheme +should be chosen by clicking the radio button labelled with the installation +scheme name (e.g., \guiseq{scheme-gust}). Each scheme is accompanied by an +\guiseq{Info} button which, when clicked, displays a short description of the +relevant scheme. + +A scheme is a large set of files targeted at some kind of usage. There are +generic schemes for basic, medium and full installations. The remaining ones +are either targeted at certain LUGs (i.e., what GUST or GUTenberg propose +for their members) or application targeted (e.g., for XML and \TeX{} +cooperation). A preselected scheme can be refined. This is done in the +\guiseq{Main customization} section by choosing additional collections from +\guiseq{Standard collections} or \guiseq{Language collections}. For example, +by clicking the \guiseq{Select} button labelled \guiseq{Standard +collections}, additional collections like Metapost, Omega or documentation +in different languages can be selected. + +\textbf{Note:} The \guiseq{Ghostscript}, \guiseq{Perl} and \guiseq{Wintools} +collections are selected by default and should be installed unless they are +already installed and you really know what you are doing. This is because +they are required by many important tools. The \verb|PERL5LIB| and +\verb|GS_LIB| environment variables will be set too. + +Next, clicking the \guiseq{Select} button labelled \guiseq{Language +Collections} in the \guiseq{Main customization} section opens the +\guiseq{Language collections} window in which the installation language can +be chosen by ticking the box next to the language. + +Next, click the \guiseq{Install} button in the \guiseq{Install} section to +start the installation proper process. + +The \TL{} system needs some post-processing steps (format files +generation, ls-R databases generation, environment variables, etc.). All +these operations are done there, some of them can be lengthy. So please wait +until you see a statement about the successfully finished installation. + +The shortcut for \cmdname{tlpmgui} will be added to the +\guiseq{Start\arw Programs\arw TeXLive2005} menu. + +If it is needed (Win9x/WinME), you will be asked to reboot your computer. + +\subsection{Support packages for Windows} +\label{sec:win-xemtex} + +To be complete, a \TL installation needs support packages that are not +commonly found on a Windows machine. Many scripts are written using the Perl +language. Some important tools require the Ghostscript \PS{} interpreter to +render or to convert files. A graphic file toolbox is also needed in some +cases. Last but not least, a \TeX-oriented editor makes it easy to type in +your \TeX{} files. + +All these tools are quite easy to find for Windows, but in order to try to +make your life even easier, we have put such a set of tools on \TL: +\begin{itemize*} +\item GNU \cmdname{Ghostscript} 7.07 +\item a minimal \cmdname{Perl} 5.8, sufficient to run all the \TL{} + Perl scripts. +\item win-tools is a set of small programs (bzip2, gzip, jpeg2ps + and tiff2png) +%\item a subset of \cmdname{ImageMagick} 5.5.6 +%\item the \cmdname{ISpell} checker +%\item \cmdname{XEmacs} 21.5.14 with a selection of packages to support +%\TeX{} typesetting. +\end{itemize*} + +These packages are borrowed from the \XEmTeX{} distribution +(the successor of fp\TeX). + +Perl and Ghostscript are installed by default; you may explicitly +deselect them during installation if you already have them. + +If you don't want to install this bundle, then you are on your own to +install the required tools to complete your \TL{} system. Here is a +list of places to get those tools: + +\begin{description} +\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} +\item[Perl] \url{http://www.activestate.com/} (but you might need some + supplementary packages from CPAN: \url{http://www.cpan.org/}) +\item[ImageMagick] \url{http://www.imagemagick.com} +\item[NetPBM] alternatively, you could use NetPBM instead of ImageMagick to + process or convert your graphic files. NetPBM home page is + \url{http://netpbm.sourceforge.net/} +\item[\TeX-oriented editors] There is a wide choice, and it is a matter of the + user's taste. Here is a selection: + \begin{itemize*} + \item \cmdname{GNU Emacs} is available natively under Windows, see + \url{http://www.gnu.org/software/emacs/windows/ntemacs.html} + \item \cmdname{XEmacs} is available natively under Windows, see + \url{http://www.xemacs.org/} + \item \cmdname{WinShell} is available on \TL in the \path|support| + directory, see \url{http://www.winshell.de} + \item \cmdname{WinEdt} is shareware available from \url{http://www.winedt.com} + \item \cmdname{Vim} is available on \TL{} in the + \path|support\vim| directory and the + reference site is \url{http://www.vim.org} + \item TeXnicCenter is free software, available from + \url{http://www.toolscenter.org} and in the proTeXt distribution. + \item \cmdname{LEd} is available from \url{http://www.ctan.org/support/LEd} + \item \cmdname{SciTE} is available from \url{http://www.scintilla.org/SciTE.html} + \end{itemize*} +\end{description} + +You might want to install other tools that are not free\footnote{Not +free, that is, in the sense of freedom to modify and redistribute, +following free software guidelines. This does not mean you can't acquire +them for no money.} and therefore not included on \TL{}, such as +\cmdname{GSView}, the \cmdname{Ghostscript} companion to more +conveniently view PS/PDF files. \cmdname{GSView} is available from +\url{http://www.cs.wisc.edu/~ghost/gsview/} or any \acro{CTAN} site. + +\section{Maintenance of the installation in Windows} + +If you have TeX Live installed, you can use \cmdname{tlpmgui} again +for modyfying and maintaining your installation. + +\subsection{Adding/removing packages} + +As the \cmdname{tlpmgui} shortcut is available in the \guiseq{Start\arw +Programs\arw TeXLive2005} menu, start it from here. The maintenance window +titled \guiseq{TeX Live installation and maintenance utility} shows. It +contains several tabs: \guiseq{Add Packages}, \guiseq{Remove packages}, +\guiseq{Manage installation}, \guiseq{Remove installation}. + +Click the tab labelled \guiseq{Add packages} or \guiseq{Remove packages} +to enter the relevant functionality and then: + +\begin{itemize} +\item In the first tab select the proper \CD{} drive (or \DVD with + \texttt{texlive} directory) by pressing the \guiseq{CD/DVD} button. +\item Click the \guiseq{Search} button in the \guiseq{Buttons} section to +display or refresh in the \guiseq{Select packages to\dots} section the +list of packages to install or remove. + +When adding packages, the list of installed packages is compared to the list +of packages available from your \CD/\DVD. Only packages not already installed are +displayed. It is up to you to select which packages you want to +install. + +When removing individual packages, only a list of installed packages +will be displayed. + +Please note that for both \guiseq{Add packages} and \guiseq{Remove packages} +the collections are listed first. + +\item Select a package by clicking on the name of the package. Clicking the +\guiseq{Info} button in the \guiseq{Buttons} section displays a short +description of the selected package in the window located in the \guiseq{Info +about the selected item} section. To select several packages at once hold +down one of the Ctrl or Shift keys at your keyboard while holding down the +left mouse button or drag the mouse pointer while holding down the left mouse +button. + +\item Click the \guiseq{Install} or \guiseq{Remove} button in the +\guiseq{Buttons} section to perform the appropriate action. +\end{itemize} + +\subsection{Configuring and other management tasks} + +The functions available in the tab labelled \guiseq{Manage the installation} +are helpful in performing actions needed when you want to add support for a +language which was not selected during the installation, or add/regenerate a +format which was not selected during the installation or was modified after +the installation. + +The following actions can be performed: + +\begin{itemize} +\item Refresh the \filename{ls-R} database +\item Create formats (All or Missing) +\item Edit \filename{language.dat} +\item Edit \filename{fmtutil.cnf} +\item Edit \filename{updmap.cfg} +\end{itemize} + +Note: you can close the Edit\dots{} window with the \guiseq{Cancel} or +\guiseq{Done} button; the latter will start rebuilding the format files +(or the fontmap files if you have edited \filename{updmap.cfg}), followed by a +\filename{ls-R} database files refresh. + +For more information about the configuration see section~\ref{sec:persconf}, +\p.\pageref{sec:persconf}. + +\subsection{Uninstalling \protect\TL{}} + +The tab labelled \guiseq{Remove the TeX Live installation} opens a window +which contains functionality not worth describing and we do not know who would +need it and what it is for\dots :-) + +Anyway, if you have the \path|texmf-local| directory for your local additions, +the removal procedure will not wipe it out or delete things in it. The \path|setup-win32| +directory containing \cmdname{tlpmgui} and related files will not be deleted. You will have to do some manual cleanup to +actually remove them. + +\subsection{Adding your own packages to the installation} + +First, whatever changes you make, \textbf{do not forget to rebuild the ls-R +database files}. Otherwise, your new files will not be found. You can do this +either via the \cmdname{tlpmgui} run and selection of the appropriate action +from the \guiseq{Manage the installation} tab, or manually running the +\file{mktexlsr} command. + +If you want to add files that are not provided by the \TL{} distribution, +it is recommended to put them in the \path|$TEXMFLOCAL| directory. This +way, you will be safe against upgrades of the \TL{} software. + +The directory pointed to by \path|$TEXMFLOCAL| is initially empty. If, +for example, you want to add the support file for the Maple symbolic +computation program, you will have to put the style files in:\\ +\path|c:\TeXLive2005\texmf-local\tex\latex\maple\|\\ and the +documentation files in:\\ \path|c:\TeXLive2005\texmf-local\doc\latex\maple\| + +\subsection{Running \texttt{tlmp.exe} from the command line} +The \cmdname{tlpm.exe} program which is used as engine by \cmdname{tlpmgui} +has a number of other useful options. You can get the list by running: +\begin{verbatim} +tlpm --help +\end{verbatim} + +More information and examples of use can be found in \path|tlpm.readme|. + +\subsection{Network installation} + +\KPS{} knows about UNC names, so you can use them to get your TEXMF +tree from the network. But there is better than this. +All the support files and configuration files, everything except the files in the +\path|bin/win32| are shareable with a \teTeX{} or Unix \TL{} installation. That means +you can use Samba either to mount from an NT server to a Unix +workstation or the converse. Several strategies are possible: +\begin{itemize} +\item Put everything on the server. Just add each set of files for the OS and +architecture you want to use in the \path|bin| directory. That means +for example \path|bin/win32| and \path|bin/i386-linux|. Next configure +your main variables. You can use UNC names to +point to the right directories under Win32. +\item Install a local copy for the binaries and format files. In this + case, assign \path|$TEXMFMAIN| to the main \path|texmf| tree that + will be accessed remotely. Set \path|$TEXMFVAR| to be a local + directory which will hold local configuration files and on-the-fly + generated files. +\end{itemize} + +\subsection{What's different in Windows?} + +The Windows version of \Webc{} has some specific features that should be +pointed out. + +\begin{description} +\item[\KPS{}] The hash-tables that \KPS{} builds are quite large for + the \TL{}. In order to cut down the starting time of any + \KPS{}-enabled program, these hash-tables have been put in shared + memory. This way, when you chain the execution of several such + programs, like \path|tex| calling \path|mpost| calling \path|tex|, + the overhead when starting each of the subprograms is + reduced. This change is hidden to the user, except if you set the + debug flag of kpathsea to the \path|-1| value: you will then trace + access to the shared memory, which is not what you want (it is + accessed very often!). What is useful in a log trace of the shared + memory access is still to be defined, so the situation might evolve + in the future. +\item[\cmdname{kpsecheck}] This command provides some options that did + not fit well into \cmdname{kpsewhich}. It will allow you to list all + the files that occur multiple times across your texmf trees. This + could be handy, but most of the time you will also get unwanted + output (like dozens of \path|README| files). It is noticeable + that all these files result in clashes inside the \KPS{}-hashing + mechanism; fortunately, \KPS{} never looks for these files. For + this reason, you can combine the \path|-multiple-occurrences| with 2 + other options for including or excluding any filename that match + some pattern (you can request for several patterns). + + The \cmdname{kpsecheck} command will also report the status of shared + memory: in use or not used. That might be useful to know because if + the status reported is \samp{in use}, that means one or several + processes are working, and the effect of any \cmdname{mktexlsr} + command will be delayed until the next time where no \KPS{} linked + process will be running. + + Last, this same command will report about the location it thinks + Ghostscript can be found. Under Win32, for many programs, it is + easier to use the Ghostscript dll, and find it by using the + Ghostscript registry key than to change the \path|PATH|, which has a + limited length anyway. +\item[\Webc{}] The engines have a few more options than in Unix + \Webc{}, and one option with a different behavior: + \begin{itemize} + \item \path|-halt-on-error| stop the compilation at the first error. + \item \path|-job-time| set the job time to the same timestamp as the + file given in argument. +\item \path|-oem| use the DOS codepage for console output. + \item \path|-output-directory| allow to write all the output files in the + specified directory. + \item \path|-time-statistics| print statistics about the job run + time. It is to be noted that Win9x not being a true multitasking + operating system, it has no reliable timer for short periods, so + the value printed is an approximation. Under NT/2K/XP, the result + is quite accurate with user time and system time values allocated + for this run. For Unix + users: the \path|time| command is not usually available to Windows + users. + \end{itemize} +\end{description} + +\subsection{Personal configurations} +\label{sec:persconf} + +\subsubsection{Dvips} + +The configuration file for dvips can be found in\\ +\verb+C:\TeXLive2005\texmf-var\dvips\config\config.ps+\\ +You may open it with any editor + %(\cmdname{WinShell} will do fine) + and change some parameters: + +\begin{description} +\item [fonts] you can change the default printer \MF{} mode or printer + resolution in case \cmdname{dvips} needs to generate PK fonts. By default it + is configured to use Type~1 versions of the CM fonts, so it should + not call \cmdname{mktexpk} too often; +\item[printer] you can tell dvips where you want to print by default. If + the \optname{o} option is not followed by a printer name, then a + \file{.ps} \PS{} file is written. You can give dvips a printer + name such as: +\begin{verbatim} +o lpt1: +% o | lpr -S server -P myprinter +% o \\server\myprinter +\end{verbatim} +\item[paper] Next, you might want + to change the paper size from European (A4) to US letter + by making the US letter the first paper size mentioned in the file. + Scroll to the group of lines beginning with \code{@}. Move + the appropriate lines so that this section begins with the lines:\\ +\hspace*{1em} @ letterSize 8.5in 11in\\ +\hspace*{1em} @ letter 8.5in 11in\\ +\hspace*{1em} @+ \%\%BeginPaperSize: Letter\\ +\hspace*{1em} @+ letter\\ +\hspace*{1em} @+ \%\%EndPaperSize +\end{description} + +The current \TL{} distribution implements the procedure of making +always up-to-date fontmaps files for Dvips and Pdftex. This is done by +the \cmdname{updmap} program during installation, as well as during any +font package addition. If you add new packages by hand, edit the file +\verb+updmap.cfg+ in \path|$TEXMFVAR/web2c|. + +\subsubsection{PdfTeX} + +If you use the program pdf{}latex to write \acro{PDF} format directly, +and you are using \acro{US} letter-size paper, edit the file +\verb+C:\TeXLive2005\texmf-var\tex\generic\config\pdftexconfig.tex+ and +change \samp{\bs pdfpagewidth} and \samp{\bs pdfpageheight}. These entries +should read: +\begin{alltt} +\bs{}pdfpagewidth=8.5 true in +\bs{}pdfpageheight=11 true in +\end{alltt} +Save the file and exit the editor. + +\subsubsection{GSView} +GSView is now distributed under the Aladdin License, and therefore is no +longer included in \TL{}. + +If you may want to change the page size to US letter size. If so, open +GSView from the \guiseq{Start} menu, and select \guiseq{Media\arw Letter}. + +Also, there are menu settings that are supposed to give you the most +readable screen image. On \guiseq{Media \arw Display Settings}, set both +\optname{Text Alpha} and \optname{Graphics Alpha} to 4~bits. + +Note that the installation process has set all \code{.ps} and +\code{.eps} files to automatically open with \cmdname{GSView}. + +For printing instructions, see section~\ref{printing} below. + +\subsubsection{WinDvi} +\label{sub:windvi} + +The \file{tlpmgui.exe} program takes care of associating the files +with the \file{.dvi} extension with \file{Windvi}, but it doesn't make an icon +on the desktop, so please do it yourself. + +Open \cmdname{windvi} by clicking an icon or from the command line. + +You can set it for US letter-size paper by going to \guiseq{View\arw +Options\arw Papertype} and selecting US (8.5\verb+"+ x 11\verb+"+) (and +then \optname{OK}. Exit \cmdname{windvi}. + +You can change other parameters from there as well, such as the ability +to execute system commands specified by the document (disabled by +default for security reasons). Also, the first time you view any .dvi +file, you may find the magnification too large. Zoom out until you get +an appropriate size. + +All configuration settings for \cmdname{windvi} are stored in a file +named \path|windvi.cnf| file. You can find it by running this command at +the prompt: +\begin{verbatim} +c:\>kpsewhich --expand-var $HOME/windvi.cnf +\end{verbatim} + +Should you have problems with \cmdname{windvi}, please remove the +configuration file and test your problem against a vanilla configuration. + +\subsection{Testing} + +For generic verification procedures, see section~\ref{sec:test-install} +(\p.\pageref{sec:test-install}). This section describes +Windows-specific tests. + +Open the file \verb+sample2e.tex+ in your editor (Xemacs, WinShell), +found in \path|C:\TeXLive2005\texmf-dist\tex\latex\base|. The \LaTeX\ source +should appear on the screen. Process it by clicking on the +\guiseq{Command\arw LaTeX} menu (XEmacs) or \LaTeX\ icon on the toolbar +(WinShell), then view it by clicking on the \guiseq{Command\arw View DVI} +menu (XEmacs) or Preview (Windvi) icon (WinShell). + +At first, when you preview files with Windvi, it will create fonts because +screen fonts were not installed. After a while, you will have created most +of the fonts you use, and you will rarely see the font-creation window. + +\textbf{Hint for the future:} If a \LaTeX\ run stops because \LaTeX\ +cannot find a file, you can press Ctrl-z to quit. + + +\subsection{Printing} +\label{printing} + +It is possible to print from Windvi. In this case, printing will be done +using the Windows unified printer driver. By definition, it is +compatible with all printers. However, there is some drawback: it can +generate some huge spool files, and some (older) versions of Windows +just don't like them. The advantage is that you can use features like +embedding BMP or WMF images. You also need to make sure that the printer +parameters are correctly set (subsection~\ref{sub:windvi}), else you +will get scaled printing (printing at 600\dpi{} on a 300\dpi{} printer +will give you only one quadrant of your page). + +Printing is faster and more reliable if you run \cmdname{dvips} to make +a \filename{.ps} file and then print from \cmdname{GSView}. In +\cmdname{GSview}, select \guiseq{File\arw Print\ldots}. A \guiseq{Print} +window will appear. + +If you are using a \PS{} printer, \textit{be sure to select +\guiseq{\PS{} Printer}}. This is done in the \guiseq{Print Method} box +at the bottom left of the \guiseq{Print} window. You can then select any +of the printers that you have previously installed. If you fail to +check the box for \optname{\PS{} Printer}, printing will not work. + +If you will be using your own non-\PS{} printer, select +\guiseq{Ghostscript device} in the \guiseq{Print Method} box, then click +on the button to the right labelled \guiseq{djet500} and select your +printer type from the list that pops up. (In the older version of +\cmdname{GSView}, make sure \optname{\PS{} Printer} is \textit{not} +selected, then select your printer type from the \guiseq{Device} list.) + +\subsection{Tips and tricks for Win32} + +\subsubsection{Different flavors of Win32} + +What we call Win32 is not an operating system by itself. It is a large +set of functions (around 12,000 in the header files of the Microsoft +\acro{SDK}) that you can use to write programs for different operating +systems of the Windows family. + +Windows comes in different flavors: +\begin{itemize} +\item Win95, Win98 and Win\acro{ME}, which \emph{are not true multitasking, + multithreading} environments. They are the latest\Dash and hopefully + last\Dash metamorphosis of \acro{DOS}. This can be more or less proven + by the fact that when booting, the PC will load the \path|command.com| + interpreter, and if you stop the boot process at this point, you can + ask for the current (\acro{DOS}) version and it will answer something + like \samp{MS-DOS 7.0} (at least for the old versions of Win9x). +\item Windows \acro{NT}, which is a new operating system written from + scratch, capable of true multitasking behavior, and including many + high level features. +\item Windows 2000, based on \acro{NT}, with all the bells and + whistles of Win98. +\item Windows \acro{XP}, which comes with Personal and Pro flavors. This is + the last step in merging both lines of products (Win9x based and + \acro{NT} based). \acro{XP} is based on \acro{NT}. +\end{itemize} + +Win9x are able to run 32~bits programs and 16~bits programs +concurrently. But the operating system by itself is not entirely +written in 32~bits mode, and does not support memory protection: 16bits +applications can overwrite parts of the operating system memory! Some +parts of the system like the \acro{GDI} (Graphical Device Interface) +manage limited resources like bitmaps, fonts, pens and so on for the set +of all programs that run concurrently. All the bitmaps headers available +at the same time can't amount for more than 64kB. This explains the +performance tool and the fact that you can put your system on his knees +by making intensive use of graphic objects for example. + +NT, 2K and XP do not suffer from these limitations, and neither from +other Win9x limitations. They are true multitasking environments, with +protected memory. They are much more responsive than Win9x because +of better memory management, better file system and so on. + +\subsubsection{Command line prompt} + +You may wonder, ``Why would I need to use a command line prompt when +I have Windows?'' + +Good question. The problem is of very general nature. Not all operations +can be done easily using only a \acro{GUI}. Command line gives you +programming power\Dash assuming a clever command interpreter. + +But the problem here is more fundamental: \TeX{} is \emph{a batch} +tool. Not an interactive one. \TeX{} needs to compute the best +layout for each page, resolve cross-references and so on. This can be +done only by a global processing of the document. It is not (yet) a +task that can be done interactively. + +This means that you should use \TeX{} from a command line. In fact the +situation is not so bad. There is an advantage to write command line +tools for complex processing: they are better debugged, because they are +independent of any \acro{GUI} problems, and \acro{GUI} tools can be +designed to interface to the command line tools. This is the case for +\TeX{}, where you will mostly interact with it through a \acro{GUI} text +editor. + +However, you may need to use the command line prompt in a number of +situations. One is when you are having difficulties and want to debug +your setup. + +\begin{description} + \item[Win9x] You can open a command line prompt by looking either for + the \acro{MS-DOS} icon in the \guiseq{Start\arw Programs} menu, + or by choosing \guiseq{Start\arw Run} menu typing in + \path|command.com| as the progrm name. + \item[NT, 2K, XP] You can open a command line prompt by looking for + \guiseq{Command Prompt} in the \guiseq{Start\arw Accessories} menu. + You can also choose \guiseq{Start\arw Run} and type in + \path|cmd.exe|, which is the name of the brand new command + interpreter for \acro{NT} (thus, it is untrue to call this a + \emph{DOS} box!). +\end{description} + +These locations may change across different Windows versions. + +\subsubsection{Path separators} + +The Win32 API understands both \path|/| and \path|\| characters as PATH +separators. But the command interpreters do not! So whenever a path name +is used programmatically, you can use both separators, and even mix them +up in the same path name. But on the command line, you must type +\path|\| as path separator. The reason is compatibility: the command +processor used \samp{/} to introduce arguments to commands. + +All this to say: do not be surprised to read path names written using +the Unix convention; \fpTeX{} is a port of \Webc, and aims to be compatible +across platforms. For this reason, all the configuration files that +need to specify path names use the Unix convention. + +\subsubsection{File systems} +\label{sec:clusters} + +The worst feature of Win9x with regard to \TeX{} is probably the +so-called FAT file system. \TeX{} uses very many small files, with size +around 1--3kB. The \acro{FAT} file system is old, and predates by +decades the multi-gigabytes hard disks we have today. As a result, it +cannot manage efficiently the tens of thousands of \TeX{} files found in +\TL{}. The \acro{FAT} file system allocates a minimum of 32kB for +\emph{any} file on a huge partition. It means that \TeX{} will use much +more disk space than it actually needs. + +The other, more modern, file systems available, \acro{FAT32} and +\acro{NTFS}, do not have this drawback. They manage clusters of 4kB +only. (You can lower the limit to 512 bytes on \acro{NTFS}.) + +\subsubsection{How to add some directory to your PATH} + +There are pairs of variables and values which behave much like global +variables inside your programs. The set of those variables is called the +environment. Each program is initialized with a copy of the +environment when it is run. It can request and change the +value of any variable. The changes happen in the copy of the +environment, and is not at all propagated to the other running +programs. + +Your PATH is a special environment variable used to search for +programs you want to run. +There is a different procedure to change it for Win9x, WinME and NT/2K/XP: + +\begin{description} +\item[Windows 95/98] Edit your \path|autoexec.bat|. In this file should be a line + starting with \texttt{PATH=} and followed by a list of directories separated + by \path|;|. Please add the directory with the executables in this line. + After this, this line could look as follows: +\begin{verbatim} +PATH=c:\windows;c:\windows\system;c:\TeXLive2005\bin\win32 +\end{verbatim} +\item[Windows ME] You need to run the special program + \path|c:\windows\system\msconfig.exe| to be able to change any + environment variable. From this program, select the `Environment' + tab, and then add or modify the variable you want. You will be asked to reboot the + machine upon any change. +\item[Windows NT/2K/XP] + Click left on \guiseq{Start \arw Settings \arw Control Panel}. Now the + window with the control panel icons opens. Double click on System. The + System Properties window opens. Click on the tab \textsf{Environment} + or look for a button named \guiseq{Environment Variables} among the + dialog boxes. Now you can change the environment variables for your + user account. Note: There are also displayed the environment settings + for the system. Normally, you can't change the system variables + unless you have administrator rights on your machine. If you want to + change the \texttt{PATH} for all users, you will have to contact your + system administrator or be the system administrator yourself\Dash in + the latter case you should know what you are doing. + + If there is already a \texttt{PATH} setting for your user account, + left click on \texttt{PATH}. In the field \textsf{Variable} appears + \texttt{PATH} while the field Value shows the current setting of + \texttt{PATH} as a list of directories separated by \path|;|. Add + the directory where the executables are located (e.g. + \path|c:\TeXLive2005\bin\win32|). If there isn't a \texttt{PATH} variable + for your user account, simply click in the field Variable and type + in \texttt{PATH}, click in the field \textsf{Value} + and type in the directory with the executables. Important: Click on + the \textsf{Apply} button before clicking \textsf{Ok}, otherwise the + changes to \texttt{PATH} won't apply to your system. Be careful when + changing the environment settings. +\end{description} + +The best way to be sure that a variable has been properly set is to +open a console and type: +\begin{verbatim} +set VARIABLE +\end{verbatim} +which should return the corresponding value. + +\subsubsection{\TeX{} engines} + +If you have a look at the \Webc{} documentation, you will read that all +the various \TeX{} derived programs use the same base engine. For +example, \path|tex.exe| and \path|latex.exe| are exact copies of the +same program, but each one will use a different format file, based on +its calling name. + +Under Unix, this feature is implemented through \emph{symbolic +links}. It saves up a bit of disk space, because some engines are +used with many different format files. + +The Win32 API does not know about file links. So to save up almost +the same amount of memory, all the \TeX{} base engines have been put +in DLLs (\emph{Dynamic Linked Library}). This means that you will have +the following layout: +\begin{alltt} +18/09/2005 14:19 3 584 latex.exe +18/09/2005 14:19 3 584 pdfetex.exe +18/09/2005 14:19 524 288 tl90pdfetex.dll +\end{alltt} +and the \path|latex.exe| file is nothing but a rough copy of +\path|pdfetex.exe| using the same core \path|tl90pdfetex.dll|. +The same trick has been used for the \path|mktex*.exe| family of programs +which are linked to the \path|mktex.dll| library. + +In fact, a generic tool called \path|irun.exe| is provided to build the +equivalent of Unix hard links for executable files only under Win32. + +\subsection{In case of problems} +\label{sec:troubleshooting} + +\subsubsection{What to do if \texttt{latex} does not find your files?} + +\begin{itemize} + +\item \cmdname{kpsewhich} is the tool of choice to debug any +problem. Unfortunately, \cmdname{kpsewhich} outputs debug information +to stderr, and the older Windows consoles do not know how to redirect stderr +to a file. (NT and Windows 2000 consoles know how to do that. But +the trick will work for any console.) For diagnostic purposes you can +temporarily set an environment variable (in a \acro{DOS} box): + +\begin{verbatim} +SET KPATHSEA_DEBUG_OUTPUT=err.log +\end{verbatim} +You can also set the debug level: +\begin{verbatim} +SET KPATHSEA_DEBUG=-1 +\end{verbatim} + +If you want to redirect stderr to stdout, which is not possible +Windows, then do: +\begin{verbatim} +SET KPATHSEA_DEBUG_OUTPUT=con: +\end{verbatim} +This way you can capture both stdout and stderr in the same file. + +\item Assuming the installation has been done in \path|c:/TeX|, check + the following values: \\ + {\small + \begin{tabular}{ll} + \path|kpsewhich -expand-path $SELFAUTOPARENT| & \path|c:/TeX| \\ + \path|kpsewhich -expand-path $TEXMF| & \path|c:/TeX/texmf....| \\ + \path|kpsewhich -expand-path $TEXMFCNF| & + \path|.;c:/TeX/texmf-var/web2c;| \\ + \path|kpsewhich -expand-var $TEXINPUTS| & \path|.;c:/TeX/texmf/tex//| + \end{tabular} +} +\item If you have other \TeX{}-related values already set in your + environment, please, remove them. They are overriding the ones in + texmf.cnf. +\item Check the values from:\\ +{\small + \begin{tabular}{ll} + \texttt{kpsewhich cmr10.tfm} & \path|c:/TeX/texmf/fonts/tfm/public/cm/cmr10.tfm|\\ + \texttt{kpsewhich latex.fmt}& \path|c:/TeX/texmf/web2c/latex.fmt| + \end{tabular} +} +\item At this point, if everything is correct, \TeX{} and friends + should work. If it is not the case, you will need to play with + the \path|-debug=n| option from \path|kpsewhich|, and check back all + the values. Try to identify and report the problem. +\end{itemize} + +\subsubsection{What to do if your setup still does not work as expected?} + +Here are several questions to investigate: + +\begin{enumerate} +\item Is \file{tex.exe} in my \path|PATH|? + +\item Is the \path|TEXMFCNF| variable correctly set to +\path|c:/TeXLive2005/texmf-var/web2c| (default value)? + +\item Are there any errors in the log file generated by the +\file{tlmpgui.exe} program? +\file{tlmpgui.log} can be found in your +\file{TEMP} directory. You can find this by searching for the +string \samp{Error}. Hint: the log file can show some errors after +building all format files. Please do not panic: perhaps some formats +weren't already installed. + +\item Are there any relevant bug fixes at \url{http://tug.org/texlive/}? +(Unlikely, but it doesn't hurt to check.) + +\end{enumerate} + +The \TL{} software consists of hundreds of programs and tens of +thousands of files, all from varying sources. So it is quite difficult to +predict all possible causes for problems. Nevertheless, we will do our +best to help you. (See section~\ref{sec:help}, \p.\pageref{sec:help}.) + +% don't use \Webc so the \uppercase in the headline works. +\section{A user's guide to Web2C} + +\Webc{} is an integrated collection of \TeX-related programs: \TeX{} +itself, \MF{}, \MP, \BibTeX{}, etc. It is the heart of \TL{}. + +A bit of history: The original implementation was by Tomas Rokicki who, +in 1987, developed a first \TeX{}-to-C system based on change files +under Unix, which were primarily the original work of Howard Trickey and +Pavel Curtis. Tim Morgan became the maintainer of the system, and +during this period the name changed to Web-to-C\@. In 1990, Karl Berry +took over the work, assisted by dozens of additional contributors, and +in 1997 he handed the baton to Olaf Weber. + +The \Webc{} system runs on Unix, 32-bit Windows systems, \MacOSX{}, and +other operating systems. It uses Knuth's original sources for \TeX{} and +other basic programs written in \web{} and translates them into C source +code. The core \TeX{} programs are: + +\begin{cmddescription} +\item[bibtex] Maintaining bibliographies. +\item[dmp] \cmdname{troff} to MPX (\MP{} pictures). +\item[dvicopy] Expands virtual font references in \dvi{} files. +\item[dvitomp] \dvi{} to MPX (MetaPost pictures). +\item[dvitype] \dvi{} to human-readable text. +\item[gftodvi] Generic font proofsheets. +\item[gftopk] Generic to packed fonts. +\item[gftype] GF to human-readable text. +\item[makempx] \MP{} label typesetting. +\item[mf] Creating typeface families. +\item[mft] Prettyprinting \MF{} source. +\item[mpost] Creating technical diagrams. +\item[mpto] MetaPost label extraction. +\item[newer] Compare modification times. +\item[patgen] Creating hyphenation patterns. +\item[pktogf] Packed to generic fonts. +\item[pktype] PK to human-readable text. +\item[pltotf] Plain text property list to TFM. +\item[pooltype] Display \web{} pool files. +\item[tangle] \web{} to Pascal. +\item[tex] Typesetting. +\item[tftopl] TFM to plain text property list. +\item[vftovp] Virtual font to virtual property list. +\item[vptovf] Virtual property list to virtual font. +\item[weave] \web{} to \TeX. +\end{cmddescription} + +\noindent The precise functions and syntax of these programs are +described in the documentation of the individual packages and of \Webc{} +itself. However, knowing a few principles governing the whole family of +programs will help you take advantage of your \Webc{} installation. + +All programs honor these standard \acro{GNU} options: +\begin{ttdescription} +\item[-{}-help] print basic usage summary. +\item[-{}-verbose] print detailed progress report. +\item[-{}-version] print version information, then exit. +\end{ttdescription} + +For locating files the \Webc{} programs use the path searching library +\KPS{}. This library uses a combination of environment variables and a +configuration files to optimize searching the (huge) collection of +\TeX{} files. \Webc{} can look at more than one directory tree +simultaneously, which is useful in maintaining \TeX's standard +distribution and local extensions in two distinct trees. To speed up +file searches the root of each tree has a file \file{ls-R}, containing +an entry showing the name and relative pathname for all files under that +root. + +\subsection{Kpathsea path searching} + +Let us first describe the generic path searching mechanism of the \KPS{} +library. + +We call a \emph{search path} a colon- or semicolon\hyph sepa\-rated list +of \emph{path elements}, which are basically directory names. A +search path can come from (a combination of) many sources. To look up +a file \samp{my-file} along a path \samp{.:/dir}, \KPS{} checks each +element of the path in turn: first \file{./my-file}, then +\file{/dir/my-file}, returning the first match (or possibly all +matches). + +In order to adapt optimally to all operating systems' conventions, on +non-Unix systems \KPS{} can use filename separators different from +colon (\samp{:}) and slash (\samp{/}). + +To check a particular path element \var{p}, \KPS{} first checks if a +prebuilt database (see ``Filename data\-base'' on +page~\pageref{Filename-database}) applies to \var{p}, i.e., if the database +is in a directory that is a prefix of \var{p}. If so, the path +specification is matched against the contents of the database. + +If the database does not exist, or does not apply to this path +element, or contains no matches, the filesystem is searched (if this +was not forbidden by a specification starting with \samp{!!}\ and if +the file being searched for must exist). \KPS{} constructs the list +of directories that correspond to this path element, and then checks +in each for the file being sought. + +The ``file must exist'' condition comes into play with \samp{.vf} files and +input files read by \TeX's \cs{openin} command. Such files may not +exist (e.g., \file{cmr10.vf}), and so it would be wrong to search the +disk for them. Therefore, if you fail to update \file{ls-R} when you +install a new \samp{.vf} file, it will never be found. +Each path element is checked in turn: first the database, then the +disk. If a match is found, the search stops and the result is +returned. + +Although the simplest and most common path element is a directory +name, \KPS{} supports additional features in search paths: layered +default values, environment variable names, config file values, users' +home directories, and recursive subdirectory searching. Thus, we say +that \KPS{} \emph{expands} a path element, meaning it transforms all +the specifications into basic directory name or names. This is +described in the following sections in the same order as it takes +place. + +Note that if the filename being searched for is absolute or explicitly +relative, i.e., starts with \samp{/} or \samp{./} or \samp{../}, +\KPS{} simply checks if that file exists. + +\ifSingleColumn +\else +\begin{figure*} +\verbatiminput{examples/ex5.tex} +\setlength{\abovecaptionskip}{0pt} + \caption{An illustrative configuration file sample} + \label{fig:config-sample} +\end{figure*} +\fi + +\subsubsection{Path sources} +\label{Path-sources} + +A search path can come from many sources. In the order in which +\KPS{} uses them: + +\begin{enumerate} +\item + A user-set environment variable, for instance, \envname{TEXINPUTS}\@. + Environment variables with a period and a program name appended + override; e.g., if \samp{latex} is the name of the program being run, + then \envname{TEXINPUTS.latex} will override \envname{TEXINPUTS}. +\item + A program-specific configuration file, for exam\-ple, a line + \samp{S /a:/b} in \cmdname{dvips}'s \file{config.ps}. +\item A \KPS{} configuration file \file{texmf.cnf}, containing a line like + \samp{TEXINPUTS=/c:/d} (see below). +\item The compile-time default. +\end{enumerate} +\noindent You can see each of these values for a given +search path by using the debugging options (see ``Debugging actions'' +on page~\pageref{Debugging}). + +\subsubsection{Config files} + +\begingroup\tolerance=3500 +\KPS{} reads \emph{runtime configuration files} named \file{texmf.cnf} +for search path and other definitions. The search path used to look +for these files is named \envname{TEXMFCNF} (by default such a file lives +in the \file{texmf/web2c} subdirectory). \emph{All} +\file{texmf.cnf} files in the search path will be read and definitions +in earlier files override those in later files. Thus, with a search +path of \verb|.:$TEXMF|, values from \file{./texmf.cnf} override those +from \verb|$TEXMF/texmf.cnf|. +\endgroup + +\begin{itemize} +\item + Comments start with \code{\%} and continue to the end of the line. +\item + Blank lines are ignored. +\item + A \bs{} at the end of a line acts as a continuation character, + i.e., the next line is appended. Whitespace at the beginning of + continuation lines is not ignored. +\item + Each remaining line has the form: +\begin{alltt} + \var{variable}[.\var{progname}] [=] \var{value} +\end{alltt}% + where the \samp{=} and surrounding whitespace are optional. +\item + The \ttvar{variable} name may contain any character other + than whitespace, \samp{=}, or \samp{.}, but sticking to + \samp{A-Za-z\_} is safest. +\item + If \samp{.\var{progname}} is present, the definition only + applies if the program that is running is named + \texttt{\var{progname}} or \texttt{\var{progname}.exe}. This allows + different flavors of \TeX{} to have different search paths, for + example. +\item \var{value} may contain any characters except + \code{\%} and \samp{@}. The + \code{\$\var{var}.\var{prog}} feature is not available on the + right-hand side; instead, you must use an additional variable. A + \samp{;}\ in \var{value} is translated to \samp{:}\ if + running under Unix; this is useful to be able to have a single + \file{texmf.cnf} for Unix, \acro{MS-DOS} and Windows systems. +\item + All definitions are read before anything is expanded, so + variables can be referenced before they are defined. +\end{itemize} +A configuration file fragment illustrating most of these points is +\ifSingleColumn +shown below: + +\verbatiminput{examples/ex5.tex} +\else +shown in Figure~\ref{fig:config-sample}. +\fi + +\subsubsection{Path expansion} +\label{Path-expansion} + + +\KPS{} recognizes certain special characters and constructions in +search paths, similar to those available in Unix shells. As a +general example, the complex path, +\verb+~$USER/{foo,bar}//baz+, expands to all subdirectories under +directories \file{foo} and \file{bar} in \texttt{\$USER}'s home +directory that contain a directory or file \file{baz}. These +expansions are explained in the sections below. +%$ +\subsubsection{Default expansion} +\label{Default-expansion} + +\tolerance=2500 +If the highest-priority search path (see ``Path sources'' on +page~\pageref{Path-sources}) contains an \emph{extra colon} (i.e., +leading, trailing, or doubled), \KPS{} inserts at that point the +next-highest-prio\-rity search path that is defined. If that inserted +path has an extra colon, the same happens with the next highest. For +example, given an environment variable setting + +\tolerance=1500 + +\begin{alltt} +> \Ucom{setenv TEXINPUTS /home/karl:} +\end{alltt} +and a \code{TEXINPUTS} value from \file{texmf.cnf} of + +\begin{alltt} + .:\$TEXMF//tex +\end{alltt} +then the final value used for searching will be: + +\begin{alltt} + /home/karl:.:\$TEXMF//tex +\end{alltt} + +Since it would be useless to insert the default value in more than one +place, \KPS{} changes only one extra \samp{:}\ and leaves any others in +place. It checks first for a leading \samp{:}, then a trailing +\samp{:}, then a doubled \samp{:}. + +\subsubsection{Brace expansion} + +A useful feature is brace expansion, which means that, for instance, +\verb+v{a,b}w+ expands to \verb+vaw:vbw+. Nesting is allowed. +This is used to implement multiple \TeX{} hierarchies, by +assigning a brace list to \code{\$TEXMF}. +For example, in \file{texmf.cnf}, the following definition +(appproximately; there are actually even more trees) is made: +\begin{verbatim} + TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN} +\end{verbatim} +Using this you can then write something like +\begin{verbatim} + TEXINPUTS = .;$TEXMF/tex// +\end{verbatim} +%$ +which means that, after looking in the current directory, the +\code{\$TEXMFHOME/tex}, \code{\$TEXMFLOCAL/tex}, \code{\$TEXMFVAR/tex} +and \code{\$TEXMFMAIN/tex} trees \emph{only}) will be searched (the +last two use using \file{ls-R} data base files). It is a convenient +way for running two parallel \TeX{} structures, one ``frozen'' (on a +\CD, for instance) and the other being continuously updated with new +versions as they become available. By using the \code{\$TEXMF} +variable in all definitions, one is sure to always search the +up-to-date tree first. + +\subsubsection{Subdirectory expansion} +\label{Subdirectory-expansion} + +Two or more consecutive slashes in a path element following a directory +\var{d} is replaced by all subdirectories of \var{d}: first those +subdirectories directly under \var{d}, then the subsubdirectories under +those, and so on. At each level, the order in which the directories are +searched is \emph{unspecified}. + +If you specify any filename components after the \samp{//}, only +subdirectories with matching components are included. For example, +\samp{/a//b} expands into directories \file{/a/1/b}, \file{/a/2/b}, +\file{/a/1/1/b}, and so on, but not \file{/a/b/c} or \file{/a/1}. + +Multiple \samp{//} constructs in a path are possible, but +\samp{//} at the beginning of a path is ignored. + +\subsubsection{List of special characters and their meaning: a summary} + +The following list summarizes the special characters in \KPS{} +configuration files. + +% need a wider space for the item labels here. +\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} +\begin{ttdescription} +\item[\CODE{:}] Separator in path specification; at the beginning or + the end of a path it substitutes the default path expansion.\par +\item[\CODE{;}] Separator on non-Unix systems (acts like \code{:}). +\item[\CODE{\$}] Variable expansion. +\item[\CODE{\string~}] Represents the user's home directory. +\item[\CODE{\char`\{...\char`\}}] Brace expansion. +\item[\CODE{//}] Subdirectory expansion (can occur anywhere in + a path, except at its beginning). +\item[\CODE{\%}] Start of comment. +\item[\CODE{\bs}] Continuation character (allows multi-line entries). +\item[\CODE{!!}] Search \emph{only} database to locate file, \emph{do + not} search the disk. +\end{ttdescription} + + +\subsection{Filename databases} +\label{Filename-database} + +\KPS{} goes to some lengths to minimize disk accesses for searches. +Nevertheless, at installations with enough directories, searching each +possible directory for a given file can take an excessively long time +(this is especially true if many hundreds of font directories have to +be traversed.) Therefore, \KPS{} can use an externally-built plain text +``database'' file named \file{ls-R} that maps files to directories, +thus avoiding the need to exhaustively search the disk. + +A second database file \file{aliases} allows you to give additional +names to the files listed in \file{ls-R}. This can be helpful to +confirm to \acro{DOS} 8.3 filename conventions in source files. + +\subsubsection{The filename database} +\label{ls-R} + +As explained above, the name of the main filename database must be +\file{ls-R}. You can put one at the root of each \TeX{} hierarchy in +your installation that you wish to be searched (\code{\$TEXMF} by +default); most sites have only one hierarchy. \KPS{} looks for +\file{ls-R} files along the \code{TEXMFDBS} path. + +The recommended way to create and maintain \samp{ls-R} is to run the +\code{mktexlsr} script included with the distribution. It is invoked +by the various \samp{mktex}\dots\ scripts. In principle, this script +just runs the command +\begin{alltt} +cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R +\end{alltt} +presuming your system's \code{ls} produces the right output format +(\acro{GNU} \code{ls} is all right). To ensure that the database is +always up-to-date, it is easiest to rebuild it regularly via +\code{cron}, so that it is automatically updated when the installed +files change, such as after installing or updating a \LaTeX{} package. + +If a file is not found in the database, by default \KPS{} goes ahead +and searches the disk. If a particular path element begins with +\samp{!!}, however, \emph{only} the database will be searched for that +element, never the disk. + + +\subsubsection{kpsewhich: Standalone path searching} +\label{Invoking-kpsewhich} + +The \texttt{kpsewhich} program exercises path searching independent of any +particular application. This can be useful as a sort of \code{find} +program to locate files in \TeX{} hierarchies (this is used heavily in +the distributed \samp{mktex}\dots\ scripts). + +\begin{alltt} +> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} +\end{alltt} +The options specified in \ttvar{option} start with either \samp{-} +or \samp{-{}-}, and any unambiguous abbreviation is accepted. + +\KPS{} looks up each non-option argument on the command line as a +filename, and returns the first file found. There is no option to +return all the files with a particular name (you can run the Unix +\samp{find} utility for that). + +The more important options are described next. + +\begin{ttdescription} +\item[\texttt{-{}-dpi=\var{num}}]\mbox{} + Set the resolution to \ttvar{num}; this only affects \samp{gf} + and \samp{pk} lookups. \samp{-D} is a synonym, for compatibility + with \cmdname{dvips}. Default is 600. + +\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ + Set the format for lookup to \ttvar{name}. By default, the + format is guessed from the filename. For formats which do not have + an associated unambiguous suffix, such as \MP{} support files and + \cmdname{dvips} configuration files, you have to specify the name as + known to \KPS{}, such as \texttt{tex} or \texttt{enc files}. Run + \texttt{kpsewhich -{}-help} for a list. + +\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ + Set the mode name to \ttvar{string}; this only affects \samp{gf} + and \samp{pk} lookups. No default: any mode will be found. +\item[\texttt{-{}-must-exist}]\mbox{}\\ + Do everything possible to find the files, notably including + searching the disk. By default, only the \file{ls-R} database is + checked, in the interest of efficiency. +\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ + Search along the path \ttvar{string} (colon-separated as usual), + instead of guessing the search path from the filename. \samp{//} and + all the usual expansions are supported. The options \samp{-{}-path} + and \samp{-{}-format} are mutually exclusive. +\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ + Set the program name to \texttt{\var{name}}. + This can affect the search paths via the \texttt{.\var{progname}} + feature. + The default is \cmdname{kpsewhich}. +\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ + shows the path used for file lookups of file type \texttt{\var{name}}. + Either a filename extension (\code{.pk}, \code{.vf}, etc.) or a + name can be used, just as with \samp{-{}-format} option. +\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ + sets the debugging options to \texttt{\var{num}}. +\end{ttdescription} + + +\subsubsection{Examples of use} +\label{SExamplesofuse} + +Let us now have a look at \KPS{} in action. Here's a straightforward search: + +\begin{alltt} +> \Ucom{kpsewhich article.cls} + /usr/local/texmf-dist/tex/latex/base/article.cls +\end{alltt} +We are looking for the file \file{article.cls}. Since the \samp{.cls} +suffix is unambiguous we do not need to specify that we want to look for a +file of type \optname{tex} (\TeX{} source file directories). We find it in +the subdirectory \file{tex/latex/base} below the \samp{texmf-dist} \TL\ +directory. Similarly, all of the following are found without problems +thanks to their unambiguous suffix. +\begin{alltt} +> \Ucom{kpsewhich array.sty} + /usr/local/texmf-dist/tex/latex/tools/array.sty +> \Ucom{kpsewhich latin1.def} + /usr/local/texmf-dist/tex/latex/base/latin1.def +> \Ucom{kpsewhich size10.clo} + /usr/local/texmf-dist/tex/latex/base/size10.clo +> \Ucom{kpsewhich small2e.tex} + /usr/local/texmf-dist/tex/latex/base/small2e.tex +> \Ucom{kpsewhich tugboat.bib} + /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib +\end{alltt} + +That last is a \BibTeX{} bibliography database for \textsl{TUGBoat} articles. + +\begin{alltt} +> \Ucom{kpsewhich cmr10.pk} +\end{alltt} +Font bitmap glyph files of type \file{.pk} are used by display +programs like \cmdname{dvips} and \cmdname{xdvi}. Nothing is returned in +this case since there are no pre-generated Computer Modern \samp{.pk} +files in \TL{}\Dash the Type~1 variants are used by default. +\begin{alltt} +> \Ucom{kpsewhich wsuipa10.pk} +\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk +\else /usr/local/texmf-var/fonts/pk/ljfour/public/ +... wsuipa/wsuipa10.600pk +\fi\end{alltt} + +For these fonts (a phonetic alphabet from the University of Washington) +we had to generate \samp{.pk} files, and since the default \MF{} mode on +our installation is \texttt{ljfour} with a base resolution of 600\dpi{} +(dots per inch), this instantiation is returned. +\begin{alltt} +> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} +\end{alltt} +In this case, when specifying that we are interested in a resolution +of 300\dpi{} (\texttt{-dpi=300}) we see that no such font is available on +the system. A program like \cmdname{dvips} or \cmdname{xdvi} would +go off and actually build the required \texttt{.pk} files +using the script \cmdname{mktexpk}. + +Next we turn our attention to \cmdname{dvips}'s header and configuration +files. We first look at one of the commonly used files, the general +prolog \file{tex.pro} for \TeX{} support, before turning our attention +to the generic configuration file (\file{config.ps}) and the \PS{} font +map \file{psfonts.map}\Dash as of 2004, map and encoding files have +their own search paths and new location in \dirname{texmf} trees. As +the \samp{.ps} suffix is ambiguous we have to specify explicitly which +type we are considering (\optname{dvips config}) for the file +\texttt{config.ps}. +\begin{alltt} +> \Ucom{kpsewhich tex.pro} + /usr/local/texmf/dvips/base/tex.pro +> \Ucom{kpsewhich --format="dvips config" config.ps} + /usr/local/texmf/dvips/config/config.ps +> \Ucom{kpsewhich psfonts.map} + /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map +\end{alltt} + +We now take a closer look at the \acro{URW} Times \PS{} support +files. The prefix for these in the standard font naming scheme is +\samp{utm}. The first file we look at is the configuration file, +which contains the name of the map file: +\begin{alltt} +> \Ucom{kpsewhich --format="dvips config" config.utm} + /usr/local/texmf-dist/dvips/psnfss/config.utm +\end{alltt} +The contents of that file is +\begin{alltt} + p +utm.map +\end{alltt} +which points to the file \file{utm.map}, which we want to +locate next. +\begin{alltt} +> \Ucom{kpsewhich utm.map} + /usr/local/texmf-dist/fonts/map/dvips/times/utm.map +\end{alltt} +This map file defines the file names of the Type~1 \PS{} fonts in +the URW collection. Its contents look like (we only show part of the +lines): +\begin{alltt} +utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} +\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb +\else /usr/local/texmf-dist/fonts/type1/ +... urw/utm/utmr8a.pfb +\fi\end{alltt} + +It should be evident from these examples how you can easily locate the +whereabouts of a given file. This is especially important if you suspect +that the wrong version of a file is picked up somehow, since +\cmdname{kpsewhich} will show you the first file encountered. + +\subsubsection{Debugging actions} +\label{Debugging} + +Sometimes it is necessary to investigate how a program resolves file +references. To make this practical, \KPS{} offers various levels of +debugging output: + +\begin{ttdescription} +\item[\texttt{\ 1}] \texttt{stat} calls (disk lookups). When running + with an up-to-date \file{ls-R} database this should almost give no + output. +\item[\texttt{\ 2}] References to hash tables (such as \file{ls-R} + databases, map files, configuration files). +\item[\texttt{\ 4}] File open and close operations. +\item[\texttt{\ 8}] General path information for file types + searched by \KPS. This is useful to find out where a particular + path for the file was defined. +\item[\texttt{16}] Directory list for each path element (only relevant + for searches on disk). +\item[\texttt{32}] File searches. +\end{ttdescription} +A value of \texttt{-1} will set all the above options; in practice, +this is usually the most convenient. + +Similarly, with the \cmdname{dvips} program, by setting a combination of +debug switches, one can follow in detail where files are being picked up +from. Alternatively, when a file is not found, the debug trace shows in +which directories the program looks for the given file, so that one can +get an indication what the problem~is. + +Generally speaking, as most programs call the \KPS{} library +internally, one can select a debug option by using the +\envname{KPATHSEA\_DEBUG} environment variable, and setting it to (a +combination of) values as described in the above list. + +(Note for Windows users: it is not easy to redirect +all messages to a file in this system. For diagnostic purposes +you can temporarily \texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log}). + +Let us consider, as an example, a small \LaTeX{} source file, +\file{hello-world.tex}, which contains the following input. +\begin{verbatim} + \documentclass{article} + \begin{document} + Hello World! + \end{document} +\end{verbatim} +This little file only uses the font \file{cmr10}, so let us look at +how \cmdname{dvips} prepares the \PS{} file (we want to use the Type~1 +version of the Computer Modern fonts, hence the option \texttt{-Pcms}). +\begin{alltt} +> \Ucom{dvips -d4100 hello-world -Pcms -o} +\end{alltt} +In this case we have combined \cmdname{dvips}'s debug class 4 (font +paths) with \KPS's path element expansion (see \cmdname{dvips} Reference +Manual, \OnCD{texmf/doc/html/dvips/dvips_toc.html}). +The output (slightly rearranged) appears in +Figure~\ref{fig:dvipsdbga}. +\begin{figure*}[tp] +\centering +\input{examples/ex6a.tex} +\caption{Finding configuration files}\label{fig:dvipsdbga} + +\bigskip + +\input{examples/ex6b.tex} +\caption{Finding the prolog file}\label{fig:dvipsdbgb} + +\bigskip + +\input{examples/ex6c.tex} +\caption{Finding the font file}\label{fig:dvipsdbgc} +\end{figure*} + +\cmdname{dvips} starts by locating its working files. First, +\file{texmf.cnf} is found, which gives the definitions of the search +paths for the other files, then the file database \file{ls-R} (to +optimize file searching) and the file \file{aliases}, which makes it +possible to declare several names (e.g., a short \acro{DOS}-like 8.3 and +a more natural longer version) for the same file. Then \cmdname{dvips} +goes on to find the generic configuration file \file{config.ps} +before looking for the customization file \file{.dvipsrc} (which, in +this case is \emph{not found}). Finally, \cmdname{dvips} locates the +config file for the Computer Modern \PS{} fonts \file{config.cms} +(this was initiated with the \texttt{-Pcms} option on the \cmdname{dvips} +command). This file contains the list of the map files which +define the relation between the \TeX{}, \PS{} and file system +names of the fonts. +\begin{alltt} +> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} + p +ams.map + p +cms.map + p +cmbkm.map + p +amsbkm.map +\end{alltt} +\cmdname{dvips} thus goes on to find all these files, plus the generic +map file \file{psfonts.map}, which is always loaded (it contains +declarations for commonly used \PS{} fonts; see the last part of +Section \ref{SExamplesofuse} for more details about \PS{} map +file handling). + +At this point \cmdname{dvips} identifies itself to the user: +\begin{alltt} +This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) +\end{alltt} +\ifSingleColumn +Then it goes on to look for the prolog file \file{texc.pro}: +\begin{alltt}\small +kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro +\end{alltt} +\else +Then it goes on to look for the prolog file \file{texc.pro} (see +Figure~\ref{fig:dvipsdbgb}). +\fi + +After having found the file in question, \cmdname{dvips} outputs +date and time, and informs us that it will generate the +file \file{hello-world.ps}, then that it needs the font file +\file{cmr10}, and that the latter is declared as ``resident'' (no +bitmaps needed): +\begin{alltt}\small +TeX output 1998.02.26:1204' -> hello-world.ps +Defining font () cmr10 at 10.0pt +Font cmr10 is resident. +\end{alltt} +Now the search is on for the file \file{cmr10.tfm}, which is found, +then a few more prolog files (not shown) are referenced, and finally +the Type~1 instance \file{cmr10.pfb} of the font is located and +included in the output file (see last line). +\begin{alltt}\small +kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, + path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: + /var/tex/fonts/tfm//). +kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm +kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, + ... + +kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb +[1] +\end{alltt} + +\subsection{Runtime options} + +Another useful feature of \Webc{} is its possibility to control a number +of memory parameters (in particular, array sizes) via the runtime file +\file{texmf.cnf} read by \KPS{}. The memory settings can be found in +Part 3 of that file in the \TL{} distribution. The more important +are: + +\begin{ttdescription} +\item[\texttt{main\_memory}] + Total words of memory available, for + \TeX{}, \MF{} and \MP. You must make a new format file for each + different setting. For instance, you could generate a ``huge'' + version of \TeX{}, and call the format file \texttt{hugetex.fmt}. + Using the standard way of specifying the program name used by \KPS{}, + the particular value of the \texttt{main\_memory} variable will then + be read from \file{texmf.cnf}. + etc.). +\item[\texttt{extra\_mem\_bot}] + Extra space for ``large'' \TeX{} data structures: + boxes, glue, breakpoints, etc. Especially useful if you use + \PiCTeX{}. +\item[\texttt{font\_mem\_size}] + Number of words for font information available for \TeX. This + is more or less the total size of all TFM files read. +\item[\texttt{hash\_extra}] + Additional space for the hash table of control sequence names. + Approximately 10,000 control sequences can be stored in the main + hash table; if you have a large book with numerous cross-references, + this might not be enough. The default value of + \texttt{hash\_extra} is \texttt{50000}. +\end{ttdescription} + +\noindent Of course, this facility is no substitute for truly dynamic +arrays and memory allocation, but since these are extremely difficult to +implement in the present \TeX{} source, these runtime parameters provide +a practical compromise allowing some flexibility. + + +\begin{comment} +\section{Building on a new Unix platform} + +If you have a platform for which executables are not included, you will +need to compile \TeX{} and friends. This is not as hard as it +sounds. What you need is all in the directory \texttt{source} in the +distribution. + +\subsection{Prerequisites} + +You will need at least 100 megabytes of disk space to compile all of +\TeX{} and its support programs. You'll also need an \acro{ANSI} C +compiler, a \cmdname{make} utility, a lexical scanner, and a parser +generator. We recommend the \acro{GNU} version of these programs +(\cmdname{gcc}, \acro{GNU} \cmdname{make}, \cmdname{m4}, \cmdname{flex}, +\cmdname{bison}). You may be able to work with other C compilers and +\cmdname{make} programs, but you will need a good understanding of +building Unix programs to sort out problems. + +Also, the command \texttt{uname} must return a sensible value. + + +\subsection{Configuration} + +To begin, perform a normal installation of \TL{} to your disk (see +section~\ref{sec:unix-install-disk} on +\p.\pageref{sec:unix-install-disk}). You may wish to skip installing +all of the prebuilt binaries. + +Then, unpack the source from the compressed \texttt{tar} file in the +directory \dirname{source} to your disk and change directory to where +you placed it. + +Next, run \cmdname{configure} with a command line like this: +\begin{alltt} +> \Ucom{sh configure -prefix=/usr/local/TeX} +\end{alltt} + +The \optname{-prefix} directory is the one where you installed the +support tree; the directory layout will be as follows (where \$TEXDIR +stands for the directory you chose): + +\noindent +\begin{tabular}{>{\ttfamily}ll@{}} + \dirname{$TEXDIR/share/texmf} & main tree with fonts,\\ + & \qquad macros, etc\\ + \dirname{$TEXDIR/man} & Unix manual pages\\ + \dirname{$TEXDIR/info} & \acro{GNU} style Info manuals\\ + \dirname{$TEXDIR/bin/$PLATFORM} & binaries\\ +\end{tabular} +%$ + +If you want to leave out the \dirname{$PLATFORM} directory level, +i.e., put the binaries directly into \dirname{$TEXDIR/bin}, specify +the \verb|--disable-multiplatform| option to \cmdname{configure}. + +Have a look at the output of \verb|./configure --help| for more +options you can use. For example, you can skip building of \OMEGA{} and +\eTeX{}. + + +\subsection{Running \cmdname{make}} + +Make sure the shell variable or option \texttt{noclobber} is not set. +Then, run the main \cmdname{make} like this: +\begin{alltt} +> \Ucom{make world} +\end{alltt} +and relax\ldots + +Alternatively, you want to log all the output, as in: +\begin{alltt} +> \Ucom{sh -c "make world >world.log 2>\&1" \&} +\end{alltt} + +Before you believe that everything went ok, please check the log file +for errors: \acro{GNU} \cmdname{make} always uses the string \samp{***} +whenever a command fails. Also, check if all the programs were built: + +\begin{alltt} +> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} +> \Ucom{ls | wc} +\end{alltt} +The result should be over 200 (you can check the exact number with the +\dirname{bin} directory contents in the distribution). + +If you need special privileges for \texttt{make install}, you can +separate the \samp{make world} into two different runs, like this: +\begin{alltt} +> \Ucom{make all} +> \Ucom{su} +> \Ucom{make install strip} +\end{alltt} + +After you've installed your new binaries, you should follow the normal +post-installation procedures, given in section~\ref{sec:postinstall} +(\p.\pageref{sec:postinstall}). + +Also, if you'd like to make your binaries available to others, please +contact us. We'll be happy to put them on the \TL\ web pages. +\end{comment} + +\section{Acknowledgements} + +\TL{} is a joint effort by virtually all of the \TeX{} user groups. +This edition of \TL{} was overseen by Sebastian Rahtz and Karl Berry. +The other principal contributors are listed below. + +\begin{itemize*} + +\item The German-speaking \TeX{} Users (\acro{DANTE} e.V.), who provide +the hardware for the \TL{} source repository; and Rainer Sch\"opf and +Reinhard Zierke who look after it. \acro{DANTE} officers Volker Schaa +and Klaus H\"oppner coordinate production with the Lehmann's Bookstore +(\url{http://www.lob.de}). + +\item The Perforce corporation (\url{http://www.perforce.com}), for providing +a free copy of their excellent change management system, which we use +to manage the \TL{} sources. + +\item Peter Breitenlohner and the \eTeX\ team for the stable foundation +of future \TeX's. + +\item Thomas Esser, without whose marvelous \teTeX{} package \TL{} +would certainly not exist, and whose continual help makes it a better +product. + +\item Michel Goossens, who co-authored the original documentation. + +\item Eitan Gurari, whose \TeX4ht was used to create the \HTML{} +version of this documentation, and who worked tirelessly to improve +it at short notice. + +\item Hans Hagen, for major testing and making the \ConTeXt\ format +conform to \TL's needs. + +\item Pawe{\l} Jackowski, for the Windows installer \cmdname{tlpm}, +and Tomasz {\L}uczak, for \cmdname{tlpmgui}. + +\item \Thanh, Martin Schr\"oder, and the pdf\TeX\ team for continuing +enhancements of \TeX's abilities. + +\item Petr Olsak, who coordinated and checked all the Czech and Slovak +material very carefully. + +\item Fabrice Popineau, for the Windows binaries in \TL{}. + +\item Staszek Wawrykiewicz, the principal tester for all of \TL{}, +and coordinator of the many major Polish contributions: fonts, Windows +installation, and more. + +\item Olaf Weber, for his patient assembly and maintenance of Web2C, +upon which all else depends. + +\item Gerben Wierda, for creating and maintaining the \MacOSX\ support, +and much integration and testing. + +\item Graham Williams, on whose work the catalogue of packages depends. + +\end{itemize*} + +Builders of the binaries: +Tigran Aivazian (\pkgname{x86\_64-linux}), +Manfred Lotz (\pkgname{i386-freebsd}), +Fabrice Popineau (\pkgname{win32}), +Norbert Preining (\pkgname{alpha-linux}), +Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-linux}, + \pkgname{sparc-solaris}), +Staszek Wawrykiewicz (\pkgname{i386-linux}), +Olaf Weber (\pkgname{mips-irix}), +Gerben Wierda (\pkgname{i386-darwin}, \pkgname{powerpc-darwin}). + +Documentation and translation updates: +Karl Berry (English), +Daniel Flipo \& Fabrice Popineau (French), +G\"unter Partosch \& Hartmut Henkel (German), +Petr Sojka \& Jan Busa (Czech\slash Slovak), +Boris Veytsman (Russian), +Staszek Wawrykiewicz (Polish). + +Of course the most important acknowledgement must go to Donald Knuth, first +for inventing \TeX, and then for giving it to the world. + + +\section{Release history} +\label{sec:history} + +\subsection{Past} + +Discussion began in late 1993 when the Dutch \TeX{} Users Group was +starting work on its 4All\TeX{} \CD{} for \acro{MS-DOS} users, and it +was hoped at that time to issue a single, rational, \CD{} for all +systems. This was too ambitious a target for the time, but it did spawn +not only the very successful 4All\TeX{} \CD{}, but also the \acro{TUG} +Technical Council working group on a \emph{\TeX{} Directory Structure} +(\url{http://tug.org/tds}), which specified how to create consistent and +manageable collections of \TeX{} support files. A complete draft of the +\TDS{} was published in the December 1995 issue of \textsl{TUGboat}, and +it was clear from an early stage that one desirable product would be a +model structure on \CD{}. The distribution you now have is a very direct +result of the working group's deliberations. It was also clear that the +success of the 4All\TeX{} \CD{} showed that Unix users would benefit +from a similarly easy system, and this is the other main strand of +\TL. + +We first undertook to make a new Unix-based \TDS{} \CD{} in the autumn +of 1995, and quickly identified Thomas Esser's \teTeX{} as the ideal +setup, as it already had multi-platform support and was built with +portability across file systems in mind. Thomas agreed to help, and work +began seriously at the start of 1996. The first edition was released in +May 1996. At the start of 1997, Karl Berry completed a major new release +of Web2c, which included nearly all the features which Thomas Esser had +added in \teTeX, and we decided to base the 2nd edition of the \CD{} on +the standard \Webc, with the addition of \teTeX's \texttt{texconfig} +script. The 3rd edition of the \CD{} was based on a major revision of +\Webc, 7.2, by Olaf Weber; at the same time, a new revision of \teTeX +was being made, and \TL{} included almost all of its features. The +4th edition followed the same pattern, using a new version of \teTeX, +and a new release of \Webc{} (7.3). The system now included a complete +Windows setup. + +For the 5th edition (March 2000) many parts of the \CD{} were revised +and checked, updating hundreds of packages. Package details were stored +in XML files. But the major change for \TeX\ Live 5 was that all +non-free software was removed. Everything in \TL{} is now intended +to be compatible with the Debian Free Software Guidelines +(\url{http://www.debian.org/intro/free}); we have done our best to check +the license conditions of all packages, but we would very much +appreciate hearing of any mistakes. + +The 6th edition (July 2001) had much more material updated. The major +change was a new install concept: the user could select a more exact set +of needed collections. Language-related collections were completely +reorganized, so selecting any of them installs not only macros, fonts, +etc., but also prepares an appropriate \texttt{language.dat}. + +The 7th edition of 2002 had the notable addition of \MacOSX{} support, +and the usual myriad of updates to all sorts of packages and +programs. An important goal was integration of the source back with +\teTeX, to correct the drift apart in versions~5 and~6. + +\subsubsection{2003} + +In 2003, with the continuing flood of updates and additions, we found +that \TL{} had grown so large it could no longer be contained on a +single \CD, so we split it into three different distributions (see +section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}). In +addition: + +\begin{itemize*} +\item At the request of the \LaTeX{} team, we changed the standard + \cmdname{latex} and \cmdname{pdflatex} commands to now use \eTeX{} (see + \p.\pageref{text:etex}). +\item The new Latin Modern fonts were included (and are recommended). +\item Support for Alpha \acro{OSF} was removed + (\acro{HPUX} support was removed previously), since no one had (or + volunteered) hardware available on which to compile new binaries. +\item Windows setup was substantially changed; for the first time + an integrated environment based on XEmacs was introduced. +\item Important supplementary programs for Windows + (Perl, Ghost\-script, Image\-Magick, Ispell) are now installed + in the \TL{} installation directory. +\item Font map files used by \cmdname{dvips}, \cmdname{dvipdfm} + and \cmdname{pdftex} are now generated by the new program + \cmdname{updmap} and installed into \dirname{texmf/fonts/map}. +\item \TeX{}, \MF{}, and \MP{} now, by default, output most input + characters (32 and above) as themselves in output (e.g., + \verb|\write|) files, + log files, and the terminal, i.e., \emph{not} translated using the + \verb|^^| notation. In \TL{}~7, this translation was + dependent on the system locale settings; now, locale settings do + not influence the \TeX{} programs' behavior. If for some reason + you need the \verb|^^| output, rename the file + \verb|texmf/web2c/cp8bit.tcx|. (Future releases will have cleaner + ways to control this.) +\item This documentation was substantially revised. +\item Finally, since the edition numbers had grown unwieldy, + the version is now simply identified by the year: \TL{} 2003. +\end{itemize*} + + +\subsubsection{2004} + +2004 saw many changes: + +\begin{itemize} + +\item If you have locally-installed fonts which use their own +\filename{.map} or (much less likely) \filename{.enc} support files, you +may need to move those support files. + +\filename{.map} files are now searched for in subdirectories of +\dirname{fonts/map} only (in each \filename{texmf} tree), along the +\envname{TEXFONTMAPS} path. Similarly, \filename{.enc} files are now +searched for in subdirectories of \dirname{fonts/enc} only, along the +\envname{ENCFONTS} path. \cmdname{updmap} will attempt to warn about +problematic files. + +For methods of handling this and other information, please see +\url{http://tug.org/texlive/mapenc.html}. + +\item The \TK\ has been expanded with the addition of a \MIKTEX-based +installable \CD, for those who prefer that implementation to Web2C. +See section~\ref{sec:struct-tl} (\p.\pageref{sec:struct-tl}). + +\item Within \TL, the single large \dirname{texmf} tree of previous +releases has been replaced by three: \dirname{texmf}, +\dirname{texmf-dist}, and \dirname{texmf-doc}. See +section~\ref{sec:tld} (\p.\pageref{sec:tld}), and the \filename{README} +files for each. + +\item All \TeX-related input files are now collected in +the \dirname{tex} subdirectory of \dirname{texmf*} trees, rather than +having separate sibling directories \dirname{tex}, \dirname{etex}, +\dirname{pdftex}, \dirname{pdfetex}, etc. See +\CDref{texmf-doc/doc/english/tds/tds.html\#Extensions} +{\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}. + +\item Helper scripts (not meant to be invoked by users) are now located +in a new \dirname{scripts} directory of \dirname{texmf*} trees, and +searched for via \verb|kpsewhich -format=texmfscripts|. So if you have +programs which call such scripts, they'll need to be adjusted. See +\CDref{texmf-doc/doc/english/tds/tds.html\#Scripts} +{\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}. + +\item Almost all formats leave most characters printable as +themselves via the ``translation file'' \filename{cp227.tcx}, instead of +translating them with the \verb|^^| notation. Specifically, characters +at positions 32--256, plus tab, vertical tab, and form feed are +considered printable and not translated. The exceptions are plain \TeX\ +(only 32--126 printable), \ConTeXt\ (0--255 printable), and the +\OMEGA-related formats. This default behavior is almost the same as in +\TL\,2003, but it's implemented more cleanly, with more possibilities +for customization. See \CDref{texmf/doc/web2c/web2c.html\#TCX-files} +{\texttt{texmf/doc/web2c/web2c.html\#TCX-files}}. +(By the way, with Unicode input, \TeX\ may output partial character +sequences when showing error contexts, since it is byte-oriented.) + +\item \textsf{pdfetex} is now the default engine for all formats +except (plain) \textsf{tex} itself. (Of course it generates \acro{DVI} +when run as \textsf{latex}, etc.) This means, among other things, that +the microtypographic features of \textsf{pdftex} are available in +\LaTeX, \ConTeXt, etc., as well as the \eTeX\ features +(\OnCD{texmf-dist/doc/etex/base/}). + +It also means it's \emph{more important than ever} to use the +\pkgname{ifpdf} package (works with both plain and \LaTeX) or equivalent +code, because simply testing whether \cs{pdfoutput} or some other +primitive is defined is not a reliable way to determine if \acro{PDF} +output is being generated. We made this backward compatible as best we +could this year, but next year, \cs{pdfoutput} may be defined even when +\acro{DVI} is being written. + +\item pdf\TeX\ (\url{http://pdftex.org}) has many new features: + + \begin{itemize*} + + \item \cs{pdfmapfile} and \cs{pdfmapline} provide font map support + from within a document. + + \item Microtypographic font expansion can be used more easily.\\ + \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} + + \item All parameters previously set through the special configuration + file \filename{pdftex.cfg} must now be set through primitives, + typically in \filename{pdftexconfig.tex}; \filename{pdftex.cfg} is no + longer supported. Any extant \filename{.fmt} files must be redumped + when \filename{pdftexconfig.tex} is changed. + + \item See the pdf\TeX\ manual for more: \OnCD{texmf/doc/pdftex/manual}. + + \end{itemize*} + +\item The \cs{input} primitive in \cmdname{tex} (and \cmdname{mf} and +\cmdname{mpost}) now accepts double quotes containing spaces and other +special characters. Typical examples: +\begin{verbatim} +\input "filename with spaces" % plain +\input{"filename with spaces"} % latex +\end{verbatim} +See the Web2C manual for more: \OnCD{texmf/doc/web2c}. + +\item enc\TeX\ support is now included within Web2C and consequently all +\TeX\ programs, via the \optname{-enc} option\Dash \emph{only when +formats are built}. enc\TeX\ supports general re-encoding of input and +output, enabling full support of Unicode (in \acro{UTF}-8). See +\OnCD{texmf-dist/doc/generic/enctex/} and +\url{http://www.olsak.net/enctex.html}. + +\item Aleph, a new engine combining \eTeX\ and \OMEGA, is available. +A little information is available in \OnCD{texmf-dist/doc/aleph/base} +and \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph}. The +\LaTeX-based format for Aleph is named \textsf{lamed}. + +\item The latest \LaTeX\ release has a new version of the +\acro{LPPL}\Dash now officially a Debian-approved license. Assorted +other updates, see the \filename{ltnews} files in +\OnCD{texmf-dist/doc/latex/base}. + +\item \cmdname{dvipng}, a new program for converting \acro{DVI} to +\acro{PNG} image files, is included. See \OnCD{texmf/doc/man/man1/dvipng.1}. + +\item We reduced the \pkgname{cbgreek} package to a ``medium'' sized set +of fonts, with the assent and advice of the author (Claudio Beccari). +The excised fonts are the invisible, outline, and transparency ones, +which are relatively rarely used, and we needed the space. The full set +is of course available from \acro{CTAN} +(\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). + +\item \cmdname{oxdvi} has been removed; just use \cmdname{xdvi}. + +\item The \cmdname{ini} and \cmdname{vir} commands (links) for +\cmdname{tex}, \cmdname{mf}, and \cmdname{mpost} are no longer created, +such as \cmdname{initex}. The \cmdname{ini} functionality has been +available through the command-line option \optname{-ini} for years now. + +\item \textsf{i386-openbsd} platform support was removed. Since the +\pkgname{tetex} package in the \acro{BSD} Ports system is available, and +\acro{GNU/}Linux and Free\acro{BSD} binaries were available, it seemed +volunteer time could be better spent elsewhere. + +\item On \textsf{sparc-solaris} (at least), you may have to set the +\envname{LD\_LIBRARY\_PATH} environment variable to run the +\pkgname{t1utils} programs. This is because they are compiled with C++, +and there is no standard location for the runtime libraries. (This is +not new in 2004, but wasn't previously documented.) Similarly, on +\textsf{mips-irix}, the \acro{MIPS}pro 7.4 runtimes are required. + +\end{itemize} + +\subsection{Present} +\label{tlcurrent} + +2005 saw the usual huge number of updates to packages and programs. +The infrastructure stayed relatively stable from 2004, but inevitably +there were some changes there as well: + +\begin{itemize} + +\item New scripts \cmdname{texconfig-sys}, \cmdname{updmap-sys}, and + \cmdname{fmtutil-sys} were introduced, which modify the + configuration in the system trees. The \cmdname{texconfig}, + \cmdname{updmap}, and \cmdname{fmtutil} scripts now modify + user-specific files, under \dirname{$HOME/.texlive2005}. + See section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig}. + +\item Corresponding new variables \envname{TEXMFCONFIG} and + \envname{TEXMFSYSCONFIG} to specify the trees where configuration + files (user or system, respectively) are found. Thus, you may + need to move personal versions of \filename{fmtutil.cnf} and + \filename{updmap.cfg} to these places; another option is to + redefine \envname{TEXMFCONFIG} or \envname{TEXMFSYSCONFIG} in + \filename{texmf.cnf}. In any case the real location of these files + and the values of \envname{TEXMFCONFIG} and \envname{TEXMFSYSCONFIG} + must agree. + See section~\ref{sec:texmftrees}, \p.\pageref{sec:texmftrees}. + +\item Last year, we kept \verb|\pdfoutput| and other primitives undefined + for DVI output, even though the \cmdname{pdfetex} program was + being used. This year, as promised, we undid that compatibility + measure. So if your document uses \verb|\ifx\pdfoutput\undefined| + to test if PDF is being output, it will need to be changed. You + can use the package \pkgname{ifpdf.sty} (which works under both + plain \TeX\ and \LaTeX) to do this, or steal its logic. + +\item Last year, we changed most formats to output (8-bit) characters as + themselves (see previous section). The new TCX file + \filename{empty.tcx} now provides an easier way to get the + original \verb|^^| notation if you so desire, as in: +\begin{verbatim} +latex --translate-file=empty.tcx yourfile.tex +\end{verbatim} + +\item The new program \cmdname{dvipdfmx} is included for translation of + DVI to PDF; this is an actively maintained update of + \cmdname{dvipdfm} (which is also still available for now, though + no longer recommended). + +\item The new programs \cmdname{pdfopen} and \cmdname{pdfclose} are included + to allow reloading of pdf files in the Adobe Acrobat Reader without + restarting the program. (Other pdf readers, notably \cmdname{xpdf}, + \cmdname{gv}, and \cmdname{gsview}, have never suffered from this + problem.) + +\item For consistency, the variables \envname{HOMETEXMF} and + \envname{VARTEXMF} have been renamed to \envname{TEXMFHOME} and + \envname{TEXMFSYSVAR}, respectively. There is also + \envname{TEXMFVAR}, which is by default user-specific. See the + first point above. + +\end{itemize} + +\subsection{Future} + +\emph{\TL{} is not perfect!} (And never will be.) We intend to +continue to release new versions yearly, and would like to provide more +help material, more utilities, more installation programs, and (of +course) an ever-improved and checked tree of macros and fonts. This work +is all done by hard-pressed volunteers in their limited spare time, and +a great deal remains to be done. If you can help, don't hesitate to put +your name forward! + +Please send corrections, suggestions, and offers of help to:\hfill\null +\begin{quote} +Sebastian Rahtz \ / \ 7 Stratfield Road \ / \ Oxford OX2 7BG \ / \ UK \\ +\email{tex-live@tug.org} \\ +\url{http://tug.org/texlive} +\end{quote} + +\medskip +\noindent \textsl{Happy \TeX ing!} + +\end{document} diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/live-2007.tex b/Master/texmf/doc/texlive/source/texlive-en/archive/live-2007.tex new file mode 100644 index 00000000000..8232db8becf --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/live-2007.tex @@ -0,0 +1,3264 @@ +% $Id: live.tex 3938 2007-02-06 01:49:45Z karl $ +% TeX Live documentation. Originally written by Sebastian Rahtz and +% Michel Goossens, now maintained by Karl Berry and others. +% Public domain. +% +\documentclass{article} +\let\tldocenglish=1 % for live4ht.cfg +\usepackage{tex-live} +\begin{document} + +\title{% + {\huge \textit{The \protect\TL{} Guide}\\\strut} + {\LARGE \textsf{\TL{} 2007}} +} + +\author{Karl Berry, editor \\[3mm] + \url{http://tug.org/texlive/} + } + +\date{January 2007} + +\maketitle + +\begin{multicols}{2} +\tableofcontents +\listoftables +\end{multicols} + +\section{Introduction} +\label{sec:intro} + +This document describes the main features of the \TL{} software +distribution\Dash \TeX{} and friends for \acro{GNU}/Linux and other Unix +flavors, \MacOSX, and (32-bit) Windows systems. (Warning: it is not +especially useful for older Mac or \acro{MS-DOS} systems.) + +\TL{} includes executables for \TeX{}, \LaTeXe{}, \ConTeXt, \MF, \MP, +\BibTeX{} and many other programs; an extensive collection of macros, +fonts and documentation; and support for typesetting in many different +scripts from around the world. It is part of the even larger \TK{} +(briefly described below in section~\ref{sec:struct-tl}, +\p.\pageref{sec:struct-tl}). Both are cooperative efforts by the \TeX\ +user groups. + +For newer versions of the packages included here, please check +\acro{CTAN}: \url{http://www.ctan.org}. + +For a brief summary of the major changes in this edition of \TL{}, +see the end of the document, section~\ref{sec:history} +(\p.\pageref{sec:history}). + + +\subsection{Basic usage of \protect\TL{}} +\label{sec:basic} + +You can use \TL{} in three principal ways: + +\begin{enumerate} + +\item You can run \TL{} directly from the \pkgname{live} \DVD +(see section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}). +This takes almost no disk space, and gives you immediate access to +everything in \TL{}. Of course performance will be worse than running +on local disk, but you may well find it useful. + +\item You can install all or part of \TL{} to a local disk, from either +the \DVD\ or the \pkgname{inst} \acro{CD}. This is the most common use +of \TL. You will need (approximately) 100 megabytes for the most +minimal system, and upwards of 1.3 gigabytes for a full system. + +\item You can integrate a particular package or collection into your +existing \TeX{} system, either a \TL{} system you installed +earlier, or a different system. + +\end{enumerate} + +\noindent All of these are described in detail in the \acro{OS}-specific +installation sections following, but here is a quick start: + +\begin{itemize*} + +\item The main installation script for Unix and \MacOSX{} is +\texttt{install-tl.sh}. +GNU/Linux users can also try a new GUI installation program: +run \texttt{setuptl/tlpmgui}. More information +can be found in section \ref{sec:win-install} on +p.~\pageref{sec:win-install}. + +\item The single package installation script is \texttt{install-pkg.sh}. +(After installation on Linux with \texttt{tlpmgui}, you can also try +running \texttt{tlpmgui} again to add or remove individual packages or +collections.) + +\item The installation program for Windows is \texttt{tlpmgui.exe}. +It can be used also for adding or removing the packages. +See section~\ref{sec:win-install} below for more information. + +\end{itemize*} + + +\subsection{Getting help} +\label{sec:help} + +The \TeX{} community is both active and friendly, and virtually all +serious questions end up getting answered. However, the support is +informal, done by volunteers and casual readers, so it's especially +important that you do your homework before asking. (If you prefer +guaranteed commercial support, you can forego \TL{} completely and +purchase a vendor's system; \url{http://tug.org/interest.html#vendors} +has a list.) + +Here is a list of resources, approximately in the order we recommend +using them: + +\begin{description} +\item [Getting Started] If you are new to \TeX, the web page +\url{http://tug.org/begin.html} gives a brief introduction to the system. + +\item [\TeX{} \acro{FAQ}] The \TeX{} \acro{FAQ} is a huge compendium of +answers to all sorts of questions, from the most basic to the most +arcane. It is included on \TL{} in \OnCD{texmf-doc/doc/english/FAQ-en}, and is +available on the Internet through \url{http://www.tex.ac.uk/faq}. +Please check here first. + +\item [\TeX{} Catalogue] If you are looking for a specific package, +font, program, etc., the \TeX{} Catalogue is the place to look. It is a +huge collection of all \TeX{}-related items. See +\OnCD{texmf-doc/doc/english/catalogue}, or +\url{http://www.ctan.org/tex-archive/help/Catalogue}. + +\item [\TeX{} Web Resources] The web page +\url{http://tug.org/interest.html} has many \TeX{}-related links, in +particular for numerous books, manuals, and articles on all aspects of +the system. + +\item [support archives] The two principal support forums are the +Usenet newsgroup \url{news:comp.text.tex} and the mailing list +\email{texhax@tug.org}. Their archives have years of past +questions and answers for your searching pleasure, via +\url{http://groups.google.com/groups?group=comp.text.tex} and +\url{http://tug.org/mail-archives/texhax}, respectively. And a general web +search, for example on \url{http://google.com}, never hurts. + +\item [asking questions] If you cannot find an answer, you can post to +\dirname{comp.text.tex} through Google or your newsreader, or to +\email{texhax@tug.org} through email. But before you post, +\emph{please} read this \acro{FAQ} entry on asking questions in such a +way that you're most likely to get an answer: +\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. + +\item [\TL{} support] If you want to report a bug or have +suggestions or comments on the \TL{} distribution, installation, or +documentation, the mailing list is \email{tex-live@tug.org}. However, +if your question is about how to use a particular program included in +\TL{}, you are better off writing to that program's maintainer or +mailing list. + +\end{description} + +The other side of the coin is helping others who have questions. Both +\dirname{comp.text.tex} and \code{texhax} are open to anyone, so feel +free to join, start reading, and help out where you can. Welcome to +\TeX{}! + + +% don't use \TL so the \uppercase in the headline works. Also so +% tex4ht ends up with the right TeX. Likewise the \protect's. +\section{Structure of \protect\TeX\protect\ Live} +\label{sec:struct-tl} + +This section describes the structure and contents of \TL{} and the +\TK{} of which it is a part. + +\subsection{Multiple distributions: \protect\pkgname{live}, + \protect\pkgname{inst}, + \protect\pkgname{protext}} +\label{sec:multiple-dist} + +Space limitations of \acro{CD-ROM} format have forced us to divide +\TK{} into several distributions, as follows. + +\begin{description} + +\item [live] A complete system on \acro{DVD}; it is too large +for \acro{CD}. It can be run live or installed to disk. It also +includes a snapshot of the \CTAN{} repository, the \pkgname{protext} +distribution for Windows and the Mac\TeX\ distribution for \MacOSX, entirely +independent of \TL{}, as well as assorted other packages in a +\texttt{texmf-extra} directory. + +\CTAN{}, \pkgname{protext}, Mac\TeX, and \texttt{texmf-extra} do not follow +the same copying conditions as \TL{}, so be careful when redistributing or +modifying. + +\item [inst(allable)] A complete system on \CD; in order to make this fit, +the packages and programs are compressed. Therefore, it is not possible +to run \TeX\ directly from the installable \CD, you have to install it +to disk (hence its name). Installation is described in subsequent sections. + +\item [protext] An enhancement of the \MIKTEX\ distribution for Windows, +\ProTeXt\ adds a few extra tools to \MIKTEX, and simplifies +installation. It is entirely independent of \TL{}, and has its own +installation instructions. It can be run live, or installed to disk. +The \ProTeXt\ home page is \url{http://tug.org/protext}. + +\ProTeXt\ is provided as both the top level of the \pkgname{live} \DVD\ +and on its own \CD\ (for those who cannot use the \DVD). + +\end{description} + +\noindent You can tell which type of distribution you're in by looking +for a \texttt{00\var{type}.TL} file at the top of the \TL{} directory. +This file also contains the \TL{} release date. + +Naturally, each user group chooses what to distribute to its own members. + + +\subsection{Top level directories} +\label{sec:tld} + +Here is a brief listing and description of the top level directories in +the \TL{} distribution. On the \pkgname{live} \DVD, the entire \TL{} +hierarchy is in a subdirectory \dirname{texliveYYYY}, not at the top +level of the disc. + +\smallskip +\begingroup + \renewcommand{\arraystretch}{1.3} % open up interrow spacing +\begin{tabular}{>{\ttfamily}lp{.78\hsize}} +bin & The \TeX{} system programs, arranged by platform. \\ +source & The source of all programs, including the main \Webc{} + \TeX{} and \MF{} distributions. These are stored in a + \cmdname{bzip2}-compressed tar archive. \\ +setuptl & Installation programs for Linux and Windows. \\ +support & Assorted auxiliary packages and programs. These are + \emph{not} installed automatically. This includes + assorted editors and \TeX\ shells. \\ +texmf & Tree for the programs, along with their support files and + documentation. Does not include \TeX\ formats and packages. + (\texttt{TEXMFMAIN} in the next section.) \\ +texmf-dist & The main tree of formats and packages. + (\texttt{TEXMFDIST} in the next section.) \\ +texmf-doc & Tree for self-contained pure documentation, arranged by + language. \\ +texmf-var & Tree for files automatically generated and stored. + (\texttt{TEXMFSYSVAR} in the next section.) \\ +\end{tabular} +\endgroup + +\smallskip + +In addition to the directories above, the installation scripts and +\filename{README} files (in various languages) are at the top level of +the distribution. + +The \dirname{texmf-doc} directory contains only documentation, but +it does not contain all the documentation. The documentation for the +programs (manuals, man pages, Info files) is in \dirname{texmf/doc}, +since the programs are in \dirname{texmf}. Similarly, the documentation +for \TeX\ packages and formats is in \dirname{texmf-dist/doc}. You can +use the \cmdname{texdoc} or \cmdname{texdoctk} programs to find any +documentation wherever it's located. The comprehensive links in the +top-level file \OnCD{doc.html} may also be helpful. + + +\subsection{Overview of the predefined texmf trees} +\label{sec:texmftrees} + +This section lists all predefined variables specifying texmf trees used +by the system, and their intended purpose. The command \texttt{texconfig +conf} shows you the values of these variables, so that you can easily +find out how they map to directory names in your installation. + +\begin{ttdescription} +\item [TEXMFMAIN] The tree which holds vital parts of the system + such as helper scripts (e.g., \verb+web2c/mktexdir+), pool files and + other support files. +\item [TEXMFDIST] The tree which holds the main set of macro packages, + fonts, etc., as originally distributed. +\item [TEXMFLOCAL] The tree which administrators can use for system-wide + installation of additional or updated macros, fonts, etc. +\item [TEXMFHOME] The tree which users can use for their own individual + installations of additional or updated macros, fonts, etc. + The expansion of this variable depends on \verb+$HOME+ by default, % $ + which dynamically adjusts for each user to an individual + directory. +\item [TEXMFCONFIG] The tree used by te\TeX's utilities + \verb+texconfig+, \verb+updmap+, and \verb+fmtutil+ to store modified + configuration data. Under \verb+$HOME+ by default. %$ +\item [TEXMFSYSCONFIG] The tree used by te\TeX's utilities + \verb+texconfig-sys+, \verb+updmap-sys+, and \verb+fmtutil-sys+ to + store modified configuration data. +\item [TEXMFVAR] The tree used by \verb+texconfig+, \verb+updmap+ and + \verb+fmtutil+ to store (cached) runtime data such as format files and + generated map files. Under \verb+$HOME+ by default. %$ +\item [TEXMFSYSVAR] The tree used by \verb+texconfig-sys+, + \verb+updmap-sys+ and \verb+fmtutil-sys+ to store (cached) runtime + data such as format files and generated map files. +\end{ttdescription} + +For more discussion of \texttt{texconfig} and related utilities, please +see section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig}. + + +\subsection{Extensions to \protect\TeX} +\label{sec:tex-extensions} + +\TL{} contains several extended versions of \TeX: + +\begin{description} + +\item [\eTeX] adds a small but powerful set of new primitives +\label{text:etex} (related to macro expansion, character scanning, +classes of marks, additional debugging features, and more) and the +\TeXXeT{} extensions for bidirectional typesetting. In default mode, +\eTeX{} is 100\% compatible with ordinary \TeX. See +\OnCD{texmf-dist/doc/etex/base/etex_man.pdf}. + +\item [pdf\TeX] builds on the \eTeX\ extensions, adding support for +writing \acro{PDF} output as well as \dvi{}. See +\OnCD{texmf/doc/pdftex/manual/} for the manual, and +\OnCD{texmf/doc/pdftex/manual/samplepdf/samplepdf.tex}. This is the +default program for all formats except plain \TeX. + +\item [Xe\TeX] adds support for Unicode input and OpenType fonts, using +third-party libraries. See \url{http://scripts.sil.org/xetex}. + +\item [\OMEGA\ (Omega)] is based on Unicode (16-bit characters), thus +supports working with almost all the world's scripts simultaneously. It +also supports so-called `\OMEGA{} Translation Processes' (\acro{OTP}s), +for performing complex transformations on arbitrary input. See +\OnCD{texmf-dist/doc/omega/base/doc-1.8.tex} (not completely up-to-date). + +\item [Aleph] combines the \OMEGA\ and \eTeX\ extensions. +See \OnCD{texmf-dist/doc/aleph/base} for some minimal documentation. + +\end{description} + + +\subsection{Other notable programs in \protect\TL} + +Here are a few other commonly-used programs included in \TL{}: + +\begin{cmddescription} + +\item [bibtex] bibliography support. + +\item [makeindex] index support. + +\item [dvips] convert \dvi{} to \PS{}. + +\item [xdvi] \dvi{} previewer for the X Window System. + +\item [dvilj] \dvi{} drive for the HP LaserJet family. + +\item [dv2dt, dt2dv] convert \dvi{} to/from plain text. + +\item [dviconcat, dviselect] cut and paste pages +from \dvi{} files. + +\item [dvipdfmx] convert \dvi{} to \acro{PDF}, an alternative approach +to pdf\TeX\ (mentioned above). See the \pkgname{ps4pdf} and +\pkgname{pdftricks} packages for still more alternatives. + +\item [psselect, psnup, \ldots] \PS{} +utilities. + +\item [lacheck] \LaTeX{} syntax checker. + +\item [texexec] Con\TeX{}t and \acro{PDF} processor. + +\item [tex4ht] \TeX{} to \acro{HTML} converter. + +\end{cmddescription} + + +\section{Unix installation} +\label{sec:unix-install} + +As introduced in section~\ref{sec:basic} (\p.\pageref{sec:basic}), +\TL{} has three principal uses: + +\begin{enumerate} +\item Run directly from media. +\item Install to disk. +\item Integrate a particular package or collection into your existing +\TeX{} installation. +\end{enumerate} + +\noindent The following sections describes the Unix-specific procedures +for each of these. + +\ifSingleColumn \begin{figure}[ht]\noindent \fi +\begin{warningbox} +\textbf{Warning: } The \TK{} \CD{}s and \DVD{} are in ISO 9660 (High Sierra) +format, \emph{with} Rock Ridge (and Joliet, for Windows) +extensions. Therefore, in order to take full advantage of the \TK{} +under Unix, your system needs to be able to use the Rock Ridge +extensions. Please consult the documentation for your \cmdname{mount} +command to see how to do this. If you have several different machines +on a local network, you may be able to mount the discs on one which +does support Rock Ridge, and use this with the others. + +\leavevmode\quad Modern systems should be able to use the discs without +problems. If troubles, let us know. The discussion below assumes you +have been able to mount the \CD{}s with full Rock Ridge compatibility. +\end{warningbox} +\ifSingleColumn\end{figure}\fi + + +% +\subsection{Running \protect\TL{} directly from media (Unix)} + +\def\runlive{% text repeated in windows section +It is possible to use the \TeX{} system directly from the \pkgname{live} +\DVD{}, without installing the distribution to disk. (Thus the name +\TeX\ `Live', in fact.) It is \emph{not} possible to run \TeX{} +directly from the other \CD{}s (see section~\ref{sec:multiple-dist}, +\p.\pageref{sec:multiple-dist}). +} + +\def\startinst{% repeated in other subsections +To start, you mount the \CD{} or \DVD{}, with Rock Ridge extensions +enabled. The exact command to do this varies from system to system; the +following works under Linux, except the name of the device +(\filename{/dev/cdrom}, here) may vary. (All our examples will use +\texttt{>} as the shell prompt; user input is +\Ucom{\texttt{underlined}}.) +\begin{alltt} +> \Ucom{mount -t iso9660 /dev/cdrom /mnt/cdrom} +\end{alltt} + +\noindent Change the current directory to the mount point: +\begin{alltt} +> \Ucom{cd /mnt/cdrom} +\end{alltt} + +\noindent Under \MacOSX, the directory is typically under +\dirname{/Volumes}, and the media will be mounted automatically. +} + +\def\installtlsh{ +Run the installation script \filename{install-tl.sh}: +\begin{alltt} +> \Ucom{sh install-tl.sh}\\ +Welcome to TeX Live... +\end{alltt} + +\noindent After various greeting messages and a list of the main menu +options, the installation will ask you to enter a command. Do this by +typing the desired character and hitting return; don't type the angle +brackets shown. Either uppercase or lowercase is ok; we'll use +lowercase in our examples. +} + +\runlive +\startinst +\installtlsh + +For running live, our first command will be \Ucom{d} and then the +subcommand \Ucom{1} to set directories. Even in this case, we must +choose a directory on the local disk to place files that the \TeX{} +system itself generates, such as fonts and formats, and also to provide +a place for updated configuration files, if need be. + +We'll use \dirname{/opt/texlive2007} in this example. It's good to +include the year in the name, as these generated files are not +in general compatible from release to release. (If the default value of +\dirname{/usr/local/texlive/2007} works for you, then you can skip this +step.) + +\begin{alltt} +Enter command: \Ucom{d} +Current directories setup: +<1> TEXDIR: /usr/local/texlive/2007 +... +Enter command: \Ucom{1} +New value for TEXDIR [/usr/local/texlive/TeX]: \Ucom{/opt/texlive2007} +... +Enter command: \Ucom{r} +\end{alltt} + +\noindent Back at the main menu, our second and last command is +\Ucom{r}, to set up for running live off the media without installing +to disk: +\begin{alltt} +Enter command: \Ucom{r} +Preparing destination directories... +... +Welcome to TeX Live! +> +\end{alltt} + +\noindent And we are back at the system prompt, as shown. + +Next, it is necessary to alter two environment variables: +\envname{PATH}, to an architecture-dependent value (so that we can run +the programs), and \envname{TEXMFSYSVAR}, to the value specified above. +See table~\ref{tab:archlist} for a list of the architecture names for +the different systems. + + +\def\textruntexconfig{% +After the main installation has completed, and environment variables +have been set, the last step is to run \cmdname{texconfig} or +\cmdname{texconfig-sys} to customize your installation to your needs. +This is explained in section~\ref{sec:texconfig}, +\p.\pageref{sec:texconfig}. +} +\textruntexconfig + +\begin{table*}[ht] +\caption[Supported system architectures.]{Supported system +architectures.} +\label{tab:archlist} +\begin{tabular}{>{\ttfamily}ll} +alpha-linux & HP Alpha GNU/Linux \\ +hppa-hpux & HPPA HP-UX \\ +i386-darwin & x86 \MacOSX \\ +i386-freebsd & x86 FreeBSD \\ +i386-linux & x86 GNU/Linux \\ +i386-openbsd & x86 OpenBSD \\ +i386-solaris & x86 Solaris \\ +mips-irix & SGI IRIX \\ +powerpc-aix & IBM RS/6000 AIX \\ +powerpc-darwin & PowerPC \MacOSX \\ +powerpc-linux & PowerPC GNU/Linux \\ +sparc-linux & Sun Sparc GNU/Linux \\ +sparc-solaris & Sun Sparc Solaris \\ +win32 & Windows (32-bit) \\ +x86\_64-linux & x86 64-bit GNU/Linux \\ +\hline +\end{tabular} +\end{table*} + +\label{text:path} +The syntax for setting the environment variables, and the initialization +file to put them in, depends on the shell you use. If you use a +Bourne-compatible shell (\cmdname{sh}, \cmdname{bash}, \cmdname{ksh}, et +al.), put the following into your \filename{$HOME/.profile} file: +\begin{alltt} +PATH=/mnt/cdrom/bin/\var{archname}:$PATH; export PATH +TEXMFSYSVAR=/opt/texlive2007/texmf-var; export TEXMFSYSVAR +\end{alltt} + +\noindent For C shell-compatible shells (\cmdname{csh}, \cmdname{tcsh}), +put the following into your \filename{$HOME/.cshrc} file: +\begin{alltt} +setenv PATH /mnt/cdrom/bin/\var{archname}:$PATH +setenv TEXMFSYSVAR /opt/texlive2007/texmf-var +\end{alltt} + +\noindent Then log out, log back in, and test your installation +(see section~\ref{sec:test-install}, \p.\pageref{sec:test-install}). + +\def\textifindoubt{% +If in doubt, please ask any local system gurus to help you with +problems; for example, the way to mount the \TL{} media, which +directory or directories to use, and precise details of the changes to +your personal initialization files can and do vary from site to site. +} +\textifindoubt + + +% +\subsection{Installing \protect\TeX\protect\ Live to disk} +\label{sec:unix-install-disk} + +It is possible, indeed typical, to install the \TL{} distribution to +hard disk. This can be done from either the \pkgname{live} or +\pkgname{inst} distributions. (See section~\ref{sec:multiple-dist}, +\p.\pageref{sec:multiple-dist}, for an explanation of the different +distributions.) + +\startinst +\installtlsh + +Table~\ref{tab:main-menu-options} briefly lists the options in the main +menu. The order in which you select the options makes little +difference, except that \Ucom{i} must be last. It's reasonable to go +through them in the order presented here. + +% apparently here.sty [H] doesn't support table*. +\begin{table}[H] +\caption{Main menu options for the installation.} +\label{tab:main-menu-options} +\begin{tabular}{>{\ttfamily}ll} +p & The platform you are running on.\\ +b & The architectures for which to install binaries.\\ +s & The base installation scheme to use (minimal, recommended, + full, etc.)\\ +c & Override the base scheme for individual collections.\\ +l & Override for language collections.\\ +d & Directories in which to install.\\ +o & Other options.\\ +i & Perform the installation.\\ +\end{tabular} +\end{table} + +Here are further details on each option. + +\textbf{\optname{p} -- Current platform.} Since the installation script +automatically guesses which platform you're running on, it is usually +unnecessary to use this option. It's there in case you need to override +the automatic detection. + +\textbf{\optname{b} -- Binary architectures.} By default, only the +binaries for your current platform will be installed. From this menu, +you can select installation of binaries for other architectures as well +(or omit installing the current platform). This can be useful if you are +sharing a \TeX\ tree across a network of heterogenous machines. For a +list of the supported architectures, see table~\ref{tab:archlist}, +\p.\pageref{tab:archlist}. + +\textbf{\optname{s} -- Base installation scheme.} From this menu, you +can choose an overall set of package collections, called a ``scheme''. +The default \optname{full} scheme installs everything available, but you +can also choose the \optname{basic} scheme for a minimal system, or +\optname{medium} to get something in between. There are also specific +sets for Omega and \acro{XML}. + +\textbf{\optname{c} -- Individual collections.} From this menu, you can +override the scheme's set of collections to install. Collections are +one level more detailed than schemes\Dash collections consist of one or +more packages, where packages (the lowest level grouping in \TL) contain +the actual \TeX\ macro files, font families, and so on. In this menu, +selection letters are case-sensitive. + +\textbf{\optname{l} -- Language collections}. This menu has the same +basic purpose as \Ucom{c}, to override the collection set in the chosen +scheme. In this case, the collections are specifically for different +languages. Selection letters are case-sensitive here too. Here is a +list of the language collections in \TL: + +% xx really should generate list from texmf/tpm/collection/tex-lang* +% a la install-tl.sh. +\begin{tabbing} +\hspace{.25\linewidth} \= +\hspace{.25\linewidth} \= +\hspace{.25\linewidth} \= +\hspace{.25\linewidth} \kill +(some) African scripts \> +Arabic \> +Armenian \> +Chinese\,Japanese\,Korean \\ +Croatian \> +Cyrillic \> +Czech/Slovak \> +Danish \\ +Dutch \> +Finnish \> +French \> +German \\ +Greek \> +Hebrew \> +Hungarian \> +Indic \\ +Italian \> +Latin \> +Manju \> +Mongolian \\ +Norwegian \> +Polish \> +Portuguese \> +Spanish \\ +Swedish \> +Tibetan \> +\acro{UK} English \> +Vietnamese \\ +\end{tabbing} + +\noindent Language collections typically include fonts, macros, +hyphenation patterns, and other support files. (For instance, +\pkgname{frenchle.sty} is installed if you select the \optname{French} +collection.) In addition, installing a language collection will alter +the \filename{language.dat} configuration file controlling which +hyphenation patterns are loaded. + +\textbf{\optname{d} -- Installation directories}. Three directories can +be changed here: +\label{text:instdir} + +\begin{ttdescription} +\item [TEXDIR] The top-level directory under which +everything else will be installed. The default value is +\dirname{/usr/local/texlive/2007}, and is often changed. We recommend +including the year in the name, to keep different releases of \TL{} +separate. (You may wish to make a version-independent name such +\dirname{/usr/local/texlive} via a symbolic link, which you can then +update after testing the new release.) + +Under \MacOSX, the usual frontends look for \TeX{} in +\dirname{/usr/local/teTeX}, so you may wish to install \TL{} there. + +\item [TEXMFLOCAL] This tree is where the \TeX{} system (not as part of +the initial installation, but rather as time goes by) puts +non-version-specific files, primarily fonts. The default value is +\dirname{/usr/local/texlive/texmf-local}, independent of the current +\TL{} release, because it's also the recommended location to put any +local packages or configuration settings. + +\item [TEXMFSYSVAR] This tree is where \cmdname{texconfig-sys} puts +files that \emph{are} version-specific. The default value is +\dirname{TEXDIR/texmf-var}, and there's generally no reason to change +it. There is also \envname{TEXMFSYSCONFIG}, which is where +\cmdname{texconfig} looks for modified configuration data. See +section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig} for more +information. + +\end{ttdescription} + +\textbf{\optname{o} -- Other options.} From this menu, you can select +the following general options: + +\begin{ttdescription} +\item [a] Specify an alternate directory for generated fonts. +The default is to use the \envname{TEXMFVAR} tree, as explained above. +Setting this is useful if you plan to mount the main tree read-only, and +therefore you need another location (perhaps host-specific) for +dynamically created fonts. + +\item [l] Create symbolic links for the binaries, man pages, +and\slash or \acro{GNU} Info files in other locations. For example, you may +wish to make the man pages available under \dirname{/usr/local/man} and +the Info files available under \dirname{/usr/local/info}. (Of course +you need appropriate privileges to write in the specified directories.) + +It is not advisable to overwrite a \TeX\ system that came with your +system with this option. It's intended primarily for creating the links +in standard directories that are known to users, such as +\dirname{/usr/local/bin}, which don't already contain any \TeX\ files. + +\item [d] Skip installation of the font/macro documentation tree. +This is useful if you need to save space, or if you've previously +installed the documentation elsewhere. + +\item [s] Skip installation of the main font/macro source +tree. This is useful if you are arranging to share that tree between +machines and\slash or architectures in some other way, such as \acro{NFS}. + +\end{ttdescription} + +\textbf{i -- Perform installation.} When you're satisfied with your +configuration options, enter \Ucom{i} to actually do the installation +from the media to your chosen locations. + +% text is similar to above, but no TEXMFSYSVAR, so we have to write out. +After the installation completes, your next step is to include the +architecture-specific subdirectory of \dirname{TEXDIR/bin} in your +\envname{PATH}, so the newly-installed programs can be found. The +architecture names are listed in table~\ref{tab:archlist}, +\p.\pageref{tab:archlist}, or you can simply list the directory +\dirname{TEXDIR/bin}. + +The syntax for doing this, and the initialization file to use, depends +on your shell. If you use a Bourne-compatible shell (\cmdname{sh}, +\cmdname{bash}, \cmdname{ksh}, et al.), put the following into your +\filename{$HOME/.profile} file: + +\begin{alltt} +PATH=/usr/local/texlive/2007/bin/\var{archname}:$PATH; export PATH +\end{alltt} + +\noindent For C shell-compatible shells (\cmdname{csh}, \cmdname{tcsh}), +put the following into your \filename{$HOME/.cshrc} file: +\begin{alltt} +setenv PATH /usr/local/texlive/2007/bin/\var{archname}:$PATH +\end{alltt} + +\textruntexconfig + +Here is a minimal annotated example which accepts the default +directories and installs binaries for the current system only. Thus, +only one command is needed, \Ucom{i} for install. The \texttt{>} is the +shell prompt as usual. + +\begin{alltt} +> \Ucom{sh install-tl.sh} +\Ucom{i} # perform installation +> \Ucom{texconfig} ... # see section \ref{sec:texconfig} +# New PATH element, with Linux as the example: +> \Ucom{PATH=/usr/local/texlive/2007/bin/i386-linux:$PATH; export PATH} +\end{alltt} + +If your Unix system supports the \cmdname{manpath} command (type \code{man +manpath} to learn more), you can make the \TL\ manual pages available +system-wide via the normal \cmdname{man} command by editing the file +\filename{/etc/manpath.config}; you might need root permissions for this. +With the following entry in \filename{/etc/manpath.config} the \TL\ +manual pages will be found at their original places within the \TL\ tree +(adapt the binary path for your system architecture): + +\begin{verbatim} +MANPATH_MAP /usr/local/texlive/2007/bin/i386-linux \ + /usr/local/texlive/2007/texmf/doc/man +\end{verbatim} + +\textifindoubt + + +\subsubsection{Non-interactive installation} +\label{sec:noninteractive-install} + +It is possible to override the default directories with environment +variables, and then install non-interactively. Example: +\begin{alltt} +> \Ucom{TEXLIVE_INSTALL_PREFIX=/opt/texlive} +> \Ucom{export TEXLIVE_INSTALL_PREFIX} +> \Ucom{echo i | sh install-tl.sh} +\end{alltt} + +The \envname{TEXLIVE\_INSTALL\_PREFIX} variable overrides the default +location of \dirname{/usr/local/texlive}, leaving all else +unchanged---so with the above invocation, the main installation will go +to \dirname{/opt/texlive/2007}. + +In the usual Unix way, the final \Ucom{echo i} can be replaced by any +sequence of input commands via a here document, so any sequence of +commands can be scripted. + +Here are all the possible overrides: + +\begin{ttdescription} +\item [TEXLIVE\_INSTALL\_PREFIX] + Override \dirname{/usr/local/texlive}. +\item [TEXLIVE\_INSTALL\_TEXDIR] + Override \dirname{\$TEXLIVE_INSTALL_PREFIX}/2007. +\item [TEXLIVE\_INSTALL\_TEXMFLOCAL] + Override \dirname{\$TEXLIVE_INSTALL_PREFIX/texmf-var}. +\item [TEXLIVE\_INSTALL\_TEXMFSYSVAR] + Override \dirname{\$TEXLIVE_INSTALL_TEXDIR/texmf-var}. +\item [TEXLIVE\_INSTALL\_TEXMFHOME] + Override \dirname{\$HOME/texmf}. +\end{ttdescription} + +It would be better to support a standard \acro{GNU}-style +\filename{configure} with options, instead of these environment +variables. Volunteers are welcome! + + +% +\subsection{Installing individual packages to disk} + +You can add individual packages or collections from the current +distribution to an existing non-\TL{} setup, or an earlier +\TL{} installation. + +\startinst + +Run the installation script \filename{install-pkg.sh} (not +\filename{install-tl.sh}, which is intended for complete installations +only): +\begin{alltt} +> \Ucom{sh install-pkg.sh \var{options}} +\end{alltt} + +The first set of options controls what gets read: + +\begin{ttdescription} +\item [-{}-package=\var{pkgname}] The individual package to work on. + +\item [-{}-collection=\var{colname}] The individual collection to work on. + +\item [-{}-nodoc] Exclude documentation files from the operation. + +\item [-{}-nosrc] Exclude source files from the operation. + +\item [-{}-cddir=\var{dir}] Source directory to read from; defaults +to the current directory. If you followed the instructions above, that +will be the distribution directory, and won't need to be changed. + +\item [-{}-listdir=\var{dir}] The so-called `lists' directory within +\var{cddir} from which to read the package information. The only +reason to change the default is if you're making changes to \TL{} +yourself. + +\end{ttdescription} + +What actually happens is controlled by the following options. If +neither of these are specified, the default action is to install the +selected files. The main destination tree is found by expanding +\envname{\$TEXMFMAIN} with \cmdname{kpsewhich}. You can override it by +setting either the environment variable \envname{TEXMFMAIN} or +\envname{TEXMF}. + +\begin{ttdescription} +\item [-{}-listonly] List the files that would be installed, but don't +actually install anything. + +\item [-{}-archive=\var{tarfile}] Instead of installing the files into +the \TeX{} system, make a \cmdname{tar} archive. + +\end{ttdescription} + +Additional options: + +\begin{ttdescription} + +\item [-{}-config] After installation, run \code{texconfig init}. + +\item [-{}-nohash] After installation, don't run \cmdname{mktexlsr} to +rebuild the filename database. + +\item [-{}-verbose] Give more information as the script runs. + +\end{ttdescription} + +Here are some usage examples: + +\begin{enumerate} + +\item To see the files in the package \pkgname{fancyhdr} without +installing it: + +\begin{alltt} +\ifSingleColumn> \Ucom{sh install-pkg.sh --package=fancyhdr --listonly} +\else> \Ucom{sh install-pkg.sh --package=fancyhdr \bs} +> \Ucom{--listonly} +\fi{} +texmf/doc/latex/fancyhdr/README +texmf/doc/latex/fancyhdr/fancyhdr.pdf +... +\end{alltt} + +\item Install the \LaTeX{} package \pkgname{natbib}: +\begin{alltt} +> \Ucom{sh install-pkg.sh --package=natbib} +\end{alltt} + +\item Install the \LaTeX{} package \pkgname{alg} without source files or +documentation: +\begin{alltt} +\ifSingleColumn> \Ucom{sh install-pkg.sh --package=alg --nosrc --nodoc} +\else> \Ucom{sh install-pkg.sh -{}-package=alg \bs} +> \Ucom{-{}-nosrc -{}-nodoc} +\fi\end{alltt} + +\item Install all the packages in the collection of additional +plain \TeX\ macros: +\begin{alltt} +> \Ucom{sh install-pkg.sh --collection=tex-plainextra} +\end{alltt} + +\item Write all files in the \pkgname{pstricks} package to a +\cmdname{tar} file in \path|/tmp|: +\begin{alltt} +\ifSingleColumn> \Ucom{sh install-pkg.sh --package=pstricks --archive=/tmp/pstricks.tar} +\else +> \Ucom{sh install-pkg.sh -{}-package=pstricks \bs} +> \Ucom{-{}-archive=/tmp/pstricks.tar} +\fi\end{alltt} + +\end{enumerate} + +\textifindoubt + + +% +\section{Post-installation} +\label{sec:postinstall} + +After the main installation is done, for any operating system, the +remaining steps are to configure the system for your local needs, and +perform some basic tests. + +Another sort of post-installation is to acquire packages, fonts, or +programs that were not included in \TL{}. The basic idea is to +install such additions in the \envname{TEXMFLOCAL} tree (if you +installed to disk), or \envname{TEXMFSYSVAR} (if you are running live). +See the ``Installation directories'' option on \p.\pageref{text:instdir}. + +Unfortunately, the details can and do vary widely, and so we do not attempt to +address them here. Here are some external links to descriptions: +\begin{itemize*} +\item +\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instpackages} +\item +\url{http://www.ctan.org/installationadvice} +\item +\url{http://www.ctan.org/tex-archive/info/beginlatex/html/chapter5.html#pkginst} +\item +\url{http://www.ctan.org/tex-archive/info/Type1fonts} for +installation information for fonts in particular. +\end{itemize*} + + +\subsection{The \protect\cmdname{texconfig} program} +\label{sec:texconfig} + +At any time after installation, you can and should use the program +\cmdname{texconfig} to configure the system to fit your local needs. It +is installed in the architecture-specific subdirectory +\texttt{TEXDIR/bin/\var{arch}} along with everything else. + +If you run it without arguments, it will enter full-screen mode and +allow you to view and change options interactively. + +You can also run it with various command-line options. Here are some of +the most common (\TL{} is configured for the A4 paper size by default): + +\begin{ttdescription} + +\item [texconfig paper letter] Set default paper size for +various programs and drivers (\cmdname{pdftex}, \cmdname{dvips}, +\cmdname{dvipdfm}, \cmdname{xdvi}) to be \acro{US} letter. The other +allowable size is \optname{a4}, which is the default. + +\item [texconfig rehash] Update all the \TeX{} ``filename databases'', +after adding or removing files. + +\item [texconfig faq] Show the \teTeX{} \acro{FAQ}. +(See also the main \TeX{} \acro{FAQ} in \OnCD{texmf-doc/doc/english/FAQ-en}.) + +\item [texconfig help] Output help information for \cmdname{texconfig}. + +\end{ttdescription} + +Of course, \cmdname{texconfig} can only support changing a few of the +many options and configuration parameters in a \TeX{} system. The main +configuration file for the base \Webc{} programs is named +\filename{texmf.cnf}. You can find its location by running +\samp{kpsewhich texmf.cnf}; it contains many comments explaining the +default settings and useful alternatives. + +\cmdname{texconfig} alters files in a user-specific directory, as in +\dirname{$HOME/.texlive2007}. If you install \TeX\ just for yourself, +that is unlikely to make a difference. But if you install \TeX\ on a +multi-user system, you will want to change the configuration for the +whole system. In this case, run \cmdname{texconfig-sys} instead of +\cmdname{texconfig}. + +Likewise, the \cmdname{updmap} and \cmdname{fmtutil} scripts were +changed, to work under \dirname{$HOME/.texliveYYYY}. To alter system +directories, use \cmdname{updmap-sys} and \cmdname{fmtutil-sys}. + +In particular, for multi-user systems, you will probably want to +pregenerate the standard formats with \texttt{fmtutil-sys --missing}. +Otherwise, each user will end up with their own formats. + +Also, if you have a personally-modified copy of \filename{fmtutil.cnf} +or \filename{updmap.cfg}, instead of using the ones generated by +installation, they must be installed in the tree referenced by the +variable \envname{TEXMFSYSCONFIG}. + +The variables specifying the directories altered by these commands are +listed in section~\ref{sec:texmftrees}, \p.\pageref{sec:texmftrees}. +You can see the actual directories by running \texttt{texconfig conf}, +and you can change them by editing \filename{texmf.cnf}. + + +\subsection{Testing the installation} +\label{sec:test-install} + +After installing \TL{} as best you can, you naturally want to test +it out, so you can start creating beautiful documents and\slash or fonts. + +This section gives some basic procedures for testing that the new system +is functional. We give Unix commands; under \MacOSX{} and Windows, +you're more likely to run the tests through a graphical interface, but +the principles are the same. + +\begin{enumerate} + +\item Make sure that you can run the \cmdname{tex} program in the first +place: + +\begin{alltt} +> \Ucom{tex -{}-version} +TeX 3.141592 (Web2C 7.5.5) +kpathsea version 3.5.5 +... +\end{alltt} +If this comes back with `command not found' instead of version and +copyright information, most likely you don't have the correct +\dirname{bin} subdirectory in your \envname{PATH}. See +the environment-setting information on \p.\pageref{text:path}. + +\item Process a basic \LaTeX{} file: +\begin{alltt} +> \Ucom{latex sample2e.tex} +This is pdfeTeXk, Version 3.141592... +... +Output written on sample2e.dvi (3 pages, 7496 bytes). +Transcript written on sample2e.log. +\end{alltt} +If this fails to find \filename{sample2e.tex} or other files, perhaps +you have interference from old environment variables or configuration +files. For a deep analysis, you can always ask \TeX{} to report on +exactly what it is searching for, and finding; see ``Debugging actions'' +on page~\pageref{Debugging}. + +\item Preview the result online: +\begin{alltt} +> \Ucom{xdvi sample2e.dvi} +\end{alltt} +(Under Windows, the analogous command is \cmdname{dviout}.) You should +see a new window with a nice document explaining some of the basics of +\LaTeX{}. (Well worth reading, by the way if you're new to the system.) +You do have to be running under X for \cmdname{xdvi} to work; if you're +not, or your \envname{DISPLAY} environment variable is set incorrectly, +you'll get an error \samp{Can't open display}. + +\item Create a \PS{} file for printing or display: +\begin{alltt} +> \Ucom{dvips sample2e.dvi -o sample2e.ps} +\end{alltt} + +\item Create a \acro{PDF} file instead of \dvi{}; this processes the +\filename{.tex} file and writes \acro{PDF} directly: +\begin{alltt} +> \Ucom{pdflatex sample2e.tex} +\end{alltt} + +\item Preview the \acro{PDF} file: +\begin{alltt} +> \Ucom{gv sample2e.pdf} +\textrm{or:} +> \Ucom{xpdf sample2e.pdf} +\end{alltt} +Unfortunately neither \cmdname{gv} nor \cmdname{xpdf} are currently +included in \TL{}, so you must install them separately. See +\url{http://www.gnu.org/software/gv} and +\url{http://www.foolabs.com/xpdf}, respectively. + +\item Other standard test files you may find useful: + +\begin{ttdescription} +\item [small2e.tex] A simpler document than \filename{sample2e}, to +reduce the input size if you're having troubles. +\item [testpage.tex] Test if your printer introduces any offsets. +\item [nfssfont.tex] For printing font tables and tests. +\item [testfont.tex] Also for font tables, but using plain \TeX{}. +\item [story.tex] The most canonical (plain) \TeX{} test file of all. +You must type \samp{\bs bye} to the \code{*} prompt after \samp{tex +story.tex}. +\end{ttdescription} +You can process these in the same way as we did with +\filename{sample2e.tex}. + +\end{enumerate} + +If you are new to \TeX{}, or otherwise need help with actually +constructing \TeX{} or \LaTeX{} documents, please visit +\url{http://tug.org/begin.html} for some introductory resources. + + +\section{\MacOSX{} installation} +\label{sec:mac-install} + +The recommended way to install \TeX\ on \MacOSX\ is from the Mac\TeX\ +distribution, new in 2005. This is provided on the \pkgname{live} +\DVD{} in the top-level \dirname{mactex/} directory. It contains its +own (native) installer for a full \TeX\ distribution, based on a +combination of te\TeX\ and \TL, along with many additional applications +and documentation. The project web page is \url{http://tug.org/mactex}. + +If you prefer, installation of \TeX{} under \MacOSX{} can also be done +directly from \TL, using the \filename{install*} scripts, as follows. + +In order to run the installation scripts under \MacOSX, you need to have +the \cmdname{bash} shell installed. If you are running \MacOSX~10.2 +or later, you have \cmdname{bash}, and can proceed. If you're running +an earlier \MacOSX{} version, however, the default shell is +\cmdname{zsh}, which won't work; you'll need to get \cmdname{bash} from +the Internet, or more likely upgrade your system. + +Once you have \cmdname{bash}, the Unix installation documentation in the +previous section can be followed. See section~\ref{sec:unix-install} on +\p.\pageref{sec:unix-install}; \MacOSX-specific notes are included there +where needed. + +\section{Windows installation} +\label{sec:win-install} + +In this release of \TL{}, happily, the distribution once +again has a native Windows installer, named \cmdname{tlpmgui.exe}. (See +section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}, for an +explanation of the different distributions.) + +\cmdname{tlpmgui} has essentially the same options as the Unix +installer, only done through a GUI interface: selecting schemes, +individual collections, installation directories, and so on. +Section~\ref{sec:unix-install-disk} on +\p.\pageref{sec:unix-install-disk} describes the basic elements. It +also allows some post-installation activities such as adding/removing +packages, updating the filename database and building formats. +Moreover, \cmdname{tlpmgui} can setup the system for running +programs directly from the \DVD. + +For those who like to look underneath the hood, \cmdname{tlpmgui} uses +as its ``engine'' a command-line Windows program named \cmdname{tlpm}. + +The Windows \TeX{} system included in \TL{} is based on new binaries +borrowed from the \acro{W32TEX} distribution, kindly provided by Akira Kakuto. +It also includes some older (but still working) tools made by Fabrice +Popineau, and also a new \texttt{dvi} previewer, \textsf{dviout} by +Toshio Oshima. + +\TL{} can be installed on systems running Windows 98, \acro{ME}, +\acro{NT}, \acro{2K} or \acro{XP}. Older versions of Windows (3.1x) +and \acro{MS-DOS} are not supported. + +\textbf{Warning:} Win9.x users must ensure they have enough environment + space before undertaking installation. The \cmdname{tlpmgui.exe} + program won't change the environment size for them. A few environment + variables will be created and it is possible you run out of + environment space. Add \texttt{SHELL=COMMAND.COM /E:4096 /P} in the + config.sys file in order to increase your environment size. + +\subsection{Installing \protect\TeX\protect\ Live to disk} + +After inserting the \TL{} \acro{CD} into the \acro{CD} drive, autostart should +activate \cmdname{tlpmgui}. If it does not, click \guiseq{Start\arw Run}, +then type \verb|:\setuptl\tplmgui.exe| (or +\verb|:\texlive\setuptl\tplmgui.exe| if you are +installing from the \TeX\ Collection \acro{DVD}), where \verb|| +is the drive letter with the \TeX\ Live \acro{CD} (or TeX Collection +\acro{DVD}), and then click \acro{OK}. + +The installation window titled \guiseq{TeX Live installation and maintenance +utility} should open. It contains the following sections: \guiseq{Main +customization}, \guiseq{Install}, \guiseq{Select a scheme}, \guiseq{Select +systems}, \guiseq{Directories} and \guiseq{Options}. + +By default, \cmdname{tlpmgui} tries to detect if \TeX{} is already +installed and depending on the result starts either in fresh +installation or maintenance mode. If you have \TeX{} already installed +but want to install the new version nevertheless, you can use +\texttt{tlpmgui~--install-mode} to force installation mode; but you +should know what you are doing, as the new \TL{} installation will +override the environment variables and other settings of the existing +installation; reverting to your old installation is not automatically +supported. + +Diagnostic information is collected by \cmdname{tlpmgui} in a log file +which is deleted at the end of the run, along with any other temporary +files. Invoking with \texttt{--debug} displays the names and contents +of all \cmdname{tlpmgui} temporary files in a separate window. + +In the \guiseq{Directories} section the installation drive (directory) +next to the \guiseq{CD/DVD} button should be displayed (e.g., +\texttt{F:/} or \texttt{F:/texlive/} for the \acro{DVD}), but if it is not, +then click the \guiseq{CD/DVD} button and select the \acro{CD/DVD} +drive, with the \TL{} \acro{CD} (or \TeX\ Collection \acro{DVD}). + +The directory in which you wish to install the software can be set by +clicking the \guiseq{TLroot} button. This directory will be set as +\path|TLroot| environment variable for later usage. + +In the \guiseq{Select a scheme} section the desired \TL{} installation scheme +should be chosen by clicking the radio button labelled with the installation +scheme name (e.g., \guiseq{scheme-gust}). Each scheme is accompanied by an +\guiseq{Info} button which, when clicked, displays a short description of the +relevant scheme. + +A scheme is a large set of files targeted at some kind of usage. There are +generic schemes for basic, medium and full installations. The remaining ones +are either targeted at certain LUGs (i.e., what GUST or GUTenberg propose +for their members) or application targeted (e.g., for XML and \TeX{} +cooperation). A preselected scheme can be refined. This is done in the +\guiseq{Main customization} section by choosing additional collections from +\guiseq{Standard collections} or \guiseq{Language collections}. For example, +by clicking the \guiseq{Select} button labelled \guiseq{Standard +collections}, additional collections like Metapost, Omega or documentation +in different languages can be selected. + +\guiseq{Wintools} collection is selected by default as it contains many small +programs, usually absent in Windows, which can be handy, like graphics +converters: \cmdname{sam2p}, \cmdname{jpeg2ps}, \cmdname{tiff2png}; +(de)compression programs: \cmdname{bzip2}, \cmdname{gzip}, \cmdname{unzip}, +and \cmdname{wget} which is needed for \cmdname{getnonfreefonts} (new) +utility. + +Next, clicking the \guiseq{Select} button labelled \guiseq{Language +Collections} in the \guiseq{Main customization} section opens the +\guiseq{Language collections} window in which the installation language can +be chosen by ticking the box next to the language. + +Next, click the \guiseq{Install} button in the \guiseq{Install} section to +start the installation proper process. + +\textbf{Note:} The \guiseq{Perl} and \guiseq{Ghostscript} are installed only +on demand. They should be installed unless they are already installed and you +really know what you are doing. Both programs are required by many important +tools. The \verb|PERL5LIB| and \verb|GS_LIB| environment variables will be +set too, as well the path to Ghostscript binaries will be added to the +\verb|PATH| variable. + +The \TL{} system needs some post-processing steps (format files +generation, ls-R databases generation, environment variables, etc.). All +these operations are done there, some of them can be lengthy. So please wait +until you see a statement about the successfully finished installation. + +The shortcut for \cmdname{tlpmgui} (and also \cmdname{dviout}, if installed) +will be added to the menu \guiseq{Start\arw Programs\arw TeXLive2007}. + +If it is needed (Win9x/WinME), you will be asked to reboot your computer. + +\subsection{Support packages for Windows} +\label{sec:win-xemtex} + +To be complete, a \TL installation needs support packages that are not +commonly found on a Windows machine. Many scripts are written using the Perl +language. Some important tools require the Ghostscript \PS{} interpreter to +render or to convert files. A graphic file toolbox is also needed in some +cases. Last but not least, a \TeX-oriented editor makes it easy to type in +your \TeX{} files. + +All these tools are quite easy to find for Windows, but in order to try to +make your life even easier, we have put such a set of tools on \TL: +\begin{itemize*} +\item GNU \cmdname{Ghostscript} 8.54 +\item a minimal \cmdname{Perl} 5.8, sufficient to run all the \TL{} + Perl scripts. +\item win-tools is a set of small programs (bzip2, gzip, jpeg2ps + and tiff2png) +%\item a subset of \cmdname{ImageMagick} 5.5.6 +%\item the \cmdname{ISpell} checker +%\item \cmdname{XEmacs} 21.5.14 with a selection of packages to support +%\TeX{} typesetting. +\end{itemize*} + +Perl and Ghostscript are installed upon request; you may explicitly +deselect them during installation if you already have them. + +If you don't want to install this bundle, then you are on your own to +install the required tools to complete your \TL{} system. Here is a +list of places to get those tools: + +\begin{description} +\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} +\item[Perl] \url{http://www.activestate.com/} (but you might need some + supplementary packages from CPAN: \url{http://www.cpan.org/}) +\item[ImageMagick] \url{http://www.imagemagick.com} +\item[NetPBM] alternatively, you could use NetPBM instead of ImageMagick to + process or convert your graphic files. NetPBM home page is + \url{http://netpbm.sourceforge.net/} +\item[\TeX-oriented editors] There is a wide choice, and it is a matter of the + user's taste. Here is a selection: + \begin{itemize*} + \item \cmdname{GNU Emacs} is available natively under Windows, see + \url{http://www.gnu.org/software/emacs/windows/ntemacs.html} + \item \cmdname{Emacs} with AucTeX is available natively under Windows, see + \url{ftp://alpha.gnu.org/gnu/auctex} + \item \cmdname{WinShell} is available on \TL in the \path|support| + directory, see \url{http://www.winshell.de} + \item \cmdname{WinEdt} is shareware available from \url{http://www.winedt.com} + \item \cmdname{Vim} is available from \url{http://www.vim.org} + \item TeXnicCenter is free software, available from + \url{http://www.toolscenter.org} and in the proTeXt distribution. + \item \cmdname{LEd} is available from \url{http://www.ctan.org/support/LEd} + \item \cmdname{SciTE} is available from \url{http://www.scintilla.org/SciTE.html} + \end{itemize*} +\end{description} + +You might want to install other tools that are not free\footnote{Not +free, that is, in the sense of freedom to modify and redistribute, +following free software guidelines. This does not mean you can't acquire +them for no money.} and therefore not included on \TL{}, such as +\cmdname{GSView}, the \cmdname{Ghostscript} companion to more +conveniently view PS/PDF files. \cmdname{GSView} is available from +\url{http://www.cs.wisc.edu/~ghost/gsview/} or any \acro{CTAN} site. + +\section{Maintenance of the installation in Windows} + +If you have \TeX\ Live installed, you can use \cmdname{tlpmgui} again +for modifying and maintaining your installation. + +\subsection{Adding/removing packages} + +As the \cmdname{tlpmgui} shortcut is available in the \guiseq{Start\arw +Programs\arw TeXLive2007} menu, start it from here. The maintenance window +titled \guiseq{TeX Live installation and maintenance utility} shows. It +contains several tabs: \guiseq{Add Packages}, \guiseq{Remove packages}, +\guiseq{Manage installation}, \guiseq{Remove installation}. + +Click the tab labelled \guiseq{Add packages} or \guiseq{Remove packages} +to enter the relevant functionality and then: + +\begin{itemize} +\item In the first tab select the proper \CD{} drive (or \DVD with + \texttt{texlive} directory) by pressing the \guiseq{CD/DVD} button. +\item Click the \guiseq{Search} button in the \guiseq{Buttons} section to +display or refresh in the \guiseq{Select packages to\dots} section the +list of packages to install or remove. + +When adding packages, the list of installed packages is compared to the list +of packages available from your \CD/\DVD. Only packages not already installed are +displayed. It is up to you to select which packages you want to +install. + +When removing individual packages, only a list of installed packages +will be displayed. + +Please note that for both \guiseq{Add packages} and \guiseq{Remove packages} +the collections are listed first. + +\item Select a package by clicking on the name of the package. Clicking the +\guiseq{Info} button in the \guiseq{Buttons} section displays a short +description of the selected package in the window located in the \guiseq{Info +about the selected item} section. To select several packages at once hold +down one of the Ctrl or Shift keys at your keyboard while holding down the +left mouse button or drag the mouse pointer while holding down the left mouse +button. + +\item Click the \guiseq{Install} or \guiseq{Remove} button in the +\guiseq{Buttons} section to perform the appropriate action. +\end{itemize} + +\subsection{Configuring and other management tasks} + +The functions available in the tab labelled \guiseq{Manage the installation} +are helpful in performing actions needed when you want to add support for a +language which was not selected during the installation, or add/regenerate a +format which was not selected during the installation or was modified after +the installation. + +The following actions can be performed: + +\begin{itemize} +\item Refresh the \filename{ls-R} database +\item Create formats (All or Missing) +\item Edit \filename{language.dat} +\item Edit \filename{fmtutil.cnf} +\item Edit \filename{updmap.cfg} +\end{itemize} + +Note: you can close the Edit\dots{} window with the \guiseq{Cancel} or +\guiseq{Done} button; the latter will start rebuilding the format files +(or the fontmap files if you have edited \filename{updmap.cfg}), followed by a +\filename{ls-R} database files refresh. + +For more information about the configuration see section~\ref{sec:persconf}, +\p.\pageref{sec:persconf}. + +\subsection{Uninstalling \protect\TL{}} + +The tab labelled \guiseq{Remove the TeX Live installation} opens a window +which contains functionality not worth describing and we do not know who would +need it and what it is for\dots :-) + +Anyway, if you have the \path|texmf-local| directory for your local additions, +the removal procedure will not wipe it out or delete things in it. However, +it will be done only if you select it explicitly. The \path|setuptl| +directory containing \cmdname{tlpmgui} and related files will not be deleted. +You will have to do some manual cleanup to actually remove them. + +\subsection{Adding your own packages to the installation} + +First, whatever changes you make, \textbf{do not forget to rebuild the ls-R +database files}. Otherwise, your new files will not be found. You can do this +either via the \cmdname{tlpmgui} run and selection of the appropriate action +from the \guiseq{Manage the installation} tab, or manually running the +\file{mktexlsr} command. + +If you want to add files that are not provided by the \TL{} distribution, +it is recommended to put them in the \path|$TEXMFLOCAL| directory. This +way, you will be safe against upgrades of the \TL{} software. + +The directory pointed to by \path|$TEXMFLOCAL| is initially empty. If, +for example, you want to add the support file for the Maple symbolic +computation program, you will have to put the style files in:\\ +\path|c:\TeXLive2007\texmf-local\tex\latex\maple\|\\ and the +documentation files in:\\ \path|c:\TeXLive2007\texmf-local\doc\latex\maple\| + +\subsection{Running \texttt{tlmp.exe} from the command line} +The \cmdname{tlpm.exe} program which is used as engine by \cmdname{tlpmgui} +has a number of other useful options. You can get the list by running: +\begin{verbatim} +tlpm --help +\end{verbatim} + +More information and examples of use can be found in \path|tlpm.readme|. + +\subsection{Network installation} + +\KPS{} knows about UNC names, so you can use them to get your TEXMF +tree from the network. But there is better than this. +All the support files and configuration files, everything except the files in the +\path|bin/win32| are shareable with a \teTeX{} or Unix \TL{} installation. That means +you can use Samba either to mount from an NT server to a Unix +workstation or the converse. Several strategies are possible: +\begin{itemize} +\item Put everything on the server. Just add each set of files for the OS and +architecture you want to use in the \path|bin| directory. That means +for example \path|bin/win32| and \path|bin/i386-linux|. Next configure +your main variables. You can use UNC names to +point to the right directories under Win32. +\item Install a local copy for the binaries and format files. In this + case, assign \path|$TEXMFMAIN| to the main \path|texmf| tree that + will be accessed remotely. Set \path|$TEXMFVAR| to be a local + directory which will hold local configuration files and on-the-fly + generated files. +\end{itemize} + +\subsection{What's different in Windows?} + +The Windows version of \Webc{} has some specific features that should be +pointed out. + +\begin{description} +\item[\cmdname{kpsecheck}] This command provides some options that did + not fit well into \cmdname{kpsewhich}. It will allow you to list all + the files that occur multiple times across your texmf trees. This + could be handy, but most of the time you will also get unwanted + output (like dozens of \path|README| files). It is noticeable + that all these files result in clashes inside the \KPS{}-hashing + mechanism; fortunately, \KPS{} never looks for these files. For + this reason, you can combine the \path|-multiple-occurrences| with 2 + other options for including or excluding any filename that match + some pattern (you can request for several patterns). + + The \cmdname{kpsecheck} command will also report the status of shared + memory: in use or not used. That might be useful to know because if + the status reported is \samp{in use}, that means one or several + processes are working, and the effect of any \cmdname{mktexlsr} + command will be delayed until the next time where no \KPS{} linked + process will be running. + + Last, this same command will report about the location it thinks + Ghostscript can be found. Under Win32, for many programs, it is + easier to use the Ghostscript dll, and find it by using the + Ghostscript registry key than to change the \path|PATH|, which has a + limited length anyway. +\item[\Webc{}] The engines have one more option than in Unix \Webc: + \begin{itemize} + \item \path|-proctimes| print statistics about the job run + time. It is to be noted that Win9x not being a true multitasking + operating system, it has no reliable timer for short periods, so + the value printed is an approximation. Under NT/2K/XP, the result + is quite accurate with user time and system time values allocated + for this run. For Unix + users: the \path|time| command is not usually available to Windows + users. + \end{itemize} +\end{description} + +\subsection{Personal configurations} +\label{sec:persconf} + +\subsubsection{Dvips} + +The configuration file for dvips can be found in\\ +\verb+C:\TeXLive2007\texmf-var\dvips\config\config.ps+\\ +You may open it with any editor + %(\cmdname{WinShell} will do fine) + and change some parameters: + +\begin{description} +\item [fonts] you can change the default printer \MF{} mode or printer + resolution in case \cmdname{dvips} needs to generate PK fonts. By default it + is configured to use Type~1 versions of the CM fonts, so it should + not call \cmdname{mktexpk} too often; +\item[printer] you can tell dvips where you want to print by default. If + the \optname{o} option is not followed by a printer name, then a + \file{.ps} \PS{} file is written. You can give dvips a printer + name such as: +\begin{verbatim} +o lpt1: +% o | lpr -S server -P myprinter +% o \\server\myprinter +\end{verbatim} +\item[paper] Next, you might want + to change the paper size from European (A4) to US letter + by making the US letter the first paper size mentioned in the file. + Scroll to the group of lines beginning with \code{@}. Move + the appropriate lines so that this section begins with the lines:\\ +\hspace*{1em} @ letterSize 8.5in 11in\\ +\hspace*{1em} @ letter 8.5in 11in\\ +\hspace*{1em} @+ \%\%BeginPaperSize: Letter\\ +\hspace*{1em} @+ letter\\ +\hspace*{1em} @+ \%\%EndPaperSize +\end{description} + +The current \TL{} distribution implements the procedure of making always +up-to-date fontmaps files for Dvips and Pdftex. This is done by the +\cmdname{updmap} program during installation. +If you add new font packages using the installation program or by hand, +edit the file \verb+updmap.cfg+ in \path|$TEXMFVAR/web2c|. + +\subsubsection{PdfTeX} + +If you use the program pdf{}latex to write \acro{PDF} format directly, +and you are using \acro{US} letter-size paper, edit the file +\verb+C:\TeXLive2007\texmf-var\tex\generic\config\pdftexconfig.tex+ and +change \samp{\bs pdfpagewidth} and \samp{\bs pdfpageheight}. These entries +should read: +\begin{alltt} +\bs{}pdfpagewidth=8.5 true in +\bs{}pdfpageheight=11 true in +\end{alltt} +Save the file and exit the editor. + +\subsubsection{Xe\TeX} +Xe\TeX{} for Windows is linked statically with fontconfig 2.4.2. +A configuration file for fontconfig is \verb+fonts.conf+. For details, +see the file \verb+fonts.conf+ itself which is in a directory shown by +the command \texttt{kpsewhich --var-value=FONTCONFIG\_PATH}. + +\subsubsection{GSView} +GSView is now distributed under the Aladdin License, and therefore is no +longer included in \TL{}. + +You may want to change the page size to US letter size. If so, open +GSView from the \guiseq{Start} menu, and select \guiseq{Media\arw Letter}. + +Also, there are menu settings that are supposed to give you the most +readable screen image. On \guiseq{Media \arw Display Settings}, set both +\optname{Text Alpha} and \optname{Graphics Alpha} to 4~bits. + +Note that the installation process has set all \code{.ps} and +\code{.eps} files to automatically open with \cmdname{GSView}. + +For printing instructions, see section~\ref{printing} below. + + +\subsection{Testing} + +For generic verification procedures, see section~\ref{sec:test-install} +(\p.\pageref{sec:test-install}). This section describes +Windows-specific tests. + +Open the file \verb+sample2e.tex+ in your editor (Xemacs, WinShell), +found in \path|C:\TeXLive2007\texmf-dist\tex\latex\base|. The \LaTeX\ source +should appear on the screen. Process it by clicking on the +\guiseq{Command\arw LaTeX} menu (XEmacs) or \LaTeX\ icon on the toolbar +(WinShell), then view it by clicking on the \guiseq{Command\arw View DVI} +menu (XEmacs) or Preview (dviout) icon (WinShell). + +At first, when you preview files with \cmdname{dviout}, it will create fonts +because screen fonts were not installed. After a while, you will have created +most of the fonts you use, and you will rarely see the font-creation window. + +\textbf{Hint for the future:} If a \LaTeX\ run stops because \LaTeX\ +cannot find a file, you can press Ctrl-z to quit. + + +\subsection{Printing} +\label{printing} + +It is possible to print from \cmdname{dviout}. In this case, printing +will be done using the Windows unified printer driver. By definition, it is +compatible with all printers. However, there is some drawback: it can +generate some huge spool files, and some (older) versions of Windows +just don't like them. The advantage is that you can use features like +embedding BMP or WMF images. You also need to make sure that the printer +parameters are correctly set, else you +will get scaled printing (printing at 600\dpi{} on a 300\dpi{} printer +will give you only one quadrant of your page). + +Printing is faster and more reliable if you run \cmdname{dvips} to make +a \filename{.ps} file and then print from \cmdname{GSView}. In +\cmdname{GSview}, select \guiseq{File\arw Print\ldots}. A \guiseq{Print} +window will appear. + +If you are using a \PS{} printer, \textit{be sure to select +\guiseq{\PS{} Printer}}. This is done in the \guiseq{Print Method} box +at the bottom left of the \guiseq{Print} window. You can then select any +of the printers that you have previously installed. If you fail to +check the box for \optname{\PS{} Printer}, printing will not work. + +If you will be using your own non-\PS{} printer, select +\guiseq{Ghostscript device} in the \guiseq{Print Method} box, then click +on the button to the right labelled \guiseq{djet500} and select your +printer type from the list that pops up. (In the older version of +\cmdname{GSView}, make sure \optname{\PS{} Printer} is \textit{not} +selected, then select your printer type from the \guiseq{Device} list.) + +\subsection{Tips and tricks for Win32} + +\subsubsection{Different flavors of Win32} + +What we call Win32 is not an operating system by itself. It is a large +set of functions (around 12,000 in the header files of the Microsoft +\acro{SDK}) that you can use to write programs for different operating +systems of the Windows family. + +Windows comes in different flavors: +\begin{itemize} +\item Win95, Win98 and Win\acro{ME}, which \emph{are not true multitasking, + multithreading} environments, but rather updated incarnations of + \acro{DOS}. This can be more or less proven by the fact that when + booting, the PC will load the \path|command.com| interpreter, and if + you stop the boot process at this point, you can ask for the current + (\acro{DOS}) version and it will answer something like \samp{MS-DOS + 7.0} (at least for the old versions of Win9x). +\item Windows \acro{NT}, which is a new operating system written from + scratch, capable of true multitasking behavior, and including many + high level features. +\item Windows 2000, based on \acro{NT}, with all the bells and + whistles of Win98. +\item Windows \acro{XP}, which comes with Personal and Pro flavors. This is + the last step in merging both lines of products (Win9x based and + \acro{NT} based). \acro{XP} is based on \acro{NT}. +\end{itemize} + +Win9x are able to run 32~bits programs and 16~bits programs +concurrently. But the operating system by itself is not entirely +written in 32~bits mode, and does not support memory protection: 16bits +applications can overwrite parts of the operating system memory! Some +parts of the system like the \acro{GDI} (Graphical Device Interface) +manage limited resources like bitmaps, fonts, pens and so on for the set +of all programs that run concurrently. All the bitmaps headers available +at the same time can't amount for more than 64kB. This explains the +performance tool and the fact that you can put your system on his knees +by making intensive use of graphic objects for example. + +NT, 2K and XP do not suffer from these limitations, and neither from +other Win9x limitations. They are true multitasking environments, with +protected memory. They are much more responsive than Win9x because +of better memory management, better file system and so on. + +\subsubsection{Command line prompt} + +You may wonder, ``Why would I need to use a command line prompt when +I have Windows?'' + +Good question! The problem is of very general nature. Not all operations +can be done easily using only a \acro{GUI}. Command line gives you +programming power\Dash assuming a clever command interpreter. + +But the problem here is more fundamental: \TeX{} is \emph{a batch} +tool. Not an interactive one. \TeX{} needs to compute the best +layout for each page, resolve cross-references and so on. This can be +done only by a global processing of the document. It is not (yet) a +task that can be done interactively. + +This means that you should use \TeX{} from a command line. In fact the +situation is not so bad. There is an advantage to write command line +tools for complex processing: they are better debugged, because they are +independent of any \acro{GUI} problems, and \acro{GUI} tools can be +designed to interface to the command line tools. This is the case for +\TeX{}, where you will mostly interact with it through a \acro{GUI} text +editor. + +However, you may need to use the command line prompt in a number of +situations. One is when you are having difficulties and want to debug +your setup. + +\begin{description} + \item[Win9x] You can open a command line prompt by looking either for + the \acro{MS-DOS} icon in the \guiseq{Start\arw Programs} menu, + or by choosing \guiseq{Start\arw Run} menu typing in + \path|command.com| as the program name. + \item[NT, 2K, XP] You can open a command line prompt by looking for + \guiseq{Command Prompt} in the \guiseq{Start\arw Accessories} menu. + You can also choose \guiseq{Start\arw Run} and type in + \path|cmd.exe|, which is the name of the brand new command + interpreter for \acro{NT} (thus, it is untrue to call this a + \emph{DOS} box!). +\end{description} + +These locations may change across different Windows versions. + +\subsubsection{Path separators} + +The Win32 API understands both \path|/| and \path|\| characters as PATH +separators. But the command interpreters do not! So whenever a path name +is used programmatically, you can use both separators, and even mix them +up in the same path name. But on the command line, you must type +\path|\| as path separator. The reason is compatibility: the command +processor used \samp{/} to introduce arguments to commands. + +All this to say: do not be surprised to read path names written using +the Unix convention; Windows-\TL{} is a port of \Webc, and aims to be +compatible across platforms. For this reason, all the configuration files +that need to specify path names use the Unix convention. + +\subsubsection{File systems} +\label{sec:clusters} + +The worst feature of Win9x with regard to \TeX{} is probably the +so-called FAT file system. \TeX{} uses very many small files, with size +around 1--3kB. The \acro{FAT} file system is old, and predates by +decades the multi-gigabytes hard disks we have today. As a result, it +cannot manage efficiently the tens of thousands of \TeX{} files found in +\TL{}. The \acro{FAT} file system allocates a minimum of 32kB for +\emph{any} file on a huge partition. It means that \TeX{} will use much +more disk space than it actually needs. + +The other, more modern, file systems available, \acro{FAT32} and +\acro{NTFS}, do not have this drawback. They manage clusters of 4kB +only. (You can lower the limit to 512 bytes on \acro{NTFS}.) + +\subsubsection{How to add some directory to your PATH} + +There are pairs of variables and values which behave much like global +variables inside your programs. The set of those variables is called the +environment. Each program is initialized with a copy of the +environment when it is run. It can request and change the +value of any variable. The changes happen in the copy of the +environment, and is not at all propagated to the other running +programs. + +Your PATH is a special environment variable used to search for +programs you want to run. +There is a different procedure to change it for Win9x, WinME and NT/2K/XP: + +\begin{description} +\item[Windows 95/98] Edit your \path|autoexec.bat|. In this file should be a line + starting with \texttt{PATH=} and followed by a list of directories separated + by \path|;|. Please add the directory with the executables in this line. + After this, this line could look as follows: +\begin{verbatim} +PATH=c:\windows;c:\windows\system;c:\TeXLive2007\bin\win32 +\end{verbatim} +\item[Windows ME] You need to run the special program + \path|c:\windows\system\msconfig.exe| to be able to change any + environment variable. From this program, select the `Environment' + tab, and then add or modify the variable you want. You will be asked to reboot the + machine upon any change. +\item[Windows NT/2K/XP] + Click left on \guiseq{Start \arw Settings \arw Control Panel}. Now the + window with the control panel icons opens. Double click on System. The + System Properties window opens. Click on the tab \textsf{Environment} + or look for a button named \guiseq{Environment Variables} among the + dialog boxes. Now you can change the environment variables for your + user account. Note: There are also displayed the environment settings + for the system. Normally, you can't change the system variables + unless you have administrator rights on your machine. If you want to + change the \texttt{PATH} for all users, you will have to contact your + system administrator or be the system administrator yourself\Dash in + the latter case you should know what you are doing. + + If there is already a \texttt{PATH} setting for your user account, + left click on \texttt{PATH}. In the field \textsf{Variable} appears + \texttt{PATH} while the field Value shows the current setting of + \texttt{PATH} as a list of directories separated by \path|;|. Add + the directory where the executables are located (e.g. + \path|c:\TeXLive2007\bin\win32|). If there isn't a \texttt{PATH} variable + for your user account, simply click in the field Variable and type + in \texttt{PATH}, click in the field \textsf{Value} + and type in the directory with the executables. Important: Click on + the \textsf{Apply} button before clicking \textsf{Ok}, otherwise the + changes to \texttt{PATH} won't apply to your system. Be careful when + changing the environment settings. +\end{description} + +The best way to be sure that a variable has been properly set is to +open a console and type: +\begin{verbatim} +set VARIABLE +\end{verbatim} +which should return the corresponding value. + +\subsubsection{\TeX{} engines} + +If you have a look at the \Webc{} documentation, you will read that all +the various \TeX{} derived programs use the same base engine. For +example, \path|tex.exe| and \path|latex.exe| are exact copies of the +same program, but each one will use a different format file, based on +its calling name. + +Under Unix, this feature is implemented through \emph{symbolic +links}. It saves up a bit of disk space, because some engines are +used with many different format files. + +The Win32 API does not know about file links. So to save up almost +the same amount of memory, all the \TeX{} base engines have been put +in DLLs (\emph{Dynamic Linked Library}). This means that you will have +the following layout: +\begin{alltt} +2006-11-23 07:06 2 560 latex.exe +2007-01-06 23:54 1 073 664 pdftex.dll +2006-01-28 08:05 2 560 pdftex.exe +\end{alltt} +and the \path|latex.exe| file is nothing but a rough copy of +\path|pdftex.exe| using the same core \path|pdftex.dll|. +The same trick has been used for the \path|mktex*.exe| family of programs +which are linked to the \path|mktex.dll| library. + +In fact, a generic tool called \path|irun.exe| is provided to build the +equivalent of Unix hard links for executable files only under Win32. + +\subsection{In case of problems} +\label{sec:troubleshooting} + +\subsubsection{What to do if \texttt{latex} does not find your files?} + +\begin{itemize} + +\item \cmdname{kpsewhich} is the tool of choice to debug any +problem. However, \cmdname{kpsewhich} outputs debug information to +stderr, and the older Windows consoles do not know how to redirect +stderr to a file. (Windows NT and later do support redirections, but +the trick below will work for any console.) For diagnostic purposes you +can temporarily set an environment variable (in a \acro{DOS}/\acro{cmd} box): + +\begin{verbatim} +SET KPATHSEA_DEBUG_OUTPUT=err.log +\end{verbatim} +You can also set the debug level: +\begin{verbatim} +SET KPATHSEA_DEBUG=-1 +\end{verbatim} + +Similarly, to redirect stderr to stdout: +\begin{verbatim} +SET KPATHSEA_DEBUG_OUTPUT=con: +\end{verbatim} +This way you can capture both stdout and stderr in the same file. +\item Assuming the installation has been done in \path|c:/TeX|, check + the following values: \\ + {\small + \begin{tabular}{ll} + \path|kpsewhich -expand-path $SELFAUTOPARENT| & \path|c:/TeX| \\ + \path|kpsewhich -expand-path $TEXMF| & \path|c:/TeX/texmf....| \\ + \path|kpsewhich -expand-path $TEXMFCNF| & + \path|.;c:/TeX/texmf-var/web2c;| \\ + \path|kpsewhich -expand-var $TEXINPUTS| & \path|.;c:/TeX/texmf/tex//| + \end{tabular} +} +\item If you have other \TeX{}-related values already set in your + environment, please, remove them. They are overriding the ones in + texmf.cnf. +\item Check the values from:\\ +{\small + \begin{tabular}{ll} + \texttt{kpsewhich cmr10.tfm} & \path|c:/TeX/texmf-dist/fonts/tfm/public/cm/cmr10.tfm|\\ + \texttt{kpsewhich latex.fmt}& \path|c:/TeX/texmf-var/web2c/latex.fmt| + \end{tabular} +} +\item At this point, if everything is correct, \TeX{} and friends + should work. If it is not the case, you will need to play with + the \path|-debug=n| option from \path|kpsewhich|, and check back all + the values. Try to identify and report the problem. +\end{itemize} + +\subsubsection{What to do if your setup still does not work as expected?} + +Here are several questions to investigate: + +\begin{enumerate} +\item Is \file{tex.exe} in my \path|PATH|? + +\item Is the \path|TEXMFCNF| variable correctly set to +\path|c:/TeXLive2007/texmf-var/web2c| (default value)? + +\item Are there any errors in the log file generated by the +\file{tlmpgui.exe} program? +\file{tlmpgui.log} can be found in your +\file{TEMP} directory. You can find this by searching for the +string \samp{Error}. Hint: the log file can show some errors after +building all format files. Please do not panic: perhaps some formats +weren't already installed. + +\item Are there any relevant bug fixes at \url{http://tug.org/texlive/}? +(Unlikely, but it doesn't hurt to check.) + +\end{enumerate} + +The \TL{} software consists of hundreds of programs and tens of +thousands of files, all from varying sources. So it is quite difficult to +predict all possible causes for problems. Nevertheless, we will do our +best to help you. (See section~\ref{sec:help}, \p.\pageref{sec:help}.) + +% don't use \Webc so the \uppercase in the headline works. +\section{A user's guide to Web2C} + +\Webc{} is an integrated collection of \TeX-related programs: \TeX{} +itself, \MF{}, \MP, \BibTeX{}, etc. It is the heart of \TL{}. + +A bit of history: The original implementation was by Tomas Rokicki who, +in 1987, developed a first \TeX{}-to-C system based on change files +under Unix, which were primarily the original work of Howard Trickey and +Pavel Curtis. Tim Morgan became the maintainer of the system, and +during this period the name changed to Web-to-C\@. In 1990, Karl Berry +took over the work, assisted by dozens of additional contributors, and +in 1997 he handed the baton to Olaf Weber. + +The \Webc{} system runs on Unix, 32-bit Windows systems, \MacOSX{}, and +other operating systems. It uses Knuth's original sources for \TeX{} and +other basic programs written in \web{} and translates them into C source +code. The core \TeX{} programs are: + +\begin{cmddescription} +\item[bibtex] Maintaining bibliographies. +\item[dmp] \cmdname{troff} to MPX (\MP{} pictures). +\item[dvicopy] Expands virtual font references in \dvi{} files. +\item[dvitomp] \dvi{} to MPX (MetaPost pictures). +\item[dvitype] \dvi{} to human-readable text. +\item[gftodvi] Generic font proofsheets. +\item[gftopk] Generic to packed fonts. +\item[gftype] GF to human-readable text. +\item[makempx] \MP{} label typesetting. +\item[mf] Creating typeface families. +\item[mft] Prettyprinting \MF{} source. +\item[mpost] Creating technical diagrams. +\item[mpto] MetaPost label extraction. +\item[newer] Compare modification times. +\item[patgen] Creating hyphenation patterns. +\item[pktogf] Packed to generic fonts. +\item[pktype] PK to human-readable text. +\item[pltotf] Plain text property list to TFM. +\item[pooltype] Display \web{} pool files. +\item[tangle] \web{} to Pascal. +\item[tex] Typesetting. +\item[tftopl] TFM to plain text property list. +\item[vftovp] Virtual font to virtual property list. +\item[vptovf] Virtual property list to virtual font. +\item[weave] \web{} to \TeX. +\end{cmddescription} + +\noindent The precise functions and syntax of these programs are +described in the documentation of the individual packages and of \Webc{} +itself. However, knowing a few principles governing the whole family of +programs will help you take advantage of your \Webc{} installation. + +All programs honor these standard \acro{GNU} options: +\begin{ttdescription} +\item[-{}-help] print basic usage summary. +\item[-{}-verbose] print detailed progress report. +\item[-{}-version] print version information, then exit. +\end{ttdescription} + +For locating files the \Webc{} programs use the path searching library +\KPS{}. This library uses a combination of environment variables and a +configuration files to optimize searching the (huge) collection of +\TeX{} files. \Webc{} can look at more than one directory tree +simultaneously, which is useful in maintaining \TeX's standard +distribution and local extensions in two distinct trees. To speed up +file searches the root of each tree has a file \file{ls-R}, containing +an entry showing the name and relative pathname for all files under that +root. + +\subsection{Kpathsea path searching} + +Let us first describe the generic path searching mechanism of the \KPS{} +library. + +We call a \emph{search path} a colon- or semicolon\hyph sepa\-rated list +of \emph{path elements}, which are basically directory names. A +search path can come from (a combination of) many sources. To look up +a file \samp{my-file} along a path \samp{.:/dir}, \KPS{} checks each +element of the path in turn: first \file{./my-file}, then +\file{/dir/my-file}, returning the first match (or possibly all +matches). + +In order to adapt optimally to all operating systems' conventions, on +non-Unix systems \KPS{} can use filename separators different from +colon (\samp{:}) and slash (\samp{/}). + +To check a particular path element \var{p}, \KPS{} first checks if a +prebuilt database (see ``Filename data\-base'' on +page~\pageref{Filename-database}) applies to \var{p}, i.e., if the database +is in a directory that is a prefix of \var{p}. If so, the path +specification is matched against the contents of the database. + +If the database does not exist, or does not apply to this path +element, or contains no matches, the filesystem is searched (if this +was not forbidden by a specification starting with \samp{!!}\ and if +the file being searched for must exist). \KPS{} constructs the list +of directories that correspond to this path element, and then checks +in each for the file being sought. + +The ``file must exist'' condition comes into play with \samp{.vf} files and +input files read by \TeX's \cs{openin} command. Such files may not +exist (e.g., \file{cmr10.vf}), and so it would be wrong to search the +disk for them. Therefore, if you fail to update \file{ls-R} when you +install a new \samp{.vf} file, it will never be found. +Each path element is checked in turn: first the database, then the +disk. If a match is found, the search stops and the result is +returned. + +Although the simplest and most common path element is a directory +name, \KPS{} supports additional features in search paths: layered +default values, environment variable names, config file values, users' +home directories, and recursive subdirectory searching. Thus, we say +that \KPS{} \emph{expands} a path element, meaning it transforms all +the specifications into basic directory name or names. This is +described in the following sections in the same order as it takes +place. + +Note that if the filename being searched for is absolute or explicitly +relative, i.e., starts with \samp{/} or \samp{./} or \samp{../}, +\KPS{} simply checks if that file exists. + +\ifSingleColumn +\else +\begin{figure*} +\verbatiminput{examples/ex5.tex} +\setlength{\abovecaptionskip}{0pt} + \caption{An illustrative configuration file sample} + \label{fig:config-sample} +\end{figure*} +\fi + +\subsubsection{Path sources} +\label{Path-sources} + +A search path can come from many sources. In the order in which +\KPS{} uses them: + +\begin{enumerate} +\item + A user-set environment variable, for instance, \envname{TEXINPUTS}\@. + Environment variables with a period and a program name appended + override; e.g., if \samp{latex} is the name of the program being run, + then \envname{TEXINPUTS.latex} will override \envname{TEXINPUTS}. +\item + A program-specific configuration file, for exam\-ple, a line + \samp{S /a:/b} in \cmdname{dvips}'s \file{config.ps}. +\item A \KPS{} configuration file \file{texmf.cnf}, containing a line like + \samp{TEXINPUTS=/c:/d} (see below). +\item The compile-time default. +\end{enumerate} +\noindent You can see each of these values for a given +search path by using the debugging options (see ``Debugging actions'' +on page~\pageref{Debugging}). + +\subsubsection{Config files} + +\begingroup\tolerance=3500 +\KPS{} reads \emph{runtime configuration files} named \file{texmf.cnf} +for search path and other definitions. The search path used to look +for these files is named \envname{TEXMFCNF} (by default such a file lives +in the \file{texmf/web2c} subdirectory). \emph{All} +\file{texmf.cnf} files in the search path will be read and definitions +in earlier files override those in later files. Thus, with a search +path of \verb|.:$TEXMF|, values from \file{./texmf.cnf} override those +from \verb|$TEXMF/texmf.cnf|. +\endgroup + +\begin{itemize} +\item + Comments start with \code{\%} and continue to the end of the line. +\item + Blank lines are ignored. +\item + A \bs{} at the end of a line acts as a continuation character, + i.e., the next line is appended. Whitespace at the beginning of + continuation lines is not ignored. +\item + Each remaining line has the form: +\begin{alltt} + \var{variable}[.\var{progname}] [=] \var{value} +\end{alltt}% + where the \samp{=} and surrounding whitespace are optional. +\item + The \ttvar{variable} name may contain any character other + than whitespace, \samp{=}, or \samp{.}, but sticking to + \samp{A-Za-z\_} is safest. +\item + If \samp{.\var{progname}} is present, the definition only + applies if the program that is running is named + \texttt{\var{progname}} or \texttt{\var{progname}.exe}. This allows + different flavors of \TeX{} to have different search paths, for + example. +\item \var{value} may contain any characters except + \code{\%} and \samp{@}. The + \code{\$\var{var}.\var{prog}} feature is not available on the + right-hand side; instead, you must use an additional variable. A + \samp{;}\ in \var{value} is translated to \samp{:}\ if + running under Unix; this is useful to be able to have a single + \file{texmf.cnf} for Unix, \acro{MS-DOS} and Windows systems. +\item + All definitions are read before anything is expanded, so + variables can be referenced before they are defined. +\end{itemize} +A configuration file fragment illustrating most of these points is +\ifSingleColumn +shown below: + +\verbatiminput{examples/ex5.tex} +\else +shown in Figure~\ref{fig:config-sample}. +\fi + +\subsubsection{Path expansion} +\label{Path-expansion} + + +\KPS{} recognizes certain special characters and constructions in +search paths, similar to those available in Unix shells. As a +general example, the complex path, +\verb+~$USER/{foo,bar}//baz+, expands to all subdirectories under +directories \file{foo} and \file{bar} in \texttt{\$USER}'s home +directory that contain a directory or file \file{baz}. These +expansions are explained in the sections below. +%$ +\subsubsection{Default expansion} +\label{Default-expansion} + +\tolerance=2500 +If the highest-priority search path (see ``Path sources'' on +page~\pageref{Path-sources}) contains an \emph{extra colon} (i.e., +leading, trailing, or doubled), \KPS{} inserts at that point the +next-highest-prio\-rity search path that is defined. If that inserted +path has an extra colon, the same happens with the next highest. For +example, given an environment variable setting + +\tolerance=1500 + +\begin{alltt} +> \Ucom{setenv TEXINPUTS /home/karl:} +\end{alltt} +and a \code{TEXINPUTS} value from \file{texmf.cnf} of + +\begin{alltt} + .:\$TEXMF//tex +\end{alltt} +then the final value used for searching will be: + +\begin{alltt} + /home/karl:.:\$TEXMF//tex +\end{alltt} + +Since it would be useless to insert the default value in more than one +place, \KPS{} changes only one extra \samp{:}\ and leaves any others in +place. It checks first for a leading \samp{:}, then a trailing +\samp{:}, then a doubled \samp{:}. + +\subsubsection{Brace expansion} + +A useful feature is brace expansion, which means that, for instance, +\verb+v{a,b}w+ expands to \verb+vaw:vbw+. Nesting is allowed. +This is used to implement multiple \TeX{} hierarchies, by +assigning a brace list to \code{\$TEXMF}. +For example, in \file{texmf.cnf}, the following definition +(appproximately; there are actually even more trees) is made: +\begin{verbatim} + TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN} +\end{verbatim} +Using this you can then write something like +\begin{verbatim} + TEXINPUTS = .;$TEXMF/tex// +\end{verbatim} +%$ +which means that, after looking in the current directory, the +\code{\$TEXMFHOME/tex}, \code{\$TEXMFLOCAL/tex}, \code{\$TEXMFVAR/tex} +and \code{\$TEXMFMAIN/tex} trees \emph{only}) will be searched (the +last two use using \file{ls-R} data base files). It is a convenient +way for running two parallel \TeX{} structures, one ``frozen'' (on a +\CD, for instance) and the other being continuously updated with new +versions as they become available. By using the \code{\$TEXMF} +variable in all definitions, one is sure to always search the +up-to-date tree first. + +\subsubsection{Subdirectory expansion} +\label{Subdirectory-expansion} + +Two or more consecutive slashes in a path element following a directory +\var{d} is replaced by all subdirectories of \var{d}: first those +subdirectories directly under \var{d}, then the subsubdirectories under +those, and so on. At each level, the order in which the directories are +searched is \emph{unspecified}. + +If you specify any filename components after the \samp{//}, only +subdirectories with matching components are included. For example, +\samp{/a//b} expands into directories \file{/a/1/b}, \file{/a/2/b}, +\file{/a/1/1/b}, and so on, but not \file{/a/b/c} or \file{/a/1}. + +Multiple \samp{//} constructs in a path are possible, but +\samp{//} at the beginning of a path is ignored. + +\subsubsection{List of special characters and their meaning: a summary} + +The following list summarizes the special characters in \KPS{} +configuration files. + +% need a wider space for the item labels here. +\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} +\begin{ttdescription} +\item[\CODE{:}] Separator in path specification; at the beginning or + the end of a path it substitutes the default path expansion.\par +\item[\CODE{;}] Separator on non-Unix systems (acts like \code{:}). +\item[\CODE{\$}] Variable expansion. +\item[\CODE{\string~}] Represents the user's home directory. +\item[\CODE{\char`\{...\char`\}}] Brace expansion. +\item[\CODE{//}] Subdirectory expansion (can occur anywhere in + a path, except at its beginning). +\item[\CODE{\%}] Start of comment. +\item[\CODE{\bs}] Continuation character (allows multi-line entries). +\item[\CODE{!!}] Search \emph{only} database to locate file, \emph{do + not} search the disk. +\end{ttdescription} + + +\subsection{Filename databases} +\label{Filename-database} + +\KPS{} goes to some lengths to minimize disk accesses for searches. +Nevertheless, at installations with enough directories, searching each +possible directory for a given file can take an excessively long time +(this is especially true if many hundreds of font directories have to +be traversed.) Therefore, \KPS{} can use an externally-built plain text +``database'' file named \file{ls-R} that maps files to directories, +thus avoiding the need to exhaustively search the disk. + +A second database file \file{aliases} allows you to give additional +names to the files listed in \file{ls-R}. This can be helpful to +confirm to \acro{DOS} 8.3 filename conventions in source files. + +\subsubsection{The filename database} +\label{ls-R} + +As explained above, the name of the main filename database must be +\file{ls-R}. You can put one at the root of each \TeX{} hierarchy in +your installation that you wish to be searched (\code{\$TEXMF} by +default); most sites have only one hierarchy. \KPS{} looks for +\file{ls-R} files along the \code{TEXMFDBS} path. + +The recommended way to create and maintain \samp{ls-R} is to run the +\code{mktexlsr} script included with the distribution. It is invoked +by the various \samp{mktex}\dots\ scripts. In principle, this script +just runs the command +\begin{alltt} +cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R +\end{alltt} +presuming your system's \code{ls} produces the right output format +(\acro{GNU} \code{ls} is all right). To ensure that the database is +always up-to-date, it is easiest to rebuild it regularly via +\code{cron}, so that it is automatically updated when the installed +files change, such as after installing or updating a \LaTeX{} package. + +If a file is not found in the database, by default \KPS{} goes ahead +and searches the disk. If a particular path element begins with +\samp{!!}, however, \emph{only} the database will be searched for that +element, never the disk. + + +\subsubsection{kpsewhich: Standalone path searching} +\label{Invoking-kpsewhich} + +The \texttt{kpsewhich} program exercises path searching independent of any +particular application. This can be useful as a sort of \code{find} +program to locate files in \TeX{} hierarchies (this is used heavily in +the distributed \samp{mktex}\dots\ scripts). + +\begin{alltt} +> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} +\end{alltt} +The options specified in \ttvar{option} start with either \samp{-} +or \samp{-{}-}, and any unambiguous abbreviation is accepted. + +\KPS{} looks up each non-option argument on the command line as a +filename, and returns the first file found. There is no option to +return all the files with a particular name (you can run the Unix +\samp{find} utility for that). + +The more important options are described next. + +\begin{ttdescription} +\item[\texttt{-{}-dpi=\var{num}}]\mbox{} + Set the resolution to \ttvar{num}; this only affects \samp{gf} + and \samp{pk} lookups. \samp{-D} is a synonym, for compatibility + with \cmdname{dvips}. Default is 600. + +\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ + Set the format for lookup to \ttvar{name}. By default, the + format is guessed from the filename. For formats which do not have + an associated unambiguous suffix, such as \MP{} support files and + \cmdname{dvips} configuration files, you have to specify the name as + known to \KPS{}, such as \texttt{tex} or \texttt{enc files}. Run + \texttt{kpsewhich -{}-help} for a list. + +\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ + Set the mode name to \ttvar{string}; this only affects \samp{gf} + and \samp{pk} lookups. No default: any mode will be found. +\item[\texttt{-{}-must-exist}]\mbox{}\\ + Do everything possible to find the files, notably including + searching the disk. By default, only the \file{ls-R} database is + checked, in the interest of efficiency. +\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ + Search along the path \ttvar{string} (colon-separated as usual), + instead of guessing the search path from the filename. \samp{//} and + all the usual expansions are supported. The options \samp{-{}-path} + and \samp{-{}-format} are mutually exclusive. +\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ + Set the program name to \texttt{\var{name}}. + This can affect the search paths via the \texttt{.\var{progname}} + feature. + The default is \cmdname{kpsewhich}. +\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ + shows the path used for file lookups of file type \texttt{\var{name}}. + Either a filename extension (\code{.pk}, \code{.vf}, etc.) or a + name can be used, just as with \samp{-{}-format} option. +\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ + sets the debugging options to \texttt{\var{num}}. +\end{ttdescription} + + +\subsubsection{Examples of use} +\label{SExamplesofuse} + +Let us now have a look at \KPS{} in action. Here's a straightforward search: + +\begin{alltt} +> \Ucom{kpsewhich article.cls} + /usr/local/texmf-dist/tex/latex/base/article.cls +\end{alltt} +We are looking for the file \file{article.cls}. Since the \samp{.cls} +suffix is unambiguous we do not need to specify that we want to look for a +file of type \optname{tex} (\TeX{} source file directories). We find it in +the subdirectory \file{tex/latex/base} below the \samp{texmf-dist} \TL\ +directory. Similarly, all of the following are found without problems +thanks to their unambiguous suffix. +\begin{alltt} +> \Ucom{kpsewhich array.sty} + /usr/local/texmf-dist/tex/latex/tools/array.sty +> \Ucom{kpsewhich latin1.def} + /usr/local/texmf-dist/tex/latex/base/latin1.def +> \Ucom{kpsewhich size10.clo} + /usr/local/texmf-dist/tex/latex/base/size10.clo +> \Ucom{kpsewhich small2e.tex} + /usr/local/texmf-dist/tex/latex/base/small2e.tex +> \Ucom{kpsewhich tugboat.bib} + /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib +\end{alltt} + +That last is a \BibTeX{} bibliography database for \textsl{TUGBoat} articles. + +\begin{alltt} +> \Ucom{kpsewhich cmr10.pk} +\end{alltt} +Font bitmap glyph files of type \file{.pk} are used by display +programs like \cmdname{dvips} and \cmdname{xdvi}. Nothing is returned in +this case since there are no pre-generated Computer Modern \samp{.pk} +files in \TL{}\Dash the Type~1 variants are used by default. +\begin{alltt} +> \Ucom{kpsewhich wsuipa10.pk} +\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk +\else /usr/local/texmf-var/fonts/pk/ljfour/public/ +... wsuipa/wsuipa10.600pk +\fi\end{alltt} + +For these fonts (a phonetic alphabet from the University of Washington) +we had to generate \samp{.pk} files, and since the default \MF{} mode on +our installation is \texttt{ljfour} with a base resolution of 600\dpi{} +(dots per inch), this instantiation is returned. +\begin{alltt} +> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} +\end{alltt} +In this case, when specifying that we are interested in a resolution +of 300\dpi{} (\texttt{-dpi=300}) we see that no such font is available on +the system. A program like \cmdname{dvips} or \cmdname{xdvi} would +go off and actually build the required \texttt{.pk} files +using the script \cmdname{mktexpk}. + +Next we turn our attention to \cmdname{dvips}'s header and configuration +files. We first look at one of the commonly used files, the general +prolog \file{tex.pro} for \TeX{} support, before turning our attention +to the generic configuration file (\file{config.ps}) and the \PS{} font +map \file{psfonts.map}\Dash as of 2004, map and encoding files have +their own search paths and new location in \dirname{texmf} trees. As +the \samp{.ps} suffix is ambiguous we have to specify explicitly which +type we are considering (\optname{dvips config}) for the file +\texttt{config.ps}. +\begin{alltt} +> \Ucom{kpsewhich tex.pro} + /usr/local/texmf/dvips/base/tex.pro +> \Ucom{kpsewhich --format="dvips config" config.ps} + /usr/local/texmf/dvips/config/config.ps +> \Ucom{kpsewhich psfonts.map} + /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map +\end{alltt} + +We now take a closer look at the \acro{URW} Times \PS{} support +files. The prefix for these in the standard font naming scheme is +\samp{utm}. The first file we look at is the configuration file, +which contains the name of the map file: +\begin{alltt} +> \Ucom{kpsewhich --format="dvips config" config.utm} + /usr/local/texmf-dist/dvips/psnfss/config.utm +\end{alltt} +The contents of that file is +\begin{alltt} + p +utm.map +\end{alltt} +which points to the file \file{utm.map}, which we want to +locate next. +\begin{alltt} +> \Ucom{kpsewhich utm.map} + /usr/local/texmf-dist/fonts/map/dvips/times/utm.map +\end{alltt} +This map file defines the file names of the Type~1 \PS{} fonts in +the URW collection. Its contents look like (we only show part of the +lines): +\begin{alltt} +utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} +\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb +\else /usr/local/texmf-dist/fonts/type1/ +... urw/utm/utmr8a.pfb +\fi\end{alltt} + +It should be evident from these examples how you can easily locate the +whereabouts of a given file. This is especially important if you suspect +that the wrong version of a file is picked up somehow, since +\cmdname{kpsewhich} will show you the first file encountered. + +\subsubsection{Debugging actions} +\label{Debugging} + +Sometimes it is necessary to investigate how a program resolves file +references. To make this practical, \KPS{} offers various levels of +debugging output: + +\begin{ttdescription} +\item[\texttt{\ 1}] \texttt{stat} calls (disk lookups). When running + with an up-to-date \file{ls-R} database this should almost give no + output. +\item[\texttt{\ 2}] References to hash tables (such as \file{ls-R} + databases, map files, configuration files). +\item[\texttt{\ 4}] File open and close operations. +\item[\texttt{\ 8}] General path information for file types + searched by \KPS. This is useful to find out where a particular + path for the file was defined. +\item[\texttt{16}] Directory list for each path element (only relevant + for searches on disk). +\item[\texttt{32}] File searches. +\end{ttdescription} +A value of \texttt{-1} will set all the above options; in practice, +this is usually the most convenient. + +Similarly, with the \cmdname{dvips} program, by setting a combination of +debug switches, one can follow in detail where files are being picked up +from. Alternatively, when a file is not found, the debug trace shows in +which directories the program looks for the given file, so that one can +get an indication what the problem~is. + +Generally speaking, as most programs call the \KPS{} library +internally, one can select a debug option by using the +\envname{KPATHSEA\_DEBUG} environment variable, and setting it to (a +combination of) values as described in the above list. + +(Note for Windows users: it is not easy to redirect +all messages to a file in this system. For diagnostic purposes +you can temporarily \texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log}). + +Let us consider, as an example, a small \LaTeX{} source file, +\file{hello-world.tex}, which contains the following input. +\begin{verbatim} + \documentclass{article} + \begin{document} + Hello World! + \end{document} +\end{verbatim} +This little file only uses the font \file{cmr10}, so let us look at +how \cmdname{dvips} prepares the \PS{} file (we want to use the Type~1 +version of the Computer Modern fonts, hence the option \texttt{-Pcms}). +\begin{alltt} +> \Ucom{dvips -d4100 hello-world -Pcms -o} +\end{alltt} +In this case we have combined \cmdname{dvips}'s debug class 4 (font +paths) with \KPS's path element expansion (see \cmdname{dvips} Reference +Manual, \OnCD{texmf/doc/html/dvips/dvips_toc.html}). +The output (slightly rearranged) appears in +Figure~\ref{fig:dvipsdbga}. +\begin{figure*}[tp] +\centering +\input{examples/ex6a.tex} +\caption{Finding configuration files}\label{fig:dvipsdbga} + +\bigskip + +\input{examples/ex6b.tex} +\caption{Finding the prolog file}\label{fig:dvipsdbgb} + +\bigskip + +\input{examples/ex6c.tex} +\caption{Finding the font file}\label{fig:dvipsdbgc} +\end{figure*} + +\cmdname{dvips} starts by locating its working files. First, +\file{texmf.cnf} is found, which gives the definitions of the search +paths for the other files, then the file database \file{ls-R} (to +optimize file searching) and the file \file{aliases}, which makes it +possible to declare several names (e.g., a short \acro{DOS}-like 8.3 and +a more natural longer version) for the same file. Then \cmdname{dvips} +goes on to find the generic configuration file \file{config.ps} +before looking for the customization file \file{.dvipsrc} (which, in +this case is \emph{not found}). Finally, \cmdname{dvips} locates the +config file for the Computer Modern \PS{} fonts \file{config.cms} +(this was initiated with the \texttt{-Pcms} option on the \cmdname{dvips} +command). This file contains the list of the map files which +define the relation between the \TeX{}, \PS{} and file system +names of the fonts. +\begin{alltt} +> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} + p +ams.map + p +cms.map + p +cmbkm.map + p +amsbkm.map +\end{alltt} +\cmdname{dvips} thus goes on to find all these files, plus the generic +map file \file{psfonts.map}, which is always loaded (it contains +declarations for commonly used \PS{} fonts; see the last part of +Section \ref{SExamplesofuse} for more details about \PS{} map +file handling). + +At this point \cmdname{dvips} identifies itself to the user: +\begin{alltt} +This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) +\end{alltt} +\ifSingleColumn +Then it goes on to look for the prolog file \file{texc.pro}: +\begin{alltt}\small +kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro +\end{alltt} +\else +Then it goes on to look for the prolog file \file{texc.pro} (see +Figure~\ref{fig:dvipsdbgb}). +\fi + +After having found the file in question, \cmdname{dvips} outputs +date and time, and informs us that it will generate the +file \file{hello-world.ps}, then that it needs the font file +\file{cmr10}, and that the latter is declared as ``resident'' (no +bitmaps needed): +\begin{alltt}\small +TeX output 1998.02.26:1204' -> hello-world.ps +Defining font () cmr10 at 10.0pt +Font cmr10 is resident. +\end{alltt} +Now the search is on for the file \file{cmr10.tfm}, which is found, +then a few more prolog files (not shown) are referenced, and finally +the Type~1 instance \file{cmr10.pfb} of the font is located and +included in the output file (see last line). +\begin{alltt}\small +kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, + path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: + /var/tex/fonts/tfm//). +kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm +kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, + ... + +kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb +[1] +\end{alltt} + +\subsection{Runtime options} + +Another useful feature of \Webc{} is its possibility to control a number +of memory parameters (in particular, array sizes) via the runtime file +\file{texmf.cnf} read by \KPS{}. The memory settings can be found in +Part 3 of that file in the \TL{} distribution. The more important +are: + +\begin{ttdescription} +\item[\texttt{main\_memory}] + Total words of memory available, for + \TeX{}, \MF{} and \MP. You must make a new format file for each + different setting. For instance, you could generate a ``huge'' + version of \TeX{}, and call the format file \texttt{hugetex.fmt}. + Using the standard way of specifying the program name used by \KPS{}, + the particular value of the \texttt{main\_memory} variable will then + be read from \file{texmf.cnf}. +\item[\texttt{extra\_mem\_bot}] + Extra space for ``large'' \TeX{} data structures: + boxes, glue, breakpoints, etc. Especially useful if you use + \PiCTeX{}. +\item[\texttt{font\_mem\_size}] + Number of words for font information available for \TeX. This + is more or less the total size of all TFM files read. +\item[\texttt{hash\_extra}] + Additional space for the hash table of control sequence names. + Approximately 10,000 control sequences can be stored in the main + hash table; if you have a large book with numerous cross-references, + this might not be enough. The default value of + \texttt{hash\_extra} is \texttt{50000}. +\end{ttdescription} + +\noindent Of course, this facility is no substitute for truly dynamic +arrays and memory allocation, but since these are extremely difficult to +implement in the present \TeX{} source, these runtime parameters provide +a practical compromise allowing some flexibility. + + +\begin{comment} +\section{Building on a new Unix platform} + +If you have a platform for which executables are not included, you will +need to compile \TeX{} and friends. This is not as hard as it +sounds. What you need is all in the directory \texttt{source} in the +distribution. + +\subsection{Prerequisites} + +You will need at least 100 megabytes of disk space to compile all of +\TeX{} and its support programs. You'll also need an \acro{ANSI} C +compiler, a \cmdname{make} utility, a lexical scanner, and a parser +generator. We recommend the \acro{GNU} version of these programs +(\cmdname{gcc}, \acro{GNU} \cmdname{make}, \cmdname{m4}, \cmdname{flex}, +\cmdname{bison}). You may be able to work with other C compilers and +\cmdname{make} programs, but you will need a good understanding of +building Unix programs to sort out problems. + +Also, the command \texttt{uname} must return a sensible value. + + +\subsection{Configuration} + +To begin, perform a normal installation of \TL{} to your disk (see +section~\ref{sec:unix-install-disk} on +\p.\pageref{sec:unix-install-disk}). You may wish to skip installing +all of the prebuilt binaries. + +Then, unpack the source from the compressed \texttt{tar} file in the +directory \dirname{source} to your disk and change directory to where +you placed it. + +Next, run \cmdname{configure} with a command line like this: +\begin{alltt} +> \Ucom{sh configure -prefix=/usr/local/TeX} +\end{alltt} + +The \optname{-prefix} directory is the one where you installed the +support tree; the directory layout will be as follows (where \$TEXDIR +stands for the directory you chose): + +\noindent +\begin{tabular}{>{\ttfamily}ll@{}} + \dirname{$TEXDIR/share/texmf} & main tree with fonts,\\ + & \qquad macros, etc\\ + \dirname{$TEXDIR/man} & Unix manual pages\\ + \dirname{$TEXDIR/info} & \acro{GNU} style Info manuals\\ + \dirname{$TEXDIR/bin/$PLATFORM} & binaries\\ +\end{tabular} +%$ + +If you want to leave out the \dirname{$PLATFORM} directory level, +i.e., put the binaries directly into \dirname{$TEXDIR/bin}, specify +the \verb|--disable-multiplatform| option to \cmdname{configure}. + +Have a look at the output of \verb|./configure --help| for more +options you can use. For example, you can skip building of \OMEGA{} and +\eTeX{}. + + +\subsection{Running \cmdname{make}} + +Make sure the shell variable or option \texttt{noclobber} is not set. +Then, run the main \cmdname{make} like this: +\begin{alltt} +> \Ucom{make world} +\end{alltt} +and relax\ldots + +Alternatively, you want to log all the output, as in: +\begin{alltt} +> \Ucom{sh -c "make world >world.log 2>\&1" \&} +\end{alltt} + +Before you believe that everything went ok, please check the log file +for errors: \acro{GNU} \cmdname{make} always uses the string \samp{***} +whenever a command fails. Also, check if all the programs were built: + +\begin{alltt} +> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} +> \Ucom{ls | wc} +\end{alltt} +The result should be over 200 (you can check the exact number with the +\dirname{bin} directory contents in the distribution). + +If you need special privileges for \texttt{make install}, you can +separate the \samp{make world} into two different runs, like this: +\begin{alltt} +> \Ucom{make all} +> \Ucom{su} +> \Ucom{make install strip} +\end{alltt} + +After you've installed your new binaries, you should follow the normal +post-installation procedures, given in section~\ref{sec:postinstall} +(\p.\pageref{sec:postinstall}). + +Also, if you'd like to make your binaries available to others, please +contact us. We'll be happy to put them on the \TL\ web pages. +\end{comment} + +\section{Acknowledgements} + +\TL{} is a joint effort by virtually all of the \TeX{} user groups. +This edition of \TL{} was overseen by Sebastian Rahtz and Karl Berry. +The other principal contributors are listed below. + +\begin{itemize*} + +\item The English, German, Dutch, and Polish \TeX{} user groups +(\acro{TUG}, \acro{DANTE} e.V., \acro{NTG}, and \acro{GUST}, +respectively), which together provide the necessary technical +and administrative infrastructure. Please join your local user group! + +\item The \acro{CTAN} team, which distributes the \TL{} images and +provides the common infrastructure for package updates, upon which \TL{} +depends. + +\item Peter Breitenlohner and the \eTeX\ team for the stable foundation +of future \TeX's. + +\item Thomas Esser, without whose marvelous \teTeX{} package \TL{} +would certainly not exist, and whose continual help makes it a better +product. + +\item Michel Goossens, who co-authored the original documentation. + +\item Eitan Gurari, whose \TeX4ht was used to create the \HTML{} +version of this documentation, and who worked tirelessly to improve +it at short notice. + +\item Hans Hagen, for major testing and making the \ConTeXt\ format +conform to \TL's needs. + +\item \Thanh, Martin Schr\"oder, and the pdf\TeX\ team for continuing +enhancements of \TeX's abilities. + +\item Taco Hoekwater, for renewed development efforts on MetaPost and +\TeX\ itself. + +\item Pawe{\l} Jackowski, for the Windows installer \cmdname{tlpm}, +and Tomasz {\L}uczak, for \cmdname{tlpmgui}. + +\item Akira Kakuto, for great assistance in incorporating the Windows +binaries from his \acro{W32TEX} distribution +(\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}). + +\item Jonathan Kew and his employer \acro{SIL}, for the major new +development of Xe\TeX{} and taking the time and trouble to integrate it +in \TL{}. + +\item Reinhard Kotucha, for helping with the massive task of updating +packages in \TL{}, as well as Windows research efforts, the +\texttt{getnonfreefonts} script, and more. + +\item Petr Ol\v{s}ak, who coordinated and checked all the Czech and Slovak +material very carefully. + +\item Toshio Oshima, for his \cmdname{dviout} previewer for Windows. + +\item Fabrice Popineau, for the original Windows support in \TL{}. + +\item Norbert Preining, for helping with the \TL{} infrastructure and +package updates, and coordinating the Debian version of \TL{} (together +with Frank K\"uster), making many suggestions for improvement along the +way. + +\item Staszek Wawrykiewicz, the principal tester for all of \TL{}, +and coordinator of the many major Polish contributions: fonts, Windows +installation, and more. + +\item Olaf Weber, for his patient assembly and maintenance of Web2C, +upon which all else depends. + +\item Gerben Wierda, for creating and maintaining the \MacOSX\ support, +and much integration and testing. + +\item Graham Williams, on whose work the catalogue of packages depends. + +\end{itemize*} + +Builders of the binaries: +Tigran Aivazian and Hartmut Henkel (\pkgname{x86\_64-linux}), +Akira Kakuto and Fabrice Popineau (\pkgname{win32}), +Manfred Lotz (\pkgname{i386-freebsd}), +Norbert Preining (\pkgname{alpha-linux}), +Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-linux}, + \pkgname{sparc-solaris}), +Karl Berry (\pkgname{i386-linux}), +Olaf Weber (\pkgname{mips-irix}), +Gerben Wierda (\pkgname{i386-darwin}, \pkgname{powerpc-darwin}). + +Documentation and translation updates: +Karl Berry (English), +Daniel Flipo \& Fabrice Popineau (French), +G\"unter Partosch \& Hartmut Henkel (German), +Petr Sojka \& Jan Busa (Czech\slash Slovak), +Boris Veytsman (Russian), +Staszek Wawrykiewicz (Polish). + +Of course the most important acknowledgement must go to Donald Knuth, first +for inventing \TeX, and then for giving it to the world. + + +\section{Release history} +\label{sec:history} + +\subsection{Past} + +Discussion began in late 1993 when the Dutch \TeX{} Users Group was +starting work on its 4All\TeX{} \CD{} for \acro{MS-DOS} users, and it +was hoped at that time to issue a single, rational, \CD{} for all +systems. This was too ambitious a target for the time, but it did spawn +not only the very successful 4All\TeX{} \CD{}, but also the \acro{TUG} +Technical Council working group on a \emph{\TeX{} Directory Structure} +(\url{http://tug.org/tds}), which specified how to create consistent and +manageable collections of \TeX{} support files. A complete draft of the +\TDS{} was published in the December 1995 issue of \textsl{TUGboat}, and +it was clear from an early stage that one desirable product would be a +model structure on \CD{}. The distribution you now have is a very direct +result of the working group's deliberations. It was also clear that the +success of the 4All\TeX{} \CD{} showed that Unix users would benefit +from a similarly easy system, and this is the other main strand of +\TL. + +We first undertook to make a new Unix-based \TDS{} \CD{} in the autumn +of 1995, and quickly identified Thomas Esser's \teTeX{} as the ideal +setup, as it already had multi-platform support and was built with +portability across file systems in mind. Thomas agreed to help, and work +began seriously at the start of 1996. The first edition was released in +May 1996. At the start of 1997, Karl Berry completed a major new release +of Web2c, which included nearly all the features which Thomas Esser had +added in \teTeX, and we decided to base the 2nd edition of the \CD{} on +the standard \Webc, with the addition of \teTeX's \texttt{texconfig} +script. The 3rd edition of the \CD{} was based on a major revision of +\Webc, 7.2, by Olaf Weber; at the same time, a new revision of \teTeX +was being made, and \TL{} included almost all of its features. The +4th edition followed the same pattern, using a new version of \teTeX, +and a new release of \Webc{} (7.3). The system now included a complete +Windows setup. + +For the 5th edition (March 2000) many parts of the \CD{} were revised +and checked, updating hundreds of packages. Package details were stored +in XML files. But the major change for \TeX\ Live 5 was that all +non-free software was removed. Everything in \TL{} is now intended +to be compatible with the Debian Free Software Guidelines +(\url{http://www.debian.org/intro/free}); we have done our best to check +the license conditions of all packages, but we would very much +appreciate hearing of any mistakes. + +The 6th edition (July 2001) had much more material updated. The major +change was a new install concept: the user could select a more exact set +of needed collections. Language-related collections were completely +reorganized, so selecting any of them installs not only macros, fonts, +etc., but also prepares an appropriate \texttt{language.dat}. + +The 7th edition of 2002 had the notable addition of \MacOSX{} support, +and the usual myriad of updates to all sorts of packages and +programs. An important goal was integration of the source back with +\teTeX, to correct the drift apart in versions~5 and~6. + +\subsubsection{2003} + +In 2003, with the continuing flood of updates and additions, we found +that \TL{} had grown so large it could no longer be contained on a +single \CD, so we split it into three different distributions (see +section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist}). In +addition: + +\begin{itemize*} +\item At the request of the \LaTeX{} team, we changed the standard + \cmdname{latex} and \cmdname{pdflatex} commands to now use \eTeX{} (see + \p.\pageref{text:etex}). +\item The new Latin Modern fonts were included (and are recommended). +\item Support for Alpha \acro{OSF} was removed + (\acro{HPUX} support was removed previously), since no one had (or + volunteered) hardware available on which to compile new binaries. +\item Windows setup was substantially changed; for the first time + an integrated environment based on XEmacs was introduced. +\item Important supplementary programs for Windows + (Perl, Ghost\-script, Image\-Magick, Ispell) are now installed + in the \TL{} installation directory. +\item Font map files used by \cmdname{dvips}, \cmdname{dvipdfm} + and \cmdname{pdftex} are now generated by the new program + \cmdname{updmap} and installed into \dirname{texmf/fonts/map}. +\item \TeX{}, \MF{}, and \MP{} now, by default, output most input + characters (32 and above) as themselves in output (e.g., + \verb|\write|) files, + log files, and the terminal, i.e., \emph{not} translated using the + \verb|^^| notation. In \TL{}~7, this translation was + dependent on the system locale settings; now, locale settings do + not influence the \TeX{} programs' behavior. If for some reason + you need the \verb|^^| output, rename the file + \verb|texmf/web2c/cp8bit.tcx|. (Future releases will have cleaner + ways to control this.) +\item This documentation was substantially revised. +\item Finally, since the edition numbers had grown unwieldy, + the version is now simply identified by the year: \TL{} 2003. +\end{itemize*} + + +\subsubsection{2004} + +2004 saw many changes: + +\begin{itemize} + +\item If you have locally-installed fonts which use their own +\filename{.map} or (much less likely) \filename{.enc} support files, you +may need to move those support files. + +\filename{.map} files are now searched for in subdirectories of +\dirname{fonts/map} only (in each \filename{texmf} tree), along the +\envname{TEXFONTMAPS} path. Similarly, \filename{.enc} files are now +searched for in subdirectories of \dirname{fonts/enc} only, along the +\envname{ENCFONTS} path. \cmdname{updmap} will attempt to warn about +problematic files. + +For methods of handling this and other information, please see +\url{http://tug.org/texlive/mapenc.html}. + +\item The \TK\ has been expanded with the addition of a \MIKTEX-based +installable \CD, for those who prefer that implementation to Web2C. +See section~\ref{sec:struct-tl} (\p.\pageref{sec:struct-tl}). + +\item Within \TL, the single large \dirname{texmf} tree of previous +releases has been replaced by three: \dirname{texmf}, +\dirname{texmf-dist}, and \dirname{texmf-doc}. See +section~\ref{sec:tld} (\p.\pageref{sec:tld}), and the \filename{README} +files for each. + +\item All \TeX-related input files are now collected in +the \dirname{tex} subdirectory of \dirname{texmf*} trees, rather than +having separate sibling directories \dirname{tex}, \dirname{etex}, +\dirname{pdftex}, \dirname{pdfetex}, etc. See +\CDref{texmf-doc/doc/english/tds/tds.html\#Extensions} +{\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}. + +\item Helper scripts (not meant to be invoked by users) are now located +in a new \dirname{scripts} directory of \dirname{texmf*} trees, and +searched for via \verb|kpsewhich -format=texmfscripts|. So if you have +programs which call such scripts, they'll need to be adjusted. See +\CDref{texmf-doc/doc/english/tds/tds.html\#Scripts} +{\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}. + +\item Almost all formats leave most characters printable as +themselves via the ``translation file'' \filename{cp227.tcx}, instead of +translating them with the \verb|^^| notation. Specifically, characters +at positions 32--256, plus tab, vertical tab, and form feed are +considered printable and not translated. The exceptions are plain \TeX\ +(only 32--126 printable), \ConTeXt\ (0--255 printable), and the +\OMEGA-related formats. This default behavior is almost the same as in +\TL\,2003, but it's implemented more cleanly, with more possibilities +for customization. See \CDref{texmf/doc/web2c/web2c.html\#TCX-files} +{\texttt{texmf/doc/web2c/web2c.html\#TCX-files}}. +(By the way, with Unicode input, \TeX\ may output partial character +sequences when showing error contexts, since it is byte-oriented.) + +\item \textsf{pdfetex} is now the default engine for all formats +except (plain) \textsf{tex} itself. (Of course it generates \acro{DVI} +when run as \textsf{latex}, etc.) This means, among other things, that +the microtypographic features of \textsf{pdftex} are available in +\LaTeX, \ConTeXt, etc., as well as the \eTeX\ features +(\OnCD{texmf-dist/doc/etex/base/}). + +It also means it's \emph{more important than ever} to use the +\pkgname{ifpdf} package (works with both plain and \LaTeX) or equivalent +code, because simply testing whether \cs{pdfoutput} or some other +primitive is defined is not a reliable way to determine if \acro{PDF} +output is being generated. We made this backward compatible as best we +could this year, but next year, \cs{pdfoutput} may be defined even when +\acro{DVI} is being written. + +\item pdf\TeX\ (\url{http://pdftex.org}) has many new features: + + \begin{itemize*} + + \item \cs{pdfmapfile} and \cs{pdfmapline} provide font map support + from within a document. + + \item Microtypographic font expansion can be used more easily.\\ + \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} + + \item All parameters previously set through the special configuration + file \filename{pdftex.cfg} must now be set through primitives, + typically in \filename{pdftexconfig.tex}; \filename{pdftex.cfg} is no + longer supported. Any extant \filename{.fmt} files must be redumped + when \filename{pdftexconfig.tex} is changed. + + \item See the pdf\TeX\ manual for more: \OnCD{texmf/doc/pdftex/manual}. + + \end{itemize*} + +\item The \cs{input} primitive in \cmdname{tex} (and \cmdname{mf} and +\cmdname{mpost}) now accepts double quotes containing spaces and other +special characters. Typical examples: +\begin{verbatim} +\input "filename with spaces" % plain +\input{"filename with spaces"} % latex +\end{verbatim} +See the Web2C manual for more: \OnCD{texmf/doc/web2c}. + +\item enc\TeX\ support is now included within Web2C and consequently all +\TeX\ programs, via the \optname{-enc} option\Dash \emph{only when +formats are built}. enc\TeX\ supports general re-encoding of input and +output, enabling full support of Unicode (in \acro{UTF}-8). See +\OnCD{texmf-dist/doc/generic/enctex/} and +\url{http://www.olsak.net/enctex.html}. + +\item Aleph, a new engine combining \eTeX\ and \OMEGA, is available. +A little information is available in \OnCD{texmf-dist/doc/aleph/base} +and \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph}. The +\LaTeX-based format for Aleph is named \textsf{lamed}. + +\item The latest \LaTeX\ release has a new version of the +\acro{LPPL}\Dash now officially a Debian-approved license. Assorted +other updates, see the \filename{ltnews} files in +\OnCD{texmf-dist/doc/latex/base}. + +\item \cmdname{dvipng}, a new program for converting \acro{DVI} to +\acro{PNG} image files, is included. See \OnCD{texmf/doc/man/man1/dvipng.1}. + +\item We reduced the \pkgname{cbgreek} package to a ``medium'' sized set +of fonts, with the assent and advice of the author (Claudio Beccari). +The excised fonts are the invisible, outline, and transparency ones, +which are relatively rarely used, and we needed the space. The full set +is of course available from \acro{CTAN} +(\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). + +\item \cmdname{oxdvi} has been removed; just use \cmdname{xdvi}. + +\item The \cmdname{ini} and \cmdname{vir} commands (links) for +\cmdname{tex}, \cmdname{mf}, and \cmdname{mpost} are no longer created, +such as \cmdname{initex}. The \cmdname{ini} functionality has been +available through the command-line option \optname{-ini} for years now. + +\item \textsf{i386-openbsd} platform support was removed. Since the +\pkgname{tetex} package in the \acro{BSD} Ports system is available, and +\acro{GNU/}Linux and Free\acro{BSD} binaries were available, it seemed +volunteer time could be better spent elsewhere. + +\item On \textsf{sparc-solaris} (at least), you may have to set the +\envname{LD\_LIBRARY\_PATH} environment variable to run the +\pkgname{t1utils} programs. This is because they are compiled with C++, +and there is no standard location for the runtime libraries. (This is +not new in 2004, but wasn't previously documented.) Similarly, on +\textsf{mips-irix}, the \acro{MIPS}pro 7.4 runtimes are required. + +\end{itemize} + +\subsubsection{2005} + +2005 saw the usual huge number of updates to packages and programs. +The infrastructure stayed relatively stable from 2004, but inevitably +there were some changes there as well: + +\begin{itemize} + +\item New scripts \cmdname{texconfig-sys}, \cmdname{updmap-sys}, and + \cmdname{fmtutil-sys} were introduced, which modify the + configuration in the system trees. The \cmdname{texconfig}, + \cmdname{updmap}, and \cmdname{fmtutil} scripts now modify + user-specific files, under \dirname{$HOME/.texlive2005}. + See section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig}. + +\item Corresponding new variables \envname{TEXMFCONFIG} and + \envname{TEXMFSYSCONFIG} to specify the trees where configuration + files (user or system, respectively) are found. Thus, you may + need to move personal versions of \filename{fmtutil.cnf} and + \filename{updmap.cfg} to these places; another option is to + redefine \envname{TEXMFCONFIG} or \envname{TEXMFSYSCONFIG} in + \filename{texmf.cnf}. In any case the real location of these files + and the values of \envname{TEXMFCONFIG} and \envname{TEXMFSYSCONFIG} + must agree. + See section~\ref{sec:texmftrees}, \p.\pageref{sec:texmftrees}. + +\item Last year, we kept \verb|\pdfoutput| and other primitives undefined + for DVI output, even though the \cmdname{pdfetex} program was + being used. This year, as promised, we undid that compatibility + measure. So if your document uses \verb|\ifx\pdfoutput\undefined| + to test if PDF is being output, it will need to be changed. You + can use the package \pkgname{ifpdf.sty} (which works under both + plain \TeX\ and \LaTeX) to do this, or steal its logic. + +\item Last year, we changed most formats to output (8-bit) characters as + themselves (see previous section). The new TCX file + \filename{empty.tcx} now provides an easier way to get the + original \verb|^^| notation if you so desire, as in: +\begin{verbatim} +latex --translate-file=empty.tcx yourfile.tex +\end{verbatim} + +\item The new program \cmdname{dvipdfmx} is included for translation of + DVI to PDF; this is an actively maintained update of + \cmdname{dvipdfm} (which is also still available for now, though + no longer recommended). + +\item The new programs \cmdname{pdfopen} and \cmdname{pdfclose} are included + to allow reloading of pdf files in the Adobe Acrobat Reader without + restarting the program. (Other pdf readers, notably \cmdname{xpdf}, + \cmdname{gv}, and \cmdname{gsview}, have never suffered from this + problem.) + +\item For consistency, the variables \envname{HOMETEXMF} and + \envname{VARTEXMF} have been renamed to \envname{TEXMFHOME} and + \envname{TEXMFSYSVAR}, respectively. There is also + \envname{TEXMFVAR}, which is by default user-specific. See the + first point above. + +\end{itemize} + + +\subsection{Present} +\label{tlcurrent} + +In 2006--2007, the major new addition to \TL{} was the Xe\TeX{} program, +available as the \texttt{xetex} and \texttt{xelatex} programs; see +\url{http://scripts.sil.org/xetex}. + +MetaPost also received a notable update, with more planned for the +future (\url{http://tug.org/metapost/articles}), likewise pdf\TeX{} +(\url{http://tug.org/applications/pdftex}) + +The \TeX\ \filename{.fmt} (high-speed format) and the similar files for +MetaPost and \MF\ are now stored in subdirectories of \dirname{texmf/web2c}, +instead of in the directory itself (although the directory is still +searched, for the sake of existing \filename{.fmt}'s). The +subdirectories are named for the `engine' in use, such as \filename{tex} +or \filename{pdftex} or \filename{xetex}. This change should be +invisible in normal use. + +The (plain) \texttt{tex} program no longer reads \texttt{\%\&} first +lines to determine what format to run; it is the pure Knuthian \TeX. +(\LaTeX\ and everything else do still read \texttt{\%\&} lines). + +The installation scripts now accept various environment variables to +allow for non-interactive installation; see +section~\ref{sec:noninteractive-install}. + +Of course the year also saw (the usual) hundreds of other updates to +packages and programs. As usual, please check \acro{CTAN} +(\url{http://www.ctan.org}) for updates. + +Internally, the source tree is now stored in Subversion, with a standard +web interface for viewing the tree, as linked from our home page. +Although not visible in the final distribution, we expect this will +provide a stable development foundation for future years. + +Finally, in May 2006 Thomas Esser announced that he would no longer be +updating te\TeX{} (\url{http://tug.org/tetex}). As a result, there was +been a surge of interest in \TL{}, especially among \acro{GNU}/Linux +distributors. (There is a new \texttt{tetex} installation scheme in +\TL{}, which provides an approximate equivalent.) We hope this will +eventually translate to improvements in the \TeX\ environment for +everyone. + + +\subsection{Future} + +\emph{\TL{} is not perfect!} (And never will be.) We intend to +continue to release new versions, and would like to provide more +help material, more utilities, more installation programs, and (of +course) an ever-improved and checked tree of macros and fonts. This work +is all done by hard-pressed volunteers in their limited spare time, and +a great deal remains to be done. If you can help, don't hesitate to put +your name forward! + +Please send corrections, suggestions, and offers of help to:\hfill\null +\begin{quote} +\email{tex-live@tug.org} \\ +\url{http://tug.org/texlive} +\end{quote} + +\medskip +\noindent \textsl{Happy \TeX ing!} + +\end{document} diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/live-2008.tex b/Master/texmf/doc/texlive/source/texlive-en/archive/live-2008.tex new file mode 100644 index 00000000000..a172d5f409e --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/live-2008.tex @@ -0,0 +1,2951 @@ +% $Id: live.tex 9531 2008-07-13 21:12:58Z siepo $ +% TeX Live documentation. Originally written by Sebastian Rahtz and +% Michel Goossens, now maintained by Karl Berry and others. +% Public domain. +% +\documentclass{article} +\let\tldocenglish=1 % for live4ht.cfg +\usepackage{tex-live} +\usepackage[latin1]{inputenc} % translators: use your preferred encodings. +\usepackage[T1]{fontenc} + +\begin{document} + +\title{% + {\huge \textit{The \TeX\ Live Guide}\\\smallskip}% + {\LARGE \textsf{\TL{} 2008}}% +} + +\author{Karl Berry, editor \\[3mm] + \url{http://tug.org/texlive/} + } + +\date{August 2008} + +\maketitle + +\begin{multicols}{2} +\tableofcontents +%\listoftables +\end{multicols} + +\section{Introduction} +\label{sec:intro} + +\subsection{\TeX\ Live and the \TeX\ Collection} + +This document describes the main features of the \TL{} software +distribution\Dash \TeX{} and related programs for \GNU/Linux +and other Unix flavors, \MacOSX, and Windows systems. + +You may have acquired \TL{} by downloading, or on the \TK{} \DVD, +which \TeX{} usergroups distribute among their members. Section +\ref{sec:tl-coll-dists} briefly describes the contents of this \DVD. +Both \TL{} and the \TK{} are cooperative efforts by the \TeX{} user +groups. This document mainly describes \TL{} itself. + +\TL{} includes executables for \TeX{}, \LaTeXe{}, \ConTeXt, +\MF, \MP, \BibTeX{} and many other programs; an extensive collection +of macros, fonts and documentation; and support for typesetting in +many different scripts from around the world. + +\TL{} packages are regularly updated from +\acro{CTAN}: \url{http://www.ctan.org}. + +For a brief summary of the major changes in this edition of \TL{}, +see the end of the document, section~\ref{sec:history} +(\p.\pageref{sec:history}). + +\subsection{Operating system support} +\label{sec:os-support} + +\TL{} contains binaries for many Unix-based architectures, +including \MacOSX. The included sources should enable installation +on platforms for which we do not have binaries. + +As to Windows: only Windows 2000 and later are supported. Windows +9\textit{x}, ME and NT have been dropped. Because of this +change, Windows requires much less special treatment compared to +the Unix systems. There are no 64-bit executables for Windows, but the +32-bit executables should run on 64-bit systems. + +See section~\ref{sec:tl-coll-dists} for alternate solutions +for Windows and \MacOSX. + +\subsection{Basic installation of \protect\TL{}} +\label{sec:basic} + +You can install \TL{} either from \DVD{} or over the Internet. The net +installer itself is small, and downloads everything requested from the +Internet. The net installer is an attractive option if you need only a +fraction of the complete \TL. + +The \DVD{} installer lets you install to a local disk, but you can +also run \TL{} directly from the \DVD{} (or from a \DVD{} image, if +your system supports that). + +\noindent This is described in the +installation sections following, but here is a quick start: + +\begin{itemize*} + +\item The installation script is named \filename{install-tl}. It can + operate in both a \GUI{} mode (default for Windows) and + a text mode (default for everything else). You can force one mode or + the other with the options \code{-gui} and \code{-no-gui}, respectively. + +\item One of the installed items is a new program, the `\TL\ Manager', + named \prog{tlmgr}. Like the installer, it can be used in both \GUI{} + mode and in text mode. You can use it to install and uninstall + packages and do various configuration tasks. + +\end{itemize*} + + +\subsection{Getting help} +\label{sec:help} + +The \TeX{} community is both active and friendly, and most serious +questions end up getting answered. However, the support is informal, +done by volunteers and casual readers, so it's especially important that +you do your homework before asking. (If you prefer guaranteed +commercial support, you can forego \TL{} completely and purchase a +vendor's system; \url{http://tug.org/interest.html#vendors} has a list.) + +Here is a list of resources, approximately in the order we recommend +using them: + +\begin{description} +\item [Getting Started] If you are new to \TeX, the web page +\url{http://tug.org/begin.html} gives a brief introduction to the system. + +\item [\TeX{} \acro{FAQ}] The \TeX{} \acro{FAQ} is a huge compendium + of answers to all sorts of questions, from the most basic to the + most arcane. It is included on \TL{} in + \OnCD{texmf-doc/doc/english/FAQ-en/html/index.html}, and is available + on the Internet through \url{http://www.tex.ac.uk/faq}. Please + check here first. + +\item [\TeX{} Catalogue] If you are looking for a specific package, +font, program, etc., the \TeX{} Catalogue is the place to look. It is a +huge collection of all \TeX{}-related items. See +\url{http://www.ctan.org/help/Catalogue/}. + +\item [\TeX{} Web Resources] The web page +\url{http://tug.org/interest.html} has many \TeX{}-related links, in +particular for numerous books, manuals, and articles on all aspects of +the system. + +\item [support archives] The two principal support forums are the +Usenet newsgroup \url{news:comp.text.tex} and the mailing list +\email{texhax@tug.org}. Their archives have years of past +questions and answers for your searching pleasure, via +\url{http://groups.google.com/group/comp.text.tex/topics} and +\url{http://tug.org/mail-archives/texhax}, respectively. And a general web +search, for example on \url{http://google.com}, never hurts. + +\item [asking questions] If you cannot find an answer, you can post to +\dirname{comp.text.tex} through Google or your newsreader, or to +\email{texhax@tug.org} through email. But before you post, +\emph{please} read this \acro{FAQ} entry, to maximize +your chances of getting a useful answer: +\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. + +\item [\TL{} support] If you want to report a bug or have +suggestions or comments on the \TL{} distribution, installation, or +documentation, the mailing list is \email{tex-live@tug.org}. However, +if your question is about how to use a particular program included in +\TL{}, please write to that program's maintainer or +mailing list. Often running a program with the \code{-{}-help} option +will provide a bug reporting address. + +\end{description} + +The other side of the coin is helping others who have questions. Both +\dirname{comp.text.tex} and \code{texhax} are open to anyone, so feel +free to join, start reading, and help out where you can. + + +% don't use \TL so the \uppercase in the headline works. Also so +% tex4ht ends up with the right TeX. Likewise the \protect's. +\section{Overview of \protect\TeX\protect\ Live} +\label{sec:overview-tl} + +This section describes the contents of \TL{} and the \TK{} of which it +is a part. + +\subsection{The \protect\TeX\protect\ Collection: \TL, pro\TeX{}t, Mac\TeX} +\label{sec:tl-coll-dists} + +The \TK{} \DVD{} comprises the following: + +\begin{description} + +\item [\TL] A complete \TeX{} system which can be run live or + installed to disk. + +\item [Mac\TeX] for \MacOSX, this adds a native \MacOSX\ installer and other +Mac applications to \TL{}. Its home page is +\url{http://www.tug.org/mactex/}. + +\item [pro\TeX{}t] An enhancement of the \MIKTEX\ distribution for Windows, +\ProTeXt\ adds a few extra tools to \MIKTEX, and simplifies +installation. It is entirely independent of \TL{}, and has its own +installation instructions. The \ProTeXt\ home page is +\url{http://tug.org/protext}. + +\item [CTAN] A snapshot of the \CTAN{} repository. + +\item [\texttt{texmf-extra}] A directory with assorted additional packages. + +\end{description} + +\CTAN{}, \pkgname{protext}, and \dirname{texmf-extra} do not +necessarily follow the same copying conditions as \TL{}, so be careful +when redistributing or modifying. + + +\subsection{Top level \TL{} directories} +\label{sec:tld} + +Here is a brief listing and description of the top level directories in +the \TL{} distribution. On the \pkgname{live} \DVD, the entire \TL{} +hierarchy is in a subdirectory \dirname{texlive}, not at the top +level of the disc. + +\begin{ttdescription} +\item[bin] The \TeX{} system programs, arranged by platform. +% +\item[readme.html] Web pages with a quick introduction and useful links, +in various languages. +% +\item[source] The source to all included programs, including the main \Webc{} + \TeX{} and \MF{} distributions. +% +\item[support] Various auxiliary packages and programs. These are + \emph{not} installed automatically. This includes + assorted editors and \TeX\ shells. +% +\item[texmf] See \dirname{TEXMFMAIN} below. +% +\item[texmf-dist] See \dirname{TEXMFDIST} below. +% +\item[texmf-doc] Tree for self-contained pure documentation, arranged by + language. +% +\item[tlpkg] Scripts, programs and data for managing the + installation. It also contains private copies of + Perl and Ghostscript for Windows, which are invisible outside \TL, + and a new Windows PostScript viewer PSView. +\end{ttdescription} + +In addition to the directories above, the installation scripts and +\filename{README} files (in various languages) are at the top level of +the distribution. + +The \dirname{texmf-doc} directory contains documentation which does +not belong to any particular package or program. The documentation +for the programs (manuals, man pages, Info files) is in +\dirname{texmf/doc}. The documentation for \TeX\ packages and +formats is in \dirname{texmf-dist/doc}. You can use the +\cmdname{texdoc} or \cmdname{texdoctk} programs to find any +documentation wherever it is located. The comprehensive links in +the top-level file \OnCD{doc.html} may also be helpful. + +This \TL\ documentation itself is in \dirname{texmf-doc} and is +available in several languages: + +\begin{itemize*} +\item{Simplified Chinese:} \OnCD{texmf-doc/doc/chinese/texlive-zh-cn} +\item{Czech/Slovak:} \OnCD{texmf-doc/doc/czechslovak/texlive-cz} +\item{English:} \OnCD{texmf-doc/doc/english/texlive-en} +\item{French:} \OnCD{texmf-doc/doc/french/texlive-fr} +\item{German:} \OnCD{texmf-doc/doc/german/texlive-de} +\item{Polish:} \OnCD{texmf-doc/doc/polish/texlive-pl} +\item{Russian:} \OnCD{texmf-doc/doc/russian/texlive-ru} +\end{itemize*} + +\subsection{Overview of the predefined texmf trees} +\label{sec:texmftrees} + +This section lists all predefined variables specifying the texmf trees +used by the system, and their intended purpose, and the default +layout of a \TL{} system. The command \texttt{texconfig conf} shows +you the values of these variables, so that you can easily find out +how they map to directory names in your installation. + +\begin{ttdescription} +\item [TEXMFMAIN] The tree which holds vital parts of the system + such as helper scripts (e.g., \verb+web2c/mktexdir+) and other + support files and their documentation. Does not include + \TeX\ formats and packages. +\item [TEXMFDIST] The tree which holds the main set of macro packages, + fonts, etc., as originally distributed. +\item [TEXMFLOCAL] The tree which administrators can use for system-wide + installation of additional or updated macros, fonts, etc. +\item [TEXMFHOME] The tree which users can use for their own individual + installations of additional or updated macros, fonts, etc. + The expansion of this variable dynamically adjusts for each user to + their own individual directory. +\item [TEXMFCONFIG] The tree used by the utilities + \verb+texconfig+, \verb+updmap+, and \verb+fmtutil+ to store modified + configuration data. Under \envname{TEXMFHOME} by default. +\item [TEXMFSYSCONFIG] The tree used by the utilities + \verb+texconfig-sys+, \verb+updmap-sys+, and \verb+fmtutil-sys+ to + store modified configuration data. +\item [TEXMFVAR] The tree used by \verb+texconfig+, \verb+updmap+ and + \verb+fmtutil+ to store (cached) runtime data such as format files and + generated map files. Under \envname{TEXMFHOME} by default. +\item [TEXMFSYSVAR] The tree used by \verb+texconfig-sys+, + \verb+updmap-sys+ and \verb+fmtutil-sys+, and also by \verb+tlmgr+, to + store (cached) runtime data such as format files and generated map files. +\end{ttdescription} + +\noindent +The default layout is: +\begin{description} + \item[system-wide root] can span multiple \TL{} releases: + \begin{ttdescription} + \item[2007] A previous release. + \begin{ttdescription} + \item [...] + \end{ttdescription} + \item[2008] The current release. + \begin{ttdescription} + \item [bin] ~ + \begin{ttdescription} + \item [i386-linux] \GNU/Linux binaries + \item [...] + \item [universal-darwin] \MacOSX binaries + \item [win32] Windows binaries + \end{ttdescription} + \item [texmf] This is \envname{TEXMFMAIN}. + \item [texmf-dist] \envname{TEXMFDIST} + \item [texmf-doc] \envname{TEXMFDOC} + \item [texmf-var] \envname{TEXMFSYSVAR} + \item [texmf-config] \envname{TEXMFSYSCONFIG} + \end{ttdescription} + \item [texmf-local] \envname{TEXMFLOCAL}, intended to be + retained from release to release. + \end{ttdescription} + \item[user's home] (\texttt{\$HOME} or + \texttt{\%USERPROFILE\%}) + \begin{ttdescription} + \item[.texlive2007] Privately generated and configuration data + for a previous release. + \item[.texlive2008] Privately generated and configuration data + for the current release. + \begin{ttdescription} + \item [texmf-var] \envname{TEXMFVAR} + \item [texmf-config] \envname{TEXMFCONFIG} + \end{ttdescription} + \item[texmf] \envname{TEXMFHOME} Personal macros. + \textit{etc.} + \end{ttdescription} +\end{description} + + +\subsection{Extensions to \protect\TeX} +\label{sec:tex-extensions} + +\TeX{} itself is frozen, apart from rare bug fixes. It is still present +in \TL\ as the program \prog{tex}, and will remain so in the +foreseeable future. \TL{} contains several extended versions of \TeX: + +\begin{description} + +\item [\eTeX] adds a set of new primitives +\label{text:etex} (related to macro expansion, character scanning, +classes of marks, additional debugging features, and more) and the +\TeXXeT{} extensions for bidirectional typesetting. In default mode, +\eTeX{} is 100\% compatible with ordinary \TeX. See +\OnCD{texmf-dist/doc/etex/base/etex_man.pdf}. + +\item [pdf\TeX] builds on the \eTeX\ extensions, adding support for +writing \acro{PDF} output as well as \dvi{}. This is the program +invoked for most formats, e.g., \prog{etex}, \prog{latex}, +\prog{pdflatex}. See \url{http://www.pdftex.org/}. +\OnCD{texmf-dist/doc/pdftex/manual/pdftex-a.pdf} for the manual, and +\OnCD{texmf-dist/doc/pdftex/manual/samplepdf/samplepdf.tex} for example usage +of some of its features. + +\item [Lua\TeX] is the designated successor of pdf\TeX, with which it +is intended to be backward-compatible. It should also supersede Aleph, +see below. The incorporated Lua interpreter (see +\url{http://www.lua.org/}) enables elegant solutions for many thorny +\TeX{} problems. When called as \filename{texlua}, it functions as a +standalone Lua interpreter, and is already used as such within \TL. See +\url{http://www.luatex.org/} and +\OnCD{texmf-dist/doc/luatex/luatexref-t.pdf}. + +\item [\XeTeX] adds support for Unicode input and OpenType- and system +fonts, implemented using standard third-party libraries. See +\url{http://scripts.sil.org/xetex}. + +\item [\OMEGA\ (Omega)] is based on Unicode (16-bit characters), thus +supports working with almost all the world's scripts simultaneously. It +also supports so-called `\OMEGA{} Translation Processes' (\acro{OTP}s), +for performing complex transformations on arbitrary input. See +\OnCD{texmf-dist/doc/omega/base/doc-1.8.tex} (not completely up-to-date). + +\item [Aleph] combines the \OMEGA\ and \eTeX\ extensions. +See \OnCD{texmf-dist/doc/aleph/base} for some minimal documentation. + +\end{description} + + +\subsection{Other notable programs in \protect\TL} + +Here are a few other commonly-used programs included in \TL{}: + +\begin{cmddescription} + +\item [bibtex] bibliography support. + +\item [makeindex] index support. + +\item [dvips] convert \dvi{} to \PS{}. + +\item [xdvi] \dvi{} previewer for the X Window System. + +\item [dvilj] \dvi{} drive for the HP LaserJet family. + +\item [dv2dt, dt2dv] convert \dvi{} to/from plain text. + +\item [dviconcat, dviselect] cut and paste pages +from \dvi{} files. + +\item [dvipdfmx] convert \dvi{} to \acro{PDF}, an alternative approach +to pdf\TeX\ (mentioned above). See the \pkgname{ps4pdf} and +\pkgname{pdftricks} packages for still more alternatives. + +\item [psselect, psnup, \ldots] \PS{} +utilities. + +\item [lacheck] \LaTeX{} syntax checker. + +\item [texexec, texmfstart] Con\TeX{}t and \acro{PDF} processor. + +\item [tex4ht] \TeX{} to \acro{HTML} (and \acro{XML} and more) converter. + +\end{cmddescription} + + +\subsection{Fonts in \protect\TL} +\label{sec:tl-fonts} + +\TL{} comes with many high-quality scalable fonts. See +\url{http://tug.org/fonts} and +\OnCD{texmf-doc/doc/english/free-math-font-survey}. + + + +\section{Installation} +\label{sec:install} + +\subsection{Starting the installer} +\label{sec:inst-start} + +To start with, get the \TK{} \DVD{} or download the \TL{} net installer, +and locate the installer script: \filename{install-tl} for Unix, +\filename{install-tl.bat} for Windows. + +\begin{description} +\item [Net installer:] Download from \CTAN, under +\dirname{systems/texlive/tlnet}; the url +\url{http://mirror.ctan.org/systems/texlive/tlnet} will automatically +redirect to a nearby, up-to-date, mirror. You can retrieve either +\filename{install-tl.zip} which can be used under Unix and Windows and +\filename{install-unx.tar.gz} which is considerably smaller, for Unix +only. After unpacking, \filename{install-tl} and +\filename{install-tl.bat} will be in the \dirname{install-tl} +subdirectory. + +\item [\TeX{} Collection \DVD:] go to its \dirname{texlive} +subdirectory. Under Windows, the installer should start automatically +when you insert the \DVD. You can get the \DVD\ by becoming a member of +a \TeX\ user group (highly recommended, +\url{http://tug.org/usergroups.html}), or purchasing it separately +(\url{http://tug.org/store}), or burning your own from the \ISO\ +image (\url{http://tug.org/texlive/acquire.html}). + +\end{description} +The following sections explain in more detail. + +\subsubsection{Unix} + +\begin{figure}[tb] +\begin{boxedverbatim} +======================> TeX Live installation procedure <===================== + +=======> Note: Letters/digits in indicate menu items <======= +=======> for commands or configurable options <======= + + + Detected platform: Intel x86 with GNU/Linux + + binary systems: 1 out of 16 + + Installation scheme (scheme-full) + + Customizing installation scheme: + standard collections + language collections + 83 collections out of 84, disk space required: 1666 MB + + directories: + TEXDIR (the main TeX directory): + !! default location: /usr/local/texlive/2008 + !! is not writable, please select a different one! + TEXMFLOCAL (directory for site-wide local files): + /usr/local/texlive/texmf-local + TEXMFSYSVAR (directory for variable and automatically generated data): + /usr/local/texlive/2008/texmf-var + TEXMFSYSCONFIG (directory for local config): + /usr/local/texlive/2008/texmf-config + TEXMFHOME (directory for user-specific files): + ~/texmf + + options: + [ ] use letter size instead of A4 by default + [X] create all format files + [X] install macro/font doc tree + [X] install macro/font source tree + [ ] create symlinks in standard directories + + Install for running from DVD + +Other actions: + start installation to HD + help + quit + +Enter command: +\end{boxedverbatim} +\caption{Main text installer screen (\GNU/Linux)}\label{fig:text-main} +\end{figure} + +\begin{figure}[tb] +\tlpng{install-w32-main}{\linewidth} +\caption{Main \GUI{} installer screen (Windows)}\label{fig:gui-main} +\end{figure} + +\noindent +Below, \texttt{>} denotes the shell prompt; user input is +\Ucom{\texttt{bold}}. +Starting in a terminal window on a Unix-compatible system, the simplest +way: +\begin{alltt} +> \Ucom{cd /path/to/installer} +> \Ucom{perl install-tl} +\end{alltt} +(Or you can invoke \Ucom{perl /path/to/installer/install-tl}, or +\Ucom{./install-tl} if it stayed executable, etc.; we won't repeat all +these variations.) + +To install in \GUI\ mode (you'll need the \dirname{Perl/TK} module), use: +\begin{alltt} +> \Ucom{perl install-tl -gui} +\end{alltt} + +For a complete listing of the various options: +\begin{alltt} +> \Ucom{perl install-tl -help} +\end{alltt} + +\textbf{Warning about Unix permissions:} Your \code{umask} at the time +of installation will be respected by the \TL{} installer. Therefore, if +you want your installation to be usable by users other than you, make +sure your setting is sufficiently permissive, for instance, \code{umask +002}. For more information about \code{umask}, consult your system +documentation. + + +\subsubsection{Mac\,OS\,X} + +As mentioned in section~\ref{sec:tl-coll-dists}, a separate distribution +is prepared for \MacOSX, named Mac\TeX\ (\url{http://tug.org/mactex}). +We recommend using the native Mac\TeX\ installer instead of the \TL\ +installer on \MacOSX, because the native installer can make a few +Mac-specific adjustments, in particular to allow easily switching +between the various \TeX\ distributions for \MacOSX\ (Mac\TeX, gw\TeX, +Fink, MacPorts, \ldots). + +Mac\TeX\ is firmly based on \TL, and the main \TeX\ trees are precisely +the same. It does add a few extra folders with Mac-specific +documentation and applications. + + +\subsubsection{Windows} + +If you are using the net installer, or the \DVD\ installer failed to +start automatically, double-click \filename{install-tl.bat}. + +You can also start the installer from the command-prompt. Below, +\texttt{>} denotes the prompt; user input is \Ucom{\texttt{bold}}. If +you are in the installer directory, run just: +\begin{alltt} +> \Ucom{install-tl} +\end{alltt} + +Or you can invoke it with an absolute location, such as: +\begin{alltt} +> \Ucom{D:\bs{}texlive\bs{}install-tl} +\end{alltt} +for the \TK\ \DVD, supposing that \dirname{D:} is the optical drive. + +To install in text mode, use: +\begin{alltt} +> \Ucom{install-tl -no-gui} +\end{alltt} + +For a complete listing of the various options: +\begin{alltt} +> \Ucom{install-tl -help} +\end{alltt} + +\subsubsection{The text installer} + +Figure~\ref{fig:text-main} displays the main text mode screen under +Unix. + +This is only a command-line installer; there is no cursor support at +all. For instance, you cannot tab around checkboxes or input fields. +You just type something (case-sensitive) at the prompt and press the +Enter key, and then the entire terminal screen will be rewritten, with +adjusted content. + +The text installer interface is this primitive for a reason: it +is designed to run on as many platforms as possible, even with a +very barebones Perl (for Windows, a Perl subset is included). + +\subsubsection{The graphical installer} + +Figure~\ref{fig:gui-main} displays the graphical installer under +Windows. Most differences in available options are due to this +screenshot being from Windows, and the previous text screen being +from \GNU/Linux. + +\subsection{Running the installer} +\label{sec:runinstall} + +The installer is intended to be mostly self-explanatory. Still, a few +quick notes about the various options and submenus: + +\subsubsection{Binary systems menu (Unix only)} +\label{sec:binary} + +\begin{figure}[tbh] +\begin{boxedverbatim} +Available sets of binaries: +=============================================================================== + + a [ ] alpha-linux DEC Alpha with GNU/Linux + b [ ] amd64-freebsd x86_64 with FreeBSD + c [ ] hppa-hpux HP-UX + d [ ] i386-freebsd Intel x86 with FreeBSD + e [X] i386-linux Intel x86 with GNU/Linux + f [ ] i386-openbsd Intel x86 with OpenBSD + g [ ] i386-solaris Intel x86 with Sun Solaris + h [ ] mips-irix SGI IRIX + i [ ] powerpc-aix PowerPC with AIX + j [ ] powerpc-linux PowerPC with GNU/Linux + k [ ] sparc-linux Sparc with GNU/Linux + l [ ] sparc-solaris Sparc with Solaris + m [ ] universal-darwin universal binaries for MacOSX/Darwin + o [ ] win32 Windows + p [ ] x86_64-linux x86_64 with GNU/Linux +\end{boxedverbatim} +\caption{Binaries menu}\label{fig:bin-text} +\end{figure} + +Figure~\ref{fig:bin-text} displays the text mode binaries menu. By +default, only the binaries for your current platform will be installed. +From this menu, you can select installation of binaries for other +architectures as well. This can be useful if you are sharing a \TeX\ +tree across a network of heterogenous machines, or for a dual-boot +system. + +\subsubsection{Selecting what is going to be installed} +\label{sec:components} + +\begin{figure}[tbh] +\begin{boxedverbatim} +Select a scheme: +=============================================================================== + + a [ ] TeX Live basic scheme + b [ ] TeX Live scheme for ConTeXt + c [X] TeX Live full scheme + d [ ] GUST TeX Live scheme + e [ ] GUTenberg TeX Live scheme + f [ ] TeX Live medium scheme + g [ ] TeX Live minimal scheme + h [ ] TeX Live for Omega users + i [ ] teTeX scheme + j [ ] XML typesetting scheme +\end{boxedverbatim} +\caption{Scheme menu}\label{fig:scheme-text} +\end{figure} + +Figure~\ref{fig:scheme-text} displays the \TL\ scheme menu; from here, +you choose a ``scheme'', which is an overall set of package collections. +The default \optname{full} scheme installs everything available, but you +can also choose the \optname{basic} scheme for a small system, +\optname{minimal} for testing purposes, and \optname{medium} or +\optname{teTeX} to get something in between. There are also various +specialized and country-specific schemes. + +\begin{figure}[tbh] +\tlpng{stdcoll}{.7\linewidth} +\caption{Collections menu (Linux)}\label{fig:collections-gui} +\end{figure} + +You can refine your scheme selection with the `standard collections' and +`language collections' menus (figure~\ref{fig:collections-gui}, shown in +\GUI\ mode for a change). + +Collections are one level more detailed than schemes\Dash in essence, a +scheme consists of several collections, a collection consists of one or +more packages, and a package (the lowest level grouping in \TL) contains +the actual \TeX\ macro files, font files, and so on. + +If you want more control than the collection menus provide, you can use +the \prog{tlmgr} program after installation (see +section~\ref{sec:tlmgr}); using that, you can control the installation +at the package level. + +\subsubsection{Directories} +\label{sec:directories} + +The default layout is described in section~\ref{sec:texmftrees}, +\p.\pageref{sec:texmftrees}. The default location of +\dirname{TEXDIR} is different between Windows +(|%PROGRAMFILES%\texlive\2008|) and Unix +(\dirname{/usr/local/texlive/2008}). + +The main reason to change this default is if you lack write permission +for the default location. You don't have to be root or adminstrator to +install \TL, but you do need write access to the target directory. + +A logical alternate choice is a directory under your home directory, +especially if you will be the sole user. Use +`|~|' to indicate this, as in `|~/texlive/2008|'. + +We recommend including the year in the name, to enable keeping different +releases of \TL{} side by side. (You may wish to make a +version-independent name such as \dirname{/usr/local/texlive-cur} via a +symbolic link, which you can then update after testing the new release.) + +Changing \dirname{TEXDIR} in the installer will also change +\dirname{TEXMFLOCAL}, \dirname{TEXMFSYSVAR} and +\dirname{TEXMFSYSCONFIG}. + +\dirname{TEXMFHOME} is the recommended location for personal +macro files or packages. The default value is |~/texmf|. In +contrast to \dirname{TEXDIR}, here a |~| is preserved in the +newly-written configuration files, since it usefully refers to the home +directory of each individual running \TeX. It expands to +\dirname{$HOME} on Unix and \verb|%USERPROFILE%| on Windows. + +\subsubsection{Options} +\label{sec:options} + +\begin{figure}[tbh] +\begin{boxedverbatim} +

use letter size instead of A4 by default: [ ] + create all format files: [X] + install font/macro doc tree: [X] + install font/macro source tree: [X] + create symlinks in standard directories: [ ] + binaries to: + manpages to: + info to: +\end{boxedverbatim} +\caption{Options menu (Unix)}\label{fig:options-text} +\end{figure} + +Figure~\ref{fig:options-text} displays the text mode options menu. +Three of the options here need mentioning: + +\begin{description} +\item[use letter size instead of A4 by default:] The usual default paper + size selection. Of course, individual documents can specify a specific + paper size, if desired. + +\item[create all format files:] Although unnecessary format files + take time to generate and disk space to store, it is still recommended + to leave this option checked: if you don't, then format files will be + generated in people's private \dirname{TEXMFVAR} tree as they are + needed. In that location, they will not be updated automatically if + (say) binaries or hyphenation patterns are updated in the + installation, and thus could end up with incompatible format files. + +\item[create symlinks in standard directories] (Unix only): + This option bypasses the need to change environment + variables. Without this option, \TL{} directories have to be added + to \envname{PATH}, \envname{MANPATH} and \envname{INFOPATH}. You will + need write permissions to the target directories. It is not + advisable to overwrite a \TeX\ system that came with your system + with this option. It is intended primarily for creating the links + in standard directories that are known to users, such as + \dirname{/usr/local/bin}, which don't already contain any + \TeX\ files. +\end{description} + +Now when all these settings are to your liking, you can type `I' to +start the installation process. When it is done, skip to +section~\ref{sec:postinstall} to read what else needs to be done, if +anything. + +\subsubsection{Set up for running from DVD{} (text mode only)} +\label{sec:fromdvd} + +Type `|V|' to select this option. This changes the main menu into something +like figure~\ref{fig:main-fromdvd}. +\begin{figure}[tbh] +\begin{boxedverbatim} +======================> TeX Live installation procedure <===================== + +=======> Note: Letters/digits in indicate menu items <======= +=======> for commands or configurable options <======= + + directories: + TEXDIRW (Writable root): + !! default location: /usr/local/texlive/2008 + !! is not writable, please select a different one! + TEXMFLOCAL (directory for site-wide local files): + /usr/local/texlive/texmf-local + TEXMFSYSVAR (directory for variable and automatically generated data): + /usr/local/texlive/2008/texmf-var + TEXMFSYSCONFIG (directory for local config): + /usr/local/texlive/2008/texmf-config + TEXMFHOME (directory for user-specific files): + ~/texmf + + options: + [ ] use letter size instead of A4 by default + [X] create all format files + + set up for installing to hard disk + +Other actions: + start installation for running from DVD + help + quit +\end{boxedverbatim} +\caption{The main menu with \optname{from DVD} + set}\label{fig:main-fromdvd} +\end{figure} + +Note the changes: all options about what to install have +disappeared, and the directories section now talks about +\dirname{TEXDIRW} or writable root. The symlinks option has also +disappeared. + +The installer will still create various directories and +configuration files, but won't copy \dirname{texmf}, +\dirname{texmf-dist} or \dirname{texmf-doc} to hard disk. + +Post-install configuration for Unix will be slightly more complicated, +because now the directory layout deviates from the default; see +section~\ref{sec:postinstall}. + +Due to time constraints, this option didn't make it into the \GUI{} +installer, but it is available both for Unix and for +Windows. Windows users have to start the installer from a command +prompt, see section~\ref{sec:cmdline}. + +Section \ref{sec:portable-unix} describes a more strictly portable +way to run \TL, which doesn't make or require changes in the +system's configuration, but doesn't allow any configuration either. + +\subsection{Command-line install options} +\label{sec:cmdline} + +Type +\begin{alltt} +> \Ucom{install-tl -help} +\end{alltt} +for a listing of command-line options. Either |-| or |--| can be used +to introduce option names. These are the more +interesting ones: + +\begin{ttdescription} +\item[-gui] If possible, use the \GUI{} installer. This requires the + Perl/Tk module (\url{http://tug.org/texlive/distro.html#perltk}); + if Perl/Tk is not available, installation continues in text mode. +\item[-no-gui] Force using the text mode installer, even under + Windows; you'll need this if you want a `from \DVD' installation, + since that is not available in \GUI{} mode. +\item[-lang {\sl LL}] Specify the installer interface + language as its standard two-letter code \textsl{LL}. Currently + supported languages: English (\texttt{en}, default), German + (\texttt{de}), French (\texttt{fr}), Dutch (\texttt{nl}), Polish + (\texttt{pl}), Slovenian (\texttt{sl}) and Vietnamese + (\texttt{vi}). The installer tries to determine the right language + itself but if it fails, or if the right language is not available, + then it uses English as a fallback. +\item[-profile {\sl profile}] The installer always writes a file + \filename{texlive.profile} to the \dirname{2008/tlpkg}- or + \dirname{tlpkg} subdirectory of your installation. This option tells + the installer to re-use such a profile file. Here's an excerpt: + \begin{fverbatim} +# texlive.profile written on Wed Jul 9 16:13:44 2008 UTC +# It will NOT be updated and reflects only the +# installation profile at installation time. +selected_scheme scheme-basic +TEXDIR /usr/local/texlive/2008 +TEXDIRW /usr/local/texlive/2008 +... +TEXMFSYSVAR /usr/local/texlive/2008/texmf-var +collection-basic 1 +... +option_symlinks 0 + \end{fverbatim} + Thus, using this option you can install in batch mode on + subsequent systems, reproducing the choices you made for the + original installation. +\item [-location {\sl url/path}] Specify a non-default source for + packages; see below. +\end{ttdescription} + +\subsubsection{The \optname{location} parameter} +\label{sec:location} + +The location value can be a url starting with \texttt{ftp:}, +\texttt{http:}, or \texttt{file:/} url, or a plain path. If the given +argument is on a local drive (either a path or a \texttt{file:/} url), +the installation type (compressed or live) is automatically determined: +if an \dirname{archive} subdirectory with \filename{.tar.lzma} files is +found then it will be used, even if uncompressed files are available as +well. + +When giving an \texttt{http:} or \texttt{ftp:} location, trailing +`\texttt{/}' characters and/or a trailing `\texttt{/tlpkg}' component +are ignored. For example, you could choose a particular \CTAN\ mirror +with something like: +\url{http://ctan.example.org/tex-archive/texlive/tlnet/2008}, +substituting of course a proper hostname and its particular top-level +\CTAN\ path (the list of \CTAN\ mirrors is maintained at +\url{http://ctan.org/mirrors}) for |ctan.example.org/tex-archive|. The +default is to pick a mirror automatically, using +\url{http://mirror.ctan.org}; in any case, the chosen host is used for +the entire download. + + +\subsection{Post-install actions} +\label{sec:postinstall} + +Some post-install may be required. + +\subsubsection{Windows} + +But on Windows, the installer takes care of everything. + +\subsubsection{If symlinks were created} + +If you elected to create symlinks in standard directories (mentioned in +section~\ref{sec:options}), then there is no need to edit environment +variables. + +\subsubsection{Environment variables for Unix} +\label{sec:env} + +The directory of the binaries for your platform must be added to +the search path. Each supported platform has its own subdirectory +under \dirname{TEXDIR/bin}. See figure~\ref{fig:bin-text} for the +list of subdirectories and corresponding platforms. + +You can also add the documentation man and Info directories to their +respective search paths, if you want the system tools to find them. + +For Bourne-compatible shells such as \prog{bash}, and using Intel x86 +GNU/Linux and a default directory setup as an example, the file to edit +might be \filename{$HOME/.profile} (or another file sourced by +\filename{.profile}, and the lines to add would look like this: + +\begin{sverbatim} +PATH=/usr/local/texlive/2008/bin/i386-linux:$PATH; export PATH +MANPATH=/usr/local/texlive/2008/texmf/doc/man:$MANPATH; export MANPATH +INFOPATH=/usr/local/texlive/2008/texmf/doc/info:$INFOPATH; export INFOPATH +\end{sverbatim} + +For csh or tcsh, the file to edit is typically \filename{$HOME/.cshrc}, and +the lines to add might look like: + +\begin{sverbatim} +setenv PATH /usr/local/texlive/2008/bin/i386-linux:$PATH +setenv MANPATH /usr/local/texlive/2008/texmf/doc/man:$MANPATH +setenv INFOPATH /usr/local/texlive/2008/texmf/doc/info:$INFOPATH +\end{sverbatim} + +Of course, you may well already have settings somewhere in your ``dot'' +files, and so then the \TL\ directories should simply be merged in as +appropriate. + +\subsubsection{Environment variables: global configuration} +\label{sec:envglobal} + +If you want to make these changes globally, or for a user newly added to +the system, then you are on your own; there is just too much variation +between systems in how and where these things are configured. + +Our two hints are: 1)~you may want to check for a file +\filename{/etc/manpath.config} and, if present, add lines such as + +\begin{sverbatim} +MANPATH_MAP /usr/local/texlive/2008/bin/i386-linux \ + /usr/local/texlive/2008/texmf/doc/man +\end{sverbatim} + +And 2)~check for a file \filename{/etc/environment} which may define the +search path and other default environment variables. + + +\subsubsection{When running from DVD} + +Normally, a \TL{} program consults a file \filename{texmf.cnf} for the +location of the various trees. It looks for this file in a series of +locations relative to its own location. However, this scheme breaks down +when a program is run from \DVD{}: the \DVD{} is read-only. Some of the +paths to be recorded in \filename{texmf.cnf} are only known at +installation time, so this file cannot be on the \DVD{} and must be +placed somewhere else. This makes it necessary to define an environment +\envname{TEXMFCNF} variable which tells \TL{} programs in what directory +to find this \filename{texmf.cnf}. It is also still necessary to modify +the \envname{PATH} environment variable, as described before. + +At the end of the installation, the installer should have printed a +message giving the value to which \envname{TEXMFCNF} should be set. In +case you missed it: this value is \dirname{$TEXMFSYSVAR/web2c}. For the +default, \dirname{/usr/local/texlive/2008/texmf-var/web2c}, you need the +lines +\begin{sverbatim} +TEXMFCNF=/usr/local/texlive/2008/texmf-var/web2c; export TEXMFCNF +\end{sverbatim} +or, for [t]csh: +\begin{sverbatim} +setenv TEXMFCNF /usr/local/texlive/2008/texmf-var/web2c +\end{sverbatim} + + +\subsubsection{\ConTeXt{} Mark IV} + +The `old' \ConTeXt{} should run out of the box. The new `Mark IV' +\ConTeXt{} will require manual setup; see +\url{http://wiki.contextgarden.net/Running_Mark_IV}. + + +\subsubsection{Integrating local and personal macros} +\label{sec:local-personal-macros} + +This is already mentioned implicitly in section~\ref{sec:texmftrees}: +\dirname{TEXMFLOCAL} (by default, +\dirname{/usr/local/texlive/texmf-local} or +\verb|C:\Program Files\texlive\texmf-local|) + +is intended for system-wide local fonts and macros; and +\dirname{TEXMFHOME} (by default, \dirname{$HOME/texmf} or +\verb|%USERPROFILE%\texmf|), is for personal fonts and macros. These +directories are intended to stick around from release to release, and +have their content seen automatically by a new \TL{} release. +Therefore, it is best to refrain from changing the definition of +\dirname{TEXMFLOCAL} to be too far away from the main \TL{} directory, +or you will need to manually change future releases. + +For both trees, files should be placed in their proper subdirectories; +see \url{http://tug.org/tds} or consult +\filename{texmf/web2c/texmf.cnf}. For instance, a \LaTeX{} class file or +package should be placed in \dirname{TEXMFLOCAL/tex/latex} or +\dirname{TEXMFHOME/tex/latex}, or a subdirectory thereof. + +\dirname{TEXMFLOCAL} requires an up-to-date filename database, or files +will not be found. You can update it with the command +\cmdname{mktexlsr} or use the `Reinit file database' button on the +configuration tab of \prog{tlmgr} in \GUI\ mode. + +\subsubsection{Integrating third-party fonts} + +This is unfortunately a very complicated and messy topic. Forget +about it unless you really know your way around blindfolded in a +\TeX{} installation. Don't forget to check first what you get for +free: see section~\ref{sec:tl-fonts}. + +A possible alternative is to use \XeTeX (see +section~\ref{sec:tex-extensions}), which lets you use operating system +fonts without any installation in \TeX. + + +\subsection{Testing the installation} +\label{sec:test-install} + +After installing \TL{} as best you can, you naturally want to test +it out, so you can start creating beautiful documents and\slash or fonts. + +This section gives some basic procedures for testing that the new system +is functional. We give Unix commands here; under \MacOSX{} and Windows, +you're more likely to run the tests through a graphical interface, but +the principles are the same. + +\begin{enumerate} + +\item Make sure that you can run the \cmdname{tex} program in the first +place: + +\begin{alltt} +> \Ucom{tex -{}-version} +TeX 3.1415926 (Web2C 7.5.7) +kpathsea version 3.5.7 +... +\end{alltt} +If this comes back with `command not found' instead of version and +copyright information, or with an older version, most likely you don't +have the correct \dirname{bin} subdirectory in your \envname{PATH}. See +the environment-setting information on \p.\pageref{sec:env}. + +\item Process a basic \LaTeX{} file: +\begin{alltt} +> \Ucom{latex sample2e.tex} +This is pdfeTeXk, Version 3.1415926... +... +Output written on sample2e.dvi (3 pages, 7484 bytes). +Transcript written on sample2e.log. +\end{alltt} +If this fails to find \filename{sample2e.tex} or other files, most +likely you have interference from old environment variables or +configuration files; we recommend unsetting all \TeX-related environment +variables for a start. (For a deep analysis, you can ask \TeX{} to +report on exactly what it is searching for, and finding; see ``Debugging +actions'' on page~\pageref{sec:debugging}.) + +\item Preview the result online: +\begin{alltt} +> \Ucom{xdvi sample2e.dvi} +\end{alltt} +(Under Windows, the analogous command is \cmdname{dviout}.) You should +see a new window with a nice document explaining some of the basics of +\LaTeX{}. (Well worth reading, by the way if you're new to the system.) +You do have to be running under X for \cmdname{xdvi} to work; if you're +not, or your \envname{DISPLAY} environment variable is set incorrectly, +you'll get an error \samp{Can't open display}. + +\item Create a \PS{} file for printing or display: +\begin{alltt} +> \Ucom{dvips sample2e.dvi -o sample2e.ps} +\end{alltt} + +\item Create a \acro{PDF} file instead of \dvi{}; this processes the +\filename{.tex} file and writes \acro{PDF} directly: +\begin{alltt} +> \Ucom{pdflatex sample2e.tex} +\end{alltt} + +\item Preview the \acro{PDF} file: +\begin{alltt} +> \Ucom{gv sample2e.pdf} +\textrm{or:} +> \Ucom{xpdf sample2e.pdf} +\end{alltt} +Unfortunately neither \cmdname{gv} nor \cmdname{xpdf} are currently +included in \TL{}, so you must install them separately. See +\url{http://www.gnu.org/software/gv} and +\url{http://www.foolabs.com/xpdf}, respectively. (There are plenty of +other \acro{PDF} viewers, too.) + +\item Standard test files you may find useful in addition to +\filename{sample2e.tex}: + +\begin{ttdescription} +\item [small2e.tex] A simpler document than \filename{sample2e}, to +reduce the input size if you're having troubles. +\item [testpage.tex] Test if your printer introduces any offsets. +\item [nfssfont.tex] For printing font tables and tests. +\item [testfont.tex] Also for font tables, but using plain \TeX{}. +\item [story.tex] The most canonical (plain) \TeX{} test file of all. +You must type \samp{\bs bye} to the \code{*} prompt after \samp{tex +story.tex}. +\end{ttdescription} + +\end{enumerate} + +If you are new to \TeX{}, or otherwise need help with actually writing +\TeX{} or \LaTeX{} documents, please visit +\url{http://tug.org/begin.html} for some introductory resources. + + +\section{Network installations} +\label{sec:netinstall} + +\TL{} has been designed to be shared between different users, and even +different systems on a network. With a standard directory layout, no +hard paths are configured: the locations for files needed by \TL{} +programs are defined relative to the places of those programs. You can +see this at work in the configuration file +\filename{$TEXMFMAIN/web2c/texmf.cnf}, which contains lines such as +\begin{sverbatim} +TEXMFMAIN = $SELFAUTOPARENT/texmf +... +TEXMFLOCAL = $SELFAUTOPARENT/../texmf-local +\end{sverbatim} +This means that other systems or other users merely need to add the +directory for \TL{} binaries for their platform to their search path. + +By the same token, you can also install \TL{} locally and then move +the entire hierarchy afterwards to a network location. + +Of course, Windows users have different expectations. The directory +\dirname{texmf-doc/source/texlive/texlive-common/w32client} contains a +sample script \filename{install-w32client} which creates settings and +menu shortcuts for using an existing \TL{} installation on a +\acro{LAN}. It is to be invoked through a batch file +\filename{install-w32client.bat} in the same directory. + +You can read more about \TL{} configuration and path searching in +section~\ref{sec:kpathsea}. + +\section{Maximally portable \protect\TL{} on DVD and USB} +\label{sec:portable-unix} + +The `running from \DVD{}' option described in +section~\ref{sec:fromdvd} is fine for your own system, but if you +are a guest on somebody else's system then you would probably like +something with minimal side effects. + +In the root of the \TL{} \DVD, or the \dirname{texlive} subdirectory of +the \TK{} \DVD, are a \filename{tl-portable} script (Unix) and a +\filename{tl-portable.bat} batchfile (Windows) which start up a +secondary shell\slash command prompt with environment settings suitable +for directly accessing the \TL{} on the \DVD. + +When it runs for the first time, some files will be generated in a +directory \dirname{~/.tlportable2008}, which will take a little time. +On subsequent runs, though, it will start almost instantaneously. + +The rest of the system will be unaware of \TL. If you want your editor +to be aware of this \TL, then you can start it from a second, parallel, +such \filename{tl-portable} session. + +You can also use \filename{tl-portable} to run \TL{} on a +\acro{USB} stick. In this case, copy all the top-level files and +the contents of the \dirname{bin}, \dirname{texmf}, +\dirname{texmf-dist}, and \dirname{tlpkg} directories (at least) to +the stick. This may take quite a while! If you are copying to a +\acro{FAT}32-formatted \acro{USB} stick, make sure to dereference +symbolic links (\code{cp -L}). A \dirname{texmf-local} directory on +the stick will also be found and used. + +Then run \filename{tl-portable} from the root of the stick, as above. +In this case, the script will notice that the stick is writable and use +it for generated files. You could burn the resulting contents of the +stick back to \DVD{} if that is more convenient to (for example) give to +others. + + +\section{\cmdname{tlmgr}: Managing your installation} +\label{sec:tlmgr} + +\begin{figure}[tb] +\tlpng{tlmgr-gui}{\linewidth} +\caption{\prog{tlmgr} in \GUI\ mode. The list of + packages/collections/schemes only shows up after clicking the + `Load' button.}\label{fig:tlmgr-gui} +\end{figure} + +\begin{figure}[tb] +\tlpng{tlmgr-config}{\linewidth} +\caption{\texttt{tlmgr} in GUI mode: Configuration tab}\label{fig:tlmgr-config} +\end{figure} + +The installer installs a program named \prog{tlmgr} for managing \TL{} +after the initial installation. The programs \prog{updmap}, +\prog{fmtutil} and \prog{texconfig} are still included and will be +retained in the future, but \prog{tlmgr} is now the preferred interface. +Its capabilities include: + +\begin{itemize*} +\item listing schemes, collections and packages; +\item installing, updating, backing up, restoring and uninstalling + individual packages, optionally taking dependencies into account; +\item searching for packages; +\item listing and adding architectures; +\item changing installation options such as paper size and source + location (see section~\ref{sec:location}). +\end{itemize*} +\textit{Warning:} \prog{tlmgr} has not been designed for or tested +with installations which run from \DVD. + +\subsection{\cmdname{tlmgr} GUI mode} +\prog{tlmgr} can be started in \GUI{} mode with +\begin{alltt} +> \Ucom{tlmgr -gui} +\end{alltt} +or in Windows via the Start menu: \texttt{Start}, \texttt{Programs}, +\texttt{TeX Live 2008}, \texttt{TeX Live Manager}. After clicking `Load' +it displays a list of available and installed packages\Dash the latter +prepended with `(i)'. This assumes of course that the installation +source is valid and reachable. + +Figure~\ref{fig:tlmgr-config} shows the configuration tab. + +\subsection{Sample \cmdname{tlmgr} command-line invocations} + +This example adds several packages, including a new `engine', from a +non-default location: + +\begin{alltt} +> \Ucom{tlmgr -location http://172.16.18.1/tldev install collection-xetex xkeyval} +\end{alltt} +It generates the following output: +\begin{fverbatim} +install: collection-xetex +install: arabxetex +install: euenc +install: bidi +install: fontspec +install: fontwrap +install: ifxetex +install: philokalia +install: polyglossia +install: xecyr +install: xecyr.i386-linux +install: xepersian +install: xetex +install: xetexconfig +install: xetex.i386-linux +running post install action for xetex +install: xetex-def +install: xetex-pstricks +install: xetexfontinfo +install: xltxtra +install: xunicode +install: xkeyval +running mktexlsr +mktexlsr: Updating /usr/local/texlive/2008/texmf/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-config/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-dist/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-doc/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/../texmf-local/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-var/ls-R... +mktexlsr: Done. +regenerating fmtutil.cnf +running fmtutil-sys --missing +... +Transcript written on xelatex.log. +fmtutil: /usr/local/texlive/2008/texmf-var/web2c/xetex/xelatex.fmt installed. +\end{fverbatim} +As you see, \prog{tlmgr} installs dependencies, and takes care of any +necessary post-install actions, including updating the filename database +and (re)generating formats. (Here we generated new formats for \XeTeX.) + +This example installs a new language. This also triggers format +regeneration: +\begin{alltt} +> \Ucom{tlmgr install collection-langdutch} +\end{alltt} +To describe a package: +\begin{alltt} +> \Ucom{tlmgr show collection-wintools} +\end{alltt} +which produces +\begin{fverbatim} +Package: collection-wintools +Category: Collection +ShortDesc: Windows support programs +LongDesc: Utilities for Windows, since they are not readily available there: + gzip, chktex, jpeg2ps, unzip, wget, xpdf. +Installed: Yes +\end{fverbatim} +Updating your entire installation to the latest versions available: +\begin{alltt} +> \Ucom{tlmgr update -all} +\end{alltt} +If this makes you nervous, first try +\begin{alltt} +> \Ucom{tlmgr update -all -dry-run} +\end{alltt} +or +\begin{alltt} +> \Ucom{tlmgr update -list} +\end{alltt} +For full documentation: +\begin{alltt} +> \Ucom{tlmgr -help} +\end{alltt} + + +\section{Notes on Windows} +\label{sec:windows} + +\TL\ has a single installer which runs on both Windows and Unix. This +was only possible by dropping support for older Windows versions, so +\TL\ can now be installed only on Windows 2000 and later. + + +\subsection{Windows-specific features} +\label{sec:winfeatures} + +Under Windows, the installer does some extra things: +\begin{description} +\item[Menus and shortcuts.] A new `\TL{}' submenu of the + Start menu is installed, which contains entries for some \GUI{} programs + (\prog{tlmgr}, \prog{texdoctk}, the PS\_View PostScript previewer) + and some documentation. PS\_View also gets a shortcut on the + desktop as a drag-and-drop target for PostScript files. +\item[Automatic setting of environment variables.] No manual + configuration steps are required. +\item[Uninstaller.] The installer creates an entry under `Add/Remove + Programs' for \TL. The uninstall tab of\prog{tlmgr} refers to + this. +\end{description} + +\subsection{Additional included software} + +\begin{figure}[tb] +\tlpng{psview}{.6\linewidth} +\caption{PS\_View: very high magnifications available!}\label{fig:psview} +\end{figure} + +To be complete, a \TL installation needs support packages that are not +commonly found on a Windows machine. \TL{} provides the missing +pieces: +\begin{description} +\item[Perl and Ghostscript.] Because of the importance of Perl and + Ghostscript, \TL{} includes `hidden' copies of these + programs. \TL{} programs that need them know where to find them, + but they don't betray their presence through environment variables + or registry settings. They aren't full-scale distributions, and + shouldn't interfere with any system installations of Perl or + Ghostscript. +\item[Command-line tools.] A number of Windows ports of common Unix + command-line programs are installed along with the usual \TL{} + binaries. These include \cmdname{gzip}, \cmdname{chktex}, + \cmdname{jpeg2ps}, \cmdname{unzip}, \cmdname{wget} and the + command-line utilities from the \cmdname{xpdf} suite. (The + \cmdname{xpdf} viewer itself is not available for Windows, but the + Sumatra \acro{PDF} viewer is based on it: + \url{http://blog.kowalczyk.info/software/sumatrapdf}.) +\item[\texttt{fc-cache}] helps \XeTeX{} to handle fonts more + efficiently. +\item[PS\_View.] Also installed is PS\_View, a new PostScript viewer + with a free license; see figure~\ref{fig:psview}. +\end{description} +\begin{description} +\item[The \texttt{support} directory,] already mentioned in + section~\ref{sec:tld}. This directory contains various programs + which can be useful in connection with \TeX, in particular a + number of \TeX-aware editors and \TeX{} frontends. The software in + this directory isn't covered by the installer. This directory also + contains the \cmdname{dviout} \dvi{} previewer; see the next section. +\end{description} + +\subsection{The Dviout previewer} + +This \TL{} release unfortunately doesn't offer a preinstalled \dvi{} +previewer for Windows. However, you can install \prog{dviout} by +Toshio Oshima from the \path{support/dviout/} directory, which +contains also a short \filename{README} describing how to install +and configure \prog{dviout} for \TL. Please read this carefully +before installation. + +At first, when you preview files with \cmdname{dviout}, it will create fonts, +because screen fonts were not installed. After a while, you will have created +most of the fonts you use, and you will rarely see the font-creation window. +More information can be found in the (very good) on-line help. + +\subsection{Links for additional downloadable software} + +Urls for some other tools you may consider installing: +\begin{description} +\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} +\item[Perl] \url{http://www.perl.org/} with + supplementary packages from \acro{CPAN}, \url{http://www.cpan.org/} +\item[ImageMagick] \url{http://www.imagemagick.com}, for graphics + processing and conversion +\item[NetPBM] \url{http://netpbm.sourceforge.net/}, also for graphics. + +\item[\TeX-oriented editors] There is a wide choice, and it is a matter of the + user's taste. Here is a selection, in no particular order: + \begin{itemize*} + \item \cmdname{GNU Emacs} is available natively under Windows, see + \url{http://www.gnu.org/software/emacs/windows/ntemacs.html}. + \item \cmdname{Emacs} with Auc\TeX\ for Windows is available in \TL's + \path{support} directory; its home page is + \url{http://www.gnu.org/software/auctex}. + \item \cmdname{WinShell} is available in \TL's \path|support| + directory; its home page is \url{http://www.winshell.de}. + \item \cmdname{WinEdt} is shareware available from + \url{http://www.winedt.com}. + \item \cmdname{Vim} is free software, available from + \url{http://www.vim.org}. + \item TeXnicCenter is free software, available from + \url{http://www.toolscenter.org} and in the pro\TeX{}t distribution. + \item \cmdname{LEd} is available from \url{http://www.ctan.org/support/LEd}. + \item \cmdname{SciTE} is available from + \url{http://www.scintilla.org/SciTE.html}. + \end{itemize*} +\end{description} + + +\subsection{User Profile is Home} +\label{sec:winhome} + +The Windows counterpart of a Unix home directory is the +\verb|%USERPROFILE%| directory. Under Windows XP and Windows 2000, this +is usually \verb|C:\Documents and Settings\|, and under +Windows Vista \verb|C:\Users\|. In the +\filename{texmf.cnf} file, and \KPS{} in general, \verb|~| will expand +appropriately on both Windows and Unix. + + +\subsection{The Windows registry} +\label{sec:registry} + +Windows stores nearly all configuration data in its registry. The +registry contains a set of hierarchically organized keys, with several +root keys. The most important ones for installation programs are +\path{HKEY_CURRENT_USER} and \path{HKEY_LOCAL_MACHINE}, \path{HKCU} and +\path{HKLM} in short. The \path{HKCU} part of the registry is in the +user's home directory (see section~\ref{sec:winhome}). \path{HKLM} is +normally in a subdirectory of the Windows directory. + +In some cases, system information could be obtained from environment +variables but for other information, for example the location of +shortcuts, it is necessary to consult the registry. Setting environment +variables permanently also requires registry access. + + +\subsection{Windows permissions} +\label{sec:winpermissions} + +In later versions of Windows, a distinction is made between regular +users and administrators, where only the latter have free access to the +entire operating system. In practice, though, you could better describe +these classes of users as unprivileged users and normal users: being an +administrator is the rule, not the exception. Nevertheless, we have made +an effort to make \TL{} installable without administrative privileges. + +If the user is an administrator, shortcuts are created for all users, +and the system environment is modified. Otherwise, shortcuts and menu +entries are created for the current user, and the user environment is +modified. Use the \optname{non-admin} option to \prog{install-tl} if +you prefer per-user settings even as an administrator. + +Regardless of administrator status, the default root of \TL{} proposed +by the installer is always under \verb|%PROGRAMFILES%|. The installer +always tests whether the root is writable for the current user. + +A problem may arise if the user is not an administrator and \TeX{} +already exists in the search path. Since the effective path consists of +the system path followed by the user path, the new \TL{} will never get +precedence. As a workaround, in this case the installer creates +shortcuts to the command-prompt in which the new \TL{} binary directory +is prepended to the local searchpath. The new \TL{} will be usable when +run in a command-line session started from such a shortcut. + + +\section{A user's guide to Web2C} + +\Webc{} is an integrated collection of \TeX-related programs: \TeX{} +itself, \MF{}, \MP, \BibTeX{}, etc. It is the heart of \TL{}. The home +page for \Webc{}, with the current manual and more, is +\url{http://tug.org/web2c}. + +A bit of history: The original implementation was by Tomas Rokicki who, +in 1987, developed a first \TeX{}-to-C system based on change files +under Unix, which were primarily the original work of Howard Trickey and +Pavel Curtis. Tim Morgan became the maintainer of the system, and +during this period the name changed to Web-to-C\@. In 1990, Karl Berry +took over the work, assisted by dozens of additional contributors, and +in 1997 he handed the baton to Olaf Weber, who returned it to Karl in +2006. + +The \Webc{} system runs on Unix, 32-bit Windows systems, \MacOSX{}, and +other operating systems. It uses Knuth's original sources for \TeX{} and +other basic programs written in the \web{} literate programming system +and translates them into C source code. The core \TeX{} programs +handled in this way are: + +\begin{cmddescription} +\item[bibtex] Maintaining bibliographies. +\item[dmp] \cmdname{troff} to MPX (\MP{} pictures). +\item[dvicopy] Expands virtual font references in \dvi{} files. +\item[dvitomp] \dvi{} to MPX (MetaPost pictures). +\item[dvitype] \dvi{} to human-readable text. +\item[gftodvi] Generic font proofsheets. +\item[gftopk] Generic to packed fonts. +\item[gftype] GF to human-readable text. +\item[makempx] \MP{} label typesetting. +\item[mf] Creating typeface families. +\item[mft] Prettyprinting \MF{} source. +\item[mpost] Creating technical diagrams. +\item[mpto] MetaPost label extraction. +\item[newer] Compare modification times. +\item[patgen] Creating hyphenation patterns. +\item[pktogf] Packed to generic fonts. +\item[pktype] PK to human-readable text. +\item[pltotf] Plain text property list to TFM. +\item[pooltype] Display \web{} pool files. +\item[tangle] \web{} to Pascal. +\item[tex] Typesetting. +\item[tftopl] TFM to plain text property list. +\item[vftovp] Virtual font to virtual property list. +\item[vptovf] Virtual property list to virtual font. +\item[weave] \web{} to \TeX. +\end{cmddescription} + +\noindent The precise functions and syntax of these programs are +described in the documentation of the individual packages and of \Webc{} +itself. However, knowing a few principles governing the whole family of +programs will help you take advantage of your \Webc{} installation. + +All programs honor these standard \GNU options: +\begin{ttdescription} +\item[-{}-help] print basic usage summary. +\item[-{}-verbose] print detailed progress report. +\item[-{}-version] print version information, then exit. +\end{ttdescription} + +For locating files the \Webc{} programs use the path searching library +\KPS{} (\url{http://tug.org/kpathsea}). This library uses a combination +of environment variables and a configuration files to optimize searching +the (huge) collection of \TeX{} files. \Webc{} can look at many +directory trees simultaneously, which is useful in maintaining \TeX's +standard distribution and local and personal extensions in distinct +trees. To speed up file searches, the root of each tree has a file +\file{ls-R}, containing an entry showing the name and relative pathname +for all files under that root. + + +\subsection{Kpathsea path searching} +\label{sec:kpathsea} + +Let us first describe the generic path searching mechanism of the \KPS{} +library. + +We call a \emph{search path} a colon- or semicolon\hyph sepa\-rated list +of \emph{path elements}, which are basically directory names. A +search path can come from (a combination of) many sources. To look up +a file \samp{my-file} along a path \samp{.:/dir}, \KPS{} checks each +element of the path in turn: first \file{./my-file}, then +\file{/dir/my-file}, returning the first match (or possibly all +matches). + +In order to adapt optimally to all operating systems' conventions, on +non-Unix systems \KPS{} can use filename separators different from +colon (\samp{:}) and slash (\samp{/}). + +To check a particular path element \var{p}, \KPS{} first checks if a +prebuilt database (see ``Filename data\-base'' on +page~\pageref{sec:filename-database}) applies to \var{p}, i.e., if the +database is in a directory that is a prefix of \var{p}. If so, the path +specification is matched against the contents of the database. + +If the database does not exist, or does not apply to this path +element, or contains no matches, the filesystem is searched (if this +was not forbidden by a specification starting with \samp{!!}\ and if +the file being searched for must exist). \KPS{} constructs the list +of directories that correspond to this path element, and then checks +in each for the file being sought. + +The ``file must exist'' condition comes into play with \samp{.vf} files and +input files read by \TeX's \cs{openin} command. Such files may not +exist (e.g., \file{cmr10.vf}), and so it would be wrong to search the +disk for them. Therefore, if you fail to update \file{ls-R} when you +install a new \samp{.vf} file, it will never be found. +Each path element is checked in turn: first the database, then the +disk. If a match is found, the search stops and the result is +returned. + +Although the simplest and most common path element is a directory +name, \KPS{} supports additional features in search paths: layered +default values, environment variable names, config file values, users' +home directories, and recursive subdirectory searching. Thus, we say +that \KPS{} \emph{expands} a path element, meaning it transforms all +the specifications into basic directory name or names. This is +described in the following sections in the same order as it takes +place. + +Note that if the filename being searched for is absolute or explicitly +relative, i.e., starts with \samp{/} or \samp{./} or \samp{../}, +\KPS{} simply checks if that file exists. + +\ifSingleColumn +\else +\begin{figure*} +\verbatiminput{examples/ex5.tex} +\setlength{\abovecaptionskip}{0pt} + \caption{An illustrative configuration file sample} + \label{fig:config-sample} +\end{figure*} +\fi + +\subsubsection{Path sources} +\label{sec:path-sources} + +A search path can come from many sources. In the order in which +\KPS{} uses them: + +\begin{enumerate} +\item + A user-set environment variable, for instance, \envname{TEXINPUTS}\@. + Environment variables with a period and a program name appended + override; e.g., if \samp{latex} is the name of the program being run, + then \envname{TEXINPUTS.latex} will override \envname{TEXINPUTS}. +\item + A program-specific configuration file, for exam\-ple, a line + \samp{S /a:/b} in \cmdname{dvips}'s \file{config.ps}. +\item A \KPS{} configuration file \file{texmf.cnf}, containing a line like + \samp{TEXINPUTS=/c:/d} (see below). +\item The compile-time default. +\end{enumerate} +\noindent You can see each of these values for a given search path by +using the debugging options (see ``Debugging actions'' on +page~\pageref{sec:debugging}). + +\subsubsection{Config files} + +\begingroup\tolerance=3500 +\KPS{} reads \emph{runtime configuration files} named \file{texmf.cnf} +for search path and other definitions. The search path used to look +for these files is named \envname{TEXMFCNF} (by default such a file lives +in the \file{texmf/web2c} subdirectory). \emph{All} +\file{texmf.cnf} files in the search path will be read and definitions +in earlier files override those in later files. Thus, with a search +path of \verb|.:$TEXMF|, values from \file{./texmf.cnf} override those +from \verb|$TEXMF/texmf.cnf|. +\endgroup + +\begin{itemize} +\item + Comments start with \code{\%} and continue to the end of the line. +\item + Blank lines are ignored. +\item + A \bs{} at the end of a line acts as a continuation character, + i.e., the next line is appended. Whitespace at the beginning of + continuation lines is not ignored. +\item + Each remaining line has the form: +\begin{alltt} + \var{variable}[.\var{progname}] [=] \var{value} +\end{alltt}% + where the \samp{=} and surrounding whitespace are optional. +\item + The \ttvar{variable} name may contain any character other + than whitespace, \samp{=}, or \samp{.}, but sticking to + \samp{A-Za-z\_} is safest. +\item + If \samp{.\var{progname}} is present, the definition only + applies if the program that is running is named + \texttt{\var{progname}} or \texttt{\var{progname}.exe}. This allows + different flavors of \TeX{} to have different search paths, for + example. +\item \var{value} may contain any characters except + \code{\%} and \samp{@}. The + \code{\$\var{var}.\var{prog}} feature is not available on the + right-hand side; instead, you must use an additional variable. A + \samp{;}\ in \var{value} is translated to \samp{:}\ if + running under Unix; this is useful to be able to have a single + \file{texmf.cnf} for Unix, \acro{MS-DOS} and Windows systems. +\item + All definitions are read before anything is expanded, so + variables can be referenced before they are defined. +\end{itemize} +A configuration file fragment illustrating most of these points is +\ifSingleColumn +shown below: + +\verbatiminput{examples/ex5.tex} +\else +shown in Figure~\ref{fig:config-sample}. +\fi + +\subsubsection{Path expansion} +\label{sec:path-expansion} + + +\KPS{} recognizes certain special characters and constructions in +search paths, similar to those available in Unix shells. As a +general example, the complex path, +\verb+~$USER/{foo,bar}//baz+, expands to all subdirectories under +directories \file{foo} and \file{bar} in \texttt{\$USER}'s home +directory that contain a directory or file \file{baz}. These +expansions are explained in the sections below. +%$ +\subsubsection{Default expansion} +\label{sec:default-expansion} + +\tolerance=2500 +If the highest-priority search path (see ``Path sources'' on +page~\pageref{sec:path-sources}) contains an \emph{extra colon} (i.e., +leading, trailing, or doubled), \KPS{} inserts at that point the +next-highest-prio\-rity search path that is defined. If that inserted +path has an extra colon, the same happens with the next highest. For +example, given an environment variable setting + +\tolerance=1500 + +\begin{alltt} +> \Ucom{setenv TEXINPUTS /home/karl:} +\end{alltt} +and a \code{TEXINPUTS} value from \file{texmf.cnf} of + +\begin{alltt} + .:\$TEXMF//tex +\end{alltt} +then the final value used for searching will be: + +\begin{alltt} + /home/karl:.:\$TEXMF//tex +\end{alltt} + +Since it would be useless to insert the default value in more than one +place, \KPS{} changes only one extra \samp{:}\ and leaves any others in +place. It checks first for a leading \samp{:}, then a trailing +\samp{:}, then a doubled \samp{:}. + +\subsubsection{Brace expansion} + +A useful feature is brace expansion, which means that, for instance, +\verb+v{a,b}w+ expands to \verb+vaw:vbw+. Nesting is allowed. +This is used to implement multiple \TeX{} hierarchies, by +assigning a brace list to \code{\$TEXMF}. +For example, in \file{texmf.cnf}, the following definition +(appproximately; there are actually even more trees) is made: +\begin{verbatim} + TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN} +\end{verbatim} +Using this you can then write something like +\begin{verbatim} + TEXINPUTS = .;$TEXMF/tex// +\end{verbatim} +%$ +which means that, after looking in the current directory, the +\code{\$TEXMFHOME/tex}, \code{\$TEXMFLOCAL/tex}, \code{\$TEXMFVAR/tex} +and \code{\$TEXMFMAIN/tex} trees \emph{only}) will be searched (the +last two use using \file{ls-R} data base files). It is a convenient +way for running two parallel \TeX{} structures, one ``frozen'' (on a +\CD, for instance) and the other being continuously updated with new +versions as they become available. By using the \code{\$TEXMF} +variable in all definitions, one is sure to always search the +up-to-date tree first. + +\subsubsection{Subdirectory expansion} +\label{sec:subdirectory-expansion} + +Two or more consecutive slashes in a path element following a directory +\var{d} is replaced by all subdirectories of \var{d}: first those +subdirectories directly under \var{d}, then the subsubdirectories under +those, and so on. At each level, the order in which the directories are +searched is \emph{unspecified}. + +If you specify any filename components after the \samp{//}, only +subdirectories with matching components are included. For example, +\samp{/a//b} expands into directories \file{/a/1/b}, \file{/a/2/b}, +\file{/a/1/1/b}, and so on, but not \file{/a/b/c} or \file{/a/1}. + +Multiple \samp{//} constructs in a path are possible, but +\samp{//} at the beginning of a path is ignored. + +\subsubsection{List of special characters and their meaning: a summary} + +The following list summarizes the special characters in \KPS{} +configuration files. + +% need a wider space for the item labels here. +\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} +\begin{ttdescription} +\item[\CODE{:}] Separator in path specification; at the beginning or + the end of a path it substitutes the default path expansion.\par +\item[\CODE{;}] Separator on non-Unix systems (acts like \code{:}). +\item[\CODE{\$}] Variable expansion. +\item[\CODE{\string~}] Represents the user's home directory. +\item[\CODE{\char`\{...\char`\}}] Brace expansion. +\item[\CODE{//}] Subdirectory expansion (can occur anywhere in + a path, except at its beginning). +\item[\CODE{\%}] Start of comment. +\item[\CODE{\bs}] Continuation character (allows multi-line entries). +\item[\CODE{!!}] Search \emph{only} database to locate file, \emph{do + not} search the disk. +\end{ttdescription} + + +\subsection{Filename databases} +\label{sec:filename-database} + +\KPS{} goes to some lengths to minimize disk accesses for searches. +Nevertheless, at installations with enough directories, searching each +possible directory for a given file can take an excessively long time +(this is especially true if many hundreds of font directories have to +be traversed.) Therefore, \KPS{} can use an externally-built plain text +``database'' file named \file{ls-R} that maps files to directories, +thus avoiding the need to exhaustively search the disk. + +A second database file \file{aliases} allows you to give additional +names to the files listed in \file{ls-R}. This can be helpful to +confirm to \acro{DOS} 8.3 filename conventions in source files. + +\subsubsection{The filename database} +\label{sec:ls-R} + +As explained above, the name of the main filename database must be +\file{ls-R}. You can put one at the root of each \TeX{} hierarchy in +your installation that you wish to be searched (\code{\$TEXMF} by +default); most sites have only one hierarchy. \KPS{} looks for +\file{ls-R} files along the \code{TEXMFDBS} path. + +The recommended way to create and maintain \samp{ls-R} is to run the +\code{mktexlsr} script included with the distribution. It is invoked +by the various \samp{mktex}\dots\ scripts. In principle, this script +just runs the command +\begin{alltt} +cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R +\end{alltt} +presuming your system's \code{ls} produces the right output format +(\GNU \code{ls} is all right). To ensure that the database is +always up-to-date, it is easiest to rebuild it regularly via +\code{cron}, so that it is automatically updated when the installed +files change, such as after installing or updating a \LaTeX{} package. + +If a file is not found in the database, by default \KPS{} goes ahead +and searches the disk. If a particular path element begins with +\samp{!!}, however, \emph{only} the database will be searched for that +element, never the disk. + + +\subsubsection{kpsewhich: Standalone path searching} +\label{sec:invoking-kpsewhich} + +The \texttt{kpsewhich} program exercises path searching independent of any +particular application. This can be useful as a sort of \code{find} +program to locate files in \TeX{} hierarchies (this is used heavily in +the distributed \samp{mktex}\dots\ scripts). + +\begin{alltt} +> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} +\end{alltt} +The options specified in \ttvar{option} start with either \samp{-} +or \samp{-{}-}, and any unambiguous abbreviation is accepted. + +\KPS{} looks up each non-option argument on the command line as a +filename, and returns the first file found. There is no option to +return all the files with a particular name (you can run the Unix +\samp{find} utility for that). + +The most common options are described next. + +\begin{ttdescription} +\item[\texttt{-{}-dpi=\var{num}}]\mbox{} + Set the resolution to \ttvar{num}; this only affects \samp{gf} + and \samp{pk} lookups. \samp{-D} is a synonym, for compatibility + with \cmdname{dvips}. Default is 600. + +\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ + Set the format for lookup to \ttvar{name}. By default, the + format is guessed from the filename. For formats which do not have + an associated unambiguous suffix, such as \MP{} support files and + \cmdname{dvips} configuration files, you have to specify the name as + known to \KPS{}, such as \texttt{tex} or \texttt{enc files}. Run + \texttt{kpsewhich -{}-help} for a list. + +\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ + Set the mode name to \ttvar{string}; this only affects \samp{gf} + and \samp{pk} lookups. No default: any mode will be found. +\item[\texttt{-{}-must-exist}]\mbox{}\\ + Do everything possible to find the files, notably including + searching the disk. By default, only the \file{ls-R} database is + checked, in the interest of efficiency. +\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ + Search along the path \ttvar{string} (colon-separated as usual), + instead of guessing the search path from the filename. \samp{//} and + all the usual expansions are supported. The options \samp{-{}-path} + and \samp{-{}-format} are mutually exclusive. +\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ + Set the program name to \texttt{\var{name}}. + This can affect the search paths via the \texttt{.\var{progname}} + feature. + The default is \cmdname{kpsewhich}. +\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ + shows the path used for file lookups of file type \texttt{\var{name}}. + Either a filename extension (\code{.pk}, \code{.vf}, etc.) or a + name can be used, just as with \samp{-{}-format} option. +\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ + sets the debugging options to \texttt{\var{num}}. +\end{ttdescription} + + +\subsubsection{Examples of use} +\label{sec:examples-of-use} + +Let us now have a look at \KPS{} in action. Here's a straightforward search: + +\begin{alltt} +> \Ucom{kpsewhich article.cls} + /usr/local/texmf-dist/tex/latex/base/article.cls +\end{alltt} +We are looking for the file \file{article.cls}. Since the \samp{.cls} +suffix is unambiguous we do not need to specify that we want to look for a +file of type \optname{tex} (\TeX{} source file directories). We find it in +the subdirectory \file{tex/latex/base} below the \samp{texmf-dist} \TL\ +directory. Similarly, all of the following are found without problems +thanks to their unambiguous suffix. +\begin{alltt} +> \Ucom{kpsewhich array.sty} + /usr/local/texmf-dist/tex/latex/tools/array.sty +> \Ucom{kpsewhich latin1.def} + /usr/local/texmf-dist/tex/latex/base/latin1.def +> \Ucom{kpsewhich size10.clo} + /usr/local/texmf-dist/tex/latex/base/size10.clo +> \Ucom{kpsewhich small2e.tex} + /usr/local/texmf-dist/tex/latex/base/small2e.tex +> \Ucom{kpsewhich tugboat.bib} + /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib +\end{alltt} + +By the way, that last is a \BibTeX{} bibliography database for \textsl{TUGBoat} articles. + +\begin{alltt} +> \Ucom{kpsewhich cmr10.pk} +\end{alltt} +Font bitmap glyph files of type \file{.pk} are used by display +programs like \cmdname{dvips} and \cmdname{xdvi}. Nothing is returned in +this case since there are no pre-generated Computer Modern \samp{.pk} +files in \TL{}\Dash the Type~1 variants are used by default. +\begin{alltt} +> \Ucom{kpsewhich wsuipa10.pk} +\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk +\else /usr/local/texmf-var/fonts/pk/ljfour/public/ +... wsuipa/wsuipa10.600pk +\fi\end{alltt} +For these fonts (a phonetic alphabet from the University of Washington) +we had to generate \samp{.pk} files, and since the default \MF{} mode on +our installation is \texttt{ljfour} with a base resolution of 600\dpi{} +(dots per inch), this instantiation is returned. +\begin{alltt} +> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} +\end{alltt} +In this case, when specifying that we are interested in a resolution +of 300\dpi{} (\texttt{-dpi=300}) we see that no such font is available on +the system. A program like \cmdname{dvips} or \cmdname{xdvi} would +go off and actually build the required \texttt{.pk} files +using the script \cmdname{mktexpk}. + +Next we turn our attention to \cmdname{dvips}'s header and configuration +files. We first look at one of the commonly used files, the general +prologue \file{tex.pro} for \TeX{} support, before turning our attention +to the generic configuration file (\file{config.ps}) and the \PS{} font +map \file{psfonts.map}\Dash as of 2004, map and encoding files have +their own search paths and new location in \dirname{texmf} trees. As +the \samp{.ps} suffix is ambiguous we have to specify explicitly which +type we are considering (\optname{dvips config}) for the file +\texttt{config.ps}. +\begin{alltt} +> \Ucom{kpsewhich tex.pro} + /usr/local/texmf/dvips/base/tex.pro +> \Ucom{kpsewhich --format="dvips config" config.ps} + /usr/local/texmf/dvips/config/config.ps +> \Ucom{kpsewhich psfonts.map} + /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map +\end{alltt} + +We now take a closer look at the \acro{URW} Times \PS{} support +files. The prefix for these in the standard font naming scheme is +\samp{utm}. The first file we look at is the configuration file, +which contains the name of the map file: +\begin{alltt} +> \Ucom{kpsewhich --format="dvips config" config.utm} + /usr/local/texmf-dist/dvips/psnfss/config.utm +\end{alltt} +The contents of that file is +\begin{alltt} + p +utm.map +\end{alltt} +which points to the file \file{utm.map}, which we want to +locate next. +\begin{alltt} +> \Ucom{kpsewhich utm.map} + /usr/local/texmf-dist/fonts/map/dvips/times/utm.map +\end{alltt} +This map file defines the file names of the Type~1 \PS{} fonts in +the URW collection. Its contents look like (we only show part of the +lines): +\begin{alltt} +utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} +\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb +\else /usr/local/texmf-dist/fonts/type1/ +... urw/utm/utmr8a.pfb +\fi\end{alltt} + +It should be evident from these examples how you can easily locate the +whereabouts of a given file. This is especially important if you suspect +that the wrong version of a file is picked up somehow, since +\cmdname{kpsewhich} will show you the first file encountered. + +\subsubsection{Debugging actions} +\label{sec:debugging} + +Sometimes it is necessary to investigate how a program resolves file +references. To make this practical, \KPS{} offers various levels of +debugging output: + +\begin{ttdescription} +\item[\texttt{\ 1}] \texttt{stat} calls (disk lookups). When running + with an up-to-date \file{ls-R} database this should almost give no + output. +\item[\texttt{\ 2}] References to hash tables (such as \file{ls-R} + databases, map files, configuration files). +\item[\texttt{\ 4}] File open and close operations. +\item[\texttt{\ 8}] General path information for file types + searched by \KPS. This is useful to find out where a particular + path for the file was defined. +\item[\texttt{16}] Directory list for each path element (only relevant + for searches on disk). +\item[\texttt{32}] File searches. +\item[\texttt{64}] Variable values. +\end{ttdescription} +A value of \texttt{-1} will set all the above options; in practice, +this is usually the most convenient. + +Similarly, with the \cmdname{dvips} program, by setting a combination of +debug switches, one can follow in detail where files are being picked up +from. Alternatively, when a file is not found, the debug trace shows in +which directories the program looks for the given file, so that one can +get an indication what the problem~is. + +Generally speaking, as most programs call the \KPS{} library +internally, one can select a debug option by using the +\envname{KPATHSEA\_DEBUG} environment variable, and setting it to (a +combination of) values as described in the above list. + +(Note for Windows users: it is not easy to redirect +all messages to a file in this system. For diagnostic purposes +you can temporarily \texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log}). + +Let us consider, as an example, a small \LaTeX{} source file, +\file{hello-world.tex}, which contains the following input. +\begin{verbatim} + \documentclass{article} + \begin{document} + Hello World! + \end{document} +\end{verbatim} +This little file only uses the font \file{cmr10}, so let us look at +how \cmdname{dvips} prepares the \PS{} file (we want to use the Type~1 +version of the Computer Modern fonts, hence the option \texttt{-Pcms}). +\begin{alltt} +> \Ucom{dvips -d4100 hello-world -Pcms -o} +\end{alltt} +In this case we have combined \cmdname{dvips}'s debug class 4 (font +paths) with \KPS's path element expansion (see \cmdname{dvips} Reference +Manual, \OnCD{texmf/doc/dvips/dvips.pdf}). +The output (slightly rearranged) appears in +Figure~\ref{fig:dvipsdbga}. +\begin{figure*}[tp] +\centering +\input{examples/ex6a.tex} +\caption{Finding configuration files}\label{fig:dvipsdbga} + +\bigskip + +\input{examples/ex6b.tex} +\caption{Finding the prolog file}\label{fig:dvipsdbgb} + +\bigskip + +\input{examples/ex6c.tex} +\caption{Finding the font file}\label{fig:dvipsdbgc} +\end{figure*} + +\cmdname{dvips} starts by locating its working files. First, +\file{texmf.cnf} is found, which gives the definitions of the search +paths for the other files, then the file database \file{ls-R} (to +optimize file searching) and the file \file{aliases}, which makes it +possible to declare several names (e.g., a short \acro{DOS}-like 8.3 and +a more natural longer version) for the same file. Then \cmdname{dvips} +goes on to find the generic configuration file \file{config.ps} +before looking for the customization file \file{.dvipsrc} (which, in +this case is \emph{not found}). Finally, \cmdname{dvips} locates the +config file for the Computer Modern \PS{} fonts \file{config.cms} +(this was initiated with the \texttt{-Pcms} option on the \cmdname{dvips} +command). This file contains the list of the map files which +define the relation between the \TeX{}, \PS{} and file system +names of the fonts. +\begin{alltt} +> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} + p +ams.map + p +cms.map + p +cmbkm.map + p +amsbkm.map +\end{alltt} +\cmdname{dvips} thus goes on to find all these files, plus the generic +map file \file{psfonts.map}, which is always loaded (it contains +declarations for commonly used \PS{} fonts; see the last part of +Section \ref{sec:examples-of-use} for more details about \PS{} map +file handling). + +At this point \cmdname{dvips} identifies itself to the user: +\begin{alltt} +This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) +\end{alltt} +\ifSingleColumn +Then it goes on to look for the prolog file \file{texc.pro}: +\begin{alltt}\small +kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro +\end{alltt} +\else +Then it goes on to look for the prolog file \file{texc.pro} (see +Figure~\ref{fig:dvipsdbgb}). +\fi + +After having found the file in question, \cmdname{dvips} outputs +the date and time, and informs us that it will generate the +file \file{hello-world.ps}, then that it needs the font file +\file{cmr10}, and that the latter is declared as ``resident'' (no +bitmaps needed): +\begin{alltt}\small +TeX output 1998.02.26:1204' -> hello-world.ps +Defining font () cmr10 at 10.0pt +Font cmr10 is resident. +\end{alltt} +Now the search is on for the file \file{cmr10.tfm}, which is found, +then a few more prolog files (not shown) are referenced, and finally +the Type~1 instance \file{cmr10.pfb} of the font is located and +included in the output file (see last line). +\begin{alltt}\small +kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, + path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: + /var/tex/fonts/tfm//). +kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm +kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, + ... + +kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb +[1] +\end{alltt} + +\subsection{Runtime options} + +Another useful feature of \Webc{} is its possibility to control a number +of memory parameters (in particular, array sizes) via the runtime file +\file{texmf.cnf} read by \KPS{}. The memory settings can be found in +Part 3 of that file in the \TL{} distribution. The more important +are: + +\begin{ttdescription} +\item[\texttt{main\_memory}] + Total words of memory available, for + \TeX{}, \MF{} and \MP. You must make a new format file for each + different setting. For instance, you could generate a ``huge'' + version of \TeX{}, and call the format file \texttt{hugetex.fmt}. + Using the standard way of specifying the program name used by \KPS{}, + the particular value of the \texttt{main\_memory} variable will then + be read from \file{texmf.cnf}. +\item[\texttt{extra\_mem\_bot}] + Extra space for ``large'' \TeX{} data structures: + boxes, glue, breakpoints, etc. Especially useful if you use + \PiCTeX{}. +\item[\texttt{font\_mem\_size}] + Number of words for font information available for \TeX. This + is more or less the total size of all \acro{TFM} files read. +\item[\texttt{hash\_extra}] + Additional space for the hash table of control sequence names. + Only $\approx$10,000 control sequences can be stored in the main + hash table; if you have a large book with numerous cross-references, + this might not be enough. The default value of + \texttt{hash\_extra} is \texttt{50000}. +\end{ttdescription} + +\noindent Of course, this facility is no substitute for truly dynamic +arrays and memory allocation, but since these are extremely difficult to +implement in the present \TeX{} source, these runtime parameters provide +a practical compromise allowing some flexibility. + + +\begin{comment} +\section{Building on a new Unix platform} + +If you have a platform for which executables are not included, you will +need to compile \TeX{} and friends. This is not as hard as it +sounds. What you need is all in the directory \texttt{source} in the +distribution. + +\subsection{Prerequisites} + +You will need at least 100 megabytes of disk space to compile all of +\TeX{} and its support programs. You'll also need an \acro{ANSI} C +compiler, a \cmdname{make} utility, a lexical scanner, and a parser +generator. We recommend the \GNU version of these programs +(\cmdname{gcc}, \GNU \cmdname{make}, \cmdname{m4}, \cmdname{flex}, +\cmdname{bison}). You may be able to work with other C compilers and +\cmdname{make} programs, but you will need a good understanding of +building Unix programs to sort out problems. + +Also, the command \texttt{uname} must return a sensible value. + + +\subsection{Configuration} + +To begin, perform a normal installation of \TL{} to your disk (see +section~\ref{sec:install-disk} on +\p.\pageref{sec:install-disk}). You may wish to skip installing +all of the prebuilt binaries. + +Then, unpack the source from the compressed \texttt{tar} file in the +directory \dirname{source} to your disk and change directory to where +you placed it. + +Next, run \cmdname{configure} with a command line like this: +\begin{alltt} +> \Ucom{sh configure -prefix=/usr/local/TeX} +\end{alltt} + +The \optname{-prefix} directory is the one where you installed the +support tree; the directory layout will be as follows (where \$TEXDIR +stands for the directory you chose): + +\noindent +\begin{tabular}{>{\ttfamily}ll@{}} + \dirname{$TEXDIR/share/texmf} & main tree with fonts,\\ + & \qquad macros, etc\\ + \dirname{$TEXDIR/man} & Unix manual pages\\ + \dirname{$TEXDIR/info} & \GNU style Info manuals\\ + \dirname{$TEXDIR/bin/$PLATFORM} & binaries\\ +\end{tabular} +%$ + +If you want to leave out the \dirname{$PLATFORM} directory level, +i.e., put the binaries directly into \dirname{$TEXDIR/bin}, specify +the \verb|--disable-multiplatform| option to \cmdname{configure}. + +Have a look at the output of \verb|./configure --help| for more +options you can use. For example, you can skip building of \OMEGA{} and +\eTeX{}. + + +\subsection{Running \cmdname{make}} + +Make sure the shell variable or option \texttt{noclobber} is not set. +Then, run the main \cmdname{make} like this: +\begin{alltt} +> \Ucom{make world} +\end{alltt} +and relax\ldots + +Alternatively, you want to log all the output, as in: +\begin{alltt} +> \Ucom{sh -c "make world >world.log 2>\&1" \&} +\end{alltt} + +Before you believe that everything went ok, please check the log file +for errors: \GNU \cmdname{make} always uses the string \samp{***} +whenever a command fails. Also, check if all the programs were built: + +\begin{alltt} +> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} +> \Ucom{ls | wc} +\end{alltt} +The result should be over 200 (you can check the exact number with the +\dirname{bin} directory contents in the distribution). + +If you need special privileges for \texttt{make install}, you can +separate the \samp{make world} into two different runs, like this: +\begin{alltt} +> \Ucom{make all} +> \Ucom{su} +> \Ucom{make install strip} +\end{alltt} + +After you've installed your new binaries, you should follow the normal +post-installation procedures, given in section~\ref{sec:postinstall} +(\p.\pageref{sec:postinstall}). + +Also, if you'd like to make your binaries available to others, please +contact us. We'll be happy to put them on the \TL\ web pages. +\end{comment} + +\ifx\HCode\undefined\else\HCode{} +\section{Acknowledgements} + +\TL{} is a joint effort by virtually all of the \TeX{} user groups. +This edition of \TL{} was overseen by Karl Berry. The other principal +contributors, past and present, are listed below. + +\begin{itemize*} + +\item The English, German, Dutch, and Polish \TeX{} user groups +(\acro{TUG}, \acro{DANTE} e.V., \acro{NTG}, and \acro{GUST}, +respectively), which provide the necessary technical and administrative +infrastructure. Please join the \TeX\ user group near you! (See +\url{http://tug.org/usergroups.html}.) + +\item The \acro{CTAN} team, most notably Robin Fairbairns, Jim Hef{}feron, +and Rainer Sch\"opf, which distributes the \TL{} images and provides the +common infrastructure for package updates, upon which \TL{} depends. + +\item Peter Breitenlohner (and the \eTeX\ team) for the stable foundation +of future \TeX's, and Peter specifically for stellar help with the GNU +autotools usage throughout \TL. + +\item Thomas Esser, without whose marvelous \teTeX{} package \TL{} +would have never existed. + +\item Michel Goossens, who co-authored the original documentation. + +\item Eitan Gurari, whose \TeX4ht was used to create the \HTML{} +version of this documentation, and who worked tirelessly to improve +it at short notice. + +\item \Thanh, Martin Schr\"oder, and the pdf\TeX\ team +(\url{http://pdftex.org}) for continuing enhancements of \TeX's +abilities. + +\item Hans Hagen, for much testing and making his \ConTeXt\ format +(\url{http://pragma-ade.com}) work within \TL's framework. + +\item Hartmut Henkel, for significant development contributions to +pdf\TeX\, Lua\TeX, and more. + +\item Taco Hoekwater, for renewed development efforts on MetaPost and +(Lua)\TeX\ (\url{http://luatex.org}) itself, and for incorporating +\ConTeXt\ into \TL. + +\item Pawe{\l} Jackowski, for the Windows installer \cmdname{tlpm}, +and Tomasz {\L}uczak, for \cmdname{tlpmgui}, used in past releases. + +\item Akira Kakuto, for providing the Windows +binaries from his \acro{W32TEX} distribution for Japanese \TeX\ +(\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}), and many +other contributions. + +\item Jonathan Kew and \acro{SIL}, for the major new development of +\XeTeX{} and taking the time and trouble to integrate it in \TL{}, as +well as the initial version of the Mac\TeX\ installer. + +\item Dick Koch, for maintaining Mac\TeX\ (\url{http://tug.org/mactex}) +in very close tandem with \TL{}, and for his great good cheer in doing +so. + +\item Reinhard Kotucha, for major contributions to the \TL{} 2008 +infrastructure and installer, as well as Windows research efforts, the +\texttt{getnonfreefonts} script, and more. + +\item Siep Kroonenberg, also for major contributions to the \TL{} 2008 +infrastructure and installer, especially on Windows, and for the bulk of +work updating this manual describing the new features. + +\item Petr Ol\v{s}ak, who coordinated and checked all the Czech and Slovak +material very carefully. + +\item Toshio Oshima, for his \cmdname{dviout} previewer for Windows. + +\item Manuel P\'egouri\'e-Gonnard, for helping with package updates, +documentation improvements, and \cmdname{tldoc} development. + +\item Fabrice Popineau, for the original Windows support in \TL{} and +work on the French documentation. + +\item Norbert Preining, the principal architect of the \TL{} 2008 +infrastructure and installer, and also for coordinating the Debian +version of \TL{} (together with Frank K\"uster), making many suggestions +along the way. + +\item Sebastian Rahtz, for originally creating \TL{} and maintaining it +for many years. + +\item Vladimir Volovich, for substantial help with porting and other +maintenance issues, and especially for making it feasible to include +\cmdname{xindy}. + +\item Staszek Wawrykiewicz, the principal tester for all of \TL{}, +and coordinator of the many major Polish contributions: fonts, Windows +installation, and more. + +\item Olaf Weber, for his patient maintenance of \Webc. + +\item Gerben Wierda, for creating and maintaining the \MacOSX\ support, +and much integration and testing. + +\item Graham Williams, on whose work the \TeX\ Catalogue of packages depends. + +\end{itemize*} + +Builders of the binaries: +Reinhard Kotucha (\pkgname{x86\_64-linux}), +Tim Arnold (\pkgname{hppa-hpux}), +Randy Au (\pkgname{amd64-freebsd}), +Edd Barrett (\pkgname{i386-openbsd}), +Karl Berry (\pkgname{i386-linux}), +Akira Kakuto (\pkgname{win32}), +Dick Koch (\pkgname{universal-darwin}), +Manfred Lotz (\pkgname{i386-freebsd}), +Norbert Preining (\pkgname{alpha-linux}), +Arthur Reutenauer (\pkgname{sparc-linux}), +Thomas Schmitz (\pkgname{powerpc-linux}), +Apostolos Syropoulos (\pkgname{i386-solaris}), +Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-solaris}), +Olaf Weber (\pkgname{mips-irix}). +For information on the \TL{} build process, see +\url{http://tug.org/texlive/build.html}. + +Documentation and translation updates: +Karl Berry (English), +Daniel Flipo (French), +Klaus H\"oppner (German), +Petr Sojka \& Jan Busa (Czech\slash Slovak), +Boris Veytsman (Russian), +Staszek Wawrykiewicz (Polish). The \TL{} documentation web page +is \url{http://tug.org/texlive/doc.html}. + +Of course the most important acknowledgement must go to Donald Knuth, +first for inventing \TeX, and then for giving it to the world. + + + +\section{Release history} +\label{sec:history} + +\subsection{Past} + +Discussion began in late 1993 when the Dutch \TeX{} Users Group was +starting work on its 4All\TeX{} \CD{} for \acro{MS-DOS} users, and it +was hoped at that time to issue a single, rational, \CD{} for all +systems. This was too ambitious a target for the time, but it did spawn +not only the very successful 4All\TeX{} \CD{}, but also the \acro{TUG} +Technical Council working group on a \emph{\TeX{} Directory Structure} +(\url{http://tug.org/tds}), which specified how to create consistent and +manageable collections of \TeX{} support files. A complete draft of the +\TDS{} was published in the December 1995 issue of \textsl{TUGboat}, and +it was clear from an early stage that one desirable product would be a +model structure on \CD{}. The distribution you now have is a very direct +result of the working group's deliberations. It was also clear that the +success of the 4All\TeX{} \CD{} showed that Unix users would benefit +from a similarly easy system, and this is the other main strand of +\TL. + +We first undertook to make a new Unix-based \TDS{} \CD{} in the autumn +of 1995, and quickly identified Thomas Esser's \teTeX{} as the ideal +setup, as it already had multi-platform support and was built with +portability across file systems in mind. Thomas agreed to help, and work +began seriously at the start of 1996. The first edition was released in +May 1996. At the start of 1997, Karl Berry completed a major new release +of Web2c, which included nearly all the features which Thomas Esser had +added in \teTeX, and we decided to base the 2nd edition of the \CD{} on +the standard \Webc, with the addition of \teTeX's \texttt{texconfig} +script. The 3rd edition of the \CD{} was based on a major revision of +\Webc, 7.2, by Olaf Weber; at the same time, a new revision of \teTeX +was being made, and \TL{} included almost all of its features. The +4th edition followed the same pattern, using a new version of \teTeX, +and a new release of \Webc{} (7.3). The system now included a complete +Windows setup. + +For the 5th edition (March 2000) many parts of the \CD{} were revised +and checked, updating hundreds of packages. Package details were stored +in XML files. But the major change for \TeX\ Live 5 was that all +non-free software was removed. Everything in \TL{} is now intended +to be compatible with the Debian Free Software Guidelines +(\url{http://www.debian.org/intro/free}); we have done our best to check +the license conditions of all packages, but we would very much +appreciate hearing of any mistakes. + +The 6th edition (July 2001) had much more material updated. The major +change was a new install concept: the user could select a more exact set +of needed collections. Language-related collections were completely +reorganized, so selecting any of them installs not only macros, fonts, +etc., but also prepares an appropriate \texttt{language.dat}. + +The 7th edition of 2002 had the notable addition of \MacOSX{} support, +and the usual myriad of updates to all sorts of packages and +programs. An important goal was integration of the source back with +\teTeX, to correct the drift apart in versions~5 and~6. + +\subsubsection{2003} + +In 2003, with the continuing flood of updates and additions, we found +that \TL{} had grown so large it could no longer be contained on a +single \CD, so we split it into three different distributions (see +section~\ref{sec:tl-coll-dists}, \p.\pageref{sec:tl-coll-dists}). In +addition: + +\begin{itemize*} +\item At the request of the \LaTeX{} team, we changed the standard + \cmdname{latex} and \cmdname{pdflatex} commands to now use \eTeX{} (see + \p.\pageref{text:etex}). +\item The new Latin Modern fonts were included (and are recommended). +\item Support for Alpha \acro{OSF} was removed + (\acro{HPUX} support was removed previously), since no one had (or + volunteered) hardware available on which to compile new binaries. +\item Windows setup was substantially changed; for the first time + an integrated environment based on XEmacs was introduced. +\item Important supplementary programs for Windows + (Perl, Ghost\-script, Image\-Magick, Ispell) are now installed + in the \TL{} installation directory. +\item Font map files used by \cmdname{dvips}, \cmdname{dvipdfm} + and \cmdname{pdftex} are now generated by the new program + \cmdname{updmap} and installed into \dirname{texmf/fonts/map}. +\item \TeX{}, \MF{}, and \MP{} now, by default, output most input + characters (32 and above) as themselves in output (e.g., + \verb|\write|) files, + log files, and the terminal, i.e., \emph{not} translated using the + \verb|^^| notation. In \TL{}~7, this translation was + dependent on the system locale settings; now, locale settings do + not influence the \TeX{} programs' behavior. If for some reason + you need the \verb|^^| output, rename the file + \verb|texmf/web2c/cp8bit.tcx|. (Future releases will have cleaner + ways to control this.) +\item This documentation was substantially revised. +\item Finally, since the edition numbers had grown unwieldy, + the version is now simply identified by the year: \TL{} 2003. +\end{itemize*} + + +\subsubsection{2004} + +2004 saw many changes: + +\begin{itemize} + +\item If you have locally-installed fonts which use their own +\filename{.map} or (much less likely) \filename{.enc} support files, you +may need to move those support files. + +\filename{.map} files are now searched for in subdirectories of +\dirname{fonts/map} only (in each \filename{texmf} tree), along the +\envname{TEXFONTMAPS} path. Similarly, \filename{.enc} files are now +searched for in subdirectories of \dirname{fonts/enc} only, along the +\envname{ENCFONTS} path. \cmdname{updmap} will attempt to warn about +problematic files. + +For methods of handling this and other information, please see +\url{http://tug.org/texlive/mapenc.html}. + +\item The \TK\ has been expanded with the addition of a \MIKTEX-based +installable \CD, for those who prefer that implementation to Web2C. +See section~\ref{sec:overview-tl} (\p.\pageref{sec:overview-tl}). + +\item Within \TL, the single large \dirname{texmf} tree of previous +releases has been replaced by three: \dirname{texmf}, +\dirname{texmf-dist}, and \dirname{texmf-doc}. See +section~\ref{sec:tld} (\p.\pageref{sec:tld}), and the \filename{README} +files for each. + +\item All \TeX-related input files are now collected in +the \dirname{tex} subdirectory of \dirname{texmf*} trees, rather than +having separate sibling directories \dirname{tex}, \dirname{etex}, +\dirname{pdftex}, \dirname{pdfetex}, etc. See +\CDref{texmf-doc/doc/english/tds/tds.html\#Extensions} +{\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}. + +\item Helper scripts (not meant to be invoked by users) are now located +in a new \dirname{scripts} directory of \dirname{texmf*} trees, and +searched for via \verb|kpsewhich -format=texmfscripts|. So if you have +programs which call such scripts, they'll need to be adjusted. See +\CDref{texmf-doc/doc/english/tds/tds.html\#Scripts} +{\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}. + +\item Almost all formats leave most characters printable as +themselves via the ``translation file'' \filename{cp227.tcx}, instead of +translating them with the \verb|^^| notation. Specifically, characters +at positions 32--256, plus tab, vertical tab, and form feed are +considered printable and not translated. The exceptions are plain \TeX\ +(only 32--126 printable), \ConTeXt\ (0--255 printable), and the +\OMEGA-related formats. This default behavior is almost the same as in +\TL\,2003, but it's implemented more cleanly, with more possibilities +for customization. See \CDref{texmf/doc/web2c/web2c.html\#TCX-files} +{\texttt{texmf/doc/web2c/web2c.html\#TCX-files}}. +(By the way, with Unicode input, \TeX\ may output partial character +sequences when showing error contexts, since it is byte-oriented.) + +\item \textsf{pdfetex} is now the default engine for all formats +except (plain) \textsf{tex} itself. (Of course it generates \acro{DVI} +when run as \textsf{latex}, etc.) This means, among other things, that +the microtypographic features of \textsf{pdftex} are available in +\LaTeX, \ConTeXt, etc., as well as the \eTeX\ features +(\OnCD{texmf-dist/doc/etex/base/}). + +It also means it's \emph{more important than ever} to use the +\pkgname{ifpdf} package (works with both plain and \LaTeX) or equivalent +code, because simply testing whether \cs{pdfoutput} or some other +primitive is defined is not a reliable way to determine if \acro{PDF} +output is being generated. We made this backward compatible as best we +could this year, but next year, \cs{pdfoutput} may be defined even when +\acro{DVI} is being written. + +\item pdf\TeX\ (\url{http://pdftex.org}) has many new features: + + \begin{itemize*} + + \item \cs{pdfmapfile} and \cs{pdfmapline} provide font map support + from within a document. + + \item Microtypographic font expansion can be used more easily.\\ + \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} + + \item All parameters previously set through the special configuration + file \filename{pdftex.cfg} must now be set through primitives, + typically in \filename{pdftexconfig.tex}; \filename{pdftex.cfg} is no + longer supported. Any extant \filename{.fmt} files must be redumped + when \filename{pdftexconfig.tex} is changed. + + \item See the pdf\TeX\ manual for more: \OnCD{texmf-dist/doc/pdftex/manual/pdftex-a.pdf}. + + \end{itemize*} + +\item The \cs{input} primitive in \cmdname{tex} (and \cmdname{mf} and +\cmdname{mpost}) now accepts double quotes containing spaces and other +special characters. Typical examples: +\begin{verbatim} +\input "filename with spaces" % plain +\input{"filename with spaces"} % latex +\end{verbatim} +See the Web2C manual for more: \OnCD{texmf/doc/web2c}. + +\item enc\TeX\ support is now included within Web2C and consequently all +\TeX\ programs, via the \optname{-enc} option\Dash \emph{only when +formats are built}. enc\TeX\ supports general re-encoding of input and +output, enabling full support of Unicode (in \acro{UTF}-8). See +\OnCD{texmf-dist/doc/generic/enctex/} and +\url{http://www.olsak.net/enctex.html}. + +\item Aleph, a new engine combining \eTeX\ and \OMEGA, is available. +A little information is available in \OnCD{texmf-dist/doc/aleph/base} +and \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph}. The +\LaTeX-based format for Aleph is named \textsf{lamed}. + +\item The latest \LaTeX\ release has a new version of the +\acro{LPPL}\Dash now officially a Debian-approved license. Assorted +other updates, see the \filename{ltnews} files in +\OnCD{texmf-dist/doc/latex/base}. + +\item \cmdname{dvipng}, a new program for converting \acro{DVI} to +\acro{PNG} image files, is included. See \OnCD{texmf/doc/man/man1/dvipng.1}. + +\item We reduced the \pkgname{cbgreek} package to a ``medium'' sized set +of fonts, with the assent and advice of the author (Claudio Beccari). +The excised fonts are the invisible, outline, and transparency ones, +which are relatively rarely used, and we needed the space. The full set +is of course available from \acro{CTAN} +(\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). + +\item \cmdname{oxdvi} has been removed; just use \cmdname{xdvi}. + +\item The \cmdname{ini} and \cmdname{vir} commands (links) for +\cmdname{tex}, \cmdname{mf}, and \cmdname{mpost} are no longer created, +such as \cmdname{initex}. The \cmdname{ini} functionality has been +available through the command-line option \optname{-ini} for years now. + +\item \textsf{i386-openbsd} platform support was removed. Since the +\pkgname{tetex} package in the \acro{BSD} Ports system is available, and +\acro{GNU/}Linux and Free\acro{BSD} binaries were available, it seemed +volunteer time could be better spent elsewhere. + +\item On \textsf{sparc-solaris} (at least), you may have to set the +\envname{LD\_LIBRARY\_PATH} environment variable to run the +\pkgname{t1utils} programs. This is because they are compiled with C++, +and there is no standard location for the runtime libraries. (This is +not new in 2004, but wasn't previously documented.) Similarly, on +\textsf{mips-irix}, the \acro{MIPS}pro 7.4 runtimes are required. + +\end{itemize} + +\subsubsection{2005} + +2005 saw the usual huge number of updates to packages and programs. +The infrastructure stayed relatively stable from 2004, but inevitably +there were some changes there as well: + +\begin{itemize} + +\item New scripts \cmdname{texconfig-sys}, \cmdname{updmap-sys}, and + \cmdname{fmtutil-sys} were introduced, which modify the + configuration in the system trees. The \cmdname{texconfig}, + \cmdname{updmap}, and \cmdname{fmtutil} scripts now modify + user-specific files, under \dirname{$HOME/.texlive2005}. + +\item Corresponding new variables \envname{TEXMFCONFIG} and + \envname{TEXMFSYSCONFIG} to specify the trees where configuration + files (user or system, respectively) are found. Thus, you may + need to move personal versions of \filename{fmtutil.cnf} and + \filename{updmap.cfg} to these places; another option is to + redefine \envname{TEXMFCONFIG} or \envname{TEXMFSYSCONFIG} in + \filename{texmf.cnf}. In any case the real location of these files + and the values of \envname{TEXMFCONFIG} and \envname{TEXMFSYSCONFIG} + must agree. + See section~\ref{sec:texmftrees}, \p.\pageref{sec:texmftrees}. + +\item Last year, we kept \verb|\pdfoutput| and other primitives undefined + for \dvi\ output, even though the \cmdname{pdfetex} program was + being used. This year, as promised, we undid that compatibility + measure. So if your document uses \verb|\ifx\pdfoutput\undefined| + to test if PDF is being output, it will need to be changed. You + can use the package \pkgname{ifpdf.sty} (which works under both + plain \TeX\ and \LaTeX) to do this, or steal its logic. + +\item Last year, we changed most formats to output (8-bit) characters as + themselves (see previous section). The new TCX file + \filename{empty.tcx} now provides an easier way to get the + original \verb|^^| notation if you so desire, as in: +\begin{verbatim} +latex --translate-file=empty.tcx yourfile.tex +\end{verbatim} + +\item The new program \cmdname{dvipdfmx} is included for translation of + DVI to PDF; this is an actively maintained update of + \cmdname{dvipdfm} (which is also still available for now, though + no longer recommended). + +\item The new programs \cmdname{pdfopen} and \cmdname{pdfclose} are included + to allow reloading of pdf files in the Adobe Acrobat Reader without + restarting the program. (Other pdf readers, notably \cmdname{xpdf}, + \cmdname{gv}, and \cmdname{gsview}, have never suffered from this + problem.) + +\item For consistency, the variables \envname{HOMETEXMF} and + \envname{VARTEXMF} have been renamed to \envname{TEXMFHOME} and + \envname{TEXMFSYSVAR}, respectively. There is also + \envname{TEXMFVAR}, which is by default user-specific. See the + first point above. + +\end{itemize} + + +\subsubsection{2006--2007} + +In 2006--2007, the major new addition to \TL{} was the \XeTeX{} program, +available as the \texttt{xetex} and \texttt{xelatex} programs; see +\url{http://scripts.sil.org/xetex}. + +MetaPost also received a notable update, with more planned for the +future (\url{http://tug.org/metapost/articles}), likewise pdf\TeX{} +(\url{http://tug.org/applications/pdftex}). + +The \TeX\ \filename{.fmt} (high-speed format) and the similar files for +MetaPost and \MF\ are now stored in subdirectories of \dirname{texmf/web2c}, +instead of in the directory itself (although the directory is still +searched, for the sake of existing \filename{.fmt}'s). The +subdirectories are named for the `engine' in use, such as \filename{tex} +or \filename{pdftex} or \filename{xetex}. This change should be +invisible in normal use. + +The (plain) \texttt{tex} program no longer reads \texttt{\%\&} first +lines to determine what format to run; it is the pure Knuthian \TeX. +(\LaTeX\ and everything else do still read \texttt{\%\&} lines). + +Of course the year also saw (the usual) hundreds of other updates to +packages and programs. As usual, please check \acro{CTAN} +(\url{http://www.ctan.org}) for updates. + +Internally, the source tree is now stored in Subversion, with a standard +web interface for viewing the tree, as linked from our home page. +Although not visible in the final distribution, we expect this will +provide a stable development foundation for future years. + +Finally, in May 2006 Thomas Esser announced that he would no longer be +updating te\TeX{} (\url{http://tug.org/tetex}). As a result, there was +been a surge of interest in \TL{}, especially among \GNU/Linux +distributors. (There is a new \texttt{tetex} installation scheme in +\TL{}, which provides an approximate equivalent.) We hope this will +eventually translate to improvements in the \TeX\ environment for +everyone. + +\medskip \noindent +Final note on the past: all releases of \TL{}, along with ancillary +material such as \CD\ labels, are available at +\url{ftp://tug.org/historic/systems/texlive}. + +\ifx\HCode\undefined\else\HCode{} +\subsection{Present} +\label{sec:tlcurrent} + +In 2008, the entire \TL{} infrastructure was redesigned and +reimplemented. Complete information about an installation is now stored +in a plain text file \filename{tlpkg/texlive.tlpdb}. + +Among other things, this finally makes possible upgrading a \TL{} +installation over the Internet after the initial installation, a feature +MiK\TeX\ has provided for many years. We expect to regularly update new +packages as they are released to \CTAN. + +The major new engine Lua\TeX\ (\url{http://luatex.org}) is included; +besides a new level of flexibility in typesetting, this provides an +excellent scripting language for use both inside and outside of \TeX\ +documents. + +Support among Windows and the Unix-based platforms is now much more +uniform. In particular, most Perl and Lua scripts are now available on +Windows, using the Perl internally distributed with \TL. + +The new \cmdname{tlmgr} script (section~\ref{sec:tlmgr}) is the +general interface for managing \TL{} after the initial installation. +It handles package updates and consequent regeneration of formats, map +files, and language files, optionally including local additions. + +With the advent of \cmdname{tlmgr}, the \cmdname{texconfig} actions to +edit the format and hyphenation configuration files are now disabled. + +The \cmdname{xindy} indexing program +(\url{http://xindy.sourceforge.net/}) is now included on most platforms. + +The \cmdname{kpsewhich} tool can now report all matches for a given file +(option \optname{--all}) and limit matches to a given subdirectory +(option \optname{--subdir}). + +The \cmdname{dvipdfmx} program now includes functionality to extract +bounding box information, via the command name \cmdname{extractbb}; this +was one of the last features provided by \cmdname{dvipdfm} not in +\cmdname{dvipdfmx}. + +The font aliases \filename{Times-Roman}, \filename{Helvetica}, and so on +have been removed. Different packages expected them to behave +differently (in particular, to have different encodings), and there was +no good way to resolve this. + +The \pkgname{platex} format has been removed, to resolve a name conflict +with a completely different Japanese \pkgname{platex}; the +\pkgname{polski} package is now the main Polish support. + +Internally, the \web\ string pool files are now compiled into the +binaries, to ease upgrades. + +Finally, the changes made by Donald Knuth in his `\TeX\ tuneup of 2008' +are included in this release. See +\url{http://tug.org/TUGboat/Articles/tb29-2/tb92knut.pdf}. + + +\subsection{Future} + +\emph{\TL{} is not perfect!} (And never will be.) We intend to +continue to release new versions, and would like to provide more help +material, more utilities, more installation programs, and (of course) an +ever-improved and better-checked tree of macros and fonts. This work is +all done by hard-pressed volunteers in their limited spare time, and a +great deal remains to be done. Please see +\url{http://tug.org/texlive/contribute.html}. + +Please send corrections, suggestions, and offers of help to: +\begin{quote} +\email{tex-live@tug.org} \\ +\url{http://tug.org/texlive} +\end{quote} + +\medskip +\noindent \textsl{Happy \TeX ing!} + +\end{document} diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/live-tl7.tex b/Master/texmf/doc/texlive/source/texlive-en/archive/live-tl7.tex new file mode 100644 index 00000000000..1e8ee77312b --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/live-tl7.tex @@ -0,0 +1,3554 @@ +% +% change history (started May 13th 2002) +% 2002/05/13: added tex-langafrican to list of collections +% 2002/05/14: corrected example files, other small errors noted by Volker +% 2002/05/18: win32 updates, by Fabrice +% 2002/05/25: remove mention of sizes, and bsr-interpolated; add Gutenberg +\documentclass{article} +\advance\textwidth by 1in +\advance\oddsidemargin by -1in +\advance\evensidemargin by -1in +\newsavebox{\warnbox} +\def\Q#1{\par\vskip6pt\leftline{#1}\par} +\setcounter{tocdepth}{2} +\pretolerance=1000 +\tolerance=1500 +\hbadness=3000 +\vbadness=3000 +\hyphenpenalty=400 +\renewcommand{\topfraction}{0.85} +\renewcommand{\floatpagefraction}{0.86} +\renewcommand{\textfraction}{0.1} +\setcounter{topnumber}{5} +\setcounter{totalnumber}{5} +\def\eTeX{$\varepsilon$-\TeX} +\def\Dash{---} +\def\hyph{-} +\def\OMEGA{$\Omega$} +\def\bs{{\protect\normalfont\ttfamily\char'134}} +\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} +\def\La{La} +\let\textsl\textit +\let\sl\it +\let\slfamily\itfamily +\def\ttdefault{cmtt} +\usepackage{tex-live} +\begin{document} +%\makeatletter\@ifundefined{HRestore}{}{\HRestore\noalign}\makeatother +\author{Sebastian Rahtz\\ +\texttt{sebastian.rahtz@oucs.ox.ac.uk} +%Michel Goossens\\ +%\texttt{m.goossens@cern.ch} +} +\title{The \protect\TeX\ Live Guide, 7th edition} +\date{May 2002} +\maketitle +\begin{multicols}{2} +\tableofcontents +\listoftables +\end{multicols} +\section{Introduction}\label{sec:intro} +This documentation describes the + main features of the \TeXLive{} 7 \CD{}\Dash a \TeX{}/\LaTeX{} + distribution for Unix, Linux, MacOSX, and Windows32 systems that includes + \TeX{}, \LaTeXe{}, \MF, \MP, \cmdname{Makeindex}, and \BibTeX{}; and + a wide-ranging set of macros, fonts and documentation conforming to + the \emph{\TeX{} Directory Standard} (\TDS{})\Dash which can be used + with nearly every \TeX{} setup. + + This \TeX{} package uses the \Webc{} version 7.3.7 + implementation of the programs, which tries to make \TeX{}ing as + easy as possible, and takes full advantage of the efficient and + highly customizable \KPS{} library from Karl Berry and Olaf Weber. + It can be run either directly from the \CD{} or installed on a hard + disk. + +Most of the runnable systems on the \CD{} include a large set of +drivers and support programs for \TeX, including \cmdname{dvips} +(PostScript driver), \cmdname{dvipdfm} (dvi to PDF), +\cmdname{xdvi} (X Windows previewer), +\cmdname{dvilj} (HP LaserJet driver), \cmdname{lacheck} (\LaTeX{} +syntax checker), \cmdname{tex4ht} (\TeX{} to HTML converter), +\cmdname{dviconcat} and \cmdname{dviselect}, \cmdname{dv2dt} and + \cmdname{dt2dv} (\texttt{dvi} to ASCII and vice versa), and Angus + Duggan's PostScript utilities. + +\subsection{Extensions to \TeX} + +The \TeXLive{} runnable systems contain three extended versions of +standard \TeX: +\begin{enumerate} +\item \eTeX, which adds a small but powerful set of new primitives, + and the \TeXXeT{} extensions for left to right typesetting; in + default mode, \eTeX{} is 100\% compatible with ordinary \TeX. See + \OnCD{texmf/doc/etex/base/etex_man.pdf} on the \CD{} for details. +\item pdf\TeX, which can optionally write Acrobat PDF format instead + of \dvi{}. You will find the user manual in + \OnCD{texmf/doc/pdftex/pdftex-l.pdf}. The + file \OnCD{texmf/doc/pdftex/samplepdf/samplepdf.tex} shows how it is + used. The \LaTeX{} \pkgname{hyperref} package has an option + `\optname{pdftex}', which turns on all the program features. +\item \OMEGA{} (Omega), which works internally with 16-bit characters, + using Unicode; this allows it to directly work with almost all the + world's scripts simultaneously. It also supports dynamically loaded + `\OMEGA{} Translation Processes' (\acro{OTP}s), which allow the user + to define complex transformations to be performed on arbitrary + streams of input. See \OnCD{texmf/doc/omega/base/doc-1.8.tex} for some + (not necessarily up to date) documentation. +\end{enumerate} +\eTeX{} (version 2.1) is stable, although subsequent releases will add +new functionality. pdf\TeX{} (version 1.00b) is also stable, +but is still being improved. +\OMEGA{} (version 1.23) is under development; the version +on this \CD{} is that current as of May 2002. + + +\section[Structure and contents of the CD-ROM]{Structure + and contents of the \protect\CD{}} +The important \CD{} top-level directories are listed below. +\begin{description} +\item[bin] The \TeX{} family programs, arranged in separate platform + directories. +\item[Books] Examples related to some books about \TeX. +\item[FAQ] Frequently Asked Questions, in English, French, and German. +\item[MacOSX] Support programs for MacOSX users +\item[info] Documentation in \acro{GNU} `info' format for the \TeX{} + system. +\item[man] Documentation in the form of Unix man pages for the \TeX{} + system. +\item[setupw32] directory contains material for installation and use + under Windows (see section \ref{sec:wintex} on p.~\pageref{sec:wintex}). +\item[source] The source of all programs, including the main \Webc{} + \TeX{} and \MF{} distributions. These are stored in a bzip2-compressed + tar archive. +\item[support] Various bits of \TeX-related software which are + \emph{not} installed by default, support programs, and a complete + distribution of \cmdname{Ghostscript} version 7.05. + You can find here some other programs (editors, \TeX\ shells), which + are usually absent from Windows installations, dedicated for beginners. + They can be installed with the \texttt{TeXSetup.exe} Windows installation + program. +\item[texmf] The main support tree of macros, fonts and documentation; +\item[usergrps] Material about \TeX\ User Groups. +\end{description} + +There are also two installation scripts for Unix systems, +\texttt{install-cd.sh} and \texttt{install-pkg.sh}; we discuss +them on in section \ref{sec:install} on p.~\pageref{sec:install}. + +\subsection[Packages and collections]{Packages and collections} +\label{packages} +The \TeXLive{} \texttt{texmf} tree consists of various `collections', +each of which refers to a set of `packages', of which there are over 700 +on the \CD{}. Normal installation allows the +user to copy all of a collection to a local hard disk from the \CD{}, but +it is also possible to install just one package of a collection. + +The collections add functionality to a \TeX\ system. One of them, named +`tex-basic', is necessary for almost all \TeX\ tasks, +and two others, called `tex-latex' and `tex-pdftex' are highly +recommended for most users. All others are optional. +The collections (defined by XML files in \texttt{texmf/tpm/collections}) +and their short descriptions are listed below. + +\begin{description} + \item[tex-basic] + These files are regarded as basic for any \TeX\ system, covering +plain \TeX\ macros, Computer Modern fonts, and configuration for common +drivers. + \item[tex-bibtexextra] + Additional, extensive libraries of BibTeX styles and bibliographies. + \item[tex-chemistry] + Essential chemistry + \item[tex-context] + Hans Hagen's powerful macro package, ConText + \item[tex-documentation] + Assorted useful documentation and guides + \item[tex-etex] + Support files for an extended \TeX\ + \item[tex-extrabin] + Various useful, but non-essential, support programs. Includes + programs and macros for texinfo system; programs for dvi file + manipulation, etc. + \item[tex-fontbin] + Programs for conversion between font formats, testing fonts + (virtual fonts stuff, .gf and .pk manipulation, + mft, fontinst, etc.) + \item[tex-fontsextra] + All sorts of extra fonts + \item[tex-formatsextra] + A collection of \TeX\ `formats', ie large-scale +macro packages designed to be dumped into .fmt file + \item[tex-games] + Setups for typesetting various board games, including chess + \item[tex-genericextra] + This is a mixed bag of macro packages and fonts which do not seem +to belong elsewhere + \item[tex-htmlxml] + Packages to convert \LaTeX\ to XML/HTML, and typeset XML/SGML + \item[tex-langafrican] + Support for some African scripts + \item[tex-langarmenian] + Essential armenian + \item[tex-langcjk] +Essential CJK (Chinese, Japanese, Korean) macros and fonts + \item[tex-langcroatian] + Essential croatian + \item[tex-langcyrillic] + Fonts and macro packages to typeset Cyrillic texts. + \item[tex-langczechslovak] + Pick this if you want Czech/Slovak fonts and other packages + \item[tex-langdanish] + Essential Danish + \item[tex-langdutch] + Essential Dutch + \item[tex-langfinnish] + Essential Finnish + \item[tex-langfrench] + Essential French + \item[tex-langgerman] + Essential German + \item[tex-langgreek] + Essential Greek + \item[tex-langhungarian] + Essential Hungarian + \item[tex-langindic] + Essential Indic + \item[tex-langitalian] + Essential Italian + \item[tex-langlatin] + Essential Latin + \item[tex-langmanju] + Essential Manju + \item[tex-langmongolian] + Essential mongolian + \item[tex-langnorwegian] + Essential Norwegian + \item[tex-langother] + Other languages + \item[tex-langpolish] + Pick this if you want Polish fonts and other packages + \item[tex-langportuguese] + Essential Portuguese + \item[tex-langspanish] + Essential Spanish + \item[tex-langswedish] + Essential Swedish + \item[tex-langtibetan] + Fonts and support for typesetting Tibetan + \item[tex-langukenglish] + Essential UK English + \item[tex-langvietnamese] + Essential Vietnamese + \item[tex-latex] + These packages are either mandated by the core \LaTeX\ team, +or very commonly recommended + \item[tex-latexextra] + A large collection of add-on packages for \LaTeX\ + \item[tex-mathextra] + Extra math + \item[tex-metapost] + MetaPost (and MetaFont) drawing packages + \item[tex-music] + Music typesetting packages + \item[tex-omega] + Omega, a 16-bit extended \TeX\ by John Plaice and Yannis Haralambous + \item[tex-pdftex] + Support files for Han The Thanh's variant of \TeX\ which can +generate PDF output + \item[tex-pictures] + Essential graphics + \item[tex-plainextra] + Plain \TeX\ extra macros + \item[tex-psfonts] + Essential psfonts + \item[tex-psutils] + Utilities to manipulate PostScript files + \item[tex-publishers] + Essential publishers + \item[tex-t1utils] + Utilities to manipulate Type1 fonts + \item[tex-texbooks] + Examples and other material from various books about TeX/LaTeX. + \item[tex-theses] + Macro packages from various Universities for their thesis styles + \item[tex-ttfutils] + Utilities to manipulate TrueType fonts + \item[win32-support] + You can choose individual tools from this collection. + There are many \TeX\ oriented editors, graphics files + toolsets, etc. +\end{description} + +The directory \texttt{texmf/tpm/packages} contains lists +of all files in each package (used by the installation programs). + +\section{Installation and use under Unix} +\label{sec:install} +You can use the \TeXLive{} \CD{} in three ways: +\begin{enumerate} +\item You can mount the \CD{} on your file system, run +the \texttt{install-cd.sh} script, and select the option \verb|| + (`do not install files, set up to run off CD-ROM'), + and run everything off the \CD; this takes very + little disk space, and gives you immediate access to everything on + the \CD; although the performance will not be optimal, it is + perfectly acceptable on, for instance, PCs running Linux. You could + also copy the entire CD contents to your hard disk and work in this way. +\item You can install all or part of the system to your local hard + disk; this is the best method for many people, if they have enough + disk space to spare (a minimum of about 100 megabytes, or 300 + megabytes for a recommended good-sized system). +\item You can install selected packages to work either with your + existing \TeX{} system or a \TeXLive{} system you installed earlier. +\end{enumerate} +Each of these methods is described in more detail in the following +sections. + +\ifSingleColumn +\begin{figure*} + \begin{center} + \leavevmode +\fi +\begin{warningbox} +\textbf{Warning: } This \CD{} is in ISO 9660 (High Sierra) format, +with Rock Ridge and Joliet extensions. In order to take full advantage +of the \CD{} on a Unix system, your system needs to be able to use +the Rock Ridge extensions. Please consult the documentation for your +\cmdname{mount} command to see if it is possible. If you have several +different machines on a local network, see if you can mount the +\CD{} on one which \emph{does} support Rock Ridge, and use this with +the others. + +\leavevmode\quad +Linux, FreeBSD, Sun, SGI and DEC Alpha systems should be able to use +the \CD{} with no problems. We would appreciate receiving detailed advice +from other system users who also succeed, for future versions of this +documentation. + +\leavevmode\quad +The discussion below about installation assumes you have been able to mount +the \CD{} with full Rock Ridge compatibility. +\end{warningbox} +\ifSingleColumn + \end{center} +\end{figure*} +\fi + +%\begin{addbymb} +\subsection[Pre-installation procedure for MacOSX users] +{Pre-installation procedure for MacOSX users} +If you do not run MacOSX, you should skip this section. + +The \texttt{install-cd.sh} script is a \emph{sh} script (begins with +``\verb=#!/bin/sh=''), but +on MacOSX \cmdname{sh} is unable to run it because +\cmdname{sh} is +emulated. However, \cmdname{bash} will run it. Unfortunately (again) +\cmdname{bash} is not +installed by default on MacOSX\footnote{there are some suggestions this will +change in the future and even +that \cmdname{bash} will be used to emulate \cmdname{sh}, +in which case it might be true +that in future versions of MacOSX, the script will just work.}. +\begin{enumerate} +\item\label{test-bash} (optional) See if \path|bash| is already installed. +Launch \path|Terminal| +(\path|/Applications/utilities/Terminal|) and type in a window +\begin{alltt} +>> \Ucom{rehash; which bash} +\end{alltt} +the answer will be: +\begin{itemize} +\item the bash location (e.g. \path|/bin/bash| or \path|/usr/local/bin/bash|) if installed; +\item \texttt{bash: command not found} if not installed. +\end{itemize} + +If bash is already installed, skip to \ref{std-install} + +\item bash installation: +\begin{description} +\item[Mac friendly procedure] +Look in the \path|MacOSX| directory of the \CD{} +for an image disk named \path|bash.dmg|. mount that +file by double-clicking it. The disk image (volume) will be mounted. +Then start the \path|i-Installer| application on that volume. You will be asked +to authenticate, if you have never seen that before, you might not have +enough privileges to install. Just enter your own user name and +password. Hit install. \path|bash| will be installed on your system. +\item[Terminal procedure] +\begin{enumerate} +\item Log in as an admin user, at least a user with Admin privileges or +sudo user or as the System Administrator. +\item Open the \path|MacOSX| directory on the \CD{} and copy +\path|bash.tar.gz| +to your home directory (\texttt{\~{}/}) +\item Then launch \path|Terminal| and type or copy/paste the +line below in a Terminal window): +\begin{alltt} +>> \Ucom{(cd /usr/local/; sudo tar xvzf ~/bash.tar.gz)} +\end{alltt} +type a carriage-return: you will be asked for your password, and +\path|bash| will be +installed. +\item Quit \path|Terminal|. +\end{enumerate} +\end{description} +\item Now after using either install method, goto \ref{test-bash}: +you must obtain \path|/usr/local/bin/bash|\ldots{} (if not, try to log out and in). +\item\label{std-install} The installation procedure is the +same on MacOSX than on other UNIX platforms (as MacOSX is UNIX, +that's quite normal!). Nevertheless, you should read what follows: +\begin{itemize} + \item Note that in all commands of the following sections, +\cmdname{sh} must be replaced by \texttt{sudo bash}: +\begin{alltt} +>> \Ucom{sh install-cd.sh} +\end{alltt} +becomes +\begin{alltt} +>> \Ucom{sudo bash install-cd.sh} +\end{alltt} +etc. +\item On MacOSX, cd are auto-mounted: you \emph{don't} need to use +\texttt{mount}. The \CD{} will be mounted in the \path|/Volumes/| +directory: in order to make it the current directory, you just have to +type in \path|Terminal|: +\begin{alltt} +>> \Ucom{cd /Volumes/TeXLive-7...} +\end{alltt} +(complete this line with the real name of the \CD{}: using +``auto completion'' by pressing the \texttt{} +key will do it). +\end{itemize} +\end{enumerate} +%\end{addbymb} + +\subsection[Running \protect\TeXLive{} from the CD-ROM]{Running \protect\TeXLive{} from the \protect\CD} +The organisation of \Webc{} means that you can run programs simply by +adding the appropriate directory under \path|bin| on the \CD{} to +your \texttt{PATH}, and the support files will all be found with no further +ado. The following shows the list of available systems and the +corresponding directories. \textbf{Only x86 Linux, Mac OSX, and + Windows are available on the default CD. You need to ask +for the Unix CD if you need the other systems.} + +\begin{flushleft} +\begin{tabular}{@{}l>{\ttfamily}ll} +Compaq Alpha Linux & alpha-linux & CD2\\ +Compaq Alphaev5 OSF 4.0d & alphaev5-osf4.0d & CD2\\ +HP9000 HPUX 10.20 & hppa2.0-hpux10.20 & CD2\\ +IBM RS 6000 AIX 4.2.* & rs6000-aix4.2.1.0 & CD2\\ +Intel x86 Solaris 2.8 & i386-solaris2.8 & CD2\\ +Intel x86 with GNU/Linux & i386-linux & CD1\\ +Mac OSX & powerpc-darwin5.3 & CD1\\ +Sun Sparc Solaris 2.7 & sparc-solaris2.7 & CD2\\ +Windows 9X/ME/NT/2K/XP & win32 & CD1\\ +\end{tabular} +\end{flushleft} + +You may worry that when you subsequently make fonts or change +configuration, things will go wrong because you cannot change files on +the \CD{}. However, you can maintain a parallel, writeable, \TeX{} +tree on your hard disk; this is searched before the main tree on the +\CD{}. The default location is \path|texmf-var| on the CD +(which does not exist!), so you \emph{must} override this by setting +the \texttt{VARTEXMF} environment variable. + + +Thus \emph{sh} or \emph{bash} users on an Intel PC +running Linux can mount the \TeXLive{} \CD{} on +\file{/mnt/cdrom} by issuing the command: + +\begin{alltt} +>> \Ucom{mount -t iso9660 /dev/cdrom /mnt/cdrom} +\end{alltt} +Then they should change the current directory to \path|/mnt/cdrom|, run +\begin{alltt} +>> \Ucom{sh install-cd.sh} +\end{alltt} +and select the option \verb|| (\emph{do not install files, set up to run +off CD-ROM}). After that, they should include the directory containing +the binaries for the given architecture into the search path +by updating the \texttt{PATH} variable. +\begin{verbatim} +PATH=/mnt/cdrom/bin/i386-linux:$PATH +export PATH +VARTEXMF=/usr/TeX/texmf-var +export VARTEXMF +\end{verbatim} +%\begin{addbymb} +\begin{description} + \item[MacOSX users] On MacOSX, the default shell is \texttt{tcsh}: +\begin{verbatim} +setenv PATH /Volumes//bin/powerpc-darwin5.3:${PATH} +setenv VARTEXMF /usr/TeX/texmf-var +\end{verbatim} +\end{description} +%\end{addbymb} +For convenience, these statements can also be entered into the +\texttt{.profile} script. +%\begin{addbymb} +(for \texttt{tcsh} on MacOSX, +\verb=~/Library/init/tcsh/rc.mine=). +%\end{addbymb} + +If in doubt, ask your local system support guru to help you work out +how to mount your \CD{} or which directory to use for your system. + +Appropriate support files will be installed on your hard disk the +first time you need them. You can edit and change local configuration +files which are stored to the directory designated +by \texttt{\$VARTEXMF}. Any format file that is needed +will be generated and stored here. + +%------------------------------------------------ +\subsection{Installing \protect\TeXLive{} to a hard disk} +All of the necessary steps to install all or part of the distribution +on your hard disk are achieved by mounting the \CD{}, changing to the +top-level directory, and typing: +\begin{alltt} +>> \Ucom{sh install-cd.sh} +\end{alltt} +(On some Unix systems, you may need to use \cmdname{sh5} or +\cmdname{bash}.) This script works by accessing lists of collections +and packages from the \CD{}, and trying to guess what sort of computer +system you are on. It should start by displaying the following: +\verbatiminput{../examples/ex1.tex} +It will then show the main control screen +(Figure~\ref{ins1}), which lets you change five +things: +\begin{enumerate} +\item the type of system you are on, or want to install for; +\item the \emph{installation scheme} you want to use (eg full, + recommended, basic etc) +\item the collections you want to change from +the installation scheme (they are organised into two sets: +\emph{standard collections} and \emph{language collections}); +\item the location on your hard disk to put the files; +\item some runtime behaviour features. +\end{enumerate} + +\begin{figure*} +\begin{center} +\ifnum\Status=2 +\boxedverbatiminput{../examples/ex2.tex} +\else +\begin{minipage}{0.8\textwidth} +\boxedverbatiminput{../examples/ex2.tex} +\end{minipage} +\fi +\caption{Main control screen}\label{ins1} +\end{center} +\end{figure*} + +You choose options by typing a letter or number and pressing `return'. +In the example, a Linux GNU/Linux system has been detected, the +default set of collections will be installed, and +the default installation directory is \path|/usr/TeX|; note +that the disk space required for the current installation +configuration is also displayed. If you make a suggested setup, you +need about 60 megabytes of disk free; however, the basic setup will +only take about 30 megabytes, and you can enhance it with selected +packages as you need them. + +%\begin{addbymb} +\begin{description} + \item[MacOSX users] Most frontends (\emph{TeXShop}, + \emph{ITeXMac}\ldots) use the \teTeX{} default location + which is \path|/usr/local/teTeX|, so, Mac users could find interest + in installing \TeXLive{} in \path|/usr/local/teTeX| +rather than in \path|/usr/TeX|. +\end{description} +%\end{addbymb} + +Under the directory you choose for installation, the installation +script will put the binaries in a subdirectory of \path|bin|, and the +support tree in \path|texmf|. An additional tree \path|texmf-var| +will contain copies of configuration files (except the main +\path|texmf.cnf|), which are to be modified by \path|texconfig| program. +This tree will also store generated format files for \TeX, \MF, etc. + +\begin{figure*} +\begin{center} +\ifnum\Status=2 +\boxedverbatiminput{../examples/ex3.tex} +\else +\begin{minipage}{.80\linewidth} +\footnotesize +\boxedverbatiminput{../examples/ex3.tex} +\end{minipage} +\fi +\caption{Selecting standard collections}\label{ins2} +\end{center} +\end{figure*} + +\begin{figure*} +\begin{center} +\ifnum\Status=2 +\boxedverbatiminput{../examples/ex4.tex} +\else +\begin{minipage}{.80\linewidth} +\footnotesize +\boxedverbatiminput{../examples/ex4.tex} +\end{minipage} +\fi +\caption{Selecting language collections}\label{ins3} +\end{center} +\end{figure*} + +When you choose || for \emph{standard collections}, you will see +the display of available collections (Figure \ref{ins2}). Each +collection --- TeX macro files, Metafont font families, and so on --- +consists of several packages. You can toggle their inclusion on or +off by pressing the key. Note that the selection letter keys are case +sensitive. + +When you choose || for \emph{language collections}, you will see +the display of available language support collections (Figure +\ref{ins3}). Each collection consists of several packages, which +provide features like hyphenation files and fonts. + +The || for \emph{options} item lets you decide whether to make new fonts +be created in another location (if you want the main package mounted +read-only for most users), and whether to make symbolic links for the +binaries, \cmdname{man} and \acro{GNU} \cmdname{info} pages in the `standard' +locations; you'll need `root' permissions for tasks to do this, of course. + +When you are finished, return to the main screen, and ask the +installation to start. It will take each of the collections and +systems that you requested, consult the list of files on the \CD{}, +and build a master list of files to transfer. These will then be +copied to your hard disk. If you installed a system, +an initialization sequence is now run +(creating format files, etc.). When this has finished, all you need do +is add the correct subdirectory of \texttt{bin} in the \TeX{} +installation to your path, and start using \TeX. If you want, you can +move the binaries up one level, e.g.\ from +\path|/usr/local/bin/alpha-osf3.2| +to \path|/usr/local/bin|; if you do this, however, you must +edit \path|texmf/web2c/texmf.cnf| (see Appendix~\ref{app:texmf.cnf}) +and change the line near the start which reads +\begin{verbatim} + TEXMFMAIN = $SELFAUTOPARENT +\end{verbatim} +to +\begin{verbatim} + TEXMFMAIN = $SELFAUTODIR +\end{verbatim} + +If you move the whole installation to another directory tree entirely, you +need to edit \envname{TEXMFMAIN} to specify the support tree explicitly, and +set \envname{TEXMFCNF} in your environment to \path|$TEXMFMAIN/texmf/web2c|. + +%------------------------------------------------ + +\subsection{Installing individual packages from \protect\TeXLive{} to a hard + disk} You may want to use the \TeXLive{} \CD{} to either update an +existing setup, or add features to an earlier installation from the +\CD{}. The main installation program is intended for the first time +only, and subsequently you should use the \texttt{install-pkg.sh} +script on the \CD{}. Run this by mounting the \CD{}, changing to +the mounted directory, and typing + +\begin{alltt} +>> \Ucom{sh install-pkg.sh \emph{options}} +\end{alltt} + + +The script supports nine options; the first four let you set the +individual package you want to install, the whole collection (i.e., +\texttt{tex-mathextra}), the name of the mounted \CD{} directory, and +the name of the directory containing the list files (normally these +latter two will be set automatically): + +\begin{tabular}{ll} +\texttt{-{}-package=}\emph{name} & \\ +\texttt{-{}-collection=}\emph{name} & \\ +\texttt{-{}-cddir=}\emph{name} & \\ +\texttt{-{}-listdir=}\emph{name} & \\ +\end{tabular} + +What actually happens is controlled by four more switches; the first +two allow you to exclude documentation or source files from the +installation, the third stops the default action of running +\texttt{mktexlsr} on completion to rebuild the file database, and +the last does nothing but list the files that would be installed: + +\begin{tabular}{ll} +\texttt{-{}-nodoc} & \\ +\texttt{-{}-nosrc} & \\ +\texttt{-{}-nohash} & \\ +\texttt{-{}-listonly} & \\ +\end{tabular} + +Finally, you can specify that, instead of installing the files, the script +should make a \cmdname{tar} archive in a specified location: + +\begin{tabular}{ll} +\texttt{-{}-archive=}\emph{name} & \\ +\end{tabular} + +Thus, if we simply wanted to see the files that make up the package +\pkgname{fancyhdr} before we installed it, our command and output would be +as follows: + +\begin{alltt} +\ifSingleColumn>> \Ucom{sh install-pkg.sh --package=fancyhdr --listonly} +\else>> \Ucom{sh install-pkg.sh -{}-package=fancyhdr \bs} +>> \Ucom{-{}-listonly} +\fi{} +texmf/doc/latex/fancyhdr/fancyhdr.dvi +texmf/doc/latex/fancyhdr/fancyhdr.tex +texmf/lists/fancyhdr +texmf/source/latex/fancyhdr/README +texmf/source/latex/fancyhdr/fancyheadings.new +texmf/tex/latex/fancyhdr/extramarks.sty +texmf/tex/latex/fancyhdr/fancyhdr.sty +texmf/tex/latex/fancyhdr/fixmarks.sty +\end{alltt} +Other examples of usage are: +\begin{itemize} +\item Install the \LaTeX{} package \texttt{natbib}: +\begin{alltt} +>> \Ucom{sh install-pkg.sh --package=natbib} +\end{alltt} +\item Install the \LaTeX{} package \texttt{alg} with no source files and no +documentation: +\begin{alltt} +\ifSingleColumn>> \Ucom{sh install-pkg.sh --package=alg --nosrc --nodoc} +\else>> \Ucom{sh install-pkg.sh -{}-package=alg \bs} +>> \Ucom{-{}-nosrc -{}-nodoc} +\fi\end{alltt} +\item Install all the packages available in the collection containing additional +Plain \TeX\ macros: +\begin{alltt} +>> \Ucom{sh install-pkg.sh --collection=tex-plainextra} +\end{alltt} +\item Place all files which are needed for PSTricks +in a \cmdname{tar} file in \path|/tmp|: +\begin{alltt} +\ifSingleColumn>> \Ucom{sh install-pkg.sh --package=pstricks --archive=/tmp/pstricks.tar} +\else +>> \Ucom{sh install-pkg.sh -{}-package=pstricks \bs} +>> \Ucom{-{}-archive=/tmp/pstricks.tar} +\fi\end{alltt} +\end{itemize} + +\subsection{The texconfig program} +\label{ssec:tex} + +After the installation program has copied all files to their final +locations, you can use a program called \cmdname{texconfig} that +allows you to configure the system to fit your local needs. This can +be called at any other time to change your setup, with a full-screen +(which requires the \cmdname{dialog} program, included as part of the +binary packages) or command-line interface. +It should be used for all maintenance, such as changes of installed +printers, or rebuilding the file database. Both modes have help text +to guide you through the facilities. + +\section{Installation and use under Windows} +\label{sec:wintex} +This section only applies to systems running Windows 9x, \acro{ME}, +\acro{NT}, \acro{2K} or \acro{XP}. + +It is also necessary to have your Windows set up so that it uses the +Microsoft Joliet extensions for reading \CD s; simply look at the +\CD{} in Explorer and see whether it shows long, mixed-case, file +names. If it does not, you cannot use the ready-to-run system on the +\CD. + +This Win32 \TeX{} systems includes a \texttt{dvi} previewer, +\textsf{Windvi}, which is similar in usage to the established Unix +\textsf{xdvi}. The documentation can be found in +\OnCD{texmf/doc/html/windvi/windvi.html}. + +\subsection[The TeXLive.exe program]{The \texttt{TeXLive.exe} program} + +\begin{figure*} + \begin{center} + \ifnum \Status=1 + \includegraphics[width=.7\textwidth]{../pictures/Welcome-to-TeXLive} + \else + \ifnum \Status=2 +\includegraphics[bb=20 20 575 432]{../pictures/Welcome-to-TeXLive.gif} + \else + \includegraphics[width=.7\textwidth]{../pictures/Welcome-to-TeXLive} + \fi + \fi + \end{center} + \caption{``Welcome to \TeXLive'' window}\label{graph:welcome} +\end{figure*} + +If your computer is configured to let the \CD{} autostart, then a +dialog box with a menu bar will popup on the screen, and you will have several choices +from there: +\begin{itemize} +\item Install \TeX{} on your hard disk, +\item Install TeX-oriented editors on your hard disk, +\item Install support packages on your hard disk (Ghostscript, NetPBM, + \ldots) +\item Do some maintenance on you \TeX{} system, +\item Remove the \TeX{} system, +\item Use \TeX{} off the \CD{}, +\item Cleanup the temporary files created on your hard disk when using + \TeX{} off the \CD{}, +\item Update some of the DLLs on your system, +\item Browse some documentation: \TeXLive{} documentation, TUG web + pages, \fpTeX web pages, +\item Run the \cmdname{TeXdocTK} application to find specific documentation. +\end{itemize} + +If your \CD{} does not autostart, you can explicitly run the program +by double clicking on \path|bin/win32/TeXLive.exe| on the \CD{} from +the explorer window. + +\subsection[Running \protect\TeXLive{} from the CD-ROM]{Running from +the \protect\CD{}} +You can run all the \TeX{} programs directly off the \CD, and have +access to all the macros and fonts immediately, at the price of a +slower performance than if you install on the hard disk. +To work effectively, one needs to modify +environment variables and to create some small auxiliary directories on a +hard disk. These directories will contain necessary configuration files +allowing the user to modify programs settings and to generate a necessary +format file. Moreover, automatically generated font files will be stored +there too. + +Should you want to run \TeX{} this way, you will have to follow these +steps: +\begin{enumerate} +\item from the menu, chose \verb|Explore CD-Rom|, then + \verb|Select a text editor|, a dialog box will open to select some \path|.exe| + program. + + This program needs to be a \TeX{} oriented editor. It must be able + to run the \TeX{} compiler, previewer and any other needed tool. If + you don't have one already installed on your system, you can install + one from the \CD{}, details section~{\ref{sec:texlive-install}}. + + \emph{There is no way we can guess if the program you will + select is actually a text editor, so be careful}. + Here is a list of frequently used \TeX{} editors: +\begin{center} + \begin{tabular}[ht]{ll} + GNU Emacs & \path|c:\Program Files\NTEmacs\bin\runemacs.exe| \\ + XEmacs & \path|c:\Program Files\XEmacs\XEmacs-21.2\i586-pc-win32\xemacs.exe| \\ + WinShell & \path|c:\Program Files\WinShell\WinShell.exe| \\ + WinEdt & \path|c:\Program Files\WinEdt Team\WinEdt\WinEdt.exe|\\ + TeXnicCenter & \path|c:\Program Files\TeXnicCenter\TEXCNTR.exe| + \end{tabular} +\end{center} + The program + selected will be memorized as the editor to use for future runs. + +\item from the menu, chose \verb|Explore CD-Rom|, then + \verb|Run TeX off CD-Rom|. The environment will be modified, a small + temporary directory created and some configuration files copied + there. Then, the selected editor selected will be launched, and you + will be able to type in some text, let \TeX{} typeset it and the + view it or print it. + + If Ghostscript is not detected on your machine, you will be warned + that rendering your DVI files might fail. You can install it from + the \path|Install|, \path|Support| menu item. See + section~\ref{sec:texlive-install} for details. + +\item you can select a different text editor any time you want. + +\item if you chose \verb|Cleanup CD-Rom setup|, everything \TeX{} + needed will be removed, comprised the selection of your text + editor, but not the extra packages you may have downloaded and + installed. If you installed \cmdname{WinShell} or \cmdname{NTEmacs}, +they won't be removed. +\end{enumerate} + +The editor is run inside a modified environment. A temporary TDS +compliant texmf tree is build in the temporary area of your computer. +It is needed to store files that may be build on the fly like pk font +files or format files. Configuration files are copied from the \CD{} +to this texmf tree, so that you can edit them if needed. The \path|ls-R| +database is computed for this texmf tree. +Then the \texttt{PATH} and \texttt{TEXMFCNF} environment +variables are set locally, and the editor is run in +this local environment. From within your editor\footnote{Actually, you can + state any other program than a text editor, and select your command + processor for example. You will then get a console with the right + settings to use \TeX{} from the \CD{}.}, you have access to a full +\TeXLive{} environment, all files referenced on the \CD{}. + + +\smallskip {\small\noindent \textbf{[For advanced users:]} You can + also use the small batch file \path|mkloctex.bat| to be called in a + directory \path|setupw32| of the \CD. From the Start menu select + `Run', then browse CD drive and select \path|mkloctex.bat|. Before + starting it, you should add two parameters separated by a space: the + letter of your CD drive and the letter of the hard disk where you + want to install the \TeX\ directory. The whole line should read, + e.g., \verb+d:\setupw32\mkloctex.bat d c+. When installation is + complete, please read carefully the information on screen. If you + are running Windows 9x/ME, then you will have to restart Windows. } + +\subsection{Installing editors or support packages} +\label{sec:texlive-install} + +You can already use the \path|TeXSetup.exe| program to install a +single, not \TeX{} dependent package. This might be either an editor +like \cmdname{WinShell} or \cmdname{NTEmacs}, +or also a support package like \cmdname{NetPBM} +(graphics formats conversion) or \cmdname{Ghostscript}. + +Some of the packages are not free, or not with the same meaning as for +the rest of the \CD{}. These packages have been made available through +the Internet. You need to enable an Internet connection in order to +install them. Chosing the \path|Enable Internet access| subitem will +search your system for an active Internet connection, or start one if +possible. \emph{If your computer is not connected to the Internet, + then the timeout might be long, 30s or more}. So try to enable it +only if you know you have a connection. + +Only a few packages are available from the \CD{}, but the most +important of them: \cmdname{NTEmacs} and \cmdname{WinShell} for the +editors, \cmdname{Ghostscript} and \cmdname{NetPBM} for the other +support packages. \cmdname{NetPBM} is needed for running \TeX{}4ht. + +The downloadable packages are sometimes huge: \cmdname{Perl} is 10Mb, +\cmdname{XEmacs} is 50Mb, so be warned that it can take a lot of time +to install such things. \path|TeXSetup.exe| does not yet provide an +estimation of the time needed to complete the download. + +When installing these packages, \path|TeXSetup| is working in +unattended mode. However, the programs that have their own installer +like WinEdt or Ghostscript for example will require human interaction. + +Those packages who have no specific installer will be unpacked and configured +for your system. You will be required to select some directory where +they will be installed. The directory to select should be the root +directory of the whole installation. Assuming you want to install +NTEmacs and NetPBM, the archive files already contain the +\path|NTEmacs\| and \path|NetPBM\| part, so the directory you have to +select is something like \path|c:\Local| or \path|c:\Program Files|. + +\subsection{Installing to your hard disk} + +Installation is started by letting the CD autostart, and +selecting the item \verb|Install| from the menu, then the subitem +\verb|TeXLive|. This will invoke the \path|TeXSetup.exe|. You can also find +it in the \path|bin/win32| directory and run it. \path|TeXSetup.exe| +is a Windows wizard and it will display several pages while running. + +\begin{description} +\item[Welcome Page] + You can choose a \emph{quick} installation from + there, in this case, the installation will run without any human + assistance from beginning to end, with all the default settings + (Figure~\ref{graph:setup-src}, + \ifnum \Status = 1 + on the left% + \else\ifnum \Status=2 + at the top% + \else + on the left% + \fi\fi + ). However, if you chose to install any support program that has its + own installer like WinEdt or Ghostscript, your intervention might be required. + If you have enough privileges (administrator or power user rights) + under a Windows version where it is applicable, then you can decide + to install the \TeXLive{} for all users or for yourself only by + checking the appropriate box. + + \begin{figure*}[!htb] + The \cmdname{TeXSetup} Wizard\hfill + Source directories for the \TeXLive{} files + + \begin{center} + \ifnum \Status=1 + \includegraphics[width=.48\textwidth]{../pictures/setup-wizard.jpg}\hfill% + \includegraphics[width=.48\textwidth]{../pictures/source-for-texlive.jpg} + \else + \ifnum \Status=2 +\includegraphics[bb=0 0 506 403]{../pictures/setup-wizard.gif} +\includegraphics[bb=0 0 506 403]{../pictures/source-for-texlive.gif} + \else + \includegraphics[width=.48\textwidth]{../pictures/setup-wizard}% + \hfill% + \includegraphics[width=.48\textwidth]{../pictures/source-for-texlive} + \fi + \fi + \caption{The \TeXLive{} setup wizard}\label{graph:setup-src} + \end{center} +\end{figure*} +\item[Source Page] + This page is a bit complex. It will allow you to select two source + directories for your \TeXLive{} system + (Figure~\ref{graph:setup-src}, + \ifnum \Status = 1 + on the right% + \else\ifnum \Status=2 + at the bottom% + \else + on the right% + \fi\fi + ). You will need a \emph{local + source directory} and possibly a \emph{remote source directory}. + + Why do we need both these directories? The very files of the + \TeXLive{} system are on the \CD{}, but some other packages useful + under a Win32 system are not, either because of space lacking or + because their license was not compatible with the \TeXLive{}'s one. + You need to enable Internet downloading if you want to install these + support packages. + + However, don't panic: the default parameters of the setup will allow + you to install a full system using the \CD{} only. Simply, you won't + have \file{WinEdt} for example, but you will be able to install it + later. + + So you can take your files from: + \begin{itemize} + \item the \CD{} or any similar flat tree of files, available through + some standard directory (this means the \CD{} can be mounted on + some remote machine and be made available through network + sharing), + \item a set of \file{.zip} files (this is the case when you are + installing the + \fpTeX{} distribution), + \item the Internet, in this case, the program takes care of + downloading the \file{.zip} files it needs for you. + \end{itemize} + This option is available only if you enable Internet file + downloading in the right part of the page. You also need to + configure this Internet access by selecting to connect either using + Internet Explorer~5 \file{wininet.dll}, or using a direct connection (\texttt{ftp}, + \texttt{http}). +% or using a proxy server. +% Last, you can be assisted in defining the \emph{local source +% directory} and \emph{remote source directory} which will be used +% to copy the files onto your hard disk. The \texttt{browse} buttons +% allow to select a directory for the former, and an url among a list +% of mirrors for the latter. +\item[Root Page] + On this page, you will tell where you want the files to be + installed (Figure~\ref{graph:root-schm}, + \ifnum \Status = 1 + on the left% + \else\ifnum \Status=2 + at the top% + \else + on the left% + \fi\fi + ). Only the root directory really matters, the other ones + are set according to the root one. You may want to make + \path|$TEXMFEXTRA| point to some TDS compliant directory with other + \TeX{} files or assign a different value to + \path|$HOMETEXMF|, which is set by default to whatever Windows think + is your `HOME' location. +\begin{figure*}[!htb] + Root and directories\hfill% + Scheme selection + \begin{center} + \ifnum \Status=1 + \includegraphics[width=.46\textwidth]{../pictures/root-of-installation.jpg}\hfill% + \includegraphics[width=.46\textwidth]{../pictures/scheme-selection.jpg} + \else + \ifnum \Status=2 +\includegraphics[bb=0 0 506 403]{../pictures/root-of-installation.gif} +\includegraphics[bb=0 0 506 403]{../pictures/scheme-selection.gif} + \else + \includegraphics[width=.46\textwidth]{../pictures/root-of-installation}% + \hfill% + \includegraphics[width=.46\textwidth]{../pictures/scheme-selection} + \fi + \fi + \caption{\TeXLive-Setup: Root and directories / Schemes}\label{graph:root-schm} + \end{center} +\end{figure*} +\item[Get TPM Page] + This page does not require any manual intervention. The \file{.tpm} + files which describe collections and packages are retrieved + (possibly from the Internet), unzipped if needed and parsed. +\item[Schemes Page] + On this page, you will select the global scheme of your + installation (Figure~\ref{graph:root-schm}, + \ifnum \Status = 1 + on the right% + \else\ifnum \Status=2 + at the bottom% + \else + on the right% + \fi\fi + ). A scheme is a large set of files targeted at some kind + of usage. There are 3 generic schemes for basic, recommended and + full installation. The other ones are devoted to LUGs (what GUST or + GUTenberg propose for their members) or applications (XML and + \TeX{}). + When a scheme is selected, it is still possible to refine the + selection by checking the appropriate box. If doing so, you will be + presented the packages page to change your selection, else you will + jump to the review page. +\item[Packages Page] + Collections and packages are presented in a tree form + (Figure~\ref{graph:win32-support}, + \ifnum \Status = 1 + on the left% + \else\ifnum \Status=2 + at the top% + \else + on the left% + \fi\fi + ). The links + in the tree are dependency links. Collections \emph{depend on} + packages and maybe other collections, and it is the same for each + package. You can select any package or collection individually, but + your request will be granted only if the object is not requested by + another one which is selected. For example, you can't deselect + \texttt{tex-basic} without deselecting all the collections that + request it. + + The \texttt{win32-support} collection displayed on the picture is Win32 specific. It + holds a number of bonus packages (Figure~\ref{graph:win32-support}, + \ifnum \Status = 1 + on the right% + \else\ifnum \Status=2 + at the bottom% + \else + on the right% + \fi\fi + ) which can be installed + automatically and individually: Ghostscript, the PostScript + interpreter, \TeX{} oriented editors, tools like Perl, + \LaTeX{}2HTML, etc. \emph{None of these packages are selected by + default}. Some of them have an Internet Explorer icon on their + right, this means that they are not on the \CD{} and they will be + available only if you previously enabled Internet + downloading. \emph{This collection cannot be selected entirely at + once: you need to select the packages individually}. This is to + avoid unwanted downloads of huge files. + + On this page, you also have the information about disk space + needed, for each object, and for the set of those who are selected, + and also the disk space available on the partition selected for the + installation. Last, you can choose to install or not the + documentation files and source files associated with each package. +\item[Review Page] + You will find there a summary of your choices + (Figure~\ref{graph:review}, + \ifnum \Status = 1 + on the left% + \else\ifnum \Status=2 + at the top% + \else + on the left% + \fi\fi + ). It is still time to + go back to change them. +\begin{figure*}[!htb] + Packages Page\hfill% + Win32 Support + \begin{center} + \ifnum \Status=1 + \includegraphics[width=.48\textwidth]{../pictures/package-selection}\hfill% + \includegraphics[width=.48\textwidth]{../pictures/win32-support} + \else + \ifnum \Status=2 +\includegraphics[bb=0 0 506 403]{../pictures/package-selection.gif}\hfill% +\includegraphics[bb=0 0 506 403]{../pictures/win32-support.gif} + \else + \includegraphics[width=.48\textwidth]{../pictures/package-selection}% + \hfill% + \includegraphics[width=.48\textwidth]{../pictures/win32-support} + \fi + \fi + \end{center} + \caption{Packages Page / Win32 goodies} + \label{graph:win32-support} +\end{figure*} +\item[Files Copy Page] + The selected files are copied on your hard disk (Figure~\ref{graph:file-copy}, + \ifnum \Status = 1 + on the right% + \else\ifnum \Status=2 + at the bottom% + \else + on the right% + \fi\fi + ). All the files not + yet available on your local disk are first downloaded from the + remote source directory on the Internet. Then every package is + unpacked (if \path|.zip| files), or copied from the \CD{}. +\item[Configuration Page] Several packages need some configuration + step to make them usable (Figure~\ref{graph:configuration}, + \ifnum \Status = 1 + on the left% + \else\ifnum \Status=2 + at the top% + \else + on the left% + \fi\fi + ). Also the \TeXLive{} system needs some post-processing step + (format files generation, ls-R databases generation, environment + variables, etc.). All these operations are done there, some of them + can be lengthy. +\begin{figure*}[!htb] + \textbf{Review Page}\hfill% + \textbf{File Copy Page} + \begin{center} + \ifnum \Status=1 + \includegraphics[width=.48\textwidth]{../pictures/review-settings}\hfill% + \includegraphics[width=.48\textwidth]{../pictures/file-copy} + \else + \ifnum \Status=2 + \includegraphics[bb=0 0 506 403]{../pictures/review-settings.gif}\hfill% + \includegraphics[bb=0 0 506 403]{../pictures/file-copy.gif} + \else + \includegraphics[width=.48\textwidth]{../pictures/review-settings}\hfill% + \includegraphics[width=.48\textwidth]{../pictures/file-copy}% + \fi + \fi + \end{center} + \caption{Review Page / File Copy Page} + \label{graph:review}\label{graph:file-copy} +\end{figure*} +\item[Final Page] The installation being over, you may want to display + the Windows specific documentation (HTML format) and / or the log + file of the setup process (Figure~\ref{graph:final} + \ifnum \Status = 1 + on the right% + \else\ifnum \Status=2 + at the bottom% + \else + on the right% + \fi\fi + ). If it is needed (Win9x/WinME), you will + be asked to reboot your computer. +\end{description} + +\begin{figure*}[!htb] + \textbf{Configuration Page}\hfill% + \textbf{Final Page} + \begin{center} + \ifnum \Status=1 + \includegraphics[width=.48\textwidth]{../pictures/configuration}\hfill% + \includegraphics[width=.48\textwidth]{../pictures/congratulations} + \else + \ifnum \Status=2 + \includegraphics[bb=0 0 506 403]{../pictures/configuration.gif}\hfill% + \includegraphics[bb=0 0 506 403]{../pictures/congratulations.gif} + \else + \includegraphics[width=.48\textwidth]{../pictures/configuration}\hfill% + \includegraphics[width=.48\textwidth]{../pictures/congratulations}% + \fi + \fi + \end{center} + \caption{Configuration Page / Final page} +\label{graph:configuration}\label{graph:final} +\end{figure*} + +Please be aware that the choice of cluster size on DOS disk +partitions can radically affect the size of your \TeX\ +installation. The support tree has hundreds of small files, and it is +not unusual for a complete installation to take up to 4 times the +amount of space used on the \CD. + + +\section[Maintenance and other aspects of the \protect\TeXLive{} +installation under Windows]{Maintenance and other aspects of the \protect\TeXLive{} +installation under Windows} + +\subsection{What's different under Win32 from the standard \Webc ?} +The Win32 version of \Webc{} has some specific features that need to +be noticed. + +\begin{description} +\item[\KPS{}] the hash-tables that \KPS{} builds are quite large for + the \TeXLive{}. In order to cut down the starting time of any + \KPS{}-enabled program, these hash-tables have been put in shared + memory. This way, when you chain the execution of several such + programs, like \path|tex| calling \path|mpost| calling \path|tex|, + the overhead when starting each of the programs but the first will + be reduced. This change is hidden to the user, except if you set the + debug flag of kpathsea to the \path|-1| value: you will then trace + access to the shared memory, which is not what you want (it is + accessed very often!). What is useful in a log trace of the shared + memory access is still to be defined, so the situation might evolve + in the future. +\item[\cmdname{kpsecheck}] this command provides some option that did + not fit well into \cmdname{kpsewhich}. It will allow you to list all + the files that occur multiple times across your texmf trees. This + could be handy, but most of the time you will also get unwanted + output (like dozens of \path|README| files)\footnote{It is noticeable + that all these files result in clashes inside the \KPS{}-hashing + mechanism, fortunately, \KPS{} never look for these files.}. For + this reason, you can combine the \path|-multiple-occurences| with 2 + other options for including or excluding any filename that match + some pattern (you can request for several patterns). + + The \cmdname{kpsecheck} command will also report the status of + shared memory: in use or not used. That might be useful to know + because if the status reported is ``in use'', that means one or + several processes are working, and the effect of any + \cmdname{mktexlsr} command will be delayed until the next time where + no \KPS{} linked process will be running. + + Last, this same command will report about the location it thinks + Ghostscript can be found. Under Win32, for many programs, it is + easier to use the Ghostscript dll, and find it by using the + Ghostscript registry key than to change the \path|PATH|, which has a + limited length anyway. +\item[\Webc{}] the engines have a few more options than the ones from regular + \Webc{}, and one option with a different behaviour: + \begin{itemize} + \item the \path|-fmt| option behaves differently. Previously and + with the regular \Webc{} distribution, this option has 2 different + meanings when you are in ``ini'' or ``vir'' mode. Under Win32, it + has the same meaning: preload the format file specified with the + argument. The meaning of building a format of such name in ``ini'' + mode is obtained by the new \path|-job-name| option. + \item \path|-job-name| option: allows to set the name of the file + resulting from the compilation process. In normal mode, it will + change the base name of all files produced (\path|.dvi|, + \path|.aux|, etc.), while in ``ini'' mode, it will set the name of + the format file written. + \item \path|-halt-on-error| stop the compilation at the first error. + \item \path|-job-time| set the job time to the same timestamp as the + file given in argument. + \item \path|-output-directory| allow to write all the output files in the + specified directory. + \item \path|-time-statistics| print statistics about the job run + time. It is to be noted that Win9x not being a true multitasking + operating system, it has no reliable timer for short periods, so + the value printed is an approximation. Under NT/2K/XP, the result + is quite accurate with user time and system time values allocated + for this run. For Unix + users: the \path|time| command is not usually available to Windows + users. + \end{itemize} +\end{description} + +\subsection{Adding packages to your installation} + +You will find an option in the \texttt{TeXLive} menu (or go to +\texttt{Start -> Programs -> TeXLive -> Add TeX package} menu) to run again +\file{TeXSetup.exe}, but in maintenance mode this time. The steps you +will go through are almost identical to the ones the first time you +run it. + +The only different step is about the packages selection page. In +maintenance mode, the list of installed packages is compared to the +list of packages available from your source directories. Packages that +are not installed will be displayed in green, out of date packages +will be displayed in red and up to date, installed packages are +displayed in black. + +This way, you can choose to add or upgrade components, either from +your \CD{} or from the +Internet, where you are likely to find some more recent version of +your packages. + +It is up to you to select which ones of the packages you want to +install. The rest of the process is similar to the first installation. + +If you want to add files that are not provided by the \TeXLive{} (or +\fpTeX{}) distribution, it is recommended to put them in the +\path|$TEXMFLOCAL| directory. This way, you will be safe against +upgrades of the \TeXLive{} software. + +The directory pointed to by \path|$TEXMFLOCAL| is initially empty. If +you want to add there the support file for Maple (symbolic computation +program) for example, you will have to put the style files in:\\ +\path|c:\Program Files\TeXLive\texmf-local\tex\latex\maple\|\\ +and the documentation files in:\\ +\path|c:\Program Files\TeXLive\texmf-local\doc\latex\maple\| + +Next, \textbf{do not forget to rebuild the ls-R databases files}, +either by using the right menu (Start -> Programs -> TeXLive + -> Maintenance), either by manually running the \file{mktexlsr} + command. + +\subsection[Removing \protect\TeXLive{} from your hard disk]{Removing + \protect\TeXLive{} from your hard disk} + +The uninstall procedure is available either from the +\file{TeXLive.exe} program, from the \path|TeXLive| menu or from the +control panel (Start menu -> Control Panel, Add/Remove Programs +option). This procedure will cleanup your hard disk of most of the +\TeXLive{} files. However, \TeX{} is a system that is creating files +and there is no mechanism to keep track of all of them. Moreover, +Win32 support packages have their own uninstall procedure, which you +will have to run separately (provided you want to get rid of them). Last, +the files you may have stored in \path|$TEXMFLOCAL| won't be +removed. So, even if the vast majority of files are automatically +removed by the uninstall procedure, you will have to do some manual +cleanup to actually remove all of them. + +\subsection{Running \texttt{TeXSetup.exe} from the command line} + +The \path|TeXSetup.exe| program has a number of other interesting +options. You can get the list by running: +\begin{verbatim} +c:\>TeXSetup --help +\end{verbatim} + +Here is the description: +\begin{description} +\item[\path|--automatic-reboot|] reboot without waiting user + confirmation once installation is over; +\item[\path|--dry-run|] do nothing, just log everything that will be + done without this option; +\item[\path|--quick|] use the recommended installation and default + directories, ask nothing up to rebooting; +\item[\path|--net-method (=ie5/direct)|] enable to download components with + restricted licenses from the Internet (either using direct + connection of Internet Explorer 5 DLLs): you need to have an available + network connection and some of the packages are huge; +\item[\path|--remote-source-directory |] this is the base url for the remote packages; +\item[\path|--local-source-directory

|] by default, \path|TeXSetup.exe| + will guess the root directory of the set of files you want it to act on, if you ever + upgrade \path|TeXSetup.exe|, you won't be able to copy the new version + onto your \CD{}, so you will need to use this option to specify the + root of the \CD{}; +\item[\path|--installation-directory |] this is the root of your + installation, all files will be copied under this location. The + default value is \verb+c:\Program Files\TeXLive+; +\item[\path|--texmfmain-directory |] +\item[\path|--texmflocal-directory |] +\item[\path|--texmfextra-directory |] +\item[\path|--texmfhome-directory |] +\item[\path|--vartexmf-directory |] +\item[\path|--vartexfonts-directory |] these are the directories + used to configure the location of your files. They map directly to + the \path|texmf.cnf| variables. +\item[\path|--with-source-files(=yes/no)|] copy the source files + for \TeX{} packages, default value is no; +\item[\path|--with-documentation-files(=yes/no)|] copy documentation files for \TeX{} + packages. Default value is yes. Beware: this is only documentation about specific + packages, general documentation will be installed anyway; +\item[\path|--program-folder |] the name of the folder under + which you will find the menus; +\item[\path|--add-package |] this is used to add or update a specific + package after a first regular installation; +\item[\path|--scheme |] install the named scheme instead of the + default \path|texlive-recommended| scheme; +\item[\path|--maintenance|] mostly the same as \path|--add-package| + without specifying a package to add; +\item[\path|--uninstall|] this option will remove anything \TeX{} related coming from + the \CD{}, which means there can be files left if you added style + files or format files, and also that supplementary tools will not be + removed\footnote{This option is still a bit crude as of \today}; +\item[\path|--help|] this option opens up a box with the list of options. +\end{description} + +\subsection{Network installation} + +\KPS{} knows about UNC names, so you can use them to get your TEXMF +tree from the network. But there is better than this. +All the support files and configuration files, everything except the files in the +\path|bin/win32| are shareable with a \teTeX{} or Unix \TeXLive{} installation. That means +you can use Samba either to mount from an NT server to a Unix +workstation or the converse. Several strategies are possible: +\begin{itemize} +\item Put everything on the server. Just add each set of files for the os and +architecture you want to use in the \path|bin| directory. That means +for example \path|bin/win32| and \path|bin/i386-linux|. Next configure +your main variables. You can use UNC names to +point to the right directories under Win32. +\item Install a local copy for the binaries and format files. In this + case, assign \path|$TEXMFMAIN| to the main \path|texmf| tree that + will be accessed remotely. Set \path|$VARTEXMF| to be a local + directory which will hold local configuration files and on-the-fly + generated files. +\end{itemize} + +\subsection{Personal Configurations} + +\subsubsection{\cmdname{WinShell}} +\label{sec:winshell} + +Start this program from the Start menu or from the Desktop shortcut. +Go to \textbf{Options} \verb+->+ \textbf{Program Calls}. + +\begin{itemize}\itemsep 0pt +\item In the DVIWin tab, if the filename is \textbf{yap}, replace it +with \textbf{windvi.exe}. +\item In Ghostview tab, make sure it gives the correct path for +gsview32.exe:\\ +\hspace*{1em} \verb+C:\ghostgum\gsview\gsview32.exe+ (for 3.6, the +current version)\\ +or \\ +\hspace*{1em} \verb+C:\gstools\gsview\gsview32.exe+ (for the older +version) + +\end{itemize} + +Click \textbf{OK}. + +Note that the install process sets all files with the \texttt{.tex} +extension to open with \cmdname{WinShell}. Unless you plan to use another editor +(such as WinEdt or Emacs), this is appropriate. + +Unfortunately, \cmdname{WinShell} does not have a spell-checking feature. +However, if you have installed the \path|tex-extrabin| collection, +your installation includes \textbf{Ispell} (a spell checking program +found on most Unix systems). The executable is in your PATH so +\verb+ispell.exe+ will be found if you invoke it from a DOS window. +If you installed documentation, look +at\\ +\verb+C:\Program Files\TeXLive\texmf\doc\html\manpages\ispell.html+\\ +for information on Ispell. (Otherwise, you can find +\verb+ispell.html+ on the CD.) If you rely on spell checking, you may +want to add an Ispell icon to \cmdname{WinShell}. See +subsection~\ref{winshell:ispell} of this document for how to do that. + +For an excellent commercial (but inexpensive) spelling checker, +see \url{http://www.microspell.com}. + +%Appendix B also contains other information about using \cmdname{WinShell}, such as: +% +%\begin{itemize} +%\item How to apply a bug fix you probably need +%\item How to print directly from \cmdname{WinShell} +%\item How to use the Project feature for multiple-file documents +%\end{itemize} + +\cmdname{WinShell} also has on-line help, which you can access via the +$\textbf{\underbar{?}}$ on the menu bar. + +Other information about using \cmdname{WinShell} can be found in +section \ref{winshell:more} on p.~\pageref{winshell:more}. + +\subsubsection{Dvips} + +The configuration file for dvips can be found in\\ +\verb+C:\Program Files\TeXLive\texmf-var\dvips\config\config.ps+\\ +You may open it with any editor (\cmdname{WinShell} will do fine) and change +some parameters: + +\begin{description} +\item [fonts] you can change the default printer \MF{} mode or printer + resolution in case dvips needs to generate PK fonts. By default it + is configured to use type1 versions of the CM fonts, so it should + not call \cmdname{mktexpk} too often; +\item[printer] you can tell dvips where you want to print by + default. If the `o' option is not followed by a printer name, then a + \file{.ps} PostScript file is written. You can give dvips a printer + name such as: +\begin{verbatim} +o lpt1: +% o | lpr -S server -P myprinter +% o \\server\myprinter +\end{verbatim} +\item[paper] Next, you might want + to change the paper size from European (A4) to US letter + by making the US letter the first paper size mentioned in the file. + Scroll to the group of lines beginning with ``@''. Move + the appropriate lines so that this section begins with the lines:\\ +\hspace*{1em} @ letterSize 8.5in 11in\\ +\hspace*{1em} @ letter 8.5in 11in\\ +\hspace*{1em} @+ \%\%BeginPaperSize: Letter\\ +\hspace*{1em} @+ letter\\ +\hspace*{1em} @+ \%\%EndPaperSize +\end{description} + +\textbf{Note:} The current \TeXLive{} distribution has implemented (for +the first time!) the procedure of making always up-to-date fontmaps files +for Dvips and Pdftex. This is done by \cmdname{updmap} program +during installation, as well as during any font package addition. +If you add new packages by hand, edit the file \verb+updmap.cfg+ +in \path|$VARTEXMF/web2c|. + +\subsubsection{Pdftex} +If you want to use the program pdf{}latex to convert directly to +pdf format, and you are using US letter file, edit the file\\ +\verb+C:\Program Files\TeXLive\texmf-var\pdftex\config\pdftex.cfg+\\ +and change ``page\_width'' and ``page\_height'' to specify letter-size paper. +These entries should read:\\ +\hspace*{1em} page\_width 8.5 true in\\ +\hspace*{1em} page\_height 11 true in\\[6pt] +Save the file and exit the editor. + +\subsubsection{GSView} +Starting from versions compatible with Ghostscript 6.50, GSView is not +free anymore, but shareware. So it is not on the \CD{} anymore. + +You may want to change the papersize to US letter size. If so, +open GSView from the Start menu. \\ +From the \textbf{Media} menu, select \textbf{Letter}. + +Also, there are menu settings that are supposed to give you the +most readable screen image:\\[4pt] + From \textbf{Media} \verb+->+ \textbf{Display Settings}, +set \textbf{Text Alpha} +and \textbf{Graphics Alpha} both to 4 bits. + +Note that the installation process has set all .ps and .eps files +to automatically open with GSView. + +For printing instructions, see section~\ref{printing} below. + +\subsubsection{WinDvi} +\label{sub:windvi} + +The \file{TeXSetup.exe} program takes care of associating the files +with the \file{.dvi} extension with \file{Windvi}. + +Open it from the Start menu (Programs \verb+->+ TeXLive \verb+->+ DVI Viewer). +You can set it for US letter paper by going to \textbf{View} \verb+->+ \textbf{Options} +and next to \textbf{Papertype}, +selecting US (8.5\verb+"+ x 11\verb+"+). +Click \textbf{OK}. +Exit Windvi. +You can change other parameters from there, like the ability to +execute commands included in path|\special{}|. +Also, the first time you +view any .dvi file, you may find the magnification too large. Zoom out +until you get an appropriate size. + +%There are two important parameters related to printing that can't yet +%be set from the dialog boxes, namely the resolution and the \MF{} mode +%for the printer. You can set them once for all by specifying them on +%the command line: +%\begin{verbatim} +%c:\>windvi -p 360 -mfmode canonbjc foo.dvi +%\end{verbatim} +%When you will exit Windvi, these parameters will be stored in the +%configuration file. The available modes are found in this file:\\ +%\path|c:\Program Files\TeXLive\texmf\metafont\misc\modes.mf| + +All the configuration for Windvi is stored in the +\path|$HOME/windvi.cnf| file. You can find it by running this command +at the prompt: +\begin{verbatim} +c:\>kpsewhich --expand-var $HOME/windvi.cnf +\end{verbatim} + +Should you have problems with Windvi, please remove the configuration +file and test your problem against a vanilla configuration. + +\subsection{Testing} + +You can test \cmdname{WinShell} by opening the file \verb+sample2e.tex+, found in +\path|C:\Local\TeX\texmf\tex\latex\base|. The \LaTeX\ source should appear +on the screen. Process it by clicking on the \LaTeX\ icon on the toolbar, +then view it by clicking on the Preview (Windvi) icon. + +At first, when you preview files with Windvi, it will create fonts because +screen fonts were not installed. After a while, you will have created most +of the fonts you use, and you will rarely see the font-creation window. +Return to \cmdname{WinShell} and try dvips, then GSView. + +\textbf{Hint for the future:} If a \LaTeX\ run stops because \LaTeX\ +cannot find a file, you can press \textbf{Ctrl-z} to quit. + +\subsection{Printing}\label{printing} + +It is possible to print from Windvi. In this case, printing will +be done using the Windows unified printer driver. By definition, it +is compatible with all printers. However, there is some drawback: it +can generate some huge spool files, and some (older) versions of Windows just +don't like them. The advantage is that you can use features like +embedding BMP or WMF images. You also need to make sure that the +printer parameters are correctly set (subsection~\ref{sub:windvi}), +else you will get scaled printing (printing at 600dpi on a 300dpi +printer will give you only one quadrant of your page). + + +Printing is faster and more reliable if you run dvips to make a +.ps file and then print from GSView. To print from GSView, first select +\textbf{Print...} from the \textbf{File} menu. A Print window will appear. + +If you will be using a PostScript printer, \textit{be sure to select +\textbf{PostScript Printer}}. In the newer version this is done in +the ``Print Method'' box at the bottom left of the Print window. You +can then select any of the printers that you have previously installed +on your PC. If you fail to check the box for PostScript Printer, +printing will not work. + +If you will be using your own non-PostScript printer, select +\textbf{Ghostscript device} in the ``Print Method'' box, then click on +the button to the right labelled \textbf{djet500} and select your +printer type from the list that pops up. (In the older version of +GSView, make sure PostScript Printer is \textit{not} selected, then +select your printer type from the ``Device'' list.) + +If you use \cmdname{WinShell} and a PostScript printer, probably the most +convenient way to print is to add an icon to the \cmdname{WinShell} toolbar that +invokes dvips in a way that sends the output directly to a default +printer. For detailed instructions on how to do this, see +\ref{winshell:print} on p.~\pageref{winshell:print} +(\textit{More About \cmdname{WinShell}}). + +\subsection{More About \cmdname{WinShell}}\label{winshell:more} +\subsubsection{Installing Bug Fixes} + +\cmdname{WinShell}'s author (\href{mailto:idb@winshell.de}{Ingo de Boer}, +thanks to him) sometimes releases beta versions of the next \cmdname{WinShell} +version which are also bug fixes. You can grab them from +\url{http://www.winshell.de}. Usually they are \file{.zip} files that +only require to be unpacked in \cmdname{WinShell} directory (\path|c:\Program +Files\WinShell| by default), either using WinZip or a similar tool, or +by using \file{unzip} on the command line. If you got some +\file{winshellbugfix.zip} file and that you saved it in the \cmdname{WinShell} +directory, then you need to run: +\begin{verbatim} +c:\>cd c:\"Program Files"\WinShell +c:\>c:\local\bin\unzip winshellbugfix.zip +\end{verbatim} +Say `yes' if you are asked if some files should be overwritten. The +\path|unzip.exe| programme can be found in the +\path|support/gnu-utils| package. If you +do not have it on your machine, you can use any archiver tool like +WinZip to achieve the same effect. + +\subsubsection{Using the Project Feature} +If your document is split into several files +(for example a thesis), look into \cmdname{WinShell}'s ``Project'' feature. From the +\textbf{Project} menu, you give the project a name (e.g., Thesis), +supply the name of the main (or root) file, and then ``add'' other +files. These filenames display on the left of the screen where you can +double click the names to view and switch between them. Clicking +the \textbf{\LaTeX} icon always processes the main file. + +Note the icons on the toolbar for toggling the project space (on the left) +and the log space (at the bottom). If you are not using the Project +feature, you may want to toggle off the space on the left, using the full +screen width to display your file. + +\subsubsection{Printing from \cmdname{WinShell} to a PostScript Printer} +\label{winshell:print} + +The Dvips icon on the \cmdname{WinShell} toolbar puts the PostScript output in a file, +which you can then view with GSView and print from there if you choose. +However, it's convenient to add a \cmdname{WinShell} ``program call'' to dvips which +sends the output directly to a designated PostScript printer. The steps +below show how to do this for the printer \textbf{vclw}; you should +substitute the name of your most frequently-used printer for \textbf{vclw}. +\begin{enumerate} +\item Make the program aware of the printer: +\begin{itemize} + +\item Open \cmdname{WinShell}, go to \textbf{Options} \verb+->+ +\textbf{Program Calls} \verb+->+ \textbf{User defined}. + +\item Click on \textbf{Tool 1} in the list on the right and fill in the +fields to the left as follows:\vspace{-6pt} +\begin{quote} +Name: \verb+Print+\\ +exe file: \verb+dvips+\\ +cmd-line: \verb+ -D600 %m -o vclw+\\ +Uncheck the box for ``DVIPS first'' +\end{quote}%\vspace{-12pt} +\item Click \textbf{OK} +\end{itemize} +\item Add Print to the toolbar: +\begin{itemize} +\item Go to \textbf{Options} \verb+->+ \textbf{View} \verb+->+ \textbf{Customize}. +\item In the Category box, select \textbf{User-Programs}. +\item Select \textbf{Print} and drag it to the toolbar, placing it just to + the right of the GSView icon. +\item You then have a choice of ``Image only'', ``Text only'', or ``Image and +Text''. The easiest is to select ``Text only'' and click \textbf{OK}. +You should then see \textbf{Print} on the toolbar. (If you prefer, you can +select ``Image only'', then ``Edit'', and edit the displayed picture to your +satisfaction.) +\end{itemize} +\end{enumerate} +Now, to print a \LaTeX\ document, just click on the \textbf{Print} icon to +send to your selected printer. To use a different printer, you will need to +click on the \textbf{Dvips} icon to print to a file. Then click on the +GSView icon and use GSView to send to any printer you have installed on +your PC. + +\subsubsection{Adding Ispell to \cmdname{WinShell}} +\label{winshell:ispell} +\begin{enumerate} +\item Add Ispell to User Tools: +\begin{itemize} +\item Open \cmdname{WinShell}, go to \textbf{Options} \verb+->+ +\textbf{Program Calls} \verb+->+ \textbf{User defined}. +\item In the list on the right, click on \textbf{Tool 1} (or \textbf{Tool + 2} if you have already used \textbf{Tool 1}) and fill in the +fields to the left as follows:\vspace{-6pt} +\begin{quote} +Name: \verb+Ispell+\\ +exe file: \verb+ispell+\\ +cmd-line: \verb+ -t -d american %c.tex+\\ +Uncheck the boxes for ``LaTeX first'' and ``DVIPS first'' +\end{quote}%\vspace{-12pt} +\item Click \textbf{OK} +\end{itemize} + +\item Add Ispell to the toolbar: %\vspace{-14pt} +\begin{itemize}\itemsep 0pt +\item Go to \textbf{Options} \verb+->+ \textbf{View} \verb+->+ \textbf{Customize}. +\item In the Category box, select \textbf{User-Programs}. +\item Select \textbf{Ispell} and drag it to the toolbar, placing it just to + the right of the GSView icon (or the last icon you added). +\item You then have a choice of ``Image only'', ``Text only'', or ``Image and +Text''. The easiest is to select ``Text only'' and click \textbf{OK}. +You should then see \textbf{Ispell} on the toolbar. (If you prefer, you can +select ``Image only'', then ``Edit'', and edit the displayed picture to your +satisfaction.) +\end{itemize} +\end{enumerate} +Now, when you have a \LaTeX\ document open, you can click on +\textbf{Ispell} to perform spell checking. Ispell will open another window +and display the first misspelled word on the left with the filename on the +right. Below that you will see the context in which the misspelling appears; +often several suggestions for replacements are also displayed. To replace +the word, enter the number corresponding to the desired replacement. Other +possible responses are listed below; for example, you can press the space +bar to ignore the misspelled word. For more information on Ispell, read the +manual page: \verb+C:\Program Files\TeXLive\texmf\doc\html\manpages\ispell.html+. + +Note that when you replace a word, you will not see the correction in your +\cmdname{WinShell} window until you close the file (click the X in the upper right +corner) and then open it again (use the File menu). + +\subsection{Tips and tricks about the Win32 platform} + +\subsubsection{Different flavors of Win32} + +What we call Win32 is not an operating system by itself. It is a set +of functions -- and a large one\footnote{Around 12000 functions in the + header files of the Microsoft SDK} -- that you can use to write +programs for different operating systems of the Windows family. + +Windows comes in different flavors: +\begin{itemize} +\item Win95, Win98 and WinME, which \emph{are not true multitasking, + multithreading} environments. They are the latest -- and hopefully + last -- metamorphosis of DOS. This can be more or less proven by the + fact that when booting, the PC will load the \path|command.com| + interpreter, and if you stop the boot process at this point, you can + ask for the current (DOS) version and it will answer something like + 'MS-DOS 7.0' (at least for the old versions of Win9x); +\item Windows NT, which is a new operating system written from scratch, + capable of + true multitasking behaviour, and loaded with high level features; +\item Windows 2K, written on an NT basis, with all the bells and + whistles of Win98. +\item Windows XP, which comes with Personal and Pro flavors. This is + the last step in merging both lines of products (Win9x based and NT + based). XP is written on an NT basis. +\end{itemize} + +Win9x are able to run 32~bits programs and 16~bits programs +concurrently. But the operating system by itself is not entirely +written in 32~bits mode, and does not support memory protection: 16bits +applications can overwrite parts of the operating system memory! Some +parts of the system like the GDI (Graphical Device Interface) manage +limited resources like bitmaps, fonts, pens and so on for the set of +all programs that run concurrently. All the bitmaps headers available +at the same time can't amount for more than 64kb. This explains the +performance tool and the fact that you can put your system on his +knees by making intensive use of graphic objects for example. + +NT, 2K and XP do not suffer from these limitations, and neither from +other Win9x limitations. They are true multitasking environments, with +protected memory. They are much more responsive than Win9x because +of better memory management, better file system and so on. + +\subsubsection{Command line prompt} + +You will wonder: ``why would I need to use a command line prompt when +I have Windows?''. + +Good question. The problem is of very general nature. Not all +operations can be done easily using only a GUI. Command line gives you +programming power -- assuming a clever command interpreter. + +But the problem here is more fundamental: \TeX{} is \emph{a batch} +tool. Not an interactive one. \TeX{} needs to compute the best +layout for each page, resolve cross-references and so on. This can be +done only by a global processing of the document. It is not (yet) a +task that can be done interactively. + +This means that you should use \TeX{} from a command line. In fact the +situation is not so bad. There is an advantage to write command line +tools for complex processing: they are better debugged, because not +tied to GUI problems, and GUI tools can be designed to interface the +command line tools. This is the case for \TeX{} where you will +interact with it most of the time through a GUI text editor -- see +section~\ref{sec:winshell} for example. + +However, you may need to use the command line prompt in a number of +situations, by example in case of problems and you want to debug your +setup -- see + section~\ref{sec:troubleshooting}. + + \begin{description} + \item[Win9x] You will open a command line prompt by looking either + for the MS-DOS icon in the ``Start->Programs'' menu, either by + choosing ``Start->Run'' menu and typing in \path|command.com| + \item[NT, 2K, XP] You will open a command line prompt by looking + for the ``Command Prompt'' in the ``Start->Accessories'' + menu\footnote{These locations may change across different OS + versions.}. You can also choose the ``Start->Run'' menu and type + in \path|cmd.exe|, which is the name of the brand new command + interpreter for NT\footnote{Which explains why it is untrue to + call this a \emph{DOS} box under NT!}. +\end{description} + +\subsubsection{Path separators} + +The Win32 API understands both \path|/| and \path|\| characters as +PATH separators. But the command interpreters do not! So whenever a +path name is used programmatically, you can use both separators, and +even mix them up in the same path name. But on the command line, you +must type \path|\| as path separator. The reason is compatibility: +the command processor used the \path|/| to introduce arguments to +commands. + +All this to say: do not be surprised to read path names written using +the Unix convention; \fpTeX{} is a port of \Webc, and aims to be compatible +across platforms. For this reason, all the configuration files that +need to specify path names use the Unix convention. + +\subsubsection{File systems} +\label{sec:clusters} + +The worse feature of Win9x with regard to \TeX{} is probably the +so-called FAT file system. \TeX{} uses many many small files, with +size around 1kb -- 3kb. The FAT file system is old, and predates by +far the multi-gigabytes hard disks we have today. It means it can't +manage efficiently the 30000 \TeX{} files found on the \CD{}. The FAT +file system will allocate a minimum of 32kb for \emph{any} file on a +huge partition. It means that \TeX{} will use much more disk space +than it actually needs. + +The other, more modern, file systems available -- namely FAT32 and +NTFS -- do not have this drawback. They manage clusters of 4kb +only\footnote{You can lower the limit to 512 bytes on NTFS}. + +\subsubsection{How to add some directory to your PATH} + +There are pairs of variables and values which behave much like global +variables inside your programs. The set of those variables is called the +environment. Each program is initialized with a copy of the +environment when it is run. It can request and change the +value of any variable. The changes happen in the copy of the +environment, and is not at all propagated to the other running +programs. + +Your PATH is a special environment variable used to search for +programs you want to run. +There is a different procedure to change it for Win9x, WinME and NT/2K/XP: + +\begin{description} +\item[Windows 95/98] Edit your \path|autoexec.bat|. In this file should be a line + starting with \texttt{PATH=} and followed by a list of directories separated + by \path|;|. Please add the directory with the executables in this line. + After this, this line could look as follows: +\begin{verbatim} +PATH=c:\windows;c:\windows\system;c:\"Program Files"\TeXLive\bin\win32 +\end{verbatim} +\item[Windows ME] You need to run the special program + \path|c:\windows\system\msconfig.exe| to be able to change any + environment variable. From this program, select the `Environment' + tab, and then add or modify the variable you want. You will be asked to reboot the + machine upon any change. +\item[Windows NT/2K/XP] + Click left on \texttt{Start --> Settings --> Control Panel}. Now the window + with the control panel icons opens. Double click on System. The + System Properties window opens. Click on the tab + \textsf{Environment} or look for a button named `Environment + Variables' among the dialog boxes. Now + you can change the environment variables for your user account. Note: + There are also displayed the environment settings for the system. + Normally, you can't change the system variables unless you have + administrator rights on your machine. If you want to change the \texttt{PATH} + for all users, you will have to contact your system administrator or + be the system administrator yourself--in the later case you should + know what you are doing. + + If there is already a \texttt{PATH} setting for your user account, + left click on \texttt{PATH}. In the field \textsf{Variable} appears + \texttt{PATH} while the field Value shows the current setting of + \texttt{PATH} as a list of directories separated by \path|;|. Add + the directory where the executables are located (e.g. + \path|c:\Program Files\TeXLive\bin\win32|). If there isn't a \texttt{PATH} variable + for your user account, simply click in the field Variable and type + in \texttt{PATH}, click in the field \textsf{Value} + and type in the directory with the executables. Important: Click on + the \textsf{Apply} button before clicking \textsf{Ok}, otherwise the + changes to \texttt{PATH} won't apply to your system. Be careful when + changing the environment settings. +\end{description} + +The best way to be sure that a variable has been properly set is to +open a console and type: +\begin{verbatim} +set VARIABLE +\end{verbatim} +which should return the corresponding value. + +\subsubsection{\TeX{} engines} + +If you have a look at the \Webc{} documentation, you will read that all +the various \TeX{} derived programs use the same base engine. For +example, \path|tex.exe| and \path|latex.exe| are exact copies of the +same program, but each one will use a different format file, based on +its calling name. + +Under Unix, this feature is implemented through \emph{symbolic + links}. It saves up a bit of disk space, because some engines are +used with many different format files. + +The Win32 API does not know about file links. So to save up almost +the same amount of memory, all the \TeX{} base engines have been put +in DLLs (\emph{Dynamic Linked Library}). This means that you will have +the following layout: +\begin{alltt} +13/05/2002 17:06 3 584 latex.exe +13/05/2002 17:06 266 240 tex.dll +13/05/2002 17:06 3 584 tex.exe +\end{alltt} +and the \path|latex.exe| file is nothing but a rough copy of +\path|tex.exe| using the same core \path|tex.dll|. +The same trick has been used for the \path|mktex*.exe| family of programs which are +linked to the \path|mktex.dll| library. + +In fact, a generic tool called \path|lnexe.exe| is provided to build the +equivalent of Unix hard links for executable files only under Win32. + +\subsection{In case of problems} +\label{sec:troubleshooting} + +\subsubsection{What to do if \texttt{latex} does not + find your files?} + +\begin{itemize} +\item \cmdname{kpsewhich} is the tool of choice to debug any +problem. Unfortunately, kpsewhich outputs debug information to +stderr, and the Windows console does not know how to redirect stderr +to a file\footnote{Well, NT and Win2k consoles know how to do + that. But the trick will work for any console.}. +For diagnostic purposes you can temporarily set an +environment variable (in DOS box): +\begin{verbatim} +SET KPATHSEA_DEBUG_OUTPUT=err.log +\end{verbatim} +You can also set the debug level: +\begin{verbatim} +SET KPATHSEA_DEBUG=-1 +\end{verbatim} + +If you want to redirect stderr to stdout, which is not possible under +either W9x or NT/2K/XP, then just do: +\begin{verbatim} +SET KPATHSEA_DEBUG_OUTPUT=con: +\end{verbatim} +This way you can capture both stdout and stderr in the same file. + +\item Assuming the installation has been done in \path|c:/Program Files/TeXLive|, check + the following values: \\ + {\small + \begin{tabular}{ll} + \path|kpsewhich -expand-path $SELFAUTOPARENT| & \path|c:/Program Files/TeXLive| \\ + \path|kpsewhich -expand-path $TEXMF| & \path|c:/Program Files/TeXLive/texmf| \\ + \path|kpsewhich -expand-path $TEXMFCNF| & + \path|.;c:/Program Files/TeXLive/texmf/web2c;| \\ + & \path|c:/Program Files/TeXLive/bin/win32;| \\ + & \path|c:/Program Files/TeXLive/bin;| \\ + & \path|c:/Program Files/TeXLive| \\ + \path|kpsewhich -expand-var $TEXINPUTS| & \path|.;c:/Program Files/TeXLive/texmf/tex//| + \end{tabular} +} +\item If you have other \TeX{}-related values already set in your + environment, please, remove them. They are overriding the ones in + texmf.cnf. +\item Check the values from:\\ +{\small + \begin{tabular}{ll} + \texttt{kpsewhich cmr10.tfm} & \path|c:/Program Files/TeXLive/texmf/fonts/tfm/public/cm/cmr10.tfm|\\ + \texttt{kpsewhich latex.fmt}& \path|c:/Program Files/TeXLive/texmf/web2c/latex.fmt| + \end{tabular} +} +\item At this point, if everything is correct, \path|tex.exe| and + co. should work. If it is not the case, you will need to play with + the \path|-debug=n| option from \path|kpsewhich|, and check back all + the values. Try to identify and report the problem. +\end{itemize} + +\subsubsection{What to do if your setup still does not work as expected?} + +There are several questions to ask about: +\begin{enumerate} +\item Is \file{tex.exe} on my \path|PATH|? +\item Is the \path|TEXMFCNF| variable correctly set to + \path|c:/Program Files/TeXLive/texmf-var/web2c| (default value)? +\item Are there any errors in the log file generated by the + \file{TeXSetup.exe} program? Errors are flagged with the sequence + \path|Error|. +% \item If everything seems correct up there, then you need to read the +% documentation in \path|texmf/doc/fptex/fptex.pdf| or +% \path|texmf/doc/html/fptex/fptex.html| for a more detailed procedure +% (available on your hard disk or on the \CD{}). +\item One can also go to \url{http://www.tug.org/tex-live.html} and + check for any bug fix. +\item The Windows distribution on the \CD{} is no more no less than + the \fpTeX{} distribution, so you can also go to the Web pages at + \url{http://www.fptex.org}, or consider subscribing to the \fpTeX{} + mailing-list by consulting + \url{http://www.tug.org/mailman/listinfo/fptex} . +\end{enumerate} + + +The \TeXLive{} software is complex and made of more than 250 programs +and around 40000 files from various sources. It is quite difficult to +predict all possible causes for problems. Nevertheless, we will do our +best to help you in every case. + + +\subsection{Compiling the source files} + +You have the whole set of source files, comprised for +Windows in the \path|source/source.tar.bz2| archive available on the +\CD{}. To be able to compile the whole distribution for Windows, you +will need: +\begin{itemize} +\item Windows 2K/XP +\item Microsoft Visual Studio .Net +\item a set of Unix tools (\texttt{sed}, + \texttt{grep}, \texttt{gawk}, etc.) and also Perl, Flex and Bison, +\item to adjust the paths in the + \path|win32/make/common.mak| file according to your installation +\item adjust the paths in the Perl script file + \path|win32/perl/build.pl|, +\item run the compilation from the \path|win32/| directory using this + command: +\begin{verbatim} +c:\texlive\source\win32>perl ./perl/build.pl --install --log=install.log +\end{verbatim} +\end{itemize} + +There is a lot of work to do to make this process easier and cleaner. + +\subsection{Where to get more information?} + +The Win32 \TeX{} distribution on the \CD{} is also known as +\fpTeX. Only the packaging differs, but \fpTeX{} is no more no less +than the current \TeXLive\ release for Windows. + +The \fpTeX home on the Web is at:\\ +\url{http://www.fptex.org/} + +The current \fpTeX release is available from any +\href{http://www.ctan.org}{CTAN} %(see also the section +%\ref{sec:ctan}) +site in the directory~:\\ +\noindent\url{ftp://ctan.tug.org/tex-archive/systems/win32/fptex/}. + +The main ftp site for \fpTeX\ is \url{ftp://ftp.dante.de/pub/fptex/} from +where beta versions of \fpTeX\ and additionnal tools are available. +This main site is (partially) mirrored daily by the CTAN backbones in their +\path|systems/win32/fptex| directory. + +% You can reach me at my email address: +% \url{mailto:Fabrice.Popineau@supelec.fr}. + +The \TeX{} Users Group is kindly hosting a mailing-list dedicated to +\fpTeX. This is a very low volume one. It is used for announcements, +bugs reports or as well to discuss about improvements or various users +problems. To subscribe, read the page at +\url{http://www.tug.org/mailman/listinfo/fptex}. The mailing list +address is \EmailURL{fptex@tug.org}. + +\section{Building on a new Unix platform} +If you have a platform for which we have not provided binary sources, +you will need to compile \TeX{} and friends from scratch. This is not +as hard as it sounds. What you need is all in the directory +\texttt{source} on the \CD{}. + +You should first install the support tree from the \TeXLive{} \CD{} (do +a basic install, with no system binaries chosen). + +\subsection{Prerequisites} +You will need about 100 megabytes of disk space to compile all of +\TeX{} and its support programs. You'll also need an \acro{ANSI} C +compiler, a \cmdname{make} utility, a lexical scanner, and a parser +generator. The \acro{GNU} utilities (\cmdname{gcc}, \acro{GNU} +\cmdname{make}, \cmdname{m4}, \cmdname{flex}, \cmdname{bison}) are the +most widely tested on different platforms. \cmdname{gcc}-2.7.* +\cmdname{flex}-2.4.7 and \acro{GNU}\,\cmdname{make}-3.72.1 or newer +should work well. You may be able to work with other C compilers and +\cmdname{make} programs, but you will need a good understanding of +building Unix programs to sort out problems. The command +\texttt{uname} must return a sensible value. + + + +\subsection{Configuration} +First, unpack the source from the compressed +\texttt{tar} file in the directory \dirname{source} to your disk and change +directory to where you placed it. Decide where the `root' of the +installation will be, e.g.\ \path|/usr/local| or +\path|/usr/local/TeX|. Obviously you should use the same location +that you specified when you installed the support tree. + +Now, start the build process by running \textsf{configure} with +a command-line like +\begin{alltt} +>> \Ucom{./configure -prefix=/usr/local/TeX} +\end{alltt} + +The `prefix' directory is the one where you installed the support +tree; the directory layout that will be used is as follows (where +\$TEXDIR stands for the directory you chose): + +\noindent +\begin{tabular}{>{\ttfamily}ll@{}} + \dirname{$TEXDIR/man} & Unix manual pages\\ + \dirname{$TEXDIR/share/texmf} & main tree with fonts,\\ + & \qquad macros, etc\\ + \dirname{$TEXDIR/info} & \acro{GNU} style info manuals\\ + \dirname{$TEXDIR/bin/$PLATFORM} & binaries\\ +\end{tabular} +%$ + +You can omit the use of `\dirname{share/}' part for the +\dirname{texmf} directory if you want, as +\dirname{$TEXDIR/share/texmf} and \dirname{$TEXDIR/texmf} are +auto-detected by configure. If you choose something different, you +have to specify that directory with the \verb|--datadir| option of +\textsf{configure}. + + +If you want to leave out the \dirname{$PLATFORM} directory level +(i.e.\ put the binaries directly into \dirname{$TEXDIR/bin}), specify +the \verb|--disable-multiplatform| option for \textsf{configure}. + + +Have a look at the output of \texttt{./configure --help} for more +options you can use (such as omitting optional packages such as \OMEGA\ +or \eTeX). + +\subsection{Running \textsf{make}} +Make sure the shell variable \texttt{noclobber} is not set, and +then type +\begin{alltt} +>> \Ucom{make world} +\end{alltt} +and relax\ldots. + +It could also be useful to log all the output, e.g.\ by +typing +\begin{alltt} +>> \Ucom{sh -c "make world >world.log 2>\&1" \&} +\end{alltt} +Before you think that everything is ok, please check the log file for +errors (\acro{GNU} \cmdname{make} always uses the string +``\texttt{Error:}'' whenever a command returns an error code) and +check if all binaries are built: +\begin{alltt} +>> \Ucom{cd /usr/local/TeX/bin/i686-pc-linux-gnu} +>> \Ucom{ls | wc} +\end{alltt} +The result should be 209. + +If you need special privileges for \texttt{make install}, you can +run two \cmdname{make} jobs in separate runs: +\begin{alltt} +>> \Ucom{make all} +>> \Ucom{su} +>> \Ucom{make install strip} +\end{alltt} + +\subsection{Final configuration steps} +Set up your \envname{PATH} to include the directory containing the +just-installed binaries (e.g.\ +\dirname{/usr/local/TeX/bin/mips-sgi-irix6.5}); similarly, +\envname{MANPATH} and \envname{INFOPATH} to include the relevant newly +installed subdirectories, i.e.\ \dirname{$TEXDIR/man} and +\dirname{$TEXDIR/info}. + +The program \textsf{texconfig} allows you to set the defaults for +hyphenation, paper size, print command, \MF{} mode, etc. You can +run this command interactively and see what options it offers, or type +\begin{alltt} +>> \Ucom{texconfig help} +\end{alltt} + +For example, if you are not using A4 format paper, you can make +`lettersize' the default using: +\begin{alltt} +>> \Ucom{texconfig dvips paper letter} +>> \Ucom{texconfig xdvi paper us} +\end{alltt} + +\section{A user's guide to the \protect\Webc{} system} + +%-------------------------------------------------------- + +\Webc{} contains a set of \TeX-related programs, i.e., \TeX{} itself, +\MF{}, \MP, \BibTeX{}, etc. The original implementation was by Tomas +Rokicki who, in 1987, developed a first \TeX{}-to-C system adapting +change files under Unix, which were primarily the work of Howard +Trickey and Pavel Curtis. Tim Morgan became the maintainer of the +system, and during this period the name changed to Web-to-C\@. In +1990, Karl Berry took over the work, assisted by dozens of additional +contributors, and in 1997 he handed the baton to Olaf Weber. The +latest result is \Webc{} Version 7.3, which was released in March +1999. Our version has some updates for the forthcoming new release, +and identifies itself as 7.3.7 + +The \Webc{} 7.3 system runs on Unix, Windows 3.1, 9x/ME/\acro{NT}/\acro{2K}/\acro{XP}, +\acro{DOS}, and other operating systems. It uses Knuth's +original sources for \TeX{} and other basic programs written in \web{} +and translates them into C source code. Moreover, the system offers a +large set of macros and functions developed to augment the original +\TeX{} software. The core \TeX{} family components are: + +\begin{description} +\renewcommand{\makelabel}[1]{\descriptionlabel{\mdseries\cmdname{#1}}} +\item[bibtex] Maintaining bibliographies. +\item[dmp] \cmdname{troff} to MPX (\MP{} pictures). +\item[dvicopy] Produces modified copy of \dvi{} file. +\item[dvitomp] \dvi{} to MPX (MetaPost pictures). +\item[dvitype] \dvi{} to human-readable text. +\item[gftodvi] Generic font proofsheets. +\item[gftopk] Generic to packed fonts. +\item[gftype] GF to human-readable text. +\item[makempx] \MP{} label typesetting. +\item[mf] Creating typeface families. +\item[mft] Prettyprinting \MF{} source. +\item[mpost] Creating technical diagrams. +\item[mpto] MetaPost label extraction. +\item[newer] Compare modification times. +\item[patgen] Creating hyphenation patterns. +\item[pktogf] Packed to generic fonts. +\item[pktype] PK to human-readable text. +\item[pltotf] Property list to TFM. +\item[pooltype] Display \web{} pool files. +\item[tangle] \web{} to Pascal. +\item[tex] Typesetting. +\item[tftopl] TFM to property list. +\item[vftovp] Virtual font to virtual property list +\item[vptovf] Virtual property list to virtual font. +\item[weave] \web{} to \TeX. +\end{description} +\noindent The precise functions and syntax of these programs are described in +the documentation of the individual packages or of \Webc{} itself. +However, knowing a few principles governing the whole family of +programs will help you to benefit optimally from your \Webc{} +installation. + +All programs honor the standard \acro{GNU} options: +\begin{description} +\item[\texttt{-{}-help\ \ \ }] print basic usage summary. +\item[\texttt{-{}-verbose}] print detailed progress report. +\item[\texttt{-{}-version}] print version information, then exit. +\end{description} + +For locating files the \Webc{} programs use the path searching library +\KPS{}. This library uses a combination of environment variables and a +few configuration files to optimize searching the \TeX{} directory +tree. \Webc{} can handle more than one directory tree +simultaneously, which is useful if one wants to maintain \TeX's +standard distribution and local extensions in two distinct trees. To +speed up file searches the root of each tree has a file \file{ls-R}, +containing an entry showing the name and relative pathname for all +files ``hanging'' under that root. + +\subsection{\protect\KPS\ path searching} + +Let us first describe the generic path searching mechanism of the \KPS{} +library. + +We call a \emph{search path} a colon- or semicolon\hyph sepa\-rated list +of \emph{path elements}, which are basically directory names. A +search path can come from (a combination of) many sources. To look up +a file \samp{my-file} along a path \samp{.:/dir}, \KPS{} checks each +element of the path in turn: first \file{./my-file}, then +\file{/dir/my-file}, returning the first match (or possibly all +matches). + +In order to adapt optimally to all operating systems' conventions, on +non-Unix systems \KPS{} can use filename separators different from +``colon'' (\samp{:}) and ``slash'' (\samp{/}). + +To check a particular path element \var{p}, \KPS{} first checks if a +prebuilt database (see ``Filename data\-base'' on +page~\pageref{Filename-database}) applies to \var{p}, i.e., if the database +is in a directory that is a prefix of \var{p}. If so, the path +specification is matched against the contents of the database. + +If the database does not exist, or does not apply to this path +element, or contains no matches, the filesystem is searched (if this +was not forbidden by a specification starting with \samp{!!}\ and if +the file being searched for must exist). \KPS{} constructs the list +of directories that correspond to this path element, and then checks +in each for the file being sought. + +The ``file must exist'' condition comes into play with \samp{.vf} files and +input files read by \TeX's \cs{openin} command. Such files may not +exist (e.g., \file{cmr10.vf}), and so it would be wrong to search the +disk for them. Therefore, if you fail to update \file{ls-R} when you +install a new \samp{.vf} file, it will never be found. +Each path element is checked in turn: first the database, then the +disk. If a match is found, the search stops and the result is +returned. + +Although the simplest and most common path element is a directory +name, \KPS{} supports additional features in search paths: layered +default values, environment variable names, config file values, users' +home directories, and recursive subdirectory searching. Thus, we say +that \KPS{} \emph{expands} a path element, meaning it transforms all +the specifications into basic directory name or names. This is +described in the following sections in the same order as it takes +place. + +Note that if the filename being searched for is absolute or explicitly +relative, i.e., starts with \samp{/} or \samp{./} or \samp{../}, +\KPS{} simply checks if that file exists. + +\ifSingleColumn +\else +\begin{figure*} +\verbatiminput{../examples/ex5.tex} +\setlength{\abovecaptionskip}{0pt} + \caption{An illustrative configuration file sample} + \label{fig:config-sample} +\end{figure*} +\fi + +\subsubsection{Path sources} +\label{Path-sources} + +A search path can come from many sources. In the order in which +\KPS{} uses them: + +\begin{enumerate} +\item + A user-set environment variable, for instance, \envname{TEXINPUTS}\@. + Environment variables with a period and a program name appended + override; e.g., if \samp{latex} is the name of the program being run, + then \envname{TEXINPUTS.latex} will override \envname{TEXINPUTS}. +\item + A program-specific configuration file, for exam\-ple, a line + ``\texttt{S /a:/b}'' in \cmdname{dvips}'s \file{config.ps}. +\item A \KPS{} configuration file \file{texmf.cnf}, containing a line like + \samp{TEXINPUTS=/c:/d} (see below). +\item The compile-time default. +\end{enumerate} +\noindent You can see each of these values for a given +search path by using the debugging options (see ``Debugging actions'' +on page~\pageref{Debugging}). + +\subsubsection{Config files} + +\tolerance=3500 +\KPS{} reads \emph{runtime configuration files} named \file{texmf.cnf} +for search path and other definitions. The search path used to look +for these files is named \envname{TEXMFCNF} (by default such a file lives +in the \file{texmf/web2c} subdirectory). \emph{All} +\file{texmf.cnf} files in the search path will be read and definitions +in earlier files override those in later files. Thus, with a search +path of \verb|.:$TEXMF|, values from \file{./texmf.cnf} override those +from \verb|$TEXMF/texmf.cnf|. + +\tolerance=1500 + +While reading the description of the format of the file +\file{texmf.cnf} below, please also refer to +appendix~\ref{app:texmf.cnf}, starting on +page~\pageref{app:texmf.cnf}, which lists the \file{texmf.cnf} file on +the \CD. + +\begin{itemize} +\item + Comments start with ``\texttt{\%}'' and continue to the end of the line. +\item + Blank lines are ignored. +\item + A \bs{} at the end of a line acts as a continuation character, + i.e., the next line is appended. Whitespace at the beginning of + continuation lines is not ignored. +\item + Each remaining line has the form: +\begin{alltt} + \emph{variable}[.\emph{progname}] [=] \emph{value} +\end{alltt}% + where the \samp{=} and surrounding whitespace are optional. +\item + The ``\texttt{\var{variable}}'' name may contain any character other + than whitespace, \samp{=}, or \samp{.}, but sticking to + \samp{A-Za-z\_} is safest. +\item + If ``\texttt{.\var{progname}}'' is present, the definition only + applies if the program that is running is named + \texttt{\var{progname}} or \texttt{\var{progname}.exe}. This allows + different flavors of \TeX{} to have different search paths, for + example. +\item ``\texttt{\var{value}}'' may contain any characters except + ``\texttt{\%}'' and \samp{@}. The + ``\texttt{\$\var{var}.\var{prog}}'' feature is not available on the + right-hand side; instead, you must use an additional variable. A + \samp{;}\ in ``\texttt{\var{value}}'' is translated to \samp{:}\ if + running under Unix; this is useful to be able to have a single + \file{texmf.cnf} for Unix, MSDOS and Windows systems. +\item + All definitions are read before anything is expanded, so + variables can be referenced before they are defined. +\end{itemize} +A configuration file fragment illustrating most of these points is +\ifSingleColumn +shown below: + +\verbatiminput{../examples/ex5.tex} +\else +shown in Figure~\ref{fig:config-sample}. +\fi + +\subsubsection{Path expansion} +\label{Path-expansion} + + +\KPS{} recognizes certain special characters and constructions in +search paths, similar to those available in Unix shells. As a +general example, the complex path, +\verb+~$USER/{foo,bar}//baz+, expands to all subdirectories under +directories \file{foo} and \file{bar} in \texttt{\$USER}'s home +directory that contain a directory or file \file{baz}. These +expansions are explained in the sections below. +%$ +\subsubsection{Default expansion} +\label{Default-expansion} + +\tolerance=2500 +If the highest-priority search path (see ``Path sources'' on +page~\pageref{Path-sources}) contains an \emph{extra colon} (i.e., +leading, trailing, or doubled), \KPS{} inserts at that point the +next-highest-prio\-rity search path that is defined. If that inserted +path has an extra colon, the same happens with the next highest. For +example, given an environment variable setting + +\tolerance=1500 + +\begin{alltt} +>> \Ucom{setenv TEXINPUTS /home/karl:} +\end{alltt} +and a \code{TEXINPUTS} value from \file{texmf.cnf} of + +\begin{alltt} + .:\$TEXMF//tex +\end{alltt} +then the final value used for searching will be: + +\begin{alltt} + /home/karl:.:\$TEXMF//tex +\end{alltt} + +Since it would be useless to insert the default value in more than one +place, \KPS{} changes only one extra \samp{:}\ and leaves any others in +place: it checks first for a leading \samp{:}, then a trailing +\samp{:}, then a doubled \samp{:}. + +\subsubsection{Brace expansion} + +A useful feature is brace expansion, which means that, for instance, +\verb+v{a,b}w+ expands to \verb+vaw:vbw+. Nesting is allowed. +This can be used to implement multiple \TeX{} hierarchies, by +assigning a brace list to \code{\$TEXMF}. +For example, in \file{texmf.cnf}, you find +the following definition: +\begin{verbatim} + TEXMF = {$HOMETEXMF,$TEXMFLOCAL,!!$VARTEXMF,!!$TEXMFMAIN} +\end{verbatim} +Using this you can then write something like +\begin{verbatim} + TEXINPUTS = .;$TEXMF/tex// +\end{verbatim} +%$ +which means that, after looking in the current directory, the +\code{\$HOMETEXMF/tex}, \code{\$TEXMFLOCAL/tex}, \code{\$VARTEXMF/tex} +and \code{\$TEXMFMAIN/tex} trees \emph{only}) will be searched (the +last two use using \file{ls-R} data base files). It is a convenient +way for running two parallel \TeX{} structures, one ``frozen'' (on a +\CD, for instance) and the other being continuously updated with new +versions as they become available. By using the \code{\$TEXMF} +variable in all definitions, one is sure to always search the +up-to-date tree first. + +\subsubsection{Subdirectory expansion} +\label{Subdirectory-expansion} + +Two or more consecutive slashes in a path element following a directory +\var{d} is replaced by all subdirectories of \var{d}: first those +subdirectories directly under \var{d}, then the subsubdirectories under +those, and so on. At each level, the order in which the directories are +searched is \emph{unspecified}. + +If you specify any filename components after the \samp{//}, only +subdirectories with matching components are included. For example, +\samp{/a//b} expands into directories \file{/a/1/b}, \file{/a/2/b}, +\file{/a/1/1/b}, and so on, but not \file{/a/b/c} or \file{/a/1}. + +Multiple \samp{//} constructs in a path are possible, but +\samp{//} at the beginning of a path is ignored. + +\subsubsection{List of special characters and their meaning: a summary} + +The following list summarises the meaning of special characters +in \KPS{} configuration files. + +\newcommand{\CODE}[1]{\makebox[2.2em][l]{\code{#1}}} +\begin{description} +\item[\CODE{:}] Separator in path specification; at the beginning or + the end of a path it substitutes the default path expansion. +\item[\CODE{;}] Separator on non-Unix systems (acts like \code{:}). +\item[\CODE{\$}] Variable expansion. +\item[\CODE{\string~}] Represents the user's home directory. +\item[\CODE{\char`\{\dots\char`\}}] Brace expansion, e.g., + \verb+a{1,2}b+ will become \verb+a1b:a2b+. +\item[\CODE{//}] Subdirectory expansion (can occur anywhere in + a path, except at its beginning). +\item[\CODE{\%}] Start of comment. +\item[\CODE{\bs}] Continuation character (allows multi-line entries). +\item[\CODE{!!}] Search \emph{only} database to locate file, \emph{do + not} search the disk. +\end{description} + + +\subsection{Filename databases} +\label{Filename-database} + + +\KPS{} goes to some lengths to minimize disk accesses for searches. +Nevertheless, at installations with enough directories, searching each +possible directory for a given file can take an excessively long time +(this is especially true if many hundreds of font directories have to +be traversed.) Therefore, \KPS{} can use an externally-built +``database'' file named \file{ls-R} that maps files to directories, +thus avoiding the need to exhaustively search the disk. + +A second database file \file{aliases} allows you to give additional +names to the files listed in \file{ls-R}. This can be helpful to +adapt to DOS-like ``8.3'' filename conventions in source files. + +\subsubsection{The filename database} +\label{ls-R} + +As explained above, the name of the main filename database must be +\file{ls-R}. You can put one at the root of each \TeX{} hierarchy in +your installation that you wish to be searched (\code{\$TEXMF} by +default); most sites have only one hierarchy. \KPS{} looks for +\file{ls-R} files along the \code{TEXMFDBS} path. + +The recommended way to create and maintain \samp{ls-R} is to run the +\code{mktexlsr} script included with the distribution. It is invoked +by the various \samp{mktex}\dots\ scripts. In principle, this script +just runs the command +\begin{alltt} +cd \var{/your/texmf/root} && ls -LAR ./ >ls-R +\end{alltt} +presuming your system's \code{ls} produces the right output format +(\acro{GNU}'s \code{ls} is all right). To ensure that the database is always +up to date, it is easiest to rebuild it regularly via \code{cron}, so +that for changes in the installed files\Dash perhaps after installing or +updating a \LaTeX{} package\Dash the file \file{ls-R} is automatically +updated. + +If a file is not found in the database, by default \KPS{} goes ahead +and searches the disk. If a particular path element begins with +\samp{!!}, however, \emph{only} the database will be searched for that +element, never the disk. + + +\subsubsection{kpsewhich: Standalone path searching} +\label{Invoking-kpsewhich} + +The \texttt{kpsewhich} program exercises path searching independent of any +particular application. This can be useful as a sort of \code{find} +program to locate files in \TeX{} hierarchies (this is used heavily in +the distributed \samp{mktex}\dots\ scripts). + +\begin{alltt} +>> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} +\end{alltt} +The options specified in ``\texttt{\var{option}}'' can start with either \samp{-} +or \samp{-{}-}, and any unambiguous abbreviation is accepted. + +\KPS{} looks up each non-option argument on the command line as a +filename, and returns the first file found. There is no option to +return all the files with a particular name (you can run the Unix +\samp{find} utility for that). + +The more important options are described next. + +\begin{description} +\item[\texttt{-{}-dpi=\var{num}}]\mbox{} + Set the resolution to ``\texttt{\var{num}}''; this only affects \samp{gf} + and \samp{pk} lookups. \samp{-D} is a synonym, for compatibility + with \cmdname{dvips}. Default is 600. +\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ + Set the format for lookup to ``\texttt{\var{name}}''. By default, the + format is guessed from the filename. For formats which do not have + an associated unambiguous suffix, such as \MP{} support files and + \cmdname{dvips} configuration files, you have to specify the name as + found in the first column of Table~\ref{TABKpathsea}, which lists + currently recognized names, a description, + associated environment variables%, + \footnote{You can find definitions for these environment variables + in the file \file{texmf.cnf} (page~\pageref{app:texmf.cnf})}, and + possible file extensions. +\end{description} + + +\def\KpathKey#1#2#3#4#5{% name, number, description, variables, + % suffixes +\SetRowColor#1 & #3 & #4 & #5\\} +\def\HEAD#1{\multicolumn{1}{l}{\emph{#1}}} +% +\begin{small} +% a footnoterule immediately under a bottom-of-page rule looks dead +% silly, so we suppress it +\renewcommand\footnoterule{\relax} +% +\begin{longtable}{@{}% + >{\ttfamily}P{.16\textwidth}% Col.1 + P{.3\textwidth}% Col 2 + >{\ttfamily\footnotesize}P{.29\textwidth}% Col 3 + >{\ttfamily}P{.14\textwidth}% Col 4 +@{}} +\caption{Kpathsea file types}\label{TABKpathsea}\\ +\emph{Name} & \HEAD{Description} & \HEAD{Variables} +& \HEAD{Suffixes}\\ +\hline +\endfirsthead +\multicolumn{3}{l}{Kpathsea file types \emph{continued}}\\ +\emph{Name} & \HEAD{Description} & \HEAD{Variables} +& \HEAD{Suffixes}\\ +\hline +\noalign{\vspace{2pt}} +\endhead +\mbox{}\\ +\hline +\endfoot +\KpathKey + {afm} + {4} + {Adobe font metrics} + {AFMFONTS} + {.afm} +\KpathKey + {base} + {5} + {Metafont memory dump} + {MFBASES, TEXMFINI} + {.base} +\KpathKey + {bib} + {6} + {\BibTeX{} bibliography source} + {BIBINPUTS, TEXBIB} + {.bib} +\KpathKey + {} + {2} + {bitmap fonts} + {GLYPHFONTS, TEXFONTS} + {} +\KpathKey + {bst} + {7} + {\BibTeX{} style files} + {BSTINPUTS} + {.bst} +\KpathKey + {cnf} + {8} + {Runtime configuration files} + {TEXMFCNF} + {.cnf} +\KpathKey + {dvips config} + {34} + {\textsf{dvips} configuration files, e.g., \file{config.ps} + and \file{psfonts.map}} + {TEXCONFIG} + {.map} +\KpathKey + {fmt} + {10} + {\TeX{} memory dump} + {TEXFORMATS, TEXMFINI} + {.fmt, .efmt, .efm} +\KpathKey + {gf} + {0} + {generic font bitmap} + {GFFONTS} + {.gf} +\KpathKey + {graphic/figure} + {25} + {Encapsulated PostScript figures} + {TEXPICTS, TEXINPUTS} + {.eps, .epsi} +\KpathKey + {ist} + {35} + {\textsf{makeindex} style files} + {TEXINDEXSTYLE, INDEXSTYLE} + {.ist} +\KpathKey + {ls-R} + {9} + {Filename databases} + {TEXMFDBS} + {} +\KpathKey + {map} + {11} + {Fontmaps} + {TEXFONTMAPS} + {.map} +\KpathKey + {mem} + {12} + {MetaPost memory dump} + {MPMEMS, TEXMFINI} + {.mem} +\KpathKey + {mf} + {13} + {Metafont source} + {MFINPUTS} + {.mf} +\KpathKey + {mfpool} + {14} + {Metafont program strings} + {MFPOOL, TEXMFINI} + {.pool} +\KpathKey + {mft} + {15} + {MFT style file} + {MFTINPUTS} + {.mft} +\KpathKey + {} + {41} + {miscellaneous fonts} + {MISCFONTS} + {} +\KpathKey + {mp} + {16} + {MetaPost source} + {MPINPUTS} + {.mp} +\KpathKey + {mppool} + {17} + {MetaPost program strings} + {MPPOOL, TEXMFINI} + {.pool} +\KpathKey + {MetaPost support} + {18} + {MetaPost support files, used by DMP} + {MPSUPPORT} + {} +\KpathKey + {ocp} + {19} + {\OMEGA{} compiled process files} + {OCPINPUTS} + {.ocp} +\KpathKey + {ofm} + {20} + {\OMEGA{} font metrics} + {OFMFONTS, TEXFONTS} + {.ofm, .tfm} +\KpathKey + {opl} + {21} + {\OMEGA{} property lists} + {OPLFONTS, TEXFONTS} + {.opl} +\KpathKey + {otp} + {22} + {\OMEGA{} translation process files} + {OTPINPUTS} + {.otp} +\KpathKey + {ovf} + {23} + {\OMEGA{} virtual fonts} + {OVFFONTS, TEXFONTS} + {.ovf} +\KpathKey + {ovp} + {24} + {\OMEGA{} virtual property lists} + {OVPFONTS, TEXFONTS} + {.ovp} +\KpathKey + {pk} + {1} + {packed bitmap fonts} + {\emph{program}FONTS \textrm{(\texttt{\emph{program}} being + \textsmaller{\cmdname{XDVI}}, + etc.)}, PKFONTS, TEXPKS, GLYPHFONTS, TEXFONTS} + {.pk} +\KpathKey + {PostScript header} + {30} + {downloadable PostScript} + {TEXPSHEADERS, PSHEADERS} + {.pro, .enc} +\KpathKey + {tex} + {26} + {\TeX{} source} + {TEXINPUTS} + {.tex, .cls, .sty, .clo, .def} +\KpathKey + {TeX system documentation} + {27} + {Documentation files for the \TeX{} system} + {TEXDOCS} + {} +\KpathKey + {TeX system sources} + {29} + {Source files for the \TeX{} system} + {TEXSOURCES} + {} +\KpathKey + {texpool} + {28} + {\TeX{} program strings} + {TEXPOOL, TEXMFINI} + {.pool} +\KpathKey + {tfm} + {3} + {\TeX{} font metrics} + {TFMFONTS, TEXFONTS} + {.tfm} +\KpathKey + {Troff fonts} + {31} + {Troff fonts, used by DMP} + {TRFONTS} + {} +\KpathKey + {truetype fonts} + {36} + {TrueType outline fonts} + {TTFONTS} + {.ttf, .ttc} +\KpathKey + {type1 fonts} + {32} + {Type 1 PostScript outline fonts} + {T1FONTS, T1INPUTS, TEXPSHEADERS, DVIPSHEADERS} + {.pfa, .pfb} +\KpathKey + {type42 fonts} + {37} + {Type 42 PostScript outline fonts} + {T42FONTS} + {} +\KpathKey + {vf} + {33} + {virtual fonts} + {VFFONTS, TEXFONTS} + {.vf} +\KpathKey + {web2c files} + {38} + {\Webc{} support files} + {WEB2C} + {} +\KpathKey + {other text files} + {39} + {text files used by `\textsf{foo}'} + {FOOINPUTS} + {} +\KpathKey + {other binary files} + {40} + {binary files used by `\textsf{foo}'} + {FOOINPUTS} + {} +\end{longtable} +\end{small} + + +\begin{multicols}{2} + +\begin{description} +\item[] The last two entries in Table~\ref{TABKpathsea} are special + cases, where the paths and environment variables depend on the name + of the program: the variable name is constructed by converting the + program name to upper case, and then appending \texttt{INPUTS}. + + The environment variables are set by default in the configuration + file \file{texmf.cnf}. It is only when you want to override one or + more of the values specified in that file that you might want to set + them explicitly in your execution environment. + + Note that the \samp{-{}-format} and \samp{-{}-path} options are mutually + exclusive. +\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ + Set the mode name to ``\texttt{\var{string}}''; this only affects \samp{gf} + and \samp{pk} lookups. No default: any mode will be found. +\item[\texttt{-{}-must-exist}]\mbox{}\\ + Do everything possible to find the files, notably including + searching the disk. By default, only the \file{ls-R} database is + checked, in the interest of efficiency. +\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ + Search along the path ``\texttt{\var{string}}'' (colon-% + separated as usual), + instead of guessing the search path from the filename. \samp{//} + and all the usual expansions are supported. + The options \samp{-{}-path} and \samp{-{}-format} are mutually + exclusive. +\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ + Set the program name to ``\texttt{\var{name}}''. + This can affect the search paths via the ``\texttt{.\var{prognam}}'' + feature in configuration files. + The default is \samp{kpsewhich}. +\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ + shows the path used for file lookups of file type ``\texttt{\var{name}}''. + Either a filename extension (\samp{.pk}, \samp{.vf}, etc.) or a + name can be used, just as with \samp{-{}-format} option. +\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ + sets the debugging options to ``\texttt{\var{num}}''. +\end{description} + + +\subsubsection{Examples of use} +\label{SExamplesofuse} + +Let us now have a look at \KPS{} in action. + +\begin{alltt} +>> \Ucom{kpsewhich article.cls} +/usr/local/texmf/tex/latex/base/article.cls +\end{alltt} +We are looking for the file \file{article.cls}. Since the \samp{.cls} +suffix is unambiguous we do not need to specify that we want to look for a +file of type ``tex'' (\TeX{} source file directories). We find it in +the subdirectory \file{tex/latex/base} below the \samp{TEXMF} root +directory. Similarly, all of the following are found without problems +thanks to their unambiguous suffix. +\begin{alltt} +>> \Ucom{kpsewhich array.sty} + /usr/local/texmf/tex/latex/tools/array.sty +>> \Ucom{kpsewhich latin1.def} + /usr/local/texmf/tex/latex/base/latin1.def +>> \Ucom{kpsewhich size10.clo} + /usr/local/texmf/tex/latex/base/size10.clo +>> \Ucom{kpsewhich small2e.tex} + /usr/local/texmf/tex/latex/base/small2e.tex +>> \Ucom{kpsewhich tugboat.bib} + /usr/local/texmf/bibtex/bib/beebe/tugboat.bib +\end{alltt} + +The latter is a \BibTeX{} bibliography database for \textsl{TUGBoat} articles. + +\begin{alltt} +>> \Ucom{kpsewhich cmr10.pk} +\end{alltt} +Font bitmap glyph files of type \file{.pk} are used by display +programs like \cmdname{dvips} and \cmdname{xdvi}. Nothing is returned in +this case since there are no pre-generated Computer Modern \samp{.pk} +files on our system (since we use the Type1 versions on the \CD{}). +\begin{alltt} +>> \Ucom{kpsewhich ecrm1000.pk} +\ifSingleColumn /usr/local/texmf/fonts/pk/ljfour/jknappen/ec/ecrm1000.600pk +\else +/usr/local/texmf/fonts/pk/ljfour/jknappen/ +... ec/ecrm1000.600pk +\fi\end{alltt} +For the extended Computer Modern files we had to generate \samp{.pk} +files, and since the default \MF{} mode on our installation is +\texttt{ljfour} with a base resolution of 600 dpi (dots per inch), +this instantiation is returned. +\begin{alltt} +>> \Ucom{kpsewhich -dpi=300 ecrm1000.pk} +\end{alltt} +In this case, when specifying that we are interested in a resolution +of 300dpi (\texttt{-dpi=300}) we see that no such font is available on +the system. In fact, a program like \cmdname{dvips} or \cmdname{xdvi} would +go off and actually build the \texttt{.pk} files at the required +resolution using the script \cmdname{mktexpk}. + +Next we turn our attention to \cmdname{dvips}'s header and configuration +files. We first look at one of the commonly used files, the general +prolog \file{tex.pro} for \TeX{} support, before turning our attention +to the generic configuration file (\file{config.ps}) and the +PostScript font map \file{psfonts.map}. As the \samp{.ps} suffix is +ambiguous we have to specify explicitly which type we are considering +(``\texttt{dvips config}'') for the file \texttt{config.ps}. +\begin{alltt} +>> \Ucom{kpsewhich tex.pro} + /usr/local/texmf/dvips/base/tex.pro +>> \Ucom{kpsewhich --format="dvips config" config.ps} + /usr/local/texmf/config/config.ps +>> \Ucom{kpsewhich psfonts.map} + /usr/local/texmf/dvips/base/psfonts.map +\end{alltt} + +We now take a closer look at the URW Times PostScript support files. +The name for these in Berry's font naming scheme is ``\texttt{utm}''. +The first file we look at is the configuration file, which contains +the name of the map file: +\begin{alltt} +>> \Ucom{kpsewhich --format="dvips config" config.utm} +/usr/local/texmf/dvips/psnfss/config.utm +\end{alltt} +The contents of that file is +\begin{alltt} + p +utm.map +\end{alltt} +which points to the file \file{utm.map}, which we want to +locate next. +\begin{alltt} +>> \Ucom{kpsewhich --format="dvips config" utm.map} + /usr/local/texmf/dvips/psnfss/utm.map +\end{alltt} +This map file defines the file names of the Type1 PostScript fonts in +the URW collection. Its contents look like (we only show part of the +lines): +\begin{alltt} + utmb8r NimbusRomNo9L-Medi ... > \Ucom{kpsewhich utmr8a.pfb} +\ifSingleColumn /usr/local/texmf/fonts/type1/urw/utm/utmr8a.pfb +\else /usr/local/texmf/fonts/type1/ +... urw/utm/utmr8a.pfb +\fi\end{alltt} + +It should be evident from these few examples how you can easily locate +the whereabouts of a given file. This is especially important if you +suspect that the wrong version of a file is picked up somehow, since +\cmdname{kpsewhich} will show you the first file encountered. + +\subsubsection{Debugging actions} +\label{Debugging} + +Sometimes it is necessary to investigate how a program resolves +file references. To make this feasible in a convenient way \KPS{} +offers various debug levels: +\begin{itemize} +\item[\texttt{\ 1}] \texttt{stat} calls (file tests). When running + with an up-to-date \file{ls-R} database this should almost give no + output. +\item[\texttt{\ 2}] References to hash tables (like \file{ls-R} + database, map files, configuration files). +\item[\texttt{\ 4}] File open and close operations. +\item[\texttt{\ 8}] General path information for file types + searched by \KPS. This is useful to find out where a particular + path for the file was defined. +\item[\texttt{16}] Directory list for each path element (only relevant + for searches on disk). +\item[\texttt{32}] File searches. +\end{itemize} +A value of \texttt{-1} will set all the above options; in practice you +will probably always use these levels if you need any debugging. + +Similarly, with the \cmdname{dvips} program, by setting a +combination of debug switches, one can follow in detail where files are being picked +up from. Alternatively, when a file is not found, the debug trace +shows in which directories the program looks for the given file, so +that one can get an indication what the problem~is. + +Generally speaking, as most programs call the \KPS{} library +internally, one can select a debug option by using the +\envname{KPATHSEA\_DEBUG} environment variable, and setting it to (a +combination of) values as described in the above list. + +(Note for Windows users: it is not easy to redirect +all messages to a file in this system. For diagnostic purposes +you can temporarily \texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log}). + +Let us consider, as an example, a small \LaTeX{} source file, +\file{hello-world.tex}, which contains the following input. +\begin{verbatim} + \documentclass{article} + \begin{document} + Hello World! + \end{document} +\end{verbatim} +This little file only uses the font \file{cmr10}, so let us look +how \cmdname{dvips} prepares the PostScript file (we want to use the Type1 +version of the Computer Modern fonts, hence the option \texttt{-Pcms}). +\begin{alltt} +>> \Ucom{dvips -d4100 hello-world -Pcms -o} +\end{alltt} +In this case we have combined \cmdname{dvips}'s debug class 4 (font +paths) with \KPS's path element expansion (see \cmdname{dvips} Reference +Manual, \OnCD{texmf/doc/html/dvips/dvips_toc.html}). +%\ifSingleColumn +%We get something +%like the following (we have rearranged the output for easier display): +%\begin{alltt}\small +%\input{../examples/ex6.tex} +%\end{alltt} +%\else +The output (slightly rearranged) appears in +Figure~\ref{fig:dvipsdbga}. +\begin{figure*}[tp] +\centering +\input{../examples/ex6a.tex} +\caption{Finding configuration files}\label{fig:dvipsdbga} + +\bigskip + +\input{../examples/ex6b.tex} +\caption{Finding the prolog file}\label{fig:dvipsdbgb} + +\bigskip + +\input{../examples/ex6c.tex} +\caption{Finding the font file}\label{fig:dvipsdbgc} +\end{figure*} +\cmdname{dvips} starts by locating its working files. First, +\file{texmf.cnf} is found, which gives the definitions of the search +paths for the other files, then the file database \file{ls-R} (to +optimize file searching) and the file \file{aliases}, which makes it +possible to declare several names (e.g., a short \acro{DOS}-like ``8.3'' and +a more natural longer version) for the same file. Then \cmdname{dvips} +goes on to find the generic configuration file \file{config.ps} +before looking for the customization file \file{.dvipsrc} (which, in +this case is \emph{not found}). Finally, \cmdname{dvips} locates the +config file for the Computer Modern PostScript fonts \file{config.cms} +(this was initiated with the \texttt{-Pcms} option on the \cmdname{dvips} +command). This file contains the list of the ``map'' files which +define the relation between the \TeX{}, PostScript and file system +names of the fonts. +\begin{alltt} +>> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} + p +ams.map + p +cms.map + p +cmbkm.map + p +amsbkm.map +\end{alltt} +\cmdname{dvips} thus goes on to find all these files, plus the generic +map file \file{psfonts.map}, which is always loaded (it contains +declarations for commonly used PostScript fonts; see the last part of +Section \ref{SExamplesofuse} for more details about PostScript map +file handling). + +At this point \cmdname{dvips} identifies itself to the user\ldots +\begin{alltt}\ifSingleColumn +This is dvips 5.78 Copyright 1998 Radical Eye Software (www.radicaleye.com) +\else\small{}This is dvips 5.78 Copyright 1998 Radical Eye... +\fi\end{alltt}% decided to accept slight overrun in tub case +\ifSingleColumn +\ldots and then goes on to look for the prolog file \file{texc.pro}, +\begin{alltt}\small +kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro +\end{alltt} +\else +then goes on to look for the prolog file \file{texc.pro} (see +Figure~\ref{fig:dvipsdbgb}). + +\fi +After having found the file in question, \cmdname{dvips} outputs +date and time, and informs us that it will generate the +file \file{hello-world.ps}, then that it needs the font file +\file{cmr10}, and that the latter is declared as ``resident'': +\begin{alltt}\small +TeX output 1998.02.26:1204' -> hello-world.ps +Defining font () cmr10 at 10.0pt +Font cmr10 is resident. +\end{alltt} +Now the search is on for the file \file{cmr10.tfm}, which is found, +then a few more prolog files (not shown) are referenced, and finally +the Type1 instance \file{cmr10.pfb} of the font is located and +included in the output file (see last line). +\begin{alltt}\small +kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, + path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: + /var/tex/fonts/tfm//). +kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm +kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, + ... + +kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb +[1] +\end{alltt} + +\subsection{Runtime options} + +Another of the nice features of \Webc{} is its possibility to +control a number of memory parameters (in particular, array sizes) via +the runtime file \file{texmf.cnf} read by \KPS{}. The listing of +\file{texmf.cnf} is shown in Appendix~\ref{app:texmf.cnf}, starting on +page~\pageref{app:texmf.cnf}; the settings of all parameters can be +found in Part 3 of that file. The more important control variables are: +\begin{description} +\item[\texttt{main\_memory}] + Total words of memory available, for + \TeX{}, \MF{} and \MP. You must make a new format file for each + different setting. For instance, you could generate a ``huge'' + version of \TeX{}, and call the format file \texttt{hugetex.fmt}. + Using the standard way of specifying the program name used by \KPS{}, + the particular value of the \texttt{main\_memory} variable will then + be read from \file{texmf.cnf} (compare the generic value + and the ``huge'' one instantiated by \texttt{hugetex}, + etc.). +\item[\texttt{extra\_mem\_bot}] + Extra space for ``large'' \TeX{} data structures: + boxes, glue, breakpoints, etc. Especially useful if you use + \PiCTeX{}. +\item[\texttt{font\_mem\_size}] + Number of words for font information available for \TeX. This + is more or less the total size of all TFM files read. +\item[\texttt{hash\_extra}] + Additional space for the hash table of control sequence names. + Approximately 10,000 control sequences can be stored in the main + hash table; if you have a large book with numerous cross-references, + this might not be enough. You can see that both the + \cmdname{hugetex} and \cmdname{pdflatex} program invocations ask for + an extra 15,000 control sequences (the default value of + \texttt{hash\_extra} is zero). +\end{description} +Of course, this facility is no substitute for truly dynamic arrays and +memory allocation, but since this is extremely difficult to implement +in present \TeX, these runtime parameters provide a practical compromise +allowing some flexibility. + +%-------------------------------------------------------- + + +\section{Acknowledgements}\label{sec:acknowl} +This edition of TeXLive is edited by Sebastian Rahtz, with the +major contributors being Fabrice Popineau, who has worked away +unceasingly at the Win32 part of the package (especially the setup!) +and contributed in many different ways with ideas, advice and code; +and Staszek Wawrykiewicz, who provided great checking feedback, and +co-ordinated the Polish contributions. Kaja Christiansen performed a +vital role in endless recompilations on assorted Unix platforms, and +Robin Laakso coordinated production for TUG. Vladimir Volovich +did great work on cleaning the source and making other improvements, +while Gerben Wierda did all the work for MacOSX. + +We are very grateful for past and present help from +\begin{itemize} +\item The German-speaking \TeX{} Users (DANTE e.V.), who provided a machine + on which the master of the CD-ROM is developed and maintained; and Rainer +Sch\"opf and Reinhard Zierke who look after it; +\item The Perforce company, for providing a free copy of their +excellent change management system, which we have used to + manage the CD-ROM +contents; +\item Karl Berry, who provided the original \Webc{} distribution, and + has continued to give invaluable advice, encouragement, and help; +\item Mimi Burbank, who arranged access + at the Florida State University School of Computational Science + and Information Technology + to a slew of different + computers to compile \TeX{} on, and acted as an essential guinea-pig + whenever asked; +\item Kaja Christiansen, who provided essential feedback, compilation, and + documentation preparation; +\item Thomas Esser, without whose marvellous \teTeX{} package this + \CD{} would certainly not exist, and whose continual help makes it a + better product; +\item Michel Goossens, who co-authored the documentation; +\item Eitan Gurari, whose \TeX4ht was used to create the \HTML{} + version of this documentation, and who worked tirelessly to improve + it at short notice; +\item Art Ogawa and Pat Monohon, who coordinated releases for TUG; +\item Petr Olsak, who coordinated and checked all the Czech/Slovak + material very carefully; +\item Olaf Weber, for his patient assembly and maintenance of Web2c; +\item Graham Williams, on whose work the catalogue of packages depends. +\end{itemize} + +Gerhard Wilhelms, Volker Schaa, Fabrice Popineau, Janka +Chleb\'\i{}kov\'a, Staszek Wawrykiewicz, Erik Frambach, and Ulrik +Vieth kindly translated documentation at various times into their +respective languages, checked other documentation, and provided very +welcome feedback. + + +\section{History} + +This \CD{} distribution is a joint effort by many \TeX{} Users +Groups, including those from Germany, the Netherlands, the UK, France, +the Czech Republic/Slovakia, India, Poland and Russia, as well as +the international TUG. +Discussion began in late 1993 when the Dutch \TeX{} Users Group was +starting work on its 4All\TeX{} \CD{} for \acro{MS-DOS} users, and it was +hoped at that time to issue a single, rational, \CD{} for all +systems. This was far too ambitious a target, but it did spawn not +only the very successful 4All\TeX{} \CD{}, but also the \acro{TUG} +Technical Council working group on a \emph{\TeX{} Directory + Structure}, which specified how to create consistent and manageable +collections of \TeX{} support files. The final draft of the \TDS{} was +published in the December 1995 issue of \textsl{TUGboat}, and it was clear from +an early stage that one desirable product would be a model structure +on \CD{}. The \CD{} you now have is a very direct result of the +working group's deliberations. It was also clear that the success of +the 4All\TeX{} \CD{} showed that Unix users would benefit from a +similarly easy system, and this is the other main strand of \TeXLive. + +We undertook to make a new Unix-based \TDS{} \CD{} in the autumn of +1995, and quickly identified Thomas Esser's \teTeX{} as the ideal +setup, as it already had multi-platform support and was built with +portability across file systems in mind. Thomas agreed to help, and +work began seriously at the start of 1996. The first edition was +released in May 1996. At the start of 1997, Karl Berry completed a +major new release of his \Webc{} package, which included nearly all +the features which Thomas Esser had added in \teTeX, and we decided to +base the 2nd edition of the \CD{} on the standard \Webc, with the +addition of \teTeX's \texttt{texconfig} script. The 3rd edition of the +\CD{} was based on a major revision of \Webc, 7.2, by Olaf Weber; at the +same time, a new revision of \teTeX was being made, +and \TeXLive{} shares almost all of its features. The 4th edition +followed the same pattern, using a new version of te\TeX, and a new +release of \Webc{} (7.3). The system now included a complete Windows setup. + +For the 5th edition (March 2000) many parts of the \CD{} were revised +and checked, updating hundreds of packages. Package details were +stored in XML files. But the major change for \TeX\ Live 5 was that +all non-free software was removed. Everything on this \CD{} should be +compatible with the Debian Free Software Guidelines +(\url{http://www.debian.org/intro/free}); we have done our best to +check the license conditions of all packages, but we would very much +appreciate hearing of any mistakes. + +The 6th edition (July 2001) had a lot material updated. The major +change was a new install concept: the user could select a more exact set +of needed collections. Language-related collections were completely +reorganized, so selecting any of them installs not only macros, fonts, +etc., but also prepares an appropriate \texttt{language.dat}. + +The 7th edition of 2002 had as a major addition a setup +for MacOSX, and the usual myriad of updates to all sorts +of packages and programs. An important goal was integration +of the source back with teTeX, to correct the drift apart +in versions 5 and 6. + +\section{Future versions} + +\emph{This \CD{} is not a perfect product!} We plan to re-issue it +once a year, and would like to provide more help material, more +utilities, more installation programs, and (of course) an +ever-improved and checked tree of macros and fonts. This work is all +done by hard-pressed volunteers in their limited spare time, and a +great deal remains to be done. If you can help, don't hesitate to put +your name forward! + +Corrections, suggestions and additions for future revisions +should be sent to:\hfill\null +\begin{quote} +Sebastian Rahtz\\ +{}7 Stratfield Road\\ +Oxford OX2 7BG\\ +United Kingdom\\ +\EmailURL{rahtz@tug.org} +\end{quote} + + +Updates, notes, and suggestions will be made available on \CTAN{} +in \path|info/texlive|. A \acro{WWW} page for +information and ordering details is at +\url{http://www.tug.org/tex-live.html}. + +\end{multicols} + +\Section{The texmf.cnf file} +\label{app:texmf.cnf} +\begin{small} +\listinginput{1}{../examples/texmf.cnf} +\end{small} + +\end{document} + + + +Notes on Nicolle Zellner's problems: +------------------------------------ +- autoexec.bat gave error, ``too many parameters''. +fix: in setvars.bat file, put "" around %PATH% to take care of spaces. + +- ``out of environment space'' when rebooting meant that autoexec.bat was +not executing properly-- path and texmfhome variable were not being set. +fix: put in config.sys file the line: shell=c:\command.com /e:1024 /p +(and reboot probably) + +[Note: alternative advice written by Pat: + The environment space is an area of memory in which the OS stores + variables such as path. To increase the memory size do the following: + + Open a MS-DOS window. Click on the Properties icon (looks like a hand + holding a sheet of paper). Click on the Memory tab in the Properties + window. Change the value under Initial Environment: to 4096. Apply the + properties. Click OK on the warning about needing to restart your computer. + The new environment memory will be in effect after the reboot.] + +- windvi did not retain settings. +fix: in setvars.bat file, add command: set Home=c:\Home and also create +the directory c:\Home. +copy windvi.cnf to c:\Home\ +reboot + +-ispell doesn't work (can't write to c:\tmp, can't create dictionary) +In addition to the the c:\Home addition above, create the folder: +d:\tmp\ (d: is where the files are that she is using.) +Now ispell should work from the command line. +Still can't get it to work from within \cmdname{WinShell}. (change cmd line to %c.tex, +it was reading the project main file) + + + +Notes on installing WinEdt: +--------------------------- +If you choose to install WinEdt, you will be asked for a folder name: any +folder name will do, as this is for temporary storage. An acceptable +choice is \verb+C:\Winedt+. Click \textbf{unzip}, then \textbf{OK}, +and finally \textbf{Close}. +--- + +later, to complete WinEdt installation: + +Run "winedt5.exe" and complete the setup procedure. + +Get from ftp://ftp.dante.de/pub/fptex/supplementary/ +30/08/2000 20:17 70 844 winedt5-cnf.zip +10/09/2000 10:43 839 086 winedt5-patch4.zip + +then unpack (use unzip or winzip with subdir creation enabled, NOT pkunzkip) + "winedt5-patch4.zip" inside the "c:\program files\winedt" directory +then at last unpack "winedt5-cnf.zip". + +When this is done, go inside the 'Options->Configurations' menu, +choose the "fpTeX Direct" option. + +If windvi previewer doesn't work, go to options->menu setup-> accessories +and change the Menu Setup so the call for DVI Preview is analogous to +the call for Dvips-- i.e., don't use "DVIVIEW" in the command line, +but rather fptex-bin and dviwin.exe. + + diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/live4ht.cfg-2004 b/Master/texmf/doc/texlive/source/texlive-en/archive/live4ht.cfg-2004 new file mode 100644 index 00000000000..8700827d62a --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/live4ht.cfg-2004 @@ -0,0 +1,36 @@ +% $Id$ +% tex4ht configuration file for the TeX Live documentation. +% +% The 2 means to separate output files for only the top sectioning levels. +% xhtml specifies the main output format. +% info for extra debugging info in the log files. +% Without the \begin{document}, LaTeX complains that it is missing. +% +\Preamble{2,xhtml,info} \begin{document} \EndPreamble + +% simplify output for HTML. We leave TeX and LaTeX alone, since tex4ht +% actually does the lowered E (and raised A) in CSS. +\def\OMEGA{Omega} +\def\LaTeXe{LaTeX2e} +\def\eTeX{e-\TeX} +\def\acro#1{#1} +\def\MF{Metafont} +\def\BibTeX{BibTeX} +\def\warningbox{} +\def\endwarningbox{} + +\newif\ifhackliterals +\ifx\tldocenglish\undefined \else \hackliteralstrue \fi +\ifx\tldocrussian\undefined \else \hackliteralstrue \fi +\ifx\tldocgerman\undefined \else \hackliteralstrue \fi +% +\ifhackliterals + % these definitions cause "missing } inserted" at \end{tabularx} in + % French and Czech. don't know why. + % + % don't make these into links, as happens with \path. We only have a couple + % special characters that actually occur. + \def\dirname{\texttt\bgroup\catcode`\$=12 \catcode`\_=12 \finishliteral} + \def\finishliteral#1{#1\egroup} + \let\filename=\dirname +\fi diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/mod.pl b/Master/texmf/doc/texlive/source/texlive-en/archive/mod.pl new file mode 100644 index 00000000000..4f8df5df762 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/mod.pl @@ -0,0 +1,976 @@ + +$M{"a0poster"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; +$M{"a4"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"a4wide"}="18 May 1996 11:33:54 Graham.Williams\@cmis.csiro.au"; +$M{"a5"}="19 Apr 1998 15:19:21 Graham.Williams\@cmis.csiro.au"; +$M{"a5comb"}="19 Apr 1998 15:19:21 Graham.Williams\@cmis.csiro.au"; +$M{"aaai"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; +$M{"abc2mtex"}="27 Nov 1996 13:50:01 Graham.Williams\@cmis.csiro.au"; +$M{"abstbook"}="5 Mar 1997 16:28:20 Graham.Williams\@cmis.csiro.au"; +$M{"abstyles"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"accents"}="25 Feb 1999 09:06:12 Graham.Williams\@cmis.csiro.au"; +$M{"accfonts"}="30 Jan 1999 06:16:19 Graham.Williams\@cmis.csiro.au"; +$M{"achemso"}="8 Jul 1998 08:11:28 Graham.Williams\@cmis.csiro.au"; +$M{"acronym"}="17 Nov 1997 09:21:35 Graham.Williams\@cmis.csiro.au"; +$M{"acroread"}="20 May 1997 18:04:58 Graham.Williams\@cmis.csiro.au"; +$M{"acrotex"}="2 Dec 1998 09:52:54 Graham.Williams\@cmis.csiro.au"; +$M{"adfathesis"}="23 Feb 1999 16:11:03 Graham.Williams\@cmis.csiro.au"; +$M{"adobe"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"adobeother"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"adobestd"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"adrlist"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"advdate"}="5 Mar 1997 11:25:37 Graham.Williams\@cmis.csiro.au"; +$M{"ae"}="5 Dec 1998 08:56:53 Graham.Williams\@cmis.csiro.au"; +$M{"afterpage"}="13 Aug 1998 05:36:56 Graham.Williams\@cmis.csiro.au"; +$M{"afthesis"}="15 Dec 1996 19:08:54 Graham.Williams\@cmis.csiro.au"; +$M{"aguplus"}="16 Sep 1998 06:02:47 Graham.Williams\@cmis.csiro.au"; +$M{"aiaa"}="24 Feb 1999 09:15:44 Graham.Williams\@cmis.csiro.au"; +$M{"akletter"}="1 Jun 1998 12:04:46 Graham.Williams\@cmis.csiro.au"; +$M{"alatex"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"alg"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"algorithms"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"alltt"}="28 May 1996 16:23:49 Graham.Williams\@cmis.csiro.au"; +$M{"alphanum"}="10 Mar 1998 06:11:22 Graham.Williams\@cmis.csiro.au"; +$M{"altfont"}="1 Jul 1996 21:06:06 Graham.Williams\@cmis.csiro.au"; +$M{"altfont"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"amiweb2c"}="25 Mar 1998 09:12:31 Graham.Williams\@cmis.csiro.au"; +$M{"amsbsy"}="18 Jun 1997 19:16:14 Graham.Williams\@cmis.csiro.au"; +$M{"amscd"}="1 Nov 1996 08:34:08 Graham.Williams\@cmis.csiro.au"; +$M{"amsfonts"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"amsfonts"}="9 Nov 1996 15:43:40 Graham.Williams\@cmis.csiro.au"; +$M{"amslatex"}="9 Nov 1996 15:40:28 Graham.Williams\@cmis.csiro.au"; +$M{"amslatex"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"amsltx11"}="9 Nov 1996 15:46:01 Graham.Williams\@cmis.csiro.au"; +$M{"amsmath"}="9 Nov 1996 16:15:32 Graham.Williams\@cmis.csiro.au"; +$M{"amsppt"}="24 Sep 1996 08:42:35 Graham.Williams\@cmis.csiro.au"; +$M{"amsppt1"}="25 Sep 1996 09:41:18 Graham.Williams\@cmis.csiro.au"; +$M{"amssym"}="25 Sep 1996 09:44:00 Graham.Williams\@cmis.csiro.au"; +$M{"amssymb"}="11 Nov 1996 20:19:40 Graham.Williams\@cmis.csiro.au"; +$M{"amstex"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"amstex"}="9 Nov 1996 15:47:35 Graham.Williams\@cmis.csiro.au"; +$M{"amstext"}="11 Nov 1996 20:24:24 Graham.Williams\@cmis.csiro.au"; +$M{"answers"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"answers"}="29 May 1996 13:08:24 Graham.Williams\@cmis.csiro.au"; +$M{"anttvf"}="5 Feb 1998 09:27:21 Graham.Williams\@cmis.csiro.au"; +$M{"anttvf"}="08 Feb 1998 staw\@gust.org.pl"; +$M{"antyktor"}="18 Jun 1998 10:23:35 Graham.Williams\@cmis.csiro.au"; +$M{"apa"}="12 Nov 1998 11:38:01 Graham.Williams\@cmis.csiro.au"; +$M{"apacite"}="12 Jul 1996 10:10:07 Graham.Williams\@cmis.csiro.au"; +$M{"apasoft"}="15 Sep 1998 06:39:47 Graham.Williams\@cmis.csiro.au"; +$M{"apl"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"appendix"}="11 Dec 1998 05:36:39 Graham.Williams\@cmis.csiro.au"; +$M{"ar"}="24 Apr 1998 16:02:22 Graham.Williams\@cmis.csiro.au"; +$M{"arabtex"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"arabtex"}="13 May 1997 16:45:22 Graham.Williams\@cmis.csiro.au"; +$M{"armenian"}="3 Jul 1997 08:23:26 Graham.Williams\@cmis.csiro.au"; +$M{"arosgn"}="21 Oct 1996 10:32:18 Graham.Williams\@cmis.csiro.au"; +$M{"arrow"}="7 Nov 1996 19:31:04 Graham.Williams\@cmis.csiro.au"; +$M{"asaetr"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; +$M{"ascii"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"astro"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"at"}="12 Nov 1996 09:27:11 Graham.Williams\@cmis.csiro.au"; +$M{"auctex"}="19 Oct 1998 06:10:29 Graham.Williams\@cmis.csiro.au"; +$M{"aurora"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"authorindex"}="16 Feb 1998 17:29:41 Graham.Williams\@cmis.csiro.au"; +$M{"autotab"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"babel"}="12 Jan 1997 11:26:33 Graham.Williams\@cmis.csiro.au"; +$M{"backgammon"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"bakoma-fonts"}="13 Dec 1996 08:26:36 Graham.Williams\@cmis.csiro.au"; +$M{"bakoma"}="22 Jan 1999 07:17:26 Graham.Williams\@cmis.csiro.au"; +$M{"barcode2"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"barcodes"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"barcodes"}="7 Jun 1996 13:43:47 Graham.Williams\@cmis.csiro.au"; +$M{"barr"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"bayer"}="10 Feb 1998 09:30:02 Graham.Williams\@cmis.csiro.au"; +$M{"bbding"}="13 May 1996 06:15:45 Graham.Williams\@cmis.csiro.au"; +$M{"bbding"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"bbm"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"beebe"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"belleek"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"beton"}="28 May 1996 16:24:30 Graham.Williams\@cmis.csiro.au"; +$M{"bez123"}="21 Oct 1998 09:36:53 Graham.Williams\@cmis.csiro.au"; +$M{"bezos"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"bibarts"}="19 Apr 1998 15:55:19 Graham.Williams\@cmis.csiro.au"; +$M{"bibindex"}="12 Jan 1997 14:53:39 Graham.Williams\@cmis.csiro.au"; +$M{"biblio"}="4 Oct 1996 08:44:47 Graham.Williams\@cmis.csiro.au"; +$M{"biblios"}="16 Aug 1996 14:40:47 Graham.Williams\@cmis.csiro.au"; +$M{"biblist"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"biblook"}="12 Jan 1997 14:53:39 Graham.Williams\@cmis.csiro.au"; +$M{"bibsort"}="12 Nov 1996 10:28:11 Graham.Williams\@cmis.csiro.au"; +$M{"bibtex8bit"}="19 Aug 1996 22:05:26 Graham.Williams\@cmis.csiro.au"; +$M{"bibtool"}="24 Feb 1998 13:38:41 Graham.Williams\@cmis.csiro.au"; +$M{"bibunits"}="29 May 1997 12:15:06 Graham.Williams\@cmis.csiro.au"; +$M{"bibweb"}="28 Nov 1997 09:12:23 Graham.Williams\@cmis.csiro.au"; +$M{"bidstobibtex"}="21 Oct 1996 13:54:10 Graham.Williams\@cmis.csiro.au"; +$M{"bitstrea"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"blackboard"}="9 Jul 1998 05:37:01 Graham.Williams\@cmis.csiro.au"; +$M{"blue"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"bluesky"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"bm"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"booktabs"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"borceux"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"bosisio"}="1 May 1998 16:53:18 Graham.Williams\@cmis.csiro.au"; +$M{"boxedminipage"}="19 Apr 1998 15:20:55 Graham.Williams\@cmis.csiro.au"; +$M{"breqn"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"bridge"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"brief"}="30 May 1996 11:22:14 Graham.Williams\@cmis.csiro.au"; +$M{"brushscr"}="24 Jun 1998 12:56:02 Graham.Williams\@cmis.csiro.au"; +$M{"btparse"}="20 Feb 1998 14:21:13 Graham.Williams\@cmis.csiro.au"; +$M{"c-pascal"}="3 Mar 1998 15:29:06 Graham.Williams\@cmis.csiro.au"; +$M{"c2cweb"}="29 Nov 1996 15:27:19 Graham.Williams\@cmis.csiro.au"; +$M{"calc"}="12 Aug 1998 06:27:04 Graham.Williams\@cmis.csiro.au"; +$M{"calendar"}="18 Mar 1997 13:07:53 Graham.Williams\@cmis.csiro.au"; +$M{"calendar"}="4 Feb 1998 13:36:58 Graham.Williams\@cmis.csiro.au"; +$M{"calligra"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"calrsfs"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"calrsfs"}="12 Jun 1996 09:16:09 Graham.Williams\@cmis.csiro.au"; +$M{"camel"}="5 Mar 1997 16:31:57 Graham.Williams\@cmis.csiro.au"; +$M{"cancel"}="26 May 1997 12:53:21 Graham.Williams\@cmis.csiro.au"; +$M{"capt-of"}="15 Dec 1996 19:04:36 Graham.Williams\@cmis.csiro.au"; +$M{"caption"}="12 Nov 1996 20:23:42 Graham.Williams\@cmis.csiro.au"; +$M{"carlisle"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"cases"}="15 Dec 1996 19:14:30 Graham.Williams\@cmis.csiro.au"; +$M{"casyl"}="24 Feb 1999 09:19:05 Graham.Williams\@cmis.csiro.au"; +$M{"catalogue"}="22 May 1996 16:49:04 Graham.Williams\@cmis.csiro.au"; +$M{"catdoc"}="5 Nov 1998 11:47:57 Graham.Williams\@cmis.csiro.au"; +$M{"cbgreek"}="24 Oct 1998 07:42:16 Graham.Williams\@cmis.csiro.au"; +$M{"cc-pl"}="09 Jun 1998 staw\@gust.org.pl"; +$M{"ccaption"}="27 Jan 1999 09:40:41 Graham.Williams\@cmis.csiro.au"; +$M{"ccfonts"}="23 Jun 1998 15:52:05 Graham.Williams\@cmis.csiro.au"; +$M{"cchess"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"cd-cover"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"cdcover"}="10 Feb 1998 09:31:30 Graham.Williams\@cmis.csiro.au"; +$M{"cdlabeler"}="2 Jan 1999 21:57:44 Graham.Williams\@cmis.csiro.au"; +$M{"cellular"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"cep"}="27 Jan 1998 16:53:11 Graham.Williams\@cmis.csiro.au"; +$M{"cep"}="08 Feb 1998 staw\@gust.org.pl"; +$M{"changebar"}="7 Oct 1997 09:02:24 Graham.Williams\@cmis.csiro.au"; +$M{"chapterbib"}="15 Dec 1996 19:13:07 Graham.Williams\@cmis.csiro.au"; +$M{"chemcono"}="21 Oct 1996 14:28:23 Graham.Williams\@cmis.csiro.au"; +$M{"chemcono"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"chemsym"}="8 Jul 1998 08:11:58 Graham.Williams\@cmis.csiro.au"; +$M{"cheq"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"cherokee"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"chess"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"china2e"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; +$M{"china2e"}="26 Feb 1998 08:51:49 Graham.Williams\@cmis.csiro.au"; +$M{"chktex"}="21 Oct 1996 13:51:58 Graham.Williams\@cmis.csiro.au"; +$M{"circ"}="18 Mar 1998 09:29:16 Graham.Williams\@cmis.csiro.au"; +$M{"circle"}="13 Oct 1998 09:09:47 Graham.Williams\@cmis.csiro.au"; +$M{"circuit-macro"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"circuit-macros"}="6 Sep 1998 05:00:37 Graham.Williams\@cmis.csiro.au"; +$M{"cirth"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"cite"}="15 Dec 1996 19:10:42 Graham.Williams\@cmis.csiro.au"; +$M{"cjk-fonts"}="8 Jan 1999 08:02:11 Graham.Williams\@cmis.csiro.au"; +$M{"cjk"}="8 Jan 1999 08:01:13 Graham.Williams\@cmis.csiro.au"; +$M{"cm"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"cmactex"}="9 Aug 1998 06:47:00 Graham.Williams\@cmis.csiro.au"; +$M{"cmbright"}="28 Dec 1998 09:33:43 Graham.Williams\@cmis.csiro.au"; +$M{"cmcyr"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"cmcyralt"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"cmdtrack"}="22 Feb 1999 16:17:02 Graham.Williams\@cmis.csiro.au"; +$M{"cmextra"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"cmpica"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"cmps"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"cmsd"}="19 Feb 1998 09:45:20 Graham.Williams\@cmis.csiro.au"; +$M{"cmtt"}="1 Jun 1996 15:43:59 Graham.Williams\@cmis.csiro.au"; +$M{"cmyk-hax"}="12 May 1997 10:23:51 Graham.Williams\@cmis.csiro.au"; +$M{"cmyk-hax"}="08 Feb 1998 staw\@gust.org.pl"; +$M{"code128"}="7 Jun 1996 13:42:22 Graham.Williams\@cmis.csiro.au"; +$M{"codepage"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"color"}="24 Sep 1996 08:56:07 Graham.Williams\@cmis.csiro.au"; +$M{"colorsep"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"colortbl"}="24 Jun 1998 13:01:21 Graham.Williams\@cmis.csiro.au"; +$M{"comma"}="11 Feb 1998 07:46:23 Graham.Williams\@cmis.csiro.au"; +$M{"comment"}="8 Sep 1998 06:29:57 Graham.Williams\@cmis.csiro.au"; +$M{"compsci"}="21 Oct 1996 14:11:57 Graham.Williams\@cmis.csiro.au"; +$M{"concmath"}="25 Dec 1996 UV"; +$M{"concprog"}="22 Oct 1996 09:37:54 Graham.Williams\@cmis.csiro.au"; +$M{"concrete-wrap"}="27 Nov 1996 13:57:24 Graham.Williams\@cmis.csiro.au"; +$M{"concrete"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"consdiag"}="21 Jan 1999 19:26:28 Graham.Williams\@cmis.csiro.au"; +$M{"context"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"corelpak"}="21 Jan 1999 14:00:25 Graham.Williams\@cmis.csiro.au"; +$M{"count1to"}="24 Oct 1998 09:04:16 Graham.Williams\@cmis.csiro.au"; +$M{"covington"}="22 Apr 1997 14:32:07 Graham.Williams\@cmis.csiro.au"; +$M{"croatian"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"crop"}="8 Dec 1998 09:21:42 Graham.Williams\@cmis.csiro.au"; +$M{"crossword"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"crosswrd"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"csfonts"}="3 May 1997 s.rahtz\@elsevier.co.uk"; +$M{"cslatex"}="3 May 1997 s.rahtz\@elsevier.co.uk"; +$M{"csplain"}="3 May 1997 s.rahtz\@elsevier.co.uk"; +$M{"cspsfonts"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"cstug"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"csx"}="12 Jul 1998 05:30:19 Graham.Williams\@cmis.csiro.au"; +$M{"cursor"}="20 Jan 1999 14:56:10 Graham.Williams\@cmis.csiro.au"; +$M{"custom-bib"}="18 Aug 1998 18:00:42 Graham.Williams\@cmis.csiro.au"; +$M{"cwebbin"}="16 Oct 1998 06:27:49 Graham.Williams\@cmis.csiro.au"; +$M{"cwebx"}="17 Feb 1999 16:44:14 Graham.Williams\@cmis.csiro.au"; +$M{"cwpuzzle"}="28 Nov 1996 10:09:18 Graham.Williams\@cmis.csiro.au"; +$M{"cyrtug"}="8 Oct 1998 11:51:48 Graham.Williams\@cmis.csiro.au"; +$M{"dancers"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"dante-src"}="11 Feb 1998 07:50:55 Graham.Williams\@cmis.csiro.au"; +$M{"dates"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"dblfont"}="1 May 1998 16:53:44 Graham.Williams\@cmis.csiro.au"; +$M{"dbprocess"}="2 Jan 1999 21:55:59 Graham.Williams\@cmis.csiro.au"; +$M{"dc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"dc"}="2 Jun 1996 11:09:21 Graham.Williams\@cmis.csiro.au"; +$M{"dco"}="16 Aug 1996 14:14:54 Graham.Williams\@cmis.csiro.au"; +$M{"dcounter"}="28 Dec 1998 09:21:00 Graham.Williams\@cmis.csiro.au"; +$M{"default"}="18 Jul 1998 06:43:35 Graham.Williams\@cmis.csiro.au"; +$M{"deleq"}="8 Jul 1998 08:12:25 Graham.Williams\@cmis.csiro.au"; +$M{"devanagari"}="7 Dec 1998 05:46:30 Graham.Williams\@cmis.csiro.au"; +$M{"dialogl"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"dinbrief"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"dinbrief"}="4 Nov 1996 09:56:05 Graham.Williams\@cmis.csiro.au"; +$M{"directory"}="10 Mar 1998 05:30:54 Graham.Williams\@cmis.csiro.au"; +$M{"dn2"}="13 Mar 1998 09:10:15 Graham.Williams\@cmis.csiro.au"; +$M{"doc"}="19 Aug 1996 22:19:13 Graham.Williams\@cmis.csiro.au"; +$M{"dotseqn"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"doublestroke"}="21 Oct 1996 13:56:41 Graham.Williams\@cmis.csiro.au"; +$M{"draftcopy"}="21 May 1996 12:52:54 Graham.Williams\@cmis.csiro.au"; +$M{"dratex"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"dropcaps"}="19 Jun 1996 13:38:04 Graham.Williams\@cmis.csiro.au"; +$M{"dropping"}="9 Jul 1998 06:27:48 Graham.Williams\@cmis.csiro.au"; +$M{"duerer"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"dvgtk"}="29 Apr 1997 14:45:04 Graham.Williams\@cmis.csiro.au"; +$M{"dvi2tty"}="7 Jun 1996 20:12:43 Graham.Williams\@cmis.csiro.au"; +$M{"dviconcat"}="1 Nov 1996 08:10:15 Graham.Williams\@cmis.csiro.au"; +$M{"dvicopy"}="= {1 Nov 1996 08:30:05 Graham.Williams\@cmis.csiro.au"; +$M{"dviljk"}="6 Apr 1998 06:10:01 Graham.Williams\@cmis.csiro.au"; +$M{"dvipaste"}="23 Feb 1998 15:46:09 Graham.Williams\@cmis.csiro.au"; +$M{"dvipdfm"}="2 Dec 1998 05:56:54 Graham.Williams\@cmis.csiro.au"; +$M{"dvips-os2"}="21 Jan 1999 13:57:52 Graham.Williams\@cmis.csiro.au"; +$M{"dvips-shell"}="5 Mar 1998 22:29:41 Graham.Williams\@cmis.csiro.au"; +$M{"dvips"}="13 May 1997 09:51:53 Graham.Williams\@cmis.csiro.au"; +$M{"dvipsdoc"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"dvipsk"}="6 Apr 1998 05:56:12 Graham.Williams\@cmis.csiro.au"; +$M{"ean"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"ean"}="7 Jun 1996 13:44:26 Graham.Williams\@cmis.csiro.au"; +$M{"easy"}="18 Aug 1998 18:24:49 Graham.Williams\@cmis.csiro.au"; +$M{"easybib"}="7 Mar 1997 16:54:36 Graham.Williams\@cmis.csiro.au"; +$M{"easybmat"}="18 Aug 1998 18:27:38 Graham.Williams\@cmis.csiro.au"; +$M{"easyeqn"}="18 Nov 1997 15:21:55 Graham.Williams\@cmis.csiro.au"; +$M{"easymat"}="18 Aug 1998 18:28:31 Graham.Williams\@cmis.csiro.au"; +$M{"easytable"}="18 Aug 1998 18:28:50 Graham.Williams\@cmis.csiro.au"; +$M{"easyvector"}="18 Nov 1997 15:22:16 Graham.Williams\@cmis.csiro.au"; +$M{"ec-plain"}="21 Apr 1998 08:38:32 Graham.Williams\@cmis.csiro.au"; +$M{"ec"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"ecc"}="11 Dec 1998 08:59:53 Graham.Williams\@cmis.csiro.au"; +$M{"ecltree"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"eco"}="22 Jul 1998 09:13:53 Graham.Williams\@cmis.csiro.au"; +$M{"ecpk"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"edmac"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"eepic"}="28 Dec 1998 09:32:41 Graham.Williams\@cmis.csiro.au"; +$M{"egplot"}="9 Jul 1998 06:27:09 Graham.Williams\@cmis.csiro.au"; +$M{"eiad"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"eijkhout"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"elsevier"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"elvish"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"emp"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; +$M{"emp"}="26 Feb 1998 08:53:14 Graham.Williams\@cmis.csiro.au"; +$M{"emtex-os2"}="31 Jul 1998 10:16:40 Graham.Williams\@cmis.csiro.au"; +$M{"emtex"}="31 Jul 1998 10:16:40 Graham.Williams\@cmis.csiro.au"; +$M{"emtexgi"}="12 Jan 1997 11:32:36 Graham.Williams\@cmis.csiro.au"; +$M{"emtextds"}="30 Sep 1998 07:58:58 Graham.Williams\@cmis.csiro.au"; +$M{"emulateapj"}="27 Nov 1997 17:06:10 Graham.Williams\@cmis.csiro.au"; +$M{"encodings"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"endfloat"}="21 Jun 1996 14:52:55 Graham.Williams\@cmis.csiro.au"; +$M{"endnotes"}="3 Sep 1996 09:20:05 Graham.Williams\@cmis.csiro.au"; +$M{"endnotes"}="4 Feb 1998 13:33:16 Graham.Williams\@cmis.csiro.au"; +$M{"engwar"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"enumerate"}="22 Jul 1998 05:47:30 Graham.Williams\@cmis.csiro.au"; +$M{"envbig"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"envlab"}="17 Jul 1997 14:37:23 Graham.Williams\@cmis.csiro.au"; +$M{"epic"}="24 Jul 1998 06:18:39 Graham.Williams\@cmis.csiro.au"; +$M{"epigraph"}="1 Dec 1998 12:42:01 Graham.Williams\@cmis.csiro.au"; +$M{"eplain"}="19 Aug 1996 22:10:25 Graham.Williams\@cmis.csiro.au"; +$M{"epmtfe"}="23 Feb 1999 15:01:08 Graham.Williams\@cmis.csiro.au"; +$M{"epsfx"}="09 Jun 1998 staw\@gust.org.pl"; +$M{"epslatex"}="9 Feb 1998 09:22:51 Graham.Williams\@cmis.csiro.au"; +$M{"eqname"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"esieecv"}="26 Feb 1998 08:54:52 Graham.Williams\@cmis.csiro.au"; +$M{"esieecv"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; +$M{"esindex"}="10 Nov 1998 10:40:44 Graham.Williams\@cmis.csiro.au"; +$M{"eso-pic"}="22 Jul 1998 06:17:37 Graham.Williams\@cmis.csiro.au"; +$M{"et"}="24 Feb 1998 13:45:45 Graham.Williams\@cmis.csiro.au"; +$M{"etexbase"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"ethiop"}="13 Dec 1998 15:02:18 Graham.Williams\@cmis.csiro.au"; +$M{"euler"}="5 Jun 1996 10:03:48 Graham.Williams\@cmis.csiro.au"; +$M{"euro"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"eurofont"}="31 Jan 1999 07:41:02 Graham.Williams\@cmis.csiro.au"; +$M{"europs"}="21 Jan 1999 13:04:27 Graham.Williams\@cmis.csiro.au"; +$M{"eurosans"}="27 Jan 1999 08:25:26 Graham.Williams\@cmis.csiro.au"; +$M{"eurosym"}="6 Jan 1999 07:26:11 Graham.Williams\@cmis.csiro.au"; +$M{"everysel"}="10 Aug 1998 09:05:43 Graham.Williams\@cmis.csiro.au"; +$M{"everyshi"}="10 Aug 1998 09:20:24 Graham.Williams\@cmis.csiro.au"; +$M{"exam"}="16 Dec 1998 08:31:47 Graham.Williams\@cmis.csiro.au"; +$M{"examdesign"}="20 Jan 1998 22:03:03 Graham.Williams\@cmis.csiro.au"; +$M{"exams"}="29 May 1996 13:09:04 Graham.Williams\@cmis.csiro.au"; +$M{"excalibur"}="8 Nov 1998 07:01:25 Graham.Williams\@cmis.csiro.au"; +$M{"expdlist"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"expl3"}="1 Jun 1998 12:09:40 Graham.Williams\@cmis.csiro.au"; +$M{"export"}="12 Jan 1997 11:45:06 Graham.Williams\@cmis.csiro.au"; +$M{"export"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"exscale"}="12 Jun 1996 06:53:11 Graham.Williams\@cmis.csiro.au"; +$M{"extdash"}="28 Dec 1998 09:21:00 Graham.Williams\@cmis.csiro.au"; +$M{"fancybox"}="2 Mar 1998 09:20:57 Graham.Williams\@cmis.csiro.au"; +$M{"fancyhdr"}="9 Sep 1998 06:51:16 Graham.Williams\@cmis.csiro.au"; +$M{"fancyref"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"fancyvrb"}="1 Apr 1998 06:01:31 Graham.Williams\@cmis.csiro.au"; +$M{"faq"}="1 Jul 1998 10:31:39 Graham.Williams\@cmis.csiro.au"; +$M{"fax"}="13 Dec 1996 09:32:37 Graham.Williams\@cmis.csiro.au"; +$M{"fc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"fc"}="5 Mar 1998 22:19:31 Graham.Williams\@cmis.csiro.au"; +$M{"fepslatex"}="6 Nov 1998 05:54:05 Graham.Williams\@cmis.csiro.au"; +$M{"feynmf"}="30 May 1996 06:34:12 Graham.Williams\@cmis.csiro.au"; +$M{"fihyph"}=" from fihyph.tex to make the Finnish accented"; +$M{"fihyph"}="6 Nov 1998 06:34:36 Graham.Williams\@cmis.csiro.au"; +$M{"finbib"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"finplain"}="29 Jun 1998 10:04:25 Graham.Williams\@cmis.csiro.au"; +$M{"fix2col"}="19 Aug 1998 16:52:30 Graham.Williams\@cmis.csiro.au"; +$M{"fixfloat"}="23 May 1997 09:28:11 Graham.Williams\@cmis.csiro.au"; +$M{"flabels"}="21 Jul 1997 09:34:31 Graham.Williams\@cmis.csiro.au"; +$M{"flatex"}="24 Sep 1996 08:59:43 Graham.Williams\@cmis.csiro.au"; +$M{"flatten"}="18 Jun 1996 09:36:48 Graham.Williams\@cmis.csiro.au"; +$M{"float"}="25 May 1996 07:26:32 Graham.Williams\@cmis.csiro.au"; +$M{"floatflt"}="8 Jul 1998 08:16:33 Graham.Williams\@cmis.csiro.au"; +$M{"fltpage"}="19 Nov 1998 05:29:33 Graham.Williams\@cmis.csiro.au"; +$M{"fncychap"}=" Each can be using a set of simple commands."; +$M{"fncychap"}="13 Dec 1996 08:41:01 Graham.Williams\@cmis.csiro.au"; +$M{"fnpara"}="10 Sep 1996 09:23:00 Graham.Williams\@cmis.csiro.au"; +$M{"foilhtml"}="19 Feb 1998 09:39:43 Graham.Williams\@cmis.csiro.au"; +$M{"foiltex"}="15 Aug 1998 07:01:05 Graham.Williams\@cmis.csiro.au"; +$M{"fontinst"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"fontmisc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"fontname"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"fonts"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"footbib"}="19 Jun 1997 11:31:23 Graham.Williams\@cmis.csiro.au"; +$M{"footmisc"}="22 Jun 1998 16:47:47 Graham.Williams\@cmis.csiro.au"; +$M{"footnpag"}="10 Sep 1996 09:26:38 Graham.Williams\@cmis.csiro.au"; +$M{"formats"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"formlett"}="27 May 1997 09:39:35 Graham.Williams\@cmis.csiro.au"; +$M{"formula"}="18 Jun 1998 10:24:39 Graham.Williams\@cmis.csiro.au"; +$M{"fourtex"}="21 Nov 1998 05:32:50 Graham.Williams\@cmis.csiro.au"; +$M{"fp"}="4 Nov 1996 09:45:28 Graham.Williams\@cmis.csiro.au"; +$M{"freefonts"}="10 Sep 1998 18:50:47 Graham.Williams\@cmis.csiro.au"; +$M{"freetype"}="2 Jan 1999 22:37:14 Graham.Williams\@cmis.csiro.au"; +$M{"french"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"fribrief"}="20 Jan 1998 21:50:51 Graham.Williams\@cmis.csiro.au"; +$M{"ftetx"}="24 Feb 1998 13:52:42 Graham.Williams\@cmis.csiro.au"; +$M{"ftn"}="10 Sep 1996 09:43:47 Graham.Williams\@cmis.csiro.au"; +$M{"ftnright"}="19 Aug 1996 22:20:55 Graham.Williams\@cmis.csiro.au"; +$M{"fullblck"}="18 Nov 1998 09:21:36 Graham.Williams\@cmis.csiro.au"; +$M{"fullpict"}="18 Feb 1999 10:39:07 Graham.Williams\@cmis.csiro.au"; +$M{"fundus"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"funnelweb"}="25 Jun 1996 12:38:19 Graham.Williams\@cmis.csiro.au"; +$M{"futhark"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"g-brief"}="20 Feb 1998 14:17:49 Graham.Williams\@cmis.csiro.au"; +$M{"gb4e"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"genealogy"}="31 May 1996 14:10:08 Graham.Williams\@cmis.csiro.au"; +$M{"genmisc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"gentl-gr"}="29 Jan 1999 09:40:36 Graham.Williams\@cmis.csiro.au"; +$M{"geometry"}="8 Apr 1998 14:26:57 Graham.Williams\@cmis.csiro.au"; +$M{"geomsty"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; +$M{"geomsty"}="26 Feb 1998 08:58:15 Graham.Williams\@cmis.csiro.au"; +$M{"german"}="15 Jul 1998 07:33:39 Graham.Williams\@cmis.csiro.au"; +$M{"germbib"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"germdoc"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"getrefs"}="12 Nov 1998 20:22:10 Graham.Williams\@cmis.csiro.au"; +$M{"ghostscript"}="20 May 1997 14:12:34 Graham.Williams\@cmis.csiro.au"; +$M{"ghostview-mac"}="27 Mar 1998 05:51:48 Graham.Williams\@cmis.csiro.au"; +$M{"ghyphen"}="8 Jul 1998 08:55:23 Graham.Williams\@cmis.csiro.au"; +$M{"gleitobjekte"}="17 Feb 1998 09:09:23 Graham.Williams\@cmis.csiro.au"; +$M{"gloss"}="19 Apr 1998 15:58:24 Graham.Williams\@cmis.csiro.au"; +$M{"glosstex"}="25 Feb 1998 09:12:56 Graham.Williams\@cmis.csiro.au"; +$M{"gn-logic"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"gnhyph"}="16 Sep 1998 09:18:43 Graham.Williams\@cmis.csiro.au"; +$M{"gnuplot-ps"}="30 May 1996 11:22:14 Graham.Williams\@cmis.csiro.au"; +$M{"go"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"gothic"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"graphfig"}="1 May 1998 16:54:18 Graham.Williams\@cmis.csiro.au"; +$M{"graphics"}="1 Nov 1996 08:16:13 Graham.Williams\@cmis.csiro.au"; +$M{"graphicx"}="12 Jun 1996 06:47:22 Graham.Williams\@cmis.csiro.au"; +$M{"gray"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"grfguide"}="11 Jun 1997 16:17:05 Graham.Williams\@cmis.csiro.au"; +$M{"grfpaste"}="23 Feb 1998 15:39:11 Graham.Williams\@cmis.csiro.au"; +$M{"grnumalt"}="23 Feb 1998 15:49:56 Graham.Williams\@cmis.csiro.au"; +$M{"gsftopk"}="12 Nov 1996 09:08:05 Graham.Williams\@cmis.csiro.au"; +$M{"gustlib"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"gustlib"}="March 1998, s.rahtz\@elsevier.co.uk"; +$M{"hands"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"hanging"}="11 Dec 1998 05:38:02 Graham.Williams\@cmis.csiro.au"; +$M{"harpoon"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"harvmac"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"hellas"}="10 Mar 1998 06:00:34 Graham.Williams\@cmis.csiro.au"; +$M{"here"}="25 May 1996 07:24:51 Graham.Williams\@cmis.csiro.au"; +$M{"hh"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"hilowres"}="21 Jan 1999 19:31:07 Graham.Williams\@cmis.csiro.au"; +$M{"histogr"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"hlatex"}="28 May 1997 16:04:14 Graham.Williams\@cmis.csiro.au"; +$M{"hoekwater"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"html"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"html2latex"}="30 Sep 1998 07:55:02 Graham.Williams\@cmis.csiro.au"; +$M{"huhyph"}="5 Nov 1998 05:50:17 Graham.Williams\@cmis.csiro.au"; +$M{"hvdashln"}="13 May 1997 09:36:00 Graham.Williams\@cmis.csiro.au"; +$M{"hyper"}="30 Aug 1997 12:04:32 Graham.Williams\@cmis.csiro.au"; +$M{"hyperlatex"}="27 Dec 1998 20:25:24 Graham.Williams\@cmis.csiro.au"; +$M{"hyperref"}="17 Feb 1999 16:41:40 Graham.Williams\@cmis.csiro.au"; +$M{"hyphenat"}="22 Feb 1999 16:42:36 Graham.Williams\@cmis.csiro.au"; +$M{"hypht1"}="3 May 1997 20:57:53 Graham.Williams\@cmis.csiro.au"; +$M{"ibm"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"idealfonts"}="20 Feb 1998 14:34:54 Graham.Williams\@cmis.csiro.au"; +$M{"ifacmtg"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"imac"}="24 Sep 1998 05:27:35 Graham.Williams\@cmis.csiro.au"; +$M{"indxcite"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"indxcite"}="24 Jun 1996 15:17:51 Graham.Williams\@cmis.csiro.au"; +$M{"info"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"inhyph"}="7 Oct 1997 08:54:26 Graham.Williams\@cmis.csiro.au"; +$M{"inputenc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"insbox"}="25 Feb 1998 09:20:32 Graham.Williams\@cmis.csiro.au"; +$M{"ipa"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"isostds"}="21 Oct 1998 09:38:15 Graham.Williams\@cmis.csiro.au"; +$M{"ithyph"}="4 Aug 1998 05:39:19 Graham.Williams\@cmis.csiro.au"; +$M{"izhitsa"}="30 Jan 1999 06:34:27 Graham.Williams\@cmis.csiro.au"; +$M{"jadetex"}="3 May 1997 s.rahtz\@elsevier.co.uk"; +$M{"javatex"}="8 Oct 1998 12:03:35 Graham.Williams\@cmis.csiro.au"; +$M{"jknappen"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"jknappen"}="10 Mar 1998 09:10:20 Graham.Williams\@cmis.csiro.au"; +$M{"jsmisc"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"jspell"}="= {5 Nov 1998 15:43:30 Graham.Williams\@cmis.csiro.au"; +$M{"jura"}="11 Jul 1998 17:22:01 Graham.Williams\@cmis.csiro.au"; +$M{"kalendar"}="27 Mar 1998 05:44:58 Graham.Williams\@cmis.csiro.au"; +$M{"kalender"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"karnaugh"}="24 Sep 1998 05:26:10 Graham.Williams\@cmis.csiro.au"; +$M{"kdgreek"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; +$M{"kix"}="19 Sep 1998 08:58:56 Graham.Williams\@cmis.csiro.au"; +$M{"kluwer"}="31 May 1997 20:08:21 Graham.Williams\@cmis.csiro.au"; +$M{"knst"}="21 Oct 1996 13:44:44 Graham.Williams\@cmis.csiro.au"; +$M{"knuth"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"koi8"}="21 Oct 1996 13:48:21 Graham.Williams\@cmis.csiro.au"; +$M{"koma-script"}="30 Nov 1998 09:41:00 Graham.Williams\@cmis.csiro.au"; +$M{"kpathsea"}="3 Feb 1999 10:29:24 Graham.Williams\@cmis.csiro.au"; +$M{"kuvio"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"lamstex"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"lated"}="11 Feb 1998 07:41:10 Graham.Williams\@cmis.csiro.au"; +$M{"latex"}="2 Jul 1998 12:56:15 Graham.Williams\@cmis.csiro.au"; +$M{"latex209"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"latex209"}="4 Jul 1996 10:07:05 Graham.Williams\@cmis.csiro.au"; +$M{"latex2e"}="4 Jul 1996 09:53:38 Graham.Williams\@cmis.csiro.au"; +$M{"latex2html"}="8 Jul 1996 23:00:59 Graham.Williams\@cmis.csiro.au"; +$M{"latex2man"}="9 Sep 1998 05:33:13 Graham.Williams\@cmis.csiro.au"; +$M{"latex2rtf"}="17 Nov 1998 08:56:23 Graham.Williams\@cmis.csiro.au"; +$M{"latexcad"}="20 Mar 1998 09:32:43 Graham.Williams\@cmis.csiro.au"; +$M{"latexfonts"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"latexmk"}="12 Jan 1997 11:30:28 Graham.Williams\@cmis.csiro.au"; +$M{"latexn"}="27 Nov 1997 17:04:03 Graham.Williams\@cmis.csiro.au"; +$M{"latin2jk"}="7 Oct 1997 08:56:04 Graham.Williams\@cmis.csiro.au"; +$M{"layout"}="13 Aug 1998 05:42:38 Graham.Williams\@cmis.csiro.au"; +$M{"layouts"}="31 Jan 1999 06:43:57 Graham.Williams\@cmis.csiro.au"; +$M{"leaflet"}="30 Sep 1998 08:20:21 Graham.Williams\@cmis.csiro.au"; +$M{"leftidx"}="4 Feb 1998 13:16:00 Graham.Williams\@cmis.csiro.au"; +$M{"letter"}="6 Nov 1998 13:26:58 Graham.Williams\@cmis.csiro.au"; +$M{"lettrine"}="25 Mar 1998 09:11:24 Graham.Williams\@cmis.csiro.au"; +$M{"levy"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"lexikon"}="1 Apr 1998 06:05:45 Graham.Williams\@cmis.csiro.au"; +$M{"lgreek"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"lgrind-win32"}="24 Mar 1998 11:41:55 Graham.Williams\@cmis.csiro.au"; +$M{"lgrind"}="5 Aug 1998 06:33:28 Graham.Williams\@cmis.csiro.au"; +$M{"lh"}="2 Oct 1998 07:20:00 Graham.Williams\@cmis.csiro.au"; +$M{"lhcyr"}="21 Jan 1999 19:44:44 Graham.Williams\@cmis.csiro.au"; +$M{"lilypond"}="21 Oct 1998 09:41:28 Graham.Williams\@cmis.csiro.au"; +$M{"lineno"}="20 Jan 1999 14:57:13 Graham.Williams\@cmis.csiro.au"; +$M{"linguex"}="1 Jun 1998 11:57:34 Graham.Williams\@cmis.csiro.au"; +$M{"lintex"}="16 Jun 1998 10:19:01 Graham.Williams\@cmis.csiro.au"; +$M{"lips"}="21 Oct 1996 10:30:25 Graham.Williams\@cmis.csiro.au"; +$M{"listings"}="11 Nov 1998 05:44:14 Graham.Williams\@cmis.csiro.au"; +$M{"lkort"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"llncs"}="4 Oct 1996 08:48:06 Graham.Williams\@cmis.csiro.au"; +$M{"localloc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"logic"}="3 May 1997 s.rahtz\@elsevier.co.uk"; +$M{"logo-ps"}="25 Jul 1998 06:24:28 Graham.Williams\@cmis.csiro.au"; +$M{"lollipop"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"longtable"}="21 Jun 1996 08:12:11 Graham.Williams\@cmis.csiro.au"; +$M{"lscape"}="7 Nov 1996 19:36:31 Graham.Williams\@cmis.csiro.au"; +$M{"lshort-english"}="21 Jan 1999 19:27:28 Graham.Williams\@cmis.csiro.au"; +$M{"lshort-finnish"}="21 Jan 1999 19:12:55 Graham.Williams\@cmis.csiro.au"; +$M{"lshort-french"}="5 Feb 1998 09:10:02 Graham.Williams\@cmis.csiro.au"; +$M{"lshort-german"}="30 Jan 1999 07:28:37 Graham.Williams\@cmis.csiro.au"; +$M{"lshort-mongolian"}="30 Jan 1999 07:28:04 Graham.Williams\@cmis.csiro.au"; +$M{"lshort-polish"}="25 Feb 1999 14:09:31 Graham.Williams\@cmis.csiro.au"; +$M{"lshort-russian"}="13 Oct 1998 09:11:31 Graham.Williams\@cmis.csiro.au"; +$M{"lshort-spanish"}="21 Jan 1999 19:12:55 Graham.Williams\@cmis.csiro.au"; +$M{"ltoh"}="8 Apr 1998 09:41:19 Graham.Williams\@cmis.csiro.au"; +$M{"ltx2rtf"}="28 Dec 1998 09:11:53 Graham.Williams\@cmis.csiro.au"; +$M{"ltx2x"}="26 Jan 1997 10:24:09 Graham.Williams\@cmis.csiro.au"; +$M{"ltxbase"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"ltxinput"}="26 Nov 1996 16:30:38 Graham.Williams\@cmis.csiro.au"; +$M{"ltxmisc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"ltxsrc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"lucida"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"lucold"}="4 Feb 1998 13:23:16 Graham.Williams\@cmis.csiro.au"; +$M{"lw35nfsx"}="28 Jul 1998 05:36:21 Graham.Williams\@cmis.csiro.au"; +$M{"ly1"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"m-pictex"}="24 Feb 1998 13:55:54 Graham.Williams\@cmis.csiro.au"; +$M{"macbibtex"}="7 Nov 1996 13:35:35 Graham.Williams\@cmis.csiro.au"; +$M{"magaz"}="17 Feb 1999 17:33:54 Graham.Williams\@cmis.csiro.au"; +$M{"mailing"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"makeindex"}="23 May 1997 13:18:35 Graham.Williams\@cmis.csiro.au"; +$M{"malayalam"}="23 Jun 1998 15:49:27 Graham.Williams\@cmis.csiro.au"; +$M{"malvern"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"manyfoot"}="28 Dec 1998 09:24:33 Graham.Williams\@cmis.csiro.au"; +$M{"mapcodes"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"maple"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"margbib"}="24 Feb 1998 13:20:27 Graham.Williams\@cmis.csiro.au"; +$M{"marvosym-mac"}="5 Nov 1998 15:47:46 Graham.Williams\@cmis.csiro.au"; +$M{"marvosym"}="21 Jul 1998 05:27:14 Graham.Williams\@cmis.csiro.auy"; +$M{"mathcmd"}="abstract Provides a slightly version of the commands for"; +$M{"mathcmd"}="1 May 1998 16:54:49 Graham.Williams\@cmis.csiro.au"; +$M{"mathcomp"}="10 Sep 1998 18:44:41 Graham.Williams\@cmis.csiro.au"; +$M{"mathematica"}="20 Jan 1998 22:00:24 Graham.Williams\@cmis.csiro.au"; +$M{"mathenv"}="1 May 1998 16:55:25 Graham.Williams\@cmis.csiro.au"; +$M{"mathinst"}="10 Sep 1998 18:54:03 Graham.Williams\@cmis.csiro.au"; +$M{"mathkit"}="4 Feb 1998 13:20:21 Graham.Williams\@cmis.csiro.au"; +$M{"mathpple"}="21 Jan 1999 19:34:23 Graham.Williams\@cmis.csiro.au"; +$M{"mathrsfs"}="27 Mar 1998 05:58:42 Graham.Williams\@cmis.csiro.au"; +$M{"mathtime"}="29 May 1996 10:39:52 Graham.Williams\@cmis.csiro.au"; +$M{"mcite"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"mdwtools"}="16 Jun 1998 10:36:35 Graham.Williams\@cmis.csiro.au"; +$M{"meta-mode"}="1 May 1997 10:10:22 Graham.Williams\@cmis.csiro.au"; +$M{"metapost"}="25 Jun 1996 10:58:40 Graham.Williams\@cmis.csiro.au"; +$M{"method"}="21 Jan 1999 07:58:21 Graham.Williams\@cmis.csiro.au"; +$M{"mex"}="08 Feb 1998 staw\@gust.org.pl"; +$M{"mf-ps"}="4 Feb 1998 13:18:00 Graham.Williams\@cmis.csiro.au"; +$M{"mf-ps"}="08 Feb 1998 staw\@gust.org.pl"; +$M{"mf2pt3"}="2 Jan 1999 21:45:21 Graham.Williams\@cmis.csiro.au"; +$M{"mf2tex"}="3 May 1997 21:09:52 Graham.Williams\@cmis.csiro.au"; +$M{"mff"}="24 Oct 1996 10:27:31 Graham.Williams\@cmis.csiro.au"; +$M{"mff"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"mflogo"}="25 Dec 1996 UV"; +$M{"mfnfss"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"mfpic"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"mftoeps"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; +$M{"mhs"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"midnight"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"mif2xfig"}="20 Nov 1996 11:23:52 Graham.Williams\@cmis.csiro.au"; +$M{"miktex-axp"}="25 Sep 1997 14:01:19 Graham.Williams\@cmis.csiro.au"; +$M{"miktex"}="23 Feb 1999 16:12:25 Graham.Williams\@cmis.csiro.au"; +$M{"miniltx"}="20 May 1996 10:13:07 Graham.Williams\@cmis.csiro.au"; +$M{"minitoc"}="12 Jan 1997 11:20:36 Graham.Williams\@cmis.csiro.au"; +$M{"mirr"}="12 May 1997 10:27:47 Graham.Williams\@cmis.csiro.au"; +$M{"mirr"}="08 Feb 1998 staw\@gust.org.pl"; +$M{"miscpk"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"mitpress"}="19 Sep 1998 10:11:07 Graham.Williams\@cmis.csiro.au"; +$M{"mkpic"}="2 Jan 1999 21:52:06 Graham.Williams\@cmis.csiro.au"; +$M{"mla"}="28 Apr 1997 09:48:03 Graham.Williams\@cmis.csiro.au"; +$M{"mlbib"}="5 Nov 1996 09:15:29 Graham.Williams\@cmis.csiro.au"; +$M{"mltex"}="28 Dec 1998 09:15:09 Graham.Williams\@cmis.csiro.au"; +$M{"mmtools"}="23 Jul 1997 09:16:45 Graham.Williams\@cmis.csiro.au"; +$M{"mnras"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"modes"}="11 Aug 1998 05:29:08 Graham.Williams\@cmis.csiro.au"; +$M{"monotype"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"monster"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"montex"}="29 Jan 1999 09:53:15 Graham.Williams\@cmis.csiro.au"; +$M{"morehelp"}="19 Feb 1998 09:36:53 Graham.Williams\@cmis.csiro.au"; +$M{"moresize"}="17 Jul 1997 14:08:56 Graham.Williams\@cmis.csiro.au"; +$M{"moreverb"}="29 May 1996 11:58:07 Graham.Williams\@cmis.csiro.au"; +$M{"moreverb"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"morse"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; +$M{"morse"}="26 Feb 1998 09:08:33 Graham.Williams\@cmis.csiro.au"; +$M{"mpattern"}="30 Sep 1998 11:00:52 Graham.Williams\@cmis.csiro.au"; +$M{"mpfnmark"}="13 Dec 1996 08:30:22 Graham.Williams\@cmis.csiro.au"; +$M{"mpfnmark"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"ms"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"mslapa"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"mslapa"}="12 Jul 1996 10:06:59 Graham.Williams\@cmis.csiro.au"; +$M{"mt11p"}="14 Feb 1997 09:21:04 Graham.Williams\@cmis.csiro.au"; +$M{"mtbe"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"multenum"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; +$M{"multicol"}="21 Dec 1998 13:35:30 Graham.Williams\@cmis.csiro.au"; +$M{"multido"}="19 Mar 1998 10:41:51 Graham.Williams\@cmis.csiro.au"; +$M{"multirow"}="25 Nov 1998 06:06:17 Graham.Williams\@cmis.csiro.au"; +$M{"multitoc"}="8 Sep 1998 05:46:30 Graham.Williams\@cmis.csiro.au"; +$M{"musictex"}="27 Nov 1996 13:59:30 Graham.Williams\@cmis.csiro.au"; +$M{"musixtex"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"mxedruli"}="25 Jul 1998 06:28:00 Graham.Williams\@cmis.csiro.au"; +$M{"mylatex"}="1 May 1998 17:00:39 Graham.Williams\@cmis.csiro.au"; +$M{"myletter"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"nassflow"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"natbib"}="17 Jul 1998 16:12:29 Graham.Williams\@cmis.csiro.au"; +$M{"nb4latex"}="21 Nov 1996 16:56:44 Graham.Williams\@cmis.csiro.au"; +$M{"nccfoots"}="28 Dec 1998 09:25:59 Graham.Williams\@cmis.csiro.au"; +$M{"ncctools"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"netpbm-win"}="10 Sep 1998 18:37:04 Graham.Williams\@cmis.csiro.au"; +$M{"newsletr"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"newthm"}="abstract A version of the theorem-style which provides"; +$M{"newthm"}="14 Feb 1997 09:30:36 Graham.Williams\@cmis.csiro.au"; +$M{"newthm"}="13 May 1997 10:24:58 Robin Fairbairns "; +$M{"niceframe"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"nomencl"}="27 May 1997 09:24:37 Graham.Williams\@cmis.csiro.au"; +$M{"norbib"}="2 Jul 1998 12:55:09 Graham.Williams\@cmis.csiro.au"; +$M{"nrc"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"ntemacs"}="19 Oct 1998 06:03:28 Graham.Williams\@cmis.csiro.au"; +$M{"ntgclass"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"ntheorem"}="11 Dec 1998 05:44:07 Graham.Williams\@cmis.csiro.au"; +$M{"numline"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"numline"}="28 May 1996 16:02:33 Graham.Williams\@cmis.csiro.au"; +$M{"objectz"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"oca"}="3 May 1997 s.rahtz\@elsevier.co.uk"; +$M{"ocr-a"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"ocr-a"}="18 May 1996 14:10:28 Graham.Williams\@cmis.csiro.au"; +$M{"ocr-b"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"ocr-b"}="18 May 1996 14:10:28 Graham.Williams\@cmis.csiro.au"; +$M{"ogham"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"ogonek"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"oldstyle"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"omega"}="11 Feb 1998 08:05:12 Graham.Williams\@cmis.csiro.au"; +$M{"omegabase"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"omegafonts"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"onepagem"}="18 Jul 1997 14:23:48 Graham.Williams\@cmis.csiro.au"; +$M{"oryia"}="1 Jul 1998 10:29:59 Graham.Williams\@cmis.csiro.au"; +$M{"os2tex"}="3 Jan 1999 10:42:23 Graham.Williams\@cmis.csiro.au"; +$M{"osmanian"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"ot2cyr"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"overcite"}="15 Dec 1996 19:11:52 Graham.Williams\@cmis.csiro.au"; +$M{"overpic"}="27 Nov 1997 17:00:55 Graham.Williams\@cmis.csiro.au"; +$M{"overword"}="13 Dec 1996 08:37:08 Graham.Williams\@cmis.csiro.au"; +$M{"overword"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"oxford"}="11 Jan 1998 20:39:42 Graham.Williams\@cmis.csiro.au"; +$M{"oztex-german"}="25 Mar 1998 09:10:39 Graham.Williams\@cmis.csiro.au"; +$M{"oztex"}="27 Dec 1998 20:16:46 Graham.Williams\@cmis.csiro.au"; +$M{"pageno"}="23 Sep 1998 09:40:33 Graham.Williams\@cmis.csiro.au"; +$M{"pandey"}="30 Sep 1998 07:56:09 Graham.Williams\@cmis.csiro.au"; +$M{"pandora"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"paper"}="20 May 1996 06:33:20 Graham.Williams\@cmis.csiro.au"; +$M{"paradissa"}="14 Jun 1996 16:18:31 Graham.Williams\@cmis.csiro.au"; +$M{"paralist"}="21 Jan 1999 19:49:45 Graham.Williams\@cmis.csiro.au"; +$M{"patch"}="3 May 1997 s.rahtz\@elsevier.co.uk"; +$M{"path"}="25 Jun 1996 09:13:30 Graham.Williams\@cmis.csiro.au"; +$M{"pawpict"}="10 Feb 1998 09:32:45 Graham.Williams\@cmis.csiro.au"; +$M{"pb-diagram"}="30 Nov 1998 13:48:18 Graham.Williams\@cmis.csiro.au"; +$M{"pcfonts"}="21 Oct 1996 13:32:14 Graham.Williams\@cmis.csiro.au"; +$M{"pdcmac"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"pdftex-djgpp"}="23 Feb 1998 15:51:42 Graham.Williams\@cmis.csiro.au"; +$M{"pdftex"}="13 Aug 1998 05:51:13 Graham.Williams\@cmis.csiro.au"; +$M{"permute"}="28 Dec 1998 09:09:59 Graham.Williams\@cmis.csiro.au"; +$M{"pf2afm"}="18 Jun 1998 10:13:25 Graham.Williams\@cmis.csiro.au"; +$M{"phonetic"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"phppcf"}="14 Jun 1996 12:35:55 Graham.Williams\@cmis.csiro.au"; +$M{"physe"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"phyzzx"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"pictex"}="24 Feb 1998 13:53:44 Graham.Williams\@cmis.csiro.au"; +$M{"piff"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"piq"}="ctan fonts/okuda//"; +$M{"piq"}="17 Nov 1996 11:28:28 Graham.Williams\@cmis.csiro.au"; +$M{"pkfind"}=" utility to understand those specials, and to act"; +$M{"pkfind"}="3 Mar 1998 15:39:16 Graham.Williams\@cmis.csiro.au"; +$M{"pl-mf"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"pl-mf"}="08 Feb 1998 staw\@gust.org.pl"; +$M{"pl-qx"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"pl"}="25 Feb 1998, s.rahtz\@elsevier.co.uk"; +$M{"plainmisc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"plaintex"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"plari"}="6 Nov 1998 06:24:51 Graham.Williams\@cmis.csiro.au"; +$M{"platex"}="18 Jun 1998 10:22:09 Graham.Williams\@cmis.csiro.au"; +$M{"plcalendar"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"plfonts"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"plgraph"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"plpsfont"}="08 Feb 1998 staw\@gust.org.pl"; +$M{"pmcstex"}="27 Nov 1997 17:12:37 Graham.Williams\@cmis.csiro.au"; +$M{"pmgraph"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"poligraf"}="17 Nov 1996 11:34:19 Graham.Williams\@cmis.csiro.au"; +$M{"poligraf"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"poligraf"}="08 Feb 1998 staw\@gust.org.pl"; +$M{"polish"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"polyglot"}="12 Sep 1997 10:32:34 Graham.Williams\@cmis.csiro.au"; +$M{"ppchtex"}="15 Jan 1997 09:54:55 Graham.Williams\@cmis.csiro.au"; +$M{"prelim2e"}="10 Aug 1998 09:16:01 Graham.Williams\@cmis.csiro.au"; +$M{"prettyref"}="29 Jul 1998 05:41:53 Graham.Williams\@cmis.csiro.au"; +$M{"progkeys"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"program"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"proofs"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"prv"}="11 Dec 1998 05:33:29 Graham.Williams\@cmis.csiro.au"; +$M{"ps_conv"}="17 Nov 1996 11:34:19 Graham.Williams\@cmis.csiro.au"; +$M{"ps_view"}="25 Jun 1998 staw\@gust.org.pl"; +$M{"psfig"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"psfixbb"}="23 Jun 1998 15:54:54 Graham.Williams\@cmis.csiro.au"; +$M{"psfont"}="1 Jul 1996 21:00:54 Graham.Williams\@cmis.csiro.au"; +$M{"psfonts"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"psfrag"}="24 Jun 1998 12:56:59 Graham.Williams\@cmis.csiro.au"; +$M{"psizzl"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"pslatex"}="2 Aug 1996 12:28:03 Graham.Williams\@cmis.csiro.au"; +$M{"pslatex"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"psmerge"}="1 Nov 1996 08:12:01 Graham.Williams\@cmis.csiro.au"; +$M{"psnfss"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"psnfss"}="24 Apr 1997 16:16:14 Graham.Williams\@cmis.csiro.au"; +$M{"psnfssx"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"pspicture"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"pstotext"}="31 Oct 1996 13:39:09 Graham.Williams\@cmis.csiro.au"; +$M{"pstricks"}="30 May 1996 11:20:11 Graham.Williams\@cmis.csiro.au"; +$M{"punk"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"qfig"}="24 Jul 1998 06:25:39 Graham.Williams\@cmis.csiro.au"; +$M{"qfonts"}="18 Jun 1998 10:17:31 Graham.Williams\@cmis.csiro.au"; +$M{"qobitree"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"qsymbols"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"quotchap"}="24 Feb 1998 13:20:08 Graham.Williams\@cmis.csiro.au"; +$M{"quotes"}="1 May 1998 16:55:48 Graham.Williams\@cmis.csiro.au"; +$M{"r-und-s"}="3 Jul 1997 08:10:21 Graham.Williams\@cmis.csiro.au"; +$M{"ragged2e"}="10 Aug 1998 09:09:43 Graham.Williams\@cmis.csiro.au"; +$M{"rail"}="1 Oct 1998 07:36:00 Graham.Williams\@cmis.csiro.au"; +$M{"rangecite"}="28 May 1996 16:31:55 Graham.Williams\@cmis.csiro.au"; +$M{"rawfonts"}="6 Jun 1997 11:32:53 Graham.Williams\@cmis.csiro.au"; +$M{"rawprint"}="21 Oct 1996 13:50:40 Graham.Williams\@cmis.csiro.au"; +$M{"rcsinfo"}="25 Feb 1999 11:36:47 Graham.Williams\@cmis.csiro.au"; +$M{"realcalc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"recipe"}="26 Nov 1996 16:28:13 Graham.Williams\@cmis.csiro.au"; +$M{"refcheck"}="12 May 1997 10:18:04 Graham.Williams\@cmis.csiro.au"; +$M{"refman"}="1 Jun 1998 12:05:47 Graham.Williams\@cmis.csiro.au"; +$M{"relenc"}="23 Feb 1999 16:14:26 Graham.Williams\@cmis.csiro.au"; +$M{"remreset"}="7 Oct 1997 08:58:13 Graham.Williams\@cmis.csiro.au"; +$M{"repeat"}="5 Jan 1999 08:27:22 Graham.Williams\@cmis.csiro.au"; +$M{"revnum"}="3 Mar 1998 15:31:13 Graham.Williams\@cmis.csiro.au"; +$M{"revtex"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"revtex"}="31 Oct 1996 13:44:58 Graham.Williams\@cmis.csiro.au"; +$M{"rlepsf"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"rmpage"}="5 Feb 1998 14:07:37 Graham.Williams\@cmis.csiro.au"; +$M{"romaniantex"}="15 Nov 1996 14:57:19 Graham.Williams\@cmis.csiro.au"; +$M{"romanneg"}="19 Apr 1998 15:22:21 Graham.Williams\@cmis.csiro.au"; +$M{"rotating"}="12 Jun 1996 06:45:47 Graham.Williams\@cmis.csiro.au"; +$M{"rplain"}="23 Sep 1998 09:45:08 Graham.Williams\@cmis.csiro.au"; +$M{"rsfs-ps"}="25 Apr 1998 06:14:30 Graham.Williams\@cmis.csiro.au"; +$M{"rsfs"}="12 Jun 1996 06:57:19 Graham.Williams\@cmis.csiro.au"; +$M{"ruhyphen"}="8 Oct 1998 11:53:41 Graham.Williams\@cmis.csiro.au"; +$M{"ruler"}="22 May 1996 16:04:57 Graham.Williams\@cmis.csiro.au"; +$M{"s2latex"}="7 Jun 1996 20:13:54 Graham.Williams\@cmis.csiro.au"; +$M{"saferef"}="4 Feb 1997 09:57:44 Graham.Williams\@cmis.csiro.au"; +$M{"sanskrit"}="19 Mar 1997 12:03:33 Graham.Williams\@cmis.csiro.au"; +$M{"sauter"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"sauterfonts"}="12 Nov 1998 20:16:14 Graham.Williams\@cmis.csiro.au"; +$M{"scale"}="6 Nov 1998 06:19:58 Graham.Williams\@cmis.csiro.au"; +$M{"scalefnt"}="7 Oct 1997 08:58:13 Graham.Williams\@cmis.csiro.au"; +$M{"schedule"}="18 Feb 1998 10:30:16 Graham.Williams\@cmis.csiro.au"; +$M{"script"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"section"}="1 May 1998 17:01:43 Graham.Williams\@cmis.csiro.au"; +$M{"sectsty"}="13 Dec 1998 05:29:30 Graham.Williams\@cmis.csiro.au"; +$M{"semantic"}="13 May 1996 06:13:26 Graham.Williams\@cmis.csiro.au"; +$M{"seminar"}="28 May 1996 16:32:44 Graham.Williams\@cmis.csiro.au"; +$M{"setspace"}="27 Nov 1998 09:26:04 Graham.Williams\@cmis.csiro.au"; +$M{"sfg"}="8 Jul 1998 09:15:14 Graham.Williams\@cmis.csiro.au"; +$M{"sfheaders"}="17 Feb 1998 09:11:27 Graham.Williams\@cmis.csiro.au"; +$M{"shadbox"}="5 Aug 1996 12:14:57 Graham.Williams\@cmis.csiro.au"; +$M{"shadbox"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"shadethm"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"shading"}="24 Sep 1996 08:55:09 Graham.Williams\@cmis.csiro.au"; +$M{"shadow"}="21 Oct 1996 10:39:52 Graham.Williams\@cmis.csiro.au"; +$M{"shalom"}="30 May 1996 11:22:14 Graham.Williams\@cmis.csiro.au"; +$M{"shapepar"}="3 Jul 1996 15:23:38 Graham.Williams\@cmis.csiro.au"; +$M{"shhyphl"}="7 Jan 1999 07:27:53 Graham.Williams\@cmis.csiro.au"; +$M{"shortlst"}="29 Nov 1998 18:20:51 Graham.Williams\@cmis.csiro.au"; +$M{"shorttoc"}="22 Jul 1998 06:07:50 Graham.Williams\@cmis.csiro.au"; +$M{"showdim"}="30 Jul 1998 05:30:48 Graham.Williams\@cmis.csiro.au"; +$M{"showlabels"}="23 Feb 1999 13:56:22 Graham.Williams\@cmis.csiro.au"; +$M{"siam"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"sidecap"}="6 Nov 1998 06:07:25 Graham.Williams\@cmis.csiro.au"; +$M{"siggraph"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"simpsons"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; +$M{"sinhala"}="31 Oct 1996 09:54:37 Graham.Williams\@cmis.csiro.au"; +$M{"sirlin"}="16 Aug 1996 14:13:00 Graham.Williams\@cmis.csiro.au"; +$M{"siunits"}="23 Jan 1999 05:00:33 Graham.Williams\@cmis.csiro.au"; +$M{"slashbox"}="20 Feb 1998 14:26:38 Graham.Williams\@cmis.csiro.au"; +$M{"slashed"}="11 Feb 1998 07:48:41 Graham.Williams\@cmis.csiro.au"; +$M{"slidenotes"}="16 Dec 1998 08:33:45 Graham.Williams\@cmis.csiro.au"; +$M{"slides"}="17 Jun 1997 20:12:00 Graham.Williams\@cmis.csiro.au"; +$M{"smallcap"}="28 May 1996 15:57:18 Graham.Williams\@cmis.csiro.au"; +$M{"smallcap"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"smartmn"}="5 Nov 1996 09:14:21 Graham.Williams\@cmis.csiro.au"; +$M{"sobolev"}="1 May 1998 16:56:12 Graham.Williams\@cmis.csiro.au"; +$M{"somedefs"}="12 Aug 1998 06:35:40 Graham.Williams\@cmis.csiro.au"; +$M{"songbook"}="30 Jun 1998 10:54:02 Graham.Williams\@cmis.csiro.au"; +$M{"sorhyph"}="12 May 1997 10:30:15 Graham.Williams\@cmis.csiro.au"; +$M{"soul"}="21 Jan 1999 19:15:44 Graham.Williams\@cmis.csiro.au"; +$M{"spanish"}="21 May 1996 13:04:45 Graham.Williams\@cmis.csiro.au"; +$M{"spanishb"}="5 Oct 1998 11:43:25 Graham.Williams\@cmis.csiro.au"; +$M{"sphack"}="28 May 1998 16:16:55 Graham.Williams\@cmis.csiro.au"; +$M{"sprite"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"ssqquote"}="25 Dec 1996 UV"; +$M{"startex"}="21 Oct 1996 14:23:19 Graham.Williams\@cmis.csiro.au"; +$M{"startex"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"stdclsdv"}="21 Jan 1999 12:51:23 Graham.Williams\@cmis.csiro.au"; +$M{"stmaryrd-ps"}="25 Jul 1998 06:01:40 Graham.Williams\@cmis.csiro.au"; +$M{"stmaryrd"}="25 Apr 1998 06:19:27 Graham.Williams\@cmis.csiro.au"; +$M{"subeqn"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"supertabular"}="7 Oct 1997 09:01:35 Graham.Williams\@cmis.csiro.au"; +$M{"swift"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"syngen"}="19 Nov 1996 08:42:42 Graham.Williams\@cmis.csiro.au"; +$M{"synttree"}="12 Aug 1998 06:13:18 Graham.Williams\@cmis.csiro.au"; +$M{"t2"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"tabbing"}="10 Feb 1998 12:54:11 Graham.Williams\@cmis.csiro.au"; +$M{"tabls"}="15 Dec 1996 19:17:27 Graham.Williams\@cmis.csiro.au"; +$M{"tap"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"tap"}="08 Feb 1998 staw\@gust.org.pl"; +$M{"taylor"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"tbe"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"tcvn"}="21 Jan 1999 19:18:03 Graham.Williams\@cmis.csiro.au"; +$M{"tcx"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"tds"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; +$M{"techexplorer"}="19 Aug 1998 07:13:20 Graham.Williams\@cmis.csiro.au"; +$M{"tengwar"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"tensind"}="18 Jun 1998 10:06:41 Graham.Williams\@cmis.csiro.au"; +$M{"tensor"}="7 Jun 1996 08:52:37 Graham.Williams\@cmis.csiro.au"; +$M{"termcal"}="14 Jan 1997 10:10:12 Graham.Williams\@cmis.csiro.au"; +$M{"tetex"}="11 Jun 1997 19:22:32 Graham.Williams\@cmis.csiro.au"; +$M{"tex-math"}="8 Jul 1996 14:14:25 Graham.Williams\@cmis.csiro.au"; +$M{"tex-ps"}="09 Jun 1998 staw\@gust.org.pl"; +$M{"tex2bib"}="27 Jan 1998 16:50:26 Graham.Williams\@cmis.csiro.au"; +$M{"tex2html"}="29 Jan 1998 09:10:30 Graham.Williams\@cmis.csiro.au"; +$M{"tex2ltx"}="28 Oct 1998 11:56:39 Graham.Williams\@cmis.csiro.au"; +$M{"tex2rtf"}="25 Jun 1996 08:56:43 Graham.Williams\@cmis.csiro.au"; +$M{"tex4ht"}="23 Oct 1998 05:35:34 Graham.Williams\@cmis.csiro.au"; +$M{"tex98"}="12 Aug 1998 06:09:09 Graham.Williams\@cmis.csiro.au"; +$M{"texdraw"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"texed"}="11 Nov 1998 05:47:04 Graham.Williams\@cmis.csiro.au"; +$M{"texi2html"}="3 Feb 1999 10:27:21 Graham.Williams\@cmis.csiro.au"; +$M{"texi2www"}="2 Jul 1996 10:33:31 Graham.Williams\@cmis.csiro.au"; +$M{"texinfo"}="3 Feb 1999 10:28:52 Graham.Williams\@cmis.csiro.au"; +$M{"texip"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"texlist"}="31 Jan 1999 07:36:23 Graham.Williams\@cmis.csiro.au"; +$M{"texperf"}="16 Aug 1996 14:08:55 Graham.Williams\@cmis.csiro.au"; +$M{"texshell32"}="28 Mar 1998 07:07:28 Graham.Williams\@cmis.csiro.au"; +$M{"texsis"}="27 Jan 1998 16:44:10 Graham.Williams\@cmis.csiro.au"; +$M{"texsk"}="7 Mar 1997 16:53:45 Graham.Williams\@cmis.csiro.au"; +$M{"text1"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"textcase"}="11 Feb 1998 07:49:12 Graham.Williams\@cmis.csiro.au"; +$M{"textfit"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"textmerg"}="31 May 1996 08:43:05 Graham.Williams\@cmis.csiro.au"; +$M{"textoolspro"}=" LaTeX- code, so you can write sections in a"; +$M{"textoolspro"}="21 Jan 1999 13:03:19 Graham.Williams\@cmis.csiro.au"; +$M{"textpos"}="23 Feb 1999 13:54:56 Graham.Williams\@cmis.csiro.au"; +$M{"tfmpk"}="16 Dec 1998 08:30:00 Graham.Williams\@cmis.csiro.au"; +$M{"thesis"}="20 May 1996 10:22:19 Graham.Williams\@cmis.csiro.au"; +$M{"threed"}="13 Apr 1998 06:37:38 Graham.Williams\@cmis.csiro.au"; +$M{"threeparttable"}="15 Dec 1996 19:16:24 Graham.Williams\@cmis.csiro.au"; +$M{"thumb"}="10 Feb 1998 09:34:21 Graham.Williams\@cmis.csiro.au"; +$M{"thumbpdf"}="17 Feb 1999 16:50:56 Graham.Williams\@cmis.csiro.au"; +$M{"tiff"}="11 Nov 1998 05:43:39 Graham.Williams\@cmis.csiro.au"; +$M{"tiff2ps"}="06 May 1998 staw\@gust.org.pl"; +$M{"time"}="7 Jun 1996 09:04:45 Graham.Williams\@cmis.csiro.au"; +$M{"times"}="28 May 1997 16:25:37 Graham.Williams\@cmis.csiro.au"; +$M{"timesht"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"timing"}="3 May 1997 s.rahtz\@elsevier.co.uk"; +$M{"tipa"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"titlefoot"}="18 Mar 1998 09:30:36 Graham.Williams\@cmis.csiro.au"; +$M{"titleref"}="15 Dec 1996 19:19:50 Graham.Williams\@cmis.csiro.au"; +$M{"titlesec"}="23 Feb 1999 14:58:36 Graham.Williams\@cmis.csiro.au"; +$M{"titletoc"}="23 Feb 1999 14:58:46 Graham.Williams\@cmis.csiro.au"; +$M{"tkbibtex"}="10 Aug 1998 06:27:23 Graham.Williams\@cmis.csiro.au"; +$M{"tmview"}="29 Jun 1998 10:00:32 Graham.Williams\@cmis.csiro.au"; +$M{"tocbibind"}="21 Jan 1999 12:54:08 Graham.Williams\@cmis.csiro.au"; +$M{"tocloft"}="21 Jan 1999 12:57:14 Graham.Williams\@cmis.csiro.au"; +$M{"tocvsec2"}="21 Jan 1999 12:52:58 Graham.Williams\@cmis.csiro.au"; +$M{"toil"}="27 Jan 1998 16:54:47 Graham.Williams\@cmis.csiro.au"; +$M{"toil"}="08 Feb 1998 staw\@gust.org.pl"; +$M{"tools"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"topcapt"}="15 Dec 1996 19:04:36 Graham.Williams\@cmis.csiro.au"; +$M{"tracking"}="5 Aug 1996 12:11:48 Graham.Williams\@cmis.csiro.au"; +$M{"tracking"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"trans"}="17 Nov 1996 11:34:19 Graham.Williams\@cmis.csiro.au"; +$M{"trans"}="08 Feb 1998 staw\@gust.org.pl"; +$M{"transfig"}="8 Jul 1998 09:08:50 Graham.Williams\@cmis.csiro.au"; +$M{"treesvr"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"truncate"}="15 Dec 1996 19:23:52 Graham.Williams\@cmis.csiro.au"; +$M{"tsconfig"}="27 Nov 1996 13:48:24 Graham.Williams\@cmis.csiro.au"; +$M{"ttf2mf"}="25 Nov 1998 05:37:46 Graham.Williams\@cmis.csiro.au"; +$M{"ttf2pk"}="2 Jan 1999 22:03:00 Graham.Williams\@cmis.csiro.au"; +$M{"ttf2tfm"}="2 Jan 1999 22:05:48 Graham.Williams\@cmis.csiro.au"; +$M{"ttftogf"}="19 Sep 1998 08:12:18 Graham.Williams\@cmis.csiro.au"; +$M{"tth-rpm"}="13 Feb 1999 08:51:59 Graham.Williams\@cmis.csiro.au"; +$M{"tth-win"}="10 Sep 1998 18:39:22 Graham.Williams\@cmis.csiro.au"; +$M{"tth"}="27 Mar 1998 12:45:38 Graham.Williams\@cmis.csiro.au"; +$M{"ttt"}="19 Mar 1997 08:34:45 Graham.Williams\@cmis.csiro.au"; +$M{"tubtoc"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"tugboat-toc"}="28 Dec 1998 09:28:11 Graham.Williams\@cmis.csiro.au"; +$M{"tugboat"}="3 May 1997 s.rahtz\@elsevier.co.uk"; +$M{"tugboat"}="3 Jul 1997 08:01:03 Graham.Williams\@cmis.csiro.au"; +$M{"twg-list"}="25 Feb 1998 09:33:34 Graham.Williams\@cmis.csiro.au"; +$M{"twoup"}="19 Mar 1998 10:39:40 Graham.Williams\@cmis.csiro.au"; +$M{"type1"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"type1"}="February 1998, s.rahtz\@elsevier.co.uk"; +$M{"type1cm"}="7 Mar 1997 16:50:06 Graham.Williams\@cmis.csiro.au"; +$M{"type1cm"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"typearea"}="12 Jun 1996 13:18:22 Graham.Williams\@cmis.csiro.au"; +$M{"typehtml"}="27 Nov 1997 17:08:38 Graham.Williams\@cmis.csiro.au"; +$M{"typespec"}="2 Jul 1998 13:03:32 Graham.Williams\@cmis.csiro.au"; +$M{"uaclasses"}="19 Mar 1997 12:05:52 Graham.Williams\@cmis.csiro.au"; +$M{"uaclasses"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"ucthesis"}="abstract A version of the standard \LaTeX{} report style"; +$M{"ukhyph"}="21 Oct 1996 10:37:20 Graham.Williams\@cmis.csiro.au"; +$M{"ulem"}="28 May 1996 16:34:03 Graham.Williams\@cmis.csiro.au"; +$M{"ulsy"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"umlaute"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"umrand"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"underlin"}="13 May 1997 10:24:58 Robin Fairbairns rf\@cl.cam.ac.uk"; +$M{"underscore"}="17 Jul 1998 07:34:04 Graham.Williams\@cmis.csiro.au"; +$M{"uniqleaf"}="2 Aug 1996 12:44:23 Graham.Williams\@cmis.csiro.au"; +$M{"units"}="6 Aug 1998 06:17:29 Graham.Williams\@cmis.csiro.au"; +$M{"universa"}="6 Sep 1998 05:46:31 Graham.Williams\@cmis.csiro.au"; +$M{"url"}="3 Jul 1996 15:23:38 Graham.Williams\@cmis.csiro.au"; +$M{"urw"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"urwstd"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"urwvf"}="5 Feb 1998 09:33:04 Graham.Williams\@cmis.csiro.au"; +$M{"ut-backref"}="10 Nov 1998 10:38:10 Graham.Williams\@cmis.csiro.au"; +$M{"ut-thesis"}="23 Feb 1999 15:02:00 Graham.Williams\@cmis.csiro.au"; +$M{"utorontothesis"}="20 Feb 1998 14:27:24 Graham.Williams\@cmis.csiro.au"; +$M{"utthesis"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"uwthesis"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"vdm"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"vector"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"verbatim"}="29 May 1996 11:58:52 Graham.Williams\@cmis.csiro.au"; +$M{"vertex"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"vfcomb"}="24 Oct 1996 10:25:22 Graham.Williams\@cmis.csiro.au"; +$M{"vfinst"}="10 Sep 1998 18:41:42 Graham.Williams\@cmis.csiro.au"; +$M{"viiptart"}="8 Jul 1998 09:20:53 Graham.Williams\@cmis.csiro.au"; +$M{"vmargin"}="12 Jun 1996 13:14:31 Graham.Williams\@cmis.csiro.au"; +$M{"vncmr"}="19 Jul 1996 08:45:39 Graham.Williams\@cmis.csiro.au"; +$M{"vrb"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"vrsion"}="8 Jul 1998 08:17:05 Graham.Williams\@cmis.csiro.au"; +$M{"vruler"}="24 Oct 1996 11:15:39 Graham.Williams\@cmis.csiro.au"; +$M{"warpcol"}="13 Sep 1998 06:27:36 Graham.Williams\@cmis.csiro.au"; +$M{"wasy-ps"}="25 Jul 1998 06:05:00 Graham.Williams\@cmis.csiro.au"; +$M{"wasy"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"wasy2-ps"}="5 Aug 1998 06:26:09 Graham.Williams\@cmis.csiro.au"; +$M{"wasy2"}="25 Jul 1998 06:18:23 Graham.Williams\@cmis.csiro.au"; +$M{"wasysym"}="5 Jan 1999 07:44:43 Graham.Williams\@cmis.csiro.au"; +$M{"web2c-win32"}="3 Apr 1998 06:38:58 Graham.Williams\@cmis.csiro.au"; +$M{"web2c"}="20 Mar 1998 09:27:08 Graham.Williams\@cmis.csiro.au"; +$M{"williams"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"win95-guide"}="12 Apr 1998 20:46:26 Graham.Williams\@cmis.csiro.au"; +$M{"windvi"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"winedt"}="2 Jul 1998 13:00:44 Graham.Williams\@cmis.csiro.au"; +$M{"winemtex"}="3 Aug 1998 18:15:29 Graham.Williams\@cmis.csiro.au"; +$M{"winshell"}="21 Nov 1998 05:34:40 Graham.Williams\@cmis.csiro.au"; +$M{"wmf2eps"}="12 Nov 1998 20:15:28 Graham.Williams\@cmis.csiro.au"; +$M{"wnri"}="30 Jun 1998 10:56:34 Graham.Williams\@cmis.csiro.au"; +$M{"wntamil"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"word2x"}="29 Apr 1997 14:47:38 Graham.Williams\@cmis.csiro.au"; +$M{"wp-conv"}="1 Aug 1998 05:39:06 Graham.Williams\@cmis.csiro.au"; +$M{"wp2latex"}="23 Sep 1998 05:24:28 Graham.Williams\@cmis.csiro.au"; +$M{"wsuipa"}="13 Aug 1998 05:27:18 Graham.Williams\@cmis.csiro.au"; +$M{"wtex95"}="24 Feb 1998 14:01:24 Graham.Williams\@cmis.csiro.au"; +$M{"xdvi"}="28 Jun 1996 10:08:55 Graham.Williams\@cmis.csiro.au"; +$M{"xdvik"}="6 Apr 1998 05:53:45 Graham.Williams\@cmis.csiro.au"; +$M{"xfig"}="8 Jul 1998 09:08:50 Graham.Williams\@cmis.csiro.au"; +$M{"xtab"}="21 Oct 1998 09:32:30 Graham.Williams\@cmis.csiro.au"; +$M{"xtcapts"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"xtem"}="27 Nov 1997 17:13:37 Graham.Williams\@cmis.csiro.au"; +$M{"xymtex"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"xypic"}="21 Nov 1998 05:35:39 Graham.Williams\@cmis.csiro.au"; +$M{"yannisgr"}="25 Feb 1998 s.rahtz\@elsevier.co.uk"; +$M{"yfonts"}="27 Jan 1999 08:26:02 Graham.Williams\@cmis.csiro.au"; +$M{"yhmath"}="16 May 1996 s.rahtz\@elsevier.co.uk"; +$M{"yi4latex"}="22 Feb 1999 s.rahtz\@elsevier.co.uk"; +$M{"youngtab"}="29 Jun 1998 10:06:42 Graham.Williams\@cmis.csiro.au"; +$M{"yplan99"}="11 Dec 1998 05:45:33 Graham.Williams\@cmis.csiro.au"; +$M{"ytex"}="12 Apr 1997 s.rahtz\@elsevier.co.uk"; +$M{"zefonts"}="30 Sep 1998 07:50:57 Graham.Williams\@cmis.csiro.au"; +1; diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/nocites.tex b/Master/texmf/doc/texlive/source/texlive-en/archive/nocites.tex new file mode 100644 index 00000000000..759b379f30e --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/nocites.tex @@ -0,0 +1,557 @@ +\nocite{a0poster} +\nocite{aaai} +\nocite{abstyles} +\nocite{accfonts} +\nocite{achemso} +\nocite{acronym} +\nocite{adfathesis} +\nocite{adobeother} +\nocite{adobestd} +\nocite{adrlist} +\nocite{ae} +\nocite{aguplus} +\nocite{aiaa} +\nocite{akletter} +\nocite{alatex} +\nocite{algorithms} +\nocite{alg} +\nocite{alphaev5-osf4.0d} +\nocite{altfont} +\nocite{amsfonts} +\nocite{amslatex} +\nocite{amstex} +\nocite{answers} +\nocite{antyktor} +\nocite{apa} +\nocite{apl} +\nocite{appendix} +\nocite{arabtex} +\nocite{arydshln} +\nocite{ar} +\nocite{asaetr} +\nocite{ascii} +\nocite{astro} +\nocite{aurora} +\nocite{authorindex} +\nocite{autotab} +\nocite{babel} +\nocite{backgammon} +\nocite{bakoma} +\nocite{barcode2} +\nocite{barcodes} +\nocite{barr} +\nocite{bbding} +\nocite{bbm} +\nocite{bbold} +\nocite{bbtbase} +\nocite{bbtdoc} +\nocite{beebe} +\nocite{belleek} +\nocite{beton} +\nocite{bez123} +\nocite{bezos} +\nocite{bibarts} +\nocite{biblist} +\nocite{bluesky} +\nocite{blue} +\nocite{booktabs} +\nocite{borceux} +\nocite{bosisio} +\nocite{bridge} +\nocite{brushscr} +\nocite{c-pascal} +\nocite{calendar} +\nocite{calligra} +\nocite{calrsfs} +\nocite{camel} +\nocite{caption} +\nocite{carlisle} +\nocite{casyl} +\nocite{catalog} +\nocite{cbgreek} +\nocite{cc-pl} +\nocite{ccaption} +\nocite{ccfonts} +\nocite{cchess} +\nocite{cdcover} +\nocite{cellular} +\nocite{changebar} +\nocite{chemcono} +\nocite{chemsym} +\nocite{cheq} +\nocite{cherokee} +\nocite{chess} +\nocite{china2e} +\nocite{circ} +\nocite{cirth} +\nocite{cite} +\nocite{cjk} +\nocite{cmbright} +\nocite{cmcyralt} +\nocite{cmcyr} +\nocite{cmdtrack} +\nocite{cmextra} +\nocite{cmpica} +\nocite{cmpk} +\nocite{cmsd} +\nocite{cm} +\nocite{codepage} +\nocite{colorsep} +\nocite{colortab} +\nocite{comment} +\nocite{concmath} +\nocite{concrete} +\nocite{context} +\nocite{covington} +\nocite{croatian} +\nocite{crop} +\nocite{crossword} +\nocite{crosswrd} +\nocite{csfonts} +\nocite{cslatex} +\nocite{csplain} +\nocite{cspsfonts} +\nocite{cstug} +\nocite{cursor} +\nocite{curves} +\nocite{custom-bib} +\nocite{cyrillic} +\nocite{dancers} +\nocite{deleq} +\nocite{devanagari} +\nocite{dialogl} +\nocite{dinbrief} +\nocite{directory} +\nocite{dotseqn} +\nocite{draftcopy} +\nocite{dratex} +\nocite{dropping} +\nocite{dstroke} +\nocite{dtk} +\nocite{duerer} +\nocite{dvipdfm} +\nocite{dvipsbase} +\nocite{dvipsdoc} +\nocite{ean} +\nocite{easy} +\nocite{ecc} +\nocite{ecltree} +\nocite{eco} +\nocite{ecpk} +\nocite{ec} +\nocite{edmac} +\nocite{eepic} +\nocite{egplot} +\nocite{eiad} +\nocite{eijkhout} +\nocite{elsevier} +\nocite{elvish} +\nocite{emp} +\nocite{emulateapj} +\nocite{encodings} +\nocite{endfloat} +\nocite{engwar} +\nocite{envbig} +\nocite{envlab} +\nocite{epigraph} +\nocite{eplain} +\nocite{eqname} +\nocite{eqnarray} +\nocite{esieecv} +\nocite{etexbase} +\nocite{etruscan} +\nocite{euler} +\nocite{euro2} +\nocite{eurofont} +\nocite{europs} +\nocite{eurosans} +\nocite{eurosym} +\nocite{euro} +\nocite{euxm} +\nocite{examdesign} +\nocite{exam} +\nocite{expdlist} +\nocite{expl3} +\nocite{export} +\nocite{fancybox} +\nocite{fancyhdr} +\nocite{fancyref} +\nocite{fancyvrb} +\nocite{fax} +\nocite{fc} +\nocite{feynmf} +\nocite{finbib} +\nocite{floatfig} +\nocite{floatflt} +\nocite{float} +\nocite{fltpage} +\nocite{fncychap} +\nocite{foilhtml} +\nocite{foiltex} +\nocite{fontinst} +\nocite{fontname} +\nocite{footbib} +\nocite{footmisc} +\nocite{footnpag} +\nocite{formats} +\nocite{formula} +\nocite{fp} +\nocite{frankenstein} +\nocite{french} +\nocite{fribrief} +\nocite{fullblck} +\nocite{fullpict} +\nocite{fundus} +\nocite{futhark} +\nocite{g-brief} +\nocite{gb4e} +\nocite{genealogy} +\nocite{general} +\nocite{genmisc} +\nocite{geometry} +\nocite{geomsty} +\nocite{german} +\nocite{germbib} +\nocite{germdoc} +\nocite{gloss} +\nocite{gn-logic} +\nocite{gothic} +\nocite{go} +\nocite{graphics} +\nocite{greek6cbc} +\nocite{grnumalt} +\nocite{grtimes} +\nocite{guides} +\nocite{gustlib} +\nocite{hands} +\nocite{hanging} +\nocite{harpoon} +\nocite{harvard} +\nocite{harvmac} +\nocite{hh} +\nocite{hilowres} +\nocite{histogr} +\nocite{hoekwater} +\nocite{hppa1.1-hpux10.10} +\nocite{html} +\nocite{hvmaths} +\nocite{hyperref} +\nocite{hyper} +\nocite{hyphenat} +\nocite{hyphen} +\nocite{i386-linux-libc5} +\nocite{i386-linux} +\nocite{ibm} +\nocite{ieeepes} +\nocite{ifacmtg} +\nocite{imac} +\nocite{indxcite} +\nocite{info} +\nocite{ini} +\nocite{insbox} +\nocite{ipa} +\nocite{isostds} +\nocite{jadetex} +\nocite{jhep} +\nocite{jknappen} +\nocite{jsmisc} +\nocite{jura} +\nocite{kalender} +\nocite{karnaugh} +\nocite{kdgreek} +\nocite{kluwer} +\nocite{knuth} +\nocite{koma-script} +\nocite{kuvio} +\nocite{labels} +\nocite{lamstex} +\nocite{lastpage} +\nocite{latexfonts} +\nocite{layouts} +\nocite{leaflet} +\nocite{leftidx} +\nocite{lettrine} +\nocite{levy} +\nocite{lgc} +\nocite{lgreek} +\nocite{lhcyr} +\nocite{lh} +\nocite{lineno} +\nocite{linguex} +\nocite{listings} +\nocite{lkort} +\nocite{localloc} +\nocite{logic} +\nocite{lollipop} +\nocite{ltablex} +\nocite{ltx2rtf} +\nocite{ltxbase} +\nocite{ltxdoc} +\nocite{ltxmisc} +\nocite{lucida} +\nocite{ly1} +\nocite{mailing} +\nocite{makeindex} +\nocite{malayalam} +\nocite{malvern} +\nocite{mapcodes} +\nocite{maple} +\nocite{margbib} +\nocite{marvosym} +\nocite{mathcomp} +\nocite{mathematica} +\nocite{mathpple} +\nocite{mcite} +\nocite{mdwtools} +\nocite{metasupp} +\nocite{method} +\nocite{mex} +\nocite{mff} +\nocite{mflogo} +\nocite{mfmisc} +\nocite{mfnfss} +\nocite{mfpic} +\nocite{mftoeps} +\nocite{mft} +\nocite{mhs} +\nocite{midnight} +\nocite{minitoc} +\nocite{mips-irix6.2} +\nocite{misc209} +\nocite{mltex} +\nocite{mnras} +\nocite{monotype} +\nocite{montex} +\nocite{morehelp} +\nocite{moresize} +\nocite{moreverb} +\nocite{morse} +\nocite{mpattern} +\nocite{mpbase} +\nocite{mpfnmark} +\nocite{mslapa} +\nocite{ms} +\nocite{mtbe} +\nocite{multenum} +\nocite{multirow} +\nocite{multi} +\nocite{musictex} +\nocite{musixtex} +\nocite{nassflow} +\nocite{natbib} +\nocite{ncctools} +\nocite{newalg} +\nocite{newlfm} +\nocite{newsletr} +\nocite{newthm} +\nocite{niceframe} +\nocite{nomencl} +\nocite{nrc} +\nocite{ntgclass} +\nocite{ntg} +\nocite{ntheorem} +\nocite{numline} +\nocite{objectz} +\nocite{oca} +\nocite{ocr-a} +\nocite{ogham} +\nocite{ogonek} +\nocite{oldstyle} +\nocite{omegabase} +\nocite{omegafonts} +\nocite{osmanian} +\nocite{ot2cyr} +\nocite{overpic} +\nocite{pacioli} +\nocite{pageno} +\nocite{pandora} +\nocite{paper} +\nocite{paralist} +\nocite{parallel} +\nocite{patch} +\nocite{pawpict} +\nocite{pb-diagram} +\nocite{pdcmac} +\nocite{pdfscreen} +\nocite{pdftex} +\nocite{permute} +\nocite{phoenician} +\nocite{phonetic} +\nocite{physe} +\nocite{phyzzx} +\nocite{picinpar} +\nocite{picins} +\nocite{pictex} +\nocite{piff} +\nocite{pl-qx} +\nocite{plainmisc} +\nocite{plaintex} +\nocite{plari} +\nocite{platex} +\nocite{play} +\nocite{plcalendar} +\nocite{plfonts} +\nocite{plgraph} +\nocite{plpatch} +\nocite{pl} +\nocite{pmgraph} +\nocite{poligraf} +\nocite{polish} +\nocite{polyglot} +\nocite{prettyref} +\nocite{progkeys} +\nocite{program} +\nocite{proofs} +\nocite{protex} +\nocite{psafm} +\nocite{psfig} +\nocite{psfrag} +\nocite{psizzl} +\nocite{pslatex} +\nocite{psnfssx} +\nocite{psnfss} +\nocite{pspicture} +\nocite{pstricks} +\nocite{punk} +\nocite{qfonts} +\nocite{qobitree} +\nocite{qsymbols} +\nocite{quotchap} +\nocite{r-und-s} +\nocite{rcsinfo} +\nocite{rcs} +\nocite{realcalc} +\nocite{refcheck} +\nocite{refman} +\nocite{relenc} +\nocite{revtex} +\nocite{rlepsf} +\nocite{rmpage} +\nocite{rotating} +\nocite{rotfloat} +\nocite{rplain} +\nocite{rs6000-aix4.1.4.0} +\nocite{rsfs} +\nocite{ruhyphen} +\nocite{runic} +\nocite{sanskrit} +\nocite{sauterfonts} +\nocite{scale} +\nocite{schedule} +\nocite{script} +\nocite{sectsty} +\nocite{semantic} +\nocite{seminar} +\nocite{setspace} +\nocite{shadbox} +\nocite{shadethm} +\nocite{shortlst} +\nocite{shorttoc} +\nocite{showdim} +\nocite{showlabels} +\nocite{siam} +\nocite{sidecap} +\nocite{siggraph} +\nocite{simpsons} +\nocite{siunits} +\nocite{slashbox} +\nocite{slidenotes} +\nocite{smallcap} +\nocite{songbook} +\nocite{soul} +\nocite{sparc-solaris2.5.1} +\nocite{sprite} +\nocite{ssqquote} +\nocite{startex} +\nocite{stdclsdv} +\nocite{stmaryrd} +\nocite{subeqnarray} +\nocite{subeqn} +\nocite{subfigure} +\nocite{supertabular} +\nocite{synttree} +\nocite{t2} +\nocite{tabbing} +\nocite{tap} +\nocite{taylor} +\nocite{tbe} +\nocite{tcx} +\nocite{tds} +\nocite{tengwar} +\nocite{tetex} +\nocite{tex-ps} +\nocite{tex4ht} +\nocite{texdraw} +\nocite{texinfo} +\nocite{texip} +\nocite{texlive} +\nocite{texsis} +\nocite{text1} +\nocite{textfit} +\nocite{textmerg} +\nocite{textpos} +\nocite{thesis} +\nocite{threed} +\nocite{thumbpdf} +\nocite{thumb} +\nocite{timesht} +\nocite{timing} +\nocite{tipa} +\nocite{titlefoot} +\nocite{titlesec} +\nocite{tmmaths} +\nocite{tocbibind} +\nocite{tocloft} +\nocite{tocvsec2} +\nocite{tools} +\nocite{tracking} +\nocite{treesvr} +\nocite{treetex} +\nocite{ttf2pk} +\nocite{tugboat} +\nocite{tug} +\nocite{type1cm} +\nocite{type1} +\nocite{typespec} +\nocite{uaclasses} +\nocite{ucthesis} +\nocite{ulsy} +\nocite{umlaute} +\nocite{umrand} +\nocite{underlin} +\nocite{units} +\nocite{universa} +\nocite{uni} +\nocite{unsupported} +\nocite{urwstd} +\nocite{useful} +\nocite{ut-thesis} +\nocite{utthesis} +\nocite{uwthesis} +\nocite{vdm} +\nocite{vector} +\nocite{vertex} +\nocite{vita} +\nocite{vrb} +\nocite{vrsion} +\nocite{warpcol} +\nocite{wasysym} +\nocite{wasy} +\nocite{williams} +\nocite{win32} +\nocite{windvi} +\nocite{wnri} +\nocite{wntamil} +\nocite{wsuipa} +\nocite{xtab} +\nocite{xtcapts} +\nocite{xymtex} +\nocite{xypic} +\nocite{yannisgr} +\nocite{yfonts} +\nocite{yhmath} +\nocite{yi4latex} +\nocite{youngtab} +\nocite{ytex} +\nocite{zed-csp} +\nocite{zefonts} diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/picture.tex b/Master/texmf/doc/texlive/source/texlive-en/archive/picture.tex new file mode 100644 index 00000000000..098cfe18f10 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/picture.tex @@ -0,0 +1,46 @@ +\documentclass{artikel3} +\pagestyle{empty} +\usepackage{pstcol,pst-text,lucidbrb} +\font\manual=manfnt %logo10 doesn't have what we need +\hyphenchar\manual=-1 +\def\MF{{\manual META}\-{\manual FONT}} +\begin{document} +\sffamily +\psset{unit=1mm} +\def\Size#1#2{\fontsize{#1}{#2}\selectfont} +\begin{pspicture}(-58,-58)(58,58) +\pscircle[linewidth=.3pt,linecolor=lightgray]{58} +%\pscircle{23} +\psset{linestyle=none} +% top of circle +\pstextpath[c]{\psarcn(0,0){48}{180}{0}} +{\Size{1.2cm}{1cm}\bfseries \TeX\ Live 4} +\rput(0,34){\begin{minipage}{8cm}\centering \textbf{March 1999}\\[3mm] +\Size{9}{10.5}Ready-to-run \TeX\ system for Linux, Unix (DEC,\\ HP, IBM, +SGI, Sun), and Win32 systems, \\ +based on Web2c 7.3\\ +\end{minipage}} +% bottom of circle +\rput(30,10){\begin{minipage}{2.7cm}\raggedleft\footnotesize +ISO 9660 with Joliet \\and Rock Ridge \\ +extensions\end{minipage}} +\rput(0,-30){\begin{minipage}{7cm}\centering +Macros, fonts, documentation to the\\ +\emph{{\TeX} Directory Structure} standard.\\[2mm] +Editor: Sebastian Rahtz +\end{minipage}} +\pstextpath[c]{\psarc(0,0){45}{180}{0}} +{ +{\Size{14}{14}\ttfamily http://www.tug.org/texlive/} } +\pstextpath[c]{\psarc(0,0){53}{180}{0}} +{\Size{13.2}{14}\bfseries +CSTUG $\bullet$ +Dante e.V. $\bullet$ +GUST $\bullet$ +GUTenberg $\bullet$ +NTG $\bullet$ +TUG $\bullet$ +TUG India $\bullet$ +UK TUG} +\end{pspicture} +\end{document} diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/split.pl b/Master/texmf/doc/texlive/source/texlive-en/archive/split.pl new file mode 100644 index 00000000000..bca00584335 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/split.pl @@ -0,0 +1,16 @@ +#@TeXIndex{a0poster, +open TMP, ">/dev/null"; +while (<>) { + chop; + if (/\@TeXIndex/) { + print TMP "\n"; + close TMP; + $keep=$_; + s/\@TeXIndex{(.*),.*/$1/; + print "[$_]\n"; + open TMP, ">$_.bib"; + print TMP "$keep\n"; + } + else { print TMP "$_\n" ; } + +} diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/status.pl b/Master/texmf/doc/texlive/source/texlive-en/archive/status.pl new file mode 100644 index 00000000000..28c3d0d6d4c --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/status.pl @@ -0,0 +1,31 @@ +#package: pIq +#license: pd +#(but erasing the headers is not allowed) +#Note that I made the most recent change, but +#Mark Shoulson (shoulson@ctr.columbia.edu) +#wrote the initial version. He should be named +#in the catalogue, too. + +#csuov@csv.warwick.ac.uk +#Subject: cmtt +#To: krab@iesd.auc.dk +#Subject: ftn +#To: inas@MIB.HARZ.DE +#Subject: newthm +#To: reckdahl@leland.stanford.edu +#Subject: epslatex +#To: miktex-bug@ronin.in-berlin.de +#Subject: miktex +#To: de8827@blackjack.usma.edu +#Subject: lated +#To: jdyoung@AFIT.AF.MIL +#Subject: afthesis +#xlwy01@uxp1.hrz.uni-dortmund.de (c2cweb) + +$L{"newlfm"}="free-latex"; +$L{"pacioli"}="gpl"; +$L{"etruscan"}="gpl"; +$L{"phoenician"}="gpl"; +$L{"greek6bc"}="gpl"; +$L{"runic"}="gpl"; +1; diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.bib b/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.bib new file mode 100644 index 00000000000..17c75e197b7 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.bib @@ -0,0 +1,235 @@ +@TeXIndex{mips-irix6.2, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {System binaries for SGI running Irix 6.2}, + status = {free}, + texlive = {systems1} +} + +@TeXIndex{alpha-osf3.2, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {System binaries for Alpha running OSF 3.2.}, + status = {free}, + texlive = {systems1} +} + +@TeXIndex{alphaev5-osf4.0d, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {System binaries for Alphaev5 running OSF 4.0d.}, + status = {free}, + texlive = {systems1} +} + +@TeXIndex{alphaev5-osf4.0b, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {System binaries for Alphaev5 running OSF 4.0b.}, + status = {free}, + texlive = {systems1} +} + +@TeXIndex{bbtbase, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {Basic \BibTeX{} support files.}, + status = {free}, + texlive = {bibtex1} +} + +@TeXIndex{bbtdoc, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {Basic \BibTeX{} documentation.}, + status = {free}, + texlive = {bibtex2} +} + +@TeXIndex{catalog, + modified = {February 1999, s.rahtz@elsevier.co.uk}, + abstract = {Graham Williams' Catalogue of \TeX{} packages.}, + status = {free}, + texlive = {doc2} +} + +@TeXIndex{cmpk, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {Computer Modern fonts in PK format.}, + status = {free}, + texlive = {fonts3} +} + +@TeXIndex{dtk, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {Macros for the DANTE publication.}, + status = {free}, + texlive = {latex3} +} + +@TeXIndex{dvipsbase, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {Basic support files for dvips.}, + status = {free}, + texlive = {dvips1} +} + +@TeXIndex{general, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {Useful general documentation.}, + status = {free}, + texlive = {doc1} +} + +@TeXIndex{guides, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {Guides to using \LaTeX, in English, German, French, + Greek and Polish.}, + status = {free}, + texlive = {doc2} +} + +@TeXIndex{hppa1.1-hpux10.10, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {System binaries for HP running hpux10.10.}, + status = {free}, + texlive = {systems1} +} + +@TeXIndex{hyphen, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {Collection of hyphenation patterns.}, + email = {s.rahtz@elsevier.co.uk}, + author = {LaTeX3 Project}, + status = {free}, + texlive = {lang1} +} + +@TeXIndex{i386-linux, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {System binaries for Intel machines running Linux.}, + status = {free}, + texlive = {systems1} +} + +@TeXIndex{i386-linux-libc5, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {System binaries for Intel machines + running Linux, with libc5}, + status = {free}, + texlive = {systems1} +} + +@TeXIndex{ini, + modified = {February 1999, s.rahtz@elsevier.co.uk}, + abstract = {Startup files for building formats.}, + status = {free}, + texlive = {texlive1} +} + +@TeXIndex{lgc, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {Examples from the \emph{\LaTeX{} Graphics Companion}.}, + status = {free}, + texlive = {doc3} +} + +@TeXIndex{metasupp, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {MetaPost support files.}, + status = {free}, + texlive = {texlive1} +} + +@TeXIndex{mfmisc, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {Small support files for \MF.}, + status = {free}, + texlive = {fonts1} +} + +@TeXIndex{mft, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {Support files for MFT.}, + status = {free}, + texlive = {texlive1} +} + +@TeXIndex{misc209, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {Miscellaneous small macro files for \LaTeX 2.09.}, + status = {free}, + texlive = {latex2} +} + +@TeXIndex{mpbase, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {Basic MetaPost support files.}, + status = {free}, + texlive = {metapost1} +} + +@TeXIndex{multi, + modified = {February 1999, s.rahtz@elsevier.co.uk}, + abstract = {dvips header for making n-up pages.}, + status = {free}, + texlive = {dvips3} +} + +@TeXIndex{psafm, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {AFM files for PostScript fonts.}, + status = {free}, + texlive = {fonts3} +} + +@TeXIndex{pspk, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {PK files for common PostScript fonts.}, + status = {free}, + texlive = {fonts3} +} + +@TeXIndex{rs6000-aix4.1, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {System binaries for RS6000 running AIX 4.1.}, + status = {free}, + texlive = {systems1} +} + +@TeXIndex{rs6000-aix4.1.4.0, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {System binaries for RS6000 running AIX 4.1.4.0}, + status = {free}, + texlive = {systems1} +} + +@TeXIndex{sparc-solaris2.5.1, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {System binaries for Sun Sparc running Solaris 2.5.1.}, + status = {free}, + texlive = {systems1} +} + +@TeXIndex{texlive, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {Basic material for \TeXLive{}.}, + status = {free}, + texlive = {texlive1} +} + +@TeXIndex{tug, + modified = {February 1999, s.rahtz@elsevier.co.uk}, + abstract = {\TeX\ Users Group information.}, + status = {free}, + texlive = {doc3} +} + +@TeXIndex{useful, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {Useful documentation; various \LaTeX{} guides, FAQ, + fontname docs, etc.}, + status = {free}, + texlive = {doc2} +} + +@TeXIndex{win32, + modified = {February 1999 s.rahtz@elsevier.co.uk}, + abstract = {System binaries for Windows 32.}, + status = {free}, + texlive = {systems1} +} diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.bst b/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.bst new file mode 100644 index 00000000000..a4954030c95 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.bst @@ -0,0 +1,60 @@ +ENTRY + { + name + status + abstract + texlive + author + ctan + keywords + version + also + modified + } + {} % no integer entry variables + { label extra.label sort.label } % label entry variables + + +STRINGS { s t a.name } + + +FUNCTION {not} +{ { #0 } + { #1 } + if$ +} + +FUNCTION {and} +{ 'skip$ + { pop$ #0 } + if$ +} + +FUNCTION {or} +{ { pop$ #1 } + 'skip$ + if$ +} + +INTEGERS { nameptr namesleft numnames } + + +FUNCTION {TexIndex} { + texlive empty$ + { } + { "\bibitem{" cite$ * "}" * write$ + cite$ "&" * write$ + status "&" * write$ + texlive "&" * write$ + newline$ + abstract write$ + newline$ + } + if$ + } + + +READ + +ITERATE {call.type$} + diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.sty-2003 b/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.sty-2003 new file mode 100644 index 00000000000..3b75b7b5bfd --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.sty-2003 @@ -0,0 +1,378 @@ +\NeedsTeXFormat{LaTeX2e}[1995/12/01] +\ProvidesPackage{tex-live}[2003/09/01 v1.0 TeX Live documentation style] +% +\RequirePackage{alltt} +\RequirePackage{array} +\RequirePackage{colortbl} +\RequirePackage{graphicx} +\RequirePackage{here} +\RequirePackage{longtable} +\RequirePackage{pslatex} +\RequirePackage{shortvrb} +\RequirePackage[normalem]{ulem} +\RequirePackage[obeyspaces]{url} +\RequirePackage{xspace} +\usepackage[T1]{fontenc} +\usepackage[latin1]{inputenc} +%\usepackage[textcomp]{lmodern} +% +\RequirePackage{europs} +\let\euro\EUR +% +\RequirePackage{mflogo} +\def\MP{MetaPost} +\let\mf\MF +% +% for a proper \acro command (even in the context of the definition in +% ltugboat -- \DRC overrides without checking) +\RequirePackage{relsize} +\DeclareRobustCommand{\acro}[1]{\textsmaller{#1}\@} +% +\RequirePackage{fancyvrb} +\DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=\normalsize} +\DefineVerbatimEnvironment{fverbatim}{Verbatim}{fontsize=\footnotesize} +\DefineVerbatimEnvironment{sverbatim}{Verbatim}{fontsize=\small} +\DefineVerbatimEnvironment{boxedverbatim} + {Verbatim}{fontsize=\scriptsize,frame=single} +\DefineVerbatimEnvironment{Verbatim}{Verbatim}{fontsize=\normalsize} +\def\verbatiminput#1{\VerbatimInput[fontsize=\scriptsize]{#1}} +\def\boxedverbatiminput#1{\VerbatimInput[frame=single,fontsize=\scriptsize]{#1}} +\def\listinginput#1#2{\VerbatimInput[fontsize=\scriptsize,firstnumber=#1,numbers=left]{#2}} +\MakeShortVerb\| +% +% +% Done with packages. +% +% Page layout. +\advance\textwidth by 1.1in +\advance\oddsidemargin by -.55in +\advance\evensidemargin by -.55in +% +\advance\textheight by 1in +\advance\topmargin by -.5in +\advance\footskip by -.5in +\pagestyle{headings} +% +% LaTeX parameters. +\renewcommand{\topfraction}{0.85} +\renewcommand{\floatpagefraction}{0.86} +\renewcommand{\textfraction}{0.1} +\renewcommand{\belowcaptionskip}{4pt} +\setcounter{tocdepth}{2} +\setcounter{topnumber}{5} +\setcounter{totalnumber}{5} +% +% linebreaking, etc. +\pretolerance=1000 +\tolerance=1500 +\hbadness=3000 +\vbadness=3000 +\hyphenpenalty=400 +\emergencystretch=.1\hsize +\relpenalty=500 +% +% fonts +\let\sl\it +\let\slfamily\itfamily +\let\textsl\textit +%\def\ttdefault{cmtt} +\def\ttdefault{lmtt} +% +% various sorts of names +\newcommand*{\pkgname}[1]{\textsf{#1}}% package name +\newcommand*{\optname}[1]{\texttt{#1}}% (package,class) option name +\newcommand*{\cmdname}[1]{\textsf{#1}}% command name +\newcommand*{\colname}[1]{\emph{#1}}% collection name +\newcommand*{\dirname}[1]{\path{#1}}% directory name +\newcommand*{\filename}[1]{\path{#1}}% file name +\newcommand*{\envname}[1]{\texttt{#1}}% environment variable name +\newcommand{\code}[1]{\texttt{#1}} +\newcommand{\file}[1]{\texttt{#1}} +\newcommand{\prog}[1]{\texttt{#1}} +\newcommand{\samp}[1]{`\texttt{#1}'} +\newcommand{\var}[1]{\emph{#1}} +\newcommand{\ttvar}[1]{\texttt{\var{#1}}} +% +% underlined command input. +\def\Ucom#1{% + \uline{\rule[-.2\baselineskip]{0pt}{.9\baselineskip}\ttfamily #1}} +\def\OnCD#1{\href{../../../../#1}{\path{#1}}} +% +% GUI menu/button/tab sequence: +\def\guiseq#1{\textsf{#1}} +\def\arw{\unskip$\rightarrow$\ignorespaces} +% +% Special names. +\def\dpi{$\,$dpi\xspace} +\def\bs{{\protect\normalfont\ttfamily\char'134}} +\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} +\def\Q#1{\par\vskip6pt\leftline{#1}\par} +\def\hyph{-} +% +% many abbreviations. +\newcommand{\CS}{$\mathcal{C}\kern-.1667em\lower.5ex% + \hbox{$\mathcal{S}$}\kern-.075em $} +\def\AFMtoTFM{\cmdname{AFM2TFM}\null} +\def\bv{\emph{Baskerville}} +\let\BV=\bv +\def\Dash{\unskip\nobreak\thinspace---\thinspace\ignorespaces} +\def\dvicopy{\cmdname{dvicopy}} +\def\dvidvi{\cmdname{dvidvi}} +\def\dvips{\cmdname{dvips}} +\def\eTeX{$\varepsilon$-\TeX} +\def\fpTeX{\textrm{fp}\TeX\xspace} +\def\GFtoDVI{\cmdname{GFtoDVI}\null} +\def\GFtoPK{\cmdname{GFtoPK}\null} +\def\GFtype{\cmdname{GFtype}} +\def\KPS{Kpathsea} +\def\La{La} +\def\OMEGA{$\Omega$} +\def\OzMF{OzMF} +\def\OzMP{OzMP} +\def\OzTeX{O\kern-.03em z\kern-.15em\TeX} +\def\PKtype{\cmdname{PKtype}} +\def\PLtoTF{\cmdname{PLtoTF}\null} +\def\teTeX{\textrm{te}\TeX\xspace} +\def\TeXLive{\TeX{} Live\xspace} +\def\TFtoPL{\cmdname{TFtoPL}\null} +\def\TK{\textsf{\TeX-Collection}} +\def\TypeI{Type~1} +\def\VFtoVP{\cmdname{VFtoVP}\null} +\def\VPtoVF{\cmdname{VPtoVF}\null} +\def\XEmTeX{\textrm{XEm}\TeX\xspace} +\def\XEmacs{\textrm{XEmacs}\xspace} +\def\Webc{Web2C} +\providecommand*{\CD}{\acro{CD}\xspace} +\providecommand*{\CTAN}{\acro{CTAN}\xspace} +\providecommand*{\DVD}{\acro{DVD}\xspace} +\providecommand*{\HTML}{\acro{HTML}\xspace} +\providecommand*{\MacOSX}{Mac\,\acro{OS\,X}\xspace} +\providecommand*{\PS}{Post\-Script\xspace} +\providecommand*{\TDS}{\acro{TDS}\xspace} +\providecommand*{\dvi}{\acro{DVI}\xspace} +\providecommand*{\web}{\texttt{web}\xspace} +% +% description-like environment that uses tt instead of bf, and doesn't +% go to the left margin. Without the \hfil, get an underfull box. +% Don't why \descriptionlabel doesn't. +\newenvironment{ttdescription} + {\begin{list}{label must be supplied}{% + \itemsep=0pt % these lists tend to have short descriptions + \let\makelabel=\ttdescriptionlabel}}% + {\end{list}} +\newcommand*\ttdescriptionlabel[1]{\hspace\labelsep + \normalfont\ttfamily #1\hfil} +% +% Likewise, for commands using sans serif. +\newenvironment{cmddescription} + {\begin{list}{label must be supplied}{% + \itemsep=0pt + \let\makelabel=\cmddescriptionlabel}}% + {\end{list}} +\newcommand*\cmddescriptionlabel[1]{\hspace\labelsep + \normalfont\sffamily #1\hfil} +% +\newsavebox{\wbox} +\newenvironment{warningbox} + {\begin{lrbox}{\wbox} + \begin{minipage}{.95\textwidth}} + {\end{minipage}\end{lrbox}\fbox{\usebox{\wbox}}} +% +% lrbox is used as a representation marking. I changed it to +% lrBox in tne source file, to get closer to logical marking +\newsavebox{\mylrbox} +\newenvironment{lrBox} + {\begin{lrbox}{\mylrbox}} + {\end{lrbox}} +% +% +% output setup +% +\newif\ifSingleColumn +\providecommand{\Status}{0} +%\typeout{Status is \Status} +% +% By default, we won't be creating hyperlinks. +\def\href#1#2{#2} +\def\hypertarget#1#2{} +\def\email#1{\href{mailto:#1}{\path{#1}}} % \path comes from url +% +% +\ifcase\Status + % \Status = 0 + \typeout{TeX Live documentation for printing} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 1 + \typeout{TeX Live documentation in PDF format} + \RequirePackage[colorlinks,bookmarksopen, + pdfstartview={FitBH -320000},hyperindex]{hyperref} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 2 + \typeout{TeX Live documentation in HTML format} + \RequirePackage[latex4ht]{tex4ht} + \or + % \Status = 3 + \typeout{TeX Live documentation as a Baskerville issue} + \@ifundefined{Fonts}% + {\RequirePackage{ae}}% + {\RequirePackage[T1]{\Fonts}} + \RequirePackage{bvoutln}% outline of baskerville + \RequirePackage{multicol} + \SingleColumnfalse + \or + % \Status = 4 + \typeout{TeX Live documentation as a TUB article} + \@ifundefined{Fonts}% + {\RequirePackage{ae}}% + {\RequirePackage[T1]{\Fonts}} + \SingleColumnfalse + \newenvironment{multicols}[1]{}{} +\fi +% +\ifnum \Status=4 +\else + \RequirePackage{texnames} + \providecommand\TeXXeT{\TeX-{}-% + \kern-.1emX\kern-.125em\lower.5ex\hbox{E}\kern-.1667emT\@} +\fi +% +% hacking at sections etc., to pay attention to baskerville status +\newcommand{\@condend@multicols}{% + \ifSingleColumn + \else + \def\@tempa{multicols}% + \ifx\@tempa\@currenvir + \end{multicols}% + \fi + \fi +} +\let\Section\section +\renewcommand{\section}{% + \@ifstar + {\Section*}% + {% + \@condend@multicols + \@dblarg\@full@section + }% +} +\def\@full@section[#1]#2{% + \Section[#1]{#2}% + \ifSingleColumn\else\begin{multicols}{2}\fi +} +\let\SubSection\subsection +\renewcommand{\subsection}{% + \@ifstar{\SubSection*}% + {% + \@condend@multicols + \@dblarg\@full@subsection + } +} +\def\@full@subsection[#1]#2{% + \SubSection[#1]{#2}% + \ifSingleColumn\else\begin{multicols}{2}\fi +} + +% calm things down a bit if we're in a multiple-column version +\ifSingleColumn +\else + \def\@listI{\leftmargin\leftmargini + \parsep \z@ + \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ + \itemsep \z@ \@plus .1\p@ + } + \let\@listi\@listI + \@listi + \def\@listii{\leftmargin\leftmarginii + \labelwidth\leftmarginii\advance\labelwidth-\labelsep + \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ + \parsep \z@ + \itemsep \z@ \@plus .1\p@ + } + \def\@listiii{\leftmargin\leftmarginiii + \labelwidth\leftmarginiii\advance\labelwidth-\labelsep + \topsep 1\p@ \@plus 1\p@ \@minus 1\p@ + \parsep \z@ + \partopsep \z@ + \itemsep \topsep + } + \def\@listiv{\leftmargin\leftmarginiv + \labelwidth\leftmarginiv\advance\labelwidth-\labelsep + } + \def\@listv{\leftmargin\leftmarginv + \labelwidth\leftmarginv\advance\labelwidth-\labelsep + } + \def\@listvi{\leftmargin\leftmarginvi + \labelwidth\leftmarginvi\advance\labelwidth-\labelsep + } +\fi +% +% array package stuff +\def\arraybackslash{\let\\=\@arraycr} +\newcolumntype{P}[1]{>{\raggedright\arraybackslash}p{#1}} +% +% shaded rows (using facilities of colortbl) +% +\definecolor{pale}{gray}{.9} +\newcount\colrow +\gdef\RowColor{pale} +\def\SetRowColor{% + \rowcolor{\RowColor}% + \global\advance\colrow by1\relax + \ifodd\colrow + \gdef\RowColor{pale}% + \else + \gdef\RowColor{white}% + \fi +} +% redefine to hack up a reference even though we don't need it... +\renewcommand\@bibitem[1]{\if@filesw \immediate\write\@auxout + {\string\bibcite{#1}{?}}\fi\ignorespaces} +% +% \unknownTeXlive is a dummy texlive entry for the biblio +\newcommand\unknownTeXlive[2][\relax]{\textbf{\textsc{unknown}}% + \global\@all@unknown\expandafter{\the\@all@unknown{#2}}% +} +\newtoks\@all@unknown +\global\@all@unknown{} +\AtEndDocument{\@message@unknowns} +\def\@message@unknowns{\edef\@tempa{\the\@all@unknown}% + \ifx\@tempa\@empty + \else + \def\@tempa{*** TeX live package location of }% + \expandafter\@output@unknowns\the\@all@unknown\@empty + \fi +} +\def\@output@unknowns#1{\edef\@tempb{#1}% + \ifx\@tempb\@empty + \typeout{ unknown}% + \else + \message{\@tempa#1,}% + \def\@tempa{}% + \expandafter\@output@unknowns + \fi +} +% +% a hack for the bibliography +\bibliographystyle{tex-live} +\newif\iffirstbibentry +\global\firstbibentrytrue +\let\@@bibitem\bibitem +\renewcommand\bibitem{\iffirstbibentry + \global\firstbibentryfalse + \else + \\\SetRowColor + \fi + \@@bibitem +} + + +% for \Dings +\RequirePackage{pifont} +% available for inter-article dinglines +\def\Dings{\nopagebreak{\footnotesize\dingline{167}}} + +\endinput diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.sty-2004 b/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.sty-2004 new file mode 100644 index 00000000000..54ff32dbe53 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.sty-2004 @@ -0,0 +1,422 @@ +% $Id$ +% TeX Live documentation style. Written by many people over many years. +% Public domain. +% +\NeedsTeXFormat{LaTeX2e}[1995/12/01] +\ProvidesPackage{tex-live}[2004/11/07 v1.0 TeX Live documentation style] +% +\RequirePackage{alltt} +\RequirePackage{array} +\RequirePackage{colortbl} +\RequirePackage{comment} +\RequirePackage{graphicx} +\RequirePackage{here} +\RequirePackage{longtable} +\RequirePackage{shortvrb} +\RequirePackage[normalem]{ulem} +\RequirePackage[obeyspaces]{url} +\RequirePackage{xspace} +% +\RequirePackage{lmodern} +\usepackage{textcomp}% including \textbullet +\usepackage[T1]{fontenc} +\usepackage[latin1]{inputenc} +% +% for a proper \acro command (even in the context of the definition in +% ltugboat -- \DRC overrides without checking) +\RequirePackage{relsize} +\DeclareRobustCommand{\acro}[1]{\textsmaller{#1}\@} +% +\RequirePackage{fancyvrb} +\DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=\normalsize} +\DefineVerbatimEnvironment{fverbatim}{Verbatim}{fontsize=\footnotesize} +\DefineVerbatimEnvironment{sverbatim}{Verbatim}{fontsize=\small} +\DefineVerbatimEnvironment{boxedverbatim} + {Verbatim}{fontsize=\scriptsize,frame=single} +\DefineVerbatimEnvironment{Verbatim}{Verbatim}{fontsize=\normalsize} +\def\verbatiminput#1{\VerbatimInput[fontsize=\scriptsize]{#1}} +\def\boxedverbatiminput#1{\VerbatimInput[frame=single,fontsize=\scriptsize]{#1}} +\def\listinginput#1#2{\VerbatimInput[fontsize=\scriptsize,firstnumber=#1,numbers=left]{#2}} +\MakeShortVerb\| +% +% +% Done with packages. +% +% Page layout. +\advance\textwidth by 1.1in +\advance\oddsidemargin by -.55in +\advance\evensidemargin by -.55in +% +\advance\textheight by 1in +\advance\topmargin by -.5in +\advance\footskip by -.5in +\pagestyle{headings} +% +% LaTeX parameters. +\renewcommand{\topfraction}{0.85} +\renewcommand{\floatpagefraction}{0.86} +\renewcommand{\textfraction}{0.1} +\renewcommand{\belowcaptionskip}{4pt} +\setcounter{tocdepth}{2} +\setcounter{topnumber}{5} +\setcounter{totalnumber}{5} +% +% linebreaking, etc. +\hbadness=4000 +\vbadness=4000 +\emergencystretch=.1\hsize +\relpenalty=500 +% +\def\slash{/\penalty\z@\hskip\z@skip } +% +% various sorts of names +\newcommand*{\pkgname}[1]{\textsf{#1}}% package name +\newcommand*{\optname}[1]{\texttt{#1}}% (package,class) option name +\newcommand*{\cmdname}[1]{\textsf{#1}}% command name +\newcommand*{\colname}[1]{\emph{#1}}% collection name +\newcommand*{\dirname}[1]{\path{#1}}% directory name +\newcommand*{\filename}[1]{\path{#1}}% file name +\newcommand*{\envname}[1]{\texttt{#1}}% environment variable name +\newcommand{\code}[1]{\texttt{#1}} +\newcommand{\file}[1]{\texttt{#1}} +\newcommand{\prog}[1]{\texttt{#1}} +\newcommand{\samp}[1]{`\texttt{#1}'} +\newcommand{\var}[1]{{\sl #1}}% not \textsl, for roman not typewriter slanted. +\newcommand{\ttvar}[1]{\texttt{\var{#1}}} +% +% underlined command input. +\def\Ucom#1{% + \uline{\rule[-.2\baselineskip]{0pt}{.9\baselineskip}\ttfamily #1}} +% +% \CDref is for url's with a #, where we need to write the target url and +% displayed url separately in the input, due to catcode madness. +% (We could simplify/remove this next time, I think.) +\def\CDref#1#2{\texttt{#1}} +% +% \OnCD is currently for any other reference to a file or directory in +% the distribution. PDF readers only open .pdf files, though, so we +% should change this to only use \href for those. Or more likely use +% different macros in the source. +\def\OnCD#1{\href{../../../../#1}{\path{#1}}} +% +% \href incorrectly appends .pdf to anything without an extension; these +% definitions using \hyper@linkurl do not, but they fail for .pdf +% references -- which are the only ones that work anyway. So this is +% useless, in practice. +%\def\CDref#1#2{\hyper@linkurl{#2}{../../../../#1}} +%\def\OnCD#1{\hyper@linkurl{\path{#1}}{../../../../#1}} + +% GUI menu/button/tab sequence: +\def\guiseq#1{\textsf{#1}} +\def\arw{\unskip$\rightarrow$\ignorespaces} +% +% Special names. +\def\dpi{$\,$dpi\xspace} +\def\bs{{\protect\normalfont\ttfamily\char'134}} +\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} +\def\Q#1{\par\vskip6pt\leftline{#1}\par} +\def\hyph{-} +% +% many abbreviations. +\newcommand{\CS}{$\mathcal{C}\kern-.1667em\lower.5ex% + \hbox{$\mathcal{S}$}\kern-.075em $} +\def\AFMtoTFM{\cmdname{AFM2TFM}\null} +\def\bv{\emph{Baskerville}} +\let\BV=\bv +\def\Dash{\unskip\nobreak\thinspace---\thinspace\ignorespaces} +\def\dvicopy{\cmdname{dvicopy}} +\def\dvidvi{\cmdname{dvidvi}} +\def\dvips{\cmdname{dvips}} +\def\eTeX{$\varepsilon$-\TeX} +\def\fpTeX{\textrm{fp}\TeX\xspace} +\def\GFtoDVI{\cmdname{GFtoDVI}\null} +\def\GFtoPK{\cmdname{GFtoPK}\null} +\def\GFtype{\cmdname{GFtype}} +\def\KPS{Kpathsea} +\def\La{La} +\def\OMEGA{$\Omega$} +\def\OzMF{OzMF} +\def\OzMP{OzMP} +\def\OzTeX{O\kern-.03em z\kern-.15em\TeX} +\def\p.{p.\,} +\def\PKtype{\cmdname{PKtype}} +\def\PLtoTF{\cmdname{PLtoTF}\null} +\def\ProTeXt{Pro\TeX t} +\def\teTeX{\textrm{te}\TeX\xspace} +\def\TeXLive{\TeX{} Live\xspace} +\def\TFtoPL{\cmdname{TFtoPL}\null} +\def\TK{\textsf{\TeX-Collection}} +\let\TL=\TeXLive +\def\TypeI{Type~1} +\def\VFtoVP{\cmdname{VFtoVP}\null} +\def\VPtoVF{\cmdname{VPtoVF}\null} +\def\Thanh{H\`an~Th\^e\llap{\raise 0.5ex\hbox{\'{}}}~Th\`anh} +\def\XEmTeX{\textrm{XEm}\TeX\xspace} +\def\XEmacs{\textrm{XEmacs}\xspace} +\def\Webc{Web2C} +\providecommand*{\CD}{\acro{CD}\xspace} +\providecommand*{\CTAN}{\acro{CTAN}\xspace} +\providecommand*{\DVD}{\acro{DVD}\xspace} +\providecommand*{\HTML}{\acro{HTML}\xspace} +\providecommand*{\MacOSX}{Mac\,\acro{OS\,X}\xspace} +\providecommand*{\PS}{Post\-Script\xspace} +\providecommand*{\TDS}{\acro{TDS}\xspace} +\providecommand*{\dvi}{\acro{DVI}\xspace} +\providecommand*{\web}{\texttt{web}\xspace} + +% Include an image. +% #1 - name of image (pictures/#1.jpg, always .jpg please) +% #2 - bb for html +% #3 - width for TeX +% +\def\tlimage#1#2#3{% + \ifnum \Status=2 % html, want relative path in output + \includegraphics[#2]{../../general/texlive-common/pictures/#1.jpg} + \else % not html, handled by TEXINPUTS in Makefile + \includegraphics[width=#3]{pictures/#1.jpg} + \fi + \\[5mm] +} +% +% description-like environment that uses tt instead of bf, and doesn't +% go to the left margin. Without the \hfil, get an underfull box. +% Don't know why \descriptionlabel doesn't. +% +\newenvironment{ttdescription} + {\begin{list}{label must be supplied}{% + \itemsep=0pt % these lists tend to have short descriptions + \parindent=0pt + \let\makelabel=\ttdescriptionlabel}}% + {\end{list}} +\newcommand*\ttdescriptionlabel[1]{\hspace\labelsep + \normalfont\ttfamily #1\hfil} +% +% Likewise, for commands using sans serif. +\newenvironment{cmddescription} + {\begin{list}{label must be supplied}{% + \itemsep=0pt + \let\makelabel=\cmddescriptionlabel}}% + {\end{list}} +\newcommand*\cmddescriptionlabel[1]{\hspace\labelsep + \normalfont\sffamily #1\hfil} + +% General squeezed itemize. +\newenvironment{itemize*}% + {\begin{itemize}% + \setlength{\itemsep}{0pt}% + \setlength{\parskip}{0pt}}% + {\end{itemize}} + +\newsavebox{\wbox} +\newenvironment{warningbox} + {\begin{lrbox}{\wbox} + \begin{minipage}{.95\textwidth}} + {\end{minipage}\end{lrbox}\fbox{\usebox{\wbox}}} +% +% lrbox is used as a representation marking. I changed it to +% lrBox in tne source file, to get closer to logical marking +\newsavebox{\mylrbox} +\newenvironment{lrBox} + {\begin{lrbox}{\mylrbox}} + {\end{lrbox}} + + +% emacs-page output setup +% +\newif\ifSingleColumn +\providecommand{\Status}{0} +%\typeout{Status is \Status} +% +% By default, we won't be creating hyperlinks. +\def\href#1#2{#2} +\def\hypertarget#1#2{} +\def\email#1{\href{mailto:#1}{\path{#1}}} % \path comes from url +% +\definecolor{hypercolor}{rgb}{0.5,0.0,0.5} % purplish external links. +% +% +\ifcase\Status + % \Status = 0 + \typeout{TeX Live documentation in DVI format} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 1 + \typeout{TeX Live documentation in PDF format} + \RequirePackage[breaklinks, + colorlinks,linkcolor=hypercolor,citecolor=hypercolor, + pagecolor=hypercolor,urlcolor=hypercolor, + filecolor=hypercolor, + bookmarksopen,pdfstartview={FitBH -320000},hyperindex] + {hyperref} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 2 + \typeout{TeX Live documentation in HTML format} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + % read our config file, live4ht.cfg; q.v., for more definitions. + % hyperref load must come after the tex4ht load. + \RequirePackage[live4ht]{tex4ht} + \RequirePackage[tex4ht]{hyperref} \hyperlinkfileprefix{} + % definitions need simplifying for TeX4ht to make relative paths work. + \def\CDref#1#2{\href{../../../../#1}{#2}} + \def\OnCD#1{\href{../../../../#1}{#1}} + \or + % \Status = 3 + \typeout{TeX Live documentation as a Baskerville issue} + \@ifundefined{Fonts}% + {\RequirePackage{ae}}% + {\RequirePackage[T1]{\Fonts}} + \RequirePackage{bvoutln}% outline of baskerville + \SingleColumnfalse + \RequirePackage{multicol} + \or + % \Status = 4 + \typeout{TeX Live documentation as a TUB article} + \@ifundefined{Fonts}% + {\RequirePackage{ae}}% + {\RequirePackage[T1]{\Fonts}} + \SingleColumnfalse + \newenvironment{multicols}[1]{}{} +\fi +% +\ifnum \Status=4 +\else + \RequirePackage{texnames} + \providecommand\TeXXeT{\TeX-{}-% + \kern-.1emX\kern-.125em\lower.5ex\hbox{E}\kern-.1667emT\@} + \def\MP{MetaPost} + \let\mf\MF + \newcommand\ConTeXt{C\kern-.0333emon\-\kern-.0667em\TeX\kern-.0333emt} + \newcommand\MIKTEX{MiK\kern-.025em \TeX}% per www.miktex.org + % from pictex.tex: + \ifx\PiC\undefined \def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC} \fi + \ifx\PiCTeX\undefined \def\PiCTeX{\PiC\kern-.11em\TeX} \fi +\fi +% +% hacking at sections etc., to pay attention to baskerville status +\newcommand{\@condend@multicols}{% + \ifSingleColumn + \else + \def\@tempa{multicols}% + \ifx\@tempa\@currenvir + \end{multicols}% + \fi + \fi +} +\let\Section\section +\renewcommand{\section}{% + \@ifstar + {\Section*}% + {% + \@condend@multicols + \@dblarg\@full@section + }% +} +\def\@full@section[#1]#2{% + \Section[#1]{#2}% + \ifSingleColumn\else\begin{multicols}{2}\fi +} +\let\SubSection\subsection +\renewcommand{\subsection}{% + \@ifstar{\SubSection*}% + {% + \@condend@multicols + \@dblarg\@full@subsection + } +} +\def\@full@subsection[#1]#2{% + \SubSection[#1]{#2}% + \ifSingleColumn\else\begin{multicols}{2}\fi +} + +% calm things down a bit if we're in a multiple-column version +\ifSingleColumn +\else + \def\@listI{\leftmargin\leftmargini + \parsep \z@ + \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ + \itemsep \z@ \@plus .1\p@ + } + \let\@listi\@listI + \@listi + \def\@listii{\leftmargin\leftmarginii + \labelwidth\leftmarginii\advance\labelwidth-\labelsep + \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ + \parsep \z@ + \itemsep \z@ \@plus .1\p@ + } + \def\@listiii{\leftmargin\leftmarginiii + \labelwidth\leftmarginiii\advance\labelwidth-\labelsep + \topsep 1\p@ \@plus 1\p@ \@minus 1\p@ + \parsep \z@ + \partopsep \z@ + \itemsep \topsep + } + \def\@listiv{\leftmargin\leftmarginiv + \labelwidth\leftmarginiv\advance\labelwidth-\labelsep + } + \def\@listv{\leftmargin\leftmarginv + \labelwidth\leftmarginv\advance\labelwidth-\labelsep + } + \def\@listvi{\leftmargin\leftmarginvi + \labelwidth\leftmarginvi\advance\labelwidth-\labelsep + } +\fi +% +% array package stuff +\def\arraybackslash{\let\\=\@arraycr} +\newcolumntype{P}[1]{>{\raggedright\arraybackslash}p{#1}} +% +% shaded rows (using facilities of colortbl) +% +\definecolor{pale}{gray}{.9} +\newcount\colrow +\gdef\RowColor{pale} +\def\SetRowColor{% + \rowcolor{\RowColor}% + \global\advance\colrow by1\relax + \ifodd\colrow + \gdef\RowColor{pale}% + \else + \gdef\RowColor{white}% + \fi +} +% redefine to hack up a reference even though we don't need it... +\renewcommand\@bibitem[1]{\if@filesw \immediate\write\@auxout + {\string\bibcite{#1}{?}}\fi\ignorespaces} +% +% \unknownTeXlive is a dummy texlive entry for the biblio +\newcommand\unknownTeXlive[2][\relax]{\textbf{\textsc{unknown}}% + \global\@all@unknown\expandafter{\the\@all@unknown{#2}}% +} +\newtoks\@all@unknown +\global\@all@unknown{} +\AtEndDocument{\@message@unknowns} +\def\@message@unknowns{\edef\@tempa{\the\@all@unknown}% + \ifx\@tempa\@empty + \else + \def\@tempa{*** TeX live package location of }% + \expandafter\@output@unknowns\the\@all@unknown\@empty + \fi +} +\def\@output@unknowns#1{\edef\@tempb{#1}% + \ifx\@tempb\@empty + \typeout{ unknown}% + \else + \message{\@tempa#1,}% + \def\@tempa{}% + \expandafter\@output@unknowns + \fi +} + + +% Silence font warnings about no bold typewriter in LM. +\def\@font@warning#1{}% + +% Silence hyperref warnings about \kern. +\def\HyPsd@Warning#1{}% + +\endinput diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.sty-2005 b/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.sty-2005 new file mode 100644 index 00000000000..487c8b8d7a2 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.sty-2005 @@ -0,0 +1,429 @@ +% $Id: tex-live.sty 1513 2006-02-13 00:22:35Z karl $ +% TeX Live documentation style. Written by many people over many years. +% Public domain. +% +\NeedsTeXFormat{LaTeX2e}[1995/12/01] +\ProvidesPackage{tex-live}[2005/09/24 v1.5 TeX Live documentation style] +% +\RequirePackage{alltt} +\RequirePackage{array} +\RequirePackage{colortbl} +\RequirePackage{comment} +\RequirePackage{float} +\RequirePackage{graphicx} +\RequirePackage{longtable} +\RequirePackage{shortvrb} +\RequirePackage[normalem]{ulem} +\RequirePackage[obeyspaces]{url} +\RequirePackage{xspace} +% +\RequirePackage{lmodern} +\usepackage{textcomp}% including \textbullet +\usepackage[T1]{fontenc} +\usepackage[latin1]{inputenc} +% +% for a proper \acro command (even in the context of the definition in +% ltugboat -- \DRC overrides without checking) +\RequirePackage{relsize} +\DeclareRobustCommand{\acro}[1]{\textsmaller{#1}\@} +% +\RequirePackage{fancyvrb} +\DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=\normalsize} +\DefineVerbatimEnvironment{fverbatim}{Verbatim}{fontsize=\footnotesize} +\DefineVerbatimEnvironment{sverbatim}{Verbatim}{fontsize=\small} +\DefineVerbatimEnvironment{boxedverbatim} + {Verbatim}{fontsize=\scriptsize,frame=single} +\DefineVerbatimEnvironment{Verbatim}{Verbatim}{fontsize=\normalsize} +\def\verbatiminput#1{\VerbatimInput[fontsize=\scriptsize]{#1}} +\def\boxedverbatiminput#1{\VerbatimInput[frame=single,fontsize=\scriptsize]{#1}} +\def\listinginput#1#2{\VerbatimInput[fontsize=\scriptsize,firstnumber=#1,numbers=left]{#2}} +\MakeShortVerb\| +% +% +% Done with packages. +% +% Page layout. +\advance\textwidth by 1.1in +\advance\oddsidemargin by -.55in +\advance\evensidemargin by -.55in +% +\advance\textheight by 1in +\advance\topmargin by -.5in +\advance\footskip by -.5in +\pagestyle{headings} +% +% LaTeX parameters. +\renewcommand{\topfraction}{0.85} +\renewcommand{\floatpagefraction}{0.86} +\renewcommand{\textfraction}{0.1} +\renewcommand{\belowcaptionskip}{4pt} +\setcounter{tocdepth}{2} +\setcounter{topnumber}{5} +\setcounter{totalnumber}{5} +% +% linebreaking, etc. +\hbadness=4000 +\vbadness=4000 +\emergencystretch=.1\hsize +\relpenalty=500 +% +\def\slash{/\penalty\z@\hskip\z@skip } +% +% various sorts of names +\newcommand*{\pkgname}[1]{\textsf{#1}}% package name +\newcommand*{\optname}[1]{\texttt{#1}}% (package,class) option name +\newcommand*{\cmdname}[1]{\textsf{#1}}% command name +\newcommand*{\colname}[1]{\emph{#1}}% collection name +\newcommand*{\dirname}[1]{\path{#1}}% directory name +\newcommand*{\filename}[1]{\path{#1}}% file name +\newcommand*{\envname}[1]{\texttt{#1}}% environment variable name +\newcommand{\code}[1]{\texttt{#1}} +\newcommand{\file}[1]{\texttt{#1}} +\newcommand{\prog}[1]{\texttt{#1}} +\newcommand{\samp}[1]{`\texttt{#1}'} +\newcommand{\var}[1]{{\sl #1}}% not \textsl, for roman not typewriter slanted. +\newcommand{\ttvar}[1]{\texttt{\var{#1}}} +% +% underlined command input. +\def\Ucom#1{% + \uline{\rule[-.2\baselineskip]{0pt}{.9\baselineskip}\ttfamily #1}} +% +% \CDref is for url's with a #, where we need to write the target url and +% displayed url separately in the input, due to catcode madness. +% (We could simplify/remove this next time, I think.) +\def\CDref#1#2{\texttt{#1}} +% +% \OnCD is currently for any other reference to a file or directory in +% the distribution. PDF readers only open .pdf files, though, so we +% should change this to only use \href for those. Or more likely use +% different macros in the source. +\def\OnCD#1{\href{../../../../#1}{\path{#1}}} +% +% \href incorrectly appends .pdf to anything without an extension; these +% definitions using \hyper@linkurl do not, but they fail for .pdf +% references -- which are the only ones that work anyway. So this is +% useless, in practice. +%\def\CDref#1#2{\hyper@linkurl{#2}{../../../../#1}} +%\def\OnCD#1{\hyper@linkurl{\path{#1}}{../../../../#1}} + +% GUI menu/button/tab sequence: +\def\guiseq#1{\textsf{#1}} +\def\arw{\unskip$\rightarrow$\ignorespaces} +% +% Special names. +\def\dpi{$\,$dpi\xspace} +\def\bs{{\protect\normalfont\ttfamily\char'134}} +\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} +\def\Q#1{\par\vskip6pt\leftline{#1}\par} +\def\hyph{-} +% +% many abbreviations. +\newcommand{\CS}{$\mathcal{C}\kern-.1667em\lower.5ex% + \hbox{$\mathcal{S}$}\kern-.075em $} +\def\AFMtoTFM{\cmdname{AFM2TFM}\null} +\def\bv{\emph{Baskerville}} +\let\BV=\bv +\def\Dash{\unskip\nobreak\thinspace---\thinspace\ignorespaces} +\def\dvicopy{\cmdname{dvicopy}} +\def\dvidvi{\cmdname{dvidvi}} +\def\dvips{\cmdname{dvips}} +\def\eTeX{$\varepsilon$-\TeX} +\def\fpTeX{\textrm{fp}\TeX\xspace} +\def\GFtoDVI{\cmdname{GFtoDVI}\null} +\def\GFtoPK{\cmdname{GFtoPK}\null} +\def\GFtype{\cmdname{GFtype}} +\def\KPS{Kpathsea} +\def\La{La} +\def\OMEGA{$\Omega$} +\def\OzMF{OzMF} +\def\OzMP{OzMP} +\def\OzTeX{O\kern-.03em z\kern-.15em\TeX} +\def\p.{p.\,} +\def\PKtype{\cmdname{PKtype}} +\def\PLtoTF{\cmdname{PLtoTF}\null} +\def\ProTeXt{Pro\TeX t} +\def\teTeX{\textrm{te}\TeX\xspace} +\def\TeXLive{\TeX{} Live\xspace} +\def\TFtoPL{\cmdname{TFtoPL}\null} +\def\TK{\textsf{\TeX\ Collection}} +\let\TL=\TeXLive +\def\TypeI{Type~1} +\def\VFtoVP{\cmdname{VFtoVP}\null} +\def\VPtoVF{\cmdname{VPtoVF}\null} +\def\Thanh{H\`an~Th\^e\llap{\raise 0.5ex\hbox{\'{}}}~Th\`anh} +\def\XEmTeX{\textrm{XEm}\TeX\xspace} +\def\XEmacs{\textrm{XEmacs}\xspace} +\def\Webc{Web2C} +\providecommand*{\CD}{\acro{CD}\xspace} +\providecommand*{\CTAN}{\acro{CTAN}\xspace} +\providecommand*{\DVD}{\acro{DVD}\xspace} +\providecommand*{\HTML}{\acro{HTML}\xspace} +\providecommand*{\MacOSX}{Mac\,\acro{OS\,X}\xspace} +\providecommand*{\PS}{Post\-Script\xspace} +\providecommand*{\TDS}{\acro{TDS}\xspace} +\providecommand*{\dvi}{\acro{DVI}\xspace} +\providecommand*{\web}{\texttt{web}\xspace} + +% Include an image. +% #1 - name of image (pictures/#1.jpg, always .jpg please) +% #2 - bb for html +% #3 - width for TeX +% +\def\tlimage#1#2#3{% + \ifnum \Status=2 % html, want relative path in output + \includegraphics[#2]{../../general/texlive-common/pictures/#1.jpg} + \else % not html, handled by TEXINPUTS in Makefile + \includegraphics[width=#3]{pictures/#1.jpg} + \fi + \\[5mm] +} +% +% description-like environment that uses tt instead of bf, and doesn't +% go to the left margin. Without the \hfil, get an underfull box. +% Don't know why \descriptionlabel doesn't. +% +\newenvironment{ttdescription} + {\begin{list}{label must be supplied}{% + \itemsep=0pt % these lists tend to have short descriptions + \parindent=0pt + \let\makelabel=\ttdescriptionlabel}}% + {\end{list}} +\newcommand*\ttdescriptionlabel[1]{\hspace\labelsep + \normalfont\ttfamily #1\hfil} +% +% Likewise, for commands using sans serif. +\newenvironment{cmddescription} + {\begin{list}{label must be supplied}{% + \itemsep=0pt + \let\makelabel=\cmddescriptionlabel}}% + {\end{list}} +\newcommand*\cmddescriptionlabel[1]{\hspace\labelsep + \normalfont\sffamily #1\hfil} + +% General squeezed itemize. +\newenvironment{itemize*}% + {\begin{itemize}% + \setlength{\itemsep}{0pt}% + \setlength{\parskip}{0pt}}% + {\end{itemize}} + +\newsavebox{\wbox} +\newenvironment{warningbox} + {\begin{lrbox}{\wbox} + \begin{minipage}{.95\textwidth}} + {\end{minipage}\end{lrbox}\fbox{\usebox{\wbox}}} +% +% lrbox is used as a representation marking. I changed it to +% lrBox in tne source file, to get closer to logical marking +\newsavebox{\mylrbox} +\newenvironment{lrBox} + {\begin{lrbox}{\mylrbox}} + {\end{lrbox}} + + +% emacs-page output setup +% +\ifx \HCode\UnDef + \providecommand{\Status}{0}% running TeX +\else + \providecommand{\Status}{2}% running TeX4ht +\fi +%\typeout{Status is \Status} +% +\newif\ifSingleColumn +% +% By default, we won't be creating hyperlinks. +\def\href#1#2{#2} +\def\hypertarget#1#2{} +\def\email#1{\href{mailto:#1}{\path{#1}}} % \path comes from url +% +\definecolor{hypercolor}{rgb}{0.5,0.0,0.5} % purplish external links. +% +% +\ifcase\Status + % \Status = 0 + \typeout{TeX Live documentation in DVI format} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 1 + \typeout{TeX Live documentation in PDF format} + \RequirePackage[breaklinks, + colorlinks,linkcolor=hypercolor,citecolor=hypercolor, + pagecolor=hypercolor,urlcolor=hypercolor, + filecolor=hypercolor, + bookmarksopen, + %pdfstartview={FitBH -320000}, % fails with acrobat7 + hyperindex] + {hyperref} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 2 + \typeout{TeX Live documentation in HTML format} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + % read our config file, live4ht.cfg; q.v., for more definitions. + % hyperref load must come after the tex4ht load. + \RequirePackage[live4ht]{tex4ht} + \RequirePackage[tex4ht]{hyperref} \hyperlinkfileprefix{} + % definitions need simplifying for TeX4ht to make relative paths work. + \def\CDref#1#2{\href{../../../../#1}{#2}} + \def\OnCD#1{\href{../../../../#1}{#1}} + \or + % \Status = 3 + \typeout{TeX Live documentation as a Baskerville issue} + \@ifundefined{Fonts}% + {\RequirePackage{ae}}% + {\RequirePackage[T1]{\Fonts}} + \RequirePackage{bvoutln}% outline of baskerville + \SingleColumnfalse + \RequirePackage{multicol} + \or + % \Status = 4 + \typeout{TeX Live documentation as a TUB article} + \@ifundefined{Fonts}% + {\RequirePackage{ae}}% + {\RequirePackage[T1]{\Fonts}} + \SingleColumnfalse + \newenvironment{multicols}[1]{}{} +\fi +% +\ifnum \Status=4 +\else + \RequirePackage{texnames} + \providecommand\TeXXeT{\TeX-{}-% + \kern-.1emX\kern-.125em\lower.5ex\hbox{E}\kern-.1667emT\@} + \def\MP{MetaPost} + \let\mf\MF + \newcommand\ConTeXt{C\kern-.0333emon\-\kern-.0667em\TeX\kern-.0333emt} + \newcommand\MIKTEX{MiK\kern-.025em \TeX}% per www.miktex.org + % from pictex.tex: + \ifx\PiC\undefined \def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC} \fi + \ifx\PiCTeX\undefined \def\PiCTeX{\PiC\kern-.11em\TeX} \fi +\fi +% +% hacking at sections etc., to pay attention to baskerville status +\newcommand{\@condend@multicols}{% + \ifSingleColumn + \else + \def\@tempa{multicols}% + \ifx\@tempa\@currenvir + \end{multicols}% + \fi + \fi +} +\let\Section\section +\renewcommand{\section}{% + \@ifstar + {\Section*}% + {% + \@condend@multicols + \@dblarg\@full@section + }% +} +\def\@full@section[#1]#2{% + \Section[#1]{#2}% + \ifSingleColumn\else\begin{multicols}{2}\fi +} +\let\SubSection\subsection +\renewcommand{\subsection}{% + \@ifstar{\SubSection*}% + {% + \@condend@multicols + \@dblarg\@full@subsection + } +} +\def\@full@subsection[#1]#2{% + \SubSection[#1]{#2}% + \ifSingleColumn\else\begin{multicols}{2}\fi +} + +% calm things down a bit if we're in a multiple-column version +\ifSingleColumn +\else + \def\@listI{\leftmargin\leftmargini + \parsep \z@ + \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ + \itemsep \z@ \@plus .1\p@ + } + \let\@listi\@listI + \@listi + \def\@listii{\leftmargin\leftmarginii + \labelwidth\leftmarginii\advance\labelwidth-\labelsep + \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ + \parsep \z@ + \itemsep \z@ \@plus .1\p@ + } + \def\@listiii{\leftmargin\leftmarginiii + \labelwidth\leftmarginiii\advance\labelwidth-\labelsep + \topsep 1\p@ \@plus 1\p@ \@minus 1\p@ + \parsep \z@ + \partopsep \z@ + \itemsep \topsep + } + \def\@listiv{\leftmargin\leftmarginiv + \labelwidth\leftmarginiv\advance\labelwidth-\labelsep + } + \def\@listv{\leftmargin\leftmarginv + \labelwidth\leftmarginv\advance\labelwidth-\labelsep + } + \def\@listvi{\leftmargin\leftmarginvi + \labelwidth\leftmarginvi\advance\labelwidth-\labelsep + } +\fi +% +% array package stuff +\def\arraybackslash{\let\\=\@arraycr} +\newcolumntype{P}[1]{>{\raggedright\arraybackslash}p{#1}} +% +% shaded rows (using facilities of colortbl) +% +\definecolor{pale}{gray}{.9} +\newcount\colrow +\gdef\RowColor{pale} +\def\SetRowColor{% + \rowcolor{\RowColor}% + \global\advance\colrow by1\relax + \ifodd\colrow + \gdef\RowColor{pale}% + \else + \gdef\RowColor{white}% + \fi +} +% redefine to hack up a reference even though we don't need it... +\renewcommand\@bibitem[1]{\if@filesw \immediate\write\@auxout + {\string\bibcite{#1}{?}}\fi\ignorespaces} +% +% \unknownTeXlive is a dummy texlive entry for the biblio +\newcommand\unknownTeXlive[2][\relax]{\textbf{\textsc{unknown}}% + \global\@all@unknown\expandafter{\the\@all@unknown{#2}}% +} +\newtoks\@all@unknown +\global\@all@unknown{} +\AtEndDocument{\@message@unknowns} +\def\@message@unknowns{\edef\@tempa{\the\@all@unknown}% + \ifx\@tempa\@empty + \else + \def\@tempa{*** TeX live package location of }% + \expandafter\@output@unknowns\the\@all@unknown\@empty + \fi +} +\def\@output@unknowns#1{\edef\@tempb{#1}% + \ifx\@tempb\@empty + \typeout{ unknown}% + \else + \message{\@tempa#1,}% + \def\@tempa{}% + \expandafter\@output@unknowns + \fi +} + + +% Silence font warnings about no bold typewriter in LM. +\def\@font@warning#1{}% + +% Silence hyperref warnings about \kern. +\def\HyPsd@Warning#1{}% + +\endinput diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.sty-2007 b/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.sty-2007 new file mode 100644 index 00000000000..487c8b8d7a2 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.sty-2007 @@ -0,0 +1,429 @@ +% $Id: tex-live.sty 1513 2006-02-13 00:22:35Z karl $ +% TeX Live documentation style. Written by many people over many years. +% Public domain. +% +\NeedsTeXFormat{LaTeX2e}[1995/12/01] +\ProvidesPackage{tex-live}[2005/09/24 v1.5 TeX Live documentation style] +% +\RequirePackage{alltt} +\RequirePackage{array} +\RequirePackage{colortbl} +\RequirePackage{comment} +\RequirePackage{float} +\RequirePackage{graphicx} +\RequirePackage{longtable} +\RequirePackage{shortvrb} +\RequirePackage[normalem]{ulem} +\RequirePackage[obeyspaces]{url} +\RequirePackage{xspace} +% +\RequirePackage{lmodern} +\usepackage{textcomp}% including \textbullet +\usepackage[T1]{fontenc} +\usepackage[latin1]{inputenc} +% +% for a proper \acro command (even in the context of the definition in +% ltugboat -- \DRC overrides without checking) +\RequirePackage{relsize} +\DeclareRobustCommand{\acro}[1]{\textsmaller{#1}\@} +% +\RequirePackage{fancyvrb} +\DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=\normalsize} +\DefineVerbatimEnvironment{fverbatim}{Verbatim}{fontsize=\footnotesize} +\DefineVerbatimEnvironment{sverbatim}{Verbatim}{fontsize=\small} +\DefineVerbatimEnvironment{boxedverbatim} + {Verbatim}{fontsize=\scriptsize,frame=single} +\DefineVerbatimEnvironment{Verbatim}{Verbatim}{fontsize=\normalsize} +\def\verbatiminput#1{\VerbatimInput[fontsize=\scriptsize]{#1}} +\def\boxedverbatiminput#1{\VerbatimInput[frame=single,fontsize=\scriptsize]{#1}} +\def\listinginput#1#2{\VerbatimInput[fontsize=\scriptsize,firstnumber=#1,numbers=left]{#2}} +\MakeShortVerb\| +% +% +% Done with packages. +% +% Page layout. +\advance\textwidth by 1.1in +\advance\oddsidemargin by -.55in +\advance\evensidemargin by -.55in +% +\advance\textheight by 1in +\advance\topmargin by -.5in +\advance\footskip by -.5in +\pagestyle{headings} +% +% LaTeX parameters. +\renewcommand{\topfraction}{0.85} +\renewcommand{\floatpagefraction}{0.86} +\renewcommand{\textfraction}{0.1} +\renewcommand{\belowcaptionskip}{4pt} +\setcounter{tocdepth}{2} +\setcounter{topnumber}{5} +\setcounter{totalnumber}{5} +% +% linebreaking, etc. +\hbadness=4000 +\vbadness=4000 +\emergencystretch=.1\hsize +\relpenalty=500 +% +\def\slash{/\penalty\z@\hskip\z@skip } +% +% various sorts of names +\newcommand*{\pkgname}[1]{\textsf{#1}}% package name +\newcommand*{\optname}[1]{\texttt{#1}}% (package,class) option name +\newcommand*{\cmdname}[1]{\textsf{#1}}% command name +\newcommand*{\colname}[1]{\emph{#1}}% collection name +\newcommand*{\dirname}[1]{\path{#1}}% directory name +\newcommand*{\filename}[1]{\path{#1}}% file name +\newcommand*{\envname}[1]{\texttt{#1}}% environment variable name +\newcommand{\code}[1]{\texttt{#1}} +\newcommand{\file}[1]{\texttt{#1}} +\newcommand{\prog}[1]{\texttt{#1}} +\newcommand{\samp}[1]{`\texttt{#1}'} +\newcommand{\var}[1]{{\sl #1}}% not \textsl, for roman not typewriter slanted. +\newcommand{\ttvar}[1]{\texttt{\var{#1}}} +% +% underlined command input. +\def\Ucom#1{% + \uline{\rule[-.2\baselineskip]{0pt}{.9\baselineskip}\ttfamily #1}} +% +% \CDref is for url's with a #, where we need to write the target url and +% displayed url separately in the input, due to catcode madness. +% (We could simplify/remove this next time, I think.) +\def\CDref#1#2{\texttt{#1}} +% +% \OnCD is currently for any other reference to a file or directory in +% the distribution. PDF readers only open .pdf files, though, so we +% should change this to only use \href for those. Or more likely use +% different macros in the source. +\def\OnCD#1{\href{../../../../#1}{\path{#1}}} +% +% \href incorrectly appends .pdf to anything without an extension; these +% definitions using \hyper@linkurl do not, but they fail for .pdf +% references -- which are the only ones that work anyway. So this is +% useless, in practice. +%\def\CDref#1#2{\hyper@linkurl{#2}{../../../../#1}} +%\def\OnCD#1{\hyper@linkurl{\path{#1}}{../../../../#1}} + +% GUI menu/button/tab sequence: +\def\guiseq#1{\textsf{#1}} +\def\arw{\unskip$\rightarrow$\ignorespaces} +% +% Special names. +\def\dpi{$\,$dpi\xspace} +\def\bs{{\protect\normalfont\ttfamily\char'134}} +\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} +\def\Q#1{\par\vskip6pt\leftline{#1}\par} +\def\hyph{-} +% +% many abbreviations. +\newcommand{\CS}{$\mathcal{C}\kern-.1667em\lower.5ex% + \hbox{$\mathcal{S}$}\kern-.075em $} +\def\AFMtoTFM{\cmdname{AFM2TFM}\null} +\def\bv{\emph{Baskerville}} +\let\BV=\bv +\def\Dash{\unskip\nobreak\thinspace---\thinspace\ignorespaces} +\def\dvicopy{\cmdname{dvicopy}} +\def\dvidvi{\cmdname{dvidvi}} +\def\dvips{\cmdname{dvips}} +\def\eTeX{$\varepsilon$-\TeX} +\def\fpTeX{\textrm{fp}\TeX\xspace} +\def\GFtoDVI{\cmdname{GFtoDVI}\null} +\def\GFtoPK{\cmdname{GFtoPK}\null} +\def\GFtype{\cmdname{GFtype}} +\def\KPS{Kpathsea} +\def\La{La} +\def\OMEGA{$\Omega$} +\def\OzMF{OzMF} +\def\OzMP{OzMP} +\def\OzTeX{O\kern-.03em z\kern-.15em\TeX} +\def\p.{p.\,} +\def\PKtype{\cmdname{PKtype}} +\def\PLtoTF{\cmdname{PLtoTF}\null} +\def\ProTeXt{Pro\TeX t} +\def\teTeX{\textrm{te}\TeX\xspace} +\def\TeXLive{\TeX{} Live\xspace} +\def\TFtoPL{\cmdname{TFtoPL}\null} +\def\TK{\textsf{\TeX\ Collection}} +\let\TL=\TeXLive +\def\TypeI{Type~1} +\def\VFtoVP{\cmdname{VFtoVP}\null} +\def\VPtoVF{\cmdname{VPtoVF}\null} +\def\Thanh{H\`an~Th\^e\llap{\raise 0.5ex\hbox{\'{}}}~Th\`anh} +\def\XEmTeX{\textrm{XEm}\TeX\xspace} +\def\XEmacs{\textrm{XEmacs}\xspace} +\def\Webc{Web2C} +\providecommand*{\CD}{\acro{CD}\xspace} +\providecommand*{\CTAN}{\acro{CTAN}\xspace} +\providecommand*{\DVD}{\acro{DVD}\xspace} +\providecommand*{\HTML}{\acro{HTML}\xspace} +\providecommand*{\MacOSX}{Mac\,\acro{OS\,X}\xspace} +\providecommand*{\PS}{Post\-Script\xspace} +\providecommand*{\TDS}{\acro{TDS}\xspace} +\providecommand*{\dvi}{\acro{DVI}\xspace} +\providecommand*{\web}{\texttt{web}\xspace} + +% Include an image. +% #1 - name of image (pictures/#1.jpg, always .jpg please) +% #2 - bb for html +% #3 - width for TeX +% +\def\tlimage#1#2#3{% + \ifnum \Status=2 % html, want relative path in output + \includegraphics[#2]{../../general/texlive-common/pictures/#1.jpg} + \else % not html, handled by TEXINPUTS in Makefile + \includegraphics[width=#3]{pictures/#1.jpg} + \fi + \\[5mm] +} +% +% description-like environment that uses tt instead of bf, and doesn't +% go to the left margin. Without the \hfil, get an underfull box. +% Don't know why \descriptionlabel doesn't. +% +\newenvironment{ttdescription} + {\begin{list}{label must be supplied}{% + \itemsep=0pt % these lists tend to have short descriptions + \parindent=0pt + \let\makelabel=\ttdescriptionlabel}}% + {\end{list}} +\newcommand*\ttdescriptionlabel[1]{\hspace\labelsep + \normalfont\ttfamily #1\hfil} +% +% Likewise, for commands using sans serif. +\newenvironment{cmddescription} + {\begin{list}{label must be supplied}{% + \itemsep=0pt + \let\makelabel=\cmddescriptionlabel}}% + {\end{list}} +\newcommand*\cmddescriptionlabel[1]{\hspace\labelsep + \normalfont\sffamily #1\hfil} + +% General squeezed itemize. +\newenvironment{itemize*}% + {\begin{itemize}% + \setlength{\itemsep}{0pt}% + \setlength{\parskip}{0pt}}% + {\end{itemize}} + +\newsavebox{\wbox} +\newenvironment{warningbox} + {\begin{lrbox}{\wbox} + \begin{minipage}{.95\textwidth}} + {\end{minipage}\end{lrbox}\fbox{\usebox{\wbox}}} +% +% lrbox is used as a representation marking. I changed it to +% lrBox in tne source file, to get closer to logical marking +\newsavebox{\mylrbox} +\newenvironment{lrBox} + {\begin{lrbox}{\mylrbox}} + {\end{lrbox}} + + +% emacs-page output setup +% +\ifx \HCode\UnDef + \providecommand{\Status}{0}% running TeX +\else + \providecommand{\Status}{2}% running TeX4ht +\fi +%\typeout{Status is \Status} +% +\newif\ifSingleColumn +% +% By default, we won't be creating hyperlinks. +\def\href#1#2{#2} +\def\hypertarget#1#2{} +\def\email#1{\href{mailto:#1}{\path{#1}}} % \path comes from url +% +\definecolor{hypercolor}{rgb}{0.5,0.0,0.5} % purplish external links. +% +% +\ifcase\Status + % \Status = 0 + \typeout{TeX Live documentation in DVI format} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 1 + \typeout{TeX Live documentation in PDF format} + \RequirePackage[breaklinks, + colorlinks,linkcolor=hypercolor,citecolor=hypercolor, + pagecolor=hypercolor,urlcolor=hypercolor, + filecolor=hypercolor, + bookmarksopen, + %pdfstartview={FitBH -320000}, % fails with acrobat7 + hyperindex] + {hyperref} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 2 + \typeout{TeX Live documentation in HTML format} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + % read our config file, live4ht.cfg; q.v., for more definitions. + % hyperref load must come after the tex4ht load. + \RequirePackage[live4ht]{tex4ht} + \RequirePackage[tex4ht]{hyperref} \hyperlinkfileprefix{} + % definitions need simplifying for TeX4ht to make relative paths work. + \def\CDref#1#2{\href{../../../../#1}{#2}} + \def\OnCD#1{\href{../../../../#1}{#1}} + \or + % \Status = 3 + \typeout{TeX Live documentation as a Baskerville issue} + \@ifundefined{Fonts}% + {\RequirePackage{ae}}% + {\RequirePackage[T1]{\Fonts}} + \RequirePackage{bvoutln}% outline of baskerville + \SingleColumnfalse + \RequirePackage{multicol} + \or + % \Status = 4 + \typeout{TeX Live documentation as a TUB article} + \@ifundefined{Fonts}% + {\RequirePackage{ae}}% + {\RequirePackage[T1]{\Fonts}} + \SingleColumnfalse + \newenvironment{multicols}[1]{}{} +\fi +% +\ifnum \Status=4 +\else + \RequirePackage{texnames} + \providecommand\TeXXeT{\TeX-{}-% + \kern-.1emX\kern-.125em\lower.5ex\hbox{E}\kern-.1667emT\@} + \def\MP{MetaPost} + \let\mf\MF + \newcommand\ConTeXt{C\kern-.0333emon\-\kern-.0667em\TeX\kern-.0333emt} + \newcommand\MIKTEX{MiK\kern-.025em \TeX}% per www.miktex.org + % from pictex.tex: + \ifx\PiC\undefined \def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC} \fi + \ifx\PiCTeX\undefined \def\PiCTeX{\PiC\kern-.11em\TeX} \fi +\fi +% +% hacking at sections etc., to pay attention to baskerville status +\newcommand{\@condend@multicols}{% + \ifSingleColumn + \else + \def\@tempa{multicols}% + \ifx\@tempa\@currenvir + \end{multicols}% + \fi + \fi +} +\let\Section\section +\renewcommand{\section}{% + \@ifstar + {\Section*}% + {% + \@condend@multicols + \@dblarg\@full@section + }% +} +\def\@full@section[#1]#2{% + \Section[#1]{#2}% + \ifSingleColumn\else\begin{multicols}{2}\fi +} +\let\SubSection\subsection +\renewcommand{\subsection}{% + \@ifstar{\SubSection*}% + {% + \@condend@multicols + \@dblarg\@full@subsection + } +} +\def\@full@subsection[#1]#2{% + \SubSection[#1]{#2}% + \ifSingleColumn\else\begin{multicols}{2}\fi +} + +% calm things down a bit if we're in a multiple-column version +\ifSingleColumn +\else + \def\@listI{\leftmargin\leftmargini + \parsep \z@ + \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ + \itemsep \z@ \@plus .1\p@ + } + \let\@listi\@listI + \@listi + \def\@listii{\leftmargin\leftmarginii + \labelwidth\leftmarginii\advance\labelwidth-\labelsep + \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ + \parsep \z@ + \itemsep \z@ \@plus .1\p@ + } + \def\@listiii{\leftmargin\leftmarginiii + \labelwidth\leftmarginiii\advance\labelwidth-\labelsep + \topsep 1\p@ \@plus 1\p@ \@minus 1\p@ + \parsep \z@ + \partopsep \z@ + \itemsep \topsep + } + \def\@listiv{\leftmargin\leftmarginiv + \labelwidth\leftmarginiv\advance\labelwidth-\labelsep + } + \def\@listv{\leftmargin\leftmarginv + \labelwidth\leftmarginv\advance\labelwidth-\labelsep + } + \def\@listvi{\leftmargin\leftmarginvi + \labelwidth\leftmarginvi\advance\labelwidth-\labelsep + } +\fi +% +% array package stuff +\def\arraybackslash{\let\\=\@arraycr} +\newcolumntype{P}[1]{>{\raggedright\arraybackslash}p{#1}} +% +% shaded rows (using facilities of colortbl) +% +\definecolor{pale}{gray}{.9} +\newcount\colrow +\gdef\RowColor{pale} +\def\SetRowColor{% + \rowcolor{\RowColor}% + \global\advance\colrow by1\relax + \ifodd\colrow + \gdef\RowColor{pale}% + \else + \gdef\RowColor{white}% + \fi +} +% redefine to hack up a reference even though we don't need it... +\renewcommand\@bibitem[1]{\if@filesw \immediate\write\@auxout + {\string\bibcite{#1}{?}}\fi\ignorespaces} +% +% \unknownTeXlive is a dummy texlive entry for the biblio +\newcommand\unknownTeXlive[2][\relax]{\textbf{\textsc{unknown}}% + \global\@all@unknown\expandafter{\the\@all@unknown{#2}}% +} +\newtoks\@all@unknown +\global\@all@unknown{} +\AtEndDocument{\@message@unknowns} +\def\@message@unknowns{\edef\@tempa{\the\@all@unknown}% + \ifx\@tempa\@empty + \else + \def\@tempa{*** TeX live package location of }% + \expandafter\@output@unknowns\the\@all@unknown\@empty + \fi +} +\def\@output@unknowns#1{\edef\@tempb{#1}% + \ifx\@tempb\@empty + \typeout{ unknown}% + \else + \message{\@tempa#1,}% + \def\@tempa{}% + \expandafter\@output@unknowns + \fi +} + + +% Silence font warnings about no bold typewriter in LM. +\def\@font@warning#1{}% + +% Silence hyperref warnings about \kern. +\def\HyPsd@Warning#1{}% + +\endinput diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.sty-2008 b/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.sty-2008 new file mode 100644 index 00000000000..6bb5d7fb57b --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/tex-live.sty-2008 @@ -0,0 +1,444 @@ +% $Id: tex-live.sty 10332 2008-08-14 01:04:30Z karl $ +% TeX Live documentation style. Written by many people over many years. +% Public domain. +% +\NeedsTeXFormat{LaTeX2e}[1995/12/01] +\ProvidesPackage{tex-live}[2008/08/08 v1.6 TeX Live documentation style] +% +\RequirePackage{alltt} +\RequirePackage{array} +\RequirePackage{colortbl} +\RequirePackage{comment} +\RequirePackage{float} +\RequirePackage{graphicx} +\RequirePackage{longtable} +\RequirePackage{shortvrb} +\RequirePackage[normalem]{ulem} +\RequirePackage[obeyspaces]{url} +\RequirePackage{xspace} +% +\RequirePackage{lmodern} +\usepackage{textcomp}% including \textbullet +\def\p.{p.\,} + +% for a proper \acro command. +\RequirePackage{relsize} +%\DeclareRobustCommand{\acro}[1]{\textscale{.9}{#1}\@} +\def\acro#1{\textscale{.9}{#1}\@} +% +\RequirePackage{fancyvrb} +\DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=\normalsize} +\DefineVerbatimEnvironment{fverbatim}{Verbatim}{fontsize=\footnotesize} +\DefineVerbatimEnvironment{sverbatim}{Verbatim}{fontsize=\small} +\DefineVerbatimEnvironment{boxedverbatim} + {Verbatim}{fontsize=\scriptsize,frame=single} +\DefineVerbatimEnvironment{Verbatim}{Verbatim}{fontsize=\normalsize} +\def\verbatiminput#1{\VerbatimInput[fontsize=\scriptsize]{#1}} +\def\boxedverbatiminput#1{\VerbatimInput[frame=single,fontsize=\scriptsize]{#1}} +\def\listinginput#1#2{\VerbatimInput[fontsize=\scriptsize,firstnumber=#1,numbers=left]{#2}} +\MakeShortVerb\| +% +% +% Done with packages. +% +% Page layout. +\advance\textwidth by 1.1in +\advance\oddsidemargin by -.55in +\advance\evensidemargin by -.55in +% +\advance\textheight by 1in +\advance\topmargin by -.5in +\advance\footskip by -.5in +\pagestyle{headings} +% +% LaTeX parameters. +\renewcommand{\topfraction}{0.85} +\renewcommand{\floatpagefraction}{0.86} +\renewcommand{\textfraction}{0.1} +\renewcommand{\abovecaptionskip}{4pt} +\renewcommand{\belowcaptionskip}{4pt} +\setcounter{tocdepth}{3} +\setcounter{secnumdepth}{3} +\setcounter{topnumber}{5} +\setcounter{totalnumber}{5} +% +% linebreaking, etc. +\hbadness=4000 +\vbadness=4000 +\emergencystretch=.1\hsize +\relpenalty=500 +% +\def\slash{/\penalty\z@\hskip\z@skip } +% +% various sorts of names +\newcommand*{\pkgname}[1]{\textsf{#1}}% package name +\newcommand*{\optname}[1]{\texttt{#1}}% (package,class) option name +\newcommand*{\cmdname}[1]{\textsf{#1}}% command name +\newcommand*{\colname}[1]{\emph{#1}}% collection name +\newcommand*{\dirname}[1]{\path{#1}}% directory name +\newcommand*{\filename}[1]{\path{#1}}% file name +\newcommand*{\envname}[1]{\texttt{#1}}% environment variable name +\newcommand{\code}[1]{\texttt{#1}} +\newcommand{\file}[1]{\texttt{#1}} +\newcommand{\prog}[1]{\textsf{#1}}% same as \cmdname +\newcommand{\samp}[1]{`\texttt{#1}'} +\newcommand{\var}[1]{{\sl #1}}% not \textsl, for roman not typewriter slanted. +\newcommand{\ttvar}[1]{\texttt{\var{#1}}} +% +% underlined command input. +%\def\Ucom#1{% +% \uline{\rule[-.2\baselineskip]{0pt}{.9\baselineskip}\ttfamily #1}} +% bold command input +\def\Ucom#1{{\bfseries\ttfamily #1}} +% +% \CDref is for url's with a #, where we need to write the target url and +% displayed url separately in the input, due to catcode madness. +% (We could simplify/remove this next time, I think.) +\def\CDref#1#2{\texttt{#1}} +% +% \OnCD is currently for any other reference to a file or directory in +% the distribution. PDF readers only open .pdf files, though, so we +% should change this to only use \href for those. Or more likely use +% different macros in the source. +\def\OnCD#1{\href{../../../../#1}{\path{#1}}} +% +% \href incorrectly appends .pdf to anything without an extension; these +% definitions using \hyper@linkurl do not, but they fail for .pdf +% references -- which are the only ones that work anyway. So this is +% useless, in practice. +%\def\CDref#1#2{\hyper@linkurl{#2}{../../../../#1}} +%\def\OnCD#1{\hyper@linkurl{\path{#1}}{../../../../#1}} + +% GUI menu/button/tab sequence: +\def\guiseq#1{\textsf{#1}} +\def\arw{\unskip$\rightarrow$\ignorespaces} +% +% Special names. +\def\dpi{$\,$dpi\xspace} +\def\bs{{\protect\normalfont\ttfamily\char'134}} +\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} +\def\Q#1{\par\vskip6pt\leftline{#1}\par} +\def\hyph{-} +% +% many abbreviations. +\newcommand{\CS}{$\mathcal{C}\kern-.1667em\lower.5ex% + \hbox{$\mathcal{S}$}\kern-.075em $} +\def\AFMtoTFM{\cmdname{AFM2TFM}\null} +\def\bv{\emph{Baskerville}} +\let\BV=\bv +\def\Dash{\unskip\nobreak\thinspace---\thinspace\ignorespaces} +\def\dvicopy{\cmdname{dvicopy}} +\def\dvidvi{\cmdname{dvidvi}} +\def\dvips{\cmdname{dvips}} +\def\eTeX{$\varepsilon$-\TeX} +\def\fpTeX{\textrm{fp}\TeX\xspace} +\def\GFtoDVI{\cmdname{GFtoDVI}\null} +\def\GFtoPK{\cmdname{GFtoPK}\null} +\def\GFtype{\cmdname{GFtype}} +\def\GUI{\acro{GUI}\xspace} +\def\KPS{Kpathsea} +\def\La{La} +\def\OMEGA{$\Omega$} +\def\OzMF{OzMF} +\def\OzMP{OzMP} +\def\OzTeX{O\kern-.03em z\kern-.15em\TeX} +\def\PKtype{\cmdname{PKtype}} +\def\PLtoTF{\cmdname{PLtoTF}\null} +\def\ProTeXt{Pro\TeX t} +\def\teTeX{\textrm{te}\TeX\xspace} +\def\TeXLive{\TeX{} Live\xspace} +\def\TFtoPL{\cmdname{TFtoPL}\null} +\def\TK{\TeX\ Collection} +\let\TL=\TeXLive +\def\TypeI{Type~1} +\def\VFtoVP{\cmdname{VFtoVP}\null} +\def\VPtoVF{\cmdname{VPtoVF}\null} +\def\Thanh{H\`an~Th\ifx % get Unicode char in tex4ht's HTML output + \HCode\UnDef\^e\llap{\raise 0.5ex\hbox{\'{}}}\else + \HCode{\string&\#x1EBF;}\fi~Th\`anh} +\def\XEmTeX{\textrm{XEm}\TeX\xspace} +\def\XEmacs{\textrm{XEmacs}\xspace} +\def\XeTeX{Xe\TeX\xspace} +\def\Webc{Web2C} +\providecommand*{\CD}{\acro{CD}\xspace} +\providecommand*{\CTAN}{\acro{CTAN}\xspace} +\providecommand*{\DVD}{\acro{DVD}\xspace} +\providecommand*{\GNU}{\acro{GNU}\xspace} +\providecommand*{\HTML}{\acro{HTML}\xspace} +\providecommand*{\ISO}{\acro{ISO}\xspace} +\providecommand*{\MacOSX}{Mac\,\acro{OS\,X}\xspace} +\providecommand*{\PS}{Post\-Script\xspace} +\providecommand*{\TDS}{\acro{TDS}\xspace} +\providecommand*{\dvi}{\acro{DVI}\xspace} +\providecommand*{\web}{\texttt{WEB}\xspace} + +% Include an image. +% #1 - name of image (pictures/#1.jpg, always .jpg please) +% #2 - bb for html +% #3 - width for TeX +% +\def\tlimage#1#2#3{% + \ifnum \Status=2 % html, want relative path in output + \includegraphics[#2]{../../general/texlive-common/pictures/#1.jpg} + \else % not html, handled by TEXINPUTS in Makefile + \includegraphics[width=#3]{pictures/#1.jpg} + \fi + \\[5mm] +} + +\def\tlpng#1#2{% + \ifnum \Status=2 % html, want relative path in output + \includegraphics[bb=0 0 1 1]{#1.png}% + \else % not html, handled by TEXINPUTS in Makefile + \includegraphics[width=#2]{#1.png}% + \fi +} +% +% description-like environment that uses tt instead of bf, and doesn't +% go to the left margin. Without the \hfil, get an underfull box. +% Don't know why \descriptionlabel doesn't. +% +\newenvironment{ttdescription} + {\begin{list}{label must be supplied}{% + \itemsep=0pt % these lists tend to have short descriptions + \parindent=0pt + \let\makelabel=\ttdescriptionlabel}}% + {\end{list}} +\newcommand*\ttdescriptionlabel[1]{\hspace\labelsep + \normalfont\ttfamily #1\hfil} +% +% Likewise, for commands using sans serif. +\newenvironment{cmddescription} + {\begin{list}{label must be supplied}{% + \itemsep=0pt + \let\makelabel=\cmddescriptionlabel}}% + {\end{list}} +\newcommand*\cmddescriptionlabel[1]{\hspace\labelsep + \normalfont\sffamily #1\hfil} + +% General squeezed itemize. +\newenvironment{itemize*}% + {\begin{itemize}% + \setlength{\itemsep}{0pt}% + \setlength{\parskip}{0pt}}% + {\end{itemize}} + +\newsavebox{\wbox} +\newenvironment{warningbox} + {\begin{lrbox}{\wbox} + \begin{minipage}{.95\textwidth}} + {\end{minipage}\end{lrbox}\fbox{\usebox{\wbox}}} +% +% lrbox is used as a representation marking. I changed it to +% lrBox in tne source file, to get closer to logical marking +\newsavebox{\mylrbox} +\newenvironment{lrBox} + {\begin{lrbox}{\mylrbox}} + {\end{lrbox}} + + +% emacs-page output setup +% +\ifx \HCode\UnDef + \providecommand{\Status}{0}% running TeX +\else + \providecommand{\Status}{2}% running TeX4ht +\fi +%\typeout{Status is \Status} +% +\newif\ifSingleColumn +% +% By default, we won't be creating hyperlinks. +\def\href#1#2{#2} +\def\hypertarget#1#2{} +\def\email#1{\href{mailto:#1}{\path{#1}}} % \path comes from url +% +\definecolor{hypercolor}{rgb}{0.5,0.0,0.5} % purplish external links. +% +% +\ifcase\Status + % \Status = 0 + \typeout{TeX Live documentation in DVI format} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 1 + \typeout{TeX Live documentation in PDF format} + \RequirePackage[breaklinks, + colorlinks,linkcolor=hypercolor,citecolor=hypercolor, + urlcolor=hypercolor,filecolor=hypercolor, + bookmarksopen, + %pdfstartview={FitBH -320000}, % fails with acrobat7 + hyperindex] + {hyperref} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 2 + \typeout{TeX Live documentation in HTML format} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + % read our config file, live4ht.cfg; q.v., for more definitions. + % hyperref load must come after the tex4ht load. + \RequirePackage[live4ht]{tex4ht} + \RequirePackage[tex4ht]{hyperref} \hyperlinkfileprefix{} + % definitions need simplifying for TeX4ht to make relative paths work. + \def\CDref#1#2{\href{../../../../#1}{#2}} + \def\OnCD#1{\href{../../../../#1}{#1}} + \or + % \Status = 3 + \typeout{TeX Live documentation as a Baskerville issue} + \@ifundefined{Fonts}% + {\RequirePackage{ae}}% + {\RequirePackage[T1]{\Fonts}} + \RequirePackage{bvoutln}% outline of baskerville + \SingleColumnfalse + \RequirePackage{multicol} + \or + % \Status = 4 + \typeout{TeX Live documentation as a TUB article} + \@ifundefined{Fonts}% + {\RequirePackage{ae}}% + {\RequirePackage[T1]{\Fonts}} + \SingleColumnfalse + \newenvironment{multicols}[1]{}{} +\fi +% +\ifnum \Status=4 +\else + \RequirePackage{texnames} + \providecommand\TeXXeT{\TeX-{}-% + \kern-.1emX\kern-.125em\lower.5ex\hbox{E}\kern-.1667emT\@} + \def\MP{MetaPost} + \let\mf\MF + \newcommand\ConTeXt{C\kern-.0333emon\-\kern-.0667em\TeX\kern-.0333emt} + \newcommand\MIKTEX{MiK\kern-.025em \TeX}% per www.miktex.org + % from pictex.tex: + \ifx\PiC\undefined \def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC} \fi + \ifx\PiCTeX\undefined \def\PiCTeX{\PiC\kern-.11em\TeX} \fi +\fi +% +% hacking at sections etc., to pay attention to baskerville status +\newcommand{\@condend@multicols}{% + \ifSingleColumn + \else + \def\@tempa{multicols}% + \ifx\@tempa\@currenvir + \end{multicols}% + \fi + \fi +} +\let\Section\section +\renewcommand{\section}{% + \@ifstar + {\Section*}% + {% + \@condend@multicols + \@dblarg\@full@section + }% +} +\def\@full@section[#1]#2{% + \Section[#1]{#2}% + \ifSingleColumn\else\begin{multicols}{2}\fi +} +\let\SubSection\subsection +\renewcommand{\subsection}{% + \@ifstar{\SubSection*}% + {% + \@condend@multicols + \@dblarg\@full@subsection + } +} +\def\@full@subsection[#1]#2{% + \SubSection[#1]{#2}% + \ifSingleColumn\else\begin{multicols}{2}\fi +} + +% calm things down a bit if we're in a multiple-column version +\ifSingleColumn +\else + \def\@listI{\leftmargin\leftmargini + \parsep \z@ + \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ + \itemsep \z@ \@plus .1\p@ + } + \let\@listi\@listI + \@listi + \def\@listii{\leftmargin\leftmarginii + \labelwidth\leftmarginii\advance\labelwidth-\labelsep + \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ + \parsep \z@ + \itemsep \z@ \@plus .1\p@ + } + \def\@listiii{\leftmargin\leftmarginiii + \labelwidth\leftmarginiii\advance\labelwidth-\labelsep + \topsep 1\p@ \@plus 1\p@ \@minus 1\p@ + \parsep \z@ + \partopsep \z@ + \itemsep \topsep + } + \def\@listiv{\leftmargin\leftmarginiv + \labelwidth\leftmarginiv\advance\labelwidth-\labelsep + } + \def\@listv{\leftmargin\leftmarginv + \labelwidth\leftmarginv\advance\labelwidth-\labelsep + } + \def\@listvi{\leftmargin\leftmarginvi + \labelwidth\leftmarginvi\advance\labelwidth-\labelsep + } +\fi +% +% array package stuff +\def\arraybackslash{\let\\=\@arraycr} +\newcolumntype{P}[1]{>{\raggedright\arraybackslash}p{#1}} +% +% shaded rows (using facilities of colortbl) +% +\definecolor{pale}{gray}{.9} +\newcount\colrow +\gdef\RowColor{pale} +\def\SetRowColor{% + \rowcolor{\RowColor}% + \global\advance\colrow by1\relax + \ifodd\colrow + \gdef\RowColor{pale}% + \else + \gdef\RowColor{white}% + \fi +} +% redefine to hack up a reference even though we don't need it... +\renewcommand\@bibitem[1]{\if@filesw \immediate\write\@auxout + {\string\bibcite{#1}{?}}\fi\ignorespaces} +% +% \unknownTeXlive is a dummy texlive entry for the biblio +\newcommand\unknownTeXlive[2][\relax]{\textbf{\textsc{unknown}}% + \global\@all@unknown\expandafter{\the\@all@unknown{#2}}% +} +\newtoks\@all@unknown +\global\@all@unknown{} +\AtEndDocument{\@message@unknowns} +\def\@message@unknowns{\edef\@tempa{\the\@all@unknown}% + \ifx\@tempa\@empty + \else + \def\@tempa{*** TeX live package location of }% + \expandafter\@output@unknowns\the\@all@unknown\@empty + \fi +} +\def\@output@unknowns#1{\edef\@tempb{#1}% + \ifx\@tempb\@empty + \typeout{ unknown}% + \else + \message{\@tempa#1,}% + \def\@tempa{}% + \expandafter\@output@unknowns + \fi +} + + +% Silence font warnings about no bold typewriter in LM. +\def\@font@warning#1{}% + +% Silence hyperref warnings about \kern. +\def\HyPsd@Warning#1{}% + +\endinput diff --git a/Master/texmf/doc/texlive/source/texlive-en/archive/texlive.pl b/Master/texmf/doc/texlive/source/texlive-en/archive/texlive.pl new file mode 100644 index 00000000000..33a19a801d6 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/archive/texlive.pl @@ -0,0 +1,574 @@ +$texlive{"a0poster"}="latex3"; +$texlive{"aaai"}="latex3"; +$texlive{"abstyles"}="bibtex3"; +$texlive{"accfonts"}="fonts3"; +$texlive{"achemso"}="latex3"; +$texlive{"acronym"}="latex3"; +$texlive{"adfathesis"}="latex3"; +$texlive{"adobeother"}="fonts3"; +$texlive{"adobestd"}="fonts1"; +$texlive{"adrlist"}="latex3"; +$texlive{"ae"}="fonts2"; +$texlive{"aguplus"}="latex3"; +$texlive{"aiaa"}="latex3"; +$texlive{"akletter"}="latex3"; +$texlive{"alatex"}="formats3"; +$texlive{"alg"}="latex3"; +$texlive{"algorithms"}="latex3"; +$texlive{"alphaev5-osf4.0d"}="systems1"; +$texlive{"alphaev5-osf4.0d"}="systems2"; +$texlive{"alphaev5-osf4.0d"}="systems3"; +$texlive{"altfont"}="latex3"; +$texlive{"amsfonts"}="fonts2"; +$texlive{"amslatex"}="latex2"; +$texlive{"amstex"}="plain2"; +$texlive{"answers"}="latex3"; +$texlive{"antyktor"}="fonts3"; +$texlive{"apa"}="latex3"; +$texlive{"apl"}="fonts3"; +$texlive{"appendix"}="latex3"; +$texlive{"ar"}="fonts3"; +$texlive{"arabtex"}="lang3"; +$texlive{"arydshln"}="latex3"; +$texlive{"asaetr"}="latex3"; +$texlive{"ascii"}="fonts3"; +$texlive{"astro"}="fonts3"; +$texlive{"aurora"}="dvips3"; +$texlive{"authorindex"}="latex3"; +$texlive{"autotab"}="latex3"; +$texlive{"babel"}="generic2"; +$texlive{"backgammon"}="fonts3"; +$texlive{"bakoma"}="fonts2"; +$texlive{"barcode2"}="fonts3"; +$texlive{"barcodes"}="fonts3"; +$texlive{"barr"}="graphics3"; +$texlive{"bbding"}="fonts3"; +$texlive{"bbm"}="fonts3"; +$texlive{"bbold"}="fonts3"; +$texlive{"bbtbase"}="bibtex1"; +$texlive{"bbtdoc"}="bibtex2"; +$texlive{"beebe"}="bibtex2"; +$texlive{"belleek"}="fonts2"; +$texlive{"beton"}="latex3"; +$texlive{"bez123"}="latex3"; +$texlive{"bezos"}="latex3"; +$texlive{"bibarts"}="bibtex3"; +$texlive{"biblist"}="latex3"; +$texlive{"blue"}="formats3"; +$texlive{"bluesky"}="fonts1"; +$texlive{"booktabs"}="latex2"; +$texlive{"borceux"}="graphics3"; +$texlive{"bosisio"}="latex3"; +$texlive{"bridge"}="latex3"; +$texlive{"brushscr"}="fonts3"; +$texlive{"c-pascal"}="generic3"; +$texlive{"calendar"}="latex3"; +$texlive{"calligra"}="fonts3"; +$texlive{"calrsfs"}="latex3"; +$texlive{"camel"}="latex3"; +$texlive{"caption"}="latex2"; +$texlive{"carlisle"}="latex2"; +$texlive{"casyl"}="lang3"; +$texlive{"catalog"}="doc2"; +$texlive{"cbgreek"}="fonts3"; +$texlive{"cc-pl"}="fonts2"; +$texlive{"ccaption"}="latex3"; +$texlive{"ccfonts"}="latex3"; +$texlive{"cchess"}="fonts3"; +$texlive{"cdcover"}="latex3"; +$texlive{"cellular"}="plain3"; +$texlive{"changebar"}="latex2"; +$texlive{"chemcono"}="latex3"; +$texlive{"chemsym"}="latex3"; +$texlive{"cheq"}="fonts3"; +$texlive{"cherokee"}="fonts3"; +$texlive{"chess"}="fonts3"; +$texlive{"china2e"}="latex3"; +$texlive{"circ"}="graphics3"; +$texlive{"cirth"}="fonts3"; +$texlive{"cite"}="latex2"; +$texlive{"cjk"}="lang3"; +$texlive{"cm"}="fonts1"; +$texlive{"cmbright"}="fonts2"; +$texlive{"cmcyr"}="fonts3"; +$texlive{"cmcyralt"}="latex3"; +$texlive{"cmdtrack"}="latex2"; +$texlive{"cmextra"}="fonts2"; +$texlive{"cmpica"}="fonts3"; +$texlive{"cmpk"}="fonts3"; +$texlive{"cmsd"}="latex3"; +$texlive{"codepage"}="latex3"; +$texlive{"colorsep"}="dvips3"; +$texlive{"colortab"}="plain3"; +$texlive{"comment"}="latex3"; +$texlive{"concmath"}="fonts3"; +$texlive{"concrete"}="fonts3"; +$texlive{"context"}="formats2"; +$texlive{"covington"}="latex3"; +$texlive{"croatian"}="lang3"; +$texlive{"crop"}="latex3"; +$texlive{"crossword"}="latex3"; +$texlive{"crosswrd"}="latex3"; +$texlive{"csfonts"}="fonts2"; +$texlive{"cslatex"}="lang2"; +$texlive{"csplain"}="lang2"; +$texlive{"cspsfonts"}="fonts2"; +$texlive{"cstug"}="doc3"; +$texlive{"cursor"}="latex3"; +$texlive{"curves"}="graphics3"; +$texlive{"custom-bib"}="bibtex2"; +$texlive{"cyrillic"}="lang2"; +$texlive{"dancers"}="fonts3"; +$texlive{"deleq"}="latex3"; +$texlive{"devanagari"}="lang3"; +$texlive{"dialogl"}="latex3"; +$texlive{"dinbrief"}="latex3"; +$texlive{"directory"}="bibtex3"; +$texlive{"dotseqn"}="latex3"; +$texlive{"draftcopy"}="latex3"; +$texlive{"dratex"}="graphics3"; +$texlive{"dropping"}="latex3"; +$texlive{"dstroke"}="fonts3"; +$texlive{"dtk"}="latex3"; +$texlive{"duerer"}="fonts3"; +$texlive{"dvipdfm"}="doc2"; +$texlive{"dvipsbase"}="dvips1"; +$texlive{"dvipsdoc"}="dvips2"; +$texlive{"ean"}="generic3"; +$texlive{"easy"}="latex3"; +$texlive{"ec"}="fonts2"; +$texlive{"ecc"}="fonts3"; +$texlive{"ecltree"}="latex2"; +$texlive{"eco"}="fonts3"; +$texlive{"ecpk"}="fonts3"; +$texlive{"edmac"}="plain3"; +$texlive{"eepic"}="graphics2"; +$texlive{"egplot"}="latex3"; +$texlive{"eiad"}="fonts3"; +$texlive{"eijkhout"}="generic3"; +$texlive{"elsevier"}="latex3"; +$texlive{"elvish"}="fonts3"; +$texlive{"emp"}="latex3"; +$texlive{"emulateapj"}="latex3"; +$texlive{"encodings"}="omega2"; +$texlive{"endfloat"}="latex3"; +$texlive{"engwar"}="fonts3"; +$texlive{"envbig"}="latex3"; +$texlive{"envlab"}="latex3"; +$texlive{"epigraph"}="latex3"; +$texlive{"eplain"}="formats2"; +$texlive{"eqname"}="latex3"; +$texlive{"eqnarray"}="latex3"; +$texlive{"esieecv"}="latex3"; +$texlive{"etexbase"}="etex2"; +$texlive{"etruscan"}="fonts3"; +$texlive{"euler"}="latex3"; +$texlive{"euro"}="fonts2"; +$texlive{"euro2"}="latex3"; +$texlive{"eurofont"}="fonts2"; +$texlive{"europs"}="fonts2"; +$texlive{"eurosans"}="latex3"; +$texlive{"eurosym"}="fonts2"; +$texlive{"euxm"}="fonts3"; +$texlive{"exam"}="latex3"; +$texlive{"examdesign"}="latex3"; +$texlive{"expdlist"}="latex3"; +$texlive{"expl3"}="latex3"; +$texlive{"export"}="latex3"; +$texlive{"fancybox"}="latex2"; +$texlive{"fancyhdr"}="latex2"; +$texlive{"fancyref"}="latex2"; +$texlive{"fancyvrb"}="latex2"; +$texlive{"fax"}="latex3"; +$texlive{"fc"}="fonts3"; +$texlive{"feynmf"}="graphics3"; +$texlive{"finbib"}="bibtex3"; +$texlive{"float"}="latex2"; +$texlive{"floatfig"}="latex3"; +$texlive{"floatflt"}="latex3"; +$texlive{"fltpage"}="latex3"; +$texlive{"fncychap"}="latex3"; +$texlive{"foilhtml"}="latex3"; +$texlive{"foiltex"}="latex3"; +$texlive{"fontinst"}="generic2"; +$texlive{"fontname"}="doc2"; +$texlive{"footbib"}="latex3"; +$texlive{"footmisc"}="latex2"; +$texlive{"footnpag"}="latex3"; +$texlive{"formats"}="texlive2"; +$texlive{"formula"}="latex3"; +$texlive{"fp"}="latex3"; +$texlive{"frankenstein"}="latex3"; +$texlive{"french"}="lang2"; +$texlive{"fribrief"}="latex3"; +$texlive{"fullblck"}="latex3"; +$texlive{"fullpict"}="latex3"; +$texlive{"fundus"}="latex3"; +$texlive{"futhark"}="fonts3"; +$texlive{"g-brief"}="latex3"; +$texlive{"gb4e"}="latex3"; +$texlive{"genealogy"}="fonts3"; +$texlive{"general"}="doc1"; +$texlive{"genmisc"}="generic3"; +$texlive{"geometry"}="latex3"; +$texlive{"geomsty"}="latex3"; +$texlive{"german"}="lang2"; +$texlive{"germbib"}="bibtex2"; +$texlive{"germdoc"}="doc2"; +$texlive{"gloss"}="latex3"; +$texlive{"gn-logic"}="latex3"; +$texlive{"go"}="fonts3"; +$texlive{"gothic"}="fonts3"; +$texlive{"graphics"}="latex1"; +$texlive{"greek6cbc"}="fonts3"; +$texlive{"grnumalt"}="latex3"; +$texlive{"grtimes"}="lang3"; +$texlive{"guides"}="doc2"; +$texlive{"gustlib"}="plain2"; +$texlive{"hands"}="fonts3"; +$texlive{"hanging"}="latex3"; +$texlive{"harpoon"}="latex3"; +$texlive{"harvard"}="bibtex2"; +$texlive{"harvmac"}="plain3"; +$texlive{"hh"}="latex3"; +$texlive{"hilowres"}="latex3"; +$texlive{"histogr"}="latex3"; +$texlive{"hoekwater"}="fonts2"; +$texlive{"hppa1.1-hpux10.10"}="systems1"; +$texlive{"hppa1.1-hpux10.10"}="systems2"; +$texlive{"hppa1.1-hpux10.10"}="systems3"; +$texlive{"html"}="doc2"; +$texlive{"hvmaths"}="fonts3"; +$texlive{"hyper"}="latex3"; +$texlive{"hyperref"}="latex2"; +$texlive{"hyphen"}="lang1"; +$texlive{"hyphenat"}="latex3"; +$texlive{"i386-linux"}="systems1"; +$texlive{"i386-linux"}="systems2"; +$texlive{"i386-linux"}="systems3"; +$texlive{"i386-linux-libc5"}="systems1"; +$texlive{"i386-linux-libc5"}="systems2"; +$texlive{"i386-linux-libc5"}="systems3"; +$texlive{"ibm"}="fonts3"; +$texlive{"ieeepes"}="latex3"; +$texlive{"ifacmtg"}="latex3"; +$texlive{"imac"}="latex3"; +$texlive{"indxcite"}="latex3"; +$texlive{"info"}="doc2"; +$texlive{"ini"}="texlive1"; +$texlive{"insbox"}="generic3"; +$texlive{"ipa"}="latex3"; +$texlive{"isostds"}="latex3"; +$texlive{"jadetex"}="formats2"; +$texlive{"jhep"}="latex3"; +$texlive{"jknappen"}="latex2"; +$texlive{"jsmisc"}="plain3"; +$texlive{"jura"}="latex3"; +$texlive{"kalender"}="latex3"; +$texlive{"karnaugh"}="latex3"; +$texlive{"kdgreek"}="fonts3"; +$texlive{"kluwer"}="latex3"; +$texlive{"knuth"}="doc3"; +$texlive{"koma-script"}="latex3"; +$texlive{"kuvio"}="graphics3"; +$texlive{"labels"}="latex3"; +$texlive{"lamstex"}="formats3"; +$texlive{"lastpage"}="latex3"; +$texlive{"latexfonts"}="latex1"; +$texlive{"layouts"}="latex3"; +$texlive{"leaflet"}="latex3"; +$texlive{"leftidx"}="latex3"; +$texlive{"lettrine"}="latex3"; +$texlive{"levy"}="latex3"; +$texlive{"lgc"}="doc3"; +$texlive{"lgreek"}="latex3"; +$texlive{"lh"}="fonts2"; +$texlive{"lhcyr"}="latex3"; +$texlive{"lineno"}="latex3"; +$texlive{"linguex"}="latex3"; +$texlive{"listings"}="latex3"; +$texlive{"lkort"}="doc3"; +$texlive{"localloc"}="latex3"; +$texlive{"logic"}="fonts3"; +$texlive{"lollipop"}="formats3"; +$texlive{"ltablex"}="latex3"; +$texlive{"ltx2rtf"}="texlive2"; +$texlive{"ltxbase"}="latex1"; +$texlive{"ltxdoc"}="doc2"; +$texlive{"ltxdoc"}="latex1"; +$texlive{"ltxmisc"}="latex2"; +$texlive{"lucida"}="fonts2"; +$texlive{"ly1"}="latex3"; +$texlive{"mailing"}="latex3"; +$texlive{"makeindex"}="doc1"; +$texlive{"malayalam"}="lang3"; +$texlive{"malvern"}="fonts3"; +$texlive{"mapcodes"}="latex3"; +$texlive{"maple"}="latex3"; +$texlive{"margbib"}="latex3"; +$texlive{"marvosym"}="fonts3"; +$texlive{"mathcomp"}="latex2"; +$texlive{"mathematica"}="fonts3"; +$texlive{"mathpple"}="fonts3"; +$texlive{"mcite"}="latex3"; +$texlive{"mdwtools"}="latex3"; +$texlive{"metasupp"}="texlive1"; +$texlive{"method"}="latex3"; +$texlive{"mex"}="lang2"; +$texlive{"mff"}="latex3"; +$texlive{"mflogo"}="latex2"; +$texlive{"mfmisc"}="fonts1"; +$texlive{"mfnfss"}="latex2"; +$texlive{"mfpic"}="graphics3"; +$texlive{"mft"}="texlive1"; +$texlive{"mftoeps"}="fonts3"; +$texlive{"mhs"}="latex3"; +$texlive{"midnight"}="generic3"; +$texlive{"minitoc"}="latex3"; +$texlive{"mips-irix6.2"}="systems1"; +$texlive{"mips-irix6.2"}="systems2"; +$texlive{"mips-irix6.2"}="systems3"; +$texlive{"misc209"}="latex2"; +$texlive{"mltex"}="latex2"; +$texlive{"mnras"}="plain3"; +$texlive{"monotype"}="fonts3"; +$texlive{"montex"}="lang3"; +$texlive{"morehelp"}="latex3"; +$texlive{"moresize"}="latex3"; +$texlive{"moreverb"}="latex3"; +$texlive{"morse"}="fonts3"; +$texlive{"mpattern"}="metapost2"; +$texlive{"mpbase"}="metapost1"; +$texlive{"mpfnmark"}="latex3"; +$texlive{"ms"}="latex3"; +$texlive{"mslapa"}="latex3"; +$texlive{"mtbe"}="plain3"; +$texlive{"multenum"}="latex3"; +$texlive{"multi"}="dvips3"; +$texlive{"multirow"}="latex3"; +$texlive{"musictex"}="generic3"; +$texlive{"musixtex"}="generic3"; +$texlive{"nassflow"}="latex3"; +$texlive{"natbib"}="bibtex2"; +$texlive{"ncctools"}="latex2"; +$texlive{"newalg"}="latex3"; +$texlive{"newlfm"}="latex3"; +$texlive{"newsletr"}="plain3"; +$texlive{"newthm"}="latex3"; +$texlive{"niceframe"}="latex3"; +$texlive{"nomencl"}="latex3"; +$texlive{"nrc"}="latex3"; +$texlive{"ntg"}="doc3"; +$texlive{"ntgclass"}="latex2"; +$texlive{"ntheorem"}="latex3"; +$texlive{"numline"}="latex3"; +$texlive{"objectz"}="latex3"; +$texlive{"oca"}="fonts3"; +$texlive{"ocr-a"}="fonts3"; +$texlive{"ogham"}="fonts3"; +$texlive{"ogonek"}="latex3"; +$texlive{"oldstyle"}="latex3"; +$texlive{"omegabase"}="omega2"; +$texlive{"omegafonts"}="omega2"; +$texlive{"osmanian"}="fonts3"; +$texlive{"ot2cyr"}="fonts2"; +$texlive{"overpic"}="latex3"; +$texlive{"pacioli"}="fonts3"; +$texlive{"pageno"}="latex3"; +$texlive{"pandora"}="fonts3"; +$texlive{"paper"}="latex3"; +$texlive{"paralist"}="latex3"; +$texlive{"parallel"}="latex3"; +$texlive{"patch"}="latex2"; +$texlive{"pawpict"}="latex3"; +$texlive{"pb-diagram"}="latex3"; +$texlive{"pdcmac"}="plain3"; +$texlive{"pdfscreen"}="latex3"; +$texlive{"pdftex"}="pdftex2"; +$texlive{"permute"}="latex3"; +$texlive{"phoenician"}="fonts3"; +$texlive{"phonetic"}="fonts3"; +$texlive{"physe"}="formats3"; +$texlive{"phyzzx"}="formats3"; +$texlive{"picinpar"}="latex3"; +$texlive{"picins"}="latex3"; +$texlive{"pictex"}="graphics2"; +$texlive{"piff"}="latex3"; +$texlive{"pl"}="latex3"; +$texlive{"pl-qx"}="fonts2"; +$texlive{"plainmisc"}="plain1"; +$texlive{"plaintex"}="plain1"; +$texlive{"plari"}="latex3"; +$texlive{"platex"}="lang2"; +$texlive{"play"}="latex3"; +$texlive{"plcalendar"}="plain3"; +$texlive{"plfonts"}="fonts2"; +$texlive{"plgraph"}="generic3"; +$texlive{"plpatch"}="plain3"; +$texlive{"pmgraph"}="latex3"; +$texlive{"poligraf"}="generic3"; +$texlive{"polish"}="doc3"; +$texlive{"polyglot"}="latex3"; +$texlive{"prettyref"}="latex3"; +$texlive{"progkeys"}="latex3"; +$texlive{"program"}="latex3"; +$texlive{"proofs"}="latex3"; +$texlive{"protex"}="generic3"; +$texlive{"psafm"}="fonts3"; +$texlive{"psfig"}="generic3"; +$texlive{"psfrag"}="graphics2"; +$texlive{"psizzl"}="formats3"; +$texlive{"pslatex"}="latex2"; +$texlive{"psnfss"}="latex1"; +$texlive{"psnfssx"}="latex2"; +$texlive{"pspicture"}="latex2"; +$texlive{"pstricks"}="graphics2"; +$texlive{"punk"}="fonts3"; +$texlive{"qfonts"}="fonts2"; +$texlive{"qobitree"}="graphics3"; +$texlive{"qsymbols"}="latex3"; +$texlive{"quotchap"}="latex3"; +$texlive{"r-und-s"}="latex3"; +$texlive{"rcs"}="latex3"; +$texlive{"rcsinfo"}="latex3"; +$texlive{"realcalc"}="generic3"; +$texlive{"refcheck"}="latex3"; +$texlive{"refman"}="latex3"; +$texlive{"relenc"}="latex3"; +$texlive{"revtex"}="latex2"; +$texlive{"rlepsf"}="generic3"; +$texlive{"rmpage"}="latex3"; +$texlive{"rotating"}="latex2"; +$texlive{"rotfloat"}="latex3"; +$texlive{"rplain"}="latex3"; +$texlive{"rs6000-aix4.1.4.0"}="systems1"; +$texlive{"rs6000-aix4.1.4.0"}="systems2"; +$texlive{"rs6000-aix4.1.4.0"}="systems3"; +$texlive{"rsfs"}="fonts2"; +$texlive{"ruhyphen"}="lang1"; +$texlive{"runic"}="fonts3"; +$texlive{"sanskrit"}="fonts3"; +$texlive{"sauterfonts"}="latex3"; +$texlive{"scale"}="latex3"; +$texlive{"schedule"}="latex3"; +$texlive{"script"}="latex3"; +$texlive{"sectsty"}="latex3"; +$texlive{"semantic"}="latex3"; +$texlive{"seminar"}="latex2"; +$texlive{"setspace"}="latex3"; +$texlive{"shadbox"}="latex3"; +$texlive{"shadethm"}="latex3"; +$texlive{"shortlst"}="latex3"; +$texlive{"shorttoc"}="latex3"; +$texlive{"showdim"}="latex3"; +$texlive{"showlabels"}="latex3"; +$texlive{"siam"}="generic3"; +$texlive{"sidecap"}="latex3"; +$texlive{"siggraph"}="latex3"; +$texlive{"simpsons"}="fonts3"; +$texlive{"siunits"}="latex3"; +$texlive{"slashbox"}="latex3"; +$texlive{"slidenotes"}="latex3"; +$texlive{"smallcap"}="latex3"; +$texlive{"songbook"}="latex3"; +$texlive{"soul"}="latex3"; +$texlive{"sparc-solaris2.5.1"}="systems1"; +$texlive{"sparc-solaris2.5.1"}="systems2"; +$texlive{"sparc-solaris2.5.1"}="systems3"; +$texlive{"sprite"}="graphics3"; +$texlive{"ssqquote"}="latex3"; +$texlive{"startex"}="formats3"; +$texlive{"stdclsdv"}="latex3"; +$texlive{"stmaryrd"}="fonts2"; +$texlive{"subeqn"}="latex3"; +$texlive{"subeqnarray"}="latex3"; +$texlive{"subfigure"}="latex3"; +$texlive{"supertabular"}="latex3"; +$texlive{"synttree"}="latex3"; +$texlive{"t2"}="lang3"; +$texlive{"tabbing"}="latex3"; +$texlive{"tap"}="generic2"; +$texlive{"taylor"}="graphics3"; +$texlive{"tbe"}="plain3"; +$texlive{"tcx"}="texlive1"; +$texlive{"tds"}="doc1"; +$texlive{"tengwar"}="fonts3"; +$texlive{"tetex"}="doc1"; +$texlive{"tex-ps"}="generic2"; +$texlive{"tex4ht"}="latex2"; +$texlive{"texdraw"}="graphics3"; +$texlive{"texinfo"}="plain2"; +$texlive{"texip"}="formats3"; +$texlive{"texlive"}="texlive1"; +$texlive{"texsis"}="formats3"; +$texlive{"text1"}="formats3"; +$texlive{"textfit"}="latex3"; +$texlive{"textmerg"}="latex3"; +$texlive{"textpos"}="latex3"; +$texlive{"thesis"}="latex3"; +$texlive{"threed"}="metapost2"; +$texlive{"thumb"}="latex3"; +$texlive{"thumbpdf"}="latex3"; +$texlive{"timesht"}="latex3"; +$texlive{"timing"}="latex3"; +$texlive{"tipa"}="fonts2"; +$texlive{"titlefoot"}="latex3"; +$texlive{"titlesec"}="latex3"; +$texlive{"tmmaths"}="fonts3"; +$texlive{"tocbibind"}="latex3"; +$texlive{"tocloft"}="latex3"; +$texlive{"tocvsec2"}="latex3"; +$texlive{"tools"}="latex1"; +$texlive{"tracking"}="latex3"; +$texlive{"treesvr"}="latex3"; +$texlive{"treetex"}="plain3"; +$texlive{"ttf2pk"}="texlive2"; +$texlive{"tug"}="doc3"; +$texlive{"tugboat"}="generic2"; +$texlive{"type1"}="fonts2"; +$texlive{"type1cm"}="latex3"; +$texlive{"typespec"}="plain3"; +$texlive{"uaclasses"}="latex3"; +$texlive{"ucthesis"}="latex3"; +$texlive{"ulsy"}="latex3"; +$texlive{"umlaute"}="latex3"; +$texlive{"umrand"}="fonts3"; +$texlive{"underlin"}="latex3"; +$texlive{"uni"}="fonts3"; +$texlive{"units"}="latex3"; +$texlive{"universa"}="fonts3"; +$texlive{"unsupported"}="fonts3"; +$texlive{"urwstd"}="fonts2"; +$texlive{"useful"}="doc2"; +$texlive{"ut-thesis"}="latex3"; +$texlive{"utthesis"}="latex3"; +$texlive{"uwthesis"}="latex3"; +$texlive{"vdm"}="latex3"; +$texlive{"vector"}="latex3"; +$texlive{"vertex"}="plain3"; +$texlive{"vita"}="latex3"; +$texlive{"vrb"}="latex3"; +$texlive{"vrsion"}="latex3"; +$texlive{"warpcol"}="latex3"; +$texlive{"wasy"}="fonts2"; +$texlive{"wasysym"}="latex2"; +$texlive{"williams"}="latex3"; +$texlive{"win32"}="systems1"; +$texlive{"win32"}="systems2"; +$texlive{"win32"}="systems3"; +$texlive{"windvi"}="doc1"; +$texlive{"wnri"}="fonts3"; +$texlive{"wntamil"}="lang3"; +$texlive{"wsuipa"}="fonts2"; +$texlive{"xtab"}="latex3"; +$texlive{"xtcapts"}="latex3"; +$texlive{"xymtex"}="latex3"; +$texlive{"xypic"}="graphics2"; +$texlive{"yannisgr"}="fonts3"; +$texlive{"yfonts"}="latex3"; +$texlive{"yhmath"}="latex3"; +$texlive{"yi4latex"}="lang3"; +$texlive{"youngtab"}="latex3"; +$texlive{"ytex"}="formats3"; +$texlive{"zed-csp"}="latex3"; +$texlive{"zefonts"}="fonts2"; diff --git a/Master/texmf/doc/texlive/source/texlive-en/live4ht.cfg b/Master/texmf/doc/texlive/source/texlive-en/live4ht.cfg new file mode 100644 index 00000000000..3435925813d --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/live4ht.cfg @@ -0,0 +1,51 @@ +% tex4ht configuration file for the TeX Live documentation. +% Accumulated over many years. Public domain. +% +% html specifies the main output format. +% info for extra debugging info in the log files. + +% have html in one piece (including footnotes). +\Preamble{charset=iso-8859-1,html,info,fn-in} + +% add extra stylesheet +\Configure{@HEAD}{\HCode{% +\Hnewline +\Hnewline +}} +% use png graphics as-is +\Configure{graphics*} + {png} + {\Needs{""}% + \Picture[pict]{\csname Gin@base\endcsname.png}% + } +% or LaTeX complains it is missing. +\begin{document} + +\EndPreamble + +% simplify output for HTML. We leave TeX and LaTeX alone, since tex4ht +% actually does the lowered E (and raised A) in CSS. +\def\OMEGA{Omega} +\def\LaTeXe{LaTeX2e} +\def\eTeX{e-\TeX} +\def\acro#1{#1} +\def\MF{Metafont} +\def\BibTeX{BibTeX} +\def\warningbox{} +\def\endwarningbox{} + +\newif\ifhackliterals +\ifx\tldocenglish\undefined \else \hackliteralstrue \fi +\ifx\tldocrussian\undefined \else \hackliteralstrue \fi +\ifx\tldocgerman\undefined \else \hackliteralstrue \fi +% +\ifhackliterals + % these definitions cause "missing } inserted" at \end{tabularx} in + % French and Czech. don't know why. + % + % don't make these into links, as happens with \path. We only have a couple + % special characters that actually occur. + \def\dirname{\texttt\bgroup\catcode`\$=12 \catcode`\_=12 \finishliteral} + \def\finishliteral#1{#1\egroup} + \let\filename=\dirname +\fi diff --git a/Master/texmf/doc/texlive/source/texlive-en/tex-live.css b/Master/texmf/doc/texlive/source/texlive-en/tex-live.css new file mode 100644 index 00000000000..5062bc0d229 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/tex-live.css @@ -0,0 +1,44 @@ +/* $Id$ + Simple CSS for TeX Live that adds margins and a little color. + original by Bzyl Wlodzimierz, edited by Karl Berry, 2005. + Public domain. */ + +html { + // top left bottom right + margin: 15pt 15pt 15pt 15pt; + background: rgb(255,255,224); +} + +body { + margin: 0 5pt 0 5pt; + padding: 0; + //matw: background: rgb(224,255,224); + // (It looks better to me to have a consistent background --karl) +// fonts in browser are low resolution; +// therefore generated serif are poor quality, +// so they disturb reading (that is my opinion) + font-family: sans-serif; + font-style: normal; +} + +/* (It looks better to me to not vary colors at every level --karl) */ + +h3.sectionHead { + padding: 12pt 10pt 12pt 20pt; + //matw: background: rgb(192,224,255); + background: rgb(224,224,255); + color: rgb(0,0,32); +} + +h4.subsectionHead { + padding: 7pt 10pt 7pt 40pt; + background: rgb(224,224,255); + color: rgb(0,0,32); +} + +h5.subsubsectionHead { + padding: 3pt 10pt 3pt 40pt; + //matw: background: rgb(224,255,255); + background: rgb(224,224,255); + color: rgb(0,0,32); +} diff --git a/Master/texmf/doc/texlive/source/texlive-en/tex-live.sty b/Master/texmf/doc/texlive/source/texlive-en/tex-live.sty new file mode 100644 index 00000000000..09956bd2a3e --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/tex-live.sty @@ -0,0 +1,446 @@ +% $Id$ +% TeX Live documentation style. Written by many people over many years. +% Public domain. +% +\NeedsTeXFormat{LaTeX2e}[1995/12/01] +\ProvidesPackage{tex-live}[2008/08/08 v1.6 TeX Live documentation style] +% +\RequirePackage{alltt} +\RequirePackage{array} +\RequirePackage{colortbl} +\RequirePackage{comment} +\RequirePackage{float} +\RequirePackage{graphicx} +\RequirePackage{longtable} +\RequirePackage{shortvrb} +\RequirePackage[normalem]{ulem} +\RequirePackage[obeyspaces]{url} +\RequirePackage{xspace} +% +\RequirePackage{lmodern} +\usepackage{textcomp}% including \textbullet +\def\p.{p.\,} + +% for a proper \acro command. +\RequirePackage{relsize} +%\DeclareRobustCommand{\acro}[1]{\textscale{.9}{#1}\@} +\def\acro#1{\textscale{.9}{#1}\@} +% +\RequirePackage{fancyvrb} +\DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=\normalsize} +\DefineVerbatimEnvironment{fverbatim}{Verbatim}{fontsize=\footnotesize} +\DefineVerbatimEnvironment{sverbatim}{Verbatim}{fontsize=\small} +\DefineVerbatimEnvironment{boxedverbatim} + {Verbatim}{fontsize=\scriptsize,frame=single} +\DefineVerbatimEnvironment{Verbatim}{Verbatim}{fontsize=\normalsize} +\def\verbatiminput#1{\VerbatimInput[fontsize=\scriptsize]{#1}} +\def\boxedverbatiminput#1{\VerbatimInput[frame=single,fontsize=\scriptsize]{#1}} +\def\listinginput#1#2{\VerbatimInput[fontsize=\scriptsize,firstnumber=#1,numbers=left]{#2}} +\MakeShortVerb\| +% +% +% Done with packages. +% +% Page layout. +\advance\textwidth by 1.1in +\advance\oddsidemargin by -.55in +\advance\evensidemargin by -.55in +% +\advance\textheight by 1in +\advance\topmargin by -.5in +\advance\footskip by -.5in +\pagestyle{headings} +% +% LaTeX parameters. +\renewcommand{\topfraction}{0.85} +\renewcommand{\floatpagefraction}{0.86} +\renewcommand{\textfraction}{0.1} +\renewcommand{\abovecaptionskip}{4pt} +\renewcommand{\belowcaptionskip}{4pt} +\setcounter{tocdepth}{3} +\setcounter{secnumdepth}{3} +\setcounter{topnumber}{5} +\setcounter{totalnumber}{5} +% +% linebreaking, etc. +\hbadness=4000 +\vbadness=4000 +\emergencystretch=.1\hsize +\relpenalty=500 +% +\def\slash{/\penalty\z@\hskip\z@skip } +% +% various sorts of names +\newcommand*{\pkgname}[1]{\textsf{#1}}% package name +\newcommand*{\optname}[1]{\texttt{#1}}% (package,class) option name +\newcommand*{\cmdname}[1]{\textsf{#1}}% command name +\newcommand*{\colname}[1]{\emph{#1}}% collection name +\newcommand*{\dirname}[1]{\path{#1}}% directory name +\newcommand*{\filename}[1]{\path{#1}}% file name +\newcommand*{\envname}[1]{\texttt{#1}}% environment variable name +\newcommand{\code}[1]{\texttt{#1}} +\newcommand{\file}[1]{\texttt{#1}} +\newcommand{\prog}[1]{\textsf{#1}}% same as \cmdname +\newcommand{\samp}[1]{`\texttt{#1}'} +\newcommand{\var}[1]{{\sl #1}}% not \textsl, for roman not typewriter slanted. +\newcommand{\ttvar}[1]{\texttt{\var{#1}}} +% +% underlined command input. +%\def\Ucom#1{% +% \uline{\rule[-.2\baselineskip]{0pt}{.9\baselineskip}\ttfamily #1}} +% bold command input +\def\Ucom#1{{\bfseries\ttfamily #1}} +% +% \CDref is for url's with a #, where we need to write the target url and +% displayed url separately in the input, due to catcode madness. +% (We could simplify/remove this next time, I think.) +\def\CDref#1#2{\texttt{#1}} +% +% \OnCD is currently for any other reference to a file or directory in +% the distribution. PDF readers only open .pdf files, though, so we +% should change this to only use \href for those. Or more likely use +% different macros in the source. +\def\OnCD#1{\href{../../../../#1}{\path{#1}}} +% +% \href incorrectly appends .pdf to anything without an extension; these +% definitions using \hyper@linkurl do not, but they fail for .pdf +% references -- which are the only ones that work anyway. So this is +% useless, in practice. +%\def\CDref#1#2{\hyper@linkurl{#2}{../../../../#1}} +%\def\OnCD#1{\hyper@linkurl{\path{#1}}{../../../../#1}} + +% GUI menu/button/tab sequence: +\def\guiseq#1{\textsf{#1}} +\def\arw{\unskip$\rightarrow$\ignorespaces} +% +% Special names. +\def\dpi{$\,$dpi\xspace} +\def\bs{{\protect\normalfont\ttfamily\char'134}} +\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} +\def\Q#1{\par\vskip6pt\leftline{#1}\par} +\def\hyph{-} +% +% many abbreviations. +\newcommand{\CS}{$\mathcal{C}\kern-.1667em\lower.5ex% + \hbox{$\mathcal{S}$}\kern-.075em $} +\def\AFMtoTFM{\cmdname{AFM2TFM}\null} +\def\bv{\emph{Baskerville}} +\let\BV=\bv +\def\Dash{\unskip\nobreak\thinspace---\thinspace\ignorespaces} +\def\dvicopy{\cmdname{dvicopy}} +\def\dvidvi{\cmdname{dvidvi}} +\def\dvips{\cmdname{dvips}} +\def\eTeX{$\varepsilon$-\TeX} +\def\fpTeX{\textrm{fp}\TeX\xspace} +\def\GFtoDVI{\cmdname{GFtoDVI}\null} +\def\GFtoPK{\cmdname{GFtoPK}\null} +\def\GFtype{\cmdname{GFtype}} +\def\GUI{\acro{GUI}\xspace} +\def\KPS{Kpathsea} +\def\La{La} +\def\OMEGA{$\Omega$} +\def\OzMF{OzMF} +\def\OzMP{OzMP} +\def\OzTeX{O\kern-.03em z\kern-.15em\TeX} +\def\PKtype{\cmdname{PKtype}} +\def\PLtoTF{\cmdname{PLtoTF}\null} +\def\ProTeXt{Pro\TeX t} +\def\teTeX{\textrm{te}\TeX\xspace} +\def\TeXLive{\TeX{} Live\xspace} +\def\TFtoPL{\cmdname{TFtoPL}\null} +\def\TK{\TeX\ Collection} +\let\TL=\TeXLive +\def\TypeI{Type~1} +\def\VFtoVP{\cmdname{VFtoVP}\null} +\def\VPtoVF{\cmdname{VPtoVF}\null} +\def\Thanh{H\`an~Th\ifx % get Unicode char in tex4ht's HTML output + \HCode\UnDef\^e\llap{\raise 0.5ex\hbox{\'{}}}\else + \HCode{\string&\#x1EBF;}\fi~Th\`anh} +\def\XEmTeX{\textrm{XEm}\TeX\xspace} +\def\XEmacs{\textrm{XEmacs}\xspace} +\def\XeTeX{Xe\TeX\xspace} +\def\Webc{Web2C} +\providecommand*{\CD}{\acro{CD}\xspace} +\providecommand*{\CTAN}{\acro{CTAN}\xspace} +\providecommand*{\DVD}{\acro{DVD}\xspace} +\providecommand*{\GNU}{\acro{GNU}\xspace} +\providecommand*{\HTML}{\acro{HTML}\xspace} +\providecommand*{\ISO}{\acro{ISO}\xspace} +\providecommand*{\MacOSX}{Mac\,\acro{OS\,X}\xspace} +\providecommand*{\PS}{Post\-Script\xspace} +\providecommand*{\TDS}{\acro{TDS}\xspace} +\providecommand*{\dvi}{\acro{DVI}\xspace} +\providecommand*{\web}{\texttt{WEB}\xspace} + +% Include an image. +% #1 - name of image (pictures/#1.jpg, always .jpg please) +% #2 - bb for html +% #3 - width for TeX +% +\def\tlimage#1#2#3{% + \ifnum \Status=2 % html, want relative path in output + \includegraphics[#2]{../../general/texlive-common/pictures/#1.jpg} + \else % not html, handled by TEXINPUTS in Makefile + \includegraphics[width=#3]{pictures/#1.jpg} + \fi + \\[5mm] +} + +\def\tlpng#1#2{% + \ifnum \Status=2 % html, want relative path in output + \includegraphics[bb=0 0 1 1]{#1.png}% + \else % not html, handled by TEXINPUTS in Makefile + \includegraphics[width=#2]{#1.png}% + \fi +} +% +% description-like environment that uses tt instead of bf, and doesn't +% go to the left margin. Without the \hfil, get an underfull box. +% Don't know why \descriptionlabel doesn't. +% +\newenvironment{ttdescription} + {\begin{list}{label must be supplied}{% + \itemsep=0pt % these lists tend to have short descriptions + \parindent=0pt + \let\makelabel=\ttdescriptionlabel}}% + {\end{list}} +\newcommand*\ttdescriptionlabel[1]{\hspace\labelsep + \normalfont\ttfamily #1\hfil} +% +% Likewise, for commands using sans serif. +\newenvironment{cmddescription} + {\begin{list}{label must be supplied}{% + \itemsep=0pt + \let\makelabel=\cmddescriptionlabel}}% + {\end{list}} +\newcommand*\cmddescriptionlabel[1]{\hspace\labelsep + \normalfont\sffamily #1\hfil} + +% General squeezed itemize. +\newenvironment{itemize*}% + {\begin{itemize}% + \setlength{\itemsep}{0pt}% + \setlength{\parskip}{0pt}}% + {\end{itemize}} + +\newsavebox{\wbox} +\newenvironment{warningbox} + {\begin{lrbox}{\wbox} + \begin{minipage}{.95\textwidth}} + {\end{minipage}\end{lrbox}\fbox{\usebox{\wbox}}} +% +% lrbox is used as a representation marking. I changed it to +% lrBox in tne source file, to get closer to logical marking +\newsavebox{\mylrbox} +\newenvironment{lrBox} + {\begin{lrbox}{\mylrbox}} + {\end{lrbox}} + + +% emacs-page output setup +% +\ifx \HCode\UnDef + \providecommand{\Status}{0}% running TeX +\else + \providecommand{\Status}{2}% running TeX4ht +\fi +%\typeout{Status is \Status} +% +\newif\ifSingleColumn +% +% By default, we won't be creating hyperlinks. +\def\href#1#2{#2} +\def\hypertarget#1#2{} +\def\email#1{\href{mailto:#1}{\path{#1}}} % \path comes from url +\def\htmlanchor#1{} +% +\definecolor{hypercolor}{rgb}{0.5,0.0,0.5} % purplish external links. +% +% +\ifcase\Status + % \Status = 0 + \typeout{TeX Live documentation in DVI format} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 1 + \typeout{TeX Live documentation in PDF format} + \RequirePackage[breaklinks, + colorlinks,linkcolor=hypercolor,citecolor=hypercolor, + urlcolor=hypercolor,filecolor=hypercolor, + bookmarksopen, + %pdfstartview={FitBH -320000}, % fails with acrobat7 + hyperindex] + {hyperref} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 2 + \typeout{TeX Live documentation in HTML format} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + % read our config file, live4ht.cfg; q.v., for more definitions. + % hyperref load must come after the tex4ht load. + \RequirePackage[live4ht]{tex4ht} + \RequirePackage[tex4ht]{hyperref} \hyperlinkfileprefix{} + % definitions need simplifying for TeX4ht to make relative paths work. + \def\CDref#1#2{\href{../../../../#1}{#2}} + \def\OnCD#1{\href{../../../../#1}{#1}} + \def\htmlanchor#1{\HCode{} + \or + % \Status = 3 + \typeout{TeX Live documentation as a Baskerville issue} + \@ifundefined{Fonts}% + {\RequirePackage{ae}}% + {\RequirePackage[T1]{\Fonts}} + \RequirePackage{bvoutln}% outline of baskerville + \SingleColumnfalse + \RequirePackage{multicol} + \or + % \Status = 4 + \typeout{TeX Live documentation as a TUB article} + \@ifundefined{Fonts}% + {\RequirePackage{ae}}% + {\RequirePackage[T1]{\Fonts}} + \SingleColumnfalse + \newenvironment{multicols}[1]{}{} +\fi +% +\ifnum \Status=4 +\else + \RequirePackage{texnames} + \providecommand\TeXXeT{\TeX-{}-% + \kern-.1emX\kern-.125em\lower.5ex\hbox{E}\kern-.1667emT\@} + \def\MP{MetaPost} + \let\mf\MF + \newcommand\ConTeXt{C\kern-.0333emon\-\kern-.0667em\TeX\kern-.0333emt} + \newcommand\MIKTEX{MiK\kern-.025em \TeX}% per www.miktex.org + % from pictex.tex: + \ifx\PiC\undefined \def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC} \fi + \ifx\PiCTeX\undefined \def\PiCTeX{\PiC\kern-.11em\TeX} \fi +\fi +% +% hacking at sections etc., to pay attention to baskerville status +\newcommand{\@condend@multicols}{% + \ifSingleColumn + \else + \def\@tempa{multicols}% + \ifx\@tempa\@currenvir + \end{multicols}% + \fi + \fi +} +\let\Section\section +\renewcommand{\section}{% + \@ifstar + {\Section*}% + {% + \@condend@multicols + \@dblarg\@full@section + }% +} +\def\@full@section[#1]#2{% + \Section[#1]{#2}% + \ifSingleColumn\else\begin{multicols}{2}\fi +} +\let\SubSection\subsection +\renewcommand{\subsection}{% + \@ifstar{\SubSection*}% + {% + \@condend@multicols + \@dblarg\@full@subsection + } +} +\def\@full@subsection[#1]#2{% + \SubSection[#1]{#2}% + \ifSingleColumn\else\begin{multicols}{2}\fi +} + +% calm things down a bit if we're in a multiple-column version +\ifSingleColumn +\else + \def\@listI{\leftmargin\leftmargini + \parsep \z@ + \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ + \itemsep \z@ \@plus .1\p@ + } + \let\@listi\@listI + \@listi + \def\@listii{\leftmargin\leftmarginii + \labelwidth\leftmarginii\advance\labelwidth-\labelsep + \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ + \parsep \z@ + \itemsep \z@ \@plus .1\p@ + } + \def\@listiii{\leftmargin\leftmarginiii + \labelwidth\leftmarginiii\advance\labelwidth-\labelsep + \topsep 1\p@ \@plus 1\p@ \@minus 1\p@ + \parsep \z@ + \partopsep \z@ + \itemsep \topsep + } + \def\@listiv{\leftmargin\leftmarginiv + \labelwidth\leftmarginiv\advance\labelwidth-\labelsep + } + \def\@listv{\leftmargin\leftmarginv + \labelwidth\leftmarginv\advance\labelwidth-\labelsep + } + \def\@listvi{\leftmargin\leftmarginvi + \labelwidth\leftmarginvi\advance\labelwidth-\labelsep + } +\fi +% +% array package stuff +\def\arraybackslash{\let\\=\@arraycr} +\newcolumntype{P}[1]{>{\raggedright\arraybackslash}p{#1}} +% +% shaded rows (using facilities of colortbl) +% +\definecolor{pale}{gray}{.9} +\newcount\colrow +\gdef\RowColor{pale} +\def\SetRowColor{% + \rowcolor{\RowColor}% + \global\advance\colrow by1\relax + \ifodd\colrow + \gdef\RowColor{pale}% + \else + \gdef\RowColor{white}% + \fi +} +% redefine to hack up a reference even though we don't need it... +\renewcommand\@bibitem[1]{\if@filesw \immediate\write\@auxout + {\string\bibcite{#1}{?}}\fi\ignorespaces} +% +% \unknownTeXlive is a dummy texlive entry for the biblio +\newcommand\unknownTeXlive[2][\relax]{\textbf{\textsc{unknown}}% + \global\@all@unknown\expandafter{\the\@all@unknown{#2}}% +} +\newtoks\@all@unknown +\global\@all@unknown{} +\AtEndDocument{\@message@unknowns} +\def\@message@unknowns{\edef\@tempa{\the\@all@unknown}% + \ifx\@tempa\@empty + \else + \def\@tempa{*** TeX live package location of }% + \expandafter\@output@unknowns\the\@all@unknown\@empty + \fi +} +\def\@output@unknowns#1{\edef\@tempb{#1}% + \ifx\@tempb\@empty + \typeout{ unknown}% + \else + \message{\@tempa#1,}% + \def\@tempa{}% + \expandafter\@output@unknowns + \fi +} + + +% Silence font warnings about no bold typewriter in LM. +\def\@font@warning#1{}% + +% Silence hyperref warnings about \kern. +\def\HyPsd@Warning#1{}% + +\endinput diff --git a/Master/texmf/doc/texlive/source/texlive-en/texlive-en.tex b/Master/texmf/doc/texlive/source/texlive-en/texlive-en.tex new file mode 100644 index 00000000000..24fbb5d1c1b --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-en/texlive-en.tex @@ -0,0 +1,2954 @@ +% $Id: live.tex 9531 2008-07-13 21:12:58Z siepo $ +% TeX Live documentation. Originally written by Sebastian Rahtz and +% Michel Goossens, now maintained by Karl Berry and others. +% Public domain. +% +\documentclass{article} +\let\tldocenglish=1 % for live4ht.cfg +\usepackage{tex-live} +\usepackage[latin1]{inputenc} % translators: use your preferred encodings. +\usepackage[T1]{fontenc} + +\begin{document} + +\title{% + {\huge \textit{The \TeX\ Live Guide}\\\smallskip}% + {\LARGE \textsf{\TL{} 2008}}% +} + +\author{Karl Berry, editor \\[3mm] + \url{http://tug.org/texlive/} + } + +\date{September 2008} + +\maketitle + +\begin{multicols}{2} +\tableofcontents +%\listoftables +\end{multicols} + +\section{Introduction} +\label{sec:intro} + +\subsection{\TeX\ Live and the \TeX\ Collection} + +This document describes the main features of the \TL{} software +distribution\Dash \TeX{} and related programs for \GNU/Linux +and other Unix flavors, \MacOSX, and Windows systems. + +You may have acquired \TL{} by downloading, or on the \TK{} \DVD, +which \TeX{} usergroups distribute among their members. Section +\ref{sec:tl-coll-dists} briefly describes the contents of this \DVD. +Both \TL{} and the \TK{} are cooperative efforts by the \TeX{} user +groups. This document mainly describes \TL{} itself. + +\TL{} includes executables for \TeX{}, \LaTeXe{}, \ConTeXt, +\MF, \MP, \BibTeX{} and many other programs; an extensive collection +of macros, fonts and documentation; and support for typesetting in +many different scripts from around the world. + +\TL{} packages are regularly updated from +\acro{CTAN}: \url{http://www.ctan.org}. + +For a brief summary of the major changes in this edition of \TL{}, +see the end of the document, section~\ref{sec:history} +(\p.\pageref{sec:history}). + +\subsection{Operating system support} +\label{sec:os-support} + +\TL{} contains binaries for many Unix-based architectures, +including \MacOSX. The included sources should enable installation +on platforms for which we do not have binaries. + +As to Windows: only Windows 2000 and later are supported. Windows +9\textit{x}, ME and NT have been dropped. Because of this +change, Windows requires much less special treatment compared to +the Unix systems. There are no 64-bit executables for Windows, but the +32-bit executables should run on 64-bit systems. + +See section~\ref{sec:tl-coll-dists} for alternate solutions +for Windows and \MacOSX. + +\subsection{Basic installation of \protect\TL{}} +\label{sec:basic} + +You can install \TL{} either from \DVD{} or over the Internet. The net +installer itself is small, and downloads everything requested from the +Internet. The net installer is an attractive option if you need only a +fraction of the complete \TL. + +The \DVD{} installer lets you install to a local disk, but you can +also run \TL{} directly from the \DVD{} (or from a \DVD{} image, if +your system supports that). + +\noindent This is described in the +installation sections following, but here is a quick start: + +\begin{itemize*} + +\item The installation script is named \filename{install-tl}. It can + operate in both a \GUI{} mode (default for Windows) and + a text mode (default for everything else). You can force one mode or + the other with the options \code{-gui} and \code{-no-gui}, respectively. + +\item One of the installed items is a new program, the `\TL\ Manager', + named \prog{tlmgr}. Like the installer, it can be used in both \GUI{} + mode and in text mode. You can use it to install and uninstall + packages and do various configuration tasks. + +\end{itemize*} + + +\subsection{Getting help} +\label{sec:help} + +The \TeX{} community is both active and friendly, and most serious +questions end up getting answered. However, the support is informal, +done by volunteers and casual readers, so it's especially important that +you do your homework before asking. (If you prefer guaranteed +commercial support, you can forego \TL{} completely and purchase a +vendor's system; \url{http://tug.org/interest.html#vendors} has a list.) + +Here is a list of resources, approximately in the order we recommend +using them: + +\begin{description} +\item [Getting Started] If you are new to \TeX, the web page +\url{http://tug.org/begin.html} gives a brief introduction to the system. + +\item [\TeX{} \acro{FAQ}] The \TeX{} \acro{FAQ} is a huge compendium + of answers to all sorts of questions, from the most basic to the + most arcane. It is included on \TL{} in + \OnCD{texmf-doc/doc/english/FAQ-en/html/index.html}, and is available + on the Internet through \url{http://www.tex.ac.uk/faq}. Please + check here first. + +\item [\TeX{} Catalogue] If you are looking for a specific package, +font, program, etc., the \TeX{} Catalogue is the place to look. It is a +huge collection of all \TeX{}-related items. See +\url{http://www.ctan.org/help/Catalogue/}. + +\item [\TeX{} Web Resources] The web page +\url{http://tug.org/interest.html} has many \TeX{}-related links, in +particular for numerous books, manuals, and articles on all aspects of +the system. + +\item [support archives] The two principal support forums are the +Usenet newsgroup \url{news:comp.text.tex} and the mailing list +\email{texhax@tug.org}. Their archives have years of past +questions and answers for your searching pleasure, via +\url{http://groups.google.com/group/comp.text.tex/topics} and +\url{http://tug.org/mail-archives/texhax}, respectively. And a general web +search, for example on \url{http://google.com}, never hurts. + +\item [asking questions] If you cannot find an answer, you can post to +\dirname{comp.text.tex} through Google or your newsreader, or to +\email{texhax@tug.org} through email. But before you post, +\emph{please} read this \acro{FAQ} entry, to maximize +your chances of getting a useful answer: +\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. + +\item [\TL{} support] If you want to report a bug or have +suggestions or comments on the \TL{} distribution, installation, or +documentation, the mailing list is \email{tex-live@tug.org}. However, +if your question is about how to use a particular program included in +\TL{}, please write to that program's maintainer or +mailing list. Often running a program with the \code{-{}-help} option +will provide a bug reporting address. + +\end{description} + +The other side of the coin is helping others who have questions. Both +\dirname{comp.text.tex} and \code{texhax} are open to anyone, so feel +free to join, start reading, and help out where you can. + + +% don't use \TL so the \uppercase in the headline works. Also so +% tex4ht ends up with the right TeX. Likewise the \protect's. +\section{Overview of \protect\TeX\protect\ Live} +\label{sec:overview-tl} + +This section describes the contents of \TL{} and the \TK{} of which it +is a part. + +\subsection{The \protect\TeX\protect\ Collection: \TL, pro\TeX{}t, Mac\TeX} +\label{sec:tl-coll-dists} + +The \TK{} \DVD{} comprises the following: + +\begin{description} + +\item [\TL] A complete \TeX{} system which can be run live or + installed to disk. + +\item [Mac\TeX] for \MacOSX, this adds a native \MacOSX\ installer and other +Mac applications to \TL{}. Its home page is +\url{http://www.tug.org/mactex/}. + +\item [pro\TeX{}t] An enhancement of the \MIKTEX\ distribution for Windows, +\ProTeXt\ adds a few extra tools to \MIKTEX, and simplifies +installation. It is entirely independent of \TL{}, and has its own +installation instructions. The \ProTeXt\ home page is +\url{http://tug.org/protext}. + +\item [CTAN] A snapshot of the \CTAN{} repository. + +\item [\texttt{texmf-extra}] A directory with assorted additional packages. + +\end{description} + +\CTAN{}, \pkgname{protext}, and \dirname{texmf-extra} do not +necessarily follow the same copying conditions as \TL{}, so be careful +when redistributing or modifying. + + +\subsection{Top level \TL{} directories} +\label{sec:tld} + +Here is a brief listing and description of the top level directories in +the \TL{} distribution. On the \pkgname{live} \DVD, the entire \TL{} +hierarchy is in a subdirectory \dirname{texlive}, not at the top +level of the disc. + +\begin{ttdescription} +\item[bin] The \TeX{} system programs, arranged by platform. +% +\item[readme.html] Web pages with a quick introduction and useful links, +in various languages. +% +\item[source] The source to all included programs, including the main \Webc{} + \TeX{} and \MF{} distributions. +% +\item[support] Various auxiliary packages and programs. These are + \emph{not} installed automatically. This includes + assorted editors and \TeX\ shells. +% +\item[texmf] See \dirname{TEXMFMAIN} below. +% +\item[texmf-dist] See \dirname{TEXMFDIST} below. +% +\item[texmf-doc] Tree for self-contained pure documentation, arranged by + language. +% +\item[tlpkg] Scripts, programs and data for managing the + installation. It also contains private copies of + Perl and Ghostscript for Windows, which are invisible outside \TL, + and a new Windows PostScript viewer PSView. +\end{ttdescription} + +In addition to the directories above, the installation scripts and +\filename{README} files (in various languages) are at the top level of +the distribution. + +The \dirname{texmf-doc} directory contains documentation which does +not belong to any particular package or program. The documentation +for the programs (manuals, man pages, Info files) is in +\dirname{texmf/doc}. The documentation for \TeX\ packages and +formats is in \dirname{texmf-dist/doc}. You can use the +\cmdname{texdoc} or \cmdname{texdoctk} programs to find any +documentation wherever it is located. The comprehensive links in +the top-level file \OnCD{doc.html} may also be helpful. + +This \TL\ documentation itself is in \dirname{texmf-doc} and is +available in several languages: + +\begin{itemize*} +\item{Simplified Chinese:} \OnCD{texmf-doc/doc/chinese/texlive-zh-cn} +\item{Czech/Slovak:} \OnCD{texmf-doc/doc/czechslovak/texlive-cz} +\item{English:} \OnCD{texmf-doc/doc/english/texlive-en} +\item{French:} \OnCD{texmf-doc/doc/french/texlive-fr} +\item{German:} \OnCD{texmf-doc/doc/german/texlive-de} +\item{Polish:} \OnCD{texmf-doc/doc/polish/texlive-pl} +\item{Russian:} \OnCD{texmf-doc/doc/russian/texlive-ru} +\end{itemize*} + +\subsection{Overview of the predefined texmf trees} +\label{sec:texmftrees} + +This section lists all predefined variables specifying the texmf trees +used by the system, and their intended purpose, and the default +layout of a \TL{} system. The command \texttt{texconfig conf} shows +you the values of these variables, so that you can easily find out +how they map to directory names in your installation. + +\begin{ttdescription} +\item [TEXMFMAIN] The tree which holds vital parts of the system + such as helper scripts (e.g., \verb+web2c/mktexdir+) and other + support files and their documentation. Does not include + \TeX\ formats and packages. +\item [TEXMFDIST] The tree which holds the main set of macro packages, + fonts, etc., as originally distributed. +\item [TEXMFLOCAL] The tree which administrators can use for system-wide + installation of additional or updated macros, fonts, etc. +\item [TEXMFHOME] The tree which users can use for their own individual + installations of additional or updated macros, fonts, etc. + The expansion of this variable dynamically adjusts for each user to + their own individual directory. +\item [TEXMFCONFIG] The tree used by the utilities + \verb+texconfig+, \verb+updmap+, and \verb+fmtutil+ to store modified + configuration data. Under \envname{TEXMFHOME} by default. +\item [TEXMFSYSCONFIG] The tree used by the utilities + \verb+texconfig-sys+, \verb+updmap-sys+, and \verb+fmtutil-sys+ to + store modified configuration data. +\item [TEXMFVAR] The tree used by \verb+texconfig+, \verb+updmap+ and + \verb+fmtutil+ to store (cached) runtime data such as format files and + generated map files. Under \envname{TEXMFHOME} by default. +\item [TEXMFSYSVAR] The tree used by \verb+texconfig-sys+, + \verb+updmap-sys+ and \verb+fmtutil-sys+, and also by \verb+tlmgr+, to + store (cached) runtime data such as format files and generated map files. +\end{ttdescription} + +\noindent +The default layout is: +\begin{description} + \item[system-wide root] can span multiple \TL{} releases: + \begin{ttdescription} + \item[2007] A previous release. + \begin{ttdescription} + \item [...] + \end{ttdescription} + \item[2008] The current release. + \begin{ttdescription} + \item [bin] ~ + \begin{ttdescription} + \item [i386-linux] \GNU/Linux binaries + \item [...] + \item [universal-darwin] \MacOSX binaries + \item [win32] Windows binaries + \end{ttdescription} + \item [texmf] This is \envname{TEXMFMAIN}. + \item [texmf-dist] \envname{TEXMFDIST} + \item [texmf-doc] \envname{TEXMFDOC} + \item [texmf-var] \envname{TEXMFSYSVAR} + \item [texmf-config] \envname{TEXMFSYSCONFIG} + \end{ttdescription} + \item [texmf-local] \envname{TEXMFLOCAL}, intended to be + retained from release to release. + \end{ttdescription} + \item[user's home] (\texttt{\$HOME} or + \texttt{\%USERPROFILE\%}) + \begin{ttdescription} + \item[.texlive2007] Privately generated and configuration data + for a previous release. + \item[.texlive2008] Privately generated and configuration data + for the current release. + \begin{ttdescription} + \item [texmf-var] \envname{TEXMFVAR} + \item [texmf-config] \envname{TEXMFCONFIG} + \end{ttdescription} + \item[texmf] \envname{TEXMFHOME} Personal macros. + \textit{etc.} + \end{ttdescription} +\end{description} + + +\subsection{Extensions to \protect\TeX} +\label{sec:tex-extensions} + +\TeX{} itself is frozen, apart from rare bug fixes. It is still present +in \TL\ as the program \prog{tex}, and will remain so in the +foreseeable future. \TL{} contains several extended versions of \TeX: + +\begin{description} + +\item [\eTeX] adds a set of new primitives +\label{text:etex} (related to macro expansion, character scanning, +classes of marks, additional debugging features, and more) and the +\TeXXeT{} extensions for bidirectional typesetting. In default mode, +\eTeX{} is 100\% compatible with ordinary \TeX. See +\OnCD{texmf-dist/doc/etex/base/etex_man.pdf}. + +\item [pdf\TeX] builds on the \eTeX\ extensions, adding support for +writing \acro{PDF} output as well as \dvi{}. This is the program +invoked for most formats, e.g., \prog{etex}, \prog{latex}, +\prog{pdflatex}. See \url{http://www.pdftex.org/}. +\OnCD{texmf-dist/doc/pdftex/manual/pdftex-a.pdf} for the manual, and +\OnCD{texmf-dist/doc/pdftex/manual/samplepdf/samplepdf.tex} for example usage +of some of its features. + +\item [Lua\TeX] is the designated successor of pdf\TeX, with which it +is intended to be backward-compatible. It should also supersede Aleph, +see below. The incorporated Lua interpreter (see +\url{http://www.lua.org/}) enables elegant solutions for many thorny +\TeX{} problems. When called as \filename{texlua}, it functions as a +standalone Lua interpreter, and is already used as such within \TL. See +\url{http://www.luatex.org/} and +\OnCD{texmf-dist/doc/luatex/luatexref-t.pdf}. + +\item [\XeTeX] adds support for Unicode input and OpenType- and system +fonts, implemented using standard third-party libraries. See +\url{http://scripts.sil.org/xetex}. + +\item [\OMEGA\ (Omega)] is based on Unicode (16-bit characters), thus +supports working with almost all the world's scripts simultaneously. It +also supports so-called `\OMEGA{} Translation Processes' (\acro{OTP}s), +for performing complex transformations on arbitrary input. See +\OnCD{texmf-dist/doc/omega/base/doc-1.8.tex} (not completely up-to-date). + +\item [Aleph] combines the \OMEGA\ and \eTeX\ extensions. +See \OnCD{texmf-dist/doc/aleph/base} for some minimal documentation. + +\end{description} + + +\subsection{Other notable programs in \protect\TL} + +Here are a few other commonly-used programs included in \TL{}: + +\begin{cmddescription} + +\item [bibtex] bibliography support. + +\item [makeindex] index support. + +\item [dvips] convert \dvi{} to \PS{}. + +\item [xdvi] \dvi{} previewer for the X Window System. + +\item [dvilj] \dvi{} drive for the HP LaserJet family. + +\item [dv2dt, dt2dv] convert \dvi{} to/from plain text. + +\item [dviconcat, dviselect] cut and paste pages +from \dvi{} files. + +\item [dvipdfmx] convert \dvi{} to \acro{PDF}, an alternative approach +to pdf\TeX\ (mentioned above). See the \pkgname{ps4pdf} and +\pkgname{pdftricks} packages for still more alternatives. + +\item [psselect, psnup, \ldots] \PS{} +utilities. + +\item [lacheck] \LaTeX{} syntax checker. + +\item [texexec, texmfstart] Con\TeX{}t and \acro{PDF} processor. + +\item [tex4ht] \TeX{} to \acro{HTML} (and \acro{XML} and more) converter. + +\end{cmddescription} + + +\subsection{Fonts in \protect\TL} +\label{sec:tl-fonts} + +\TL{} comes with many high-quality scalable fonts. See +\url{http://tug.org/fonts} and +\OnCD{texmf-doc/doc/english/free-math-font-survey}. + + + +\section{Installation} +\label{sec:install} + +\subsection{Starting the installer} +\label{sec:inst-start} + +To start with, get the \TK{} \DVD{} or download the \TL{} net installer, +and locate the installer script: \filename{install-tl} for Unix, +\filename{install-tl.bat} for Windows. + +\begin{description} +\item [Net installer:] Download from \CTAN, under +\dirname{systems/texlive/tlnet}; the url +\url{http://mirror.ctan.org/systems/texlive/tlnet} will automatically +redirect to a nearby, up-to-date, mirror. You can retrieve either +\filename{install-tl.zip} which can be used under Unix and Windows and +\filename{install-unx.tar.gz} which is considerably smaller, for Unix +only. After unpacking, \filename{install-tl} and +\filename{install-tl.bat} will be in the \dirname{install-tl} +subdirectory. + +\item [\TeX{} Collection \DVD:] go to its \dirname{texlive} +subdirectory. Under Windows, the installer should start automatically +when you insert the \DVD. You can get the \DVD\ by becoming a member of +a \TeX\ user group (highly recommended, +\url{http://tug.org/usergroups.html}), or purchasing it separately +(\url{http://tug.org/store}), or burning your own from the \ISO\ +image (\url{http://tug.org/texlive/acquire.html}). + +\end{description} +The following sections explain in more detail. + +\subsubsection{Unix} + +\begin{figure}[tb] +\begin{boxedverbatim} +======================> TeX Live installation procedure <===================== + +=======> Note: Letters/digits in indicate menu items <======= +=======> for commands or configurable options <======= + + + Detected platform: Intel x86 with GNU/Linux + + binary systems: 1 out of 16 + + Installation scheme (scheme-full) + + Customizing installation scheme: + standard collections + language collections + 83 collections out of 84, disk space required: 1666 MB + + directories: + TEXDIR (the main TeX directory): + !! default location: /usr/local/texlive/2008 + !! is not writable, please select a different one! + TEXMFLOCAL (directory for site-wide local files): + /usr/local/texlive/texmf-local + TEXMFSYSVAR (directory for variable and automatically generated data): + /usr/local/texlive/2008/texmf-var + TEXMFSYSCONFIG (directory for local config): + /usr/local/texlive/2008/texmf-config + TEXMFHOME (directory for user-specific files): + ~/texmf + + options: + [ ] use letter size instead of A4 by default + [X] create all format files + [X] install macro/font doc tree + [X] install macro/font source tree + [ ] create symlinks in standard directories + + Install for running from DVD + +Other actions: + start installation to HD + help + quit + +Enter command: +\end{boxedverbatim} +\caption{Main text installer screen (\GNU/Linux)}\label{fig:text-main} +\end{figure} + +\begin{figure}[tb] +\tlpng{install-w32-main}{\linewidth} +\caption{Main \GUI{} installer screen (Windows)}\label{fig:gui-main} +\end{figure} + +\noindent +Below, \texttt{>} denotes the shell prompt; user input is +\Ucom{\texttt{bold}}. +Starting in a terminal window on a Unix-compatible system, the simplest +way: +\begin{alltt} +> \Ucom{cd /path/to/installer} +> \Ucom{perl install-tl} +\end{alltt} +(Or you can invoke \Ucom{perl /path/to/installer/install-tl}, or +\Ucom{./install-tl} if it stayed executable, etc.; we won't repeat all +these variations.) + +To install in \GUI\ mode (you'll need the \dirname{Perl/TK} module), use: +\begin{alltt} +> \Ucom{perl install-tl -gui} +\end{alltt} + +For a complete listing of the various options: +\begin{alltt} +> \Ucom{perl install-tl -help} +\end{alltt} + +\textbf{Warning about Unix permissions:} Your \code{umask} at the time +of installation will be respected by the \TL{} installer. Therefore, if +you want your installation to be usable by users other than you, make +sure your setting is sufficiently permissive, for instance, \code{umask +002}. For more information about \code{umask}, consult your system +documentation. + + +\subsubsection{Mac\,OS\,X} + +As mentioned in section~\ref{sec:tl-coll-dists}, a separate distribution +is prepared for \MacOSX, named Mac\TeX\ (\url{http://tug.org/mactex}). +We recommend using the native Mac\TeX\ installer instead of the \TL\ +installer on \MacOSX, because the native installer can make a few +Mac-specific adjustments, in particular to allow easily switching +between the various \TeX\ distributions for \MacOSX\ (Mac\TeX, gw\TeX, +Fink, MacPorts, \ldots). + +Mac\TeX\ is firmly based on \TL, and the main \TeX\ trees are precisely +the same. It does add a few extra folders with Mac-specific +documentation and applications. + + +\subsubsection{Windows} + +If you are using the net installer, or the \DVD\ installer failed to +start automatically, double-click \filename{install-tl.bat}. + +You can also start the installer from the command-prompt. Below, +\texttt{>} denotes the prompt; user input is \Ucom{\texttt{bold}}. If +you are in the installer directory, run just: +\begin{alltt} +> \Ucom{install-tl} +\end{alltt} + +Or you can invoke it with an absolute location, such as: +\begin{alltt} +> \Ucom{D:\bs{}texlive\bs{}install-tl} +\end{alltt} +for the \TK\ \DVD, supposing that \dirname{D:} is the optical drive. + +To install in text mode, use: +\begin{alltt} +> \Ucom{install-tl -no-gui} +\end{alltt} + +For a complete listing of the various options: +\begin{alltt} +> \Ucom{install-tl -help} +\end{alltt} + +\subsubsection{The text installer} + +Figure~\ref{fig:text-main} displays the main text mode screen under +Unix. + +This is only a command-line installer; there is no cursor support at +all. For instance, you cannot tab around checkboxes or input fields. +You just type something (case-sensitive) at the prompt and press the +Enter key, and then the entire terminal screen will be rewritten, with +adjusted content. + +The text installer interface is this primitive for a reason: it +is designed to run on as many platforms as possible, even with a +very barebones Perl (for Windows, a Perl subset is included). + +\subsubsection{The graphical installer} + +Figure~\ref{fig:gui-main} displays the graphical installer under +Windows. Most differences in available options are due to this +screenshot being from Windows, and the previous text screen being +from \GNU/Linux. + +\subsection{Running the installer} +\label{sec:runinstall} + +The installer is intended to be mostly self-explanatory. Still, a few +quick notes about the various options and submenus: + +\subsubsection{Binary systems menu (Unix only)} +\label{sec:binary} + +\begin{figure}[tbh] +\begin{boxedverbatim} +Available sets of binaries: +=============================================================================== + + a [ ] alpha-linux DEC Alpha with GNU/Linux + b [ ] amd64-freebsd x86_64 with FreeBSD + c [ ] hppa-hpux HP-UX + d [ ] i386-freebsd Intel x86 with FreeBSD + e [X] i386-linux Intel x86 with GNU/Linux + f [ ] i386-openbsd Intel x86 with OpenBSD + g [ ] i386-solaris Intel x86 with Sun Solaris + h [ ] mips-irix SGI IRIX + i [ ] powerpc-aix PowerPC with AIX + j [ ] powerpc-linux PowerPC with GNU/Linux + k [ ] sparc-linux Sparc with GNU/Linux + l [ ] sparc-solaris Sparc with Solaris + m [ ] universal-darwin universal binaries for MacOSX/Darwin + o [ ] win32 Windows + p [ ] x86_64-linux x86_64 with GNU/Linux +\end{boxedverbatim} +\caption{Binaries menu}\label{fig:bin-text} +\end{figure} + +Figure~\ref{fig:bin-text} displays the text mode binaries menu. By +default, only the binaries for your current platform will be installed. +From this menu, you can select installation of binaries for other +architectures as well. This can be useful if you are sharing a \TeX\ +tree across a network of heterogenous machines, or for a dual-boot +system. + +\subsubsection{Selecting what is going to be installed} +\label{sec:components} + +\begin{figure}[tbh] +\begin{boxedverbatim} +Select a scheme: +=============================================================================== + + a [ ] TeX Live basic scheme + b [ ] TeX Live scheme for ConTeXt + c [X] TeX Live full scheme + d [ ] GUST TeX Live scheme + e [ ] GUTenberg TeX Live scheme + f [ ] TeX Live medium scheme + g [ ] TeX Live minimal scheme + h [ ] TeX Live for Omega users + i [ ] teTeX scheme + j [ ] XML typesetting scheme +\end{boxedverbatim} +\caption{Scheme menu}\label{fig:scheme-text} +\end{figure} + +Figure~\ref{fig:scheme-text} displays the \TL\ scheme menu; from here, +you choose a ``scheme'', which is an overall set of package collections. +The default \optname{full} scheme installs everything available, but you +can also choose the \optname{basic} scheme for a small system, +\optname{minimal} for testing purposes, and \optname{medium} or +\optname{teTeX} to get something in between. There are also various +specialized and country-specific schemes. + +\begin{figure}[tbh] +\tlpng{stdcoll}{.7\linewidth} +\caption{Collections menu (Linux)}\label{fig:collections-gui} +\end{figure} + +You can refine your scheme selection with the `standard collections' and +`language collections' menus (figure~\ref{fig:collections-gui}, shown in +\GUI\ mode for a change). + +Collections are one level more detailed than schemes\Dash in essence, a +scheme consists of several collections, a collection consists of one or +more packages, and a package (the lowest level grouping in \TL) contains +the actual \TeX\ macro files, font files, and so on. + +If you want more control than the collection menus provide, you can use +the \prog{tlmgr} program after installation (see +section~\ref{sec:tlmgr}); using that, you can control the installation +at the package level. + +\subsubsection{Directories} +\label{sec:directories} + +The default layout is described in section~\ref{sec:texmftrees}, +\p.\pageref{sec:texmftrees}. The default location of +\dirname{TEXDIR} is different between Windows +(|%PROGRAMFILES%\texlive\2008|) and Unix +(\dirname{/usr/local/texlive/2008}). + +The main reason to change this default is if you lack write permission +for the default location. You don't have to be root or adminstrator to +install \TL, but you do need write access to the target directory. + +A logical alternate choice is a directory under your home directory, +especially if you will be the sole user. Use +`|~|' to indicate this, as in `|~/texlive/2008|'. + +We recommend including the year in the name, to enable keeping different +releases of \TL{} side by side. (You may wish to make a +version-independent name such as \dirname{/usr/local/texlive-cur} via a +symbolic link, which you can then update after testing the new release.) + +Changing \dirname{TEXDIR} in the installer will also change +\dirname{TEXMFLOCAL}, \dirname{TEXMFSYSVAR} and +\dirname{TEXMFSYSCONFIG}. + +\dirname{TEXMFHOME} is the recommended location for personal +macro files or packages. The default value is |~/texmf|. In +contrast to \dirname{TEXDIR}, here a |~| is preserved in the +newly-written configuration files, since it usefully refers to the home +directory of each individual running \TeX. It expands to +\dirname{$HOME} on Unix and \verb|%USERPROFILE%| on Windows. + +\subsubsection{Options} +\label{sec:options} + +\begin{figure}[tbh] +\begin{boxedverbatim} +

use letter size instead of A4 by default: [ ] + create all format files: [X] + install font/macro doc tree: [X] + install font/macro source tree: [X] + create symlinks in standard directories: [ ] + binaries to: + manpages to: + info to: +\end{boxedverbatim} +\caption{Options menu (Unix)}\label{fig:options-text} +\end{figure} + +Figure~\ref{fig:options-text} displays the text mode options menu. +Three of the options here need mentioning: + +\begin{description} +\item[use letter size instead of A4 by default:] The usual default paper + size selection. Of course, individual documents can specify a specific + paper size, if desired. + +\item[create all format files:] Although unnecessary format files + take time to generate and disk space to store, it is still recommended + to leave this option checked: if you don't, then format files will be + generated in people's private \dirname{TEXMFVAR} tree as they are + needed. In that location, they will not be updated automatically if + (say) binaries or hyphenation patterns are updated in the + installation, and thus could end up with incompatible format files. + +\item[create symlinks in standard directories] (Unix only): + This option bypasses the need to change environment + variables. Without this option, \TL{} directories have to be added + to \envname{PATH}, \envname{MANPATH} and \envname{INFOPATH}. You will + need write permissions to the target directories. It is not + advisable to overwrite a \TeX\ system that came with your system + with this option. It is intended primarily for creating the links + in standard directories that are known to users, such as + \dirname{/usr/local/bin}, which don't already contain any + \TeX\ files. +\end{description} + +Now when all these settings are to your liking, you can type `I' to +start the installation process. When it is done, skip to +section~\ref{sec:postinstall} to read what else needs to be done, if +anything. + +\htmlanchor{runfromdvd} +\subsubsection{Set up for running from DVD{} (text mode only)} +\label{sec:fromdvd} + +Type `|V|' to select this option. This changes the main menu into something +like figure~\ref{fig:main-fromdvd}. +\begin{figure}[tbh] +\begin{boxedverbatim} +======================> TeX Live installation procedure <===================== + +=======> Note: Letters/digits in indicate menu items <======= +=======> for commands or configurable options <======= + + directories: + TEXDIRW (Writable root): + !! default location: /usr/local/texlive/2008 + !! is not writable, please select a different one! + TEXMFLOCAL (directory for site-wide local files): + /usr/local/texlive/texmf-local + TEXMFSYSVAR (directory for variable and automatically generated data): + /usr/local/texlive/2008/texmf-var + TEXMFSYSCONFIG (directory for local config): + /usr/local/texlive/2008/texmf-config + TEXMFHOME (directory for user-specific files): + ~/texmf + + options: + [ ] use letter size instead of A4 by default + [X] create all format files + + set up for installing to hard disk + +Other actions: + start installation for running from DVD + help + quit +\end{boxedverbatim} +\caption{The main menu with \optname{from DVD} + set}\label{fig:main-fromdvd} +\end{figure} + +Note the changes: all options about what to install have +disappeared, and the directories section now talks about +\dirname{TEXDIRW} or writable root. The symlinks option has also +disappeared. + +The installer will still create various directories and +configuration files, but won't copy \dirname{texmf}, +\dirname{texmf-dist} or \dirname{texmf-doc} to hard disk. + +Post-install configuration for Unix will be slightly more complicated, +because now the directory layout deviates from the default; see +section~\ref{sec:postinstall}. + +Due to time constraints, this option didn't make it into the \GUI{} +installer, but it is available both for Unix and for +Windows. Windows users have to start the installer from a command +prompt, see section~\ref{sec:cmdline}. + +Section \ref{sec:portable-unix} describes a more strictly portable +way to run \TL, which doesn't make or require changes in the +system's configuration, but doesn't allow any configuration either. + +\subsection{Command-line install options} +\label{sec:cmdline} + +Type +\begin{alltt} +> \Ucom{install-tl -help} +\end{alltt} +for a listing of command-line options. Either |-| or |--| can be used +to introduce option names. These are the more +interesting ones: + +\begin{ttdescription} +\item[-gui] If possible, use the \GUI{} installer. This requires the + Perl/Tk module (\url{http://tug.org/texlive/distro.html#perltk}); + if Perl/Tk is not available, installation continues in text mode. +\item[-no-gui] Force using the text mode installer, even under + Windows; you'll need this if you want a `from \DVD' installation, + since that is not available in \GUI{} mode. +\item[-lang {\sl LL}] Specify the installer interface + language as its standard two-letter code \textsl{LL}. Currently + supported languages: English (\texttt{en}, default), German + (\texttt{de}), French (\texttt{fr}), Dutch (\texttt{nl}), Polish + (\texttt{pl}), Slovenian (\texttt{sl}) and Vietnamese + (\texttt{vi}). The installer tries to determine the right language + itself but if it fails, or if the right language is not available, + then it uses English as a fallback. +\item[-profile {\sl profile}] The installer always writes a file + \filename{texlive.profile} to the \dirname{2008/tlpkg}- or + \dirname{tlpkg} subdirectory of your installation. This option tells + the installer to re-use such a profile file. Here's an excerpt: + \begin{fverbatim} +# texlive.profile written on Wed Jul 9 16:13:44 2008 UTC +# It will NOT be updated and reflects only the +# installation profile at installation time. +selected_scheme scheme-basic +TEXDIR /usr/local/texlive/2008 +TEXDIRW /usr/local/texlive/2008 +... +TEXMFSYSVAR /usr/local/texlive/2008/texmf-var +collection-basic 1 +... +option_symlinks 0 + \end{fverbatim} + Thus, using this option you can install in batch mode on + subsequent systems, reproducing the choices you made for the + original installation. +\item [-location {\sl url/path}] Specify a non-default source for + packages; see below. +\end{ttdescription} + +\subsubsection{The \optname{location} parameter} +\label{sec:location} + +The location value can be a url starting with \texttt{ftp:}, +\texttt{http:}, or \texttt{file:/} url, or a plain path. If the given +argument is on a local drive (either a path or a \texttt{file:/} url), +the installation type (compressed or live) is automatically determined: +if an \dirname{archive} subdirectory with \filename{.tar.lzma} files is +found then it will be used, even if uncompressed files are available as +well. + +When giving an \texttt{http:} or \texttt{ftp:} location, trailing +`\texttt{/}' characters and/or a trailing `\texttt{/tlpkg}' component +are ignored. For example, you could choose a particular \CTAN\ mirror +with something like: +\url{http://ctan.example.org/tex-archive/texlive/tlnet/2008}, +substituting of course a proper hostname and its particular top-level +\CTAN\ path (the list of \CTAN\ mirrors is maintained at +\url{http://ctan.org/mirrors}) for |ctan.example.org/tex-archive|. The +default is to pick a mirror automatically, using +\url{http://mirror.ctan.org}; in any case, the chosen host is used for +the entire download. + + +\subsection{Post-install actions} +\label{sec:postinstall} + +Some post-install may be required. + +\subsubsection{Windows} + +But on Windows, the installer takes care of everything. + +\subsubsection{If symlinks were created} + +If you elected to create symlinks in standard directories (mentioned in +section~\ref{sec:options}), then there is no need to edit environment +variables. + +\subsubsection{Environment variables for Unix} +\label{sec:env} + +The directory of the binaries for your platform must be added to +the search path. Each supported platform has its own subdirectory +under \dirname{TEXDIR/bin}. See figure~\ref{fig:bin-text} for the +list of subdirectories and corresponding platforms. + +You can also add the documentation man and Info directories to their +respective search paths, if you want the system tools to find them. + +For Bourne-compatible shells such as \prog{bash}, and using Intel x86 +GNU/Linux and a default directory setup as an example, the file to edit +might be \filename{$HOME/.profile} (or another file sourced by +\filename{.profile}, and the lines to add would look like this: + +\begin{sverbatim} +PATH=/usr/local/texlive/2008/bin/i386-linux:$PATH; export PATH +MANPATH=/usr/local/texlive/2008/texmf/doc/man:$MANPATH; export MANPATH +INFOPATH=/usr/local/texlive/2008/texmf/doc/info:$INFOPATH; export INFOPATH +\end{sverbatim} + +For csh or tcsh, the file to edit is typically \filename{$HOME/.cshrc}, and +the lines to add might look like: + +\begin{sverbatim} +setenv PATH /usr/local/texlive/2008/bin/i386-linux:$PATH +setenv MANPATH /usr/local/texlive/2008/texmf/doc/man:$MANPATH +setenv INFOPATH /usr/local/texlive/2008/texmf/doc/info:$INFOPATH +\end{sverbatim} + +Of course, you may well already have settings somewhere in your ``dot'' +files, and so then the \TL\ directories should simply be merged in as +appropriate. + +\subsubsection{Environment variables: global configuration} +\label{sec:envglobal} + +If you want to make these changes globally, or for a user newly added to +the system, then you are on your own; there is just too much variation +between systems in how and where these things are configured. + +Our two hints are: 1)~you may want to check for a file +\filename{/etc/manpath.config} and, if present, add lines such as + +\begin{sverbatim} +MANPATH_MAP /usr/local/texlive/2008/bin/i386-linux \ + /usr/local/texlive/2008/texmf/doc/man +\end{sverbatim} + +And 2)~check for a file \filename{/etc/environment} which may define the +search path and other default environment variables. + + +\subsubsection{When running from DVD} + +Normally, a \TL{} program consults a file \filename{texmf.cnf} for the +location of the various trees. It looks for this file in a series of +locations relative to its own location. However, this scheme breaks down +when a program is run from \DVD{}: the \DVD{} is read-only. Some of the +paths to be recorded in \filename{texmf.cnf} are only known at +installation time, so this file cannot be on the \DVD{} and must be +placed somewhere else. This makes it necessary to define an environment +\envname{TEXMFCNF} variable which tells \TL{} programs in what directory +to find this \filename{texmf.cnf}. It is also still necessary to modify +the \envname{PATH} environment variable, as described before. + +At the end of the installation, the installer should have printed a +message giving the value to which \envname{TEXMFCNF} should be set. In +case you missed it: this value is \dirname{$TEXMFSYSVAR/web2c}. For the +default, \dirname{/usr/local/texlive/2008/texmf-var/web2c}, you need the +lines +\begin{sverbatim} +TEXMFCNF=/usr/local/texlive/2008/texmf-var/web2c; export TEXMFCNF +\end{sverbatim} +or, for [t]csh: +\begin{sverbatim} +setenv TEXMFCNF /usr/local/texlive/2008/texmf-var/web2c +\end{sverbatim} + + +\subsubsection{\ConTeXt{} Mark IV} + +The `old' \ConTeXt{} should run out of the box. The new `Mark IV' +\ConTeXt{} will require manual setup; see +\url{http://wiki.contextgarden.net/Running_Mark_IV}. + + +\subsubsection{Integrating local and personal macros} +\label{sec:local-personal-macros} + +This is already mentioned implicitly in section~\ref{sec:texmftrees}: +\dirname{TEXMFLOCAL} (by default, +\dirname{/usr/local/texlive/texmf-local} or +\verb|C:\Program Files\texlive\texmf-local|) + +is intended for system-wide local fonts and macros; and +\dirname{TEXMFHOME} (by default, \dirname{$HOME/texmf} or +\verb|%USERPROFILE%\texmf|), is for personal fonts and macros. These +directories are intended to stick around from release to release, and +have their content seen automatically by a new \TL{} release. +Therefore, it is best to refrain from changing the definition of +\dirname{TEXMFLOCAL} to be too far away from the main \TL{} directory, +or you will need to manually change future releases. + +For both trees, files should be placed in their proper subdirectories; +see \url{http://tug.org/tds} or consult +\filename{texmf/web2c/texmf.cnf}. For instance, a \LaTeX{} class file or +package should be placed in \dirname{TEXMFLOCAL/tex/latex} or +\dirname{TEXMFHOME/tex/latex}, or a subdirectory thereof. + +\dirname{TEXMFLOCAL} requires an up-to-date filename database, or files +will not be found. You can update it with the command +\cmdname{mktexlsr} or use the `Reinit file database' button on the +configuration tab of \prog{tlmgr} in \GUI\ mode. + +\subsubsection{Integrating third-party fonts} + +This is unfortunately a very complicated and messy topic. Forget +about it unless you really know your way around blindfolded in a +\TeX{} installation. Don't forget to check first what you get for +free: see section~\ref{sec:tl-fonts}. + +A possible alternative is to use \XeTeX (see +section~\ref{sec:tex-extensions}), which lets you use operating system +fonts without any installation in \TeX. + + +\subsection{Testing the installation} +\label{sec:test-install} + +After installing \TL{} as best you can, you naturally want to test +it out, so you can start creating beautiful documents and\slash or fonts. + +This section gives some basic procedures for testing that the new system +is functional. We give Unix commands here; under \MacOSX{} and Windows, +you're more likely to run the tests through a graphical interface, but +the principles are the same. + +\begin{enumerate} + +\item Make sure that you can run the \cmdname{tex} program in the first +place: + +\begin{alltt} +> \Ucom{tex -{}-version} +TeX 3.1415926 (Web2C 7.5.7) +kpathsea version 3.5.7 +... +\end{alltt} +If this comes back with `command not found' instead of version and +copyright information, or with an older version, most likely you don't +have the correct \dirname{bin} subdirectory in your \envname{PATH}. See +the environment-setting information on \p.\pageref{sec:env}. + +\item Process a basic \LaTeX{} file: +\begin{alltt} +> \Ucom{latex sample2e.tex} +This is pdfeTeXk, Version 3.1415926... +... +Output written on sample2e.dvi (3 pages, 7484 bytes). +Transcript written on sample2e.log. +\end{alltt} +If this fails to find \filename{sample2e.tex} or other files, most +likely you have interference from old environment variables or +configuration files; we recommend unsetting all \TeX-related environment +variables for a start. (For a deep analysis, you can ask \TeX{} to +report on exactly what it is searching for, and finding; see ``Debugging +actions'' on page~\pageref{sec:debugging}.) + +\item Preview the result online: +\begin{alltt} +> \Ucom{xdvi sample2e.dvi} +\end{alltt} +(Under Windows, the analogous command is \cmdname{dviout}.) You should +see a new window with a nice document explaining some of the basics of +\LaTeX{}. (Well worth reading, by the way if you're new to the system.) +You do have to be running under X for \cmdname{xdvi} to work; if you're +not, or your \envname{DISPLAY} environment variable is set incorrectly, +you'll get an error \samp{Can't open display}. + +\item Create a \PS{} file for printing or display: +\begin{alltt} +> \Ucom{dvips sample2e.dvi -o sample2e.ps} +\end{alltt} + +\item Create a \acro{PDF} file instead of \dvi{}; this processes the +\filename{.tex} file and writes \acro{PDF} directly: +\begin{alltt} +> \Ucom{pdflatex sample2e.tex} +\end{alltt} + +\item Preview the \acro{PDF} file: +\begin{alltt} +> \Ucom{gv sample2e.pdf} +\textrm{or:} +> \Ucom{xpdf sample2e.pdf} +\end{alltt} +Unfortunately neither \cmdname{gv} nor \cmdname{xpdf} are currently +included in \TL{}, so you must install them separately. See +\url{http://www.gnu.org/software/gv} and +\url{http://www.foolabs.com/xpdf}, respectively. (There are plenty of +other \acro{PDF} viewers, too.) + +\item Standard test files you may find useful in addition to +\filename{sample2e.tex}: + +\begin{ttdescription} +\item [small2e.tex] A simpler document than \filename{sample2e}, to +reduce the input size if you're having troubles. +\item [testpage.tex] Test if your printer introduces any offsets. +\item [nfssfont.tex] For printing font tables and tests. +\item [testfont.tex] Also for font tables, but using plain \TeX{}. +\item [story.tex] The most canonical (plain) \TeX{} test file of all. +You must type \samp{\bs bye} to the \code{*} prompt after \samp{tex +story.tex}. +\end{ttdescription} + +\end{enumerate} + +If you are new to \TeX{}, or otherwise need help with actually writing +\TeX{} or \LaTeX{} documents, please visit +\url{http://tug.org/begin.html} for some introductory resources. + + +\section{Network installations} +\label{sec:netinstall} + +\TL{} has been designed to be shared between different users, and even +different systems on a network. With a standard directory layout, no +hard paths are configured: the locations for files needed by \TL{} +programs are defined relative to the places of those programs. You can +see this at work in the configuration file +\filename{$TEXMFMAIN/web2c/texmf.cnf}, which contains lines such as +\begin{sverbatim} +TEXMFMAIN = $SELFAUTOPARENT/texmf +... +TEXMFLOCAL = $SELFAUTOPARENT/../texmf-local +\end{sverbatim} +This means that other systems or other users merely need to add the +directory for \TL{} binaries for their platform to their search path. + +By the same token, you can also install \TL{} locally and then move +the entire hierarchy afterwards to a network location. + +Of course, Windows users have different expectations. The directory +\dirname{texmf-doc/source/texlive/texlive-common/w32client} contains a +sample script \filename{install-w32client} which creates settings and +menu shortcuts for using an existing \TL{} installation on a +\acro{LAN}. It is to be invoked through a batch file +\filename{install-w32client.bat} in the same directory. + +You can read more about \TL{} configuration and path searching in +section~\ref{sec:kpathsea}. + +\section{Maximally portable \protect\TL{} on DVD and USB} +\label{sec:portable-unix} + +The `running from \DVD{}' option described in +section~\ref{sec:fromdvd} is fine for your own system, but if you +are a guest on somebody else's system then you would probably like +something with minimal side effects. + +In the root of the \TL{} \DVD, or the \dirname{texlive} subdirectory of +the \TK{} \DVD, are a \filename{tl-portable} script (Unix) and a +\filename{tl-portable.bat} batchfile (Windows) which start up a +secondary shell\slash command prompt with environment settings suitable +for directly accessing the \TL{} on the \DVD. + +When it runs for the first time, some files will be generated in a +directory \dirname{~/.tlportable2008}, which will take a little time. +On subsequent runs, though, it will start almost instantaneously. + +The rest of the system will be unaware of \TL. If you want your editor +to be aware of this \TL, then you can start it from a second, parallel, +such \filename{tl-portable} session. + +You can also use \filename{tl-portable} to run \TL{} on a +\acro{USB} stick. In this case, copy all the top-level files and +the contents of the \dirname{bin}, \dirname{texmf}, +\dirname{texmf-dist}, and \dirname{tlpkg} directories (at least) to +the stick. This may take quite a while! If you are copying to a +\acro{FAT}32-formatted \acro{USB} stick, make sure to dereference +symbolic links (\code{cp -L}). A \dirname{texmf-local} directory on +the stick will also be found and used. + +Then run \filename{tl-portable} from the root of the stick, as above. +In this case, the script will notice that the stick is writable and use +it for generated files. You could burn the resulting contents of the +stick back to \DVD{} if that is more convenient to (for example) give to +others. + + +\section{\cmdname{tlmgr}: Managing your installation} +\label{sec:tlmgr} + +\begin{figure}[tb] +\tlpng{tlmgr-gui}{\linewidth} +\caption{\prog{tlmgr} in \GUI\ mode. The list of + packages/collections/schemes only shows up after clicking the + `Load' button.}\label{fig:tlmgr-gui} +\end{figure} + +\begin{figure}[tb] +\tlpng{tlmgr-config}{\linewidth} +\caption{\texttt{tlmgr} in GUI mode: Configuration tab}\label{fig:tlmgr-config} +\end{figure} + +The installer installs a program named \prog{tlmgr} for managing \TL{} +after the initial installation. The programs \prog{updmap}, +\prog{fmtutil} and \prog{texconfig} are still included and will be +retained in the future, but \prog{tlmgr} is now the preferred interface. +Its capabilities include: + +\begin{itemize*} +\item listing schemes, collections and packages; +\item installing, updating, backing up, restoring and uninstalling + individual packages, optionally taking dependencies into account; +\item searching for packages; +\item listing and adding architectures; +\item changing installation options such as paper size and source + location (see section~\ref{sec:location}). +\end{itemize*} +\textit{Warning:} \prog{tlmgr} has not been designed for or tested +with installations which run from \DVD. + +\subsection{\cmdname{tlmgr} GUI mode} +\prog{tlmgr} can be started in \GUI{} mode with +\begin{alltt} +> \Ucom{tlmgr -gui} +\end{alltt} +or in Windows via the Start menu: \texttt{Start}, \texttt{Programs}, +\texttt{TeX Live 2008}, \texttt{TeX Live Manager}. After clicking `Load' +it displays a list of available and installed packages\Dash the latter +prepended with `(i)'. This assumes of course that the installation +source is valid and reachable. + +Figure~\ref{fig:tlmgr-config} shows the configuration tab. + +\subsection{Sample \cmdname{tlmgr} command-line invocations} + +This example adds several packages, including a new `engine', from a +non-default location: + +\begin{alltt} +> \Ucom{tlmgr -location http://172.16.18.1/tldev install collection-xetex xkeyval} +\end{alltt} +It generates the following output: +\begin{fverbatim} +install: collection-xetex +install: arabxetex +install: euenc +install: bidi +install: fontspec +install: fontwrap +install: ifxetex +install: philokalia +install: polyglossia +install: xecyr +install: xecyr.i386-linux +install: xepersian +install: xetex +install: xetexconfig +install: xetex.i386-linux +running post install action for xetex +install: xetex-def +install: xetex-pstricks +install: xetexfontinfo +install: xltxtra +install: xunicode +install: xkeyval +running mktexlsr +mktexlsr: Updating /usr/local/texlive/2008/texmf/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-config/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-dist/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-doc/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/../texmf-local/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-var/ls-R... +mktexlsr: Done. +regenerating fmtutil.cnf +running fmtutil-sys --missing +... +Transcript written on xelatex.log. +fmtutil: /usr/local/texlive/2008/texmf-var/web2c/xetex/xelatex.fmt installed. +\end{fverbatim} +As you see, \prog{tlmgr} installs dependencies, and takes care of any +necessary post-install actions, including updating the filename database +and (re)generating formats. (Here we generated new formats for \XeTeX.) + +This example installs a new language. This also triggers format +regeneration: +\begin{alltt} +> \Ucom{tlmgr install collection-langdutch} +\end{alltt} +To describe a package: +\begin{alltt} +> \Ucom{tlmgr show collection-wintools} +\end{alltt} +which produces +\begin{fverbatim} +Package: collection-wintools +Category: Collection +ShortDesc: Windows support programs +LongDesc: Utilities for Windows, since they are not readily available there: + gzip, chktex, jpeg2ps, unzip, wget, xpdf. +Installed: Yes +\end{fverbatim} +Updating your entire installation to the latest versions available: +\begin{alltt} +> \Ucom{tlmgr update -all} +\end{alltt} +If this makes you nervous, first try +\begin{alltt} +> \Ucom{tlmgr update -all -dry-run} +\end{alltt} +or +\begin{alltt} +> \Ucom{tlmgr update -list} +\end{alltt} +For full documentation: +\begin{alltt} +> \Ucom{tlmgr -help} +\end{alltt} + + +\section{Notes on Windows} +\label{sec:windows} + +\TL\ has a single installer which runs on both Windows and Unix. This +was only possible by dropping support for older Windows versions, so +\TL\ can now be installed only on Windows 2000 and later. + + +\subsection{Windows-specific features} +\label{sec:winfeatures} + +Under Windows, the installer does some extra things: +\begin{description} +\item[Menus and shortcuts.] A new `\TL{}' submenu of the + Start menu is installed, which contains entries for some \GUI{} programs + (\prog{tlmgr}, \prog{texdoctk}, the PS\_View PostScript previewer) + and some documentation. PS\_View also gets a shortcut on the + desktop as a drag-and-drop target for PostScript files. +\item[Automatic setting of environment variables.] No manual + configuration steps are required. +\item[Uninstaller.] The installer creates an entry under `Add/Remove + Programs' for \TL. The uninstall tab of\prog{tlmgr} refers to + this. +\end{description} + +\subsection{Additional included software} + +\begin{figure}[tb] +\tlpng{psview}{.6\linewidth} +\caption{PS\_View: very high magnifications available!}\label{fig:psview} +\end{figure} + +To be complete, a \TL installation needs support packages that are not +commonly found on a Windows machine. \TL{} provides the missing +pieces: +\begin{description} +\item[Perl and Ghostscript.] Because of the importance of Perl and + Ghostscript, \TL{} includes `hidden' copies of these + programs. \TL{} programs that need them know where to find them, + but they don't betray their presence through environment variables + or registry settings. They aren't full-scale distributions, and + shouldn't interfere with any system installations of Perl or + Ghostscript. +\item[Command-line tools.] A number of Windows ports of common Unix + command-line programs are installed along with the usual \TL{} + binaries. These include \cmdname{gzip}, \cmdname{chktex}, + \cmdname{jpeg2ps}, \cmdname{unzip}, \cmdname{wget} and the + command-line utilities from the \cmdname{xpdf} suite. (The + \cmdname{xpdf} viewer itself is not available for Windows, but the + Sumatra \acro{PDF} viewer is based on it: + \url{http://blog.kowalczyk.info/software/sumatrapdf}.) +\item[\texttt{fc-cache}] helps \XeTeX{} to handle fonts more + efficiently. +\item[PS\_View.] Also installed is PS\_View, a new PostScript viewer + with a free license; see figure~\ref{fig:psview}. +\end{description} +\begin{description} +\item[The \texttt{support} directory,] already mentioned in + section~\ref{sec:tld}. This directory contains various programs + which can be useful in connection with \TeX, in particular a + number of \TeX-aware editors and \TeX{} frontends. The software in + this directory isn't covered by the installer. This directory also + contains the \cmdname{dviout} \dvi{} previewer; see the next section. +\end{description} + +\subsection{The Dviout previewer} + +This \TL{} release unfortunately doesn't offer a preinstalled \dvi{} +previewer for Windows. However, you can install \prog{dviout} by +Toshio Oshima from the \path{support/dviout/} directory, which +contains also a short \filename{README} describing how to install +and configure \prog{dviout} for \TL. Please read this carefully +before installation. + +At first, when you preview files with \cmdname{dviout}, it will create fonts, +because screen fonts were not installed. After a while, you will have created +most of the fonts you use, and you will rarely see the font-creation window. +More information can be found in the (very good) on-line help. + +\subsection{Links for additional downloadable software} + +Urls for some other tools you may consider installing: +\begin{description} +\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} +\item[Perl] \url{http://www.perl.org/} with + supplementary packages from \acro{CPAN}, \url{http://www.cpan.org/} +\item[ImageMagick] \url{http://www.imagemagick.com}, for graphics + processing and conversion +\item[NetPBM] \url{http://netpbm.sourceforge.net/}, also for graphics. + +\item[\TeX-oriented editors] There is a wide choice, and it is a matter of the + user's taste. Here is a selection, in no particular order: + \begin{itemize*} + \item \cmdname{GNU Emacs} is available natively under Windows, see + \url{http://www.gnu.org/software/emacs/windows/ntemacs.html}. + \item \cmdname{Emacs} with Auc\TeX\ for Windows is available in \TL's + \path{support} directory; its home page is + \url{http://www.gnu.org/software/auctex}. + \item \cmdname{WinShell} is available in \TL's \path|support| + directory; its home page is \url{http://www.winshell.de}. + \item \cmdname{WinEdt} is shareware available from + \url{http://www.winedt.com}. + \item \cmdname{Vim} is free software, available from + \url{http://www.vim.org}. + \item TeXnicCenter is free software, available from + \url{http://www.toolscenter.org} and in the pro\TeX{}t distribution. + \item \cmdname{LEd} is available from \url{http://www.ctan.org/support/LEd}. + \item \cmdname{SciTE} is available from + \url{http://www.scintilla.org/SciTE.html}. + \end{itemize*} +\end{description} + + +\subsection{User Profile is Home} +\label{sec:winhome} + +The Windows counterpart of a Unix home directory is the +\verb|%USERPROFILE%| directory. Under Windows XP and Windows 2000, this +is usually \verb|C:\Documents and Settings\|, and under +Windows Vista \verb|C:\Users\|. In the +\filename{texmf.cnf} file, and \KPS{} in general, \verb|~| will expand +appropriately on both Windows and Unix. + + +\subsection{The Windows registry} +\label{sec:registry} + +Windows stores nearly all configuration data in its registry. The +registry contains a set of hierarchically organized keys, with several +root keys. The most important ones for installation programs are +\path{HKEY_CURRENT_USER} and \path{HKEY_LOCAL_MACHINE}, \path{HKCU} and +\path{HKLM} in short. The \path{HKCU} part of the registry is in the +user's home directory (see section~\ref{sec:winhome}). \path{HKLM} is +normally in a subdirectory of the Windows directory. + +In some cases, system information could be obtained from environment +variables but for other information, for example the location of +shortcuts, it is necessary to consult the registry. Setting environment +variables permanently also requires registry access. + + +\subsection{Windows permissions} +\label{sec:winpermissions} + +In later versions of Windows, a distinction is made between regular +users and administrators, where only the latter have free access to the +entire operating system. In practice, though, you could better describe +these classes of users as unprivileged users and normal users: being an +administrator is the rule, not the exception. Nevertheless, we have made +an effort to make \TL{} installable without administrative privileges. + +If the user is an administrator, shortcuts are created for all users, +and the system environment is modified. Otherwise, shortcuts and menu +entries are created for the current user, and the user environment is +modified. Use the \optname{non-admin} option to \prog{install-tl} if +you prefer per-user settings even as an administrator. + +Regardless of administrator status, the default root of \TL{} proposed +by the installer is always under \verb|%PROGRAMFILES%|. The installer +always tests whether the root is writable for the current user. + +A problem may arise if the user is not an administrator and \TeX{} +already exists in the search path. Since the effective path consists of +the system path followed by the user path, the new \TL{} will never get +precedence. As a workaround, in this case the installer creates +shortcuts to the command-prompt in which the new \TL{} binary directory +is prepended to the local searchpath. The new \TL{} will be usable when +run in a command-line session started from such a shortcut. + + +\section{A user's guide to Web2C} + +\Webc{} is an integrated collection of \TeX-related programs: \TeX{} +itself, \MF{}, \MP, \BibTeX{}, etc. It is the heart of \TL{}. The home +page for \Webc{}, with the current manual and more, is +\url{http://tug.org/web2c}. + +A bit of history: The original implementation was by Tomas Rokicki who, +in 1987, developed a first \TeX{}-to-C system based on change files +under Unix, which were primarily the original work of Howard Trickey and +Pavel Curtis. Tim Morgan became the maintainer of the system, and +during this period the name changed to Web-to-C\@. In 1990, Karl Berry +took over the work, assisted by dozens of additional contributors, and +in 1997 he handed the baton to Olaf Weber, who returned it to Karl in +2006. + +The \Webc{} system runs on Unix, 32-bit Windows systems, \MacOSX{}, and +other operating systems. It uses Knuth's original sources for \TeX{} and +other basic programs written in the \web{} literate programming system +and translates them into C source code. The core \TeX{} programs +handled in this way are: + +\begin{cmddescription} +\item[bibtex] Maintaining bibliographies. +\item[dmp] \cmdname{troff} to MPX (\MP{} pictures). +\item[dvicopy] Expands virtual font references in \dvi{} files. +\item[dvitomp] \dvi{} to MPX (MetaPost pictures). +\item[dvitype] \dvi{} to human-readable text. +\item[gftodvi] Generic font proofsheets. +\item[gftopk] Generic to packed fonts. +\item[gftype] GF to human-readable text. +\item[makempx] \MP{} label typesetting. +\item[mf] Creating typeface families. +\item[mft] Prettyprinting \MF{} source. +\item[mpost] Creating technical diagrams. +\item[mpto] MetaPost label extraction. +\item[newer] Compare modification times. +\item[patgen] Creating hyphenation patterns. +\item[pktogf] Packed to generic fonts. +\item[pktype] PK to human-readable text. +\item[pltotf] Plain text property list to TFM. +\item[pooltype] Display \web{} pool files. +\item[tangle] \web{} to Pascal. +\item[tex] Typesetting. +\item[tftopl] TFM to plain text property list. +\item[vftovp] Virtual font to virtual property list. +\item[vptovf] Virtual property list to virtual font. +\item[weave] \web{} to \TeX. +\end{cmddescription} + +\noindent The precise functions and syntax of these programs are +described in the documentation of the individual packages and of \Webc{} +itself. However, knowing a few principles governing the whole family of +programs will help you take advantage of your \Webc{} installation. + +All programs honor these standard \GNU options: +\begin{ttdescription} +\item[-{}-help] print basic usage summary. +\item[-{}-verbose] print detailed progress report. +\item[-{}-version] print version information, then exit. +\end{ttdescription} + +For locating files the \Webc{} programs use the path searching library +\KPS{} (\url{http://tug.org/kpathsea}). This library uses a combination +of environment variables and a configuration files to optimize searching +the (huge) collection of \TeX{} files. \Webc{} can look at many +directory trees simultaneously, which is useful in maintaining \TeX's +standard distribution and local and personal extensions in distinct +trees. To speed up file searches, the root of each tree has a file +\file{ls-R}, containing an entry showing the name and relative pathname +for all files under that root. + + +\subsection{Kpathsea path searching} +\label{sec:kpathsea} + +Let us first describe the generic path searching mechanism of the \KPS{} +library. + +We call a \emph{search path} a colon- or semicolon\hyph sepa\-rated list +of \emph{path elements}, which are basically directory names. A +search path can come from (a combination of) many sources. To look up +a file \samp{my-file} along a path \samp{.:/dir}, \KPS{} checks each +element of the path in turn: first \file{./my-file}, then +\file{/dir/my-file}, returning the first match (or possibly all +matches). + +In order to adapt optimally to all operating systems' conventions, on +non-Unix systems \KPS{} can use filename separators different from +colon (\samp{:}) and slash (\samp{/}). + +To check a particular path element \var{p}, \KPS{} first checks if a +prebuilt database (see ``Filename data\-base'' on +page~\pageref{sec:filename-database}) applies to \var{p}, i.e., if the +database is in a directory that is a prefix of \var{p}. If so, the path +specification is matched against the contents of the database. + +If the database does not exist, or does not apply to this path +element, or contains no matches, the filesystem is searched (if this +was not forbidden by a specification starting with \samp{!!}\ and if +the file being searched for must exist). \KPS{} constructs the list +of directories that correspond to this path element, and then checks +in each for the file being sought. + +The ``file must exist'' condition comes into play with \samp{.vf} files and +input files read by \TeX's \cs{openin} command. Such files may not +exist (e.g., \file{cmr10.vf}), and so it would be wrong to search the +disk for them. Therefore, if you fail to update \file{ls-R} when you +install a new \samp{.vf} file, it will never be found. +Each path element is checked in turn: first the database, then the +disk. If a match is found, the search stops and the result is +returned. + +Although the simplest and most common path element is a directory +name, \KPS{} supports additional features in search paths: layered +default values, environment variable names, config file values, users' +home directories, and recursive subdirectory searching. Thus, we say +that \KPS{} \emph{expands} a path element, meaning it transforms all +the specifications into basic directory name or names. This is +described in the following sections in the same order as it takes +place. + +Note that if the filename being searched for is absolute or explicitly +relative, i.e., starts with \samp{/} or \samp{./} or \samp{../}, +\KPS{} simply checks if that file exists. + +\ifSingleColumn +\else +\begin{figure*} +\verbatiminput{examples/ex5.tex} +\setlength{\abovecaptionskip}{0pt} + \caption{An illustrative configuration file sample} + \label{fig:config-sample} +\end{figure*} +\fi + +\subsubsection{Path sources} +\label{sec:path-sources} + +A search path can come from many sources. In the order in which +\KPS{} uses them: + +\begin{enumerate} +\item + A user-set environment variable, for instance, \envname{TEXINPUTS}\@. + Environment variables with a period and a program name appended + override; e.g., if \samp{latex} is the name of the program being run, + then \envname{TEXINPUTS.latex} will override \envname{TEXINPUTS}. +\item + A program-specific configuration file, for exam\-ple, a line + \samp{S /a:/b} in \cmdname{dvips}'s \file{config.ps}. +\item A \KPS{} configuration file \file{texmf.cnf}, containing a line like + \samp{TEXINPUTS=/c:/d} (see below). +\item The compile-time default. +\end{enumerate} +\noindent You can see each of these values for a given search path by +using the debugging options (see ``Debugging actions'' on +page~\pageref{sec:debugging}). + +\subsubsection{Config files} + +\begingroup\tolerance=3500 +\KPS{} reads \emph{runtime configuration files} named \file{texmf.cnf} +for search path and other definitions. The search path used to look +for these files is named \envname{TEXMFCNF} (by default such a file lives +in the \file{texmf/web2c} subdirectory). \emph{All} +\file{texmf.cnf} files in the search path will be read and definitions +in earlier files override those in later files. Thus, with a search +path of \verb|.:$TEXMF|, values from \file{./texmf.cnf} override those +from \verb|$TEXMF/texmf.cnf|. +\endgroup + +\begin{itemize} +\item + Comments start with \code{\%} and continue to the end of the line. +\item + Blank lines are ignored. +\item + A \bs{} at the end of a line acts as a continuation character, + i.e., the next line is appended. Whitespace at the beginning of + continuation lines is not ignored. +\item + Each remaining line has the form: +\begin{alltt} + \var{variable}[.\var{progname}] [=] \var{value} +\end{alltt}% + where the \samp{=} and surrounding whitespace are optional. +\item + The \ttvar{variable} name may contain any character other + than whitespace, \samp{=}, or \samp{.}, but sticking to + \samp{A-Za-z\_} is safest. +\item + If \samp{.\var{progname}} is present, the definition only + applies if the program that is running is named + \texttt{\var{progname}} or \texttt{\var{progname}.exe}. This allows + different flavors of \TeX{} to have different search paths, for + example. +\item \var{value} may contain any characters except + \code{\%} and \samp{@}. The + \code{\$\var{var}.\var{prog}} feature is not available on the + right-hand side; instead, you must use an additional variable. A + \samp{;}\ in \var{value} is translated to \samp{:}\ if + running under Unix; this is useful to be able to have a single + \file{texmf.cnf} for Unix, \acro{MS-DOS} and Windows systems. +\item + All definitions are read before anything is expanded, so + variables can be referenced before they are defined. +\end{itemize} +A configuration file fragment illustrating most of these points is +\ifSingleColumn +shown below: + +\verbatiminput{examples/ex5.tex} +\else +shown in Figure~\ref{fig:config-sample}. +\fi + +\subsubsection{Path expansion} +\label{sec:path-expansion} + + +\KPS{} recognizes certain special characters and constructions in +search paths, similar to those available in Unix shells. As a +general example, the complex path, +\verb+~$USER/{foo,bar}//baz+, expands to all subdirectories under +directories \file{foo} and \file{bar} in \texttt{\$USER}'s home +directory that contain a directory or file \file{baz}. These +expansions are explained in the sections below. +%$ +\subsubsection{Default expansion} +\label{sec:default-expansion} + +\tolerance=2500 +If the highest-priority search path (see ``Path sources'' on +page~\pageref{sec:path-sources}) contains an \emph{extra colon} (i.e., +leading, trailing, or doubled), \KPS{} inserts at that point the +next-highest-prio\-rity search path that is defined. If that inserted +path has an extra colon, the same happens with the next highest. For +example, given an environment variable setting + +\tolerance=1500 + +\begin{alltt} +> \Ucom{setenv TEXINPUTS /home/karl:} +\end{alltt} +and a \code{TEXINPUTS} value from \file{texmf.cnf} of + +\begin{alltt} + .:\$TEXMF//tex +\end{alltt} +then the final value used for searching will be: + +\begin{alltt} + /home/karl:.:\$TEXMF//tex +\end{alltt} + +Since it would be useless to insert the default value in more than one +place, \KPS{} changes only one extra \samp{:}\ and leaves any others in +place. It checks first for a leading \samp{:}, then a trailing +\samp{:}, then a doubled \samp{:}. + +\subsubsection{Brace expansion} + +A useful feature is brace expansion, which means that, for instance, +\verb+v{a,b}w+ expands to \verb+vaw:vbw+. Nesting is allowed. +This is used to implement multiple \TeX{} hierarchies, by +assigning a brace list to \code{\$TEXMF}. +For example, in \file{texmf.cnf}, the following definition +(appproximately; there are actually even more trees) is made: +\begin{verbatim} + TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN} +\end{verbatim} +Using this you can then write something like +\begin{verbatim} + TEXINPUTS = .;$TEXMF/tex// +\end{verbatim} +%$ +which means that, after looking in the current directory, the +\code{\$TEXMFHOME/tex}, \code{\$TEXMFLOCAL/tex}, \code{\$TEXMFVAR/tex} +and \code{\$TEXMFMAIN/tex} trees \emph{only}) will be searched (the +last two use using \file{ls-R} data base files). It is a convenient +way for running two parallel \TeX{} structures, one ``frozen'' (on a +\CD, for instance) and the other being continuously updated with new +versions as they become available. By using the \code{\$TEXMF} +variable in all definitions, one is sure to always search the +up-to-date tree first. + +\subsubsection{Subdirectory expansion} +\label{sec:subdirectory-expansion} + +Two or more consecutive slashes in a path element following a directory +\var{d} is replaced by all subdirectories of \var{d}: first those +subdirectories directly under \var{d}, then the subsubdirectories under +those, and so on. At each level, the order in which the directories are +searched is \emph{unspecified}. + +If you specify any filename components after the \samp{//}, only +subdirectories with matching components are included. For example, +\samp{/a//b} expands into directories \file{/a/1/b}, \file{/a/2/b}, +\file{/a/1/1/b}, and so on, but not \file{/a/b/c} or \file{/a/1}. + +Multiple \samp{//} constructs in a path are possible, but +\samp{//} at the beginning of a path is ignored. + +\subsubsection{List of special characters and their meaning: a summary} + +The following list summarizes the special characters in \KPS{} +configuration files. + +% need a wider space for the item labels here. +\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} +\begin{ttdescription} +\item[\CODE{:}] Separator in path specification; at the beginning or + the end of a path it substitutes the default path expansion.\par +\item[\CODE{;}] Separator on non-Unix systems (acts like \code{:}). +\item[\CODE{\$}] Variable expansion. +\item[\CODE{\string~}] Represents the user's home directory. +\item[\CODE{\char`\{...\char`\}}] Brace expansion. +\item[\CODE{//}] Subdirectory expansion (can occur anywhere in + a path, except at its beginning). +\item[\CODE{\%}] Start of comment. +\item[\CODE{\bs}] Continuation character (allows multi-line entries). +\item[\CODE{!!}] Search \emph{only} database to locate file, \emph{do + not} search the disk. +\end{ttdescription} + + +\subsection{Filename databases} +\label{sec:filename-database} + +\KPS{} goes to some lengths to minimize disk accesses for searches. +Nevertheless, at installations with enough directories, searching each +possible directory for a given file can take an excessively long time +(this is especially true if many hundreds of font directories have to +be traversed.) Therefore, \KPS{} can use an externally-built plain text +``database'' file named \file{ls-R} that maps files to directories, +thus avoiding the need to exhaustively search the disk. + +A second database file \file{aliases} allows you to give additional +names to the files listed in \file{ls-R}. This can be helpful to +confirm to \acro{DOS} 8.3 filename conventions in source files. + +\subsubsection{The filename database} +\label{sec:ls-R} + +As explained above, the name of the main filename database must be +\file{ls-R}. You can put one at the root of each \TeX{} hierarchy in +your installation that you wish to be searched (\code{\$TEXMF} by +default); most sites have only one hierarchy. \KPS{} looks for +\file{ls-R} files along the \code{TEXMFDBS} path. + +The recommended way to create and maintain \samp{ls-R} is to run the +\code{mktexlsr} script included with the distribution. It is invoked +by the various \samp{mktex}\dots\ scripts. In principle, this script +just runs the command +\begin{alltt} +cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R +\end{alltt} +presuming your system's \code{ls} produces the right output format +(\GNU \code{ls} is all right). To ensure that the database is +always up-to-date, it is easiest to rebuild it regularly via +\code{cron}, so that it is automatically updated when the installed +files change, such as after installing or updating a \LaTeX{} package. + +If a file is not found in the database, by default \KPS{} goes ahead +and searches the disk. If a particular path element begins with +\samp{!!}, however, \emph{only} the database will be searched for that +element, never the disk. + + +\subsubsection{kpsewhich: Standalone path searching} +\label{sec:invoking-kpsewhich} + +The \texttt{kpsewhich} program exercises path searching independent of any +particular application. This can be useful as a sort of \code{find} +program to locate files in \TeX{} hierarchies (this is used heavily in +the distributed \samp{mktex}\dots\ scripts). + +\begin{alltt} +> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} +\end{alltt} +The options specified in \ttvar{option} start with either \samp{-} +or \samp{-{}-}, and any unambiguous abbreviation is accepted. + +\KPS{} looks up each non-option argument on the command line as a +filename, and returns the first file found. There is no option to +return all the files with a particular name (you can run the Unix +\samp{find} utility for that). + +The most common options are described next. + +\begin{ttdescription} +\item[\texttt{-{}-dpi=\var{num}}]\mbox{} + Set the resolution to \ttvar{num}; this only affects \samp{gf} + and \samp{pk} lookups. \samp{-D} is a synonym, for compatibility + with \cmdname{dvips}. Default is 600. + +\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ + Set the format for lookup to \ttvar{name}. By default, the + format is guessed from the filename. For formats which do not have + an associated unambiguous suffix, such as \MP{} support files and + \cmdname{dvips} configuration files, you have to specify the name as + known to \KPS{}, such as \texttt{tex} or \texttt{enc files}. Run + \texttt{kpsewhich -{}-help} for a list. + +\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ + Set the mode name to \ttvar{string}; this only affects \samp{gf} + and \samp{pk} lookups. No default: any mode will be found. +\item[\texttt{-{}-must-exist}]\mbox{}\\ + Do everything possible to find the files, notably including + searching the disk. By default, only the \file{ls-R} database is + checked, in the interest of efficiency. +\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ + Search along the path \ttvar{string} (colon-separated as usual), + instead of guessing the search path from the filename. \samp{//} and + all the usual expansions are supported. The options \samp{-{}-path} + and \samp{-{}-format} are mutually exclusive. +\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ + Set the program name to \texttt{\var{name}}. + This can affect the search paths via the \texttt{.\var{progname}} + feature. + The default is \cmdname{kpsewhich}. +\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ + shows the path used for file lookups of file type \texttt{\var{name}}. + Either a filename extension (\code{.pk}, \code{.vf}, etc.) or a + name can be used, just as with \samp{-{}-format} option. +\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ + sets the debugging options to \texttt{\var{num}}. +\end{ttdescription} + + +\subsubsection{Examples of use} +\label{sec:examples-of-use} + +Let us now have a look at \KPS{} in action. Here's a straightforward search: + +\begin{alltt} +> \Ucom{kpsewhich article.cls} + /usr/local/texmf-dist/tex/latex/base/article.cls +\end{alltt} +We are looking for the file \file{article.cls}. Since the \samp{.cls} +suffix is unambiguous we do not need to specify that we want to look for a +file of type \optname{tex} (\TeX{} source file directories). We find it in +the subdirectory \file{tex/latex/base} below the \samp{texmf-dist} \TL\ +directory. Similarly, all of the following are found without problems +thanks to their unambiguous suffix. +\begin{alltt} +> \Ucom{kpsewhich array.sty} + /usr/local/texmf-dist/tex/latex/tools/array.sty +> \Ucom{kpsewhich latin1.def} + /usr/local/texmf-dist/tex/latex/base/latin1.def +> \Ucom{kpsewhich size10.clo} + /usr/local/texmf-dist/tex/latex/base/size10.clo +> \Ucom{kpsewhich small2e.tex} + /usr/local/texmf-dist/tex/latex/base/small2e.tex +> \Ucom{kpsewhich tugboat.bib} + /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib +\end{alltt} + +By the way, that last is a \BibTeX{} bibliography database for \textsl{TUGBoat} articles. + +\begin{alltt} +> \Ucom{kpsewhich cmr10.pk} +\end{alltt} +Font bitmap glyph files of type \file{.pk} are used by display +programs like \cmdname{dvips} and \cmdname{xdvi}. Nothing is returned in +this case since there are no pre-generated Computer Modern \samp{.pk} +files in \TL{}\Dash the Type~1 variants are used by default. +\begin{alltt} +> \Ucom{kpsewhich wsuipa10.pk} +\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk +\else /usr/local/texmf-var/fonts/pk/ljfour/public/ +... wsuipa/wsuipa10.600pk +\fi\end{alltt} +For these fonts (a phonetic alphabet from the University of Washington) +we had to generate \samp{.pk} files, and since the default \MF{} mode on +our installation is \texttt{ljfour} with a base resolution of 600\dpi{} +(dots per inch), this instantiation is returned. +\begin{alltt} +> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} +\end{alltt} +In this case, when specifying that we are interested in a resolution +of 300\dpi{} (\texttt{-dpi=300}) we see that no such font is available on +the system. A program like \cmdname{dvips} or \cmdname{xdvi} would +go off and actually build the required \texttt{.pk} files +using the script \cmdname{mktexpk}. + +Next we turn our attention to \cmdname{dvips}'s header and configuration +files. We first look at one of the commonly used files, the general +prologue \file{tex.pro} for \TeX{} support, before turning our attention +to the generic configuration file (\file{config.ps}) and the \PS{} font +map \file{psfonts.map}\Dash as of 2004, map and encoding files have +their own search paths and new location in \dirname{texmf} trees. As +the \samp{.ps} suffix is ambiguous we have to specify explicitly which +type we are considering (\optname{dvips config}) for the file +\texttt{config.ps}. +\begin{alltt} +> \Ucom{kpsewhich tex.pro} + /usr/local/texmf/dvips/base/tex.pro +> \Ucom{kpsewhich --format="dvips config" config.ps} + /usr/local/texmf/dvips/config/config.ps +> \Ucom{kpsewhich psfonts.map} + /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map +\end{alltt} + +We now take a closer look at the \acro{URW} Times \PS{} support +files. The prefix for these in the standard font naming scheme is +\samp{utm}. The first file we look at is the configuration file, +which contains the name of the map file: +\begin{alltt} +> \Ucom{kpsewhich --format="dvips config" config.utm} + /usr/local/texmf-dist/dvips/psnfss/config.utm +\end{alltt} +The contents of that file is +\begin{alltt} + p +utm.map +\end{alltt} +which points to the file \file{utm.map}, which we want to +locate next. +\begin{alltt} +> \Ucom{kpsewhich utm.map} + /usr/local/texmf-dist/fonts/map/dvips/times/utm.map +\end{alltt} +This map file defines the file names of the Type~1 \PS{} fonts in +the URW collection. Its contents look like (we only show part of the +lines): +\begin{alltt} +utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} +\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb +\else /usr/local/texmf-dist/fonts/type1/ +... urw/utm/utmr8a.pfb +\fi\end{alltt} + +It should be evident from these examples how you can easily locate the +whereabouts of a given file. This is especially important if you suspect +that the wrong version of a file is picked up somehow, since +\cmdname{kpsewhich} will show you the first file encountered. + +\subsubsection{Debugging actions} +\label{sec:debugging} + +Sometimes it is necessary to investigate how a program resolves file +references. To make this practical, \KPS{} offers various levels of +debugging output: + +\begin{ttdescription} +\item[\texttt{\ 1}] \texttt{stat} calls (disk lookups). When running + with an up-to-date \file{ls-R} database this should almost give no + output. +\item[\texttt{\ 2}] References to hash tables (such as \file{ls-R} + databases, map files, configuration files). +\item[\texttt{\ 4}] File open and close operations. +\item[\texttt{\ 8}] General path information for file types + searched by \KPS. This is useful to find out where a particular + path for the file was defined. +\item[\texttt{16}] Directory list for each path element (only relevant + for searches on disk). +\item[\texttt{32}] File searches. +\item[\texttt{64}] Variable values. +\end{ttdescription} +A value of \texttt{-1} will set all the above options; in practice, +this is usually the most convenient. + +Similarly, with the \cmdname{dvips} program, by setting a combination of +debug switches, one can follow in detail where files are being picked up +from. Alternatively, when a file is not found, the debug trace shows in +which directories the program looks for the given file, so that one can +get an indication what the problem~is. + +Generally speaking, as most programs call the \KPS{} library +internally, one can select a debug option by using the +\envname{KPATHSEA\_DEBUG} environment variable, and setting it to (a +combination of) values as described in the above list. + +(Note for Windows users: it is not easy to redirect +all messages to a file in this system. For diagnostic purposes +you can temporarily \texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log}). + +Let us consider, as an example, a small \LaTeX{} source file, +\file{hello-world.tex}, which contains the following input. +\begin{verbatim} + \documentclass{article} + \begin{document} + Hello World! + \end{document} +\end{verbatim} +This little file only uses the font \file{cmr10}, so let us look at +how \cmdname{dvips} prepares the \PS{} file (we want to use the Type~1 +version of the Computer Modern fonts, hence the option \texttt{-Pcms}). +\begin{alltt} +> \Ucom{dvips -d4100 hello-world -Pcms -o} +\end{alltt} +In this case we have combined \cmdname{dvips}'s debug class 4 (font +paths) with \KPS's path element expansion (see \cmdname{dvips} Reference +Manual, \OnCD{texmf/doc/dvips/dvips.pdf}). +The output (slightly rearranged) appears in +Figure~\ref{fig:dvipsdbga}. +\begin{figure*}[tp] +\centering +\input{examples/ex6a.tex} +\caption{Finding configuration files}\label{fig:dvipsdbga} + +\bigskip + +\input{examples/ex6b.tex} +\caption{Finding the prolog file}\label{fig:dvipsdbgb} + +\bigskip + +\input{examples/ex6c.tex} +\caption{Finding the font file}\label{fig:dvipsdbgc} +\end{figure*} + +\cmdname{dvips} starts by locating its working files. First, +\file{texmf.cnf} is found, which gives the definitions of the search +paths for the other files, then the file database \file{ls-R} (to +optimize file searching) and the file \file{aliases}, which makes it +possible to declare several names (e.g., a short \acro{DOS}-like 8.3 and +a more natural longer version) for the same file. Then \cmdname{dvips} +goes on to find the generic configuration file \file{config.ps} +before looking for the customization file \file{.dvipsrc} (which, in +this case is \emph{not found}). Finally, \cmdname{dvips} locates the +config file for the Computer Modern \PS{} fonts \file{config.cms} +(this was initiated with the \texttt{-Pcms} option on the \cmdname{dvips} +command). This file contains the list of the map files which +define the relation between the \TeX{}, \PS{} and file system +names of the fonts. +\begin{alltt} +> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} + p +ams.map + p +cms.map + p +cmbkm.map + p +amsbkm.map +\end{alltt} +\cmdname{dvips} thus goes on to find all these files, plus the generic +map file \file{psfonts.map}, which is always loaded (it contains +declarations for commonly used \PS{} fonts; see the last part of +Section \ref{sec:examples-of-use} for more details about \PS{} map +file handling). + +At this point \cmdname{dvips} identifies itself to the user: +\begin{alltt} +This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) +\end{alltt} +\ifSingleColumn +Then it goes on to look for the prolog file \file{texc.pro}: +\begin{alltt}\small +kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro +\end{alltt} +\else +Then it goes on to look for the prolog file \file{texc.pro} (see +Figure~\ref{fig:dvipsdbgb}). +\fi + +After having found the file in question, \cmdname{dvips} outputs +the date and time, and informs us that it will generate the +file \file{hello-world.ps}, then that it needs the font file +\file{cmr10}, and that the latter is declared as ``resident'' (no +bitmaps needed): +\begin{alltt}\small +TeX output 1998.02.26:1204' -> hello-world.ps +Defining font () cmr10 at 10.0pt +Font cmr10 is resident. +\end{alltt} +Now the search is on for the file \file{cmr10.tfm}, which is found, +then a few more prolog files (not shown) are referenced, and finally +the Type~1 instance \file{cmr10.pfb} of the font is located and +included in the output file (see last line). +\begin{alltt}\small +kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, + path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: + /var/tex/fonts/tfm//). +kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm +kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, + ... + +kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb +[1] +\end{alltt} + +\subsection{Runtime options} + +Another useful feature of \Webc{} is its possibility to control a number +of memory parameters (in particular, array sizes) via the runtime file +\file{texmf.cnf} read by \KPS{}. The memory settings can be found in +Part 3 of that file in the \TL{} distribution. The more important +are: + +\begin{ttdescription} +\item[\texttt{main\_memory}] + Total words of memory available, for + \TeX{}, \MF{} and \MP. You must make a new format file for each + different setting. For instance, you could generate a ``huge'' + version of \TeX{}, and call the format file \texttt{hugetex.fmt}. + Using the standard way of specifying the program name used by \KPS{}, + the particular value of the \texttt{main\_memory} variable will then + be read from \file{texmf.cnf}. +\item[\texttt{extra\_mem\_bot}] + Extra space for ``large'' \TeX{} data structures: + boxes, glue, breakpoints, etc. Especially useful if you use + \PiCTeX{}. +\item[\texttt{font\_mem\_size}] + Number of words for font information available for \TeX. This + is more or less the total size of all \acro{TFM} files read. +\item[\texttt{hash\_extra}] + Additional space for the hash table of control sequence names. + Only $\approx$10,000 control sequences can be stored in the main + hash table; if you have a large book with numerous cross-references, + this might not be enough. The default value of + \texttt{hash\_extra} is \texttt{50000}. +\end{ttdescription} + +\noindent Of course, this facility is no substitute for truly dynamic +arrays and memory allocation, but since these are extremely difficult to +implement in the present \TeX{} source, these runtime parameters provide +a practical compromise allowing some flexibility. + + +\begin{comment} +\section{Building on a new Unix platform} + +If you have a platform for which executables are not included, you will +need to compile \TeX{} and friends. This is not as hard as it +sounds. What you need is all in the directory \texttt{source} in the +distribution. + +\subsection{Prerequisites} + +You will need at least 100 megabytes of disk space to compile all of +\TeX{} and its support programs. You'll also need an \acro{ANSI} C +compiler, a \cmdname{make} utility, a lexical scanner, and a parser +generator. We recommend the \GNU version of these programs +(\cmdname{gcc}, \GNU \cmdname{make}, \cmdname{m4}, \cmdname{flex}, +\cmdname{bison}). You may be able to work with other C compilers and +\cmdname{make} programs, but you will need a good understanding of +building Unix programs to sort out problems. + +Also, the command \texttt{uname} must return a sensible value. + + +\subsection{Configuration} + +To begin, perform a normal installation of \TL{} to your disk (see +section~\ref{sec:install-disk} on +\p.\pageref{sec:install-disk}). You may wish to skip installing +all of the prebuilt binaries. + +Then, unpack the source from the compressed \texttt{tar} file in the +directory \dirname{source} to your disk and change directory to where +you placed it. + +Next, run \cmdname{configure} with a command line like this: +\begin{alltt} +> \Ucom{sh configure -prefix=/usr/local/TeX} +\end{alltt} + +The \optname{-prefix} directory is the one where you installed the +support tree; the directory layout will be as follows (where \$TEXDIR +stands for the directory you chose): + +\noindent +\begin{tabular}{>{\ttfamily}ll@{}} + \dirname{$TEXDIR/share/texmf} & main tree with fonts,\\ + & \qquad macros, etc\\ + \dirname{$TEXDIR/man} & Unix manual pages\\ + \dirname{$TEXDIR/info} & \GNU style Info manuals\\ + \dirname{$TEXDIR/bin/$PLATFORM} & binaries\\ +\end{tabular} +%$ + +If you want to leave out the \dirname{$PLATFORM} directory level, +i.e., put the binaries directly into \dirname{$TEXDIR/bin}, specify +the \verb|--disable-multiplatform| option to \cmdname{configure}. + +Have a look at the output of \verb|./configure --help| for more +options you can use. For example, you can skip building of \OMEGA{} and +\eTeX{}. + + +\subsection{Running \cmdname{make}} + +Make sure the shell variable or option \texttt{noclobber} is not set. +Then, run the main \cmdname{make} like this: +\begin{alltt} +> \Ucom{make world} +\end{alltt} +and relax\ldots + +Alternatively, you want to log all the output, as in: +\begin{alltt} +> \Ucom{sh -c "make world >world.log 2>\&1" \&} +\end{alltt} + +Before you believe that everything went ok, please check the log file +for errors: \GNU \cmdname{make} always uses the string \samp{***} +whenever a command fails. Also, check if all the programs were built: + +\begin{alltt} +> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} +> \Ucom{ls | wc} +\end{alltt} +The result should be over 200 (you can check the exact number with the +\dirname{bin} directory contents in the distribution). + +If you need special privileges for \texttt{make install}, you can +separate the \samp{make world} into two different runs, like this: +\begin{alltt} +> \Ucom{make all} +> \Ucom{su} +> \Ucom{make install strip} +\end{alltt} + +After you've installed your new binaries, you should follow the normal +post-installation procedures, given in section~\ref{sec:postinstall} +(\p.\pageref{sec:postinstall}). + +Also, if you'd like to make your binaries available to others, please +contact us. We'll be happy to put them on the \TL\ web pages. +\end{comment} + +\htmlanchor{ack} +\section{Acknowledgements} + +\TL{} is a joint effort by virtually all of the \TeX{} user groups. +This edition of \TL{} was overseen by Karl Berry. The other principal +contributors, past and present, are listed below. + +\begin{itemize*} + +\item The English, German, Dutch, and Polish \TeX{} user groups +(\acro{TUG}, \acro{DANTE} e.V., \acro{NTG}, and \acro{GUST}, +respectively), which provide the necessary technical and administrative +infrastructure. Please join the \TeX\ user group near you! (See +\url{http://tug.org/usergroups.html}.) + +\item The \acro{CTAN} team, most notably Robin Fairbairns, Jim Hef{}feron, +and Rainer Sch\"opf, which distributes the \TL{} images and provides the +common infrastructure for package updates, upon which \TL{} depends. + +\item Peter Breitenlohner (and the \eTeX\ team) for the stable foundation +of future \TeX's, and Peter specifically for stellar help with the GNU +autotools usage throughout \TL. + +\item Thomas Esser, without whose marvelous \teTeX{} package \TL{} +would have never existed. + +\item Michel Goossens, who co-authored the original documentation. + +\item Eitan Gurari, whose \TeX4ht was used to create the \HTML{} +version of this documentation, and who worked tirelessly to improve +it at short notice. + +\item \Thanh, Martin Schr\"oder, and the pdf\TeX\ team +(\url{http://pdftex.org}) for continuing enhancements of \TeX's +abilities. + +\item Hans Hagen, for much testing and making his \ConTeXt\ format +(\url{http://pragma-ade.com}) work within \TL's framework. + +\item Hartmut Henkel, for significant development contributions to +pdf\TeX\, Lua\TeX, and more. + +\item Taco Hoekwater, for renewed development efforts on MetaPost and +(Lua)\TeX\ (\url{http://luatex.org}) itself, and for incorporating +\ConTeXt\ into \TL. + +\item Pawe{\l} Jackowski, for the Windows installer \cmdname{tlpm}, +and Tomasz {\L}uczak, for \cmdname{tlpmgui}, used in past releases. + +\item Akira Kakuto, for providing the Windows +binaries from his \acro{W32TEX} distribution for Japanese \TeX\ +(\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}), and many +other contributions. + +\item Jonathan Kew and \acro{SIL}, for the major new development of +\XeTeX{} and taking the time and trouble to integrate it in \TL{}, as +well as the initial version of the Mac\TeX\ installer. + +\item Dick Koch, for maintaining Mac\TeX\ (\url{http://tug.org/mactex}) +in very close tandem with \TL{}, and for his great good cheer in doing +so. + +\item Reinhard Kotucha, for major contributions to the \TL{} 2008 +infrastructure and installer, as well as Windows research efforts, the +\texttt{getnonfreefonts} script, and more. + +\item Siep Kroonenberg, also for major contributions to the \TL{} 2008 +infrastructure and installer, especially on Windows, and for the bulk of +work updating this manual describing the new features. + +\item Petr Ol\v{s}ak, who coordinated and checked all the Czech and Slovak +material very carefully. + +\item Toshio Oshima, for his \cmdname{dviout} previewer for Windows. + +\item Manuel P\'egouri\'e-Gonnard, for helping with package updates, +documentation improvements, and \cmdname{tldoc} development. + +\item Fabrice Popineau, for the original Windows support in \TL{} and +work on the French documentation. + +\item Norbert Preining, the principal architect of the \TL{} 2008 +infrastructure and installer, and also for coordinating the Debian +version of \TL{} (together with Frank K\"uster), making many suggestions +along the way. + +\item Sebastian Rahtz, for originally creating \TL{} and maintaining it +for many years. + +\item Phil Taylor, for setting up the BitTorrent downloads. + +\item Vladimir Volovich, for substantial help with porting and other +maintenance issues, and especially for making it feasible to include +\cmdname{xindy}. + +\item Staszek Wawrykiewicz, the principal tester for all of \TL{}, +and coordinator of the many major Polish contributions: fonts, Windows +installation, and more. + +\item Olaf Weber, for his patient maintenance of \Webc. + +\item Gerben Wierda, for creating and maintaining the \MacOSX\ support, +and much integration and testing. + +\item Graham Williams, on whose work the \TeX\ Catalogue of packages depends. + +\end{itemize*} + +Builders of the binaries: +Reinhard Kotucha (\pkgname{x86\_64-linux}), +Tim Arnold (\pkgname{hppa-hpux}), +Randy Au (\pkgname{amd64-freebsd}), +Edd Barrett (\pkgname{i386-openbsd}), +Karl Berry (\pkgname{i386-linux}), +Akira Kakuto (\pkgname{win32}), +Dick Koch (\pkgname{universal-darwin}), +Manfred Lotz (\pkgname{i386-freebsd}), +Norbert Preining (\pkgname{alpha-linux}), +Arthur Reutenauer (\pkgname{sparc-linux}), +Thomas Schmitz (\pkgname{powerpc-linux}), +Apostolos Syropoulos (\pkgname{i386-solaris}), +Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-solaris}), +Olaf Weber (\pkgname{mips-irix}). +For information on the \TL{} build process, see +\url{http://tug.org/texlive/build.html}. + +Documentation and translation updates: +Karl Berry (English), +Daniel Flipo (French), +Klaus H\"oppner (German), +Petr Sojka \& Jan Busa (Czech\slash Slovak), +Boris Veytsman (Russian), +Staszek Wawrykiewicz (Polish). The \TL{} documentation web page +is \url{http://tug.org/texlive/doc.html}. + +Of course the most important acknowledgement must go to Donald Knuth, +first for inventing \TeX, and then for giving it to the world. + + + +\section{Release history} +\label{sec:history} + +\subsection{Past} + +Discussion began in late 1993 when the Dutch \TeX{} Users Group was +starting work on its 4All\TeX{} \CD{} for \acro{MS-DOS} users, and it +was hoped at that time to issue a single, rational, \CD{} for all +systems. This was too ambitious a target for the time, but it did spawn +not only the very successful 4All\TeX{} \CD{}, but also the \acro{TUG} +Technical Council working group on a \emph{\TeX{} Directory Structure} +(\url{http://tug.org/tds}), which specified how to create consistent and +manageable collections of \TeX{} support files. A complete draft of the +\TDS{} was published in the December 1995 issue of \textsl{TUGboat}, and +it was clear from an early stage that one desirable product would be a +model structure on \CD{}. The distribution you now have is a very direct +result of the working group's deliberations. It was also clear that the +success of the 4All\TeX{} \CD{} showed that Unix users would benefit +from a similarly easy system, and this is the other main strand of +\TL. + +We first undertook to make a new Unix-based \TDS{} \CD{} in the autumn +of 1995, and quickly identified Thomas Esser's \teTeX{} as the ideal +setup, as it already had multi-platform support and was built with +portability across file systems in mind. Thomas agreed to help, and work +began seriously at the start of 1996. The first edition was released in +May 1996. At the start of 1997, Karl Berry completed a major new release +of Web2c, which included nearly all the features which Thomas Esser had +added in \teTeX, and we decided to base the 2nd edition of the \CD{} on +the standard \Webc, with the addition of \teTeX's \texttt{texconfig} +script. The 3rd edition of the \CD{} was based on a major revision of +\Webc, 7.2, by Olaf Weber; at the same time, a new revision of \teTeX +was being made, and \TL{} included almost all of its features. The +4th edition followed the same pattern, using a new version of \teTeX, +and a new release of \Webc{} (7.3). The system now included a complete +Windows setup. + +For the 5th edition (March 2000) many parts of the \CD{} were revised +and checked, updating hundreds of packages. Package details were stored +in XML files. But the major change for \TeX\ Live 5 was that all +non-free software was removed. Everything in \TL{} is now intended +to be compatible with the Debian Free Software Guidelines +(\url{http://www.debian.org/intro/free}); we have done our best to check +the license conditions of all packages, but we would very much +appreciate hearing of any mistakes. + +The 6th edition (July 2001) had much more material updated. The major +change was a new install concept: the user could select a more exact set +of needed collections. Language-related collections were completely +reorganized, so selecting any of them installs not only macros, fonts, +etc., but also prepares an appropriate \texttt{language.dat}. + +The 7th edition of 2002 had the notable addition of \MacOSX{} support, +and the usual myriad of updates to all sorts of packages and +programs. An important goal was integration of the source back with +\teTeX, to correct the drift apart in versions~5 and~6. + +\subsubsection{2003} + +In 2003, with the continuing flood of updates and additions, we found +that \TL{} had grown so large it could no longer be contained on a +single \CD, so we split it into three different distributions (see +section~\ref{sec:tl-coll-dists}, \p.\pageref{sec:tl-coll-dists}). In +addition: + +\begin{itemize*} +\item At the request of the \LaTeX{} team, we changed the standard + \cmdname{latex} and \cmdname{pdflatex} commands to now use \eTeX{} (see + \p.\pageref{text:etex}). +\item The new Latin Modern fonts were included (and are recommended). +\item Support for Alpha \acro{OSF} was removed + (\acro{HPUX} support was removed previously), since no one had (or + volunteered) hardware available on which to compile new binaries. +\item Windows setup was substantially changed; for the first time + an integrated environment based on XEmacs was introduced. +\item Important supplementary programs for Windows + (Perl, Ghost\-script, Image\-Magick, Ispell) are now installed + in the \TL{} installation directory. +\item Font map files used by \cmdname{dvips}, \cmdname{dvipdfm} + and \cmdname{pdftex} are now generated by the new program + \cmdname{updmap} and installed into \dirname{texmf/fonts/map}. +\item \TeX{}, \MF{}, and \MP{} now, by default, output most input + characters (32 and above) as themselves in output (e.g., + \verb|\write|) files, + log files, and the terminal, i.e., \emph{not} translated using the + \verb|^^| notation. In \TL{}~7, this translation was + dependent on the system locale settings; now, locale settings do + not influence the \TeX{} programs' behavior. If for some reason + you need the \verb|^^| output, rename the file + \verb|texmf/web2c/cp8bit.tcx|. (Future releases will have cleaner + ways to control this.) +\item This documentation was substantially revised. +\item Finally, since the edition numbers had grown unwieldy, + the version is now simply identified by the year: \TL{} 2003. +\end{itemize*} + + +\subsubsection{2004} + +2004 saw many changes: + +\begin{itemize} + +\item If you have locally-installed fonts which use their own +\filename{.map} or (much less likely) \filename{.enc} support files, you +may need to move those support files. + +\filename{.map} files are now searched for in subdirectories of +\dirname{fonts/map} only (in each \filename{texmf} tree), along the +\envname{TEXFONTMAPS} path. Similarly, \filename{.enc} files are now +searched for in subdirectories of \dirname{fonts/enc} only, along the +\envname{ENCFONTS} path. \cmdname{updmap} will attempt to warn about +problematic files. + +For methods of handling this and other information, please see +\url{http://tug.org/texlive/mapenc.html}. + +\item The \TK\ has been expanded with the addition of a \MIKTEX-based +installable \CD, for those who prefer that implementation to Web2C. +See section~\ref{sec:overview-tl} (\p.\pageref{sec:overview-tl}). + +\item Within \TL, the single large \dirname{texmf} tree of previous +releases has been replaced by three: \dirname{texmf}, +\dirname{texmf-dist}, and \dirname{texmf-doc}. See +section~\ref{sec:tld} (\p.\pageref{sec:tld}), and the \filename{README} +files for each. + +\item All \TeX-related input files are now collected in +the \dirname{tex} subdirectory of \dirname{texmf*} trees, rather than +having separate sibling directories \dirname{tex}, \dirname{etex}, +\dirname{pdftex}, \dirname{pdfetex}, etc. See +\CDref{texmf-doc/doc/english/tds/tds.html\#Extensions} +{\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}. + +\item Helper scripts (not meant to be invoked by users) are now located +in a new \dirname{scripts} directory of \dirname{texmf*} trees, and +searched for via \verb|kpsewhich -format=texmfscripts|. So if you have +programs which call such scripts, they'll need to be adjusted. See +\CDref{texmf-doc/doc/english/tds/tds.html\#Scripts} +{\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}. + +\item Almost all formats leave most characters printable as +themselves via the ``translation file'' \filename{cp227.tcx}, instead of +translating them with the \verb|^^| notation. Specifically, characters +at positions 32--256, plus tab, vertical tab, and form feed are +considered printable and not translated. The exceptions are plain \TeX\ +(only 32--126 printable), \ConTeXt\ (0--255 printable), and the +\OMEGA-related formats. This default behavior is almost the same as in +\TL\,2003, but it's implemented more cleanly, with more possibilities +for customization. See \CDref{texmf/doc/web2c/web2c.html\#TCX-files} +{\texttt{texmf/doc/web2c/web2c.html\#TCX-files}}. +(By the way, with Unicode input, \TeX\ may output partial character +sequences when showing error contexts, since it is byte-oriented.) + +\item \textsf{pdfetex} is now the default engine for all formats +except (plain) \textsf{tex} itself. (Of course it generates \acro{DVI} +when run as \textsf{latex}, etc.) This means, among other things, that +the microtypographic features of \textsf{pdftex} are available in +\LaTeX, \ConTeXt, etc., as well as the \eTeX\ features +(\OnCD{texmf-dist/doc/etex/base/}). + +It also means it's \emph{more important than ever} to use the +\pkgname{ifpdf} package (works with both plain and \LaTeX) or equivalent +code, because simply testing whether \cs{pdfoutput} or some other +primitive is defined is not a reliable way to determine if \acro{PDF} +output is being generated. We made this backward compatible as best we +could this year, but next year, \cs{pdfoutput} may be defined even when +\acro{DVI} is being written. + +\item pdf\TeX\ (\url{http://pdftex.org}) has many new features: + + \begin{itemize*} + + \item \cs{pdfmapfile} and \cs{pdfmapline} provide font map support + from within a document. + + \item Microtypographic font expansion can be used more easily.\\ + \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} + + \item All parameters previously set through the special configuration + file \filename{pdftex.cfg} must now be set through primitives, + typically in \filename{pdftexconfig.tex}; \filename{pdftex.cfg} is no + longer supported. Any extant \filename{.fmt} files must be redumped + when \filename{pdftexconfig.tex} is changed. + + \item See the pdf\TeX\ manual for more: \OnCD{texmf-dist/doc/pdftex/manual/pdftex-a.pdf}. + + \end{itemize*} + +\item The \cs{input} primitive in \cmdname{tex} (and \cmdname{mf} and +\cmdname{mpost}) now accepts double quotes containing spaces and other +special characters. Typical examples: +\begin{verbatim} +\input "filename with spaces" % plain +\input{"filename with spaces"} % latex +\end{verbatim} +See the Web2C manual for more: \OnCD{texmf/doc/web2c}. + +\item enc\TeX\ support is now included within Web2C and consequently all +\TeX\ programs, via the \optname{-enc} option\Dash \emph{only when +formats are built}. enc\TeX\ supports general re-encoding of input and +output, enabling full support of Unicode (in \acro{UTF}-8). See +\OnCD{texmf-dist/doc/generic/enctex/} and +\url{http://www.olsak.net/enctex.html}. + +\item Aleph, a new engine combining \eTeX\ and \OMEGA, is available. +A little information is available in \OnCD{texmf-dist/doc/aleph/base} +and \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph}. The +\LaTeX-based format for Aleph is named \textsf{lamed}. + +\item The latest \LaTeX\ release has a new version of the +\acro{LPPL}\Dash now officially a Debian-approved license. Assorted +other updates, see the \filename{ltnews} files in +\OnCD{texmf-dist/doc/latex/base}. + +\item \cmdname{dvipng}, a new program for converting \acro{DVI} to +\acro{PNG} image files, is included. See \OnCD{texmf/doc/man/man1/dvipng.1}. + +\item We reduced the \pkgname{cbgreek} package to a ``medium'' sized set +of fonts, with the assent and advice of the author (Claudio Beccari). +The excised fonts are the invisible, outline, and transparency ones, +which are relatively rarely used, and we needed the space. The full set +is of course available from \acro{CTAN} +(\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). + +\item \cmdname{oxdvi} has been removed; just use \cmdname{xdvi}. + +\item The \cmdname{ini} and \cmdname{vir} commands (links) for +\cmdname{tex}, \cmdname{mf}, and \cmdname{mpost} are no longer created, +such as \cmdname{initex}. The \cmdname{ini} functionality has been +available through the command-line option \optname{-ini} for years now. + +\item \textsf{i386-openbsd} platform support was removed. Since the +\pkgname{tetex} package in the \acro{BSD} Ports system is available, and +\acro{GNU/}Linux and Free\acro{BSD} binaries were available, it seemed +volunteer time could be better spent elsewhere. + +\item On \textsf{sparc-solaris} (at least), you may have to set the +\envname{LD\_LIBRARY\_PATH} environment variable to run the +\pkgname{t1utils} programs. This is because they are compiled with C++, +and there is no standard location for the runtime libraries. (This is +not new in 2004, but wasn't previously documented.) Similarly, on +\textsf{mips-irix}, the \acro{MIPS}pro 7.4 runtimes are required. + +\end{itemize} + +\subsubsection{2005} + +2005 saw the usual huge number of updates to packages and programs. +The infrastructure stayed relatively stable from 2004, but inevitably +there were some changes there as well: + +\begin{itemize} + +\item New scripts \cmdname{texconfig-sys}, \cmdname{updmap-sys}, and + \cmdname{fmtutil-sys} were introduced, which modify the + configuration in the system trees. The \cmdname{texconfig}, + \cmdname{updmap}, and \cmdname{fmtutil} scripts now modify + user-specific files, under \dirname{$HOME/.texlive2005}. + +\item Corresponding new variables \envname{TEXMFCONFIG} and + \envname{TEXMFSYSCONFIG} to specify the trees where configuration + files (user or system, respectively) are found. Thus, you may + need to move personal versions of \filename{fmtutil.cnf} and + \filename{updmap.cfg} to these places; another option is to + redefine \envname{TEXMFCONFIG} or \envname{TEXMFSYSCONFIG} in + \filename{texmf.cnf}. In any case the real location of these files + and the values of \envname{TEXMFCONFIG} and \envname{TEXMFSYSCONFIG} + must agree. + See section~\ref{sec:texmftrees}, \p.\pageref{sec:texmftrees}. + +\item Last year, we kept \verb|\pdfoutput| and other primitives undefined + for \dvi\ output, even though the \cmdname{pdfetex} program was + being used. This year, as promised, we undid that compatibility + measure. So if your document uses \verb|\ifx\pdfoutput\undefined| + to test if PDF is being output, it will need to be changed. You + can use the package \pkgname{ifpdf.sty} (which works under both + plain \TeX\ and \LaTeX) to do this, or steal its logic. + +\item Last year, we changed most formats to output (8-bit) characters as + themselves (see previous section). The new TCX file + \filename{empty.tcx} now provides an easier way to get the + original \verb|^^| notation if you so desire, as in: +\begin{verbatim} +latex --translate-file=empty.tcx yourfile.tex +\end{verbatim} + +\item The new program \cmdname{dvipdfmx} is included for translation of + DVI to PDF; this is an actively maintained update of + \cmdname{dvipdfm} (which is also still available for now, though + no longer recommended). + +\item The new programs \cmdname{pdfopen} and \cmdname{pdfclose} are included + to allow reloading of pdf files in the Adobe Acrobat Reader without + restarting the program. (Other pdf readers, notably \cmdname{xpdf}, + \cmdname{gv}, and \cmdname{gsview}, have never suffered from this + problem.) + +\item For consistency, the variables \envname{HOMETEXMF} and + \envname{VARTEXMF} have been renamed to \envname{TEXMFHOME} and + \envname{TEXMFSYSVAR}, respectively. There is also + \envname{TEXMFVAR}, which is by default user-specific. See the + first point above. + +\end{itemize} + + +\subsubsection{2006--2007} + +In 2006--2007, the major new addition to \TL{} was the \XeTeX{} program, +available as the \texttt{xetex} and \texttt{xelatex} programs; see +\url{http://scripts.sil.org/xetex}. + +MetaPost also received a notable update, with more planned for the +future (\url{http://tug.org/metapost/articles}), likewise pdf\TeX{} +(\url{http://tug.org/applications/pdftex}). + +The \TeX\ \filename{.fmt} (high-speed format) and the similar files for +MetaPost and \MF\ are now stored in subdirectories of \dirname{texmf/web2c}, +instead of in the directory itself (although the directory is still +searched, for the sake of existing \filename{.fmt}'s). The +subdirectories are named for the `engine' in use, such as \filename{tex} +or \filename{pdftex} or \filename{xetex}. This change should be +invisible in normal use. + +The (plain) \texttt{tex} program no longer reads \texttt{\%\&} first +lines to determine what format to run; it is the pure Knuthian \TeX. +(\LaTeX\ and everything else do still read \texttt{\%\&} lines). + +Of course the year also saw (the usual) hundreds of other updates to +packages and programs. As usual, please check \acro{CTAN} +(\url{http://www.ctan.org}) for updates. + +Internally, the source tree is now stored in Subversion, with a standard +web interface for viewing the tree, as linked from our home page. +Although not visible in the final distribution, we expect this will +provide a stable development foundation for future years. + +Finally, in May 2006 Thomas Esser announced that he would no longer be +updating te\TeX{} (\url{http://tug.org/tetex}). As a result, there was +been a surge of interest in \TL{}, especially among \GNU/Linux +distributors. (There is a new \texttt{tetex} installation scheme in +\TL{}, which provides an approximate equivalent.) We hope this will +eventually translate to improvements in the \TeX\ environment for +everyone. + +\medskip \noindent +Final note on the past: all releases of \TL{}, along with ancillary +material such as \CD\ labels, are available at +\url{ftp://tug.org/historic/systems/texlive}. + +\htmlanchor{news} +\subsection{Present} +\label{sec:tlcurrent} + +In 2008, the entire \TL{} infrastructure was redesigned and +reimplemented. Complete information about an installation is now stored +in a plain text file \filename{tlpkg/texlive.tlpdb}. + +Among other things, this finally makes possible upgrading a \TL{} +installation over the Internet after the initial installation, a feature +MiK\TeX\ has provided for many years. We expect to regularly update new +packages as they are released to \CTAN. + +The major new engine Lua\TeX\ (\url{http://luatex.org}) is included; +besides a new level of flexibility in typesetting, this provides an +excellent scripting language for use both inside and outside of \TeX\ +documents. + +Support among Windows and the Unix-based platforms is now much more +uniform. In particular, most Perl and Lua scripts are now available on +Windows, using the Perl internally distributed with \TL. + +The new \cmdname{tlmgr} script (section~\ref{sec:tlmgr}) is the +general interface for managing \TL{} after the initial installation. +It handles package updates and consequent regeneration of formats, map +files, and language files, optionally including local additions. + +With the advent of \cmdname{tlmgr}, the \cmdname{texconfig} actions to +edit the format and hyphenation configuration files are now disabled. + +The \cmdname{xindy} indexing program +(\url{http://xindy.sourceforge.net/}) is now included on most platforms. + +The \cmdname{kpsewhich} tool can now report all matches for a given file +(option \optname{--all}) and limit matches to a given subdirectory +(option \optname{--subdir}). + +The \cmdname{dvipdfmx} program now includes functionality to extract +bounding box information, via the command name \cmdname{extractbb}; this +was one of the last features provided by \cmdname{dvipdfm} not in +\cmdname{dvipdfmx}. + +The font aliases \filename{Times-Roman}, \filename{Helvetica}, and so on +have been removed. Different packages expected them to behave +differently (in particular, to have different encodings), and there was +no good way to resolve this. + +The \pkgname{platex} format has been removed, to resolve a name conflict +with a completely different Japanese \pkgname{platex}; the +\pkgname{polski} package is now the main Polish support. + +Internally, the \web\ string pool files are now compiled into the +binaries, to ease upgrades. + +Finally, the changes made by Donald Knuth in his `\TeX\ tuneup of 2008' +are included in this release. See +\url{http://tug.org/TUGboat/Articles/tb29-2/tb92knut.pdf}. + + +\subsection{Future} + +\emph{\TL{} is not perfect!} (And never will be.) We intend to +continue to release new versions, and would like to provide more help +material, more utilities, more installation programs, and (of course) an +ever-improved and better-checked tree of macros and fonts. This work is +all done by hard-pressed volunteers in their limited spare time, and a +great deal remains to be done. Please see +\url{http://tug.org/texlive/contribute.html}. + +Please send corrections, suggestions, and offers of help to: +\begin{quote} +\email{tex-live@tug.org} \\ +\url{http://tug.org/texlive} +\end{quote} + +\medskip +\noindent \textsl{Happy \TeX ing!} + +\end{document} diff --git a/Master/texmf/doc/texlive/source/texlive-fr/Makefile b/Master/texmf/doc/texlive/source/texlive-fr/Makefile new file mode 100644 index 00000000000..519abf8798a --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-fr/Makefile @@ -0,0 +1,5 @@ +include ../texlive-en/Makefile +doc = texlive-fr +lang = french + + diff --git a/Master/texmf/doc/texlive/source/texlive-fr/live.tex b/Master/texmf/doc/texlive/source/texlive-fr/live.tex new file mode 100644 index 00000000000..ccb25a86f0b --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-fr/live.tex @@ -0,0 +1,3945 @@ +%Format: pdf + +% $Id: //depot/Master/texmf-doc/source/english/texlive-en/live.tex#31 $ +% $Author: staw $ $Date: 2005/10/31 $ +% +% Change history (started May 18th 2002) +% 2007/01/18: synced with 2007 English version, by Daniel Flipo +% 2005/11/01: synced with 2005 English version, by Daniel Flipo +% 2005/05/05: re-added section on building binaries (Daniel Flipo) +% 2004/10/28: synced with 2004 English version, by Daniel Flipo +% 2003/08/28: synced with 2003 English version, by Éric Picheral and Jacques André +% 2002/05/25: proof-reading and corrections, by Daniel Flipo +% 2002/05/18: synced with English version, by Fabrice +% +\documentclass{article} +%\let\tldocenglish=1 % *NOT* for French + +\usepackage[latin1]{inputenc} + +\usepackage{caption} +\DeclareCaptionLabelSeparator{endash}{\space\textendash\space} +\captionsetup{labelsep=endash} + +\usepackage[frenchb]{babel} +\usepackage{xspace} +\addto\captionsfrench{\def\figurename{{\scshape Figure}}} +\addto\captionsfrench{\def\tablename{{\scshape Table}}} +\AddThinSpaceBeforeFootnotes +\FrenchFootnotes +\NoAutoSpaceBeforeFDP + +\newcommand{\THANH}{Hàn Th\'{ê} Thanh} + +\usepackage{comment} + +\usepackage{ifpdf} +% tex-live.sty suppose \hyper@linkurl défini... +\ifpdf + \def\Status{1} % (df) Pour faire charger hyperref dans tex-live.sty +\else + \makeatletter + \def\hyper@linkurl#1#2{#2} % undefined if hyperref.sty not loaded + \makeatother +\fi + +\usepackage{tex-live} +%%%% Ajout J.A. à garder +\newcommand{\CDdemo}{\acro{CD} \pkgname{demo}\xspace} +\newcommand{\CDinst}{\acro{CD} \pkgname{inst}\xspace} +\newcommand{\DVDlive}{\acro{DVD} \pkgname{live}\xspace} +\renewcommand{\samp}[1]{\og \texttt{#1}\fg{}} + +%%%% Ajout (df) +% Alias +\let\XemTeX\XEmTeX +% (df) La commande \TeXLive n'est pas utilisée en v.f. +\renewcommand{\TL}{\TeX{} Live\xspace}% Robuste (pas besoin de \protect)... +% tex-live.sty fait précéder les no de page d'une fine... si on veut +% une insécable normale, décommenter la ligne suivante : +\def\p.{p.~} +% Chez Karl, la commande \url{} ne protège pas les caractères actifs (:?), +% d'où ceci (essai provisoire... erreurs avec le car. #) : +%\let\urlORI\url +%\renewcommand*{\url}[1]{\foreignlanguage{english}{\urlORI{#1}}} +%\renewcommand*{\url}[1]{{\shorthandoff{:?!;}\urlORI{#1}}} +% La commande \path de url.sty ajoute des espaces parasites, pas \url, d'où +\let\path\url +% mais ceci impose de remplacer \path|...| par \path{...}, et les \$ inclus +% par des $. + +\setlength{\parindent}{0mm} +\addtolength{\parskip}{.25\baselineskip} + +\begin{document} + +\title{{\huge Guide pratique de \TL{}} \\ \strut + {\LARGE\textsf{\TK{} 2007}} + } + +\author{Karl Berry \\[3mm] + \url{http://tug.org/texlive/}\\[5mm] + \textit{Version française}\\[3mm] + Daniel Flipo (GUTenberg) + } + +\date{Janvier 2007} + +\maketitle +\thispagestyle{empty} % no need for page number + +\newpage +\begin{multicols}{2} +\tableofcontents +\listoftables +\end{multicols} + +\section{Introduction} +\label{sec:intro} + +Ce document décrit les principales caractéristiques de la +distribution \TL{}, une distribution de \TeX{} et \LaTeX{} +pour Linux et autres Unix, \MacOSX{} et systèmes Windows 32 bits +(attention, cette distribution n'est pas vraiment utilisable avec +les anciens systèmes Mac ou \acro{MS-DOS}). Elle comprend les binaires +pré-compilés de \TeX{}, \LaTeXe{}, \MF, \MP, \BibTeX{} et de nombreux +autres programmes ainsi qu'une bibliothèque étendue de macros, de +fontes et de documentations. Elle traite aussi la composition de textes +qui utilisent plusieurs systèmes d'écritures différentes venant de toute +la surface du globe. +La distribution \TL{} est en fait un sous-ensemble de \TK{} (décrit brièvement +à la section ~\ref{sec:struct-tl}, \p.\pageref{sec:struct-tl}) +produit grâce aux efforts combinés des différents groupes d'utilisateurs +de \TeX. + +L'édition 2007 a été figée en janvier 2007. +Les futures mises à jour des composants de la distribution 2007 +seront disponibles au fur et à mesure de leur parution sur le site +\acro{CTAN}, \url{http://www.ctan.org}. + +On trouvera à la fin du document, section~\ref{sec:history} +(\p.\pageref{sec:history}), un bref historique des principales modifications +apportées au fil du temps à la distribution \TL. + +Les utilisateurs des éditions précédentes de \TL{} sont invités +à lire, \emph{avant toute mise à jour}, la section~\ref{tlcurrent} +\p.\pageref{tlcurrent} qui présente les principaux changements intervenus +cette année. + + +\subsection{Utilisation élémentaire de \TL{}} +\label{sec:basic} + +Vous pouvez utiliser \TL{} de trois façons différentes : +\begin{enumerate} +\item Vous pouvez exécuter \TL{} directement depuis le + \DVDlive{} (toutes plates-formes). + Cela prend très peu d'espace disque et + donne un accès immédiat à tout le contenu de + \TL. C'est une solution parfaitement acceptable même si les + performances obtenues sont moins bonnes que si \TL{} était + lancé depuis un disque local. +\item Vous pouvez installer tout ou partie de \TL{} sur un disque + local. C'est l'utilisation la plus fréquente de \TL{}. + Ceci peut se faire à partir du \DVDlive{} ou de l'un des \CD de la + distribution (voir section~\ref{sec:multiple-dist}, + \p.\pageref{sec:multiple-dist}). + Il faut disposer d'un minimum de 120\,Mo, mais on recommande au moins +%(df) un peu mensonger... schéma GUT = 800 Mo chez moi ! + 400\,Mo pour un système standard ou 800\,Mo pour un système complet. +\item Vous pouvez incorporer un jeu de composants particulier ou une + collection dans un système \TeX{} déjà présent, soit un + système \TL{} installé précédemment, soit un système \TeX{} différent. +\end{enumerate} + +Ces trois utilisations sont décrites en détail dans les sections +concernant l'installation spécifique à chaque système. +Quelques remarques générales : + +\begin{itemize} + +\item Le script d'installation globale pour Unix et pour \MacOSX{} s'appelle +\texttt{install-tl.sh}. +Les utilisateurs de Linux peuvent aussi essayer le nouvel installeur +\texttt{setuptl/tlpmgui} développé au départ pour Windows et adapté à Linux. +Consulter la section \ref{sec:win-install} p.~\pageref{sec:win-install} pour +plus d'informations. + +\item Pour installer une extension ou une collection, on utilise le script + d'installation \texttt{install-pkg.sh}. +Après une installation faite à l'aide de \texttt{tlpmgui}, il est possible +d'utiliser \texttt{tlpmgui} pour ajouter ou supprimer des extensions ou des +collections. + +\item Le programme d'installation pour Windows s'appelle + \cmdname{tlpmgui.exe}, il sert aussi à ajouter ou supprimer des composants + dans une installation existante (voir section~\ref{sec:win-install}). + +\end{itemize} + +\subsection{Obtenir de l'aide} +\label{sec:help} + +La communauté \TeX{} est à la fois active et conviviale ; pratiquement +toute question sérieuse finit par obtenir une réponse. Le support est +pourtant informel, assuré par des volontaires et des lecteurs +occasionnels, aussi est-il particulièrement important que vous fassiez +votre propre travail de recherche avant de poser la question (si vous +préférez un support commercial, vous pouvez renoncer à \TL{} et +acheter un système payant ; voir une liste à +\url{http://tug.org/interest.html#vendors}). + +Voici une liste de ressources, classées selon l'ordre dans lequel nous +recommandons de les utiliser : + +\begin{description} +\item [Getting Started] Pour ceux qui débutent en \TeX, la page web +\url{http://tug.org/begin.html} contient une courte description +du système. + +\item [\acro{FAQ} \TeX{}] La \acro{FAQ} \TeX{} est un vaste recueil + de réponses à toutes sortes de questions, de la plus élémentaire à la + plus complexe. Elle est enregistrée sur le \DVDlive{} dans + \OnCD{texmf-doc/doc/english/FAQ-en} + et elle est disponible sur Internet à + l'adresse \url{http://www.tex.ac.uk/faq}. + Merci de consulter cette FAQ avant toute question. + +\item [Catalogue \TeX{}] Si vous recherchez une extension, une fonte, + un programme, ... particuliers, il faut examiner le catalogue + \TeX{}. C'est une importante liste de tous les éléments relatifs à + \TeX{}. Voir \OnCD{texmf-doc/doc/english/catalogue} sur le \DVDlive{}, + ou \url{http://www.ctan.org/tex-archive/help/Catalogue}. + +\item [Ressources \TeX{} sur le Web ] La page web + \url{http://tug.org/interest.html} propose + beaucoup de liens relatifs à \TeX{}, en particulier concernant des + livres, manuels et articles portant sur tous les aspects du système. + +\item [Archives des forums d'aide] Les principaux forums dédiés + au support de \TeX{} sont les groupes de news Usenet + \url{news:comp.text.tex} (en anglais) et \url{news:fr.comp.text.tex} + (en français) ainsi que les listes de diffusion + \email{texhax@tug.org} (en anglais) et \email{gut@ens.fr} (en français). + Les archives correspondantes contiennent des + milliers de questions et réponses déjà traitées et permettent + une recherche fructueuse. Voir + \url{http://groups.google.com/groups?group=comp.text.tex} + et \url{http://tug.org/mail-archives/texhax}, respectivement. Une + question posée sur un moteur de recherche, tel que + \url{http://google.com}, peut aussi fournir des réponses pertinentes. + +\item [Poster une question] Si vous n'obtenez pas de réponse, vous + pouvez poster la question à \dirname{comp.text.tex} via Google ou + votre lecteur de news, ou encore par messagerie à + \email{texhax@tug.org}. Mais avant de le faire, merci de lire + l'introduction de la \acro{FAQ} donnant les conseils sur la façon de + rédiger la question pour avoir des chances d'obtenir une réponse : + \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. + +\item [Support de \TL{}] Si vous voulez faire un rapport + d'anomalie, émettre des suggestions ou des commentaires sur la + distribution \TL{}, l'installation ou la documentation, utilisez + la liste de diffusion \email{tex-live@tug.org}. Mais attention, si + la question concerne l'utilisation d'un programme particulier inclus + dans \TL{}, il vaut mieux que vous écriviez directement à la + personne ou à la liste de diffusion qui maintient le programme. + +\end{description} + +L'autre aspect du sujet concerne l'aide à apporter aux personnes +soumettant des questions. Les forums \dirname{comp.text.tex}, +\dirname{fr.comp.text.tex} ainsi que les listes de diffusion \code{texhax} +et \code{gut} +sont ouverts à tous, aussi n'hésitez pas à vous y joindre, à commencer +la lecture et à fournir de l'aide là où cela vous est possible. +Bienvenue dans le monde \TeX{} ! + +% No \protect needed as \TL is defined in French with \newcommand (robust). +\section{Structure de \TL} +\label{sec:struct-tl} + +Nous décrivons ici la structure et le contenu de \TL{} et +de \TK{} qui est un sur-ensemble de \TL. + +\subsection {Distributions multiples : \protect\pkgname{live}, + \protect\pkgname{inst}, \protect\pkgname{protext}} +\label{sec:multiple-dist} + +Des limitations d'espace liées au format des \acro{CD-ROM} nous ont contraint +à diviser \TK{} en plusieurs distributions : + +\begin{description} + +\item [live] Un système exécutable complet sur \acro{DVD} ; il est + trop volumineux pour tenir sur \acro{CD-ROM}. Le \DVD{} contient + aussi une image du système \CTAN{}, totalement indépendant de + \TL{}, la distribution Mac\TeX{} pour \MacOSX, la distribution \ProTeXt{} + pour Windows, ainsi que d'autres extensions + réunies dans un répertoire \texttt{texmf-extra}. + + Les droits d'utilisation des fichiers présents dans \CTAN, \ProTeXt, + Mac\TeX{} et \texttt{texmf-extra} diffèrent de ceux de \TL{}, pensez à lire + les licences si vous envisagez de modifier ou de redistribuer certains de + ces fichiers. + +\item [inst\textrm{(allable)}] Un système complet sur \CD{} pour les Unix + (dont Linux et \MacOSX{}) ; pour le faire + tenir sur le \CD, il a fallu compresser tout ce que nous avons + pu. Du coup, il n'est pas possible d'exécuter directement \TeX\ + depuis le \CD\ d'installation, il vous faut l'installer sur disque + (d'où le nom). L'installation est décrite dans les sections + concernées (\ref{sec:unix-install-disk} et \ref{sec:osx-unix-inst} + pour \MacOSX). + +\item [protext] Une extension du système \MIKTEX\ sur \CD{} pour + Windows. Cette distribution est totalement indépendante du \TL{}, + elle nécessite un mode d'installation spécifique. + Elle peut être installée sur disque ou exécutée directement + depuis le \CD. Le site de \ProTeXt\ se trouve ici : + \url{http://tug.org/protext}. + + \pkgname{protext} est fourni à la fois sur le \DVDlive{} et + sur un \CD{} spécifique pour ceux qui n'ont pas de lecteur de \DVD. + +\end{description} + +\noindent On peut déterminer la nature de la distribution +utilisée en recherchant le fichier \texttt{00\var{type}.TL} dans le +répertoire racine du médium utilisé (\CD{} ou \DVD{}). +Ce fichier contient aussi la date de dernière mise à jour du \TL. + +%(df) Que fait GUT ? +%Naturally, each user group chooses what to distribute, at its own +%discretion. + +\subsection{Répertoires situés à la racine} +\label{sec:tld} + +Les répertoires les plus importants situés à la racine +% (df) bin et source ne sont pas sur \CDinst +du \DVDlive{} +sont énumérés ci-dessous. Cette année, la distribution \TL{} +est dans un sous-répertoire \dirname{texlive2007} et non à la racine. +%%% (df) confus : on parle du CD ou du DVD +\smallskip +\begingroup + \renewcommand{\arraystretch}{1.3} % open up interrow spacing +\begin{tabular}{>{\ttfamily}lp{.78\hsize}} +% (df) bin pas présent sur \CDinst : les .zip des binaires sont dans 'archive' +bin & Programmes de la famille \TeX{}, rangés dans des + sous-répertoires selon les plates-formes. \\ +% pas sur \CDinst +source & Le code source de tous les programmes, incluant la + distribution \Webc{} de \TeX{} et \MF{}. Il s'agit d'une archive au + format \texttt{tar}, compressée par bzip2. + % Ajout (df) + Faute de place, le répertoire \texttt{source} + n'est pas sur le \CDinst{} (seulement sur le \DVDlive{}).\\ +setuptl & Programmes d'installation pour Windows et Linux. \\ +support & Ensemble d'extensions et programmes auxiliaires. Ils ne + sont \emph{pas} installés par défaut. +% Faux (df) +% On y trouve \cmdname{Ghostscript}, \cmdname{netpbm} et un ensemble +% d'éditeurs orientés \TeX{}. +\\ +texmf & Répertoire contenant les programmes et leur documentation. + Ne contient ni les formats ni les extensions + (appelé \envname{TEXMFMAIN} dans la section suivante.) \\ +texmf-dist & Répertoire principal où se trouvent les extensions, + les fontes, etc., avec leur documentation + (appelé \envname{TEXMFDIST} dans la section suivante.) \\ +texmf-doc & Répertoire contenant le reste de la documentation, + le sous-répertoire doc est organisé par langue. \\ +texmf-var & Répertoire contenant les fichiers générés automatiquement + (appelé \envname{TEXMFSYSVAR} dans la section suivante.) \\ +\end{tabular} +\endgroup + +\smallskip + +Le répertoire \dirname{texmf-doc} ne contient que de la documentation +mais pas toute la documentation. Celle concernant les programmes (manuels, +pages \textit{man} et fichiers de type \textit{info} est dans +\dirname{texmf/doc} car les programmes correspondants sont dans +\dirname{texmf}. De même, la documentation des extensions et formats +est dans \dirname{texmf-dist/doc}. Les commandes \cmdname{texdoc} ou +\cmdname{texdoctk} trouveront pour vous les documentations où quelles soient +sur le disque. % Bof... pas vrai chez moi (df) ? +Le fichier \OnCD{doc.html} du \DVDlive{} contient une liste de liens bien +utiles pour localiser les fichiers de documentation. + +On trouve également, au même niveau que les répertoires mentionnés ci-dessus, +les scripts d'installation et les fichiers \filename{README} (dans +différentes langues). + +\subsection{Description des arborescences texmf utilisées} +\label{sec:texmftrees} + +Nous donnons ici la liste complète des variables prédéfinies qui contiennent +les noms des différentes arborescences de type texmf et l'usage qui en est +fait. La commande \cmdname{texconfig conf} retourne les valeurs de ces +variables, ce qui permet de savoir où se trouvent ces différentes +arborescences dans une installation donnée. + +\begin{ttdescription} +\item [TEXMFMAIN] contient les éléments essentiels du système, comme les + scripts (\cmdname{web2c/mktexdir}, etc.), les fichiers \file{.pool}, + etc. +\item [TEXMFDIST] contient les fichiers de macro (Plain, \LaTeX, \ConTeXt, + etc.,), les fontes, etc., de la distribution \TL. Rien ne devrait être + ni ajouté ni supprimé dans cette arborescence. +\item [TEXMFLOCAL] c'est là que l'administrateur de la machine + place les classes et extensions locales, les fontes non disponibles + dans \TL, etc. +\item [TEXMFHOME] contient les fichiers personnels (extensions, classes, + fontes) de l'utilisateur ; ce répertoire est sous \verb+$HOME+ % $ + par défaut. La variable \envname{TEXINPUTS} ne devrait plus être utilisée. +\item [TEXMFCONFIG] c'est là que les scripts \cmdname{updmap} et + \cmdname{fmtutil} recherchent leurs fichiers de configuration en priorité. + \cmdname{texconfig} y place les versions modifiées des fichiers de + configuration. Sous \verb+$HOME+ par défaut. %$ +\item [TEXMFSYSCONFIG] c'est là que les scripts \cmdname{updmap-sys} et + \cmdname{fmtutil-sys} recherchent leurs fichiers de configuration en + priorité. \cmdname{texconfig-sys} y place les versions modifiées des + fichiers de configuration. +\item [TEXMFVAR] c'est là que les scripts \cmdname{texconfig}, + \cmdname{updmap} et \cmdname{fmtutil} rangent les formats et les fichiers + \file{.map} qu'ils produisent. Sous \verb+$HOME+ par défaut. %$ +\item [TEXMFSYSVAR] c'est là que les scripts \cmdname{texconfig-sys}, + \cmdname{updmap-sys} et \cmdname{fmtutil-sys} rangent les formats et les + fichiers \file{.map} qu'ils produisent. +\end{ttdescription} + +Les possibilités offertes par \cmdname{texconfig} sont décrites à la + section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig}. + + +\subsection{Les extensions de \TeX} +\label{sec:tex-extensions} + +\TL{} contient plusieurs extensions de \TeX{}. + +\begin{description} + +\item [\eTeX{}] \label{text:etex} ajoute un jeu, petit mais puissant, + de nouvelles + primitives et les extensions \TeXXeT{} pour l'écriture de droite + à gauche ; \eTeX{} est, en mode normal, 100\% compatible avec + \TeX{} standard. Pour plus de détails consulter le + fichier \OnCD{texmf-dist/doc/etex/base/etex_man.pdf} du \DVDlive{}. + +\item [pdf\TeX{}] inclut les extensions \eTeX{} et produit, au choix, + des fichiers au format Acrobat \acro{PDF} ou au format \dvi{}. + Le manuel d'utilisation se trouve sur le \DVDlive{} + dans \OnCD{texmf/doc/pdftex/manual/}. Le fichier + \OnCD{texmf/doc/pdftex/pdftex/manual/samplepdf/samplepdf.tex}\relax{} + donne un exemple d'utilisation. pdf\TeX{} est le moteur de base + sur lequel sont construits tous les formats autres que plain\TeX. + +\item [Xe\TeX] ajoute la possibilité d'utiliser le codage Unicode en entrée + et les fontes OpenType en sortie, ceci grâce à des bibliothèques + externes : voir \url{http://scripts.sil.org/xetex}. + +\item [\OMEGA{} (Omega)] fonctionne en utilisant Unicode et des + caractères 16 bits, ce qui lui permet de travailler directement et + simultanément avec presque toutes les écritures du monde entier. + L'extension supporte aussi le chargement dynamique d'\acro{OTP} + (\OMEGA{} \emph{Translation Processes}) qui permet à l'utilisateur + d'appliquer sur des flux d'entrée quelconques des transformations + complexes qu'il aura lui-même définies. Voir la documentation + (pas vraiment à jour) dans \OnCD{texmf-dist/doc/omega/base/doc-1.8.tex}. + +\item [Aleph] combine les fonctionnalités de \OMEGA\ et de \eTeX. + \OnCD{texmf-dist/doc/aleph/base} contient une documentation de base. + +\end{description} + +\subsection{Quelques autres programmes intéressants + dans \TL} + +Voici quelques autres programmes couramment utilisés et présents dans +\TL{} : + +\begin{cmddescription} + +\item [bibtex] Traitement de la bibliographie. + +\item [makeindex] Traitement des index. + +\item [dvips] Conversion \dvi{} vers \PS{}. + +\item [xdvi] Visualisation \dvi{} pour le système X Window. + +\item [dvilj] Pilote \dvi{} pour les imprimantes HP LaserJet. + +\item [dv2dt, dt2dv] Conversion \dvi{} vers ou depuis du texte simple. + +\item [dviconcat, dviselect] Couper/Coller de pages à partir de fichiers + \dvi{}. + +\item [dvipdfmx] Conversion \dvi{} vers \acro{PDF}, une autre approche que + celle de pdf\TeX\ (mentionné ci-dessus). Voir les extensions + \pkgname{ps4pdf} et \pkgname{pdftricks} pour d'autres alternatives. + +\item [psselect, psnup, \ldots] Utilitaires \PS{}. + +\item [lacheck] Vérification de syntaxe \LaTeX{}. + +\item [texexec] Processeur Con\TeX{}t et \acro{PDF}. + +\item [tex4ht] Conversion \TeX{} vers \acro{HTML}. + +\end{cmddescription} + + +\section{Utilisation sous Unix} +\label{sec:unix-install} + +Comme on l'a vu en section~\ref{sec:basic} \p.\pageref{sec:basic}, +le \TL{} peut être utilisé de trois façons principales : + +\begin{enumerate} +\item Exécution directe depuis le \DVDlive. +\item Installation sur le disque dur. +\item Intégration d'un jeu de composants ou collections dans un système +\TeX{} déjà installé. +\end{enumerate} + +\noindent +Les procédures spécifiques à Unix sont décrites pour chacun de ces cas +dans les sections qui suivent. + +\ifSingleColumn \begin{figure}[ht]\noindent \fi +\begin{warningbox} + \textbf{ATTENTION : } Les \CD{} et le \DVD{} sont au format ISO~9660 + (High Sierra), avec les extensions \og Rock Ridge\fg{} (et \og Joliet\fg{} + pour Windows). Votre système doit pouvoir reconnaître les + extensions \og Rock Ridge\fg{} pour une utilisation optimale de + \TL{}. Consultez votre documentation concernant la commande + \cmdname{mount} pour voir si c'est le cas. Si votre réseau local est + constitué de machines différentes, regardez + si vous pouvez monter les \CD{} sur une machine qui supporte + Rock Ridge et utiliser ce point de montage pour les autres machines. + +\leavevmode\quad +L'utilisation des \CD{} sur les systèmes modernes +ne devrait pas poser de problèmes. S'il y en avait, n'hésitez pas à +nous le faire savoir. +La suite de ce document suppose que vous avez installé et monté les + \CD{} avec une compatibilité Rock Ridge parfaite. +\end{warningbox} + +\ifSingleColumn\end{figure}\fi + +N.B. : les droits de \og root \fg{} sont souvent requis pour monter le \CD{}. +D'autre part, selon le type d'Unix utilisé, il vous faudra probablement +connaître le mot de passe de \og root \fg{} ou tout au moins utiliser la +commande \cmdname{sudo} pour effectuer l'installation (le droit +d'écriture sur le(s) répertoire(s) d'installation est évidemment +indispensable). Cette remarque concerne particulièrement les utilisateurs de +\MacOSX{} à qui nous recommandons de prendre d'abord connaissance de la +section~\ref{sec:mac-install} avant toute installation. + + +\subsection{Utiliser \TL{} à partir du \DVDlive} + +La liste des architectures sur lesquelles fonctionne \TL{} est donnée +page~\pageref{tab:archlist} (table~\ref{tab:archlist}). + +\def\runlive{% text repeated in windows section +On peut utiliser le système \TeX{} directement depuis \DVDlive, +sans l'installer sur le disque dur (d'où en fait le nom \TL). +Il \emph{n'est pas possible} de faire tourner \TeX{} directement +depuis le \CDinst{} (voir section~\ref{sec:multiple-dist}, +page~\pageref{sec:multiple-dist}). +}% fin \runlive + +\def\startinst{% repeated in other subsections +Pour démarrer, il faut d'abord \og monter \fg{} le médium avec les +extensions Rock Ridge. +La commande exacte varie d'un système à l'autre ; la commande suivante +fonctionne sous Linux, mais les noms du périphérique (ici +\filename{/dev/cdrom}) et du point de montage (ici \dirname{/mnt/cdrom}) +peuvent changer. +\\ N.B. Tous nos exemples utilisent \texttt{>} pour les lignes de +commandes \textit{(shell prompt)} ; les commandes de l'utilisateur sont +\underline{soulignées}. +\begin{alltt} +> \Ucom{mount -t iso9660 /dev/cdrom /mnt/cdrom} +\end{alltt} + +\noindent Se placer au point de montage du lecteur : +\begin{alltt} +> \Ucom{cd /mnt/cdrom} +\end{alltt} +}% fin startinst + +\def\installtlsh{% repeated in other subsections +Lancer le script \filename{install-tl.sh} : +\begin{alltt} +> \Ucom{sh install-tl.sh}\\ +Welcome to TeX Live... +\end{alltt} + +\noindent Après l'affichage de divers messages de bienvenue et une liste des +options du menu principal, l'installation réclame l'entrée d'une commande. +Taper alors le caractère voulu suivi d'un retour-chariot. Ne pas taper les +chevrons (ni \texttt{<} ni \texttt{>}) ; on peut utiliser des majuscules ou +des minuscules ; ici, les exemples utilisent des minuscules. +}% fin \installtlsh + +\runlive +\startinst +\installtlsh + +Pour exécuter \pkgname{live}, la première commande est \Ucom{d} +suivie de la sous-commande \Ucom{1} pour choisir le répertoire du disque +local où seront placés les fichiers (tels que les fontes et les formats) que +le système \TeX{} génère lui-même ainsi que les fichiers de configuration si +besoin est. On utilisera \dirname{/opt/texlive2007} dans cet exemple, +mais un utilisateur non privilégié peut très bien choisir un +sous-répertoire non-existant de son répertoire personnel (il sera créé +et ne contiendra donc que du matériel \TL{}). +Étant donné que les fichiers créés ne sont pas toujours compatibles d'une +année sur l'autre, il est recommandé d'inclure l'année dans le nom du +répertoire. +Si la valeur par défaut \dirname{/usr/local/texlive/2007} vous convient +(c.-à-d. que \dirname{/usr/local/texlive/2007} n'est pas un répertoire +existant et que vous avez les droits pour écrire sous \dirname{/usr/local}), +vous pouvez sauter cette étape. +\begin{alltt} +Enter command: \Ucom{d} +Current directories setup: +<1> TEXDIR: /usr/local/texlive/2007 +... +Enter command: \Ucom{1} +New value for TEXDIR [/usr/local/texlive/2007]: \Ucom{/opt/texlive2007} +... +Enter command: \Ucom{r} +\end{alltt} + +Retour au menu principal. La seconde (et dernière) commande est +\Ucom{r} +pour faire tourner \pkgname{live} à partir du \DVD{} sans pour autant +l'installer sur le disque dur : + +\begin{alltt} +Enter command: \Ucom{r} +Preparing destination directories... +... +Welcome to the TeX Live! +> +\end{alltt} + +On se retrouve au niveau de la ligne de commande +comme on vient de le voir. + +Il faut maintenant modifier les deux variables +d'environnement \envname{PATH} et \envname{TEXMFSYSVAR} comme indiqué +à l'écran quelques lignes au dessus de \og Welcome to TeX Live!\fg. +La syntaxe dépend du \textit{shell} utilisé. Les syntaxes +précises sont affichées pour les \textit{shell} de type Bourne ou compatible +(\cmdname{bash}, \cmdname{sh} \cmdname{ksh}, etc.) et pour les +\textit{C~shells} (\cmdname{csh}, \cmdname{tcsh}). +Rappelons qu'il suffit de taper la commande \verb+echo $SHELL+ %$ +pour connaître le nom du \textit{shell} utilisé. +Le plus simple est de recopier par copier-coller, soit les deux lignes +commençant par \og\cmdname{setenv}\fg{} pour les \textit{C~shells}, +soit les trois lignes \og\envname{PATH=}\fg, \og\envname{TEXMFSYSVAR=}\fg, +\og\envname{export ...}\fg{} pour les \textit{shell} de type Bourne +(suivies d'un retour-chariot) dans le terminal de commandes. + +Ceci suffit pour pouvoir utiliser la distribution \TL{} +pendant toute la session. +Pour ne pas avoir à redéfinir \envname{PATH} et \envname{TEXMFSYSVAR} +à chaque nouvelle connexion, il suffit d'entrer les mêmes commandes +à l'aide d'un éditeur dans le fichier d'initialisation du \textit{shell} +(\file{.bash\_profile}, \file{.profile} ou \file{.cshrc} +selon le cas). +L'initialisation se fera ensuite automatiquement au début de chaque nouvelle +session. + +\def\textruntexconfig{% + Une fois l'installation terminée et les variables d'environnement + initialisées, la dernière étape consiste à exécuter \cmdname{texconfig} ou + \cmdname{texconfig-sys} pour éventuellement modifier certains paramètres. + Ceci est expliqué à la section~\ref{sec:texconfig}, + \p.\pageref{sec:texconfig}.% +} +\textruntexconfig + +\def\textifindoubt{% +Passez maintenant à la section~\ref{sec:test-install} pour effectuer +quelques tests de bon fonctionnement. + +En cas de doute, n'hésitez pas à contacter un gourou système pour +vous aider à résoudre vos problèmes, tels que la façon de monter le + médium \TL{}, le choix des répertoires à utiliser ou les modifications +à apporter dans vos fichiers d'initialisation. +}%fin textifindoubt +\textifindoubt + +\subsection{Installer \TL{} sur le disque} +\label{sec:unix-install-disk} + +Il est possible, et même habituel, d'installer le système \TeX{} à +partir du \TL{} sur le disque (\og dur\fg{}). +Ceci peut se faire en utilisant soit le \DVDlive, soit le \CDinst +(voir section~\ref{sec:multiple-dist}, \p.\pageref{sec:multiple-dist} +pour des explications sur les différentes distributions). + +\startinst +\installtlsh + +La table~\ref{tab:main-menu-options} donne la liste des options du menu +principal. On peut choisir les options dans n'importe quel ordre, mais +\Ucom{i} doit être la dernière choisie. Il est cependant raisonnable de +procéder dans l'ordre où elles apparaissent ici ! + +% apparently here.sty [H] doesn't support table*. +\begin{table}[H] +\caption{Options d'installation du menu principal} +\label{tab:main-menu-options} +\begin{tabular}{>{\ttfamily}ll} +p & plate-forme que vous utilisez\\ +b & choix des binaires à installer (architectures multiples)\\ +s & \emph{schéma d'installation} de base + (complet, recommandé, GUTenberg, etc.).\\ +c & modifier le choix des collections individuelles\\ +l & modifier le choix des langues à installer\\ +d & répertoire où faire l'installation\\ +o & autres options\\ +i & lancer l'installation\\ +\end{tabular} +\end{table} + +Voici quelques précisions sur chaque option. + +\begin{description} + +\item[\optname{p} -- Platform (current).] Plate-forme utilisée.\\ +Le script d'installation détecte automatiquement la plate-forme +sur laquelle il tourne, il est en général inutile de modifier cette option, +sauf en cas d'erreur. + +\item[\optname{b} -- Binary architectures.] Binaires pour d'autres +architectures.\\ +Par défaut, seuls les binaires pour votre plate-forme seront installés. À +l'aide de ce menu-ci, il est possible de choisir d'installer aussi les +binaires pour d'autres plates-formes (ou de ne pas installer pour la +plate-forme courante). C'est utile si on partage un arbre \TeX\ +au travers d'un réseau de machines hétérogènes. +La table~\ref{tab:archlist} ci-dessous donne la liste des architectures +pour lesquelles des binaires sont disponibles. + +\begin{table*}[!ht] +%\captionsetup{margin=5mm,justification=centerfirst} +\caption{Les binaires sont disponibles pour les architectures suivantes.} +\label{tab:archlist} +%(df) vérifier la liste finale +\begin{tabular}{>{\hspace*{15mm}\ttfamily}lll} +alpha-linux & HP Alpha GNU/Linux \\ +%alphaev5-osf4.0d & HP Alphaev5 OSF \\ +%hppa2.0-hpux10.20 & HP9000 HPUX 10.20 \\ +i386-darwin & Intel x86 \MacOSX \\ +i386-freebsd & Intel x86 FreeBSD \\ +i386-linux & Intel x86 GNU/Linux \\ +%i386-openbsd3.3 & Intel x86 OpenBSD \\ +%i386-solaris2.8 & Intel x86 Solaris \\ +mips-irix & SGI IRIX \\ +powerpc-aix & IBM RS/6000 AIX \\ +powerpc-darwin & PowerPC \MacOSX \\ +sparc-linux & Sun Sparc GNU/Linux \\ +sparc-solaris & Sun Sparc Solaris \\ +win32 & Windows (32-bit) \\ +x86\_64-linux & Intel x86 64-bit GNU/Linux \\ +% \\ \hline +\end{tabular} +\end{table*} + +\item[\optname{s} -- Base Installation scheme.] +Schéma d'installation de base.\\ +Ce menu permet de choisir un type d'installation plus ou moins complet. +L'option par défaut (\optname{full}) installe tout, c'est un bon choix si +l'espace disque n'est pas limité. Les francophones préféreront peut-être +le schéma \acro{GUT}enberg, mais on peut choisir un ensemble minimal +(\optname{basic}) pour économiser de la place sur le disque. On trouve +aussi des ensembles spécifiques pour Omega ou pour les utilisateurs +d'\acro{XML}. + +\item[\optname{c} -- Individual collections.] Collections individuelles.\\ +Ce menu permet d'ajouter ou de supprimer des collections +parmi celles retenues par le schéma choisi ci-dessus. +Chaque collection\Dash fichiers de macros TeX, familles de fontes Metafont, +etc.\Dash{} est formée de plusieurs composants. +Attention, le programme différencie les lettres minuscules +des lettres capitales pour les touches de sélection. + +\item[\optname{l} -- Language collections.] Collections de langues.\\ +Ce menu fonctionne comme celui de \Ucom{c} pour modifier +le choix des langues à installer. +Attention, le programme différencie les lettres minuscules +des lettres capitales pour les touches de sélection. + +Voici la liste des collections de langues du \TL{} +(on garde ici les noms anglais des options qui sont ceux du système !) : + +% xx really should generate list from texmf/tpm/collection/tex-lang* +% a la install-tl.sh. +\begin{tabbing} +\hspace{.25\linewidth} \= +\hspace{.20\linewidth} \= +\hspace{.20\linewidth} \= +\hspace{.35\linewidth} \kill +African \textit{(qq scripts)} \> +Arabic \> +Armenian \> +Chinese\,Japanese\,Korean \\ +Croatian \> +Cyrillic \> +Czech/Slovak \> +Danish \\ +Dutch \> +Finnish \> +French \> +German \\ +Greek \> +Hebrew \> +Hungarian \> +Indic \\ +Italian \> +Latin \> +Manju \> +Mongolian \\ +Norwegian \> +Polish \> +Portuguese \> +Spanish \\ +Swedish \> +Tibetan \> +\acro{UK} English \> +Vietnamese \\ +\end{tabbing} + +\noindent Les collections de langues comprennent normalement des fontes, +macros, motifs de césure et autres fichiers. Par exemple, +\pkgname{frenchle.sty} est installé lorsqu'on sélectionne la collection +\optname{French}. Par ailleurs, l'installation d'une langue de la collection +modifie le fichier de configuration \filename{language.dat} qui contrôle +quelles divisions (ou coupures de mots) sont chargées. + +\item[\optname{d} -- Installation directories] Choix des +répertoires d'installation.\\ \label{text:instdir} +Ceci concerne les trois répertoires suivants : + +\begin{ttdescription} +\item [TEXDIR] +Répertoire de plus haut niveau sous lequel tout le reste sera installé, +la valeur par défaut est \dirname{/usr/local/texlive/2007}. +Il est conseillé de faire figurer l'année dans le nom choisi, de façon à +pouvoir conserver séparément plusieurs versions de \TL. +L'ajout d'un lien symbolique +\dirname{/usr/local/texlive/current} qui pointe vers la version à utiliser +facilitera grandement le basculement d'une version +à l'autre et le retour à l'ancienne version en cas de problème. + +Sous \MacOSX, les interfaces utilisateurs recherchent \TeX{} +dans \dirname{/usr/local/teTeX} ; plutôt que d'installer la distribution \TL{} +dans ce répertoire, on pourra faire l'installation par défaut +(dans \dirname{/usr/local/texlive/2007} donc) et ajouter deux liens +symboliques : \dirname{current} qui pointe vers \dirname{2007} et +\dirname{teTeX} qui pointe vers \dirname{current}. Pour cela il suffit de +taper les deux commandes suivantes dans un terminal : +\begin{alltt} +> \Ucom{(cd /usr/local/texlive ; ln -s ./2007 ./current)} +> \Ucom{(cd /usr/local ; ln -s ./texlive/current teTeX)} +\end{alltt} + +\item [TEXMFLOCAL] +C'est dans cette arborescence que doivent être placés les fichiers +non fournis par \TL{}. +La valeur par défaut est \dirname{/usr/local/texlive/texmf-local}. +C'est l'endroit recommandé pour y mettre les classes et les fichiers de style +locaux, les fontes (par exemple commerciales) non disponibles +sur \TL{} ainsi que les paramètres de configuration locaux. + +\item [TEXMFSYSVAR] +C'est dans cette arborescence que les scripts \cmdname{texconfig-sys}, +\cmdname{fmtutil-sys}, \cmdname{updmap-sys} installent les fichiers qui +sont spécifiques à la version, notamment les fichiers de format. +La valeur par défaut est \dirname{TEXDIR/texmf-var}, il n'y a en +général aucune raison de la changer. +Les fichiers configuration modifiables par \cmdname{texconfig-sys} (voir +section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig}), comme +\filename{fmtutil.cnf} et \filename{updmap.cfg}, sont eux dans +\envname{TEXMFSYSCONFIG}. +\end{ttdescription} + +\item[\optname{o} -- Other Options.] +Ce menu permet de choisir les options suivantes : + +\begin{ttdescription} +\item [a] Pour spécifier un autre répertoire pour les fontes générées. +La valeur par défaut utilise l'arborescence \envname{TEXMFVAR}, comme on +l'a dit plus haut. +Si vous voulez que l'arborescence principale soit accessible en lecture +uniquement, cette option permet de choisir une autre localisation +(qui doit bien sûr être accessible en lecture-écriture pour tous) +pour ranger les fontes créées dynamiquement. + +\item [l] Pour créer des liens symboliques pour les binaires, +la documentation \textit{(man pages)} ou les fichiers Info \acro{GNU}. +Par exemple, on peut désirer rendre la documentation de type \textit{man} +accessible depuis \dirname{/usr/local/man} et les fichiers Info +depuis \dirname{/usr/local/info} (il faut alors bien sûr avoir les droits +d'écriture dans les répertoires spécifiés). + +En revanche, il est déconseillé d'utiliser cette option pour les binaires. +Rendre les binaires \TL{} accessibles depuis \dirname{/usr/local/bin} +risque de masquer définitivement, y compris pour \textit{root}, les +binaires \TeX\ fournis en standard sur la plate-forme. +Sous Linux par exemple, \textit{root} doit utiliser par défaut les binaires +\teTeX{} fournis avec la distribution installée (Debian, Mandrake, RedHat, +etc.) et non ceux fournis par \TL. + +\item [d] Pour ne pas installer l'arborescence de la documentation +sur les fontes et les macros. Utile pour économiser de l'espace +disque ou bien si la documentation a été installée auparavant à un +autre emplacement. + +\item [s] Pour ne pas installer l'arborescence des fichiers source. +Ceci peut être utile si cette arborescence est commune à +différentes machines ou architectures, (partage par \acro{NFS} ou +\cmdname{automount} par exemple). + +\end{ttdescription} + +\item[\optname{i} -- Perform Installation.] Installer.\\ +Quand les options de configuration sont satisfaisantes, on peut taper +\Ucom{i} pour lancer effectivement l'installation. + +\end{description} + +Lorsque l'installation est terminée, l'étape suivante consiste à inclure dans +la variable \envname{PATH} des usagers (autres que \textit{root} +cf. ci-dessus) le sous-répertoire de \dirname{TEXDIR/bin} spécifique à +l'architecture de façon que les programmes nouvellement installés puissent +être trouvés. Le tableau~\ref{tab:archlist} (page~\pageref{tab:archlist}) +donne la liste des noms des architectures ; on peut aussi lister le contenu de +\dirname{TEXDIR/bin} pour déterminer le nom du sous-répertoire de +\dirname{TEXDIR/bin} à inclure en tête de \envname{PATH}. + +\label{text:path} +La syntaxe de cette commande et le fichier d'initialisation à utiliser +dépendent du système utilisé. Pour un \textit{shell} Bourne ou +compatible (\cmdname{sh}, \cmdname{bash}, \cmdname{ksh}, etc.), il +faut mettre dans le fichier \filename{$HOME/.profile}% %$ +\footnote{Pour les utilisateurs qui possèdent un fichier + \filename{$HOME/.bash_profile}, c'est dans ce dernier qu'il faut redéfinir + la variable \envname{PATH}, car pour eux, \filename{$HOME/.profile} est + sans effet.} +des futurs utilisateurs de \TL{} : +\begin{alltt} +PATH=/\Ucom{\emph{TEXDIR}}/bin/\Ucom{\emph{archname}}:$PATH; export PATH +\end{alltt} + +\noindent +et pour un \textit{C~shell} (\cmdname{csh}, \cmdname{tcsh}), +mettre dans le fichier \filename{$HOME/.cshrc} : +\begin{alltt} +setenv PATH /\Ucom{\emph{TEXDIR}}/bin/\Ucom{\emph{archname}}:$PATH +\end{alltt} %$ + +Sous \MacOSX{} ceci se peut se faire de la manière suivante, qui évite d'avoir +à ouvrir un éditeur sur un fichier caché : +on redevient utilisateur de base, on se place dans son répertoire personnel, +en tapant dans le Terminal +\begin{alltt} +> \Ucom{exit ; cd} +\end{alltt} +On vérifie quel est le \textit{shell} utilisé en tapant +\begin{alltt} +> \Ucom{echo $SHELL} +\end{alltt} %$ +Si la réponse est \filename{bash} (ou \filename{sh}) le fichier à modifier est +\file{.profile}, si c'est \filename{tcsh} (ou \filename{csh}) +le fichier à modifier est \file{.cshrc}.\\ +Cas de \filename{bash} : on tape dans le terminal\footnotemark{} +\addtocounter{footnote}{-1} +\begin{alltt} +> \Ucom{touch .profile} +> \Ucom{echo "export PATH=/usr/local/texlive/2007/bin/powerpc-darwin:$PATH" >> .profile} +> \Ucom{source .profile} +\end{alltt} %$ +Cas de \filename{tcsh} : on tape dans le terminal% +\footnote{Cet exemple suppose qu'on a fait l'installation dans +\dirname{/usr/local/texlive/2007} et que processeur est un Motorola, sinon il +faut adapter \envname{PATH} en conséquence (changer \dirname{powerpc-darwin} +en \dirname{i386-darwin} pour les Mac à base de processeur Intel).} +\begin{alltt} +> \Ucom{touch .cshrc} +> \Ucom{echo "setenv PATH /usr/local/texlive/2007/bin/powerpc-darwin:$PATH" >> .cshrc} +> \Ucom{source .cshrc} +\end{alltt} %$ +La mise à jour de la variable \envname{PATH} est terminée. + +\medskip +Voici un court exemple qui sélectionne une installation complète avec +les binaires du système actuel seulement (on accepte tous les choix par +défaut). Les \acro{RETURN} sont omis ici. + +% Respecter les espaces pour aligner les # !!! +\begin{alltt} +> \Ucom{sh install-tl.sh} +\Ucom{i} # lancer l'installation +# Redevenir utilisateur de base (non root) +> \Ucom{exit ; cd} +# Nouveau PATH (sous Linux, SHELL=bash, compte avec fichier \file{.bash_profile}) : +> \Ucom{echo "export PATH=/usr/local/texlive/2007/bin/i386-linux:$PATH" >> .bash_profile} +> \Ucom{source .bash_profile} # faire prendre en compte le nouveau PATH +\end{alltt} %$ + +Si votre système Unix connaît la commande \cmdname{manpath} (essayez en tapant +\code{man manpath} dans un terminal), vous pourrez accéder à la documentation +de \TL{} grâce à la commande \cmdname{man} en ajoutant la ligne suivante +(en adaptant les chemins éventuellement) dans +le fichier \filename{/etc/manpath.config} (ceci nécessite les droits de +\textit{root}) : +\begin{alltt} +MANPATH_MAP /usr/local/texlive/2007/bin/i386-linux /usr/local/texlive/2007/texmf/doc/man +\end{alltt} + + +\textruntexconfig + +\medskip %J.A. + +\textifindoubt + + +\subsubsection{Installation non interactive } +\label{sec:noninteractive-install} + +Lorsqu'on doit dupliquer la même installation sur plusieurs machines, il +peut être fastidieux de devoir répondre à chaque fois à la même liste de +questions. Une installation personnalisée automatique est possible. + +Exemple : pour réaliser une installation standard de \TL{} sous +\dirname{/opt/texlive} plutôt que sous \dirname{/usr/local/texlive}, +il suffit d'exécuter les trois commandes suivantes : +\begin{alltt} +> \Ucom{TEXLIVE_INSTALL_PREFIX=/opt/texlive} +> \Ucom{export TEXLIVE_INSTALL_PREFIX} +> \Ucom{echo i | sh install-tl.sh} +\end{alltt} + +L'argument \og\texttt{i}\fg{} passé au script d'installation sert à lancer +l'installation (en mode interactif, on taperait \texttt{i} au clavier). + +Cinq variables d'environnement permettent de choisir où aura lieu +l'installation : +\begin{ttdescription} +\item [TEXLIVE\_INSTALL\_PREFIX] + remplace \dirname{/usr/local/texlive}. +\item [TEXLIVE\_INSTALL\_TEXDIR] + remplace \dirname{/usr/local/texlive/2007}. +\item [TEXLIVE\_INSTALL\_TEXMFLOCAL] + remplace \dirname{/usr/local/texlive/texmf-local}. +\item [TEXLIVE\_INSTALL\_TEXMFSYSVAR] + remplace \dirname{/usr/local/texlive/2007/texmf-var}. +\item [TEXLIVE\_INSTALL\_TEXMFHOME] + remplace \dirname{$HOME/texmf}. %$ +\end{ttdescription} + +\enlargethispage*{\baselineskip} +Pour réaliser une installation personnalisée, il est facile d'écrire un petit +script qui passe les arguments adéquats à la commande \cmdname{install-tl.sh} ; +par exemple pour une installation selon le schéma Gutenberg, avec comme langues +supplémentaires l'espagnol et l'anglais britannique, à placer sous +\dirname{/opt/texlive}, on pourrait lancer (sous root, en supposant que +le SHELL est \cmdname{sh} ou \cmdname{bash} le script suivant : +\begin{verbatim} +TEXLIVE_INSTALL_PREFIX=/opt/texlive +export TEXLIVE_INSTALL_PREFIX +sh install-tl.sh <} pour les lignes de +commandes \textit{(shell prompt)} ; les commandes de l'utilisateur sont +\underline{soulignées}. +\begin{alltt} +> \Ucom{mount -t iso9660 /dev/cdrom /mnt/cdrom} +\end{alltt} + +\noindent Se placer au point de montage du lecteur : +\begin{alltt} +> \Ucom{cd /mnt/cdrom} +\end{alltt} + +Lancer le script \filename{install-pkg.sh} (et non +\filename{install-tl.sh} qui n'est destiné qu'à l'installation complète) : + +\begin{alltt} +> \Ucom{sh install-pkg.sh \var{options}} +\end{alltt} + +Le premier jeu d'options permet de choisir ce qui sera installé : + +\begin{ttdescription} +\item [-{}-package=\var{pkgname}] Le composant individuel à installer. + +\item [-{}-collection=\var{colname}] La collection individuelle à installer. + +\item [-{}-nodoc] Ne pas installer les fichiers de documentation pour +cette opération. + +\item [-{}-nosrc] Ne pas installer les fichiers source pour cette opération. + +\item [-{}-cddir=\var{dir}] Répertoire source d'où on lit ; +par défaut le répertoire courant. Si on a suivi les instructions ci-dessus, +il n'a pas besoin d'être modifié. + +\item [-{}-listdir=\var{dir}] +Ce qu'on appelle \og répertoire des listes\fg{} dans \var{cddir} +d'où on lira l'information sur le composant. +Si on a suivi les instructions ci-dessus, il n'y a pas besoin de le modifier. + +\end{ttdescription} + +La suite des opérations est contrôlée par les options décrites ci-dessous. +Si aucune n'est spécifiée, par défaut on installe les fichiers spécifiés. +L'arborescence principale de destination est +le répertoire père du répertoire \dirname{bin} affiché par la commande +\cmdname{which tex}. +On peut la modifier en changeant les variables d'environnement +\envname{TEXMFMAIN} ou \envname{TEXMF}. + +\begin{ttdescription} + +\item [-{}-listonly] Liste les fichiers à installer mais n'installe + rien du tout ! + +\item [-{}-archive=\var{tarfile}] Au lieu d'installer les fichiers + dans le système \TeX{}, crée une archive \cmdname{tar}. + +\end{ttdescription} + +Options additionnelles : + +\begin{ttdescription} + +\item [-{}-config] Après l'installation, exécuter \code{texconfig init}. + +\item [-{}-nohash] Après installation, ne pas lancer \cmdname{mktexlsr} +pour reconstruire la base de données des noms de fichiers. +\item [-{}-verbose] Donner plus d'informations durant l'exécution des scripts. +\end{ttdescription} + +Voici quelques exemples d'utilisation : + +\begin{enumerate} + +\item Voir les fichiers du composant \pkgname{fancyhdr} sans l'installer : + +\begin{alltt} +\ifSingleColumn> \Ucom{sh install-pkg.sh --package=fancyhdr --listonly} +\else> \Ucom{sh install-pkg.sh --package=fancyhdr \bs} +> \Ucom{--listonly} +\fi{} +texmf-dist/doc/latex/fancyhdr/README +texmf-dist/doc/latex/fancyhdr/fancyhdr.pdf +... +\end{alltt} + +\item Installer le composant \LaTeX{} \pkgname{natbib}: +\begin{alltt} +> \Ucom{sh install-pkg.sh --package=natbib} +\end{alltt} + +\item Installer le composant + \LaTeX{} \pkgname{alg} sans les sources ni la documentation : + +\begin{alltt} +\ifSingleColumn> \Ucom{sh install-pkg.sh --package=alg --nosrc --nodoc} +\else> \Ucom{sh install-pkg.sh -{}-package=alg \bs} +> \Ucom{-{}-nosrc -{}-nodoc} +\fi\end{alltt} + +\item Installer tous les composants dans la collection de macros + additionnelles de plain \TeX\ : +\begin{alltt} +> \Ucom{sh install-pkg.sh --collection=tex-plainextra} +\end{alltt} + +\item +Faire une archive \cmdname{tar} dans \path{/tmp} contenant tous les +composants +de \pkgname{pstricks} : +\begin{alltt} +\ifSingleColumn> \Ucom{sh install-pkg.sh --package=pstricks --archive=/tmp/pstricks.tar} +\else +> \Ucom{sh install-pkg.sh -{}-package=pstricks \bs} +> \Ucom{-{}-archive=/tmp/pstricks.tar} +\fi\end{alltt} + +\end{enumerate} + +\textifindoubt + +% +\section{À faire après l'installation} +\label{sec:postinstall} + +Une fois l'installation terminée il faut, quel que soit le système, +configurer le système pour certains besoins locaux et +faire des tests de base. + +Cette phase de post-installation comprend éventuellement la prise en compte de +composants, fontes ou de programmes qui n'étaient pas inclus dans \TL{}. +L'idée de base est de faire les ajouts dans l'arborescence +\envname{TEXMFLOCAL} (si vous avez installé depuis le disque) +ou dans \envname{TEXMFSYSVAR} (si vous exécutez depuis le disque) ; +voir \og répertoires d'installation\fg{} en page~\pageref{text:instdir}. + +Bien sûr, les détails varient d'un cas à l'autre et nous n'essayerons +donc pas de les traiter ici. Voici quelques pointeurs à consulter : +\begin{itemize} +\item +\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instpackages} +\item +\url{http://www.ctan.org/installationadvice} +\item +\url{http://www.ctan.org/tex-archive/info/beginlatex/html/chapter5.html#pkginst} +\item +\url{http://www.ctan.org/tex-archive/info/Type1fonts} sur l'installation +de fontes. +\end{itemize} + +\subsection{Le programme \protect\cmdname{texconfig}} +\label{sec:texconfig} + +Vous pouvez utiliser le programme \cmdname{texconfig} n'importe quand après +votre installation pour reconfigurer votre système +de façon à satisfaire les besoins locaux. +Il peut être nécessaire de l'exécuter au moins une fois juste après +l'installation si les valeurs par défaut de certains paramètres ne vous +conviennent pas. +Ce programme est installé avec les autres sous le répertoire propre à +votre architecture \texttt{TEXDIR/bin/\var{archname}}, si vous n'avez pas +modifié le \envname{PATH} de \textit{root}, il faudra le lancer +(sous \textit{root}) avec son chemin complet. + +Si on le lance sans arguments, il entre en mode plein-écran et on peut +alors voir et modifier interactivement les paramètres. + +On peut aussi le lancer avec diverses options. Voici les plus courantes +(la distribution \TL{} est configurée pour utiliser du papier~A4 par défaut) : + +\begin{ttdescription} + +\item [texconfig paper letter] +Mettre la taille par défaut du papier à \textit{letter} pour les pilotes +\cmdname{pdftex}, \cmdname{dvips}, \cmdname{dvipdfm}, \cmdname{xdvi}, etc. + +\item [texconfig rehash] Mettre à jour toutes les bases de données des +fichiers du système \TeX{} (à faire après tout ajout ou suppression de +fichier). + +\item [texconfig faq] Afficher la \acro{FAQ} sur \teTeX{}. +(voir aussi la \acro{FAQ} principale de \TeX{} dans +\OnCD{texmf-doc/doc/english/FAQ-en} sur le \DVDlive{}). + +\item [texconfig help] Obtenir de l'aide sur la commande \cmdname{texconfig}. + +\end{ttdescription} + +Bien sûr, \cmdname{texconfig} ne permet de changer que certaines des +nombreuses options et paramètres de configuration d'un système \TeX{}. +Le fichier principal de configuration pour les programmes de la base +\Webc{} s'appelle \filename{texmf.cnf}. ; on peut trouver son emplacement +en exécutant \samp{kpsewhich texmf.cnf}. Ce fichier contient de nombreux +commentaires expliquant les options par défaut et la signification des +paramètres, sa lecture est recommandée. + +Depuis 2005, la commande \cmdname{texconfig} \emph{ne modifie plus les +fichiers de configuration de la machine}, mais ceux de l'utilisateur qui la +lance ; ces fichiers sont dans le répertoire \dirname{$HOME/.texlive2007} %$ +de l'utilisateur. + +De même, les commandes \cmdname{updmap} et \cmdname{fmtutil} +opèrent maintenant au niveau de l'utilisateur dans le répertoire +\dirname{$HOME/.texlive2007} %$ + +\textbf{Important : machines multi-utilisateurs}. Les administrateurs +installant \TL{} sur une machine multi-utilisateurs devront dorénavant +utiliser les commandes \cmdname{texconfig-sys}, \cmdname{updmap-sys} et +\cmdname{fmtutil-sys} pour respectivement modifier la configuration, mettre à +jour les fichiers \file{.map} et créer les formats \emph{au niveau de la + machine}. Noter qu'aucun format n'est créé à l'installation, ils sont +fabriqués à la demande ; depuis cette année, le format créé par un utilisateur +l'est uniquement pour lui (il est mis dans \dirname{$HOME/.texlive2007}). %$ +Afin d'éviter la multiplication de fichiers de formats, il y a donc lieu créer +au moins les formats les plus utilisés au niveau du système à la fin de +l'installation par la commande \cmdname{fmtutil-sys}. Le plus simple est de +les créer tous (c.-à-d. ceux qui figurent dans le fichier fmtutil.conf) par +\begin{alltt} +> \Ucom{fmtutil-sys --all} +\end{alltt} +De plus, ceux qui ont des fichiers de configuration spécifiques +\filename{fmtutil.cnf} ou \filename{updmap.cfg} devront les placer +dans l'arborescence pointée par la nouvelle variable +\envname{TEXMFSYSCONFIG}, +faute de quoi ces fichiers ne seront pas trouvés par les scripts +\cmdname{fmtutil-sys} et \cmdname{updmap-sys}. +Si les fichiers \filename{fmtutil.cnf} et \filename{updmap.cfg} propres à la +machine sont, par exemple, dans \envname{\$TEXMFLOCAL}, +rien n'empêche de définir \envname{TEXMFSYSCONFIG} comme +\envname{\$TEXMFLOCAL}, +mais il faut le faire explicitement dans le fichier \filename{texmf.cnf}. + +Rappelons que la commande \cmdname{texconfig conf} retourne les valeurs des +variables \envname{TEXMFSYSCONFIG}, \envname{TEXMFLOCAL}, etc., et que +l'utilisation des différentes arborescences texmf a été décrite à la +section~\ref{sec:texmftrees} \p.\pageref{sec:texmftrees}. + + +\subsection{Tester l'installation} +\label{sec:test-install} + +Une fois l'installation de \TL{} terminée, il faut +la tester avant de créer des documents ou des fontes. +Les tests doivent être faits par un utilisateur non privilégié +(autre que \textit{root}). + +On donne ici quelques procédures de base pour vérifier que le nouveau +système est opérationnel. On les décrit pour Unix ; pour \MacOSX{} ou +Windows, il vaut mieux tester au travers d'une interface graphique, +mais les principes sont les mêmes. + +\begin{enumerate} + +\item +S'assurer en premier lieu que le programme \cmdname{tex} fonctionne : + +\begin{alltt} +> \Ucom{tex -{}-version} +TeX 3.141592 (Web2C 7.5.5) +kpathsea version 3.5.5 +... +\end{alltt} + +Si on récupère un \textit{command not found} au lieu d'informations +comme le numéro de version et le copyright, il est fort probable que +vous n'avez pas le bon répertoire \dirname{bin} dans votre +\envname{PATH}. +Voir les informations sur l'environnement page~\pageref{text:path}. + +\item Traiter un fichier \LaTeX{} simple : + +\begin{alltt} +> \Ucom{latex sample2e.tex} +This is pdfeTeXk, Version 3.141592... +... +Output written on sample2e.dvi (3 pages, 7496 bytes). +Transcript written on sample2e.log. +\end{alltt} +Si ça échoue en cherchant \filename{sample2e.tex} ou d'autres fichiers, +il y a peut-être des interférences entre vos anciennes variables +d'environnement ou fichiers de configuration. Pour analyser en détail +votre problème, vous pouvez demander à \TeX{} de dire exactement ce +qu'il cherche et trouve ; voir \og Actions de débogage \fg{} +page~\pageref{Debugging}. + +\item Prévisualiser les résultats en ligne : +\begin{alltt} +> \Ucom{xdvi sample2e.dvi} +\end{alltt} +Sous Windows, la commande équivalente est \cmdname{dviout}. +Une nouvelle fenêtre doit s'ouvrir et montrer un document expliquant les +bases de \LaTeX{} (document à lire d'ailleurs si vous êtes débutant !). +Vous devez tourner sous X pour que \cmdname{xdvi} fonctionne. Sinon, votre +variable d'environnement \envname{DISPLAY} n'est pas correcte et vous +aurez une erreur \samp{Can't open display}. + +\item Créer un fichier \PS{} pour l'imprimer ou l'afficher : + +\begin{alltt} +> \Ucom{dvips sample2e.dvi -o sample2e.ps} +\end{alltt} + +\item Créer un fichier \acro{PDF} au lieu de \dvi{} ; +cet exemple traite le fichier \filename{sample2e.tex} et crée directement +du \acro{PDF} : + +\begin{alltt} +> \Ucom{pdflatex sample2e.tex} +\end{alltt} + +\item Prévisualiser le fichier \acro{PDF} : + +\begin{alltt} +> \Ucom{gv sample2e.pdf} +\textrm{ou} +> \Ucom{xpdf sample2e.pdf} +\end{alltt} + +Hélas, ni \cmdname{gv} ni \cmdname{xpdf} ne sont actuellement inclus dans +\TL{}, aussi devez-vous les installer séparément si ce n'est déjà fait. +Voir respectivement +\url{http://www.gnu.org/software/gv} et +\url{http://www.foolabs.com/xpdf}. + +\item Autres fichiers de tests utiles : + +\begin{ttdescription} + +\item [small2e.tex] Un document plus simple à compiler que +\filename{sample2e} si celui-ci pose des problèmes. + +\item [testpage.tex] Teste que l'imprimante n'introduit pas de décalages. + +\item [nfssfont.tex] Imprime des tables de fontes et des tests. +\item [testfont.tex] Aussi pour les tables de fontes, mais en (plain) \TeX. +\item [story.tex] Le fichier de test de (plain) \TeX{} le plus canonique +de tous. Il faut taper \samp{\bs bye} à la commande \code{*} après +\samp{tex story.tex}. + +\end{ttdescription} +Pour exécuter ces tests procéder comme on l'a fait pour +\filename{sample2e.tex}. + +\end{enumerate} + +Si vous êtes débutant ou si vous avez besoin d'aide pour réaliser des +documents \TeX{} ou \LaTeX{}, n'hésitez pas à consulter +\url{http://tug.org/begin.html}. +On vous recommande également l'introduction à \LaTeX{} de Tobias Oetiker +dans sa version anglaise (la version française n'est plus à jour) +disponible après installation sous +\url{texmf-doc/doc/english/lshort-english/lshort.pdf}. + + +\section{Installation pour \MacOSX} +\label{sec:mac-install} + +\TL{} traite \MacOSX, mais pas les versions antérieures des Macintosh. + +On peut installer \TeX{} sous \MacOSX{} de deux façons : + +\begin{enumerate} + +\item Utiliser la nouvelle distribution, appellée Mac\TeX{}, disponible + depuis l'édition 2005 sur le \DVDlive ; elle se trouve dans le répertoire + \dirname{mactex/}, voir section~\ref{sec:mactex}. C'est la méthode + \emph{vivement recommandée}, car l'installation est très simple. + +\item Utiliser les commandes \filename{install*} comme pour Unix (lire d'abord + la section~\ref{sec:osx-unix-inst} ci-dessous pour les spécificités \MacOSX{} +puis la section~\ref{sec:unix-install}). Cette méthode offre plus de choix +quant à ce qui sera installé mais déroute bien des utilisateurs de Macintosh +(ceux qui répugnent à taper des commandes dans un Terminal). + +\end{enumerate} + +\noindent Par ailleurs, l'utilisation de \TeX{} sous \MacOSX{} se fait +normalement par le biais d'une interface graphique (\emph{frontend}), +comme expliqué ci-dessous à la section~\ref{sec:interf-graph-macosx}. + +\subsection{Installation de Mac\TeX} +\label{sec:mactex} + +La distribution Mac\TeX{} est une variante de \TL{} complétée par de +nombreuses applications et de la documentation spécifique. +Elle dispose de son propre installeur intégré. + +Le site de référence pour Mac\TeX{} est \url{http://tug.org/mactex}. + +\subsection{\protect\cmdname{install*.sh} : installation depuis \TL{}} +\label{sec:osx-unix-inst} + +Le système \MacOSX{} est un Unix (presque) comme les autres, mais Apple +cache soigneusement ce fait, ce qui ne facilite pas l'installation de +logiciels comme \TL{}. + +Nous allons essayer de décrire en détail la procédure d'installation. +La première chose à faire est d'ouvrir une fenêtre \og Terminal \fg{}. +L'application \og Terminal\fg{} se trouve dans le répertoire +/Applications/Utilitaires, elle est accessible à partir du menu +principal en haut de l'écran. + +Ensuite, nous allons vérifier si l'interpréteur de commandes +(ou \textit{shell} en anglais) \cmdname{bash} est présent ou non. +Pour cela, taper dans la fenêtre \og Terminal \fg{} la commande suivante : +\begin{alltt} +> \Ucom{which bash} +\end{alltt} +Si le \textit{shell} \cmdname{bash} est présent (cas des versions +de 10.2 et suivantes de \MacOSX) la réponse sera un chemin, par exemple +\filename{/bin/bash}. +Si la réponse est \texttt{command not found}, vous avez une version +antérieure à 10.2, sur laquelle \cmdname{bash} n'est pas installé par défaut. +Vous devrez alors récupérer le \textit{shell} \cmdname{bash} sur internet +(par exemple ici : \url{http://tug.org/texlive/bash.dmg}) +et l'installer\dots{} ou mieux, mettre à jour votre version de \MacOSX. + +Supposons désormais le \textit{shell} \cmdname{bash} présent. +Il faut maintenant \og passer \textit{root} \fg{}, c'est-à-dire +se donner le pouvoir d'effectuer des opérations normalement interdites +aux utilisateurs de base. Ceci se fait en tapant dans le \og Terminal\fg{} +la commande : +\begin{alltt} +> \Ucom{sudo su -} +\end{alltt} + +Mettre le \CDinst{} ou le \DVDlive{} dans le lecteur, son contenu +devient automatiquement accessible sous le répertoire \dirname{/Volumes}. +On tape ensuite dans le \og Terminal\fg{} les commandes : +\begin{alltt} +> \Ucom{cd /Volumes/texlive2007} +> \Ucom{sh install-tl.sh} +\end{alltt} +pour se placer à la racine de l'image disque montée et y lancer le script +d'installation. Il suffit ensuite de suivre la documentation +d'installation de la section~\ref{sec:unix-install-disk} +\p.\pageref{sec:unix-install-disk} où des notes spécifiques pour \MacOSX{} +ont été incluses si nécessaire. + +\subsection{Interfaces graphiques pour \MacOSX{}} +\label{sec:interf-graph-macosx} + +Normalement, l'utilisation de \TeX{} sur un Macintosh se fait à travers +une interface graphique, comprenant un \textit{shell} d'exécution, un +éditeur, un prévisualiseur et d'autres outils (on échappe toutefois +difficilement à l'utilisation de \og Terminal \fg{} dès que l'on veut +réaliser des tâches un tant soit peu évoluées\ldots). + +Voici les principales interfaces disponibles : + +\begin{cmddescription} +\item [TeXShop] Inclus dans \TL{} sous +\filename{./MacOSX/texshop.dmg}.\\ +Voir \url{http://www.uoregon.edu/~koch/texshop/texshop.html}. + +\item [ITeXMac] Inclus dans \TL{} sous \filename{./MacOSX/iTM-*.dmg}.\\ +Voir \url{http://itexmac.sourceforge.net}. + +\item [Mac-emacs] Une adaptation d'Emacs à \MacOSX{}, avec +\pkgname{AucTeX} inclus.\\ +Voir \url{http://www.cs.man.ac.uk/~franconi/mac-emacs}. + +\end{cmddescription} + +Si vous choisissez d'utiliser \cmdname{TeXShop} ou \cmdname{ITeXMac}, +il sera nécessaire de donner à ces logiciels les informations concernant +le PATH : + +\begin{cmddescription} + +\item [TeXshop] Lancer l'application et ouvrir le panneau préférences (menu + TeXShop). Sélectionner l'onglet \og Moteur\fg{} et modifier la première + ligne en saisissant votre PATH, par exemple : + \dirname{/usr/local/texlive/2007/bin/powerpc-darwin}. + +\item [ITeXMac] Lancer l'application et ouvrir le panneau préférences (menu + ITeXMac). Sélectionner le bouton \og Assistant teTeX\fg{}, puis l'onglet + \og TeX\fg{} et cliquer sur le bouton radio \og{} Autre\fg{}. Saisir alors + votre PATH, par exemple : + \dirname{/usr/local/texlive/2007/bin/powerpc-darwin}. + +\end{cmddescription} + + +\section{Installation sous Windows} +\label{sec:win-install} + +La distribution \TL{} inclut un +installeur pour Windows qui s'appelle \cmdname{tlpmgui}. + +%%%%%%%%%%%%%%%%%%%% Ajout (df) %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +\begin{quote} +\textbf{Note du traducteur :} à titre personnel, je ne recommande pas +l'installation sous Windows à partir de \cmdname{tlpmgui}, sauf aux +utilisateurs qui connaissent bien \TL{} sous Unix et veulent avoir sous +Windows une distribution aussi proche que possible de celle-ci. + +Une autre piste, non basée sur la distribution \TL{}, me semble nettement plus +adaptée : il s'agit installer la distribution \ProTeXt{} à partir du +\DVDlive{} ou du \CD{} spécifique, elle est basée sur \MIKTEX{} distribution +très appréciée sous Windows ; + +Si vous décidez d'opter pour \ProTeXt{} la suite de toute cette +section ainsi que la suivante (Maintenance sous Windows) ne vous +concernent pas. +\end{quote} +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +\cmdname{tlpmgui} propose essentiellement les mêmes options que le script +\cmdname{install-tl.sh} sous Unix mais dans une interface graphique : + sélection des schémas, choix des collections, etc., se reporter +à la section~\ref{sec:unix-install-disk} \p.\pageref{sec:unix-install-disk}. +Certaines manipulations telles que l'ajout ou la suppression +de composants, la mise à jour des bases de données +et la constructions de formats sont également possibles. +De plus, \cmdname{tlpmgui} offre la possibilité d'utiliser \TL{} depuis +le \DVDlive{} (sans l'installer sur le disque dur). + +Pour les connaisseurs, \cmdname{tlpmgui} repose sur le programme +\cmdname{tlpm} accessible en ligne de commande Windows. + +Les binaires pour Windows sont empruntés à la distribution \acro{W32TEX}, +fournie par Akira Kakuto. +Certains outils de l'ancienne distribution \fpTeX{} de Fabrice Popineau ont +été conservés, le nouveau visualiseur \cmdname{dviout} de Toshio Oshima +a remplacé celui de Fabrice (\cmdname{Windvi}). + +\TL{} peut être installé sur les systèmes Windows~9x, \acro{ME}, +\acro{NT}, \acro{2K} or \acro{XP}. Il ne fonctionne pas avec les versions +plus anciennes Windows (3.1x) et \acro{MS-DOS}. + +\textbf{Attention :} Les utilisateurs de Windows~9x + doit vérifier qu'il disposent d'assez d'espace pour les variables + d'environnement. Le programme \cmdname{tlpmgui.exe} crée un certain + nombre de variables d'environnement, si l'espace manque ajouter + \texttt{SHELL=COMMAND.COM /E:4096 /P} dans le fichier + \filename{config.sys}. + +\subsection{Installation sous Windows depuis le \CDinst} + +Le programme \cmdname{tlpmgui} devrait démarrer automatiquement +dès l'insertion du \CDinst{} dans le lecteur de \acro{CD}. +Si ce n'est pas le cas, cliquer sur \guiseq{Start\arw Run} puis +taper \path{:\string\setuptl\string\tplmgui.exe} +--- resp. +\path{:\string\texlive\string\setuptl\string\tplmgui.exe} +si vous installez à partir du \DVDlive{} --- où \path{} +désigne la lettre correspondant au lecteur de \acro{CD} ; cliquer ensuite +sur OK. + +La fenêtre intitulée \guiseq{TeX Live installation and maintenance utility} +devrait s'ouvrir. Elle propose les options suivantes : +\guiseq{Main customization}, \guiseq{Install}, \guiseq{Select a scheme}, +\guiseq{Select systems}, \guiseq{Directories} et \guiseq{Options}. + +Dans la section \guiseq{Directories}, le nom du lecteur de \acro{CD/DVD} +(par exemple \texttt{F:/}) devrait apparaître à côté du bouton +\acro{CD/DVD}. S'il n'est pas affiché utiliser ce bouton pour +sélectionner le lecteur de \acro{CD/DVD} contenant \TL. + +Il est possible de choisir le répertoire devant contenir la distribution \TL{} +en cliquant sur le bouton \guiseq{TLroot}(la variable \path{TLroot} contiendra +le nom de ce répertoire). +% Le contenu des variables d'environnement +% \path{TEXMFTEMP} et \path{TEXMFCNF} est affiché à côté des boutons +% \guiseq{TEXMFTEMP} et \guiseq{TEXMFCNF}, il sera mis à jour automatiquement +% pendant l'installation (il est possible de le modifier en cas de besoin +% particulier). + +La section \guiseq{Select a scheme} permet, comme sous Unix, de choisir le +schéma de base souhaité pour l'installation (complète, GUTenberg, etc.) : +utiliser le bouton radio pour faire ce choix et le bouton \guiseq{Info} +pour une description du schéma sélectionné. + +Il est possible de personnaliser le schéma choisi en lui ajoutant ou en +supprimant certaines de ses composantes (appelées \guiseq{collections}). +Ceci se fait en utilisant les boutons \guiseq{Standard collections} +et \guiseq{Language collections} (choix des langues utilisables) +dans \guiseq{Main customization}. + +La collection \guiseq{Wintools} est sélectionnée par défaut car elle contient +beaucoup de petits utilitaires non fournis avec Windows, comme des +convertisseurs tels que \cmdname{sam2p}, \cmdname{jpeg2ps}, \cmdname{tiff2png}, +des prgramme de compression tels que \cmdname{bzip2}, \cmdname{gzip}, +\cmdname{unzip} et \cmdname{wget} qui est requis par le nouvel utilitaire +\cmdname{getnonfreefonts}. + +\textbf{Remarque :} Les collections \guiseq{Ghostscript}, \guiseq{Perl} +sont sélectionnées par défaut. Elles \emph{doivent être +installées}\dots{} sauf si elles l'ont été par ailleurs. +Les variables d'environnement \envname{PERL5LIB} et \verb|GS_LIB| doivent +aussi être initialisées et le chemin complet des binaires \guiseq{Ghostscript} +doit être ajouté à la variable \verb|PATH|. + +Finalement, cliquer sur le bouton \guiseq{Install} dans la section +\guiseq{Install} pour lancer le processus d'installation. + +Laisser le processus se poursuivre jusqu'à l'affichage du message annonçant +que l'installation a réussi (un certain nombre d'étapes sont nécessaires, +comme la création des formats, la mise à jour des bases de données, etc. ce +qui peut prendre un certain temps). + +Un raccourci pour \cmdname{tlpmgui} (et pour \cmdname{dviout} s'il est +installé), sera ajouté dans le menu \guiseq{Start\arw Programs\arw +TeXLive2007}. + +Si nécessaire (Windows~9x/WinME), il vous sera demandé de +redémarrer l'ordinateur. + + +\subsection{Programmes auxiliaires pour Windows} +\label{sec:win-xemtex} + +Pour être complète, une installation \TL{} a besoin de programmes +auxiliaires qu'on ne trouve pas fréquemment sur une machine Windows. +De nombreux scripts sont écrits en Perl. Certains outils importants utilisent +l'interpréteur \PS{} Ghostscript pour afficher ou convertir les fichiers. +Il faut aussi dans certains cas une boîte à outils graphique. +Enfin, un éditeur orienté \TeX{} facilite la saisie de fichiers \TeX{}. + +Tous ces outils sont assez faciles à trouver pour \TeX{}, mais pour essayer +de vous rendre la vie plus facile, nous avons incorporé des outils de ce type +dans \TL{} : +\begin{itemize} +\item GNU \cmdname{GhostScript} 8.54 ; +\item un \cmdname{Perl} 5.8 minimum, suffisant pour exécuter tous les scripts +Perl du \TL{} ; +\item quelques utilitaires comme bzip2, gzip, jpeg2ps et tiff2png. +\end{itemize} + +Perl et Ghostscript sont installés par défaut ; vous pouvez empêcher +leur installation en les déselectionant explicitement lors de +l'installation si vous les avez déjà. + +Si vous préférez ne pas installer les outils inclus dans \TL{}, vous êtes +libre d'installer les outils nécessaires pour compléter votre système \TL{} ; +voici une liste des adresses où les obtenir : +\begin{description} +\item[GhostScript] \url{http://www.cs.wisc.edu/~ghost/} +\item[Perl] \url{http://www.activestate.com/} (mais il vous faudra peut-être + chercher des bibliothèques supplémentaires sur CPAN, + \url{http://www.cpan.org/}) +\item[ImageMagick] \url{http://www.imagemagick.com} +\item[NetPBM] Vous pouvez aussi utiliser NetPBM à la place de ImageMagick + pour traiter ou convertir vos fichiers graphiques. La page d'accueil + de NetPBM est + \url{http://netpbm.sourceforge.net/} +\item[Éditeurs orientés \TeX] Il y a un large choix, et cela dépend des + préférences de l'utilisateur. En voici une sélection : + \begin{itemize} + \item \cmdname{GNU Emacs} avec l'extension AucTeX existe nativement + sous Windows, l'url de référence est + \url{ftp://alpha.gnu.org/gnu/auctex} ; + \item \cmdname{WinShell} se trouve sur \TL{} dans le répertoire + \path{support}, l'url de référence est \url{http://www.winshell.de} ; + \item \cmdname{WinEdt} est un partagiciel disponible à l'adresse + \url{http://www.winedt.com} ; + \item TeXnicCenter est libre et se trouve à l'adresse + \url{http://www.toolscenter.org/products/texniccenter/} et aussi dans + la distribution \ProTeXt{} ; + \item \cmdname{Vim} peut être téléchargé sur le site + \url{http://www.vim.org} ; + \item \cmdname{LEd} se trouve à l'adresse + \url{http://www.ctan.org/support/LEd} ; + \item \cmdname{SciTE} se trouve à l'adresse + \url{http://www.scintilla.org/SciTE.html}. + \end{itemize} +\end{description} + +Il est aussi possible d'installer d'autres outils qui ne sont pas +libres\footnote{Pas libres en fait dans le sens de la liberté de les + modifier et les redistribuer, selon les +\emph{Debian's guidelines}. Cela ne signifie pas qu'on ne peut pas les +acquérir gratuitement.} +comme \cmdname{GSView}, le programme compagnon de \cmdname{GhostScript} +pour afficher plus facilement les fichiers PS/PDF. +\cmdname{GSView} est disponible à l'url +\url{http://www.cs.wisc.edu/~ghost/gsview/} +ou sur tout site \acro{CTAN}. + +\section{Maintenance sous Windows} + +Une fois la distribution \TL{} installée, vous pouvez vous servir du programme +\cmdname{tlpmgui} pour modifier ou compléter votre installation. + +\subsection{Ajouter ou supprimer des composants} + +Le raccourci \cmdname{tlpmgui} du menu +\guiseq{Start\arw Programs\arw TeXLive2007} permet de lancer le programme +et affiche la fenêtre \guiseq{TeX Live installation and maintenance utility}. +Les sections à utiliser sont \guiseq{Add Packages} (ajout de composants), +\guiseq{Remove packages} (suppression de composants), +\guiseq{Manage installation} (maintenace), \guiseq{Remove installation} +(suppression totale de \TL). + +Cliquer sur \guiseq{Add packages} ou \guiseq{Remove packages}, puis + +\begin{itemize} +\item Choisir le lecteur de \acro{CD} (ou le répertoire \texttt{texlive} + du lecteur de \acro{DVD}) grâce au bouton \guiseq{CD/DVD}. + +\item Cliquer sur le bouton \guiseq{Search} dans la section \guiseq{Buttons} +pour afficher la liste de composants à installer ou à supprimer +dans \guiseq{Select packages to\dots}. + +Lors de l'ajout de composants, la liste des composants installés est comparée +à la liste des composants disponibles sur le \acro{CD/DVD}. +Seuls les composants non installés sont affichés, à vous de choisir ceux que +vous souhaitez ajouter. + +Inversement, lors de la suppression de composants, seuls les composants +installés sont affichés. + +Noter que les collections sont en tête de liste. + +\item Sélectionner un composant en cliquant sur son nom dans la liste. +Un clic sur le bouton \guiseq{Info} donne une courte description du contenu. +Il est possible de sélectionner plusieurs composants à la fois à l'aide des +touches \og Ctrl \fg{} et \og Shift \fg{} (majuscules). + +\item Cliquer sur \guiseq{Install} ou \guiseq{Remove} pour terminer +l'opération. +\end{itemize} + +\subsection{Configuration et maintenance} + +La section \guiseq{Manage the installation} permet d'effectuer les opérations +courantes de configuration et de maintenance. + +Voici la liste des actions possibles : +\begin{itemize} + \item mettre à jour la base \filename{ls-R}, + \item créer les formats, + \item modifier le fichier \filename{language.dat}, + \item modifier le fichier \filename{fmtutil.cnf}, + \item modifier le fichier \filename{updmap.cfg}. + \end{itemize} + +Il faut sortir de la fenêtre d'édition en cliquant sur le bouton \guiseq{Done} +pour que les mises à jour des formats, fichiers \file{.map}, base +\filename{ls-R} soient effectuées. + +Les autres possibilités de configuration sont décrites à la +section~\ref{sec:persconf}, \p.\pageref{sec:persconf}. + +\subsection{Désinstallation complète de \TL{}} + +L'option \guiseq{Remove the TeX Live installation} permet de supprimer toute +la distribution \TL{}. + +Attention, ce que vous avez éventuellement installé dans le répertoire +\path{texmf-local} ne sera pas supprimé ; le répertoire \path{setuptl} +contenant \cmdname{tlpmgui} doit être également nettoyé à la main si +nécessaire. + +\subsection{Ajouter des composants à votre système} + +Tout d'abord, quelles que soient les modifications faites, +\emph{n'oubliez pas de reconstruire les fichiers ls-R de bases de + données}, sinon les nouveaux fichiers ne seront jamais retrouvés. +Pour cela, vous pouvez soit utiliser le programme \cmdname{tlpmgui}, option +\guiseq{Manage the installation}, soit lancer manuellement la commande +\file{mktexlsr}. + +Si vous choisissez d'ajouter des fichiers qui ne proviennent pas de la +distribution \TL{} (ou fp\TeX{}), il est fortement +recommandé de les mettre dans le répertoire \path{$TEXMFLOCAL}. %$ +De cette manière, vous serez certain qu'il n'y aura pas de problème +lors d'une mise à jour de \TL. + +L'arborescence pointée par \path{$TEXMFLOCAL} est initialement %$ +vide. Si vous souhaitez y ajouter par exemple les fichiers de style +pour le logiciel de calcul formel Maple, vous devrez mettre ces +fichiers dans le répertoire +\path{C:\string\TeXLive2007\string\texmf-local\string\tex\string\latex\string\maple} +et les fichiers de documentation dans +\path{C:\string\TeXLive2007\string\texmf-local\string\doc\string\latex\string\maple} + + +\subsection{Exécution de \texttt{tlmp.exe} en ligne de commande} + +Le programme \cmdname{tlpm.exe} utilisé par \cmdname{tlpmgui} +possède de nombreuses options utiles dont la liste est donnée par +\begin{verbatim} +tlpm --help +\end{verbatim} + +Consulter le fichier \filename{tlpm.readme} pour plus de renseignements et des +exemples. + +\subsection{Installation en réseau} + +\KPS{} est compatible avec les noms UNC, ceux-ci peuvent donc être utilisés +pour récupérer l'arborescence TEXMF depuis le réseau. Mais +encore mieux, tous les fichiers, y compris ceux de +configuration et excepté les binaires dans \path{bin/win32}, sont +compatibles et partageables avec \teTeX{} ou le \TL{} Unix. Cela +signifie que vous pouvez utiliser Samba, soit pour monter la +distribution Unix sur un client Windows, ou un client Unix +depuis un serveur NT. Plusieurs stratégies sont possibles : +\begin{itemize} + +\item tout mettre sur le serveur. Il faut simplement être certain de mettre dans \path{bin/} les binaires pour tous les couples systèmes d'exploitation / architectures nécessaires. Par exemple, ajouter \path{bin/win32} et + \path{bin/i386-linux}. Ensuite configurer les variables principales ; vous + pouvez utiliser des noms UNC pour pointer sur les répertoires appropriés + sous Win32. + +\item Installer une copie locale pour les binaires et les fichiers de + format. Dans ce cas, assigner \path{$TEXMFMAIN} au répertoire + principal \path{texmf} qui sera pris sur le réseau. Faire pointer + \path{$VARTEXMF} vers un répertoire local qui contiendra les fichiers + de configuration locaux et les fichiers générés au vol. %$ + +\end{itemize} + +\subsection{Différences entre la version Windows et la version + Unix de \TL} + +La version Windows de \Webc{} possède quelques spécificités qui méritent +d'être notées. + +\begin{description} +\item [\cmdname{kpsecheck}] Cette commande fournit des fonctionnalités + qui ne rentraient pas bien dans \cmdname{kpsewhich}. En particulier, + elle permet de lister tous les fichiers qui apparaissent plusieurs + fois à travers les multiples arborescences \path{texmf/}. Ceci à + l'air pratique, sauf qu'en réalité, la sortie est polluée par des + occurrences multiples de fichiers qui ne sont pas utiles à \TeX{} à + proprement parler (commes des dizaines de fichiers + \filename{README})\footnote{Tous ces fichiers + sont susceptibles de produire des collisions lors de l'accès à la + table de hachage ; heureusement \TeX{} ne les utilise pas, ils ne + sont donc pas pris en compte !}. Pour cette raison, vous pouvez combiner + l'option \path{-multiple-occurences} avec deux autres options pour + inclure ou exclure de la recherche tout fichier conforme à un + certain motif (plusieurs motifs d'inclusion ou d'exclusion peuvent + être spécifiés). + + La commande \cmdname{kpsecheck} peut aussi indiquer le statut + d'utilisation de la mémoire partagée : en utilisation ou + non-utilisée. Cette information peut être très utile, car si le + statut rapporté est \og en utilisation\fg{}, cela signifie qu'un + ou plusieurs processus tournent et utilisent le bloc de mémoire + partagée. Dans ce cas, une réinitialisation des tables de hachage + basée sur les fichiers \filename{ls-R}, comme la commande + \cmdname{mktexlsr} l'effectue, sera automatiquement repoussée + jusqu'à ce que tous les processus utilisant la version courante en + mémoire partagée soient terminés. Il est prévu d'enlever cette + limitation dans une version future, mais la version actuelle de + \KPS{} ne permet pas de faire facilement cette réinitialisation. + + Enfin, la même commande \cmdname{kpsecheck} peut indiquer l'endroit + où \KPS{} pense pouvoir trouver la Dll de Ghostscript. En effet, + sous Win32, il est souvent plus simple de travailler directement + avec la Dll de Ghostscript, et de la trouver en utilisant la clé + appropriée dans la base de registre, que d'utiliser \path{gswin32c.exe} et + de modifier le \path{PATH} qui a une longueur limitée. + +\item [\Webc] Les moteurs \TeX{} ont une option supplémentaire + par rapport à la version standard : + \path{-proctimes} affiche des statistiques à propos du + temps d'exécution. Il est à noter que Windows~9x n'étant pas un + système multi-tâche préemptif, il ne possède pas d'horloge + interne suffisamment précise pour mesurer ces temps d'exécution + et donc la valeur affichée n'est qu'une approximation. Sous + NT/2K/XP, le résultat est assez précis et comprend le temps + utilisateur et le temps système alloués à la compilation. Pour + les utilisateurs d'Unix : la commande \path{time} n'existe pas + sous Windows. +\end{description} + +\subsection{Personnalisation de l'installation} +\label{sec:persconf} + +\subsubsection{Dvips} + +Le fichier de configuration de \texttt{dvips} se trouve par défaut en +\path{C:\string\TeXLive2007\string\texmf-var\string\dvips\string\config\string\config.ps}. Il peut être ouvert avec n'importe quel éditeur de texte +% (comme \cmdname{WinShell}) +pour modifier certains paramètres : +\begin{description} +\item[fontes] vous pouvez changer la résolution et le mode de + l'imprimante à laquelle sont destinés vos fichiers dans le cas où + \texttt{dvips} aurait besoin de générer des fontes bitmap. Par défaut, + les fontes Type1 CM interpolées sont utilisées, et donc + \path{mktexpk} ne devrait pas être appelé trop souvent. +\item[imprimante] vous pouvez spécifier où se fera l'impression par + défaut. Si l'option `o' n'est pas suivie d'un nom d'imprimante, un + fichier est créé avec l'extension \file{.ps}. Sinon, vous pouvez + spécifier un nom d'imprimante tel que : +\begin{verbatim} +o lpt1: +% o | lpr -S server -P myprinter +% o \\server\myprinter +\end{verbatim} +\item[papier] vous pouvez changer le format de papier retenu par + défaut (A4), par exemple en format US letter, le premier format + mentionné. Allez vers les lignes débutant par \path{@}. Déplacez les + lignes adéquates, ainsi le fichier commencera par les lignes qui suivent. +\begin{verbatim} +@ letterSize 8.5in 11in + +@ letter 8.5in 11in +@+ %%BeginPaperSize: Letter +@+ letter +@+ %%EndPaperSize +\end{verbatim} +\end{description} + +La distribution \TL{} actuelle intègre un programme \og \cmdname{updmap} \fg{} +facilitant la mise à jour des fichiers \file{psfonts.map} pour Dvips et +\file{pdftex.map} pour PdfTeX. +\cmdname{updmap} est lancé automatiquement durant l'installation. +Si vous ajoutez de nouvelles fontes à la main, +éditez le fichier \verb+updmap.cfg+ dans \path{$TEXMFVAR/web2c}. %$ +et relancez \cmdname{updmap}. + +\subsubsection{PdfTeX} + +Si le programme \cmdname{pdflatex} est utilisé pour écrire directement en +format +\acro{PDF} et qu'on utilise du papier au format \acro{US} letter-size, +éditer le fichier +\path{C:\string\TeXLive2007\string\texmf-var\string\tex\string\generic\string\config\string\pdftexconfig.tex} +et modifier \samp{\bs page\_width} et \samp{\bs page\_height}. +Ces entrées doivent être : +\begin{alltt} +\bs{}pdfpagewidth=8.5 true in +\bs{}pdfpageheight=11 true in +\end{alltt} + +Sauvegarder le fichier et sortir de l'éditeur. + +\subsubsection{Xe\TeX} + +Xe\TeX{} pour Windows est lié statiquement à la bibliothèque fontconfig 2.4.2. +Le fichier de configuration pour les fontes s'appelle \verb+fonts.conf+. +Ce fichier se trouve dans le répertoire indiqué par la commande +\texttt{kpsewhich --var-value=FONTCONFIG\_PATH}. + +\subsubsection{Gsview} + +\cmdname{GSView} est maintenant distribué sous licence Aladdin et n'est donc +plus inclus dans \TL{}. + +Si vous voulez changer le format du papier, ouvrez \cmdname{GSView} à +partir du menu \guiseq{Démarrer} et sélectionnez \guiseq{Media\arw Letter}. +Le sous menu Display Settings vous permet +également d'améliorer la netteté du rendu en positionnant les +deux valeurs \textbf{Text Alpha} et \textbf{Graphics Alpha} à 4 bits. + +Pour ce qui est de l'impression, consulter la +sous-section~\ref{sub:printing}. + +Les fichiers \file{.ps} et \file{.eps} seront automatiquement ouverts +par \cmdname{GSView}. + +\subsection{Tests} + +Pour des procédures génériques de vérification, voir +section~\ref{sec:test-install}, page~\pageref{sec:test-install}. +Cette section décrit les tests spécifiques à Windows. + +Vous pouvez tester l'installation +en ouvrant le fichier +\verb+sample2e.tex+ dans votre éditeur (\cmdname{XEmacs}, +\cmdname{WinShell}) qui se trouve dans +\path{C:\string\TeXLive2007\string\texmf-dist\string\tex\string\latex\string\base}. +Le source \LaTeX{} doit apparaître à l'écran. Compilez-le en cliquant +sur le menu (XEmacs) \guiseq{Command\arw LaTeX} ou sur l'icône \LaTeX{} +(WinShell) dans la barre d'outils, ensuite affichez-le en +cliquant sur le menu (XEmacs) \guiseq{Command\arw View DVI} +ou sur l'icône Preview (dviout). + +La première fois que vous afficherez un document avec \cmdname{dviout}, il va +créer les fichiers de fontes bitmaps qui ne sont pas installées. +Après avoir visualisé quelques fichiers, vous aurez créé la plupart de ces +fichiers et vous ne verrez plus souvent apparaître la fenêtre de création de +fontes. + +En cas de problèmes, reportez-vous à la +sous-section~\ref{sec:troubleshooting}. + +\subsection{Impression} +\label{sub:printing} + +Il est possible d'imprimer depuis \cmdname{dviout}. Dans ce cas, l'impression +utilise le pilote unifié d'impression de Windows, il est donc par +définition compatible avec toutes les imprimantes. Cependant, il y a +un inconvénient : cette impression génère des fichiers (spool) très +importants, quelques versions anciennes de Windows le supportent mal. +L'avantage est que vous pouvez tirer +parti de l'impression d'images BMP ou WMF par exemple. Il faut +également faire bien attention à ce que les paramètres de l'imprimante +soient correctement définis sous peine +d'avoir un effet d'échelle +(imprimer à 600\,dpi sur une imprimante qui fait réellement 300\,dpi +aboutit à n'avoir qu'un seul quart de la page visible). + +L'impression est souvent plus rapide en utilisant \cmdname{dvips}, puis en +imprimant le fichier \file{.ps} depuis \cmdname{GSView}. Pour imprimer +depuis \cmdname{GSView}, sélectionner \textbf{Print\dots{}} dans le menu +\textbf{File}. Une fenêtre de dialogue pour l'impression apparaît. + +Si vous utilisez une imprimante PostScript, \emph{soyez sûr de + sélectionner \textbf{PostScript Printer}} en choisissant cette +option dans \textbf{Print Method} en bas à gauche de la boîte de +dialogue, faute de quoi l'impression échouera. Vous +pouvez ensuite sélectionner une imprimante quelconque parmi celles +installées. + +Si vous utilisez une imprimante qui ne supporte pas PostScript, +sélectionnez \textbf{Ghostscript Device} dans \textbf{Print + Method}. Ensuite cliquez sur le bouton \textbf{djet500} et +sélectionnez votre imprimante. + +\subsection{Trucs et astuces à propos de la plate-forme Win32} + +\subsubsection{Différentes déclinaisons de Win32} + +Ce que recouvre la dénomination Win32 n'est pas un système +d'exploitation. C'est un ensemble de fonctions très +vaste (environ 12000 fonctions dans les fichiers d'en-tête du + SDK Microsoft) que vous pouvez utiliser pour écrire des programmes +pour différentes versions des systèmes d'exploitation de la famille +Windows. + +Windows se décline en plusieurs versions : +\begin{itemize} +\item Win95, Win98 et WinME, qui \emph{ne sont pas de vrais systèmes + d'exploitation multitâches et multithreads}. Ils sont en fait les + dernières incarnations de DOS. On peut s'en apercevoir, car en + lançant le PC, l'interpréteur de commandes \path{command.com} est + chargé et si vous arrêtez le processus à ce moment, vous pouvez + demander la version courante (de DOS) et il vous est répondu quelque + chose du style "MS-DOS 7.0", au moins pour les versions anciennes de + Windows~9x ; +\item Windows \acro{NT} est un système d'exploitation écrit à partir + de zéro, avec un + vrai multitâche préemptif et des fonctionnalités de très haut niveau ; +\item Windows 2000 est écrit sur une base \acro{NT}, il est doté de toutes les + facilités offertes par Win98 ; +\item Windows \acro{XP} existe en versions Personnelle et + Professionnelle. C'est la dernière étape dans la fusion entre les + deux lignes de produits (basée sur Windows~9x et basée sur NT). \acro{XP} est + écrit sur une base NT. +\end{itemize} + +Windows~9x peut faire tourner des programmes 32~bits et des +programmes 16~bits en même temps. Mais le système d'exploitation +lui-même n'est pas entièrement écrit en mode 32~bits et ne fournit pas +une protection mémoire entre les applications : les applications +16~bits peuvent écraser des parties du système d'exploitation en +mémoire ! Des parties du système telles que le \acro{GDI} +(\emph{Graphical Device Interface}) ne se voient allouer que des +ressources de taille très +limitée pour gérer les bitmaps, les pinceaux et les polices, et ces +ressources sont allouées de manière globale pour tous les programmes +qui tournent de manière concurrente. Par exemple, toutes les entêtes de +bitmaps utilisés par tous les programmes qui tournent simultanément ne +doivent pas requérir plus de 64~ko de mémoire. Ceci explique le +comportement du moniteur de performance et le fait que vous pouvez +mettre votre système à genoux en utilisant de manière intensive les +objets graphiques. + +NT, 2K et XP ne souffrent pas de ces limitations, ni d'aucune autre +limitation de Windows~9x. Ce sont de vrais environnements multitâches, avec +une vraie mémoire protégée. Ils répondent de manière plus fluide que +Windows~9x de par leur meilleure gestion de la mémoire, leur système de +gestion de fichiers plus performant, etc. + +\subsubsection{La ligne de commande} + +Vous allez demander : mais pourquoi diable devrais-je me +préoccuper d'une ligne de commande alors que j'ai Windows ? + +Bonne question. Le problème est de nature très générale. Toutes les +opérations ne peuvent pas être accomplies très facilement à l'aide de +la seule interface graphique. La ligne de commande vous donne la +puissance de la programmation -- si vous avez un bon interpréteur de +commandes. + +Mais le problème est plus fondamental : \TeX{} est un outil qui +fonctionne \emph{en batch}, de manière non interactive. \TeX{} a +besoin de calculer la meilleure mise en page pour chaque page, de +résoudre les références croisées, etc. Ceci ne peut être réalisé +que par un traitement global du document. Ce n'est pas encore une tâche +qui peut être réalisée interactivement. + +Ceci implique que vous devriez utiliser \TeX{} depuis la ligne de +commande. En fait la situation n'est pas si catastrophique. Il y a un +avantage à écrire des outils en ligne de commande pour des tâches +complexes : ils sont bien plus fiables, parce qu'ils n'héritent pas de +la complexité inhérente aux interfaces graphiques. +Il est ensuite possible de +concevoir des outils graphiques qui servent d'interface aux outils en +ligne de commande. C'est le cas de \TeX{} : vous interagirez avec lui +la plupart du temps au travers d'un éditeur de textes qui possède une +interface graphique. + +Cependant, il se peut que vous ayez besoin d'utiliser la ligne de +commande dans certaines situations. Par exemple en cas de +problèmes, parce que vous avez besoin de trouver une erreur dans votre +installation -- voir la section~\ref{sec:troubleshooting}. + +\begin{description} +\item[Windows~9x, WinME] Vous ouvrirez une ligne de commande soit en cherchant + l'icône \acro{MS-DOS} dans le menu \og \guiseq{Démarrer\arw Programmes}\fg{}, + soit en choisissant \og \guiseq{Démarrer\arw Exécuter}\fg{}, puis en tapant + \path{command.com} . +\item[NT, 2K, XP] Vous ouvrirez une ligne de commande en cherchant + \og \guiseq{Invite de commandes}\fg{} dans le menu \og \guiseq{Démarrer\arw + Accessoires}\fg{} (ces emplacements peuvent changer d'une version de Windows à + l'autre). Vous pouvez aussi choisir le menu + \og Démarrer -> Exécuter\fg{} et taper \path{cmd.exe}, qui est le nom + du nouvel interpréteur de commandes pour NT. +\end{description} + +\subsubsection{Les séparateurs de chemins} + +L'API Win32 admet les deux caractères \verb+/+ et \verb+\+ comme +séparateurs pour les noms de fichiers. Mais pas les interpréteurs +de commande ! Donc, chaque fois qu'un nom de fichier est utilisé par +un programme, vous pouvez utiliser l'un ou l'autre séparateur, mais +sur la ligne de commande, vous devez utiliser \verb+\+ comme unique +séparateur. Ce qui explique que vous pouvez taper : +\begin{verbatim} + C:\>set TEXMFCNF=C:/Program Files/TeXLive/texmf-var/web2c +\end{verbatim} +mais pas : +\begin{verbatim} +C:\>dir "C:/Program Files/TeXLive" +\end{verbatim} +Dans le premier cas, seuls des programmes utiliseront le chemin que +vous avez fourni, dans le deuxième cas, c'est l'interpréteur de commandes +qui va vouloir s'en servir directement. + +Tout ceci pour dire, ne soyez pas surpris de voir des noms de +fichiers écrits avec des \path{/} en guise de séparateurs, à la mode Unix ; +Windows-\TL{} est un portage de \Webc, dont l'objectif est d'être +compatible avec toutes les plates-formes. Pour cette raison, les +fichiers de configuration utilisent la convention Unix des séparateurs +dans les noms de fichiers. + +\subsubsection{Les systèmes de gestion de fichiers} + +Une des plus mauvaises caractéristiques de Windows~9x vis-à-vis de \TeX{} +est probablement ce qu'on appelle le système de fichiers FAT. +\TeX{} utilise une myriade de petits fichiers dont la taille varie +entre 1~ko et 5~ko. Le système FAT est ancien et date d'une époque bien +antérieure à l'apparition des disques de plusieurs Go qui sont monnaie +courante aujourd'hui. Tout ceci pour dire qu'il n'est pas possible de +gérer efficacement les dizaines de fichiers de \TL{} sur un disque dur +formaté en FAT. Les fichiers se voient allouer chacun 32~ko au +minimum, donc l'installation de \TL{} utilise beaucoup plus de +place que nécessaire. + +Le seul moyen d'éviter ce problème consiste à +passer en FAT32 ou NTFS. Ces systèmes sont plus récents et n'ont pas +l'inconvénient de FAT. La taille des clusters par défaut y est de 4~ko, +leur accès est plus performant. NTFS est protégé, redondant et on peut +même ajuster la taille des clusters jusqu'à un minimum de 512 octets +à la création. + +\subsubsection{Comment ajouter un répertoire à votre PATH} + +Il existe dans votre système des variables qui +agissent un peu comme des variables globales à tous vos programmes. On +appelle cet ensemble de variables \emph{l'environnement}. Chaque +programme hérite à son démarrage d'une copie de l'environnement. Il peut +modifier les valeurs des variables, ajouter ou enlever des variables, +mais les modifications ne sont effectives que pour sa propre copie et +ne sont pas propagées aux autres programmes, sauf à ceux qu'il lance +lui-même. + +Votre variable PATH est une variable spéciale de l'environnement +utilisée pour chercher les programmes lorsque vous en demandez +l'exécution. Il y a une procédure différente pour modifier cette +variable selon que vous êtes sous Windows~9x, \acro{ME} ou +\acro{NT}/\acro{2K}/\acro{XP}. + +\begin{description} +\item[Windows 95/98] +Éditez votre fichier \path{autoexec.bat}. Dans ce fichier, vous +trouverez une ligne commençant par \path{PATH=} et suivie par une +liste de répertoires séparés par des points-virgules. Ajoutez le répertoire +contenant les programmes exécutables au bout de cette ligne. Cette +ligne ressemble alors à la suivante : +\begin{verbatim} +PATH=C:\windows;C:\windows\system;C:\TeXLive2007\bin\win32 +\end{verbatim} +Les modifications ne prendront effet qu'après redémarrage de la machine. +\item[Windows ME] + Vous devez utiliser le programme + \path{C:\string\windows\string\system\string\msconfig.exe} pour pouvoir + modifier une des + variables d'environnement. Dans ce programme, choisissez l'onglet + Environnement, ensuite ajoutez ou modifiez la variable de votre + choix. Il faut alors redémarrer la machine pour que les modifications + prennent effet. +\item[Windows NT/2K/XP] + Ouvrez le \guiseq{Panneau~de~Contrôle}, accessible depuis le menu + \guiseq{Démarrer\arw} \guiseq{Paramètres\arw Panneau~de~Contrôle}. + Ouvrez l'icône Système, la fenêtre des \guiseq{Propriétés système} + s'ouvre. Choisissez l'onglet \textsf{Environnement} ou cherchez un + bouton \guiseq{Variables d'environnement} +parmi les différentes boîtes de dialogue offertes. +Vous pouvez maintenant modifier vos propres variables d'environnement. +Il est à noter que les variables d'environnement système communes à +tous les utilisateurs sont également affichées. Vous ne pouvez les +modifier que si vous avez les droits d'administrateur. Si c'est le +cas, vous pouvez modifier la variable \path{PATH} pour tous les +utilisateurs du système -- mais vous devez savoir précisément ce que +vous faites. + +S'il y a déjà un \path{PATH} défini pour votre compte utilisateur, cliquez +dessus. Dans le champ \textsf{Variable} apparaît \path{PATH} et dans le champ +\textsf{Valeur}, la liste courante de répertoires séparés par des +points-virgules. Ajoutez les répertoires où se trouvent vos exécutables (i.e. +\path{C:\string\TeXLive2007\string\bin\string\win32}). Si la variable +\path{PATH} n'est pas encore définie, il suffit de taper son nom dans le champ +\textsf{Variable} et la valeur initiale que vous souhaitez lui donner dans le +champ \textsf{Valeur}. Important : cliquez sur le bouton \textsf{Appliquer} +avant de cliquer sur \textsf{Ok}, de cette façon, les modifications seront +propagées immédiatement à la session courante. Soyez prudent quand vous +modifiez les variables d'environnement. +\end{description} + +Le meilleur moyen de savoir si une variable a été correctement définie +consiste à ouvrir une console et à taper +\begin{verbatim} +set VARIABLE +\end{verbatim} +la valeur correspondante doit alors être affichée.. + +\subsubsection{Les moteurs \TeX{}} + +En lisant la documentation de \Webc{}, on voit +que les différents programmes dérivés de \TeX{} +utilisent le même moteur de base. Par exemple, \path{tex.exe} et +\path{latex.exe} sont des copies exactes du même programme, mais +chacun utilise un fichier de format différent, en se basant sur le nom +par lequel il a été invoqué. + +Sous Unix, ce mode de fonctionnement est réalisé en faisant appel aux +\emph{liens symboliques}. On peut ainsi économiser un peu d'espace disque, +car plusieurs moteurs de base sont utilisés avec différents fichiers +de format. + +L'API Win32 ne connaît pas les liens symboliques. Dans le but +d'économiser presqu'autant d'espace disque, tous les moteurs +\TeX{} de base ont été mis dans des DLL (\emph{Dynamic Linked + Library}). Ceci se traduit par l'aspect suivant pour les fichiers : +\begin{alltt} + 2006-11-23 07:06 2 560 latex.exe + 2007-01-06 23:54 1 073 664 pdftex.dll + 2006-01-28 08:05 2 560 pdftex.exe +\end{alltt} +\noindent et le fichier \path{latex.exe} n'est ni plus ni moins qu'une copie +presqu'identique du fichier \path{pdfetex.exe}, utilisant le même moteur +\path{pdftex.dll}. La même astuce a été utilisée pour la famille de +programmes \path{mktex*.exe} qui utilisent tous la bibliothèque +\path{mktex.dll}. + +Il existe même un outil générique appelé \path{irun.exe} qui permet +de simuler les liens durs de Unix sous Win32, mais uniquement pour les +fichiers \file{.exe}. + +\subsection{En cas de problème} +\label{sec:troubleshooting} + +\subsubsection{Que faire si \texttt{latex} ne trouve pas vos fichiers ?} + +\begin{itemize} +\item \cmdname{kpsewhich} est l'outil de choix pour trouver la source + de n'importe quel problème. Malheureusement, \cmdname{kpsewhich} + écrit le résultat de ses recherches sur le flux \path{stderr}, et + les anciennes versions de la console de Windows ne savaient pas + rediriger ce flux vers un fichier\footnote{En fait, les systèmes + Windows NT/2K/XP savent le faire, grâce à leur nouvel interpréteur + de commandes, mais l'astuce spécifique à \KPS{}-Win32 fonctionne + sur toutes les consoles.}. Pour des besoins de diagnostic, vous + pouvez positionner temporairement une variable d'environnement en tapant + dans une console : +\begin{verbatim} +SET KPATHSEA_DEBUG_OUTPUT=err.log +\end{verbatim} +Vous pouvez également définir un niveau de trace : +\begin{verbatim} +SET KPATHSEA_DEBUG=-1 +\end{verbatim} + +La trace de l'exécution des commandes suivantes sera conservée dans le +fichier \filename{err.log}. Si vous voulez rediriger le flux stderr sur le +flux stdout, ce qui n'est normalement possible sous aucune version de Windows, +il vous suffit de faire : +\begin{verbatim} +SET KPATHSEA_DEBUG_OUTPUT=con: +\end{verbatim} +De cette manière, vous pourrez rediriger à la fois stdout et stderr +dans le même fichier. + +\item En supposant que l'installation a été faite dans + \texttt{C:/TeX}, vérifiez les valeurs suivantes :\\ + \begin{tabular}{ll} + \texttt{kpsewhich -expand-path \$SELFAUTOPARENT} & \texttt{C:/TeX} \\ + \texttt{kpsewhich -expand-path \$TEXMF} & \texttt{C:/TeX/texmf....} \\ + \texttt{kpsewhich -expand-path \$TEXMFCNF} & + \texttt{.;C:/TeX/texmf-var/web2c;} \\ + \texttt{kpsewhich -expand-var \$TEXINPUTS} & \texttt{.;C:/TeX/texmf/tex//} + \end{tabular} + +\item Si des variables d'environnement liées à TeX sont + positionnées dans votre environnement, enlevez-les, car elles + masquent les valeurs existant dans le fichier \filename{texmf.cnf}. + +\item Vérifiez les valeurs de :\\ + \begin{tabular}{ll} + \texttt{kpsewhich cmr10.tfm} & \texttt{C:/TeX/texmf-dist/fonts/tfm/public/cm/cmr10.tfm}\\ + \texttt{kpsewhich latex.fmt}& \texttt{C:/TeX/texmf-var/web2c/latex.fmt} + \end{tabular} + +\item à ce point, si tout est correct, \TeX{} et tous les + programmes associés doivent fonctionner. Si ce n'est pas le cas, + vous devez poursuivre vos investigations avec l'option \path{-debug=n} de + \path{kpsewhich} et contrôler toutes les valeurs. Essayez + d'identifier et de signaler le problème. +\end{itemize} + +\subsubsection{Que faire si votre installation ne fonctionne toujours + pas selon vos attentes ?} + +Il faut se poser plusieurs questions : +\begin{enumerate} +\item Est-ce que \path{tex.exe} est bien dans mon \path{PATH} ? + +\item Est-ce que la variable d'environnement \path{TEXMFCNF} est bien + positionnée à \\ + \path{C:/TeXLive2007/texmf-var/web2c} (valeur par défaut) ? + +\item Est-ce qu'il y a des erreurs dans le fichier de log \file{tlmpgui.log} + généré lors de l'installation par \filename{tlmpgui} ? Ce fichier est dans + le répertoire \file{TEMP}, les erreurs sont repérées par la séquence + \samp{Error}. + +\item Y a-t-il des correctifs de bogues correspondant au problème à + \url{http://www.tug.org/tex-live.html} (improbable, mais il vaut + mieux le vérifier). + +\end{enumerate} + +Le logiciel \TL{} est composé de centaines de +programmes et de milliers de fichiers d'origines très diverses. Il +est pratiquement impossible de prédire toutes les causes possibles de +problèmes. Néanmoins, nous ferons notre possible pour vous aider dans +tous les cas (voir section~\ref{sec:help}, \p.\pageref{sec:help}). + +% don't use \Webc so the \uppercase in the headline works. +%\section{Guide d'utilisation du système \protect\Webc{}} +\section{Guide d'utilisation du système Web2C} + +\Webc{}est une collection intégrée de programmes relatifs à \TeX, +c.-à-d. \TeX{} lui-même, \MF{}, \MP, \BibTeX{}, etc. +C'est le c\oe ur de \TL{}. + +Un peu d'histoire : la première implémentation a été réalisée par Tomas +Rokicki qui, en 1987, a développé un premier système \TeX{}-to-C en adaptant +les \textit{change files} pour Unix (travail de Howard Trickey et Pavel Curtis +principalement). Tim Morgan assura la maintenance du système, dont le nom fut +remplacé durant cette période par Web-to-C. En 1990, Karl Berry reprit le +travail, assisté par des dizaines de contributeurs, et en 1997 il passa le +relais à Olaf Weber. + +Le système \Webc{} fonctionne sur Unix, les systèmes Windows 32 bits, +\MacOSX{} et de nombreux autres systèmes d'exploitation. Il utilise les +sources originales de D.E.~Knuth pour \TeX{} et les autres programmes de base +écrits en \web{} qui sont tous traduits en langage C. Les composants du noyau +de \TeX{} sont : + +\begin{description} +%\renewcommand{\makelabel}[1]{\descriptionlabel{\makebox[0.6in][l]{#1}}} +\item[bibtex] Gère les bibliographies. +\item[dmp] \cmdname{troff} vers MPX (dessins \MP{}). +\item[dvicopy] Copie le fichier \dvi{} en supprimant les fontes +virtuelles. +\item[dvitomp] Convertit le fichier \dvi{} en MPX (dessins \MP{}). +\item[dvitype] Convertit le fichier \dvi{} en un texte lisible. +\item[gftodvi] Visualisation de fontes génériques GF. +\item[gftopk] Convertit les fontes génériques GF en fontes bitmap PK. +\item[gftype] Convertit le fichier GF en un texte lisible. +\item[makempx] Typographie des étiquettes \MP{}. +\item[mf] Création de fontes. +\item[mft] Mise en page de code source \MF{}. +\item[mpost] Création de diagrammes techniques. +\item[mpto] Extraction d'étiquettes \MP{}. +\item[newer] Comparaison de dates de modification (fichiers). +\item[patgen] Création de motifs de césure. +\item[pktogf] Convertit les fontes bitmap PK en fontes génériques GF. +\item[pktype] Convertit les fontes PK en un texte lisible. +\item[pltotf] Convertit les fichiers PL (lisibles) en TFM. +\item[pooltype] Affiche les fichiers \web{} pool. +\item[tangle] \web{} vers Pascal. +\item[tex] Composition de textes. +\item[tftopl] Convertit les fichiers TFM en PL (lisibles). +\item[vftovp] Convertit les fontes virtuelles VF en VPL (lisibles). +\item[vptovf] Convertit les fontes VPL en fontes virtuelles VF. +\item[weave] \web{} vers \TeX. +\end{description} + +La syntaxe et les fonctions précises de ces programmes sont décrites +dans +la documentation des composants individuels et dans le manuel \Webc{} +lui-même. Toutefois, connaître un certain nombre de principes +régissant +l'ensemble de la famille de programmes peut aider à exploiter de +façon +optimale votre installation \Webc{}. + + Presque tous ces programmes suivent les +options standard de \acro{GNU} : +\begin{description} +%\renewcommand{\descriptionlabel}[1]{\makebox[1.4in][l]{#1}} + \item[\texttt{-{}-help}] imprime le sommaire de l'utilisation, + \item[\texttt{-{}-verbose}] imprime le rapport détaillé du processus, + \item[\texttt{-{}-version}] imprime seulement le numéro de version. +\end{description} + +Pour localiser les fichiers, les programmes \Webc{} utilisent la +bibliothèque de recherche \KPS{}. Cette bibliothèque utilise une +combinaison de +variables d'environnement et un certain nombre de fichiers de +paramètres pour optimiser la recherche dans l'énorme arborescence +\TeX{}. +\Webc{} peut exécuter une recherche dans plusieurs arborescences +simultanément, ce qui est utile si l'on souhaite maintenir la +distribution standard de \TeX{} et les extensions locales dans deux +arborescences distinctes. Afin d'accélérer la recherche de fichiers, la +racine de chaque arborescence possède un fichier \file{ls-R} contenant +une +entrée donnant le nom et le chemin de chaque fichier situé sous la +racine. + +\subsection{Kpathsea et la recherche de fichiers} + +Décrivons en premier lieu le mécanisme de recherche de la bibliothèque +\KPS{}. + +Nous appelons \emph{chemin de recherche} une liste, séparée par +\og deux-points\fg{} ou \og point-virgule\fg{}, d'éléments, appelés +\emph{éléments de chemin}, qui sont des noms de répertoires. +Un chemin de recherche peut provenir de plusieurs sources. +Pour rechercher un fichier \samp{my-file} le long +d'un chemin \samp{.:/dir}, \KPS{} vérifie chaque élément du +chemin : +d'abord \filename{./my-file}, puis \filename{/dir/my-file}, et renvoie la +première occurrence (voire toutes). + +Afin d'optimiser l'adaptation à tous les systèmes d'exploitation, +\KPS{} peut utiliser dans les noms de fichiers des séparateurs +différents +de deux-points (\samp{:}) et barre oblique (\samp{/}) + pour les systèmes non-Unix. + +Pour vérifier un élément de chemin particulier \var{p}, \KPS{} +vérifie d'abord si une base de données existante (voir +page~\pageref{Filename-database}) contient \var{p}, +c.-à-d. si la base de données se trouve dans un +répertoire qui est un préfixe de \var{p}. Si oui, la spécification +du chemin est comparée avec le contenu de la base de données. + +Si la base de données n'existe pas, si elle ne s'applique pas à cet +élément de chemin ou si elle ne contient aucune correspondance, +la recherche est lancée sur tout le système de fichiers (si cela +n'a +pas été interdit +par une commande commençant par \samp{!!} + et si le fichier cherché est censé exister). +\KPS{} construit la liste de répertoires qui correspondent +à cet élément de chemin, puis cherche le fichier dans chaque +élément +de cette liste. + +La condition \og le fichier est censé exister\fg{} est liée aux +fichiers~\samp{.vf} et aux fichiers d'entrée lus par la commande \TeX\ +\cs{openin}. +De tels fichiers peuvent ne pas exister (par exemple \file{cmr10.vf}), +il +est donc inutile de les rechercher sur le disque. De plus, si vous +n'actualisez pas le fichier \file{ls-R} lors de l'installation d'un +nouveau fichier +\samp{.vf}, +il ne sera jamais trouvé. +Chaque élément de chemin est alors vérifié : d'abord dans +la base de données puis sur le disque. Si une occurrence est +trouvée, la recherche s'arrête et le résultat est obtenu. + +Bien que l'élément de chemin le plus simple et le plus fréquent +soit un +nom de répertoire, \KPS{} supporte d'autres types d'éléments dans +les +chemins de recherche : des valeurs par défaut différentes pour chaque +programme, des noms de variables d'environnement, des valeurs de +fichiers de +configuration, les répertoires de l'utilisateur et la recherche +récursive +de sous-répertoires. Nous disons alors que \KPS{} \emph{étend} un +élément, c'est-à-dire que \KPS{} transforme toutes ces +spécifications +en noms de répertoires de base. Cette opération est décrite dans les sections +suivantes. + +Notons que si le nom de fichier cherché est absolu ou explicitement +relatif, c'est-à-dire commençant par \samp{/}, \samp{./} ou +\samp{../}, \KPS{} ne vérifie que l'existence de ce fichier. +\ifSingleColumn +\else +\begin{figure*} +\verbatiminput{examples/ex5.tex} +\setlength{\abovecaptionskip}{0pt} + \caption{Un exemple de fichier de configuration} + \label{fig:config-sample} +\end{figure*} +\fi + +\subsubsection{Les différentes sources} +\label{Path-sources} + +Un chemin de recherche peut provenir de plusieurs sources. Voici l'ordre +dans lequel \KPS\ les utilise. + +\begin{enumerate} +\item + Une variable d'environnement définie par l'utilisateur, par exemple + \envname{TEXINPUTS}. Les variables d'environnement avec une + extension attachée (nom de programme) sont d'abord prises en compte : + par exemple, si \samp{latex} est le nom du programme exécuté, + \envname{TEXINPUTS.latex} passera avant \envname{TEXINPUTS}. +\item + Un fichier de configuration de programme spécifique, par exemple une +ligne + \og \texttt{S /a:/b}\fg{} dans le fichier \file{config.ps} de \cmdname{dvips}. +\item + Un fichier de configuration \file{texmf.cnf} de \KPS{} contenant une + ligne telle que \\ \samp{TEXINPUTS=/c:/d} (voir ci-dessous). +\item La valeur par défaut obtenue à la compilation. +\end{enumerate} +\noindent On peut voir chacune de ces valeurs pour un chemin de +recherche +donné en utilisant l'option de débogage (voir page~\pageref{Debugging}). + +\subsubsection{Fichiers de configuration} + +\begingroup\tolerance=3500 +\KPS{} lit dans les \emph{fichiers de configuration à + l'exécution} appelés \file{texmf.cnf} les chemins de recherche et +d'autres définitions. Le chemin pour accéder à ces fichiers dans +l'arborescence est stocké dans la variable \envname{TEXMFCNF} +(par défaut ces +fichiers se trouvent dans le sous-répertoire \file{texmf/web2c}). +\emph{Tous} les fichiers \file{texmf.cnf} se trouvant dans le chemin +de recherche vont être lus et les définitions provenant +de fichiers précédents écraseront celles des fichiers suivants. Par +exemple, avec un chemin tel que \verb|.:$TEXMF|, les définitions du +fichier \filename{./texmf.cnf} écrasent celles de +\verb|$TEXMF/texmf.cnf|. +\endgroup + +\begin{itemize} +\item + Les commentaires sont signalés par un \texttt{\%} et + se terminent à la fin de la ligne. +\item + Les lignes vides sont ignorées. +\item + Un \bs{} à la fin d'une ligne joue le rôle d'un lien entre deux + lignes, c'est-à-dire que la ligne courante se poursuit à la ligne + suivante. Dans ce cas, les espaces présents au début de la ligne + suivante ne sont pas ignorés. +\item + Toutes les autres lignes sont de la forme : +\begin{alltt} + \emph{variable}[.\emph{progname}] [=] \emph{value} +\end{alltt}% + où le \samp{=} et les espaces autour sont optionnels. +\item + Le nom de la \ttvar{variable} peut contenir n'importe + quel caractère autre que les espaces, \samp{=}, ou \samp{.}, mais + on recommande d'utiliser \samp{A-Za-z\_} pour éviter les + problèmes. +\item + Si \samp{.\var{progname}} est présent, sa définition + s'applique seulement si le programme exécuté se nomme + \texttt{\var{progname}} ou \texttt{\var{progname}.exe}. Ceci permet + par exemple à différentes variantes de \TeX{} d'avoir des chemins de + recherche différents. +\item + \var{value} peut contenir n'importe quel caractère + excepté \code{\%} et \samp{@}. + L'option + \code{\$\var{var}.\var{prog}} + n'est pas disponible à droite du signe \samp{=} ; + à la place, on doit utiliser une variable supplémentaire. Un +\samp{;}\ dans \var{value} +est compris comme un + \samp{:}\ si on travaille sous Unix ; ceci est très utile et + permet d'avoir un seul \file{texmf.cnf} pour les systèmes Unix, + \acro{MS-DOS} et Windows. +\item + Toutes les définitions sont lues avant tout désarchivage ou + décompactage, de telle façon que les variables peuvent être + référencées avant d'être définies. +\end{itemize} +Voici un fichier de configuration illustrant les points +précédents +\ifSingleColumn + +%\verbatiminput{examples/ex5.tex} % trop petit (df) +\begin{verbatim} +TEXMF = {$TEXMFLOCAL,!!$TEXMFMAIN} +TEXINPUTS.latex = .;$TEXMF/tex/{latex,generic;}// +TEXINPUTS.fontinst = .;$TEXMF/tex//;$TEXMF/fonts/afm// +% e-TeX related files +TEXINPUTS.elatex = .;$TEXMF/{etex,tex}/{latex,generic;}// +TEXINPUTS.etex = .;$TEXMF/{etex,tex}/{eplain,plain,generic;}// +\end{verbatim} + +\else +dans la figure~\ref{fig:config-sample}. +\fi + +\subsubsection{Expansion d'un chemin de recherche} +\label{Path-expansion} + +\KPS{} reconnaît certains caractères et constructions spéciales dans +les chemins de recherche, semblables à ceux disponibles dans les +\textit{shells} Unix. Ainsi, le chemin complexe, +\verb+~$USER/{foo,bar}//baz+ %$ +étend la recherche vers tous les sous-répertoires situés sous les +répertoires \file{foo} et \file{bar} dans le répertoire utilisateur +\texttt{\$USER} contenant un répertoire ou un fichier appelé %$ +\file{baz}. Ces expansions sont explicitées dans les sections +suivantes. + +\subsubsection{Expansion par défaut} +\label{Default-expansion} + +\tolerance=2500 +Si le chemin de recherche le plus prioritaire (voir +section~\ref{Path-sources}) contient un \samp{:} +\emph{supplémentaire} (c.-à-d. en début ou fin de ligne ou +double), \KPS{} insère à cet endroit le chemin suivant dont la +priorité définie est immédiatement inférieure. Si ce chemin inséré +possède un \samp{:} supplémentaire, le même processus se +répète pour le chemin prioritaire suivant. +Par exemple, étant donné une variable d'environnement définie ainsi + +\tolerance=1500 + +\begin{alltt} +> \Ucom{setenv TEXINPUTS /home/karl:} +\end{alltt} +la valeur de \code{TEXINPUTS} d'après le fichier \file{texmf.cnf} étant + +\begin{alltt} + .:\$TEXMF//tex +\end{alltt} +alors la valeur finale utilisée pour la recherche sera + +\begin{alltt} + /home/karl:.:\$TEXMF//tex +\end{alltt} + +Comme il est inutile d'insérer la valeur par défaut en plusieurs +endroits, \KPS{} applique la substitution à seulement un \samp{:} +supplémentaire et laisse les autres inchangés : il cherche d'abord un +\samp{:} en début de ligne, puis en fin de ligne et enfin un double +\samp{:}. + +\subsubsection{Expansion spécifiée par les accolades} + +Option utile, l'expansion par le biais des accolades +signifie, par exemple, que \verb+v{a,b}w+ va permettre la recherche +dans \verb+vaw:vbw+. Les définitions emboîtées sont autorisées. Ceci +peut être utilisé pour établir des hiérarchies \TeX{} multiples en +attribuant une liste entre accolades à \code{\$TEXMF}. Par exemple, +dans \file{texmf.cnf}, on trouve une définition du type suivant +(il y a en fait plus de répertoires) : +\begin{verbatim} + TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFSYSVAR,!!$TEXMFMAIN} +\end{verbatim} +Avec ceci, on peut écrire quelque chose comme +\begin{verbatim} + TEXINPUTS = .;$TEXMF/tex// +\end{verbatim} +%$ +ce qui signifie que, après avoir cherché dans le répertoire courant, les +arborescences complètes \code{\$TEXMFHOME/tex} suivie de +\code{\$TEXMFLOCAL/tex} (sur le disque) et ensuite les arborescences +\code{!!\$TEXMFVAR/tex} et \code{!!\$TEXMFMAIN/tex} +(définies dans le fichier de référence \file{ls-R} \emph{seulement}) seront +inspectées. C'est un moyen pratique permettant d'utiliser en parallèle deux +distributions \TeX{}, une \og gelée\fg{} (sur un \CD, par exemple) et une +autre régulièrement mise à jour avec de nouvelles versions quand elles +deviennent disponibles. En utilisant la variable \code{\$TEXMF} dans toutes +les définitions, on est toujours sûr d'inspecter d'abord l'arborescence la +plus récente. + +\subsubsection{Expansion des sous-répertoires} +\label{Subdirectory-expansion} + +Deux barres \samp{//} ou plus consécutives dans une partie d'un chemin suivant +un répertoire \var{d} sont remplacées par tous les sous-répertoires de +\var{d} : d'abord les sous-répertoires directement présents dans +\var{d}, ensuite les sous-répertoires de ceux-ci, et ainsi de suite. À +chaque niveau, l'ordre dans lequel les répertoires sont inspectés est +\emph{non-déterminé}. + +Dans le cas où l'on spécifie une partie de nom de fichier après le +\samp{//}, seuls sont inclus les sous-répertoires auxquels le nom +correspond. Par exemple, \samp{/a//b} va correspondre aux répertoires +\file{/a/1/b}, \file{/a/2/b}, +\file{/a/1/1/b}, et ainsi de suite, mais pas à \file{/a/b/c} ni +\file{/a/1}. + +Des \samp{//} multiples et successifs dans un chemin sont possibles, +mais \samp{//} au début d'un chemin est ignoré. + +\subsubsection{Liste des caractères spéciaux et de leur signification : + récapitulatif} + +La liste suivante récapitule la signification des caractères spéciaux +dans les fichiers de configuration de \KPS{}. + +\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} + +\begin{ttdescription} + +\item[\CODE{:}] Séparateur dans un chemin de recherche ; au début + ou à la fin d'un chemin, il remplace le chemin par défaut. + +\item[\CODE{;}] Séparateur dans les systèmes non-Unix + (joue le rôle de \code{:}). + +\item[\CODE{\$}] Substitue le contenu d'une variable. + +\item[\CODE{\string~}] Représente le répertoire racine de + l'utilisateur. + +\item[\CODE{\char`\{...\char`\}}] Expansion par les accolades, + par exemple \verb+a{1,2}b+ devient \verb+a1b:a2b+. + +\item[\CODE{//}] La recherche concernera aussi les sous-répertoires + (peut être inséré n'importe où dans un chemin sauf au début). + +\item[\CODE{\%}] Début d'un commentaire. + +\item[\CODE{\bs}] Caractère de continuation de ligne (permet les + entrées sur plusieurs lignes). + +\item[\CODE{!!}] Cherche \emph{seulement} dans la base de + données pour localiser le fichier et \emph{ne cherche pas} sur le disque. + +\end{ttdescription} + +\subsection{Les bases de données} +\label{Filename-database} + +\KPS{} a une certaine profondeur d'investigation pour minimiser les +accès disque durant les recherches. Néanmoins, dans le cas de +distributions comprenant beaucoup de répertoires, inspecter chaque +répertoire possible pour un fichier donné peut durer excessivement +longtemps (ceci est typiquement le cas quand plusieurs centaines de +répertoires de polices de caractères doivent être parcourus). En +conséquence, \KPS{} peut utiliser un fichier texte appelé \file{ls-R} --- en +fait une base de données +construite au préalable --- qui fait correspondre +les fichiers à leur répertoire, ce qui permet d'éviter une recherche +exhaustive sur le disque. + +Un deuxième fichier appelé \file{aliases} (qui est également une base de +données) permet de donner +des noms différents aux fichiers listés dans \mbox{\file{ls-R}}. Ceci peut +aider à adapter ses fichiers source aux conventions de \acro{DOS}~8.3 pour les +noms de fichiers. + +\subsubsection{Le fichier base de données} +\label{ls-R} + +Comme nous l'avons expliqué ci-dessus, le nom du principal fichier-base de +données doit être \mbox{\file{ls-R}}. +Dans votre installation, vous pouvez en mettre un à la racine de chaque +arborescence \TeX{} que vous désirez voir +inspecter (\code{\$TEXMF} par défaut) ; la plupart des sites ont +une seule arborescence \TeX{}. \KPS{} cherche les fichiers \file{ls-R} +dans le chemin spécifié dans la variable \code{TEXMFDBS}. + +La meilleure façon de créer et mettre à jour le fichier \file{ls-R} +est d'exécuter le script \cmdname{mktexlsr} inclus dans la +distribution. Il est appelé par les divers scripts \cmdname{mktex}\dots\ +En principe, ce script exécute uniquement la commande +%cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R| +% Remplacé (df) car \path|...| plante à cause de \let\path\url. +\begin{alltt} +cd \var{/your/texmf/root} && \boi{}ls -1LAR ./ >ls-R +\end{alltt} +en supposant que la commande \code{ls} de votre système produise le bon +format de sortie (le \code{ls} de \acro{GNU} convient +parfaitement). Pour s'assurer que la base de données est toujours à +jour, le meilleur moyen est de la reconstruire en utilisant la table +des \code{cron}, de telle façon que le fichier \file{ls-R} prenne +automatiquement en compte les changements dans les fichiers +installés, par exemple après une installation ou une +mise à jour d'un composant \LaTeX{}. + +Si un fichier n'est pas trouvé dans la base de données, par défaut +\KPS{} décide de le chercher sur le disque. Par contre, si un élément du +chemin commence par \samp{!!}, \emph{seule} la base de données +sera inspectée pour cet élément, jamais le disque. + +\subsubsection{kpsewhich : programme de recherche dans une arborescence} +\label{Invoking-kpsewhich} + +Le programme \texttt{kpsewhich} effectue une recherche dans une +arborescence indépendamment de toute application. On peut le +considérer comme une sorte de \code{find} pour localiser des fichiers +dans les arborescences \TeX{} (ceci est largement utilisé dans les +scripts \cmdname{mktex}\dots\ de la distribution). + +\begin{alltt} +> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} +\end{alltt} +Les options spécifiées dans \ttvar{option} peuvent +commencer soit par \samp{-} soit par \samp{-{}-} ; n'importe quelle +abréviation claire est acceptée. + +\KPS{} considère tout argument non optionnel dans la ligne de commande +comme un nom de fichier et renvoie la première occurrence trouvée. Il +n'y a pas d'option pour renvoyer tous les fichiers ayant un nom +particulier (vous pouvez utiliser le \cmdname{find} d'Unix pour cela). + +Les options les plus importantes sont décrites ci-après. + +\begin{ttdescription} +%\renewcommand{\makelabel}[1]{\descriptionlabel{\makebox[1.2in]{#1}}} +\item[\texttt{-{}-dpi=\var{num}}]\mbox{} \\ + Définit la résolution à \ttvar{num} ; ceci affecte + seulement la recherche des fichiers \samp{gf} et \samp{pk}. \samp{-D} est un + synonyme pour assurer la compatibilité avec \cmdname{dvips}. Le défaut + est 600. +\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ + Définit le format pour la recherche à \ttvar{name}. + Par défaut, le format est estimé en fonction du nom de fichier. + Pour les formats qui n'ont pas de suffixe clair associé, comme les + fichiers de support \MP{} et les fichiers de configuration + \cmdname{dvips}, vous devez spécifier le nom connu de \KPS, comme + \texttt{tex} ou \texttt{enc files}. Exécutez la commande + \texttt{kpsewhich -{}-help} pour obtenir la liste précise. + +\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ + Définit le nom du mode comme étant \ttvar{string} ; +ceci affecte seulement la recherche des \samp{gf} et des \samp{pk}. +Pas d'option par défaut, n'importe quel mode sera trouvé. +\item[\texttt{-{}-must-exist}]\mbox{}\\ + Fait tout ce qui est possible pour trouver les fichiers, ce qui +inclut une recherche sur le disque. Par défaut, seule la base de +données \file{ls-R} est inspectée, dans un souci d'efficacité. +\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ + Recherche dans le chemin \ttvar{string} (séparé par +deux-points comme d'habitude), au lieu de prendre le chemin à partir +du nom de fichier. \samp{//} et toutes les expansions habituelles sont +supportées. + Les options \samp{-{}-path} et \samp{-{}-format} s'excluent mutuellement. +\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ + Définit le nom de programme comme étant \ttvar{name}. + Ceci peut affecter les chemins de recherche via l'option + \texttt{.\var{progname}} dans les fichiers de configuration. + Le défaut est \cmdname{kpsewhich}. +\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ + Montre le chemin utilisé pour la recherche des fichiers de type +\ttvar{name}. + On peut utiliser soit une extension de fichier (\code{.pk}, \code{.vf}, + etc.), soit un nom de fichier, comme avec l'option \samp{-{}-format}. +\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ + Définit les options de débogage comme étant + \ttvar{num}. +\end{ttdescription} + +\subsubsection{Exemples d'utilisation} +\label{SExamplesofuse} + +Jetons un coup d'{\oe}il à \KPS{} en action ; voici une recherche +toute simple : + +\begin{alltt} +> \Ucom{kpsewhich article.cls} +/usr/local/texmf-dist/tex/latex/base/article.cls +\end{alltt} +Nous recherchons le fichier \file{article.cls}. Puisque le suffixe +\file{.cls} est non-ambigu, nous n'avons pas besoin de spécifier que +nous voulons rechercher un fichier de type \optname{tex} (répertoires des +fichiers sources de \TeX{}). Nous le trouvons dans le sous-répertoire +\filename{tex/latex/base} du répertoire racine \samp{TEXMF}. De même, + le suffixe non-ambigu permet de trouver facilement les autres fichiers. +\begin{alltt} +> \Ucom{kpsewhich array.sty} + /usr/local/texmf-dist/tex/latex/tools/array.sty +> \Ucom{kpsewhich latin1.def} + /usr/local/texmf-dist/tex/latex/base/latin1.def +> \Ucom{kpsewhich size10.clo} + /usr/local/texmf-dist/tex/latex/base/size10.clo +> \Ucom{kpsewhich small2e.tex} + /usr/local/texmf-dist/tex/latex/base/small2e.tex +> \Ucom{kpsewhich tugboat.bib} + /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib +\end{alltt} + +Le dernier exemple est une base de données bibliographiques pour \BibTeX{} +servant aux articles de \textsl{TUGBoat}. + +\begin{alltt} +> \Ucom{kpsewhich cmr10.pk} +\end{alltt} +Les fichiers de glyphes de fontes bitmaps, de type +\file{.pk}, sont +utilisés pour l'affichage par des programmes comme \cmdname{dvips} et +\cmdname{xdvi}. Rien n'est renvoyé dans ce cas puisque il n'y a pas +de fichiers Computer Modern \file{.pk} pré-créés sur nos systèmes +(nous utilisons les versions type~1 du \TL{}). +\begin{alltt} +> \Ucom{kpsewhich wsuipa10.pk} +\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk +\else /usr/local/texmf-var/fonts/pk/ljfour/public/ +... wsuipa/wsuipa10.600pk +\fi\end{alltt} +Pour ces fontes (alphabet phonétique de l'université Washington), +nous avons dû créer les fichiers \file{.pk} et, puisque le mode \MF{} par +défaut sur notre installation est \texttt{ljfour} avec une résolution de +base de 600\dpi{} \textit{(dots per inch)}, cette instance est trouvée. +\begin{alltt} +> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} +\end{alltt} +Dans ce cas, lorsque l'on spécifie que nous recherchons une +résolution de 300\dpi{} (\texttt{-dpi=300}) nous voyons qu'aucune fonte +pour cette résolution n'est disponible dans le système. En fait, un +programme comme \cmdname{dvips} ou \cmdname{xdvi} ne s'en +préoccuperait pas et créerait les fichiers \file{.pk} à la +résolution demandée en utilisant le script \cmdname{mktexpk}. + +Intéressons-nous à présent aux fichiers d'en-tête et de configuration +pour \cmdname{dvips}. +Regardons en premier le fichier \file{tex.pro} communément utilisé +pour le support de \TeX{} avant de regarder le fichier +de configuration générique (\file{config.ps}) et la liste des fontes +\PS{} \file{psfonts.map}. Depuis l'édition 2004, les fichiers +\file{.map} et les fichiers de codage ont changé de place dans +l'arborescence \dirname{texmf}. Comme le suffixe \file{.ps} est +ambigu, nous devons spécifier quel type particulier du fichier +\texttt{config.ps} nous considérons (\optname{dvips config}). +\begin{alltt} +> \Ucom{kpsewhich tex.pro} + /usr/local/texmf/dvips/base/tex.pro +> \Ucom{kpsewhich -{}-format="dvips config" config.ps} + /usr/local/texmf-var/dvips/config/config.ps +> \Ucom{kpsewhich psfonts.map} + /usr/local/texmf-var/fonts/map/dvips/updmap/psfonts.map +\end{alltt} + +Regardons plus en détail les fichiers de support Times +\PS{} d'\acro{URW}. Leur nom standard dans le schéma de nommage des fontes +est \samp{utm}. Le premier fichier que nous voyons est le +fichier de configuration, qui contient le nom du fichier +de la liste : +\begin{alltt} +> \Ucom{kpsewhich -{}-format="dvips config" config.utm} + /usr/local/texmf-dist/dvips/psnfss/config.utm +\end{alltt} +Le contenu de ce fichier est +\begin{alltt} + p +utm.map +\end{alltt} +qui pointe vers le fichier \file{utm.map}, que nous cherchons à +localiser ensuite. +\begin{alltt} +> \Ucom{kpsewhich utm.map} + /usr/local/texmf-dist/fonts/map/dvips/times/utm.map +\end{alltt} +Ce fichier liste les noms des fichiers des +fontes \PS{} de type~1 dans la collection URW. Son contenu +ressemble à (nous ne montrons qu'une partie des lignes) : +\begin{alltt} +utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} +\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb +\else /usr/local/texmf-dist/fonts/type1/ +... urw/utm/utmr8a.pfb +\fi\end{alltt} + +Il devrait être clair, d'après ces quelques exemples, qu'il est facile +de trouver l'endroit où se cache un fichier donné. C'est +particulièrement important si vous suspectez que c'est, pour une +raison quelconque, une mauvaise version du fichier qui est utilisée, +puisque \cmdname{kpsewhich} va vous montrer le premier fichier +trouvé. + +\subsubsection{Opérations de débogage} +\label{Debugging} + +Il est quelquefois nécessaire de savoir comment un programme référence +les fichiers. Pour permettre cela, \KPS{} offre +plusieurs niveaux de débogage : +\begin{ttdescription} +\item[\texttt{\ 1}] Appels à \texttt{stat} (test d'existence de fichier). Lors d'une + exécution utilisant une base de données \file{ls-R} à jour, ce niveau + ne devrait donner presque aucune information en sortie. +\item[\texttt{\ 2}] Références aux différentes tables (comme la base + de données \file{ls-R}, les fichiers de correspondance de fontes, les fichiers de + configuration). +\item[\texttt{\ 4}] Opérations d'ouverture et de fermeture des + fichiers. +\item[\texttt{\ 8}] Information globale sur la localisation des types + de fichiers recherchés par \KPS. Ceci est utile pour trouver où a été + défini le chemin particulier pour un fichier. +\item[\texttt{16}] Liste des répertoires pour chaque élément du + chemin (utilisé uniquement en cas de recherche sur le disque). +\item[\texttt{32}] Recherche de fichiers. +\end{ttdescription} +Une valeur de \texttt{-1} activera toutes les options ci-dessus ; en +pratique, c'est habituellement la valeur la plus adaptée. + +De la même façon, avec le programme \cmdname{dvips}, en utilisant une +combinaison d'options de débogage, on peut suivre en détail la +localisation des +différents fichiers. De plus, lorsqu'un fichier n'est +pas trouvé, la trace du débogage montre les différents répertoires dans +lesquels le programme va chercher tel ou tel fichier, donnant ainsi +des indices sur le problème. + +Généralement, comme la plupart des programmes appellent la +bibliothèque \KPS{} en interne, on peut sélectionner une option de +débogage en utilisant la variable d'environnement +\envname{KPATHSEA\_DEBUG}, et en la définissant égale à la valeur (ou +à une combinaison de valeurs) décrite(s) dans la liste ci-dessus. + +Note à l'intention des utilisateurs de Windows : il n'est pas facile +de rediriger les messages d'erreur vers un fichier sur ces +systèmes. À des fins de diagnostic, vous pouvez temporairement +affecter \texttt{KPATHSEA\_DEBUG\_OUTPUT=err.log} pour capturer le flux +standard d'erreur dans le fichier \texttt{err.log}. + +Considérons comme exemple un petit fichier source \LaTeX{}, +\file{hello-world.tex}, dont le contenu est le suivant. +\begin{verbatim} + \documentclass{article} + \begin{document} + Hello World! + \end{document} +\end{verbatim} +Ce petit fichier utilise simplement la fonte \file{cmr10}, aussi +allons voir comment \cmdname{dvips} prépare le fichier \PS{} +(nous voulons utiliser la version type~1 +des fontes Computer Modern, d'où l'option \texttt{-Pcms}). +\begin{alltt} +> \Ucom{dvips -d4100 hello-world -Pcms -o} +\end{alltt} +Dans ce cas, nous avons combiné le niveau 4 de débogage de +\cmdname{dvips} (chemins des fontes) avec l'option d'expansion des +éléments du chemin de \KPS\ (voir \cmdname{dvips} Reference Manual, +\OnCD{texmf/doc/html/dvips/dvips_toc.html} sur le \DVDlive{}). +La sortie (légèrement formatée) apparaît dans la +figure~\ref{fig:dvipsdbga}. +\begin{figure*}[tp] +\centering +\input{examples/ex6a.tex} +\caption{Recherche des fichiers de configuration}\label{fig:dvipsdbga} + +\bigskip + +\input{examples/ex6b.tex} +\caption{Recherche du fichier prolog}\label{fig:dvipsdbgb} + +\bigskip + +\input{examples/ex6c.tex} +\caption{Recherche du fichier de fontes}\label{fig:dvipsdbgc} +\end{figure*} + +\cmdname{dvips} commence par localiser ses fichiers de +fonctionnement. D'abord, \file{texmf.cnf} est trouvé, ce qui donne les +définitions pour les chemins de recherche servant à localiser les +autres fichiers, ensuite le fichier base de données \file{ls-R} (pour +optimiser la recherche des fichiers) et le fichier \file{aliases}, qui +permet de déclarer plusieurs noms (\p.ex., un nom \acro{DOS} de type +8.3 court et une version longue plus naturelle) pour le même +fichier. Ensuite \cmdname{dvips} continue en cherchant le fichier de +configuration générique \file{config.ps} avant de rechercher le fichier +de paramétrisation \file{.dvipsrc} (qui, dans notre cas, \emph{n'est +pas trouvé}). Enfin, \cmdname{dvips} localise le fichier de +configuration pour les fontes \PS{} Computer Modern +\file{config.cms} (ceci est lancé par l'option \mbox{\texttt{-Pcms}} de la +commande \cmdname{dvips}). Ce fichier contient la liste des fichiers + qui définissent la relation entre les noms des fontes +selon \TeX{}, selon \PS{} et dans le système de fichiers. +\begin{alltt} +> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} + p +ams.map + p +cms.map + p +cmbkm.map + p +amsbkm.map +\end{alltt} +\cmdname{dvips} veut chercher tous ces fichiers, y compris le +fichier générique d'association \file{psfonts.map}, qui est toujours +chargé (il contient des déclarations pour les fontes \PS{} les +plus communément utilisées ; voir la dernière partie de la Section +\ref{SExamplesofuse} pour plus de détails sur la gestion du fichier +d'association \PS{}). + +Arrivé là, \cmdname{dvips} s'identifie à l'utilisateur : + \begin{alltt} + This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) + \end{alltt} + +\ifSingleColumn +pour continuer ensuite en cherchant le fichier prologue \file{texc.pro}, +\begin{alltt}\small +kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro +\end{alltt} +\else +pour continuer ensuite en cherchant le fichier prologue \file{texc.pro} +(voir la figure~\ref{fig:dvipsdbgb}). +\fi + +Après avoir trouvé ce fichier, \cmdname{dvips} affiche la date et +l'heure, et nous informe qu'il va générer le fichier +\file{hello-world.ps}, puis qu'il a besoin du fichier de fonte +\file{cmr10}, et que ce dernier est déclaré comme \og résident\fg{} +(pas besoin de bitmaps) : +\begin{alltt}\small +TeX output 1998.02.26:1204' -> hello-world.ps +Defining font () cmr10 at 10.0pt +Font cmr10 is resident. +\end{alltt} +Maintenant la recherche concerne le fichier \file{cmr10.tfm}, qui est +trouvé, puis quelques fichiers de prologue de plus (non montrés) sont +référencés ; finalement le fichier de la fonte type~1 \file{cmr10.pfb} +est localisé et inclus dans le fichier de sortie (voir la dernière ligne). +\begin{alltt}\small +kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, + path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: + /var/tex/fonts/tfm//). +kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm +kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, + ... + +kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb +[1] +\end{alltt} + +\subsection{Options à l'exécution} + +\Webc{} offre la possibilité de contrôler à l'exécution bon nombre de +paramètres concernant la mémoire (en particulier la taille des +tableaux utilisés) à partir du fichier +\file{texmf.cnf} qui est lu par \KPS. +Les paramètres en question se trouvent +dans la troisième partie du fichier inclus dans la distribution \TL{}. + Les variables les plus importantes sont : +\begin{ttdescription} +\item[\texttt{main\_memory}] + Nombre total de mots mémoire disponibles pour + \TeX{}, \MF{} et \MP. Vous devez générer un nouveau fichier de + format pour chaque nouveau paramétrage. Par exemple, vous pouvez + générer une version large de \TeX{} et appeler le fichier de format + \texttt{hugetex.fmt}. En utilisant la méthode supportée par \KPS{} + qui consiste à suffixer la variable par le nom du programme, la valeur + particulière de la variable \texttt{main\_memory} destinée à ce + fichier de format sera lue dans le fichier \file{texmf.cnf}. +\item[\texttt{extra\_mem\_bot}] + Espace supplémentaire pour certaines structures de données de \TeX{} : + boîtes, \textit{glue}, points d'arrêt\dots{} Surtout utile si vous utilisez + \PiCTeX{} par exemple. +\item[\texttt{font\_mem\_size}] + Nombre de mots mémoire disponibles pour décrire les polices. C'est + plus ou moins l'espace occupé par les fichiers TFM lus. +\item[\texttt{hash\_extra}] + Espace supplémentaire pour la table de hachage des noms de séquences + de contrôle. Environ 10~000 de ces noms peuvent être stockés dans la + table principale ; si vous avez un document très volumineux avec + beaucoup de références croisées, il se peut que ce ne soit pas + suffisant. La valeur par défaut \texttt{hash\_extra} est \texttt{50000}. +\end{ttdescription} + +\noindent Évidemment, cette possibilité ne remplace pas une véritable +allocation dynamique des tableaux et de la mémoire, mais puisque c'est +complexe à implémenter dans le présent source \TeX{}, ces paramètres lus +à l'exécution fournissent un compromis pratique qui procure une certaine +souplesse. + +%\begin{comment} (supprimé (df) 5/5/2006, mail à K.B. + +\section{Installation sur un nouveau système Unix} + +Si vous avez un système Unix ne correspondant à aucun des exécutables +fournis, il faut compiler vous-même \TeX{} et tous ses programmes +satellites à partir des sources. Cela n'est pas aussi difficile qu'il +y paraît. Tout ce dont vous aurez besoin est contenu dans le +répertoire \texttt{source} qui se trouve sur le \DVDlive. + +\subsection{Prérequis} + +Il faut au moins 400\,Mo d'espace sur disque pour compiler la +totalité de \TeX{} et des programmes associés. +Vous aurez aussi besoin d'un +compilateur C \acro{ANSI}, de l'utilitaire \cmdname{make}, +d'un générateur d'analyseur lexical et d'un générateur d'analyseur +syntaxique. Nous recommandons les versions \acro{GNU} des programmes suivants +(\cmdname{gcc}, \acro{GNU}\cmdname{make}, \cmdname{m4}, +\cmdname{flex}, \cmdname{bison}). Vous pouvez utiliser d'autres compilateurs C +et d'autres programmes \cmdname{make} si vous maîtrisez +correctement la programmation sous Unix pour résoudre les +problèmes éventuels. La commande \texttt{uname} doit renvoyer une valeur +raisonnable. + +\subsection{Configuration} + +Tout d'abord, effectuez l'installation normale de \TL{} sur le disque +dur (voir section~\ref{sec:unix-install-disk}, +\p.\pageref{sec:unix-install-disk}). Vous pouvez sauter l'installation de +tous les binaires précompilés. +Décompactez ensuite sur le disque le fichier +\file{source.tar.bz2} (archive compressée) trouvé dans +le répertoire \dirname{source} et placez-vous dans +le répertoire où vous avez transféré l'ensemble. +\begin{alltt} +> \Ucom{cd /tmp/tl-source} +> \Ucom{bunzip2 source.tar.bz2} +> \Ucom{tar xf source.tar} +\end{alltt} + +Lancez maintenant \textsf{configure} de la façon suivante : +\begin{alltt} +> \Ucom{sh configure -prefix=/usr/local/texlive/2007} +\end{alltt} + +Le répertoire \optname{-prefix} est le répertoire de base de +l'arborescence \TL{}, il est désigné par \var{TEXDIR} dans la suite. +\begin{comment} +Les répertoires utilisés sont les suivants : + +\noindent +\begin{tabular}{>{\ttfamily}ll@{}} + \dirname{$TEXDIR/texmf-dist} & répertoire de base pour les fontes, + macros, etc\\ + \dirname{$TEXDIR/man} & pages du manuel Unix\\ + \dirname{$TEXDIR/info} & manuels \acro{GNU} en format Info\\ + \dirname{$TEXDIR/bin/$archname} & exécutables.\\ +\end{tabular}\\ +\end{comment} +%$ + +Si vous ne voulez pas créer de répertoire \dirname{$archname} spécifique %$ +au système choisi pour stocker les exécutables (c.-à-d. les +copier directement dans \dirname{$TEXDIR/bin}), %$ +il faut exécuter \textsf{configure} avec l'option \\ +\verb|--disable-multiplatform|. + +Tapez \verb|./configure --help|, le programme affichera +les options supplémentaires disponibles (telles que supprimer l'installation +des extensions optionnelles comme \OMEGA\ ou \eTeX). + +\subsection{Exécuter \textsf{make}} +S'assurer que la variable ou l'option \texttt{noclobber} n'est pas définie. + et lancer le \cmdname{make} à la racine de l'arborescence de la façon +suivante : +\begin{alltt} +>> \Ucom{make world} +\end{alltt} +et aller prendre un café\dots + +Il peut être utile de garder une trace complète dans un fichier log en tapant : +\begin{alltt} +>> \Ucom{sh -c "make world >world.log 2>\&1" \&} +\end{alltt} +Avant de conclure que tout va bien, vérifier que le fichier log ne contient +pas de message d'erreur : le \cmdname{make} de \acro{GNU} renvoie toujours +le message \samp{***} à chaque erreur d'exécution. Vérifier aussi que +tous les exécutables ont été créés. +\begin{alltt} +>> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} +>> \Ucom{ls | wc} +\end{alltt} +Le résultat doit être supérieur à 200 (on peut tester le nombre exact +dans le répertoire \dirname{bin} de la distribution). + +Si vous avez besoin de droits spéciaux pour exécuter \texttt{make install}, +vous pouvez séparer \samp{make world} en deux processus différents : +\begin{alltt} +>> \Ucom{make all} +>> \Ucom{su} +>> \Ucom{make install strip} +\end{alltt} + +Après avoir installé vos nouveaux binaires, il faut suivre les procédures +normales de la post-installation, indiquées dans la +section~\ref{sec:postinstall}, \p.\pageref{sec:postinstall}. + +%\end{comment} supprimé (df) 5/5/2006 + +\section{Remerciements} + +\TL{} est le résultat des efforts +collectifs de pratiquement tous les groupes d'utilisateurs de \TeX. +La présente édition de \TL{} a été coordonnée par +Sebastian Rahtz et Karl Berry. +Voici la liste des principaux contributeurs : + +\begin{itemize} + +\item Les associations d'utilisateurs anglais, allemands, néerlandais et + polonais (\acro{TUG}, \acro{DANTE} e.V., \acro{NTG}, and \acro{GUST}, + respectivement) qui contribuent ensemble à l'infrastructure technique et + administrative. Soutenez votre association locale (\acro{GUTenberg} pour + les francophones) ! + +\item L'équipe du \acro{CTAN} qui distribue les images des distributions \TL{} + et fournit les sites d'hébergement pour le stockage et la mise à jour des + extensions qui sont la base de \TL. + +\item Peter Breitenlohner et toute l'équipe \eTeX{} qui construisent + les bases des successeurs de \TeX. + +\item Thomas Esser, car, sans lui, sa merveilleuse distribution \teTeX{} et + son aide continuelle, \TL{} n'existerait probablement pas. + +\item Michel Goossens, en tant que co-auteur de la documentation initiale. + +\item Eitan Gurari, dont le programme \TeX4ht a été utilisé pour créer la + version \HTML{} de cette documentation et qui travailla inlassablement à + l'améliorer, avec des délais très brefs. + +\item Hans Hagen qui, outre sa participation active aux tests, + a adapté le format \ConTeXt\ aux besoins de \TL{}. + +\item \Thanh, Martin Schr\"oder et toute l'équipe pdf\TeX\ qui continuent + inlassablement à étendre les performances de \TeX. + +\item Taco Hoekwater, pour ses efforts sans cesse renouvelés à l'amélioration + de MetaPost et de \TeX\ lui-même. + +\item Pawe{\l} Jackowski, pour l'installeur Windows \cmdname{tlpm}, +et Tomasz {\L}uczak, pour la version graphique \cmdname{tlpmgui}. + +\item Akira Kakuto, pour son aide précieuse qui nous a permis + d'intégrer dans \TL{} les binaires Windows de sa distribution \acro{W32TEX} + (\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}). + +\item Jonathan Kew et son employeur \acro{SIL}, pour avoir produit + Xe\TeX{} et pour avoir pris la peine de l'intégrer dans \TL{}. + +\item Reinhard Kotucha, pour son aide dans la lourde tâche consistant à +mettre à jour les innombrables extensions incluses dans \TL{} et pour ses +contributions sous Windows en particulier le script \texttt{getnonfreefonts}. + +\item Petr Ol\v{s}ak, qui coordonna et vérifia minutieusement toute la + partie tchèque et slovaque. + +\item Toshio Oshima, pour le visualisateur \cmdname{dviout} pour Windows. + +\item Fabrice Popineau, pionnier du développement de \TL{} sous Windows. + +\item Norbert Preining, pour son aide à la mise à jour de \TL, ses nombreuses + suggestions d'amélioration et pour avoir coordonné (avec Frank K\"uster) la + version Debian de \TL. + +\item Staszek Wawrykiewicz, principal testeur de \TL{} et + coordinateur des contributions polonaises + (fontes, installation Windows, etc.). + +\item Olaf Weber, pour son patient assemblage et la maintenance de \Webc{} + sur laquelle tout repose. + +\item Gerben Wierda, qui a créé et maintient la partie \MacOSX{} + et qui participe activement aux tests. + +\item Graham Williams, du travail duquel dépend le catalogue des +composants. +\end{itemize} + +Les binaires ont été compilés par : +Hartmut Henkel (\pkgname{x86\_64-linux}), +Akira Kakuto et Fabrice Popineau (\pkgname{win32}), +Manfred Lotz (\pkgname{i386-freebsd}), +Norbert Preining (\pkgname{alpha-linux}), +Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-linux} + et \pkgname{sparc-solaris}), +Karl Berry (\pkgname{i386-linux}), +Olaf Weber (\pkgname{mips-irix}), +Gerben Wierda (\pkgname{i386-darwin}, \pkgname{powerpc-darwin}). + +Documentation et mises à jour des traductions : +Karl Berry (anglais), +G\"unter Partosch, Hartmut Henkel \& Klaus H\"oppner (allemand), +Daniel Flipo (français), +Petr Sojka \& Janka Chleb\'\i kov\'a (tchèque et slovaque), +Boris Veytsman (russe), +Staszek Wawrykiewicz (polonais). + +Bien sûr, notre gratitude va en premier lieu à Donald Knuth pour avoir +inventé \TeX{} et l'avoir offert au monde entier. + +\section{Historique des versions successives} +\label{sec:history} + +\subsection{Les éditions précédentes} + +La discussion commença à la fin de 1993 quand le Groupe des Utilisateurs +Néerlandais de \TeX{} commençait à travailler à son \CD{} 4All\TeX{} pour les +utilisateurs de \acro{MS-DOS}, et on espérait à ce moment sortir un \CD{} +unique pour tous les systèmes. C'était un objectif beaucoup trop ambitieux, +mais il permit la naissance du \CD{} 4All\TeX{}, projet couronné de succès, +mais aussi d'un groupe de travail \og \acro{TUG} Technical Council\fg{} pour +mettre en place TDS (\emph{\TeX{} Directory Structure} : +\url{http://tug.org/tds}), qui spécifiait la gestion des fichiers \TeX{} sous +une forme logique. La mouture finale de \TDS{} fut publiée dans le numéro de +décembre 1995 de \textsl{TUGboat}, et il était clair depuis un certain temps +qu'il fallait proposer un produit contenant une structure modèle sur \CD{}. +La distribution que vous possédez est le résultat direct des délibérations de +ce groupe de travail. Il était également clair que le succès des \CD{} +4All\TeX{} démontrait que les utilisateurs d'Unix trouveraient leur bonheur +avec une distribution aussi simple, et ceci a été l'autre objectif de +\TL. + +Nous avons d'abord entrepris de créer un nouveau \CD{} \TDS{} Unix à l'automne +1995, et nous avons rapidement choisi \teTeX{} de Thomas Esser comme étant la +configuration idéale, car il supportait déjà plusieurs plates-formes et avait +été construit en gardant à l'esprit la portabilité entre systèmes. Thomas +accepta de nous aider et commença à travailler sérieusement au début de 1996. +La première édition sortit en mai 1996. Au début de 1997, Karl Berry acheva +une nouvelle distribution de \Webc{}, qui incluait presque toutes les +caractéristiques que Thomas Esser avait ajoutées dans \teTeX, et il fut décidé +de baser la deuxième édition du \CD{} sur le standard \Webc, en y ajoutant le +script \texttt{texconfig} de \teTeX. La troisième édition du \CD{} était +basée sur une version majeure de \Webc, 7.2, par Olaf Weber ; en même temps, +une nouvelle version révisée de \teTeX{} était achevée dont \TL{} partageait +presque toutes les caractéristiques. La quatrième édition a suivi le même +schéma, en utilisant une nouvelle version de \teTeX{} et une nouvelle version +de \Webc{} (7.3). Le système incluait dorénavant un programme complet +d'installation pour Windows. + +Pour la cinquième édition (mars 2000), de nombreuses parties du \CD{} +ont été vérifiées et révisées, des centaines de composants +mis à jour. +Le contenu détaillé des composants était décrit par des +fichiers XML. Mais le changement majeur de cette cinquième édition a +été la suppression de tout logiciel non libre de droits. +Tout ce qui se trouve dans \TL{} devait être compatible avec la licence +Debian (\emph{Debian Free Software Guidelines} : +\url{http://www.debian.org/intro/free}) ; nous avons +fait de notre mieux pour vérifier les termes des licences de chaque +composant, et nous souhaiterions que toute erreur nous soit signalée. + +La sixième édition (juillet 2001) contient un grand nombre de mises à jour. +Le changement majeur de cette version réside dans la refonte du +processus d'installation : l'utilisateur peut désormais choisir +les collections de manière plus précise. Les collections concernant +les langues ont été entièrement réorganisées, aussi le choix d'une +langue installe non seulement les macros, les fontes, etc. mais +prépare également un fichier \file{language.dat} adéquat. + +La septième édition (mai 2002) a comme ajout majeur une installation +pour \MacOSX{} et l'habituelle myriade de mises à jour de composants et +de programmes. Un objectif important a été de fusionner à +nouveau les sources avec ceux de \teTeX{}, alors que les versions +5 et 6 s'en étaient éloignées. + +\subsubsection{2003} + +En 2003, le flot de mises à jour et d'additions a continué, mais nous +avons constaté que \TL{} était devenu si volumineux qu'il ne +pouvait plus tenir sur un seul \CD, aussi l'avons-nous divisé en trois +distributions distinctes (voir section~\ref{sec:multiple-dist}, +\p.\pageref{sec:multiple-dist}). Par ailleurs : +\begin{itemize} +\item À la demande de l'équipe \LaTeX{}, nous avons modifié les + commandes standard \cmdname{latex} et \cmdname{pdflatex} pour + qu'elles utilisent \eTeX{} (voir \p.\pageref{text:etex}). +\item Les nouvelles fontes Latin Modern sont disponibles (et + recommandées). +\item Le support pour Alpha \acro{OSF} a été supprimé + (celui pour \acro{HPUX} l'avait été auparavant), car personne + disposant des machines nécessaires ne s'est + proposé pour compiler les nouveaux binaires. +\item L'installation pour Windows a été largement modifiée ; un environnement + de travail intégré basé sur \cmdname{XEmacs} a été introduit. +\item Des programmes supplémentaires importants pour Windows (Perl, + Ghost\-script, Image\-Magick, Ispell) sont maintenant installés dans le + répertoire d'installation de \TL{}. +\item Les fichiers \emph{font map} utilisés par \cmdname{dvips}, + \cmdname{dvipdfm} et \cmdname{pdftex} sont maintenant générés par le + nouveau programme \cmdname{updmap} et installés dans + \dirname{texmf/fonts/map}. +\item Dorénavant, \TeX{}, \MF{} et \MP{} écrivent les caractères 8-bit + présentés en entrée sans modification, et non pas avec la notation + \verb|^^|, que ce soit dans des fichiers (par la commande + \verb|write|), dans les fichiers de trace (\verb|.log|) ou sur le + terminal. Dans le \TL{}~7, l'écriture de ces caractères + 8-bit était influencée par les paramètres de localisation du + système; maintenant ces paramètres n'influent plus du tout sur le + comportement des programmes \TeX{}. Si pour quelque raison que ce + soit, vous avez besoin de la notation \verb|^^| en sortie, + renommez le fichier \verb|texmf/web2c/cp8bit.tcx|. Les prochaines + versions disposeront d'un moyen plus propre pour contrôler cette + sortie. +\item La documentation de \TL{} a été largement révisée. +\item Enfin, comme la numérotation séquentielle des versions + devenait peu maniable, il a été décidé d'identifier désormais la version + de \TL{} par l'année : \TL{}~2003 au lieu de \TL{}~8. +\end{itemize} + + +\subsubsection{2004} + +2004 a apporté beaucoup de changements (et quelques incompatibilités avec les +versions précédentes) : + +\begin{itemize} + +\item Si vous avez installé des fontes supplémentaires qui ont leur propre +fichier \file{.map} ou des fichiers \file{.enc} spécifiques, vous +devrez vraisemblablement déplacer ces fichiers. + +Les fichiers \file{.map} sont désormais recherchés uniquement dans les +sous-répertoires \dirname{fonts/map} (dans chaque arborescence +\filename{texmf}), leur chemin de recherche est donné par la variable +\envname{TEXFONTMAPS} de \filename{texmf.cnf}. +De même, les fichiers \file{.enc} sont désormais recherchés uniquement +dans les sous-répertoires \dirname{fonts/enc}, leur chemin de recherche est +donné par la variable \envname{ENCFONTS} de \filename{texmf.cnf}. +Le script \cmdname{updmap} devrait émettre des messages d'avertissement +pour les fichiers \file{.map} et \file{.enc} mal placés. + +Sur les différentes façons de traiter le problème, consulter +\url{http://tug.org/texlive/mapenc.html}. + +\item La distribution pour Windows a changé cette année : +l'installation de la distribution \fpTeX{} (basée sur \Webc{}) de Fabrice +Popineau n'est provisoirement plus proposée dans l'attente +d'un nouvel installeur. À la place, vous pouvez tester et installer +la distribution \MIKTEX{} (indépendante de \Webc{}), +voir section~\ref{sec:struct-tl}, \p.\pageref{sec:struct-tl}. +Le \CDdemo{} diffusé en 2003 a été supprimé. + +\item L'ancien répertoire \dirname{texmf} a été éclaté en trois parties : +\dirname{texmf}, \dirname{texmf-dist} et \dirname{texmf-doc}. Voir +section~\ref{sec:tld}, \p.\pageref{sec:tld}. +% et les fichiers \filename{README} à la racine de ces répertoires. +% (df) Y'en a pas !!! + +\item Tous les fichiers relatifs aux différents avatars de \TeX{} sont +désormais regroupés dans le même sous-répertoire \dirname{tex} des +arborescences \dirname{texmf*} (ils étaient jusqu'ici placés dans des +sous-répertoires spécifiques \dirname{tex}, \dirname{etex}, +\dirname{pdftex}, \dirname{pdfetex}, etc.). Voir +\CDref{texmf-doc/doc/english/tds/tds.html\#Extensions} +{\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}. + +\item Les scripts auxiliaires, normalement pas exécutés directement +par les utilisateurs, sont regroupés dans un répertoire \dirname{scripts} +des arborescences \dirname{texmf*}. On les localise grâce à la +commande \verb|kpsewhich -format=texmfscripts|. Au cas où vous en auriez, +les programmes utilisant ces scripts nécessiteront une adaptation. Voir +\OnCD{texmf-doc/doc/english/tds/tds.html\#Scripts}. + +\item La plupart des formats affichent en clair (dans les fichiers +\file{.log} en particulier) les caractères imprimables au lieu +de les transcrire en notation hexadécimale \verb|^^|. Ceci se fait +grâce au fichier \filename{cp227.tcx}, qui considère comme imprimables +les caractères 32 à 256, ainsi que les tabulations et les changements +de page (caractères 9 à 11). Les formats faisant exception sont +plain \TeX\ (seuls les caractères 32 à 127 sont déclarés imprimables), +\ConTeXt{} (0 à 255 imprimables) et les formats basés sur \OMEGA. +Il y a peu de différence avec le comportement de \TL\,2003 +mais la mise en {\oe}uvre est plus propre et plus facilement configurable. +Voir \OnCD{texmf/doc/web2c/web2c.html\#TCX-files}. +Noter que l'utilisation du codage Unicode en entrée peut provoquer +des affichages défectueux en sortie (TeX code sur un seul octet). + +\item Tous les formats, sauf plain \TeX, font appel au moteur +\textsf{pdfetex} (qui produit bien sûr par défaut des fichiers \acro{DVI} +lorsque le format choisi est \LaTeX). Ceci permet aux formats +\LaTeX, \ConTeXt, etc., d'avoir accès aux fonctionnalités +micro-typographiques de pdf\TeX{} (alignement optique des marges par exemple) +et aux fonctionnalités de \eTeX{} (\OnCD{texmf-dist/doc/etex/base/}). + +Ceci rend \emph{indispensable} le recours à l'extension \pkgname{ifpdf} +(qui fonctionne aussi bien avec plain que \LaTeX) pour déterminer si +le format de sortie est \acro{DVI} ou \acro{PDF}. Tester si la commande +\cs{pdfoutput} est définie ou non \emph{n'est pas} un moyen fiable +de le faire. + +\item pdf\TeX\ (\url{http://pdftex.org}) offre de nouvelles fonctionnalités : + + \begin{itemize} + + \item Les commandes \cs{pdfmapfile} et \cs{pdfmapline} permettent + de spécifier le choix des fichiers \file{.map} à utiliser + pour le document en cours. + + \item L'amélioration du gris typographique par variation (infime) de la + largeur des caractères (\textit{font expansion}) est plus facile à + mettre en {\oe}uvre, voir + \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} + + \item Le fichier \filename{pdftex.cfg} n'est plus utilisé. + Toutes les affectations de paramètres doivent désormais être + faites dans le préambule en utilisant les primitives ad~hoc. + + \item Pour plus d'informations, consulter le manuel de pdf\TeX\ : + \OnCD{texmf/doc/pdftex/manual}. + + \end{itemize} + +\item La primitive \cs{input} de \cmdname{tex}, \cmdname{mf} et +\cmdname{mpost}, accepte désormais les espaces et autres caractères +spéciaux dans les noms de fichiers à condition d'utiliser des +\textit{double quotes}, en voici deux exemples typiques : +\begin{verbatim} +\input "filename with spaces" % plain +\input{"filename with spaces"} % latex +\end{verbatim} +Consulter le manuel \Webc{} pour plus d'informations : \OnCD{texmf/doc/web2c}. + +\item Les fonctionnalités de enc\TeX\ sont désormais incluses dans \Webc{}. +Ainsi, tous les formats \emph{construits avec l'option \optname{-enc}} y ont +accès. enc\TeX\ permet le transcodage en entrée et en sortie et +l'utilisation transparente du codage Unicode \acro{UTF}-8. Voir +\OnCD{texmf-dist/doc/generic/enctex/} et +\url{http://www.olsak.net/enctex.html}. + +\item Un nouveau moteur combinant les fonctionnalités de \eTeX\ +et d'\OMEGA, appelé Aleph, est disponible. \OnCD{texmf-dist/doc/aleph/base} +et \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph} +fournissent une information succincte. Le format \LaTeX{} utilisant +Aleph s'appelle \textsf{lamed}. + +\item La licence \acro{LPPL} de \LaTeX\ (version décembre 2003) a changé, +elle est désormais compatible avec les prescriptions Debian. +Les autres changements sont décrits dans le fichier \filename{ltnews}, voir +\OnCD{texmf-dist/doc/latex/base}. + +\item Un nouveau programme, \cmdname{dvipng}, qui convertit les fichiers +\acro{DVI} en images \acro{PNG} a été ajouté. Voir +\OnCD{texmf/doc/man/man1/dvipng.1}. + +\item Nous avons dû réduire le nombre de fontes incluses dans l'extension +\pkgname{cbgreek}, ceci a été fait avec l'accord et l'aide de l'auteur +(Claudio Beccari). Les fontes exclues (invisibles, transparentes, contours) +sont rarement utilisées et la place nous manquait. La collection complète +des fontes \pkgname{cbgreek} est disponible sur \acro{CTAN} +(\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). + +\item La commande \cmdname{oxdvi} a été supprimée, il suffit utiliser +\cmdname{xdvi} à la place. + +\item Les commandes \cmdname{initex}, \cmdname{virtex} et leurs +homologues pour \cmdname{mf} et \cmdname{mpost} ont disparu. +Vous pouvez les recréer si nécessaire mais elles sont avantageusement +remplacées, depuis des années maintenant, par l'option \optname{-ini} +(\cmdname{tex} \optname{-ini} pour \cmdname{initex} et \cmdname{virtex}). + +\item Les binaires pour l'architecture \textsf{i386-openbsd} ont été + supprimés par manque de volontaires pour les compiler. + +Sur \textsf{sparc-solaris} (au moins) il sera probablement +nécessaire de positionner la variable d'environnement +\envname{LD\_LIBRARY\_PATH} pour utiliser les programmes de la famille +\pkgname{t1utils}. Ceci vient du fait qu'ils sont compilés en C++, +et que l'emplacement des bibliothèques dynamiques est variable. +Ce n'est pas une nouveauté 2004 mais ce point n'était pas documenté +précédemment. De même, sur \textsf{mips-irix}, les bibliothèques dynamiques +\acro{MIPS}pro 7.4 sont nécessaires. + +\end{itemize} + +\subsubsection{2005} + +2005 a apporté son lot habituel d'innombrables mises à jour d'extensions +et de programmes. L'infrastructure est restée relativement stable par rapport +à 2004, à quelques changements inévitables près : + +\begin{itemize} + +\item Trois nouveaux scripts \cmdname{texconfig-sys}, \cmdname{updmap-sys} et + \cmdname{fmtutil-sys} ont été introduits ; ils agissent sur la + configuration générale de la machine, comme le faisaient les + scripts \cmdname{texconfig}, \cmdname{updmap} et \cmdname{fmtutil} + jusqu'à l'an dernier. Les nouveaux scripts \cmdname{texconfig}, + \cmdname{updmap} et \cmdname{fmtutil} modifient maintenant + la configuration \emph{personnelle} de l'utilisateur qui les lance ; + le résultat est placé dans le répertoire personnel de l'utilisateur + (sous \dirname{$HOME/.texlive2005}), voir %$ + section~\ref{sec:texconfig}, \p.\pageref{sec:texconfig}. + +\item De nouvelles variables, \envname{TEXMFCONFIG} (resp. + \envname{TEXMFSYSCONFIG}) ont été introduites ; elles définissent + les répertoires où doivent se trouver les fichiers de configuration de + l'utilisateur (resp. de la machine), comme \filename{fmtutil.cnf} et + \filename{updmap.cfg}. Les utilisateurs de fichiers de configuration + locaux \filename{fmtutil.cnf} ou \filename{updmap.cfg} devront + probablement les déplacer ; une autre possibilité est de modifier la + définition des variables \envname{TEXMFCONFIG} ou + \envname{TEXMFSYSCONFIG} dans \filename{texmf.cnf}. L'important est + de s'assurer de la cohérence entre les définitions de ces variables + dans \filename{texmf.cnf} et l'emplacement réel de ces fichiers. + Voir section~\ref{sec:texmftrees}, \p.\pageref{sec:texmftrees} pour + la description des différentes arborescences texmf utilisées. + +\item L'an dernier nous avions rendu \og \texttt{undefined} \fg certaines + primitives propres à \cmdname{pdftex} (comme \verb|\pdfoutput|) + dans les formats créés à partir de \cmdname{pdfetex} (\cmdname{latex} + \cmdname{amstex}, \cmdname{context} par exemple)). + C'était à titre transitoire, aussi cette année, ces primitives sont de + nouveau définies dans tous les formats à base \cmdname{pdf(e)tex}, + \emph{même lorsqu'ils sont utilisés pour produire des fichiers + \file{.dvi}}. Ceci implique qu'il vous faudra modifier vos + documents qui utilisent le test \verb|\ifx\pdfoutput\undefined| + pour déterminer si la sortie est en DVI ou en PDF. Le mieux est + d'utiliser l'extension \pkgname{ifpdf.sty} et son test + \verb|\ifpdf| qui fonctionne même en plain \TeX. + +\item L'an dernier nous avions fait en sorte que la plupart des formats + impriment dans les sorties \file{.log} des caractères 8-bit + lisibles à la place des notations hexadécimales \verb|^^| + (voir section précédente). + Le nouveau fichier TCX \filename{empty.tcx} permet + de revenir facilement à la notation traditionnelle \verb|^^|, il suffit + de coder : +\begin{verbatim} +latex --translate-file=empty.tcx fichier.tex +\end{verbatim} + +\item Le nouveau programme \cmdname{dvipdfmx} est disponible pour convertir + des fichier DVI en PDF ; ce programme remplace \cmdname{dvipdfm}, + toujours disponible mais dont l'usage est maintenant déconseillé. + +\item Les variables \envname{HOMETEXMF} et \envname{VARTEXMF} ont été renommées + en \envname{TEXMFHOME} et \envname{TEXMFSYSVAR} respectivement pour + raisons de cohérence avec les autres noms de variables. Il y a aussi + \envname{TEXMFVAR} qui désigne maintenant un répertoire personnel + de l'utilisateur (cf. le premier point de la présente liste). + +\end{itemize} + +\subsection{L'édition 2006--2007} +\label{tlcurrent} + +En 2006--2007, la nouveauté majeure a été l'arrivée dans \TL{} de Xe\TeX{} +disponible sous forme de deux programmes \texttt{xetex} et \texttt{xelatex}, +voir \url{http://scripts.sil.org/xetex}. + +MetaPost a subi une mise à jour importante et d'autres améliorations +sont prévues, voir \url{http://tug.org/metapost/articles}. Il en va de même +pour pdf\TeX{}, voir \url{http://tug.org/applications/pdftex}. + +Le format \filename{tex.fmt} et les formats pour MetaPost and \MF\ ne +se trouvent plus dans \dirname{texmf/web2c} mais dans des +sous-répertoires de \dirname{texmf/web2c} (la recherche de fichiers +\filename{.fmt} est néanmoins faite aussi dans \dirname{texmf/web2c}). +Ces sous-répertoires portent le nom du moteur utilisé pour construire +le format, par exemple \filename{tex}, \filename{pdftex} ou +\filename{xetex}. Ce changement ne devrait pas avoir d'effet visible +pour les utilisateurs. + +Le programme (plain) \texttt{tex} ignore désormais les lignes commençant +par \texttt{\%\&} qui permettent de déterminer le format à utiliser ; +c'est un vrai \TeX{} \og à la Knuth \fg ! +\LaTeX\ et tous les autres prennent toujours en compte les lignes commençant +par \texttt{\%\&}. + +Les scripts d'installation peuvent maintenant être utilisés de manière +non interactive (voir section~\ref{sec:noninteractive-install}) en +positionnant des variables d'environnement. + +Comme chaque année des centaines d'extensions et de programmes ont été mis à +jour, voir les sites \acro{CTAN} (\url{http://www.ctan.org}). + +L'arborescence utilisée en interne a été réorganisée avec de nouveaux outils +qui devraient fournir une meilleure base de travail pour les développements +futurs. + +Enfin, en mai 2006 Thomas Esser a annoncé qu'il renonçait à poursuivre +le développement de te\TeX{} (\url{http://tug.org/tetex}). Sa décision a +relancé l'intérêt pour \TL, en particulier chez les distributeurs de solutions + \acro{GNU}/Linux (un nouveau schéma d'installation \texttt{tetex} a été + ajouté dans le script d'installation de \TL{} pour produire une + distribution proche de l'ancienne te\TeX). La distribution \TL{} existe +déjà sous forme de paquets Debian, espérons que les autres acteurs du monde +Linux (RedHat, SuSe, etc.) suivront et que les utilisateurs +se verront proposer à l'avenir des distributions \TeX{} riches et plus +faciles à installer. + + + +\subsection{Versions futures} + +\emph{\TL{} n'est pas un produit parfait !} +(et ne le sera jamais). Nous prévoyons de continuer à produire de +nouvelles versions, et aimerions fournir plus d'aide, de +fonctionnalités, de programmes d'installation, et (bien sûr) une +arborescence améliorée et vérifiée de macros et de fontes. Ce travail +est effectué par des volontaires débordés, dans la limite de leur temps +libre, et beaucoup reste à faire. Si vous pouvez nous aider, n'hésitez pas +à vous proposer ! + +Corrections, suggestions et propositions d'aide doivent +être envoyées à :\hfill\null +\begin{quote} +\email{tex-live@tug.org} \\ +\url{http://tug.org/texlive} +\end{quote} + +\medskip +\noindent \textsl{Bon travail avec \TeX{} !} + +\end{document} + +%%% Local Variables: +%%% mode: latex +%%% mode: flyspell +%%% ispell-local-dictionary: "francais" +%%% TeX-master: t +%%% coding: latin-1 +%%% End: diff --git a/Master/texmf/doc/texlive/source/texlive-fr/live4ht.cfg b/Master/texmf/doc/texlive/source/texlive-fr/live4ht.cfg new file mode 100644 index 00000000000..4da18b3c746 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-fr/live4ht.cfg @@ -0,0 +1,47 @@ +% tex4ht configuration file for the TeX Live documentation. +% Accumulated over many years. Public domain. +% +% html specifies the main output format. +% info for extra debugging info in the log files. + +% better approach is to have html in one piece (including footnotes). +% charset=utf-8 fails for French, all accented letters get lost. +\Preamble{html,info,fn-in} + +% add extra stylesheet +\Configure{@HEAD}{\HCode{% +\Hnewline +\Hnewline +}} + +% or LaTeX complains it is missing. +\begin{document} + +\EndPreamble + +% simplify output for HTML. We leave TeX and LaTeX alone, since tex4ht +% actually does the lowered E (and raised A) in CSS. +\def\OMEGA{Omega} +\def\LaTeXe{LaTeX2e} +\def\eTeX{e-\TeX} +\def\acro#1{#1} +\def\MF{Metafont} +\def\BibTeX{BibTeX} +\def\warningbox{} +\def\endwarningbox{} + +\newif\ifhackliterals +\ifx\tldocenglish\undefined \else \hackliteralstrue \fi +\ifx\tldocrussian\undefined \else \hackliteralstrue \fi +\ifx\tldocgerman\undefined \else \hackliteralstrue \fi +% +\ifhackliterals + % these definitions cause "missing } inserted" at \end{tabularx} in + % French and Czech. don't know why. + % + % don't make these into links, as happens with \path. We only have a couple + % special characters that actually occur. + \def\dirname{\texttt\bgroup\catcode`\$=12 \catcode`\_=12 \finishliteral} + \def\finishliteral#1{#1\egroup} + \let\filename=\dirname +\fi diff --git a/Master/texmf/doc/texlive/source/texlive-fr/tex-live.css b/Master/texmf/doc/texlive/source/texlive-fr/tex-live.css new file mode 100644 index 00000000000..5062bc0d229 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-fr/tex-live.css @@ -0,0 +1,44 @@ +/* $Id$ + Simple CSS for TeX Live that adds margins and a little color. + original by Bzyl Wlodzimierz, edited by Karl Berry, 2005. + Public domain. */ + +html { + // top left bottom right + margin: 15pt 15pt 15pt 15pt; + background: rgb(255,255,224); +} + +body { + margin: 0 5pt 0 5pt; + padding: 0; + //matw: background: rgb(224,255,224); + // (It looks better to me to have a consistent background --karl) +// fonts in browser are low resolution; +// therefore generated serif are poor quality, +// so they disturb reading (that is my opinion) + font-family: sans-serif; + font-style: normal; +} + +/* (It looks better to me to not vary colors at every level --karl) */ + +h3.sectionHead { + padding: 12pt 10pt 12pt 20pt; + //matw: background: rgb(192,224,255); + background: rgb(224,224,255); + color: rgb(0,0,32); +} + +h4.subsectionHead { + padding: 7pt 10pt 7pt 40pt; + background: rgb(224,224,255); + color: rgb(0,0,32); +} + +h5.subsubsectionHead { + padding: 3pt 10pt 3pt 40pt; + //matw: background: rgb(224,255,255); + background: rgb(224,224,255); + color: rgb(0,0,32); +} diff --git a/Master/texmf/doc/texlive/source/texlive-fr/texlive-fr.tex b/Master/texmf/doc/texlive/source/texlive-fr/texlive-fr.tex new file mode 100644 index 00000000000..6b74bc3bd13 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-fr/texlive-fr.tex @@ -0,0 +1,3148 @@ +%Format: pdf +% +% Change history (started May 18th 2002) +% 2008/07/26: synced with 2008 English version, by Daniel Flipo +% 2007/01/18: synced with 2007 English version, by Daniel Flipo +% 2005/11/01: synced with 2005 English version, by Daniel Flipo +% 2005/05/05: re-added section on building binaries (Daniel Flipo) +% 2004/10/28: synced with 2004 English version, by Daniel Flipo +% 2003/08/28: synced with 2003 English version, by Éric Picheral & Jacques André +% 2002/05/25: proof-reading and corrections, by Daniel Flipo +% 2002/05/18: synced with English version, by Fabrice +% +\documentclass{article} +\let\tldocfrench=1 % NOT used... + +\usepackage[utf8]{inputenc} +\usepackage[T1]{fontenc} + +\usepackage[frenchb]{babel} +\usepackage{xspace} +\frenchbsetup{AutoSpacePunctuation=false, og=», fg=»} + +\usepackage{ifpdf} +% tex-live.sty suppose \hyper@linkurl défini... +\ifpdf + \def\Status{1} % (df) Pour faire charger hyperref dans tex-live.sty +\else + \makeatletter + \def\hyper@linkurl#1#2{#2} % undefined if hyperref.sty not loaded + \makeatother +\fi + +\usepackage{tex-live} +% Correctifs à tex-live.sty (df) +\renewcommand{\samp}[1]{\og \texttt{#1}\fg{}} +% (df) La commande \TeXLive n'est pas utilisée en v.f. +\renewcommand{\TL}{\TeX{} Live\xspace}% Robuste (pas besoin de \protect)... +\renewcommand{\TK}{\TeX{} Collection\xspace}% idem. +% tex-live.sty fait précéder les no de page d'une fine... si on veut +% une insécable normale, décommenter la ligne suivante : +\def\p.{page~} +% Chez Karl, la commande \url{} ne protège pas les caractères actifs (:?), +% d'où ceci (essai provisoire... erreurs avec le car. #) : +%\let\urlORI\url +%\renewcommand*{\url}[1]{\foreignlanguage{english}{\urlORI{#1}}} +%\renewcommand*{\url}[1]{{\shorthandoff{:?!;}\urlORI{#1}}} +% La commande \path de url.sty ajoute des espaces parasites, pas \url, d'où +\let\path\url +% mais ceci impose de remplacer \path|...| par \path{...}, et les \$ inclus +% par des $. + +\newcommand{\THANH}{Hàn Th\'{ê} Thanh} + +\setlength{\parindent}{0mm} +\addtolength{\parskip}{.25\baselineskip} + +\begin{document} + +\title{{\huge Guide pratique de \TL{} \\\smallskip} + {\LARGE\textsf{\TL{} 2008}}% + } + +\author{Karl Berry \\[3mm] + \url{http://tug.org/texlive/}\\[5mm] + \textit{Version française}\\[3mm] + Daniel Flipo (GUTenberg) + } + +\date{Juillet 2008} + +\maketitle +\thispagestyle{empty} % no need for page number + +\begin{multicols}{2} +\tableofcontents +%\listoftables +\end{multicols} + +\section{Introduction} +\label{sec:intro} + +\subsection{\TeX\ Live et \TeX\ Collection} + +Ce document décrit les principales caractéristiques de la +distribution \TL{}, une distribution complète de \TeX{} +pour Linux et autres Unix, \MacOSX{} et systèmes Windows. + +Cette distribution peut être obtenue par téléchargement ou sur le \DVD{} \TK{} +distribué par les groupes d'utilisateurs de \TeX{} à leurs membres. +La section \ref{sec:tl-coll-dists} décrit brièvement le contenu de ce \DVD. +\TL{} comme \TK{} sont produits grâce au travail des groupes d'utilisateurs de +\TeX. La description qui suit porte essentiellement sur \TL. + +La distribution \TL{} comprend les binaires +pré-compilés de \TeX{}, \LaTeXe{}, \MF, \MP, \BibTeX{} et de nombreux +autres programmes ainsi qu'une bibliothèque étendue de macros, de +fontes et de documentations. Elle traite aussi de la composition de textes +dans la plupart des langues utilisées dans le monde. + +Les composants de la distribution \TL{} sont régulièrement mis à jour +sur le site \acro{CTAN}, \url{http://www.ctan.org}. + +On trouvera à la fin du document, section~\ref{sec:history} +(page~\pageref{sec:history}), un bref historique des principales modifications +apportées au fil du temps à la distribution \TL. + +% Ajout (df) +Les utilisateurs des éditions précédentes de \TL{} sont invités +à lire, \emph{avant toute mise à jour}, la section~\ref{tlcurrent} +page~\pageref{tlcurrent} qui présente les principaux changements intervenus +cette année. + +\subsection{Support pour différents systèmes d'exploitation} +\label{sec:os-support} + +\TL{} contient les exécutables pour les principales architectures Unix, en +particulier Linux et \MacOSX. Les sources inclus dans la distribution +devraient permettre de compiler les exécutables nécessaires aux autres +systèmes d'exploitation. + +En ce qui concerne Windows, seuls Windows 2000 et ses successeurs (XP, Vista) +sont supportés ; les architectures antérieures (Windows 9\textit{x}, ME et NT) +ne le sont plus. Il n'y a pas d'exécutables 64-bit mais les versions 32-bit +devraient fonctionner aussi sur les systèmes 64-bit. + +Consulter la section~\ref{sec:tl-coll-dists} pour des solutions alternatives +sous Windows et \MacOSX. + +\subsection{Utilisation élémentaire de \TL{}} +\label{sec:basic} + +Vous pouvez installer \TL{} de deux façons différentes : soit en utilisant +l'installeur qui télécharge toute la distribution sur Internet, soit à partir +du \DVD{} ce qui ne nécessite pas de connexion au réseau. + +Vous pouvez aussi exécuter \TL{} directement depuis le +\DVD{} (ou depuis une image iso du \DVD{} si votre système le permet) sans +(presque) rien installer sur le disque dur. + +Ces trois utilisations sont décrites en détail dans les sections suivantes, +voici quelques remarques générales pour débuter : + +\begin{itemize} + +\item Le script d'installation globale s'appelle +\filename{install-tl}. Il fonctionne en mode graphique (mode par défaut sous +Windows) et en mode texte (mode par défaut pour les autres systèmes). +Ajouter l'option \code{-gui} ou \code{-no-gui} pour imposer le mode graphique +ou le mode texte. + +\item Ce script installe en particulier un nouveau programme, le +« \TL\ Manager » appelé \prog{tlmgr}. Comme l'installeur, il peut être +utilisé en mode graphique ou en mode texte. Il permet d'ajouter ou de +supprimer des composants et de procéder à différents réglages de +configuration. + +\end{itemize} + +\subsection{Obtenir de l'aide} +\label{sec:help} + +La communauté \TeX{} est à la fois active et conviviale ; la plupart des +questions finissent par obtenir une réponse. Le support est +pourtant informel, assuré par des volontaires et des lecteurs +occasionnels, aussi est-il particulièrement important que vous fassiez +votre propre travail de recherche avant de poser la question (si vous +préférez un support commercial, vous pouvez renoncer à \TL{} et +acheter un système payant ; voir une liste à +\url{http://tug.org/interest.html#vendors}). + +Voici une liste de ressources, classées selon l'ordre dans lequel nous +recommandons de les utiliser : + +\begin{description} +\item [Getting Started] -- pour ceux qui débutent en \TeX, la page web +\url{http://tug.org/begin.html} contient une courte description +du système. + +\item [\acro{FAQ} \TeX{}] -- la \acro{FAQ} \TeX{} est un vaste recueil + de réponses à toutes sortes de questions, de la plus élémentaire à la + plus complexe. Elle est enregistrée sur le \DVD{} dans + \OnCD{texmf-doc/doc/english/FAQ-en/html/index.html} + et elle est disponible sur Internet à + l'adresse \url{http://www.tex.ac.uk/faq}. + Merci de consulter cette FAQ avant toute question. + +\item [Catalogue \TeX{}] -- si vous recherchez une extension, une fonte, + un programme, etc., le mieux est de consulter le catalogue + \TeX{} ici : \url{http://www.ctan.org/help/Catalogue/}. + +\item [Ressources \TeX{} sur le Web] -- la page web + \url{http://tug.org/interest.html} propose + beaucoup de liens relatifs à \TeX{}, en particulier concernant des + livres, manuels et articles portant sur tous les aspects du système. + +\item [Archives des forums d'aide] -- les principaux forums dédiés + au support de \TeX{} sont les groupes de news Usenet + \url{news:comp.text.tex} (en anglais) et \url{news:fr.comp.text.tex} + (en français) ainsi que les listes de diffusion + \email{texhax@tug.org} (en anglais) et \email{gut@ens.fr} (en français). + Les archives correspondantes contiennent des + milliers de questions et réponses déjà traitées et permettent + une recherche fructueuse. Voir + \url{http://groups.google.com/groups?group=fr.comp.text.tex} + et \url{http://tug.org/mail-archives/texhax}, respectivement. Une + question posée sur un moteur de recherche, tel que + \url{http://google.com}, peut aussi fournir des réponses pertinentes. + +\item [Poster une question] -- si vous ne trouvez pas de réponse, vous + pouvez poster la question à \dirname{fr.comp.text.tex} via Google ou + votre lecteur de news, ou encore par messagerie à + \email{texhax@tug.org}. Mais avant de le faire, merci de lire + l'introduction de la \acro{FAQ} donnant les conseils sur la façon de + rédiger la question pour avoir des chances d'obtenir une réponse pertinente : + \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. + +\item [Support de \TL{}] -- si vous voulez faire un rapport + d'anomalie, émettre des suggestions ou des commentaires sur la + distribution \TL{}, son installation ou sa documentation, utilisez + la liste de diffusion \email{tex-live@tug.org}. Mais attention, si + la question concerne l'utilisation d'un programme particulier inclus + dans \TL{}, il vaut mieux que vous vous adressiez directement à la + personne ou à la liste de diffusion qui maintient le programme. Il suffit + souvent d'ajouter l'option \code{-{}-help} lors de l'exécution du programme + pour trouver à qui adresser le rapport. + +\end{description} + +L'autre aspect du sujet concerne l'aide à apporter aux personnes +soumettant des questions. Les forums \dirname{comp.text.tex}, +\dirname{fr.comp.text.tex} ainsi que les listes de diffusion \code{texhax} +et \code{gut} +sont ouverts à tous, aussi n'hésitez pas à vous y joindre, à commencer +la lecture et à fournir de l'aide là où cela vous est possible. + +% No \protect needed as \TL is defined in French with \newcommand (robust). +\section{Structure de \TK} +\label{sec:overview-tl} + +Nous décrivons ici le contenu de \TK{} qui est un sur-ensemble de \TL. + +\subsection {\TK{} : \TL, pro\TeX{}t, Mac\TeX} +\label{sec:tl-coll-dists} + +Le \DVD{} \TK{} contient les éléments suivants : + +\begin{description} + +\item [\TL{}] -- un système \TeX{} complet (\TL) qui peut au choix, être lancé à + partir du \DVD{} (sans installation) ou être installé sur le disque dur. + +\item [CTAN] -- une image du site d'archives \CTAN. + +\item [pro\TeX{}t] -- une extension du système \MIKTEX\ pour Windows qui en + facilite l'installation. Cette distribution est totalement indépendante de + \TL{}, elle nécessite un mode d'installation spécifique. Le site de + \ProTeXt\ se trouve ici : \url{http://tug.org/protext}. + +\item [Mac\TeX] -- un programme d'installation spécifique de \TL{} pour + \MacOSX{} et quelques applications propres au système Mac. + Le site de Mac\TeX{} se trouve ici : \url{http://www.tug.org/mactex/}. + +\item [\texttt{texmf-extra}] -- un répertoire contenant quelques extensions + supplémentaires. + +\end{description} + +Les droits d'utilisation des fichiers présents dans \CTAN, \ProTeXt{} +et \texttt{texmf-extra} diffèrent de ceux de \TL{}, pensez à lire +les licences si vous envisagez de modifier ou de redistribuer certains de +ces fichiers. + +\subsection{Répertoires situés à la racine de \TL{}} +\label{sec:tld} + +La distribution \TL{} est dans le sous-répertoire \dirname{texlive} +du \DVD{} \TK{}. Les répertoires les plus importants +situés à la racine de la distribution \TL{} sont énumérés ci-dessous : + +\begin{ttdescription} +\item[bin] -- programmes de la famille \TeX{}, rangés dans des + sous-répertoires selon les plates-formes. +% +\item[readme.html] -- une brève introduction et quelques liens utiles sous forme + de pages \textsc{html} dans différentes langues. +% +\item[source] -- le code source de tous les programmes, incluant la + distribution \Webc{} de \TeX{} et \MF{}. +% +\item[support] -- ensemble d'extensions et programmes auxiliaires (en + particulier des éditeurs et des \textit{shells} dédiés à \TeX) ; ils ne sont + \emph{pas} installés par défaut. +% +\item[texmf] -- répertoire contenant les programmes et leur documentation ; ne + contient ni les formats ni les extensions (la variable \envname{TEXMFMAIN} + de la section suivante pointe sur ce répertoire). +% +\item[texmf-dist] -- répertoire principal où se trouvent les extensions, + les fontes, etc., avec leur documentation (la variable \envname{TEXMFDIST} + de la section suivante pointe sur ce répertoire). +% +\item[texmf-doc] -- répertoire contenant le reste de la documentation, le + sous-répertoire doc est organisé par langue. +% +\item[tlpkg] -- scripts et programmes d'installation ; des versions de + Perl et de Ghostscript (inaccessibles en dehors de \TL) ainsi qu'un + nouveau visualiseur de fichiers PostScript ont été ajoutés pour + Windows. +\end{ttdescription} + +On trouve également, au même niveau que les répertoires mentionnés ci-dessus, +les scripts d'installation et les fichiers \filename{README} (disponibles dans +différentes langues). + +Le répertoire \dirname{texmf-doc} ne contient que de la documentation +mais pas toute la documentation. Celle concernant les programmes (manuels, +pages \textit{man} et fichiers de type \textit{info} est dans +\dirname{texmf/doc} car les programmes correspondants sont dans +\dirname{texmf}. De même, la documentation des extensions et formats +est dans \dirname{texmf-dist/doc}. Les commandes \cmdname{texdoc} ou +\cmdname{texdoctk} trouveront pour vous les documentations où qu'elles soient +sur le disque. +Le fichier \OnCD{doc.html} du \DVD{} contient une liste de liens bien +utiles pour localiser les fichiers de documentation. + +La documentation de \TL\ proprement dite est disponible dans le répertoire +\dirname{texmf-doc} en plusieurs langues, + +\begin{itemize} +\item{anglais :} \OnCD{texmf-doc/doc/english/texlive-en}, +\item{allemand :} \OnCD{texmf-doc/doc/german/texlive-de}, +\item{chinois (simplifié) :} \OnCD{texmf-doc/doc/chinese/texlive-zh-cn}, +\item{français :} \OnCD{texmf-doc/doc/french/texlive-fr}, +\item{polonais :} \OnCD{texmf-doc/doc/polish/texlive-pl}, +\item{russe :} \OnCD{texmf-doc/doc/russian/texlive-ru}, +\item{tchèque \& slovaque :} \OnCD{texmf-doc/doc/czechslovak/texlive-cz}. +\end{itemize} + +\subsection{Description des arborescences « texmf » de \TL} +\label{sec:texmftrees} + +Nous donnons ici la liste complète des variables prédéfinies qui contiennent +les noms des différentes arborescences de type « texmf » et l'usage qui +en est fait. La commande \cmdname{texconfig conf} retourne les valeurs de ces +variables, ce qui permet de savoir où se trouvent ces différentes +arborescences dans une installation donnée. + +\begin{ttdescription} +\item [TEXMFMAIN] -- contient les éléments essentiels du système, comme les + scripts (\cmdname{web2c/mktexdir}, etc.), leur documentation mais pas les + formats ni les fichiers de macros.-- +\item [TEXMFDIST] -- contient les fichiers de macros (Plain, \LaTeX, \ConTeXt, + etc.,), les fontes, etc., de la distribution \TL{} ; rien ne devrait être + ni ajouté ni supprimé dans cette arborescence. +\item [TEXMFLOCAL] -- c'est là que l'administrateur de la machine doit + placer les classes et extensions locales, les fontes non disponibles + dans \TL, etc. +\item [TEXMFHOME] -- contient les fichiers personnels (extensions, classes, + fontes) de l'utilisateur ; ce répertoire est installé automatiquement dans + le répertoire personnel de l'utilisateur. +\item [TEXMFCONFIG] -- c'est là que les scripts \cmdname{updmap} et + \cmdname{fmtutil} recherchent leurs fichiers de configuration en priorité. + \cmdname{texconfig} y place les versions modifiées des fichiers de + configuration. Sous \envname{TEXMFHOME} par défaut. +\item [TEXMFSYSCONFIG] -- c'est là que les scripts \cmdname{updmap-sys} et + \cmdname{fmtutil-sys} recherchent leurs fichiers de configuration en + priorité. \cmdname{texconfig-sys} y place les versions modifiées des + fichiers de configuration. +\item [TEXMFVAR] -- c'est là que les scripts \cmdname{texconfig}, + \cmdname{updmap} et \cmdname{fmtutil} rangent les formats et les fichiers + \file{.map} qu'ils produisent. Sous \verb+$HOME+ par défaut. %$ +\item [TEXMFSYSVAR] -- c'est là que les scripts \cmdname{texconfig-sys}, + \cmdname{updmap-sys} et \cmdname{fmtutil-sys} rangent les formats et les + fichiers \file{.map} qu'ils produisent. +\end{ttdescription} + +La structure de l'arborescence \TL{} est par défaut la suivante : +\begin{description} +\item[racine multi-utilisateurs] (par exemple \verb|/usr/local/texlive|, + \verb|D:\texlive|,\dots) qui contient éventuellement plusieurs + distributions : + \begin{ttdescription} + \item[2007] -- la distribution précédente, + \begin{ttdescription} + \item [...] + \end{ttdescription} + \item[2008] -- la distribution actuelle, + \begin{ttdescription} + \item [bin] ~ + \begin{ttdescription} + \item [i386-linux] -- exécutables Linux, + \item [...] + \item [universal-darwin] -- exécutables \MacOSX, + \item [win32] -- exécutables Windows, + \end{ttdescription} + \item [texmf] -- correspond à \envname{TEXMFMAIN}, + \item [texmf-dist] -- correspond à \envname{TEXMFDIST}, + \item [texmf-doc] -- correspond à \envname{TEXMFDOC}, + \item [texmf-var] -- correspond à \envname{TEXMFSYSVAR}, + \item [texmf-config] -- correspond à \envname{TEXMFSYSCONFIG}, + \end{ttdescription} + \item [texmf-local] -- correspond à \envname{TEXMFLOCAL}, normalement + commun à plusieurs distributions \TL{} (2007, 2008, etc.), + \end{ttdescription} + \item[répertoire personnel de l'utilisateur] \texttt{\$HOME} ou + \texttt{\%USERPROFILE\%} : + \begin{ttdescription} + \item[.texlive2007] -- fichiers générés automatiquement par la + distribution \TL{} précédente, + \item[.texlive2008] -- fichiers générés automatiquement par la + distribution \TL{} actuelle, + \begin{ttdescription} + \item [texmf-var] -- correspond à \envname{TEXMFVAR}, + \item [texmf-config] -- correspond à \envname{TEXMFCONFIG}, + \end{ttdescription} + \item[texmf] -- correspond à \envname{TEXMFHOME}, répertoire regroupant + tous les répertoires de macros personnelles : \dirname{texmf/tex/latex} + par exemple pour les fichiers de macros LaTeX, etc. + \end{ttdescription} +\end{description} + +\subsection{Les extensions de \TeX} +\label{sec:tex-extensions} + +\TL{} contient, à part \TeX{} lui-même (le programme \prog{tex}) qui est figé +sauf rares corrections de bogues, plusieurs extensions de \TeX{}. + +\begin{description} + +\item [\eTeX{}] \label{text:etex} ajoute un jeu de nouvelles + primitives et les extensions \TeXXeT{} pour l'écriture de droite + à gauche ; \eTeX{} est, en mode normal, 100\% compatible avec + \TeX{} standard. Pour plus de détails consulter le + fichier \OnCD{texmf-dist/doc/etex/base/etex_man.pdf} du \DVD{}. + +\item [pdf\TeX{}] inclut les extensions \eTeX{} et produit, au choix, + des fichiers au format Acrobat \acro{PDF} ou au format \dvi{}. + C'est le moteur de base sur lequel sont construits tous les formats autres + que plain\TeX{} (voir \url{http://www.pdftex.org/}). + Le manuel d'utilisation se trouve sur le \DVD{} + dans \OnCD{texmf/doc/pdftex/manual/}. Le fichier + \OnCD{texmf/doc/pdftex/pdftex/manual/samplepdf/samplepdf.tex} + donne des exemples d'utilisation. + +\item [Lua\TeX] est le successeur de pdf\TeX{} + avec lequel il reste compatible. Il devrait également remplacer Aleph, voir + ci-dessous. Lua\TeX{} fait appel à l'interpréteur de commande Lua (voir + \url{http://www.lua.org/}) qui apporte des solutions élégantes + à beaucoup de problèmes épineux en \TeX{} pur. + La commande \filename{texlua}, qui fonctionne comme un interpréteur Lua + indépendant, est déjà utilisée en tant que telle dans \TL. + Voir \url{http://www.luatex.org/} et + \OnCD{texmf-dist/doc/luatex/luatexref-t.pdf}. + +\item [Xe\TeX] ajoute la possibilité d'utiliser en entrée le codage Unicode + et en sortie les fontes OpenType et les fontes système de la machine, ceci + grâce à des bibliothèques externes : voir \url{http://scripts.sil.org/xetex}. + +\item [\OMEGA{} (Omega)] fonctionne en utilisant Unicode et des + caractères 16 bits, ce qui lui permet de travailler directement et + simultanément avec presque toutes les écritures du monde. + L'extension supporte aussi le chargement dynamique d'\acro{OTP} + (\OMEGA{} \emph{Translation Processes}) qui permet à l'utilisateur + d'appliquer sur des flux d'entrée quelconques des transformations + complexes qu'il aura lui-même définies. Voir la documentation + (pas vraiment à jour) dans \OnCD{texmf-dist/doc/omega/base/doc-1.8.tex}. + +\item [Aleph] combine les fonctionnalités de \OMEGA\ et de \eTeX. + \OnCD{texmf-dist/doc/aleph/base} contient une documentation de base. + +\end{description} + +% Fin MAJ 15/07/2008 +\subsection{Quelques autres programmes intéressants + dans \TL} + +Voici quelques autres programmes couramment utilisés et présents dans +\TL{} : + +\begin{cmddescription} + +\item [bibtex] -- traitement de la bibliographie. + +\item [makeindex] -- traitement des index. + +\item [dvips] -- conversion \dvi{} vers \PS{}. + +\item [xdvi] -- visualisation \dvi{} pour le système X Window. + +\item [dvilj] -- pilote \dvi{} pour les imprimantes HP LaserJet. + +\item [dv2dt, dt2dv] -- conversion \dvi{} vers ou depuis du texte simple. + +\item [dviconcat, dviselect] -- couper/Coller de pages à partir de fichiers + \dvi{}. + +\item [dvipdfmx] -- conversion \dvi{} vers \acro{PDF}, une autre façon de + produire des fichiers \acro{PDF}, concurrente de pdf\TeX\ mentionné + ci-dessus ; voir aussi les extensions \pkgname{ps4pdf} et + \pkgname{pdftricks} pour d'autres alternatives. + +\item [psselect, psnup, \ldots] -- utilitaires \PS{}. + +\item [lacheck] -- vérification de syntaxe \LaTeX{}. + +\item [texexec, texmfstart] -- processeurs Con\TeX{}t et \acro{PDF}. + +\item [tex4ht] -- conversion \TeX{} vers \acro{HTML} et \acro{XML}. + +\end{cmddescription} + +\subsection{Fontes incluses dans \TL} +\label{sec:tl-fonts} + +La distribution \TL{} contient un grand nombre de fontes vectorielles de haute +qualité : voir \url{http://tug.org/fonts} et +\OnCD{texmf-doc/english/free-math-fonts-survey}. + + +\section{Installation} +\label{sec:install} + +\subsection{Démarrage de l'installation} +\label{sec:inst_start} + +La première chose à faire est de récupérer le \DVD{} \TK ou de +télécharger le programme d'installation par le réseau. +Le programme d'installation s'appelle \filename{install-tl} pour Unix +et \filename{install-tl.bat} pour Windows. + +\begin{description} +\item [Installeur réseau] -- à télécharger sur CTAN dans + \dirname{systems/texlive/tlnet}; l'url + \url{http://mirror.ctan.org/systems/texlive/tlnet} vous redirigera + automatiquement vers le serveur d'archive le plus proche de chez vous. + Deux versions sont disponibles, \filename{install-tl.zip} utilisable sous + Unix et sous Windows et \filename{install-unx.tar.gz} pour Unix seulement + (y compris \MacOSX). Après décompression de l'un de ces deux fichiers, les + scripts \filename{install-tl} et \filename{install-tl.bat} se trouveront + dans le sous-répertoire \dirname{install-tl}. + +\item [\DVD \TK{}] -- aller dans le répertoire \dirname{texlive}. + Sous Windows, l'installation démarrera probablement + automatiquement quand vous insérerez le \DVD, sinon, il faudra lancer le + script d'installation \filename{install-tl} ou \filename{install-tl.bat}. + Le \DVD \TK{} est distribué gratuitement aux membres des groupes + d'utilisateurs de \TeX{} (Gutenberg par exemple en France, voir la liste + des groupes sur \url{http://tug.org/usergroups.html}). Il est également + possible de l'acheter séparément (\url{http://tug.org/store}) ou de graver + l'image \ISO{} (\url{http://tug.org/texlive/acquire.html}). +\end{description} +Les sections suivantes détaillent le processus d'installation. + + +\begin{figure}[tb] +\centering +\begin{boxedverbatim} +======================> TeX Live installation procedure <===================== + +=======> Note: Letters/digits in indicate menu items <======= +=======> for commands or configurable options <======= + + + Detected platform: Intel x86 with GNU/Linux + + binary systems: 1 out of 16 + + Installation scheme (scheme-full) + + Customizing installation scheme: + standard collections + language collections + 83 collections out of 84, disk space required: 1666 MB + + directories: + TEXDIR (the main TeX directory): + !! default location: /usr/local/texlive/2008 + !! is not writable, please select a different one! + TEXMFLOCAL (directory for site-wide local files): + /usr/local/texlive/texmf-local + TEXMFSYSVAR (directory for variable and automatically generated data): + /usr/local/texlive/2008/texmf-var + TEXMFSYSCONFIG (directory for local config): + /usr/local/texlive/2008/texmf-config + TEXMFHOME (directory for user-specific files): + ~/texmf + + options: + [ ] use letter size instead of A4 by default + [X] create all format files + [X] install macro/font doc tree + [X] install macro/font source tree + [ ] create symlinks in standard directories + + Install for running from DVD + +Other actions: + start installation to HD + help + quit + +Enter command: +\end{boxedverbatim} +\caption{Écran principal de configuration (\GNU/Linux)}\label{fig:text-main} +\end{figure} + +\begin{figure}[tb] +\centering +\tlpng{install-w32-main}{\linewidth} +\caption{Écran principal de configuration (Windows)}\label{fig:gui-main} +\end{figure} + +\subsubsection{Installation sous Unix} + +Dans ce qui suit l'invite du \textit{shell} est notée \texttt{>} ; les +commandes de l'utilisateur sont en \Ucom{\texttt{gras}}.\linebreak +Commandes à lancer dans un terminal sur tout système Unix pour travailler en +mode texte : +\begin{alltt} +> \Ucom{cd /chemin/de/installeur} +> \Ucom{perl install-tl} +\end{alltt} + +Pour travailler en mode graphique : +\begin{alltt} +> \Ucom{cd /chemin/de/installeur} +> \Ucom{./install-tl -gui} +\end{alltt} + +La liste complète des options est donnée par +\begin{alltt} +> \Ucom{perl install-tl -help} +\end{alltt} + +\textbf{Attention} : le matériel installé doit normalement être accessible à +tous les utilisateurs de la machine ; si celui qui installe n'est pas +\textit{root}, il devra s'assurer que son \code{umask} est adapté, par +exemple \code{umask 022} ou \code{umask 002}. +Consulter la documentation système pour plus de précisions. + +\subsubsection{Installation sous Mac\,OS\,X} + +Une distribution spécifique, Mac\TeX\ (\url{http://tug.org/mactex}), a été +mise au point pour \MacOSX. Nous recommandons de l'utiliser plutôt que +d'installer la distribution \TL{} en suivant la procédure indiquée pour Unix. + +En effet, Mac\TeX{} permet des ajustements spécifiques pour le système +\MacOSX{} et facilite la cohabitation entre plusieurs distributions \TeX{} +(Mac\TeX, gw\TeX, Fink, MacPorts, \ldots). + +Mac\TeX\ est très proche de \TL, les arborescences principales sont en tous +points identiques, quelques répertoires contenant de la documentation et des +applications spécifiques au Mac sont ajoutés. + +\subsubsection{Installation sous Windows} + +Si vous utilisez l'installeur réseau ou si l'insertion du \DVD{} ne lance pas +l'installation automatiquement, double-cliquez sur \filename{install-tl.bat}. + +Il est également possible de travailler en ligne de commande ; +dans ce qui suit l'invite du \textit{shell} est notée \texttt{>}, les +commandes de l'utilisateur sont notées \Ucom{\texttt{en gras}}. Voici les +commandes à lancer : +\begin{alltt} +> \Ucom{install-tl} +\end{alltt} +à condition d'être dans répertoire du script d'installation, sinon +\begin{alltt} +> \Ucom{D:\bs{}texlive\bs{}install-tl} +\end{alltt} +où \texttt{D:} désigne le lecteur de \DVD. + +Pour travailler en mode texte : +\begin{alltt} +> \Ucom{install-tl -no-gui} +\end{alltt} +La liste complète des options est donnée par +\begin{alltt} +> \Ucom{install-tl -help} +\end{alltt} + +\subsubsection{Installation en mode texte} + +La figure~\ref{fig:text-main} page~\pageref{fig:text-main} présente l'écran +principal de configuration en mode texte sous Unix/Linux. + +Taper une des lettres proposées (en respectant la casse) suivie de +« Entrée » (retour-chariot), l'écran se mettra automatiquement à jour. + +L'interface est volontairement rudimentaire afin de permettre son utilisation +sur le plus grand nombre possible de systèmes même avec des versions très +dépouillées de Perl (un sous-ensemble de commande Perl est fourni pour Windows). + +\subsubsection{Installation en mode graphique} + +La figure~\ref{fig:gui-main} page~\pageref{fig:gui-main} présente l'écran +principal de configuration en mode graphique sous Windows. Les différences +entre les options disponibles en mode texte et en mode graphique s'expliquent +par le changement de système (\GNU/Linux pour le premier, Windows pour le +second). + +\subsection{Choix des options d'installation} +\label{sec:runinstall} + +Les options proposées sont censées être assez explicites, voici cependant +quelques précisions. + +\subsubsection{Choix des binaires (Unix seulement)} +\label{sec:binary} + +\begin{figure}[tbh] +\centering +\begin{boxedverbatim} +Available sets of binaries: +=============================================================================== + + a [ ] alpha-linux DEC Alpha with GNU/Linux + b [ ] amd64-freebsd x86_64 with FreeBSD + c [ ] hppa-hpux HP-UX + d [ ] i386-freebsd Intel x86 with FreeBSD + e [X] i386-linux Intel x86 with GNU/Linux + f [ ] i386-openbsd Intel x86 with OpenBSD + g [ ] i386-solaris Intel x86 with Sun Solaris + h [ ] mips-irix SGI IRIX + i [ ] powerpc-aix PowerPC with AIX + j [ ] powerpc-linux PowerPC with GNU/Linux + k [ ] sparc-linux Sparc with GNU/Linux + l [ ] sparc-solaris Sparc with Solaris + m [ ] universal-darwin universal binaries for MacOSX/Darwin + o [ ] win32 Windows + p [ ] x86_64-linux x86_64 with GNU/Linux +\end{boxedverbatim} +\caption{Menu pour le choix des binaires}\label{fig:bin-text} +\end{figure} + +La figure~\ref{fig:bin-text} présente les choix de binaires possibles en mode +texte. Seuls les binaires correspondant à l'architecture détectée seront +installés par défaut. Rien n'empêche d'en sélectionner d'autres si nécessaire, +ce qui peut être intéressant dans le cas de serveurs en réseau ou sur des +machines en « double boot ». + +\subsubsection{Choix des composants de l'installation} +\label{sec:components} + +\begin{figure}[tbh] +\centering +\begin{boxedverbatim} +Select a scheme: +=============================================================================== + + a [ ] TeX Live basic scheme + b [ ] TeX Live scheme for ConTeXt + c [X] TeX Live full scheme + d [ ] GUST TeX Live scheme + e [ ] GUTenberg TeX Live scheme + f [ ] TeX Live medium scheme + g [ ] TeX Live minimal scheme + h [ ] TeX Live for Omega users + i [ ] teTeX scheme + j [ ] XML typesetting scheme +\end{boxedverbatim} +\caption{Menu « Scheme »}\label{fig:scheme-text} +\end{figure} + +Dans le menu « Scheme » (voir figure~\ref{fig:scheme-text}) on choisit +un schéma général de configuration qui détermine un ensemble de collections à +installer. Par défaut, on procède à l'installation de tout ce qui est +disponible (option \optname{scheme-full}). Des installations plus ou moins +complètes sont proposées : \optname{minimal} pour effectuer des tests +uniquement, \optname{basic} pour un système de base, \optname{medium} ou +\optname{teTeX} pour des systèmes intermédiaires. +Pour les francophones, l'option \optname{GUTenberg} est une bonne base de +départ. Le choix pourra être affiné à l'étape suivante. + +\begin{figure}[tbh] +\centering +\tlpng{stdcoll}{.7\linewidth} +\caption{Menu « Collections » (Linux)}\label{fig:collections-gui} +\end{figure} + +Une fois choisi le schéma général, il est possible de d'ajouter ou de +supprimer des composants, appelés +ici collections. Il y a deux types de collections : les +« Standard Collections » qui concernent les fontes, les extensions, les +formats, etc. (voir figure~\ref{fig:collections-gui}) et les +« Language Collections » qui permettent de préciser la liste des langues +qui seront utilisables sur le système (indispensable !). Attention, si vous +travaillez en mode texte, dans ces menus la casse des lettres est importante. +En mode graphique, il suffit de cocher ou de décocher les cases en cliquant. + +Il est possible de raffiner encore les choix mais il faudra alors utiliser +le programme \prog{tlmgr} ultérieurement, voir la section~\ref{sec:tlmgr}. + +\subsubsection{Répertoires d'installation} +\label{sec:directories} + +La racine de l'installation principale est donnée par \dirname{TEXDIR} qui +vaut par défaut \dirname{/usr/local/texlive/2008} sous Unix et +|%PROGRAMFILES%\texlive\2008| sous Windows. +La liste des sous-répertoires de \dirname{TEXDIR} choisis par défaut est +donnée à la section~\ref{sec:texmftrees}, page~\pageref{sec:texmftrees}. + +Il peut être nécessaire de changer la valeur de \dirname{TEXDIR} +lorsque celui qui procède à l'installation n'a pas les droits d'écriture +sur le répertoire \dirname{TEXDIR} (l'installation n'est pas réservée au +super-utilisateur « root » ou « Administrateur »). +Il est possible d'installer \TL{} dans le répertoire personnel d'un +utilisateur, dans ce cas on peut choisir par exemple |~/texlive/2008|. + +Dans tous les cas, il est recommandé d'inclure l'année dans le chemin afin de +pouvoir conserver plusieurs versions de \TL{} en parallèle. +Rien n'empêche d'ajouter un lien symbolique (par exemple +\dirname{/usr/local/texlive-current}) qui pointe sur la version actuellement +utilisée. Ceci facilite les basculements d'une version à une autre. + +Le répertoire \envname{TEXMFHOME} (|~/texmf| par défaut) est destiné à +regrouper les répertoires de macros personnelles. Le caractère |~| désignant +le répertoire personnel est traité différemment, selon qu'il est utilisé dans +\dirname{TEXDIR} --~il s'agit alors du répertoire de \emph{l'installateur}~-- +ou dans \envname{TEXMFHOME}, là |~| est traité dynamiquement utilisateur par +utilisateur est vaut \envname{\$HOME} %$ +sous Unix et |%USERPROFILE%| sous Windows. + +\subsubsection{Options} +\label{sec:options} + +\begin{figure}[tbh] +\centering +\begin{boxedverbatim} +

use letter size instead of A4 by default: [ ] + create all format files: [X] + install font/macro doc tree: [X] + install font/macro source tree: [X] + create symlinks in standard directories: [ ] + binaries to: + manpages to: + info to: +\end{boxedverbatim} +\caption{menu « Options » (Unix)}\label{fig:options-text} +\end{figure} + +La figure~\ref{fig:options-text} présente le menu « Options » en mode +texte. Normalement il n'y a pas lieu de modifier les choix par défaut. +Voici quelques précisions cependant. + +\begin{description} +\item[use letter size instead of A4 by default] -- la taille du papier pour + l'impression est A4, il est possible de la changer ici, en \textit{letter} + par exemple. + +\item[create all format files] -- création de tous les formats à l'installation. + Bien que cette opération prenne un peu de temps, il est conseillé de ne pas + la supprimer, sinon les formats seront créés au coup par coup dans les + répertoires personnels des utilisateurs (sous \envname{TEXMFVAR}). Les + formats personnels ainsi créés ne bénéficieront pas des mises à jour + éventuelles effectuées ultérieurement sur l'installation \TL{}, ce qui + peut engendrer des incompatibilités. + +\item[create symlinks in standard directories] (Unix seulement) -- + cette option permet d'éviter de modifier les variables d'environnement + \envname{PATH}, \envname{MANPATH} et \envname{INFOPATH}. En revanche, + elle peut perturber une installation \TeX{} incluse dans votre distribution + (Debian, RedHat, etc.). La modification des trois variables d'environnement + ci-dessus est préférable. +\end{description} + +Lorsque vous êtes satisfait des réglages faits, il vous reste à taper +\code{I} pour lancer le processus d'installation. Lorsque celui-ci sera +terminé, sautez à la section~\ref{sec:postinstall} pour voir s'il y a +d'autres choses à faire. + +\subsubsection{Utilisation de \TL{} à partir du DVD{} (mode texte uniquement)} +\label{sec:fromdvd} + +Taper `|V|' pour choisir ce mode de fonctionnement, le menu qui s'affiche +alors est présenté figure~\ref{fig:main-fromdvd}. +\begin{figure}[tbh] +\centering +\begin{boxedverbatim} +======================> TeX Live installation procedure <===================== + +=======> Note: Letters/digits in indicate menu items <======= +=======> for commands or configurable options <======= + + directories: + TEXDIRW (Writable root): + !! default location: /usr/local/texlive/2008 + !! is not writable, please select a different one! + TEXMFLOCAL (directory for site-wide local files): + /usr/local/texlive/texmf-local + TEXMFSYSVAR (directory for variable and automatically generated data): + /usr/local/texlive/2008/texmf-var + TEXMFSYSCONFIG (directory for local config): + /usr/local/texlive/2008/texmf-config + TEXMFHOME (directory for user-specific files): + ~/texmf + + options: + [ ] use letter size instead of A4 by default + [X] create all format files + + set up for installing to hard disk + +Other actions: + start installation for running from DVD + help + quit +\end{boxedverbatim} +\caption{Menu principal après choix de l'option « \optname{running from DVD} »}% +\label{fig:main-fromdvd} +\end{figure} +Noter les changements : toutes les options concernant le choix du matériel à +installer, les liens symboliques, ont disparu. Le menu « Directories » +parle maintenant de \dirname{TEXDIRW} (racine accessible en écriture). + +L'exécution de \TL{} à partir du \DVD{} nécessite la création de quelques +répertoires mais un minimum de fichiers sont installés sur le disque dur. + +La configuration après installation pour Unix est un peu plus complexe, voir +section~\ref{sec:postinstall}. + +Faute de temps, cette option n'a pu être intégrée à l'interface graphique. +Elle reste utilisable en mode texte y compris sous Windows, voir +section~\ref{sec:cmdline}. + +La section \ref{sec:portable-unix} décrit une autre façon d'utiliser \TL{} à +partir du \DVD{}. Elle ne nécessite aucune modification du système mais ne +permet aucune personnalisation. + +\subsection{Options en ligne de commande} +\label{sec:cmdline} + +Taper +\begin{alltt} +> \Ucom{install-tl -help} +\end{alltt} +pour obtenir la liste de toutes les options disponibles. +Voici les principales : + +\begin{ttdescription} +\item[-gui] -- exécution en mode graphique (si possible). Ceci nécessite le + module Perl/Tk (\url{http://tug.org/texlive/distro.html#perltk}) ; si + Perl/Tk n'est pas disponible, l'installation se poursuit en mode texte. +\item[-no-gui] -- exécution en mode texte, même sous Windows ; + ceci est utile pour exécuter \TL{} à partir du \DVD{} (option non disponible + en mode graphique). +\item[-lang {\sl LL}] -- impose la langue utilisée dans les menus lors de + l'installation. Le code de langue comporte deux lettres. Sont actuellement + disponibles les langues suivantes : : anglais (\texttt{en}, langue par + défaut), allemand (\texttt{de}), français (\texttt{fr}), néerlandais + (\texttt{nl}), polonais (\texttt{pl}), Slovène (\texttt{sl}) et vietnamien + (\texttt{vi}). Le programme s'efforce de déterminer automatiquement + la langue à utiliser et se rabat sur l'anglais en cas d'échec. +\item[-profile {\sl profile}] -- à chaque exécution, le script d'installation + écrit un compte-rendu dans le fichier + \filename{texlive.profile} du répertoire \dirname{2008/tlpkg} ou + \dirname{tlpkg}. L'option \texttt{-profile} demande au script de réutiliser + le fichier \filename{texlive.profile}. En voici un extrait : + \begin{fverbatim} +# texlive.profile written on Wed Jul 9 16:13:44 2008 UTC +# It will NOT be updated and reflects only the +# installation profile at installation time. +selected_scheme scheme-basic +TEXDIR /usr/local/texlive/2008 +TEXDIRW /usr/local/texlive/2008 +... +TEXMFSYSVAR /usr/local/texlive/2008/texmf-var +collection-basic 1 +... +option_symlinks 0 + \end{fverbatim} + Il est ainsi facile de reproduire un même scéma d'installation sur plusieurs + machines. +\item [-location {\slshape url/path}] -- choix d'une source où récupérer le + matériel à installer. \label{item:location} + +L'argument de l'option \texttt{{\slshape url/path}} peut être une url +commençant par \texttt{ftp:}, \texttt{http:}, ou \texttt{file:/} ou bien un +chemin local. + +Si l'argument correspond à un chemin local (ou une url de type +\texttt{file:/}), le script recherche un sous-répertoire +\dirname{archive} contenant des fichiers compressés \filename{.tar.lzma}, +ceux-ci seront utilisés en priorité. + +Si l'argument est une url distante (\texttt{http:} ou \texttt{ftp:}) +le `\texttt{/}' final ainsi que la chaîne `\texttt{/tlpkg}' sont ignorés. +Par exemple, le choix du miroir \CTAN{} +\url{http://mirrors.ircam.fr/pub/CTAN/systems/texlive/tlnet/2008/} +est valide. La liste des miroirs \CTAN{} est ici : +\url{http://ctan.org/mirrors}. + +Lorsqu'aucune option \texttt{-location} n'est spécifiée, le script +d'installation choisit un miroir automatiquement, celui-ci servira +pour tout le téléchargement. +\end{ttdescription} + +\subsection{Terminer l'installation} +\label{sec:postinstall} + +Selon les cas quelques opérations supplémentaires peuvent être nécessaires. + +\subsubsection{Windows} + +Sous Windows, le programme d'installation s'occupe de tout (normalement). + +\subsubsection{Cas où des liens symboliques sont créés} + +Si vous avez opté pour l'option créant des liens symboliques (voir +section~\ref{sec:options}), il n'est pas nécessaire d'ajuster les variables +d'environnement. + +\subsubsection{Variables d'environnement Unix} +\label{sec:env} + +Le chemin des binaires correspondant à votre machine doit être ajouté à la +variable \envname{PATH}. À chaque architecture correspond un sous-répertoire +de \dirname{TEXDIR/bin}, voir la liste à la figure~\ref{fig:bin-text} +\pageref{fig:bin-text}. + +Si vous voulez que votre système trouve les fichiers de documentation +concernant \TL{}, il faut également ajuster les variables \envname{MANPATH} +et \envname{INFOPATH}. + +Pour les \textit{shells} dits « Bourne-compatible » tels que +\prog{bash} sous GNU/Linux, le fichier à éditer peut être +\filename{$HOME/.bash\_profile} ou \filename{$HOME/.profile} et les lignes à +ajouter sont de la forme suivante : + +\begin{sverbatim} +PATH=/usr/local/texlive/2008/bin/i386-linux:$PATH; export PATH +MANPATH=/usr/local/texlive/2008/texmf/doc/man:$MANPATH; export MANPATH +INFOPATH=/usr/local/texlive/2008/texmf/doc/info:$INFOPATH; export INFOPATH +\end{sverbatim} + +Pour les \textit{shells} \prog{csh} ou \prog{tcsh}, le fichier à éditer +est en principe \filename{$HOME/.cshrc} %$ +et les lignes à ajouter sont de la forme suivante : +\begin{sverbatim} +setenv PATH /usr/local/texlive/2008/bin/i386-linux:$PATH +setenv MANPATH /usr/local/texlive/2008/texmf/doc/man:$MANPATH +setenv INFOPATH /usr/local/texlive/2008/texmf/doc/info:$INFOPATH +\end{sverbatim} + +%$ + +\subsubsection{Variables d'environnement : configuration multi-utilisateur} +\label{sec:envglobal} + +Il est possible d'ajuster les variables \envname{PATH}, \envname{MANPATH} +et \envname{INFOPATH} globalement pour tous les utilisateurs présents et +futurs sans avoir à éditer les fichiers personnels de chacun mais les façons +de le faire sont trop différentes d'un système à l'autre pour être présentées +ici. + +Voici quelques pistes : pour \envname{MANPATH} chercher un fichier +\filename{/etc/manpath.config}, s'il est présent lui ajouter +des lignes du genre +\begin{sverbatim} +MANPATH_MAP /usr/local/texlive/2008/bin/i386-linux \ + /usr/local/texlive/2008/texmf/doc/man +\end{sverbatim} +Pour les deux autres, chercher un fichier\filename{/etc/environment}, il est +éventuellement possible d'y définir les valeurs des variables d'environnement +telles que \envname{PATH} et \envname{INFOPATH}. + +\subsubsection{Exécution à partir du DVD} + +Les programmes de \TL{} consultent le fichier \filename{texmf.cnf} pour savoir +dans quelles arborescences se trouvent les fichiers dont ils ont besoin. +Malheureusement, ceci ne fonctionne pas lorsque les programmes sont lancés à +partir d'un \DVD{} ; en effet certains chemins ne sont connus qu'à +l'installation et ne peuvent être inscrits sur le \DVD{} puisqu'il est +accessible uniquement en lecture. Il faut donc créer un fichier +\filename{texmf.cnf} sur le disque et préciser où il se trouve grâce à la +variable d'environnement \envname{TEXMFCNF}. Ceci ne dispense pas de +modifier la variable d'environnement \envname{PATH} comme indiqué ci-dessus. + +Le script d'installation affiche en fin de traitement, un message indiquant la +valeur à donner à la variable \envname{TEXMFCNF}. Si ce message vous a +échappé, cette valeur est \dirname{$TEXMFSYSVAR/web2c}, %$ +qui vaut par défaut \dirname{/usr/local/texlive/2008/texmf-var/web2c}. + +Voici les lignes à taper dans ce cas : +\begin{sverbatim} +TEXMFCNF=/usr/local/texlive/2008/texmf-var/web2c; export TEXMFCNF +\end{sverbatim} +ou pour [t]csh: +\begin{sverbatim} +setenv TEXMFCNF /usr/local/texlive/2008/texmf-var/web2c +\end{sverbatim} + +\subsubsection{\ConTeXt{} Mark IV} + +L'ancien \ConTeXt{} devrait fonctionner sans problème. La nouvelle version, +appelée « Mark IV » demande un peu de configuration spécifique, voir +\url{http://wiki.contextgarden.net/Running_Mark_IV}. + +\subsubsection{Ajout de fichiers locaux ou personnels} + +Comme cela a déjà été indiqué à la section~\ref{sec:texmftrees}, +\envname{TEXMFLOCAL} (par défaut \dirname{/usr/local/texlive/texmf-local} ou +\verb|C:\Program Files\texlive\texmf-local|) est la racine de +l'arborescence prévue pour regrouper les fichiers de macros, les fontes et le +matériel utilisable par l'ensemble des utilisateurs du système. +D'autre part \envname{TEXMFHOME} (par défaut \dirname{$HOME/texmf} %$ +(ou |%USERPROFILE%\texmf|) regroupe le matériel personnel de chaque +utilisateur. + +Dans les deux cas, les fichiers ajoutés doivent être placés, non pas en vrac à +la racine de \envname{TEXMFLOCAL} ou \envname{TEXMFHOME} mais dans des +sous-répertoires bien choisis (voir \url{http://tug.org/tds} ou lire le +fichier \filename{texmf.cnf}). Par exemple, une classe ou une extension +\LaTeX{} ne sera trouvée que si elle est dans \dirname{TEXMFLOCAL/tex/latex} ou +\dirname{TEXMFHOME/tex/latex} ou dans un sous-répertoire de ceux-ci. + +Enfin, si les ajouts ont été faits sous \envname{TEXMFLOCAL}, il y a lieu de +régénérer les bases de données \filename{ls-R} (commande \cmdname{mktexlsr} +ou bouton « Reinit file database » du programme \prog{tlmgr} +en mode graphique). + +L'emplacement des répertoires \envname{TEXMFLOCAL} et \envname{TEXMFHOME} est +fixe (il ne change pas d'une version à l'autre de \TL{}). Leur contenu est +pris en compte par toutes les versions de \TL{} aussi est-il préférable de ne +pas changer la valeur des variables \envname{TEXMFLOCAL} et \envname{TEXMFHOME} +à l'installation. + + +\subsubsection{Ajout de fontes externes à \TL{}} + +Cette question est malheureusement trop complexe pour être abordée ici. +Renoncez-y sauf si connaissez bien les arcanes d'une installation \TeX. +Vérifiez en premier lieu ce qui existe déjà en libre : voir la +section~\ref{sec:tl-fonts}. + +Une alternative possible est d'utiliser \XeTeX (voir +section~\ref{sec:tex-extensions}) qui permet l'accès aux fontes disponibles +sur le système sans aucune installation supplémentaire. + + +\subsection{Tester l'installation} +\label{sec:test-install} + +Une fois l'installation de \TL{} terminée, il faut la tester avant de créer +des documents ou des fontes. Les tests doivent être faits par un utilisateur +non privilégié (autre que \textit{root}). + +On donne ici quelques procédures de base pour vérifier que le nouveau +système est opérationnel. On les décrit pour Unix ; pour \MacOSX{} ou +Windows, il vaut mieux tester au travers d'une interface graphique +mais les principes sont les mêmes. + +\begin{enumerate} + +\item S'assurer en premier lieu que le programme \cmdname{tex} fonctionne : + +\begin{alltt} +> \Ucom{tex -{}-version} +TeX 3.1415926 (Web2C 7.5.7) +kpathsea version 3.5.7 +... +\end{alltt} + +Si la réponse est \texttt{command not found} ou si le numéro de version est +différent, il est fort probable que vous n'avez pas le bon répertoire +de binaires dans votre \envname{PATH}. +Voir les informations sur l'environnement page~\pageref{sec:env}. + +\item Traiter un fichier \LaTeX{} simple : + +\begin{alltt} +> \Ucom{latex sample2e.tex} +This is pdfeTeXk, Version 3.1415926... +... +Output written on sample2e.dvi (3 pages, 7484 bytes). +Transcript written on sample2e.log. +\end{alltt} +Si le fichier \filename{sample2e.tex} ou d'autres ne sont pas trouvés, +il y a probablement des interférences avec vos anciennes variables +d'environnement ou fichiers de configuration. Pour analyser en détail +votre problème, vous pouvez demander à \TeX{} de dire exactement ce +qu'il cherche et trouve ; voir la section~\ref{sec:debugging} +page~\pageref{sec:debugging}. + +\item Prévisualiser les résultats en ligne : +\begin{alltt} +> \Ucom{xdvi sample2e.dvi} +\end{alltt} +Sous Windows, la commande équivalente est \cmdname{dviout}. +Une nouvelle fenêtre doit s'ouvrir et montrer un joli document expliquant les +bases de \LaTeX{} (document dont la lecture attentive est recommandée si vous +êtes débutant !). +Vous devez travailler sous X pour que \cmdname{xdvi} fonctionne. Sinon, votre +variable d'environnement \envname{DISPLAY} n'est pas correcte et vous +aurez une erreur \samp{Can't open display}. + +\item Créer un fichier \PS{} pour l'imprimer ou l'afficher : + +\begin{alltt} +> \Ucom{dvips sample2e.dvi -o sample2e.ps} +\end{alltt} + +\item Créer un fichier \acro{PDF} au lieu de \dvi{} ; +cet exemple traite le fichier \filename{sample2e.tex} et crée directement +du \acro{PDF} : + +\begin{alltt} +> \Ucom{pdflatex sample2e.tex} +\end{alltt} + +\item Prévisualiser le fichier \acro{PDF} : + +\begin{alltt} +> \Ucom{gv sample2e.pdf} +\textrm{ou} +> \Ucom{xpdf sample2e.pdf} +\end{alltt} + +Hélas, ni \cmdname{gv} ni \cmdname{xpdf} ne sont actuellement inclus dans +\TL{}, aussi devez-vous les installer séparément si ce n'est déjà fait. +Voir respectivement +\url{http://www.gnu.org/software/gv} et +\url{http://www.foolabs.com/xpdf} (il y a bien d'autres lecteurs de +fichiers \acro{PDF}). + +\item Autres fichiers de tests utiles en plus de \filename{sample2e.tex} : + +\begin{ttdescription} + +\item [small2e.tex] à compiler avant \filename{sample2e} si celui-ci pose des + problèmes. + +\item [testpage.tex] teste que l'imprimante n'introduit pas de décalages. + +\item [nfssfont.tex] imprime des tables des fontes et des tests. +\item [testfont.tex] aussi pour les tables de fontes mais en (plain)\TeX. +\item [story.tex] le fichier de test de (plain)\TeX{} le plus canonique +de tous. Il faut taper \samp{\bs bye} à la commande \code{*} après +\samp{tex story.tex}. + +\end{ttdescription} +Pour exécuter ces tests procéder comme pour \filename{sample2e.tex}. + +\end{enumerate} + +Si vous êtes débutant ou si vous avez besoin d'aide pour réaliser des +documents \TeX{} ou \LaTeX{}, n'hésitez pas à consulter +\url{http://tug.org/begin.html}. +On vous recommande également l'introduction à \LaTeX{} de Tobias Oetiker +dans sa version anglaise (la version française n'est plus à jour) +disponible après installation sous +\url{texmf-doc/doc/english/lshort-english/lshort.pdf}. + +\section{Utilisation de \TL{} en réseau} +\label{sec:netinstall} + +\TL{} a été conçu comme un système multi-utilisateurs capable de fonctionner +en réseau. Un même serveur peut proposer la distribution \TL{} à différentes +machines, éventuellement d'architectures différentes, il suffit que le serveur +possède les répertoires de binaires adéquats. + +La seule chose à faire par chaque utilisateur local ou distant est d'ajouter +le chemin des exécutables correspondant à son architecture dans son +\envname{PATH}% +\footnote{Plus précisément \emph{en tête} du \envname{PATH} s'il y a d'autres + binaires \TeX{} en concurrence.}. + +Ceci fonctionne parce que les répertoires de recherche des fichiers utilisés +par \TL{} (\envname{TEXMFMAIN}, \envname{TEXMFDIST}, \envname{TEXMFSYSVAR}, +\envname{TEXMFSYSCONFIG} et \envname{TEXMFLOCAL} sont définis +\emph{relativement aux exécutables} lors de l'installation (voir dans le fichier +\filename{TEXMFMAIN/web2c/texmf.cnf} le rôle de la variable +\envname{\$SELFAUTOPARENT}). %$ + +Cette disposition permet aussi de faire une installation sur une machine et +de la déplacer après coup sur un serveur, la seule chose à changer est le +contenu de la variable \envname{PATH}. + +Ce qui précède vaut pour les utilisateurs d'Unix. +Pour ceux qui sont sous Windows, le répertoire +\dirname{texmf-doc/source/texlive/texlive-common/w32client} +contient un exemple de script \filename{install-w32client} qui permet +de partager une installation \TL{} à travers un réseau local. Il se lance +par l'intermédiaire du fichier « batch » +\filename{install-w32client.bat} qui se trouve dans le même répertoire. + +De plus amples informations sur la configuration de \TL{} et sur la recherche +de fichiers sont disponibles à la section~\ref{sec:kpathsea}. + +\section{\TL{} sur une machine hôte (DVD ou USB)} +\label{sec:portable-unix} + +L'utilisation de \TL{} à partir du \DVD{} décrite à la +section~\ref{sec:fromdvd} impose la création de quelques répertoires sur le +disque dur, ce qui n'est pas gênant sur une machine personnelle. En revanche, +lorsqu'on travaille sur une machine hôte, il est préférable de limiter les +ajouts et modifications à faire sur le disque dur. + +Les scripts \filename{tl-portable} (pour Unix) et \filename{tl-portable.bat} +pour Windows, présents à la racine de \TL{} (ou dans le répertoire +\dirname{texlive} du \DVD \TK) facilitent l'utilisation de \TL{} sur des +machines hôtes. Lors de leur première exécution, ces scripts créent un +répertoire \dirname{~/.tlportable2008} contenant divers fichiers de +configuration qui permettront l'accès à la distribution \TL{} du \DVD. +Ceci peut prendre un peu de temps mais lors des exécutions +suivantes le démarrage est presque immédiat. Rien n'est modifié sur la machine +en dehors du répertoire \dirname{~/.tlportable2008}. + +Pour qu'un éditeur prenne en compte la distribution \TL{} du \DVD, il suffit +de le lancer par l'intermédiaire du script \filename{tl-portable}. + +Le script \filename{tl-portable} est utile aussi pour créer une distribution +\TL{} sur une clé \acro{USB}. Pour ce faire, copier sur la clé les fichiers +et les répertoires situés à la racine de \TL{} (au moins \dirname{bin}, +\dirname{texmf}, \dirname{texmf-dist} et \dirname{tlpkg}). Si la clé est +formatée en \acro{FAT32}, attention aux liens symboliques (utiliser \code{cp + -L} pour copier). Il est possible d'ajouter un répertoire +\dirname{texmf-local} sur la clé, il sera pris en compte à l'exécution. Il +reste à lancer le script \filename{tl-portable} à la racine de la clé comme +ci-dessus ; celle-ci étant accessible en écriture, lors des exécutions de \TL{} +tous les fichiers seront créés sur elle et rien ne sera écrit sur le +disque dur. + +\section{Maintenance de l'installation avec \cmdname{tlmgr}} +\label{sec:tlmgr} + +\begin{figure}[tb] +\centering +\tlpng{tlmgr-gui}{\linewidth} +\caption{\prog{tlmgr} en mode graphique (après clic sur le bouton « Load »).}% +\label{fig:tlmgr-gui} +\end{figure} + +\begin{figure}[tb] +\centering +\tlpng{tlmgr-config}{\linewidth} +\caption{\texttt{tlmgr} en mode graphique, onglet « configuration »}% +\label{fig:tlmgr-config} +\end{figure} + +Un nouveau programme appelé \prog{tlmgr} est installé avec la +distribution \TL. Il fournit une interface conviviale pour la +maintenance de la distribution. Les programmes \prog{updmap}, +\prog{fmtutil} et \prog{texconfig} ont été conservés et le seront à +l'avenir bien que \prog{tlmgr} soit appelé à devenir l'interface +standard de configuration. +\prog{tlmgr} permet en particulier +\begin{itemize} +\item de voir la liste de toutes les collections et extensions + disponibles, avec la mention \texttt{(i)} pour celles qui sont installées ; +\item d'installer, de mettre à jour ou de désinstaller tel ou tel composant, + en respectant les dépendances (sauf si l'utilisateur le refuse) ; +\item de rechercher des extensions ; +\item de voir la liste des binaires disponibles et d'en installer ; +\item de modifier la configuration (taille du papier, choix du + répertoire source pour le téléchargement voir option \texttt{-location} + page~\pageref{item:location}, etc.). +\end{itemize} +\textit{Attention :} \prog{tlmgr} ne doit pas être utilisé lorsque \TL{} est +exécuté à partir du \DVD{} (sans installation sur le disque dur). + +\subsection{\cmdname{tlmgr} en mode graphique} + +\prog{tlmgr} est lancé en mode graphique par la commande +\begin{alltt} +> \Ucom{tlmgr -gui} +\end{alltt} +ou sous Windows dans le menu « Démarrer » : \texttt{Démarrer} $\rightarrow$ +\texttt{Programmes} $\rightarrow$ \texttt{TeX Live 2008} $\rightarrow$ +\texttt{TeX Live Manager}. + +La première chose à faire est de cliquer sur le bouton « Load% +\footnote{Dans la description qui suit, le nom des boutons est celui de la + version anglaise par souci de cohérence avec les figures. L'affichage se + fait normalement dans la langue de l'utilisateur (variable \envname{LANG} + sous Unix).} » ce qui affiche la liste des collections, extensions, etc. ; +le préfixe \texttt{(i)} indique celles qui sont déjà installées. + +La figure~\ref{fig:tlmgr-config} présente l'onglet « configuration ». + +\subsection{Exemples d'utilisation de \cmdname{tlmgr} + en ligne de commande} + +Premier exemple : ajout de la collection « xetex » et de l'extension « xkeyval » +qui devront être téléchargées à partir d'un site spécifié. La commande + +\begin{alltt} +> \Ucom{tlmgr -location http://172.16.18.1/tldev install collection-xetex xkeyval} +\end{alltt} +retourne +\begin{fverbatim} +install: collection-xetex +install: arabxetex +install: euenc +install: bidi +install: fontspec +install: fontwrap +install: ifxetex +install: philokalia +install: polyglossia +install: xecyr +install: xecyr.i386-linux +install: xepersian +install: xetex +install: xetexconfig +install: xetex.i386-linux +running post install action for xetex +install: xetex-def +install: xetex-pstricks +install: xetexfontinfo +install: xltxtra +install: xunicode +install: xkeyval +running mktexlsr +mktexlsr: Updating /usr/local/texlive/2008/texmf/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-config/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-dist/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-doc/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/../texmf-local/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-var/ls-R... +mktexlsr: Done. +regenerating fmtutil.cnf +running fmtutil-sys --missing +... +Transcript written on xelatex.log. +fmtutil: /usr/local/texlive/2008/texmf-var/web2c/xetex/xelatex.fmt installed. +\end{fverbatim} +Le programme \prog{tlmgr} prend en compte les dépendances et effectue +automatiquement toutes les opérations nécessaires comme la mise à jour des +bases de données et la génération de formats (ici un nouveau format a été créé +pour \XeTeX). + +Deuxième exemple : ajout d'une langue de travail (néerlandais) ; ceci provoque +la régénération de plusieurs formats. +\begin{alltt} +> \Ucom{tlmgr install collection-langdutch} +\end{alltt} + +La demande de description de l'extension « collection-wintools » +\begin{alltt} +> \Ucom{tlmgr show collection-wintools} +\end{alltt} +retourne +\begin{fverbatim} +Package: collection-wintools +Category: Collection +ShortDesc: Windows support programs +LongDesc: Utilities for Windows, since they are not readily available there: + gzip, chktex, jpeg2ps, unzip, wget, xpdf. +Installed: Yes +\end{fverbatim} + +Mise à jour complète de l'installation avec les dernières versions disponibles : +\begin{alltt} +> \Ucom{tlmgr update -all} +\end{alltt} +ou juste pour voir ce qui se passerait en cas de mise à jour complète : +\begin{alltt} +> \Ucom{tlmgr update -all -dry-run} +\end{alltt} +ou bien +\begin{alltt} +> \Ucom{tlmgr update -list} +\end{alltt} + +Documentation complète de \prog{tlmgr} : +\begin{alltt} +> \Ucom{tlmgr -help} +\end{alltt} + +\section{Spécificités Windows} +\label{sec:windows} + +Le nouveau programme d'installation de \TL{} est conçu pour +fonctionner aussi bien sous Unix que sous Windows. Ceci nous a +obligés à nous limiter à Windows 2000 et à ses successeurs (XP, Vista), +au détriment des anciennes versions (9\textit{x}, ME et NT). + +\subsection{Installation} +\label{sec:winfeatures} + +Sous Windows le programme d'installation effectue quelques tâches +supplémentaires : +\begin{description} +\item[Menus et raccourcis] -- un sous-menu «\TL{}» est ajouté au menu + « Démarrer », il contient des entrées pour les programmes \prog{tlmgr}, + \prog{texdoctk}, PS\_View et pour de la documentation. + Une icône PS\_View est ajoutée sur le bureau, il suffit d'y déposer un + fichier PostScript pour provoquer son affichage. +\item[Variables d'environnement] -- leurs valeurs sont préremplies + automatiquement sans intervention de l'utilisateur. +\item[Désinstallation] -- une entrée est ajoutée pour \TL{} dans le menu + « Ajout et suppression de programmes ». +\end{description} + +\subsection{Programmes supplémentaires} + +\begin{figure}[tb] +\centering +\tlpng{psview}{.6\linewidth} +\caption{PS\_View: de très forts grossissements sont possibles !}% +\label{fig:psview} +\end{figure} + +L'installation de \TL{} ajoute quelques utilitaires non fournis en standard +avec Windows : +\begin{description} +\item[Perl et Ghostscript] -- \TL{} installe des copies « cachées » de ces + programmes : ce sont des versions spécifiques adaptées à \TL{}, elles + sont invisibles hors de \TL{} et n'interfèrent donc en aucune façon avec + d'autres versions éventuellement présentes sur la machine. +\item[Outils en ligne de commande] -- des versions pour Windows de programmes + Unix sont installées, en particulier \cmdname{gzip}, \cmdname{chktex}, + \cmdname{jpeg2ps}, \cmdname{unzip}, \cmdname{wget} et quelques utilitaires + de la suite \cmdname{xpdf} (\cmdname{xpdf} lui-même n'est pas disponible + sous Windows mais le visualiseur \acro{PDF} Sumatra en est dérivé, voir + \url{http://blog.kowalczyk.info/software/sumatrapdf}). +\item[\texttt{fc-cache}] -- facilite l'accès aux fontes système pour \XeTeX. +\item[PS\_View] -- nouveau visualiseur PostScript sous licence libre, + voir figure~\ref{fig:psview}. +\item[Répertoire \texttt{support}] -- ce répertoire, déjà mentionné à la + section~\ref{sec:tld}, contient divers programmes éventuellement utiles + comme des éditeurs adaptés aux fichiers \TeX{} ou le visualiseur Dviout + présenté à la section suivante. Ces programmes ne sont + pas installés automatiquement par la commande \prog{install-tl}. +\end{description} + +\subsection{Visualiseur Dviout} + +Cette année, la distribution \TL{} ne contient malheureusement pas de +visualiseur \dvi{} pour Windows. Le programme \prog{dviout} de +Toshio Oshima est disponible dans le répertoire \path{support/dviout/}, il est +accompagné d'un fichier \filename{README} (à lire attentivement) décrivant +l'installation et la configuration de \prog{dviout} pour \TL. + +Lors des premières exécutions de \cmdname{dviout}, de nombreuses fontes sont +créées à la volée pour l'écran utilisé. Ceci prend un peu de temps mais se +produit de plus en plus rarement au fur et à mesure des utilisations. +Une bonne aide en ligne est disponible. + +\subsection{Téléchargement de logiciels supplémentaires} + +Voici quelques liens vers des sites proposant des outils intéressants : +\begin{description} +\item[Ghostscript] -- \url{http://www.cs.wisc.edu/~ghost/} ; +\item[Perl] -- \url{http://www.activestate.com/} et \acro{CPAN} + \url{http://www.cpan.org/} ; +\item[ImageMagick] -- \url{http://www.imagemagick.com} pour l'affichage et la + conversion d'images ; +\item[NetPBM] -- \url{http://netpbm.sourceforge.net/} un concurrent du + précédent ; +\item[Éditeurs orientés \TeX] -- le choix est large, en voici une sélection : + \begin{itemize} +% \item \cmdname{GNU Emacs} disponible sous Windows, see +% \url{http://www.gnu.org/software/emacs/windows/ntemacs.html} ; + \item \cmdname{Emacs} avec Auc\TeX\ pour Windows disponible dans le + répertoire \path{support} de \TL{} ; le site de référence est + \url{http://www.gnu.org/software/auctex} ; + \item \cmdname{WinShell} disponible également dans le répertoire + \path{support} ; le site de référence est \url{http://www.winshell.de} ; + \item \cmdname{WinEdt} est un \textit{shareware}, voir + \url{http://www.winedt.com} ; + \item TeXnicCenter est libre, il est disponible sur + \url{http://www.toolscenter.org} et dans la distribution \ProTeXt{} ; + \item \cmdname{Vim} est libre, voir \url{http://www.vim.org} ; + \item \cmdname{LEd} voir \url{http://www.ctan.org/support/LEd} ; + \item \cmdname{SciTE} voir + \url{http://www.scintilla.org/SciTE.html}. + \end{itemize} +\end{description} + + +\subsection{Répertoire personnel} +\label{sec:winhome} + +L'équivalent du répertoire personnel noté \envname{\$HOME} sous +Unix s'appelle \verb|%USERPROFILE%| sous Windows. % +Cette variable vaut en général +\verb|C:\Documents and Settings\| sous Windows XP et 2000 +et \verb|C:\Utilisateurs\| sous Vista. +La notation \verb|~|, utilisée dans \filename{texmf.cnf} et dans \KPS{} en +général pour désigner un répertoire personnel, est correctement interprétée +sous Windows comme sous Unix. + + +\subsection{Base de registre Windows} +\label{sec:registry} + +% (df) Je ne vois pas bien l'utilité de cette section... + +Windows stocke pratiquement tous les paramètres de configuration dans sa base +de registres. Celle-ci contient un ensemble de clés organisées par niveau. +Les clés les plus importantes pour l'installation de programmes sont +\path{HKEY_CURRENT_USER} et \path{HKEY_LOCAL_MACHINE}, \path{HKCU} et +\path{HKLM} en abrégé. La partie \path{HKCU} de la base de registres +se trouve dans le répertoire personnel de l'utilisateur (voir +section~\ref{sec:winhome}). La partie \path{HKLM} est normalement dans un +sous-répertoire du répertoire Windows. + +Certaines informations système peuvent s'obtenir à partir des variables +d'environnement mais pour d'autres, la localisation des raccourcis par +exemple, la consultation de la base de registre est indispensable. +La modification des variables d'environnement nécessite l'accès à la base de +registre. + + +\subsection{Droits d'accès sous Windows} +\label{sec:winpermissions} + +Dans les versions récentes de Windows, la distinction est faite entre +« utilisateurs » et « administrateurs », ces derniers ayant accès en écriture +à la totalité du système. En pratique on devrait plutôt parler d'utilisateurs +« non privilégiés » et d'utilisateurs « normaux » car être « administrateur » +est la règle et non l'exception. + +Nous nous sommes efforcés de rendre l'installation de \TL{} possible aux +utilisateurs non privilégiés. + +Si celui qui fait l'installation est « administrateur », les raccourcis +et les entrées des menus sont créés pour tous les utilisateurs ; +sinon, seul celui qui a fait l'installation aura accès à ces éléments. +L'option \optname{non-admin} du programme \prog{install-tl} permet à un +« administrateur » de faire une installation comme utilisateur non privilégié. + +Dans tous les cas, le répertoire proposé comme racine de l'installation est +\verb|%PROGRAMFILES%|. % +Le programme \prog{install-tl} vérifie si le répertoire choisi comme racine +est accessible en écriture pour celui qui procède à l'installation. + +Lorsqu'une installation \TeX{} est présente sur la machine, l'installation +de \TL{} par un utilisateur non privilégié est problématique : +cet utilisateur n'aura jamais accès aux exécutables \TL{} car la recherche +s'effectue d'abord dans les répertoires système, puis dans les répertoires de +l'utilisateur. Une parade sommaire a été prévue : les raccourcis intègrent +dans ce cas le chemin complet des exécutables qu'ils représentent. La +distribution \TL{} est ainsi utilisable en ligne de commande à partir de ces +raccourcis. + + +\section{Guide d'utilisation du système Web2C} + +\Webc{} est une collection intégrée de programmes relatifs à \TeX, +c.-à-d. \TeX{} lui-même, \MF{}, \MP, \BibTeX{}, etc. +C'est le cÅ“ur de \TL{}. Le site de référence est \url{http://tug.org/web2c}. + +Un peu d'histoire : la première implémentation a été réalisée par Tomas +Rokicki qui, en 1987, a développé un premier système \TeX{}-to-C en adaptant +les \textit{change files} pour Unix (travail de Howard Trickey et Pavel Curtis +principalement). Tim Morgan assura la maintenance du système, dont le nom fut +remplacé durant cette période par Web-to-C. En 1990, Karl Berry reprit le +travail, assisté par des dizaines de contributeurs et en 1997 il passa le +relais à Olaf Weber qui le rendit à Karl en 2006. + +Le système \Webc{} fonctionne sur Unix, sur les systèmes Windows 32 bits, +sur \MacOSX{} et sur de nombreux autres systèmes d'exploitation. Il utilise les +sources originales de Knuth pour \TeX{} et les autres programmes de base +écrits en \web{} (système de programmation documentée) qui sont tous traduits +en langage C. Les composants du noyau de \TeX{} issus de ce processus sont : + +\begin{description} +\item[bibtex] -- gère les bibliographies. +\item[dmp] -- \cmdname{troff} vers MPX (dessins \MP{}). +\item[dvicopy] -- copie le fichier \dvi{} en supprimant les fontes virtuelles. +\item[dvitomp] -- convertit le fichier \dvi{} en MPX (dessins \MP{}). +\item[dvitype] -- convertit le fichier \dvi{} en un texte lisible. +\item[gftodvi] -- visualisation de fontes génériques GF. +\item[gftopk] -- convertit les fontes génériques GF en fontes bitmap PK. +\item[gftype] -- convertit le fichier GF en un texte lisible. +\item[makempx] -- typographie des étiquettes \MP{}. +\item[mf] -- création de fontes. +\item[mft] -- mise en page de code source \MF{}. +\item[mpost] -- création de diagrammes techniques. +\item[mpto] -- extraction d'étiquettes \MP{}. +\item[newer] -- comparaison de dates de modification (fichiers). +\item[patgen] -- création de motifs de césure. +\item[pktogf] -- convertit les fontes bitmap PK en fontes génériques GF. +\item[pktype] -- convertit les fontes PK en un texte lisible. +\item[pltotf] -- convertit les fichiers PL (lisibles) en TFM. +\item[pooltype] -- affiche les fichiers \web{} pool. +\item[tangle] -- \web{} vers Pascal. +\item[tex] -- composition de textes. +\item[tftopl] -- convertit les fichiers TFM en PL (lisibles). +\item[vftovp] -- convertit les fontes virtuelles VF en VPL (lisibles). +\item[vptovf] -- convertit les fontes VPL en fontes virtuelles VF. +\item[weave] -- \web{} vers \TeX. +\end{description} + +La syntaxe et les fonctions précises de ces programmes sont décrites dans +la documentation des composants individuels et dans le manuel \Webc{} +lui-même. Toutefois, connaître un certain nombre de principes régissant +l'ensemble de la famille de programmes peut aider à exploiter de façon +optimale votre installation \Webc{}. + + Presque tous ces programmes suivent les options standard de \GNU : +\begin{description} + \item[\texttt{-{}-help}] imprime le sommaire de l'utilisation, + \item[\texttt{-{}-verbose}] imprime le rapport détaillé du processus, + \item[\texttt{-{}-version}] imprime seulement le numéro de version. +\end{description} + +Pour localiser les fichiers, les programmes \Webc{} utilisent la bibliothèque +de recherche \KPS{} (\url{http://tug.org/kpathsea}). Cette bibliothèque +utilise une combinaison de variables d'environnement et un certain nombre de +fichiers de paramètres pour optimiser la recherche dans l'énorme arborescence +\TeX{}. \Webc{} peut exécuter une recherche dans plusieurs arborescences +simultanément, ce qui est utile si l'on souhaite maintenir la distribution +standard de \TeX{} et les extensions locales dans deux arborescences +distinctes. Afin d'accélérer la recherche de fichiers, la racine de chaque +arborescence possède un fichier \file{ls-R} contenant une entrée donnant le +nom et le chemin de chaque fichier situé sous la racine. + +\subsection{Kpathsea et la recherche de fichiers} +\label{sec:kpathsea} + +Décrivons en premier lieu le mécanisme de recherche de la bibliothèque \KPS{}. + +Nous appelons \emph{chemin de recherche} une liste, séparée par +« deux-points» ou « point-virgule», d'éléments, appelés +\emph{éléments de chemin}, qui sont des noms de répertoires. +Un chemin de recherche peut provenir de plusieurs sources. +Pour rechercher un fichier \samp{my-file} le long +d'un chemin \samp{.:/dir}, \KPS{} vérifie chaque élément du chemin : +d'abord \filename{./my-file}, puis \filename{/dir/my-file} et renvoie la +première occurrence (voire toutes). + +Afin d'optimiser l'adaptation à tous les systèmes d'exploitation, \KPS{} peut +utiliser dans les noms de fichiers des séparateurs différents de deux-points +(\samp{:}) et barre oblique (\samp{/}) pour les systèmes non-Unix. + +Pour vérifier un élément de chemin particulier \var{p}, \KPS{} +vérifie d'abord si une base de données existante (voir +page~\pageref{sec:filename-database}) contient \var{p}, +c.-à-d. si la base de données se trouve dans un +répertoire qui est un préfixe de \var{p}. Si oui, la spécification +du chemin est comparée avec le contenu de la base de données. + +Si la base de données n'existe pas, si elle ne s'applique pas à cet élément de +chemin ou si elle ne contient aucune correspondance, la recherche est lancée +sur tout le système de fichiers (si cela n'a pas été interdit par une commande +commençant par \samp{!!} et si le fichier cherché est censé exister). \KPS{} +construit la liste de répertoires qui correspondent à cet élément de chemin, +puis cherche le fichier dans chaque élément de cette liste. + +La condition « le fichier est censé exister » est liée aux fichiers~\samp{.vf} +et aux fichiers d'entrée lus par la commande \TeX\ \cs{openin}. De tels +fichiers peuvent ne pas exister (par exemple \file{cmr10.vf}), il est donc +inutile de les rechercher sur le disque. De plus, si vous n'actualisez pas le +fichier \file{ls-R} lors de l'installation d'un nouveau fichier \samp{.vf}, il +ne sera jamais trouvé. Chaque élément de chemin est alors vérifié : d'abord +dans la base de données puis sur le disque. Si une occurrence est trouvée, la +recherche s'arrête et le résultat est obtenu. + +Bien que l'élément de chemin le plus simple et le plus fréquent soit un nom de +répertoire, \KPS{} supporte d'autres types d'éléments dans les chemins de +recherche : des valeurs par défaut différentes pour chaque programme, des noms +de variables d'environnement, des valeurs de fichiers de configuration, les +répertoires de l'utilisateur et la recherche récursive de +sous-répertoires. Nous disons alors que \KPS{} \emph{étend} un élément, +c'est-à-dire que \KPS{} transforme toutes ces spécifications en noms de +répertoires de base. Cette opération est décrite dans les sections suivantes. + +Notons que si le nom de fichier cherché est absolu ou explicitement +relatif, c'est-à-dire commençant par \samp{/}, \samp{./} ou +\samp{../}, \KPS{} ne vérifie que l'existence de ce fichier. +\ifSingleColumn +\else +\begin{figure*} +\centering +\verbatiminput{examples/ex5.tex} +\setlength{\abovecaptionskip}{0pt} + \caption{Un exemple de fichier de configuration} + \label{fig:config-sample} +\end{figure*} +\fi + +\subsubsection{Les différentes sources} +\label{sec:path-sources} + +Un chemin de recherche peut provenir de plusieurs sources. Voici l'ordre +dans lequel \KPS\ les utilise. + +\begin{enumerate} +\item Une variable d'environnement définie par l'utilisateur, par exemple + \envname{TEXINPUTS}. Les variables d'environnement avec une extension + attachée (nom de programme) sont d'abord prises en compte : par exemple, si + \samp{latex} est le nom du programme exécuté, \envname{TEXINPUTS.latex} + passera avant \envname{TEXINPUTS}. +\item Un fichier de configuration de programme spécifique, par exemple une + ligne « \texttt{S /a:/b} » dans le fichier \file{config.ps} de + \cmdname{dvips}. +\item Un fichier de configuration \file{texmf.cnf} de \KPS{} contenant une + ligne telle que \\ \samp{TEXINPUTS=/c:/d} (voir ci-dessous). +\item La valeur par défaut obtenue à la compilation. +\end{enumerate} +\noindent On peut voir chacune de ces valeurs pour un chemin de recherche +donné en utilisant l'option de débogage (voir page~\pageref{sec:debugging}). + +\subsubsection{Fichiers de configuration} + +\begingroup\tolerance=3500 +\KPS{} lit dans les \emph{fichiers de configuration à + l'exécution} appelés \file{texmf.cnf} les chemins de recherche et +d'autres définitions. Le chemin pour accéder à ces fichiers dans +l'arborescence est stocké dans la variable \envname{TEXMFCNF} +(par défaut ces +fichiers se trouvent dans le sous-répertoire \file{texmf/web2c}). +\emph{Tous} les fichiers \file{texmf.cnf} se trouvant dans le chemin +de recherche vont être lus et les définitions provenant +de fichiers précédents écraseront celles des fichiers suivants. Par +exemple, avec un chemin tel que \verb|.:$TEXMF|, les définitions du +fichier \filename{./texmf.cnf} écrasent celles de +\verb|$TEXMF/texmf.cnf|. +\endgroup + +\begin{itemize} +\item Les commentaires sont signalés par un \texttt{\%} et se terminent à la + fin de la ligne. +\item Les lignes vides sont ignorées. +\item Un \bs{} à la fin d'une ligne joue le rôle d'un lien entre deux lignes, + c'est-à-dire que la ligne courante se poursuit à la ligne suivante. Dans ce + cas, les espaces présents au début de la ligne suivante ne sont pas ignorés. +\item Toutes les autres lignes sont de la forme : +\begin{alltt} + \emph{variable}[.\emph{progname}] [=] \emph{value} +\end{alltt}% + où le \samp{=} et les espaces autour sont optionnels. +\item Le nom de la \ttvar{variable} peut contenir n'importe quel caractère + autre que les espaces, \samp{=}, ou \samp{.} mais on recommande d'utiliser + \samp{A-Za-z\_} pour éviter les problèmes. +\item Si \samp{.\var{progname}} est présent, sa définition s'applique + seulement si le programme exécuté se nomme \texttt{\var{progname}} ou + \texttt{\var{progname}.exe}. Ceci permet par exemple à différentes variantes + de \TeX{} d'avoir des chemins de recherche différents. +\item \var{value} peut contenir n'importe quel caractère excepté \code{\%} et + \samp{@}. L'option \code{\$\var{var}.\var{prog}} n'est pas disponible à + droite du signe \samp{=} ; à la place, on doit utiliser une variable + supplémentaire. Un \samp{;}\ dans \var{value} est compris comme un \samp{:}\ + si on travaille sous Unix ; ceci est très utile et permet d'avoir un seul + \file{texmf.cnf} pour les systèmes Unix, \acro{MS-DOS} et Windows. +\item Toutes les définitions sont lues avant tout désarchivage ou + décompactage, de telle façon que les variables peuvent être référencées + avant d'être définies. +\end{itemize} +Voici un fichier de configuration illustrant les points précédents +\ifSingleColumn + +%\verbatiminput{examples/ex5.tex} % trop petit (df) +\begin{verbatim} +TEXMF = {$TEXMFLOCAL,!!$TEXMFMAIN} +TEXINPUTS.latex = .;$TEXMF/tex/{latex,generic;}// +TEXINPUTS.fontinst = .;$TEXMF/tex//;$TEXMF/fonts/afm// +% e-TeX related files +TEXINPUTS.elatex = .;$TEXMF/{etex,tex}/{latex,generic;}// +TEXINPUTS.etex = .;$TEXMF/{etex,tex}/{eplain,plain,generic;}// +\end{verbatim} + +\else +dans la figure~\ref{fig:config-sample}. +\fi + +\subsubsection{Expansion d'un chemin de recherche} +\label{sec:path-expansion} + +\KPS{} reconnaît certains caractères et constructions spéciales dans +les chemins de recherche, semblables à ceux disponibles dans les +\textit{shells} Unix. Ainsi, le chemin complexe, +\verb+~$USER/{foo,bar}//baz+ %$ +étend la recherche vers tous les sous-répertoires situés sous les +répertoires \file{foo} et \file{bar} dans le répertoire utilisateur +\texttt{\$USER} contenant un répertoire ou un fichier appelé %$ +\file{baz}. Ces expansions sont explicitées dans les sections +suivantes. + +\subsubsection{Expansion par défaut} +\label{sec:default-expansion} + +\tolerance=2500 +Si le chemin de recherche le plus prioritaire (voir +section~\ref{sec:path-sources}) contient un \samp{:} +\emph{supplémentaire} (c.-à-d. en début ou fin de ligne ou +double), \KPS{} insère à cet endroit le chemin suivant dont la +priorité définie est immédiatement inférieure. Si ce chemin inséré +possède un \samp{:} supplémentaire, le même processus se +répète pour le chemin prioritaire suivant. +Par exemple, étant donné une variable d'environnement définie ainsi + +\tolerance=1500 + +\begin{alltt} +> \Ucom{setenv TEXINPUTS /home/karl:} +\end{alltt} +la valeur de \code{TEXINPUTS} d'après le fichier \file{texmf.cnf} étant + +\begin{alltt} + .:\$TEXMF//tex +\end{alltt} +alors la valeur finale utilisée pour la recherche sera + +\begin{alltt} + /home/karl:.:\$TEXMF//tex +\end{alltt} + +Comme il est inutile d'insérer la valeur par défaut en plusieurs +endroits, \KPS{} applique la substitution à seulement un \samp{:} +supplémentaire et laisse les autres inchangés : il cherche d'abord un +\samp{:} en début de ligne, puis en fin de ligne et enfin un double +\samp{:}. + +\subsubsection{Expansion spécifiée par les accolades} + +Option utile, l'expansion par le biais des accolades +signifie, par exemple, que \verb+v{a,b}w+ va permettre la recherche +dans \verb+vaw:vbw+. Les définitions emboîtées sont autorisées. Ceci +peut être utilisé pour établir des hiérarchies \TeX{} multiples en +attribuant une liste entre accolades à \code{\$TEXMF}. Par exemple, +dans \file{texmf.cnf}, on trouve une définition du type suivant +(il y a en fait plus de répertoires) : +\begin{verbatim} + TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFSYSVAR,!!$TEXMFMAIN} +\end{verbatim} +Avec ceci, on peut écrire quelque chose comme +\begin{verbatim} + TEXINPUTS = .;$TEXMF/tex// +\end{verbatim} +%$ +ce qui signifie que, après avoir cherché dans le répertoire courant, les +arborescences complètes \code{\$TEXMFHOME/tex} suivie de +\code{\$TEXMFLOCAL/tex} (sur le disque) et ensuite les arborescences +\code{!!\$TEXMFVAR/tex} et \code{!!\$TEXMFMAIN/tex} +(définies dans le fichier de référence \file{ls-R} \emph{seulement}) seront +inspectées. C'est un moyen pratique permettant d'utiliser en parallèle deux +distributions \TeX{}, une « figée » (sur un \CD, par exemple) et une +autre régulièrement mise à jour avec de nouvelles versions quand elles +deviennent disponibles. En utilisant la variable \code{\$TEXMF} dans toutes +les définitions, on est toujours sûr d'inspecter d'abord l'arborescence la +plus récente. + +\subsubsection{Expansion des sous-répertoires} +\label{sec:subdirectory-expansion} + +Deux barres \samp{//} ou plus consécutives dans une partie d'un chemin suivant +un répertoire \var{d} sont remplacées par tous les sous-répertoires de +\var{d} : d'abord les sous-répertoires directement présents dans +\var{d}, ensuite les sous-répertoires de ceux-ci et ainsi de suite. À +chaque niveau, l'ordre dans lequel les répertoires sont inspectés est +\emph{non-déterminé}. + +Dans le cas où l'on spécifie une partie de nom de fichier après le +\samp{//}, seuls sont inclus les sous-répertoires auxquels le nom +correspond. Par exemple, \samp{/a//b} va correspondre aux répertoires +\file{/a/1/b}, \file{/a/2/b}, \file{/a/1/1/b} et ainsi de suite, +mais pas à \file{/a/b/c} ni \file{/a/1}. + +Des \samp{//} multiples et successifs dans un chemin sont possibles, +mais \samp{//} au début d'un chemin est ignoré. + +\subsubsection{Liste des caractères spéciaux et de leur signification : + récapitulatif} + +La liste suivante récapitule la signification des caractères spéciaux +dans les fichiers de configuration de \KPS{}. + +\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} + +\begin{ttdescription} + +\item[\CODE{:}] Séparateur dans un chemin de recherche ; au début + ou à la fin d'un chemin, il remplace le chemin par défaut. + +\item[\CODE{;}] Séparateur dans les systèmes non-Unix + (joue le rôle de \code{:}). + +\item[\CODE{\$}] Substitue le contenu d'une variable. + +\item[\CODE{\string~}] Représente le répertoire racine de + l'utilisateur. + +\item[\CODE{\char`\{...\char`\}}] Expansion par les accolades, + par exemple \verb+a{1,2}b+ devient \verb+a1b:a2b+. + +\item[\CODE{//}] La recherche concernera aussi les sous-répertoires + (peut être inséré n'importe où dans un chemin sauf au début). + +\item[\CODE{\%}] Début d'un commentaire. + +\item[\CODE{\bs}] Caractère de continuation de ligne (permet les + entrées sur plusieurs lignes). + +\item[\CODE{!!}] Cherche \emph{seulement} dans la base de + données pour localiser le fichier et \emph{ne cherche pas} sur le disque. + +\end{ttdescription} + +\subsection{Les bases de données} +\label{sec:filename-database} + +\KPS{} a une certaine profondeur d'investigation pour minimiser les +accès disque durant les recherches. Néanmoins, dans le cas de +distributions comprenant beaucoup de répertoires, inspecter chaque +répertoire possible pour un fichier donné peut durer excessivement +longtemps (ceci est typiquement le cas quand plusieurs centaines de +répertoires de polices de caractères doivent être parcourus). En +conséquence, \KPS{} peut utiliser un fichier texte appelé \file{ls-R} --- en +fait une base de données construite au préalable --- qui fait correspondre +les fichiers à leur répertoire, ce qui permet d'éviter une recherche +exhaustive sur le disque. + +Un deuxième fichier appelé \file{aliases} (qui est également une base de +données) permet de donner des noms différents aux fichiers listés dans +\mbox{\file{ls-R}}. Ceci peut aider à adapter ses fichiers source aux +conventions de \acro{DOS}~8.3 pour les noms de fichiers. + +\subsubsection{Le fichier base de données} +\label{sec:ls-R} + +Comme nous l'avons expliqué ci-dessus, le nom du principal fichier-base de +données doit être \mbox{\file{ls-R}}. +Dans votre installation, vous pouvez en mettre un à la racine de chaque +arborescence \TeX{} que vous désirez voir +inspecter (\code{\$TEXMF} par défaut) ; la plupart des sites ont +une seule arborescence \TeX{}. \KPS{} cherche les fichiers \file{ls-R} +dans le chemin spécifié dans la variable \code{TEXMFDBS}. + +La meilleure façon de créer et mettre à jour le fichier \file{ls-R} +est d'exécuter le script \cmdname{mktexlsr} inclus dans la +distribution. Il est appelé par les divers scripts \cmdname{mktex}\dots\ +En principe, ce script exécute uniquement la commande +%cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R| +% Remplacé (df) car \path|...| plante à cause de \let\path\url. +\begin{alltt} +cd \var{/your/texmf/root} && \boi{}ls -1LAR ./ >ls-R +\end{alltt} +en supposant que la commande \code{ls} de votre système produise le bon +format de sortie (le \code{ls} de \GNU convient +parfaitement). Pour s'assurer que la base de données est toujours à +jour, le meilleur moyen est de la reconstruire en utilisant la table +des \code{cron}, de telle façon que le fichier \file{ls-R} prenne +automatiquement en compte les changements dans les fichiers +installés, par exemple après une installation ou une +mise à jour d'un composant \LaTeX{}. + +Si un fichier n'est pas trouvé dans la base de données, par défaut +\KPS{} décide de le chercher sur le disque. Par contre, si un élément du +chemin commence par \samp{!!}, \emph{seule} la base de données +sera inspectée pour cet élément, jamais le disque. + +\subsubsection{kpsewhich : programme de recherche dans une arborescence} +\label{sec:invoking-kpsewhich} + +Le programme \texttt{kpsewhich} effectue une recherche dans une +arborescence indépendamment de toute application. On peut le +considérer comme une sorte de \code{find} pour localiser des fichiers +dans les arborescences \TeX{} (ceci est largement utilisé dans les +scripts \cmdname{mktex}\dots\ de la distribution). + +\begin{alltt} +> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} +\end{alltt} +Les options spécifiées dans \ttvar{option} peuvent +commencer soit par \samp{-} soit par \samp{-{}-} ; n'importe quelle +abréviation claire est acceptée. + +\KPS{} considère tout argument non optionnel dans la ligne de commande +comme un nom de fichier et renvoie la première occurrence trouvée. Il +n'y a pas d'option pour renvoyer tous les fichiers ayant un nom +particulier (vous pouvez utiliser le \cmdname{find} d'Unix pour cela). + +Les options les plus importantes sont décrites ci-après. + +\begin{ttdescription} +\item[\texttt{-{}-dpi=\var{num}}]\mbox{} \\ + Définit la résolution à \ttvar{num} ; ceci affecte + seulement la recherche des fichiers \samp{gf} et \samp{pk}. \samp{-D} est un + synonyme pour assurer la compatibilité avec \cmdname{dvips}. Le défaut + est 600. +\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ + Définit le format pour la recherche à \ttvar{name}. + Par défaut, le format est estimé en fonction du nom de fichier. + Pour les formats qui n'ont pas de suffixe clair associé, comme les + fichiers de support \MP{} et les fichiers de configuration + \cmdname{dvips}, vous devez spécifier le nom connu de \KPS, comme + \texttt{tex} ou \texttt{enc files}. Exécutez la commande + \texttt{kpsewhich -{}-help} pour obtenir la liste précise. + +\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ + Définit le nom du mode comme étant \ttvar{string} ; +ceci affecte seulement la recherche des \samp{gf} et des \samp{pk}. +Pas d'option par défaut, n'importe quel mode sera trouvé. +\item[\texttt{-{}-must-exist}]\mbox{}\\ + Fait tout ce qui est possible pour trouver les fichiers, ce qui +inclut une recherche sur le disque. Par défaut, seule la base de +données \file{ls-R} est inspectée, dans un souci d'efficacité. +\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ + Recherche dans le chemin \ttvar{string} (séparé par +deux-points comme d'habitude), au lieu de prendre le chemin à partir +du nom de fichier. \samp{//} et toutes les expansions habituelles sont +supportées. + Les options \samp{-{}-path} et \samp{-{}-format} s'excluent mutuellement. +\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ + Définit le nom de programme comme étant \ttvar{name}. + Ceci peut affecter les chemins de recherche via l'option + \texttt{.\var{progname}} dans les fichiers de configuration. + Le défaut est \cmdname{kpsewhich}. +\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ + Montre le chemin utilisé pour la recherche des fichiers de type +\ttvar{name}. + On peut utiliser soit une extension de fichier (\code{.pk}, \code{.vf}, + etc.), soit un nom de fichier, comme avec l'option \samp{-{}-format}. +\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ + Définit les options de débogage comme étant + \ttvar{num}. +\end{ttdescription} + +\subsubsection{Exemples d'utilisation} +\label{sec:examples-of-use} + +Jetons un coup d'Å“il à \KPS{} en action ; voici une recherche +toute simple : + +\begin{alltt} +> \Ucom{kpsewhich article.cls} +/usr/local/texmf-dist/tex/latex/base/article.cls +\end{alltt} +Nous recherchons le fichier \file{article.cls}. Puisque le suffixe +\file{.cls} est non-ambigu, nous n'avons pas besoin de spécifier que +nous voulons rechercher un fichier de type \optname{tex} (répertoires des +fichiers sources de \TeX{}). Nous le trouvons dans le sous-répertoire +\filename{tex/latex/base} du répertoire racine \samp{TEXMF}. De même, + le suffixe non-ambigu permet de trouver facilement les autres fichiers. +\begin{alltt} +> \Ucom{kpsewhich array.sty} + /usr/local/texmf-dist/tex/latex/tools/array.sty +> \Ucom{kpsewhich latin1.def} + /usr/local/texmf-dist/tex/latex/base/latin1.def +> \Ucom{kpsewhich size10.clo} + /usr/local/texmf-dist/tex/latex/base/size10.clo +> \Ucom{kpsewhich small2e.tex} + /usr/local/texmf-dist/tex/latex/base/small2e.tex +> \Ucom{kpsewhich tugboat.bib} + /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib +\end{alltt} + +Le dernier exemple est une base de données bibliographiques pour \BibTeX{} +servant aux articles de \textsl{TUGBoat}. + +\begin{alltt} +> \Ucom{kpsewhich cmr10.pk} +\end{alltt} +Les fichiers de glyphes de fontes bitmaps, de type +\file{.pk}, sont +utilisés pour l'affichage par des programmes comme \cmdname{dvips} et +\cmdname{xdvi}. Rien n'est renvoyé dans ce cas puisque il n'y a pas +de fichiers Computer Modern \file{.pk} pré-créés sur nos systèmes +(nous utilisons les versions type~1 du \TL{}). +\begin{alltt} +> \Ucom{kpsewhich wsuipa10.pk} +\ifSingleColumn + /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk +\else /usr/local/texmf-var/fonts/pk/ljfour/public/ +... wsuipa/wsuipa10.600pk +\fi\end{alltt} +Pour ces fontes (alphabet phonétique de l'université Washington), +nous avons dû créer les fichiers \file{.pk} et, puisque le mode \MF{} par +défaut sur notre installation est \texttt{ljfour} avec une résolution de +base de 600\dpi{} \textit{(dots per inch)}, cette instance est trouvée. +\begin{alltt} +> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} +\end{alltt} +Dans ce cas, lorsque l'on spécifie que nous recherchons une +résolution de 300\dpi{} (\texttt{-dpi=300}) nous voyons qu'aucune fonte +pour cette résolution n'est disponible dans le système. En fait, un +programme comme \cmdname{dvips} ou \cmdname{xdvi} ne s'en +préoccuperait pas et créerait les fichiers \file{.pk} à la +résolution demandée en utilisant le script \cmdname{mktexpk}. + +Intéressons-nous à présent aux fichiers d'en-tête et de configuration +pour \cmdname{dvips}. +Regardons en premier le fichier \file{tex.pro} communément utilisé +pour le support de \TeX{} avant de regarder le fichier +de configuration générique (\file{config.ps}) et la liste des fontes +\PS{} \file{psfonts.map}. Depuis l'édition 2004, les fichiers +\file{.map} et les fichiers de codage ont changé de place dans +l'arborescence \dirname{texmf}. Comme le suffixe \file{.ps} est +ambigu, nous devons spécifier quel type particulier du fichier +\texttt{config.ps} nous considérons (\optname{dvips config}). +\begin{alltt} +> \Ucom{kpsewhich tex.pro} + /usr/local/texmf/dvips/base/tex.pro +> \Ucom{kpsewhich -{}-format="dvips config" config.ps} + /usr/local/texmf-var/dvips/config/config.ps +> \Ucom{kpsewhich psfonts.map} + /usr/local/texmf-var/fonts/map/dvips/updmap/psfonts.map +\end{alltt} + +Regardons plus en détail les fichiers de support Times +\PS{} d'\acro{URW}. Leur nom standard dans le schéma de nommage des fontes +est \samp{utm}. Le premier fichier que nous voyons est le +fichier de configuration, qui contient le nom du fichier +de la liste : +\begin{alltt} +> \Ucom{kpsewhich -{}-format="dvips config" config.utm} + /usr/local/texmf-dist/dvips/psnfss/config.utm +\end{alltt} +Le contenu de ce fichier est +\begin{alltt} + p +utm.map +\end{alltt} +qui pointe vers le fichier \file{utm.map}, que nous cherchons à +localiser ensuite. +\begin{alltt} +> \Ucom{kpsewhich utm.map} + /usr/local/texmf-dist/fonts/map/dvips/times/utm.map +\end{alltt} +Ce fichier liste les noms des fichiers des +fontes \PS{} de type~1 dans la collection URW. Son contenu +ressemble à (nous ne montrons qu'une partie des lignes) : +\begin{alltt} +utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} +\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb +\else /usr/local/texmf-dist/fonts/type1/ +... urw/utm/utmr8a.pfb +\fi\end{alltt} + +Il devrait être clair, d'après ces quelques exemples, qu'il est facile +de trouver l'endroit où se cache un fichier donné. C'est +particulièrement important si vous suspectez que c'est, pour une +raison quelconque, une mauvaise version du fichier qui est utilisée, +puisque \cmdname{kpsewhich} va vous montrer le premier fichier +trouvé. + +\subsubsection{Opérations de débogage} +\label{sec:debugging} + +Il est quelquefois nécessaire de savoir comment un programme référence +les fichiers. Pour permettre cela, \KPS{} offre +plusieurs niveaux de débogage : +\begin{ttdescription} +\item[\texttt{\ 1}] Appels à \texttt{stat} (test d'existence de fichier). Lors d'une + exécution utilisant une base de données \file{ls-R} à jour, ce niveau + ne devrait donner presque aucune information en sortie. +\item[\texttt{\ 2}] Références aux différentes tables (comme la base + de données \file{ls-R}, les fichiers de correspondance de fontes, les fichiers de + configuration). +\item[\texttt{\ 4}] Opérations d'ouverture et de fermeture des + fichiers. +\item[\texttt{\ 8}] Information globale sur la localisation des types + de fichiers recherchés par \KPS. Ceci est utile pour trouver où a été + défini le chemin particulier pour un fichier. +\item[\texttt{16}] Liste des répertoires pour chaque élément du + chemin (utilisé uniquement en cas de recherche sur le disque). +\item[\texttt{32}] Recherche de fichiers. +\item[\texttt{64}] Valeur des variables. +\end{ttdescription} +Une valeur de \texttt{-1} activera toutes les options ci-dessus ; en +pratique, c'est habituellement la valeur la plus adaptée. + +De la même façon, avec le programme \cmdname{dvips}, en utilisant une +combinaison d'options de débogage, on peut suivre en détail la +localisation des +différents fichiers. De plus, lorsqu'un fichier n'est +pas trouvé, la trace du débogage montre les différents répertoires dans +lesquels le programme va chercher tel ou tel fichier, donnant ainsi +des indices sur le problème. + +Généralement, comme la plupart des programmes appellent la +bibliothèque \KPS{} en interne, on peut sélectionner une option de +débogage en utilisant la variable d'environnement +\envname{KPATHSEA\_DEBUG} et en la définissant égale à la valeur (ou +à une combinaison de valeurs) décrite(s) dans la liste ci-dessus. + +Note à l'intention des utilisateurs de Windows : il n'est pas facile +de rediriger les messages d'erreur vers un fichier sur ces +systèmes. À des fins de diagnostic, vous pouvez temporairement +affecter \texttt{KPATHSEA\_DEBUG\_OUTPUT=err.log} pour capturer le flux +standard d'erreur dans le fichier \texttt{err.log}. + +Considérons comme exemple un petit fichier source \LaTeX{}, +\file{hello-world.tex}, dont le contenu est le suivant. +\begin{verbatim} + \documentclass{article} + \begin{document} + Hello World! + \end{document} +\end{verbatim} +Ce petit fichier utilise simplement la fonte \file{cmr10}, aussi +allons voir comment \cmdname{dvips} prépare le fichier \PS{} +(nous voulons utiliser la version type~1 +des fontes Computer Modern, d'où l'option \texttt{-Pcms}). +\begin{alltt} +> \Ucom{dvips -d4100 hello-world -Pcms -o} +\end{alltt} +Dans ce cas, nous avons combiné le niveau 4 de débogage de +\cmdname{dvips} (chemins des fontes) avec l'option d'expansion des +éléments du chemin de \KPS\ (voir \cmdname{dvips} Reference Manual, +\OnCD{texmf/doc/html/dvips/dvips_toc.html} sur le \DVD{}). +La sortie (légèrement formatée) apparaît dans la +figure~\ref{fig:dvipsdbga}. +\begin{figure*}[tp] +\centering +\input{examples/ex6a.tex} +\caption{Recherche des fichiers de configuration}\label{fig:dvipsdbga} + +\bigskip + +\input{examples/ex6b.tex} +\caption{Recherche du fichier prolog}\label{fig:dvipsdbgb} + +\bigskip + +\input{examples/ex6c.tex} +\caption{Recherche du fichier de fontes}\label{fig:dvipsdbgc} +\end{figure*} + +\cmdname{dvips} commence par localiser ses fichiers de +fonctionnement. D'abord, \file{texmf.cnf} est trouvé, ce qui donne les +définitions pour les chemins de recherche servant à localiser les +autres fichiers, ensuite le fichier base de données \file{ls-R} (pour +optimiser la recherche des fichiers) et le fichier \file{aliases}, qui +permet de déclarer plusieurs noms (par exemple un nom \acro{DOS} de type +8.3 court et une version longue plus naturelle) pour le même +fichier. Ensuite \cmdname{dvips} continue en cherchant le fichier de +configuration générique \file{config.ps} avant de rechercher le fichier +de paramétrisation \file{.dvipsrc} (qui, dans notre cas, \emph{n'est +pas trouvé}). Enfin, \cmdname{dvips} localise le fichier de +configuration pour les fontes \PS{} Computer Modern +\file{config.cms} (ceci est lancé par l'option \mbox{\texttt{-Pcms}} de la +commande \cmdname{dvips}). Ce fichier contient la liste des fichiers + qui définissent la relation entre les noms des fontes +selon \TeX{}, selon \PS{} et dans le système de fichiers. +\begin{alltt} +> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} + p +ams.map + p +cms.map + p +cmbkm.map + p +amsbkm.map +\end{alltt} +\cmdname{dvips} veut chercher tous ces fichiers, y compris le +fichier générique d'association \file{psfonts.map}, qui est toujours +chargé (il contient des déclarations pour les fontes \PS{} les +plus communément utilisées ; voir la dernière partie de la Section +\ref{sec:examples-of-use} pour plus de détails sur la gestion du fichier +d'association \PS{}). + +Arrivé là, \cmdname{dvips} s'identifie à l'utilisateur : + \begin{alltt} + This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) + \end{alltt} + +\ifSingleColumn +pour continuer ensuite en cherchant le fichier prologue \file{texc.pro}, +\begin{alltt}\small +kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro +\end{alltt} +\else +pour continuer ensuite en cherchant le fichier prologue \file{texc.pro} +(voir la figure~\ref{fig:dvipsdbgb}). +\fi + +Après avoir trouvé ce fichier, \cmdname{dvips} affiche la date et +l'heure, nous informe qu'il va générer le fichier +\file{hello-world.ps} puis qu'il a besoin du fichier de fonte +\file{cmr10} et que ce dernier est déclaré comme « résident» +(pas besoin de bitmaps) : +\begin{alltt}\small +TeX output 1998.02.26:1204' -> hello-world.ps +Defining font () cmr10 at 10.0pt +Font cmr10 is resident. +\end{alltt} +Maintenant la recherche concerne le fichier \file{cmr10.tfm}, qui est +trouvé, puis quelques fichiers de prologue de plus (non montrés) sont +référencés ; finalement le fichier de la fonte type~1 \file{cmr10.pfb} +est localisé et inclus dans le fichier de sortie (voir la dernière ligne). +\begin{alltt}\small +kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, + path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: + /var/tex/fonts/tfm//). +kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm +kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, + ... + +kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb +[1] +\end{alltt} + +\subsection{Options à l'exécution} + +\Webc{} offre la possibilité de contrôler à l'exécution bon nombre de +paramètres concernant la mémoire (en particulier la taille des +tableaux utilisés) à partir du fichier +\file{texmf.cnf} qui est lu par \KPS. +Les paramètres en question se trouvent +dans la troisième partie du fichier inclus dans la distribution \TL{}. + Les variables les plus importantes sont : +\begin{ttdescription} +\item[\texttt{main\_memory}] + Nombre total de mots mémoire disponibles pour + \TeX{}, \MF{} et \MP. Vous devez générer un nouveau fichier de + format pour chaque nouveau paramétrage. Par exemple, vous pouvez + générer une version large de \TeX{} et appeler le fichier de format + \texttt{hugetex.fmt}. En utilisant la méthode supportée par \KPS{} + qui consiste à suffixer la variable par le nom du programme, la valeur + particulière de la variable \texttt{main\_memory} destinée à ce + fichier de format sera lue dans le fichier \file{texmf.cnf}. +\item[\texttt{extra\_mem\_bot}] + Espace supplémentaire pour certaines structures de données de \TeX{} : + boîtes, \textit{glue}, points d'arrêt\dots{} Surtout utile si vous utilisez + \PiCTeX{} par exemple. +\item[\texttt{font\_mem\_size}] + Nombre de mots mémoire disponibles pour décrire les polices. C'est + plus ou moins l'espace occupé par les fichiers \acro{TFM} lus. +\item[\texttt{hash\_extra}] + Espace supplémentaire pour la table de hachage des noms de séquences + de contrôle. Environ 10~000 de ces noms peuvent être stockés dans la + table principale ; si vous avez un document très volumineux avec + beaucoup de références croisées, il se peut que ce ne soit pas + suffisant. La valeur par défaut \texttt{hash\_extra} est \texttt{50000}. +\end{ttdescription} + +\noindent Évidemment, cette possibilité ne remplace pas une véritable +allocation dynamique des tableaux et de la mémoire mais puisque c'est +complexe à implémenter dans le présent source \TeX{}, ces paramètres lus +à l'exécution fournissent un compromis pratique qui procure une certaine +souplesse. + +\section{Installation sur un nouveau système Unix} + +Si vous avez un système Unix ne correspondant à aucun des exécutables +fournis, il faut compiler vous-même \TeX{} et tous ses programmes +satellites à partir des sources. Cela n'est pas aussi difficile qu'il +y paraît. Tout ce dont vous aurez besoin est contenu dans le +répertoire \texttt{source} qui se trouve sur le \DVD. + +\subsection{Prérequis} + +Il faut au moins 400\,Mo d'espace sur disque pour compiler la +totalité de \TeX{} et des programmes associés. +Vous aurez aussi besoin d'un +compilateur C \acro{ANSI}, de l'utilitaire \cmdname{make}, +d'un générateur d'analyseur lexical et d'un générateur d'analyseur +syntaxique. Nous recommandons les versions \GNU des programmes suivants +(\cmdname{gcc}, \GNU{}\cmdname{make}, \cmdname{m4}, +\cmdname{flex}, \cmdname{bison}). Vous pouvez utiliser d'autres compilateurs C +et d'autres programmes \cmdname{make} si vous maîtrisez +correctement la programmation sous Unix pour résoudre les +problèmes éventuels. La commande \texttt{uname} doit renvoyer une valeur +raisonnable. + +\subsection{Configuration} + +Tout d'abord, effectuez l'installation normale de \TL{} sur le disque +dur (voir section~\ref{sec:install}, +page~\pageref{sec:install}). Vous pouvez sauter l'installation de +tous les binaires précompilés. +Décompactez ensuite sur le disque le fichier +\file{source.tar.bz2} (archive compressée) trouvé dans +le répertoire \dirname{source} et placez-vous dans +le répertoire où vous avez transféré l'ensemble. +\begin{alltt} +> \Ucom{cd /tmp/tl-source} +> \Ucom{bunzip2 source.tar.bz2} +> \Ucom{tar xf source.tar} +\end{alltt} + +Lancez maintenant \textsf{configure} de la façon suivante : +\begin{alltt} +> \Ucom{sh configure -prefix=/usr/local/texlive/2007} +\end{alltt} + +Le répertoire \optname{-prefix} est le répertoire de base de +l'arborescence \TL{}, il est désigné par \var{TEXDIR} dans la suite. +\begin{comment} +Les répertoires utilisés sont les suivants : + +\noindent +\begin{tabular}{>{\ttfamily}ll@{}} + \dirname{$TEXDIR/texmf-dist} & répertoire de base pour les fontes, + macros, etc\\ + \dirname{$TEXDIR/man} & pages du manuel Unix\\ + \dirname{$TEXDIR/info} & manuels \GNU en format Info\\ + \dirname{$TEXDIR/bin/$archname} & exécutables.\\ +\end{tabular}\\ +\end{comment} +%$ + +Si vous ne voulez pas créer de répertoire \dirname{$archname} spécifique %$ +au système choisi pour stocker les exécutables (c.-à-d. les +copier directement dans \dirname{$TEXDIR/bin}), %$ +il faut exécuter \textsf{configure} avec l'option \\ +\verb|--disable-multiplatform|. + +Tapez \verb|./configure --help|, le programme affichera +les options supplémentaires disponibles (telles que supprimer l'installation +des extensions optionnelles comme \OMEGA\ ou \eTeX). + +\subsection{Exécuter \textsf{make}} +S'assurer que la variable ou l'option \texttt{noclobber} n'est pas définie. + et lancer le \cmdname{make} à la racine de l'arborescence de la façon +suivante : +\begin{alltt} +>> \Ucom{make world} +\end{alltt} +et aller prendre un café\dots + +Il peut être utile de garder une trace complète dans un fichier log en tapant : +\begin{alltt} +>> \Ucom{sh -c "make world >world.log 2>\&1" \&} +\end{alltt} +Avant de conclure que tout va bien, vérifier que le fichier log ne contient +pas de message d'erreur : le \cmdname{make} de \GNU renvoie toujours +le message \samp{***} à chaque erreur d'exécution. Vérifier aussi que +tous les exécutables ont été créés. +\begin{alltt} +>> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} +>> \Ucom{ls | wc} +\end{alltt} +Le résultat doit être supérieur à 200 (on peut tester le nombre exact +dans le répertoire \dirname{bin} de la distribution). + +Si vous avez besoin de droits spéciaux pour exécuter \texttt{make install}, +vous pouvez séparer \samp{make world} en deux processus différents : +\begin{alltt} +>> \Ucom{make all} +>> \Ucom{su} +>> \Ucom{make install strip} +\end{alltt} + +Après avoir installé vos nouveaux binaires, il faut suivre les procédures +normales de la post-installation, indiquées dans la +section~\ref{sec:postinstall}, page~\pageref{sec:postinstall}. + +\section{Remerciements} + +\TL{} est le résultat des efforts +collectifs de pratiquement tous les groupes d'utilisateurs de \TeX. +La présente édition de \TL{} a été coordonnée par Karl Berry. +Voici la liste des principaux contributeurs : + +\begin{itemize} + +\item Les associations d'utilisateurs anglais, allemands, néerlandais et + polonais (\acro{TUG}, \acro{DANTE} e.V., \acro{NTG}, and \acro{GUST}, + respectivement) qui contribuent ensemble à l'infrastructure technique et + administrative. Soutenez votre association locale (voir la liste + \url{http://tug.org/usergroups.html}) ! + +\item L'équipe du \acro{CTAN}, en particulier Robin Fairbairns, Jim Hef{}feron + et Rainer Schöpf, qui distribue les images des distributions \TL{} et + fournit les sites d'hébergement pour le stockage et la mise à jour des + extensions qui sont la base de \TL. + +\item Peter Breitenlohner et toute l'équipe \eTeX{} qui construisent + les bases des successeurs de \TeX. + +\item Thomas Esser et sa merveilleuse distribution \teTeX{} sans laquelle + \TL{} n'aurait jamais vu le jour. + +\item Michel Goossens, en tant que co-auteur de la documentation initiale. + +\item Eitan Gurari, dont le programme \TeX4ht a été utilisé pour créer la + version \HTML{} de cette documentation et qui travaille inlassablement à + l'améliorer, ce dans des délais très courts. + +\item \Thanh, Martin Schr\"oder et toute l'équipe pdf\TeX\ qui continuent + inlassablement à étendre les performances de \TeX. + +\item Hans Hagen qui, outre sa participation active aux tests, a adapté le + format \ConTeXt\ (\url{http://pragma-ade.com}) aux besoins de \TL{}. + +\item Hartmut Henkel, pour ses contributions au développement + de pdf\TeX{} et Lua\TeX{} entre autres. + +\item Taco Hoekwater, pour ses efforts sans cesse renouvelés à l'amélioration + de MetaPost et de (Lua)\TeX\ (\url{http://luatex.org}). + +\item Pawe{\l} Jackowski pour l'installeur Windows \cmdname{tlpm} et Tomasz + {\L}uczak pour la version graphique \cmdname{tlpmgui} utilisée dans + l'édition précédente. + +\item Akira Kakuto, pour son aide précieuse qui nous a permis + d'intégrer dans \TL{} les binaires Windows de sa distribution \acro{W32TEX} + (\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}). + +\item Jonathan Kew et \acro{SIL}, pour avoir produit + Xe\TeX{}, pour l'avoir intégré dans \TL{} et pour avoir + créé la première version de l'installeur Mac\TeX. + +\item Dick Koch, pour la maintenance de Mac\TeX\ (\url{http://tug.org/mactex}) + faite en symbiose avec \TL. + +\item Reinhard Kotucha, pour ses contributions majeures à l'infrastructure de + \TL{} 2008 et à son programme d'installation, pour ses contributions sous + Windows et pour son script \texttt{getnonfreefonts} en particulier. + +\item Siep Kroonenberg, également pour ses contributions majeures à + l'infrastructure de \TL{} 2008 et à son programme d'installation ainsi que + pour la réécriture de cette documentation. + +\item Petr Ol\v{s}ak, qui coordonna et vérifia minutieusement toute la + partie tchèque et slovaque. + +\item Toshio Oshima, pour le visualisateur \cmdname{dviout} pour Windows. + +\item Manuel Pégourié-Gonnard, pour son aide concernant le programme de mise à + jour de la distribution, la documentation et pour le développement de + \cmdname{tldoc}. + +\item Fabrice Popineau, pionnier du développement de \TL{} sous Windows et + pour son travail sur la documentation française. + +\item Norbert Preining, principal architecte de la distribution \TL{} 2008 et + de son installeur et coordinateur (avec Frank K\"uster) de la + version Debian de \TL. + +\item Sebastian Rahtz, qui a créé la distribution \TL{} et en a assuré la + maintenance pendant de nombreuses années. + +\item Vladimir Volovich, pour son aide substantielle, en particulier pour + avoir rendu possible l'intégration de \cmdname{xindy} dans \TL. + +\item Staszek Wawrykiewicz, principal testeur de \TL{} et coordinateur des + contributions polonaises (fontes, installation Windows, etc.). + +\item Olaf Weber, pour son patient assemblage de \Webc. + +\item Gerben Wierda, qui a créé et maintient la partie \MacOSX{} + et qui participe activement aux tests. + +\item Graham Williams, pour son travail sur le catalogue \TeX\ des + composants. + +\end{itemize} + +Les binaires ont été compilés par : +Tigran Aivazian (\pkgname{x86\_64-linux}), +Tim Arnold (\pkgname{hppa-hpux}), +Randy Au (\pkgname{amd64-freebsd}), +Edd Barrett (\pkgname{i386-openbsd}), +Karl Berry (\pkgname{i386-linux}), +Akira Kakuto (\pkgname{win32}), +Dick Koch (\pkgname{universal-darwin}), +Manfred Lotz (\pkgname{i386-freebsd}), +Norbert Preining (\pkgname{alpha-linux}), +Arthur Reutenauer (\pkgname{sparc-linux}), +Thomas Schmitz (\pkgname{powerpc-linux}), +Apostolos Syropoulos (\pkgname{i386-solaris}), +Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-solaris}), +Olaf Weber (\pkgname{mips-irix}). + +Documentation et mises à jour des traductions : +Karl Berry (anglais), +Daniel Flipo (français), +Klaus H\"oppner (allemand), +Petr Sojka \& Jan Busa (tchèque et slovaque), +Boris Veytsman (russe), +Staszek Wawrykiewicz (polonais). + +La page d'accueil de la documentation \TL{} est +\url{http://tug.org/texlive/doc.html}. + +Bien sûr, notre gratitude va en premier lieu à Donald Knuth pour avoir +inventé \TeX{} et l'avoir offert au monde entier. + +\section{Historique des versions successives} +\label{sec:history} + +\subsection{Les éditions précédentes} + +La discussion commença à la fin de 1993 quand le Groupe des Utilisateurs +Néerlandais de \TeX{} commençait à travailler à son \CD{} 4All\TeX{} pour les +utilisateurs de \acro{MS-DOS} et on espérait à ce moment sortir un \CD{} +unique pour tous les systèmes. C'était un objectif beaucoup trop ambitieux +mais il permit la naissance du \CD{} 4All\TeX{}, projet couronné de succès et +aussi d'un groupe de travail « \acro{TUG} Technical Council » pour +mettre en place TDS (\emph{\TeX{} Directory Structure} : +\url{http://tug.org/tds}), qui spécifiait la gestion des fichiers \TeX{} sous +une forme logique. La mouture finale de \TDS{} fut publiée dans le numéro de +décembre 1995 de \textsl{TUGboat} et il était clair depuis un certain temps +qu'il fallait proposer un produit contenant une structure modèle sur \CD{}. +La distribution que vous possédez est le résultat direct des délibérations de +ce groupe de travail. Il était également clair que le succès des \CD{} +4All\TeX{} démontrait que les utilisateurs d'Unix trouveraient leur bonheur +avec une distribution aussi simple et ceci a été l'autre objectif de +\TL. + +Nous avons d'abord entrepris de créer un nouveau \CD{} \TDS{} Unix à l'automne +1995 et nous avons rapidement choisi \teTeX{} de Thomas Esser comme étant la +configuration idéale, car il supportait déjà plusieurs plates-formes et avait +été construit en gardant à l'esprit la portabilité entre systèmes. Thomas +accepta de nous aider et commença à travailler sérieusement au début de 1996. +La première édition sortit en mai 1996. Au début de 1997, Karl Berry acheva +une nouvelle distribution de \Webc{}, qui incluait presque toutes les +caractéristiques que Thomas Esser avait ajoutées dans \teTeX{} et il fut décidé +de baser la deuxième édition du \CD{} sur le standard \Webc, en y ajoutant le +script \texttt{texconfig} de \teTeX. La troisième édition du \CD{} était +basée sur une version majeure de \Webc, 7.2, par Olaf Weber ; en même temps, +une nouvelle version révisée de \teTeX{} était achevée dont \TL{} partageait +presque toutes les caractéristiques. La quatrième édition a suivi le même +schéma, en utilisant une nouvelle version de \teTeX{} et une nouvelle version +de \Webc{} (7.3). Le système incluait dorénavant un programme complet +d'installation pour Windows. + +Pour la cinquième édition (mars 2000), de nombreuses parties du \CD{} +ont été vérifiées et révisées, des centaines de composants +mis à jour. +Le contenu détaillé des composants était décrit par des +fichiers XML. Mais le changement majeur de cette cinquième édition a +été la suppression de tout logiciel non libre de droits. +Tout ce qui se trouve dans \TL{} devait être compatible avec la licence +Debian (\emph{Debian Free Software Guidelines} : +\url{http://www.debian.org/intro/free}) ; nous avons +fait de notre mieux pour vérifier les termes des licences de chaque +composant et nous souhaiterions que toute erreur nous soit signalée. + +La sixième édition (juillet 2001) contient un grand nombre de mises à jour. +Le changement majeur de cette version réside dans la refonte du +processus d'installation : l'utilisateur peut désormais choisir +les collections de manière plus précise. Les collections concernant +les langues ont été entièrement réorganisées, aussi le choix d'une +langue installe non seulement les macros, les fontes, etc. mais +prépare également un fichier \file{language.dat} adéquat. + +La septième édition (mai 2002) a comme ajout majeur une installation +pour \MacOSX{} et l'habituelle myriade de mises à jour de composants et +de programmes. Un objectif important a été de fusionner à +nouveau les sources avec ceux de \teTeX{}, alors que les versions +5 et 6 s'en étaient éloignées. + +\subsubsection{2003} + +En 2003, le flot de mises à jour et d'additions a continué mais nous +avons constaté que \TL{} était devenu si volumineux qu'il ne +pouvait plus tenir sur un seul \CD, aussi l'avons-nous divisé en trois +distributions distinctes (voir section~\ref{sec:tl-coll-dists}, +page~\pageref{sec:tl-coll-dists}). Par ailleurs : +\begin{itemize} +\item À la demande de l'équipe \LaTeX{}, nous avons modifié les + commandes standard \cmdname{latex} et \cmdname{pdflatex} pour + qu'elles utilisent \eTeX{} (voir page~\pageref{text:etex}). +\item Les nouvelles fontes Latin Modern sont disponibles (et + recommandées). +\item Le support pour Alpha \acro{OSF} a été supprimé + (celui pour \acro{HPUX} l'avait été auparavant), car personne + disposant des machines nécessaires ne s'est + proposé pour compiler les nouveaux binaires. +\item L'installation pour Windows a été largement modifiée ; un environnement + de travail intégré basé sur \cmdname{XEmacs} a été introduit. +\item Des programmes supplémentaires importants pour Windows (Perl, + Ghost\-script, Image\-Magick, Ispell) sont maintenant installés dans le + répertoire d'installation de \TL{}. +\item Les fichiers \emph{font map} utilisés par \cmdname{dvips}, + \cmdname{dvipdfm} et \cmdname{pdftex} sont maintenant générés par le + nouveau programme \cmdname{updmap} et installés dans + \dirname{texmf/fonts/map}. +\item Dorénavant, \TeX{}, \MF{} et \MP{} écrivent les caractères 8-bit + présentés en entrée sans modification et non pas avec la notation + \verb|^^|, que ce soit dans des fichiers (par la commande + \verb|write|), dans les fichiers de trace (\verb|.log|) ou sur le + terminal. Dans le \TL{}~7, l'écriture de ces caractères + 8-bit était influencée par les paramètres de localisation du + système; maintenant ces paramètres n'influent plus du tout sur le + comportement des programmes \TeX{}. Si pour quelque raison que ce + soit, vous avez besoin de la notation \verb|^^| en sortie, + renommez le fichier \verb|texmf/web2c/cp8bit.tcx|. Les prochaines + versions disposeront d'un moyen plus propre pour contrôler cette + sortie. +\item La documentation de \TL{} a été largement révisée. +\item Enfin, comme la numérotation séquentielle des versions + devenait peu maniable, il a été décidé d'identifier désormais la version + de \TL{} par l'année : \TL{}~2003 au lieu de \TL{}~8. +\end{itemize} + + +\subsubsection{2004} + +2004 a apporté beaucoup de changements (et quelques incompatibilités avec les +versions précédentes) : + +\begin{itemize} + +\item Si vous avez installé des fontes supplémentaires qui ont leur propre +fichier \file{.map} ou des fichiers \file{.enc} spécifiques, vous +devrez vraisemblablement déplacer ces fichiers. + +Les fichiers \file{.map} sont désormais recherchés uniquement dans les +sous-répertoires \dirname{fonts/map} (dans chaque arborescence +\filename{texmf}), leur chemin de recherche est donné par la variable +\envname{TEXFONTMAPS} de \filename{texmf.cnf}. +De même, les fichiers \file{.enc} sont désormais recherchés uniquement +dans les sous-répertoires \dirname{fonts/enc}, leur chemin de recherche est +donné par la variable \envname{ENCFONTS} de \filename{texmf.cnf}. +Le script \cmdname{updmap} devrait émettre des messages d'avertissement +pour les fichiers \file{.map} et \file{.enc} mal placés. + +Sur les différentes façons de traiter le problème, consulter +\url{http://tug.org/texlive/mapenc.html}. + +\item La distribution pour Windows a changé cette année : +l'installation de la distribution \fpTeX{} (basée sur \Webc{}) de Fabrice +Popineau n'est plus proposée. À la place, vous pouvez tester et installer +la distribution \ProTeXt{} basée sur \MIKTEX{} (indépendante de \Webc{}), +voir section~\ref{sec:overview-tl}, page~\pageref{sec:overview-tl}. + +\item L'ancien répertoire \dirname{texmf} a été éclaté en trois parties : +\dirname{texmf}, \dirname{texmf-dist} et \dirname{texmf-doc}. Voir +section~\ref{sec:tld}, page~\pageref{sec:tld}. + +\item Tous les fichiers relatifs aux différents avatars de \TeX{} sont +désormais regroupés dans le même sous-répertoire \dirname{tex} des +arborescences \dirname{texmf*} (ils étaient jusqu'ici placés dans des +sous-répertoires spécifiques \dirname{tex}, \dirname{etex}, +\dirname{pdftex}, \dirname{pdfetex}, etc.). Voir +\OnCD{texmf-doc/doc/english/tds/tds.html\#Extensions}. + +\item Les scripts auxiliaires, normalement pas exécutés directement +par les utilisateurs, sont regroupés dans un répertoire \dirname{scripts} +des arborescences \dirname{texmf*}. On les localise grâce à la +commande \verb|kpsewhich -format=texmfscripts|. Au cas où vous en +auriez, les programmes utilisant ces scripts nécessiteront une adaptation. +Voir \OnCD{texmf-doc/doc/english/tds/tds.html\#Scripts}. + +\item La plupart des formats affichent en clair (dans les fichiers +\file{.log} en particulier) les caractères imprimables au lieu +de les transcrire en notation hexadécimale \verb|^^|. Ceci se fait +grâce au fichier \filename{cp227.tcx}, qui considère comme imprimables +les caractères 32 à 256, ainsi que les tabulations et les changements +de page (caractères 9 à 11). Les formats faisant exception sont +plain \TeX\ (seuls les caractères 32 à 127 sont déclarés imprimables), +\ConTeXt{} (0 à 255 imprimables) et les formats basés sur \OMEGA. +Il y a peu de différence avec le comportement de \TL\,2003 +mais la mise en Å“uvre est plus propre et plus facilement configurable. +Voir \OnCD{texmf/doc/web2c/web2c.html\#TCX-files}. +Noter que l'utilisation du codage Unicode en entrée peut provoquer +des affichages défectueux en sortie (TeX code sur un seul octet). + +\item Tous les formats, sauf plain \TeX, font appel au moteur +\textsf{pdfetex} (qui produit bien sûr par défaut des fichiers \acro{DVI} +lorsque le format choisi est \LaTeX). Ceci permet aux formats +\LaTeX, \ConTeXt, etc., d'avoir accès aux fonctionnalités +micro-typographiques de pdf\TeX{} (alignement optique des marges par exemple) +et aux fonctionnalités de \eTeX{} (\OnCD{texmf-dist/doc/etex/base/}). + +Ceci rend \emph{indispensable} le recours à l'extension \pkgname{ifpdf} +(qui fonctionne aussi bien avec plain que \LaTeX) pour déterminer si +le format de sortie est \acro{DVI} ou \acro{PDF}. Tester si la commande +\cs{pdfoutput} est définie ou non \emph{n'est pas} un moyen fiable +de le faire. + +\item pdf\TeX\ (\url{http://pdftex.org}) offre de nouvelles fonctionnalités : + + \begin{itemize} + + \item Les commandes \cs{pdfmapfile} et \cs{pdfmapline} permettent + de spécifier le choix des fichiers \file{.map} à utiliser + pour le document en cours. + + \item L'amélioration du gris typographique par variation (infime) de la + largeur des caractères (\textit{font expansion}) est plus facile à + mettre en Å“uvre, voir + \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} + + \item Le fichier \filename{pdftex.cfg} n'est plus utilisé. + Toutes les affectations de paramètres doivent désormais être + faites dans le préambule en utilisant les primitives ad~hoc. + + \item Pour plus d'informations, consulter le manuel de pdf\TeX\ : + \OnCD{texmf/doc/pdftex/manual}. + + \end{itemize} + +\item La primitive \cs{input} de \cmdname{tex}, \cmdname{mf} et +\cmdname{mpost}, accepte désormais les espaces et autres caractères +spéciaux dans les noms de fichiers à condition d'utiliser des +\textit{double quotes}, en voici deux exemples typiques : +\begin{verbatim} +\input "filename with spaces" % plain +\input{"filename with spaces"} % latex +\end{verbatim} +Consulter le manuel \Webc{} pour plus d'informations : \OnCD{texmf/doc/web2c}. + +\item Les fonctionnalités de enc\TeX\ sont désormais incluses dans \Webc{}. +Ainsi, tous les formats \emph{construits avec l'option \optname{-enc}} y ont +accès. enc\TeX\ permet le transcodage en entrée et en sortie et +l'utilisation transparente du codage Unicode \acro{UTF}-8. Voir +\OnCD{texmf-dist/doc/generic/enctex/} et +\url{http://www.olsak.net/enctex.html}. + +\item Un nouveau moteur combinant les fonctionnalités de \eTeX\ +et d'\OMEGA, appelé Aleph, est disponible. \OnCD{texmf-dist/doc/aleph/base} +et \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph} +fournissent une information succincte. Le format \LaTeX{} utilisant +Aleph s'appelle \textsf{lamed}. + +\item La licence \acro{LPPL} de \LaTeX\ (version décembre 2003) a changé, +elle est désormais compatible avec les prescriptions Debian. +Les autres changements sont décrits dans le fichier \filename{ltnews}, voir +\OnCD{texmf-dist/doc/latex/base}. + +\item Un nouveau programme, \cmdname{dvipng}, qui convertit les fichiers +\acro{DVI} en images \acro{PNG} a été ajouté. Voir +\OnCD{texmf/doc/man/man1/dvipng.1}. + +\item Nous avons dû réduire le nombre de fontes incluses dans l'extension +\pkgname{cbgreek}, ceci a été fait avec l'accord et l'aide de l'auteur +(Claudio Beccari). Les fontes exclues (invisibles, transparentes, contours) +sont rarement utilisées et la place nous manquait. La collection complète +des fontes \pkgname{cbgreek} est disponible sur \acro{CTAN} +(\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). + +\item La commande \cmdname{oxdvi} a été supprimée, il suffit utiliser +\cmdname{xdvi} à la place. + +\item Les commandes \cmdname{initex}, \cmdname{virtex} et leurs +homologues pour \cmdname{mf} et \cmdname{mpost} ont disparu. +Vous pouvez les recréer si nécessaire mais elles sont avantageusement +remplacées, depuis des années maintenant, par l'option \optname{-ini} +(\cmdname{tex} \optname{-ini} pour \cmdname{initex} et \cmdname{virtex}). + +\item Les binaires pour l'architecture \textsf{i386-openbsd} ont été + supprimés par manque de volontaires pour les compiler. + +Sur \textsf{sparc-solaris} (au moins) il sera probablement +nécessaire de positionner la variable d'environnement +\envname{LD\_LIBRARY\_PATH} pour utiliser les programmes de la famille +\pkgname{t1utils}. Ceci vient du fait qu'ils sont compilés en C++ et +que l'emplacement des bibliothèques dynamiques est variable. +Ce n'est pas une nouveauté 2004 mais ce point n'était pas documenté +précédemment. De même, sur \textsf{mips-irix}, les bibliothèques dynamiques +\acro{MIPS}pro 7.4 sont nécessaires. + +\end{itemize} + +\subsubsection{2005} + +2005 a apporté son lot habituel d'innombrables mises à jour d'extensions +et de programmes. L'infrastructure est restée relativement stable par rapport +à 2004, à quelques changements inévitables près : + +\begin{itemize} + +\item Trois nouveaux scripts \cmdname{texconfig-sys}, \cmdname{updmap-sys} et + \cmdname{fmtutil-sys} ont été introduits ; ils agissent sur la + configuration générale de la machine, comme le faisaient les + scripts \cmdname{texconfig}, \cmdname{updmap} et \cmdname{fmtutil} + jusqu'à l'an dernier. Les nouveaux scripts \cmdname{texconfig}, + \cmdname{updmap} et \cmdname{fmtutil} modifient maintenant + la configuration \emph{personnelle} de l'utilisateur qui les lance ; + le résultat est placé dans le répertoire personnel de l'utilisateur + (sous \dirname{$HOME/.texlive2005}). %$ + +\item De nouvelles variables, \envname{TEXMFCONFIG} (resp. + \envname{TEXMFSYSCONFIG}) ont été introduites ; elles définissent + les répertoires où doivent se trouver les fichiers de configuration de + l'utilisateur (resp. de la machine), comme \filename{fmtutil.cnf} et + \filename{updmap.cfg}. Les utilisateurs de fichiers de configuration + locaux \filename{fmtutil.cnf} ou \filename{updmap.cfg} devront + probablement les déplacer ; une autre possibilité est de modifier la + définition des variables \envname{TEXMFCONFIG} ou + \envname{TEXMFSYSCONFIG} dans \filename{texmf.cnf}. L'important est + de s'assurer de la cohérence entre les définitions de ces variables + dans \filename{texmf.cnf} et l'emplacement réel de ces fichiers. + Voir section~\ref{sec:texmftrees}, page~\pageref{sec:texmftrees} pour + la description des différentes arborescences texmf utilisées. + +\item L'an dernier nous avions rendu « \texttt{undefined} » certaines + primitives propres à \cmdname{pdftex} (comme \verb|\pdfoutput|) + dans les formats créés à partir de \cmdname{pdfetex} (\cmdname{latex} + \cmdname{amstex}, \cmdname{context} par exemple)). + C'était à titre transitoire, aussi cette année, ces primitives sont de + nouveau définies dans tous les formats à base \cmdname{pdf(e)tex}, + \emph{même lorsqu'ils sont utilisés pour produire des fichiers + \file{.dvi}}. Ceci implique qu'il vous faudra modifier vos + documents qui utilisent le test \verb|\ifx\pdfoutput\undefined| + pour déterminer si la sortie est en DVI ou en PDF. Le mieux est + d'utiliser l'extension \pkgname{ifpdf.sty} et son test + \verb|\ifpdf| qui fonctionne même en plain \TeX. + +\item L'an dernier nous avions fait en sorte que la plupart des formats + impriment dans les sorties \file{.log} des caractères 8-bit + lisibles à la place des notations hexadécimales \verb|^^| + (voir section précédente). + Le nouveau fichier TCX \filename{empty.tcx} permet + de revenir facilement à la notation traditionnelle \verb|^^|, il suffit + de coder : +\begin{verbatim} +latex --translate-file=empty.tcx fichier.tex +\end{verbatim} + +\item Le nouveau programme \cmdname{dvipdfmx} est disponible pour convertir + des fichier DVI en PDF ; ce programme remplace \cmdname{dvipdfm}, + toujours disponible mais dont l'usage est maintenant déconseillé. + +\item Les variables \envname{HOMETEXMF} et \envname{VARTEXMF} ont été renommées + en \envname{TEXMFHOME} et \envname{TEXMFSYSVAR} respectivement pour + raisons de cohérence avec les autres noms de variables. Il y a aussi + \envname{TEXMFVAR} qui désigne maintenant un répertoire personnel + de l'utilisateur (cf. le premier point de la présente liste). + +\end{itemize} + +\subsubsection{2006--2007} + +En 2006--2007, la nouveauté majeure a été l'arrivée dans \TL{} de Xe\TeX{} +disponible sous forme de deux programmes \texttt{xetex} et \texttt{xelatex}, +voir \url{http://scripts.sil.org/xetex}. + +MetaPost a subi une mise à jour importante et d'autres améliorations +sont prévues, voir \url{http://tug.org/metapost/articles}. Il en va de même +pour pdf\TeX{}, voir \url{http://tug.org/applications/pdftex}. + +Le format \filename{tex.fmt} et les formats pour MetaPost and \MF\ ne +se trouvent plus dans \dirname{texmf/web2c} mais dans des +sous-répertoires de \dirname{texmf/web2c} (la recherche de fichiers +\filename{.fmt} est néanmoins faite aussi dans \dirname{texmf/web2c}). +Ces sous-répertoires portent le nom du moteur utilisé pour construire +le format, par exemple \filename{tex}, \filename{pdftex} ou +\filename{xetex}. Ce changement ne devrait pas avoir d'effet visible +pour les utilisateurs. + +Le programme (plain) \texttt{tex} ignore désormais les lignes commençant +par \texttt{\%\&} qui permettent de déterminer le format à utiliser ; +c'est un vrai \TeX{} « à la Knuth » ! +\LaTeX\ et tous les autres prennent toujours en compte les lignes commençant +par \texttt{\%\&}. + +Comme chaque année des centaines d'extensions et de programmes ont été mis à +jour, voir les sites \acro{CTAN} (\url{http://www.ctan.org}). + +L'arborescence utilisée en interne a été réorganisée avec de nouveaux outils +qui devraient fournir une meilleure base de travail pour les développements +futurs. + +Enfin, en mai 2006 Thomas Esser a annoncé qu'il renonçait à poursuivre le +développement de te\TeX{} (\url{http://tug.org/tetex}). Sa décision a relancé +l'intérêt pour \TL, en particulier chez les distributeurs de solutions +\GNU/Linux (un nouveau schéma d'installation \texttt{tetex} a été ajouté dans +le script d'installation de \TL{} pour produire une distribution proche de +l'ancienne te\TeX). La distribution \TL{} existe déjà sous forme de paquets +Debian, espérons que les autres acteurs du monde Linux (RedHat, SuSe, etc.) +suivront et que les utilisateurs se verront proposer à l'avenir des +distributions \TeX{} riches et plus faciles à installer. + +Remarque finale : toutes les anciennes distributions \TL{} ainsi que les +jaquettes des \CD{} correspondants sont disponibles ici : +\url{ftp://tug.org/historic/systems/texlive}. + +\subsection{L'édition 2008} +\label{tlcurrent} + +En 2008, l'infrastructure de la distribution \TL{} a été entièrement remaniée. +Un nouveau fichier texte, \filename{tlpkg/texlive.tlpdb}, regroupe toutes les +informations concernant la configuration \TL{} de la machine. + +Ce fichier permet entre autres choses de procéder à des mises à jour par le +réseau après l'installation initiale. Cette possibilité était offerte depuis +des années par MiK\TeX. Nous espérons pouvoir fournir des mises à jour +régulières du contenu des archives \CTAN. + +Le nouveau moteur Lua\TeX\ (\url{http://luatex.org}) a été intégré ; +il offre de nouvelles fonctionnalités typographiques et repose +sur l'excellent langage de commande Lua qui peut aussi être utilisé +en dehors de \TeX. + +Les versions Windows et Unix sont beaucoup plus proches que par le passé. +En particulier les scripts en Perl et en Lua sont communs aux deux +architectures. + +\TL{} dispose d'une nouvelle interface pour la maintenance (\cmdname{tlmgr} +voir section~\ref{sec:tlmgr}), elle permet les ajouts, mises à jour et +suppressions de composants et prend en charge la régénération des bases +\texttt{ls-R}, des formats et des fichiers \filename{.map} lorsque c'est +nécessaire. + +Les fonctionnalités de \cmdname{tlmgr} englobent toutes les tâches dévolues +auparavant à \cmdname{texconfig} qui ne devrait plus être utilisé (il est +conservé mais avec un champ d'action réduit). + +Le programme d'indexation \cmdname{xindy} (\url{http://xindy.sourceforge.net/}) +est maintenant disponible pour la plupart des plates-formes. + +L'utilitaire \cmdname{kpsewhich} dispose de deux options nouvelles : +\optname{--all} qui retourne toutes les occurrences du fichier recherché +et \optname{--subdir} qui limite la recherche à un sous-répertoire donné. + +Le programme \cmdname{dvipdfmx} permet maintenant d'extraire les informations +concernant la \textit{bounding box} par le biais de la commande +\cmdname{extractbb}; c'était une des dernières fonctionnalités de +\cmdname{dvipdfm} qui manquaient à \cmdname{dvipdfmx}. + +Les alias de polices \filename{Times-Roman}, \filename{Helvetica}, etc. +ont été supprimés, les conflits de codage qu'ils induisaient n'ayant pas pu +être résolus. + +Le format \pkgname{platex} a été supprimé afin de résoudre un conflit de nom +avec son homonyme japonais ; le support pour le polonais est assuré +maintenant par l'extension \pkgname{polski}. + +Les fichiers \web{} d'extension \filename{.pool} sont maintenant inclus dans +les binaires afin de faciliter les mises à jour. + +Enfin, les changements décrits par Donald Knuth dans « \TeX\ tuneup of 2008 » +(voir \url{http://tug.org/TUGboat/Articles/tb29-2/tb92knut.pdf}) sont inclus +dans la présente édition. + +\subsection{Versions futures} + +\emph{\TL{} n'est pas un produit parfait !} (et ne le sera jamais). +Nous prévoyons de continuer à produire de nouvelles versions et aimerions +fournir plus d'aide, de fonctionnalités, de programmes d'installation et +(bien sûr) une arborescence améliorée et vérifiée de macros et de fontes. Ce +travail est effectué par des volontaires débordés, dans la limite de leur +temps libre et beaucoup reste à faire. Si vous pouvez nous aider, n'hésitez +pas à nous contacter, voir \url{http://tug.org/texlive/contribute.html}. + +Corrections, suggestions et propositions d'aide doivent être envoyées à : +\begin{quote} +\email{tex-live@tug.org} \\ +\url{http://tug.org/texlive} +\end{quote} + +\medskip +\noindent \textsl{Bon travail avec \TeX{} !} + +\end{document} + +%%% Local Variables: +%%% mode: latex +%%% mode: flyspell +%%% ispell-local-dictionary: "francais" +%%% TeX-master: t +%%% coding: utf-8 +%%% End: diff --git a/Master/texmf/doc/texlive/source/texlive-pl/Makefile b/Master/texmf/doc/texlive/source/texlive-pl/Makefile new file mode 100644 index 00000000000..4f0d8cc9985 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-pl/Makefile @@ -0,0 +1,3 @@ +include ../texlive-en/Makefile +doc = texlive-pl +lang = polish diff --git a/Master/texmf/doc/texlive/source/texlive-pl/live4ht.cfg b/Master/texmf/doc/texlive/source/texlive-pl/live4ht.cfg new file mode 100644 index 00000000000..2927d07cb93 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-pl/live4ht.cfg @@ -0,0 +1,52 @@ +% tex4ht configuration file for the TeX Live documentation. +% Accumulated over many years. Public domain. +% +% html specifies the main output format. +% info for extra debugging info in the log files. + +% have html in one piece (including footnotes). +%\Preamble{charset=iso-8559-2,html,info,fn-in} +\Preamble{html,info,fn-in} + +% add extra stylesheet +\Configure{@HEAD}{\HCode{% +\Hnewline +\Hnewline +}} +% use png graphics as-is +\Configure{graphics*} + {png} + {\Needs{""}% + \Picture[pict]{\csname Gin@base\endcsname.png}% + } +% or LaTeX complains it is missing. +\begin{document} + +\EndPreamble + +% simplify output for HTML. We leave TeX and LaTeX alone, since tex4ht +% actually does the lowered E (and raised A) in CSS. +%\def\OMEGA{Omega} +\def\LaTeXe{LaTeX2e} +\def\eTeX{e-\TeX} +\def\acro#1{#1} +\def\MF{Metafont} +\def\BibTeX{BibTeX} +\def\warningbox{} +\def\endwarningbox{} +\def\Thanh{H\`an Th\^e Th\`anh} + +\Configure{crosslinks}{[}{] + }{nastêpny}{poprzedni}{wstecz} + {pocz±tek}{koniec}{spis} + +\ifx\tldocenglish\undefined \else + % these definitions cause "missing } inserted" at \end{tabularx} in + % other langs. don't know why. + % + % don't make these into links, as happens with \path. We only have a couple + % special characters that actually occur. + \def\dirname{\texttt\bgroup\catcode`\$=12 \catcode`\_=12 \finishliteral} + \def\finishliteral#1{#1\egroup} + \let\filename=\dirname +\fi diff --git a/Master/texmf/doc/texlive/source/texlive-pl/tex-livep.sty b/Master/texmf/doc/texlive/source/texlive-pl/tex-livep.sty new file mode 100644 index 00000000000..e81908a5d47 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-pl/tex-livep.sty @@ -0,0 +1,446 @@ +% TeX Live documentation style. Written by many people over many years. +% Public domain. +% +\NeedsTeXFormat{LaTeX2e}[1995/12/01] +\ProvidesPackage{tex-livep}[2008/07/31 v1.6 TeX Live documentation style] +% +\RequirePackage{alltt} +\RequirePackage{array} +\RequirePackage{colortbl} +\RequirePackage{comment} +\RequirePackage{float} +\RequirePackage{graphicx} +\RequirePackage{longtable} +\RequirePackage{shortvrb} +\RequirePackage[normalem]{ulem} +\RequirePackage[obeyspaces]{url} +\RequirePackage{xspace} +% +\RequirePackage{lmodern} +\usepackage{textcomp}% including \textbullet +\usepackage[T1]{fontenc} +%\usepackage[latin1]{inputenc} +% +% for a proper \acro command (even in the context of the definition in +% ltugboat -- \DRC overrides without checking) +\RequirePackage{relsize} +%\DeclareRobustCommand{\acro}[1]{\textsmaller{#1}\@} +\def\acro#1{\textscale{.9}{#1}\@} +% +\RequirePackage{fancyvrb} +\DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=\normalsize} +\DefineVerbatimEnvironment{fverbatim}{Verbatim}{fontsize=\footnotesize} +\DefineVerbatimEnvironment{sverbatim}{Verbatim}{fontsize=\small} +\DefineVerbatimEnvironment{boxedverbatim} + {Verbatim}{fontsize=\scriptsize,frame=single} +\DefineVerbatimEnvironment{Verbatim}{Verbatim}{fontsize=\normalsize} +\def\verbatiminput#1{\VerbatimInput[fontsize=\scriptsize]{#1}} +\def\boxedverbatiminput#1{\VerbatimInput[frame=single,fontsize=\scriptsize]{#1}} +\def\listinginput#1#2{\VerbatimInput[fontsize=\scriptsize,firstnumber=#1,numbers=left]{#2}} +\MakeShortVerb\| +% +% +% Done with packages. +% +% Page layout. +\advance\textwidth by 1.1in +\advance\oddsidemargin by -.55in +\advance\evensidemargin by -.55in +% +\advance\textheight by 1in +\advance\topmargin by -.5in +\advance\footskip by -.5in +\pagestyle{headings} +% +% LaTeX parameters. +\renewcommand{\topfraction}{0.85} +\renewcommand{\floatpagefraction}{0.86} +\renewcommand{\textfraction}{0.1} +\renewcommand{\abovecaptionskip}{4pt} +\renewcommand{\belowcaptionskip}{4pt} +\setcounter{tocdepth}{3} +\setcounter{secnumdepth}{3} +\setcounter{topnumber}{5} +\setcounter{totalnumber}{5} +% +% linebreaking, etc. +\hbadness=4000 +\vbadness=4000 +\emergencystretch=.1\hsize +\relpenalty=500 +% +\def\slash{/\penalty\z@\hskip\z@skip } +% +% various sorts of names +\newcommand*{\pkgname}[1]{\textsf{#1}}% package name +\newcommand*{\optname}[1]{\texttt{#1}}% (package,class) option name +\newcommand*{\cmdname}[1]{\textsf{#1}}% command name +\newcommand*{\colname}[1]{\emph{#1}}% collection name +\newcommand*{\dirname}[1]{\path{#1}}% directory name +\newcommand*{\filename}[1]{\path{#1}}% file name +\newcommand*{\envname}[1]{\texttt{#1}}% environment variable name +\newcommand{\code}[1]{\texttt{#1}} +\newcommand{\file}[1]{\texttt{#1}} +\newcommand{\prog}[1]{\textsf{#1}}% same as \cmdname +\newcommand{\samp}[1]{`\texttt{#1}'} +\newcommand{\var}[1]{{\sl #1}}% not \textsl, for roman not typewriter slanted. +\newcommand{\ttvar}[1]{\texttt{\var{#1}}} +% +% underlined command input. +%\def\Ucom#1{% +% \uline{\rule[-.2\baselineskip]{0pt}{.9\baselineskip}\ttfamily #1}} +% bold command input +\def\Ucom#1{{\bfseries\ttfamily #1}} + +% \CDref is for url's with a #, where we need to write the target url and +% displayed url separately in the input, due to catcode madness. +% (We could simplify/remove this next time, I think.) +\def\CDref#1#2{\texttt{#1}} +% +% \OnCD is currently for any other reference to a file or directory in +% the distribution. PDF readers only open .pdf files, though, so we +% should change this to only use \href for those. Or more likely use +% different macros in the source. +\def\OnCD#1{\href{../../../../#1}{\path{#1}}} +% +% \href incorrectly appends .pdf to anything without an extension; these +% definitions using \hyper@linkurl do not, but they fail for .pdf +% references -- which are the only ones that work anyway. So this is +% useless, in practice. +%\def\CDref#1#2{\hyper@linkurl{#2}{../../../../#1}} +%\def\OnCD#1{\hyper@linkurl{\path{#1}}{../../../../#1}} + +% GUI menu/button/tab sequence: +\def\guiseq#1{\textsf{#1}} +\def\arw{\unskip$\rightarrow$\ignorespaces} +% +% Special names. +\def\dpi{$\,$dpi\xspace} +\def\bs{{\protect\normalfont\ttfamily\char'134}} +\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} +\def\Q#1{\par\vskip6pt\leftline{#1}\par} +\def\hyph{-} +% +% many abbreviations. +\newcommand{\CS}{$\mathcal{C}\kern-.1667em\lower.5ex% + \hbox{$\mathcal{S}$}\kern-.075em $} +\def\AFMtoTFM{\cmdname{AFM2TFM}\null} +\def\bv{\emph{Baskerville}} +\let\BV=\bv +\def\Dash{\unskip\nobreak\thinspace---\thinspace\ignorespaces} +\def\dvicopy{\cmdname{dvicopy}} +\def\dvidvi{\cmdname{dvidvi}} +\def\dvips{\cmdname{dvips}} +\def\eTeX{$\varepsilon$-\TeX} +\def\fpTeX{\textrm{fp}\TeX\xspace} +\def\GFtoDVI{\cmdname{GFtoDVI}\null} +\def\GFtoPK{\cmdname{GFtoPK}\null} +\def\GFtype{\cmdname{GFtype}} +\def\GUI{\acro{GUI}\xspace} +\def\KPS{Kpathsea} +\def\La{La} +\def\OMEGA{$\Omega$} +\def\OzMF{OzMF} +\def\OzMP{OzMP} +\def\OzTeX{O\kern-.03em z\kern-.15em\TeX} +\def\p.{p.\,} +\def\PKtype{\cmdname{PKtype}} +\def\PLtoTF{\cmdname{PLtoTF}\null} +\def\ProTeXt{Pro\TeX t} +\def\teTeX{\textrm{te}\TeX\xspace} +\def\TeXLive{\TeX{} Live\xspace} +\def\TFtoPL{\cmdname{TFtoPL}\null} +\def\TK{\TeX\ Collection} +\let\TL=\TeXLive +\def\TypeI{Type~1} +\def\VFtoVP{\cmdname{VFtoVP}\null} +\def\VPtoVF{\cmdname{VPtoVF}\null} +\def\Thanh{H\`an~Th\ifx % get Unicode char in tex4ht's HTML output + \HCode\UnDef\^e\llap{\raise 0.5ex\hbox{\'{}}}\else + \HCode{\string&\#x1EBF;}\fi~Th\`anh} +\def\XEmTeX{\textrm{XEm}\TeX\xspace} +\def\XEmacs{\textrm{XEmacs}\xspace} +\def\XeTeX{Xe\TeX\xspace} +\def\Webc{Web2C} +\providecommand*{\CD}{\acro{CD}\xspace} +\providecommand*{\CTAN}{\acro{CTAN}\xspace} +\providecommand*{\DVD}{\acro{DVD}\xspace} +\providecommand*{\GNU}{\acro{GNU}\xspace} +\providecommand*{\HTML}{\acro{HTML}\xspace} +\providecommand*{\MacOSX}{Mac\,\acro{OS\,X}\xspace} +\providecommand*{\PS}{Post\-Script\xspace} +\providecommand*{\TDS}{\acro{TDS}\xspace} +\providecommand*{\dvi}{\acro{DVI}\xspace} +\providecommand*{\web}{\texttt{WEB}\xspace} + +% Include an image. +% #1 - name of image (pictures/#1.jpg, always .jpg please) +% #2 - bb for html +% #3 - width for TeX +% +\def\tlimage#1#2#3{% + \ifnum \Status=2 % html, want relative path in output + \includegraphics[#2]{../../general/texlive-common/pictures/#1.jpg} + \else % not html, handled by TEXINPUTS in Makefile + \includegraphics[width=#3]{pictures/#1.jpg} + \fi + \\[5mm] +} + +\def\tlpng#1#2{% + \ifnum \Status=2 % html, want relative path in output + \includegraphics[bb=0 0 1 1]{#1.png}% + \else % not html, handled by TEXINPUTS in Makefile + \includegraphics[width=#2]{#1.png}% + \fi +} + +% +% description-like environment that uses tt instead of bf, and doesn't +% go to the left margin. Without the \hfil, get an underfull box. +% Don't know why \descriptionlabel doesn't. +% +\newenvironment{ttdescription} + {\begin{list}{label must be supplied}{% + \itemsep=0pt % these lists tend to have short descriptions + \parindent=0pt + \let\makelabel=\ttdescriptionlabel}}% + {\end{list}} +\newcommand*\ttdescriptionlabel[1]{\hspace\labelsep + \normalfont\ttfamily #1\hfil} +% +% Likewise, for commands using sans serif. +\newenvironment{cmddescription} + {\begin{list}{label must be supplied}{% + \itemsep=0pt + \let\makelabel=\cmddescriptionlabel}}% + {\end{list}} +\newcommand*\cmddescriptionlabel[1]{\hspace\labelsep + \normalfont\sffamily #1\hfil} + +% General squeezed itemize. +\newenvironment{itemize*}% + {\begin{itemize}% + \setlength{\itemsep}{0pt}% + \setlength{\parskip}{0pt}}% + {\end{itemize}} + +\newsavebox{\wbox} +\newenvironment{warningbox} + {\begin{lrbox}{\wbox} + \begin{minipage}{.95\textwidth}} + {\end{minipage}\end{lrbox}\fbox{\usebox{\wbox}}} +% +% lrbox is used as a representation marking. I changed it to +% lrBox in tne source file, to get closer to logical marking +\newsavebox{\mylrbox} +\newenvironment{lrBox} + {\begin{lrbox}{\mylrbox}} + {\end{lrbox}} + + +% emacs-page output setup +% +\ifx \HCode\UnDef + \providecommand{\Status}{0}% running TeX +\else + \providecommand{\Status}{2}% running TeX4ht +\fi +%\typeout{Status is \Status} +% +\newif\ifSingleColumn +% +% By default, we won't be creating hyperlinks. +\def\href#1#2{#2} +\def\hypertarget#1#2{} +\def\email#1{\href{mailto:#1}{\path{#1}}} % \path comes from url +% +\definecolor{hypercolor}{rgb}{0.5,0.0,0.5} % purplish external links. +% +% +\ifcase\Status + % \Status = 0 + \typeout{TeX Live documentation in DVI format} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 1 + \typeout{TeX Live documentation in PDF format} + \RequirePackage[breaklinks, + colorlinks,linkcolor=hypercolor,citecolor=hypercolor, + urlcolor=hypercolor,filecolor=hypercolor, + bookmarksopen, + %pdfstartview={FitBH -320000}, % fails with acrobat7 + hyperindex] + {hyperref} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 2 + \typeout{TeX Live documentation in HTML format} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + % read our config file, live4ht.cfg; q.v., for more definitions. + % hyperref load must come after the tex4ht load. + \RequirePackage[live4ht]{tex4ht} + \RequirePackage[tex4ht]{hyperref} \hyperlinkfileprefix{} + % definitions need simplifying for TeX4ht to make relative paths work. + \def\CDref#1#2{\href{../../../../#1}{#2}} + \def\OnCD#1{\href{../../../../#1}{#1}} + \or + % \Status = 3 + \typeout{TeX Live documentation as a Baskerville issue} + \@ifundefined{Fonts}% + {\RequirePackage{ae}}% + {\RequirePackage[T1]{\Fonts}} + \RequirePackage{bvoutln}% outline of baskerville + \SingleColumnfalse + \RequirePackage{multicol} + \or + % \Status = 4 + \typeout{TeX Live documentation as a TUB article} + \@ifundefined{Fonts}% + {\RequirePackage{ae}}% + {\RequirePackage[T1]{\Fonts}} + \SingleColumnfalse + \newenvironment{multicols}[1]{}{} +\fi +% +\ifnum \Status=4 +\else + \RequirePackage{texnames} + \providecommand\TeXXeT{\TeX-{}-% + \kern-.1emX\kern-.125em\lower.5ex\hbox{E}\kern-.1667emT\@} + \def\MP{MetaPost} + \let\mf\MF + \newcommand\ConTeXt{C\kern-.0333emon\-\kern-.0667em\TeX\kern-.0333emt} + \newcommand\MIKTEX{MiK\kern-.025em \TeX}% per www.miktex.org + % from pictex.tex: + \ifx\PiC\undefined \def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC} \fi + \ifx\PiCTeX\undefined \def\PiCTeX{\PiC\kern-.11em\TeX} \fi +\fi +% +% hacking at sections etc., to pay attention to baskerville status +\newcommand{\@condend@multicols}{% + \ifSingleColumn + \else + \def\@tempa{multicols}% + \ifx\@tempa\@currenvir + \end{multicols}% + \fi + \fi +} +\let\Section\section +\renewcommand{\section}{% + \@ifstar + {\Section*}% + {% + \@condend@multicols + \@dblarg\@full@section + }% +} +\def\@full@section[#1]#2{% + \Section[#1]{#2}% + \ifSingleColumn\else\begin{multicols}{2}\fi +} +\let\SubSection\subsection +\renewcommand{\subsection}{% + \@ifstar{\SubSection*}% + {% + \@condend@multicols + \@dblarg\@full@subsection + } +} +\def\@full@subsection[#1]#2{% + \SubSection[#1]{#2}% + \ifSingleColumn\else\begin{multicols}{2}\fi +} + +% calm things down a bit if we're in a multiple-column version +\ifSingleColumn +\else + \def\@listI{\leftmargin\leftmargini + \parsep \z@ + \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ + \itemsep \z@ \@plus .1\p@ + } + \let\@listi\@listI + \@listi + \def\@listii{\leftmargin\leftmarginii + \labelwidth\leftmarginii\advance\labelwidth-\labelsep + \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ + \parsep \z@ + \itemsep \z@ \@plus .1\p@ + } + \def\@listiii{\leftmargin\leftmarginiii + \labelwidth\leftmarginiii\advance\labelwidth-\labelsep + \topsep 1\p@ \@plus 1\p@ \@minus 1\p@ + \parsep \z@ + \partopsep \z@ + \itemsep \topsep + } + \def\@listiv{\leftmargin\leftmarginiv + \labelwidth\leftmarginiv\advance\labelwidth-\labelsep + } + \def\@listv{\leftmargin\leftmarginv + \labelwidth\leftmarginv\advance\labelwidth-\labelsep + } + \def\@listvi{\leftmargin\leftmarginvi + \labelwidth\leftmarginvi\advance\labelwidth-\labelsep + } +\fi +% +% array package stuff +\def\arraybackslash{\let\\=\@arraycr} +\newcolumntype{P}[1]{>{\raggedright\arraybackslash}p{#1}} +% +% shaded rows (using facilities of colortbl) +% +\definecolor{pale}{gray}{.9} +\newcount\colrow +\gdef\RowColor{pale} +\def\SetRowColor{% + \rowcolor{\RowColor}% + \global\advance\colrow by1\relax + \ifodd\colrow + \gdef\RowColor{pale}% + \else + \gdef\RowColor{white}% + \fi +} +% redefine to hack up a reference even though we don't need it... +\renewcommand\@bibitem[1]{\if@filesw \immediate\write\@auxout + {\string\bibcite{#1}{?}}\fi\ignorespaces} +% +% \unknownTeXlive is a dummy texlive entry for the biblio +\newcommand\unknownTeXlive[2][\relax]{\textbf{\textsc{unknown}}% + \global\@all@unknown\expandafter{\the\@all@unknown{#2}}% +} +\newtoks\@all@unknown +\global\@all@unknown{} +\AtEndDocument{\@message@unknowns} +\def\@message@unknowns{\edef\@tempa{\the\@all@unknown}% + \ifx\@tempa\@empty + \else + \def\@tempa{*** TeX live package location of }% + \expandafter\@output@unknowns\the\@all@unknown\@empty + \fi +} +\def\@output@unknowns#1{\edef\@tempb{#1}% + \ifx\@tempb\@empty + \typeout{ unknown}% + \else + \message{\@tempa#1,}% + \def\@tempa{}% + \expandafter\@output@unknowns + \fi +} + + +% Silence font warnings about no bold typewriter in LM. +\def\@font@warning#1{}% + +% Silence hyperref warnings about \kern. +\def\HyPsd@Warning#1{}% + +\endinput diff --git a/Master/texmf/doc/texlive/source/texlive-pl/texlive-pl.tex b/Master/texmf/doc/texlive/source/texlive-pl/texlive-pl.tex new file mode 100644 index 00000000000..0378da6518b --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-pl/texlive-pl.tex @@ -0,0 +1,3335 @@ +% iso8859-2 +% $Id: live.tex, v. 36 2008/08/17 +% TeX Live documentation. +% Originally written by Sebastian Rahtz and Michel Goossens, +% now maintained by Karl Berry and others. +% Polish translation and additions by Staszek Wawrykiewicz et al. +% Public domain. +% ---- +% UWAGA dla recenzentów/t³umaczy: %%! to moje komentarze (StaW) +\documentclass{article} +\let\tldocenglish=0 % for live4ht.cfg +\def\La{La} +\let\textsl\textit +\usepackage{tex-livep} +\usepackage{polski} %% for PL +\usepackage[latin2]{inputenc} %% for PL +\exhyphenpenalty=10000 %% for PL +\def\Dash{---} +\widowpenalty=10000 +\clubpenalty=10000 +%% redefined MF logo! %% for PL +%\def\MF{\textlogo{META}\-\textlogo{FONT}} %% for PL +%\def\MP{\textlogo{META}\-\textlogo{POST}} %% *** TP *** +\def\shac{\char178} % for PL + qtmr (HTML) +\def\aac{\char225} % for PL + qtmr (HTML) +\def\iac{\char237} % for PL + qtmr (HTML) +\renewcommand{\samp}[1]{,,\texttt{#1}''} %% for PL +%% Polish style for sections +\makeatletter +\renewcommand{\@seccntformat}[1]{% + \csname the#1\endcsname.\hspace{.5em}} %% +\def\numberline#1{\hb@xt@\@tempdima{#1.\hfill}} +\makeatother +\hyphenation{tex-basic la-tex pdf-tex} +%% ----- +\begin{document} + +\title{{\huge \textit{Przewodnik po \protect\TL}\\[1ex]} + {\LARGE \textsf\TL{} 2008} +} + +\author{Redakcja: Karl Berry \\[3mm] + \url{http://tug.org/texlive/} +} + +\date{Sierpieñ 2008} + +\maketitle + +\begin{multicols}{2} +\tableofcontents +%\listoftables +\end{multicols} +%-------------------------- +\section{Wstêp}\label{sec:intro} + +\subsection{\TeX\ Live i \TeX\ Collection} +Niniejsza dokumentacja opisuje oprogramowanie \TL{} -- +dystrybucjê \TeX-a wraz z~programami pomocniczymi, dostêpn± dla +systemów \acro{GNU}/Linux, ró¿nych wersji Unix (w~tym \MacOSX{}) +oraz Windows. + +\TL{} mo¿na ¶ci±gn±æ z~sieci b±d¼ otrzymaæ na p³ytce \DVD \TK{}, dostarczanej +swoim cz³onkom przez Grupy U¿ytkowników Systemu \TeX{} . +Czê¶æ \ref{sec:tl-coll-dists} omawia pokrótce zawarto¶æ tej p³ytki. +Zarówno \TL{}, jak i \TK{} powsta³y dziêki zbiorowemu wysi³kowi Grup. +W~tym dokumencie omówimy g³ównie sam± dystrybucjê \TL. + +\TL{} zawiera skompilowane programy: \TeX{}, \LaTeXe{}, \mbox{\MF}, \MP, +\BibTeX{} i~wiele innych oraz bogaty zestaw pakietów makr o~wielorakim +zastosowaniu, a tak¿e fonty i~dokumentacje. Wszystko to umo¿liwia sk³ad +publikacji w~wielu jêzykach. + +Pakiety zawarte w~\TL{} s± regularnie aktualizowane z serwerów \acro{CTAN}: +\url{http://www.ctan.org}. + +Lista najwa¿niejszych zmian dokonanych w~tej edycji \TL{} +znajduje siê w~czê¶ci~\ref{sec:tlcurrent}, na str.~\pageref{sec:tlcurrent}. + %w~czê¶ci~\ref{sec:history}, na str.~\pageref{sec:history}. + +Nie opisujemy tu, czym jest system \TeX{}, a~jedynie kwestiê instalacji +i~konfiguracji oprogramowania \TL. +Pocz±tkuj±cy u¿ytkownicy mog± siê zapoznaæ z~podstawowymi pojêciami +np. w~artykule {\it Przewodnik po systemie \TeX\/}: +\OnCD{texmf-doc/doc/polish/tex-virtual-academy-pl/cototex.html}. + +\subsection{Obs³ugiwane systemy operacyjne} +\label{sec:os_support} + +\TL{} zawiera oprogramowanie dla wielu platform linuksowych i uniksowych, +w~tym \MacOSX. Za³±czone pliki ¼ród³owe pozwalaj± te¿ na instalacjê +na dodatkowych platformach. + +Spo¶ród systemów Windows obs³ugiwane s± tylko wersje 2000 i nowsze. +Zaniechano wsparcia dla Windows~9x, ME oraz NT, których obs³uga by³a bardzo +pracoch³onna (w~porównaniu z~Linux/Unix). Wprawdzie brak jest +oprogramowania na wersje 64-bitowe, ale aplikacje 32-bitowe powinny na nich +dzia³aæ. + +W czê¶ci \ref{sec:tl-coll-dists} omówiono alternatywne dystrybucje, +przeznaczone dla Windows oraz \MacOSX. + +\subsection{Podstawy instalacji \protect\TL{}} +\label{sec:basic} + +\TL{} mo¿na zainstalowaæ z~p³ytki \DVD{} lub internetu. Program instalacyjny +jest niewielki i~pozwala pobraæ z sieci wszystkie potrzebne pakiety. +Jest to wygodne, gdy potrzebujemy jedynie czê¶ci oprogramowania \TL. + +Posiadaj±c p³ytkê \DVD{}, mo¿emy nie tylko zaistalowaæ \TL{} na twardym dysku, +ale i~uruchomiæ programy bezpo¶rednio z~niej (a~nawet z~obrazu +\DVD{}, je¶li nasz system pozwala na jego zamontowanie). + +Szczegó³owy opis instalacji \TL{} znajduje siê w dalszych rozdzia³ach +tego dokumentu, tu podamy jedynie skrócony przepis: + +\begin{itemize*} + \item program instalacyjny \filename{install-tl} mo¿e dzia³aæ w~dwóch +trybach: tekstowym (domy¶lnym dla Unix/Linux) i~graficznym (tzw. \GUI, +domy¶lnym dla Windows); tryb mo¿na wymusiæ podaj±c parametr \code{-gui} +b±d¼ \code{-no-gui}; + +\item jednym z~instalowanych programów jest \prog{tlmgr} (mened¿er \TL{}), +który równie¿ mo¿na uruchomiæ w~trybie tekstowym b±d¼ graficznym; pozwala +on doinstalowaæ lub usun±æ pakiety, aktualizowaæ je z~sieci, a tak¿e +wykonaæ ró¿ne czynno¶ci konfiguracyjne. + +\end{itemize*} + +\subsection{Dostêpna pomoc} +\label{sec:help} + +Spo³eczno¶æ \TeX-owa jest bardzo aktywna i~pomocna, st±d te¿ wiêkszo¶æ +powa¿nych zapytañ nie pozostaje bez odpowiedzi. Przed zadaniem +pytania warto je uprzednio dobrze przemy¶leæ i~sformu³owaæ, poniewa¿ +respondenci to wolontariusze, w¶ród których znale¼æ siê mog± mniej lub +bardziej do¶wiadczeni u¿ytkownicy. +(Je¶li preferujemy komercyjne wsparcie techniczne, mo¿emy zamiast +\TL{} zakupiæ system u~jednego z~dostawców, których listê mo¿na znale¼æ +na \url{http://tug.org/interest.html#vendors}.) + +Oto lista ¼róde³ pomocy, w~kolejno¶ci przez nas rekomendowanej: + +\begin{description} +\item [\TeX{} \acro{FAQ}] \TeX-owy \acro{FAQ} jest obszernym zbiorem +odpowiedzi na wszelkie rodzaje pytañ, od najprostszych do najbardziej +zaawansowanych. Jest on za³±czony na \TL{} w~katalogu +\OnCD{texmf-doc/doc/english/FAQ-en}, +a~tak¿e dostêpny w~sieci: \url{http://www.tex.ac.uk/faq}. Proponujemy +zajrzeæ najpierw tam. Uruchomiono te¿ serwis \acro{FAQ} +w~jêzyku polskim: \url{http://faq.gust.org.pl}. + +\item [\TeX{} Catalogue] Je¶li poszukujemy konkretnego pakietu, fontu, +programu itp., to polecamy \TeX{} Catalogue. Jest to obszerne zestawienie +wszelkich pakietów dotycz±cych \TeX-a. Patrz: + %\OnCD{texmf-doc/doc/english/catalogue} lub + \url{http://www.ctan.org/help/Catalogue/}. + +\item [\TeX{} Web Resources] Strona \url{http://tug.org/interest.html} +zawiera wiele odsy³aczy, w~szczególno¶ci do ksi±¿ek, podrêczników +i~artyku³ów po¶wiêconych wszelkim aspektom pracy z~systemem \TeX. + +\item [archiwa pomocy] Dwa g³ówne fora pomocy to grupa +Usenet \url{news:comp.text.tex} oraz lista dyskusyjna +\email{texhax@tug.org}. Warto przeszukaæ archiwa list dyskusyjnych, +zawieraj±ce mnóstwo pytañ i odpowiedzi zbieranych przez wiele lat: +\url{http://groups.google.com/group/comp.text.tex/topics} oraz +\url{http://tug.org/mail-archives/texhax}. Nie zaszkodzi +skorzystanie z~wyszukiwarki, np. \url{http://www.google.com}. + +\item [wysy³anie pytañ] Je¶li nadal nie znajdujemy rozwi±zania problemu, +to mo¿emy wys³aæ pytanie do \dirname{comp.text.tex}, korzystaj±c z~Google, +czytnika wiadomo¶ci b±d¼ pisz±c list na adres \email{texhax@tug.org}. +Przedtem jednak \emph{nale¿y} siê zapoznaæ z~poradami dotycz±cymi sposobu +zadawania pytañ, zawartymi w~\acro{FAQ}: +\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. +Polscy u¿ytkownicy maj± do dyspozycji listê dyskusyjn± GUST (polskiej Grupy +U¿ytkowników Systemu \TeX); informacje o niej +znajdziemy na stronie \url{http://www.gust.org.pl}. + +\item [wsparcie \TL{}] Gdy chcemy zg³osiæ b³±d b±d¼ sugestie +i~komentarze dotycz±ce dystrybucji \TL{}, instalacji lub dokumentacji, +mamy do dyspozycji listê dyskusyjn± \email{tex-live@tug.org}. Je¶li kwestia +dotyczy konkretnego programu (pakietu makr itp.) z~\TL{}, +to lepiej jednak skierowaæ pytanie do osoby opiekuj±cej siê danym programem +lub na specjalistyczn± listê dyskusyjn±. + +\end{description} + +Druga strona medalu to pomaganie tym, którzy maj± problemy. Zarówno +\dirname{comp.text.tex}, jak i~\code{texhax} (oraz lista dyskusyjna GUST) +s± otwarte dla ka¿dego, +tak wiêc zapraszamy do w³±czenia siê, czytania wiadomo¶ci i~pomagania +innym w~miarê w³asnych mo¿liwo¶ci. Witamy w¶ród u¿ytkowników +systemu \TeX! + +%-------------------------- +\section{Struktura \protect\TeX\protect\ Live}\label{sec:struct-tl} + +Omówimy tutaj strukturê i~zawarto¶æ dystrybucji \TL{}, a~tak¿e \TK{} -- +p³ytki \DVD, w~sk³ad której wchodzi \TL. + +\subsection{The \protect\TeX\protect\ Collection: \TL, pro\TeX{}t, Mac\TeX} +\label{sec:tl-coll-dists} + +The \TK{} \DVD{} zawiera: + +\begin{description} + +\item [\TL] kompletny system na \acro{DVD}, z mo¿liwo¶ci± uruchamiania +bezpo¶rednio z~p³yty b±d¼ instalacji na twardym dysku; + +\item [Mac\TeX] dla systemu \MacOSX; posiada on w³asny program instalacyjny +i~dodatkowe programy dla tego systemu; strona domowa projektu: +\url{http://www.tug.org/mactex/}; + +\item [pro\TeX{}t] dystrybucja dla Windows, oparta na dystrybucji \MIKTEX{}, +rozszerzonej o~dodatkowe narzêdzia; ca³kowicie niezale¿na od \TL; +\ProTeXt\ posiada w³asny, ³atwy w~obs³udze program instalacyjny; + %i~równie¿ mo¿e byæ uruchamiany bezpo¶rednio z~p³ytki. + strona domowa projektu: \url{http://tug.org/protext}; + +\item [CTAN] zrzut zawarto¶ci archiwów \CTAN{}; + +\item [\texttt{texmf-extra}] katalog z wybranymi pakietami dodatkowymi. + +\end{description} + +\CTAN, \pkgname{protext}, i~\texttt{texmf-extra} nie spe³niaj± przyjêtych dla +\TL{} wymogów dotycz±cych swobody kopiowania, wobec tego nale¿y ten fakt +uwzglêdniæ przy redystrybucji b±d¼ modyfikacji zawarto¶ci wymienionych +katalogów. + +\subsection{G³ówne katalogi \TL} +\label{sec:tld} + +Poni¿ej wymieniono wa¿niejsze podkatalogi g³ównego katalogu dystrybucji \TL. +Na p³ytce \pkgname{live} \DVD ca³a dystrybucja \TL{} zosta³a +umieszczona w katalogu \dirname{texlive}, nie za¶ w~katalogu g³ównym +(poni¿ej traktujemy go jako katalog g³ówny we wszystkich odniesieniach +do \TL). + +\begin{ttdescription} +\item[bin] skompilowane programy \TeX-owe, zorganizowane w~podkatalogach + wed³ug platform systemowych; + +\item[readme.html] krótki wstêp z~u¿ytecznymi odno¶nikami; + +\item[source] ¼ród³a wszystkich programów, w³±cznie z~g³ównymi dystrybucjami + \Webc{} \TeX-a i~\MF{}-a; + +\item[support] ró¿ne programy pomocnicze zwi±zane z~\TeX-em, które \emph{nie} + s± domy¶lnie instalowane; + dla u¿ytkowników systemów Windows do³±czono ponadto szereg programów + (edytory, ,,shelle TeX-owe''), których zwykle brak w~typowej instalacji + Windows (programy te mog± byæ szczególnie przydatne dla pocz±tkuj±cych); + +\item[texmf] drzewo katalogów plików pomocniczych i~dokumentacji dla + \emph{programów} (patrz: \texttt{TEXMFMAIN} w~nastêpnej czê¶ci); + +\item[texmf-dist] g³ówne drzewo katalogów formatów i~pakietów (zawiera makra, + fonty i~dokumentacje; patrz: \texttt{TEXMDIST} w~nastêpnej czê¶ci); + +\item[texmf-doc] drzewo samodzielnych dokumentacji (m.in. podrêczniki itp.), + niezwi±zane z~konkretnymi pakietami, zorganizowane wed³ug jêzyków. + +\item[tlpkg] skrypty, programy i~inne dane potrzebne do instalacji; + katalog zawiera tak¿e ,,prywatne'' dla \TL{} kopie systemów Perl i~Ghostscript + dla Windows (nie koliduj± one z~posiadanymi przez u¿ytkownika podobnymi + programami i~dzia³aj± tylko w~ramach instalacji); poza tym do³±czono + szybki i~wygodny program do podgl±du plików postscriptowych (a~tak¿e PDF) + -- PS\_View dla Windows. +\end{ttdescription} + +Prócz podkatalogów wymienionych powy¿ej, katalog g³ówny zawiera skrypty +instalacyjne oraz pliki \filename{README}, w~formacie tekstowym lub HTML, +w~kilku jêzykach (równie¿ polskim). + +Katalog \dirname{texmf-doc} zawiera, jak wspomniano wy¿ej, dokumentacje +ogólne, np. podrêczniki (tak¿e po polsku). Dokumentacje programów (man, info, +tak¿e w~formacie PDF) znajduj± siê w~katalogu +\dirname{texmf/doc}, za¶ dokumentacje pakietów makr, fontów i~formatów +w~katalogu \dirname{texmf-dist/doc}. W~odszukaniu konkretnej +dokumentacji w~dowolnym z~wymienionych katalogów mog± pomóc +programy \cmdname{texdoc} lub \cmdname{texdoctk}. Pomocnym mo¿e te¿ byæ +plik \OnCD{doc.html}, który znajdziemy w~g³ównym katalogu. + +Niniejsza dokumentacja w~kilku jêzykach znajduje siê w katalogu +\dirname{texmf-doc}: + +\begin{itemize*} +\item{uproszczony chiñski:} \OnCD{texmf-doc/doc/chinese/texlive-zh-cn} +\item{czeski/s³owacki:} \OnCD{texmf-doc/doc/czechslovak/texlive-cz} +\item{angielski:} \OnCD{texmf-doc/doc/english/texlive-en} +\item{francuski:} \OnCD{texmf-doc/doc/french/texlive-fr} +\item{niemiecki:} \OnCD{texmf-doc/doc/german/texlive-de} +\item{polski:} \OnCD{texmf-doc/doc/polish/texlive-pl} +\item{rosyjski:} \OnCD{texmf-doc/doc/russian/texlive-ru} +\end{itemize*} + +\subsection{Predefiniowane drzewa katalogów texmf} +\label{sec:texmftrees} + +W tej czê¶ci wymieniono wszystkie u¿ywane przez system, predefiniowane zmienne +specyfikuj±ce drzewa katalogów texmf, omówiono te¿ ich przeznaczenie. +Uruchomiaj±c polecenie \texttt{texconfig conf}, zobaczymy warto¶ci tych +zmiennych, dziêki czemu ³atwo ustalimy, które katalogi w~naszej instalacji s± +przypisane do konkretnych zmiennych. + +\begin{ttdescription} +\item [TEXMFMAIN] Drzewo katalogów zawieraj±ce podstawowe dla + dystrybucji elementy systemu, jak skrypty (np. \verb+web2c/mktexdir+), + i~inne pliki pomocnicze oraz ich dokumentacjê (nie zawiera zatem + pakietów makr ani formatów). +\item [TEXMFDIST] Drzewo katalogów zawieraj±ce pakiety makr, fontów itp., + tak jak s± one oryginalnie dystrybuowane; drzewo to mo¿e byæ + wspó³dzielone z~dowoln± dystybucj±. +\item [TEXMFLOCAL] Drzewo katalogów, które administratorzy mog± wykorzystaæ + do przechowywania lokalnych makr, fontów itp., dostêpnych dla wszystkich + u¿ytkowników serwera. +\item [TEXMFHOME] Drzewo katalogów dla prywatnych makr, fontów itp. + u¿ytkownika. Rozwiniêcie tej zmiennej zale¿y domy¶lnie od warto¶ci przypisanej + zmiennej systemowej \verb+$HOME+ (w~Windows \verb+%USERPROFILE%+). +\item [TEXMFCONFIG] Drzewo katalogów wykorzystywane przez narzêdzia + \verb+texconfig+, \verb+updmap+ oraz \verb+fmtutil+ do przechowywania + danych konfiguracyjnych (domy¶lnie w~ramach \envname{TEXMFHOME}). +\item [TEXMFSYSCONFIG] Drzewo katalogów wykorzystywane przez narzêdzia + \verb+texconfig-sys+, \verb+updmap-sys+ oraz \verb+fmtutil-sys+ + do przechowywania danych konfiguracyjnych dla ca³ej instalacji. +\item [TEXMFVAR] Drzewo katalogów wykorzystywane przez \verb+texconfig+, + \verb+updmap+ i~\verb+fmtutil+ do przechowywania wygenerowanych plików + formatów i~map fontowych (domy¶lnie w~ramach \envname{TEXMFHOME}). +\item [TEXMFSYSVAR] Drzewo katalogów wykorzystywane przez + \verb+texconfig-sys+, \verb+updmap-sys+ oraz \verb+fmtutil-sys+, a~tak¿e + przez program \verb+tlmgr+ do przechowywania wygenerowanych plików + formatów i~map fontowych dla ca³ej instalacji. +\end{ttdescription} + + %Wiêcej informacji na temat \texttt{texconfig} znajdziemy + %w~czê¶ci~\ref{sec:texconfig}, na str.~\pageref{sec:texconfig}. + +\noindent +Domy¶lny uk³ad katalogów: +\begin{description} + \item[ogólnosystemowy katalog instalacji] mo¿e zawieraæ kilka wydañ \TL{}: + \begin{ttdescription} + \item[2007] poprzednie wydanie, + \begin{ttdescription} + \item [...] + \end{ttdescription} + \item[2008] wydanie aktualne: + \begin{ttdescription} + \item [bin] ~ + \begin{ttdescription} + \item [i386-linux] programy dla \GNU/Linux + \item [...] + \item [universal-darwin] programy dla \MacOSX + \item [win32] programy dla Windows + \end{ttdescription} + \item [texmf] okre¶lany zmienn± \envname{TEXMFMAIN} + \item [texmf-dist] \envname{TEXMFDIST} + \item [texmf-doc] \envname{TEXMFDOC} + \item [texmf-var] \envname{TEXMFSYSVAR} + \item [texmf-config] \envname{TEXMFSYSCONFIG} + \end{ttdescription} + \item [texmf-local] \envname{TEXMFLOCAL}, katalog zachowywany + od wydania do wydania, + \end{ttdescription} + \item[katalog domowy u¿ytkownika] (\texttt{\$HOME} lub + \texttt{\%USERPROFILE\%}) + \begin{ttdescription} + \item[.texlive2007] prywatne pliki konfiguracyjne + poprzedniego wydania: + \item[.texlive2008] prywatne pliki konfiguracyjne + dla bie¿±cego wydania: + \begin{ttdescription} + \item [texmf-var] \envname{TEXMFVAR} + \item [texmf-config] \envname{TEXMFCONFIG} + \end{ttdescription} + \item[texmf] \envname{TEXMFHOME} prywatne makra, fonty itp. + \end{ttdescription} +\end{description} + +\subsection{Rozszerzenia \protect\TeX-a} +\label{sec:tex-extensions} + +Standardowy \TeX{} zosta³ zamro¿ony, ale jest i~bêdzie w~przysz³o¶ci dostêpny +w~dystrybucji. \TL{} zawiera ponadto kilka wersji rozszerzonych +standardowego \TeX-a: + +\begin{description} +\item [\eTeX] wersja \label{text:etex} programu \TeX{}, w~której dodano + po¿yteczny zestaw nowych poleceñ wbudowanych + (dotycz±cych g³ównie rozwijania makr, leksemów znakowych, interpretacji + znaczników itp.) oraz rozszerzenie \TeXXeT{} dla sk³adu + od prawej do lewej. W~trybie domy¶lnym \eTeX{} jest w~100\% zgodny ze + standardowym programem \TeX. Wiêcej szczegó³ów mo¿na znale¼æ + w~\OnCD{texmf-dist/doc/etex/base/etex_man.pdf}. + +\item [pdf\TeX] program zawieraj±cy silnik \eTeX, umo¿liwiaj±cy +tworzenie plików zarówno w~formacie PDF, jak i~\dvi{}. Jest on domy¶lnym +programem dla wiêkszo¶ci formatów (prócz plain \TeX), nie ma wiêc obecnie +rozró¿nienia na ,,maszyny'' \textsf{pdftex} i \textsf{pdfetex}, jak to mia³o +miejsce w~poprzednich wersjach programów i~w~poprzednich dystrybucjach \TL. +Podrêczniki znajdziemy w~katalogu +\OnCD{texmf-dist/doc/pdftex/manual/pdftex-a.pdf}, +za¶ przyk³ad wykorzystania -- w~pliku +\OnCD{texmf-dist/doc/pdftex/manual/samplepdf/samplepdf.tex}. + +\item [Lua\TeX] docelowo sukcesor pdf\TeX-a, z~którym ma byæ zgodny wstecz. + Powinien tak¿e zast±piæ Aleph (patrz ni¿ej). Za³±czony +interpreter Lua (patrz strona domowa \url{http://www.lua.org/}) +pozwala na eleganckie rozwi±zanie wielu trudnych problemów \TeX-a. +Program \filename{texlua} ma funkcjonalno¶æ samodzielnego +interpretera Lua, co sprawia, ¿e jest u¿ywany w~\TL{} do wielu zadañ. +Patrz \url{http://www.luatex.org/} i~na \DVD{} +\OnCD{texmf-dist/doc/luatex/luatexref-t.pdf}. + +\item [Xe\TeX] umo¿liwia kodowanie tekstów w~Unicode oraz korzystanie +z~fontów OpenType (tak¿e tych dostêpnych w~systemie operacyjnym), +przy czym stosuje biblioteki obce, patrz +\OnCD{texmf-dist/doc/xetex/XeTeX-reference.pdf} lub +\url{http://scripts.sil.org/xetex}. + +\item [\OMEGA{} (Omega)] program, który pracuje wewnêtrznie ze znakami +kodowanymi 16-bitowo (Unicode), pozwalaj±c sk³adaæ jednocze¶nie +wiêkszo¶æ tekstów spotykanych na ¶wiecie. Wspomaga dynamicznie +³adowane tzw. ,,procesy t³umaczenia \OMEGA'' (\acro{OTP}), co pozwala +u¿ytkownikowi definiowaæ z³o¿one transformacje, wykonywane na dowolnych +strumieniach wej¶ciowych. Wiêcej szczegó³ów znale¼æ mo¿na na \DVD: +\OnCD{texmf-dist/doc/omega/base/doc-1.8.tex} (dokumentacja niezbyt aktualna; +sam program te¿ od dawna nie jest aktualizowany). + +\item [Aleph] ³±czy rozszerzenia \OMEGA\ i~\eTeX; powsta³ jako niezale¿ny +projekt z~potrzeby stabilnej ,,u¿ywalno¶ci'' programu Omega, w~sytuacji +gdy ten jest ci±gle w~fazie eksperymentalnej. Minimalna dokumentacja: +\OnCD{texmf-dist/doc/aleph/base}. + +\end{description} + +\subsection{Inne wa¿niejsze programy \protect\TL} + +Poni¿ej zestawiono inne najczê¶ciej u¿ywane programy dostêpne +w~dystrybucji \TL{}: + +\begin{cmddescription} + +\item[bibtex] tworzenie spisów bibliograficznych; + +\item[makeindex] tworzenie posortowanych skorowidzów; + +\item[dvips] konwersja \dvi{} do \PS{}; + +\item[xdvi] przegl±darka plików \dvi{} dla X~Window; + +\item[dvilj] sterownik dla drukarek HP LaserJet; + +\item [dv2dt, dt2dv] konwerter \dvi{} do/z tekstu ASCII; + +\item [dviconcat, dviselect] programy do manipulacji stronami w~plikach + \dvi{}; + +\item [dvipdfmx] konwersja \dvi{} do PDF, metoda alternatywna w~stosunku + do wspomnianego wy¿ej programu pdf\TeX{} (pakiety + \pkgname{ps4pdf} i~\pkgname{pdftricks} dostarczaj± kolejnych mo¿liwo¶ci); + +\item [psselect, psnup, \ldots] narzêdzia do manipulacji na plikach +postscriptowych; + +\item [lacheck] kontrola syntaktyki plików \LaTeX-owych; + +\item [texexec, texmfstart] programy uruchamiaj±ce dla Con\TeX{}t; + +\item [tex4ht] postprocesor dla \TeX-a konwersji do HTML i XML. + +\end{cmddescription} + +%%! zostawiam tê czê¶æ, choæ wylecia³a z wersji oryginalnej!!! 27.08.2003 + +\subsection[Pakiety i ich zestawy]{Pakiety i ich zestawy} +\label{packages} +Zawarto¶æ drzew \texttt{texmf} na \TL{} zosta³a do celów instalacji +zorganizowana w~szereg ,,zestawów'' (\emph{collections}), +z~których ka¿dy posiada zbiór ,,pakietów'' (\emph{packages}; jest ich obecnie +ponad 2500). Normalna instalacja pozwala u¿ytkownikowi skopiowaæ +z~\DVD{} na twardy dysk jeden lub wiêcej zestawów, mo¿na te¿ +zainstalowaæ jedynie pojedynczy pakiet. + +Zestawy pozwalaj± lepiej dobraæ instalowane sk³adniki, a~tak¿e okre¶liæ, +jakie jêzyki bêd± obs³ugiwane po instalacji. Najwa¿niejszy zestaw, wymagany +dla wiêkszo¶ci zastosowañ, to ,,basic''. Zestawy ,,latex'' +i~,,pdftex'' s± rekomendowane dla wiêkszo¶ci u¿ytkowników. Pozosta³e +zestawy s± opcjonalne. + +Oto dostêpne zestawy i~krótki opis ich zawarto¶ci: + +\begin{description} +\item[basic] podstawowe programy, pakiety makr i~fontów systemu \TeX{}, + pliki konfiguracyjne dla podstawowych sterowników; +\item[bibtexextra] dodatkowa, obszerna biblioteka stylów Bib\TeX-owych + i~bazy danych bibliograficznych (podstawowe style znajduj± siê w~zestawie + ,,basic''); +\item[chemistry] pakiety makr do sk³adu wzorów chemicznych; +\item[context] pakiet makr do Con\TeX{}t -- ,,dialektu'' \TeX-a + autorstwa Hansa Hagena; +\item[documentation] dodatkowe, u¿yteczne dokumentacje; +\item[etex] pliki pomocnicze dla programu e-\TeX; +\item[extrabin] ró¿ne programy pomocnicze; zestaw zawiera m.in. + programy i~makra dla systemu texinfo, programy do manipulacji na plikach + DVI itp.; +\item[fontbin] programy do konwersji plików fontowych oraz testowania + i~instalacji fontów (zestaw do tworzenia fontów wirtualnych, manipulacji + plikami .gf i~.pk, programy \texttt{mft}, \texttt{fontinst} itp.); +\item[fontsrecommended] obszerna biblioteka czê¶ciej u¿ywanych fontów + w~postaci ¼ród³owej (.mf) b±d¼ fontów obwiedniowych oraz pliki z~definicjami + i~stylami \LaTeX-a dla tych fontów; +\item[fontsextra] biblioteka ró¿nych rzadziej u¿ywanych fontów; +\item[formatsextra] pliki pomocnicze do generowania dodatkowych + ,,formatów'' (tj. obszerne zestawy makr s³u¿±ce do wstêpnego przetworzenia + i~utworzenia pliku \texttt{.fmt}); +\item[games] pakiety do prezentacji zapisu ró¿nych gier (szachy, + bryd¿ itp.); +\item[genericextra] obszerna biblioteka makr, trudnych do sklasyfikowania, + dzia³aj±cych z~ró¿nymi formatami (Plain, \LaTeX{} itp.); +\item[htmlxml] pakiety konwersji \LaTeX-a do XML/HTML oraz do sk³adu + dokumentów XML/SGML; +\item[lang\dots] wsparcie poszczególnych jêzyków; zestawy zawieraj± + wzorce przenoszenia wyrazów i~makra obs³ugi danych jêzyków, czasem te¿ + specyficzne fonty itp., przyk³adowo: + %\item[langarmenian] armeñski; +%\item[langcjk] pakiety CJK (obs³uga chiñskiego, japoñskiego i~koreañskiego); +%\item[langcroatian] chorwacki; +%\item[langcyrillic] fonty i makra do sk³adu cyrylic±; +%\item[langczechslovak] fonty i pakiety makr dla czeskiego i~s³owackiego; +%\item[langdanish] duñski; +%\item[langdutch] holenderski; +%\item[langfinnish] fiñski; +%\item[langfrench] francuski; +%\item[langgerman] niemiecki; +%\item[langgreek] grecki; +%\item[langhungarian] wêgierski; +%\item[langindic] wsparcie dla jêzyków indyjskich; +%\item[langitalian] w³oski; +%\item[langlatin] ³acina; +%\item[langmanju] jêzyk Manju; +%\item[langmongolian] mongolski; +%\item[langnorwegian] norweski; +%\item[langother] wzorce przenoszenia wyrazów dla innych jêzyków; +\item[langpolish] zawiera polskie pakiety: makra do tworzenia formatu MeX, + pakiety \texttt{polski}, \texttt{mwcls}, fonty i~makra dodatkowe, + przydatne dla polskich u¿ytkowników, dokumentacje w~jêzyku polskim; +%\item[langportuguese] portugalski; +%\item[langspanish] hiszpañski; +%\item[langswedish] szwedzki; +%\item[langtibetan] fonty i~wsparcie do sk³adu tybetañskiego; +%\item[langukenglish] angielski (brytyjski); +%\item[langvietnamese] wietnamski; +\item[latex] podstawowe pakiety \LaTeX-a; +\item[latexrecommended] rekomendowany zestaw czêsto u¿ywanych pakietów + dodatkowych; +\item[latex3] pakiety-,,zwiastuny'' \LaTeX3, dzia³aj±ce z~\LaTeXe; +\item[latexextra] bogaty wybór dodatkowych pakietów dla \LaTeX-a; +\item[mathextra] dodatkowe pakiety do sk³adu zaawansowanej matematyki; +\item[metapost] MetaPost i~pakiety do tworzenia rysunków z~u¿yciem + MetaFonta; +\item[music] makra do sk³adu nutowego; +\item[omega] rozszerzenie \TeX{}a autorstwa Johna Plaice'a i~Yannisa Haralambousa, dzia³aj±ce ze znakami kodowanymi 16-bitowo; +\item[pdftex] pliki pomocnicze dla pdf\TeX{}-a, wersji programu \TeX{} + tworz±cej pliki w~formacie PDF; +\item[pictures] pakiety do tworzenia diagramów i~innych obiektów graficznych; +\item[plainextra] dodatkowe biblioteki makr dla Plain \TeX; +\item[psutils] narzêdzia do manipulacji plikami \PS-owymi; +\item[publishers] pakiety makr pochodz±ce od ró¿nych wydawnictw; +\item[t1utils] narzêdzia do obs³ugi fontów w~formacie Type~1; +\item[texbooks] przyk³ady i~inne materia³y autorstwa D.E.~Knutha; +\item[ttfutils] narzêdzia do konwersji fontów True Type. +\end{description} +%-------------------------- +%%! koniec pozostawionej sekcji 27.08.2003 + +Plik \texttt{tlpdb/texlive.tlpdb} (wykorzystywany podczas instalacji) +zawiera spis wszystkich plików w~ka¿dym pakiecie. + +\subsection{Fonty w \protect\TL} +\label{sec:tl-fonts} + +\TL{} zawiera wiele wysokiej jako¶ci fontów skalowanych. Patrz +\url{http://tug.org/fonts} oraz +\OnCD{texmf-doc/doc/english/free-math-fonts-survey}. + +%==== + +\section{Instalacja} +\label{sec:install} + +\subsection{Start instalacji} +\label{sec:inst-start} + +Instalacjê \TL{} uruchamiamy skryptem \filename{install-tl} +(\filename{install-tl.bat} dla Windows) z~p³ytki \TK{} \DVD{} +b±d¼ dostêpnym w~pobranym z~sieci pakiecie instalacyjnym. + +\begin{description} +\item [Instalator z sieci:] z~archiwum \CTAN, z~katalogu +\dirname{systems/texlive/tlnet} +(\url{http://mirror.ctan.org/systems/texlive/tlnet} automatycznie +przekierowuje do najbli¿szej kopii \CTAN) nale¿y pobraæ plik +\filename{install-tl.zip} (dla Unix i Windows) lub znacznie mniejszy +\filename{install-unx.tar.gz} (tylko dla Unix). Po rozpakowaniu, +w~katalogu \dirname{install-tl/} znajdziemy skrypty instalacyjne +\filename{install-tl} i~\filename{install-tl.bat}. + +\item [\TeX{} Collection \DVD:] po zamontowaniu p³ytki nale¿y +zmieniæ katalog bie¿±cy na \dirname{texlive} (w~Windows program +instalacyjny powinien uruchomiæ siê automatycznie). \DVD{} otrzymamy +w ramach cz³onkowstwa w~dowolnej Grupie U¿ytkowników Systemu \TeX{} +(kontakt w Polsce \url{http://www.gust.org.pl}). +\end{description} + +Dalsze kroki omówiono dok³adniej w~nastêpnych czê¶ciach. + +\subsubsection{Unix} + +\noindent +Poni¿ej \texttt{>} oznacza prompt systemu; to, co wpisuje u¿ytkownik, +zaznaczono \Ucom{\texttt{pogrubieniem}}. W~systemach zgodnych z~Unix +nale¿y wykonaæ w~oknie terminala: +\begin{alltt} +> \Ucom{cd /path/to/installer} +> \Ucom{perl install-tl} +\end{alltt} +(mo¿na tak¿e uruchomiæ \Ucom{perl /path/to/installer/install-tl} lub +\Ucom{./install-tl}; w dalszej czê¶ci nie bêdziemy powtarzaæ wszelkich +mo¿liwych kombinacji). + +Do uruchomienia w~trybie graficznym (\GUI) wymagany jest w~systemie modu³ +\dirname{Perl/TK}: +\begin{alltt} +> \Ucom{perl install-tl -gui} +\end{alltt} + +Kompletny wykaz dostêpnych opcji otrzymamy, uruchamiaj±c: +\begin{alltt} +> \Ucom{perl install-tl -help} +\end{alltt} + +\textbf{Uwaga dotycz±ca uprawnieñ w Unix:} program instalacyjny +bêdzie respektowa³ aktualn± warto¶æ \code{umask}. +Je¶li wiêc chcemy, aby instalacja by³a dostêpna dla innych, to musimy +ustawiæ warto¶æ np. \code{umask 002}. Wiêcej informacji na temat +\code{umask} znajdziemy w~podrêcznikach systemu operacyjnego. + +\begin{figure}[tb] +\begin{boxedverbatim} +======================> TeX Live installation procedure <===================== + +=======> Note: Letters/digits in indicate menu items <======= +=======> for commands or configurable options <======= + + + Detected platform: Intel x86 with GNU/Linux + + binary systems: 1 out of 16 + + Installation scheme (scheme-full) + + Customizing installation scheme: + standard collections + language collections + 83 collections out of 84, disk space required: 1666 MB + + directories: + TEXDIR (the main TeX directory): + !! default location: /usr/local/texlive/2008 + !! is not writable, please select a different one! + TEXMFLOCAL (directory for site-wide local files): + /usr/local/texlive/texmf-local + TEXMFSYSVAR (directory for variable and automatically generated data): + /usr/local/texlive/2008/texmf-var + TEXMFSYSCONFIG (directory for local config): + /usr/local/texlive/2008/texmf-config + TEXMFHOME (directory for user-specific files): + ~/texmf + + options: + [ ] use letter size instead of A4 by default + [X] create all format files + [X] install macro/font doc tree + [X] install macro/font source tree + [ ] create symlinks in standard directories + + Install for running from DVD + +Other actions: + start installation to HD + help + quit + +Enter command: +\end{boxedverbatim} +\caption{G³ówny ekran instalatora w~trybie tekstowym (\GNU/Linux)}\label{fig:text-main} +\end{figure} + +\begin{figure}[tb] +\tlpng{install-w32-main}{\linewidth} +\caption{G³ówny ekran instalatora \GUI{} (Windows)}\label{fig:gui-main} +\end{figure} + +\subsubsection{Mac\,OS\,X} + +Jak wspomniano w czê¶ci \ref{sec:tl-coll-dists}, dla \MacOSX{} +przygotowano odrêbn± dystrybucjê Mac\TeX\ (\url{http://tug.org/mactex}), +w~tym wypadku nale¿y u¿yæ dedykowanego programu instalacyjnego, gdy¿ +zmienia on w~specyficzny sposób ustawienia systemu, w~szczególno¶ci pozwala +na ³atwe prze³±czanie pomiêdzy ró¿nymi dystrybucjami \TeX-a dla +\MacOSX: Mac\TeX, gw\TeX, Fink, MacPorts,\ldots + +Mac\TeX\ jest oparty na \TL{} i g³ówne drzewa katalogów s± dok³adnie te +same, jedynie dodawane s± katalogi ze specyficznymi dla systemu +\MacOSX\ dokumentacjami i~aplikacjami. + +\subsubsection{Windows} + +Gdy u¿ywamy instalatora pobranego z~sieci (b±d¼ program ten nie uruchamia siê +automatycznie po w³o¿eniu \DVD{} do napêdu), nale¿y uruchomiæ +\filename{install-tl.bat} (np. podwójnym klikniêciem myszy). +Mo¿na to uczyniæ tak¿e z~linii poleceñ -- gdy katalog zawieraj±cy ten plik +jest bie¿±cym, wystarczy uruchomiæ: +\begin{alltt} +> \Ucom{install-tl} +\end{alltt} + +W linii poleceñ mo¿na te¿ podaæ ¶cie¿kê do programu, np.: +\begin{alltt} +> \Ucom{D:\bs{}texlive\bs{}install-tl} +\end{alltt} +dla \TK\ \DVD, zak³adaj±c, ¿e \dirname{D:} jest napêdem \DVD. + +Instalacja w~trybie tekstowym wymaga podania: +\begin{alltt} +> \Ucom{install-tl -no-gui} +\end{alltt} + +Wszystkie dostêpne opcje wy¶wietlimy uruchamiaj±c: +\begin{alltt} +> \Ucom{install-tl -help} +\end{alltt} + +\subsubsection{Instalator w trybie tekstowym} + +Rysunek \ref{fig:text-main} przedstawia g³ówny ekran programu +\filename{install-tl} w~trybie tekstowym w~systemie Unix. +W tym trybie nie u¿ywamy ani klawiszy kursora, ani myszy, +tylko wy³±cznie klawiszy cyfr i~liter (uwaga: du¿e i ma³e litery s± +rozró¿niane!). Wybran± opcjê zatwierdzamy klawiszem Enter. +Instalator w~trybie tekstowym jest dlatego tak prosty, by dzia³a³ na +mo¿liwie wielu platformach, nawet wyposa¿onych w~ubogie biblioteki Perla +(dla Windows za³±czono taki w³a¶nie podzbiór dystrybucji Perla). + +\subsubsection{Instalator w trybie graficznym} + +Rysunek \ref{fig:gui-main} pokazuje instalator w~trybie graficznym +(zrzut ekranu w systemie Windows). + +\subsection{Podczas instalacji} +\label{sec:runinstall} + +Program instalacyjny jest z~za³o¿enia na tyle prosty, ¿e szczegó³owe +wyja¶nienia s± zbêdne. Podamy jednak kilka uwag dotycz±cych ró¿nych opcji +i~dostêpnych podmenu. + +\subsubsection{Menu: binary systems (tylko Unix)} +\label{sec:binary} + +\begin{figure}[tbh] +\begin{boxedverbatim} +Available sets of binaries: (Dostêpne zestawy programów dla:) +=============================================================================== + + a [ ] alpha-linux DEC Alpha with GNU/Linux + b [ ] amd64-freebsd x86_64 with FreeBSD + c [ ] hppa-hpux HP-UX + d [ ] i386-freebsd Intel x86 with FreeBSD + e [X] i386-linux Intel x86 with GNU/Linux + f [ ] i386-openbsd Intel x86 with OpenBSD + g [ ] i386-solaris Intel x86 with Sun Solaris + h [ ] mips-irix SGI IRIX + i [ ] powerpc-aix PowerPC with AIX + j [ ] powerpc-linux PowerPC with GNU/Linux + k [ ] sparc-linux Sparc with GNU/Linux + l [ ] sparc-solaris Sparc with Solaris + m [ ] universal-darwin universal binaries for MacOSX/Darwin + o [ ] win32 Windows + p [ ] x86_64-linux x86_64 with GNU/Linux +\end{boxedverbatim} +\caption{Wybór platformy (systemu operacyjnego)}\label{fig:bin-text} +\end{figure} + +Rysunek \ref{fig:bin-text} pokazuje (w~trybie tekstowym) wybór platformy +(systemu operacyjnego). +Domy¶lnie instalowane s± tylko programy dla bie¿±cej platformy, +ale menu to pozwala wybraæ tak¿e zestaw dla innych platform. Mo¿e byæ to +przydatne do instalacji na serwerze i~wspó³dzielenia zasobów w~sieci +dla ró¿nych systemów operacyjnych b±d¼ dla instalacji + %\textit{dual-boot} + dla kilku systemów na tej samej maszynie. + +\subsubsection{Wybór tego, co ma byæ zainstalowane} +\label{sec:components} + +\begin{figure}[tbh] +\begin{boxedverbatim} +Select a scheme: (Wybór schematu do instalacji:) +=============================================================================== + + a [ ] TeX Live basic scheme + b [ ] TeX Live scheme for ConTeXt + c [X] TeX Live full scheme + d [ ] GUST TeX Live scheme + e [ ] GUTenberg TeX Live scheme + f [ ] TeX Live medium scheme + g [ ] TeX Live minimal scheme + h [ ] TeX Live for Omega users + i [ ] teTeX scheme + j [ ] XML typesetting scheme +\end{boxedverbatim} +\caption{Menu: wybór schematów}\label{fig:scheme-text} +\end{figure} + +Rysunek \ref{fig:scheme-text} pokazuje menu ,,Wybór schematów''. Schematy to +obszerne zestawy pakietów, przeznaczone do wstêpnego wyboru instalowanych +komponentów. Mamy tu schematy do instalacji: podstawowej (\optname{basic}), +typowej (\optname{medium}) i~pe³nej (\optname{full}; jest ona +domy¶lna), pozosta³e przygotowano z~my¶l± o~wybranych grupach +u¿ytkowników (np.~GUST i~GUTenberg przygotowa³y schematy dla swoich +cz³onków) lub zastosowaniach (np.~XML lub Omega). + +\begin{figure}[tbh] +\begin{center} +\tlpng{stdcoll}{.7\linewidth} +\caption{Menu Standard Collections (Kolekcje standardowe) (Linux)}\label{fig:collections-gui} +\end{center} +\end{figure} + +Wstêpnie wybrane schematy mo¿na modyfikowaæ. W sk³ad ,schematów'' wchodz± +tzw. ,,kolekcje'', które mo¿na wybraæ w~kolejnych menu o~nazwach: ,,Kolekcje +standardowe'' i~,,Kolekcje jêzykowe'' (rysunek \ref{fig:collections-gui}). +Kolekcje stanowi± ni¿szy poziom ni¿ schematy, a~same sk³adaj± siê z +,,pakietów''. Dopiero pakiety zawieraj± w³a¶ciwe pliki makr, fontów itp. +Je¶li chcemy dodaæ lub usun±æ pakiet, to po instalacji w³a¶ciwej u¿yjemy +programu \prog{tlmgr} (patrz czê¶æ~\ref{sec:tlmgr}). + +\subsubsection{Katalogi} +\label{sec:directories} + +Domy¶lny uk³ad katalogów opisano w czê¶ci~\ref{sec:texmftrees} na +str.~\pageref{sec:texmftrees}. Po³o¿enie domy¶lne ca³ej instalacji +(\dirname{TEXDIR}) ró¿ni siê w~Windows (|%PROGRAMFILES%\texlive\2008|) +i~w~Unix (\dirname{/usr/local/texlive/2008}). + +G³ównym powodem, dla którego zmieniamy domy¶lne po³o¿enie \dirname{TEXDIR}, +mo¿e byæ brak uprawnieñ. Aby zainstalowaæ \TL{}, nie musimy byæ +administratorem systemu, musimy jednak posiadaæ uprawnienia do zapisu +w~docelowym katalogu. Logiczn± alternatyw± mo¿e byæ wtedy instalacja +w~katalogu domowym, szczególnie wtedy, gdy bêdziemy jedynym u¿ytkownikiem. +Stosujemy tu zapis ,,|~|'' do zaznaczenia takiego wyboru, np. +|~/texlive/2008|. Zalecamy stosowanie katalogu z~nazw± odzwierciedlaj±c± +rok wydania, co pozwoli na zainstalowanie obok siebie ró¿nych wydañ \TL{}. + %%! przegadane, na razie olewam (SW) + %(You may wish to make a + %version-independent name such as \dirname{/usr/local/texlive-cur} via a + %symbolic link, which you can then update after testing the new release.) + +Zmiana \dirname{TEXDIR} w programie instalacyjnym zmieni tak¿e ¶cie¿ki +katalogów okre¶lone przez zmienne \dirname{TEXMFLOCAL}, \dirname{TEXMFSYSVAR} +i~\dirname{TEXMFSYSCONFIG}. + +\dirname{TEXMFHOME} jest zalecanym po³o¿eniem dla prywatnych makr i~fontów +u¿ytkownika. Domy¶lnym katalogiem jest |~/texmf|. W odró¿nieniu od +\dirname{TEXDIR}, znak |~| jest zachowywany w generowanych plikach +konfiguracyjnych, poniewa¿ w~wygodny sposób odnosi siê do katalogu domowego +podczas ka¿dego uruchamiania programów. Znak ten rozwijany jest do zmiennej +\dirname{$HOME} w~Unix i~\verb|%USERPROFILE%| w~Windows. + +\subsubsection{Opcje} +\label{sec:options} + +\begin{figure}[tbh] +\begin{boxedverbatim} +

use letter size instead of A4 by default: [ ] + create all format files: [X] + install font/macro doc tree: [X] + install font/macro source tree: [X] + create symlinks in standard directories: [ ] + binaries to: + manpages to: + info to: +\end{boxedverbatim} +\caption{Menu: Options (Opcje) w Unix}\label{fig:options-text} +\end{figure} + +Rysunek \ref{fig:options-text} pokazuje menu (w~trybie tekstowym) +z~dodatkowymi opcjami. Warto tu wspomnieæ o~trzech z nich: + +\begin{description} +\item[use letter size instead of A4 by default] (u¿yj domy¶lnego formatu +papieru letter zamiast A4): pozwala okre¶liæ domy¶lny format papieru +dla wielu programów. Oczywi¶cie format papieru mo¿na specyfikowaæ potem +dla ka¿dego dokumentu. + +\item[create all format files] (generuj wszystkie pliki formatów): +chocia¿ zbêdne formaty zajmuj± miejsce na dysku, to zaleca siê +pozostawiæ tê opcjê w³±czon±; je¶li tego nie zrobimy, formaty bêd± +generowane automatycznie (w~razie potrzeby) w~prywatnych katalogach +\dirname{TEXMFVAR} u¿ytkowników, nie bêd± jednak od¶wie¿ane, gdy w~instalacji +zostan± zaktualizowane np. programy b±d¼ wzorce przenoszenia; wskutek tego +formaty mog± utraciæ zgodno¶æ ze ¶rodowiskiem, w~którym s± u¿ywane. + +\item[create symlinks in standard directories] (utwórz dowi±zania + w~standardowych katalogach, tylko Unix): opcja ta pozwala unikn±æ ustawiania + zmiennych ¶rodowiska po instalacji (\envname{PATH}, \envname{MANPATH} + i~\envname{INFOPATH}), ale jej u¿ycie nie jest zalecane, bo mo¿e powodowaæ kolizje + z ju¿ zainstalowanym w~systemie ¶rodowiskiem \TeX; mo¿e byæ ona przydatna + jedynie wtedy, gdy w~standardowych katalogach (np. \dirname{/usr/local/bin}) +nie ma jakichkolwiek programów \TeX-owych. +\end{description} + +Po wszystkich potrzebnych ustawieniach mo¿na rozpocz±æ instalacjê +(klawisz ,,I''). Po instalacji zaleca siê zajrzeæ do czê¶ci +\ref{sec:postinstall}, bo byæ mo¿e potrzebne oka¿± siê jeszcze +dodatkowe kroki. + +\subsubsection{Uruchamianie bezpo¶rednio z DVD{} (tylko w trybie tekstowym)} +\label{sec:fromdvd} + +Aby uruchomiæ programy bezpo¶rednio z~p³ytki \DVD{} nale¿y wybraæ +opcjê ,,|V|'', co zmienia menu na przedstawione na +rys.~~\ref{fig:main-fromdvd}. +\begin{figure}[tbh] +\begin{boxedverbatim} +======================> TeX Live installation procedure <===================== + +=======> Note: Letters/digits in indicate menu items <======= +=======> for commands or configurable options <======= + + directories: + TEXDIRW (Writable root): + !! default location: /usr/local/texlive/2008 + !! is not writable, please select a different one! + TEXMFLOCAL (directory for site-wide local files): + /usr/local/texlive/texmf-local + TEXMFSYSVAR (directory for variable and automatically generated data): + /usr/local/texlive/2008/texmf-var + TEXMFSYSCONFIG (directory for local config): + /usr/local/texlive/2008/texmf-config + TEXMFHOME (directory for user-specific files): + ~/texmf + + options: + [ ] use letter size instead of A4 by default + [X] create all format files + + set up for installing to hard disk + +Other actions: + start installation for running from DVD + help + quit +\end{boxedverbatim} +\caption{Menu g³ówne dla uruchamiania z~\optname{DVD}}% +\label{fig:main-fromdvd} +\end{figure} + +Zwróæmy uwagê na nastêpuj±ce zmiany: zniknê³y wszystkie opcje dotycz±ce wyboru +pakietów, sekcja dotycz±ca katalogów pokazuje teraz \dirname{TEXDIRW} -- +katalog z~prawami do zapisu. Pozwoli to uruchamiaæ dowolny program +bezpo¶rednio z~p³ytki; na dysku twardym znajd± siê (w odpowiednich +katalogach) jedynie niezbêdne pliki konfiguracyjne. + +Poniewa¿ struktura katalogów ró¿ni siê nieco od domy¶lnej, niezbêdne bêd± +pewne czynno¶ci konfiguracyjne, omówione w~czê¶ci~\ref{sec:postinstall}. + + %Z powodu pilniejszych prac i braku czasu + Instalator \GUI nie posiada opcji ,,V'', dlatego + %ale jest dostêpna dla wszystkich systemów. + u¿ytkownicy Windows mog± uruchomiæ program jedynie +z~linii poleceñ, jak opisano to w~czê¶ci~\ref{sec:cmdline}. + +W~rozdziale \ref{sec:portable-unix} opisano jeszcze inny, przeno¶ny sposób +uruchamiania \TL, który nie wymaga zmian w~konfiguracji systemu +(a~nawet nie pozwala na nie). + +\subsection{Parametry instalacji z linii poleceñ} +\label{sec:cmdline} + +Uruchom +\begin{alltt} +> \Ucom{install-tl -help} +\end{alltt} +aby wy¶wietliæ wszystkie dostêpne parametry. + % Either |-| or |--| can be used to introduce option names. + Najbardziej interesuj±ce to: + +\begin{ttdescription} +\item[-gui] u¿yj programu w~wersji graficznej (\GUI), je¶li to mo¿liwe; + wymagane jest posiadanie modu³u Perl/Tk + (\url{http://tug.org/texlive/distro.html#perltk}); + gdy jest on niedostêpny, program instalacyjny uruchomiony zostanie + w trybie tekstowym; +\item[-no-gui] wymusza tryb tekstowy, np. w~Windows potrzebny jest on + dla przygotowania do uruchamiania bezpo¶rednio z~\DVD; +\item[-lang {\sl LL}] pozwala wybraæ jêzyk komunikatów, + \textsl{LL} oznacza tu dwuliterowy kod jêzyka; aktualnie dostêpne s±: + angielski (\texttt{en}, domy¶lny), niemiecki (\texttt{de}), francuski + (\texttt{fr}), holenderski (\texttt{nl}), polski (\texttt{pl}), + s³oweñski (\texttt{sl}) i~wietnamski (\texttt{vi}); program samoczynnie + w³±cza jêzyk, ale je¶li jest to niemo¿liwe, komunikaty i menu bêd± + wy¶wietlane w jêzyku angielskim; +\item[-profile {\sl profile}] program instalacyjny zapisuje plik + \filename{texlive.profile} w~katalogu \dirname{2008/tlpkg}, co pozwala + wykorzystaæ go dla powielenia wszystkich wyborów i~ustawieñ w~kolejnych + instalacjach; + %%! zbêdny przyk³ad, patrz wer. oryg. (SW) +\item [-location {\sl url/path}] pozwala okre¶liæ inne ni¿ domy¶lne ¼ród³o + instalacji (patrz poni¿ej). +\end{ttdescription} + +\subsubsection{Parametr \optname{location}} +\label{sec:location} + +Parametrowi \optname{location} mo¿na przypisaæ adres w sieci +(rozpoczynaj±cy siê od \texttt{ftp:}, \texttt{http:} lub \texttt{file:/}), +lub pe³n± ¶cie¿kê. Je¶li podany argument wskazuje na lokalny dysk +(¶cie¿ka b±d¼ adres \texttt{file:/}), to automatycznie zostanie dostosowany +typ instalacji (ze skompresowanych plików b±d¼ nie): gdy dostêpny bêdzie +katalog \dirname{archive}, zawieraj±cy pliki \filename{.tar.lzma}, wybrana +zostanie instalacja z~tych¿e plików, nawet je¶li dostêpne bêd± równolegle +katalogi z~plikami nieskompresowanymi. + +%%! póki co, brak czasu na takie szczegó³y (SW) +%%! When giving an \texttt{http:} or \texttt{ftp:} location, trailing +%%! `\texttt{/}' characters and/or a trailing `\texttt{/tlpkg}' component +%%! are ignored. For example, you could choose a particular \CTAN\ mirror +%%! with something like: +%%! \url{http://ctan.example.org/tex-archive/texlive/tlnet/2008}, +%%! substituting of course a proper hostname and its particular top-level +%%! \CTAN\ path (the list of \CTAN\ mirrors is maintained at +%%! \url{http://ctan.org/mirrors}) for |ctan.example.org/tex-archive|. The +%%! default is to pick a mirror automatically, using +%%! \url{http://mirror.ctan.org}; in any case, the chosen host is used for +%%! the entire download. + +\subsection{Czynno¶ci poinstalacyjne} +\label{sec:postinstall} + +Czê¶æ ta nie dotyczy systemu Windows, dla którego program instalacyjny +przeprowadza ca³± konfiguracjê, w³±cznie z~menu systemowym i~ikonami na +pulpicie. Poni¿sze uwagi mog± byæ przydatne dla u¿ytkowników innych systemów. + +\subsubsection{Gdy zastosujemy dowi±zania symboliczne} + +U¿ycie opisanej w~czê¶ci~\ref{sec:options} opcji tworzenia dowi±zañ +symbolicznych w~standardowych katalogach nie wymaga zmian w zmiennych +¶rodowiska systemowego. + +\subsubsection{Zmienne ¶rodowiska dla Unix} +\label{sec:env} + +Po instalacji trzeba do zmiennej \envname{PATH} dodaæ ¶cie¿kê do +programów \TL. Ka¿da z~obs³ugiwanych platform ma w³asny podkatalog +w~ramach \dirname{TEXDIR/bin}. Listê platform i odpowiadaj±cych im katalogów +przedstawiono na rys.~\ref{fig:bin-text}. + +Równie¿ korzystanie z~systemowych przegl±darek dokumentacji \prog{man} +i~\prog{info} staje siê mo¿liwe dopiero +po dodaniu odpowiednich katalogów do ich ¶cie¿ek przeszukiwania. + +Dla pow³oki zgodnej z~Bourne shell (\cmdname{sh}, \cmdname{bash}, +\cmdname{ksh}) mo¿emy dopisaæ do pliku \filename{$HOME/.profile}: + +\begin{sverbatim} +PATH=/usr/local/texlive/2008/bin/i386-linux:$PATH; export PATH +MANPATH=/usr/local/texlive/2008/texmf/doc/man:$MANPATH; export MANPATH +INFOPATH=/usr/local/texlive/2008/texmf/doc/info:$INFOPATH; export INFOPATH +\end{sverbatim} + +W~wypadku csh lub tcsh nale¿y zmodyfikowaæ plik \filename{$HOME/.cshrc}, np: + +\begin{sverbatim} +setenv PATH /usr/local/texlive/2008/bin/i386-linux:$PATH +setenv MANPATH /usr/local/texlive/2008/texmf/doc/man:$MANPATH +setenv INFOPATH /usr/local/texlive/2008/texmf/doc/info:$INFOPATH +\end{sverbatim} + +%%! ??? (SW) +%%! Of course, you may well already have settings somewhere in your ``dot'' +%%! files, and so then the \TL\ directories should simply be merged in as +%%! appropriate. + +%%! ??? (SW) +%%! \subsubsection{Environment variables: global configuration} +%%! \label{sec:envglobal} +%%! +%%! If you want to make these changes globally, or for a user newly added to +%%! the system, then you are on your own; there is just too much variation +%%! between systems in how and where these things are configured. +%%! +%%! Our two hints are: 1)~you may want to check for a file +%%! \filename{/etc/manpath.config} and, if present, add lines such as +%%! +%%! \begin{sverbatim} +%%! MANPATH_MAP /usr/local/texlive/2008/bin/i386-linux \ +%%! /usr/local/texlive/2008/texmf/doc/man +%%! \end{sverbatim} +%%! +%%! And 2)~check for a file \filename{/etc/environment} which may define the +%%! search path and other default environment variables. + +\subsubsection{Gdy uruchamiamy programy z~DVD} + +Programy \TL{} wyszukuj± potrzebne dane w~ró¿nych drzewach katalogów +korzystaj±c z~pliku \filename{texmf.cnf}. Plik ten znajdowany jest w ca³ej +serii po³o¿eñ wzglêdem po³o¿enia samych programów, ale zasada ta nie dzia³a, +gdy uruchamiamy programy bezpo¶rednio z~\DVD. Wynika to z faktu, ¿e niektóre +pliki s± zapisywane na twardym dysku (\DVD{} jest medium tylko do odczytu) +i~trac± tym samym predefiniowane wzglêdne po³o¿enie. Wymagane jest zatem +zdefiowanie w~¶rodowisku zmiennej \envname{TEXMFCNF}, która wska¿e po³o¿enie +\filename{texmf.cnf}. Nadal jest potrzebna modyfikacja zmiennej +\envname{PATH}, jak opisano wy¿ej. + +Na zakoñczenie instalacji program powinien pokazaæ komunikat informuj±cy, +jak± warto¶æ nale¿y przypisaæ zmiennej \envname{TEXMFCNF}. Gdyby¶my +to przeoczyli -- warto¶ci± t± jest \dirname{$TEXMFSYSVAR/web2c}, czyli dla +domy¶lnych ustawieñ (\dirname{/usr/local/texlive/2008/texmf-var/web2c}) +potrzebujemy deklaracji: +\begin{sverbatim} +TEXMFCNF=/usr/local/texlive/2008/texmf-var/web2c; export TEXMFCNF +\end{sverbatim} +lub, dla [t]csh: +\begin{sverbatim} +setenv TEXMFCNF /usr/local/texlive/2008/texmf-var/web2c +\end{sverbatim} + +\subsubsection{\ConTeXt{} Mark IV} + +Tak zwany ,,stary'' \ConTeXt{} dzia³a jak dotychczas. Nowy \ConTeXt{} +,,Mark~IV'' wymaga rêcznego dostrojenia -- patrz: +\url{http://wiki.contextgarden.net/Running_Mark_IV}. + +\subsubsection{Integracja lokalnych i prywatnych pakietów makr} +\label{sec:local-personal-macros} + +Jak ju¿ wspomniano w~czê¶ci~\ref{sec:texmftrees}, katalog \dirname{TEXMFLOCAL} +(domy¶lnie \dirname{/usr/local/texlive/texmf-local} lub +\verb|C:\Program Files\texlive\texmf-local|) przeznaczony jest na lokalne +(np. w~danej sieci komputerowej) fonty oraz pakiety makr. Z~kolei +\dirname{TEXMFHOME} (domy¶lnie \dirname{$HOME/texmf} lub +\verb|%USERPROFILE%\texmf|) jest przeznaczony na prywatne makra i~fonty +u¿ytkownika. W zamierzeniu oba te katalogi powinny byæ zachowywane przy +instalacji nowszych wersji \TL{}, a~ich zawarto¶æ ma byæ automatycznie +dostêpna w~kolejnych wydaniach. Zalecamy zatem, by nie +przedefiniowywaæ \dirname{TEXMFLOCAL}, co pozwoli unikn±æ rêcznego +konfigurowania w~przysz³o¶ci. + +W~obu drzewach katalogów pliki powinny byæ umieszczane w~odpowiednich +podkatalogach, zgodnie z~zaleceniami TDS (patrz: \url{http://tug.org/tds}, +tak¿e plik \filename{texmf/web2c/texmf.cnf}). Przyk³adowo pliki klas lub +makr \LaTeX-a powinny byæ umieszczane w~katalogu +\dirname{TEXMFLOCAL/tex/latex/} lub \dirname{TEXMFHOME/tex/latex/} +(lub ich podkatalogach). + +\dirname{TEXMFLOCAL} po zmianie zawarto¶ci wymaga od¶wie¿enia bazy danych -- +poleceniem \cmdname{mktexlsr} lub poprzez u¿ycie przycisku ,,Od¶wie¿ bazy +danych'' w~graficznym trybie programu \prog{tlmgr}. + +\subsubsection{Integracja fontów z innych ¼róde³} + +Jest to, niestety, + %mocno zagmatwany temat, + bardzo skomplikowane zagadnienie, wymagaj±ce sporej wiedzy +u¿ytkownika. Warto najpierw siê dowiedzieæ, jakie fonty mamy dostêpne +bezp³atnie (patrz czê¶æ~~\ref{sec:tl-fonts}). + +Alternatyw± jest \XeTeX{} (patrz +czê¶c~\ref{sec:tex-extensions}), który umo¿liwia u¿ycie fontów systemowych +bez potrzeby instalowania ich dla programów \TeX-owych. + +\subsection{Testowanie instalacji} +\label{sec:test-install} + +Po zainstalowaniu \TL{} warto sprawdziæ, czy programy dzia³aj± +poprawnie. Opiszemy tu podstawowe procedury testuj±ce funkcjonowanie +systemu w~systemach Unix. W~\MacOSX{} i~Windows najczê¶ciej u¿yjemy +¶rodowiska graficznego (\GUI), regu³y jednak bêd± podobne. + +\begin{enumerate} +\item Sprawdzamy najpierw, czy uruchamia siê program \cmdname{tex}: + +\begin{alltt} +> \Ucom{tex -{}-version} +TeX 3.1415926 (Web2C 7.5.7) +kpathsea version 3.5.7 +... +\end{alltt} +Je¶li uruchomienie koñczy siê komunikatem \emph{command not found} +(\emph{Nie znaleziono pelecenia}), oznacza to, ¿e niepoprawnie +zadeklarowano zmienn± \envname{PATH} (patrz deklaracje zmiennych +¶rodowiska na str.~\pageref{sec:env}). + +\item Nastêpnie przetwarzamy prosty plik \LaTeX-owy: +\begin{alltt} +> \Ucom{latex sample2e.tex} +This is pdfeTeXk, Version 3.1415926... +..... +Output written on sample2e.dvi (3 pages, 7484 bytes). +Transcript written on sample2e.log. +\end{alltt} +Gdy program nie znajduje \filename{sample2e.tex} (b±d¼ innych wymaganych +plików), mo¿e to oznaczaæ, ¿e nadal dzia³aj± ustawienia zmiennych ¶rodowiska +b±d¼ pliki konfiguracyjne z~poprzedniej instalacji. +Szczegó³ow± analizê, gdzie pliki s± szukane i~znajdowane, +umo¿liwia diagnostyka opisana w~czê¶ci \ref{sec:debugging} na +str.~\pageref{sec:debugging}. + +\item Podgl±d wyniku sk³adu: +\begin{alltt} +> \Ucom{xdvi sample2e.dvi} +\end{alltt} +Polecenie to wymaga uruchomionego ¶rodowiska graficznego X~Window. +Dla MS Windows analogicznym poleceniem jest \cmdname{dviout} (o~ile +samodzielnie zainstalowali¶my ten program). + %%! + %%! You should see a new window with a nice document explaining some of the + %%! basics of \LaTeX{}. (Well worth reading, by the way if you're new to the + %%! system.) You do have to be running under X for \cmdname{xdvi} to work; if + %%! you're not, or your \envname{DISPLAY} environment variable is set + %%! incorrectly, you'll get an error \samp{Can't open display}. + +\item Przetwarzanie wyniku sk³adu do \PS{} w~celu wy¶wietlenia lub wydruku: +\begin{alltt} +> \Ucom{dvips sample2e.dvi -o sample2e.ps} +\end{alltt} + +\item Tworzenie dokumentu bezpo¶rednio w~formacie \acro{PDF}: +\begin{alltt} +> \Ucom{pdflatex sample2e.tex} +\end{alltt} + +\item Podgl±d dokumentu \acro{PDF}: +\begin{alltt} +> \Ucom{gv sample2e.pdf} +\textrm{lub:} +> \Ucom{xpdf sample2e.pdf} +\end{alltt} +Programy \cmdname{gv} i~\cmdname{xpdf} s± zwykle dostarczane +w~ramach systemu operacyjnego, wobec tego nie zamieszczono ich +na \TL. Przed samodzieln± instalacj± warto odwiedziæ strony, +odpowiednio: \url{http://www.gnu.org/software/gv} +i~\url{http://www.foolabs.com/xpdf}. W~sieci dostêpny jest tak¿e +bezp³atny program Adobe Reader (\url{http://www.adobe.com}). +W~systemie Windows domy¶lnie instalowany jest dla \TL{} program +\cmdname{psv} +(PS\_View), pozwalaj±cy przegl±daæ pliki \cmdname{.ps} i~\cmdname{.pdf}. +Program ten mo¿na te¿ zainstalowaæ samodzielnie w~systemach Linux +(w~katalogu \dirname{support/} znajdziemy plik \filename{psview-5.09t.zip}). + +\item Inne przydatne pliki testowe: + +\begin{ttdescription} +\item [small2e.tex] przyk³ad prostszy ni¿ \filename{sample2e}; +\item [testpage.tex] test po³o¿enia wydruku na kartce papieru, przydatny + do sprawdzenia, czy nasza drukarka nie wprowadza przesuniêæ; +\item [nfssfont.tex] s³u¿y do wydruku tablic fontowych; +\item [testfont.tex] jak wy¿ej, z~tym ¿e zamiast \LaTeX-a trzeba u¿yæ plain + \TeX{}; +\item [story.tex] najbardziej kanoniczny przyk³ad dla plain \TeX{}; + na zakoñczenie przetwarzania uruchomionego poleceniem \samp{tex story}, + po ukazaniu siê \code{*}, nale¿y wpisaæ \samp{\bs bye}. +\end{ttdescription} + +\end{enumerate} + +Pocz±tkuj±cym u¿ytkownikom polecamy stronê +\url{http://tug.org/begin.html} oraz podrêcznik +Petera Flynna \textsl{Formatting Information}, dostêpny pod adresem +\url{http://www.ctan.org/tex-archive/documentation/beginlatex}. + +\section{Instalacje sieciowe} +\label{sec:netinstall} + +\TL{} zaprojektowano tak, by mog³o z~niego korzystaæ wielu +u¿ytkowników, nawet w~ró¿nych systemach operacyjnych w~sieci komputerowej. +Dziêki standardowej strukturze katalogów nie ma potrzeby konfiguracji +i~okre¶lania konkretnych ¶cie¿ek: po³o¿enie plików wymaganych przez programy +\TL{} jest zdefiniowane jako wzglêdne wobec samych programów. Mo¿na to +zobaczyæ w~pliku \filename{$TEXMFMAIN/web2c/texmf.cnf}, który zawiera np. +takie wiersze: +\begin{sverbatim} +TEXMFMAIN = $SELFAUTOPARENT/texmf +... +TEXMFLOCAL = $SELFAUTOPARENT/../texmf-local +\end{sverbatim} +W konsekwencji oznacza to, ¿e dla ró¿nych systemów operacyjnych b±d¼ +u¿ytkowników wystarczy dodaæ do ich ¶cie¿ek przeszukiwania tylko ¶cie¿kê +do programów \TL{}. + +Mo¿liwa jest zatem np. instalacja lokalna \TL{}, po czym przeniesienie +ca³ej struktury w~inne miejsce w~sieci. + +U¿ytkownicy Windows mog± mieæ tak¿e inne wymagania. +W~katalogu \dirname{texmf-doc/source/texlive/texlive-common/w32client} +znajdziemy przyk³adowy skrypt \filename{install-w32client}, który +pozwala dostosowaæ istniej±c± instalacjê \TL{} dla potrzeb sieci +(w³±cznie z~utworzeniem skrótów w~menu systemowym). Wystarczy +w~tym katalogu uruchomiæ \filename{install-w32client.bat}. + +W czê¶ci~\ref{sec:kpathsea} dowiemy siê wiêcej o~konfigurowaniu \TL{} +i~zasadach przeszukiwania ¶cie¿ek. + +%%! 2 sekcje t³umaczy³ Kocio (Andrzej Borzyszkowski), przeredagowa³ StaW +\section{Maksymalnie przeno¶ny \protect\TL{} na DVD i~USB} +\label{sec:portable-unix} + +Opcja ,,uruchom z~\DVD{}'', opisana w~rozdziale~\ref{sec:fromdvd}, jest +wprzydatna, je¶li dzia³amy na swoim w³asnym komputerze. Gdy go¶cimy na +cudzym, to prawdopodobnie woleliby¶my wybraæ inn± mo¿liwo¶æ, bez zbêdnych +skutków ubocznych. + +W~g³ównym katalogu \TL{} \DVD (w~podkatalogu \dirname{texlive} \TK{} \DVD) +znajdziemy skrypt uniksowy \filename{tl-portable} oraz widowsowy +\filename{tl-portable.bat}, które uruchamiaj± terminal z~ustawieniami +odpowiednimi do bezpo¶redniego dostêpu do \TL{} na \DVD. + +Gdy skrypt ten jest wykonywany po raz pierwszy, generowane s± pewne pliki +w~podkatalogu \dirname{~/.tlportable2008}, co trwa kilka chwil. +W~kolejnych wywo³aniach skrypt rozpoczyna dzia³anie niemal natychmiast. + +Reszta systemu nie jest ¶wiadoma istnienia \TL. Je¶li chcemy, by nasz edytor +móg³ wspó³pracowaæ z~\TL, to musimy uruchomiæ go z~innej, +równoleg³ej sesji \filename{tl-portable}. + +Mo¿na równie¿ u¿yæ \filename{tl-portable} do wywo³ania \TL{} z~pendrive'a +\acro(USB). W~tym wypadku nale¿y skopiowaæ wszystkie pliki najwy¿szego +poziomu oraz zawarto¶æ (co najmniej) katalogów \dirname{bin}, +\dirname{texmf}, \dirname{texmf-dist} i~\dirname{tlpkg} na pendrive. Zajmie +to trochê czasu! Je¶li kopiujemy na pendrive \acro{USB} sformatowany +z~systemem plików \acro{FAT}32, to nale¿y siê upewniæ, ¿e dowi±zania +symboliczne s± zastêpowane plikami (polecenie \code{cp -L}). U¿ywany te¿ +bêdzie katalog \dirname{texmf-local} na pendrive. + +Nastêpnie wywo³ajmy \filename{tl-portable} z~katalogu g³ównego pendrive'a. +W~tym wypadku skrypt zauwa¿y, ¿e pendrive mo¿na zapisywaæ i~u¿yje go do +zapisania wygenerowanych plików. Zawarto¶æ tê mo¿na z~powrotem zapisaæ na +\DVD{} (np. do przekazania innym). + +\section{\cmdname{tlmgr}: zarz±dzanie instalacj±} +\label{sec:tlmgr} + +\begin{figure}[tb] +\tlpng{tlmgr-gui}{\linewidth} +\caption{\prog{tlmgr} w~trybie graficznym. Lista pokietów\slash +kolekcji\slash schematów poka¿e siê dopiero po naci¶niêciu klawisza +,,£aduj'' (Load).}\label{fig:tlmgr-gui} +\end{figure} + +\begin{figure}[tb] +\tlpng{tlmgr-config}{\linewidth} +\caption{\texttt{tlmgr} w~trybie graficznym: zak³adka +konfiguracji}\label{fig:tlmgr-config} +\end{figure} + +Instalator instaluje program o~nazwie \prog{tlmgr}, s³u¿±cy do dalszego +zarz±dzania \TL{} po pierwotnej instalacji. Programy \prog{updmap}, +\prog{fmtutil} oraz \prog{texconfig} s± nadal dostêpne i~bêd± utrzymywane +w~przysz³o¶ci, jednak¿e obecnie polecanym interfejsem jest \prog{tlmgr}. Jego +mo¿liwo¶ci obejmuj±: + +\begin{itemize*} +\item pokazanie listy schematów, kolekcji i~pakietów; +\item instalowanie, aktualizacjê, tworzenie kopii zapasowych, odtwarzanie + oraz usuwanie pojedynczych pakietów (opcjonalnie~-- z~uwzglêdnieniem + zale¿no¶ci pomiêdzy pakietami); +\item wyszczególnianie oraz dodawanie architektur (platform systemowych); +\item zmianê opcji instalacji, takich jak rozmiar papieru czy zmiana + po³o¿enia ¼ród³a instalacji (patrz czê¶æ~\ref{sec:location}). +\end{itemize*} +\textit{Ostrze¿enie:} \prog{tlmgr} nie zosta³ zaprojektowany ani + przetestowany z~instalacjami, które s± wywo³ywane bezpo¶rednio z~\DVD. + +\subsection{\cmdname{tlmgr} -- tryb graficzny (GUI)} +\prog{tlmgr} mo¿e byæ uruchomiony w~trybie graficznym za pomoc± polecenia +\begin{alltt} +> \Ucom{tlmgr -gui} +\end{alltt} +za¶ w~systemie Windows poprzez wybór menu: \texttt{Start} \verb+->+ +\texttt{Programy} \verb+->+ \texttt{TeX Live 2008} \verb+->+ \texttt{TeX Live +Manager}. Po klikniêciu przycisku ,,£aduj'' wy¶wietla listê dostêpnych +oraz listê zainstalowanych pakietów (te ostatnie poprzedzone s± ,,(i)''). +Zak³adamy oczywi¶cie, ¿e ¼ród³a instalacji s± poprawne i~s± dostêpne. + +Rysunek~\ref{fig:tlmgr-config} przedstawia zak³adkê konfiguracji. + +\subsection{Przyk³adowe wywo³ania \cmdname{tlmgr} z~linii poleceñ} + +Poni¿szy przyk³ad dodaje kilka pakietów, w³±cznie z nowym ,,silnikiem'', +z~innego ni¿ domy¶lne po³o¿enia ¼ród³a instalacji: + +\begin{alltt} +> \Ucom{tlmgr -location http://172.16.18.1/tldev install collection-xetex xkeyval} +\end{alltt} +Generuje on poni¿szy wynik: +\begin{fverbatim} +install: collection-xetex +install: arabxetex +install: euenc +install: bidi +install: fontspec +install: fontwrap +install: ifxetex +install: philokalia +install: polyglossia +install: xecyr +install: xecyr.i386-linux +install: xepersian +install: xetex +install: xetexconfig +install: xetex.i386-linux +running post install action for xetex +install: xetex-def +install: xetex-pstricks +install: xetexfontinfo +install: xltxtra +install: xunicode +install: xkeyval +running mktexlsr +mktexlsr: Updating /usr/local/texlive/2008/texmf/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-config/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-dist/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-doc/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/../texmf-local/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-var/ls-R... +mktexlsr: Done. +regenerating fmtutil.cnf +running fmtutil-sys --missing +... +Transcript written on xelatex.log. +fmtutil: /usr/local/texlive/2008/texmf-var/web2c/xetex/xelatex.fmt installed. +\end{fverbatim} +Jak widaæ, \prog{tlmgr} instaluje zale¿ne pakiety i~dba o~niezbêdne czynno¶ci +poinstalacyjne, w³±cznie z~aktualizacj± bazy danych nazw plików i~powtórnym +wygenerowaniem formatów (w przyk³adzie wygenerowali¶my nowy format dla +\XeTeX). + +Poni¿szy przyk³ad prezentuje instalacjê nowego jêzyka oraz uruchamia powtórne +wygenerowanie formatów: +\begin{alltt} +> \Ucom{tlmgr install collection-langdutch} +\end{alltt} +Aby wy¶wietliæ informacjê o~pakiecie, nale¿y uruchomiæ np.: +\begin{alltt} +> \Ucom{tlmgr show collection-wintools} +\end{alltt} +co daje w~wyniku +\begin{fverbatim} +Package: collection-wintools +Category: Collection +ShortDesc: Windows support programs +LongDesc: Utilities for Windows, since they are not readily available there: + gzip, chktex, jpeg2ps, unzip, wget, xpdf. +Installed: Yes +\end{fverbatim} +Aktualizacja ca³ej instalacji do najnowszej dostêpnej wersji: +\begin{alltt} +> \Ucom{tlmgr update -all} +\end{alltt} +Aby unikn±æ zdenerwowania, proponujemy zacz±æ od: +\begin{alltt} +> \Ucom{tlmgr update -all -dry-run} +\end{alltt} +albo +\begin{alltt} +> \Ucom{tlmgr update -list} +\end{alltt} +Pe³n± dokumentacjê programu poka¿e polecenie: +\begin{alltt} +> \Ucom{tlmgr -help} +\end{alltt} + +\section{Uwagi dotycz±ce Windows} +\label{sec:windows} + +\TL\ ma tylko jeden program instalacyjny, dzia³aj±cy zarówno w~Unix, +jak i~w~Windows. Stworzenie takiego programu by³o mo¿liwe dopiero +po zaniechaniu wsparcia dla starszych wersji Windows. Obecnie +\TL\ mo¿na instalowaæ tylko w~Windows 2000 i~nowszych. + +\subsection{Cechy specyficzne w~systemie Windows} +\label{sec:winfeatures} + +W systemie Windows program instalacyjny wykonuje kilka dodatkowych czynno¶ci: +\begin{description} +\item[Menu i skróty.] W~menu systemowym instalowane jest podmenu ,,\TL'', +które zawiera kilka pozycji dla programów dzia³aj±cych w~trybie graficznym +(\prog{tlmgr}, \prog{texdoctk}, PS\_View -- przegl±darka plików +postscriptowych) oraz dokumentacji. Dla PS\_View tworzony jest tak¿e +skrót (ikona) na pulpicie, umo¿liwiaj±cy ,,przeci±ganie\dywiz upuszczanie'' +na ikonie plików postscriptowych. +\item[Automatyczne ustawienie zmiennych ¶rodowiska.] +Po instalacji nie s± wymagane ¿adne ,,rêczne'' zmiany ustawieñ. +\item[Odinstalowanie.] Program instalacyjny rejestruje instalacjê +w~menu ,,Dodaj/Usuñ programy'' w~Panelu sterowania; odinstalowanie +odbywa siê zatem w~standardowy dla Windows sposób. +\end{description} + +\subsection{Programy pomocnicze dla Windows} + +Aby instalacja by³a kompletna, \TL{} wymaga kilku pomocniczych +programów, które nie s± dostarczane z~systemem Windows. +Wiele skryptów napisano w~jêzyku Perl, ponadto wiele narzêdzi wymaga +programu Ghostscript (interpretera jêzyka PostScript) do +rasteryzacji b±d¼ konwersji plików. Przydatne s± tak¿e w~wielu wypadkach +ró¿ne programy do obróbki grafiki. Ponadto posiadanie edytora +zorientowanego na ¶rodowisko \TeX{} znacznie u³atwi pracê. + +Wszystkie te programy dla Windows mo¿na dosyæ ³atwo znale¼æ w~sieci, +poniewa¿ jednak jest ich spory wybór, postanowili¶my te najbardziej istotne +umie¶ciæ w~dystrybucji \TL: +\begin{description} +\item[Perl i Ghostscript.] Oba te programy s± niezbêdne do +poprawnego dzia³ania \TL, do³±czyli¶my zatem \cmdname{Ghostscript} 8.62 +i~minimaln± dystrybucjê \cmdname{Perl} 5.8, wystarczaj±c± do +uruchomienia wszystkich, zawartych w~\TL{} skryptów perlowych; +oba programy zosta³y ,,ukryte'', to znaczy tylko programy \TL, które +z~nich korzystaj±, ,,wiedz±'' gdzie je znale¼æ; tym samym nie powinny +kolidowaæ z~ewentualnie zainstalowanymi w~systemie programami Perl +i~Ghostscript; +\item[narzêdzia uruchamiane z~linii poleceñ] -- zestaw kilku przydatnych + programów + %(\texttt{bzip2}, %% NIE MA!! (SW) + (\texttt{gzip}, \texttt{unzip}, \texttt{jpeg2ps} i~\texttt{tiff2png}) + a~tak¿e kilka narzêdzi z~zestawu \cmdname{xpdf}, uruchamianych z~linii + poleceñ (sam \cmdname{xpdf} nie jest dostêpny dla Windows, + mo¿na jednak pobraæ z~internetu opart± na nim przegl±darkê \acro{PDF}: + \url{http://blog.kowalczyk.info/software/sumatrapdf}); +\item[\texttt{fc-cache}] -- program rejestruj±cy dla \XeTeX-a fonty + systemowe lub dostarczane w~dystrybucji \TL{} fonty OpenType; +\item[PS\_View] -- nowy program podgl±du plików postscriptowych (a~tak¿e + plików \acro{PDF}), patrz rys.~\ref{fig:psview}. +\end{description} +\begin{description} +\item[katalog \texttt{support,}] wspomniany ju¿ w~czê¶ci~\ref{sec:tld}, + zawiera ró¿ne programy, które mog± byæ u¿yteczne w~¶rodowisku \TeX-owym + (np. edytory/¶rodowiska dla \TeX-a); programy te \emph{nie s±} uwzglêdniane + podczas instalacji samego \TL, nale¿y je wiêc zainstalowaæ samodzielnie. +\end{description} + +\begin{figure}[h] +\begin{center} +\tlpng{psview}{.6\linewidth} +\caption{PS\_View: umo¿liwia bardzo du¿e powiêkszenia!}\label{fig:psview} +\end{center} +\end{figure} + +Poni¿ej zamieszczono listê miejsc, z~których mo¿na pobraæ programy +pomocnicze: + +\begin{description} +\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} +\item[Perl] \url{http://www.perl.org} (uzupe³niaj±ce, przydatne + pakiety nale¿y pobraæ z~zasobów CPAN \url{http://cpan.org}) +\item[ImageMagick] -- bogaty zestaw narzêdzi do wsadowego przetwarzania + plików graficznych (\url{http://www.imagemagick.com}) +\item[NetPBM] -- do przetwarzania i~konwersji plików graficznych mo¿emy + u¿yæ alternatywnego dla \textsf{ImageMagick} programu NetPBM + (\url{http://netpbm.sourceforge.net/}) +\item[Edytory dla systemu \TeX{}] -- spory wybór programów, uwzglêdniaj±cy + indywidualne preferencje u¿ytkownika: + \begin{itemize*} + \item \cmdname{GNU Emacs} -- w~wersji zintegrowanej z~\textsf{AucTeX} + dostêpny jest w~\TL{} w~katalogu \path{support/} + (\url{ftp://alpha.gnu.org/gnu/auctex}) +% http://www.gnu.org/software/emacs/windows/ntemacs.html}) +% \item \cmdname{XEmacs} -- bardziej przyjazna wersja dla Windows +% (\url{http://www.xemacs.org/}) + \item \cmdname{WinShell} -- prosty edytor/shell, dostêpny na \TL + w~katalogu \dirname{support/WinShell} (\url{http://www.winshell.de}) + \item \cmdname{WinEdt} -- bogaty w~funkcje edytor dla \TeX-a, dostêpny jako + \emph{shareware} (\url{http://www.winedt.com}) + \item TeXnicCenter -- kolejny, dosyæ bogaty w~funkcje edytor + (\url{http://www.toolscenter.org/products/texniccenter/}) + \item \cmdname{Vim} -- rozbudowany i~bardzo funkcjonalny edytor, wywodz±cy siê + z~klasycznego dla systemów Unix edytora \cmdname{vi} + %, dostêpny na \TL{} w~katalogu \dirname{support/vim} + (\url{http://www.vim.org}) + \item \cmdname{LEd} -- polski edytor, dostêpny + z~\url{http://www.ctan.org/support/LEd} + \item \cmdname{SciTE} -- edytor dostêpny + z \url{http://www.scintilla.org/SciTE.html} + \end{itemize*} +\end{description} + +%Mo¿emy zainstalowaæ z~sieci tak¿e inne narzêdzia, których zabrak³o na +%\TL{} z~powodów licencyjnych. Przyk³adem jest tu \cmdname{GSView}, +%wygodny program wykorzystuj±cy \cmdname{Ghostscript} do wy¶wietlania +%i~drukowania plików PS/PDF. Dostêpny jest on m.in. +%na \url{http://www.cs.wisc.edu/~ghost/gsview/}, a~tak¿e na ka¿dym serwerze +%\acro{CTAN}. + +\subsection{Program Dviout} + +Obecne wydanie \TL{} nie oferuje niestety preinstalowanego programu do +podgl±du plików \acro{DVI} dla Windows, mo¿na jednak samodzielnie +zainstalowaæ doskona³y \prog{dviout}, autorstwa Toshio Oshimy. Znajdziemy go +w~katalogu \path{support/dviout/}, zawieraj±cym równie¿ krótki plik +\filename{README} omawiaj±cy, jak zaistalowaæ i~skonfigurowaæ \prog{dviout} +dla \TL. Przed instalacj± zalecamy przeczytaæ informacje tam zawarte. + +Pierwsze uruchomienie \verb+dviout+ zazwyczaj automatycznie generuje wymagane +fonty ekranowe. Po kilku sesjach komunikaty dotycz±ce generowania fontów +stan± siê rzadsze. Wiêcej informacji mo¿na znale¼æ w~bardzo dobrym +poradniku \emph{on-line} tego programu. + +\subsection{User Profile to inaczej Home (katalog domowy)} +\label{sec:winhome} + +Odpowiednikiem uniksowego katalogu domowego u¿ytkownika (HOME) jest +w~Windows katalog okre¶lany zmienn± \verb|%USERPROFILE%|. W~Windows +2000 i~XP jest to zazwyczaj katalog +\verb|C:\Documents and Settings\|, za¶ w~Windows Vista +\verb|C:\Users\|. W~pliku konfiguracyjnym +\filename{texmf.cnf} i~bibliotekach \KPS{} znak \verb|~| +jest poprawnie rozwijany do odpowiedniej zmiennej zarówno w~Windows, jak +i~w~Unix. + +\subsection{Rejestr Windows} +\label{sec:registry} + +W systemie Windows prawie wszystkie dane konfiguracyjne przechowywane s± +w~tzw. rejestrze. Zawiera on hierachicznie zorganizowane klucze, w~ramach +kilku kluczy g³ównych. Najbardziej istotne dla programów instalacyjnych +s± klucze \path{HKEY_CURRENT_USER} oraz \path{HKEY_LOCAL_MACHINE} +(w~skrócie \path{HKCU} i \path{HKLM}). Czê¶æ \path{HKCU} dotyczy katalogów +domowych u¿ytkowników (patrz~\ref{sec:winhome}), za¶ \path{HKLM} -- podkatalogów +systemowych (w~katalogu Windows). + +Informacje o~ustawieniach systemu mo¿na czasem uzyskaæ ze zmiennych +¶rodowiska, ale po inne informacje, np. po³o¿enie tzw. skrótów, trzeba +odwo³aæ siê do rejestru. Tak¿e zapis zmiennych ¶rodowiska na sta³e wymaga +dostêpu do rejestru. + +\subsection{Uprawnienia w Windows} +\label{sec:winpermissions} + +%%! UWAGA SW: ca³a ta czê¶æ jest mocno niejasna w oryginale. T³umaczy³em +%%! j± maj±c na uwadze ogólny sens, w niektórych miejscach doprecyzowuj±c +%%! sformu³owania. Ale i tak jest, wg mnie, do bani :-) + +W nowszych wersjach Windows istnieje wyra¼ne rozró¿nienie miêdzy +zwyk³ymi u¿ytkownikami i~administratorami, przy czym tylko ci ostatni maj± +pe³n± swobodê dostêpu do ca³o¶ci systemu. + %%! ??? + %In practice, though, you could better describe + %these classes of users as unprivileged users and normal users: being an + %administrator is the rule, not the exception. + Do³o¿ono wielu starañ, aby umo¿liwiæ instalacjê \TL{} tak¿e osobom bez + uprawnieñ administratora. + +Je¶li osoba instaluj±ca jest administratorem, to skróty s± tworzone dla +wszystkich u¿ytkowników, tak¿e zmienne ¶rodowiska s± ustawiane dla ca³ego +systemu. W~przeciwnym wypadku skróty i~menu s± tworzone jedynie dla konkretnego +u¿ytkownika, tak¿e definiowane zmienne ¶rodowiska dotycz± zwyk³ych +u¿ytkowników. Maj±c uprawnienia admistratora mo¿emy zainstalowaæ \TL{} tylko +dla u¿ytkowników; nale¿y wtedy uruchomiæ \prog{install-tl} z~parametrem +\optname{-non-admin}. + +Bez wzglêdu na status u¿ytkownika domy¶lnym katalogiem g³ównym instalacji +jest katalog w~ramach \verb|%PROGRAMFILES%|. Program instalacyjny zawsze +sprawdza, czy ten katalog jest dostêpny do zapisu dla aktualnego u¿ytkownika. + +Problem mo¿e siê pojawiæ wtedy, gdy u¿ytkownik instaluj±cy \TL{} nie jest +administratorem, a~programy \TeX-owe ju¿ s± w~¶cie¿ce przeszukiwania. +Wynikowa ¶cie¿ka zawiera wtedy ¶cie¿kê systemow±, do której dodano ¶cie¿kê do +programów u¿ytkownika. W~konsekwencji nie bêd± znajdowane nowo instalowane +programy. W~celu obej¶cia tego problemu program instalacyjny tworzy skrót do +okna z~wierszem poleceñ, w~którym ¶cie¿ka do nowych programów \TL{} ma +priorytet. W~ten sposób, po uruchomieniu tego skrótu, bêdzie mo¿na korzystaæ +z~\TL. + +%%% Zostawione z poprzedniej wersji tylko w polskim t³umaczeniu! + +\subsection{\cmdname{WinShell}}\label{sec:winshell} + +Je¶li nie decydujemy siê na instalowanie rozbudowanego (ale i~bardzo +bogatego w~funkcje) edytora Emacs, mo¿emy samodzielnie zainstalowaæ prosty +i~³atwy w~obs³udze edytor WinShell. Znajdziemy go na p³ytce w~katalogu +\dirname{support/winshell}. Wystarczy dwukrotnie klikn±æ klawiszem myszy +na znajduj±cym siê tam pliku \texttt{.exe}. +Program uruchamiamy z~menu Start b±d¼ z~ikony/skrótu na pulpicie. +Dostosowanie do polskiej wersji Windows wymaga, prócz okre¶lenia jêzyka +dla menu i~komunikatów, u¿ycia menu +\verb+Opcje+ (Options) \verb+->+ \verb+Font+ \verb+->+ \verb+Zmieñ+ +i~wyboru w~wy¶wietlonym oknie \texttt{Skrypt} +napisu \texttt{Europa ¦rodkowa}. +Dziêki temu poprawnie bêd± wy¶wietlane polskie znaki diakrytyczne, +wpisywane za pomoc± prawego klawisza Alt. + +Aby skonfigurowaæ uruchamianie programów, otwieramy menu +\texttt{Options} \verb+->+ \texttt{Program Calls}. + +\begin{itemize}\itemsep 0pt +\item W zak³adce DVIWin, w~polu ,,exe-file'', wpisujemy +\texttt{dviout.exe} (o~ile go wcze¶niej zaistalowali¶my). +\item W zak³adce Ghostview wpisujemy psv.bat. + %sprawdziæ, czy prawid³owo podano + %¶cie¿kê dla gsview32.exe:\\ + %\hspace*{1em} \verb+C:\ghostgum\gsview\gsview32.exe+ (dla wersji 3.6 + %i~nowszych). +\end{itemize} +Po wci¶niêciu przycisku \texttt{OK} zatwierdzamy zmiany. + +Instalacja programu ustawia w~Windows skojarzenie plików \texttt{.tex} +z~uruchamianiem \cmdname{WinShell}. O~ile nie zamierzamy korzystaæ +z~innego edytora (jak WinEdt lub Emacs), jest to poprawne. + +\cmdname{WinShell} jest wyposa¿ony w~modu³ pomocy, dostêpnej po +naci¶niêciu symbolu $\textbf{\underbar{?}}$ na pasku z~narzêdziami. + +\subsubsection{U¿ycie plików ,,projektu''} + Wielokrotnie mamy do czynienia z~dokumentami sk³adaj±cymi siê z~wielu +czê¶ci. Najwygodniej gdy s± one zapisane w~odrêbnych plikach. +\cmdname{WinShell} umo¿liwia utworzenie pliku projektu (\textit{Project +file}), w~którym deklarujemy poszczególne czê¶ci wiêkszego dokumentu. Nazwy +plików projektu: traktowanego jako g³ówny (\textit{Main file}) oraz plików +czê¶ci s± wy¶wietlane w~lewym oknie edytora. Dwukrotne klikniêcie mysz± na +nazwie pliku powoduje jego wy¶wietlenie w~g³ównym oknie edytora. Naci¶niêcie +ikony LaTeX na belce narzêdziowej uruchamia zawsze przetwarzanie g³ównego +pliku, bez wzglêdu na to, który plik jest aktualnie wy¶wietlany. + +Na belce narzêdziowej mamy dodatkowe przyciski, pozwalaj±ce wy³±czyæ lub +w³±czyæ wy¶wietlanie okna projektu (po lewej stronie) i~okna zapisu sesji +(log) -- u~do³u. Gdy plik projektu nie jest u¿ywany, lew± czê¶æ okna mo¿na +zamkn±æ, zyskuj±c w~ten sposób ca³± szeroko¶æ ekranu dla edytowanego pliku. + +\subsubsection{Drukowanie z~\cmdname{WinShell} na drukarce PostScriptowej} +\label{winshell:print} + Ikona Dvips belki narzêdziowej uruchamia program, który wynik pracy +zapisuje zwykle w~pliku \verb+.ps+. Ogl±danie i/lub drukowanie takiego pliku +wymaga uruchomienia + %GSView. + PS\_View. + \cmdname{WinShell} pozwala zdefiniowaæ +wygodne wywo³anie polecenia dvips, które wynik przetwarzania wy¶le od razu +do drukarki wyposa¿onej w~interpreter PostScript. Przyk³adowo, dla drukarki +o~nazwie \texttt{vclw}, postêpowanie bêdzie nastêpuj±ce: +\begin{enumerate} +\item Deklaracja danej drukarki w programie: +\begin{itemize} +\item otworzyæ \cmdname{WinShell}, wybraæ menu \texttt{Opcje} \verb+->+ + \texttt{Programy u¿ytkownika}. +\item wybraæ \texttt{Tool 1} w~spisie po prawej stronie i~wype³niæ pola + po stronie lewej, np.:\vspace{-3pt} + \begin{quote} + Name: \verb+Drukuj+\\ + exe file: \verb+dvips+\\ + cmd-line: \verb+ -D600 %c.dvi -o vclw+\\ + skasowaæ zaznaczenie okienka ,,najpierw DVIPS'' +\end{quote}%\vspace{-12pt} +\item nacisn±æ \texttt{OK}. +\end{itemize} +\item Dodanie polecenia ,,Drukuj'' do belki narzêdziowej: +\begin{itemize} +\item wybraæ menu \texttt{Opcje} \verb+->+ \texttt{Przegl±daj} \verb+->+ + \texttt{Dostosuj paski}; +\item w~okienku \verb+Kategoria+ wybraæ \texttt{Programy u¿ytkownika}; +\item wskazaæ \texttt{Drukuj} i~przeci±gn±æ go mysz± na belkê narzêdziow±, + umieszczaj±c w~dowolnym miejscu obok innych poleceñ; +\item w kolejno wy¶wietlanym oknie dokonaæ wyboru: ,,Tylko obrazek'' + (\textit{Image only}), ,,Tylko tekst'' lub ,,Tekst i~obrazek''; najpro¶ciej + wybraæ ,,Tylko tekst'' i~zatwierdziæ guzikiem \texttt{OK}. + Napis \texttt{Drukuj} uka¿e siê na belce. (Bardziej wymagaj±cy u¿ytkownicy + mog± wybraæ opcjê ,,Tylko obrazek'', nastêpnie ,,Edytuj'' i~skonstruowaæ + sobie w³asn± ikonkê.) +\end{itemize} +\end{enumerate} +Uruchamianie polecenia zosta³o zdefiniowane. Aby drukowaæ bezpo¶rednio na +drukarce, wystarczy teraz nacisn±æ guzik z~napisem ,,Drukuj''. + +\subsection{W razie problemów} +\label{troubleshooting} + +\subsubsection{Co zrobiæ gdy \texttt{latex} nie mo¿e znale¼æ potrzebnych +plików?} + +\begin{itemize} +\item Program \cmdname{kpsewhich} jest podstawowym narzêdziem do diagnozowania + problemów. Wyprowadza on informacje diagnostyczne na wyj¶cie stderr, przy +czym konsole (okienka wierszy poleceñ) starszych systemów Windows nie +potrafi± przekierowaæ stderr do pliku. Umo¿liwia to dopiero system Windows +NT i~pó¼niejsze, ale rozwi±zanie przedstawione poni¿ej dzia³a dla ka¿dej +konsoli (okienka wierszy poleceñ). Otó¿ dla celów diagnostycznych mo¿na +tymczasowo zdefiniowaæ zmienn± ¶rodowiska (w~oknie poleceñ): +\begin{verbatim} +SET KPATHSEA_DEBUG_OUTPUT=err.log +\end{verbatim} +Mo¿na równie¿ zadaæ zakres diagnostyki: +\begin{verbatim} +SET KPATHSEA_DEBUG=-1 +\end{verbatim} + +Podobnie, aby przekierowaæ wyj¶cie stderr na stdout: +\begin{verbatim} +SET KPATHSEA_DEBUG_OUTPUT=con: +\end{verbatim} +W ten sposób mo¿na skierowaæ zarówno stderr, jak i stdout do tego samego pliku. +\item Przy za³o¿eniu, ¿e instalacjê wykonano w \path|c:/TeX|, nale¿y + sprawdziæ (porównaæ) nastêpuj±ce warto¶ci:\\ + {\small + \begin{tabular}{ll} + \path|kpsewhich -expand-path $SELFAUTOPARENT| & \path|c:/TeX| \\ + \path|kpsewhich -expand-path $TEXMF| & \path|c:/TeX/texmf....| \\ + \path|kpsewhich -expand-var $TEXINPUTS| & \path|.;c:/TeX/texmf/tex//| + \end{tabular} +} + +Je¶li w otoczeniu systemowym s± zdefiniowane zmienne zwi±zane z~\TeX-em, +nale¿y je usun±æ, maj± bowiem pierwszeñstwo przed tymi, +które okre¶lono w~pliku \filename{texmf.cnf}. +\item Nastêpnie nale¿y sprawdziæ (porównaæ) warto¶ci:\\ +{\small + \begin{tabular}{ll} + \texttt{kpsewhich cmr10.tfm} & \path|c:/TeX/texmf-dist/fonts/tfm/public/cm/cmr10.tfm|\\ + \texttt{kpsewhich latex.fmt}& \path|c:/TeX/texmf-var/web2c/pdftex/latex.fmt| + \end{tabular} +} + +Je¶li sprawdzenia nie wykaza³y odstêpstw, to \TeX{} i~programy towarzysz±ce +powinny dzia³aæ. Je¶li tak nie jest, nale¿y poeksperymentowaæ z opcj± +\path|-debug=n| programu \path|kpsewhich| i~zweryfikowaæ wszystkie uzyskane +warto¶ci. Po zidentyfikowaniu problemu warto go zg³osiæ. +\end{itemize} + +%-------------------------- +% don't use \Webc so the \uppercase in the headline works. +\section{Instrukcja obs³ugi systemu Web2C} + +\Webc{} to zestaw programów zwi±zanych z~\TeX-em, tj. sam \TeX{}, \MF{}, +\MP, \BibTeX{} itd. Stanowi± one rdzeñ dystrybucji \TL. + +Oryginalna implementacja wykonana zosta³a przez Tomasa Rokickiego, który +w~roku 1987 stworzy³ pierwszy system \TeX{}-to-C, adaptuj±c pliki wymiany +(\emph{change files}) pod Unix-em (pierwotnie by³y one dzie³em Howarda +Trickey'a oraz Pavela Curtisa). W~czasie, gdy Tim Morgan zajmowa³ siê +systemem, jego nazwa zosta³a zmieniona na Web-to-C\@. W~1990 roku prace nad +projektem przej±³ Karl Berry wraz z~dziesi±tkami wspó³pracowników, a~w~roku +1997 pa³eczkê przej±³ Olaf Weber. + +\Webc{} dzia³a na platformach systemowych, takich jak Unix (w~tym \MacOSX), +Windows 9x/\acro{NT/2K/XP} i~innych. +System wykorzystuje oryginalne ¼ród³a \TeX-owe autorstwa Donalda Knutha +oraz inne programy napisane w~\web{} i~t³umaczy je na kod ¼ród³owy~C. +Ponadto system udostêpnia spory zestaw makr i~funkcji stworzonych dla +zwiêkszenia funkcjonalno¶ci oryginalnych zasobów oprogramowania +zwi±zanego z~\TeX-em. Podstawowymi sk³adnikami systemu s±: + +\begin{cmddescription} +\item[bibtex] tworzenie spisów bibliograficznych; +\item[dmp] konwersja \cmdname{troff} do MPX (rysunki \MP{}-owe); +\item[dvicopy] modyfikowanie pliku \dvi; +\item[dvitomp] konwersja \dvi{} do MPX (rysunki \MP{}-owe); +\item[dvitype] konwersja \dvi{} na plik tekstowy (ASCII); +\item[gftodvi] zamiana fontu GF na plik \dvi; +\item[gftopk] zamiana fontu w~formacie GF na font spakowany (PK); +\item[gftype] zamiana fontu GF na plik tekstowy (ASCII); +\item[makempx] sk³ad etykiet \MP{}-owych; +\item[mf] generowanie fontów bitmapowych w formacie GF; +\item[mft] sk³ad plików ¼ród³owych \MF{}-a; +\item[mpost] tworzenie rysunków oraz diagramów technicznych; +\item[mpto] ekstrakcja etykiet \MP{}-owych; +\item[newer] porównywanie czasów modyfikacji; +\item[patgen] tworzenie wzorców przenoszenia wyrazów; +\item[pktogf] zamiana fontów w formacie PK na fonty GF; +\item[pktype] zamiana fontu PK na plik tekstowy (ASCII); +\item[pltotf] konwersja tekstowej listy w³a¶ciwo¶ci do TFM; +\item[pooltype] wy¶wietlanie \web-owych plików pool; +\item[tangle] konwersja \web{} do jêzyka Pascal; +\item[tex] sk³ad tekstu; +\item[tftopl] konwersja TFM do tekstowej listy w³a¶ciwo¶ci (PL); +\item[vftovp] konwersja fontów wirtualnych do wirtualnej listy + w³a¶ciwo¶ci (VPL); +\item[vptovf] konwersja wirtualnej listy w³a¶ciwo¶ci do fontów wirtualnych; +\item[weave] konwersja \web{} do \TeX-a. +\end{cmddescription} + +\noindent +Dok³adny opis funkcji oraz sk³adni tych programów zawarty jest +w~dokumentacji poszczególnych pakietów samego \Webc{}. +Do optymalnego korzystania z~instalacji \Webc{} +przyda siê znajomo¶æ kilku zasad rz±dz±cych ca³± rodzin± programów. + +Wszystkie programy obs³uguj± standardowe opcje \acro{GNU}: +\begin{description} +\item[\texttt{-{}-help\ \ \ }] podaje podstawowe zasady u¿ytkowania; +\item[\texttt{-{}-verbose}] podaje dok³adny raport z~dzia³ania programu; +\item[\texttt{-{}-version}] podaje informacjê o~wersji, po czym koñczy + dzia³anie programu. +\end{description} + +Do lokalizowania plików programy oparte na \Webc{} u¿ywaj± biblioteki do +przeszukiwania ¶cie¿ek zwanej \KPS{}. +Dla optymalizacji przeszukiwania \TeX-owego drzewa podkatalogów biblioteka ta +u¿ywa kombinacji zmiennych ¶rodowiskowych oraz kilku plików konfiguracyjnych. +\Webc{} potrafi obs³ugiwaæ jednocze¶nie wiêcej ni¿ jedno drzewo +podkatalogów, co jest u¿yteczne w~wypadku, gdy chce siê przechowywaæ +standardow± dystrybucjê \TeX-a jak i~lokalne rozszerzenia w~dwóch ró¿nych +drzewach katalogów. +Aby przyspieszyæ poszukiwanie plików, katalog g³ówny ka¿dego drzewa ma swój +plik \file{ls-R}, zawieraj±cy pozycje okre¶laj±ce nazwê i~wzglêdn± ¶cie¿kê +dla wszystkich plików zawartych w~tym katalogu. + +\subsection{Przeszukiwanie ¶cie¿ek przez Kpathsea} +\label{sec:kpathsea} + +Opiszemy najpierw ogólny mechanizm przeszukiwania ¶cie¿ek przez bibliotekê +\KPS{}. + +Tym, co nazywamy \emph{¶cie¿k± przeszukiwania}, jest rozdzielona dwukropkami +lub ¶rednikami lista \emph{elementów ¶cie¿ki}, które zasadniczo s± nazwami +podkatalogów. ¦cie¿ka przeszukiwania mo¿e pochodziæ z~(kombinacji) wielu +¼róde³. Przyk³adowo, aby odnale¼æ plik \samp{my-file} w~¶cie¿ce +\samp{.:/dir}, \KPS{} sprawdza istnienie danego elementu ¶cie¿ki +w~nastêpuj±cej kolejno¶ci: najpierw \file{./my-file}, potem +\file{/dir/my-file}, zwracaj±c pierwszy odnaleziony (lub mo¿liwie wszystkie). + +Aby optymalnie zaadaptowaæ siê do konwencji wszystkich systemów operacyjnych, +na systemach nieunixowych \KPS{} mo¿e u¿ywaæ +jako separatorów nazw ¶cie¿ek znaków innych +ni¿ dwukropek (\samp{:}) oraz ,,ciach'' (\samp{/}). + +W~celu sprawdzenia konkretnego elementu \var{p} ¶cie¿ki, \KPS{} najpierw +sprawdza, czy zbudowana wcze¶niej baza danych (patrz ,,Baza nazw plików'' na +stronie~\pageref{Filename-database}) odnosi sie do \var{p}, tj. +czy baza danych znajduje siê w~podkatalogu z~prefiksem~\var{p}. +Je¿eli tak, to specyfikacja ¶cie¿ki jest porównywana z~zawarto¶ci± bazy. + +Je¶li baza danych nie istnieje b±d¼ nie odnosi siê do danego elementu +¶cie¿ki albo te¿ nie zawiera elementów zgodnych, to przeszukiwany jest system +plików (je¿eli nie zosta³o to zabronione przez specyfikacjê rozpoczynaj±c± +siê od~\samp{!!}\ oraz je¿eli poszukiwany plik musi istnieæ). +\KPS{} konstruuje listê podkatalogów, które koresponduj± z~danym elementem +¶cie¿ki, a~nastêpnie sprawdza w~ka¿dym z~nich, czy nie ma tam poszukiwanego +pliku. + +Warunek mówi±cy, ¿e ,,plik musi istnieæ'' dotyczy np. plików \samp{.vf} +i~plików do³±czanych \TeX-owym poleceniem \cs{openin}. +Takiego pliku mo¿e nie byæ (np. \file{cmr10.vf}), b³êdne by³oby zatem +poszukiwanie go na dysku. +Je¶li wiêc zapomnisz o~aktualizacji \file{ls-R} po instalacji nowego +pliku \samp{.vf}, to nie zostanie on odnaleziony. +Ka¿dy element ¶cie¿ki sprawdzany jest w~nastêpuj±cej kolejno¶ci: najpierw +w~bazie danych, potem na dysku. +Je¿eli plik siê znajdzie, to przeszukiwanie zostanie zatrzymane i~zwrócony +zostanie wynik. + +Poniewa¿ najprostszym i~najbardziej powszechnym elementem ¶cie¿ki jest +nazwa katalogu, \KPS{} korzysta z~dodatkowych mo¿liwo¶ci w~przeszukiwaniu +¶cie¿ek: +wielowarstwowych warto¶ci domy¶lnych, zmiennych ¶rodowiskowych, warto¶ci +pliku konfiguracyjnego, lokalnych +podkatalogów u¿ytkownika oraz rekursywnego przeszukiwania podkatalogów. +Mo¿na wiêc powiedzieæ, ¿e \KPS{} \emph{rozwija} element ¶cie¿ki, tzn. +transformuje wszystkie specyfikacje do podstawowej nazwy lub nazw katalogów. +Jest to opisane w~kolejnych akapitach, w~kolejno¶ci w~jakiej ma to miejsce. + +Trzeba zauwa¿yæ, ¿e je¿eli nazwa poszukiwanego pliku jest +absolutna lub jawnie wzglêdna, tj. zaczyna siê od \samp{/} lub \samp{./} +lub \samp{../}, to \KPS{} ogranicza siê do sprawdzenia, czy ten plik istnieje. + +\ifSingleColumn +\else +\begin{figure*} +\verbatiminput{examples/ex5.tex} +\setlength{\abovecaptionskip}{0pt} + \caption{Przyk³ad pliku konfiguracyjnego} + \label{fig:config-sample} +\end{figure*} +\fi + +\subsubsection{¬ród³a ¶cie¿ek} +\label{Path-sources} + +Nazwa przeszukiwanej ¶cie¿ki mo¿e pochodziæ z~wielu ¼róde³. +Oto kolejno¶æ, w~jakiej \KPS{} ich u¿ywa: + +\begin{enumerate} +\item + Zmienna ¶rodowiskowa ustawiana przez u¿ytkownika, np. + \envname{TEXINPUTS}. + Zmienne ¶rodowiskowe z~do³±czon± kropk± i~nazw± programu zastêpuj± inne, + np. je¿eli \samp{latex} jest nazw± uruchomionego programu, wtedy zamiast + \envname{TEXINPUTS} wykorzystana zostanie zmienna \envname{TEXINPUTS.latex}. +\item + Plik konfiguracyjny konkretnego programu, np. linia ,,\texttt{S /a:/b}'' + w~pliku \file{config.ps} programu \cmdname{dvips}. +\item Plik konfiguracyjny \KPS{} \file{texmf.cnf}, zawieraj±cy tak± liniê, + jak \samp{TEXINPUTS=/c:/d} (patrz poni¿ej). +\item Warto¶ci domy¶lne dla uruchamianych programów. +\end{enumerate} +\noindent Ka¿d± z~tych warto¶ci dla danej ¶cie¿ki przeszukiwania mo¿na +zobaczyæ, u¿ywaj±c opcji diagnostyki b³êdów (patrz ,,Diagnostyka b³êdów'' na +stronie~\pageref{sec:debugging}). + +\subsubsection{Pliki konfiguracyjne} + +\tolerance=3500 + \KPS{} szuka ¶cie¿ek przeszukiwania i~innych definicji w~\emph{plikach +konfiguracyjnych} o~nazwach \file{texmf.cnf}. +¦cie¿ka przeszukiwania u¿ywana do znajdowania tych plików okre¶lana jest +przez zmienn± \envname{TEXMFCNF} (domy¶lnie taki plik znajduje siê w~podkatalogu +\file{texmf/web2c}). +Czytane bêd± \emph{wszystkie} pliki \file{texmf.cnf} w~¶cie¿ce +przeszukiwania, +a~definicje we wcze¶niejszych plikach zast±pi± te w~pó¼niejszych. +Tak wiêc w~¶cie¿ce \verb|.:$TEXMF| warto¶ci pochodz±ce z~\file{./texmf.cnf} +zast±pi± te z~\verb|$TEXMF/texmf.cnf|. + +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +Dociekliwy czytelnik mo¿e byæ zainteresowany sposobem, w~jaki programy +znajduj± plik \file{texmf.cnf}, skoro nie ma konieczno¶ci deklarowania +specyficznej zmiennej ¶rodowiskowej systemu. Otó¿ po³o¿enie domy¶lne jest +wkompilowane w~programy jako wzglêdne do ich po³o¿enia (okre¶lanego, jak +wiemy, w~¶cie¿ce specyfikowanej przez \texttt{\$PATH}): +\path{../../texmf/web2c/} b±d¼ \path{../texmf/web2c/}. Je¶li jawnie +deklarujemy zmienn± \envname{TEXMFCNF}, wymagane jest podanie bezwzglêdnej +¶cie¿ki. + +Czytaj±c zamieszczony poni¿ej opis formatu pliku \file{texmf.cnf}, +warto przegl±daæ jego zawarto¶æ. Po³o¿enie \emph{aktywnego} pliku +znajdziemy za pomoc± polecenia \texttt{kpsewhich texmf.cnf}. + +\begin{itemize} +\item + Komentarze zaczynaj± siê od ,,\texttt{\%}'', a~koñcz± na koñcu wiersza. +\item + Puste wiersze nie s± brane pod uwagê. +\item + Znak \bs{} na koñcu wiersza dzia³a jako znak kontynuacji, tzn. + oznacza, ¿e kolejny wiersz jest kontynuacj± bie¿±cego. + Spacja na pocz±tku kolejnego wiersza nie jest ignorowana. +\item + Pozosta³e wiersze maj± postaæ: +\begin{alltt} + \emph{zmienna}[.\emph{program}] [=] \emph{warto¶æ} +\end{alltt}% + gdzie \samp{=} i~otaczaj±ce spacje s± opcjonalne. +\item + ,,\texttt{\var{zmienna}}'' zawieraæ mo¿e dowolne znaki poza spacj±, + \samp{=}, lub \samp{.} (kropk±), najbezpieczniej jednak u¿ywaæ znaków + z~zakresu \samp{A-Za-z\_}. +\item + Napis ,,\texttt{.\var{program}}'' ma zastosowanie w~wypadku, gdy + uruchamiany program nosi nazwê \texttt{\var{program}} lub + \texttt{\var{program}.exe}. Pozwala to ró¿nym odmianom \TeX-a stosowaæ + ró¿ne ¶cie¿ki przeszukiwania. +\item ,,\texttt{\var{warto¶æ}}'' zawieraæ mo¿e dowolne znaki poza + ,,\texttt{\%}'' i \samp{@}. + Nie mo¿na u¿ywaæ konstrukcji ,,\texttt{\$\var{zmienna}.\var{program}}'' + po prawej stronie. Zamiast tego trzeba zastosowaæ zmienn± pomocnicz±. + ¦rednik \samp{;}\ u¿yty w~,,\texttt{\var{warto¶æ}}'' zamieniany jest na + \samp{:}\ je¿eli systemem operacyjnym jest Unix; umo¿liwia to istnienie + wspólnego pliku \file{texmf.cnf} dla systemów Unix oraz Windows. +\item + Wszystkie definicje czytane s± zanim cokolwiek zostanie rozwiniête, tak + wiêc do zmiennych mo¿na siê odwo³ywaæ przed ich zdefiniowaniem. +\end{itemize} +Oto fragment pliku konfiguracyjnego, ilustruj±cy wiêkszo¶æ opisanych powy¿ej +regu³ notacji: +\ifSingleColumn +\verbatiminput{examples/ex5.tex} +\else +jest pokazany na rys.~\ref{fig:config-sample}. +\fi + +\subsubsection{Rozwijanie ¶cie¿ek} +\label{Path-expansion} + +\KPS{} rozpoznaje w~¶cie¿kach przeszukiwania pewne specjalne znaki oraz +konstrukcje, podobne do tych dostêpnych w~pow³okach Unix. +Jako ogólny przyk³ad: z³o¿ona ¶cie¿ka +\verb+~$USER/{foo,bar}//baz+ rozwija siê do wszystkich podkatalogów pod +katalogami \file{foo} i~\file{bar} w~katalogu g³ównym \texttt{\$USER}, +które zawieraj± katalog lub plik \file{baz}. +Rozwiniêcia te opisane s± w~poni¿szych podrozdzia³ach. + +\subsubsection{Rozwijanie domy¶lne} +\label{Default-expansion} + +\tolerance=2500 +Je¿eli ¶cie¿ka przeszukiwania najwiêkszego uprzywilejowania (patrz ,,¬ród³a +¶cie¿ek'' na stronie~\pageref{Path-sources}) zawiera +\emph{dodatkowy dwukropek} (np. na pocz±tku, na koñcu lub podwójny) to \KPS{} +wstawia w~tym miejscu nastêpn± zdefiniowan± w~hierarchii uprzywilejowania +¶cie¿kê przeszukiwania. +Je¿eli ta wstawiona ¶cie¿ka ma dodatkowy dwukropek, to dzieje siê dalej to samo. +Przyk³adowo, je¿eli ustawiæ zmienn± ¶rodowiskow± +\tolerance=1500 + +\begin{alltt} +> \Ucom{setenv TEXINPUTS /home/karl:} +\end{alltt} +oraz warto¶æ \code{TEXINPUTS} pobran± z~\file{texmf.cnf} + +\begin{alltt} + .:\$TEXMF//tex +\end{alltt} +koñcow± warto¶ci± u¿yt± w~przeszukiwaniu bêdzie: + +\begin{alltt} + /home/karl:.:\$TEXMF//tex +\end{alltt} + +Poniewa¿ nieu¿ytecznym by³oby wstawiaæ warto¶æ domy¶ln± w~wiêcej ni¿ jednym +miejscu, \KPS{} zmienia tylko jeden dodatkowy \samp{:}\ i~pozostawia +inne bez zmian. \KPS{} najpierw szuka dwukropków na pocz±tku linii, potem na koñcu, +a~nastêpnie podwójnych. + +\subsubsection{Rozwijanie nawiasów} + +U¿yteczna jest mo¿liwo¶æ rozwijania nawiasów, co oznacza, ¿e np. +\verb+v{a,b}w+ rozwija siê do \verb+vaw:vbw+. +Nawiasy mo¿na te¿ zagnie¿d¿aæ. +Funkcji tej mo¿na u¿yæ do zaimplementowania ró¿nych hierarchii \TeX-owych +przez przypisanie listy nawiasów do \code{\$TEXMF}. Przyk³adowo, +w~pliku \file{texmf.cnf} mo¿na znale¼æ nastêpuj±c± definicjê: +\begin{verbatim} + TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN} +\end{verbatim} +U¿ywaj±c jej, mo¿na nastêpnie napisaæ co¶ w~rodzaju: +\begin{verbatim} + TEXINPUTS = .;$TEXMF/tex// +\end{verbatim} +co oznacza, ¿e po szukaniu w~katalogu bie¿±cym bêd± przeszukane kolejno +\code{\$TEXMFHOME/tex}, \code{\$TEXMFLOCAL/tex}, \code{\$TEXMFVAR/tex} +i~\code{\$TEXMFMAIN/tex} (wszystkie wraz z~katalogami ni¿szego poziomu; +dwie ostatnie ¶cie¿ki \emph{wy³±cznie} na podstawie zawarto¶ci +pliku \file{ls-R}). +Jest to wygodny sposób na uruchamianie dwóch równoleg³ych struktur \TeX-owych, +jednej ,,zamro¿onej'' (np. na \CD), a~drugiej ci±gle uaktualnianej nowo +pojawiaj±cymi siê wersjami. +U¿ywaj±c zmiennej \code{\$TEXMF} we wszystkich definicjach daje pewno¶æ, +¿e najpierw przeszukiwane jest drzewo uaktualnione. + +\subsubsection{Rozwijanie podkatalogów} +\label{Subdirectory-expansion} + +Dwa lub wiêcej kolejnych ,,ciachów'' (,,/'') w~elemencie ¶cie¿ki, +wystêpuj±cych po nazwie katalogu~\var{d}, zastêpowanych jest przez wszystkie +podkatalogi~\var{d}, najpierw podkatalogi znajduj±ce siê bezpo¶rednio +pod~\var{d}, potem te pod powy¿szymi i~tak dalej. Na ka¿dym etapie +kolejno¶æ, w~jakiej przeszukiwane s± katalogi, jest \emph{nieokre¶lona}. + +Je¶li wyszczególni siê cz³ony nazwy pliku po \samp{//}, to uwzglêdnione zostan± +tylko te podkatalogi, które zawieraj± powy¿sze cz³ony. +Na przyk³ad \samp{/a//b} rozwija siê do katalogów \file{/a/1/b}, +\file{/a/2/b}, \file{/a/1/1/b} itd., ale nie do \file{/a/b/c} czy \file{/a/1}. + +Mo¿liwe jest wielokrotne u¿ycie \samp{//} w~¶cie¿ce, jednak¿e \samp{//} +wystêpuj±ce na pocz±tku ¶cie¿ki nie jest brane pod uwagê. + +\subsubsection{Lista znaków specjalnych i~ich znaczeñ -- podsumowanie} + +Poni¿sza lista podsumowuje znaczenie znaków specjalnych w~plikach +konfiguracyjnych. + +\newcommand{\CODE}[1]{\makebox[2.2em][l]{\code{#1}}} +\begin{description} +\item[\CODE{:}] znak rozdzielaj±cy w~specyfikacji ¶cie¿ki; umieszczony na +pocz±tku lub na koñcu ¶cie¿ki zastêpuje domy¶lne rozwiniêcie ¶cie¿ki; +\item[\CODE{;}] znak rozdzielaj±cy dla systemów nieuniksowych + (dzia³a tak jak ,,\code{:}''); +\item[\CODE{\$}] rozwijanie zmiennej; +\item[\CODE{\string~}] oznacza katalog g³ówny u¿ytkownika; +\item[\CODE{\char`\{\dots\char`\}}] rozwijanie nawiasów, np. + \verb+a{1,2}b+ zmieni siê w~\verb+a1b:a2b+; +\item[\CODE{//}] rozwijanie podkatalogów (mo¿e wyst±piæ gdziekolwiek + w~¶cie¿ce, poza jej pocz±tkiem); +\item[\CODE{\%}] pocz±tek komentarza, obejmuj±cego wszystkie znaki do koñca + linii; +\item[\CODE{\bs}] znak kontynuacji (pozwala na prze³amanie wiersza + z~wyra¿eniem); +\item[\CODE{!!}] przeszukiwanie \emph{tylko} bazy danych, + a~\emph{nie} dysku. +\end{description} + + +\subsection{Bazy nazw plików} +\label{Filename-database} + +Podczas przeszukiwania \KPS{} stara siê zminimalizowaæ dostêp do dysku. +Niemniej, w~przypadku instalacji ze zbyt du¿± liczb± katalogów +przegl±danie ka¿dego dopuszczalnego katalogu w~poszukiwaniu pliku mo¿e +zabieraæ sporo czasu (ma to miejsce zw³aszcza, je¿eli przeszukaæ trzeba setki +katalogów z~fontami). +Dlatego te¿ \KPS{} mo¿e u¿ywaæ zewnêtrznego pliku z~,,baz± danych'' +o~nazwie \file{ls-R}, który zawiera przypisania plików do katalogów. +Unika siê w~ten sposób czasoch³onnego przeszukiwania dysku. + +Drugi plik z~baz± danych -- \file{aliases} -- pozwala na nadawanie +dodatkowych nazw plikom zawartym w~\file{ls-R}. +Mo¿e to byæ pomocne do adaptacji do DOS-owej konwencji ,,8.3'' nazewnictwa +plików w~plikach ¼ród³owych. + +\subsubsection{Baza nazw plików} +\label{ls-R} + +Jak ju¿ wspomniano powy¿ej, plik zawieraj±cy g³ówn± bazê nazw +plików musi nosiæ nazwê \file{ls-R}. +W~katalogu podstawowym ka¿dej hierarchii \TeX-owej (domy¶lnie \code{\$TEXMF}), +któr± chcemy w³±czyæ w~mechanizm przeszukiwania, umieszczaæ mo¿na po jednym +pliku \file{ls-R}; w~wiêkszo¶ci przypadków istnieje tylko jedna hierarchia. +\KPS{} szuka pliku \file{ls-R} w~¶cie¿ce \code{TEXMFDBS}. + +Najlepszym sposobem stworzenia i~utrzymywania pliku \file{ls-R} jest +uruchomienie skryptu \code{mktexlsr}, bêd±cego sk³adnikiem dystrybucji. +Jest on wywo³ywany przez ró¿ne skrypty typu \samp{mktex...}. +W~zasadzie skrypt ten jedynie wykonuje polecenie +\begin{alltt} +cd \var{/your/texmf/root} && ls -LAR ./ >ls-R +\end{alltt} +zak³adaj±c, ¿e polecenie \code{ls} danego systemu utworzy w³a¶ciwy format +strumienia wyj¶ciowego (\acro{GNU} \code{ls} dzia³a prawid³owo). +Aby mieæ pewno¶æ, ¿e baza danych jest zawsze aktualna, wygodnie jest + przebudowywaæ j± regularnie za pomoc± demona \code{cron}. + %tak ¿e wraz ze zmianami + %w~instalowanych plikach -- np. po instalacji lub uaktualnianiu pakietu + %\LaTeX{} -- plik \file{ls-R} jest uaktualniany automatycznie. + +Je¶li pliku nie ma w~bazie danych, \KPS{} domy¶lnie przechodzi do +przeszukiwania dysku. Je¿eli jednak dany element ¶cie¿ki zaczyna sie od +\samp{!!}, w~poszukiwaniu tego elementu sprawdzona zostanie \emph{jedynie} +baza danych, a~nigdy dysk. + +\subsubsection{kpsewhich -- program do przeszukiwania ¶cie¿ek} +\label{Invoking-kpsewhich} + +Przeszukiwanie ¶cie¿ek przez program \texttt{kpsewhich} jest niezale¿ne od +jakiejkolwiek aplikacji. +Mo¿e on byæ przydatny jako rodzaj programu \code{find}, za pomoc± którego +lokalizowaæ mo¿na pliki w~hierarchiach \TeX-owych (jest on u¿ywany +intensywnie w~skryptach \samp{mktex...} tej dystrybucji). + +\begin{alltt} +> \Ucom{kpsewhich \var{opcje}\dots{} \var{nazwa-pliku}\dots{}} +\end{alltt} +Parametry wyszczególnione w~,,\texttt{\var{opcje}}'' mog± zaczynaæ siê zarówno od +\samp{-}, jak i~od \samp{-{}-}, a~dozwolony jest ka¿dy jednoznaczny skrót. + +\KPS{} traktuje ka¿dy argument nie bêd±cy parametrem jako nazwê pliku +i~zwraca pierwsz± odnalezion± nazwê. +Nie ma parametru nakazuj±cego zwracanie wszystkich nazw plików o~okre¶lonej +nazwie (w~tym celu mo¿na wykorzystaæ Unix-owy program \samp{find}). + +Wa¿niejsze parametry opisane s± poni¿ej. + +\begin{ttdescription} +\item[\texttt{-{}-dpi=\var{num}}]\mbox{}\\* + Ustaw rozdzielczo¶æ na ,,\texttt{\var{num}}''; ma to tylko wp³yw na + przeszukiwanie fontów \samp{gf} i~\samp{pk}. Dla zgodno¶ci + z~\cmdname{dvips} parametr + \samp{-D} dzia³a identycznie. Domy¶ln± warto¶ci± jest 600. +\item[\texttt{-{}-format=\var{nazwa}}]\mbox{}\\ + Ustawienie formatu (typu pliku) przeszukiwania na ,,\texttt{\var{nazwa}}''. + Domy¶lnie format odgadywany jest z~nazwy pliku. + Dla formatów, które nie maj± przydzielonego jednoznacznego rozszerzenia, + takich jak niektóre pliki \MP{}-owe czy pliki konfiguracyjne + \cmdname{dvips}-a, nale¿y wyszczególniæ nazwê, których listê wy¶wietli + uruchomienie \texttt{kpsewhich -{}-help}. + +\item[\texttt{-{}-mode=\var{napis}}]\mbox{}\\* + Ustaw nazwê trybu na ,,\texttt{\var{napis}}''; dotyczy to jedynie szukania + fontów \samp{gf} oraz \samp{pk}. + Brakuje warto¶ci domy¶lnej -- odnaleziony zostanie dowolny + wyszczególniony tryb. +\item[\texttt{-{}-must-exist}]\mbox{}\\ + Zrób wszystko co mo¿liwe, aby odnale¼æ pliki, w³±czaj±c w~to przede wszystkim + przeszukanie dysku. + Domy¶lnie, w~celu zwiêkszeniu efektywno¶ci dzia³ania, sprawdzana jest + tylko baza \file{ls-R}. +\item[\texttt{-{}-path=\var{napis}}]\mbox{}\\ + Szukaj w~¶cie¿ce ,,\texttt{\var{napis}}'' (rozdzielonej, jak + zwykle, dwukropkami), zamiast zgadywaæ ¶cie¿kê przeszukiwania z~nazwy + pliku. + \samp{//} i~wszystkie zwyk³e rozszerzenia s± mo¿liwe. + Parametry \samp{-{}-path} oraz \samp{-{}-format} wzajemnie siê wykluczaj±. +\item[\texttt{-{}-progname=\var{nazwa}}]\mbox{}\\ + Ustaw nazwê programu na ,,\texttt{\var{nazwa}}''. + Mo¿e to mieæ wp³yw na ¶cie¿kê przeszukiwania poprzez + ,,\texttt{.\var{program}}'' w~plikach konfiguracyjnych. + Ustawieniem domy¶lnym jest \samp{kpsewhich}. +\item[\texttt{-{}-show-path=\var{nazwa}}]\mbox{}\\ + Pokazuje ¶cie¿kê u¿ywan± do poszukiwania plików typu + ,,\texttt{\var{nazwa}}''. + U¿yte mo¿e byæ zarówno rozszerzenie (\samp{.pk}, \samp{.vf}, etc.), jak + i~nazwa pliku, tak jak w~wypadku parametru \samp{-{}-format}. +\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ + ustawia parametry wykrywania b³êdów na ,,\texttt{\var{num}}''. +\end{ttdescription} + +%Zmienne ¶rodowiskowe domy¶lnie ustawiane s± w~pliku konfiguracyjnym +%\file{texmf.cnf}. W~wypadku gdy chce siê uniewa¿niæ warto¶ci zmiennych +%wyszczególnione w~tym pliku, mo¿na narzuciæ ich ustawienie w~¶rodowisku, +%w~którym uruchamiane s± programy. + +\subsubsection{Przyk³ady u¿ycia} +\label{SExamplesofuse} + +Przyjrzyjmy sie teraz, jak dzia³a \KPS{}. + +\begin{alltt} +> \Ucom{kpsewhich article.cls} +/usr/local/texmf-dist/tex/latex/base/article.cls +\end{alltt} +Szukamy pliku \file{article.cls}. +Poniewa¿ rozszerzenie \samp{.cls} jest jednoznaczne, nie musimy zaznaczaæ, ¿e +poszukujemy pliku typu ,,tex'' (katalogi plików ¼ród³owych \TeX-a). +Znajdujemy go w~podkatalogu \file{tex/latex/base}, pod katalogiem nadrzêdnym +\samp{texmf-dist}. +Podobnie wszystkie poni¿sze pliki odnajdowane s± bez\-pro\-ble\-mo\-wo +dziêki swoim jednoznacznym rozszerzeniom: +\begin{alltt} +> \Ucom{kpsewhich array.sty} +/usr/local/texmf-dist/tex/latex/tools/array.sty +> \Ucom{kpsewhich latin1.def} +/usr/local/texmf-dist/tex/latex/base/latin1.def +> \Ucom{kpsewhich size10.clo} +/usr/local/texmf-dist/tex/latex/base/size10.clo +> \Ucom{kpsewhich small2e.tex} +/usr/local/texmf-dist/tex/latex/base/small2e.tex +> \Ucom{kpsewhich tugboat.bib} +/usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib +\end{alltt} + +\noindent (ostatni plik to \BibTeX-owa baza bibliograficzna dla artyku³ów +\textsl{TUGBoat}). + +\begin{alltt} +> \Ucom{kpsewhich cmr10.pk} +\end{alltt} +Pliki czcionek bitmapowych typu \file{.pk} u¿ywane s± przez sterowniki, +takie jak \cmdname{dvips} % ??? dvips to chyba nie przegl±darka --- +czy \cmdname{xdvi}. % w oryg. by³o display programs like dvips... +W~tym wypadku wynik przeszukiwania oka¿e siê pusty, poniewa¿ +w~systemie brak gotowych wygenerowanych czcionek \samp{.pk} Computer Modern +(wynika to z~faktu u¿ywania w~\TL{} fontów PostScript-owych Type1). +\begin{alltt} +> \Ucom{kpsewhich wsuipa10.pk} +\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk +\else /usr/local/texmf-var/fonts/pk/ljfour/public/ +..... wsuipa/wsuipa10.600pk +\fi\end{alltt} +Dla tych fontów (alfabetu fonetycznego) musieli¶my wygenerowaæ pliki +\samp{.pk}, a~poniewa¿ domy¶lnym \MF{}-owym trybem naszej instalacji jest +\texttt{ljfour} z~podstawow± rozdzielczo¶ci± 600dpi, zwracany jest taki +w³a¶nie wynik. +\begin{alltt} +> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} +\end{alltt} +W~tym wypadku, kiedy zaznaczamy, ¿e interesuje nas rozdzielczo¶æ +300dpi (\texttt{-dpi=300}), to widzimy, ¿e w~naszej instalacji taka +czcionka nie jest dostêpna. +Program taki jak \cmdname{dvips} czy \cmdname{xdvi} zatrzyma³by siê, aby +utworzyæ pliki \texttt{.pk} w~wymaganej rozdzielczo¶ci (u¿ywaj±c skryptu +\cmdname{mktexpk}). + +Zwrócimy teraz nasz± uwagê na pliki nag³ówkowe i~konfiguracyjne +programu \cmdname{dvips}. +Najpierw szukamy pliku PostScript-owego prologu \file{tex.pro}, +wykorzystywanego dla potrzeb \TeX-a. Drugi przyk³ad pokazuje +poszukiwanie pliku konfiguracyjnego \file{config.ps}, za¶ trzeci -- +szukanie pliku mapy czcionek PostScriptowych \file{psfonts.map} +(pocz±wszy od obecnej edycji, pliki \file{.map} i~\file{.enc} +maj± w³asne regu³y przeszukiwania ¶cie¿ek i~zmienione po³o¿enie w~ramach +drzew \dirname{texmf}). +Poniewa¿ rozszerzenie \samp{.ps} nie jest jednoznaczne, musimy zaznaczyæ +wyra¼nie jaki typ jest wymagany dla pliku +\texttt{config.ps} (,,\texttt{dvips config}''). +\begin{alltt} +> \Ucom{kpsewhich tex.pro} +/usr/local/texmf/dvips/base/tex.pro +> \Ucom{kpsewhich --format="dvips config" config.ps} +/usr/local/texmf-var/dvips/config/config.ps +> \Ucom{kpsewhich psfonts.map} +/usr/local/texmf-var/fonts/map/dvips/updmap/psfonts.map +\end{alltt} + +Nastêpnie przyjrzymy siê bli¿ej plikom pomocniczym fontów Times z~kolekcji +URW. W~standardzie nazewnictwa fontów maj± one prefiks \samp{utm}. +Pierwszy plik którego szukamy, to plik konfiguracyjny, zawieraj±cy nazwê +pliku z~przemapowaniem fontów: +\begin{alltt} +> \Ucom{kpsewhich --format="dvips config" config.utm} + /usr/local/texmf-dist/dvips/psnfss/config.utm +\end{alltt} +W~pliku tym znajduje siê wiersz: +\begin{alltt} + p +utm.map +\end{alltt} +wskazuj±cy na plik \file{utm.map}, który chcemy zlokalizowaæ w~nastêpnej +kolejno¶ci: +\begin{alltt} +> \Ucom{kpsewhich utm.map} + /usr/local/texmf-dist/fonts/map/dvips/times/utm.map +\end{alltt} +Plik z~przemapowaniem definiuje nazwy czcionek PostScriptowych Type~1 +w~zestawie fontów URW, za¶ jego zawarto¶æ wygl±da nastêpuj±co +(pokazane s± tylko fragmenty wierszy): +\begin{alltt} +utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} +\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb +\else /usr/local/texmf-dist/fonts/type1/ +... urw/utm/utmr8a.pfb +\fi\end{alltt} + +Powy¿sze przyk³ady pokazuj±, jak ³atwo mo¿na znajdowaæ lokalizacjê danego +pliku. Jest to wa¿ne zw³aszcza wówczas, gdy istnieje podejrzenie, ¿e gdzie¶ +zawieruszy³a siê b³êdna wersja jakiego¶ pliku; \cmdname{kpsewhich} poka¿e tylko +pierwszy napotkany plik. + +\subsubsection{Diagnostyka b³êdów} +\label{sec:debugging} + +Czasami niezbêdne s± informacje o~tym, jak program sobie radzi +z~odniesieniami do plików. Aby da³o siê je uzyskaæ w~wygodny sposób, +\KPS{} oferuje ró¿ne poziomy diagnostyki b³êdów: +\begin{itemize} +\item[\texttt{\ 1}] wywo³ania \texttt{stat} (testy pliku). Podczas + uruchamiania z~uaktualnion± baz± danych \file{ls-R} nie powinno to + przewa¿nie dawaæ ¿adnego wyniku. +\item[\texttt{\ 2}] Zapis odwo³añ do tablic asocjacyjnych (\emph{hash + tables}), takich jak baza \file{ls-R}, pliki przemapowañ, pliki konfiguracyjne. +\item[\texttt{\ 4}] Operacje otwarcia i~zamkniêcia pliku. +\item[\texttt{\ 8}] Ogólne informacje o~¶cie¿kach dla typów + plików szukanych przez \KPS; u¿yteczne dla znalezienia ¶cie¿ki + zdefiniowanej dla danego pliku. +\item[\texttt{16}] Lista katalogów dla ka¿dego z~elementów ¶cie¿ki + (odnosi siê tylko do poszukiwañ na dysku). +\item[\texttt{32}] Poszukiwania plików. +\end{itemize} +Warto¶æ \texttt{-1} ustawia wszystkie powy¿sze opcje -- w~praktyce, +poszukuj±c przyczyny b³êdów, prawdopodobnie bêdziesz zawsze u¿ywaæ +tych poziomów. + +Podobnie, w~przypadku programu \cmdname{dvips}, ustawiaj±c kombinacjê +prze³±czników wykrywania b³êdów, mo¿na dok³adnie ¶ledziæ, sk±d pochodz± pliki. +W~sytuacji, gdy plik nie zostanie odnaleziony, widaæ, w~których katalogach +program szuka³ danego pliku, dziêki czemu mo¿na siê zorientowaæ, w~czym +problem. + +Ogólnie mówi±c, poniewa¿ programy odwo³uj± siê wewnêtrznie do +biblioteki \KPS{}, opcje wykrywania b³êdów mo¿na wybraæ przy u¿yciu +zmiennej ¶rodowiskowej \envname{KPATHSEA\_DEBUG}, ustawiaj±c j± +na opisan± powy¿ej warto¶æ (kombinacjê warto¶ci). + +\noindent +\textbf{Uwaga dla u¿ytkowników Windows:} w~systemie tym nie³atwo +przekierowaæ komunikaty programu do pliku. Do celów diagnostycznych +mo¿na chwilowo ustawiæ zmienne (w~oknie CMD): +\begin{verbatim} +SET KPATHSEA_DEBUG_OUTPUT=err.log +SET KPATHSEA_DEBUG=-1 +\end{verbatim} + +Rozwa¿my na przyk³ad ma³y \LaTeX-owy plik ¼ród³owy \file{hello-world.tex}, +który zawiera: +\begin{verbatim} + \documentclass{article} + \begin{document} + Hello World! + \end{document} +\end{verbatim} +Ten ma³y plik korzysta jedynie z~fontu \file{cmr10}. Przyjrzyjmy siê, jak +\cmdname{dvips} przygotowuje plik PostScript-owy (chcemy u¿yæ wersji Type1 +fontu Computer Modern, st±d opcja \texttt{-Pcms}). +\begin{alltt} +> \Ucom{dvips -d4100 hello-world -Pcms -o} +\end{alltt} +Mamy tu do czynienia jednocze¶nie z~czwart± klas± wykrywania b³êdów +programu \cmdname{dvips} (¶cie¿ki fontowe) oraz z~rozwijaniem elementu +¶cie¿ki przez \KPS{} (patrz: \emph{Dvips Reference Manual}, +\OnCD{texmf/doc/dvips/dvips.pdf}). + %Komunikaty z~uruchomienia programu (lekko zmodyfikowane) znajduj± siê + %na~rys.~\ref{fig:dvipsdbga}. + %\begin{figure*}[tp] + %\centering + %\input{examples/ex6a.tex} + %\caption{Szukanie pliku konfiguracyjnego}\label{fig:dvipsdbga} + % + %\bigskip + % + %\input{examples/ex6b.tex} + %\caption{Szukanie pliku prologu}\label{fig:dvipsdbgb} + % + %\bigskip + % + %\input{examples/ex6c.tex} + %\caption{Szukanie pliku fontu}\label{fig:dvipsdbgc} + %\end{figure*} + Program \cmdname{dvips} zaczyna pracê od zlokalizowania potrzebnych mu plików. +Najpierw znajduje plik \file{texmf.cnf}, który zawiera ¶cie¿ki +przeszukiwania dla innych plików. Potem znajduje bazê danych \file{ls-R} +(w~celu optymalizacji szukania plików), nastêpnie plik \file{aliases}, +który umo¿liwia deklarowanie ró¿nych nazw (np. krótkie \acro{DOS}-owe ,,8.3'' +i~bardziej naturalne d³u¿sze wersje) dla tych samych plików. +Nastêpnie \cmdname{dvips} znajduje podstawowy plik konfiguracyjny +\file{config.ps}, zanim poszuka pliku z~ustawieniami u¿ytkownika +\file{.dvipsrc} (który w~tym wypadku \emph{nie} zostaje odnaleziony). +W~koñcu \cmdname{dvips} lokalizuje plik konfiguracyjny \file{config.cms} +dla fontów PostScript-owych Computer Modern (jest to inicjowane przez +dodanie parametru \texttt{-Pcms} przy uruchamianiu programu). +Plik ten zawiera listê plików z~,,mapami'', które definiuj± relacje +pomiêdzy \TeX-owymi, PostScript-owymi i~systemowymi nazwami fontów. +\begin{alltt} +> \Ucom{more /usr/local/texmf/dvips/config/config.cms} +p +bsr.map +p +bakomaextra.map +\end{alltt} +W~ten sposób \cmdname{dvips} wyszukuje wszystkie te pliki oraz g³ówny plik +z~przemapowaniem +\file{psfonts.map}, który ³adowany jest domy¶lnie (zawiera on deklaracje +czêsto u¿ywanych fontów postscriptowych; wiêcej szczegó³ów na temat +postscriptowych plików przemapowañ fontów mo¿na znale¼æ w~ostatniej czê¶ci +rozdzia³u \ref{SExamplesofuse}). + +W~tym miejscu \cmdname{dvips} zg³asza siê u¿ytkownikowi: +\begin{alltt}\ifSingleColumn +This is dvips 5.86 Copyright 1999 Radical Eye Software (www.radicaleye.com) +\else\small{}This is dvips 5.86 Copyright 1999 Radical Eye... +\fi\end{alltt}% decided to accept slight overrun in tub case +\ifSingleColumn +\ldots potem szuka pliku prologu \file{texc.pro}: +\begin{alltt}\small +kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro +\end{alltt} +\else +potem szuka pliku prologu \file{texc.pro}. + %(patrz rys.~\ref{fig:dvipsdbgb}). + +\fi +Po znalezieniu szukanego pliku \cmdname{dvips} podaje datê i~czas +oraz informuje o~generowaniu pliku \file{hello-world.ps}. +Poniewa¿ potrzebuje pliku z~fontem \file{cmr10}, a~jest on +zadeklarowany jako dostêpny, wy¶wietla komunikat: +\begin{alltt}\small +TeX output 1998.02.26:1204' -> hello-world.ps +Defining font () cmr10 at 10.0pt +Font cmr10 is resident. +\end{alltt} +Teraz trwa poszukiwanie pliku \file{cmr10.tfm}, który zostaje znaleziony, +po czym \cmdname{dvips} powo³uje siê na kilka innych plików startowych +(nie pokazanych). W~koñcu przyk³adowy font Type1 \file{cmr10.pfb} +zostaje zlokalizowany i~do³±czony do pliku wynikowego (patrz ostatnia linia): +\begin{alltt}\small +kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, + path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: + /var/tex/fonts/tfm//). +kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm +kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, + ... + +kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb +[1] +\end{alltt} + +\subsection{Parametry kontroluj±ce dzia³anie programów} +Inn± u¿yteczn± cech± \Webc{} jest mo¿liwo¶æ ustalania wielu parametrów +okre¶laj±cych wielko¶æ pamiêci za pomoc± pliku \texttt{texmf.cnf}. + %Za³±cznik~\ref{app:texmf.cnf} zaczynaj±cy siê na + %stronie~\pageref{app:texmf.cnf} zawiera listing pliku \texttt{texmf.cnf}. + Ustawienia wszystkich parametrów znajduj± siê w~czê¶ci trzeciej pliku. +Najwa¿niejszymi zmiennymi s±: +\begin{description} +\item[\code{main\_memory}] Ca³kowita wielko¶æ pamiêci dostêpnej dla + \TeX-a, \MF{}-a i~\MP{}-a. Dla ka¿dego nowego ustawienia tej zmiennej + nale¿y wykonaæ nowy format. + %Przyk³adowo, mo¿esz wygenerowaæ ,,ogromn±'' wersjê formatu \TeX{} i~nazwaæ + %taki plik \texttt{hugetex.fmt}. + %Dziêki standardowemu sposobowi nazywania programów przez + %\KPS{}, okre¶lona warto¶æ zmiennej \verb|main_memory| bêdzie + %przeczytana z~pliku \texttt{texmf.cnf} (por. warto¶æ standardow± + %oraz warto¶æ ,,ogromn±'', wykorzystywan± przez program \texttt{hugetex}, + %itd.). + % +\item[\code{extra\_mem\_bot}] Dodatkowa wielko¶æ pamiêci przeznaczonej + na ,,du¿e'' struktury danych \TeX-a, takie jak: pude³ka, kleje itd.; + przydatna zw³aszcza w~wypadku korzystania z~pakietu \PiCTeX{}. + % +\item[\code{font\_mem\_size}] Wielko¶æ pamiêci przeznaczonej przez + \TeX-a na informacje o~fontach. Jest to mniej wiêcej ogólna + wielko¶æ wczytywanych przez \TeX-a plików TFM. + % +\item[\code{hash\_extra}] Dodatkowa wielko¶æ pamiêci przeznaczonej + na tablicê zawieraj±c± nazwy instrukcji. Tablica g³ówna + mo¿e zmie¶ciæ w~przybli¿eniu 10000 nazw; wielko¶æ ta mo¿e siê okazaæ + zbyt ma³a, np. w~wypadku obszernej ksi±¿ki zawieraj±cej liczne + odsy³acze. Domy¶lna warto¶æ \texttt{hash\_extra} to \texttt{50000}. +\end{description} + % +Oczywi¶cie powy¿sza mo¿liwo¶æ nie zast±pi prawdziwej, dynamicznej +alokacji pamiêci. Jest to jednak niezwykle trudne +do zaimplementowania w~obecnej wersji \TeX-a i~dlatego +powy¿sze parametry stanowi± praktyczny kompromis, pozwalaj±c +na pewn± elastyczno¶æ. + +Nale¿y tu jednak nadmieniæ, i¿ nie wszystkie programy korzystaj± +z tych zmiennych. Np. Lua\TeX\ posiada nowoczesn±, +w~pe³ni dynamiczn± alokacjê pamiêci, a zatem powy¿sze zmienne s± +w tym przypadku po prostu ignorowane. + +%%==== +%\begin{comment} %% nie wiem czemu rezygnowaæ z tej czê¶ci (SW) +\section{Budowa systemu na nowej platformie uniksowej}\label{sec:build} +Je¿eli mamy do czynienia z~platform±, dla której nie s± dostarczone binaria, +trzeba bêdzie skompilowaæ \TeX-a oraz towarzysz±ce mu programy. +Nie jest to takie trudne, jak siê wydaje. +Wszystko czego potrzebujemy, znajduje siê na \DVD{} w~katalogu +\texttt{source}. + +Najpierw nale¿y zainstalowaæ g³ówne drzewo plików \TeX-owych z~\CD{} +\TL{} (najlepiej wykonaæ instalacjê podstawow±, bez wybierania +binariów systemowych). + +\subsection{Warunki wstêpne} +Do skompilowania ca³ego \TeX-a i~jego programów pomocniczych potrzeba +oko³o 100 megabajtów wolnego miejsca na dysku. +Potrzebny jest tak¿e kompilator \acro{ANSI}~C, oprogramowanie \cmdname{make}, +skaner leksykalny oraz generator parserów. +Programy u¿ytkowe \acro{GNU} (\cmdname{gcc}, \acro{GNU} +\cmdname{make}, \cmdname{m4}, \cmdname{flex}, \cmdname{bison}) +s± najlepiej przetestowanymi na ró¿nych platformach. +Poprawnie powinny pracowaæ \cmdname{gcc}-2.7.*, \cmdname{flex}-2.4.7 +i~\acro{GNU}\,\cmdname{make}-3.72.1 lub nowszy. +Mo¿na te¿ korzystaæ z~innych kompilatorów C i~programów +\cmdname{make}, wymaga to jednak dobrego zrozumienia zasad tworzenia +programów uniksowych, aby móc poradziæ sobie z~ewentualnymi problemami. + %W~wyniku wykonania polecenia \texttt{uname} powinni¶my + %otrzymaæ jak±¶ rozs±dn± warto¶æ. + +\subsection{Konfiguracja} +Nale¿y rozpakowaæ ¼ród³a ze skompresowanego pliku \texttt{tar} +z~katalogu \dirname{source} na twardy dysk, a~potem przej¶æ do katalogu, +do którego zosta³y one skopiowane. +Teraz trzeba siê zdecydowaæ, gdzie bêdzie g³ówny katalog instalacji, +np.\ \path|/usr/TeX| lub \path|/usr/local/TeX|. +Naturalnie, nale¿y u¿yæ tej samej lokalizacji, która zosta³a u¿yta +podczas instalacji g³ównego drzewa \TeX-owego. + +Uruchomiæ \textsf{configure} z~linii poleceñ: +\begin{alltt} +> \Ucom{./configure --prefix=/usr/local/TeX} +\end{alltt} + +Katalog ,,prefix'' to ten, w~którym zainstalowane zosta³o g³ówne drzewo +\TeX-owe. Zostanie u¿yty nastêpuj±cy uk³ad katalogów + (\verb|$TEXDIR| oznacza wybrany powy¿ej katalog): + +\noindent +\begin{tabular}{>{\ttfamily}ll@{}} + \dirname{$TEXDIR/man} & strony manuala uniksowego,\\ + \dirname{$TEXDIR/share/texmf} & g³ówne drzewo \TeX-owe, + zawieraj±ce makra itp.,\\ + \dirname{$TEXDIR/info} & podrêczniki w formacie \acro{GNU} + info,\\ + \dirname{$TEXDIR/bin/$PLATFORM} & binaria\\ +\end{tabular} +%$ + +Mo¿na unikn±æ stosowania ,,\dirname{share/}'' przed katalogiem +\dirname{texmf}, poniewa¿ \dirname{$TEXDIR/share/texmf} +i~\dirname{$TEXDIR/texmf} s± wykrywane automatycznie przez skrypt \cmdname{configure}. +W~razie wybrania innego katalogu, trzeba ten katalog wyszczególniæ +parametrem \verb|--datadir| skryptu \cmdname{configure}. + +Je¿eli nie chcemy u¿ywaæ katalogu \dirname{$PLATFORM} +(a~wiêc umie¶ciæ binaria bezpo¶rednio w~\dirname{$TEXDIR/bin}), to +w~wywo³aniu skryptu \cmdname{configure} nale¿y u¿yæ parametru +\verb|--disable-multiplatform|. + +Wiêcej dostêpnych parametrów (np. pomijanie pakietów opcjonalnych, takich +jak \OMEGA) mo¿na zobaczyæ, uruchamiaj±c +\texttt{./configure -{}-help}. + +\subsection{Uruchamianie \textsf{make}} +Po upewnieniu siê, ¿e nie jest ustawiona zmienna pow³oki \texttt{noclobber}, +nale¿y napisaæ: +\begin{alltt} +> \Ucom{make world} +\end{alltt} +i~\ldots zaparzyæ sobie kawê. + +Mo¿e siê te¿ przydaæ zapisanie ca³ego procesu +kompilacji w~pliku \texttt{.log}: +\begin{alltt} +> \Ucom{sh -c "make world >world.log 2>\&1" \&} +\end{alltt} +Zanim stwierdzimy, ¿e wszystko jest w~porz±dku, warto sprawdziæ, czy w~pliku +\texttt{.log} nie ma komunikatów b³êdów (kiedy polecenie zwraca kod b³êdu, +\acro{GNU} \cmdname{make} zawsze u¿ywa sekwencji \samp{***}), +i~czy utworzone zosta³y wszystkie binaria: +\begin{alltt} +> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} +> \Ucom{ls | wc} +\end{alltt} +Oczekiwanym rezultatem jest ponad 200. Polecenie \texttt{make world} jest +równowa¿ne z~\texttt{make all install strip}. +Je¶li do uruchamiania \texttt{make install} potrzebne s± specjalne +uprawnienia, mo¿na uruchomiæ dwie oddzielne sesje \cmdname{make}: +\begin{alltt} +> \Ucom{make all} +> \Ucom{su} +> \Ucom{make install strip} +\end{alltt} + +\subsection{Koñcowe kroki konfiguracyjne} +Nale¿y uaktualniæ zmienn± \envname{PATH} o~nazwê katalogu zawieraj±cego +w³a¶nie zainstalowane binaria (np.\ +\dirname{/usr/local/TeX/bin/mips-sgi-irix6.3}); podobnie post±piæ trzeba +z~\envname{MANPATH} i~\envname{INFOPATH} i~do³±czyæ do nich +odpowiednie nazwy podkatalogów, tj.\ +\dirname{$TEXDIR/man} oraz \dirname{$TEXDIR/info}. +Patrz czê¶æ~\ref{sec:postinstall} (str.~\pageref{sec:postinstall}). + +Je¶li zechcesz udostêpniæ skompilowane przez siebie programy, skontaktuj +siê z~nami (\url{tex-live@tug.org}); chêtnie umie¶cimy je na stronie \TL. +%\end{comment} + +%-------------------------- +\section{Podziêkowania} %\label{sec:acknowl} + +\TL{} jest wspólnym dzie³em prawie wszystkich grup \TeX-owych. +Niniejsza edycja \TL{} zosta³a opracowana pod kierownictwem Karla Berry'ego, +przy g³ównym wspó³udziale: + +\begin{itemize*} +\item grup \TeX-owych: miêdzynarodowej, niemieckiej, holenderskiej i~polskiej + (odpowiednio: \acro{TUG}, \acro{DANTE} e.V., \acro{NTG}, i~\acro{GUST}), + które wspólnie zapewniaj± potrzebn± infrastrukturê techniczn± + i~organizacyjn±. Do³±cz do swojej grupy \TeX-owej!; +\item zespo³u \acro{CTAN} (w~szczególno¶ci Robina Fairbairnsa, Jima + Hef{}ferona i~Rainera Sch\"opfa), który dystrybuuje obrazy \TL{} i~udostêpnia + wspóln± infrastrukturê s³u¿±c± aktualizacji pakietów, od której zale¿y \TL{}; +\item Petera Breitenlohnera i~zespo³u \eTeX, którzy stworzyli stabiln± + podstawê przysz³ych wersji \TeX-a (Peter dodatkowo s³u¿y nieustann± pomoc± + w~wykorzystaniu narzêdzi autotools w~\TL); +\item Thomasa Essera, autora wspania³ego \teTeX-a, bez którego + \TL{} z~ca³± pewno¶ci± by nie powsta³, i~którego sta³a + pomoc umo¿liwi³a doskonalenie tej dystrybucji; +\item Michaela Goossensa, który by³ wspó³autorem pierwotnej dokumentacji; +\item Eitana Gurari, autora programu \TeX4ht{} (wykorzystanego do + tworzenia niniejszej dokumentacji w~wersji \HTML), który niezmordowanie + pracowa³ nad jego ulepszaniem i~b³yskawicznie dostarcza³ poprawki; +\item Hansa Hagena, który dostosowywa³ \ConTeXt\ do potrzeb \TL; +\item \Thanh{}a, Martina Schr\"odera i~zespo³u pdf\TeX-a, którzy ci±gle + ulepszali mo¿liwo¶ci \TeX-a; +\item Hartmuta Henkela, maj±cego istotny udzia³ w~rozwoju pdf\TeX-a, + Lua\TeX-a i~innych programów; +\item Taco Hoekwatera, który wznowi³ rozwój MetaPosta i~pracowa³ nad + Lua\TeX-em, jak te¿ pomóg³ w~integracji \ConTeXt\ w~\TL; +\item Paw³a Jackowskiego, który wykona³ instalator dla Windows \cmdname{tlpm} + i~Tomka £uczaka, twórcy \cmdname{tlpmgui} (programy te by³y wykorzystane + w~poprzednich edycjach); +\item Akira Kakuto, który dostarczy³ programy dla Windows, pochodz±ce + z~dystrybucji \acro{W32TEX} + (\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}), + stale dostosowywane i~aktualizowane dla potrzeb \TL; +\item Jonathana Kew z firmy \acro{SIL}, który zainicjowa³ now± ¶cie¿kê + rozwojow± -- Xe\TeX{}, i~który w³o¿y³ sporo wysi³ku w~zintegrowanie + tego programu z~\TL, jak równie¿ zapocz±tkowa³ prace nad instalatorem dla + Mac\TeX; +\item Dicka Kocha, który pielêgnuje Mac\TeX-a (\url{http://tug.org/mactex}) + w~¶cis³ym po³±czeniu z~\TL i~bardzo sympatycznie wspó³pracuje; +\item Reinharda Kotuchy, maj±cego istotny udzia³ w~stworzeniu nowej infrastruktury + i~programu instalacyjnego dla \TL{} 2008, uparcie d±¿±cego do ujednolicenia + dzia³ania \TL{} w~Windows i~Unix, który równie¿ opracowa³ skrypt + \texttt{getnonfreefonts} i~wykona³ wiele innych prac; +\item Siep Kroonenberg, która równie¿ wziê³a udzia³ w~stworzeniu nowej + infrastruktury i~programu instalacyjnego dla \TL{} 2008 (szczególnie dla + Windows) oraz w³o¿y³a ogrom pracy aktualizuj±c tê dokumentacjê; +\item Petra Ol\shac{}\aac{}ka, który koordynowa³ i~sprawdza³ + przygotowanie czeskich i~s³owackich pakietów; +\item Toshio Oshimy, który opracowa³ przegl±darkê \cmdname{dviout} dla Windows; +\item Manuela P\'egouri\'e-Gonnarda, który pomóg³ w~aktualizacji pakietów + i~pracowa³ nad \cmdname{tldoc}. +\item Fabrice'a Popineau, który pierwszy stworzy³ wersje oprogramowania + dla Windows; +\item Norberta Preininga, g³ównego architekta infrastruktury i~programu + instalacyjnego \TL{} 2008, a~przyczyni³ siê te¿ do aktualizacji pakietów, + koordynowania (wraz z~Frankiem K\"usterem) debianowej wersji \TL{}, + i~przedstawi³ wiele sugestii ulepszeñ; +\item Sebastiana Rahtza, który stworzy³ \TL{} i~kierowa³ projektem przez + wiele lat; +\item Vladimira Volovicha, który wydatnie pomóg³ w~rozwi±zywaniu problemów + przeno¶no¶ci, szczególnie za¶ umo¿liwi³ do³±czenia \cmdname{xindy}; +\item Staszka Wawrykiewicza, g³ównego testuj±cego \TL{} w~ró¿nych systemach, + który ponadto koordynowa³ przygotowanie wszystkich polskich dodatków (fontów, + programów instalacyjnych i~wielu innych); +\item Olafa Webera, który cierpliwie pielêgnowa³ Web2C, od którego wszystko zale¿y; +\item Gerbena Wierda, który przygotowa³ oprogramowanie i~wsparcie dla + \MacOSX{}; +\item Grahama Williamsa, którego prace nad katalogiem pakietów bardzo + pomog³y w~przygotowaniu dystrybucji. +\end{itemize*} + +Binaria dla ró¿nych platform skompilowali: +Reinhard Kotucha (\pkgname{x86\_64-linux}), +Tim Arnold (\pkgname{hppa-hpux}), +Randy Au (\pkgname{amd64-freebsd}), +Edd Barrett (\pkgname{i386-openbsd}), +Karl Berry (\pkgname{i386-linux}), +Akira Kakuto (\pkgname{win32}), +Dick Koch (\pkgname{universal-darwin}), +Manfred Lotz (\pkgname{i386-freebsd}), +Norbert Preining (\pkgname{alpha-linux}), +Arthur Reutenauer (\pkgname{sparc-linux}), +Thomas Schmitz (\pkgname{powerpc-linux}), +Apostolos Syropoulos (\pkgname{i386-solaris}), +Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-solaris}), +Olaf Weber (\pkgname{mips-irix}). +Informacje na temat procesu budowy \TL{} mo¿na znale¼æ na stonie: +\url{http://tug.org/texlive/build.html}. + +Aktualizacje i~t³umaczenia dokumentacji wykonali: +Siep Kroonenberg i~Karl Berry (angielski), +Daniel Flipo (francuski), +Klaus H\"oppner (niemiecki), +Petr Sojka i~Jan Busa (czeski\slash s³owacki), +Boris Veytsman (rosyjski), +Staszek Wawrykiewicz (polski). +Na stronie \url{http://tug.org/texlive/doc.html} bêd± umieszczane ewentualne +aktualizacje tej dokumentacji. + +Oczywi¶cie, najwa¿niejsze podziêkowania nale¿± siê Donaldowi Knuthowi +za stworzenie systemu \TeX{} i~ofiarowanie go nam wszystkim. + +%%% +\section{Historia} +\label{sec:history} + +\subsection{Poprzednie wersje} + +Dystrybucja \TL{} jest wspólnym przedsiêwziêciem +grup U¿ytkowników Systemu \TeX{} z Niemiec, Holandii, Wielkiej +Brytanii, Francji, Czech, S³owacji, Polski, Indii i~Rosji oraz grupy +miêdzynarodowej TUG (\emph{\TeX{} Users Group}). +Dyskusje nad projektem rozpoczê³y siê pod koniec 1993 roku, kiedy holenderska +Grupa U¿ytkowników \TeX-a rozpoczê³a prace nad swoim +4All\TeX{} \CD{} dla u¿ytkowników \acro{MS-DOS}. W~tym te¿ +czasie pojawi³y siê nadzieje na opracowanie jednego \CD{} dla +wszystkich systemów. +Projekt ten by³ wprawdzie zbyt ambitny, zrodzi³ jednak nie tylko bardzo +popularny i~uwieñczony du¿ym powodzeniem projekt 4All\TeX{} \CD{}, +lecz równie¿ spowodowa³ powstanie Grupy Roboczej TUG ds. Standardu Katalogów +\TeX-owych (\emph{\TeX{} Directory Structure}), okre¶laj±cego, w~jaki +sposób tworzyæ zgodne i~³atwe do zarz±dzania zestawy pakietów \TeX-owych. +Koñcowy raport \TDS{} zosta³ opublikowany w~grudniowym numerze +\textsl{TUGboat}-a, i~jasnym siê sta³o, ¿e +jednym z~oczekiwanych wyników wprowadzenia tego standardu mog³aby +byæ modelowa struktura na p³ytce \CD. +Wydana wówczas p³ytka \CD{} by³a bezpo¶rednim rezultatem rozwa¿añ i~zaleceñ +Grupy Roboczej ds. \TDS. +Jasne tak¿e by³o, ¿e sukces 4All\TeX{} \CD{} pokaza³, ¿e +u¿ytkownicy Unixa tak¿e wiele by zyskali, mog±c korzystaæ +z~podobnie ³atwego w~instalacji/pielêgnacji i~u¿ytkowaniu systemu. +By³o to jednym z~celów projektu \TL. + +Projekt przygotowania p³ytki \CD, opartej na standardzie \TDS i~zorientowanej +na systemy uniksowe, rozpocz±³ siê jesieni± 1995 roku. Szybko +zdecydowali¶my siê na wykorzystanie \teTeX-a autorstwa Thomasa Essera, poniewa¿ +dzia³a³ na wielu platformach i~zosta³ zaprojektowany z~my¶l± +o~przeno¶no¶ci pomiêdzy ró¿nymi systemami plików. Thomas zgodzi³ siê pomóc +i~prace rozpoczê³y siê na dobre na pocz±tku 1996 roku. Pierwsze wydanie +ukaza³o siê w~maju 1996 roku. Na pocz±tku 1997 roku Karl Berry udostêpni³ +now±, istotnie zmienion± wersjê swojego pakietu \Webc, zawieraj±c± prawie +wszystkie funkcje wprowadzone do \teTeX-a przez Thomasa Essera. W~zwi±zku +z~tym zdecydowali¶my siê oprzeæ drugie wydanie \CD{} na standardowej +bibliotece \Webc, z~dodaniem skryptu \texttt{texconfig} z~pakietu \teTeX. +Trzecie wydanie \CD{} by³o oparte na \Webc{} wersji 7.2, przygotowanej przez +Olafa Webera. W~tym samym czasie zosta³a przygotowana nowa wersja \teTeX-a +i~\TL{} udostêpnia³ prawie wszystkie jego nowe funkcje. +Czwarta edycja by³a przygotowana podobnie, +z~u¿yciem nowej wersji te\TeX-a i~nowej wersji \Webc{} (7.3). +Wtedy to te¿ zapocz±tkowano kompletn± dystrybucjê dla Windows. + +Edycja pi±ta (marzec 2000) zawiera³a wiele poprawek i~uzupe³nieñ; +zaktualizowano setki pakietów. Szczegó³ow± zawarto¶æ pakietów +zapisano w~plikach XML. +G³ówn± zmian± w~\TeX\ Live~5 by³o usuniêcie programów, które nie mia³y +statusu {\it public domain}. Zawarto¶æ ca³ej p³ytki powinna odpowiadaæ ustaleniom +Debian Free Software Guidelines (\url{http://www.debian.org/intro/free}). +Do³o¿yli¶my wszelkich starañ, aby sprawdziæ warunki licencyjne pakietów, +nadal jednak bardzo prosimy o~zg³aszanie zauwa¿onych pomy³ek. + +Szósta edycja (lipiec 2001) zawiera³a aktualizacje ca³ego materia³u. G³ówn± +zmian± by³o wprowadzenie nowej koncepcji programów instalacyjnych -- u¿ytkownik +mia³ odt±d mo¿liwo¶æ dok³adniejszego wyboru potrzebnych zestawów i~pakietów. +Zestawy dotycz±ce obs³ugi poszczególnych jêzyków zosta³y ca³kowicie +zreorganizowane, dziêki czemu wybór jednego z~nich nie tylko instalowa³ +potrzebne makra i~fonty, ale te¿ przygotowywa³ odpowiedni plik +\texttt{language.dat}. + +\TL~7 (rok 2002) zawiera³ po raz pierwszy oprogramowanie dla \MacOSX{} +i -- jak zwykle -- aktualizacjê wszelkich programów i~pakietów. +Wa¿nym zadaniem, które wykonano, by³o ujednolicenie plików ¼ród³owych +programów z~dystrybucj± te\TeX. W~programach instalacyjnych wprowadzono +mo¿liwo¶æ wyboru bardziej ogólnych, predefiniowanych zestawów pakietów +(m.in. dla u¿ytkowników francuskojêzycznych oraz polskich). Nowo¶ci± +by³o tak¿e wprowadzenie procedury aktualizacji map fontowych dla Dvips +i~PDFTeX podczas instalacji oraz doinstalowywania pakietów fontowych. + +W~2003~r., wraz z~nap³ywem aktualizacji i~dodatkowych nowych pakietów, +okaza³o siê, ¿e \TL{} nie mie¶ci siê na pojedynczym \CD. +Zmuszeni byli¶my podzieliæ \TL{} na trzy dystrybucje, które wydano +na \DVD{} i~dwóch p³ytkach \CD. Ponadto: + +\begin{itemize*} +\item na ¿yczenie ,,\LaTeX{} team'' zmieniono standardowe u¿ycie + programów \cmdname{latex} i~\cmdname{pdflatex}~-- by korzysta³y + one z~\eTeX{} (patrz str.~\pageref{text:etex}); +\item za³±czono nowe fonty obwiedniowe Latin Modern, które zastêpuj± + m.in. fonty EC (zawieraj±c komplet znaków europejskich), szczególnie + do tworzenia poprawnych plików PDF; +\item usuniêto binaria dla platformy Alpha \acro{OSF} (poprzednio + usuniêto tak¿e binaria dla \acro{HPUX}), niestety nie uda³o siê znale¼æ + osób chêtnych do wykonania kompilacji; +\item zmieniono instalacjê w~systemach Windows, wprowadzaj±c po raz pierwszy + zintegrowane ¶rodowisko pracy, oparte na edytorze XEmacs; +\item potrzebne programy pomocnicze dla Windows (Perl, Ghost\-script, + Image\-Magick, Ispell) instalowano w~strukturze katalogów + instalacji \TL; +\item mapy fontowe, z~których korzystaj± programy \cmdname{dvips}, + \cmdname{dvipdfm} oraz \cmdname{pdftex}, generowano odt±d w~katalogu + \dirname{texmf/fonts/map}; +\item \TeX{}, \MF{} oraz \MP{} domy¶lnie pozwala³y wypisywaæ komunikaty + na ekranie i~w~pliku .log, a~tak¿e w~operacjach \verb|\write| w~ich + reprezentacji 8-bitowej, zamiast tradycyjnej notacji \verb|^^|; + w~\TL{}~7 eksperymentalnie wprowadzono zale¿no¶æ przekodowania + wyj¶cia programów od systemowej strony kodowej, potem ten pomys³ + zarzucono; +\item znacznie zmieniono niniejsz± dokumentacjê; +\item wreszcie, poniewa¿ numery wersji kolejnych edycji mog³y wprowadzaæ + w~b³±d, postanowiono identyfikowaæ edycje \TL{} zgodnie z~rokiem + wydania. +\end{itemize*} + +\subsection{Edycja 2004} + +Jak w~ka¿dej kolejnej wersji, w~2004 roku uaktualniono wiele pakietów +i~programów. Poni¿ej wymieniamy najbardziej istotne zmiany. + +\begin{itemize} +\item Gdy mieli¶my ju¿ lokalnie zainstalowane fonty, które korzysta³y +z~w³asnych plików \filename{.map} i/lub \filename{.enc}, \emph{nale¿a³o} +przenie¶æ te pliki w~nowe miejsce w~strukturze \filename{texmf/}. + +Pliki \filename{.map} (map fontowych) s± odt±d wyszukiwane w~podkatalogach +\dirname{fonts/map} (w~ka¿dym drzewie \filename{texmf}), zgodnie ze ¶cie¿k± +okre¶lon± przez zmienn± \envname{TEXFONTMAPS}. Analogicznie, pliki +\filename{.enc} (przekodowañ fontów) s± odt±d wyszukiwane w~podkatalogach +\dirname{fonts/enc}, zgodnie ze ¶cie¿k± okre¶lon± przez zmienn± +\envname{ENCFONTS}. O~niew³a¶ciwie umieszczonych plikach tego typu +zostaniemy ostrze¿eni podczas uruchomienia programu \cmdname{updmap}. +Zmiany te wprowadzono w~celu uporz±dkowania struktury katalogów: wszystkie +pliki dotycz±ce fontów znajduj± siê odt±d w~ramach jednego podkatalogu +\dirname{fonts/}. + +Metody radzenia sobie z~sytuacjami zwi±zanymi z~przej¶ciem na nowy uk³ad +katalogów omawia³ artyku³ \url{http://tug.org/texlive/mapenc.html}. + +\item Do \TK\ \DVD{} dodano now± dystrybucjê dla Windows o~nazwie +pro\TeX{}t (opart± na \MIKTEX-u). By³a ona dostêpna tak¿e na odrêbnym \CD. +Choæ pro\TeX{}t nie bazuje na implementacji Web2C, stosuje uk³ad katalogów +zgodny z~\TDS (patrz czê¶æ~\ref{sec:struct-tl} na +str.~\pageref{sec:struct-tl}). + +\item W ramach \TL{} dotychczasowe pojedyncze drzewo katalogów +\dirname{texmf} zosta³o rozdzielone na trzy mniejsze: \dirname{texmf}, +\dirname{texmf-dist} i~\dirname{texmf-doc} (patrz +czê¶æ~\ref{sec:tld}, str.~\pageref{sec:tld}) oraz pliki \filename{README} +w~ka¿dym z~tych katalogów). + +\item Wszystkie pliki makr wczytywane przez \TeX-a zosta³y +umieszczone wy³±cznie w~podkalogu \dirname{tex} w~ramach +\dirname{texmf*}. Tym samym usuniêto zbêdne katalogi +\dirname{etex}, \dirname{pdftex}, \dirname{pdfetex} itp. i~uproszczono +metody wyszukiwania plików. + +\item Pomocnicze skrypty wykonywalne, niezale¿ne od platformy +i~zwykle uruchamiane w~sposób automatyczny, by³y odt±d +umieszczone w~nowym podkatalogu \dirname{scripts} w~ramach \dirname{texmf*}. +Znajdowane s± poleceniem \verb|kpsewhich -format=texmfscripts|. +Programy korzystaj±ce z tych skryptów mog³y wymagaæ modyfikacji. +Patrz \CDref{texmf-doc/doc/english/tds/tds.html\#Scripts} +{\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}. + +\item Prawie wszystkie formaty traktuj± od tego wydania wiêkszo¶æ znaków jako +jawnie ,,wy¶wietlalne'' (\emph{printable}), nie za¶, jak by³o dotychczas, +konwertowane na \TeX-ow± notacjê \verb|^^|. By³o to mo¿liwe dziêki domy¶lnemu +wczytywaniu tablicy przekodowañ \filename{cp227.tcx}. Dok³adniej, znaki +o~kodach 32--256, HT, VT oraz FF zosta³y potraktowane dos³ownie podczas +wy¶wietlania komunikatów. Wyj±tkiem jest plain \TeX{} (tylko znaki z~zakresu +32--127 s± nie zmieniane), \ConTeXt{} (znaki z zakresu 0--255) oraz formaty +bazuj±ce na Omedze. Podobna domy¶lna w³a¶ciwo¶æ wystêpowa³a w~\TL\,2003, ale +w~tej edycji zosta³a zaimplementowana w~bardziej elegancki sposób +i~z~wiêkszymi mo¿liwo¶ciami indywidualnego dostosowania (patrz +\CDref{texmf/doc/web2c/web2c.html\#TCX-files} {\texttt{texmf/doc/web2c/web2c. +tml\#TCX-files}}. (Warto wspomnieæ, ¿e wczytuj±c Unicode, \TeX{} mo¿e +w~komunikatach b³êdów pokazywaæ niekompletne sekwencje znaków, poniewa¿ +zosta³ zaprojektowany ,,bajtowo''.) + %%! hmmm, ca³y akapit by o strumieniach we-wy? + +\item Program \textsf{pdfetex} zosta³ domy¶ln± ,,maszyn±'' dla +wiêkszo¶ci formatów (nie dotyczy to samego Plain \textsf{tex}). +Domy¶lnie, gdy uruchamiamy polecenie \textsf{latex}, \textsf{mex} +itp., generowane s± pliki \acro{DVI}. Mo¿liwe jest jednak wykorzystanie +w~\LaTeX, \ConTeXt{} itp. m.in. w³a¶ciwo¶ci mikrotypograficznych +zaimplementowanych w~\textsf{pdftex}, a~tak¿e rozszerzonych cech \eTeX-a +(\OnCD{texmf-dist/doc/etex/base/}). + +Oznacza to tak¿e, co warto podkre¶liæ, ¿e \emph{zalecane} jest odt±d u¿ycie +pakietu \pkgname{ifpdf} (który dzia³a zarówno z~plain, jak i~\LaTeX) +lub analogicznych makr. Zwyk³e sprawdzanie czy zdefiniowano \cs{pdfoutput} +b±d¼ kilka innych poleceñ pierwotnych mo¿e nie wystarczyæ do rozstrzygniêcia +czy nie jest generowany plik \acro{PDF}. W~2004 roku podjêli¶my +wysi³ek by zachowaæ, najlepiej jak to mo¿liwe, kompatybilno¶æ +z~dotychczasowymi przyzwyczajeniami u¿ytkowników. Brano wówczas pod uwagê, +¿e \cs{pdfoutput} mo¿e byæ zdefiniowany nawet wtedy, +gdy generowany jest plik \acro{DVI}. + +\item pdf\TeX\ (\url{http://pdftex.org}) zyska³ wówczas wiele nowych +cech: + + \begin{itemize*} + \item \cs{pdfmapfile} i~\cs{pdfmapline} pozwalaj± okre¶liæ + z~poziomu dokumentu u¿yte mapy fontowe, a~tak¿e pojedyncze + dodatkowe wpisy w~tych mapach. + + \item mikrotypograficzne operacje z~fontami s± ³atwiejsze w u¿yciu;\\ + \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} + + \item wszystkie parametry pracy pdf\TeX-a, dotychczas okre¶lane + w~specjalnym pliku konfiguracyjnym \filename{pdftex.cfg}, musz± byæ + odt±d ustawiane poleceniami wbudowanymi, jak w~pliku + \filename{pdftexconfig.tex}; plik \filename{pdftex.cfg} + nie jest ju¿ w~ogóle wykorzystywany. Po zmianie \filename{pdftexconfig.tex} + nale¿a³o na nowo wygenerowaæ pliki formatów (wci±¿ jednak u¿ytkownik mia³ + pe³n± swobodê okre¶lania parametrów w~redagowanym dokumencie); + + \item wiêcej informacji zawarto w~podrêczniku pdf\TeX-a: + \OnCD{texmf-dist/doc/pdftex/manual/pdftex-a.pdf}. + + \end{itemize*} + +\item Polecenie \cs{input} w~programach \cmdname{tex}, + \cmdname{mf} oraz \cmdname{mpost} akceptowa³o odt±d nazwy + plików ograniczone podwójnymi apostrofami, zawieraj±ce spacje i~inne + znaki, np.: +\begin{verbatim} +\input "nazwa_pliku ze spacjami" % plain +\input{"nazwa_pliku ze spacjami"} % latex +\end{verbatim} +Wiêcej informacji zawarto w~podrêczniku Web2C: \OnCD{texmf/doc/web2c}. + +\item \texttt{-output-directory} -- nowa opcja programów \cmdname{tex}, + \cmdname{mf} oraz \cmdname{mpost} -- pozwala³a na zapisanie wyniku pracy + w~wyspecyfikowanym katalogu (np. mo¿na uruchomiæ program \texttt{tex} + z~plikiem znajduj±cym siê na dysku tylko do odczytu, za¶ wynik zapisaæ + na dysku pozwalaj±cym na~to); + +\item Rozszerzenie enc\TeX\ zosta³o szczê¶liwie w³±czone do Web2C. + Aby uaktywniæ to rozszerzenie, nale¿a³o podczas generowania formatu + u¿yæ opcji \optname{-enc}. Ogólnie mówi±c, enc\TeX\ obs³uguje + przekodowanie wej¶cia i~wyj¶cia, w³±czaj±c tak¿e Unicode (\acro{UTF}-8) + (patrz \OnCD{texmf-dist/doc/generic/enctex/} oraz + \url{http://www.olsak.net/enctex.html}). + +\item Udostêpniono nowy program Aleph, który ³±czy³ cechy \eTeX\ i~\OMEGA. + Skromna dokumentacja jest dostêpna na \OnCD{texmf-dist/doc/aleph/base} + oraz \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph}. + Format oparty na \LaTeX-u dla programu Aleph nazwano \textsf{lamed}. + +\item Dystrybucja \LaTeX-a zosta³a po raz pierwszy zaopatrzona w~now± + licencjê \acro{LPPL}, odt±d w~pe³ni zgodn± i~aprobowan± przez zalecenia + okre¶lone w~licencji Debiana. O~nowo¶ciach i~uaktualnieniach mo¿na siê + dowiedzieæ przegl±daj±c pliki \filename{ltnews} + w~\OnCD{texmf-dist/doc/latex/base}. + +\item Do³±czono tak¿e program \cmdname{dvipng} konwertuj±cy pliki \acro{DVI} +do formatu graficznego \acro{PNG} (\OnCD{texmf/doc/man/man1/dvipng.1}). + +\item W~porozumieniu i~z~pomoc± autora, Claudio Beccariego, ograniczono + pakiet \pkgname{cbgreek} do zestawu fontów rozs±dnego rozmiaru. Usuniêto + sporadycznie u¿ywane fonty konturowe i~s³u¿±ce do prezentacji. Pe³en + zestaw by³ oczywi¶cie nadal dostêpny z~serwerów \acro{CTAN} + (\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). + +\item Usuniêto program \cmdname{oxdvi}; jego funkcje przej±³ + \cmdname{xdvi}. + +\item Programy z~przedrostkiem \cmdname{ini} oraz \cmdname{vir} + (np. \cmdname{initex}), które zwykle by³y dowi±zaniami do programów + \cmdname{tex}, \cmdname{mf} i~\cmdname{mpost}, nie by³y od tej pory dostêpne + -- w~zupe³no¶ci wystarcza u¿ycie w~wierszu poleceñ opcji \optname{-ini}. + +\item Dystrybucja nie zawiera³a binariów dla platformy \textsf{i386-openbsd} + (g³ównie z~powodu braku chêtnych do wykonania kompilacji). + +\item W~systemie \textsf{sparc-solaris} nale¿a³o ustawiæ zmienn± systemow± + \envname{LD\_LIBRARY\_PATH}, aby uruchomiæ programy \pkgname{t1utils}. + Binaria by³y kompilowane w~C++, ale w~tym systemie brakowa³o standardowego + po³o¿enia bibliotek uruchomieniowych. Wiedziano o~tym ju¿ wcze¶niej, + nie by³o to jednak dotychczas udokumentowane. Z~kolei dla systemu + \textsf{mips-irix} wymagana by³a obecno¶æ bibliotek \acro{MIPS}pro 7.4. + +\end{itemize} + +\subsection{Edycja 2005} + +Kolejna edycja przynios³a, jak zwykle, mnóstwo aktualizacji pakietów +i~programów. Struktura dystrybucji ustabilizowa³a siê, niemniej +pojawi³o siê nieco zmian w~konfiguracji: + +\begin{itemize} + +\item Wprowadzono nowe skrypty \cmdname{texconfig-sys}, \cmdname{updmap-sys} + i~\cmdname{fmtutil-sys}, których zadaniem jest modyfikowanie plików + konfiguracyjnych w~g³ównych drzewach katalogów systemu. Dotychczasowe + skrypty \cmdname{texconfig}, \cmdname{updmap} i~\cmdname{fmtutil} + modyfikuj± odt±d pliki u¿ytkownika w~katalogu \dirname{$HOME/.texlive2005}. + %(Patrz czê¶æ~\ref{sec:texconfig}, str.~\pageref{sec:texconfig}). + +\item Dodano nowe zmienne ¶rodowiskowe \envname{TEXMFCONFIG} + i~\envname{TEXMFSYSCONFIG}, które wskazuj± po³o¿enie drzew katalogów + z~plikami konfiguracyjnymi, odpowiednio: u¿ytkownika i~systemu. Tak wiêc + mog³o okazaæ siê koniecznym przeniesienie w³asnych wersji + \filename{fmtutil.cnf} i~\filename{updmap.cfg} w~odpowiednie miejsca. + Inn± mo¿liwo¶ci± by³o przedefiniowanie \envname{TEXMFCONFIG} lub + \envname{TEXMFSYSCONFIG} w~pliku \file{texmf.cnf}. W~ka¿dym z~przypadków + po³o¿enie tych plików i~przypisania + \envname{TEXMFCONFIG} i~\envname{TEXMFSYSCONFIG} musz± byæ zgodne. + (Patrz czê¶æ~\ref{sec:texmftrees}, str.~\pageref{sec:texmftrees}.) + +\item W~wydaniu z~poprzedniego roku podczas tworzenia wynikowego pliku + DVI \verb|\pdfoutput| i~podobne polecenia pozostawa³y niezdefiniowane, mimo + ¿e u¿ywany by³ program \cmdname{pdfetex}. Zgodnie z~obietnic±, + w~2005 roku zarzucono to rozwi±zanie (jego celem by³o zapewnienie + kompatybilno¶ci). Z~tego powodu u¿ytkownik by³ zmuszony zmieniæ te dokumenty, + które u¿ywa³y \verb|\ifx\pdfoutput\undefined| do sprawdzania, czy plik + wynikowy ma byæ w~formacie PDF. Zamiast tego nale¿a³o zastosowaæ pakiet + \pkgname{ifpdf.sty}, który dzia³a zarówno z~plain \TeX-em jak i~\LaTeX-em, + albo zapo¿yczyæ zastosowane w~nim rozwi±zania. + +\item W~wydaniu z~2004 roku zmieniono wiêkszo¶æ formatów tak, by + na wyj¶ciu 8-bitowe znaki by³y reprezentowane przez same siebie (por. + poprzednia czê¶æ). Nowy plik TCX o~nazwie \filename{empty.tcx} pozwala³ + w~³atwy sposób uzyskaæ w~razie potrzeby oryginaln± notacjê (\verb|^^|), + np.: + +\begin{verbatim} +latex --translate-file=empty.tcx twojplik.tex +\end{verbatim} + +\item Do³±czono nowy program \cmdname{dvipdfmx}, s³u¿±cy do konwersji DVI + do PDF. Program jest aktywnie pielêgnowan± wersj± programu + \cmdname{dvipdfm}, który wci±¿ jest dostêpny, ale nie jest ju¿ jednak + polecany. + +\item Nowe programy \cmdname{pdfopen} i~\cmdname{pdfclose} pozwala³y na + prze³adowanie plików PDF w~Adobe Acrobat Reader, bez konieczno¶ci ponownego + uruchamiania programu. (Inne przegl±darki formatu PDF, jak \cmdname{xpdf}, + \cmdname{gv} i~\cmdname{gsview}, nigdy na tê przypad³o¶æ nie cierpia³y.) + +\item Dla spójno¶ci, zmienne \envname{HOMETEXMF} i~\envname{VARTEXMF} zosta³y + przemianowane odpowiednio na \envname{TEXMFHOME} i~\envname{TEXMFSYSVAR}. + Zachowano zmienn± \envname{TEXMFVAR}, przeznaczon± domy¶lnie dla + u¿ytkownika. Patrz te¿ punkt pierwszy, powy¿ej. + +\end{itemize} + +\subsection{Edycja 2007} + +Najwiêksz± nowo¶ci± edycji lat 2006 i~2007 by³ Xe\TeX{}, +w~postaci programów \texttt{xetex} i~\texttt{xelatex}; patrz +\OnCD{texmf-dist/doc/xetex/XeTeX-reference.pdf} lub +\url{http://scripts.sil.org/xetex}. + +W istotny sposób zosta³ zaktualizowany MetaPost, zaplanowano tak¿e jego +dalszy rozwój (\url{http://tug.org/metapost/articles}); to samo dotyczy +pdf\TeX-a (\url{http://tug.org/applications/pdftex}). + +Pliki formatów (pdf)TeX-a (\filename{.fmt}) oraz analogiczne dla MetaPosta +i~Meta\-Fonta s± od tej edycji zapisywane w~podkatalogach +\dirname{texmf/web2c}, choæ sam ten katalog jest nadal przeszukiwany. +Podkatalogi te maj± nazwê zgodn± z~zastosowanym podczas generowania +,,silnikiem'', np. \filename{tex}, \filename{pdftex} lub \filename{xetex}. +Zmiana ta nie powinna byæ zauwa¿alna w~typowym u¿yciu. + +Program \texttt{tex} (plain) od tej edycji ju¿ nie analizowa³ pierwszego +wiersza rozpoczynaj±cego siê znakami \texttt{\%\&}, aby ustaliæ jaki ma +wczytaæ format. Pozosta³ zatem czysty, Knuthowy \TeX. \LaTeX\ i~wszystkie +pozosta³e formaty nadal analizuj± pierwszy wiersz z~\texttt{\%\&}. + +Oczywi¶cie, jak zwykle, w~okresie od poprzedniego wydania opracowano setki +innych aktualizacji pakietów i programów. Kolejne aktualizacje mo¿na znale¼æ +tradycyjnie na \acro{CTAN} (\url{http://www.ctan.org}). + +Drzewo ¼ród³owe \TL{} jest odt±d przechowywane w~Subversion. Przegl±danie +umo¿liwia standardowy interfejs www, a~jego adres zamieszczono na stronie +\url{http://tug.org.pl/texlive}. +Mimo i¿ nie widaæ efektów tej zmiany w koñcowej dystrybucji, mamy nadziejê, +¿e w~nadchodz±cych latach bêdzie to stabilne repozytorium oprogramowania +dla rozwoju \TL{}. + +W~maju 2006~r. Thomas Esser og³osi³, ¿e zaprzestaje aktualizowania +dystrybucji te\TeX{} (\url{http://tug.org/tetex}). Spowodowa³o to znaczny +wzrost zainteresowanie \TL, szczególnie w¶ród dystrybutorów +\acro{GNU}/Linuksa. (W~\TL{} zdefiniowano w przybli¿eniu równowa¿ny, nowy +schemat instalacyjny pod nazw± \texttt{tetex}.) Mamy nadziejê, ¿e +w~przysz³o¶ci doprowadzi to do takich ulepszeñ w~otoczeniu \TeX-owym, na +których skorzystaj± wszyscy. + +\medskip \noindent + %%!Koñcowa uwaga, dotycz±ca przesz³o¶ci: + Wszystkie wydania \TL{}, wraz z~dodatkowymi materia³ami (np. ok³adkami +p³ytek), s± dostêpne na stronie: +\url{ftp://tug.org/historic/systems/texlive}. + +\subsection{Wydanie obecne} +\label{sec:tlcurrent} + +W 2008 roku ca³a infrastruktura \TL{} zosta³a przeprojektowana +i~przeprogramowana. Informacja dotycz±ca instalacji jest przechowywana +obecnie w~zwyk³ym pliku tekstowym \filename{tlpkg/texlive.tlpdb}. + +Po zainstalowaniu \TL{} wreszcie jest mo¿liwa jego aktualizacja z~internetu, +podobnie jak od paru lat umo¿liwia to dystrybucja MiK\TeX. Zamierzamy +regularnie aktualizowaæ pakiety, w~miarê jak bêd± siê pojawiaæ na serwerach +\CTAN. + +W~tym wydaniu pojawi³ siê nowy ,,silnik'', Lua\TeX\ +(\url{http://luatex.org}). Prócz nowych, elastycznych mo¿liwo¶ci +dotycz±cych sk³adu, udostêpnia on doskona³y jêzyk skryptowy do +zastosowania zarówno w~dokumentach \TeX-owych, jak i~poza nimi. + +Obs³uga dla Windows i~platform opartych na Unix zosta³a obecnie znacznie +bardziej zunifikowana. W~szczególno¶ci wiêkszo¶æ skryptów w~Perlu i~Lua +dostêpna jest teraz tak¿e dla Windows (zastosowano ,,wewnêtrzny'' Perl, +dostarczany wraz z~\TL). + +Pojawi³ siê nowy skrypt \cmdname{tlmgr} (patrz czê¶æ~\ref{sec:tlmgr}), który +staje siê g³ównym narzêdziem do zarz±dzania \TL{} po jego instalacji. +Umo¿liwia on aktualizacjê pakietów wraz z~niezbêdnymi wtedy czynno¶ciami, +jak regenerowanie formatów, aktualizacja map fontowych itp. + +Wraz z pojawieniem siê \cmdname{tlmgr} niektóre funkcje \cmdname{texconfig} +zosta³y zablokowane (edycja plików konfiguracyjnych formatów i~wzorców +przenoszenia). + +Program \cmdname{xindy} do tworzenia skorowidzów +(\url{http://xindy.sourceforge.net/}) jest obecnie dostêpny dla wiêkszo¶ci +platform. + +Narzêdzie \cmdname{kpsewhich} mo¿e obecnie raportowaæ wszystkie wyniki +przeszukiwania danego pliku (parametr \optname{--all}), jak równie¿ +ograniczyæ wyszukiwanie do jednego katalogu (parametr \optname{--subdir}). + +Program \cmdname{dvipdfmx} posiada obecnie funkcjê \cmdname{extractbb} +uzyskania informacji o~prostok±cie ograniczaj±cym (\textit{bounding box}); +jest to jedna z~ostatnich cech przejêtych od dawniej u¿ywanego programu +\cmdname{dvipdfm} (który jest nadal dostêpny). + +Usuniêto aliasy fontów \filename{Times-Roman}, \filename{Helvetica}, itd. +Ró¿ne pakiety korzysta³y z~nich w~nieoczekiwany sposób (np. spodziewaj±c +siê, ¿e fonty te bêd± mia³y ró¿ne kodowanie). Nie ma obecnie dobrego sposobu +na rozwi±zanie tych sprzeczno¶ci. + +Usuniêto format \pkgname{platex}, by unikn±æ konfliktu nazwy z~u¿ywanym od +wielu lat japoñskim pakietem \pkgname{platex}; pakiet \pkgname{polski} (czyli +dawny \pkgname{platex}) jest obecnie wystarczaj±cym sposobem na polonizacjê +dla \LaTeX-a. + +Usuniêto pliki \filename{.pool}, które s± obecnie wkompilowane w~programy, +co u³atwia ich aktualizacjê. + +Do tego wydania w³±czono tak¿e ostatnie zmiany dokonane przez +Donalda Knutha (tzw. \textit{\TeX\ tuneup of 2008}); patrz: +\url{http://tug.org/TUGboat/Articles/tb29-2/tb92knut.pdf}. + +\subsection{Przysz³e wersje} + +\emph{Niniejsza dystrybucja nie jest doskona³a!} Planujemy kontynuowaæ +wydawanie nowych wersji i~chcieliby¶my, ¿eby zawiera³y one jeszcze wiêcej +pomocnej dokumentacji, wiêcej programów u¿ytkowych, lepsze programy +instalacyjne oraz stale ulepszany i~poprawiany katalog makr +i~fontów. Zadanie to jest wykonywane przez ciê¿ko pracuj±cych ochotników, +po¶wiêcaj±cych na to wiele swojego wolnego czasu. Wiele jeszcze zosta³o do +zrobienia. Je¿eli mo¿esz pomóc, nie zastanawiaj siê i~przy³±cz siê do nas. +Patrz: \url{http://tug.org/texlive/contribute.html}. + +Prosimy o~przesy³anie poprawek, sugestii i~uzupe³nieñ oraz deklaracji +pomocy w~opracowywaniu kolejnych edycji pod adres: +%\begin{quote} +\email{tex-live@tug.org} +%\url{http://tug.org/texlive} +%\end{quote} + +%Uaktualnienia, og³oszenia i~wskazówki bêd± dostêpne na stronie +%\url{http://tug.org/texlive.html}. + +\end{document} + diff --git a/Master/texmf/doc/texlive/source/texlive-ru/Makefile b/Master/texmf/doc/texlive/source/texlive-ru/Makefile new file mode 100644 index 00000000000..93708128b74 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-ru/Makefile @@ -0,0 +1,3 @@ +include ../texlive-en/Makefile +doc = texlive-ru +lang = russian diff --git a/Master/texmf/doc/texlive/source/texlive-ru/live4ht.cfg b/Master/texmf/doc/texlive/source/texlive-ru/live4ht.cfg new file mode 100644 index 00000000000..508ccca27c8 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-ru/live4ht.cfg @@ -0,0 +1,47 @@ +% tex4ht configuration file for the TeX Live documentation. +% Accumulated over many years. Public domain. +% +% html specifies the main output format. +% info for extra debugging info in the log files. + +% better approach is to have html in one piece (including footnotes). +% also the newest TeX4ht could produce UTF-8 output (-utf8 option) +\Preamble{charset=iso-8859-5,html,info,fn-in} + +% add extra stylesheet +\Configure{@HEAD}{\HCode{% +\Hnewline +\Hnewline +}} + +% or LaTeX complains it is missing. +\begin{document} + +\EndPreamble + +% simplify output for HTML. We leave TeX and LaTeX alone, since tex4ht +% actually does the lowered E (and raised A) in CSS. +\def\OMEGA{Omega} +\def\LaTeXe{LaTeX2e} +\def\eTeX{e-\TeX} +\def\acro#1{#1} +\def\MF{Metafont} +\def\BibTeX{BibTeX} +\def\warningbox{} +\def\endwarningbox{} + +\newif\ifhackliterals +\ifx\tldocenglish\undefined \else \hackliteralstrue \fi +\ifx\tldocrussian\undefined \else \hackliteralstrue \fi +\ifx\tldocgerman\undefined \else \hackliteralstrue \fi +% +\ifhackliterals + % these definitions cause "missing } inserted" at \end{tabularx} in + % French and Czech. don't know why. + % + % don't make these into links, as happens with \path. We only have a couple + % special characters that actually occur. + \def\dirname{\texttt\bgroup\catcode`\$=12 \catcode`\_=12 \finishliteral} + \def\finishliteral#1{#1\egroup} + \let\filename=\dirname +\fi diff --git a/Master/texmf/doc/texlive/source/texlive-ru/texlive-ru.tex b/Master/texmf/doc/texlive/source/texlive-ru/texlive-ru.tex new file mode 100644 index 00000000000..9184449b75c --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-ru/texlive-ru.tex @@ -0,0 +1,2998 @@ +% $Id$ +% +%\def\Status{1} +\documentclass{article} +\let\tldocrussian=1 % for live4ht.cfg +\usepackage{tex-live} +\usepackage[koi8-r]{inputenc} +\usepackage[russian]{babel} +\newcommand\Unix{Unix} +\newcommand\Windows{Windows} +\usepackage{indentfirst, cmap} +\def\p.{ÓÔÒ.~}% +\renewcommand{\samp}[1]{<<\texttt{#1}>>} +% +\begin{document} + +\title{% + {\huge \textit{òÕËÏ×ÏÄÓÔ×Ï ÐÏÌØÚÏ×ÁÔÅÌÑ \protect\TL{}}\\\strut} + {\LARGE \textsf{\TL{} 2008}} +} + +\author{òÅÄÁËÔÏÒ: ëÁÒÌ âÅÒÒÉ\\[3mm] + \url{http://tug.org/texlive/}} +\date{éÀÌØ 2008} + +\maketitle + + +\begin{multicols}{2} +\tableofcontents +\listoftables +\end{multicols} + +\section{÷×ÅÄÅÎÉÅ} +\label{sec:intro} + +\subsection{\TeX\ Live É \TeX\ Collection} + + +÷ ÜÔÏÍ ÄÏËÕÍÅÎÔÅ ÏÐÉÓÁÎÙ ÏÓÎÏ×ÎÙÅ ×ÏÚÍÏÖÎÏÓÔÉ ÐÒÏÇÒÁÍÍÎÏÇÏ ÐÒÏÄÕËÔÁ +\TL{} "--- ÄÉÓÔÒÉÂÕÔÉ×Á \TeX{}Á É ÄÒÕÇÉÈ ÐÒÏÇÒÁÍÍ ÄÌÑ +\acro{GNU}/ìÉÎÕËÓÁ É ÄÒÕÇÉÈ àÎÉËÓÏ×, \MacOSX É (32-ÂÉÔÎÙÈ) Windows. + +\TL{} ÍÏÖÎÏ ÓËÁÞÁÔØ Ó éÎÔÅÒÎÅÔÁ, Á ÍÏÖÎÏ ÐÏÌÕÞÉÔØ ÎÁ \DVD{} <<\TK{}>>. üÔÉ +\DVD{} ÒÁÓÐÒÏÓÔÒÁÎÑÀÔÓÑ ÇÒÕÐÐÁÍÉ ÐÏÌØÚÏ×ÁÔÅÌÅÊ \TeX Á. ÷ ÒÁÚÄÅÌÅ +\ref{sec:tl-coll-dists} ËÒÁÔËÏ ÏÐÉÓÁÎÏ ÓÏÄÅÒÖÁÎÉÅ ÔÁËÏÇÏ \DVD{}. é +\TL{}, É \TK{} ÐÏÄÄÅÒÖÉ×ÁÀÔÓÑ ÇÒÕÐÐÁÍÉ ÐÏÌØÚÏ×ÁÔÅÌÅÊ \TeX Á. ÷ ÜÔÏÍ +ÄÏËÕÍÅÎÔÅ × ÏÓÎÏ×ÎÏÍ ÏÐÉÓÁÎ \TL{}. + +÷ \TL{} ×ËÌÀÞÅÎÙ ÐÒÏÇÒÁÍÍÙ \TeX{}, \LaTeXe{}, \ConTeXt, \MF, \MP, +\BibTeX{} É ÍÎÏÇÉÅ ÄÒÕÇÉÅ; ÏÂÛÉÒÎÁÑ ËÏÌÌÅËÃÉÑ ÍÁËÒÏÓÏ×, ÛÒÉÆÔÏ× É +ÄÏËÕÍÅÎÔÁÃÉÉ; Á ÔÁËÖÅ ÐÏÄÄÅÒÖËÁ ×£ÒÓÔËÉ ÎÁ ÍÎÏÇÉÈ ÑÚÙËÁÈ ÍÉÒÁ. + + +âÏÌÅÅ ÎÏ×ÙÅ ×ÅÒÓÉÉ ÐÁËÅÔÏ×, ×ËÌÀÞ£ÎÎÙÈ × ÄÉÓÔÒÉÂÕÔÉ×, ÍÏÖÎÏ ÎÁÊÔÉ × +ÁÒÈÉ×Å \acro{CTAN}, \url{http://www.ctan.org}. + +ëÒÁÔËÉÊ ÓÐÉÓÏË ÏÓÎÏ×ÎÙÈ ÉÚÍÅÎÅÎÉÊ × ÜÔÏÍ ÉÚÄÁÎÉÉ \TeXLive{} ÍÏÖÎÏ +ÎÁÊÔÉ × ÒÁÚÄÅÌÅ~\ref{sec:history}, \p.\pageref{sec:history}. + + +\subsection{ðÏÄÄÅÒÖÉ×ÁÅÍÙÅ ÏÐÅÒÁÃÉÏÎÎÙÅ ÓÉÓÔÅÍÙ} +\label{sec:os-support} + +÷ \TL{} ×ËÌÀÞÅÎÙ ÓËÏÍÐÉÌÉÒÏ×ÁÎÎÙÅ ÐÒÏÇÒÁÍÍÙ ÄÌÑ ÍÎÏÇÉÈ ÀÎÉËÓÏÐÏÄÏÂÎÙÈ +ÓÉÓÔÅÍ, ×ËÌÀÞÁÑ \MacOSX. éÓÈÏÄÎÙÊ ËÏÄ ÔÁËÖÅ ×ËÌÀÞÅÎ × ÄÉÓÔÒÉÂÕÔÉ×, +ÞÔÏ ÐÏÚ×ÏÌÑÅÔ ÕÓÔÁÎÏ×ÉÔØ \TL{} ÎÁ ÍÁÛÉÎÁÈ, ÄÌÑ ÁÒÈÉÔÅËÔÕÒ ËÏÔÏÒÙÈ ÍÙ ÎÅ +ÓÏÂÒÁÌÉ ÐÒÏÇÒÁÍÍÙ. + +þÔÏ ËÁÓÁÅÔÓÑ Windows: ÐÏÄÄÅÒÖÉ×ÁÀÔÓÑ ÔÏÌØËÏ ×ÅÒÓÉÉ Windows 2000 É +ÍÌÁÄÛÅ. íÙ ÐÒÅËÒÁÔÉÌÉ ÐÏÄÄÅÒÖÉ×ÁÔØ Windows 9\textit{x}, ME É NT. üÔÏ +ÐÏÚ×ÏÌÉÌÏ ÚÎÁÞÉÔÅÌØÎÏ ÓÏËÒÁÔÉÔØ ÚÁÔÒÁÔÙ ÔÒÕÄÁ ÎÁ ÜÔÕ ÐÌÁÔÆÏÒÍÕ. íÙ ÎÅ +ÓÏÂÒÁÌÉ 64-ÂÉÔÏ×ÙÅ ÐÒÏÇÒÁÍÍÙ ÄÌÑ Windows, ÎÏ 32-ÂÉÔÏ×ÙÅ ×ÁÒÉÁÎÔÙ +ÄÏÌÖÎÙ ÒÁÂÏÔÁÔØ ÎÁ 64-ÂÉÔÏ×ÙÈ ÓÉÓÔÅÍ. + +áÌØÔÅÒÎÁÔÉ×ÎÙÅ ×ÁÒÉÁÎÔÙ ÄÌÑ Windows É \MacOSX{} ÏÐÉÓÁÎÙ × +ÒÁÚÄÅÌÅ~\ref{sec:tl-coll-dists}. + +\subsection{ïÓÎÏ×Ù ÕÓÔÁÎÏ×ËÉ \protect\TL{}} +\label{sec:basic} + +\TL{} ÍÏÖÎÏ ÕÓÔÁÎÏ×ÉÔØ Ó \DVD{} ÉÌÉ Ó éÎÔÅÒÎÅÔÁ. ðÒÏÇÒÁÍÍÁ ÄÌÑ +ÕÓÔÁÎÏ×ËÉ Ó ÓÅÔÉ ÓÁÍÁ ÐÏ ÓÅÂÅ ÍÁÌÁ "--- ÏÎÁ ÓËÁÞÉ×ÁÅÔ ×ÓÅ ÎÕÖÎÏÅ Ó +éÎÔÅÒÎÅÔÁ. üÔÏ ÕÄÏÂÎÏ, ÅÓÌÉ ×ÁÍ ÎÕÖÎÁ ÔÏÌØËÏ ÞÁÓÔØ ÐÁËÅÔÏ× \TL{}. + +ðÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ Ó \DVD{} ÐÏÚ×ÏÌÑÅÔ ÕÓÔÁÎÏ×ÉÔØ \TL{} ÎÁ ÄÉÓË +ËÏÍÐØÀÔÅÒÁ, ÎÏ ÍÏÖÎÏ ÔÁËÖÅ ÚÁÐÕÓËÁÔØ \TL{} ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ Ó \DVD{} +(ÉÌÉ Ó ÏÂÒÁÚÁ \DVD{}, ÅÓÌÉ ×ÁÛÁ ÓÉÓÔÅÍÁ ÐÏÄÄÅÒÖÉ×ÁÅÔ ÍÏÎÔÉÒÏ×ÁÎÉÅ +ÏÂÒÁÚÁ ÄÉÓËÁ). + + +\noindent ÷Ó£ ÜÔÏ ÐÏÄÒÏÂÎÏ ÏÐÉÓÁÎÏ × ÓÌÅÄÕÀÝÉÈ ÒÁÚÄÅÌÁÈ. ÷ËÒÁÔÃÅ: +\begin{itemize*} +\item óËÒÉÐÔ ÄÌÑ ÕÓÔÁÎÏ×ËÉ ÓÉÓÔÅÍÙ ÎÁÚÙ×ÁÅÔÓÑ \texttt{install-tl}. ïÎ + ÍÏÖÅÔ ÒÁÂÏÔÁÔØ × Ä×ÕÈ ×ÁÒÉÁÎÔÁÈ: ÇÒÁÆÉÞÅÓËÏÍ (ÒÅÖÉÍ ÐÏ ÕÍÏÌÞÁÎÉÀ ÄÌÑ + Windows) ÉÌÉ × ÔÅËÓÔÏ×ÏÍ (ÒÅÖÉÍ ÐÏ ÕÍÏÌÞÁÎÉÀ ÄÌÑ ÏÓÔÁÌØÎÙÈ + ÁÒÈÉÔÅËÔÕÒ). îÕÖÎÙÊ ×ÁÒÉÁÎÔ ÍÏÖÎÏ ×ÙÂÒÁÔØ ÐÒÉ ÐÏÍÏÝÉ ÏÐÃÉÊ + \code{-gui} É \code{-no-gui}. + +\item óÒÅÄÉ ÕÓÔÁÎÏ×ÌÅÎÎÙÈ ÐÒÏÇÒÁÍÍ ÅÓÔØ <<íÅÎÅÄÖÅÒ \TL{}>>, + \prog{tlmgr}. ëÁË É ÐÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ, ÏÎ ÍÏÖÅÔ ÒÁÂÏÔÁÔØ ËÁË × + ÇÒÁÆÉÞÅÓËÏÍ, ÔÁË É × ÔÅËÓÔÏ×ÏÍ ÒÅÖÉÍÁÈ. üÔÁ ÐÒÏÇÒÁÍÍÁ ÐÏÚ×ÏÌÑÅÔ + ÕÓÔÁÎÁ×ÌÉ×ÁÔØ É ÕÄÁÌÑÔØ ÐÁËÅÔÙ, Á ÔÁËÖÅ ÎÁÓÔÒÁÉ×ÁÔØ ÓÉÓÔÅÍÕ. +\end{itemize*} + + +\subsection{çÄÅ ÍÏÖÎÏ ÐÏÌÕÞÉÔØ ÐÏÄÄÅÒÖËÕ} +\label{sec:help} + +óÏÏÂÝÅÓÔ×Ï ÐÏÌØÚÏ×ÁÔÅÌÅÊ \TeX{}Á ÁËÔÉ×ÎÏ É ÄÒÕÖÅÌÀÂÎÏ, É ÐÒÁËÔÉÞÅÓËÉ +ÎÁ ËÁÖÄÙÊ ÓÅÒØ£ÚÎÙÊ ×ÏÐÒÏÓ ÎÁÊÄ£ÔÓÑ ÏÔ×ÅÔ. ïÄÎÁËÏ ÜÔÁ ÐÏÄÄÅÒÖËÁ +ÎÅÆÏÒÍÁÌØÎÁ, ×ÙÐÏÌÎÑÅÔÓÑ ÄÏÂÒÏ×ÏÌØÃÁÍÉ, É ÐÏÜÔÏÍÕ ÏÞÅÎØ ×ÁÖÎÏ, ÞÔÏÂÙ +×Ù ÓÁÍÉ ÐÏÐÒÏÂÏ×ÁÌÉ ÎÁÊÔÉ ÏÔ×ÅÔ ÐÅÒÅÄ ÔÅÍ, ËÁË ÚÁÄÁ×ÁÔØ ×ÏÐÒÏÓ. (åÓÌÉ +×Ù ÐÒÅÄÐÏÞÉÔÁÅÔÅ ËÏÍÍÅÒÞÅÓËÕÀ ÐÏÄÄÅÒÖËÕ, ×ÏÚÍÏÖÎÏ ×ÁÍ ÓÔ\'ÏÉÔ ×ÍÅÓÔÏ +\TL{} ËÕÐÉÔØ ÏÄÎÕ ÉÚ ËÏÍÍÅÒÞÅÓËÉÈ ×ÅÒÓÉÊ \TeX{}Á, ÓÍ. ÓÐÉÓÏË ÐÏ +ÁÄÒÅÓÕ \url{http://tug.org/interest.html#vendors}). + +÷ÏÔ ÓÐÉÓÏË ÉÓÔÏÞÎÉËÏ× ÐÏÄÄÅÒÖËÉ, ÐÒÉÂÌÉÚÉÔÅÌØÎÏ × ÔÏÍ ÐÏÒÑÄËÅ, × +ËÏÔÏÒÏÍ ÍÙ ÒÅËÏÍÅÎÄÕÅÍ Ë ÎÉÍ ÏÂÒÁÝÁÔØÓÑ: + +\begin{description} + +\item[óÔÒÁÎÉÃÁ ÄÌÑ ÎÏ×ÉÞËÏ×:] åÓÌÉ ×Ù "--- ÎÏ×ÉÞÏË, ÔÏ ÓÔÒÁÎÉÃÁ + \url{http://tug.org/begin.html} ÍÏÖÅÔ ÐÏÓÌÕÖÉÔØ ÄÌÑ ÎÁÞÁÌÁ. + +\item [\TeX{} \acro{FAQ}:] \TeX{} \acro{FAQ} (þÁ÷Ï, ÞÁÓÔÏ ÚÁÄÁ×ÁÅÍÙÅ + ×ÏÐÒÏÓÙ) "--- ÏÇÒÏÍÎÁÑ ËÏÌÌÅËÃÉÑ ÏÔ×ÅÔÏ× ÎÁ ×ÓÅ×ÏÚÍÏÖÎÙÅ ×ÏÐÒÏÓÙ, ÏÔ + ÓÁÍÙÈ ÐÒÏÓÔÙÈ ÄÏ ÓÁÍÙÈ ÓÌÏÖÎÙÈ. áÎÇÌÉÊÓËÁÑ ×ÅÒÓÉÑ þÁ÷Ï ÎÁÈÏÄÉÔÓÑ ÎÁ + \TL{} × ÒÁÚÄÅÌÅ \OnCD{texmf-doc/doc/english/FAQ-en/html/index.html} + É ÄÏÓÔÕÐÎÁ × éÎÔÅÒÎÅÔÅ ÐÏ ÁÄÒÅÓÕ \url{http://www.tex.ac.uk/faq}. + ðÏÖÁÌÕÊÓÔÁ, ÎÁÞÉÎÁÊÔÅ ÐÏÉÓË ÏÔ×ÅÔÁ ÎÁ ×ÁÛÉ ×ÏÐÒÏÓÙ ÏÔÓÀÄÁ. + +\item [\TeX{} Catalogue:] åÓÌÉ ×Ù ÉÝÅÔÅ ËÁËÏÊ-ÌÉÂÏ ÐÁËÅÔ, ÛÒÉÆÔ, + ÐÒÏÇÒÁÍÍÕ É Ô.Ð., ÔÏ ×ÁÍ ÓÔÏÉÔ ÚÁÇÌÑÎÕÔØ × \TeX{} Catalogue. üÔÏ + ÏÇÒÏÍÎÙÊ ËÁÔÁÌÏÇ ×ÓÅÇÏ, ÞÔÏ ÏÔÎÏÓÉÔÓÑ Ë \TeX{}Õ. óÍ. + \url{http://www.ctan.org/help/Catalogue}. + +\item [\TeX{} ×Ï ×ÓÅÍÉÒÎÏÊ ÐÁÕÔÉÎÅ:] ÷ÏÔ ÓÔÒÁÎÉÞËÁ, ÎÁ ËÏÔÏÒÏÊ ÍÎÏÇÏ + ÓÓÙÌÏË ÐÏ \TeX{}Õ, ×ËÌÀÞÁÑ ÍÎÏÇÏÞÉÓÌÅÎÎÙÅ ËÎÉÇÉ, ÒÕËÏ×ÏÄÓÔ×Á É + ÓÔÁÔØÉ: \url{http://tug.org/interest.html}. + +\item [áÒÈÉ×Ù ÓÐÉÓËÏ× ÒÁÓÓÙÌËÉ É ÇÒÕÐÐ:] ä×Á ÏÓÎÏ×ÎÙÈ ÆÏÒÕÍÁ + ÔÅÈÎÉÞÅÓËÏÊ ÐÏÄÄÅÒÖËÉ "--- ÇÒÕÐÐÁ \url{news:comp.text.tex} É ÓÐÉÓÏË + ÒÁÓÓÙÌËÉ \email{texhax@tug.org}. ÷ ÉÈ ÁÒÈÉ×ÁÈ ÔÙÓÑÞÉ ×ÏÐÒÏÓÏ× É + ÏÔ×ÅÔÏ× ÎÁ ×ÓÅ ÓÌÕÞÁÉ ÖÉÚÎÉ. óÍ. + \url{http://groups.google.com/groups?group=comp.text.tex} É + \url{http://tug.org/mail-archives/texhax}. ðÏÉÓË, ÎÁÐÒÉÍÅÒ, × çÕÇÌÅ + (\url{http://google.com}) ÔÏÖÅ ÞÁÓÔÏ ÐÏÍÏÇÁÅÔ ÎÁÊÔÉ ÏÔ×ÅÔ. + +\item [÷ÏÐÒÏÓÙ ÎÁ ÆÏÒÕÍÁÈ] åÓÌÉ ×Ù ÎÅ ÍÏÖÅÔÅ ÎÁÊÔÉ ÏÔ×ÅÔÁ ÎÁ ×ÁÛ + ×ÏÐÒÏÓ, ×Ù ÍÏÖÅÔÅ ÌÉÂÏ ÏÐÕÂÌÉËÏ×ÁÔØ ×ÏÐÒÏÓ × \dirname{comp.text.tex} + ÐÒÉ ÐÏÍÏÝÉ Google ÉÌÉ ×ÁÛÅÊ ÌÀÂÉÍÏÊ ÎÏ×ÏÓÔÎÏÊ ÐÒÏÇÒÁÍÍÙ, ÌÉÂÏ + ÐÏÓÌÁÔØ ÐÉÓØÍÏ ÎÁ ÌÉÓÔ ÒÁÓÓÙÌËÉ \email{texhax@tug.org}. îÏ ÐÅÒÅÄ + ÜÔÉÍ \emph{ÐÏÖÁÌÕÊÓÔÁ} ÐÒÏÞÔÉÔÅ × þÁ÷Ï ÓÏ×ÅÔ Ï ÔÏÍ, ËÁË ÐÒÁ×ÉÌØÎÏ + ÚÁÄÁ×ÁÔØ ×ÏÐÒÏÓÙ ÎÁ ÜÔÉÈ ÆÏÒÕÍÁÈ: + \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}. + +\item [ðÏÄÄÅÒÖËÁ \TL{}] åÓÌÉ ×Ù ÈÏÔÉÔÅ ÓÏÏÂÝÉÔØ Ï ÂÁÇÅ ÉÌÉ + ×ÙÓËÁÚÁÔØ ÎÁÍ Ó×ÏÉ ÐÒÅÄÌÏÖÅÎÉÑ É ÚÁÍÅÞÁÎÉÑ Ï ÄÉÓÔÒÉÂÕÔÉ×Å \TL{}, + ÅÇÏ ÕÓÔÁÎÏ×ËÅ ÉÌÉ ÄÏËÕÍÅÎÔÁÃÉÉ, ÐÉÛÉÔÅ ÎÁ ÌÉÓÔ ÒÁÓÓÙÌËÉ + \email{tex-live@tug.org}. ïÄÎÁËÏ ÅÓÌÉ ×ÁÛ ×ÏÐÒÏÓ ËÁÓÁÅÔÓÑ + ËÏÎËÒÅÔÎÏÊ ÐÒÏÇÒÁÍÍÙ, ×ÈÏÄÑÝÅÊ × \TL{}, ×ÁÍ ÌÕÞÛÅ ÚÁÄÁ×ÁÔØ + ×ÏÐÒÏÓ٠ţ Á×ÔÏÒÕ ÉÌÉ ÐÏÓÙÌÁÔØ ÉÈ ÎÁ ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÊ ÓÐÉÓÏË + ÒÁÓÓÙÌËÉ. þÁÓÔÏ ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÊ ÁÄÒÅÓ ÍÏÖÎÏ ÐÏÌÕÞÉÔØ ÐÒÉ ÐÏÍÏÝÉ + ÏÐÃÉÉ \code{-{}-help} ÎÕÖÎÏÊ ÐÒÏÇÒÁÍÍÙ. + +\item[òÕÓÓËÏÑÚÙÞÎÙÅ ÒÅÓÕÒÓÙ] \emph{(ÄÏÂÁ×ÌÅÎÏ ÐÅÒÅ×ÏÄÞÉËÏÍ)} + üÈÏËÏÎÆÅÒÅÎÃÉÑ \dirname{ru.tex} ÄÏÓÔÕÐÎÁ ËÁË × ÓÅÔÉ æéäï, ÔÁË É × + éÎÔÅÒÎÅÔÅ (ËÁË \url{news:fido7.ru.tex}). òÕÓÓËÉÅ ÇÒÕÐÐÙ æéäï ÍÏÖÎÏ + ÎÁÊÔÉ ÎÁ ÍÎÏÇÉÈ ÓÅÒ×ÅÒÁÈ, ÎÁÐÒÉÍÅÒ \code{demos.ddt.su}. ÷ FAQ + ÜÔÏÊ ÇÒÕÐÐÙ (Á×ÔÏÒ "--- íÉÈÁÉÌ ëÏÌÏÄÉÎ) ÐÒÉ×ÏÄÉÔÓÑ ÍÎÏÇÏ ÓÓÙÌÏË ÎÁ + ÒÕÓÓËÏÑÚÙÞÎÙÅ ÒÅÓÕÒÓÙ. + +\end{description} + +ó ÄÒÕÇÏÊ ÓÔÏÒÏÎÙ, ×Ù ÓÁÍÉ ÔÏÖÅ ÍÏÖÅÔÅ ÐÏÍÏÞØ ÔÅÍ, Õ ËÏÇÏ ÅÓÔØ ×ÏÐÒÏÓÙ. +é \dirname{comp.text.tex}, É \code{texhax}, É \dirname{fido7.ru.tex} +ÏÔËÒÙÔÙ ÄÌÑ ×ÓÅÈ, ÐÏÜÔÏÍÕ ×Ù ÔÏÖÅ ÍÏÖÅÔÅ ÐÒÉÓÏÅÄÉÎÉÔØÓÑ, ÞÉÔÁÔØ É +ÐÏÍÏÇÁÔØ ÄÒÕÇÉÍ. + + +% don't use \TL so the \uppercase in the headline works. Also so +% tex4ht ends up with the right TeX. Likewise the \protect's. + +\section{óÔÒÕËÔÕÒÁ \protect\TeX\protect\ Live} +\label{sec:overview-tl} + +üÔÏÔ ÒÁÚÄÅÌ ÏÐÉÓÙ×ÁÅÔ ÓÔÒÕËÔÕÒÕ É ÓÏÄÅÒÖÁÎÉÅ \TK{} É ÅÇÏ ÓÏÓÔÁ×ÎÏÊ +ÞÁÓÔÉ \TL{}. + + +\subsection{\protect\TeX\protect\ Collection: \TL, pro\TeX{}t, Mac\TeX} +\label{sec:tl-coll-dists} + +\DVD{} \TK{} ÓÏÄÅÒÖÉÔ ÓÌÅÄÕÀÝÉÅ ÐÁËÅÔÙ: + +\begin{description} + +\item [\TL:] ÐÏÌÎÁÑ ÓÉÓÔÅÍÁ, ËÏÔÏÒÏÊ ÍÏÖÎÏ ÐÏÌØÚÏ×ÁÔØÓÑ + ÌÉÂÏ ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ Ó \DVD{}, ÌÉÂÏ ÕÓÔÁÎÏ×É× ÎÁ ÄÉÓË ËÏÍÐØÀÔÅÒÁ. + +\item [Mac\TeX:] ×ÁÒÉÁÎÔ ÄÌÑ \MacOSX{}. üÔÏÔ ÐÁËÅÔ ÄÏÂÁ×ÌÑÅÔ Ë \TL{} + ÐÒÏÇÒÁÍÍÕ ÕÓÔÁÎÏ×ËÉ ÄÌÑ \MacOSX{} É ÄÒÕÇÉÅ ÐÒÏÇÒÁÍÍÙ ÄÌÑ íÁËÉÎÔÏÛÅÊ. + óÔÒÁÎÉÃÁ ÐÒÏÅËÔÁ "--- \url{http://www.tug.org/mactex/}. + + +\item[pro\TeX{}t:] ÕÌÕÞÛÅÎÎÙÊ ×ÁÒÉÁÎÔ ÄÉÓÔÒÉÂÕÔÉ×Á \MIKTEX\ ÄÌÑ Windows. + \ProTeXt\ ×ËÌÀÞÁÅÔ × ÓÅÂÑ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ÐÒÏÇÒÁÍÍÙ É ÕÐÒÏÝ£ÎÎÕÀ + ÕÓÔÁÎÏ×ËÕ. ïÎ ÎÅ ÚÁ×ÉÓÉÔ ÏÔ \TL{} É ×ËÌÀÞÁÅÔ ÓÏÂÓÔ×ÅÎÎÙÅ ÉÎÓÔÒÕËÃÉÉ + ÐÏ ÕÓÔÁÎÏ×ËÅ. óÔÒÁÎÉÃÁ \ProTeXt{} "--- + \url{http://tug.org/protext}. + +\item [CTAN:] úÅÒËÁÌÏ ÁÒÈÉ×Á \CTAN. + +\item[\texttt{texmf-extra}:] ÄÉÒÅËÔÏÒÉÑ Ó ÒÁÚÎÏÏÂÒÁÚÎÙÍÉ + ÄÏÐÏÌÎÉÔÅÌØÎÙÍÉ ÐÁËÅÔÁÍÉ. + + +\end{description} + +ìÉÃÅÎÚÉÉ ÎÁ ÉÓÐÏÌØÚÏ×ÁÎÉÅ \CTAN{}, \pkgname{protext} É +\texttt{texmf-extra} ÏÔÌÉÞÁÀÔÓÑ ÏÔ ÌÉÃÅÎÚÉÉ \TL{}, ÐÏÜÔÏÍÕ ÂÕÄØÔÅ +×ÎÉÍÁÔÅÌØÎÙ ÐÒÉ ÒÁÓÐÒÏÓÔÒÁÎÅÎÉÉ ÉÌÉ ÍÏÄÉÆÉËÁÃÉÉ ÐÒÏÇÒÁÍÍ, ×ÈÏÄÑÝÉÈ × +ÜÔÉ ÄÉÓÔÒÉÂÕÔÉ×Ù. + + +\subsection{ëÏÒÎÅ×ÙÅ ÄÉÒÅËÔÏÒÉÉ} +\label{sec:tld} + +÷ÏÔ ËÒÁÔËÏÅ ÏÐÉÓÁÎÉÅ ËÏÒÎÅ×ÙÈ ÄÉÒÅËÔÏÒÉÊ × ÄÉÓÔÒÉÂÕÔÉ×Å \TL{}. îÁ + \DVD \TK{} ×ÓÑ ÉÅÒÁÒÈÉÑ \TL{} ÐÏÍÅÝÅÎÁ × ÐÏÄÄÉÒÅËÔÏÒÉÀ +\dirname{texlive}, Á ÎÅ × ËÏÒÅÎØ ÄÉÓËÁ. + +\begin{ttdescription} +\item[bin:] ðÒÏÇÒÁÍÍÙ ÓÉÓÔÅÍÙ \TeX{}, ÓÇÒÕÐÐÉÒÏ×ÁÎÎÙÅ ÐÏ ÐÌÁÔÆÏÒÍÁÍ. +% +\item[readme.html:] óÔÒÁÎÉÞËÉ WWW Ó ËÒÁÔËÉÍ ÒÕËÏ×ÏÄÓÔ×ÏÍ ÄÌÑ + ÐÏÌØÚÏ×ÁÔÅÌÑ É ÒÁÚÌÉÞÎÙÍÉ ÓÓÙÌËÁÍÉ, ÎÁ ÒÁÚÎÙÈ ÑÚÙËÁÈ. +% +\item[source:] éÓÈÏÄÎÙÊ ËÏÄ ×ÓÅÈ ÐÒÏÇÒÁÍÍ, ×ËÌÀÞÁÑ ÄÉÓÔÒÉÂÕÔÉ×Ù \Webc{} + \TeX{} É \MF{}. +% +\item[support:] òÁÚÎÙÅ ×ÓÐÏÍÏÇÁÔÅÌØÎÙÅ ÐÁËÅÔÙ É ÐÒÏÇÒÁÍÍÙ. ïÎÉ + \emph{ÎÅ} ÕÓÔÁÎÁ×ÌÉ×ÁÀÔÓÑ ÐÏ ÕÍÏÌÞÁÎÉÀ. óÀÄÁ ÏÔÎÏÓÑÔÓÑ + ÒÁÚÎÏÏÂÒÁÚÎÙÅ ÒÅÄÁËÔÏÒÙ É ÏÂÏÌÏÞËÉ ÄÌÑ \TeX{}Á. +% +\item[texmf:] óÍ. \dirname{TEXMFMAIN} ÎÉÖÅ. +% +\item[texmf-dist:] óÍ. \dirname{TEXMFDIST} ÎÉÖÅ. +% +\item[texmf-doc:] äÅÒÅ×Ï ÓÁÍÏÓÔÏÑÔÅÌØÎÏÊ ÄÏËÕÍÅÎÔÁÃÉÉ, ÓÇÒÕÐÐÉÒÏ×ÁÎÎÏÊ + ÐÏ ÑÚÙËÁÍ. +% +\item[tlpkg:] óËÒÉÐÔÙ, ÐÒÏÇÒÁÍÍÙ É ÄÒÕÇÉÅ ÆÁÊÌÙ ÄÌÑ ÐÏÄÄÅÒÖËÉ ÓÉÓÔÅÍÙ. + üÔÏ ÄÅÒÅ×Ï ÔÁËÖÅ ÓÏÄÅÒÖÉÔ ÓÏÂÓÔ×ÅÎÎÙÅ ËÏÐÉÉ ÐÒÏÇÒÁÍÍ Perl É + Ghostscript, ÎÅ×ÉÄÉÍÙÅ ×ÎÅ \TL{}, Á ÔÁËÖÅ ÎÏ×ÕÀ ÏÂÏÌÏÞËÕ ÄÌÑ + ÐÒÏÓÍÏÔÒÁ ÐÏÓÔÓËÒÉÐÔÏ×ÓËÉÈ ÆÁÊÌÏ× ÐÏÄ Windows, PSView. +\end{ttdescription} + + +ëÒÏÍÅ ÜÔÉÈ ÄÉÒÅËÔÏÒÉÊ, × ËÏÒÎÅ×ÏÊ ÄÉÒÅËÔÏÒÉÉ ÎÁÈÏÄÑÔÓÑ ÓËÒÉÐÔÙ +ÕÓÔÁÎÏ×ËÉ É ÆÁÊÌÙ \filename{README} (ÎÁ ÒÁÚÎÙÈ ÑÚÙËÁÈ). + +äÉÒÅËÔÏÒÉÑ \dirname{texmf-doc} ÓÏÄÅÒÖÉÔ ÄÏËÕÍÅÎÔÁÃÉÀ, ËÏÔÏÒÁÑ ÎÅ +ÏÔÎÏÓÉÔÓÑ Ë ÏÔÄÅÌØÎÙÍ ÐÁËÅÔÁÍ ÉÌÉ ÐÒÏÇÒÁÍÍÁÍ. äÏËÕÍÅÎÔÁÃÉÑ Ë +ÐÒÏÇÒÁÍÍÁÍ (ÒÕËÏ×ÏÄÓÔ×Á, man, info) ÎÁÈÏÄÉÔÓÑ × ÄÉÒÅËÔÏÒÉÉ +\dirname{texmf/doc}. äÏËÕÍÅÎÔÁÃÉÑ ÍÁËÒÏÐÁËÅÔÏ× É ÆÏÒÍÁÔÏ× +ÎÁÈÏÄÉÔÓÑ × ÄÉÒÅËÔÏÒÉÉ \dirname{texmf-dist/doc}. äÌÑ ÐÏÉÓËÁ +ÄÏËÕÍÅÎÔÁÃÉÉ ÍÏÖÎÏ ×ÏÓÐÏÌØÚÏ×ÁÔØÓÑ ÐÒÏÇÒÁÍÍÁÍÉ \cmdname{texdoc} ÉÌÉ +\cmdname{texdoctk}. íÏÖÎÏ ÔÁËÖÅ ×ÏÓÐÏÌØÚÏ×ÁÔØÓÑ ÓÓÙÌËÁÍÉ × ÆÁÊÌÅ +\OnCD{doc.html} × ËÏÒÎÅ×ÏÊ ÄÉÒÅËÔÏÒÉÉ. + +äÏËÕÍÅÎÔÁÃÉÑ Ë ÓÁÍÏÍÕ ÄÉÓÔÒÉÂÕÔÉ×Õ \TL{} ÎÁÈÏÄÉÔÓÑ × ÄÉÒÅËÔÏÒÉÉ +\dirname{texmf-doc} É ÄÏÓÔÕÐÎÁ ÎÁ ÎÅÓËÏÌØËÉÈ ÑÚÙËÁÈ: +\begin{itemize*} +\item{áÎÇÌÉÊÓËÉÊ:} \OnCD{texmf-doc/doc/english/texlive-en} +\item{õÐÒÏÝÅÎÎÙÊ ËÉÔÁÊÓËÉÊ:} \OnCD{texmf-doc/doc/chinese/texlive-zh-cn} +\item{îÅÍÅÃËÉÊ:} \OnCD{texmf-doc/doc/german/texlive-de} +\item{ðÏÌØÓËÉÊ:} \OnCD{texmf-doc/doc/polish/texlive-pl} +\item{òÕÓÓËÉÊ:} \OnCD{texmf-doc/doc/russian/texlive-ru} +\item{æÒÁÎÃÕÚÓËÉÊ:} \OnCD{texmf-doc/doc/french/texlive-fr} +\item{þÅÛÓËÉÊ É ÓÌÏ×ÁÃËÉÊ:} \OnCD{texmf-doc/doc/czechslovak/texlive-cz} +\end{itemize*} + +\subsection{ïÐÉÓÁÎÉÅ ÄÉÒÅËÔÏÒÉÊ texmf} +\label{sec:texmftrees} + +÷ ÜÔÏÍ ÒÁÚÄÅÌÅ ÏÐÉÓÁÎÙ ×ÓÅ ÐÅÒÅÍÅÎÎÙÅ, ÚÁÄÁÀÝÉÅ ÐÏÌÏÖÅÎÉÅ ÄÅÒÅ×ØÅ× +ÄÉÒÅËÔÏÒÉÊ texmf É ÉÈ ÚÎÁÞÅÎÉÑ ÐÏ ÕÍÏÌÞÁÎÉÀ. ëÏÍÁÎÄÁ +\texttt{texconfig conf} ÐÏËÁÚÙ×ÁÅÔ ÔÅËÕÝÉÅ ÚÎÁÞÅÎÉÑ ÜÔÉÈ ÐÅÒÅÍÅÎÎÙÈ, +ÔÁË ÞÔÏ ×Ù ÍÏÖÅÔÅ ÌÅÇËÏ ÐÒÏ×ÅÒÉÔØ, ÇÄÅ ÜÔÉ ÄÉÒÅËÔÏÒÉÉ ÎÁÈÏÄÑÔÓÑ × +×ÁÛÅÊ ÓÉÓÔÅÍÅ. + +\begin{ttdescription} +\item [TEXMFMAIN] äÅÒÅ×Ï, ÇÄÅ ÎÁÈÏÄÑÔÓÑ ÏÓÎÏ×ÎÙÅ ÞÁÓÔÉ ÓÉÓÔÅÍÙ, + ÔÁËÉÅ, ËÁË ×ÓÐÏÍÏÇÁÔÅÌØÎÙÅ ÓËÒÉÐÔÙ (ÎÁÐÒÉÍÅÒ, + \verb+web2c/mktexdir+), ÄÒÕÇÉÅ ×ÓÐÏÍÏÇÁÔÅÌØÎÙÅ ÆÁÊÌÙ É ÄÏËÕÍÅÎÔÁÃÉÑ + Ë ÎÉÍ. üÔÏ ÄÅÒÅ×Ï ÎÅ ÓÏÄÅÒÖÉÔ ÆÏÒÍÁÔÏ× \TeX Á É ÐÁËÅÔÏ×. +\item [TEXMFDIST] äÅÒÅ×Ï Ó ÏÓÎÏ×ÎÙÍ ÎÁÂÏÒÏÍ ÍÁËÒÏÐÁËÅÔÏ×, ÛÒÉÆÔÏ× É + Ô.Ä. × ÐÅÒ×ÏÎÁÞÁÌØÎÏÊ ËÏÎÆÉÇÕÒÁÃÉÉ. +\item [TEXMFLOCAL] äÅÒÅ×Ï, ËÏÔÏÒÏÅ ÍÏÖÅÔ ÂÙÔØ ÉÓÐÏÌØÚÏ×ÁÎÏ + ÁÄÍÉÎÉÓÔÒÁÔÏÒÁÍÉ ÓÉÓÔÅÍÙ ÄÌÑ ÄÏÐÏÌÎÉÔÅÌØÎÙÈ ÐÁËÅÔÏ×, + ÛÒÉÆÔÏ× É Ô.Ä., ÉÌÉ ÕÓÔÁÎÏ×ËÉ ÏÂÎÏ×ÌÅÎÉÊ. +\item [TEXMFHOME] äÅÒÅ×Ï, ËÏÔÏÒÏÅ ÐÏÌØÚÏ×ÁÔÅÌÉ ÍÏÇÕÔ ÉÓÐÏÌØÚÏ×ÁÔØ ÄÌÑ + ÕÓÔÁÎÏ×ËÉ ÓÏÂÓÔ×ÅÎÎÙÈ ÐÁËÅÔÏ×, ÛÒÉÆÔÏ× É Ô.Ä., ÉÌÉ ÄÌÑ ÏÂÎÏ×Ì£ÎÎÙÈ + ×ÅÒÓÉÊ ÓÉÓÔÅÍÎÙÈ ÐÁËÅÔÏ×. üÔÁ ÐÅÒÅÍÅÎÎÁÑ Ñ×ÌÑÅÔÓÑ + Ó×ÏÅÊ ÄÌÑ ËÁÖÄÏÇÏ ÐÏÌØÚÏ×ÁÔÅÌÑ. +\item [TEXMFCONFIG] üÔÏ ÄÅÒÅ×Ï ÉÓÐÏÌØÚÕÅÔÓÑ ÕÔÉÌÉÔÁÍÉ + \verb+texconfig+, \verb+updmap+ É \verb+fmtutil+ + ÄÌÑ ÈÒÁÎÅÎÉÑ ÍÏÄÉÆÉÃÉÒÏ×ÁÎÎÙÈ ÆÁÊÌÏ× ËÏÎÆÉÇÕÒÁÃÉÉ. ðÏ ÕÍÏÌÞÁÎÉÀ + ÎÁÈÏÄÉÔÓÑ × ÄÉÒÅËÔÏÒÉÉ \envname{TEXMFHOME}. +\item [TEXMFSYSCONFIG] üÔÏ ÄÅÒÅ×Ï ÉÓÐÏÌØÚÕÅÔÓÑ ÕÔÉÌÉÔÁÍÉ + \verb+texconfig-sys+, \verb+updmap-sys+ É \verb+fmtutil-sys+ + ÄÌÑ ÈÒÁÎÅÎÉÑ ÍÏÄÉÆÉÃÉÒÏ×ÁÎÎÙÈ ÆÁÊÌÏ× + ËÏÎÆÉÇÕÒÁÃÉÉ, ÏÂÝÉÈ ÄÌÑ ×ÓÅÈ ÐÏÌØÚÏ×ÁÔÅÌÅÊ. +\item [TEXMFVAR] üÔÏ ÄÅÒÅ×Ï ÉÓÐÏÌØÚÕÅÔÓÑ ÕÔÉÌÉÔÁÍÉ \verb+texconfig+, + \verb+updmap+ É \verb+fmtutil+ ÄÌÑ ÈÒÁÎÅÎÉÑ + ÓÏÚÄÁ×ÁÅÍÙÈ Á×ÔÏÍÁÔÉÞÅÓËÉ ÆÁÊÌÏ×: ÆÏÒÍÁÔÏ×, ËÁÒÔ ÛÒÉÆÔÏ×. ðÏ + ÕÍÏÌÞÁÎÉÀ ÎÁÈÏÄÉÔÓÑ × ÄÉÒÅËÔÏÒÉÉ \envname{TEXMFHOME}. +\item [TEXMFSYSVAR] üÔÏ ÄÅÒÅ×Ï ÉÓÐÏÌØÚÕÅÔÓÑ ÕÔÉÌÉÔÁÍÉ + \verb+texconfig-sys+, \verb+updmap-sys+, \verb+fmtutil-sys+, Á ÔÁËÖÅ + \verb+tlmgr+ + ÄÌÑ ÈÒÁÎÅÎÉÑ ÓÏÚÄÁ×ÁÅÍÙÈ Á×ÔÏÍÁÔÉÞÅÓËÉ ÆÁÊÌÏ×: + ÆÏÒÍÁÔÏ×, ËÁÒÔ ÛÒÉÆÔÏ×, "--- ÏÂÝÉÈ ÄÌÑ ×ÓÅÈ ÐÏÌØÚÏ×ÁÔÅÌÅÊ. +\end{ttdescription} + +\noindent +ðÏ ÕÍÏÌÞÁÎÉÀ ÓÔÒÕËÔÕÒÁ ÄÉÒÅËÔÏÒÉÊ ×ÙÇÌÑÄÉÔ ÔÁË: +\begin{description} + \item[ËÏÒÎÅ×ÁÑ ÄÉÒÅËÔÏÒÉÑ] ÍÏÖÅÔ ÓÏÄÅÒÖÁÔØ ÎÅÓËÏÌØËÏ ×ÅÒÓÉÊ \TL{}: + \begin{ttdescription} + \item[2007] ðÒÅÄÙÄÕÝÁÑ ×ÅÒÓÉÑ. + \begin{ttdescription} + \item [...] + \end{ttdescription} + \item[2008] ôÅËÕÝÁÑ ×ÅÒÓÉÑ. + \begin{ttdescription} + \item [bin] ~ + \begin{ttdescription} + \item [i386-linux] ðÒÏÇÒÁÍÍÙ ÄÌÑ \GNU/Linux + \item [...] + \item [universal-darwin] ðÒÏÇÒÁÍÍÙ ÄÌÑ \MacOSX + \item [win32] ðÒÏÇÒÁÍÍÙ ÄÌÑ Windows + \end{ttdescription} + \item [texmf] \envname{TEXMFMAIN}. + \item [texmf-dist] \envname{TEXMFDIST} + \item [texmf-doc] \envname{TEXMFDOC} + \item [texmf-var] \envname{TEXMFSYSVAR} + \item [texmf-config] \envname{TEXMFSYSCONFIG} + \end{ttdescription} + \item [texmf-local] \envname{TEXMFLOCAL}, ÏÂÝÁÑ ÄÌÑ ×ÓÅÈ ×ÅÒÓÉÊ + \TL{}. + \end{ttdescription} + \item[ÄÏÍÁÛÎÑÑ ÄÉÒÅËÔÏÒÉÑ ÐÏÌØÚÏ×ÁÔÅÌÑ] (\texttt{\$HOME} ÉÌÉ + \texttt{\%USERPROFILE\%}) + \begin{ttdescription} + \item[.texlive2007] äÁÎÎÙÅ É ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÆÁÊÌÙ ÐÒÅÄÙÄÕÝÅÊ + ×ÅÒÓÉÉ. + \item[.texlive2008] äÁÎÎÙÅ É ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÆÁÊÌÙ ÔÅËÕÝÅÊ + ×ÅÒÓÉÉ. + \begin{ttdescription} + \item [texmf-var] \envname{TEXMFVAR} + \item [texmf-config] \envname{TEXMFCONFIG} + \end{ttdescription} + \item[texmf] \envname{TEXMFHOME} ìÉÞÎÙÅ ÍÁËÒÏÐÁËÅÔÙ. + \textit{etc.} + \end{ttdescription} +\end{description} + +\subsection{òÁÓÛÉÒÅÎÉÑ \protect\TeX{}Á} +\label{sec:tex-extensions} + +ëÎÕÔÏ×ÓËÉÊ ×ÁÒÉÁÎÔ \TeX Á ÚÁÍÏÒÏÖÅÎ "--- ÚÁ ÉÓËÌÀÞÅÎÉÅÍ ÒÅÄËÉÈ +ÉÓÐÒÁ×ÌÅÎÉÊ ÂÁÇÏ×, × ÎÅÇÏ ÎÅ ×ÎÏÓÉÔÓÑ ÎÉËÁËÉÈ ÉÚÍÅÎÅÎÉÊ. ïÎ ×ÓÅ ÅÝ£ +ÒÁÓÐÒÏÓÔÒÁÎÑÅÔÓÑ × \TL{} ËÁË \prog{tex} É ÂÕÄÅÔ ÒÁÓÐÒÏÓÔÒÁÎÑÔØÓÑ × +ÏÂÏÚÒÉÍÏÍ ÂÕÄÕÝÅÍ. ÷ ÓÏÓÔÁ× \TL{} ×ÈÏÄÉÔ ÎÅÓËÏÌØËÏ ÒÁÓÛÉÒÅÎÉÊ \TeX{}Á: + +\begin{description} + +\item [\eTeX] ÄÏÂÁ×ÌÑÅÔ ÎÁÂÏÒ ÎÏ×ÙÈ ÐÒÉÍÉÔÉ×Ï× +\label{text:etex} +(ÏÔÎÏÓÑÝÉÊÓÑ Ë ÍÁËÒÏÐÏÄÓÔÁÎÏ×ËÁÍ, ÞÔÅÎÉÀ ÓÉÍ×ÏÌÏ×, ÄÏÐÏÌÎÉÔÅÌØÎÙÍ +×ÏÚÍÏÖÎÏÓÔÑÍ ÏÔÌÁÄËÉ É ÍÎÏÇÏÍÕ ÄÒÕÇÏÍÕ) É ÒÁÓÛÉÒÅÎÉÑ \TeXXeT{} ÄÌÑ +×£ÒÓÔËÉ ÓÐÒÁ×Á ÎÁÌÅ×Ï É ÓÌÅ×Á ÎÁÐÒÁ×Ï. ÷ ÏÂÙÞÎÏÍ ÒÅÖÉÍÅ \eTeX{} ÎÁ +100\% ÓÏ×ÍÅÓÔÉÍ ÓÏ ÓÔÁÎÄÁÒÔÎÙÍ\TeX{}ÏÍ. óÍ. +\OnCD{texmf-dist/doc/etex/base/etex_man.pdf}. + +\item [pdf\TeX] ×ËÌÀÞÁÅÔ × ÓÅÂÑ ÒÁÓÛÉÒÅÎÉÑ \eTeX Á, ÄÏÂÁ×ÌÑÑ ÐÏÄÄÅÒÖËÕ + ÆÏÒÍÁÔÁ \acro{PDF}, ÐÏÍÉÍÏ ÓÔÁÎÄÁÒÔÎÏÇÏ \dvi{}. üÔÁ ÐÒÏÇÒÁÍÍÁ + ÉÓÐÏÌØÚÕÅÔÓÑ ÂÏÌØÛÉÎÓÔ×ÏÍ ÆÏÒÍÁÔÏ×, ÎÁÐÒÉÍÅÒ, \prog{etex}, + \prog{latex}, \prog{pdflatex}. óÍ. \url{http://www.pdftex.org/}. + ÷ ÒÕËÏ×ÏÄÓÔ×Å ÐÏÌØÚÏ×ÁÔÅÌÑ \OnCD{texmf/doc/pdftex/manual/} É ÐÒÉÍÅÒÅ + \OnCD{texmf/doc/pdftex/manual/samplepdf/samplepdf.tex} ÏÐÉÓÁÎÙ + ×ÏÚÍÏÖÎÏÓÔÉ ÐÒÏÇÒÁÍÍÙ. + +\item[Lua\TeX] ÐÒÅÄÎÁÚÎÁÞÅÎ ÚÁÍÅÎÉÔØ pdf\TeX{} × ÂÕÄÕÝÅÍ. + ðÒÅÄÐÏÌÁÇÁÅÔÓÑ, ÞÔÏ ÏÎ ÂÕÄÅÔ ÓÏ×ÍÅÓÔÉÍ Ó ÐÏÓÌÅÄÎÉÍ. ïÎ ÔÁËÖÅ + ÚÁÍÅÎÉÔ Aleph, ÓÍ. ÎÉÖÅ. ÷ÓÔÒÏÅÎÎÙÊ ÉÎÔÅÒÐÒÅÔÁÔÏÒ ÑÚÙËÁ Lua (ÓÍ. + \url{http://www.lua.org/}) ÐÏÚ×ÏÌÑÅÔ ÜÌÅÇÁÎÔÎÏ ÒÅÛÉÔØ ÍÎÏÇÉÅ ÓÌÏÖÎÙÅ + ÐÒÏÂÌÅÍÙ \TeX Á. ëÏÇÄÁ ÜÔÁ ÐÒÏÇÒÁÍÍÁ ÚÁÐÕÓËÁÅÔÓÑ ËÁË + \filename{texlua}, ÏÎÁ ÒÁÂÏÔÁÅÔ ËÁË ÉÎÔÅÒÐÒÅÔÁÔÏÒ Lua, É × ÜÔÏÍ + ËÁÞÅÓÔ×Å ÉÓÐÏÌØÚÕÅÔÓÑ × \TL{}. óÍ. \url{http://www.luatex.org/} É + \OnCD{texmf-dist/doc/luatex/luatexref-t.pdf}. + +\item [Xe\TeX] ÄÏÂÁ×ÌÑÅÔ ÐÏÄÄÅÒÖËÕ Unicode É ÛÒÉÆÔÏ× × ÆÏÒÍÁÔÅ + OpenType, ÓÄÅÌÁÎÎÕÀ ÞÅÒÅÚ ÓÔÁÎÄÁÒÔÎÙÅ ÂÉÂÌÉÏÔÅËÉ. óÍ. + \url{http://scripts.sil.org/xetex}. + +\item [\OMEGA\ (ïÍÅÇÁ)] ÏÓÎÏ×ÁÎÁ ÎÁ Unicode (ÓÉÓÔÅÍÁ 16-ÂÉÔÏ×ÙÈ + ÓÉÍ×ÏÌÏ×), ÞÔÏ ÐÏÚ×ÏÌÑÅÔ ÒÁÂÏÔÁÔØ ÏÄÎÏ×ÒÅÍÅÎÎÏ ÐÏÞÔÉ ÓÏ ×ÓÅÍÉ + ÐÉÓØÍÅÎÎÏÓÔÑÍÉ ÍÉÒÁ. ïÎÁ ÔÁËÖÅ ÐÏÄÄÅÒÖÉ×ÁÅÔ ÔÁË ÎÁÚÙ×ÁÅÍÙÊ <<ÐÒÏÃÅÓÓ + ÔÒÁÎÓÌÑÃÉÉ \OMEGA{}>> (\acro{OTP}s) ÄÌÑ ÓÌÏÖÎÙÈ ÐÒÅÏÂÒÁÚÏ×ÁÎÉÊ + ÐÒÏÉÚ×ÏÌØÎÏÇÏ ×ÈÏÄÎÏÇÏ ÐÏÔÏËÁ. óÍ. + \OnCD{texmf-dist/doc/omega/base/doc-1.8.tex} (ÔÅËÓÔ ÎÅÓËÏÌØËÏ ÕÓÔÁÒÅÌ). + + +\item[Aleph] ÏÂßÅÄÉÎÑÅÔ \OMEGA\ É \eTeX. óÍ. ËÒÁÔËÕÀ ÄÏËÕÍÅÎÔÁÃÉÀ × + \OnCD{texmf-dist/doc/aleph/base}. + +\end{description} + + +\subsection{äÒÕÇÉÅ ÉÎÔÅÒÅÓÎÙÅ ÐÒÏÇÒÁÍÍÙ × ÄÉÓÔÒÉÂÕÔÉ×Å \protect\TL} + +÷ÏÔ ÎÅÓËÏÌØËÏ ÄÒÕÇÉÈ ÞÁÓÔÏ ÉÓÐÏÌØÚÕÅÍÙÈ ÐÒÏÇÒÁÍÍ × ÄÉÓÔÒÉÂÕÔÉ×Å \TL{}: + +\begin{cmddescription} + +\item [bibtex] ÐÏÄÄÅÒÖËÁ ÂÉÂÌÉÏÇÒÁÆÉÊ. + +\item [makeindex] ÐÏÄÄÅÒÖËÁ ÁÌÆÁ×ÉÔÎÙÈ ÕËÁÚÁÔÅÌÅÊ. + +\item [dvips] ÐÒÅÏÂÒÁÚÏ×ÁÎÉÅ \dvi{} × \PS{}. + +\item [xdvi] ÐÒÏÇÒÁÍÍÁ ÄÌÑ ÐÒÏÓÍÏÔÒÁ \dvi{} ÄÌÑ X Window System. + +\item [dvilj] ÄÒÁÊ×ÅÒ ÄÌÑ ÌÁÚÅÒÎÙÈ ÐÒÉÎÔÅÒÏ× ÓÅÍÅÊÓÔ×Á HP LaserJet. + +\item [dv2dt, dt2dv] ÐÒÅÏÂÒÁÚÏ×ÁÎÉÅ \dvi{} × ÔÅËÓÔ É ÏÂÒÁÔÎÏ. + +\item [dviconcat, dviselect] ÐÅÒÅÓÔÁÎÏ×ËÁ ÓÔÒÁÎÉÃ × ÆÁÊÌÁÈ \dvi{}. + +\item [dvipdfmx] ÐÒÅÏÂÒÁÚÏ×ÁÎÉÅ \dvi{} × \acro{PDF}, ÁÌØÔÅÒÎÁÔÉ×Á + pdf\TeX{}Õ, ÕÐÏÍÑÎÕÔÏÍÕ ×ÙÛÅ. ðÁËÅÔÙ \pkgname{ps4pdf} É +\pkgname{pdftricks} ÐÒÅÄÌÁÇÁÀÔ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ×ÏÚÍÏÖÎÏÓÔÉ. + +\item [psselect, psnup, \ldots] ÕÔÉÌÉÔÙ ÄÌÑ ÆÏÒÍÁÔÁ \PS{}. + +\item [lacheck] ÐÒÏ×ÅÒËÁ ÓÉÎÔÁËÓÉÓÁ \LaTeX{}Á. + +\item [texexec, texmfstart] ÐÒÏÃÅÓÓÏÒ ÄÌÑ Con\TeX{}tÁ É \acro{PDF}. + +\item [tex4ht] ËÏÎ×ÅÒÔÅÒ ÉÚ \TeX{}Á × \acro{HTML}, \acro{XML} É ÍÎÏÇÉÅ + ÄÒÕÇÉÅ ÆÏÒÍÁÔÙ. + +\end{cmddescription} + +\subsection{ûÒÉÆÔÙ × \protect\TL{}} +\label{sec:tl-fonts} + +÷ \TL{} ×ËÌÀÞÅÎÏ ÍÎÏÇÏ ×ÅËÔÏÒÎÙÈ ÛÒÉÆÔÏ× ×ÙÓÏËÏÇÏ ËÁÞÅÓÔ×Á. +óÍ. \url{http://tug.org/fonts} É +\OnCD{texmf-doc/english/free-math-fonts-survey}. + +\section{õÓÔÁÎÏ×ËÁ} +\label{sec:install} + +\subsection{úÁÐÕÓË ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ} +\label{sec:inst-start} + +äÌÑ ÎÁÞÁÌÁ ×ÁÍ ÐÏÔÒÅÂÕÅÔÓÑ \DVD{} \TK{} ÉÌÉ ÐÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ \TL{} +Ó éÎÔÅÒÎÅÔÁ. îÁÊÄÉÔÅ ÓËÒÉÐÔ ÕÓÔÁÎÏ×ËÉ: \filename{install-tl} ÄÌÑ +àÎÉËÓÁ, \filename{install-tl.bat} ÄÌÑ Windows. + +\begin{description} +\item [õÓÔÁÎÏ×ËÁ Ó ÓÅÔÉ:] ÓËÁÞÁÊÔÅ ÐÒÏÇÒÁÍÍÕ ÉÚ ÁÒÈÉ×Á \CTAN, ÄÉÒÅËÔÏÒÉÑ +\dirname{systems/texlive/tlnet}; ÁÄÒÅÓ +\url{http://mirror.ctan.org/systems/texlive/tlnet} Á×ÔÏÍÁÔÉÞÅÓËÉ +ÐÒÉ×ÏÄÉÔ Ë ÂÌÉÖÁÊÛÅÍÕ ÚÅÒËÁÌÕ ÁÒÈÉ×Á. ÷Ù ÍÏÖÅÔÅ ÓËÁÞÁÔØ ÌÉÂÏ +\filename{install-tl.zip} (ÕÓÔÁÎÏ×ËÁ ÐÏÄ àÎÉËÓÏÍ É Windows), ÌÉÂÏ ÆÁÊÌ +ÓÕÝÅÓÔ×ÅÎÎÏ ÍÅÎØÛÅÇÏ ÒÁÚÍÅÒÁ +\filename{install-unx.tar.gz} (ÔÏÌØËÏ ÄÌÑ àÎÉËÓÁ). ðÏÓÌÅ ÒÁÓÐÁËÏ×ËÉ +ÆÁÊÌÙ \filename{install-tl} É +\filename{install-tl.bat} ÏËÁÖÕÔÓÑ × ÄÉÒÅËÔÏÒÉÉ \dirname{install-tl}. + +\item [\TeX{} Collection \DVD:] ðÅÒÅÊÄÉÔÅ × ÐÏÄÄÉÒÅËÔÏÒÉÀ + \dirname{texlive}. ðÏÄ Windows ÐÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ ÚÁÐÕÓËÁÅÔÓÑ + Á×ÔÏÍÁÔÉÞÅÓËÉ, ËÏÇÄÁ ×Ù ×ÓÔÁ×ÌÑÅÔÅ \DVD{} × ËÏÍÐØÀÔÅÒ. ÷Ù ÍÏÖÅÔÅ + ÐÏÌÕÞÉÔØ \DVD, ×ÓÔÕÐÉ× × ÇÒÕÐÐÕ ÐÏÌØÚÏ×ÁÔÅÌÅÊ \TeX Á (ÍÙ + ÎÁÓÔÏÑÔÅÌØÎÏ ÒÅËÏÍÅÎÄÕÅÍ ÜÔÏ ÓÄÅÌÁÔØ, + \url{http://tug.org/usergroups.html}), ÌÉÂÏ ËÕÐÉ× ÅÇÏ ÏÔÄÅÌØÎÏ + (\url{http://tug.org/store}), ÌÉÂÏ ÓÄÅÌÁ× ÅÇÏ ÓÁÍÏÓÔÏÑÔÅÌØÎÏ, ÓËÁÞÁ× + \ISO\ ÏÂÒÁÚ ÄÉÓËÁ (\url{http://tug.org/texlive/acquire.html}). + +\end{description} + + +÷ ÓÌÅÄÕÀÝÉÈ ÒÁÚÄÅÌÁÈ ÕÓÔÁÎÏ×ËÁ ÏÐÉÓÙ×ÁÅÔÓÑ ÂÏÌÅÅ ÐÏÄÒÏÂÎÏ. + +\subsubsection{àÎÉËÓ} + +\begin{figure}[tb] +\begin{boxedverbatim} +======================> TeX Live installation procedure <===================== + +=======> Note: Letters/digits in indicate menu items <======= +=======> for commands or configurable options <======= + + + Detected platform: Intel x86 with GNU/Linux + + binary systems: 1 out of 16 + + Installation scheme (scheme-full) + + Customizing installation scheme: + standard collections + language collections + 83 collections out of 84, disk space required: 1666 MB + + directories: + TEXDIR (the main TeX directory): + !! default location: /usr/local/texlive/2008 + !! is not writable, please select a different one! + TEXMFLOCAL (directory for site-wide local files): + /usr/local/texlive/texmf-local + TEXMFSYSVAR (directory for variable and automatically generated data): + /usr/local/texlive/2008/texmf-var + TEXMFSYSCONFIG (directory for local config): + /usr/local/texlive/2008/texmf-config + TEXMFHOME (directory for user-specific files): + ~/texmf + + options: + [ ] use letter size instead of A4 by default + [X] create all format files + [X] install macro/font doc tree + [X] install macro/font source tree + [ ] create symlinks in standard directories + + Install for running from DVD + +Other actions: + start installation to HD + help + quit + +Enter command: +\end{boxedverbatim} +\caption{çÌÁ×ÎÏÅ ÍÅÎÀ ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ × ÔÅËÓÔÏ×ÏÍ ÒÅÖÉÍÅ + (\GNU/Linux)}\label{fig:text-main} +\end{figure} + + +\begin{figure}[tb] +\tlpng{install-w32-main}{\linewidth} +\caption{çÌÁ×ÎÏÅ ÍÅÎÀ ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ × ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ + (Windows)}\label{fig:gui-main} +\end{figure} + +\noindent +îÉÖÅ \texttt{>} ÕËÁÚÙ×ÁÅÔ ÓÉÓÔÅÍÎÙÊ ÐÒÏÍÐÔ; ÔÏ, ÞÔÏ ××ÏÄÉÔ +ÐÏÌØÚÏ×ÁÔÅÌØ, ÐÏËÁÚÁÎÏ \Ucom{\texttt{ÖÉÒÎÙÍ ÛÒÉÆÔÏÍ}}. +ïÔËÒÙ× ÔÅÒÍÉÎÁÌØÎÏÅ ÏËÎÏ × àÎÉËÓÅ, ÚÁÐÕÓÔÉÔÅ ÐÒÏÇÒÁÍÍÕ ÕÓÔÁÎÏ×ËÉ: +\begin{alltt} +> \Ucom{cd /path/to/installer} +> \Ucom{perl install-tl} +\end{alltt} +(áÌØÔÅÒÎÁÔÉ×ÎÏ, ×Ù ÍÏÖÅÔÅ ÚÁÐÕÓÔÉÔØ \Ucom{perl + /path/to/installer/install-tl}, ÉÌÉ +\Ucom{./install-tl}, ÅÓÌÉ Õ ÜÔÏÇÏ ÓËÒÉÐÔÁ ÅÓÔØ ÐÒÁ×Á ÎÁ ×ÙÐÏÌÎÅÎÉÅ, É +Ô.Ä. íÙ ÎÅ ÂÕÄÅÍ ÕËÁÚÙ×ÁÔØ ×ÓÅ ÜÔÉ ×ÁÒÉÁÎÔÙ.) + + +äÌÑ ÕÓÔÁÎÏ×ËÉ × ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ (×ÁÍ ÐÏÔÒÅÂÕÅÔÓÑ ÍÏÄÕÌØ +\dirname{Perl/TK}) ÉÓÐÏÌØÚÕÊÔÅ +\begin{alltt} +> \Ucom{perl install-tl -gui} +\end{alltt} + +ðÏÌÎÙÊ ÓÐÉÓÏË ×ÏÚÍÏÖÎÙÈ ÏÐÃÉÊ ÄÁÅÔ ËÏÍÁÎÄÁ +\begin{alltt} +> \Ucom{perl install-tl -help} +\end{alltt} + +\textbf{ðÒÅÄÕÐÒÅÖÄÅÎÉÅ Ï ÐÒÁ×ÁÈ ÄÏÓÔÕÐÁ × àÎÉËÓÅ:} ÓÉÓÔÅÍÁ ÕÓÔÁÎÏ×ËÉ +\TL{} ÉÓÐÏÌØÚÕÅÔ ÔÅËÕÝÅÅ ÚÎÁÞÅÎÉÅ ÐÁÒÁÍÅÔÒÁ \code{umask}. ðÏÜÔÏÍÕ +ÅÓÌÉ ×Ù ÈÏÔÉÔÅ, ÞÔÏÂÙ ÐÏÌÕÞÅÎÎÏÊ ÓÉÓÔÅÍÙ ÍÏÇÌÉ ÐÏÌØÚÏ×ÁÔØÓÑ ÎÅ ÔÏÌØËÏ +×Ù, ÎÏ É ÄÒÕÇÉÅ ÐÏÌØÚÏ×ÁÔÅÌÉ, ×Ù ÄÏÌÖÎÙ ÕÓÔÁÎÏ×ÉÔØ, ÎÁÐÒÉÍÅÒ, \code{ + umask 022}. âÏÌÅÅ ÐÏÄÒÏÂÎÏ \code{umask} ÏÂÓÕÖÄÁÅÔÓÑ × ÄÏËÕÍÅÎÔÁÃÉÉ +Ë ×ÁÛÅÊ ÓÉÓÔÅÍÅ. + +\subsubsection{Mac\,OS\,X} + +ëÁË ÏÔÍÅÞÁÅÔÓÑ × ÒÁÚÄÅÌÅ~\ref{sec:tl-coll-dists}, ÄÌÑ \MacOSX{} +ÓÕÝÅÓÔ×ÕÅÔ ÓÐÅÃÉÁÌØÎÙÊ ÄÉÓÔÒÉÂÕÔÉ×, Mac\TeX{} +(\url{http://tug.org/mactex}). íÙ ÒÅËÏÍÅÎÄÕÅÍ ÐÏÌØÚÏ×ÁÔØÓÑ ÅÇÏ +ÓÉÓÔÅÍÏÊ ÕÓÔÁÎÏ×ËÉ, Á ÎÅ ÏÂÝÉÍ ÓËÒÉÐÔÏÍ \TL{}, ÐÏÓËÏÌØËÕ Õ ÎÅÇÏ ÅÓÔØ +ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ×ÏÚÍÏÖÎÏÓÔÉ, ÓÐÅÃÉÆÉÞÅÓËÉÅ ÄÌÑ íÁËÏ×, ÎÁÐÒÉÍÅÒ, ÕÄÏÂÎÏÅ +ÐÅÒÅËÌÀÞÅÎÉÅ ÍÅÖÄÕ ÒÁÚÌÉÞÎÙÍÉ ÄÉÓÔÒÉÂÕÔÉ×ÁÍÉ \TeX Á ÄÌÑ \MacOSX{} +(Mac\TeX, gw\TeX, Fink, MacPorts, \ldots). + +Mac\TeX{} ÏÓÎÏ×ÁÎ ÎÁ \TL{}, É ÏÓÎÏ×ÎÙÅ ÄÅÒÅ×ØÑ ÄÉÒÅËÔÏÒÉÊ Õ ÎÉÈ +ÓÏ×ÐÁÄÁÀÔ. ïÎ ÄÏÂÁ×ÌÑÅÔ ÎÅÓËÏÌØËÏ ÐÏÄÄÉÒÅËÔÏÒÉÊ Ó ÐÒÏÇÒÁÍÍÁÍÉ É +ÄÏËÕÍÅÎÔÁÃÉÅÊ, ÏÔÎÏÓÑÝÉÍÉÓÑ ÔÏÌØËÏ Ë íÁËÁÍ. + +\subsubsection{Windows} + +åÓÌÉ ×Ù ÕÓÔÁÎÁ×ÌÉ×ÁÅÔÅ ÓÉÓÔÅÍÕ Ó ÓÅÔÉ, ÉÌÉ ÅÓÌÉ ÐÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ Ó +\DVD{} ÎÅ ÓÔÁÒÔÏ×ÁÌÁ Á×ÔÏÍÁÔÉÞÅÓËÉ, Ä×ÁÖÄÙ ÝÅÌËÎÉÔÅ ÐÏ +\filename{install-tl.bat}. + +íÏÖÎÏ ÔÁËÖÅ ÚÁÐÕÓÔÉÔØ ÐÒÏÇÒÁÍÍÕ ÉÚ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ. îÉÖÅ \texttt{>} +ÏÚÎÁÞÁÅÔ ÓÉÓÔÅÍÎÙÊ ÐÒÏÍÐÔ; ÔÏ, ÞÔÏ ××ÏÄÉÔ ÐÏÌØÚÏ×ÁÔÅÌØ, ÕËÁÚÁÎÏ +\Ucom{\texttt{ÖÉÒÎÙÍ ÛÒÉÆÔÏÍ}}. åÓÌÉ ×Ù ÎÁÈÏÄÉÔÅÓØ × ÄÉÒÅËÔÏÒÉÉ +ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ, ÎÁÐÅÞÁÔÁÊÔÅ: +\begin{alltt} +> \Ucom{install-tl} +\end{alltt} + +ðÒÏÇÒÁÍÍÕ ÍÏÖÎÏ ×ÙÚ×ÁÔØ É ÉÚ ÄÒÕÇÏÊ ÄÉÒÅËÔÏÒÉÉ, ÎÁÐÒÉÍÅÒ, +\begin{alltt} +> \Ucom{D:\bs{}texlive\bs{}install-tl} +\end{alltt} +(ÐÒÅÄÐÏÌÁÇÁÅÔÓÑ, ÞÔÏ × \dirname{D:} ÎÁÈÏÄÉÔÓÑ \DVD{} \TK{}). + +äÌÑ ÕÓÔÁÎÏ×ËÉ × ÔÅËÓÔÏ×ÏÍ ÒÅÖÉÍÅ ÉÓÐÏÌØÚÕÊÔÅ +\begin{alltt} +> \Ucom{install-tl -no-gui} +\end{alltt} + + +÷ÓÅ ÏÐÃÉÉ ÐÒÏÇÒÁÍÍÙ ÍÏÖÎÏ ÐÏÌÕÞÉÔØ ÐÒÉ ÐÏÍÏÝÉ ËÏÍÁÎÄÙ +\begin{alltt} +> \Ucom{install-tl -help} +\end{alltt} + +\subsubsection{õÓÔÁÎÏ×ËÁ × ÔÅËÓÔÏ×ÏÍ ÒÅÖÉÍÅ} + +îÁ ÒÉÓÕÎËÅ~\ref{fig:text-main} ÐÏËÁÚÁÎÏ ÏÓÎÏ×ÎÏÅ ÍÅÎÀ ÐÒÏÇÒÁÍÍÙ +ÕÓÔÁÎÏ×ËÉ × ÔÅËÓÔÏ×ÏÍ ÒÅÖÉÍÅ ÄÌÑ àÎÉËÓÁ. + +éÎÔÅÒÆÅÊÓ ÐÒÏÇÒÁÍÍÙ ÄÏ×ÏÌØÎÏ ÐÒÉÍÉÔÉ×ÅÎ: ÐÏÄÄÅÒÖËÉ ËÕÒÓÏÒÁ × ÎÅÍ +ÎÅÔ. îÁÐÒÉÍÅÒ, ÎÅÌØÚÑ ÐÅÒÅÄ×ÉÇÁÔØÓÑ ÐÏ ÐÏÌÑÍ ÐÒÉ ÐÏÍÏÝÉ ËÌÁ×ÉÛÉ +<>. ÷Ù ÐÒÏÓÔÏ ÐÅÞÁÔÁÅÔÅ ÞÔÏ-ÔÏ (ÒÅÇÉÓÔÒ ÕÞÉÔÙ×ÁÅÔÓÑ!) É +ÎÁÖÉÍÁÅÔÅ ËÌÁ×ÉÛÕ <>, ÐÏÓÌÅ ÞÅÇÏ ÐÅÒÅÒÉÓÏ×Ù×ÁÅÔÓÑ ×ÅÓØ ÜËÒÁÎ. + +üÔÏÔ ÉÎÔÅÒÆÅÊÓ ÐÒÉÍÉÔÉ×ÅÎ ÐÏ ÓÌÅÄÕÀÝÅÊ ÐÒÉÞÉÎÅ: ÏÎ ÄÏÌÖÅÎ ÒÁÂÏÔÁÔØ ÎÁ +ËÁË ÍÏÖÎÏ ÂÏÌØÛÅÍ ËÏÌÉÞÅÓÔ×Å ÐÌÁÔÆÏÒÍ, ×ËÌÀÞÁÑ ÔÁËÉÅ, ÇÄÅ ÅÓÔØ ÔÏÌØËÏ +ÕÓÅÞÅÎÎÙÊ ×ÁÒÉÁÎÔ PerlÁ (ÄÌÑ Windows ÔÁËÏÊ ×ÁÒÉÁÎÔ +PerlÁ ×ËÌÀÞÅÎ × ÄÉÓÔÒÉÂÕÔÉ×). + +\subsubsection{õÓÔÁÎÏ×ËÁ × ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ} + +îÁ ÒÉÓÕÎËÅ~\ref{fig:gui-main} ÉÚÏÂÒÁÖÅÎÏ ÍÅÎÀ ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ × +ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ. ïÓÎÏ×ÎÙÅ ÒÁÚÌÉÞÉÑ Ó ÒÉÓÕÎËÏÍ~\ref{fig:text-main} +Ó×ÑÚÁÎÙ Ó ÔÅÍ, ÞÔÏ ÜÔÁ ÐÒÏÇÒÁÍÍÁ ÒÁÂÏÔÁÅÔ ÐÏÄ Windows, Á ÐÒÅÄÙÄÕÝÁÑ +"--- ÐÏÄ GNU/Linux. + +\subsection{òÁÂÏÔÁ ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ} +\label{sec:runinstall} + +íÅÎÀ ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ ÄÏÌÖÎÏ ÂÙÔØ ÐÏÎÑÔÎÏ ÂÅÚ ÏÂßÑÓÎÅÎÉÊ. íÙ ×ÓÅ +ÖÅ ÐÒÉ×ÅÄÅÍ ÎÅÓËÏÌØËÏ ËÒÁÔËÉÈ ÚÁÍÅÞÁÎÉÊ. + +\subsubsection{íÅÎÀ ×ÙÂÏÒÁ ÐÌÁÔÆÏÒÍÙ (ÔÏÌØËÏ ÄÌÑ àÎÉËÓÁ)} +\label{sec:binary} + +\begin{figure}[tbh] +\begin{boxedverbatim} +Available sets of binaries: +==================================================================== + + a [ ] alpha-linux DEC Alpha with GNU/Linux + b [ ] amd64-freebsd x86_64 with FreeBSD + c [ ] hppa-hpux HP-UX + d [ ] i386-freebsd Intel x86 with FreeBSD + e [X] i386-linux Intel x86 with GNU/Linux + f [ ] i386-openbsd Intel x86 with OpenBSD + g [ ] i386-solaris Intel x86 with Sun Solaris + h [ ] mips-irix SGI IRIX + i [ ] powerpc-aix PowerPC with AIX + j [ ] powerpc-linux PowerPC with GNU/Linux + k [ ] sparc-linux Sparc with GNU/Linux + l [ ] sparc-solaris Sparc with Solaris + m [ ] universal-darwin universal binaries for MacOSX/Darwin + o [ ] win32 Windows + p [ ] x86_64-linux x86_64 with GNU/Linux +\end{boxedverbatim} +\caption{íÅÎÀ ×ÙÂÏÒÁ ÐÌÁÔÆÏÒÍÙ}\label{fig:bin-text} +\end{figure} + +îÁ ÒÉÓÕÎËÅ~\ref{fig:bin-text} ÉÚÏÂÒÁÖÅÎÏ ÍÅÎÀ ×ÙÂÏÒÁ ÐÌÁÔÆÏÒÍÙ. ðÏ +ÕÍÏÌÞÁÎÉÀ ÕÓÔÁÎÁ×ÌÉ×ÁÀÔÓÑ ÔÏÌØËÏ ÐÒÏÇÒÁÍÍÙ ÄÌÑ ×ÁÛÅÊ ÔÅËÕÝÅÊ +ÁÒÈÉÔÅËÔÕÒÙ. ÷ ÜÔÏÍ ÍÅÎÀ ×Ù ÍÏÖÅÔÅ ×ÙÂÒÁÔØ ÔÁËÖÅ ÕÓÔÁÎÏ×ËÕ ÐÒÏÇÒÁÍÍ +ÄÌÑ ÄÒÕÇÉÈ ÐÌÁÔÆÏÒÍ. üÔÏ ÍÏÖÅÔ ÂÙÔØ ÐÏÌÅÚÎÏ, ÅÓÌÉ ×Ù ÉÓÐÏÌØÚÕÅÔÅ ÏÄÎÏ +É ÔÏ ÖÅ ÄÅÒÅ×Ï \TeX{}Á ÄÌÑ ÒÁÚÎÙÈ ÍÁÛÉÎ É ÒÁÚÄÁ£ÔÅ ÅÇÏ ÐÏ ÌÏËÁÌØÎÏÊ +ÓÅÔÉ, ÌÉÂÏ ÅÓÌÉ ÎÁ ×ÁÛÅÊ ÍÁÛÉÎÅ ÕÓÔÁÎÏ×ÌÅÎÏ ÎÅÓËÏÌØËÏ ÏÐÅÒÁÃÉÏÎÎÙÈ +ÓÉÓÔÅÍ. + +\subsubsection{÷ÙÂÏÒ ÏÓÎÏ×ÎÙÈ ËÏÍÐÏÎÅÎÔÏ×} +\label{sec:components} + +\begin{figure}[tbh] +\begin{boxedverbatim} +Select a scheme: +==================================================================== + + a [ ] TeX Live basic scheme + b [ ] TeX Live scheme for ConTeXt + c [X] TeX Live full scheme + d [ ] GUST TeX Live scheme + e [ ] GUTenberg TeX Live scheme + f [ ] TeX Live medium scheme + g [ ] TeX Live minimal scheme + h [ ] TeX Live for Omega users + i [ ] teTeX scheme + j [ ] XML typesetting scheme +\end{boxedverbatim} +\caption{÷ÙÂÏÒ ÏÓÎÏ×ÎÙÈ ËÏÍÐÏÎÅÎÔÏ×}\label{fig:scheme-text} +\end{figure} + +îÁ ÒÉÓÕÎËÅ~\ref{fig:scheme-text} ÐÏËÁÚÁÎÏ ÍÅÎÀ ×ÙÂÏÒÁ ÏÓÎÏ×ÎÙÈ +ËÏÍÐÏÎÅÎÔÏ× (ÓÈÅÍ) \TL{}. ÷ ÜÔÏÍ ÍÅÎÀ ×Ù ÍÏÖÅÔÅ ×ÙÂÒÁÔØ <<ÓÈÅÍÕ>>, +Ô.Å. ÎÁÂÏÒ ËÏÌÌÅËÃÉÊ ÐÁËÅÔÏ×. ðÏ ÕÍÏÌÞÁÎÉÀ ÉÓÐÏÌØÚÕÅÔÓÑ ÓÈÅÍÁ +\optname{full}, Ô.Å. ×ÓÅ ÐÁËÅÔÙ \TL{}, ÎÏ ×Ù ÍÏÖÅÔÅ ×ÙÂÒÁÔØ ÓÈÅÍÕ +\optname{basic} ÄÌÑ ÎÅÂÏÌØÛÏÊ ÓÉÓÔÅÍÙ, ÓÈÅÍÕ \optname{minimal} ÄÌÑ +ÔÅÓÔÉÒÏ×ÁÎÉÑ ÉÌÉ ÓÈÅÍÙ \optname{medium} ÉÌÉ \optname{teTeX}. åÓÔØ +ÔÁËÖÅ ÒÑÄ ÓÐÅÃÉÁÌØÎÙÈ ÓÈÅÍ, × ÔÏÍ ÞÉÓÌÅ É ÐÒÅÄÎÁÚÎÁÞÅÎÎÙÈ ÄÌÑ +ÒÁÚÌÉÞÎÙÈ ÓÔÒÁÎ. + +\begin{figure}[tbh] +\tlpng{stdcoll}{.7\linewidth} +\caption{íÅÎÀ ËÏÌÌÅËÃÉÊ (ìÉÎÕËÓ)}\label{fig:collections-gui} +\end{figure} + +÷Ù ÍÏÖÅÔÅ ÕÔÏÞÎÉÔØ ×ÁÛ ×ÙÂÏÒ ÐÒÉ ÐÏÍÏÝÉ ÍÅÎÀ <<ËÏÌÌÅËÃÉÊ>> +(ÒÉÓÕÎÏË~\ref{fig:collections-gui}, ÄÌÑ ÒÁÚÎÏÏÂÒÁÚÉÑ ÓÄÅÌÁÎÎÙÊ × +ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ). + +ëÏÌÌÅËÃÉÉ ÐÒÅÄÓÔÁ×ÌÑÀÔ ÓÏÂÏÊ ÓÌÅÄÕÀÝÉÊ ÐÏÓÌÅ ÓÈÅÍ ÕÒÏ×ÅÎØ +ÉÅÒÁÒÈÉÉ \TL{}. çÒÕÂÏ ÇÏ×ÏÒÑ, ÓÈÅÍÙ ÓÏÓÔÏÑÔ ÉÚ ËÏÌÌÅËÃÉÊ, ËÏÌÌÅËÃÉÉ +ÓÏÓÔÏÑÔ ÉÚ ÐÁËÅÔÏ×, Á ÐÁËÅÔÙ (ÎÉÖÎÉÊ ÕÒÏ×ÅÎØ ÉÅÒÁÒÈÉÉ \TL{}) ÓÏÄÅÒÖÁÔ +ÍÁËÒÏÓÙ, ÛÒÉÆÔÙ É Ô.Ä. + +åÓÌÉ ×Ù ÈÏÔÉÔÅ ÂÏÌÅÅ ÔÏÎËÏÊ ÎÁÓÔÒÏÊËÉ, ÞÅÍ ×ÏÚÍÏÖÎÁ × ÍÅÎÀ ËÏÌÌÅËÃÉÊ, +×Ù ÍÏÖÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ ÐÒÏÇÒÁÍÍÕ \prog{tlmgr} ÐÏÓÌÅ ÕÓÔÁÎÏ×ËÉ +(ÓÍ. ÒÁÚÄÅÌ~\ref{sec:tlmgr}). üÔÁ ÐÒÏÇÒÁÍÍÁ ÐÏÚ×ÏÌÑÅÔ ÕÓÔÁÎÁ×ÌÉ×ÁÔØ +ÉÌÉ ÕÄÁÌÑÔØ ÏÔÄÅÌØÎÙÅ ÐÁËÅÔÙ. + +\subsubsection{äÉÒÅËÔÏÒÉÉ} +\label{sec:directories} + +óÈÅÍÁ ÄÉÒÅËÔÏÒÉÊ ÐÏ ÕÍÏÌÞÁÎÉÀ ÏÐÉÓÁÎÁ × ÒÁÚÄÅÌÅ~\ref{sec:texmftrees}, +\p.\pageref{sec:texmftrees}. ðÏÌÏÖÅÎÉÅ ÄÅÒÅ×Á +\dirname{TEXDIR} ÏÔÌÉÞÁÅÔÓÑ ÄÌÑ Windows +(|%PROGRAMFILES%\texlive\2008|) É àÎÉËÓÁ +(\dirname{/usr/local/texlive/2008}). + +ïÓÎÏ×ÎÁÑ ÐÒÉÞÉÎÁ, ÐÏ ËÏÔÏÒÏÊ ÂÙ×ÁÅÔ ÎÅÏÂÈÏÄÉÍÏ ÉÚÍÅÎÉÔØ ÜÔÕ ÓÈÅÍÕ +"--- ÏÔÓÕÔÓÔ×ÉÅ Õ ×ÁÓ ÐÒÁ× ÎÁ ÚÁÐÉÓØ × ÎÕÖÎÙÅ ÄÉÒÅËÔÏÒÉÉ. ÷ÁÍ ÎÅ +ÎÁÄÏ ÉÍÅÔØ ÐÒÁ×Á ÁÄÍÉÎÉÓÔÒÁÔÏÒÁ ÄÌÑ ÕÓÔÁÎÏ×ËÉ \TL{}, ÏÄÎÁËÏ ×ÁÍ ÎÁÄÏ +ÉÍÅÔØ ÐÒÁ×Ï ÐÉÓÁÔØ × ÄÉÒÅËÔÏÒÉÀ, ËÕÄÁ ÕÓÔÁÎÁ×ÌÉ×ÁÅÔÓÑ ÓÉÓÔÅÍÁ. + +åÓÌÉ Õ ×ÁÓ ÎÅÔ ÐÒÁ×Á ÎÁ ÚÁÐÉÓØ × ÓÉÓÔÅÍÎÙÅ ÄÉÒÅËÔÏÒÉÉ, ÅÓÔÅÓÔ×ÅÎÎÏÊ +ÁÌØÔÅÒÎÁÔÉ×ÏÊ Ñ×ÌÑÅÔÓÑ ÕÓÔÁÎÏ×ËÁ × ×ÁÛÕ ÄÏÍÁÛÎÀÀ ÄÉÒÅËÔÏÒÉÀ, ÏÓÏÂÅÎÎÏ +ÅÓÌÉ ×Ù ÂÕÄÅÔÅ ÅÄÉÎÓÔ×ÅÎÎÙÍ ÐÏÌØÚÏ×ÁÔÅÌÅÍ ÓÉÓÔÅÍÙ. äÌÑ ÜÔÏÇÏ +ÉÓÐÏÌØÚÕÊÔÅ `|~|' ÎÁÐÒÉÍÅÒ `|~/texlive/2008|'. + +íÙ ÒÅËÏÍÅÎÄÕÅÍ ×ËÌÀÞÁÔØ ÎÏÍÅÒ ÇÏÄÁ × ÎÁÚ×ÁÎÉÅ ÄÉÒÅËÔÏÒÉÉ, ÞÔÏÂÙ ÍÏÖÎÏ +ÂÙÌÏ ÄÅÒÖÁÔØ ÏÔÄÅÌØÎÏ ÒÁÚÎÙÅ ×ÅÒÓÉÉ \TL{}. ðÏÓÌÅ ÔÅÓÔÉÒÏ×ÁÎÉÑ ÎÏ×ÏÊ +×ÅÒÓÉÉ ×Ù ÓÍÏÖÅÔÅ ÓÄÅÌÁÔØ \dirname{/usr/local/texlive-cur} ÓÓÙÌËÏÊ ÎÁ +ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÕÀ ÄÉÒÅËÔÏÒÉÀ. + +éÚÍÅÎÅÎÉÅ \dirname{TEXDIR} ÉÚÍÅÎÉÔ ÔÁËÖÅ \dirname{TEXMFLOCAL}, +\dirname{TEXMFSYSVAR} É \dirname{TEXMFSYSCONFIG}. + +ìÉÞÎÙÅ ÐÁËÅÔÙ É ÆÁÊÌÙ ÒÅËÏÍÅÎÄÕÅÔÓÑ ÄÅÒÖÁÔØ × ÄÉÒÅËÔÏÒÉÉ +\dirname{TEXMFHOME}. ðÏ ÕÍÏÌÞÁÎÉÀ ÜÔÏ |~/texmf|. ÷ ÏÔÌÉÞÉÅ ÏÔ +\dirname{TEXDIR}, ÚÄÅÓØ |~| ÂÕÄÅÔ Ó×ÏÉÍ ÄÌÑ ËÁÖÄÏÇÏ ÐÏÌØÚÏ×ÁÔÅÌÑ. +üÔÁ ÐÅÒÅÍÅÎÎÁÑ ÓÔÁÎÏ×ÉÔÓÑ \dirname{$HOME} ÐÏÄ àÎÉËÓÏÍ É +\verb|%USERPROFILE%| ÐÏÄ Windows. + +\subsubsection{ïÐÃÉÉ} +\label{sec:options} + +\begin{figure}[tbh] +\begin{boxedverbatim} +

use letter size instead of A4 by default: [ ] + create all format files: [X] + install font/macro doc tree: [X] + install font/macro source tree: [X] + create symlinks in standard directories: [ ] + binaries to: + manpages to: + info to: +\end{boxedverbatim} +\caption{íÅÎÀ ÏÐÃÉÊ (Unix)}\label{fig:options-text} +\end{figure} + +îÁ ÒÉÓÕÎËÅ~\ref{fig:options-text} ÐÒÉ×ÅÄÅÎÏ ÍÅÎÀ ÏÐÃÉÊ (ÔÅËÓÔÏ×ÙÊ +ÒÅÖÉÍ). óÔÏÉÔ ÕÐÏÍÑÎÕÔØ ÔÒÉ ÉÚ ÎÉÈ: +\begin{description} +\item[use letter size instead of A4 by default (ÉÓÐÏÌØÚÏ×ÁÔØ ÐÏ + ÕÍÏÌÏÞÁÎÉÀ ÒÁÚÍÅÒ letter ×ÍÅÓÔÏ A4):] ×ÙÂÏÒ ÒÁÚÍÅÒÁ ÂÕÍÁÇÉ + ÐÏ ÕÍÏÌÞÁÎÉÀ. òÁÚÕÍÅÅÔÓÑ, ÏÔÄÅÌØÎÙÅ ÄÏËÕÍÅÎÔÙ ÍÏÇÕÔ ÐÒÉ + ÎÅÏÂÈÏÄÉÏÓÔÉ ÕËÁÚÁÔØ ÓÏÂÓÔ×ÅÎÎÙÊ ÒÁÚÍÅÒ ÂÕÍÁÇÉ. + +\item[create all format files (ÓÏÚÁÔØ ×ÓÅ ÆÏÒÍÁÔÙ):] èÏÔÑ ÎÅÎÕÖÎÙÅ ÆÏÒÍÁÔÙ ÚÁÎÉÍÁÀÔ ÍÅÓÔÏ + ÎÁ ÄÉÓËÅ É ÔÒÅÂÕÀÔ ×ÒÅÍÅÎÉ ÄÌÑ ÓÏÚÄÁÎÉÑ, ÍÙ ×ÓÅ ÖÅ ÒÅËÏÍÅÎÄÕÅÍ ÎÅ + ÉÚÍÅÎÑÔØ ÜÔÕ ÏÐÃÉÀ. ÷ ÐÒÏÔÉ×ÎÏÍ ÓÌÕÞÁÅ ÏÔÓÕÔÓÔ×ÕÀÝÉÅ ÆÏÒÍÁÔÙ ÂÕÄÕÔ ÇÅÎÒÉÒÏ×ÁÔØÓÑ + × ÄÉÒÅËÔÏÒÉÑÈ \dirname{TEXMFVAR} ÄÌÑ ËÁÖÄÏÇÏ ÐÏÌØÚÏ×ÁÔÅÌÑ. ïÎÉ ÎÅ + ÂÕÄÕÔ Á×ÔÏÍÁÔÉÞÅÓËÉ ÐÅÒÅÇÅÎÅÒÉÒÏ×ÁÔØÓÑ ÐÒÉ ÉÚÍÅÎÅÎÉÉ ÐÒÏÇÒÁÍÍ É ÓÈÅÍ + ÐÅÒÅÎÏÓÁ, É × ÉÔÏÇÅ ÍÏÇÕÔ ÏËÁÚÁÔØÓÑ ÎÅÓÏ×ÍÅÓÔÉÍÙÍÉ Ó ÎÏ×ÏÊ + ÓÉÓÔÅÍÏÊ. + +\item[create symlinks in standard directories (ÓÏÚÄÁÔØ ÓÉÍÌÉÎËÉ × + ÓÔÁÎÄÁÒÔÎÙÈ ÄÉÒÅËÔÏÒÉÑÈ)] (ÔÏÌØËÏ ÄÌÑ àÎÉËÓÁ): üÔÁ ÏÐÃÉÑ ÄÅÌÁÅÔ + ÎÅÎÕÖÎÏÊ ÓÍÅÎÕ ÐÅÒÅÍÅÎÎÙÈ ÏËÒÕÖÅÎÉÑ. âÅÚ ÎÅ£ ÄÉÒÅËÔÏÒÉÉ \TL{} ÎÕÖÎÏ + ÄÏÂÁ×ÉÔØ Ë \envname{PATH}, \envname{MANPATH} É \envname{INFOPATH}. + äÌÑ ÜÔÏÊ ÏÐÃÉÉ ×ÁÍ ÎÕÖÎÙ ÐÒÁ×Á ÎÁ ÚÁÐÉÓØ × ÓÔÁÎÄÁÒÔÎÙÅ ÄÉÒÅËÔÏÒÉÉ. + íÙ ÎÅ ÓÏ×ÅÔÕÅÍ ×ÁÍ ÐÏÄÍÅÎÑÔØ \TeX{} ÉÚ ÄÉÓÔÒÉÂÕÔÉ×Á ×ÁÛÅÊ ÓÉÓÔÅÍÙ + ÐÒÉ ÐÏÍÏÝÉ ÜÔÏÊ ÏÐÃÉÉ. ïÎÁ ÎÕÖÎÁ ÄÌÑ ÓÏÚÄÁÎÉÑ ÓÉÍÌÉÎËÏ× × + ÄÉÒÅËÔÏÒÉÑÈ ÔÉÐÁ \dirname{/usr/local/bin}, ËÏÔÏÒÙÅ ÎÅ ÓÏÄÅÒÖÁÔ + ÆÁÊÌÏ× \TeX Á ÉÚ ÓÉÓÔÅÍÎÏÇÏ ÄÉÓÔÒÉÂÕÔÉ×Á. +\end{description} + +úÁÄÁ× ÎÕÖÎÙÅ ÎÁÓÔÒÏÊËÉ, ×Ù ÍÏÖÅÔÅ ÎÁÞÁÔØ ÕÓÔÁÎÏ×ËÕ ÓÉÓÔÅÍÙ, ÎÁÖÁ× +ËÌÁ×ÉÛÕ <<|I|>>. ëÏÇÄÁ ÕÓÔÁÎÏ×ËÁ ÚÁËÏÎÞÅÎÁ, ÐÅÒÅÊÄÉÔÅ Ë +ÒÁÚÄÅÌÕ~\ref{sec:postinstall}. + +\subsubsection{îÁÓÔÒÏÊËÁ ÄÌÑ ÒÁÂÏÔÙ Ó DVD{} (ÔÏÌØËÏ ÔÅËÓÔÏ×ÙÊ ÒÅÖÉÍ)} +\label{sec:fromdvd} + +äÌÑ ×ÙÂÏÒÁ ÜÔÏÊ ÏÐÃÉÉ ÎÁÖÍÉÔÅ ËÌÁ×ÉÛÕ <<|V|>>. ïÓÎÏ×ÎÏÅ ÍÅÎÀ ÓÔÁÎÅÔ +ÔÁËÉÍ, ËÁË ÎÁ ÒÉÓÕÎËÅ~\ref{fig:main-fromdvd}. +\begin{figure}[tbh] +\begin{boxedverbatim} +======================> TeX Live installation procedure <===================== + +=======> Note: Letters/digits in indicate menu items <======= +=======> for commands or configurable options <======= + + directories: + TEXDIRW (Writable root): + !! default location: /usr/local/texlive/2008 + !! is not writable, please select a different one! + TEXMFLOCAL (directory for site-wide local files): + /usr/local/texlive/texmf-local + TEXMFSYSVAR (directory for variable and automatically generated data): + /usr/local/texlive/2008/texmf-var + TEXMFSYSCONFIG (directory for local config): + /usr/local/texlive/2008/texmf-config + TEXMFHOME (directory for user-specific files): + ~/texmf + + options: + [ ] use letter size instead of A4 by default + [X] create all format files + + set up for installing to hard disk + +Other actions: + start installation for running from DVD + help + quit +\end{boxedverbatim} +\caption{ïÓÎÏ×ÎÏÅ ÍÅÎÀ ÐÏÓÌÅ ×ÙÂÏÒÁ ÏÐÃÉÉ \optname{from + DVD}}\label{fig:main-fromdvd} +\end{figure} + +ïÂÒÁÔÉÔÅ ×ÎÉÍÁÎÉÅ ÎÁ ÉÚÍÅÎÅÎÉÑ: ÉÓÞÅÚÌÉ ×ÓÅ ÏÐÃÉÉ ×ÙÂÏÒÁ, ÞÔÏ +ÕÓÔÁÎÁ×ÌÉ×ÁÔØ, Á ÍÅÎÀ ÄÉÒÅËÔÏÒÉÊ ÇÏ×ÏÒÉÔ ÔÅÐÅÒØ Ï \dirname{TEXDIRW}, +Ô.Å. ÞÁÓÔÉ ÄÅÒÅ×Á ÎÁ ÌÏËÁÌØÎÏÍ ÄÉÓËÅ. ïÐÃÉÑ ÓÏÚÄÁÎÉÑ ÓÉÍÌÉÎËÏ× ÔÁËÖÅ +ÉÓÞÅÚÌÁ. + +ðÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ ÓÏÚÄÁÓÔ ÒÁÚÌÉÞÎÙÅ ÄÉÒÅËÔÏÒÉÉ É ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ +ÆÁÊÌÙ, ÎÏ ÎÅ ÂÕÄÅÔ ËÏÐÉÒÏ×ÁÔØ ÎÁ ÄÉÓË ËÏÍÐØÀÔÅÒÁ \dirname{texmf}, +\dirname{texmf-dist} ÉÌÉ \dirname{texmf-doc}. + +äÅÊÓÔ×ÉÑ ÐÏÓÌÅ ÕÓÔÁÎÏ×ËÉ ÄÌÑ àÎÉËÓÁ ÂÕÄÕÔ ÞÕÔØ ÓÌÏÖÎÅÅ, ÞÅÍ × +ÐÒÅÄÙÄÕÝÅÍ ÓÌÕÞÁÅ, ÐÏÓËÏÌØËÕ ÒÁÓÐÏÌÏÖÅÎÉÅ ÄÉÒÅËÔÏÒÉÊ ÔÅÐÅÒØ ÏÔÌÉÞÁÅÔÓÑ +ÏÔ ÓÔÁÎÄÁÒÔÎÏÇÏ; ÓÍ. ÒÁÚÄÅÌ~\ref{sec:postinstall}. + +éÚ-ÚÁ ÎÅÄÏÓÔÁÔËÁ ×ÒÅÍÅÎÉ ÜÔÏÊ ÏÐÃÉÉ ÐÏËÁ ÎÅÔ × ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ, ÎÏ +ÏÎÁ ÄÏÓÔÕÐÎÁ É ÄÌÑ àÎÉËÓÁ, É ÄÌÑ Wiindows. ðÏÌØÚÏ×ÁÔÅÌÑÍ Windows +ÐÒÉÄÅÔÓÑ ÚÁÐÕÓÔÉÔØ ÐÒÏÇÒÁÍÍÕ ÕÓÔÁÎÏ×ËÉ ÉÚ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ, +ÓÍ. ÒÁÚÄÅÌ~\ref{sec:cmdline}. + +÷ ÒÁÚÄÅÌÅ~\ref{sec:portable-unix} ÏÐÉÓÁÎ ÄÒÕÇÏÊ ÓÐÏÓÏ ÚÁÐÕÓËÁ \TL{} Ó +ÄÉÓËÁ, ËÏÔÏÒÙÊ ÎÅ ÔÒÅÂÕÅÔ ÉÚÍÅÎÅÎÉÊ × ËÏÎÆÉÇÕÒÁÃÉÉ ÓÉÓÔÅÍÙ "--- ÎÏ É +ÎÅ ÐÏÚ×ÏÌÑÅÔ ÎÁÓÔÒÁÉ×ÁÔØ \TL{}. + +\subsection{ïÐÃÉÉ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ} +\label{sec:cmdline} + +îÁÐÅÞÁÔÁÊÔÅ +\begin{alltt} +> \Ucom{install-tl -help} +\end{alltt} +ÞÔÏÂÙ ÐÏÌÕÞÉÔØ ÓÐÉÓÏË ÏÐÃÉÊ ËÏÍÁÄÎÏÊ ÓÔÒÏËÉ. ÷ ÏÐÃÉÑÈ ÍÏÖÎÏ +ÉÓÐÏÌØÚÏ×ÁÔØ ËÁË |-|, ÔÁË É |--|. ÷ÏÔ ÓÁÍÙÅ ÉÎÔÅÒÅÓÎÙÅ ÏÐÃÉÉ: + +\begin{ttdescription} +\item[-gui] åÓÌÉ ×ÏÚÍÏÖÎÏ, ÉÓÐÏÌØÚÏ×ÁÔØ ÇÒÁÇÉÞÅÓËÉÊ ÒÅÖÉÍ. äÌÑ ÜÔÏÇÏ + ÎÕÖÅÎ ÍÏÄÕÌØ Perl/Tk (\url{http://tug.org/texlive/distro.html#perltk}); + ÅÓÌÉ ÜÔÏÇÏ ÍÏÄÕÌÑ × ÓÉÓÔÅÍÅ ÎÅÔ, ÕÓÔÁÎÏ×ËÁ ÐÒÏÉÓÈÏÄÉÔ × ÔÅËÓÔÏ×ÏÍ + ÒÅÖÉÍÅ. +\item[-no-gui] éÓÐÏÌØÚÏ×ÁÔØ ÔÅËÓÔÏ×ÙÊ ÒÅÖÉÍ, ÄÁÖÅ ÐÏÄ Windows. ÷ÁÍ + ÐÏÎÁÄÏÂÉÔÓÑ ÜÔÁ ÏÐÃÉÑ, ÅÓÌÉ ×Ù ÈÏÔÉÔÅ ÚÁÐÕÓËÁÔØ \TL{} Ó \DVD{}, + ÐÏÓËÏÌØËÕ ÜÔÏ ÐÏËÁ ÎÅ×ÏÚÍÏÖÎÏ × ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ. +\item[-lang {\sl LL}] úÁÄÁÔØ ÑÚÙË ÉÎÔÅÒÆÅÊÓÁ ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ + (ÓÔÁÎÄÁÒÔÎÙÍ ËÏÄÏÍ ÓÔÒÁÎÙ \textsl{LL}). óÅÊÞÁÓ ÄÏÓÔÕÐÎÙ ÓÌÅÄÕÀÝÉÅ ÑÚÙËÉ: + ÁÎÇÌÉÊÓËÉÊ (\texttt{en}, ÚÎÁÞÅÎÉÅ ÐÏ ÕÍÏÌÞÁÎÉÀ), ÎÅÍÅÃËÉÊ + (\texttt{de}), ÆÒÁÎÃÕÚÓËÉÊ (\texttt{fr}), ÇÏÌÌÁÎÄÓËÉÊ (\texttt{nl}), ÐÏÌØÓËÉÊ + (\texttt{pl}), ÓÌÏ×ÅÎÓËÉÊ (\texttt{sl}) É ×ØÅÔÎÁÍÓËÉÊ + (\texttt{vi}). ðÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ ÐÙÔÁÅÔÓÑ ÏÐÒÅÄÅÌÅÔØ ÎÕÖÎÙÊ ÑÚÙË + Á×ÔÏÍÁÔÉÞÅÓËÉ, ÎÏ ÅÓÌÉ ÜÔÏ ÎÅ ÐÏÌÕÞÁÅÔÓÑ ÉÌÉ ÅÓÌÉ ÎÕÖÎÙÊ ÑÚÙË ÎÅ + ÐÏÄÄÅÒÖÉ×ÁÅÔÓÑ, ÏÎÁ ÐÅÒÅÈÏÄÉÔ ÎÁ ÁÎÇÌÉÊÓËÉÊ. +\item[-profile {\sl profile}] ðÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ ×ÓÅÇÄÁ ÚÁÐÉÓÙ×ÁÅÔ ÆÁÊÌ + \filename{texlive.profile} × ÐÏÄÄÉÒÅËÔÏÒÉÀ \dirname{2008/tlpkg} ÉÌÉ + \dirname{tlpkg}. üÔÁ ÏÐÃÉÑ ÚÁÓÔÁ×ÌÑÅÔ ÐÒÏÇÒÁÍÍÕ ÉÓÐÏÌØÚÏ×ÁÔØ ÜÔÏÔ + ÆÁÊÌ. ÷ÏÔ ÐÒÉÍÅÒ ÔÁËÏÇÏ ÆÁÊÌÁ: + \begin{fverbatim} +# texlive.profile written on Wed Jul 9 16:13:44 2008 UTC +# It will NOT be updated and reflects only the +# installation profile at installation time. +selected_scheme scheme-basic +TEXDIR /usr/local/texlive/2008 +TEXDIRW /usr/local/texlive/2008 +... +TEXMFSYSVAR /usr/local/texlive/2008/texmf-var +collection-basic 1 +... +option_symlinks 0 + \end{fverbatim} + ðÒÉ ÐÏÍÏÝÉ ÜÔÏÊ ÏÐÃÉÉ ×Ù ÍÏÖÅÔÅ ÕÓÔÁÎÁ×ÌÉ×ÁÔØ \TL{} ÎÁ ÎÅÓËÏÌØËÉÈ + ÍÁÛÉÎÁÈ Ó ÏÄÎÉÍÉ É ÔÅÍÉ ÖÅ ÐÁÒÁÍÅÔÒÁÍÉ. +\item [-location {\sl url/path}] õËÁÚÁÔØ ÁÌØÔÅÒÎÁÔÉ×ÎÙÊ ÉÓÔÏÞÎÉË + ÐÁËÅÔÏ×; ÓÍ. ÎÉÖÅ. +\end{ttdescription} + +\subsubsection{ðÁÒÁÍÅÔÒ \optname{location}} +\label{sec:location} + +úÎÁÞÅÎÉÅ ÜÔÏÇÏ ÐÁÒÁÍÅÔÒÁ ÍÏÖÅÔ ÂÙÔØ URL, ÎÁÞÉÎÁÀÝÉÓÑ Ó \texttt{ftp:}, +\texttt{http:}, \texttt{file:/} ÉÌÉ ÄÉÒÅËÔÏÒÉÑ ÎÁ ÄÉÓËÅ. åÓÌÉ +ÁÒÇÕÍÅÎÔ ÚÁÄÁÅÔ ÄÉÒÅËÔÏÒÉÀ ÎÁ ÄÉÓËÉ (ÐÒÑÍÏ ÉÌÉ ÐÒÉ ÐÏÍÏÝÉ +\texttt{file:/}), ÓÉÓÔÅÍÁ Á×ÔÏÍÁÔÉÞÅÓËÉ ÏÐÒÅÄÅÌÑÅÔ, Ñ×ÌÑÅÔÓÑ ÌÉ +ÉÓÔÏÞÎÉË ÁÒÈÉ×ÏÍ: ÅÓÌÉ ÎÁÊÄÅÎÁ ÐÏÄÄÉÒÅËÔÏÒÉÑ \dirname{archive} Ó +ÆÁÊÌÁÍÉ \filename{.tar.lzma}, ÔÏ ÏÎÁ ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÎÁ, ÄÁÖÅ ÅÓÌÉ +ÒÑÄÏÍ ÎÁÈÏÄÑÔÓÑ ÎÅÚÁÁÒÈÉ×ÉÒÏ×ÁÎÎÙÅ ÆÁÊÌÙ. + +åÓÌÉ ÐÁÒÁÍÅÔÒ ÎÁÞÉÎÁÅÔÓÑ Ó \texttt{http:} ÉÌÉ \texttt{ftp:}, ÔÏ ÓÉÍ×ÏÌ +\texttt{/} ÉÌÉ ÄÉÒÅËÔÏÒÉÑ \texttt{/tlpkg} × ËÏÎÃÅ ÐÁÒÁÍÅÔÒÁ +ÉÇÎÏÒÉÒÕÀÔÓÑ. îÁÐÒÉÍÅÒ, ×Ù ÍÏÖÅÔÅ ÚÁÄÁÔØ × ËÁÞÅÓÔ×Å ÐÁÒÁÍÅÔÒÁ ÚÅÒËÁÌÏ +\CTAN{}: +\url{http://ctan.example.org/tex-archive/texlive/tlnet/2008}. +òÁÚÕÍÅÅÔÓÑ, ×ÁÍ ÓÌÅÄÕÅÔ ÐÏÄÓÔÁ×ÉÔØ ×ÍÅÓÔÏ \dirname{example.ctan.org} +ÎÕÖÎÏÅ ÚÅÒËÁÌÏ É ÐÕÔØ Ë ÁÒÈÉ×Õ ÎÁ ÜÔÏÍ ÚÅÒËÁÌÅ (ÓÐÉÓÏË ÚÅÒËÁÌ +ÎÁÈÏÄÉÔÓÑ ÎÁ \url{http://mirror.ctan.org}). ðÏ ÕÍÏÌÞÁÎÉÀ ÚÅÒËÁÌÏ +ÏÐÒÅÄÅÌÑÅÔÓÑ Á×ÔÏÍÁÔÉÞÅÓËÉ ÉÚ ÓÐÉÓËÁ ÎÁ \url{http://mirror.ctan.org}; +× ÌÀÂÏÍ ÓÌÕÞÁÅ ×ÙÂÒÁÎÎÏÅ ÚÅÒËÁÌÏ ÉÓÐÏÌØÚÕÅÔÓÑ ÄÌÑ ×ÓÅÊ ÕÓÔÁÎÏ×ËÉ. + + +\subsection{äÅÊÓÔ×ÉÑ ÐÏÓÌÅ ÕÓÔÁÎÏ×ËÉ} +\label{sec:postinstall} + +éÎÏÇÄÁ ÐÏÓÌÅ ÕÓÔÁÎÏ×ËÉ ÓÉÓÔÅÍÙ ÔÒÅÂÕÀÔÓÑ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ÄÅÊÓÔ×ÉÑ. + +\subsubsection{Windows} + +ðÏÄ Windows ÐÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ ÓÁÍÁ ÄÅÌÁÅÔ ×ÓÅ ÎÅÏÂÈÏÄÉÍÏÅ. + +\subsubsection{åÓÌÉ ÓÏÚÄÁÎÙ ÓÉÍÌÉÎËÉ} + +åÓÌÉ ×Ù ÒÅÛÉÌÉ ÓÏÚÄÁÔØ ÓÉÍÌÉÎËÉ × ÓÔÁÎÄÁÒÔÎÙÈ ÄÉÒÅËÔÏÒÉÑÈ +(ÓÍ. ÒÁÚÄÅÌ~\ref{sec:options}), ÔÏ ÍÅÎÑÔØ ÐÅÒÅÍÅÎÎÙÅ ÏËÒÕÖÅÎÉÑ ÎÅ +ÎÕÖÎÏ. + +\subsubsection{ðÅÒÅÍÅÎÎÙÅ ÏËÒÕÖÅÎÉÑ ÄÌÑ àÎÉËÓÁ} +\label{sec:env} + +äÉÒÅËÔÏÒÉÑ Ó ÐÒÏÇÒÁÍÍÁÍÉ ÄÌÑ ×ÁÛÅÊ ÐÌÁÔÆÏÒÍÙ ÄÏÌÖÎÁ ÂÙÔØ ÄÏÂÁ×ÌÅÎÁ Ë +ÐÕÔÉ ÐÏÉÓËÁ. ðÒÏÇÒÁÍÍÙ ÄÌÑ ËÁÖÄÏÊ ÁÒÈÉÔÅËÔÕÒÙ ÐÏÍÅÝÁÀÔÓÑ × +ÓÏÂÓÔ×ÅÎÎÕÀ ÐÏÄÄÉÒÅËÔÏÒÉÀ ÐÏÄ \dirname{TEXDIR/bin}. óÍ. ÓÐÉÓÏË +ÐÏÄÄÉÒÅËÔÏÒÉÊ É ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÈ ÐÌÁÔÆÏÒÍ ÎÁ +ÒÉÓÕÎËÅ~\ref{fig:bin-text}. + +÷Ù ÍÏÖÅÔÅ ÔÁËÖÅ ÄÏÂÁ×ÉÔØ ÄÉÒÅËÔÏÒÉÉ Ó ÄÏËÕÍÅÎÔÁÃÉÅÊ × ÆÏÒÍÁÔÅ man É +info Ë ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÍ ÐÕÔÑÍ ÐÏÉÓËÁ, ÅÓÌÉ ×Ù ÈÏÔÉÔÅ, ÞÔÏÂÙ ×ÁÛÁ +ÏÐÅÒÁÃÉÏÎÎÁÑ ÓÉÓÔÅÍÁ ÚÎÁÌÁ Ï ÎÉÈ. + +îÉÖÅ ÍÙ ÉÓÐÏÌØÚÕÅÍ ÄÌÑ ÐÒÉÍÅÒÁ ÓÔÁÎÄÁÒÔÎÕÀ ÓÉÓÔÅÍÕ ÄÉÒÅËÔÏÒÉÊ × ÓÉÓÔÅÍÅ +Intel86 GNU/Linux. + +äÌÑ ÏÂÏÌÏÞÅË ÔÉÐÁ Bourne (\prog{bash} É Ô.Ð.) ×Ù ÍÏÖÅÔÅ ÄÏÂÁ×ÉÔØ × +ÆÁÊÌ \filename{$HOME/.profile} (ÉÌÉ × ÆÁÊÌ, ËÏÔÏÒÙÊ ×ÙÚÙ×ÁÅÔÓÑ ÉÚ +\filename{.profile}) ÓÌÅÄÕÀÝÅÅ: + +\begin{sverbatim} +PATH=/usr/local/texlive/2008/bin/i386-linux:$PATH; export PATH +MANPATH=/usr/local/texlive/2008/texmf/doc/man:$MANPATH; export MANPATH +INFOPATH=/usr/local/texlive/2008/texmf/doc/info:$INFOPATH; export INFOPATH +\end{sverbatim} + +äÌÑ \prog{csh} ÉÌÉ \prog{tcsh} ÓÌÅÄÕÅÔ ÒÅÄÁËÔÉÒÏ×ÁÔØ ÆÁÊÌ +\filename{$HOME/.cshrc}, É ÓÌÅÄÕÅÔ ÄÏÂÁ×ÉÔØ ÞÔÏ-ÔÏ ×ÒÏÄÅ + +\begin{sverbatim} +setenv PATH /usr/local/texlive/2008/bin/i386-linux:$PATH +setenv MANPATH /usr/local/texlive/2008/texmf/doc/man:$MANPATH +setenv INFOPATH /usr/local/texlive/2008/texmf/doc/info:$INFOPATH +\end{sverbatim} + +òÁÚÕÍÅÅÔÓÑ, × ×ÁÛÉÈ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÈ ÆÁÊÌÁÈ ÕÖÅ ÍÏÇÕÔ ÂÙÔØ ÏÐÒÅÄÅÌÅÎÙ +ÜÔÉ ÐÅÒÅÍÅÎÎÙÅ; ÆÒÁÇÍÅÎÔÙ ×ÙÛÅ ÄÏÂÁ×ÌÑÀÔ Ë ÎÉÍ ÄÉÒÅËÔÏÒÉÉ \TL{}. + +\subsubsection{ðÅÒÅÍÅÎÎÙÅ ÏËÒÕÖÅÎÉÑ: ÇÌÏÂÁÌØÎÁÑ ËÏÎÆÉÇÕÒÁÃÉÑ} +\label{sec:envglobal} + +åÓÌÉ ×Ù ÈÏÔÉÔÅ ×ÎÅÓÔÉ ÜÔÉ ÉÚÍÅÎÅÎÉÑ ÄÌÑ ×ÓÅÈ ÐÏÌØÚÏ×ÁÔÅÌÅÊ, ÉÌÉ +ÄÏÂÁ×ÌÑÔØ ÉÈ Á×ÔÏÍÁÔÉÞÅÓËÉ ÄÌÑ ÎÏ×ÙÈ ÐÏÌØÚÏ×ÁÔÅÌÅÊ, ÔÏ ×ÁÍ ÓÌÅÄÕÅÔ +ÒÁÚÏÂÒÁÔØÓÑ ÓÁÍÏÍÕ: × ÒÁÚÎÙÈ ÓÉÓÔÅÍÁÈ ÜÔÏ ÄÅÌÁÅÔÓÑ ÓÌÉÛËÏÍ +ÐÏ-ÒÁÚÎÏÍÕ. + +ä×Á ÓÏ×ÅÔÁ: 1)~×ÏÚÍÏÖÎÏ, ×ÁÍ ÓÌÅÄÕÅÔ ÄÏÂÁ×ÉÔØ × ÆÁÊÌ +\filename{/etc/manpath.config} ÓÔÒÏÞËÉ ×ÒÏÄÅ: + +\begin{sverbatim} +MANPATH_MAP /usr/local/texlive/2008/bin/i386-linux \ + /usr/local/texlive/2008/texmf/doc/man +\end{sverbatim} + +é 2)~ÉÎÏÇÄÁ ÐÕÔÉ ÐÏÉÓËÁ É ÄÒÕÇÉÅ ÇÌÏÂÁÌØÎÙÅ ÐÅÒÅÍÅÎÎÙÅ ÏËÒÕÖÅÎÉÑ +ÚÁÄÁÀÔÓÑ × ÆÁÊÌÅ \filename{/etc/environment}. + +\subsubsection{òÁÂÏÔÁ Ó DVD} + +ïÂÙÞÎÏ ÐÒÏÇÒÁÍÍÙ \TL{} ÕÚÎÁÀÔ, ÇÄÅ ÎÁÈÏÄÑÔÓÑ ÎÕÖÎÙÅ ÄÉÒÅËÔÏÒÉÉ, ÉÚ +ÆÁÊÌÁ \filename{texmf.cnf}. ïÎÉ ÉÝÕÔ ÜÔÏÔ ÆÁÊÌ, ÉÓÈÏÄÑ ÉÚ ÔÏÇÏ, ÇÄÅ +ÎÁÈÏÄÑÔÓÑ ÓÁÍÉ. ïÄÎÁËÏ ÜÔÁ ÓÈÅÍÁ ÎÅ ÒÁÂÏÔÁÅÔ, ËÏÇÄÁ ÐÒÏÇÒÁÍÍÁ +ÚÁÐÕÓËÁÅÔÓÑ Ó \DVD{}. îÁ \DVD{} ÎÅÌØÚÑ ÐÉÓÁÔØ, ÎÏ ÎÅËÏÔÏÒÙÅ ÐÕÔÉ, +ËÏÔÏÒÙÅ ÄÏÌÖÎÙ ÂÙÔØ × \filename{texmf.cnf}, ÉÚ×ÅÓÔÎÙ ÔÏÌØËÏ ÐÏÓÌÅ +ÕÓÔÁÎÏ×ËÉ, ÐÏÜÔÏÍÕ ÜÔÏÔ ÆÁÊÌ ÎÅ ÍÏÖÅÔ ÎÁÈÏÄÉÔØÓÑ ÎÁ \DVD{}, É ÄÏÌÖÅÎ +ÂÙÔØ × ÄÒÕÇÏÍ ÍÅÓÔÅ. üÔÏ ÏÚÎÁÞÁÅÔ, ÞÔÏ ÎÅÏÂÈÏÄÉÍÏ ÏÐÒÅÄÅÌÉÔØ +ÐÅÒÅÍÅÎÎÕÀ ÏËÒÕÖÅÎÉÑ \envname{TEXMFCNF}, ËÏÔÏÒÁÑ ÇÏ×ÏÒÉÔ ÐÒÏÇÒÁÍÍÁÍ +\TL{}, ÇÄÅ ÉÓËÁÔØ ÆÁÊÌ \filename{texmf.cnf}. îÅÏÂÈÏÄÉÍÏ ÔÁËÖÅ +ÉÚÍÅÎÉÔØ ÐÅÒÅÍÅÎÎÕÀ \envname{PATH}, ËÁË ÏÐÓÁÎÏ ×ÙÛÅ. + +÷ ËÏÎÃÅ ÕÓÔÁÎÏ×ËÉ ÐÒÏÇÒÁÍÍÁ ÐÉÛÅÔ ÓÏÏÂÝÅÎÉÅ, ÇÄÅ ÕËÁÚÁÎÏ, ÞÅÍÕ ÄÏÌÖÎÁ +ÒÁ×ÎÑÔØÓÑ ÐÅÒÅÍÅÎÎÁÑ \envname{TEXMFCNF}. îÁ ÓÌÕÞÁÊ, ÅÓÌÉ ×Ù +ÐÒÏÐÕÓÔÉÌÉ ÜÔÏ ÓÏÏÂÝÅÎÉÅ: ÜÔÏ \dirname{$TEXMFSYSVAR/web2c}. ðÏ +ÕÍÏÌÞÁÎÉÀ ÜÔÏ \dirname{/usr/local/texlive/2008/texmf-var/web2c}, É +×ÁÍ ÎÕÖÎÏ ÕÓÔÁÎÏ×ÉÔØ Å£ ÔÁË: +\begin{sverbatim} +TEXMFCNF=/usr/local/texlive/2008/texmf-var/web2c; export TEXMFCNF +\end{sverbatim} +ÉÌÉ, ÄÌÑ [t]csh: +\begin{sverbatim} +setenv TEXMFCNF /usr/local/texlive/2008/texmf-var/web2c +\end{sverbatim} + +\subsubsection{\ConTeXt{} Mark IV} + +<<óÔÁÒÙÊ>> \ConTeXt{} ÄÏÌÖÅÎ ÒÁÂÏÔÁÔØ <<ÉÚ ËÏÒÏÂËÉ>>. îÏ×ÁÑ ÓÉÓÔÅÍÁ +Mark~IV ÔÒÅÂÕÅÔ ÒÕÞÎÏÊ ËÏÎÆÉÇÕÒÁÃÉÉ; +ÓÍ. \url{http://wiki.contextgarden.net/Running_Mark_IV}. + + +\subsubsection{äÏÂÁ×ÌÅÎÉÅ ÌÉÞÎÙÈ É ÌÏËÁÌØÎÙÈ ÐÁËÅÔÏ×} +\label{sec:local-personal-macros} + +üÔÏÔ ×ÏÐÒÏÓ ÕÖÅ ÏÂÓÕÖÄÁÌÓÑ × ÒÁÚÄÅÌÅ~\ref{sec:texmftrees}: ÄÌÑ +ÌÏËÁÌØÎÙÈ ÛÒÉÆÔÏ× É ÐÁËÅÔÏ× ÐÒÅÄÎÁÚÎÁÞÅÎÁ ÄÉÒÅËÔÏÒÉÑ +\dirname{TEXMFLOCAL} (ÐÏ ÕÍÏÌÞÁÎÉÀ, +\dirname{/usr/local/texlive/texmf-local} ÉÌÉ +\verb|C:\Program Files\texlive\texmf-local|), Á ÄÌÑ ÌÉÞÎÙÈ ÛÒÉÆÔÏ× É +ÐÁËÅÔÏ× "--- ÄÉÒÅËÔÏÒÉÑ \dirname{TEXMFHOME} (ÐÏ ÕÍÏÌÞÁÎÉÀ, +\dirname{$HOME/texmf} ÉÌÉ \verb|%USERPROFILE%\texmf|). üÔÉ ÄÉÒÅËÔÏÒÉÉ +ÐÒÅÄÐÏÌÁÇÁÀÔÓÑ ÏÂÝÉÍÉ ÄÌÑ ×ÓÅÈ ×ÅÒÓÉÊ \TL{}, É ËÁÖÄÁÑ ×ÅÒÓÉÑ \TL{} +×ÉÄÉÔ ÉÈ Á×ÔÏÍÁÔÉÞÅÓËÉ. ðÏÜÔÏÍÕ ÍÙ ÎÅ ÒÅËÏÍÅÎÄÕÅÍ ÍÅÎÑÔØ ÚÎÁÞÅÎÉÅ +\dirname{TEXMFLOCAL}, ÉÎÁÞÅ ×ÁÍ ÐÒÉÄÅÔÓÑ ÄÅÌÁÔØ ÜÔÏ ÄÌÑ ËÁÖÄÏÊ ÎÏ×ÏÊ +×ÅÒÓÉÉ. + +æÁÊÌÙ × ÏÂÅÉÈ ÄÉÒÅËÔÏÒÉÑÈ ÄÏÌÖÎÙ ÎÁÈÏÄÉÔØÓÑ × ÐÒÁ×ÉÌØÎÙÈ +ÐÏÄÄÉÒÅËÔÏÒÉÑÈ; ÓÍ. \url{http://tug.org/tds} É +\filename{texmf/web2c/texmf.cnf}. îÁÐÒÉÍÅÒ, \LaTeX Ï×ÓËÉÊ ËÌÁÓÓ ÉÌÉ +ÐÁËÅÔ ÄÏÌÖÅÎ ÎÁÈÏÄÉÔØÓÑ × ÄÉÒÅËÔÏÒÉÉ \dirname{TEXMFLOCAL/tex/latex} ÉÌÉ +\dirname{TEXMFHOME/tex/latex} ÉÌÉ ËÁËÏÊ-ÌÉÂÏ ÉÚ ÉÈ ÐÏÄÄÉÒÅËÔÏÒÉÊ. + +äÌÑ ÄÉÒÅËÔÏÒÉÉ \dirname{TEXMFLOCAL} ÄÏÌÖÎÁ ÐÏÄÄÅÒÖÉ×ÁÔØÓÑ ÂÁÚÁ ÄÁÎÎÙÈ +Ï ÆÁÊÌÁÈ, ÉÎÁÞÅ ÓÉÓÔÅÍÁ ÎÅ ÓÍÏÖÅÔ ÎÁÊÔÉ ÔÁÍ ÎÕÖÎÙÅ ÆÁÊÌÙ. üÔÁ ÂÁÚÁ +ÏÂÎÏ×ÌÑÅÔÓÑ ËÏÍÁÎÄÏÊ \cmdname{mktexlsr} ÉÌÉ ËÎÏÐËÏÊ <> × ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ ÐÒÏÇÒÁÍÍÙ \prog{tlmgr}. + +\subsubsection{äÏÂÁ×ÌÅÎÉÅ ÛÒÉÆÔÏ×} + +ë ÓÏÖÁÌÅÎÉÀ, ÜÔÏ ÏÞÅÎØ ÓÌÏÖÎÁÑ ÚÁÄÁÞÁ. îÅ ÄÅÌÁÊÔÅ ÜÔÏÇÏ, ÅÓÌÉ ×Ù ÎÅ +ÚÎÁÅÔÅ \TeX Á ËÁË Ó×ÏÉ ÐÑÔØ ÐÁÌØÃÅ×. îÅ ÚÁÂÕÄØÔÅ ÓÎÁÞÁÌÁ ÐÒÏ×ÅÒÉÔØ, +ËÁËÉÅ ÛÒÉÆÔÙ Õ ×ÁÓ ÕÖÅ ÅÓÔØ, ÓÍ. ÒÁÚÄÅÌ~\ref{sec:tl-fonts}. + +÷ÏÚÍÏÖÎÁÑ ÁÌØÔÅÒÎÁÔÉ×Á "--- ÐÒÏÇÒÁÍÍÁ \XeTeX{} (ÓÍ. +ÒÁÚÄÅÌ~\ref{sec:tex-extensions}), ËÏÔÏÒÁÑ ÐÏÚ×ÏÌÑÅÔ Á×ÔÏÍÁÔÉÞÅÓËÉ +ÉÓÐÏÌØÚÏ×ÁÔØ × \TeX Å ÛÒÉÆÔÙ ×ÁÛÅÊ ÏÐÅÒÁÃÉÏÎÎÏÊ ÓÉÓÔÅÍÙ. + +\subsection{ôÅÓÔÉÒÏ×ÁÎÉÅ ÓÉÓÔÅÍÙ} +\label{sec:test-install} + + +ðÏÓÌÅ ÕÓÔÁÎÏ×ËÉ \TL{} ×Ù, ÓËÏÒÅÅ ×ÓÅÇÏ, ÚÁÈÏÔÉÔÅ ÐÒÏ×ÅÒÉÔØ ÒÁÂÏÔÕ +ÓÉÓÔÅÍÙ, Á ÕÖÅ ÚÁÔÅÍ ÐÅÒÅÊÔÉ Ë ÓÏÚÄÁÎÉÀ ÐÒÅËÒÁÓÎÙÈ ÄÏËÕÍÅÎÔÏ× É/ÉÌÉ +ÛÒÉÆÔÏ×. + +÷ ÜÔÏÍ ÒÁÚÄÅÌÅ ÏÐÉÓÙ×ÁÀÔÓÑ ÏÓÎÏ×ÎÙÅ ÐÒÏÃÅÄÕÒÙ ÐÏ ÔÅÓÔÉÒÏ×ÁÎÉÀ ÓÉÓÔÅÍÙ. +íÙ ÐÒÉ×ÏÄÉÍ ËÏÍÁÎÄÙ ÄÌÑ ÏÐÅÒÁÃÉÏÎÎÙÈ ÓÉÓÔÅÍ ÔÉÐÁ Unix; ÐÏÄ \MacOSX{} É +Windows ×Ù, ÓËÏÒÅÅ ×ÓÅÇÏ, ÂÕÄÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ ÇÒÁÆÉÞÅÓËÉÊ ÉÎÔÅÒÆÅÊÓ, +ÎÏ ÐÒÉÎÃÉÐ ÔÏÔ ÖÅ. + +\begin{enumerate} + +\item óÎÁÞÁÌÁ ÐÒÏ×ÅÒØÔÅ, ÞÔÏ ×Ù ÍÏÖÅÔÅ ÚÁÐÕÓËÁÔØ ÐÒÏÇÒÁÍÍÕ + \cmdname{tex}: + +\begin{alltt} +> \Ucom{tex -{}-version} +TeX 3.1415926 (Web2C 7.5.7) +kpathsea version 3.5.7 +... +\end{alltt} +åÓÌÉ ×Ù ÐÏÌÕÞÁÅÔÅ × ÏÔ×ÅÔ <> ×ÍÅÓÔÏ ÎÏÍÅÒÁ ×ÅÒÓÉÉ É +ÉÎÆÏÒÍÁÃÉÉ Ï ËÏÐÉÒÁÊÔÅ, Õ ×ÁÓ, ÓËÏÒÅÅ ×ÓÅÇÏ, ÎÅÔ ÄÉÒÅËÔÏÒÉÉ Ó ÎÕÖÎÙÍÉ +ÐÒÏÇÒÁÍÍÁÍÉ × ÐÅÒÅÍÅÎÎÏÊ \envname{PATH}. óÍ. ÏÂÓÕÖÄÅÎÉÅ ÎÁ +ÓÔÒÁÎÉÃÅ~\pageref{sec:env}. + + +\item óËÏÍÐÉÌÉÒÕÊÔÅ ÐÒÏÓÔÏÊ \LaTeX{}Ï×ÓËÉÊ ÆÁÊÌ: +\begin{alltt} +> \Ucom{latex sample2e.tex} +This is pdfeTeXk, Version 3.1415926... +... +Output written on sample2e.dvi (3 pages, 7484 bytes). +Transcript written on sample2e.log. +\end{alltt} +åÓÌÉ ÐÒÏÇÒÁÍÍÁ ÎÅ ÍÏÖÅÔ ÎÁÊÔÉ \filename{sample2e.tex} ÉÌÉ ÄÒÕÇÉÅ +ÆÁÊÌÙ, ×ÏÚÍÏÖÎÏ, Õ ×ÁÓ ÏÓÔÁÌÉÓØ ÓÌÅÄÙ ÏÔ ÓÔÁÒÏÊ ÕÓÔÁÎÏ×ËÉ: ÐÅÒÅÍÅÎÎÙÅ +ÏËÒÕÖÅÎÉÑ ÉÌÉ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÆÁÊÌÙ. íÙ ÒÅËÏÍÅÎÄÕÅÍ ÓÎÁÞÁÌÁ ÕÂÒÁÔØ +×ÓÅ ÐÅÒÅÍÅÎÎÙÅ ÏËÒÕÖÅÎÉÑ, ÏÔÎÏÓÑÝÉÅÓÑ Ë \TeX Õ. (äÌÑ ÏÔÌÁÄËÉ ×Ù ×ÓÅÇÄÁ ÍÏÖÅÔÅ +ÐÏÐÒÏÓÉÔØ \TeX{} ÔÏÞÎÏ ÓËÁÚÁÔØ, ÞÔÏ ÉÍÅÎÎÏ ÏÎ ÉÝÅÔ; ÓÍ. <<ïÔÌÁÄËÁ>> ÎÁ +ÓÔÒ.~\pageref{sec:debugging}.) + +\item ðÏÓÍÏÔÒÉÔÅ ÒÅÚÕÌØÔÁÔ ÎÁ ÜËÒÁÎÅ: +\begin{alltt} +> \Ucom{xdvi sample2e.dvi} +\end{alltt} +(ðÏÄ Windows ÁÎÁÌÏÇÉÞÎÁÑ ËÏÍÁÎÄÁ ÎÁÚÙ×ÁÅÔÓÑ \cmdname{dviout}.) ÷Ù ÄÏÌÖÎÙ +Õ×ÉÄÅÔØ ÎÏ×ÏÅ ÏËÎÏ Ó ËÒÁÓÉ×Ï Ó×£ÒÓÔÁÎÎÙÍ ÄÏËÕÍÅÎÔÏÍ, ÏÂßÑÓÎÑÀÝÉÍ ÏÓÎÏ×Ù +\LaTeX{}Á. (åÓÌÉ ×Ù "--- ÎÏ×ÉÞÏË, ×ÁÍ ÓÔ\'ÏÉÔ ÅÇÏ ÐÒÏÞÅÓÔØ.) þÔÏÂÙ +ÐÒÏÇÒÁÍÍÁ \cmdname{xdvi} ÍÏÇÌÁ ÚÁÐÕÓÔÉÔØÓÑ, ×Ù ÄÏÌÖÎÙ ÂÙÔØ × ÓÒÅÄÅ X Window; +ÅÓÌÉ ÜÔÏ ÎÅ ÔÁË, ÉÌÉ ÅÓÌÉ ÐÅÒÅÍÅÎÎÁÑ \envname{DISPLAY} ÕÓÔÁÎÏ×ÌÅÎÁ +ÎÅÐÒÁ×ÉÌØÎÏ, ×Ù Õ×ÉÄÉÔÅ ÏÛÉÂËÕ \samp{Can't open display}. + +\item óÏÚÄÁÊÔÅ ÆÁÊÌ × ÆÏÒÍÁÔÅ \PS{} ÄÌÑ ÐÅÞÁÔÉ ÉÌÉ ÐÒÏÓÍÏÔÒÁ ÎÁ ÜËÒÁÎÅ: +\begin{alltt} +> \Ucom{dvips sample2e.dvi -o sample2e.ps} +\end{alltt} + +\item óÏÚÄÁÊÔÅ ÆÁÊÌ × ÆÏÒÍÁÔÅ \acro{PDF} ×ÍÅÓÔÏ \dvi{}; ËÏÍÁÎÄÁ ÎÉÖÅ + ËÏÍÐÉÌÉÒÕÅÔ ÆÁÊÌ \filename{.tex} É ÓÏÚÄÁ£Ô \acro{PDF}: +\begin{alltt} +> \Ucom{pdflatex sample2e.tex} +\end{alltt} + +\item ðÏÓÍÏÔÒÉÔÅ ÒÅÚÕÌØÔÁÔ ÎÁ ÜËÒÁÎÅ: +\begin{alltt} +> \Ucom{gv sample2e.pdf} +\textrm{ÉÌÉ:} +> \Ucom{xpdf sample2e.pdf} +\end{alltt} +ë ÓÏÖÁÌÅÎÉÀ, ÎÉ \cmdname{gv}, ÎÉ \cmdname{xpdf} ÎÅ ×ËÌÀÞÅÎÙ × ÔÅËÕÝÕÀ +×ÅÒÓÉÀ \TL{}, ÔÁË ÞÔÏ ×ÁÍ ÐÒÉÄ£ÔÓÑ ÕÓÔÁÎÁ×ÌÉ×ÁÔØ ÉÈ +ÏÔÄÅÌØÎÏ. óÍ. ÓÏÏÔ×ÅÔÓÔ×ÅÎÎÏ +\url{http://www.gnu.org/software/gv} É +\url{http://www.foolabs.com/xpdf}. (òÁÚÕÍÅÅÔÓÑ, ÅÓÔØ É ÍÎÏÇÏ ÄÒÕÇÉÈ +ÐÒÏÇÒÁÍÍ ÄÌÑ ÐÒÏÓÔÍÏÔÒÁ ÆÁÊÌÏ× × ÆÏÒÍÁÔÅ \acro{PDF}). + +\item äÒÕÇÉÅ ÓÔÁÎÄÁÒÔÎÙÅ ÔÅÓÔÏ×ÙÅ ÆÁÊÌÙ, ËÏÔÏÒÙÅ ×ÁÍ ÍÏÇÕÔ ÐÒÉÇÏÄÉÔØÓÑ: + +\begin{ttdescription} +\item [small2e.tex] âÏÌÅÅ ÐÒÏÓÔÏÊ ÄÏËÕÍÅÎÔ, ÞÅÍ \filename{sample2e}, + ÕÄÏÂÎÙÊ, ÅÓÌÉ ÐÏÓÌÅÄÎÉÊ ÓÌÉÛËÏÍ ×ÅÌÉË ÄÌÑ ×ÁÓ. +\item [testpage.tex] ðÒÏ×ÅÒÑÅÔ ÐÏÌÑ É ÐÏÚÉÃÉÏÎÉÒÏ×ÁÎÉÅ ÂÕÍÁÇÉ ÄÌÑ + ×ÁÛÅÇÏ ÐÒÉÎÔÅÒÁ. +\item [nfssfont.tex] éÓÐÏÌØÚÕÅÔÓÑ ÄÌÑ ÐÅÞÁÔÉ ÔÁÂÌÉà ÛÒÉÆÔÏ× É ÔÅÓÔÏ×. +\item [testfont.tex] ðÅÞÁÔØ ÔÁÂÌÉà ÛÒÉÆÔÏ× ÐÏÄ plain \TeX{}. +\item [story.tex] óÁÍÙÊ ËÁÎÏÎÉÞÅÓËÉÊ ÆÁÊÌ × ÆÏÒÍÁÔÅ (plain) \TeX. ÷Ù + ÄÏÌÖÎÙ ÎÁÐÅÞÁÔÁÔØ \samp{\bs bye} × ÏÔ×ÅÔ ÎÁ ÐÒÉÇÌÁÛÅÎÉÅ \code{*} + ÐÏÓÌÅ \samp{tex story.tex}. +\end{ttdescription} +\end{enumerate} + + +åÓÌÉ ×Ù ÎÏ×ÉÞÏË × \TeX{}Å, ÉÌÉ ×ÁÍ ÎÕÖÎÁ ÐÏÍÏÝØ × ÓÏÚÄÁÎÉÉ ÄÏËÕÍÅÎÔÏ× +ÎÁ ÑÚÙËÅ \TeX{} ÉÌÉ \LaTeX{}, ÐÏÓÅÔÉÔÅ +\url{http://tug.org/begin.html}. + +\section{õÓÔÁÎÏ×ËÁ × ÌÏËÁÌØÎÏÊ ÓÅÔÉ} +\label{sec:netinstall} + +\TL{} ÍÏÖÅÔ ÉÓÐÏÌØÚÏ×ÁÔØÓÑ ÏÄÎÏ×ÒÅÍÅÎÎÏ ÒÁÚÎÙÍÉ ÐÏÌØÚÏ×ÁÔÅÌÑÍÉ ÉÌÉ +ÄÁÖÅ ÒÁÚÎÙÍÉ ÍÁÛÉÎÁÍÉ × ÌÏËÁÌØÎÏÊ ÓÅÔÉ. ÷ ÓÔÁÎÄÁÒÔÎÏÊ ÓÈÅÍÅ +ÄÉÒÅËÔÏÒÉÊ ×ÓÅ ÐÕÔÉ Ë ÆÁÊÌÁÍ Ñ×ÌÑÀÔÓÑ ÏÔÎÏÓÉÔÅÌØÎÙÍÉ: ÐÒÏÇÒÁÍÍÙ \TL{} +ÏÐÒÅÄÅÌÑÀÔ, ÇÄÅ ÌÅÖÁÔ ÎÕÖÎÙÅ ÉÍ ÆÁÊÌÙ, ÉÓÈÏÄÑ ÉÚ ÔÏÇÏ, ÇÄÅ ÏÎÉ +ÎÁÈÏÄÑÔÓÑ ÓÁÍÉ. ÷Ù ÍÏÖÅÔÅ Õ×ÉÄÅÔØ, ËÁË ÜÔÏ ÄÅÌÁÅÔÓÑ, ÐÏÓÍÏÔÒÅ× +ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ \filename{$TEXMFMAIN/web2c/texmf.cnf} ÓÏ +ÓÔÒÏÞËÁÍÉ ÔÉÐÁ +\begin{sverbatim} +TEXMFMAIN = $SELFAUTOPARENT/texmf +... +TEXMFLOCAL = $SELFAUTOPARENT/../texmf-local +\end{sverbatim} +üÔÏ ÏÚÎÁÞÁÅÔ, ÞÔÏ ÄÒÕÇÉÅ ÓÉÓÔÅÍÙ ÉÌÉ ÐÏÌØÚÏ×ÁÔÅÌÉ ÄÏÌÖÎÙ ÐÒÏÓÔÏ +ÄÏÂÁ×ÉÔØ ÄÉÒÅËÔÏÒÉÀ Ó ÐÒÏÇÒÁÍÍÁÍÉ \TL{} Ë ÄÉÒÅËÔÏÒÉÑÍ ÐÏÉÓËÁ. + +ôÏÞÎÏ ÔÁË ÖÅ ×Ù ÍÏÖÅÔÅ ÕÓÔÁÎÏ×ÉÔØ \TL{} ÎÁ ÏÄÉÎ ËÏÍÐØÀÔÅÒ, Á ÚÁÔÅÍ +ÐÅÒÅÎÅÓÔÉ ×ÓÀ ÉÅÒÁÒÈÉÀ ÎÁ ÌÏËÁÌØÎÕÀ ÓÅÔØ. + +òÁÚÕÍÅÅÔÓÑ, ÐÏÌØÚÏ×ÁÔÅÌÉ Windows ÐÒÉ×ÙËÌÉ Ë ÄÒÕÇÏÍÕ. ÷ ÄÉÒÅËÔÏÒÉÉ +\dirname{texmf-doc/source/texlive/texlive-common/w32client} ÎÁÈÏÄÉÔÓÑ +ÐÒÉÍÅÒ ÓËÒÉÐÔÁ \filename{install-w32client}, ËÏÔÏÒÙÊ ÓÏÚÄÁÅÔ ÎÁÓÔÒÏÊËÉ +É ÑÒÌÙËÉ ÄÌÑ ÓÕÝÅÓÔ×ÕÀÝÅÊ ÓÉÓÔÅÍÙ \TL{} × ÌÏËÁÌØÎÏÊ ÓÅÔÉ. åÇÏ ÍÏÖÎÏ +ÚÁÐÕÓÔÉÔØ ÉÚ ÆÁÊÌÁ \filename{install-w32client.bat}, ËÏÔÏÒÙÊ ÎÁÈÏÄÉÔÓÑ +× ÔÏÊ ÖÅ ÄÉÒÅËÔÏÒÉÉ. + +äÏÐÏÌÎÉÔÅÌØÎÁÑ ÉÎÆÏÒÍÁÃÉÑ Ï ËÏÎÆÉÇÕÒÁÃÉÉ \TL{} É ÐÏÉÓËÅ ÆÁÊÌÏ× +ÎÁÈÏÄÉÔÓÑ × ÒÁÚÄÅÌÅ~\ref{sec:kpathsea}. + +\section{íÁËÓÉÍÁÌØÎÏ ÐÅÒÅÎÏÓÉÍÁÑ ÓÉÓÔÅÍÁ \protect\TL{} ÎÁ DVD É USB} +\label{sec:portable-unix} + +÷ÁÒÉÁÎÔ <<ÒÁÂÏÔÙ Ó \DVD>>, ÏÐÉÓÁÎÎÙÊ × ÒÁÚÄÅÌÅ~\ref{sec:fromdvd}, +ÐÏÄÈÏÄÉÔ ÄÌÑ ×ÁÛÅÊ ÓÏÂÓÔ×ÅÎÎÏÊ ÓÉÓÔÅÍÙ, ÎÏ ÅÓÌÉ ×Ù "--- ÇÏÓÔØ ÎÁ +ÞØÅÍ-ÎÉÂÕÄØ ÞÕÖÏÍ ËÏÍÐØÀÔÅÒÅ, ×Ù ÚÁÈÏÔÉÔÅ ÓÄÅÌÁÔØ ÔÁË, ÞÔÏÂÙ ÐÏÓÌÅ ×ÁÓ +ÎÅ ÏÓÔÁ×ÁÌÏÓØ ÎÉËÁËÉÈ ÉÚÍÅÎÅÎÉÊ × ÓÉÓÔÅÍÅ. + +÷ ËÏÒÎÅ×ÏÊ ÄÉÒÅËÔÏÒÉÉ \DVD{} \TL{}, ÉÌÉ × ÄÉÒÅËÔÏÒÉÉ \dirname{texlive} +\DVD{} \TK{} ÎÁÈÏÄÉÔÓÑ ÓËÒÉÐÔ \filename{tl-portable} (àÎÉËÓ) É ÆÁÊÌ +\filename{tl-portable.bat} (Windows), ËÏÔÏÒÙÅ ÏÔËÒÙ×ÁÀÔ ÔÅÒÍÉÎÁÌ Ó +ÐÅÒÅÍÅÎÎÙÍÉ ÏËÒÕÖÅÎÉÑ, ÐÏÄÈÏÄÑÝÉÍÉ ÄÌÑ ÒÁÂÏÔÙ Ó \TL{} ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ +Ó \DVD{}. + +ëÏÇÄÁ ÜÔÁ ÐÒÏÇÒÁÍÍÁ ÚÁÐÕÓËÁÅÔÓÑ × ÐÅÒ×ÙÊ ÒÁÚ, ÏÎÁ ÓÏÚÄÁÅÔ ÎÅÓËÏÌØËÏ +ÆÁÊÌÏ× × ÄÉÒÅËÔÏÒÉÉ \dirname{~/.tlportable2008}, ÞÔÏ ÔÒÅÂÕÅÔ +ÎÅËÏÔÏÒÏÇÏ ×ÒÅÍÅÎÉ. ÷ÐÏÓÌÅÄÓÔ×ÉÉ ÏÎÁ ÚÁÐÕÓËÁÅÔÓÑ ÐÒÁËÔÉÞÅÓËÉ +ÍÇÎÏ×ÅÎÎÏ. + +ïÓÔÁÌØÎÁÑ ÓÉÓÔÅÍÁ ÎÅ ÂÕÄÅÔ ÎÉÞÅÇÏ ÚÎÁÔØ Ï \TL{}. åÓÌÉ ×Ù ÈÏÔÉÔÅ, +ÞÔÏÂÙ ×ÁÛ ÒÅÄÁËÔÏÒ ÚÎÁÌ Ï \TL{}, ÚÁÐÕÓÔÉÔÅ ÅÇÏ ÉÚ ÐÁÒÁÌÌÅÌØÎÏÊ ÓÅÓÓÉÉ +\filename{tl-portable}. + +÷Ù ÔÁËÖÅ ÍÏÖÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ \filename{tl-portable}, ÞÔÏÂÙ ÚÁÐÕÓËÁÔØ +\TL{} Ó ÆÌÅÛËÉ \acro{USB}. äÌÑ ÜÔÏÇÏ ÓËÏÐÉÒÕÊÔÅ ×ÓÅ ÆÁÊÌÙ × ËÏÒÎÅ×ÏÊ +ÄÉÒÅËÔÏÒÉÉ, Á ÔÁËÖÅ ÐÏ ËÒÁÊÎÅÊ ÍÅÒÅ ÓÏÄÅÒÖÉÍÏÅ \dirname{bin}, +\dirname{texmf}, \dirname{texmf-dist} É \dirname{tlpkg} ÎÁ ÆÌÅÛËÕ. +üÔÏ ÍÏÖÅÔ ÚÁÎÑÔØ ÍÎÏÇÏ ×ÒÅÍÅÎÉ! åÓÌÉ ×Ù ËÏÐÉÒÕÅÔÅ ÎÁ ÆÌÅÛËÕ × ÆÏÒÍÁÔÅ +\acro{FAT}32, ×Ù ÄÏÌÖÎÙÅ ÒÁÓËÒÙÔØ ÓÉÍÌÉÎËÉ (\code{cp -L}). åÓÌÉ ÎÁ +ÆÌÅÛËÅ ÅÓÔØ ÄÉÒÅËÔÏÒÉÑ \dirname{texmf-local}, ÏÎÁ ÂÕÄÅÔ ÎÁÊÄÅÎÁ É +ÉÓÐÏÌØÚÏ×ÁÎÁ. + +ðÏÓÌÅ ÜÔÏÇÏ ×Ù ÍÏÖÅÔÅ ÚÁÐÕÓËÁÔØ ÓËÒÉÐÔ \filename{tl-portable} ÉÚ +ËÏÒÎÅ×ÏÊ ÄÉÒÅËÔÏÒÉÉ ÆÌÅÛËÉ, ËÁË ÏÐÉÓÁÎÏ ×ÙÛÅ. ÷ ÜÔÏÍ ÓÌÕÞÁÅ ÓËÒÉÐÔ +ÐÏÊÍÅÔ, ÞÔÏ ÎÁ ÆÌÅÛËÕ ÍÏÖÎÏ ÐÉÓÁÔØ, É ÂÕÄÅÔ ÚÁÐÉÓÙ×ÁÔØ Á×ÔÏÍÁÔÉÞÅÓËÉ +ÓÏÚÄÁÎÎÙÅ ÆÁÊÌÙ ÔÕÄÁ. ÷Ù ÍÏÖÅÔÅ ÐÒÏÖÅÞØ \DVD{}, ÅÓÌÉ ÜÔÏ ÂÏÌÅÅ ÕÄÏÂÎÏ +(ÎÁÐÒÉÍÅÒ, ÞÔÏÂÙ ÐÏÄÅÌÉÔØÓÑ Ó ËÅÍ-ÎÉÂÕÄØ \TL{}). + +\section{áÄÍÉÎÉÓÔÒÉÒÏ×ÁÎÉÅ ÓÉÓÔÅÍÙ ÐÒÉ ÐÏÍÏÝÉ \cmdname{tlmgr}} +\label{sec:tlmgr} + +\begin{figure}[tb] +\tlpng{tlmgr-gui}{\linewidth} +\caption{\prog{tlmgr} × ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ. óÐÉÓÏË + ÐÁËÅÔÏ×/ËÏÌÌÅËÃÉÊ/ÓÈÅÍ ×ÉÄÅÎ ÔÏÌØËÏ ÐÏÓÌÅ ÎÁÖÁÔÉÑ ÎÁ ËÌÁ×ÉÛÕ + <>}\label{fig:tlmgr-gui} +\end{figure} + +\begin{figure}[tb] +\tlpng{tlmgr-config}{\linewidth} +\caption{\texttt{tlmgr} × ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ: ÍÅÎÀ + ËÏÎÆÉÇÕÒÁÃÉÉ}\label{fig:tlmgr-config} +\end{figure} + +\TL{} ÓÏÄÅÒÖÉÔ ÐÒÏÇÒÁÍÍÕ \prog{tlmgr} ÄÌÑ ÁÄÍÉÎÉÓÔÒÉÒÏ×ÁÎÉÑ ÓÉÓÔÅÍÙ +ÐÏÓÌÅ ÕÓÔÁÎÏ×ËÉ. ðÒÏÇÒÁÍÍÙ \prog{updmap}, \prog{fmtutil} É +\prog{texconfig} ×ÓÅ ÅÝ£ ÅÓÔØ × ÓÉÓÔÅÍÅ É ÂÕÄÕÔ ÔÁÍ × ÂÕÄÕÝÅÍ, ÎÏ +ÍÙ ÒÅËÏÍÅÎÄÕÅÍ ÔÅÐÅÒØ ÐÒÏÇÒÁÍÍÕ \prog{tlmgr}. óÒÅÄÉ Å£ ×ÏÚÍÏÖÎÏÓÔÅÊ: +\begin{itemize*} +\item ÐÏÄÄÅÒÖËÁ ÓÐÉÓËÏ× ÓÈÅÍ, ËÏÌÌÅËÃÉÊ É ÐÁËÅÔÏ×; +\item ÕÓÔÁÎÏ×ËÁ, ÏÂÎÏ×ÌÅÎÉÅ, ÁÒÈÉ×ÉÒÏ×ÁÎÉÅ, ×ÏÓÓÔÁÎÏ×ÌÅÎÉÅ É ÕÄÁÌÅÎÉÅ + ÏÔÄÅÌØÎÙÈ ÐÁËÅÔÏ×, ÐÒÉ ÖÅÌÁÎÉÉ Ó ÕÞÅÔÏÍ ÚÁ×ÉÓÉÍÏÓÔÅÊ ÍÅÖÄÕ ÎÉÍÉ; +\item ÐÏÉÓË ÐÁËÅÔÏ×; +\item ÄÏÂÁ×ÌÅÎÉÅ ÐÌÁÔÆÏÒÍ; +\item ÉÚÍÅÎÅÎÉÅ ÐÁÒÁÍÅÔÒÏ× ÓÉÓÔÅÍÙ, ÎÁÐÒÉÍÅÒ, ÒÁÚÍÅÒÁ ÂÕÍÁÇÉ É + ÉÓÔÏÞÎÉËÁ ÕÓÔÁÎÏ×ËÉ (ÓÍ. ÒÁÚÄÅÌ~\ref{sec:location}). +\end{itemize*} +\textit{÷ÎÉÍÁÎÉÅ:} \prog{tlmgr} ÎÅ ÐÒÅÄÎÁÚÎÁÞÅÎÁ ÄÌÑ ÚÁÐÕÓËÁ \TL{} Ó +\DVD{}, É ÎÅ ÔÅÓÔÉÒÏ×ÁÌÁÓØ × ÜÔÏÍ ÒÅÖÉÍÅ. + +\subsection{ðÒÏÇÒÁÍÍÁ \cmdname{tlmgr} × ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ} +ðÒÏÇÒÁÍÍÁ \prog{tlmgr} ÍÏÖÅÔ ÂÙÔØ ÚÁÐÕÝÅÎÁ × ÇÒÁÆÉÞÅÓËÏÍ ÒÅÖÉÍÅ: +\begin{alltt} +> \Ucom{tlmgr -gui} +\end{alltt} +ÉÌÉ ÎÁ Windows ÉÚ ÍÅÎÀ Start: \texttt{Start}, \texttt{Programs}, +\texttt{TeX Live 2008}, \texttt{TeX Live Manager}. ðÏÓÌÅ ÎÁÖÁÔÉÑ ÎÁ +ËÌÁ×ÉÛÕ <>, ÏÎÁ ÐÏËÁÚÙ×ÁÅÔ ÓÐÉÓÏË ÄÏÓÔÕÐÎÙÈ É ÕÓÔÁÎÏ×ÌÅÎÎÙÈ +ÐÁËÅÔÏ× "--- ÐÅÒÅÄ ÐÏÓÌÅÄÎÉÍÉ ÓÔÏÉÔ ÚÎÁÞÏË <<(i)>>. üÔÏ, ÒÁÚÕÍÅÅÔÓÑ, +ÐÒÏÉÓÈÏÄÉÔ ÐÒÉ ÕÓÌÏ×ÉÉ, ÞÔÏ ÉÓÔÏÞÎÉË ÕÓÔÁÎÏ×ËÉ ÄÏÓÔÕÐÅÎ. + +îÁ ÒÉÓÕÎËÅ~\ref{fig:tlmgr-config} ÐÏËÁÚÁÎÏ ÍÅÎÀ ËÏÎÆÉÇÕÒÁÃÉÉ. + +\subsection{úÁÐÕÓË ÐÒÏÇÒÁÍÍÙ \cmdname{tlmgr} ÉÚ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ} + +÷ ÐÒÉÍÅÒÅ ÎÉÖÅ ÍÙ ÄÏÂÁ×ÌÑÅÍ ÎÅÓËÏÌØËÏ ÐÁËÅÔÏ×, ×ËÌÀÞÁÑ ÎÏ×ÕÀ +ÐÒÏÇÒÁÍÍÕ, ÉÚ ÎÅÓÔÁÎÄÁÒÔÎÏÇÏ ÉÓÔÏÞÎÉËÁ: +\begin{alltt} +> \Ucom{tlmgr -location http://172.16.18.1/tldev install collection-xetex xkeyval} +\end{alltt} +óÉÓÔÅÍÁ ÏÔ×ÅÞÁÅÔ: +\begin{fverbatim} +install: collection-xetex +install: arabxetex +install: euenc +install: bidi +install: fontspec +install: fontwrap +install: ifxetex +install: philokalia +install: polyglossia +install: xecyr +install: xecyr.i386-linux +install: xepersian +install: xetex +install: xetexconfig +install: xetex.i386-linux +running post install action for xetex +install: xetex-def +install: xetex-pstricks +install: xetexfontinfo +install: xltxtra +install: xunicode +install: xkeyval +running mktexlsr +mktexlsr: Updating /usr/local/texlive/2008/texmf/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-config/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-dist/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-doc/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/../texmf-local/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-var/ls-R... +mktexlsr: Done. +regenerating fmtutil.cnf +running fmtutil-sys --missing +... +Transcript written on xelatex.log. +fmtutil: /usr/local/texlive/2008/texmf-var/web2c/xetex/xelatex.fmt installed. +\end{fverbatim} +ëÁË ×ÉÄÎÏ, \prog{tlmgr} ÕÓÔÁÎÁ×ÌÉ×ÁÅÔ ÚÁ×ÉÓÉÍÏÓÔÉ É ÐÒÉÚ×ÏÄÉÔ ×ÓÅ +ÎÕÖÎÙÅ ÐÏÓÌÅ ÕÓÔÁÎÏ×ËÉ ÄÅÊÓÔ×ÉÑ, ×ËÌÀÞÁÑ ÏÂÎÏ×ÌÅÎÉÅ ÂÁÚÙ ÄÁÎÎÙÈ ÆÁÊÌÏ× +É ÓÏÚÄÁÎÉÅ ÆÏÒÍÁÔÏ× (ÚÄÅÓØ ÓÏÚÄÁÎÙ ÆÏÒÍÁÔÙ ÄÌÑ \XeTeX Á). + +÷ ÓÌÅÄÕÀÝÅÍ ÐÒÉÍÅÒÅ ÍÙ ÄÏÂÁ×ÌÑÅÍ ÎÏ×ÙÊ ÑÚÙË. üÔÏ ÔÁËÖÅ ÐÒÉ×ÏÄÉÔ Ë +ÐÅÒÅÇÅÎÅÒÁÃÉÉ ÆÏÒÍÁÔÏ×: +\begin{alltt} +> \Ucom{tlmgr install collection-langdutch} +\end{alltt} +ïÐÉÓÁÎÉÅ ÐÁËÅÔÁ: +\begin{alltt} +> \Ucom{tlmgr show collection-wintools} +\end{alltt} +ÞÔÏ ×ÙÚÙ×ÁÅÔ ÓÌÅÄÕÀÝÉÊ ÏÔ×ÅÔ: +\begin{fverbatim} +Package: collection-wintools +Category: Collection +ShortDesc: Windows support programs +LongDesc: Utilities for Windows, since they are not readily available there: + gzip, chktex, jpeg2ps, unzip, wget, xpdf. +Installed: Yes +\end{fverbatim} +ïÂÎÏ×ÌÅÎÉÅ ×ÓÅÊ ÓÉÓÔÅÍÙ ÄÏ ÐÏÓÌÅÄÎÅÊ ×ÅÒÓÉÉ: +\begin{alltt} +> \Ucom{tlmgr update -all} +\end{alltt} +åÓÌÉ ×ÁÍ ÜÔÏ ËÁÖÅÔÓÑ ÓÔÒÁÛÎÏ×ÁÔÙÍ, ÐÏÐÒÏÂÕÊÔÅ ÓÎÁÞÁÌÁ +\begin{alltt} +> \Ucom{tlmgr update -all -dry-run} +\end{alltt} +ÉÌÉ +\begin{alltt} +> \Ucom{tlmgr update -list} +\end{alltt} +äÏËÕÍÅÎÔÁÃÉÑ: +\begin{alltt} +> \Ucom{tlmgr -help} +\end{alltt} + +\section{äÏÐÏÌÎÉÔÅÌØÎÙÅ ÚÁÍÅÞÁÎÉÑ Ï Windows} +\label{sec:windows} + +õ \TL{} ÏÂÝÁÑ ÐÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ, ËÏÔÏÒÁÑ ÒÁÂÏÔÁÅÔ É ÐÏÄ Windows, É +ÐÏÄ àÎÉËÓÏÍ. üÔÏ ÓÔÁÌÏ ×ÏÚÍÏÖÎÙÍ ÔÏÌØËÏ ÐÏÓÌÅ ÔÏÇÏ, ËÁË ÍÙ ÏÔËÁÚÁÌÉÓØ +ÏÔ ÐÏÄÄÅÒÖËÉ ÓÔÁÒÙÈ ×ÅÒÓÉÊ Windows, ÐÏÜÔÏÍÕ \TL{} ÔÅÐÅÒØ ÍÏÖÎÏ +ÕÓÔÁÎÏ×ÉÔØ ÔÏÌØËÏ ÎÁ Windows 2000 É ÍÌÁÄÛÅ. + +\subsection{äÏÐÏÌÎÉÔÅÌØÎÙÅ ×ÏÚÍÏÖÎÏÓÔÉ Windows} +\label{sec:winfeatures} + +ðÏÄ Windows ÐÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ ÄÅÌÁÅÔ ÎÅÓËÏÌØËÏ ÄÏÐÏÌÎÉÔÅÌØÎÙÈ ×ÅÝÅÊ: +\begin{description} +\item[íÅÎÀ É ÑÒÌÙËÉ.] õÓÔÁÎÁ×ÌÉ×ÁÅÔÓÑ ÐÏÄÍÅÎÀ <<\TL{}>> ÍÅÎÀ + <>, ËÏÔÏÒÏÅ ÓÏÄÅÒÖÉÔ ÎÅËÏÔÏÒÙÅ ÐÒÏÇÒÁÍÍÙ + (\prog{tlmgr}, \prog{texdoctk}, ÐÒÏÇÒÁÍÍÁ PS\_View ÄÌÑ ÐÒÏÓÍÏÔÒÁ + ÆÁÊÌÏ× × ÆÏÒÍÁÔÅ PostScript) É ÄÏËÕÍÅÎÔÁÃÉÀ. äÏÂÁ×ÌÑÅÔÓÑ ÑÒÌÙË + PS\_View ÎÁ ÄÅÓËÔÏÐÅ, ËÕÄÁ ÍÏÖÎÏ ÏÔÐÒÁ×ÌÑÔØ ÐÏÓÔÓËÒÉÐÔÏ×ÓËÉÅ ÆÁÊÌÙ. +\item[á×ÔÏÍÁÔÉÞÅÓËÁÑ ÕÓÔÁÎÏ×ËÁ ÐÅÒÅÍÅÎÎÙÈ ÏËÒÕÖÅÎÉÑ.] ÷ÓÅ ÐÅÒÅÍÅÎÎÙÅ + ÏËÒÕÖÅÎÉÑ ÕÓÔÁÎÁ×ÌÉ×ÁÀÔÓÑ Á×ÔÏÍÁÔÉÞÅÓËÉ. +\item[õÄÁÌÅÎÉÅ ÓÉÓÔÅÍÙ.] ðÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ ÓÏÚÄÁÅÔ × ÍÅÎÀ + <> ÚÁÐÉÓØ <<\TL{}>>. ëÌÁ×ÉÛÁ <<ÕÄÁÌÉÔØ>> × + ÍÅÎÀ \prog{tlmgr} ÏÔÎÏÓÉÔÓÑ Ë ÜÔÏÍÕ. +\end{description} + + + +\subsection{äÏÐÏÌÎÉÔÅÌØÎÙÅ ÐÁËÅÔÙ ÄÌÑ Windows} + +\begin{figure}[tb] +\tlpng{psview}{.6\linewidth} +\caption{PS\_View: ×ÏÚÍÏÖÎÏ ÏÞÅÎØ ÂÏÌØÛÏÅ Õ×ÅÌÉÞÅÎÉÅ!}\label{fig:psview} +\end{figure} + + +äÌÑ ÐÏÌÎÏÔÙ ÄÉÓÔÒÉÂÕÔÉ×Õ \TL ÎÅÏÂÈÏÄÉÍÙ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ÐÁËÅÔÙ, +ËÏÔÏÒÙÅ ÏÂÙÞÎÏ ÎÅ ×ÓÔÒÅÞÁÀÔÓÑ ÎÁ ÍÁÛÉÎÅ ÐÏÄ Windows. ÷ \TL{} ÅÓÔØ +ÎÅÄÏÓÔÁÀÝÉÅ ×ÅÝÉ: +\begin{description} +\item[Perl É Ghostscript.] ÷×ÉÄÕ ×ÁÖÎÏÓÔÉ ÜÔÉÈ ÐÒÏÇÒÁÍÍ, \TL{} + ×ËÌÀÞÁÅÔ ÉÈ <<ÓËÒÙÔÙÅ>> ËÏÐÉÉ. ðÒÏÇÒÁÍÍÙ \TL{}, ËÏÔÏÒÙÍ ÏÎÉ ÎÕÖÎÙ, + ÚÎÁÀÔ, ÇÄÅ ÉÈ ÎÁÊÔÉ, ÎÏ ÏÎÉ ÎÅ ×ÙÄÁÀÔ ÉÈ ÐÒÉÓÕÔÓÔ×ÉÑ ÓÉÓÔÅÍÅ ÞÅÒÅÚ + ÐÅÒÅÍÅÎÎÙÅ ÏËÒÕÖÅÎÉÑ ÉÌÉ ÒÅÇÉÓÔÒ. üÔÏ ÕÓÅÞÅÎÎÙÅ ×ÁÒÉÁÎÔÙ ÐÒÏÇÒÁÍÍ + Perl É Ghostscript, É ÏÎÉ ÎÅ ÄÏÌÖÎÙ ÚÁÍÅÝÁÔØ ÓÉÓÔÅÍÎÙÅ ×ÅÒÓÉÉ. +\item[õÔÉÌÉÔÙ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ.] ÷ÍÅÓÔÅ Ó ÐÒÏÇÒÁÍÍÁÍÉ \TL{} + ÕÓÔÁÎÁ×ÌÉ×ÁÅÔÓÑ ÒÑÄ ÐÏÒÔÉÒÏ×ÁÎÎÙÈ ÐÏÄ Windows ÓÔÁÎÄÁÒÔÎÙÈ + ÀÎÉËÓÏ×ÓËÉÈ ÕÔÉÌÉÔ: \cmdname{gzip}, \cmdname{chktex}, + \cmdname{jpeg2ps}, \cmdname{unzip}, \cmdname{wget} É ÐÒÏÇÒÁÍÍÙ ÉÚ + ÎÁÂÏÒÁ \cmdname{xpdf}. (óÁÍ \cmdname{xpdf} ÐÏÄ Windows ÎÅ ÒÁÂÏÔÁÅÔ, + ÎÏ ÎÁ ÎÅÍ ÏÓÎÏ×ÁÎÁ ÐÒÏÇÒÁÍÍÁ Sumatra: + \url{http://blog.kowalczyk.info/software/sumatrapdf}.) +\item[\texttt{fc-cache}] ÐÏÍÏÇÁÅÔ \XeTeX Õ ÜÆÆÅËÔÉ×ÎÏ ÒÁÂÏÔÁÔØ ÓÏ + ÛÒÉÆÔÁÍÉ. +\item[PS\_View.] ôÁËÖÅ ÕÓÔÁÎÁ×ÌÉ×ÁÅÔÓÑ PS\_View, ÎÏ×ÁÑ ÐÒÏÇÒÁÍÍÁ ÄÌÑ + ÐÒÏÓÍÏÔÒÁ ÆÁÊÌÏ× ÆÏÒÍÁÔÅ PostScript ÐÏÄ Ó×ÏÂÏÄÎÏÊ ÌÉÃÅÎÚÉÅÊ, + ÓÍ. ÒÉÓÕÎÏË~\ref{fig:psview}. +\end{description} +\begin{description} +\item[äÉÒÅËÔÏÒÉÑ \texttt{support},] ÕÖÅ ÕÐÏÍÑÎÕÔÁÑ × + ÒÁÚÄÅÌÅ~\ref{sec:tld}. ÷ ÜÔÏÊ ÄÉÒÅËÔÏÒÉÉ ÎÁÈÏÄÑÔÓÑ ÒÁÚÌÉÞÎÙÅ + ÐÒÏÇÒÁÍÍÙ, ËÏÔÏÒÙÅ ÍÏÇÕÔ ÂÙÔØ ÐÏÌÅÚÎÙ Ó \TeX ÏÍ, × ÞÁÓÔÎÏÓÔÉ, ÒÑÄ + ÕÄÏÂÎÙÈ ÒÅÄÁËÔÏÒÏ× É ÏÂÏÌÏÞÅË. ðÒÏÇÒÁÍÍÙ × ÜÔÏÊ ÄÉÒÅËÔÏÒÉÉ ÎÅ + ÕÓÔÁÎÁ×ÌÉ×ÁÀÔÓÑ Á×ÔÏÍÁÔÉÞÅÓËÉ. ÷ ÜÔÏÊ ÄÉÒÅËÔÏÒÉÉ ÔÁËÖÅ ÎÁÈÏÄÉÔÓÑ + ÐÒÏÇÒÁÍÍÁ ÄÌÑ ÐÒÏÓÍÏÔÒÁ \dvi{} "--- ÐÒÏÇÒÁÍÍÁ \cmdname{dviout}, ÏÐÉÓÁÎÎÁÑ × + ÓÌÅÄÕÀÝÅÍ ÒÁÚÄÅÌÅ. +\end{description} + +\subsection{ðÒÏÇÒÁÍÍÁ Dviout} + +ë ÓÏÖÁÌÅÎÉÀ, × ÜÔÏÊ ×ÅÒÓÉÉ \TL{} ÎÅÔ Á×ÔÏÍÁÔÉÞÅÓËÉ ÕÓÔÁÎÁ×ÌÉ×ÁÅÍÏÊ +ÐÒÏÇÒÁÍÍÙ ÄÌÑ ÐÒÏÓÍÏÔÒÁ \dvi{} ÄÌÑ Windows. ïÄÎÁËÏ ×Ù ÍÏÖÅÔÅ ÕÓÔÁÎÏ×ÉÔØ +ÐÒÏÇÒÁÍÍÕ ôÏÛÉÏ ïÛÉÍÙ \prog{dviout} ÉÚ ÄÉÒÅËÔÏÒÉÉ +\path{support/dviout/}. ÷ ÜÔÏÊ ÄÉÒÅËÔÏÒÉÉ ÅÓÔØ ÔÁËÖÅ ÎÅÂÏÌØÛÏÊ ÆÁÊÌ +\filename{README}, ÏÐÉÓÙ×ÁÀÝÉÊ ÕÓÔÁÎÏ×ËÕ É ËÏÎÆÉÇÕÒÁÃÉÀ \prog{dviout} +ÄÌÑ \TL{}. ÷ÎÉÍÁÔÅÌØÎÏ ÐÒÏÞÔÉÔÅ ÅÇÏ ÐÅÒÅÄ ÕÓÔÁÎÏ×ËÏÊ. + +ðÒÉ ÐÅÒ×ÏÍ ÚÁÐÕÓËÅ ÐÒÏÇÒÁÍÍÙ ÏÎÁ ÓÏÚÄÁÅÔ ÛÒÉÆÔÙ ÄÌÑ ÐÒÏÓÍÏÔÒÁ ÆÁÊÌÏ×. +åÓÌÉ ×Ù ÂÕÄÅÔÅ ÐÏÌØÚÏ×ÁÔØÓÑ ÅÊ ÎÅËÏÔÏÒÏÅ ×ÒÅÍÑ, ÏÎÁ ÓÏÚÄÁÓÔ +ÐÒÁËÔÉÞÅÓËÉ ×ÓÅ ÎÕÖÎÙÅ ×ÁÍ ÛÒÉÆÔÙ, É ÏËÎÏ ÓÏÚÄÁÎÉÑ ÛÒÉÆÔÏ× ÂÕÄÅÔ +ÐÏÑ×ÌÑÔØÓÑ ×ÓÅ ÒÅÖÅ. äÏÐÏÌÎÉÔÅÌØÎÁÑ ÉÎÆÏÒÍÁÃÉÑ Ï ÐÒÏÇÒÁÍÍÅ ÓÏÄÅÒÖÉÔÓÑ +× (ÏÞÅÎØ ÈÏÒÏÛÅÍ) ÍÅÎÀ ÐÏÍÏÝÉ. + +\subsection{óÓÙÌËÉ ÎÁ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ÐÒÏÇÒÁÍÍÙ} + +÷ÏÔ ÓÓÙÌËÉ ÎÁ ÎÅËÏÔÏÒÙÅ ÄÒÕÇÉÅ ÐÒÏÇÒÁÍÍÙ, ËÏÔÏÒÙÅ ×ÁÍ ÍÏÇÕÔ +ÐÏÎÒÁ×ÉÔØÓÑ: +\begin{description} +\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} +\item[Perl] \url{http://www.activestate.com/} Ó ÄÏÐÏÌÎÉÔÅÌØÎÙÍÉ + ÐÁËÅÔÁÍÉ ÉÚ ÁÒÈÉ×Á \acro{CPAN}, \url{http://www.cpan.org/} +\item[ImageMagick] \url{http://www.imagemagick.com}, ÄÌÑ + ËÏÎ×ÅÒÔÉÒÏ×ÁÎÉÑ É ÐÒÅÏÂÒÁÚÏ×ÁÎÉÑ ÇÒÁÆÉËÉ. +\item[NetPBM] \url{http://netpbm.sourceforge.net/}, ÔÏÖÅ ÄÌÑ ÇÒÁÆÉËÉ/ + +\item[òÅÄÁËÔÏÒÙ ÄÌÑ \TeX Á] éÈ ÏÞÅÎØ ÍÎÏÇÏ, É ×ÙÂÏÒ ÉÈ "--- ÄÅÌÏ + ×ËÕÓÁ. ÷ÏÔ ÎÅÓËÏÌØËÏ, × ÐÒÏÉÚ×ÏÌØÎÏÍ ÐÏÒÑÄËÅ: + \begin{itemize*} + \item \cmdname{GNU Emacs} ÅÓÔØ ÄÌÑ Windows, ÓÍ. + \url{http://www.gnu.org/software/emacs/windows/ntemacs.html}. + \item \cmdname{Emacs} Ó Auc\TeX ÏÍ ÄÌÑ Windows ÅÓÔØ × ÄÉÒÅËÔÏÒÉÉ + \path{support} ÎÁ \TL{}; ÅÇÏ ÓÔÒÁÎÉÃÁ ÎÁ ÓÅÔÉ: + \url{http://www.gnu.org/software/auctex}. + \item \cmdname{WinShell} ÅÓÔØ × ÄÉÒÅËÔÏÒÉÉ \path|support| ÎÁ \TL{}; + ÅÇÏ ÓÔÒÁÎÉÃÁ ÎÁ ÓÅÔÉ: \url{http://www.winshell.de}. + \item \cmdname{WinEdt} ÜÔÏ shareware, ËÏÔÏÒÏÅ ÍÏÖÎÏ ÓËÁÞÁÔØ Ó + \url{http://www.winedt.com}. + \item \cmdname{Vim} ÜÔÏ Ó×ÏÂÏÄÎÁÑ ÐÒÏÇÒÁÍÍÁ, ËÏÔÏÒÕÀ ÍÏÖÎÏ ÓËÁÞÁÔØ Ó + \url{http://www.vim.org}. + \item TeXnicCenter ÜÔÏ Ó×ÏÂÏÄÎÁÑ ÐÒÏÇÒÁÍÍÁ, ËÏÔÏÒÕÀ ÍÏÖÎÏ ÓËÁÞÁÔØ Ó + \url{http://www.toolscenter.org} É × ÄÉÓÔÒÉÂÕÔÉ×Å pro\TeX{}t. + \item \cmdname{LEd} ÍÏÖÎÏ ÓËÁÞÁÔØ Ó \url{http://www.ctan.org/support/LEd}. + \item \cmdname{SciTE} ÍÏÖÎÏ ÓËÁÞÁÔØ Ó + \url{http://www.scintilla.org/SciTE.html}. + \end{itemize*} +\end{description} + +\subsection{äÏÍÁÛÎÑÑ ÄÉÒÅËÔÏÒÉÑ ÐÏÄ Windows} +\label{sec:winhome} + +äÏÍÁÛÎÅÊ ÄÉÒÅËÔÏÒÉÉ ÐÏÄ àÎÉËÓÏÍ ÓÏÏÔ×ÅÔÓÔ×ÕÅÔ ÄÉÒÅËÔÏÒÉÑ +\verb|%USERPROFILE%|. ðÏÄ Windows XP É Windows 2000 ÜÔÏ ÏÂÙÞÎÏ +\verb|C:\Documents and Settings\|, Á ÐÏÄ Windows Vista "--- +\verb|C:\Users\|. ÷ ÆÁÊÌÅ \filename{texmf.cnf} É ×ÏÏÂÝÅ ÐÒÉ +ÒÁÂÏÔÅ \KPS{}, \verb|~| ÐÒÁ×ÉÌØÎÏ ÉÎÔÅÒÐÒÅÔÉÒÕÅÔÓÑ É ÐÏÄ Windows, É +ÐÏÄ àÎÉËÓÏÍ. + +\subsection{òÅÇÉÓÔÒ Windows} +\label{sec:registry} + +Windows ÈÒÁÎÉÔ ÐÏÞÔÉ ×ÓÅ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÄÁÎÎÙÅ × ÒÅÇÉÓÔÒÅ. òÅÇÉÓÔÒ +ÓÏÄÅÒÖÉÔ ÎÁÂÏÒ ÉÅÒÁÒÈÉÞÅÓËÉ ÏÒÇÁÎÉÚÏ×ÁÎÎÙÈ ÚÁÐÉÓÅÊ, Ó ÎÅÓËÏÌØËÉÍÉ +ËÏÒÎÅ×ÙÍÉ ÚÁÐÉÓÑÍÉ. îÁÉÂÏÌÅÅ ×ÁÖÎÙ ÄÌÑ ÐÒÏÇÒÁÍÍ ÕÓÔÁÎÏ×ËÉ ÚÁÐÉÓÉ +\path{HKEY_CURRENT_USER} É \path{HKEY_LOCAL_MACHINE}, ÓÏËÒÁÝÅÎÎÏ +\path{HKCU} É \path{HKLM}. ëÁË ÐÒÁ×ÉÌÏ, \path{HKCU} ÎÁÈÏÄÉÔÓÑ × +ÄÏÍÁÛÎÅÊ ÄÉÒÅËÔÏÒÉÉ ÐÏÌØÚÏ×ÁÔÅÌÑ (ÓÍ. ÒÁÚÄÅÌ~\ref{sec:winhome}), Á +\path{HKLM} "--- ÐÏÄÄÉÒÅËÔÏÒÉÑ ÄÉÒÅËÔÏÒÉÉ Windows. + +éÎÏÇÄÁ ËÏÎÆÉÇÕÒÁÃÉÑ ÓÉÓÔÅÍÙ ÏÐÒÅÄÅÌÑÅÔÓÑ ÐÅÒÅÍÅÎÎÙÍÉ ÏËÒÕÖÅÎÉÑ, ÎÏ +ÎÅËÏÔÏÒÙÅ ×ÅÝÉ (ÎÁÐÒÉÍÅÒ, ÐÏÌÏÖÅÎÉÅ ÑÒÌÙËÏ×) ÚÁÄÁÀÔÓÑ × ÒÅÇÉÓÔÒÅ. äÌÑ +ÔÏÇÏ, ÞÔÏÂÙ ÐÅÒÍÁÎÅÎÔÎÏ ÚÁÄÁÔØ ÐÅÒÅÍÅÎÎÙÅ ÏËÒÕÖÅÎÉÑ, ÔÁËÖÅ ÎÕÖÅÎ +ÄÏÓÔÕÐ Ë ÒÅÇÉÓÔÒÕ. + +\subsection{ðÒÁ×Á ÄÏÓÔÕÐÁ ÐÏÄ Windows} +\label{sec:winpermissions} + +÷ ÐÏÚÄÎÉÈ ×ÅÒÓÉÑÈ Windows ÄÅÌÁÅÔÓÑ ÒÁÚÌÉÞÉÅ ÍÅÖÄÕ ÏÂÙÞÎÙÍÉ +ÐÏÌØÚÏ×ÁÔÅÌÑÍÉ É ÁÄÍÉÎÉÓÔÒÁÔÏÒÁÍÉ, ÐÒÉÞÅÍ ÔÏÌØËÏ ÐÏÓÌÅÄÎÉÅ ÉÍÅÀÔ ÐÒÁ×Ï +ÄÏÓÔÕÐÁ ËÏ ×ÓÅÊ ÏÐÅÒÁÃÉÏÎÎÏÊ ÓÉÓÔÅÍÅ. îÁ ÐÒÁËÔÉËÅ ÏÄÎÁËÏ ÂÙÌÏ ÂÙ +ÂÏÌÅÅ ÐÒÁ×ÉÌØÎÏ ÏÐÉÓÙ×ÁÔØ ÜÔÉ ËÌÁÓÓÙ ÐÏÌØÚÏ×ÁÔÅÌÅÊ ËÁË +<<ÎÅÐÒÉ×ÉÌÅÇÉÒÏ×ÁÎÎÙÅ ÐÏÌØÚÏ×ÁÔÅÌÉ>> É <<ÏÂÙÞÎÙÅ ÐÏÌØÚÏ×ÁÔÅÌÉ>>: ÐÒÁ×Á +ÁÄÍÉÎÉÓÔÒÁÔÏÒÁ Ñ×ÌÑÀÔÓÑ ÐÒÁ×ÉÌÏÍ, Á ÎÅ ÉÓËÌÀÞÅÎÉÅÍ. ïÄÎÁËÏ ÍÙ +ÐÏÓÔÁÒÁÌÉÓØ ÓÄÅÌÁÔØ ×ÏÚÍÏÖÎÙÍ ÕÓÔÁÎÏ×ËÕ \TL{} ÂÅÚ ÐÒÁ× +ÁÄÍÉÎÉÓÔÒÁÔÏÒÁ. + +åÓÌÉ ÐÏÌØÚÏ×ÁÔÅÌØ Ñ×ÌÑÅÔÓÑ ÁÄÍÉÎÉÓÔÒÁÔÏÒÏÍ, ÑÒÌÙËÉ ÓÏÚÄÁÀÔÓÑ ÄÌÑ ×ÓÅÈ +ÐÏÌØÚÏ×ÁÔÅÌÅÊ, É ÍÏÄÉÆÉÃÉÒÕÀÔÓÑ ÓÉÓÔÅÍÎÙÅ ÐÁÒÁÍÅÔÒÙ. ÷ ÐÒÏÔÉ×ÎÏÍ +ÓÌÕÞÁÅ ÑÒÌÙËÉ É ÍÅÎÀ ÓÏÚÄÁÀÔÓÑ ÔÏÌØËÏ ÄÌÑ ÔÅËÕÝÅÇÏ ÐÏÌØÚÏ×ÁÔÅÌÑ, É +ÍÏÄÉÆÉÃÉÒÕÀÔÓÑ ÅÇÏ ÐÁÒÁÍÅÔÒÙ. åÓÌÉ ×Ù ÈÏÔÉÔÅ ÕÓÔÁÎÏ×ÉÔØ ÓÉÓÔÅÍÕ +ÔÏÌØËÏ ÄÌÑ ÏÄÎÏÇÏ ÐÏÌØÚÏ×ÁÔÅÌÑ, ÄÁÖÅ ÂÕÄÕÞÉ ÁÄÍÉÎÉÓÔÒÁÔÏÒÏÍ, +ÉÓÐÏÌØÚÕÊÔÅ ÏÐÃÉÀ \optname{non-admin} ÐÒÏÇÒÁÍÍÙ \prog{install-tl}. + +÷ÎÅ ÚÁ×ÉÓÉÍÏÓÔÉ ÏÔ ÓÔÁÔÕÓÁ ÐÏÌØÚÏ×ÁÔÅÌÑ, ËÏÒÅÎØ ÕÓÔÁÎÏ×ËÉ \TL{}, +ÐÒÅÄÌÁÇÁÅÍÙÊ ÐÏ ÕÍÏÌÞÁÎÉÀ, ×ÓÅÇÄÁ ÎÁÈÏÄÉÔÓÑ ÐÏÄ +\verb|%PROGRAMFILES%|. ðÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ ×ÓÅÇÄÁ ÐÒÏ×ÅÒÑÅÔ, ÏÔËÒÙÔÁ +ÌÉ ËÏÒÎÅ×ÁÑ ÄÉÒÅËÔÏÒÉÑ ÄÌÑ ÔÅËÕÝÅÇÏ ÐÏÌØÚÏ×ÁÔÅÌÑ. + +íÏÖÅÔ ×ÏÚÎÉËÎÕÔØ ÐÒÏÂÌÅÍÁ, ÅÓÌÉ Õ ÐÏÌØÚÏ×ÁÔÅÌÑ ÎÅÔ ÐÒÁ× +ÁÄÍÉÎÉÓÔÒÁÔÏÒÁ, Á × ÐÕÔÉ ÐÏÉÓËÁ ÕÖÅ ÅÓÔØ \TeX{}. ðÏÓËÏÌØËÕ × ÐÕÔÉ +ÐÏÉÓËÁ ÓÉÓÔÅÍÎÙÊ ÐÕÔØ ÓÔÏÉÔ ÐÅÒÅÄ ÐÕÔÅÍ ÐÏÌØÚÏ×ÁÔÅÌÑ, \TeX{} ÉÚ \TL{} +ÎÅ ÂÕÄÅÔ ÎÁÊÄÅÎ. þÔÏÂÙ ÏÂÏÊÔÉ ÜÔÕ ÐÒÏÂÌÅÍÕ, ÐÒÏÇÒÁÍÍÁ × ÔÁËÏÍ ÓÌÕÞÁÅ +ÓÏÚÄÁÅÔ ÑÒÌÙË Ó ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÏÊ, × ËÏÔÏÒÏÊ ÄÉÒÅËÔÏÒÉÑ \TL{} ÓÔÏÉÔ +ÐÅÒ×ÏÊ × ÐÕÔÉ ÐÏÉÓËÁ. éÚ ÜÔÏÊ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ ÍÏÖÎÏ ÐÏÌØÚÏ×ÁÔØÓÑ +\TL{}. + +\section{òÕËÏ×ÏÄÓÔ×Ï ÐÏÌØÚÏ×ÁÔÅÌÑ Web2C} + +\Webc{} "--- ÜÔÏ ÉÎÔÅÇÒÉÒÏ×ÁÎÎÁÑ ËÏÌÌÅËÃÉÑ ÐÒÏÇÒÁÍÍ, ÏÔÎÏÓÑÝÉÈÓÑ Ë +\TeX{}Õ: ÓÁÍ \TeX{}, \MF{}, \MP, \BibTeX{}, É Ô.Ä. üÔÏ ÓÅÒÄÃÅ +\TL{}. óÔÒÁÎÉÃÁ \Webc{} Ó ÒÕËÏ×ÏÄÓÔ×ÏÍ ÐÏÌØÚÏ×ÁÔÅÌÑ É ÍÎÏÇÉÍ ÄÒÕÇÉÍ +ÎÁÈÏÄÉÔÓÑ ÎÁ \url{http://tug.org/web2c}. + +îÅÍÎÏÇÏ ÉÓÔÏÒÉÉ. ðÅÒ×ÁÑ ×ÅÒÓÉÑ ÐÒÏÇÒÁÍÍÙ ÂÙÌÁ ÎÁÐÉÓÁÎÁ ôÏÍÁÓÏÍ +òÏËÉËÉ, ËÏÔÏÒÙÊ × 1987 ÇÏÄÕ ÓÏÚÄÁÌ ÓÉÓÔÅÍÕ \TeX{}-to-C, ÁÄÁÐÔÉÒÏ×Á× +ÐÁÔÞÉ ÄÌÑ àÎÉËÓÁ, ÒÁÚÒÁÂÏÔÁÎÎÙÅ × ÏÓÎÏ×ÎÏÍ çÏ×ÁÒÄÏÍ ôÒÉËÉ É ðÁ×ÌÏÍ +ëÕÒÔÉÓÏÍ. ôÉÍ íÏÒÇÁÎ ÓÔÁÌ ÐÏÄÄÅÒÖÉ×ÁÔØ ÓÉÓÔÅÍÕ, É × ÜÔÏÔ ÐÅÒÉÏÄ Å£ +ÎÁÚ×ÁÎÉÅ ÓÍÅÎÉÌÏÓØ ÎÁ Web-to-C\@. ÷ 1990 ÇÏÄÕ ëÁÒÌ âÅÒÒÉ ×ÚÑÌ ÎÁ ÓÅÂÑ +ÜÔÏÔ ÐÒÏÅËÔ, ËÏÏÒÄÉÎÉÒÕÑ ÒÁÂÏÔÕ ÄÅÓÑÔËÏ× ÐÒÏÇÒÁÍÍÉÓÔÏ×, Á × 1997 ÏÎ +ÐÅÒÅÄÁÌ ÒÕËÏ×ÏÄÓÔ×Ï ïÌÁÆÕ ÷ÅÂÅÒÕ. + +óÉÓÔÅÍÁ \Webc{} ÒÁÂÏÔÁÅÔ ÎÁ àÎÉËÓÅ, 32-ÂÉÔÏ×ÙÈ Windows, \MacOSX{}, É +ÄÒÕÇÉÈ ÏÐÅÒÁÃÉÏÎÎÙÈ ÓÉÓÔÅÍÁÈ. ïÎÁ ÉÓÐÏÌØÚÕÅÔ ÏÒÉÇÉÎÁÌØÎÙÅ ÉÓÈÏÄÎÉËÉ +ëÎÕÔÁ ÄÌÑ \TeX{}Á É ÄÒÕÇÉÈ ÐÒÏÇÒÁÍÍ, ÎÁÐÉÓÁÎÎÙÈ ÎÁ ÑÚÙËÅ \web{} É +ÐÅÒÅ×ÅÄ£ÎÎÙÈ ÎÁ C. ïÓÎÏ×ÎÙÅ ÐÒÏÇÒÁÍÍÙ ÓÉÓÔÅÍÙ: + +\begin{cmddescription} +\item[bibtex] ðÏÄÄÅÒÖËÁ ÂÉÂÌÉÏÇÒÁÆÉÊ. +\item[dmp] ðÅÒÅ×ÏÄ \cmdname{troff} × MPX (ËÁÒÔÉÎËÉ × \MP{}). +\item[dvicopy] òÁÓËÒÙÔÉÅ ×ÉÒÔÕÁÌØÎÙÅ ÛÒÉÆÔÙ × ÆÁÊÌÁÈ \dvi{}. +\item[dvitomp] ðÅÒÅ×ÏÄ \dvi{} × MPX (ÒÉÓÕÎËÉ × \MP{}). +\item[dvitype] ðÅÒÅ×ÏÄ \dvi{} × ÔÅËÓÔ. +\item[gftodvi] çÒÁÎËÉ ÛÒÉÆÔÏ×. +\item[gftopk] õÐÁËÏ×ËÁ ÛÒÉÆÔÏ× +\item[gftype] ðÅÒÅ×ÏÄ GF × ÔÅËÓÔ. +\item[makempx] ÷£ÒÓÔËÁ ÍÅÔÏË \MP{}. +\item[mf] óÏÚÄÁÎÉÅ ÛÒÉÆÔÏ×. +\item[mft] ÷£ÒÓÔËÁ ÉÓÈÏÄÎÉËÏ× \MF{}. +\item[mpost] óÏÚÄÁÎÉÅ ÔÅÈÎÉÞÅÓËÉÈ ÄÉÁÇÒÁÍÍ. +\item[mpto] éÚ×ÌÅÞÅÎÉÅ ÍÅÔÏË \MP{}. +\item[newer] óÒÁ×ÎÅÎÉÅ ÄÁÔ ÍÏÄÉÆÉËÁÃÉÉ. +\item[patgen] óÏÚÄÁÎÉÅ ÔÁÂÌÉà ÐÅÒÅÎÏÓÏ×. +\item[pktogf] ðÅÒÅ×ÏÄ PK × GF. +\item[pktype] ðÅÒÅ×ÏÄ PK × ÔÅËÓÔ +\item[pltotf] ðÅÒÅ×ÏÄ ÉÚ ÓÐÉÓËÁ Ó×ÏÊÓÔ× ÛÒÉÆÔÁ × TFM. +\item[pooltype] ðÏËÁÚ ÆÁÊÌÏ× pool × \web{}. +\item[tangle] ðÅÒÅ×ÏÄ \web{} × Pascal. +\item[tex] ÷£ÒÓÔËÁ. +\item[tftopl] ðÅÒÅ×ÏÄ TFM × ÓÐÉÓÏË Ó×ÏÊÓÔ× ÛÒÉÆÔÁ. +\item[vftovp] ðÅÒÅ×ÏÄ ×ÉÒÔÕÁÌØÎÏÇÏ ÛÒÉÆÔÁ × ÓÐÉÓÏË Ó×ÏÊÓÔ× ÛÒÉÆÔÁ. +\item[vptovf] ðÅÒÅ×ÏÄ ÓÐÉÓËÁ Ó×ÏÊÓÔ× ÛÒÉÆÔÁ × ×ÉÒÔÕÁÌØÎÙÊ ÛÒÉÆÔ. +\item[weave] ðÅÒÅ×ÏÄ \web{} × \TeX. +\end{cmddescription} + +\noindent ðÏÌÎÏÓÔØÀ ÜÔÉ ÐÒÏÇÒÁÍÍÙ ÏÐÉÓÁÎÙ × ÄÏËÕÍÅÎÔÁÃÉÉ Ë +ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÍ ÐÁËÅÔÁÍ É ÓÁÍÏÊ \Webc{}. ïÄÎÁËÏ ÚÎÁÎÉÅ ÎÅËÏÔÏÒÙÈ +ÏÂÝÉÈ ÐÒÉÎÃÉÐÏ× ÄÌÑ ×ÓÅÊ ÓÅÍØÉ ÐÒÏÇÒÁÍÍ ÐÏÍÏÖÅÔ ×ÁÍ ÐÏÌÎÅÅ +ÉÓÐÏÌØÚÏ×ÁÔØ ÐÒÏÇÒÁÍÍÙ ÓÉÓÔÅÍÙ \Webc{}. + +÷ÓÅ ÐÒÏÇÒÁÍÍÙ ÐÏÄÄÅÒÖÉ×ÁÀÔ ÓÔÁÎÄÁÒÔÎÙÅ ÏÐÃÉÉ \acro{GNU}: +\begin{ttdescription} +\item[-{}-help] ÎÁÐÅÞÁÔÁÔØ ËÒÁÔËÕÀ ÓÐÒÁ×ËÕ +\item[-{}-verbose] ÐÅÞÁÔÁÔØ ÐÏÄÒÏÂÎÕÀ ÉÎÆÏÒÍÁÃÉÀ ÐÏ ÍÅÒÅ ÒÁÂÏÔÙ +\item[-{}-version] îÁÐÅÞÁÔÁÔØ ×ÅÒÓÉÀ ÐÒÏÇÒÁÍÍÙ É ÚÁ×ÅÒÛÉÔØ ÒÁÂÏÔÕ. +\end{ttdescription} + +äÌÑ ÐÏÉÓËÁ ÆÁÊÌÏ× ÐÒÏÇÒÁÍÍÙ \Webc{} ÉÓÐÏÌØÚÕÀÔ ÂÉÂÌÉÏÔÅËÕ \KPS{} +(\url{http://tug.org/kpathsea}). üÔÁ ÂÉÂÌÉÏÔÅËÁ ÉÓÐÏÌØÚÕÅÔ ËÏÍÂÉÎÁÃÉÀ +ÐÅÒÅÍÅÎÎÙÈ ÏËÒÕÖÅÎÉÑ É ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÈ ÆÁÊÌÏ×, ÞÔÏÂÙ ÎÁÊÔÉ ÎÕÖÎÙÅ +ÆÁÊÌÙ × ÏÇÒÏÍÎÏÊ ÓÉÓÔÅÍÅ \TeX{}. \Webc{} ÍÏÖÅÔ ÐÒÏÓÍÁÔÒÉ×ÁÔØ +ÏÄÎÏ×ÒÅÍÅÎÎÏ ÂÏÌØÛÅ ÏÄÎÏÇÏ ÄÅÒÅ×Á ÄÉÒÅËÔÏÒÉÊ, ÞÔÏ ÐÏÌÅÚÎÏ ÄÌÑ ÒÁÂÏÔÙ +ÓÏ ÓÔÁÎÄÁÒÔÎÙÍ ÄÉÓÔÒÉÂÕÔÉ×ÏÍ \TeX{}Á É ÅÇÏ ÌÏËÁÌØÎÙÍÉ ÒÁÓÛÉÒÅÎÉÑÍÉ. +äÌÑ ÕÓËÏÒÅÎÉÑ ÐÏÉÓËÏ× ÆÁÊÌÏ× ËÁÖÄÏÅ ÄÅÒÅ×Ï ÓÏÄÅÒÖÉÔ ÆÁÊÌ \file{ls-R}, +× ËÏÔÏÒÏÍ ÕËÁÚÁÎÙ ÎÁÚ×ÁÎÉÑ É ÏÔÎÏÓÉÔÅÌØÎÙÅ ÐÕÔÉ ×ÓÅÈ ÆÁÊÌÏ× × ÜÔÏÍ +ÄÅÒÅ×Å. + +\subsection{ðÏÉÓË ÆÁÊÌÏ× × Kpathsea} +\label{sec:kpathsea} + +òÁÓÓÍÏÔÒÉÍ ÓÎÁÞÁÌÁ ÏÂÝÉÊ ÁÌÇÏÒÉÔÍ ÂÉÂÌÉÏÔÅËÉ \KPS. + +âÕÄÅÍ ÎÁÚÙ×ÁÔØ \emph{ÐÕÔ£Í ÐÏÉÓËÁ} ÎÁÂÏÒ ÒÁÚÄÅÌ£ÎÎÙÈ Ä×ÏÅÔÏÞÉÅÍ ÉÌÉ +ÔÏÞËÏÊ Ó ÚÁÐÑÔÏÊ \emph{ÜÌÅÍÅÎÔÏ× ÐÕÔÉ}, ÐÒÅÄÓÔÁ×ÌÑÀÝÉÈ ÉÚ ÓÅÂÑ × +ÏÓÎÏ×ÎÏÍ ÎÁÚ×ÁÎÉÑ ÄÉÒÅËÔÏÒÉÊ. ðÕÔØ ÐÏÉÓËÁ ÍÏÖÅÔ ÉÍÅÔØ ÍÎÏÇÏ +ÉÓÔÏÞÎÉËÏ×. þÔÏÂÙ ÎÁÊÔÉ ÆÁÊÌ \samp{my-file} × ÄÉÒÅËÔÏÒÉÉ +\samp{.:/dir}, \KPS{} ÐÒÏ×ÅÒÑÅÔ ËÁÖÄÙÊ ÜÌÅÍÅÎÔ ÐÕÔÉ ÐÏ ÏÞÅÒÅÄÉ: +ÓÎÁÞÁÌÁ \file{./my-file}, ÚÁÔÅÍ \file{/dir/my-file}, ×ÏÚ×ÒÁÝÁÑ ÐÅÒ×ÙÊ +ÆÁÊÌ (ÉÌÉ, ×ÏÚÍÏÖÎÏ, ×ÓÅ ÆÁÊÌÙ). + +þÔÏÂÙ ÒÁÂÏÔÁÔØ Ó ÒÁÚÎÙÍÉ ÏÐÅÒÁÃÉÏÎÎÙÍÉ ÓÉÓÔÅÍÁÍÉ, \KPS{} ÐÏÄ ÓÉÓÔÅÍÏÊ, +ÏÔÌÉÞÎÏÊ ÏÔ àÎÉËÓÁ ÍÏÖÅÔ ÉÓÐÏÌØÚÏ×ÁÔØ ÒÁÚÄÅÌÉÔÅÌÉ, ÏÔÌÉÞÎÙÅ ÏÔ +\samp{:} É \samp{/}. + +þÔÏÂÙ ÐÒÏ×ÅÒÉÔØ ÏÐÒÅÄÅÌ£ÎÎÙÊ ÜÌÅÍÅÎÔ ÐÕÔÉ \var{p}, \KPS{} ×ÎÁÞÁÌÅ +ÐÒÏ×ÅÒÑÅÔ ÎÁÌÉÞÉÅ ÂÁÚÙ ÄÁÎÎÙÈ (ÓÍ. ÒÁÚÄÅÌ <<âÁÚÁ ÄÁÎÎÙÈ +ÆÁÊÌÏ×>> ÎÁ ÓÔÒ.~\pageref{sec:filename-database}), Ô.Å., ÅÓÔØ ÌÉ ÂÁÚÁ × +ÄÉÒÅËÔÏÒÉÉ, ËÏÔÏÒÁÑ Ñ×ÌÑÅÔÓÑ ÐÒÅÆÉËÓÏÍ ÄÌÑ \var{p}. åÓÌÉ ÜÔÏ ÔÁË, +ÓÐÅÃÉÆÉËÁÃÉÑ ÐÕÔÉ ÓÒÁ×ÎÉ×ÁÅÔÓÑ Ó ÓÏÄÅÒÖÉÍÙÍ ÂÁÚÙ ÄÁÎÎÙÈ. + +åÓÌÉ ÂÁÚÁ ÄÁÎÎÙÈ ÎÅ ÓÕÝÅÓÔ×ÕÅÔ, ÉÌÉ ÎÅ ÏÔÎÏÓÉÔÓÑ Ë ÜÔÏÍÕ ÜÌÅÍÅÎÔÕ +ÐÕÔÉ, ÉÌÉ ÎÅ ÓÏÄÅÒÖÉÔ ÎÕÖÎÏÇÏ ÜÌÅÍÅÎÔÁ, ÐÒÏ×ÅÒÑÅÔÓÑ ÆÁÊÌÏ×ÁÑ ÓÉÓÔÅÍÁ +(ÅÓÌÉ ÜÔÏ ÎÅ ÚÁÐÒÅÝÅÎÏ ÓÐÅÃÉÆÉËÁÃÉÅÊ, ÎÁÞÉÎÁÀÝÅÊÓÑ Ó \samp{!!}, É ÅÓÌÉ +ÆÁÊÌ ÄÏÌÖÅÎ ÓÕÝÅÓÔ×Ï×ÁÔØ). \KPS{} ËÏÎÓÔÒÕÉÒÕÅÔ ÓÐÉÓÏË ÄÉÒÅËÔÏÒÉÊ, +ËÏÔÏÒÙÅ ÓÏÏÔ×ÅÔÓÔ×ÕÀÔ ÜÌÅÍÅÎÔÕ, É × ËÁÖÄÏÊ ÄÉÒÅËÔÏÒÉÉ ÉÝÅÔ ÎÕÖÎÙÊ +ÆÁÊÌ. + +õÓÌÏ×ÉÅ <<ÆÁÊÌ ÄÏÌÖÅÎ ÓÕÝÅÓÔ×Ï×ÁÔØ>> ×ÁÖÎÏ ÄÌÑ ÆÁÊÌÏ× \samp{.vf} É +ÆÁÊÌÏ×, ËÏÔÏÒÙÅ ÏÔËÒÙ×ÁÅÔ \TeX{} ÐÏ ËÏÍÁÎÄÅ \cs{openin}. ôÁËÉÅ ÆÁÊÌÙ +ÍÏÇÕÔ É ÎÅ ÓÕÝÅÓÔ×Ï×ÁÔØ (ÎÁÐÒÉÍÅÒ, ÆÁÊÌ \file{cmr10.vf}), É ÂÙÌÏ ÂÙ +ÎÅÐÒÁ×ÉÌØÎÏ ÉÓËÁÔØ ÉÈ ÎÁ ÄÉÓËÅ. ðÏÜÔÏÍÕ, ÅÓÌÉ ×Ù ÎÅ ÏÂÎÏ×ÉÔÅ +\file{ls-R} ÐÒÉ ÕÓÔÁÎÏ×ËÅ ÎÏ×ÏÇÏ ÆÁÊÌÁ \samp{.vf}, ÏÎ ÎÉËÏÇÄÁ ÎÅ ÂÕÄÅÔ +ÎÁÊÄÅÎ. ëÁÖÄÙÊ ÜÌÅÍÅÎÔ ÐÕÔÉ ÉÝÅÔÓÑ ÐÏ ÏÞÅÒÅÄÉ: ÓÎÁÞÁÌÁ ÂÁÚÁ ÄÁÎÎÙÈ, +ÚÁÔÅÍ ÄÉÓË. åÓÌÉ ÎÕÖÎÙÊ ÆÁÊÌ ÎÁÊÄÅÎ, ÐÏÉÓË ÏÓÔÁÎÁ×ÌÉ×ÁÅÔÓÑ, É +×ÏÚ×ÒÁÝÁÅÔÓÑ ÒÅÚÕÌØÔÁÔ. + +èÏÔÑ ÓÁÍÙÊ ÐÒÏÓÔÏÊ É ÞÁÓÔÏ ×ÓÔÒÅÞÁÀÝÉÊÓÑ ÜÌÅÍÅÎÔ ÐÕÔÉ "--- ÜÔÏ +ÎÁÚ×ÁÎÉÅ ÄÉÒÅËÔÏÒÉÉ, \KPS{} ÐÏÄÄÅÒÖÉ×ÁÅÔ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ×ÏÚÍÏÖÎÏÓÔÉ: +ÒÁÚÎÏÏÂÒÁÚÎÙÅ ÚÎÁÞÅÎÉÑ ÐÏ ÕÍÏÌÞÁÎÉÀ, ÉÍÅÎÁ ÐÅÒÅÍÅÎÎÙÈ ÏËÒÕÖÅÎÉÑ, +ÚÎÁÞÅÎÉÑ ÉÚ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÈ ÆÁÊÌÏ×, ÄÏÍÁÛÎÉÅ ÄÉÒÅËÔÏÒÉÉ +ÐÏÌØÚÏ×ÁÔÅÌÅÊ, ÒÅËÕÒÓÉ×ÎÙÊ ÐÏÉÓË ÐÏÄÄÉÒÅËÔÏÒÉÊ. ðÏÜÔÏÍÕ ÍÙ ÇÏ×ÏÒÉÍ, +ÞÔÏ \KPS{} \emph{×ÙÞÉÓÌÑÅÔ} ÜÌÅÍÅÎÔ ÐÕÔÉ, Ô.Å., ÞÔÏ ÂÉÂÌÉÏÔÅËÁ +ÐÒÅÏÂÒÁÚÕÅÔ ÓÐÅÃÉÆÉËÁÃÉÉ × ÉÍÑ ÉÌÉ ÉÍÅÎÁ ÄÉÒÅËÔÏÒÉÉ. üÔÏ ÏÐÉÓÁÎÏ × +ÓÌÅÄÕÀÝÉÈ ÒÁÚÄÅÌÁÈ × ÔÏÍ ÖÅ ÐÏÒÑÄËÅ, × ËÏÔÏÒÏÍ ÐÒÏÉÓÈÏÄÉÔ ÐÏÉÓË. + +úÁÍÅÔØÔÅ, ÞÔÏ ÉÍÑ ÆÁÊÌÁ ÐÒÉ ÐÏÉÓËÅ ÍÏÖÅÔ ÂÙÔØ ÁÂÓÏÌÀÔÎÙÍ ÉÌÉ +ÏÔÎÏÓÉÔÅÌØÎÙÍ, Ô.Å. ÎÁÞÉÎÁÔØÓÑ Ó \samp{/}, ÉÌÉ \samp{./}, ÉÌÉ +\samp{../}, \KPS{} ÐÒÏÓÔÏ ÐÒÏ×ÅÒÑÅÔ, ÓÕÝÅÓÔ×ÕÅÔ ÌÉ ÆÁÊÌ. + +\ifSingleColumn +\else +\begin{figure*} +\verbatiminput{examples/ex5.tex} +\setlength{\abovecaptionskip}{0pt} + \caption{ðÒÉÍÅÒ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÏÇÏ ÆÁÊÌÁ} + \label{fig:config-sample} +\end{figure*} +\fi + +\subsubsection{éÓÔÏÞÎÉËÉ ÐÕÔÅÊ ÐÏÉÓËÁ} +\label{sec:path-sources} + +ðÕÔØ ÐÏÉÓËÁ ÍÏÖÅÔ ÉÍÅÔØ ÒÁÚÎÙÅ ÉÓÔÏÞÎÉËÉ. \KPS{} ÉÓÐÏÌØÚÕÅÔ ÉÈ × +ÓÌÅÄÕÀÝÅÍ ÐÏÒÑÄËÅ: + +\begin{enumerate} +\item õÓÔÁÎÏ×ÌÅÎÎÙÅ ÐÏÌØÚÏ×ÁÔÅÌÅÍ ÐÅÒÅÍÅÎÎÙÅ ÏËÒÕÖÅÎÉÑ, ÎÁÐÒÉÍÅÒ + \envname{TEXINPUTS}\@. ðÅÒÅÍÅÎÎÙÅ ÏËÒÕÖÅÎÉÑ Ó ÔÏÞËÏÊ É ÎÁÚ×ÁÎÉÅÍ + ÐÒÏÇÒÁÍÍÙ ÉÍÅÀÔ ÐÒÅÉÍÕÝÅÓÔ×Ï; ÎÁÐÒÉÍÅÒ ÅÓÌÉ \samp{latex} "--- ÉÍÑ + ÐÒÏÇÒÁÍÍÙ. ÔÏ \envname{TEXINPUTS.latex} ÉÍÅÅÔ ÐÒÅÉÍÕÝÅÓÔ×Ï ÐÅÒÅÄ + \envname{TEXINPUTS}. +\item + ëÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ, ÓÐÅÃÉÆÉÞÅÓËÉÊ ÄÌÑ ÄÁÎÎÏÊ ÐÒÏÇÒÁÍÍÙ, ÎÁÐÒÉÍÅÒ, + ÓÔÒÏËÁ + \samp{S /a:/b} × \file{config.ps} ÄÌÑ \cmdname{dvips}. +\item + ëÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ \KPS{} \file{texmf.cnf}, ÓÏÄÅÒÖÁÝÉÊ ÓÔÒÏËÕ + ÔÉÐÁ + \samp{TEXINPUTS=/c:/d} (ÓÍ. ÎÉÖÅ). +\item úÎÁÞÅÎÉÅ, ÚÁÄÁÎÎÏÅ ÐÒÉ ËÏÍÐÉÌÑÃÉÉ. +\end{enumerate} +\noindent ÷Ù ÍÏÖÅÔÅ Õ×ÉÄÅÔØ ËÁÖÄÏÅ ÉÚ ÜÔÉÈ ÚÎÁÞÅÎÉÊ ÄÌÑ ÄÁÎÎÏÇÏ ÐÕÔÉ +ÐÏÉÓËÁ, ÚÁÄÁ× ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÊ ÕÒÏ×ÅÎØ ÏÔÌÁÄËÉ (ÓÍ. <<ïÔÌÁÄËÁ>> +ÎÁ ÓÔÒ.~\pageref{sec:debugging}). + +\subsubsection{ëÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÆÁÊÌÙ} + +\begingroup\tolerance=3500 +\KPS{} ÞÉÔÁÅÔ \emph{ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÆÁÊÌÙ} +\file{texmf.cnf} ÄÌÑ ÚÁÄÁÎÉÑ Ó×ÏÉÈ ÐÁÒÁÍÅÔÒÏ×. ðÕÔØ ÐÏÉÓËÁ ÄÌÑ ÜÔÉÈ +ÆÁÊÌÏ× ÎÁÚÙ×ÁÅÔÓÑ \envname{TEXMFCNF} (ÐÏ ÕÍÏÌÞÁÎÉÀ, ÔÁËÏÊ ÆÁÊÌ +ÎÁÈÏÄÉÔÓÑ × ÐÏÄÄÉÒÅËÔÏÒÉÉ \file{texmf/web2c}). \emph{÷ÓÅ} ÎÁÊÄÅÎÎÙÅ +ÆÁÊÌÙ \file{texmf.cnf} ÂÕÄÕÔ ÐÒÏÞÉÔÁÎÙ, É ÏÐÒÅÄÅÌÅÎÉÑ × ÂÏÌÅÅ ÒÁÎÎÉÈ +ÆÁÊÌÁÈ ÉÍÅÀÔ ÐÒÅÉÍÕÝÅÓÔ×Ï ÐÅÒÅÄ ÏÐÒÅÄÅÌÅÎÉÑÍÉ × ÂÏÌÅÅ ÐÏÚÄÎÉÈ. ôÁËÉÍ +ÏÂÒÁÚÏÍ, ÅÓÌÉ ÐÕÔØ ÐÏÉÓËÁ ÚÁÄÁÎ ËÁË \verb|.:$TEXMF|, ÚÎÁÞÅÎÉÑ × +\file{./texmf.cnf} ÉÍÅÀÔ ÐÒÅÉÍÕÝÅÓÔ×Ï ÐÅÒÅÄ ÚÎÁÞÅÎÉÑÍÉ × +\verb|$TEXMF/texmf.cnf|. +\endgroup + +\begin{itemize} +\item + ëÏÍÍÅÎÔÁÒÉÉ ÎÁÞÉÎÁÀÔÓÑ Ó \code{\%} É ÐÒÏÄÏÌÖÁÀÔÓÑ ÄÏ ËÏÎÃÁ ÓÔÒÏËÉ. +\item + ðÕÓÔÙÅ ÓÔÒÏËÉ ÉÇÎÏÒÉÒÕÀÔÓÑ +\item + \bs{} × ËÏÎÃÅ ÓÔÒÏËÉ ÏÚÎÁÞÁÅÔ ÐÒÏÄÏÌÖÅÎÉÅ, Ô.Å. ÄÏÂÁ×ÌÑÅÔÓÑ + ÓÌÅÄÕÀÝÁÑ ÓÔÒÏËÁ. ðÒÏÂÅÌÙ × ÎÁÞÁÌÅ ÓÌÅÄÕÀÝÅÊ ÓÔÒÏËÉ ÎÅ + ÉÇÎÏÒÉÒÕÀÔÓÑ. +\item + ïÓÔÁ×ÛÉÅÓÑ ÓÔÒÏËÉ ÉÍÅÀÔ ×ÉÄ +\begin{alltt} + \emph{variable}[.\emph{progname}] [=] \emph{value} +\end{alltt}% + ÇÄÅ \samp{=} É ÐÒÏÂÅÌÙ ×ÏËÒÕÇ ÍÏÇÕÔ ÏÐÕÓËÁÔØÓÑ. +\item + \ttvar{variable} ÍÏÖÅÔ ÓÏÄÅÒÖÁÔØ ÌÀÂÙÅ ÓÉÍ×ÏÌÙ, ËÒÏÍÅ ÐÒÏÂÅÌÁ, + \samp{=} ÉÌÉ \samp{.}, ÎÏ ÎÁÄ£ÖÎÅÅ ×ÓÅÇÏ ÐÒÉÄÅÒÖÉ×ÁÔØÓÑ ÎÁÂÏÒÁ + \samp{A-Za-z\_}. +\item + åÓÌÉ ÅÓÔØ \samp{.\var{progname}}, ÏÐÒÅÄÅÌÅÎÉÅ ÏÔÎÏÓÉÔÓÑ ÔÏÌØËÏ Ë + ÐÒÏÇÒÁÍÍÅ, ËÏÔÏÒÁÑ ÎÁÚÙ×ÁÅÔÓÑ + \texttt{\var{progname}} ÉÌÉ \texttt{\var{progname}.exe}. üÔÏ + ÐÏÚ×ÏÌÑÅÔ, ÎÁÐÒÉÍÅÒ ÒÁÚÎÙÍ ×ÉÄÁÍ \TeX{}Á ÉÍÅÔØ ÒÁÚÎÙÅ ÐÕÔÉ ÐÏÉÓËÁ. +\item \var{value} ÍÏÖÅÔ ÓÏÄÅÒÖÁÔØ ÌÀÂÙÅ ÓÉÍ×ÏÌÙ, ËÒÏÍÅ + \code{\%} É \samp{@}. îÅÌØÚÑ ÉÓÐÏÌØÚÏ×ÁÔØ + \code{\$\var{var}.\var{prog}} × ÐÒÁ×ÏÊ ÞÁÓÔÉ; ×ÍÅÓÔÏ ÜÔÏÇÏ ×Ù ÄÏÌÖÎÙ + ÚÁÄÁÔØ ÄÏÐÏÌÎÉÔÅÌØÎÕÀ ÐÅÒÅÍÅÎÎÕÀ. + \samp{;} × \samp{:} ÐÏÄ àÎÉËÓÏÍ ÜË×É×ÁÌÅÎÔÎÏ \samp{:}; ÜÔÏ + ÐÏÌÅÚÎÏ, ÞÔÏÂÙ ÐÏÄÄÅÒÖÉ×ÁÔØ ÏÂÝÉÊ ÆÁÊÌ ÄÌÑ àÎÉËÓÁ, \acro{MS-DOS} É + Windows. +\item + ÷ÓÅ ÏÐÒÅÄÅÌÅÎÉÑ ÞÉÔÁÀÔÓÑ ÄÏ ÐÏÄÓÔÁÎÏ×ÏË, ÐÏÜÔÏÍÕ Ë ÐÅÒÅÍÅÎÎÙÍ ÍÏÖÎÏ + ÏÂÒÁÝÁÔØÓÑ ÄÏ ÔÏÇÏ, ËÁË ÏÎÉ ÏÐÒÅÄÅÌÅÎÙ. +\end{itemize} +æÒÁÇÍÅÎÔ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÏÇÏ ÆÁÊÌÁ, ÉÌÌÀÓÔÒÉÒÕÀÝÉÊ ÜÔÉ ÐÒÁ×ÉÌÁ, ÐÒÉ×ÅÄeÎ +\ifSingleColumn +ÎÉÖÅ: + +\verbatiminput{examples/ex5.tex} +\else +ÐÒÉ×ÅÄeÎ ÎÁ òÉÓ.~\ref{fig:config-sample}. +\fi + +\subsubsection{ðÏÄÓÔÁÎÏ×ËÁ ÐÕÔÅÊ} +\label{sec:path-expansion} + + +\KPS{} ÒÁÓÐÏÚÎÁ£Ô ÏÐÒÅÄÅÌ£ÎÎÙÅ ÓÐÅÃÉÁÌØÎÙÅ ÓÉÍ×ÏÌÙ É ËÏÎÓÔÒÕËÃÉÉ × +ÐÕÔÑÈ ÐÏÉÓËÁ, ÁÎÁÌÏÇÉÞÎÙÅ ËÏÎÓÔÒÕËÃÉÑÍ × ÓÔÁÎÄÁÒÔÎÙÈ ÏÂÏÌÏÞËÁÈ +àÎÉËÓÁ. îÁÐÒÉÍÅÒ, ÓÌÏÖÎÙÊ ÐÕÔØ +\verb+~$USER/{foo,bar}//baz+, ÏÚÎÁÞÁÅÔ ×ÓÅ ÐÏÄÄÉÒÅËÔÏÒÉÉ ÄÉÒÅËÔÏÒÉÊ +\file{foo} É \file{bar} × ÄÏÍÁÛÎÅÊ ÄÉÒÅËÔÏÒÉÉ ÐÏÌØÚÏ×ÁÔÅÌÑ +\texttt{\$USER}, ËÏÔÏÒÙÅ ÓÏÄÅÒÖÁÔ ÆÁÊÌ ÉÌÉ ÐÏÄÄÉÒÅËÔÏÒÉÀ \file{baz}. +üÔÏ ÏÂßÑÓÎÅÎÏ × ÓÌÅÄÕÀÝÉÈ ÒÁÚÄÅÌÁÈ. + +%$ +\subsubsection{ðÏÄÓÔÁÎÏ×ËÁ ÐÏ ÕÍÏÌÞÁÎÉÀ} +\label{sec:default-expansion} + +\tolerance=2500 + +åÓÌÉ ÐÕÔØ ÐÏÉÓËÁ Ó ÎÁÉÂÏÌØÛÉÍ ÐÒÉÏÒÉÔÅÔÏÍ (ÓÍ. ÒÁÚÄÅÌ <<éÓÔÏÞÎÉËÉ ÐÕÔÅÊ +ÐÏÉÓËÁ>> ÎÁ ÓÔÒ.~\pageref{sec:path-sources}) ÓÏÄÅÒÖÉÔ \emph{ÄÏÐÏÌÎÉÔÅÌØÎÏÅ + Ä×ÏÅÔÏÞÉÅ} (× ÎÁÞÁÌÅ, × ËÏÎÃÅ, Ä×ÏÊÎÏÅ), \KPS{} ÚÁÍÅÎÑÅÔ ÅÇÏ +ÓÌÅÄÕÀÝÉÍ ÐÏ ÐÒÉÏÒÉÔÅÔÕ ÐÕÔ£Í. åÓÌÉ ÜÔÏÔ ×ÓÔÁ×ÌÅÎÎÙÊ ÐÕÔØ ÓÏÄÅÒÖÉÔ +ÄÏÐÏÌÎÉÔÅÌØÎÏÅ Ä×ÏÅÔÏÞÉÅ, ÔÏ ÖÅ ÐÒÏÉÓÈÏÄÉÔ ÓÏ ÓÌÅÄÕÀÝÉÍ ÐÕÔ£Í. +îÁÐÒÉÍÅÒ, ÅÓÌÉ ÐÅÒÅÍÅÎÎÁÑ ÏËÒÕÖÅÎÉÑ ÚÁÄÁÎÁ ËÁË + +\tolerance=1500 + +\begin{alltt} +> \Ucom{setenv TEXINPUTS /home/karl:} +\end{alltt} +É \code{TEXINPUTS} × ÆÁÊÌÅ \file{texmf.cnf} ÓÏÄÅÒÖÉÔ + +\begin{alltt} + .:\$TEXMF//tex +\end{alltt} +ÔÏ ÐÏÉÓË ÂÕÄÅÔ ÐÒÏÉÓÈÏÄÉÔØ Ó ÐÕÔ£Í + +\begin{alltt} + /home/karl:.:\$TEXMF//tex +\end{alltt} + +ðÏÓËÏÌØËÕ ÂÙÌÏ ÂÙ ÂÅÓÐÏÌÅÚÎÏ ×ÓÔÁ×ÌÑÔØ ÚÎÁÞÅÎÉÅ ÐÏ ÕÍÏÌÞÁÎÉÀ ÂÏÌÅÅ ÞÅÍ +ÏÄÉÎ ÒÁÚ, \KPS{} ÉÚÍÅÎÑÅÔ ÔÏÌØËÏ ÏÄÎÏ ÌÉÛÎÅÅ Ä×ÏÅÔÏÞÉÅ, É ÏÓÔÁ×ÌÑÅÔ +ÏÓÔÁÌØÎÙÅ: ÏÎÁ ÐÒÏ×ÅÒÑÅÔ ÓÎÁÞÁÌÁ Ä×ÏÅÔÏÞÉÅ × ÎÁÞÁÌÅ, ÐÏÔÏÍ × ËÏÎÃÅ, +ÐÏÔÏÍ Ä×ÏÊÎÙÅ Ä×ÏÅÔÏÞÉÑ. + +\subsubsection{ðÏÄÓÔÁÎÏ×ËÁ ÓËÏÂÏË} + +ðÏÌÅÚÎÁ ÔÁËÖÅ ÐÏÄÓÔÁÎÏ×ËÁ ÓËÏÂÏË, ÉÚ-ÚÁ ËÏÔÏÒÏÊ, ÎÁÐÒÉÍÅÒ, +\verb+v{a,b}w+ ÏÚÎÁÞÁÅÔ \verb+vaw:vbw+. ÷ÌÏÖÅÎÎÏÓÔØ ÔÕÔ ÄÏÐÕÓËÁÅÔÓÑ. +âÌÁÇÏÄÁÒÑ ÜÔÏÍÕ ÍÏÖÎÏ ÉÍÅÔØ ÎÅÓËÏÌØËÏ ÉÅÒÁÒÈÉÊ ÄÉÒÅËÔÏÒÉÊ, ÐÕÔ£Í +ÐÒÉÓ×ÏÅÎÉÑ ÚÎÁÞÅÎÉÑ ÓÏ ÓËÏÂËÁÍÉ \code{\$TEXMF}. +îÁÐÒÉÍÅÒ, × ÆÁÊÌÅ \file{texmf.cnf}, ÍÏÖÎÏ ÎÁÊÔÉ ÓÌÅÄÕÀÝÅÅ ÏÐÒÅÄÅÌÅÎÉÅ +(ÜÔÏ ÕÐÒÏÝÅÎÉÅ, ÎÁ ÓÁÍÏÍ ÄÅÌÅ ÔÁÍ ÅÝ£ ÂÏÌØÛÅ ÄÅÒÅ×ØÅ×): +\begin{verbatim} + TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN} +\end{verbatim} +âÌÁÇÏÄÁÒÑ ÜÔÏÍÕ ÍÏÖÎÏ ÐÉÓÁÔØ ÔÁËÏÅ: +\begin{verbatim} + TEXINPUTS = .;$TEXMF/tex// +\end{verbatim} +%$ +ÞÔÏ ÏÚÎÁÞÁÅÔ, ÞÔÏ ËÒÏÍÅ ÔÅËÕÝÅÊ ÄÉÒÅËÔÏÒÉÉ ÂÕÄÅÔ ÐÒÏÉÓÈÏÄÉÔØ ÐÏÉÓË +\emph{ÔÏÌØËÏ} × \code{\$TEXMFHOME/tex}, \code{\$TEXMFLOCAL/tex}, +\code{\$TEXMFVAR/tex} É \code{\$TEXMFMAIN/tex} (ÐÏÓÌÅÄÎÉÅ Ä×Á ÄÅÒÅ×Á +ÉÓÐÏÌØÚÕÀÔ ÆÁÊÌÙ \file{ls-R}). üÔÏ ÕÄÏÂÎÏ ÄÌÑ ÐÏÄÄÅÒÖËÉ Ä×ÕÈ +ÐÁÒÁÌÌÅÌØÎÙÈ ÓÔÒÕËÔÕÒ, <<ÚÁÍÏÒÏÖÅÎÎÏÊ>> (ÎÁÐÒÉÍÅÒ, ÎÁ \CD) É +ÏÂÎÏ×ÌÑÅÍÏÊ ÐÏ ÍÅÒÅ ÐÏÑ×ÌÅÎÉÑ ÎÏ×ÙÈ ×ÅÒÓÉÊ. éÓÐÏÌØÚÕÑ ÐÅÒÅÍÅÎÎÕÀ +\code{\$TEXMF} ×Ï ×ÓÅÈ ÏÐÒÅÄÅÌÅÎÉÑÈ, ÍÏÖÎÏ ÚÁÄÁÔØ ÐÏÉÓË × ÏÂÎÏ×ÌÑÅÍÏÍ +ÄÅÒÅ×Å ÐÅÒ×ÙÍ. + +\subsubsection{ðÏÄÓÔÁÎÏ×ËÁ ÐÏÄÄÉÒÅËÔÏÒÉÊ} +\label{sec:subdirectory-expansion} + +ä×Á ÉÌÉ ÂÏÌÅÅ ÓÌÜÛÁ \samp{/} × ÜÌÅÍÅÎÔÅ ÐÕÔÉ ×ÓÌÅÄ ÚÁ ÉÍÅÎÅÍ ÄÉÒÅËÔÏÒÉÉ +\var{d} ÚÁÍÅÎÑÀÔÓÑ ×ÓÅÍÉ ÐÏÄÄÉÒÅËÔÏÒÉÑÍÉ \var{d} ÒÅËÕÒÓÉ×ÎÏ. îÁ ËÁÖÄÏÍ +ÕÒÏ×ÎÅ ÐÏÒÑÄÏË ÐÏÉÓËÁ ÐÏ ÄÉÒÅËÔÏÒÉÑÍ \emph{ÎÅ ÏÐÒÅÄÅÌ£Î}. + +åÓÌÉ ×Ù ÏÐÒÅÄÅÌÉÔÅ ËÏÍÐÏÎÅÎÔÙ ÉÍÅÎÉ ÆÁÊÌÁ ÐÏÓÌÅ \samp{//}, ÔÏÌØËÏ +ÐÏÄÄÉÒÅËÔÏÒÉÉ Ó ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÍÉ ËÏÍÐÏÎÅÎÔÁÍÉ ÂÕÄÕÔ ×ËÌÀÞÅÎÙ. +îÁÐÒÉÍÅÒ, \samp{/a//b} ÄÁ£Ô ÐÏÄÄÉÒÅËÔÏÒÉÉ \file{/a/1/b}, +\file{/a/2/b}, \file{/a/1/1/b}, É Ô.Ä., ÎÏ ÎÅ \file{/a/b/c} ÉÌÉ +\file{/a/1}. + +÷ÏÚÍÏÖÎÙ ÎÅÓËÏÌØËÏ ËÏÎÓÔÒÕËÃÉÊ \samp{//} × ÏÄÎÏÍ ÐÕÔÉ, ÎÏ +\samp{//} × ÎÁÞÁÌÅ ÐÕÔÉ ÉÇÎÏÒÉÒÕÀÔÓÑ. + +\subsubsection{óÐÉÓÏË ÓÐÅÃÉÁÌØÎÙÈ ÓÉÍ×ÏÌÏ× É ÉÈ ÚÎÁÞÅÎÉÊ} + +÷ ÓÌÅÄÕÀÝÅÍ ÓÐÉÓËÅ ÐÒÉ×ÏÄÑÔÓÑ ÓÐÅÃÉÁÌØÎÙÅ ÓÉÍ×ÏÌÙ × ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÈ +ÆÁÊÌÁÈ \KPS{}. + +\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} +\begin{ttdescription} +\item[\CODE{:}] òÁÚÄÅÌÉÔÅÌØ × ÓÐÅÃÉÆÉËÁÃÉÑÈ ÐÕÔÅÊ; × ÎÁÞÁÌÅ ÉÌÉ ËÏÎÃÅ + ÏÚÎÁÞÁÅÔ ÐÏÄÓÔÁÎÏ×ËÕ ÐÏ ÕÍÏÌÞÁÎÉÀ. +\item[\CODE{;}] òÁÚÄÅÌÉÔÅÌØ ÄÌÑ ÎÅ-àÎÉËÓÁ (ÔÏ ÖÅ, ÞÔÏ \code{:}). +\item[\CODE{\$}] ðÏÄÓÔÁÎÏ×ËÁ ÐÅÒÅÍÅÎÎÙÈ. +\item[\CODE{\string~}] ïÚÎÁÞÁÅÔ ÄÏÍÁÛÎÀÀ ÄÉÒÅËÔÏÒÉÀ ÐÏÌØÚÏ×ÁÔÅÌÑ. +\item[\CODE{\char`\{...\char`\}}] ðÏÄÓÔÁÎÏ×ËÁ ÓËÏÂÏË. +\item[\CODE{//}] ðÏÄÓÔÁÎÏ×ËÁ ÐÏÄÄÉÒÅËÔÏÒÉÊ (ÍÏÖÅÔ ×ÓÔÒÅÔÉÔØÓÑ ÇÄÅ + ÕÇÏÄÎÏ, ËÒÏÍÅ ÎÁÞÁÌÁ ÐÕÔÉ). +\item[\CODE{\%}] îÁÞÁÌÏ ËÏÍÍÅÎÔÁÒÉÑ. +\item[\CODE{\bs}] óÉÍ×ÏÌ ÐÒÏÄÏÌÖÅÎÉÑ (ÄÌÑ ËÏÍÁÎÄ ÉÚ ÎÅÓËÏÌØËÉÈ ÓÔÒÏË). +\item[\CODE{!!}] ðÏÉÓË \emph{ÔÏÌØËÏ} × ÂÁÚÅ ÄÁÎÎÙÈ, ÎÏ \emph{ÎÅ} ÎÁ + ÄÉÓËÅ. +\end{ttdescription} + + +\subsection{âÁÚÙ ÄÁÎÎÙÈ} +\label{sec:filename-database} + +\KPS{} ÓÔÁÒÁÅÔÓÑ ÍÉÎÉÍÉÚÉÒÏ×ÁÔØ ÏÂÒÁÝÅÎÉÅ Ë ÄÉÓËÕ ÐÒÉ ÐÏÉÓËÅ. ôÅÍ ÎÅ +ÍÅÎÅÅ × ÓÉÓÔÅÍÁÈ Ó ÂÏÌØÛÉÍ ËÏÌÉÞÅÓÔ×ÏÍ ÄÉÒÅËÔÏÒÉÊ ÐÏÉÓË × ËÁÖÄÏÊ +×ÏÚÍÏÖÎÏÊ ÄÉÒÅËÔÏÒÉÉ ÍÏÖÅÔ ÚÁÎÑÔØ ÄÏÌÇÏÅ ×ÒÅÍÑ (ÜÔÏ ÏÓÏÂÅÎÎÏ ×ÅÒÎÏ, +ÅÓÌÉ ÎÁÄÏ ÐÒÏ×ÅÒÉÔØ ÓÏÔÎÉ ÄÉÒÅËÔÏÒÉÊ ÓÏ ÛÒÉÆÔÁÍÉ). ðÏÜÔÏÍÕ \KPS{} +ÕÍÅÅÔ ÉÓÐÏÌØÚÏ×ÁÔØ ×ÎÅÛÎÉÊ ÔÅËÓÔÏ×ÙÊ ÆÁÊÌ, +<<ÂÁÚÕ ÄÁÎÎÙÈ>> \file{ls-R}, ËÏÔÏÒÙÊ ÚÎÁÅÔ, ÇÄÅ ÎÁÈÏÄÑÔÓÑ ÆÁÊÌÙ × +ÄÉÒÅËÔÏÒÉÑÈ, ÞÔÏ ÄÁ£Ô ×ÏÚÍÏÖÎÏÓÔØ ÉÚÂÅÖÁÔØ ÞÁÓÔÙÈ ÏÂÒÁÝÅÎÉÊ Ë ÄÉÓËÕ. + +åÝ£ ÏÄÎÁ ÂÁÚÁ ÄÁÎÎÙÈ, ÆÁÊÌ \file{aliases} ÐÏÚ×ÏÌÑÅÔ ×ÁÍ ÄÁ×ÁÔØ +ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ÎÁÚ×ÁÎÉÑ ÆÁÊÌÁÍ × \file{ls-R}. üÔÏ ÐÏÌÅÚÎÏ, ÅÓÌÉ ×ÁÍ +ÎÕÖÎÏ ÓÏÂÌÀÄÁÔØ ÐÒÁ×ÉÌÏ \acro{DOS} <<8.3>>. + +\subsubsection{âÁÚÙ ÄÁÎÎÙÈ \texttt{ls-R}} +\label{sec:ls-R} + +ëÁË ÏÂßÑÓÎÅÎÏ ×ÙÛÅ, ÏÓÎÏ×ÎÁÑ ÂÁÚÁ ÄÁÎÎÙÈ ÎÁÚÙ×ÁÅÔÓÑ \file{ls-R}. ÷Ù +ÍÏÖÅÔÅ ÓÏÚÄÁÔØ Å£ × ËÏÒÎÅ ËÁÖÄÏÇÏ ÄÅÒÅ×Á \TeX{}Á, ËÏÔÏÒÏÅ +ÐÒÏÓÍÁÔÒÉ×ÁÅÔÓÑ \KPS{} (ÐÏ ÕÍÏÌÞÁÎÉÀ, \code{\$TEXMF}); × ÂÏÌØÛÉÎÓÔ×Å +ÓÌÕÞÁÅ× ÉÅÒÁÒÈÉÑ ÔÏÌØËÏ ÏÄÎÁ. \KPS{} ÉÝÅÔ ÆÁÊÌÙ \file{ls-R} × ÐÕÔÉ +\code{TEXMFDBS}. + +òÅËÏÍÅÎÄÕÅÍÙÊ ÓÐÏÓÏ ÓÏÚÄÁÎÉÑ É ÐÏÄÄÅÒÖËÉ \samp{ls-R} "--- ÓËÒÉÐÔ +\code{mktexlsr}, ×ËÌÀÞ£ÎÎÙÊ × ÄÉÓÔÒÉÂÕÔÉ×. ïÎ ×ÙÚÙ×ÁÅÔÓÑ ÒÁÚÎÙÍÉ +ÓËÒÉÐÔÁÍÉ \samp{mktex}\dots. ÷ ÐÒÉÎÃÉÐÅ ÜÔÏÔ ÓËÒÉÐÔ ×ÙÐÏÌÎÑÅÔ ËÏÍÁÎÄÙ +ÔÉÐÁ +\begin{alltt} +cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R +\end{alltt} +ÐÒÉ ÕÓÌÏ×ÉÉ, ÞÔÏ × ×ÁÛÅÊ ÓÉÓÔÅÍÅ \code{ls} ÄÁ£Ô ×Ù×ÏÄ × ÎÕÖÎÏÍ ÆÏÒÍÁÔÅ +(\acro{GNU} \code{ls} ÇÏÄÉÔÓÑ). þÔÏÂÙ ÐÏÄÄÅÒÖÉ×ÁÔØ ÂÁÚÕ ÄÁÎÎÙÈ × +ÔÅËÕÝÅÍ ÓÏÓÔÏÑÎÉÉ, ÐÒÏÝÅ ×ÓÅÇÏ ÐÅÒÅÇÅÎÅÒÉÒÏ×ÁÔØ Å£ ÒÅÇÕÌÑÒÎÏ ÉÚ +\code{cron}Á, ÔÁË ÞÔÏ ÏÎÁ Á×ÔÏÍÁÔÉÞÅÓËÉ ÏÂÎÏ×ÌÑÅÔÓÑ ÐÏÓÌÅ ÕÓÔÁÎÏ×ËÉ +ÎÏ×ÏÇÏ ÐÁËÅÔÁ. + +åÓÌÉ ÆÁÊÌ ÎÅ ÎÁÊÄÅÎ × ÂÁÚÅ ÄÁÎÎÙÈ, ÐÏ ÕÍÏÌÞÁÎÉÀ \KPS{} ÉÝÅÔ ÅÇÏ ÎÁ ÄÉÓËÅ. +åÓÌÉ ÜÌÅÍÅÎÔ ÐÕÔÉ ÎÁÞÉÎÁÅÔÓÑ Ó \samp{!!}, ÔÏ ÐÏÉÓË ÐÒÏÉÓÈÏÄÉÔ +\emph{ÔÏÌØËÏ} × ÂÁÚÅ ÄÁÎÎÙÈ. + + +\subsubsection{kpsewhich: ÐÏÉÓË ÆÁÊÌÏ×} +\label{sec:invoking-kpsewhich} + +ðÒÏÇÒÁÍÍÁ \texttt{kpsewhich} ×ÙÐÏÌÎÑÅÔ ÐÏÉÓË × ÓÏÏÔ×ÅÔÓÔ×ÉÉ Ó +ÁÌÇÏÒÉÔÍÏÍ, ÏÐÉÓÁÎÎÙÍ ×ÙÛÅ. üÔÏ ÍÏÖÅÔ ÂÙÔØ ÐÏÌÅÚÎÏ × ËÁÞÅÓÔ×Å +×ÁÒÉÁÎÔÁ ËÏÍÁÎÄÙ \code{find} ÄÌÑ ÐÏÉÓËÁ ÆÁÊÌÏ× × ÉÅÒÁÒÈÉÑÈ \TeX{}Á +(ÜÔÏ ÛÉÒÏËÏ ÉÓÐÏÌØÚÕÅÔÓÑ × ÓËÒÉÐÔÁÈ \samp{mktex}\dots). + +\begin{alltt} +> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} +\end{alltt} +ïÐÃÉÉ, ÕËÁÚÁÎÎÙÅ × \ttvar{option}, ÎÁÞÉÎÁÀÔÓÑ ÌÉÂÏ Ó \samp{-} +ÌÉÂÏ \samp{-{}-}, É ÌÀÂÙÅ ÏÄÎÏÚÎÁÞÎÙÅ ÓÏËÒÁÝÅÎÉÑ ÄÏÐÕÓÔÉÍÙ. + +\KPS{} ÒÁÓÓÍÁÔÒÉ×ÁÅÔ ËÁÖÄÙÊ ÁÒÇÕÍÅÎÔ, ÎÅ Ñ×ÌÑÀÝÉÊÓÑ ÏÐÃÉÅÊ, ËÁË ÉÍÑ +ÆÁÊÌÁ, É ×ÏÚ×ÒÁÝÁÅÔ ÐÅÒ×ÙÊ ÎÁÊÄÅÎÎÙÊ ÆÁÊÌ. îÅÔ ÏÐÃÉÉ ×ÅÒÎÕÔØ ×ÓÅ +ÎÁÊÄÅÎÎÙÅ ÆÁÊÌÙ (ÄÌÑ ÜÔÏÇÏ ÍÏÖÎÏ ÉÓÐÏÌØÚÏ×ÁÔØ ÐÒÏÇÒÁÍÍÕ \samp{find}). + +îÁÉÂÏÌÅÅ ×ÁÖÎÙÅ ÏÐÃÉÉ ÏÐÉÓÁÎÙ ÎÉÖÅ. + +\begin{ttdescription} +\item[\texttt{-{}-dpi=\var{num}}]\mbox{}\\ + õÓÔÁÎÏ×ÉÔØ ÒÁÚÒÅÛÅÎÉÅ \ttvar{num}; ÜÔÏ ×ÌÉÑÅÔ ÔÏÌØËÏ ÎÁ ÐÏÉÓË ÆÁÊÌÏ× + \samp{gf} É \samp{pk}. óÉÎÏÎÉÍ \samp{-D}, ÄÌÑ + ÓÏ×ÍÅÓÔÉÍÏÓÔÉ Ó \cmdname{dvips}. ðÏ ÕÍÏÌÞÁÎÉÀ 600. + +\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ + õÓÔÁÎÏ×ÉÔØ ÆÏÒÍÁÔ ÄÌÑ ÐÏÉÓËÁ \ttvar{name}. ðÏ ÕÍÏÌÞÁÎÉÀ, ÆÏÒÍÁÔ + ÏÐÒÅÄÅÌÑÅÔÓÑ ÉÚ ÉÍÅÎÉ ÆÁÊÌÁ. äÌÑ ÆÏÒÍÁÔÏ×, ÄÌÑ ËÏÔÏÒÙÈ ÎÅÔ + ÏÄÎÏÚÎÁÞÎÏÇÏ ÓÕÆÆÉËÓÁ, ÎÁÐÒÉÍÅÒ, ÆÁÊÌÏ× \MP{} É ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÈ + ÆÁÊÌÏ× + \cmdname{dvips}, ×Ù ÄÏÌÖÎÙ ÕËÁÚÁÔØ ÎÁÚ×ÁÎÉÅ, ÉÚ×ÅÓÔÎÏÅ \KPS{}, + ÎÁÐÒÉÍÅÒ, \texttt{tex} ÉÌÉ \texttt{enc files}. óÐÉÓÏË ÍÏÖÎÏ + ÐÏÌÕÞÉÔØ ËÏÍÁÎÄÏÊ \texttt{kpsewhich -{}-help}. + +\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ + õÓÔÁÎÏ×ÉÔØ ÚÎÁÞÅÎÉÅ ÒÅÖÉÍÁ \ttvar{string}; ÜÔÏ ×ÉÌÑÅÔ ÔÏÌØËÏ ÎÁ + ÐÏÉÓË ÆÁÊÌÏ× \samp{gf} É \samp{pk}. úÎÁÞÅÎÉÑ ÐÏ ÕÍÏÌÞÁÎÉÀ ÎÅÔ: + ÉÝÕÔÓÑ ÆÁÊÌÙ ÄÌÑ ×ÓÅÈ ÒÅÖÉÍÏ×. + +\item[\texttt{-{}-must-exist}]\mbox{}\\ + óÄÅÌÁÔØ ×Ó£ ×ÏÚÍÏÖÎÏÅ, ÞÔÏÂÙ ÎÁÊÔÉ ÆÁÊÌ ×ËÌÀÞÁÑ ÐÏÉÓË ÎÁ ÄÉÓËÅ. ðÏ + ÕÍÏÌÞÁÎÉÀ ÄÌÑ ÐÏ×ÙÛÅÎÉÑ ÜÆÆÅËÔÉ×ÎÏÓÔÉ ÐÒÏÓÍÁÔÒÉ×ÁÅÔÓÑ ÔÏÌØËÏ ÂÁÚÁ + ÄÁÎÎÙÈ \file{ls-R}. + +\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ + éÓËÁÔØ × ÎÁÂÏÒÅ ÄÉÒÅËÔÏÒÉÊ \ttvar{string} (ËÁË ÏÂÙÞÎÏ, ÒÁÚÄÅÌ£ÎÎÙÈ + Ä×ÏÅÔÏÞÉÑÍÉ), ×ÍÅÓÔÏ ÔÏÇÏ, ÞÔÏÂÙ ×ÙÞÉÓÌÑÔØ ÐÕÔØ ÐÏÉÓËÁ ÐÏ ÉÍÅÎÉ + ÆÁÊÌÁ. \samp{//} É ÏÂÙÞÎÙÅ ÐÏÄÓÔÁÎÏ×ËÉ ÒÁÂÏÔÁÀÔ. ïÐÃÉÉ + \samp{-{}-path} É \samp{-{}-format} ÎÅÓÏ×ÍÅÓÔÉÍÙ. + +\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ + õÓÔÁÎÏ×ÉÔØ ÉÍÑ ÐÒÏÇÒÁÍÍÙ ÒÁ×ÎÙÍ \texttt{\var{name}}. üÔÏ ×ÌÉÑÅÔ ÎÁ + ÐÕÔØ ÐÏÉÓËÁ ÉÚ-ÚÁ ÐÒÅÆÉËÓÁ \texttt{.\var{progname}}. ðÏ ÕÍÏÌÞÁÎÉÀ + \cmdname{kpsewhich}. + +\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ + ðÏËÁÚÁÔØ ÐÕÔØ, ÉÓÐÏÌØÚÕÅÍÙÊ ÐÒÉ ÐÏÉÓËÁÈ ÆÁÊÌÏ× ÔÉÐÁ + \texttt{\var{name}}. íÏÖÎÏ ÉÓÐÏÌØÚÏ×ÁÔØ ÒÁÓÛÉÒÅÎÉÅ (\code{.pk}, + \code{.vf} É Ô.Ä.) ÉÌÉ ÎÁÚ×ÁÎÉÅ, ËÁË ÄÌÑ ÏÐÃÉÉ \samp{-{}-format}. + +\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ + õÓÔÁÎÏ×ÉÔØ ÕÒÏ×ÅÎØ ÏÔÌÁÄËÉ \texttt{\var{num}}. +\end{ttdescription} + + + +\subsubsection{ðÒÉÍÅÒÙ ÉÓÐÏÌØÚÏ×ÁÎÉÑ} +\label{sec:examples-of-use} + +äÁ×ÁÊÔÅ ÐÏÓÍÏÔÒÉÍ ÎÁ \KPS{} × ÄÅÊÓÔ×ÉÉ. ÷ÏÔ ÐÒÏÓÔÏÊ ÐÏÉÓË: + +\begin{alltt} +> \Ucom{kpsewhich article.cls} + /usr/local/texmf-dist/tex/latex/base/article.cls +\end{alltt} +íÙ ÉÝÅÍ ÆÁÊÌ \file{article.cls}. ôÁË ËÁË ÓÕÆÆÉËÓ \samp{.cls} +ÏÄÎÏÚÎÁÞÅÎ, ÎÁÍ ÎÅ ÎÕÖÎÏ ÕËÁÚÙ×ÁÔØ, ÞÔÏ ÍÙ ÉÝÅÍ ÆÁÊÌ ÔÉÐÁ +\optname{tex} (ÉÓÈÏÄÎÉËÉ \TeX{}Á). íÙ ÎÁÈÏÄÉÍ ÅÇÏ × ÐÏÄÄÉÒÅËÔÏÒÉÉ +\file{tex/latex/base} ÄÉÒÅËÔÏÒÉÉ \samp{temf-dist} \TL. áÎÁÌÏÇÉÞÎÏ, +×Ó£ ÐÏÓÌÅÄÕÀÝÅÅ ÎÁÈÏÄÉÔÓÑ ÂÅÚ ÐÒÏÂÌÅÍ ÂÌÁÇÏÄÁÒÑ ÏÄÎÏÚÎÁÞÎÏÍÕ ÓÕÆÆÉËÓÕ: +\begin{alltt} +> \Ucom{kpsewhich array.sty} + /usr/local/texmf-dist/tex/latex/tools/array.sty +> \Ucom{kpsewhich latin1.def} + /usr/local/texmf-dist/tex/latex/base/latin1.def +> \Ucom{kpsewhich size10.clo} + /usr/local/texmf-dist/tex/latex/base/size10.clo +> \Ucom{kpsewhich small2e.tex} + /usr/local/texmf-dist/tex/latex/base/small2e.tex +> \Ucom{kpsewhich tugboat.bib} + /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib +\end{alltt} + +ëÓÔÁÔÉ, ÐÏÓÌÅÄÎÅÅ "--- ÂÉÂÌÉÏÇÒÁÆÉÞÅÓËÁÑ ÂÁÚÁ ÄÁÎÎÙÈ ÄÌÑ ÓÔÁÔÅÊ ÖÕÒÎÁÌÁ +\textsl{TUGBoat}. + +\begin{alltt} +> \Ucom{kpsewhich cmr10.pk} +\end{alltt} +âÉÔÍÁÐÙ ÛÒÉÆÔÏ× ÔÉÐÁ \file{.pk} ÉÓÐÏÌØÚÕÀÔÓÑ ÐÒÏÇÒÁÍÍÁÍÉ +\cmdname{dvips} Ï \cmdname{xdvi}. îÉÞÅÇÏ ÎÅ ÎÁÊÄÅÎÏ, ÔÁË ËÁË Õ ÎÁÓ +ÎÅÔ ÇÏÔÏ×ÙÈ ÆÁÊÌÏ× ÛÒÉÆÔÏ× Computer Modern × ÆÏÒÍÁÔÅ \samp{.pk} (ÔÁË +ËÁË ÍÙ ÉÓÐÏÌØÚÕÅÍ ×ÅÒÓÉÉ × ÆÏÒÍÁÔÅ Type~1 ÉÚ ÄÉÓÔÒÉÂÕÔÉ×Á \TL{}). +\begin{alltt} +> \Ucom{kpsewhich wsiupa10.pk} +\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk +\else /usr/local/texmf-var/fonts/pk/ljfour/public/ +... wsuipa/wsuipa10.600pk +\fi\end{alltt} +äÌÑ ÜÔÉÈ ÛÒÉÆÔÏ× (ÆÏÎÅÔÉÞÅÓËÉÊ ÁÌÆÁ×ÉÔ, ÓÏÚÄÁÎÎÙÊ × ÕÎÉ×ÅÒÓÉÔÅÔÅ +ÛÔÁÔÁ ÷ÁÛÉÎÇÔÏÎ) ÍÙ ÄÏÌÖÎÙ ÓÇÅÎÅÒÉÒÏ×ÁÔØ +\samp{.pk}, É ÔÁË ËÁË ÒÅÖÉÍ \MF{} [Ï ÕÍÏÌÞÁÎÉÀ × ÎÁÛÅÊ ÓÉÓÔÅÍÅ +\texttt{ljfour} Ó ÒÁÚÒÅÛÅÎÉÅÍ of 600\dpi{} (ÔÏÞÅË ÎÁ ÄÀÊÍ), ÜÔÏÔ ÛÒÉÆÔ +É ÎÁÊÄÅÎ. +\begin{alltt} +> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} +\end{alltt} +÷ ÜÔÏÍ ÓÌÕÞÁÅ ÎÁÍ ÎÕÖÎÏ ÒÁÚÒÅÛÅÎÉÅ 300\dpi{} (\texttt{-dpi=300}); ÍÙ +×ÉÄÉÍ, ÞÔÏ ÔÁËÏÇÏ ÛÒÉÆÔÁ × ÓÉÓÔÅÍÅ ÎÅÔ. îÁ ÓÁÍÏÍ ÄÅÌÅ ÐÒÏÇÒÁÍÍÁ +\cmdname{dvips} ÉÌÉ \cmdname{xdvi} ÐÏÓÔÒÏÉÌÁ ÂÙ ÎÕÖÎÙÊ ÆÁÊÌ +\texttt{.pk} ÐÒÉ ÐÏÍÏÝÉ ÓËÒÉÐÔÁ \cmdname{mktexpk}. + +ôÅÐÅÒØ ÏÂÒÁÔÉÍÓÑ Ë ÚÁÇÏÌÏ×ËÁÍ É ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÍ ÆÁÊÌÁÍ +\cmdname{dvips}. ÷ÎÁÞÁÌÅ ÒÁÓÓÍÏÔÒÉÍ ÏÄÉÎ ÉÚ ÎÁÉÂÏÌÅÅ ÞÁÓÔÏ +ÉÓÐÏÌØÚÕÅÍÙÈ ÆÁÊÌÏ×, ÐÒÏÌÏÇ \file{tex.pro} ÄÌÑ ÐÏÄÄÅÒÖËÉ \TeX{}Á, Á +ÚÁÔÅÍ ÒÁÓÓÍÏÔÒÉÍ ÏÂÝÉÊ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ \file{config.ps} É ËÁÒÔÕ +ÛÒÉÆÔÏ× \file{psfonts.map} (Ó 2004 ÇÏÄÁ ËÁÒÔÙ É ÆÁÊÌÙ ËÏÄÉÒÏ×ÏË ÉÍÅÀÔ +ÓÏÂÓÔ×ÅÎÎÙÅ ÐÕÔÉ ÐÏÉÓËÁ × ÄÅÒÅ×ØÑÈ \dirname{texmf}). ôÁË ËÁË ÓÕÆÆÉËÓ +\samp{.ps} ÎÅÏÄÎÏÚÎÁÞÅÎ, ÍÙ ÄÏÌÖÎÙÅ Ñ×ÎÏ ÕËÁÚÁÔØ ÔÉÐ ÆÁÊÌÁ, ËÏÔÏÒÙÊ ÍÙ +ÉÝÅÍ: (\optname{dvips config}) ÄÌÑ ÆÁÊÌÁ \texttt{config.ps}. +\begin{alltt} +> \Ucom{kpsewhich tex.pro} + /usr/local/texmf/dvips/base/tex.pro +> \Ucom{kpsewhich --format="dvips config" config.ps} + /usr/local/texmf/dvips/config/config.ps +> \Ucom{kpsewhich psfonts.map} + /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map +\end{alltt} + +òÁÓÓÍÏÔÒÉÍ ÔÅÐÅÒØ ÆÁÊÌÙ ÐÏÄÄÅÒÖËÉ \acro{URW} Times (\PS{}). ðÒÅÆÉËÓ +ÄÌÑ ÜÔÉÈ ÆÁÊÌÏ× × ÓÔÁÎÄÁÒÔÎÏÊ ÓÈÅÍÅ ÏÂÏÚÎÁÞÅÎÉÑ ÛÒÉÆÔÏ× \samp{utm}. +÷ÎÁÞÁÌÅ ÍÙ ÒÁÓÓÍÏÔÒÉÍ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ, ËÏÔÏÒÙÊ ÓÏÄÅÒÖÉÔ ÎÁÚ×ÁÎÉÅ +ËÁÒÔÙ ÛÒÉÆÔÏ×: +\begin{alltt} +> \Ucom{kpsewhich --format="dvips config" config.utm} +/usr/local/texmf-dist/dvips/psnfss/config.utm +\end{alltt} +óÏÄÅÒÖÁÎÉÅ ÜÔÏÇÏ ÆÁÊÌÁ: +\begin{alltt} + p +utm.map +\end{alltt} +ÞÔÏ ÕËÁÚÙ×ÁÅÔ ÎÁ ÆÁÊÌ \file{utm.map}, ËÏÔÏÒÙÊ ÍÙ ÈÏÔÉÍ ÔÅÐÅÒØ ÎÁÊÔÉ. +\begin{alltt} +> \Ucom{kpsewhich --format="dvips config" utm.map} + /usr/local/texmf-dist/fonts/map/dvips/times/utm.map +\end{alltt} +üÔÁ ËÁÒÔÁ ÏÐÒÅÄÅÌÑÅÔ ÎÁÚ×ÁÎÉÑ ÛÒÉÆÔÏ× ÆÏÒÍÁÔÁ Type~1 (\PS{}) × +ËÏÌÌÅËÃÉÉ URW. ïÎÁ ×ÙÇÌÑÄÉÔ ÔÁË (ÍÙ ÐÏËÁÚÙ×ÁÅÍ ÔÏÌØËÏ ÞÁÓÔØ ÆÁÊÌÁ): +\begin{alltt} +utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} +\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb +\else /usr/local/texmf-dist/fonts/type1/ +... urw/utm/utmr8a.pfb +\fi\end{alltt} + +éÚ ÜÔÉÈ ÐÒÉÍÅÒÏ× ×ÉÄÎÏ, ÞÔÏ ×Ù ÍÏÖÅÔÅ ÌÅÇËÏ ÎÁÊÔÉ ÚÁÄÁÎÎÙÊ ÆÁÊÌ. +üÔÏ ÏÓÏÂÅÎÎÏ ×ÁÖÎÏ, ÅÓÌÉ ×Ù ÐÏÄÏÚÒÅ×ÁÅÔÅ, ÞÔÏ ÐÒÏÇÒÁÍÍÙ ÎÁÈÏÄÑÔ +ÎÅÐÒÁ×ÉÌØÎÕÀ ×ÅÒÓÉÀ ÆÁÊÌÁ, ÐÏÓËÏÌØËÕ \cmdname{kpsewhich} ÐÏËÁÚÙ×ÁÅÔ +ÐÅÒ×ÙÊ ÎÁÊÄÅÎÎÙÊ ÆÁÊÌ. + +\subsubsection{ïÔÌÁÄËÁ} +\label{sec:debugging} + +éÎÏÇÄÁ ÎÅÏÂÈÏÄÉÍÏ ÐÒÏ×ÅÒÉÔØ, ËÁË ÐÒÏÇÒÁÍÍÁ ÉÝÅÔ ÆÁÊÌÙ. ó ÜÔÏÊ ÃÅÌØÀ +\KPS{} ÐÒÅÄÌÁÇÁÅÔ ÒÁÚÎÙÅ ÕÒÏ×ÎÉ ÏÔÌÁÄËÉ: + +\begin{ttdescription} +\item[\texttt{\ 1}] ÓÔÁÔÉÓÔÉËÁ ÏÂÒÁÝÅÎÉÊ Ë ÄÉÓËÕ. ðÒÉ ÒÁÂÏÔÅ Ó ÂÁÚÁÍÉ + \file{ls-R} ÜÔÏ ÐÏÞÔÉ ÎÅ ÄÏÌÖÎÏ ÄÁ×ÁÔØ ÚÁÐÉÓÅÊ × ÌÏÇ. +\item[\texttt{\ 2}] óÓÙÌËÉ ÎÁ ÈÅÛÉ (ÎÁÐÒÉÍÅÒ, ÂÁÚÙ ÄÁÎÎÙÈ \file{ls-R}, + ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÆÁÊÌÙ É Ô.Ä.). +\item[\texttt{\ 4}] ïÐÅÒÁÃÉÉ ÏÔËÒÙÔÉÑ É ÚÁËÒÙÔÉÑ ÆÁÊÌÏ×. +\item[\texttt{\ 8}] ïÂÝÁÑ ÉÎÆÏÒÍÁÃÉÑ Ï ÔÉÐÁÈ ÆÁÊÌÏ×, ËÏÔÏÒÙÅ ÉÝÅÔ + \KPS. üÔÏ ÐÏÌÅÚÎÏ ÄÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÎÁÊÔÉ, ÇÄÅ ÏÐÒÅÄÅÌÑÅÔÓÑ ÔÉÐ ÐÕÔÉ + ÐÏÉÓËÁ ÄÌÑ ÄÁÎÎÏÇÏ ÆÁÊÌÁ. +\item[\texttt{16}] óÐÉÓÏË ÄÉÒÅËÔÏÒÉÊ ÄÌÑ ËÁÖÄÏÇÏ ÜÌÅÍÅÎÔÁ ÐÕÔÉ (ÐÒÉ + ÐÏÉÓËÁÈ ÎÁ ÄÉÓËÅ). +\item[\texttt{32}] ðÏÉÓËÉ ÆÁÊÌÏ×. +\item[\texttt{64}] úÎÁÞÅÎÉÑ ÐÅÒÅÍÅÎÎÙÈ. +\end{ttdescription} +úÎÁÞÅÎÉÅ \texttt{-1} ÚÁÄÁÓÔ ×ÓÅ ÏÐÃÉÉ ×ÙÛÅ; ÉÍÅÎÎÏ ÜÔÏ ÚÎÁÞÅÎÉÅ ÞÁÝÅ +×ÓÅÇÏ ÉÓÐÏÌØÚÕÅÔÓÑ ÎÁ ÐÒÁËÔÉËÅ. + +áÎÁÌÏÇÉÞÎÏ, ÚÁÐÕÓÔÉ× ÐÒÏÇÒÁÍÍÕ \cmdname{dvips} É ÉÓÐÏÌØÚÕÑ ÓÏÞÅÔÁÎÉÅ +ÜÔÉÈ ÏÐÃÉÊ, ÍÏÖÎÏ ÐÒÏÓÌÅÄÉÔØ ÐÏÄÒÏÂÎÏ, ËÁË ÉÝÕÔÓÑ ÆÁÊÌÙ. ó ÄÒÕÇÏÊ +ÓÔÏÒÏÎÙ, ÅÓÌÉ ÆÁÊÌ ÎÅ ÎÁÊÄÅÎ, ÔÒÁÓÓÉÒÏ×ËÁ ÐÏËÁÚÙ×ÁÅÔ, ÇÄÅ ÅÇÏ ÉÓËÁÌÉ, +ÔÁË ÞÔÏ ÍÏÖÎÏ ÐÏÎÑÔØ, × Þ£Í ÓÏÓÔÏÉÔ ÐÒÏÂÌÅÍÁ. + +÷ÏÏÂÝÅ ÇÏ×ÏÒÑ, ÐÏÓËÏÌØËÕ ÂÏÌØÛÉÎÓÔ×Ï ÐÒÏÇÒÁÍÍ ÐÏÌØÚÕÀÔÓÑ ÂÉÂÌÉÏÔÅËÏÊ +\KPS{}, ×Ù ÍÏÖÅÔÅ ÕÓÔÁÎÏ×ÉÔØ ÏÐÃÉÀ ÏÔÌÁÄËÉ ÉÓÐÏÌØÚÕÑ ÐÅÒÅÍÅÎÎÕÀ +ÏËÒÕÖÅÎÉÑ \envname{KPATHSEA\_DEBUG}, É ÕÓÔÁÎÏ×É× Å£ ÎÁ ËÏÍÂÉÎÁÃÉÀ +ÏÐÉÓÁÎÎÙÈ ×ÙÛÅ ÚÎÁÞÅÎÉÊ. + +(ðÒÉÍÅÞÁÎÉÅ ÄÌÑ ÐÏÌØÚÏ×ÁÔÅÌÅÊ Windows: × ÜÔÏÊ ÓÉÓÔÅÍÅ ÔÒÕÄÎÏ +ÐÅÒÅÎÁÐÒÁ×ÉÔØ ×ÓÅ ÓÏÏÂÝÅÎÉÑ × ÆÁÊÌ. äÌÑ ÄÉÁÇÎÏÓÔÉËÉ ×Ù ÍÏÖÅÔÅ ×ÒÅÍÅÎÎÏ +ÕÓÔÁÎÏ×ÉÔØ \texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log}). + + +òÁÓÓÍÏÔÒÉÍ × ËÁÞÅÓÔ×Å ÐÒÉÍÅÒÁ ÐÒÏÓÔÏÊ ÆÁÊÌ × ÆÏÒÍÁÔÅ \LaTeX{}, +\file{hello-world.tex}, ÓÏ ÓÌÅÄÕÀÝÉÍ ÓÏÄÅÒÖÁÎÉÅÍ: +\begin{verbatim} + \documentclass{article} + \begin{document} + Hello World! + \end{document} +\end{verbatim} +üÔÏÔ ÍÁÌÅÎØËÉÊ ÆÁÊÌ ÉÓÐÏÌØÚÕÅÔ ÔÏÌØËÏ ÛÒÉÆÔ \file{cmr10}, ÔÁË ÞÔÏ +ÄÁ×ÁÊÔÅ ÐÏÓÍÏÔÒÉÍ, ËÁË \cmdname{dvips} ÓÏÚÄÁ£Ô ÆÁÊÌ × ÆÏÒÍÁÔÅ \PS{} +(ÍÙ ÈÏÔÉÍ ÉÓÐÏÌØÚÏ×ÁÔØ ×ÅÒÓÉÀ ÛÒÉÆÔÏ× × ÆÏÒÍÁÔÅ Type~1, ÏÔÓÀÄÁ ÏÐÃÉÑ +\texttt{-Pcms}). +\begin{alltt} +> \Ucom{dvips -d4100 hello-world -Pcms -o} +\end{alltt} +÷ ÜÔÏÍ ÓÌÕÞÁÅ ÍÙ ÏÂßÅÄÉÎÉÌÉ ÏÔÌÁÄÏÞÎÙÊ ÕÒÏ×ÅÎØ 4 ÄÌÑ \cmdname{dvips} +(ÄÉÒÅËÔÏÒÉÉ ÛÒÉÆÔÏ×) Ó ÐÏÄÓÔÁÎÏ×ËÏÊ ÜÌÅÍÅÎÔÏ× ÐÕÔÅÊ × \KPS (ÓÍ. +òÕËÏ×ÏÄÓÔ×Ï ÐÏÌØÚÏ×ÁÔÅÌÑ \cmdname{dvips}, +\OnCD{texmf/doc/html/dvips/dvips_toc.html}). òÅÚÕÌØÔÁÔ (ÓÌÅÇËÁ +ÏÔÒÅÄÁËÔÉÒÏ×ÁÎÎÙÊ) ÐÏËÁÚÁÎ ÎÁ ÒÉÓÕÎËÅ~\ref{fig:dvipsdbga}. +\begin{figure*}[tp] +\centering +\input{examples/ex6a.tex} +\caption{ðÏÉÓË ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÈ ÆÁÊÌÏ×}\label{fig:dvipsdbga} + +\bigskip + +\input{examples/ex6b.tex} +\caption{ðÏÉÓË ÆÁÊÌÁ ÐÒÏÌÏÇÁ}\label{fig:dvipsdbgb} + +\bigskip + +\input{examples/ex6c.tex} +\caption{ðÏÉÓË ÆÁÊÌÁ ÛÒÉÆÔÁ}\label{fig:dvipsdbgc} +\end{figure*} + +ðÒÏÇÒÁÍÍÁ \cmdname{dvips} ×ÎÁÞÁÌÅ ÉÝÅÔ Ó×ÏÉ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÆÁÊÌÙ. +óÎÁÞÁÌÁ ÎÁÈÏÄÉÔÓÑ \file{texmf.cnf}, ËÏÔÏÒÙÊ ÓÏÄÅÒÖÉÔ ÏÐÒÅÄÅÌÅÎÉÑ ÄÌÑ +ÐÕÔÅÊ ÐÏÉÓËÁ ÏÓÔÁÌØÎÙÈ ÆÁÊÌÏ×, ÚÁÔÅÍ ÂÁÚÁ ÄÁÎÎÙÈ \file{ls-R} (ÄÌÑ +ÏÐÔÉÍÉÚÁÃÉÉ ÐÏÉÓËÁ ÆÁÊÌÏ×) É ÆÁÊÌ \file{aliases}, ËÏÔÏÒÙÊ ÐÏÚ×ÏÌÑÅÔ +ÏÂßÑ×ÉÔØ ÎÅÓËÏÌØËÏ ÉͣΠ(ÎÁÐÒÉÍÅÒ, ËÏÒÏÔËÉÅ 8.3 É ÂÏÌÅÅ ÄÌÉÎÎÙÅ) ÄÌÑ +ÏÄÎÏÇÏ ÆÁÊÌÁ. úÁÔÅÍ \cmdname{dvips} ÉÝÅÔ Ó×ÏÊ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ +\file{config.ps} É ÆÁÊÌ +\file{.dvipsrc} (ËÏÔÏÒÙÊ × ÄÁÎÎÏÍ ÓÌÕÞÁÅ \emph{ÎÅ ÎÁÊÄÅÎ}). îÁËÏÎÅÃ, +\cmdname{dvips} ÎÁÈÏÄÉÔ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ ÄÌÑ ÛÒÉÆÔÏ× Computer +Modern \PS{} \file{config.cms} (ÜÔÏ ÂÙÌÏ ÚÁÄÁÎÏ ÏÐÃÉÅÊ \texttt{-Pcms} +× ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÅ). üÔÏÔ ÆÁÊÌ ÓÏÄÅÒÖÉÔ ÓÐÉÓÏË ËÁÒÔ, ËÏÔÏÒÙÅ +ÏÐÒÅÄÅÌÑÀÔ ÓÏÏÔÎÏÛÅÎÉÑ ÍÅÖÄÕ ÆÁÊÌÁÍÉ × ÆÏÒÍÁÔÁÈ \TeX{}, \PS{} +É ÎÁÚ×ÁÎÉÑÍÉ ÛÒÉÆÔÏ×: +\begin{alltt} +> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} + p +ams.map + p +cms.map + p +cmbkm.map + p +amsbkm.map +\end{alltt} +\cmdname{dvips} ÎÁÈÏÄÉÔ ×ÓÅ ÜÔÉ ÆÁÊÌÙ ÐÌÀÓ ÏÂÝÕÀ ËÁÒÔÕ ÛÒÉÆÔÏ× +\file{psfonts.map}, ËÏÔÏÒÁÑ ×ÓÅÇÄÁ ÚÁÇÒÕÖÁÅÔÓÑ (ÏÎÁ ÓÏÄÅÒÖÉÔ ÏÂÙÞÎÙÅ +ÛÒÉÆÔÙ × ÆÏÒÍÁÔÅ \PS{}; ÓÍ. ÐÏÓÌÅÄÎÀÀ ÞÁÓÔØ +ÒÁÚÄÅÌÁ~\ref{sec:examples-of-use}). + +÷ ÜÔÏÔ ÍÏÍÅÎÔ \cmdname{dvips} ÓÏÏÂÝÁÅÔ Ï ÓÅÂÅ ÐÏÌØÚÏ×ÁÔÅÌÀ: +\begin{alltt} +This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) +\end{alltt} +\ifSingleColumn +úÁÔÅÍ ÏÎÁ ÉÝÅÔ ÐÒÏÌÏÇ \file{texc.pro}: +\begin{alltt}\small +kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro +\end{alltt} +\else +úÁÔÅÍ ÏÎÁ ÉÝÅÔ ÐÒÏÌÏÇ \file{texc.pro} (ÓÍ. +ÒÉÓÕÎÏË~\ref{fig:dvipsdbgb}). +\fi + +îÁÊÄÑ ÜÔÏÔ ÆÁÊÌ, \cmdname{dvips} ÐÅÞÁÔÁÅÔ ÄÁÔÕ É ×ÒÅÍÑ, É ÉÎÆÏÒÍÉÒÕÅÔ +ÎÁÓ, ÞÔÏ ÓÏÂÉÒÁÅÔÓÑ ÇÅÎÅÒÉÒÏ×ÁÔØ ÆÁÊÌ \file{hello-world.ps}, ÞÔÏ ÅÊ +ÎÕÖÅÎ ÆÁÊÌ \file{cmr10}, É ÞÔÏ ÐÏÓÌÅÄÎÉÊ Ñ×ÌÑÅÔÓÑ <<ÒÅÚÉÄÅÎÔÎÙÍ>> +(ÂÉÔÍÁÐÙ ÎÅ ÎÕÖÎÙ): +\begin{alltt}\small +TeX output 1998.02.26:1204' -> hello-world.ps +Defining font () cmr10 at 10.0pt +Font cmr10 is resident. +\end{alltt} +ôÅÐÅÒØ ÏÎÁ ÉÝÅÔ ÆÁÊÌ \file{cmr10.tfm}, ËÏÔÏÒÙÊ ÏÎÁ ÎÁÈÏÄÉÔ, ÚÁÔÅÍ ÅÝ£ +ÎÅÓËÏÌØËÏ ÐÒÏÌÏÇÏ× (ÚÄÅÓØ ÏÎÉ ÏÐÕÝÅÎÙ), É ÎÁËÏÎÅà ÆÁÊÌ ÆÏÒÍÁÔÁ Type~1 +\file{cmr10.pfb} ÎÁÊÄÅÎ É ×ËÌÀÞ£Î × ×ÙÈÏÄÎÏÊ ÆÁÊÌ (ÓÍ, ÐÏÓÌÅÄÎÀÀ +ÓÔÒÏËÕ): +\begin{alltt}\small +kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, + path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: + /var/tex/fonts/tfm//). +kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm +kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, + ... + +kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb +[1] +\end{alltt} + +\subsection{ïÐÃÉÉ ÚÁÐÕÓËÁ} + +åÝ£ ÏÄÎÁ ÐÏÌÅÚÎÁÑ ×ÏÚÍÏÖÎÏÓÔØ \Webc{} "--- ËÏÎÔÒÏÌØ ÐÁÒÁÍÅÔÒÏ× ÐÁÍÑÔÉ +(× ÏÓÏÂÅÎÎÏÓÔÉ ÒÁÚÍÅÒ ÍÁÓÓÉ×Ï×) ÐÒÉ ÚÁÐÕÓËÅ, ×Ï ×ÒÅÍÑ ÞÔÅÎÉÑ ÆÁÊÌÁ +\file{texmf.cnf} ÂÉÂÌÉÏÔÅËÏÊ \KPS{}. ðÁÒÁÍÅÔÒÙ ÐÁÍÑÔÉ ÎÁÈÏÄÑÔÓÑ × +ÞÁÓÔÉ~3 ÜÔÏÇÏ ÆÁÊÌÁ × ÄÉÓÔÒÉÂÕÔÉ×Å \TL{}. ÷ÏÔ ÓÁÍÙÅ ×ÁÖÎÙÅ: + +\begin{ttdescription} +\item[\texttt{main\_memory}] ïÂÝÅÅ ËÏÌÉÞÅÓÔ×Ï ÓÌÏ× × ÐÁÍÑÔÉ ÄÌÑ + ÐÒÏÇÒÁÍÍ \TeX{}, \MF{} É \MP. ðÏÓÌÅ ÉÚÍÅÎÅÎÉÑ ÜÔÏÇÏ ÐÁÒÁÍÅÔÒÁ ÎÁÄÏ + ÐÅÒÅÇÅÎÅÒÉÒÏ×ÁÔØ ÆÏÒÍÁÔ. îÁÐÒÉÍÅÒ, ×Ù ÍÏÖÅÔÅ ÓÏÚÄÁÔØ <<ÏÇÒÏÍÎÕÀ>> + ×ÅÒÓÉÀ \TeX{}Á, É ÎÁÚ×ÁÔØ ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÊ ÆÏÒÍÁÔ + \texttt{hugetex.fmt}. ðÏ ÏÂÝÉÍ ÐÒÁ×ÉÌÁÍ \KPS{}, ÚÎÁÞÅÎÉÅ ÐÅÒÅÍÅÎÎÏÊ + \texttt{main\_memory} ÂÕÄÅÔ ÞÉÔÁÔØÓÑ ÉÚ ÆÁÊÌÁ \file{texmf.cnf}. +\item[\texttt{extra\_mem\_bot}] äÏÐÏÌÎÉÔÅÌØÎÁÑ ÐÁÍÑÔØ ÄÌÑ <<ÂÏÌØÛÉÈ>> + ÓÔÒÕËÔÕÒ, ËÏÔÏÒÙÅ ÓÏÚÄÁ£Ô \TeX{}: ÂÏËÓÏ×, ËÌÅÑ É Ô.Ä. ïÓÏÂÅÎÎÏ + ÐÏÌÅÚÎÏ ÐÒÉ ÉÓÐÏÌØÚÏ×ÁÎÉÉ \PiCTeX{}Á. +\item[\texttt{font\_mem\_size}] ëÏÌÉÞÅÓÔ×Ï ÓÌÏ× ÉÎÆÏÒÍÁÃÉÉ Ï ÛÒÉÆÔÁÈ + ÄÌÑ \TeX{}Á. üÔÏ ÐÒÉÍÅÒÎÏ ÓÕÍÍÁÒÎÙÊ ÒÁÚÍÅÒ ×ÓÅÈ ÆÁÊÌÏ× TFM, ËÏÔÏÒÙÅ + ÞÉÔÁÅÔ \TeX. +\item[\texttt{hash\_extra}] + äÏÐÏÌÎÉÔÅÌØÎÙÊ ÒÁÚÍÅÒ ÈÅÛÁ ÄÌÑ ÉͣΠËÏÍÁÎÄ. ðÒÉÍÅÒÎÏ 10\,000 ËÏÍÁÎÄ + ÍÏÖÅÔ ÂÙÔØ ÐÏÍÅÝÅÎÏ × ÏÓÎÏ×ÎÏÊ ÈÅÛ. åÓÌÉ ×Ù ÄÅÌÁÅÔÅ ÂÏÌØÛÕÀ ËÎÉÇÕ ÓÏ + ÍÎÏÇÉÍÉ ÐÅÒÅËÒ£ÓÔÎÙÍÉ ÓÓÙÌËÁÍÉ, ÜÔÏÇÏ ÍÏÖÅÔ ÎÅ È×ÁÔÉÔØ. ðÏ ÕÍÏÌÞÁÎÉÀ + \texttt{hash\_extra} ÒÁ×ÅÎ \texttt{50000}. +\end{ttdescription} + +òÁÚÕÍÅÅÔÓÑ, ÜÔÏ ÎÅ ÚÁÍÅÎÁ ÎÁÓÔÏÑÝÉÈ ÄÉÎÁÍÉÞÅÓËÉÈ ÍÁÓÓÉ×Ï× É +ÒÁÓÐÒÅÄÅÌÅÎÉÑ ÐÁÍÑÔÉ, ÎÏ ÐÏÓËÏÌØËÕ ÜÔÉ ÞÅÒÔÙ ÉÓËÌÀÞÉÔÅÌØÎÏ ÓÌÏÖÎÏ +ÏÓÕÝÅÓÔ×ÉÔØ × ÔÅËÕÝÅÍ \TeX{}Å, ÉÓÐÏÌØÚÏ×ÁÎÉÅ ÜÔÉÈ ÐÁÒÁÍÅÔÒÏ× +ÐÒÅÄÓÔÁ×ÌÑÅÔ ÓÏÂÏÊ ÐÏÌÅÚÎÙÊ ËÏÍÐÒÏÍÉÓÓ É ÏÂÅÓÐÅÞÉ×ÁÅÔ ÎÅËÏÔÏÒÕÀ +ÇÉÂËÏÓÔØ. + + +\begin{comment} +\section{ëÏÍÐÉÌÉÒÏ×ÁÎÉÅ ÄÌÑ ÎÏ×ÏÊ ÐÌÁÔÆÏÒÍÙ ÔÉÐÁ Unix} + + +åÓÌÉ Õ ×ÁÓ ÐÌÁÔÆÏÒÍÁ, ÄÌÑ ËÏÔÏÒÏÊ ÍÙ ÎÅ ÓËÏÍÐÉÌÉÒÏ×ÁÌÉ ÐÒÏÇÒÁÍÍ, ×ÁÍ +ÐÒÉÄ£ÔÓÑ ÜÔÏ ÓÄÅÌÁÔØ ÓÁÍÉÍ. üÔÏ ÎÅ ÔÁË ÕÖ ÓÌÏÖÎÏ. ÷Ó£, ÞÔÏ ×ÁÍ ÍÏÖÅÔ +ÐÏÎÁÄÏÂÉÔØÓÑ, ÅÓÔØ × ÄÉÓÔÒÉÂÕÔÉ×Å × ÄÉÒÅËÔÏÒÉÉ \texttt{source}. + +\subsection{îÅÏÂÈÏÄÉÍÙÅ ÉÎÓÔÒÕÍÅÎÔÙ} + +÷ÁÍ ÎÕÖÎÏ ÐÏ ËÒÁÊÎÅÊ ÍÅÒÅ 100\,Mb ÎÁ ÄÉÓËÅ ÄÌÑ ËÏÍÐÉÌÉÒÏ×ÁÎÉÑ \TeX{}Á É +ÄÒÕÇÉÈ ÐÒÏÇÒÁÍÍ. ÷ÁÍ ÐÏÔÒÅÂÕÅÔÓÑ ËÏÍÐÉÌÑÔÏÒ \acro{ANSI} C, ÐÒÏÇÒÁÍÍÁ +\cmdname{make}, ÌÅËÓÉÞÅÓËÉÊ ÓËÁÎÅÒ É ÇÅÎÅÒÁÔÏÒ ÐÁÒÓÅÒÏ×. íÙ +ÒÅËÏÍÅÎÄÕÅÍ ×ÅÒÓÉÉ ÜÔÉÈ ÐÒÏÇÒÁÍÍ ÏÔ \acro{GNU} +(\cmdname{gcc}, \acro{GNU} \cmdname{make}, \cmdname{m4}, \cmdname{flex}, +\cmdname{bison}). ÷Ù ÍÏÖÅÔÅ ÒÁÂÏÔÁÔØ É Ó ÄÒÕÇÉÍÉ ËÏÍÐÉÌÑÔÏÒÁÍÉ É +×ÅÒÓÉÑÍÉ \cmdname{make}, ÎÏ ×ÁÍ ÐÏÔÒÅÂÕÅÔÓÑ ÇÌÕÂÏËÏÅ ÐÏÎÉÍÁÎÉÅ àÎÉËÓÁ, +ÞÔÏÂÙ ÒÁÚÏÂÒÁÔØÓÑ × ×ÏÚÍÏÖÎÙÈ ÐÒÏÂÌÅÍÁÈ. + +ëÒÏÍÅ ÔÏÇÏ, ËÏÍÁÎÄÁ \texttt{uname} ÄÏÌÖÎÁ ÄÁ×ÁÔØ ÒÁÚÕÍÎÙÊ ÒÅÚÕÌØÔÁÔ. + + +\subsection{ëÏÎÆÉÇÕÒÁÃÉÑ} + +óÎÁÞÁÌÁ ÐÒÏÉÚ×ÅÄÉÔÅ ÎÏÒÍÁÌØÎÕÀ ÕÓÔÁÎÏ×ËÕ \TL{} ÎÁ ×ÁÛ ÄÉÓË (ÓÍ. +ÒÁÚÄÅÌ~\ref{sec:unix-install-disk} +\p.~\pageref{sec:unix-install-disk}). ÷Ù ÍÏÖÅÔÅ ÐÒÏÐÕÓÔÉÔØ ÕÓÔÁÎÏ×ËÕ +ÓËÏÍÐÉÌÉÒÏ×ÁÎÎÙÈ ÐÒÏÇÒÁÍÍ. + +úÁÔÅÍ ÒÁÓÐÁËÕÊÔÅ ÉÓÈÏÄÎÉËÉ ÉÚ ÆÁÊÌÁ × ÄÉÒÅËÔÏÒÉÉ \dirname{source} ÎÁ +×ÁÛ ÄÉÓË É ÓÍÅÎÉÔÅ ÄÉÒÅËÔÏÒÉÀ ÔÕÄÁ, ÇÄÅ ×Ù ÒÁÓËÒÙÌÉ ÜÔÏÔ ÆÁÊÌ. + +úÁÔÅÍ ÚÁÐÕÓÔÉÔÅ \cmdname{configure}, ÎÁÐÒÉÍÅÒ, ÔÁË: +\begin{alltt} +> \Ucom{sh configure -prefix=/usr/local/TeX} +\end{alltt} + +äÉÒÅËÔÏÒÉÑ \optname{-prefix} "--- ÜÔÏ ÍÅÓÔÏ, ËÕÄÁ ×Ù ÕÓÔÁÎÏ×ÉÌÉ +ÏÓÎÏ×ÎÏÅ ÄÅÒÅ×Ï ÐÏÄÄÅÒÖËÉ. óÔÒÕËÔÕÒÁ ÄÉÒÅËÔÏÒÉÊ ÂÕÄÅÔ ÔÁËÏ×Á +(\$TEXDIR ÏÚÎÁÞÁÅÔ ×ÙÂÒÁÎÎÕÀ ÄÉÒÅËÔÏÒÉÀ): + +\noindent +\begin{tabular}{>{\ttfamily}ll@{}} + \dirname{$TEXDIR/share/texmf} & ÏÓÎÏ×ÎÏÅ ÄÅÒÅ×Ï ÓÏ ÛÒÉÆÔÁÍÉ,\\ + & \qquad ÍÁËÒÏÓÙ É Ô.Ä.\\ + \dirname{$TEXDIR/man} & ÒÕËÏ×ÏÄÓÔ×Á × ÆÏÒÍÁÔÅ Unix man\\ + \dirname{$TEXDIR/info} & ÒÕËÏ×ÏÄÓÔ×Á × ÆÏÒÍÁÔÅ \acro{GNU} Info \\ + \dirname{$TEXDIR/bin/$PLATFORM} & ÐÒÏÇÒÁÍÍÙ\\ +\end{tabular} +%$ + +åÓÌÉ ×Ù ÈÏÔÉÔÅ ÕÂÒÁÔØ ÕÒÏ×ÅÎØ ÄÉÒÅËÔÏÒÉÊ \dirname{$PLATFORM}, +Ô.Å. ÐÏÍÅÓÔÉÔØ ÐÒÏÇÒÁÍÍÙ ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ × \dirname{$TEXDIR/bin}, +ÄÏÂÁ×ØÔÅ Ë ÏÐÃÉÑÍ \verb|--disable-multiplatform|. + +ðÏÓÍÏÔÒÉÔÅ ÎÁ ÒÅÚÕÌØÔÁÔ \verb|./configure --help| ÄÌÑ ÏÓÔÁÌØÎÙÈ +ÏÐÃÉÊ. îÁÐÒÉÍÅÒ, ×Ù ÍÏÖÅÔÅ ÎÅ ËÏÍÐÉÌÉÒÏ×ÁÔØ \OMEGA{} É +\eTeX{}. + + +\subsection{úÁÐÕÓË \cmdname{make}} + +õÂÅÄÉÔÅÓØ, ÞÔÏ ÐÅÒÅÍÅÎÎÁÑ ÏÂÏÌÏÞËÉ ÉÌÉ ÏÐÃÉÑ \texttt{noclobber} ÎÅ +ÚÁÄÁÎÁ. úÁÔÅÍ ÚÁÐÕÓÔÉÔÅ \cmdname{make}: +\begin{alltt} +> \Ucom{make world} +\end{alltt} +É ÒÁÓÓÌÁÂØÔÅÓØ\ldots + +åÓÌÉ ×Ù ÈÏÔÉÔÅ ÚÁÐÉÓÁÔØ × ÌÏÇ ×ÓÅ ÐÒÏÉÓÈÏÄÑÝÅÅ, ÉÓÐÏÌØÚÕÊÔÅ: +\begin{alltt} +> \Ucom{sh -c "make world >world.log 2>\&1" \&} +\end{alltt} + +ðÅÒÅÄ ÔÅÍ, ËÁË ×Ù ÒÅÛÉÔÅ, ÞÔÏ ×Ó£ ÐÒÏÛÌÏ ÎÏÒÍÁÌØÎÏ, ÐÒÏ×ÅÒØÔÅ ÌÏÇ ÎÁ +ÏÛÉÂËÉ; \acro{GNU} \cmdname{make} ×ÓÅÇÄÁ ÉÓÐÏÌØÚÕÅÔ ÓÔÒÏËÕ \samp{***} +ÐÒÉ ÏÛÉÂËÅ. ëÒÏÍÅ ÔÏÇÏ, ÐÒÏ×ÅÒØÔÅ, ÞÔÏ ×ÓÅ ÐÒÏÇÒÁÍÍÙ +ÓËÏÍÐÉÌÉÒÏ×ÁÌÉÓØ: +\begin{alltt} +> \Ucom{cd \emph{TEXDIR}/bin/\emph{archname}} +> \Ucom{ls | wc} +\end{alltt} +òÅÚÕÌØÔÁÔ ÄÏÌÖÅÎ ÂÙÔØ ÂÏÌØÛÅ 200 (×Ù ÍÏÖÅÔÅ ÐÏÌÕÞÉÔØ ÔÏÞÎÏÅ ÞÉÓÌÏ, +ÐÒÏ×ÅÒÉ× ÓÏÄÅÒÖÉÍÏÅ ÄÉÒÅËÔÏÒÉÉ +\dirname{bin} × ÄÉÓÔÒÉÂÕÔÉ×Å). + +åÓÌÉ ×ÁÍ ÎÕÖÎÙ ÓÐÅÃÉÁÌØÎÙÅ ÐÒÉ×ÉÌÅÇÉÉ ÄÌÑ \texttt{make install}, ×Ù +ÍÏÖÅÔÅ ÒÁÚÄÅÌÉÔØ \samp{make world} ÎÁ Ä×Á ÐÒÉ£ÍÁ: +\begin{alltt} +> \Ucom{make all} +> \Ucom{su} +> \Ucom{make install strip} +\end{alltt} + +ðÏÓÌÅ ÕÓÔÁÎÏ×ËÉ ×ÁÛÉÈ ÎÏ×ÙÈ ÐÒÏÇÒÁÍÍ, ×ÙÐÏÌÎÉÔÅ ÏÂÙÞÎÙÅ ÐÒÏÃÅÄÕÒÙ +ÎÁÓÔÒÏÊËÉ, ÏÐÉÓÁÎÎÙÅ × ÒÁÚÄÅÌÅ~\ref{sec:postinstall}, +\p.~\pageref{sec:postinstall}. + +ëÒÏÍÅ ÔÏÇÏ, ÅÓÌÉ ×Ù ÈÏÔÉÔÅ, ÞÔÏÂÙ ×ÁÛÉÍÉ ÐÒÏÇÒÁÍÍÁÍÉ ÐÏÌØÚÏ×ÁÌÉÓØ +ÄÒÕÇÉÅ ÌÀÄÉ, ÎÁÐÉÛÉÔÅ ÎÁÍ. íÙ ÂÕÄÅÍ ÒÁÄÙ ÐÏÍÅÓÔÉÔØ ÉÈ ÎÁ ÓÔÒÁÎÉÃÙ +\TL{} × ÓÅÔÉ. + +\end{comment} + +\section{âÌÁÇÏÄÁÒÎÏÓÔÉ} + +\TL{} "--- ÒÅÚÕÌØÔÁÔ ÏÂßÅÄÉΣÎÎÙÈ ÕÓÉÌÉÊ ÐÒÁËÔÉÞÅÓËÉ ×ÓÅÈ ÇÒÕÐÐ +ÐÏÌØÚÏ×ÁÔÅÌÅÊ \TeX Á. üÔÏ ÉÚÄÁÎÉÅ \TL{} ×ÙÈÏÄÉÔ ÐÏÄ ÒÅÄÁËÃÉÅÊ ëÁÒÌÁ +âÅÒÒÉ. äÒÕÇÉÅ ÏÓÎÏ×ÎÙÅ Á×ÔÏÒÙ, ÐÒÏÛÌÙÅ É ÎÁÓÔÏÑÝÉÅ, ÐÅÒÅÞÉÓÌÅÎÙ ÎÉÖÅ. +íÙ ÂÌÁÇÏÄÁÒÉÍ: + +\begin{itemize*} + +\item áÎÇÌÏÑÚÙÞÎÕÀ, ÎÅÍÅÃËÕÀ, ÇÏÌÌÁÎÄÓËÕÀ É ÐÏÌØÓËÕÀ ÇÒÕÐÐÙ + ÐÏÌØÚÏ×ÁÔÅÌÅÊ \TeX{}Á (\acro{TUG}, \acro{DANTE} e.V., \acro{NTG} É + \acro{GUST}) ÚÁ ÎÅÏÂÈÏÄÉÍÕÀ ÔÅÈÎÉÞÅÓËÕÀ É ÁÄÍÉÎÉÓÔÒÁÔÉ×ÎÕÀ + ÉÎÆÒÁÓÔÒÕËÔÕÒÕ. ðÏÖÁÌÕÊÓÔÁ, ×ÓÔÕÐÁÊÔÅ × ÇÒÕÐÐÙ ÐÏÌØÚÏ×ÁÔÅÌÅÊ \TeX + Á (ÓÍ. \url{http://tug.org/usergroups.html}). + +\item çÒÕÐÐÕ ÐÏÄÄÅÒÖËÉ \acro{CTAN}, × ÏÓÏÂÅÎÎÏÓÔÉ òÏÂÉÎÁ æÜÊÒÂÜÊÒÎÓÁ, + äÖÉÍÁ èÅÆÆÅÒÏÎÁ É òÁÊÎÅÒÁ ûÏÐÆÁ ÚÁ ÒÁÚÍÅÝÅÎÉÅ ÄÉÓËÏ× \TL{} É + ÐÏÄÄÅÒÖËÕ ÉÎÆÒÁÓÔÒÕËÔÕÒÙ ÏÂÎÏ×ÌÅÎÉÑ ÐÁËÅÔÏ×, ÏÔ ËÏÔÏÒÏÊ ÚÁ×ÉÓÉÔ + \TL. + +\item ðÉÔÅÒÁ âÒÅÊÔÅÎÌÏÈÎÅÒÁ É ËÏÍÁÎÄÕ ÒÁÚÒÁÂÏÔÞÉËÏ× \eTeX Á ÚÁ + ÂÕÄÕÝÉÊ \TeX Ï×, É × ÏÓÏÂÅÎÎÏÓÔÉ ðÉÔÅÒÁ ÚÁ ÂÌÅÓÔÑÝÕÀ ÒÁÂÏÔÕ Ó + ÓÉÓÔÅÍÏÊ GNU autoools ÄÌÑ \TL{}. + + +\item ôÏÍÁÓÁ üÓÓÅÒÁ, ÂÅÚ ÚÁÍÅÞÁÔÅÌØÎÏÇÏ ÐÁËÅÔÁ \teTeX{} ËÏÔÏÒÏÇÏ \TL{} + ÎÅ ÓÕÝÅÓÔ×Ï×ÁÌ ÂÙ, É ËÏÔÏÒÙÊ ÍÎÏÇÏ ÐÏÍÏÇÁÌ ÎÁÍ × ÒÁÂÏÔÅ ÎÁÄ \TL. + +\item íÁÊËÌÁ çÕÓÅÎÓÁ, ËÏÔÏÒÙÊ ÂÙÌ ÓÏÁ×ÔÏÒÏÍ ÐÅÒ×ÏÊ ×ÅÒÓÉÉ ÄÏËÕÍÅÎÔÁÃÉÉ. + + +\item üÊÔÁÎÁ çÕÒÁÒÉ, ÞÅÊ \TeX4ht{} ÉÓÐÏÌØÚÏ×ÁÌÓÑ ÄÌÑ ÓÏÚÄÁÎÉÑ ÆÁÊÌÏ× × + ÆÏÒÍÁÔÅ \HTML{}, É ËÏÔÏÒÙÊ ÎÅÕÓÔÁÎÎÏ ÒÁÂÏÔÁÌ, ÐÏ ÐÅÒ×ÏÍÕ ÔÒÅÂÏ×ÁÎÉÀ + ÄÏÂÁ×ÌÑÑ ÎÕÖÎÙÅ ÎÁÍ ×ÏÚÍÏÖÎÏÓÔÉ. + +\item èÁÎ ôÅ ôÁÎÁ, íÁÒÔÉÎÁ ûÒ£ÄÅÒÁ É ËÏÍÁÎÄÕ pdf\TeX a + (\url{http://pdftex.org}) ÚÁ ÎÅÕÓÔÁÎÎÏÅ ÒÁÓÛÉÒÅÎÉÅ ×ÏÚÍÏÖÎÏÓÔÅÊ \TeX + Á. + + +\item çÁÎÓÁ èÁÇÅÎÁ ÚÁ ÐÏÍÏÝØ × ÔÅÓÔÉÒÏ×ÁÎÉÉ É ÐÒÉÓÐÏÓÏÂÌÅÎÉÉ ÆÏÒÍÁÔÁ + \ConTeXt\ (\url{http://pragma-ade.com}) Ë ÎÁÛÉÍ ÎÕÖÄÁÍ. + +\item èÁÒÔÍÕÔÁ èÅÎËÅÌÑ ÚÁ ÓÕÝÅÓÔ×ÅÎÎÙÊ ×ËÌÁÄ × pdf\TeX\, Lua\TeX{} É + ÄÒÕÇÉÅ ÐÒÏÇÒÁÍÍÙ. + + +\item ôÁËÏ èÏË×ÁÔÅÒÁ ÚÁ ×ÏÚÏÂÎÏ×ÌÅÎÉÅ ÒÁÂÏÔÙ ÎÁÄ \MP{} É (Lua)\TeX ÏÍ + (\url{http://luatex.org}) É ÚÁ ÉÎÔÅÇÒÉÒÏ×ÁÎÉÅ \ConTeXt Á × \TL. + +\item ðÁ×ÌÁ ñËÏ×ÓËÏÇÏ ÚÁ ÉÎÓÔÁÌÌÑÔÏÒ ÄÌÑ Windows \cmdname{tlpm}, É + ôÏÍÁÛÁ ìÕÖÁËÁ ÚÁ \cmdname{tlpmgui}, ÉÓÐÏÌØÚÏ×ÁÎÎÙÅ × ÐÒÏÛÌÙÈ ×ÅÒÓÉÑÈ + \TL{}. + +\item áËÉÒÕ ëÁËÕÔÏ ÚÁ ÂÏÌØÛÕÀ ÐÏÍÏÝØ × ÉÎÔÅÇÒÉÒÏ×ÁÎÉÉ × ÓÉÓÔÅÍÕ + ÐÒÏÇÒÁÍÍ ÄÌÑ Windows ÉÚ ÅÇÏ ÄÉÓÔÒÉÂÕÔÉ×Á \acro{W32TEX} + (\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}) É ÍÎÏÇÏÅ + ÄÒÕÇÏÅ. + +\item äÖÏÎÁÔÁÎÁ ëØÀ É ÅÇÏ ÒÁÂÏÔÏÄÁÔÅÌÑ \acro{SIL} ÚÁ ÓÏÚÄÁÎÉÅ ×ÁÖÎÏÊ + ÎÏ×ÏÊ ÓÉÓÔÅÍÙ Xe\TeX{}, ÚÁ ÕÓÉÌÉÑ ÐÏ Å£ ÉÎÔÅÇÒÉÒÏ×ÁÎÉÀ × \TL{} É ÚÁ + ÉÓÈÏÄÎÕÀ ×ÅÒÓÉÀ ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ Mac\TeX. + +\item äÉËÁ ëÏÞÁ ÚÁ ÐÏÄÄÅÒÖËÕ Mac\TeX Á (\url{http://tug.org/mactex}) × + ÔÅÓÎÏÍ ÓÏÔÒÕÄÎÉÞÅÓÔ×Å Ó \TL{}, É ÚÁ ÅÇÏ ÎÅÉÓÔÏÝÉÍÙÈ ÜÎÔÕÚÉÁÚÍ. + +\item òÅÊÎÈÁÒÄÁ ëÏÔÕÞÕ ÚÁ ÏÇÒÏÍÎÕÀ ÒÁÂÏÔÕ ÐÏ ÉÎÆÒÁÓÔÒÕËÔÕÒÅ + \TL{} 2008, ÚÁ ÉÓÓÌÅÄÏ×ÁÔÅÌØÓËÕÀ ÒÁÂÏÔÕ × ÏÂÌÁÓÔÉ Windows, ÚÁ + ÓËÒÉÐÔ \texttt{getnonfreefonts} É ÍÎÏÇÏÅ ÄÒÕÇÏÅ. + + +\item óÉÐÁ ëÒÏÎÅÎÂÅÒÇÁ, ÔÁËÖÅ ÚÁ ÂÏÌØÛÏÊ ×ÌÁÄ × ÉÎÆÒÁÓÔÒÕËÔÕÒÕ \TL{} + 2008 É ÐÒÏÇÒÁÍÍÕ ÕÓÔÁÎÏ×ËÉ, ÏÓÏÂÅÎÎÏ ÄÌÑ Windows, Á ÔÁËÖÅ ÚÁ + ÏÓÎÏ×ÎÕÀ ÒÁÂÏÔÕ ÐÏ ÄÏËÕÍÅÎÔÁÃÉÉ ÎÏ×ÙÈ ×ÏÚÍÏÖÎÏÓÔÅÊ. + +\item ðÅÔÒÁ ïÌÛÁËÁ ÚÁ ËÏÏÒÄÉÎÁÃÉÀ É ÔÝÁÔÅÌØÎÕÀ ÐÒÏ×ÅÒËÕ ÞÅÛÓËÏÇÏ É + ÓÌÏ×ÁÃËÏÇÏ ÍÁÔÅÒÉÁÌÁ. + +\item ôÏÛÉÏ ïÛÉÍÕ ÚÁ ÅÇÏ ÐÒÏÓÍÏÔÒÝÉË \cmdname{dviout} ÄÌÑ Windows. + + +\item íÁÎÕÜÌÑ ðØÅÇÏÒØÅ-çÏÎÎÁÒÁ ÚÁ ÐÏÍÏÝØ × ÏÂÎÏ×ÌÅÎÉÉ ÐÁËÅÔÏ×, + ÄÏËÕÍÅÎÔÁÃÉÉ É ÒÁÚÒÁÂÏÔËÕ ÐÒÏÇÒÁÍÍÙ \cmdname{tldoc}. + +\item æÁÂÒÉÃÉÑ ðÏÐÉÎØÅ, ÚÁ ÐÏÄÄÅÒÖËÕ Windows × ÐÅÒ×ÙÈ ×ÅÒÓÉÑÈ \TL{} É + ÚÁ ÒÁÂÏÔÕ ÎÁÄ ÆÒÁÎÃÕÚÓËÏÊ ÄÏËÕÍÅÎÔÁÃÉÅÊ. + +\item îÏÒÂÅÒÔÁ ðÒÅÊÎÉÎÇÁ, ËÏÔÏÒÙÊ ÂÙÌ ÇÌÁ×ÎÙÍ ÁÒÈÉÔÅËÔÏÒÏÍ + ÉÎÆÒÁÓÔÒÕËÔÕÒÙ É ÐÒÏÇÒÁÍÍÙ ÕÓÔÁÎÏ×ËÉ \TL{} 2008, Á ÔÁËÖÅ + ËÏÏÒÄÉÎÉÒÏ×ÁÌ ÄÅÂÉÁÎÏ×ÓËÕÀ ×ÅÒÓÉÀ \TL{} (ÓÏ×ÍÅÓÔÎÏ Ó æÒÁÎËÏÍ + ëÀÓÔÅÒÏÍ), ×ÙÄ×ÉÎÕ× ÍÎÏÇÏ ÃÅÎÎÙÈ ÐÒÅÄÌÏÖÅÎÉÊ. + + +\item óÅÂÁÓÔØÑÎÁ òÁÔÃÁ, ÓÏÚÄÁ×ÛÅÇÏ ÐÒÏÅËÔ \TL{} É ÍÎÏÇÏ ÌÅÔ + ÐÏÄÄÅÒÖÉ×ÁÀÝÅÇÏ ÅÇÏ. + + +\item ÷ÌÁÄÉÍÉÒÁ ÷ÏÌÏ×ÉÞÁ ÚÁ ÐÏÍÏÝØ × ÐÏÒÔÉÒÏ×ÁÎÉÉ É ÐÏÄÄÅÒÖËÅ + ÐÒÏÇÒÁÍÍ, × ÏÓÏÂÅÎÎÏÓÔÉ ÚÁ ÒÁÂÏÔÕ ÎÁÄ \cmdname{xindy}, ËÏÔÏÒÁÑ ÄÁÌÁ + ×ÏÚÍÏÖÎÏÓÔØ ×ËÌÀÞÉÔØ ÜÔÕ ÐÒÏÇÒÁÍÍÕ × ÄÉÓÔÒÉÂÕÔÉ×. + +\item óÔÁÛÅËa ÷Á×ÒÉËÅ×ÉÞÁ, ËÏÔÏÒÙÊ ÂÙÌ ÇÌÁ×ÎÙÍ ÔÅÓÔÅÒÏÍ \TL{} É + ËÏÏÒÄÉÎÉÒÏ×ÁÌ ÍÎÏÇÉÅ ÐÏÌØÓËÉÅ ÐÒÏÅËÔÙ: ÛÒÉÆÔÙ, ÕÓÔÁÎÏ×ËÕ ÐÏÄ + Windows É ÍÎÏÇÏÅ ÄÒÕÇÏÅ. + +\item ïÌÁÆÁ ÷ÅÂÅÒÁ ÚÁ ÔÅÒÐÅÌÉ×ÕÀ ÒÁÂÏÔÕ ÎÁÄ \Webc. + +\item çÅÒÂÅÎÁ ÷ÉÅÒÄÕ ÚÁ ÒÁÚÒÁÂÏÔËÕ É ÐÏÄÄÅÒÖËÕ \MacOSX, ÕÞÁÓÔÉÅ × + ÉÎÔÅÇÒÁÃÉÉ É ÔÅÓÔÉÒÏ×ÁÎÉÉ. + +\item çÒÜÍÁ ÷ÉÌÌÉÁÍÓÁ, ÓÏÚÄÁ×ÛÅÇÏ ËÁÔÁÌÏÇ ÐÁËÅÔÏ× \TeX\ Catalogue. + +\end{itemize*} + +ðÒÏÇÒÁÍÍÙ ËÏÍÐÉÌÉÒÏ×ÁÌÉ: +ôÉÇÒÁÎ áÊ×ÁÚÑÎ (\pkgname{x86\_64-linux}), +ôÉÍ áÒÎÏÌØÄ (\pkgname{hppa-hpux}), +òÜÎÄÉ áÕ (\pkgname{amd64-freebsd}), +üÄÄ âÁÒÒÅÔÔ (\pkgname{i386-openbsd}), +ëÁÒÌ âÅÒÒÉ (\pkgname{i386-linux}), +áËÉÒÁ ëÁËÕÔÏ (\pkgname{win32}), +äÉË ëÏÞ (\pkgname{universal-darwin}), +íÁÎÆÒÅÄ ìÏÔà (\pkgname{i386-freebsd}), +îÅÒÂÅÒÔ ðÒÅÊÎÉÎÇ (\pkgname{alpha-linux}), +áÒÔÕÒ òÅÊÔÅÎÁÕÜÒ (\pkgname{sparc-linux}), +ôÏÍÁÓ ûÍÉÔà (\pkgname{powerpc-linux}), +áÐÏÓÔÏÌÏÓ óÉÒÏÐÕÌÏÓ (\pkgname{i386-solaris}), +÷ÌÁÄÉÍÉÒ ×ÏÌÏ×ÉÞ (\pkgname{powerpc-aix}, \pkgname{sparc-solaris}), +ïÌÁÆ ÷ÅÂÅÒ (\pkgname{mips-irix}). +éÎÆÏÒÍÁÃÉÑ Ï ÐÒÏÃÅÓÓÅ ËÏÍÐÉÌÉÒÏ×ÁÎÉÑ \TL{} ÎÁÈÏÄÉÔÓÑ ÎÁ +\url{http://tug.org/texlive/build.html}. + + +äÏËÕÍÅÎÔÁÃÉÑ É ÐÅÒÅ×ÏÄÙ: ëÁÒÌ âÅÒÒÉ (ÁÎÇÌÉÊÓËÉÊ), +äÁÎÉÜÌØ æÌÉÐÏ (ÆÒÁÎÃÕÚÓËÉÊ), +ëÌÁÕÓ è£ÐÐÎÅÒ (ÎÅÍÅÃËÉÊ), +ðÅÔÒ óÏÊËÁ É ñÎ âÕÓÁ (ÞÅÛÓËÉÊ É ÓÌÏ×ÁÃËÉÊ), +âÏÒÉÓ ÷ÅÊÃÍÁÎ (ÒÕÓÓËÉÊ), +óÔÁÛÅË ÷Á×ÒÉËÅ×ÉÞ (ÐÏÌØÓËÉÊ). +óÔÒÁÎÉÃÁ ÄÏËÕÍÅÎÔÁÃÉÉ \TL{}: \url{http://tug.org/texlive/doc.html}. + +òÁÚÕÍÅÅÔÓÑ, ÎÁÛÁ ÇÌÁ×ÎÁÑ ÂÌÁÇÏÄÁÒÎÏÓÔØ "--- äÏÎÁÌØÄÕ ëÎÕÔÕ, ×Ï-ÐÅÒ×ÙÈ, +ÚÁ ÒÁÚÒÁÂÏÔËÕ \TeX Á, É ×Ï-×ÔÏÒÙÈ, ÚÁ ÔÏ, ÞÔÏ ÏÎ ÐÏÄÁÒÉÌ ÅÇÏ ÍÉÒÕ. + +\section{éÓÔÏÒÉÑ ÉÚÄÁÎÉÑ} +\label{sec:history} + +\subsection{ðÒÏÛÌÏÅ} + +÷ ËÏÎÃÅ 1993 ÇÏÄÁ × ÇÏÌÌÁÎÄÓËÏÊ ÇÒÕÐÐÅ ÐÏÌØÚÏ×ÁÔÅÌÅÊ \TeX{}Á ×Ï ×ÒÅÍÑ +ÒÁÂÏÔÙ ÎÁÄ ÄÉÓÔÒÉÂÕÔÉ×ÏÍ 4All\TeX{} \CD{} ÄÌÑ ÐÏÌØÚÏ×ÁÔÅÌÅÊ +\acro{MS-DOS} ×ÏÚÎÉËÌÁ ÎÏ×ÁÑ ÉÄÅÑ. âÙÌÁ ÐÏÓÔÁ×ÌÅÎÁ ÃÅÌØ ÓÏÚÄÁÔØ +ÅÄÉÎÙÊ \CD{} ÄÌÑ ×ÓÅÈ ÓÉÓÔÅÍ. üÔÁ ÃÅÌØ ÂÙÌÁ ÞÅÒÅÞÕÒ ÓÌÏÖÎÁ ÄÌÑ ÔÏÇÏ +×ÒÅÍÅÎÉ, ÏÄÎÁËÏ ÏÎÁ ÐÒÉ×ÅÌÁ ÎÅ ÔÏÌØËÏ Ë ÐÏÑ×ÌÅÎÉÀ ÏÞÅÎØ ÕÓÐÅÛÎÏÇÏ \CD{} +4All\TeX{}, ÎÏ É Ë ÓÏÚÄÁÎÉÀ ÒÁÂÏÞÅÊ ÇÒÕÐÐÙ ôÅÈÎÉÞÅÓËÏÇÏ óÏ×ÅÔÁ +\acro{TUG} ÐÏ ÓÔÒÕËÔÕÒÅ ÄÉÒÅËÔÏÒÉÊ ÄÌÑ \TeX{}Á +(\url{http://tug.org/tds}), ËÏÔÏÒÁÑ ÒÁÚÒÁÂÏÔÁÌÁ ÓÔÁÎÄÁÒÔ ÓÔÒÕËÔÕÒÙ +ÄÉÒÅËÔÏÒÉÊ ÄÌÑ ÓÉÓÔÅÍÙ \TeX{} É ÕËÁÚÁÌÁ, ËÁË ÓÏÚÄÁÔØ ÌÏÇÉÞÎÕÀ ÅÄÉÎÕÀ +ÓÉÓÔÅÍÕ ÆÁÊÌÏ× ÄÌÑ \TeX Á. îÅÓËÏÌØËÏ ×ÅÒÓÉÊ \TDS{} ÂÙÌÏ ÏÐÕÂÌÉËÏ×ÁÎÏ +× ÄÅËÁÂÒØÓËÏÍ ×ÙÐÕÓËÅ \textsl{TUGboat} × 1995 ÇÏÄÕ, É Ó ÓÁÍÏÇÏ ÎÁÞÁÌÁ +ÓÔÁÌÏ ÑÓÎÏ, ÞÔÏ ÓÌÅÄÕÅÔ ÓÏÚÄÁÔØ ÐÒÉÍÅÒ ÓÔÒÕËÔÕÒÙ ÎÁ \CD{}. äÉÓÔÒÉÂÕÔÉ×, +ËÏÔÏÒÙÊ ×Ù ÄÅÒÖÉÔÅ × ÒÕËÁÈ, "--- ÐÒÑÍÏÊ ÒÅÚÕÌØÔÁÔ ÒÁÂÏÔÙ ÜÔÏÊ ÇÒÕÐÐÙ. +éÚ ÕÓÐÅÈÁ 4All\TeX{} ÂÙÌ ÓÄÅÌÁÎ ×Ù×ÏÄ, ÞÔÏ ÐÏÌØÚÏ×ÁÔÅÌÑÍ àÎÉËÓÁ ÔÁËÖÅ +ÐÏÄÏÊÄ£Ô ÔÁËÁÑ ÕÄÏÂÎÁÑ ÓÉÓÔÅÍÁ, É ÔÁË ÒÏÄÉÌÁÓØ ÄÒÕÇÁÑ ×ÁÖÎÁÑ ÞÁÓÔØ +\TL. + +íÙ ÎÁÞÁÌÉ ÄÅÌÁÔØ \CD{} Ó àÎÉËÓÏÍ É ÓÔÒÕËÔÕÒÏÊ ÄÉÒÅËÔÏÒÉÊ \TDS{} ÏÓÅÎØÀ +1995 ÇÏÄÁ, É ÂÙÓÔÒÏ ÐÏÎÑÌÉ, ÞÔÏ Õ \teTeX{}Á ôÏÍÁÓÁ üÓÓÅÒÁ ÉÄÅÁÌØÎÙÊ +ÓÏÓÔÁ× ÄÉÓÔÒÉÂÕÔÉ×Á É ÐÏÄÄÅÒÖËÁ ÍÎÏÇÉÈ ÐÌÁÔÆÏÒÍ. ôÏÍÁÓ ÓÏÇÌÁÓÉÌÓÑ ÎÁÍ +ÐÏÍÏÞØ, É ÍÙ × ÎÁÞÁÌÅ 1996 ÇÏÄÁ ÓÔÁÌÉ ÓÅÒØ£ÚÎÏ ÒÁÂÏÔÁÔØ ÎÁÄ +ÄÉÓÔÒÉÂÕÔÉ×ÏÍ. ðÅÒ×ÏÅ ÉÚÄÁÎÉÅ ×ÙÛÌÏ × ÍÁÅ 1996 ÇÏÄÁ. ÷ ÎÁÞÁÌÅ 1997 +ÇÏÄÁ ëÁÒÌ âÅÒÒÉ ÚÁ×ÅÒÛÉÌ ÎÏ×ÕÀ ×ÅÒÓÉÀ Web2C, ËÏÔÏÒÁÑ ×ËÌÀÞÉÌÁ +ÐÒÁËÔÉÞÅÓËÉ ×ÓÅ ÎÏ×ÙÅ ×ÏÚÍÏÖÎÏÓÔÉ, ÄÏÂÁ×ÌÅÎÎÙÅ ôÏÍÁÓÏÍ üÓÓÅÒÏÍ × +\teTeX, É ÍÙ ÒÅÛÉÌÉ ÏÓÎÏ×ÁÔØ ×ÔÏÒÏÅ ÉÚÄÁÎÉÅ ÎÁ ÓÔÁÎÄÁÒÔÎÏÍ \Webc, Ó +ÄÏÂÁ×ÌÅÎÉÅÍ ÓËÒÉÐÔÁ \texttt{texconfig} ÉÚ \teTeX{}Á. ôÒÅÔØÅ ÉÚÄÁÎÉÅ +\CD{} ÏÓÎÏ×Ù×ÁÌÏÓØ ÎÁ ÎÏ×ÏÊ ×ÅÒÓÉÉ \Webc{} 7.2, ïÌÁÆÁ ÷ÅÂÅÒÁ; × ÔÏ ÖÅ +×ÒÅÍÑ ÂÙÌÁ ×ÙÐÕÝÅÎÁ ÎÏ×ÁÑ ×ÅÒÓÉÑ \teTeX{}Á, É \TL{} ×ËÌÀÞÉÌ ÐÏÞÔÉ ×ÓÅ +ÅÇÏ ÎÏ×ÙÅ ×ÏÚÍÏÖÎÏÓÔÉ. þÅÔ×ÅÒÔÏÅ ÉÚÄÁÎÉÅ ÓÌÅÄÏ×ÁÌÏ ÔÏÊ ÖÅ ÔÒÁÄÉÃÉÉ, +ÉÓÐÏÌØÚÕÑ ÎÏ×ÕÀ ×ÅÒÓÉÀ \teTeX{}Á É \Webc{} (7.3). ôÅÐÅÒØ × Î£Í ÂÙÌÁ +ÐÏÌÎÁÑ ÓÉÓÔÅÍÁ ÄÌÑ Windows. + +äÌÑ ÐÑÔÏÇÏ ÉÚÄÁÎÉÑ (ÍÁÒÔ 2000 ÇÏÄÁ) ÍÎÏÇÉÅ ÐÁËÅÔÙ ÎÁ \CD{} ÂÙÌÉ +ÐÅÒÅÓÍÏÔÒÅÎÙ É ÐÒÏ×ÅÒÅÎÙ. éÎÆÏÒÍÁÃÉÑ Ï ÐÁËÅÔÁÈ ÂÙÌÁ ÓÏÂÒÁÎÁ × ÆÁÊÌÙ +XML. îÏ ÇÌÁ×ÎÙÍ ÉÚÍÅÎÅÎÉÅÍ × \TeX\ Live 5 ÂÙÌÏ ÕÄÁÌÅÎÉÅ ×ÓÅÈ +ÎÅÓ×ÏÂÏÄÎÙÈ ÐÒÏÇÒÁÍÍ. ÷Ó£ ÎÁ \TL{} ÐÒÅÐÏÌÁÇÁÅÔÓÑ ÓÏ×ÍÅÓÔÉÍÙÍ Ó +ðÒÁ×ÉÌÁÍÉ äÅÂÉÁÎÁ ÄÌÑ ó×ÏÂÏÄÎÙÈ ðÒÏÇÒÁÍÍ +(\url{http://www.debian.org/intro/free}); ÍÙ ÓÄÅÌÁÌÉ ×Ó£, ÞÔÏ ÍÏÇÌÉ, +ÞÔÏÂÙ ÐÒÏ×ÅÒÉÔØ ÌÉÃÅÎÚÉÉ ×ÓÅÈ ÐÁËÅÔÏ×, É ÍÙ ÂÕÄÅÍ ÂÌÁÇÏÄÁÒÎÙ ÚÁ ÌÀÂÏÅ +ÕËÁÚÁÎÉÅ ÎÁ ÏÛÉÂËÉ. + +÷ ÛÅÓÔÏÍ ÉÚÄÁÎÉÉ (ÉÀÌØ 2001 ÇÏÄÁ) ÂÙÌÏ ÍÎÏÇÏ ÎÏ×ÏÇÏ ÍÁÔÅÒÉÁÌÁ. +çÌÁ×ÎÙÍ ÂÙÌÁ ÎÏ×ÁÑ ËÏÎÃÅÐÃÉÑ ÕÓÔÁÎÏ×ËÉ: ÐÏÌØÚÏ×ÁÔÅÌØ ×ÙÂÉÒÁÌ ÎÕÖÎÙÊ +ÎÁÂÏÒ ËÏÌÌÅËÃÉÊ. ñÚÙËÏ×ÙÅ ËÏÌÌÅËÃÉÉ ÂÙÌÉ ÐÏÌÎÏÓÔØÀ ÒÅÏÒÇÁÎÉÚÏ×ÁÎÙ, +ÔÁË ÞÔÏ ×ÙÂÏÒ ÌÀÂÏÊ ÉÚ ÎÉÈ ÕÓÔÁÎÁ×ÌÉ×ÁÌ ÎÅ ÔÏÌØËÏ ÍÁËÒÏÓÙ, ÛÒÉÆÔÙ É É +Ô.Ä., ÎÏ É ×ÎÏÓÉÌ ÉÚÍÅÎÅÎÉÑ × \texttt{language.dat}. + +óÅÄØÍÏÅ ÉÚÄÁÎÉÅ 2002 ÇÏÄÁ ÄÏÂÁ×ÉÌÏ ÐÏÄÄÅÒÖËÕ \MacOSX{}, É ÂÏÌØÛÏÅ +ËÏÌÉÞÅÓÔ×Ï ÏÂÎÏ×ÌÅÎÉÊ ÄÌÑ ÐÁËÅÔÏ× É ÐÒÏÇÒÁÍÍ. ÷ÁÖÎÏÊ ÃÅÌØÀ ÂÙÌÁ +ÉÎÔÅÇÒÁÃÉÑ Ó \teTeX{}ÏÍ, ÞÔÏÂÙ ÉÓÐÒÁ×ÉÔØ ÒÁÓÈÏÖÄÅÎÉÅ, ÎÁÍÅÔÉ×ÛÅÅÓÑ × +×ÅÒÓÉÑÈ~5 É~6. + +\subsubsection{2003} + +÷ 2003 ÇÏÄÕ ÍÙ ÐÒÏÄÏÌÖÉÌÉ ÉÚÍÅÎÅÎÉÑ É ÄÏÐÏÌÎÅÎÉÑ, É ÏÂÎÁÒÕÖÉÌÉ, ÞÔÏ +\TL{} ÔÁË ×ÙÒÏÓ, ÞÔÏ ÎÅ ÐÏÍÅÝÁÅÔÓÑ ÎÁ \CD. ðÏÜÔÏÍÕ ÍÙ ÒÁÚÄÅÌÉÌÉ ÅÇÏ ÎÁ +ÔÒÉ ÄÉÓÔÒÉÂÕÔÉ×Á. ëÒÏÍÅ ÔÏÇÏ: + +\begin{itemize*} +\item ðÏ ÐÒÏÓØÂÅ Á×ÔÏÒÏ× \LaTeX{}Á, ÍÙ ÓÍÅÎÉÌÉ ÓÔÁÎÄÁÒÔÎÙÅ ËÏÍÁÎÄÙ + \cmdname{latex} É \cmdname{pdflatex}: ÔÅÐÅÒØ ÏÎÉ ÉÓÐÏÌØÚÕÀÔ \eTeX{} + (ÓÍ. ÓÔÒ.~\pageref{text:etex}). +\item îÏ×ÙÅ ÛÒÉÆÔÙ Latin Modern ×ËÌÀÞÅÎÙ É ÒÅËÏÍÅÎÄÏ×ÁÎÙ ÄÌÑ ÉÓÐÏÌØÚÏ×ÁÎÉÑ. +\item õÂÒÁÎÁ ÐÏÄÄÅÒÖËÁ ÄÌÑ Alpha \acro{OSF} + (ÐÏÄÄÅÒÖËÁ ÄÌÑ \acro{HPUX} ÂÙÌÁ ÕÂÒÁÎÁ ÒÁÎÅÅ), ÐÏÓËÏÌØËÕ ÎÉËÔÏ + ÎÅ ÉÍÅÌ (É ÎÅ ÐÒÅÄÌÏÖÉÌ) ËÏÍÐØÀÔÅÒÏ× ÄÌÑ ËÏÍÐÉÌÉÒÏ×ÁÎÉÑ + ÐÒÏÇÒÁÍÍ. +\item óÉÌØÎÏ ÉÚÍÅÎÉÌÁÓØ ÕÓÔÁÎÏ×ËÁ ÄÌÑ Windows: ×ÐÅÒ×ÙÅ ÂÙÌÁ ÐÒÅÄÌÏÖÅÎÁ + ÉÎÔÅÇÒÉÒÏ×ÁÎÎÁÑ ÓÒÅÄÁ ÎÁ ÏÓÎÏ×Å ÒÅÄÁËÔÏÒÁ XEmacs. +\item äÏÂÁ×ÌÅÎÙ ×ÓÐÏÍÏÇÁÔÅÌÎÙÅ ÐÒÏÇÒÁÍÍÙ ÄÌÑ Windows + (Perl, Ghost\-script, Image\-Magick, Ispell). +\item æÁÊÌÙ Fontmap ÄÌÑ \cmdname{dvips}, \cmdname{dvipdfm} + É \cmdname{pdftex} ÇÅÎÅÒÉÒÕÀÔÒÓÑ ÐÒÏÇÒÁÍÍÏÊ + \cmdname{updmap} É ÕÓÔÁÎ×ÁÌÉ×ÁÀÔÓÑ × \dirname{texmf/fonts/map}. +\item \TeX{}, \MF{}, and \MP{} ÔÅÐÅÒØ ÐÏ ÕÍÏÌÞÁÎÉÀ ×Ù×ÏÄÑÔ ÓÉÍ×ÏÌÙ + ÉÚ ×ÅÒÈÎÅÊ ÐÏÌÏ×ÉÎÙ ÔÁÂÌÉÃÙ ASCII × ÆÁÊÌÙ, ÏÔËÒÙÔÙÅ + ËÏÍÁÎÄÏÊ \verb|\write|, ÌÏÇÉ É ÎÁ ÔÅÒÍÉÎÁÌ ÂÕË×ÁÌØÎÏ, + Ô.Å. \emph{ÎÅ} ÉÓÐÏÌØÚÕÑ ÆÏÒÍÁÔ \verb|^^|. ÷ \TL{}~7 ÜÔÏ ÚÁ×ÉÓÅÌÏ ÏÔ + ÓÉÓÔÅÍÎÏÊ ÌÏËÁÌÉ, ÎÏ ÔÅÐÅÒØ ÜÔÏ ×ÅÒÎÏ ÄÌÑ ×ÓÅÈ ÌÏËÁÌÅÊ. åÓÌÉ + ×ÁÍ ÎÕÖÅÎ ÆÏÒÍÁÔ \verb|^^|, ÐÅÒÅÉÍÅÎÕÊÔÅ ÆÁÊÌ + \verb|texmf/web2c/cp8bit.tcx|. ÷ ÂÕÄÕÝÅÍ ÜÔÁ ÐÒÏÃÅÄÕÒÁ ÂÕÄÅÔ + ÕÐÒÏÝÅÎÁ. +\item äÏËÕÍÅÎÔÁÃÉÑ ÂÙÌÁ ÓÕÝÅÓÔ×ÅÎÎÏ ÏÂÎÏ×ÌÅÎÁ. +\item îÁËÏÎÅÃ, ÉÚ-ÚÁ ÔÏÇÏ, ÞÔÏ ÎÕÍÅÒÁÃÉÑ ÐÏ ÉÚÄÁÎÉÑÍ ÓÔÁÌÁ ÎÅÕÄÏÂÎÏÊ, + ÍÙ ÐÅÒÅÛÌÉ ÎÁ ÎÕÍÅÒÁÃÉÀ ÐÏ ÇÏÄÁÍ: \TL{} 2003. +\end{itemize*} + +\subsubsection{2004} + +÷ 2004 ÇÏÄÕ ÍÙ ×ÎÅÓÌÉ ÍÎÏÇÏ ÉÚÍÅÎÅÎÉÊ. + +\begin{itemize} + +\item åÓÌÉ Õ ×ÁÓ ÅÓÔØ ÌÏËÁÌØÎÙÅ ÛÒÉÆÔÙ Ó ÓÏÂÓÔ×ÅÎÎÙÍÉ ÆÁÊÌÁÍÉ + \filename{.map} ÉÌÉ \filename{.enc}, ×ÁÍ ÍÏÖÅÔ ÐÏÎÁÄÏÂÉÔØÓÑ + ÐÅÒÅÍÅÓÔÉÔØ ÜÔÉ ÆÁÊÌÙ. + + æÁÊÌÙ \filename{.map} ÔÅÐÅÒØ ÉÝÕÔÓÑ ÔÏÌØËÏ × ÐÏÄÄÉÒÅËÔÏÒÉÑÈ + \dirname{fonts/map} (× ËÁÖÄÏÍ ÄÅÒÅ×Å \filename{texmf}) × ÐÕÔÉ + \envname{TEXFONTMAPS}. áÎÁÌÏÇÉÞÎÏ ÆÁÊÌÙ \filename{.enc} ÔÅÐÅÒØ + ÉÝÕÔÓÑ × ÔÏÌØËÏ × ÐÏÄÄÉÒÅËÔÏÒÉÑÈ \dirname{fonts/enc} × ÐÕÔÉ + \envname{ENCFONTS}. ðÒÏÇÒÁÍÍÁ \cmdname{updmap} ÐÒÅÄÕÐÒÅÖÄÁÅÔ, ÅÓÌÉ + ÎÁÈÏÄÉÔ ÜÔÉ ÆÁÊÌÙ ÎÅ ÔÁÍ, ÇÄÅ ÏÎÉ ÄÏÌÖÎÙ ÂÙÔØ. + + óÍ. ÏÐÉÓÁÎÉÅ ÜÔÏÊ ÓÔÒÕËÔÕÒÙ ÎÁ + \url{http://tug.org/texlive/mapenc.html}. + +\item ë ËÏÌÌÅËÃÉÉ \TK{} ÂÙÌ ÄÏÂÁ×ÌÅÎ ÕÓÔÁÎÏ×ÏÞÎÙÊ \CD{} Ó + ÄÉÓÔÒÉÂÕÔÉ×ÏÍ \MIKTEX{} ÄÌÑ ÔÅÈ, ËÔÏ ÐÒÅÄÐÏÞÉÔÁÅÔ \MIKTEX{} + ÐÒÏÇÒÁÍÍÁÍ, ÏÓÎÏ×ÁÎÎÙÍ ÎÁ \Webc. óÍ. ÒÁÚÄÅÌ~\ref{sec:overview-tl} + (\p.\pageref{sec:overview-tl}). + + +\item äÅÒÅ×Ï \dirname{texmf} × \TL{} ÂÙÌÏ ÒÁÚÄÅÌÅÎÏ ÎÁ ÔÒÉ: + \dirname{texmf}, \dirname{texmf-dist} É \dirname{texmf-doc}. + óÍ. ÒÁÚÄÅÌ~\ref{sec:tld} (\p.\pageref{sec:tld}) É ÆÁÊÌÙ + \filename{README} × ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÈ ÄÉÒÅËÔÏÒÉÑÈ. + +\item ÷ÓÅ ÆÁÊÌÙ, ËÏÔÏÒÙÅ ÞÉÔÁÅÔ \TeX, ÓÏÂÒÁÎÙ × ÐÏÄÄÉÒÅËÔÏÒÉÉ + \dirname{tex} ÄÅÒÅ×ØÅ× \dirname{texmf*} ×ÍÅÓÔÏ ÒÁÚÄÅÌÅÎÉÑ ÎÁ + \dirname{tex}, \dirname{etex}, \dirname{pdftex}, \dirname{pdfetex} É + Ô.Ä. óÍ. \CDref{texmf-doc/doc/english/tds/tds.html\#Extensions} + {\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}. + + +\item ÷ÓÐÏÍÏÇÁÔÅÌØÎÙÅ ÓËÒÉÐÔÙ (×ÙÚÙ×ÁÅÍÙÅ ÄÒÕÇÉÍÉ ÐÒÏÇÒÁÍÍÁÍÉ, Á ÎÅ + ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ ÐÏÌØÚÏ×ÁÔÅÌÅÍ) ÔÅÐÅÒØ ÓÏÂÒÁÎÙ × ÄÉÒÅËÔÏÒÉÉ + \dirname{scripts} ÄÅÒÅ×ØÅ× \dirname{texmf*} É ÉÝÕÔÓÑ ËÏÍÁÎÄÏÊ + \verb|kpsewhich -format=texmfscripts|. ðÏÜÔÏÍÕ ÅÓÌÉ Õ ×ÁÓ ÅÓÔØ + ÐÒÏÇÒÁÍÍÙ, ËÏÔÏÒÙÅ ×ÙÚÙ×ÁÀÔ ÔÁËÉÅ ÓËÒÉÐÔÙ, ÉÈ ÎÁÄÏ ÉÚÍÅÎÉÔØ. óÍ. + \CDref{texmf-doc/doc/english/tds/tds.html\#Scripts} + {\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}. + + +\item ðÏÞÔÉ ×ÓÅ ÆÏÒÍÁÔÙ ÔÅÐÅÒØ ÐÅÞÁÔÁÀÔ ÂÏÌØÛÉÎÓÔ×Ï ÓÉÍ×ÏÌÏ× + ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ, ÉÓÐÏÌØÚÕÑ <<ÔÁÂÌÉÃÙ ÐÅÒÅ×ÏÄÁ>> \filename{cp227.tcx} + ×ÍÅÓÔÏ ÆÏÒÍÁÔÁ \verb|^^|. ÷ ÞÁÓÔÎÏÓÔÉ, ÓÉÍ×ÏÌÙ Ó ËÏÄÁÍÉ 32--256 + ÐÌÀÓ ÔÁÂÕÌÑÃÉÑ, ×ÅÒÔÉËÁÌØÎÁÑ ÔÁÂÕÌÑÃÉÑ É ÐÅÒÅ×ÏÄ ÓÔÒÁÎÉÃÙ ÐÅÞÁÔÁÀÔÓÑ + ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ. éÓËÌÀÞÅÎÉÑÍÉ Ñ×ÌÑÀÔÓÑ plain \TeX{} (ÐÅÞÁÔÁÀÔÓÑ + ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ ÓÉÍ×ÏÌÙ 32--127), \ConTeXt{} (0--255) É ÆÏÒÍÁÔÙ, + ÏÔÎÏÓÑÝÉÅÓÑ Ë ÐÒÏÇÒÁÍÍÅ \OMEGA. üÔÏ ÐÏ×ÅÄÅÎÉÅ ÐÏÞÔÉ ÔÁËÏÅ ÖÅ, ËÁË Õ + \TL\,2003, ÎÏ ÒÅÁÌÉÚÏ×ÁÎÏ ÂÏÌÅÅ ÁËËÕÒÁÔÎÏ, Ó Â\'ÏÌØÛÅÊ ×ÏÚÍÏÖÎÏÓÔØÀ + ÎÁÓÔÒÏÊËÉ. óÍ. \CDref{texmf/doc/web2c/web2c.html\#TCX-files} + {\texttt{texmf/doc/web2c/web2c.html\#TCX-files}}. (ëÓÔÁÔÉ, ÐÒÉ ××ÏÄÅ + × Unicode, \TeX\ ÍÏÖÅÔ ×Ù×ÏÄÉÔØ ÐÒÉ ÕËÁÚÁÎÉÉ ÎÁ ÏÛÉÂËÕ ÔÏÌØËÏ ÞÁÓÔØ + ÍÎÏÇÏÂÁÊÔÎÏÇÏ ÓÉÍ×ÏÌÁ, ÔÁË ËÁË ×ÎÕÔÒÉ \TeX\ ÒÁÂÏÔÁÅÔ Ó ÂÁÊÔÁÍÉ). + + +\item \textsf{pdfetex} ÔÅÐÅÒØ ÉÓÐÏÌØÚÕÅÔÓÑ ÄÌÑ ×ÓÅÈ ÆÏÒÍÁÔÏ×, ËÒÏÍÅ + plain \textsf{tex}. (òÁÚÕÍÅÅÔÓÑ, ÏÎ ÄÅÌÁÅÔ ÆÁÊÌÙ × ÆÏÒÍÁÔÅ + \acro{DVI}, ÅÓÌÉ ×ÙÚ×ÁÎ ËÁË \textsf{latex} É Ô.Ð.). üÔÏ ÏÚÎÁÞÁÅÔ, + ÐÏÍÉÍÏ ÐÒÏÞÅÇÏ, ÞÔÏ ×ÏÚÍÏÖÎÏÓÔÉ \textsf{pdftex}a ÄÌÑ ÍÉËÒÏÔÉÐÏÇÒÁÆÉÉ + Á ÔÁËÖÅ ×ÏÚÍÏÖÎÏÓÔÉ \eTeX Á ÄÏÓÔÕÐÎÙ × ÆÏÒÍÁÔÁÈ \LaTeX, \ConTeXt{} É + Ô.Ä. (\OnCD{texmf-dist/doc/etex/base/}). + + üÔÏ ÔÁËÖÅ ÏÚÎÁÞÁÅÔ, ÞÔÏ ÔÅÐÅÒØ \emph{ÏÞÅÎØ ×ÁÖÎÏ} ÉÓÐÏÌØÚÏ×ÁÔØ ÐÁËÅÔ + \pkgname{ifpdf} (ÒÁÂÏÔÁÅÔ É Ó plain, É Ó \LaTeX) ÉÌÉ ÜË×É×ÁÌÅÎÔÎÙÅ + ÓÒÅÄÓÔ×Á, ÐÏÓËÏÌØËÕ ÐÒÏÓÔÏ ÐÒÏ×ÅÒËÁ, ÏÐÒÅÄẠ̊ΠÌÉ \cs{pdfoutput} ÉÌÉ + ÄÒÕÇÏÊ ÐÒÉÍÉÔÉ× ÎÅ ÄÏÓÔÁÔÏÞÎÁ ÄÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÐÏÎÑÔØ, × ËÁËÏÍ + ÆÏÒÍÁÔÅ ÇÅÎÅÒÉÒÕÅÔÓÑ ÒÅÚÕÌØÔÁÔ. íÙ ÓÄÅÌÁÌÉ ×Ó£ ×ÏÚÍÏÖÎÏÅ ÄÌÑ + ÓÏ×ÍÅÓÔÉÍÏÓÔÉ × ÜÔÏÍ ÇÏÄÕ, ÎÏ × ÂÕÄÕÝÅÍ ÇÏÄÕ \cs{pdfoutput} ÍÏÖÅÔ + ÂÙÔØ ÏÐÒÅÄẠ̊ΠÄÁÖÅ ÅÓÌÉ ÇÅÎÅÒÉÒÕÅÔÓÑ \acro{DVI}. + + +\item õ ÐÒÏÇÒÁÍÍÙ pdf\TeX\ (\url{http://pdftex.org}) ÍÎÏÇÏ ÎÏ×ÙÈ + ×ÏÚÍÏÖÎÏÓÔÅÊ: + + \begin{itemize*} + + \item ðÏÄÄÅÒÖËÁ ËÁÒÔ ÛÒÉÆÔÏ× ÉÚÎÕÔÒÉ ÄÏËÕÍÅÎÔÁ ÐÒÉ ÐÏÍÏÝÉ + \cs{pdfmapfile} É \cs{pdfmapline}. + + \item íÉËÒÏÔÉÐÏÇÒÁÆÉÞÅÓËÉÅ ÒÁÓÛÉÒÅÎÉÑ ÍÏÇÕÔ ÂÙÔØ ÉÓÐÏÌØÚÏ×ÁÎÙ + ÎÁÍÎÏÇÏ + ÐÒÏÝÅ.\\ + \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} + + + \item ÷ÓÅ ÐÁÒÁÍÅÔÒÙ, ÒÁÎÅÅ ÚÁÄÁ×Á×ÛÉÅÓÑ × ÓÐÅÃÉÁÌØÎÏÍ + ËÏÎÆÉÇÕÒÁÃÉÏÎÎÏÍ ÆÁÊÌÅ \filename{pdftex.cfg}, ÔÅÐÅÒØ ÄÏÌÖÎÙ ÂÙÔØ + ÕÓÔÁÎÏ×ÌÅÎÙ ÐÒÉÍÉÔÉ×ÁÍÉ, ÎÁÐÒÉÍÅÒ, × ÆÁÊÌÅ + \filename{pdftexconfig.tex}. æÁÊÌ \filename{pdftex.cfg} ÂÏÌØÛÅ ÎÅ + ÐÏÄÄÅÒÖÉ×ÁÅÔÓÑ. ðÒÉ ÉÚÍÅÎÅÎÉÉ ÆÁÊÌÁ \filename{pdftexconfig.tex} + ×ÓÅ ÆÏÒÍÁÔÙ \filename{.fmt} ÄÏÌÖÎÙ ÂÙÔØ ÐÅÒÅÇÅÎÅÒÉÒÏ×ÁÎÙ. + + \item ïÓÔÁÌØÎÙÅ ÉÚÍÅÎÅÎÉÑ ÏÐÉÓÁÎÙ × ÒÕËÏ×ÏÄÓÔ×Å ÐÏÌØÚÏ×ÁÔÅÌÑ + ÐÒÏÇÒÁÍÍÏÊ pdf\TeX: \OnCD{texmf/doc/pdftex/manual}. + + \end{itemize*} + + +\item ðÒÉÍÉÔÉ× \cs{input} × ÐÒÏÇÒÁÍÍÅ \cmdname{tex} (É \cmdname{mf} É + \cmdname{mpost}) ÔÅÐÅÒØ ÐÒÁ×ÉÌØÎÏ ÉÎÔÅÒÐÒÅÔÉÒÕÅÔ ÐÒÏÂÅÌÙ É ÄÒÕÇÉÅ + ÓÐÅÃÉÁÌØÎÙÅ ÓÉÍ×ÏÌÙ × Ä×ÏÊÎÙÈ ËÁ×ÙÞËÁÈ. ÷ÏÔ ÔÉÐÉÞÎÙÅ ÐÒÉÍÅÒÙ: +\begin{verbatim} +\input "filename with spaces" % plain +\input{"filename with spaces"} % latex +\end{verbatim} +óÍ. ÐÏÄÒÏÂÎÏÓÔÉ × ÒÕËÏ×ÏÄÓÔ×Å Ë ÐÒÏÇÒÁÍÍÅ \Webc: \OnCD{texmf/doc/web2c}. + + +\item ðÏÄÄÅÒÖËÁ enc\TeX Á ×ËÌÀÞÅÎÁ × \Webc, É ÐÏÜÔÏÍÕ ×Ï ×ÓÅ + ÐÒÏÇÒÁÍÍÙ \TeX, ËÏÔÏÒÙÅ ÔÅÐÅÒØ ÐÏÄÄÅÒÖÉ×ÁÀÔ ÏÐÃÉÀ \optname{-enc} + (ÔÏÌØËÏ ÐÒÉ ÇÅÎÅÒÉÒÏ×ÁÎÉÉ ÆÏÒÍÁÔÏ×). enc\TeX{} + ÏÂÅÓÐÅÞÉ×ÁÅÔ ÏÂÝÕÀ ÐÅÒÅËÏÄÉÒÏ×ËÕ ×ÈÏÄÎÏÇÏ É ×ÙÈÏÄÎÏÇÏ ÐÏÔÏËÏ×, ÞÔÏ + ÐÏÚ×ÏÌÑÅÔ ÐÏÌÎÕÀ ÐÏÄÄÅÒÖËÕ Unicode (× \acro{UTF}-8). + óÍ. \OnCD{texmf-dist/doc/generic/enctex/} É + \url{http://www.olsak.net/enctex.html}. + +\item ÷ ÄÉÓÔÒÉÂÕÔÉ×Å ÐÏÑ×ÉÌÁÓØ ÎÏ×ÁÑ ÐÒÏÇÒÁÍÍÁ Aleph, ÓÏÞÅÔÁÀÝÁÑ + \eTeX\ É \OMEGA. ëÒÁÔËÁÑ ÉÎÆÏÒÍÁÃÉÑ Ï ÎÅÊ ÎÁÈÏÄÉÔÓÑ × + \OnCD{texmf-dist/doc/aleph/base} É + \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph}. æÏÒÍÁÔ + ÄÌÑ \LaTeX Á ÎÁ ÏÓÎÏ×Å ÜÔÏÊ ÐÒÏÇÒÁÍÍÙ ÎÁÚÙ×ÁÅÔÓÑ \textsf{lamed}. + +\item ðÏÓÌÅÄÎÑÑ ×ÅÒÓÉÑ \LaTeX Á ×ËÌÀÞÁÅÔ ÎÏ×ÕÀ ×ÅÒÓÉÀ ÌÉÃÅÎÚÉÉ + \acro{LPPL} "--- ÔÅÐÅÒØ ÏÆÉÃÉÁÌØÎÏ ÏÄÏÂÒÅÎÎÕÀ DebianÏÍ. îÅËÏÔÏÒÙÅ + ÄÒÕÇÉÅ ÉÚÍÅÎÅÎÉÑ ÐÅÒÅÞÉÓÌÅÎÙ × ÆÁÊÌÁÈ \filename{ltnews} × + \OnCD{texmf-dist/doc/latex/base}. + +\item ÷ ÄÉÓÔÒÉÂÕÔÉ×Å ÐÏÑ×ÉÌÁÓØ \cmdname{dvipng}, ÎÏ×ÁÑ ÐÒÏÇÒÁÍÍÁ ÄÌÑ + ÐÅÒÅ×ÏÄÁ \acro{DVI} × \acro{PNG}. + óÍ. \OnCD{texmf/doc/man/man1/dvipng.1}. + +\item íÙ ÕÍÅÎØÛÉÌÉ ÒÁÚÍÅÒ ÐÁËÅÔÁ \pkgname{cbgreek} ÄÏ ÐÒÉÅÍÌÅÍÏÇÏ + ÎÁÂÏÒÁ ÛÒÉÆÔÏ×, Ó ÓÏÇÌÁÓÉÑ É ÓÏ×ÅÔÁ Á×ÔÏÒÁ (ëÌÁÕÄÉÏ âÅËËÁÒÉ). + éÓËÌÀÞÅÎÙ ÎÅ×ÉÄÉÍÙÅ, ÐÒÏÚÒÁÞÎÙÅ É ÐÏÌÕÐÒÏÚÒÁÞÎÙÅ ÛÒÉÆÔÙ, ËÏÔÏÒÙÅ + ÏÔÎÏÓÉÔÅÌØÎÏ ÒÅÄËÏ ÉÓÐÏÌØÚÕÀÔÓÑ, Á ÎÁÍ ÎÅ È×ÁÔÁÌÏ ÍÅÓÔÁ. ðÏÌÎÙÊ + ÎÁÂÏÒ ÛÒÉÆÔÏ× ÍÏÖÎÏ ÎÁÊÔÉ × ÁÒÈÉ×Å \acro{CTAN} + (\url{http://www.ctan.org/tex-archive/fonts/greek/cb}). + + +\item ðÒÏÇÒÁÍÍÁ \cmdname{oxdvi} ÕÄÁÌÅÎÁ ÉÚ ÄÉÓÔÒÉÂÕÔÉ×Á; ÉÓÐÏÌØÚÕÊÔÅ + \cmdname{xdvi}. + + +\item ìÉÎËÉ \cmdname{ini} É \cmdname{vir} ÄÌÑ ÐÒÏÇÒÁÍÍ \cmdname{tex}, + \cmdname{mf} É \cmdname{mpost} (ÎÁÐÒÉÍÅÒ, \cmdname{initex}) ÂÏÌØÛÅ + ÎÅ ÓÏÚÄÁÀÔÓÑ. õÖÅ ÍÎÏÇÏ ÌÅÔ ÏÐÃÉÑ \optname{-ini} ÉÈ ÕÓÐÅÛÎÏ + ÚÁÍÅÎÑÅÔ. + +\item õÂÒÁÎÁ ÐÏÄÄÅÒÖËÁ ÐÌÁÔÆÏÒÍÙ \textsf{i386-openbsd}. ôÁË ËÁË × + ÐÏÒÔÁÈ BSD ÅÓÔØ ÐÁËÅÔ \pkgname{tetex}, É ÍÏÖÎÏ ÐÏÌØÚÏ×ÁÔØÓÑ + ÐÒÏÇÒÁÍÍÁÍÉ ÄÌÑ \acro{GNU/}Linux É Free\acro{BSD}, ÍÙ ÐÏÓÞÉÔÁÌÉ, ÞÔÏ + ×ÒÅÍÑ ÄÏÂÒÏ×ÏÌØÎÙÈ ÓÏÔÒÕÄÎÉËÏ× ÐÒÏÅËÔÁ ÍÏÖÎÏ ÐÏÔÒÁÔÉÔØ Ó Â\'ÏÌØÛÅÊ + ÐÏÌØÚÏÊ ÐÏ-ÄÒÕÇÏÍÕ. + + +\item ðÏ ËÒÁÊÎÅÊ ÍÅÒÅ ÄÌÑ ÐÌÁÔÆÏÒÍÙ \textsf{sparc-solaris} ÔÒÅÂÕÅÔÓÑ + ÕÓÔÁÎÏ×ÉÔØ ÐÅÒÅÍÅÎÎÕÀ ÏËÒÕÖÅÎÉÑ \envname{LD\_LIBRARY\_PATH} ÄÌÑ + ÒÁÂÏÔÙ ÐÒÏÇÒÁÍÍ \pkgname{t1utils}. üÔÏ ×ÙÚ×ÁÎÏ ÔÅÍ, ÞÔÏ ÏÎÉ + ÎÁÐÉÓÁÎÙ ÎÁ C++, Á ÓÔÁÎÄÁÒÔÎÏÊ ÄÉÒÅËÔÏÒÉÉ ÄÌÑ ÂÉÂÉÌÉÏÔÅË C++ × + ÓÉÓÔÅÍÅ ÎÅÔ (ÜÔÏ ÐÏÑ×ÉÌÏÓØ ÄÏ 2004 ÇÏÄÁ, ÎÏ ÒÁÎÅÅ ÜÔÁ ÏÓÏÂÅÎÎÏÓÔØ ÎÅ + ÂÙÌÁ ÄÏËÕÍÅÎÔÉÒÏ×ÁÎÁ). áÎÁÌÏÇÉÞÎÏ, × \textsf{mips-irix} ÔÒÅÂÕÀÔÓÑ + ÂÉÂÌÉÏÔÅËÉ \acro{MIPS}pro~7.4. + +\end{itemize} + +\subsubsection{2005} + +÷ 2005 ÇÏÄÕ ÂÙÌÏ, ËÁË ×ÓÅÇÄÁ, ÓÄÅÌÁÎÏ ÍÎÏÇÏ ÉÚÍÅÎÅÎÉÊ × ÐÁËÅÔÁÈ É +ÐÒÏÇÒÁÍÍÁÈ. éÎÆÒÁÓÔÒÕËÔÕÒÁ ÐÏÞÔÉ ÎÅ ÉÚÍÅÎÉÌÁÓØ ÐÏ ÓÒÁ×ÎÅÎÅÎÉÀ Ó 2004 +ÇÏÄÏÍ, ÎÏ ÎÅËÏÔÏÒÙÅ ÎÅÉÚÂÅÖÎÙÅ ÉÚÍÅÎÅÎÉÑ ÂÙÌÉ ÓÄÅÌÁÎÙ. + +\begin{itemize} + +\item âÙÌÉ ÄÏÂÁ×ÌÅÎÙ ÎÏ×ÙÅ ÓËÒÉÐÔÙ \cmdname{texconfig-sys}, + \cmdname{updmap-sys} É \cmdname{fmtutil-sys}, ËÏÔÏÒÙÅ ÉÚÍÅÎÑÀÔ + ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÆÁÊÌÙ × ÓÉÓÔÅÍÎÙÈ ÄÅÒÅ×ØÑÈ. óËÒÉÐÔÙ + \cmdname{texconfig}, \cmdname{updmap} É \cmdname{fmtutil} ÔÅÐÅÒØ + ÍÏÄÉÆÉÃÉÒÕÀÔ ÉÎÄÉ×ÉÄÕÁÌØÎÙÅ ÆÁÊÌÙ ÐÏÌØÚÏ×ÁÔÅÌÑ × + \dirname{$HOME/.texlive2005}. + +\item âÙÌÉ ÄÏÂÁ×ÌÅÎÙ ÎÏ×ÙÅ ÐÅÒÅÍÅÎÎÙÅ \envname{TEXMFCONFIG} É + \envname{TEXMFSYSCONFIG} ÄÌÑ ÕËÁÚÁÎÉÑ, ÇÄÅ ÎÁÈÏÄÑÔÓÑ + ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÆÁÊÌÙ (ÐÏÌØÚÏ×ÁÔÅÌØÓËÉÅ É ÓÉÓÔÅÍÎÙÅ). ôÁËÉÍ + ÏÂÒÁÚÏÍ, ×ÁÍ ÎÁÄÏ ÐÅÒÅÍÅÓÔÉÔØ ÔÕÄÁ ×ÁÛÉ ÌÉÞÎÙÅ ËÏÐÉÉ + \filename{fmtutil.cnf} É \filename{texmf.cnf}. ÷ ÌÀÂÏÍ ÓÌÕÞÁÅ + ÐÏÌÏÖÅÎÉÅ ÜÔÉÈ ÆÁÊÌÏ× É ÚÎÁÞÅÎÉÑ ÐÅÒÅÍÅÎÎÙÈ \envname{TEXMFCONFIG} É + \envname{TEXMFSYSCONFIG} ÄÏÌÖÎÙ ÂÙÔØ ÓÏÇÌÁÓÏ×ÁÎÙ. + óÍ. ÒÁÚÄÅÌ~\ref{sec:texmftrees}, \p.\pageref{sec:texmftrees}. + +\item ÷ ÐÒÏÛÌÏÍ ÇÏÄÕ ÍÙ ÏÓÔÁ×ÉÌÉ ÎÅÏÐÒÅÄÅÌ£ÎÎÙÍÉ \verb|\pdfoutput| É + ÄÒÕÇÉÅ ÐÅÒÅÍÅÎÎÙÅ ÐÒÉ ÇÅÎÅÒÉÒÏ×ÁÎÉÉ ÆÁÊÌÏ× × ÆÏÒÍÁÔÅ DVI, ÈÏÔÑ ÄÌÑ + ÜÔÏÇÏ ÉÓÐÏÌØÚÏ×ÁÌÁÓØ ÐÒÏÇÒÁÍÍÁ \cmdname{pdfetex}. ÷ ÜÔÏÍ ÇÏÄÕ, ËÁË + É ÂÙÌÏ ÏÂÅÝÁÎÏ, ÜÔÏ ÕÖÅ ÎÅ ÔÁË. ðÏÜÔÏÍÕ ÅÓÌÉ ×ÁÛ ÄÏËÕÍÅÎÔ + ÉÓÐÏÌØÚÕÅÔ ÄÌÑ ÐÒÏ×ÅÒËÉ ÆÏÒÍÁÔÁ \verb|\ifx\pdfoutput\undefined|, ÅÇÏ + ÎÁÄÏ ÉÚÍÅÎÉÔØ. ÷Ù ÍÏÖÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ ÐÁËÅÔ \pkgname{ifpdf.sty} + (ÒÁÂÏÔÁÅÔ × plain \TeX{} É \LaTeX) ÉÌÉ ÁÎÁÌÏÇÉÞÎÕÀ ÌÏÇÉËÕ. + +\item ÷ ÐÒÏÛÌÏÍ ÇÏÄÕ ÍÙ ÉÚÍÅÎÉÌÉ ÂÏÌØÛÉÎÓÔ×Ï ÆÏÒÍÁÔÏ×, ËÏÔÏÒÙÅ ÓÔÁÌÉ + ×ÙÄÁ×ÁÔØ 8-ÂÉÔÏ×ÙÅ ÓÉÍ×ÏÌÙ. åÓÌÉ ×ÁÍ ×Ó£ ÖÅ ÎÕÖÎÙ ÓÔÁÒÙÊ ×ÁÒÉÁÎÔ Ó + \verb|^^|, ÉÓÐÏÌØÚÕÊÔÅ ÎÏ×ÙÊ ÆÁÊÌ \filename{empty.tcx}: +\begin{verbatim} +latex --translate-file=empty.tcx yourfile.tex +\end{verbatim} + + +\item äÏÂÁ×ÌÅÎÁ ÎÏ×ÁÑ ÐÒÏÇÒÁÍÍÁ \cmdname{dvipdfmx} ÄÌÑ ÐÅÒÅ×ÏÄÁ ÉÚ DVI + × PDF; ÜÔÏ ÁËÔÉ×ÎÏ ÐÏÄÄÅÒÖÉ×ÁÅÍÁÑ ×ÅÒÓÉÑ ÐÒÏÇÒÁÍÍÙ + \cmdname{dvipdfm}, ËÏÔÏÒÁÑ ÐÏËÁ ÅÝ£ ×ËÌÀÞÅÎÁ × ÄÉÓÔÒÉÂÕÔÉ×, ÎÏ ÕÖÅ + ÎÅ ÒÅËÏÍÅÎÄÏ×ÁÎÁ. + +\item äÏÂÁ×ÌÅÎÙ ÎÏ×ÙÅ ÐÒÏÇÒÁÍÍÙ \cmdname{pdfopen} É + \cmdname{pdfclose}, ËÏÔÏÒÙÅ ÐÏÚ×ÏÌÑÀÔ ÐÅÒÅÇÒÕÚÉÔØ ÆÁÊÌ PDF × Adobe + Acrobat Reader, ÎÅ ÐÅÒÅÚÁÐÕÓËÁÑ ÐÒÏÇÒÁÍÍÕ (Õ ÄÒÕÇÉÈ ÐÒÏÇÒÁÍÍ ÄÌÑ + ÞÔÅÎÉÑ ÆÁÊÌÏ× PDF, ×ËÌÀÞÁÑ \cmdname{xpdf}, \cmdname{gv} É + \cmdname{gsview}, ÔÁËÏÊ ÐÒÏÂÌÅÍÙ ÎÉËÏÇÄÁ ÎÅ ÂÙÌÏ). + +\item äÌÑ ÅÄÉÎÏÏÂÒÁÚÉÑ ÍÙ ÐÅÒÅÉÍÅÎÏ×ÁÌÉ ÐÅÒÅÍÅÎÎÙÅ \envname{HOMETEXMF} + É \envname{VARTEXMF} × \envname{TEXMFHOME} É \envname{TEXMFSYSVAR}. + åÓÔØ ÔÁËÖÅ \envname{TEXMFVAR}, ÉÎÄÉ×ÉÄÕÁÌØÎÁÑ ÄÌÑ ËÁÖÄÏÇÏ + ÐÏÌØÚÏ×ÁÔÅÌÑ (ÓÍ. ÐÅÒ×ÙÊ ÐÕÎËÔ ×ÙÛÅ). +\end{itemize} + +\subsubsection{2006--2007} + +÷ 2006--2007 ÇÌÁ×ÎÙÍ ÎÏ×Ï××ÅÄÅÎÉÅÍ ÂÙÌÁ ÐÒÏÇÒÁÍÍÁ Xe\TeX{}, ×ÙÚÙ×ÁÅÍÁÑ +ËÁË \texttt{xetex} ÉÌÉ \texttt{xelatex}; +ÓÍ. \url{http://scripts.sil.org/xetex}. + +úÎÁÞÉÔÅÌØÎÏ ÏÂÎÏ×ÌÅÎÁ ÐÒÏÇÒÁÍÍÁ \MP; ÐÒÅÄÐÏÌÁÇÁÀÔÓÑ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ +ÏÂÎÏ×ÌÅÎÉÑ × ÂÕÄÕÝÅÍ (\url{http://tug.org/metapost/articles}). ôÁËÖÅ +ÏÂÎÏ×̣Πpdf\TeX{} (\url{http://tug.org/applications/pdftex}). + +æÏÒÍÁÔÙ \filename{.fmt} É Ô.Ä. ÔÅÐÅÒØ ÈÒÁÎÑÔÓÑ × ÐÏÄÄÉÒÅËÔÏÒÉÑÈ +\dirname{texmf/web2c}, Á ÎÅ × ÓÁÍÏÊ ÄÉÒÅËÔÏÒÉÉ (ÈÏÔÑ ÄÉÒÅËÔÏÒÉÑ ×Ó£ ÅÝ£ +×ËÌÀÞÅÎÁ × ÐÏÉÓË ÆÏÒÍÁÔÏ×, ÎÁ ÓÌÕÞÁÊ, ÅÓÌÉ ÔÁÍ ÎÁÈÏÄÑÔÓÑ ÓÔÁÒÙÅ +ÆÁÊÌÙ). ðÏÄÄÉÒÅËÔÏÒÉÉ ÎÁÚ×ÁÎÙ ÐÏ ÉÍÅÎÉ ÐÒÏÇÒÁÍÍÙ, ÎÁÐÒÉÍÅÒ, +\filename{tex}, \filename{pdftex}, \filename{xetex}. üÔÏ ÉÚÍÅÎÅÎÉÅ ÎÅ +ÄÏÌÖÎÏ ×ÌÉÑÔØ ÎÁ ÒÁÂÏÔÕ ÐÒÏÇÒÁÍÍ. + +ðÒÏÇÒÁÍÍÁ (plain) \texttt{tex} ÂÏÌØÛÅ ÎÅ ÏÐÒÅÄÅÌÑÅÔ ÐÏ \texttt{\%\&} × +ÐÅÒ×ÏÊ ÓÔÒÏËÅ, ËÁËÏÊ ÆÏÒÍÁÔ ÉÓÐÏÌØÚÏ×ÁÔØ: ÜÔÏ ×ÓÅÇÄÁ ëÎÕÔÏ×ÓËÉÊ +\TeX{} (\LaTeX{} É ÄÒÕÇÉÅ ÅÝ£ ÉÓÐÏÌØÚÕÀÔ \texttt{\%\&}). + +òÁÚÕÍÅÅÔÓÑ, × ÜÔÏÍ ÇÏÄÕ ÂÙÌÉ, ËÁË ÏÂÙÞÎÏ, ÓÏÔÎÉ ÏÂÎÏ×ÌÅÎÉÊ ÐÁËÅÔÏ× É +ÐÒÏÇÒÁÍÍ. ëÁË ÏÂÙÞÎÏ, ÏÂÎÏ×Ì£ÎÎÙÅ ×ÅÒÓÉÉ ÍÏÖÎÏ ÎÁÊÔÉ × ÓÅÔÉ \acro{CTAN} +(\url{http://www.ctan.org}). + +äÅÒÅ×Ï \TL{} ÔÅÐÅÒØ ÈÒÁÎÉÔÓÑ × ÓÉÓÔÅÍÅ Subversion, É Õ ÎÁÓ ÐÏÑ×ÉÌÓÑ +WWW-ÉÎÔÅÒÆÅÊÓ ÄÌÑ ÅÇÏ ÐÒÏÓÍÏÔÒÁ. íÙ ÐÒÅÄÐÏÌÁÇÁÅÍ, ÞÔÏ ÜÔÁ ÓÉÓÔÅÍÁ +ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÎÁ ÄÌÑ ÒÁÚÒÁÂÏÔËÉ × ÂÌÉÖÁÊÛÅÍ ÂÕÄÕÝÅÍ. + +îÁËÏÎÅÃ, × ÍÁÅ 2006 ÇÏÄÁ ôÏÍÁÓ üÓÓÅÒ ÏÂßÑ×ÉÌ Ï ÐÒÅËÒÁÝÅÎÉÉ ÒÁÂÏÔÙ ÎÁÄ +te\TeX ÏÍ (\url{http://tug.org/tetex}). üÔÏ ×ÙÚ×ÁÌÏ ×ÓÐÌÅÓË ÉÎÔÅÒÅÓÁ +Ë \TL, ÏÓÏÂÅÎÎÏ ÓÒÅÄÉ ÒÁÚÒÁÂÏÔÞÉËÏ× ÓÉÓÔÅÍ \acro{GNU}/ìÉÎÕËÓÁ (ÍÙ +ÄÏÂÁ×ÉÌÉ ÓÈÅÍÕ \texttt{tetex}, ËÏÔÏÒÁÑ ÕÓÔÁÎÁ×ÌÉ×ÁÅÔ ÓÉÓÔÅÍÕ, ÐÒÉÍÅÒÎÏ +ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÕÀ te\TeX Õ). íÙ ÎÁÄÅÅÍÓÑ, ÞÔÏ ÜÔÏ ÐÒÉ×ÅÄ£Ô × ËÏÎÅÞÎÏÍ +ÉÔÏÇÅ Ë ÕÌÕÞÛÅÎÉÀ ÒÁÂÏÔÙ × \TeX Å ÄÌÑ ×ÓÅÈ. + +\medskip \noindent +ðÏÓÌÅÄÎÅÅ ÚÁÍÅÞÁÎÉÅ Ï ÐÒÏÛÌÏÍ: ×ÓÅ ×ÙÐÕÓËÉ \TL{} ×ÍÅÓÔÅ Ó +ÄÏÐÏÌÎÉÔÅÌØÎÙÍÉ ÍÁÔÅÒÉÁÌÁÍÉ ×ÒÏÄÅ ÏÂÌÏÖÅË \CD{} ÈÒÁÎÑÔÓÑ ÎÁ +\url{ftp://tug.org/historic/systems/texlive}. +\url{ftp://tug.org/historic/systems/texlive}. + +\subsection{îÁÓÔÏÑÝÅÅ} +\label{sec:tlcurrent} + + +÷ 2008 ÂÙÌÁ ÚÁÎÏ×Ï ÒÁÚÒÁÂÏÔÁÎÁ É ÐÅÒÅÐÉÓÁÎÁ ×ÓÑ ÓÔÒÕËÔÕÒÁ +\TL{}. ðÏÌÎÁÑ ÉÎÆÏÒÍÁÃÉÑ Ï ÕÓÔÁÎÏ×ËÅ ÓÉÓÔÅÍÙ ÔÅÐÅÒØ ÈÒÁÎÉÔÓÑ × +ÔÅËÓÔÏ×ÏÍ ÆÁÊÌÅ \filename{tlpkg/texlive.tlpdb}. + +ðÏÍÉÍÏ ÐÒÏÞÅÇÏ, ÜÔÏ ÎÁËÏÎÅà ÐÏÚ×ÏÌÉÌÏ ÏÂÎÏ×ÌÅÎÉÅ \TL{} ÐÏ ÓÅÔÉ "--- +×ÏÚÍÏÖÎÏÓÔØ, ËÏÔÏÒÁÑ ÍÎÏÇÏ ÌÅÔ ÂÙÌÁ Õ ÐÒÏÇÒÁÍÍÙ MiK\TeX{}. íÙ +ÐÒÅÄÐÏÌÁÇÁÅÍ ÒÅÇÕÌÑÒÎÏ ÏÂÎÏ×ÌÑÔØ ÐÁËÅÔÙ, ÐÏÓÔÕÐÁÀÝÉÅ ÎÁ \CTAN. + +÷ËÌÀÞÅÎ ÎÏ×ÙÊ ×ÁÖÎÙÊ <<Ä×ÉÖÏË>> Lua\TeX\ (\url{http://luatex.org}); +ÐÏÍÉÍÏ ÎÏ×ÏÇÏ ÕÒÏ×ÎÑ ×ÅÒÓÔËÉ, ÜÔÏ ÄÁÅÔ ÐÒÅËÒÁÓÎÙÊ ÓËÒÉÐÔÏ×ÙÊ ÑÚÙË ÄÌÑ +ÉÓÐÏÌØÚÏ×ÁÎÉÑ ËÁË ÉÚÎÕÔÒÉ ÄÏËÕÍÅÎÔÏ× \TeX Á, ÔÁË É ÏÔÄÅÌØÎÏ. + +ðÏÄÄÅÒÖËÁ ÍÎÏÇÉÈ ÐÌÁÔÆÏÒÍ ÎÁ ÏÓÎÏ×Å àÎÉËÓÁ É Windows ÔÅÐÅÒØ ÇÏÒÁÚÄÏ +ÂÏÌÅÅ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÁ. ÷ ÞÁÓÔÎÏÓÔÉ, ÂÏÌØÛÉÎÓÔ×Ï ÓËÒÉÐÔÏ× ÎÁ ÑÚÙËÁÈ +Perl É Lua ÔÅÐÅÒØ ÄÏÓÔÕÐÎÙ ÐÏÄ Windows ÂÌÁÇÏÄÁÒÑ ×ÅÒÓÉÉ PerlÁ, +ÒÁÓÐÒÏÓÔÒÁÎÑÅÍÏÊ Ó \TL{}. + +îÏ×ÙÊ ÓËÒÉÐÔ \cmdname{tlmgr} (ÓÍ. ÒÁÚÄÅÌ~\ref{sec:tlmgr}) ÔÅÐÅÒØ +Ñ×ÌÑÅÔÓÑ ÏÓÎÏ×ÎÙÍ ÉÎÔÅÒÆÅÊÓÏÍ ÄÌÑ ÁÄÍÉÎÉÓÔÒÉÒÏ×ÁÎÉÑ \TL{} ÐÏÓÌÅ +ÕÓÔÁÎÏ×ËÉ. ïÎ ÏÓÕÝÅÓÔ×ÌÑÅÔ ÏÂÎÏ×ÌÅÎÉÅ ÐÁËÅÔÏ× É ÐÅÒÅÇÅÎÅÒÉÒÏ×ÁÎÉÅ +ÆÏÒÍÁÔÏ×, ËÁÒÔ ÛÒÉÆÔÏ× É ÑÚÙËÏ×, ×ËÌÀÞÁÑ ÌÏËÁÌØÎÙÅ ÄÏÂÁ×ÌÅÎÉÑ. + +÷ Ó×ÑÚÉ Ó ÐÏÑ×ÌÅÎÉÅÍ ÐÒÏÇÒÁÍÍÙ \cmdname{tlmgr}, ×ÏÚÍÏÖÎÏÓÔÉ ÐÒÏÇÒÁÍÍÙ +\cmdname{texconfig} ÐÏ ÒÅÄÁËÔÉÒÏ×ÁÎÉÀ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÈ ÆÁÊÌÏ× ÆÏÒÍÁÔÏ× +É ÔÁÂÌÉà ÐÅÒÅÎÏÓÁ ÏÔËÌÀÞÅÎÙ. + +ðÒÏÇÒÁÍÍÁ \cmdname{xindy} (\url{http://xindy.sourceforge.net/}) ÄÌÑ +ÓÏÚÄÁÎÉÑ ÕËÁÚÁÔÅÌÅÊ ÔÅÐÅÒØ ÒÁÂÏÔÁÅÔ ÎÁ ÂÏÌØÛÉÎÓÔ×Å ÐÌÁÔÆÏÒÍ. + +ðÒÏÇÒÁÍÍÁ \cmdname{kpsewhich} ÔÅÐÅÒØ ÍÏÖÅÔ ÓÏÏÂÝÉÔØ ÏÂÏ ×ÓÅÈ ÎÕÖÎÙÈ +ÆÁÊÌÁÈ (ÏÐÃÉÑ \optname{--all}) É ÏÇÒÁÎÉÞÉÔØ ÐÏÉÓË ÏÐÒÅÄÅÌÅÎÎÏÊ +ÐÏÄÄÉÒÅËÔÏÒÉÅÊ (ÏÐÃÉÑ \optname{--subdir}). + +ðÒÏÇÒÁÍÍÁ \cmdname{dvipdfmx} ÔÅÐÅÒØ ÍÏÖÅÔ ÉÚ×ÌÅËÁÔØ ÉÎÆÏÒÍÁÃÉÀ Ï +ÒÁÍËÅ, ÅÓÌÉ ×ÙÚ×ÁÎÁ ËÁË \cmdname{extractbb}; ÜÔÏ ÏÄÎÁ ÉÚ ÐÏÓÌÅÄÎÉÈ +×ÏÚÍÏÖÎÏÓÔÅÊ ÐÒÏÇÒÁÍÍÙ \cmdname{dvipdfm}, ËÏÔÏÒÏÊ ÎÅ ÂÙÌÏ Õ +\cmdname{dvipdfmx}. + +áÌÉÁÓÙ \filename{Times-Roman}, \filename{Helvetica} É Ô.Ä. ÕÂÒÁÎÙ. +òÁÚÎÙÅ ÐÁËÅÔÙ ÏÖÉÄÁÀÔ ÏÔ ÎÉÈ ÒÁÚÎÏÇÏ ÐÏ×ÅÄÅÎÉÑ (ÏÓÏÂÅÎÎÏ ÐÒÉ ÒÁÚÎÙÈ +ËÏÄÉÒÏ×ËÁÈ), É ÍÙ ÎÅ ÎÁÛÌÉ ÓÐÏÓÏÂÁ ÒÅÛÉÔØ ÜÔÕ ÐÒÏÂÌÅÍÕ ÅÄÉÎÏÏÂÒÁÚÎÏ. + +æÏÒÍÁÔ \pkgname{platex} ÕÂÒÁÎ ÉÚ-ÚÁ ËÏÎÆÌÉËÔÁ Ó ÑÐÏÎÓËÉÍ ÐÁËÅÔÏÍ +\pkgname{platex}; ÔÅÐÅÒØ ÏÓÎÏ×ÎÁÑ ÐÏÄÄÅÒÖËÁ ÐÏÌØÓËÏÇÏ ÑÚÙËÁ +ÏÓÕÝÅÓÔ×ÌÑÅÔÓÑ ÞÅÒÅÚ ÐÁËÅÔ \pkgname{polski}. + +ðÕÌÙ ÓÔÒÏËÏ×ÙÈ ËÏÎÓÔÁÎÔ \web\ ÔÅÐÅÒØ ËÏÍÐÉÌÉÒÕÀÔÓÑ × ÓÁÍÉ ÐÒÏÇÒÁÍÍÙ +ÄÌÑ ÕÄÏÂÓÔ×Á ÏÂÎÏ×ÌÅÎÉÊ. + +îÁËÏÎÅÃ, ÄÏÂÁ×ÌÅÎÙ ÉÚÍÅÎÅÎÉÑ, ÓÄÅÌÁÎÎÙÅ äÏÎÁÌØÄÏÍ ëÎÕÔÏÍ × ÅÇÏ +<<îÁÓÔÒÏÊËÅ \TeX Á 2008 ÇÏÄÁ>>, ÓÍ. +\url{http://tug.org/TUGboat/Articles/tb29-2/tb92knut.pdf}. + +\subsection{âÕÄÕÝÅÅ} + +\emph{\TL{} ÎÅ ÓÏ×ÅÒÛÅÎÅÎ!} (é ÎÉËÏÇÄÁ ÎÅ ÂÕÄÅÔ.) íÙ ÐÒÅÄÐÏÌÁÇÁÅÍ +×ÙÐÕÓËÁÔØ ÎÏ×ÙÅ ×ÅÒÓÉÉ, ÄÏÂÁ×ÌÑÑ ÓÐÒÁ×ÏÞÎÙÊ ÍÁÔÅÒÉÁÌ, +ÕÔÉÌÉÔÙ, ÕÓÔÁÎÏ×ÏÞÎÙÅ ÐÒÏÇÒÁÍÍÙ É (ËÏÎÅÞÎÏ) ÎÏ×ÏÅ, ÕÌÕÞÛÅÎÎÏÅ É +ÐÒÏ×ÅÒÅÎÎÏÅ ÄÅÒÅ×Ï ÍÁËÒÏÓÏ× É ÛÒÉÆÔÏ×. üÔÁ ÒÁÂÏÔÁ ÄÅÌÁÅÔÓÑ ÏÞÅÎØ +ÚÁÎÑÔÙÍÉ ÄÏÂÒÏ×ÏÌØÃÁÍÉ × Ó×ÏÂÏÄÎÏÅ ×ÒÅÍÑ, É ÍÎÏÇÏÅ ÏÓÔÁÅÔÓÑ ÓÄÅÌÁÔØ. +åÓÌÉ ×Ù ÍÏÖÅÔÅ ÐÏÍÏÞØ, ÎÅ +ÓÔÅÓÎÑÊÔÅÓØ. óÍ. \url{http://tug.org/texlive/contribute.html}. + +ðÒÉÓÙÌÁÊÔÅ, ÐÏÖÁÌÕÊÓÔÁ, ÚÁÍÅÞÁÎÉÑ É ÐÒÅÄÌÏÖÅÎÉÑ ÐÏ ÁÄÒÅÓÕ:\hfill\null +\begin{quote} +\email{tex-live@tug.org} \\ +\url{http://tug.org/texlive} +\end{quote} + +\medskip +\noindent \textsl{Happy \TeX ing!} + +\end{document} + +%%% Local Variables: +%%% mode: latex +%%% TeX-master: t +%%% LaTeX-command-style: (("." "pdflatex")) +%%% TeX-view-style: (("." "acroread %s.pdf")) +%%% End: diff --git a/Master/texmf/doc/texlive/source/texlive-zh-cn/Makefile b/Master/texmf/doc/texlive/source/texlive-zh-cn/Makefile new file mode 100644 index 00000000000..6541a022547 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-zh-cn/Makefile @@ -0,0 +1,47 @@ +# $Id:$ +# Makefile for TeX Live documentation. Public domain. +TEX = xelatex +doc = texlive-zh-cn +source = $(doc).tex +pdf = $(doc).pdf +lang = chinese + +all: $(pdf) + +env = TEXINPUTS=../texlive-common:../texlive-zh-cn:; export TEXINPUTS; + +$(pdf): $(source) + $(env) $(TEX) $< + $(env) $(TEX) $< + +clean: + rm -f *.aux *.log *.blg *.toc *.out *.lot tex4ht.ps *.4* + rm -f *.xref* *.lg *.idv *.out *.otc *.tmp tmp.* + rm -f $(doc).dvi $(doc).ps + +realclean: clean + rm -f $(doc).pdf + rm -f *.html *.htm $(doc).css *.gif *.jpg + + +insttop = ../../../doc +instfiles = $(doc)*html $(doc).css $(doc).pdf +copyfiles = *.png +install: +# lang=`dirname \`pwd\` | sed 's,.*/,,'`; + lang=$(lang); \ + tldir=`pwd | sed 's,.*/,,'`; \ + instdir=$(insttop)/$$lang/$$tldir; \ + echo tldoc install to $$instdir; \ + for f in $(instfiles); do \ + cmp -s $$f $$instdir/$$f && rm -v $$f && continue; \ + mv -v $$f $$instdir/$$f; \ + done; \ + lang=$(lang); \ + tldir=`pwd | sed 's,.*/,,'`; \ + instdir=$(insttop)/$$lang/$$tldir; \ + for f in $(copyfiles); do \ + cmp -s $$f $$instdir/$$f && continue; \ + cp -v $$f $$instdir/$$f; \ + done; echo "$$instdir" + diff --git a/Master/texmf/doc/texlive/source/texlive-zh-cn/README-live.ZH-CN b/Master/texmf/doc/texlive/source/texlive-zh-cn/README-live.ZH-CN new file mode 100644 index 00000000000..a308e7daaa1 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-zh-cn/README-live.ZH-CN @@ -0,0 +1,34 @@ +TeX Live Guide Translation (Simplified Chinese) +=============================================== + +To compile live.tex, you need: + +1. Xe(La)TeX (and related packages like fontspec) +0.997+ (a recent version is bundled with TeX Live). + +2. xeCJK macro package. + +3. At least one CJK font (with Simpified Chinese +glyphs), preferably two, one for normal text, +another for emphasized text. To change the font, +open tex-live.sty (line 23 - 25): + + \setCJKmainfont[BoldFont=Adobe Heiti Std]{Adobe Song Std} + \setCJKmonofont[Scale=0.9]{Adobe Kaiti Std} + \setCJKfamilyfont{song}[BoldFont=Adobe Heiti Std]{Adobe Song Std} + +Replace "Adobe Heiti Std" and "Adobe Song Std" to +some OpenType/TrueType fonts you already installed. + +4. Type make or simply + + xelatex texlive-zh-cn.tex + +for several times to make sure cross-references are +correctly generated. + +5. If you have any problems, please contact: + gzjjgod at gmail dot com + +jjgod, 2007/01/03. + diff --git a/Master/texmf/doc/texlive/source/texlive-zh-cn/tex-live.sty b/Master/texmf/doc/texlive/source/texlive-zh-cn/tex-live.sty new file mode 100644 index 00000000000..2289ab97ace --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-zh-cn/tex-live.sty @@ -0,0 +1,464 @@ +% $Id: tex-live.sty 9758 2008-07-25 00:47:03Z karl $ +% TeX Live documentation style. Written by many people over many years. +% Public domain. +% +\NeedsTeXFormat{LaTeX2e}[1995/12/01] +\ProvidesPackage{tex-live}[2005/09/24 v1.5 TeX Live documentation style] +% +\RequirePackage{alltt} +\RequirePackage{array} +\RequirePackage{colortbl} +\RequirePackage{comment} +\RequirePackage{float} +\RequirePackage{graphicx} +\RequirePackage{longtable} +\RequirePackage{shortvrb} +\RequirePackage[normalem]{ulem} +\RequirePackage[obeyspaces]{url} +\RequirePackage{xspace} + +% Chinese support (with XeTeX 0.997+) +\RequirePackage{xeCJK} +\def\Status{1} +\parindent=20pt +\defaultfontfeatures{Mapping=tex-text} +\setCJKmainfont[BoldFont=Adobe Heiti Std]{Adobe Song Std} +\setCJKmonofont[Scale=0.9]{Adobe Kaiti Std} +\setCJKfamilyfont{song}[BoldFont=Adobe Heiti Std]{Adobe Song Std} + +\renewcommand\contentsname{目录} +\renewcommand\listfigurename{æ’图列表} +\renewcommand\listtablename{表格列表} +\renewcommand\refname{å‚考文献} +\renewcommand\indexname{索引} +\renewcommand\figurename{图} +\renewcommand\tablename{表} +\renewcommand\partname{部分} +\renewcommand\appendixname{附录} +\renewcommand\abstractname{摘è¦} +\setlength{\parskip}{5pt} + +% +%\RequirePackage{lmodern} +%\usepackage{textcomp}% including \textbullet +\def\p.{p.\,} + +% for a proper \acro command. +\RequirePackage{relsize} +%\DeclareRobustCommand{\acro}[1]{\textscale{.9}{#1}\@} +\def\acro#1{\textscale{.9}{#1}\@} +% +\RequirePackage{fancyvrb} +\DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=\normalsize} +\DefineVerbatimEnvironment{fverbatim}{Verbatim}{fontsize=\footnotesize} +\DefineVerbatimEnvironment{sverbatim}{Verbatim}{fontsize=\small} +\DefineVerbatimEnvironment{boxedverbatim} + {Verbatim}{fontsize=\scriptsize,frame=single} +\DefineVerbatimEnvironment{Verbatim}{Verbatim}{fontsize=\normalsize} +\def\verbatiminput#1{\VerbatimInput[fontsize=\scriptsize]{#1}} +\def\boxedverbatiminput#1{\VerbatimInput[frame=single,fontsize=\scriptsize]{#1}} +\def\listinginput#1#2{\VerbatimInput[fontsize=\scriptsize,firstnumber=#1,numbers=left]{#2}} +\MakeShortVerb\| +% +% +% Done with packages. +% +% Page layout. +\advance\textwidth by 1.1in +\advance\oddsidemargin by -.55in +\advance\evensidemargin by -.55in +% +\advance\textheight by 1in +\advance\topmargin by -.5in +\advance\footskip by -.5in +\pagestyle{headings} +% +% LaTeX parameters. +\renewcommand{\topfraction}{0.85} +\renewcommand{\floatpagefraction}{0.86} +\renewcommand{\textfraction}{0.1} +\renewcommand{\abovecaptionskip}{4pt} +\renewcommand{\belowcaptionskip}{4pt} +\setcounter{tocdepth}{3} +\setcounter{secnumdepth}{3} +\setcounter{topnumber}{5} +\setcounter{totalnumber}{5} +% +% linebreaking, etc. +\hbadness=4000 +\vbadness=4000 +\emergencystretch=.1\hsize +\relpenalty=500 +% +\def\slash{/\penalty\z@\hskip\z@skip } +% +% various sorts of names +\newcommand*{\pkgname}[1]{\textsf{#1}}% package name +\newcommand*{\optname}[1]{\texttt{#1}}% (package,class) option name +\newcommand*{\cmdname}[1]{\textsf{#1}}% command name +\newcommand*{\colname}[1]{\emph{#1}}% collection name +\newcommand*{\dirname}[1]{\path{#1}}% directory name +\newcommand*{\filename}[1]{\path{#1}}% file name +\newcommand*{\envname}[1]{\texttt{#1}}% environment variable name +\newcommand{\code}[1]{\texttt{#1}} +\newcommand{\file}[1]{\texttt{#1}} +\newcommand{\prog}[1]{\textsf{#1}}% same as \cmdname +\newcommand{\samp}[1]{`\texttt{#1}'} +\newcommand{\var}[1]{{\sl #1}}% not \textsl, for roman not typewriter slanted. +\newcommand{\ttvar}[1]{\texttt{\var{#1}}} +% +% underlined command input. +%\def\Ucom#1{% +% \uline{\rule[-.2\baselineskip]{0pt}{.9\baselineskip}\ttfamily #1}} +% bold command input +\def\Ucom#1{{\bfseries\ttfamily #1}} +% +% \CDref is for url's with a #, where we need to write the target url and +% displayed url separately in the input, due to catcode madness. +% (We could simplify/remove this next time, I think.) +% \def\CDref#1#2{\texttt{#1}} +% +% \OnCD is currently for any other reference to a file or directory in +% the distribution. PDF readers only open .pdf files, though, so we +% should change this to only use \href for those. Or more likely use +% different macros in the source. +% \def\OnCD#1{\href{../../../../#1}{\path{#1}}} +% +% \href incorrectly appends .pdf to anything without an extension; these +% definitions using \hyper@linkurl do not, but they fail for .pdf +% references -- which are the only ones that work anyway. So this is +% useless, in practice. +\def\CDref#1#2{\hyper@linkurl{#2}{../../../../#1}} +\def\OnCD#1{\hyper@linkurl{\path{#1}}{../../../../#1}} + +% GUI menu/button/tab sequence: +\def\guiseq#1{\textsf{#1}} +\def\arw{\unskip$\rightarrow$\ignorespaces} +% +% Special names. +\def\dpi{$\,$dpi\xspace} +\def\bs{{\protect\normalfont\ttfamily\char'134}} +\DeclareRobustCommand{\cs}[1]{{\normalfont\ttfamily\char`\\#1}} +\def\Q#1{\par\vskip6pt\leftline{#1}\par} +\def\hyph{-} +% +% many abbreviations. +\newcommand{\CS}{$\mathcal{C}\kern-.1667em\lower.5ex% + \hbox{$\mathcal{S}$}\kern-.075em $} +\def\AFMtoTFM{\cmdname{AFM2TFM}\null} +\def\bv{\emph{Baskerville}} +\let\BV=\bv +\def\Dash{\unskip\nobreak\thinspace---\thinspace\ignorespaces} +\def\dvicopy{\cmdname{dvicopy}} +\def\dvidvi{\cmdname{dvidvi}} +\def\dvips{\cmdname{dvips}} +\def\eTeX{$\varepsilon$-\TeX} +\def\fpTeX{\textrm{fp}\TeX\xspace} +\def\GFtoDVI{\cmdname{GFtoDVI}\null} +\def\GFtoPK{\cmdname{GFtoPK}\null} +\def\GFtype{\cmdname{GFtype}} +\def\GUI{\acro{GUI}\xspace} +\def\KPS{Kpathsea} +\def\La{La} +\def\OMEGA{$\Omega$} +\def\OzMF{OzMF} +\def\OzMP{OzMP} +\def\OzTeX{O\kern-.03em z\kern-.15em\TeX} +\def\PKtype{\cmdname{PKtype}} +\def\PLtoTF{\cmdname{PLtoTF}\null} +\def\ProTeXt{Pro\TeX t} +\def\teTeX{\textrm{te}\TeX\xspace} +\def\TeXLive{\TeX{} Live\xspace} +\def\TFtoPL{\cmdname{TFtoPL}\null} +\def\TK{\TeX\ Collection} +\let\TL=\TeXLive +\def\TypeI{Type~1} +\def\VFtoVP{\cmdname{VFtoVP}\null} +\def\VPtoVF{\cmdname{VPtoVF}\null} +\def\Thanh{H\`an~Th\^e\llap{\raise 0.5ex\hbox{\'{}}}~Th\`anh} +\def\XEmTeX{\textrm{XEm}\TeX\xspace} +\def\XEmacs{\textrm{XEmacs}\xspace} +\def\XeTeX{Xe\TeX\xspace} +\def\Webc{Web2C} +\providecommand*{\CD}{\acro{CD}\xspace} +\providecommand*{\CTAN}{\acro{CTAN}\xspace} +\providecommand*{\DVD}{\acro{DVD}\xspace} +\providecommand*{\GNU}{\acro{GNU}\xspace} +\providecommand*{\ISO}{\acro{ISO}\xspace} +\providecommand*{\HTML}{\acro{HTML}\xspace} +\providecommand*{\MacOSX}{Mac\,\acro{OS\,X}\xspace} +\providecommand*{\PS}{Post\-Script\xspace} +\providecommand*{\TDS}{\acro{TDS}\xspace} +\providecommand*{\dvi}{\acro{DVI}\xspace} +\providecommand*{\web}{\texttt{WEB}\xspace} + +% Include an image. +% #1 - name of image (pictures/#1.jpg, always .jpg please) +% #2 - bb for html +% #3 - width for TeX +% +\def\tlimage#1#2#3{% + \ifnum \Status=2 % html, want relative path in output + \includegraphics[#2]{../../general/texlive-common/pictures/#1.jpg} + \else % not html, handled by TEXINPUTS in Makefile + \includegraphics[width=#3]{pictures/#1.jpg} + \fi + \\[5mm] +} + +\def\tlpng#1#2{% + \ifnum \Status=2 % html, want relative path in output + \includegraphics[bb=0 0 1 1]{#1.png}% + \else % not html, handled by TEXINPUTS in Makefile + \includegraphics[width=#2]{#1.png}% + \fi +} +% +% description-like environment that uses tt instead of bf, and doesn't +% go to the left margin. Without the \hfil, get an underfull box. +% Don't know why \descriptionlabel doesn't. +% +\newenvironment{ttdescription} + {\begin{list}{label must be supplied}{% + \itemsep=0pt % these lists tend to have short descriptions + \parindent=0pt + \let\makelabel=\ttdescriptionlabel}}% + {\end{list}} +\newcommand*\ttdescriptionlabel[1]{\hspace\labelsep + \normalfont\ttfamily #1\hfil} +% +% Likewise, for commands using sans serif. +\newenvironment{cmddescription} + {\begin{list}{label must be supplied}{% + \itemsep=0pt + \let\makelabel=\cmddescriptionlabel}}% + {\end{list}} +\newcommand*\cmddescriptionlabel[1]{\hspace\labelsep + \normalfont\sffamily #1\hfil} + +% General squeezed itemize. +\newenvironment{itemize*}% + {\begin{itemize}% + \setlength{\itemsep}{0pt}% + \setlength{\parskip}{0pt}}% + {\end{itemize}} + +\newsavebox{\wbox} +\newenvironment{warningbox} + {\begin{lrbox}{\wbox} + \begin{minipage}{.95\textwidth}} + {\end{minipage}\end{lrbox}\fbox{\usebox{\wbox}}} +% +% lrbox is used as a representation marking. I changed it to +% lrBox in tne source file, to get closer to logical marking +\newsavebox{\mylrbox} +\newenvironment{lrBox} + {\begin{lrbox}{\mylrbox}} + {\end{lrbox}} + + +% emacs-page output setup +% +\ifx \HCode\UnDef + \providecommand{\Status}{0}% running TeX +\else + \providecommand{\Status}{2}% running TeX4ht +\fi +%\typeout{Status is \Status} +% +\newif\ifSingleColumn +% +% By default, we won't be creating hyperlinks. +\def\href#1#2{#2} +\def\hypertarget#1#2{} +\def\email#1{\href{mailto:#1}{\path{#1}}} % \path comes from url +% +\definecolor{hypercolor}{rgb}{0.5,0.0,0.5} % purplish external links. +% +% +\ifcase\Status + % \Status = 0 + \typeout{TeX Live documentation in DVI format} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 1 + \typeout{TeX Live documentation in PDF format} + \RequirePackage[breaklinks, + colorlinks,linkcolor=hypercolor,citecolor=hypercolor, + urlcolor=hypercolor,filecolor=hypercolor, + bookmarksopen, + %pdfstartview={FitBH -320000}, % fails with acrobat7 + hyperindex] + {hyperref} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + \or + % \Status = 2 + \typeout{TeX Live documentation in HTML format} + \SingleColumntrue + \newenvironment{multicols}[1]{}{} + % read our config file, live4ht.cfg; q.v., for more definitions. + % hyperref load must come after the tex4ht load. + \RequirePackage[live4ht]{tex4ht} + \RequirePackage[tex4ht]{hyperref} \hyperlinkfileprefix{} + % definitions need simplifying for TeX4ht to make relative paths work. + \def\CDref#1#2{\href{../../../../#1}{#2}} + \def\OnCD#1{\href{../../../../#1}{#1}} + \or + % \Status = 3 + \typeout{TeX Live documentation as a Baskerville issue} + \@ifundefined{Fonts}% + {\RequirePackage{ae}}% + {\RequirePackage[T1]{\Fonts}} + \RequirePackage{bvoutln}% outline of baskerville + \SingleColumnfalse + \RequirePackage{multicol} + \or + % \Status = 4 + \typeout{TeX Live documentation as a TUB article} + \@ifundefined{Fonts}% + {\RequirePackage{ae}}% + {\RequirePackage[T1]{\Fonts}} + \SingleColumnfalse + \newenvironment{multicols}[1]{}{} +\fi +% +\ifnum \Status=4 +\else + \RequirePackage{texnames} + \providecommand\TeXXeT{\TeX-{}-% + \kern-.1emX\kern-.125em\lower.5ex\hbox{E}\kern-.1667emT\@} + \def\MP{MetaPost} + \let\mf\MF + \newcommand\ConTeXt{C\kern-.0333emon\-\kern-.0667em\TeX\kern-.0333emt} + \newcommand\MIKTEX{MiK\kern-.025em \TeX}% per www.miktex.org + % from pictex.tex: + \ifx\PiC\undefined \def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC} \fi + \ifx\PiCTeX\undefined \def\PiCTeX{\PiC\kern-.11em\TeX} \fi +\fi +% +% hacking at sections etc., to pay attention to baskerville status +\newcommand{\@condend@multicols}{% + \ifSingleColumn + \else + \def\@tempa{multicols}% + \ifx\@tempa\@currenvir + \end{multicols}% + \fi + \fi +} +\let\Section\section +\renewcommand{\section}{% + \@ifstar + {\Section*}% + {% + \@condend@multicols + \@dblarg\@full@section + }% +} +\def\@full@section[#1]#2{% + \Section[#1]{#2}% + \ifSingleColumn\else\begin{multicols}{2}\fi +} +\let\SubSection\subsection +\renewcommand{\subsection}{% + \@ifstar{\SubSection*}% + {% + \@condend@multicols + \@dblarg\@full@subsection + } +} +\def\@full@subsection[#1]#2{% + \SubSection[#1]{#2}% + \ifSingleColumn\else\begin{multicols}{2}\fi +} + +% calm things down a bit if we're in a multiple-column version +\ifSingleColumn +\else + \def\@listI{\leftmargin\leftmargini + \parsep \z@ + \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ + \itemsep \z@ \@plus .1\p@ + } + \let\@listi\@listI + \@listi + \def\@listii{\leftmargin\leftmarginii + \labelwidth\leftmarginii\advance\labelwidth-\labelsep + \topsep 2\p@ \@plus 1\p@ \@minus 1\p@ + \parsep \z@ + \itemsep \z@ \@plus .1\p@ + } + \def\@listiii{\leftmargin\leftmarginiii + \labelwidth\leftmarginiii\advance\labelwidth-\labelsep + \topsep 1\p@ \@plus 1\p@ \@minus 1\p@ + \parsep \z@ + \partopsep \z@ + \itemsep \topsep + } + \def\@listiv{\leftmargin\leftmarginiv + \labelwidth\leftmarginiv\advance\labelwidth-\labelsep + } + \def\@listv{\leftmargin\leftmarginv + \labelwidth\leftmarginv\advance\labelwidth-\labelsep + } + \def\@listvi{\leftmargin\leftmarginvi + \labelwidth\leftmarginvi\advance\labelwidth-\labelsep + } +\fi +% +% array package stuff +\def\arraybackslash{\let\\=\@arraycr} +\newcolumntype{P}[1]{>{\raggedright\arraybackslash}p{#1}} +% +% shaded rows (using facilities of colortbl) +% +\definecolor{pale}{gray}{.9} +\newcount\colrow +\gdef\RowColor{pale} +\def\SetRowColor{% + \rowcolor{\RowColor}% + \global\advance\colrow by1\relax + \ifodd\colrow + \gdef\RowColor{pale}% + \else + \gdef\RowColor{white}% + \fi +} +% redefine to hack up a reference even though we don't need it... +\renewcommand\@bibitem[1]{\if@filesw \immediate\write\@auxout + {\string\bibcite{#1}{?}}\fi\ignorespaces} +% +% \unknownTeXlive is a dummy texlive entry for the biblio +\newcommand\unknownTeXlive[2][\relax]{\textbf{\textsc{unknown}}% + \global\@all@unknown\expandafter{\the\@all@unknown{#2}}% +} +\newtoks\@all@unknown +\global\@all@unknown{} +\AtEndDocument{\@message@unknowns} +\def\@message@unknowns{\edef\@tempa{\the\@all@unknown}% + \ifx\@tempa\@empty + \else + \def\@tempa{*** TeX live package location of }% + \expandafter\@output@unknowns\the\@all@unknown\@empty + \fi +} +\def\@output@unknowns#1{\edef\@tempb{#1}% + \ifx\@tempb\@empty + \typeout{ unknown}% + \else + \message{\@tempa#1,}% + \def\@tempa{}% + \expandafter\@output@unknowns + \fi +} + + +% Silence font warnings about no bold typewriter in LM. +\def\@font@warning#1{}% + +% Silence hyperref warnings about \kern. +\def\HyPsd@Warning#1{}% + +\endinput diff --git a/Master/texmf/doc/texlive/source/texlive-zh-cn/texlive-zh-cn.tex b/Master/texmf/doc/texlive/source/texlive-zh-cn/texlive-zh-cn.tex new file mode 100644 index 00000000000..c444dca64c2 --- /dev/null +++ b/Master/texmf/doc/texlive/source/texlive-zh-cn/texlive-zh-cn.tex @@ -0,0 +1,2576 @@ +% $Id$ +% TeX Live documentation. Originally written by Sebastian Rahtz and +% Michel Goossens, now maintained by Karl Berry and others. +% Translated by Jjgod Jiang , +% Jinsong Zhao , +% Yue Wang +% Helin Gai +% Public domain. +% +\documentclass{article} +\let\tldocenglish=1 % for live4ht.cfg + +\usepackage{tex-live, indentfirst} + +\begin{document} + +\title{% + {\huge \textit{\TeX\ Live 指å—}\\\smallskip}% + {\LARGE \textsf{\TL{} 2008}} +} + +\author{Karl Berry 编写 \\[3mm] + \url{http://tug.org/texlive/} + } + +\date{2008 å¹´ 7 月} + +\maketitle + +\begin{multicols}{2} +\tableofcontents +%\listoftables +\end{multicols} + +\section{简介} +\label{sec:intro} + +\subsection{\TeX\ Live 与 \TeX\ Collection} + +本文档æè¿° \TL{} 软件的主è¦åŠŸèƒ½å’Œç‰¹æ€§ï¼Œ\TL{} 是 \TeX{} åŠå…¶ç›¸å…³ç¨‹åºåœ¨ +\acro{GNU}/Linux åŠå…¶ä»–ç±» Unix 系统ã€\MacOSX\ å’Œ Windows +系统下的一套å‘行版。 + +ä½ å¯ä»¥ç›´æŽ¥ä¸‹è½½ \TL{},也å¯ä»¥åœ¨ \TeX{} 用户组织给会员分å‘çš„ \TK{} +\DVD 中找到。第 \ref{sec:tl-coll-dists} 节中,简è¦åœ°ä»‹ç»äº† +\DVD 的内容。这两套å‘行版都是用户组织共åŒå作完æˆçš„。 +这篇文档, 主è¦ä»‹ç» \TL{} 本身。 + +\TL{} 包括了 \TeX{}, \LaTeXe{}, \ConTeXt, \MF, \MP, \BibTeX{} +等许多å¯æ‰§è¡Œç¨‹åºï¼›ç§ç±»ç¹å¤šçš„å®åŒ…ã€å­—体和文档,并支æŒä¸–界上许多 +ä¸åŒçš„语言。 + +\TL{} ä¸­çš„å®‰è£…åŒ…å®šæœŸæ ¹æ® \acro{CTAN}:\url{http://www.ctan.org} +上的内容进行更新。 + +文档末尾的第 \ref{sec:history} 节 (第 \pageref{sec:history} 页) +介ç»äº†è¿™ä¸€ç‰ˆ \TL{} çš„é‡è¦æ”¹å˜ã€‚ + +\subsection{æ“作系统支æŒ} +\label{sec:os-support} + +\TL{} 为包括 \MacOSX 在内的多ç§åŸºäºŽ Unix çš„æ“作系统æ供了å¯æ‰§è¡Œ +文件。它还包å«äº†æºä»£ç ï¼Œå¯ä¾›åœ¨æ²¡æœ‰æä¾›å¯æ‰§è¡Œæ–‡ä»¶çš„å¹³å°ä¸Šç¼–译安装。 + +至于 Windows,\TL{} ä»…æ”¯æŒ Windows 2000 或åŽç»­ç‰ˆæœ¬ã€‚ +ä¸å†æ”¯æŒ Windows 9\textit{x}, ME å’Œ NT。 +因为这一改å˜ï¼ŒWindows 支æŒç›¸å¯¹äºŽ Unix 支æŒç³»ç»Ÿè€Œè¨€ä¸å†éœ€è¦å¾ˆå¤šçš„ +ç‰¹æ®Šå¯¹å¾…ã€‚æˆ‘ä»¬æ²¡æœ‰åŒ…å« 64 ä½çš„ Windows å¯æ‰§è¡Œæ–‡ä»¶ï¼Œä¸è¿‡ 32 ä½çš„å¯ +执行文件也能 64 ä½çš„系统上正常è¿è¡Œã€‚ + +除了 \TL{} 以外,Windows å’Œ \MacOSX 用户还有其它的选择,请å‚考第 +\ref{sec:tl-coll-dists} 节。 + +\subsection{\protect\TL{} 的基本安装} +\label{sec:basic} + +ä½ å¯ä»¥ä½¿ç”¨ \DVD{} æ–¹å¼æˆ–者网络方å¼æ¥å®‰è£… \TL{}。 +通过网络的安装程åºæœ¬èº«éžå¸¸å°ï¼Œå®ƒå¯ä»¥ä»Žç½‘上下载所有的你所è¦æ±‚的软 +件包。网络安装程åºå¯¹ä»…使用 \TL{} 一å°éƒ¨åˆ†çš„用户æ¥è¯´éžå¸¸é€‚宜。 + +\DVD{} 安装程åºå¯ä»¥æŠŠ \TL{} 安装到你的本地ç£ç›˜ä¸Šï¼Œä¹Ÿå¯ä»¥ç›´æŽ¥ä»Ž +\DVD{} 上è¿è¡Œ \TL{} (其实如果你的系统支æŒæŒ‚è½½ DVD é•œåƒï¼Œä½ ä¹Ÿå¯ä»¥ +从 \DVD é•œåƒä¸Šè¿è¡Œ)。 + +\noindent 安装方法将在下é¢çš„章节介ç»ï¼Œè¿™é‡Œæ供一个快速入门: + +\begin{itemize*} + +\item 安装脚本的å称是 \filename{install-tl}。它å¯ä»¥åœ¨ \GUI{} æ¨¡å¼ +(Windows 下的默认模å¼) å’Œæ–‡æœ¬æ¨¡å¼ (其它系统下默认模å¼) ä¸‹å·¥ä½œï¼Œä½ å¯ +以分别使用 \code{-gui} 或 \code{-no-gui} 命令行å‚æ•°æ¥å¼ºåˆ¶ä»¥æŸä¸€æ¨¡å¼ +è¿è¡Œç¨‹åºã€‚ + +\item 安装完æˆåŽå¯ä»¥å¾—到一个å为 \prog{tlmgr} 的程åºï¼š`\TL\ Manager'。 +和安装程åºä¸€æ ·ï¼Œå®ƒå¯ä»¥åœ¨ \GUI{} 模å¼æˆ–文本模å¼ä¸‹è¿è¡Œã€‚ä½ ä¸ä½†å¯ä»¥ç”¨å®ƒ +æ¥å®‰è£…或å¸è½½è½¯ä»¶åŒ…,还å¯ä»¥ç”¨æ¥å®Œæˆå„ç§é…置工作。 + +\end{itemize*} + + +\subsection{获得帮助} +\label{sec:help} + +\TeX{} 社群是活跃而å‹å¥½çš„,几乎所有认真的æ问都能得到回答。尽管如此,这ç§ç”±å¿—愿者 +和业余读者组æˆçš„技术支æŒä»ç„¶æ˜¾å¾—ä¸å¤ªæ­£å¼ï¼Œæ‰€ä»¥ï¼Œåœ¨æé—®å‰æœ€å¥½åšå¥½åŠŸè¯¾ã€‚(如果你更喜欢 +有ä¿éšœçš„商业性技术支æŒï¼Œå¯ä»¥æ”¾å¼ƒ \TL{},改为购买商业 \TeX{} 系统,在 +\url{http://tug.org/interest.html#vendors} 上有一份销售商的列表。) + +按照推è使用的顺åºï¼Œæˆ‘们列出了这样一份资æºåˆ—表: + +\begin{description} +\item [èµ·æ­¥] 如果你刚刚接触 \TeX,\url{http://tug.org/begin.html} +这个网页æ供了这个系统的简短介ç»ã€‚ + +\item [\TeX{} \acro{FAQ}] 这套庞大的 \TeX{} \acro{FAQ} 对å„ç§å„æ ·çš„ +问题——从最基础到最晦涩的——都给予了简明的回答,它在 \TL{} çš„ +\OnCD{texmf-doc/doc/english/FAQ-en/html/index.html},也å¯ä»¥åœ¨ +\url{http://www.tex.ac.uk/faq} 网站上找到。有问题时请先看看这里能å¦æ‰¾ +到解答。 + +\item [\TeX{} Catalogue] 如果你在寻找æŸä¸ªç‰¹å®šçš„å®åŒ…ã€å­—体ã€ç¨‹åºç­‰ç­‰ï¼Œ\TeX{} +Catalogue 就是你首先该找的地方。这里是所有 \TeX{} 相关内容的一个巨大集åˆã€‚å‚è§ +\url{http://www.ctan.org/help/Catalogue/}。 + +\item [\TeX{} 网上资æº] \url{http://tug.org/interest.html} 页é¢ä¸Šæœ‰ +许多和 \TeX{} 相关的链接,包括讨论这个系统方方é¢é¢çš„许多书ç±ã€æ‰‹å†Œå’Œæ–‡ç« ã€‚ + +\item [支æŒä¿¡æ¯çš„å½’æ¡£] 最é‡è¦çš„两个技术支æŒè®ºå›æ˜¯ Usenet 的新闻组 +\url{news:comp.text.tex} 和邮件列表 \email{texhax@tug.org}。它们的内容 +归档中有多年以æ¥çš„æ问和回答供你æœç´¢ã€‚ä½ å¯ä»¥åˆ†åˆ«ä»Ž +\url{http://groups.google.com/groups?group=comp.text.tex} å’Œ +\url{http://tug.org/mail-archives/texhax} 进行查询。当然,一般性的æœç´¢ +æ–¹å¼ï¼Œæ¯”如用 \url{http://google.com} 找找,总没有å处。 + +\item [æé—®] 如果你还是找ä¸åˆ°ç­”案,就å¯ä»¥é€šè¿‡ Google 或者你的新闻组阅读器在 +\dirname{comp.text.tex} 上æ问,或者å‘é€é‚®ä»¶åˆ° \email{texhax@tug.org}。 +ä¸è¿‡ï¼Œåœ¨æ问之å‰\emph{请一定}先阅读 \acro{FAQ} 上的这一æ¡ï¼š +\url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion}, +它能æ高你获得回答的å¯èƒ½æ€§ã€‚ + +\item [\TL{} 技术支æŒ] 如果你需è¦æŠ¥å‘Š bug,或者æ出对 \TL{} çš„å‘è¡Œã€å®‰è£…或 +文档的建议和æ„è§ï¼Œå¯ä»¥ä½¿ç”¨ \email{tex-live@tug.org} 这个邮件列表。ä¸è¿‡ï¼Œå¦‚果问题 +是针对 \TL{} 中包å«çš„æŸä¸ªç‰¹å®šç¨‹åºï¼Œé‚£æœ€å¥½è¿˜æ˜¯å†™ä¿¡ç»™è¿™ä¸ªç¨‹åºçš„维护者或邮件列表。 +用 \code{-{}-help} å‚æ•°æ¥è¿è¡Œç¨‹åºéƒ½ä¸€èˆ¬èƒ½å¾—到用æ¥æŠ¥å‘Šå…¶ bug 的地å€ã€‚ + +\end{description} + +å¦ä¸€æ–¹é¢ï¼Œä½ ä¹Ÿä¸å¦¨å¸®åŠ©å…¶ä»–有问题的朋å‹ï¼Œ\dirname{comp.text.tex} 与 +\code{texhax} 都是对所有人开放的,请尽管å‚与进去,在你能力所åŠçš„范围内æ供帮助。 + +% don't use \TL so the \uppercase in the headline works. Also so +% tex4ht ends up with the right TeX. Likewise the \protect's. +\section{\protect\TeX\protect\ Live 概览} +\label{sec:overview-tl} + +这个å°èŠ‚æ述的是 \TL{} 的内容,以åŠåŒ…å« \TL{} çš„ \TK{}。 + +\subsection{\TL, pro\TeX{}t, Mac\TeX\ 的大集åˆï¼š\TK} +\label{sec:tl-coll-dists} + +\TK{} çš„ \DVD{} 包å«äº†ä»¥ä¸‹å†…容: + +\begin{description} + +\item [\TL] 是一个完整的 \TeX{} 系统,它å¯ä»¥ç›´æŽ¥åœ¨å…‰ç›˜ä¸Šè¿è¡Œï¼Œä¹Ÿå¯ä»¥å®‰è£…在本 +地ç£ç›˜ä¸Šã€‚ + +\item [Mac\TeX] 在 \TL{} 的基础上增加了原生的 \MacOSX\ 的安装程åºå’Œä¸€äº›å…¶å®ƒçš„ +Mac 应用程åºã€‚它的主页在 \url{http://www.tug.org/mactex/}。 + +\item [pro\TeX{}t] 是 Windows 下的 \MIKTEX\ å‘行版的一个增强版本。\ProTeXt\ 在 +\MIKTEX\ 基础上增加了一些工具,简化了安装。它完全独立于 \TL{},有其 +自己的安装步骤。\ProTeXt\ 的主页在 \url{http://tug.org/protext}。 + +\item [CTAN] 一份 \CTAN{} 仓库的快照。 + +\item[\texttt{texmf-extra}] 一个æä¾›é¢å¤–çš„é…套软件包的目录。 + +\end{description} + +\CTAN{}, \pkgname{protext} å’Œ \dirname{texmf-extra} 并ä¸ä¸€å®šéµå¾ª \TL{} +的版æƒå议,因此在分å‘或修改时è¦æ ¼å¤–地å°å¿ƒã€‚ + +\subsection{\TL{} 的顶层目录} +\label{sec:tld} + +这里是 \TL{} å‘行版顶层目录的一个简短的列表和æ述。注æ„在 \pkgname{live} +\DVD\ 中,整个 \TL{} 目录结构都存放于 \dirname{texlive} å­ç›®å½•ä¸­ï¼Œè€Œéž +光盘的顶层目录下。 + +\begin{ttdescription} +\item[bin] \TeX{} 系统程åºï¼ŒæŒ‰å¹³å°ç»„织。 +% +\item[readme.html] 网页,æ供了多ç§è¯­è¨€çš„简介和有用的链接。 +% +\item[source] 所有程åºçš„æºä»£ç ï¼ŒåŒ…括主è¦çš„ \Webc{} \TeX{} å’Œ \MF{} + å‘行版。 +% +\item[support] å„类辅助性å®åŒ…与程åºã€‚这些内容\emph{ä¸ä¼š}自动安装。 +包括é…套的编辑器和 \TeX\ çš„å‰ç«¯ (外壳) 程åºã€‚ +% +\item[texmf] è§ä¸‹æ–‡çš„ \dirname{TEXMFMAIN}。 +% +\item[texmf-dist] è§ä¸‹æ–‡çš„ \dirname{TEXMFDIST}。 +% +\item[texmf-doc] 这个目录树用于存放和具体程åºã€å®åŒ…关系ä¸å¤§çš„纯粹 +文档,按语言组织。 +% +\item[tlpkg] 用æ¥ç»´æŠ¤å®‰è£…程åºæ‰€ç”¨åˆ°çš„脚本,程åºå’Œæ•°æ®ã€‚还内置了 +Windows 下 Perl å’Œ Ghostscript 的专有版本,它们ä¸èƒ½åœ¨ \TL 外使用。 +还有一个新的 Windows PostScript 阅读器 PSView。 +\end{ttdescription} + +上述目录之外,安装脚本和 (多ç§è¯­è¨€çš„) \filename{README} 文件也存放在å‘行版的顶层目录下。 + +\dirname{texmf-doc} 目录包å«äº†é‚£äº›ä¸éš¶å±žäºŽä»»ä½•ç‰¹å®šå®åŒ…或程åºçš„文档。 +程åºçš„文档 (手册,man page, Info 文件等) 在 \dirname{texmf/doc} +目录下,因为这些程åºæœ¬èº«æ˜¯å±žäºŽ \dirname{texmf} 目录的。\TeX\ å®åŒ…与格å¼æ–‡ä»¶ +的文档则放在 \dirname{texmf-dist/doc} 目录。但ä¸ç®¡æ”¾åœ¨å“ªä¸ªåœ°æ–¹ï¼Œä½ éƒ½å¯ä»¥ä½¿ç”¨ +\cmdname{texdoc} 或 \cmdname{texdoctk} 程åºæ¥å¯»æ‰¾è¿™äº›æ–‡æ¡£ã€‚顶层目录下的 +\OnCD{doc.html} 文件中æ供的完整的链接也会有所帮助。 + +\TL\ 本身的文档在 \dirname{texmf-doc} 目录下,有以下这些语言的版本: + +\begin{itemize*} +\item{简体中文:} \OnCD{texmf-doc/doc/chinese/texlive-zh-cn} +\item{æ·å…‹/斯洛ä¼å…‹è¯­:} \OnCD{texmf-doc/doc/czechslovak/texlive-cz} +\item{英语:} \OnCD{texmf-doc/doc/english/texlive-en} +\item{法语:} \OnCD{texmf-doc/doc/french/texlive-fr} +\item{德语:} \OnCD{texmf-doc/doc/german/texlive-de} +\item{波兰语:} \OnCD{texmf-doc/doc/polish/texlive-pl} +\item{俄语:} \OnCD{texmf-doc/doc/russian/texlive-ru} +\end{itemize*} + + +\subsection{预定义的 texmf 目录树概览} +\label{sec:texmftrees} + +本å°èŠ‚列出了系统中用于指定 texmf 目录的所有预定义å˜é‡åŠå…¶ç”¨é€”, +还有一个 \TL{} 系统的默认布局。\texttt{texconfig conf} å‘½ä»¤å¯ +以列出这些å˜é‡çš„值,这样你å¯ä»¥å¾ˆå®¹æ˜“找到它们和你所安装到的目录 +å称的对应关系。 + +\begin{ttdescription} +\item [TEXMFMAIN] 存储系统核心部件的目录树,包括辅助脚本 (比如 +\verb+web2c/mktexdir+) 和其他支æŒæ–‡ä»¶å’Œæ–‡æ¡£ã€‚ +这个目录ä¸åŒ…å« \TeX\ æ ¼å¼æ–‡ä»¶å’Œå®åŒ…。 +\item [TEXMFDIST] 存储主è¦çš„å®åŒ…ã€å­—体等等,å³ä¸€å¼€å§‹å°±åœ¨å‘行版中包括的而éžè‡ªå·± +åŽç»­æ·»åŠ çš„那些文件。 +\item [TEXMFLOCAL] 系统管ç†å‘˜ç”¨æ¥å®‰è£…供整个系统使用的é¢å¤–的或更新过的å®åŒ…ã€å­—体的目录。 +\item [TEXMFHOME] 给用户存放它们自己独立安装的的å®åŒ…ã€å­—体等等。 +这个å˜é‡æ ¹æ®ä¸åŒçš„用户选择ä¸åŒçš„主目录。 +\item [TEXMFCONFIG] ç»™ \verb+texconfig+ã€\verb+updmap+ã€å’Œ \verb+fmtutil+ +这些程åºå­˜å‚¨ä¿®æ”¹è¿‡çš„é…置文件。默认在 \envname{TEXMFHOME} 目录树下。 +\item [TEXMFSYSCONFIG] ç»™ \verb+texconfig-sys+ã€\verb+updmap-sys+ å’Œ +\verb+fmtutil-sys+ 这些程åºå­˜å‚¨ä¿®æ”¹è¿‡çš„文件. +\item [TEXMFVAR] 这个目录是给 \verb+texconfig+ã€\verb+updmap+ å’Œ + \verb+fmtutil+ 存储 (缓存) æ ¼å¼æ–‡ä»¶ã€ç”Ÿæˆ map 文件这类è¿è¡Œæ—¶æ•°æ®çš„。默认在 + \envname{TEXMFHOME} 目录下。 +\item [TEXMFSYSVAR] ç»™ \verb+texconfig-sys+ã€\verb+updmap-sys+ å’Œ +\verb+fmtutil-sys+ 还有 \verb+tlmgr+ 这几个命令存储ã€ç¼“å­˜è¿è¡Œæ—¶ä½¿ç”¨çš„æ ¼å¼æ–‡ä»¶å’Œ +生æˆçš„ map 文件。 +\end{ttdescription} + +\noindent +默认的目录结构: +\begin{description} + \item[全系统根目录] å¯ä»¥åŒ…å«å¤šä¸ª \TL{} 版本: + \begin{ttdescription} + \item[2007] 上一个版本。 + \begin{ttdescription} + \item [...] + \end{ttdescription} + \item[2008] 当å‰ç‰ˆæœ¬ã€‚ + \begin{ttdescription} + \item [bin] ~ + \begin{ttdescription} + \item [i386-linux] \GNU/Linux 二进制文件 + \item [...] + \item [universal-darwin] \MacOSX 二进制文件 + \item [win32] Windows 二进制文件 + \end{ttdescription} + \item [texmf] 这是 \envname{TEXMFMAIN}。 + \item [texmf-dist] \envname{TEXMFDIST} + \item [texmf-doc] \envname{TEXMFDOC} + \item [texmf-var] \envname{TEXMFSYSVAR} + \item [texmf-config] \envname{TEXMFSYSCONFIG} + \end{ttdescription} + \item [texmf-local] \envname{TEXMFLOCAL} 用æ¥å­˜æ”¾åœ¨ä¸åŒç‰ˆæœ¬é—´å…±äº«çš„æ•°æ®ã€‚ + \end{ttdescription} + \item[用户主 (home) 目录] (\texttt{\$HOME} 或 + \texttt{\%USERPROFILE\%}) + \begin{ttdescription} + \item[.texlive2007] 给上个版本的,个人生æˆå’Œé…置的数æ®ã€‚ + \item[.texlive2008] 给这个版本的,个人生æˆå’Œé…置的数æ®ã€‚ + \begin{ttdescription} + \item [texmf-var] \envname{TEXMFVAR} + \item [texmf-config] \envname{TEXMFCONFIG} + \end{ttdescription} + \item[texmf] \envname{TEXMFHOME} 个人的å®åŒ…文件。 + \textit{等等。} + \end{ttdescription} +\end{description} + + +\subsection{\protect\TeX\ 的扩展版本} +\label{sec:tex-extensions} + +\TeX{} çš„å¼€å‘å·²ç»å†»ç»“了,仅仅修改除去å‘现的æžå…¶å°‘é‡çš„错误。 +在现在以åŠå¯é¢„è§çš„未æ¥ï¼Œ\TL\ 中ä»ç„¶æä¾› \prog{tex} 这个程åºã€‚ +除此以外,\TL{} 包括了一些建立在 \TeX\ 基础上的的扩展程åºã€‚ +\TL{} 包括下列 \TeX\ 扩展版本: + +\begin{description} + +\item [\eTeX] 为 \TeX\ 增加了一套新的原语 (primitive)。 +\label{text:etex} (包括å®å±•å¼€ï¼Œå­—符扫æ,mark 的分类,é¢å¤–的调试功能,等等) +以åŠç”¨äºŽåŒå‘排版的 \TeXXeT{} 扩展模å¼ã€‚在默认模å¼ä¸‹ï¼Œ\eTeX{} 是与原始的 \TeX\ +100\% 兼容的。å‚è§ \OnCD{texmf-dist/doc/etex/base/etex_man.pdf}。 + +\item [pdf\TeX] 在 \eTeX\ 扩展的基础上构建,在 \dvi{} 输出之外增加对 +\acro{PDF} 输出的支æŒã€‚ +这是针对 \prog{etex}, \prog{latex} 或 \prog{pdflatex} 这些格å¼ä½¿ç”¨çš„缺çœç¨‹åºã€‚ +è§ \url{http://www.pdftex.org}。它的手册在 \OnCD{texmf/doc/pdftex/manual}。展 +示其一些功能的例å­å¯ä»¥åœ¨ \OnCD{texmf/doc/pdftex/manual/samplepdf/samplepdf.tex} +中找到。 + +\item [Lua\TeX] 是 pdf\TeX\ 指定的åŽç»§è€…,尽å¯èƒ½å¯¹ pdf\TeX\ ä¿æŒå‘å‰å…¼å®¹ã€‚ +它åŒæ—¶ä¹Ÿæ˜¯ Aleph (è§åŽ) 的继任者。 +它内置的 Lua 语言解释器 (\url{http://www.lua.org}) 为许多 \TeX{} 的棘手问题 +æ供了优雅的解决方案。 +当以 \filename{texlua} 命令执行时,它就åƒä¸€ä¸ªæ ‡å‡†çš„ Lua 解释器一样工作, +所以,Lua\TeX\ 在 \TL\ 中也被作为 Lua 程åºçš„解释器。 +è§ \url{http://www.luatex.org} å’Œ \OnCD{texmf-dist/doc/luatex/luatexref-t.pdf}。 + +\item [Xe\TeX] 通过第三方库,增加对 Unicode 输入文本和 OpenType 字体的支æŒï¼Œ +能够直接使用系统字体。å‚è§ \url{http://scripts.sil.org/xetex}。 + +\item [\OMEGA\ (Omega)] 基于 Unicode (16 ä½å­—符集),因而åŒæ—¶æ”¯æŒå¤„ç†ä¸–界上 +几乎所有的语言。它åŒæ—¶è¿˜æ”¯æŒæ‰€è°“çš„ `\OMEGA{} Translation Processes' (\acro{OTP}), +用于对任æ„输入进行å¤æ‚çš„å˜æ¢æ“作。å‚è§ +\OnCD{texmf-dist/doc/omega/base/doc-1.8.tex} (文档的更新å¯èƒ½ä¸æ˜¯å¾ˆåŠæ—¶)。 + +\item [Aleph] å°† \OMEGA\ 与 \eTeX\ 扩展åˆå¹¶åˆ°ä¸€èµ·å¾—到的。 +在 \OnCD{texmf-dist/doc/aleph/base} å¯ä»¥æ‰¾åˆ°ä¸€äº›ç®€çŸ­çš„文档。 + +\end{description} + + +\subsection{\protect\TL\ 中其他值得一æ的程åº} + +这里是在 \TL{} 中其他的一些常用程åºï¼š + +\begin{cmddescription} + +\item [bibtex] å‚考文献支æŒã€‚ + +\item [makeindex] 索引支æŒã€‚ + +\item [dvips] å°† \dvi{} 转æ¢ä¸º \PS{}。 + +\item [xdvi] X Window System 下的 \dvi{} 阅读器。 + +\item [dvilj] HP LaserJet 系列打å°æœºçš„ \dvi{} 驱动。 + +\item [dv2dt, dt2dv] \dvi{} 和纯文本之间的相互转æ¢ã€‚ + +\item [dviconcat, dviselect] 从 \dvi{} 文件中å¤åˆ¶å’Œç²˜è´´é¡µé¢ã€‚ + +\item [dvipdfmx] å°† \dvi{} 转æ¢ä¸º \acro{PDF},是 (å‰é¢æ到过的) +pdf\TeX\ 的一套替æ¢æ–¹æ¡ˆã€‚å‚è§ \pkgname{ps4pdf} å’Œ +\pkgname{pdftricks} 软件包以了解其他的方案。 + +\item [psselect, psnup, \ldots] \PS{} +实用程åºã€‚ + +\item [lacheck] \LaTeX{} 语法检查器。 + +\item [texexec, texmfstart] Con\TeX{}t å’Œ \acro{PDF} 处ç†å·¥å…·ã€‚ + +\item [tex4ht] \TeX{} 到 \acro{HTML} (还有 \acro{XML} 等其他格å¼) +的转æ¢å™¨ã€‚ + +\end{cmddescription} + + +\subsection{\TL\ 中的字体} +\label{sec:tl-fonts} + +\TL{} 中包括了很多的高质é‡çŸ¢é‡å­—体,å‚è§ \url{http://tug.org/fonts} å’Œ +\OnCD{texmf-doc/english/free-math-fonts-survey}。 + +\section{安装} +\label{sec:install} + +\subsection{å¯åŠ¨å®‰è£…程åº} +\label{sec:inst-start} + +首先请找æ¥ä¸€å¼  \TK{} çš„ \DVD{},或者下载 \TL{} 的网络安装程åºï¼Œç„¶åŽ +找到这个安装脚本:Unix 下是 \filename{install-tl},Windows 下是 +\filename{install-tl.bat}。 + +\begin{description} +\item [网络安装程åºï¼š] 在 \CTAN çš„ \dirname{systems/texlive/tlnet} +目录下å¯ä»¥ä¸‹è½½ï¼Œ\url{http://mirror.ctan.org/systems/texlive/tlnet} 这个地å€èƒ½ +自动将你导å‘一个附近的ã€ä¿æŒæ›´æ–°çš„é•œåƒã€‚ä½ å¯ä»¥ä¸‹è½½åŒæ—¶æ”¯æŒ Unix å’Œ +Windows çš„ \filename{install-tl.zip} 或者å°å¾—多但åªæ”¯æŒ Unix çš„ +\filename{install-unx.tar.gz}。解压åŽï¼Œ\filename{install-tl} å’Œ +\filename{install-tl.bat} 就会出现在 \dirname{install-tl} å­ç›®å½•ä¸­ã€‚ + +\item [\TeX{} Collection \DVD:] 打开 \dirname{texlive} 这个å­ç›®å½•ã€‚ +在 Windows 下安装程åºåº”该在æ’å…¥ \DVD åŽå°±è‡ªåŠ¨å¯åŠ¨äº†ã€‚è¦èŽ·å¾— \DVD çš„ +è¯å¯ä»¥åŠ å…¥ä¸€ä¸ª \TeX\ 用户组织 (推è这么åšï¼Œå‚è§ +\url{http://tug.org/usergroups.html}) 或是å•ç‹¬è´­ä¹° (通过 +\url{http://tug.org/store}),åˆæˆ–者是自己从 \ISO\ é•œåƒåˆ»å½• +(\url{http://tug.org/texlive/acquire.html})。 + +\end{description} + +下é¢çš„章节介ç»å¾—更为详细。 + +\subsubsection{Unix} + +\begin{figure}[tb] +\begin{boxedverbatim} +======================> TeX Live installation procedure <===================== + +=======> Note: Letters/digits in indicate menu items <======= +=======> for commands or configurable options <======= + + + Detected platform: Intel x86 with GNU/Linux + + binary systems: 1 out of 16 + + Installation scheme (scheme-full) + + Customizing installation scheme: + standard collections + language collections + 83 collections out of 84, disk space required: 1666 MB + + directories: + TEXDIR (the main TeX directory): + !! default location: /usr/local/texlive/2008 + !! is not writable, please select a different one! + TEXMFLOCAL (directory for site-wide local files): + /usr/local/texlive/texmf-local + TEXMFSYSVAR (directory for variable and automatically generated data): + /usr/local/texlive/2008/texmf-var + TEXMFSYSCONFIG (directory for local config): + /usr/local/texlive/2008/texmf-config + TEXMFHOME (directory for user-specific files): + ~/texmf + + options: + [ ] use letter size instead of A4 by default + [X] create all format files + [X] install macro/font doc tree + [X] install macro/font source tree + [ ] create symlinks in standard directories + + Install for running from DVD + +Other actions: + start installation to HD + help + quit + +Enter command: +\end{boxedverbatim} +\caption{文本模å¼ä¸»å®‰è£…ç•Œé¢ (\GNU/Linux)}\label{fig:text-main} +\end{figure} + +\begin{figure}[tb] +\tlpng{install-w32-main}{\linewidth} +\caption{\GUI{} 模å¼ä¸»å®‰è£…ç•Œé¢ (Windows)}\label{fig:gui-main} +\end{figure} + +\noindent +下é¢çš„ \texttt{>} 表示 shell æ示符;用户的输入则用 +\Ucom{\texttt{bold}} 体表示。 +在 Unix 兼容的系统的一个终端窗å£ä¸‹ï¼Œæœ€ç®€å•çš„æ–¹å¼æ˜¯: +\begin{alltt} +> \Ucom{cd /path/to/installer} +> \Ucom{perl install-tl} +\end{alltt} +(或者你å¯ä»¥ç›´æŽ¥è¿è¡Œ \Ucom{perl /path/to/installer/install-tl},或者 +\Ucom{./install-tl},如果这个文件有å¯æ‰§è¡Œå±žæ€§ï¼Œæˆ‘们ä¸ä¼šæŠŠæ‰€æœ‰è¿™äº›æ‰§ +行方法列出æ¥ã€‚) + +è¦åœ¨ \GUI\ 模å¼ä¸‹å®‰è£… (ä½ éœ€è¦ \dirname{Perl/TK} 模å—),使用: +\begin{alltt} +> \Ucom{perl install-tl -gui} +\end{alltt} + +è¦åˆ—出所有这些选项: +\begin{alltt} +> \Ucom{perl install-tl -help} +\end{alltt} + +\textbf{关于 Unix 下æƒé™çš„警告:} 在安装过程中,\TL{} 安装程åºå°†ä¼š +éµç…§ä½ çš„ \code{umask} 行事。所以如果你需è¦è®©ä½ çš„安装能给其他用户使 +用,就必须ä¿è¯ä½ è®¾ç½®çš„æƒé™è¶³å¤Ÿï¼Œæ¯”如 \code{umask 002}。更多关于 +\code{umask} çš„ä¿¡æ¯è¯·å‚è§ä½ è‡ªå·±ç³»ç»Ÿçš„文档。 + +\subsubsection{Mac\,OS\,X} + +如第 \ref{sec:tl-coll-dists} 节æ到的,我们给 \MacOSX 准备了一套独立的 +å‘行版,å«åš Mac\TeX\ (\url{http://tug.org/mactex})。我们推è使用原生的 +Mac\TeX\ 安装程åºï¼Œè€Œä¸æ˜¯ \TL\ 自带的那个,因为原生的这个能进行一些专门 +针对 Mac 的调整,尤其方便在多个 \MacOSX 下的 \TeX\ å‘行版 (Mac\TeX, gw\TeX, +Fink, MacPorts, \ldots) 之间切æ¢ã€‚ + +Mac\TeX\ 是严格ä¾èµ– \TL 构建的,所以主 \TeX\ 树也是完全一致的。ä¸è¿‡å®ƒæ·» +加了一些用æ¥å­˜æ”¾ Mac 专有文档和程åºçš„目录。 + +\subsubsection{Windows} + +如果你使用的是网络安装程åºï¼Œåˆæˆ–者 \DVD 安装程åºæ— æ³•è‡ªåŠ¨å¯åŠ¨äº†ï¼Œè¯· +åŒå‡» \filename{install-tl.bat}。 + +你也å¯ä»¥ä»Žå‘½ä»¤è¡Œæ示符下å¯åŠ¨å®‰è£…程åºã€‚ä¸‹é¢ \texttt{>} 表示的就是æ示符, +用户输入用 \Ucom{\texttt{bold}} 体表示。如果你正在安装程åºç›®å½•ä¸‹ï¼Œåªéœ€è¦ +è¿è¡Œï¼š +\begin{alltt} +> \Ucom{install-tl} +\end{alltt} + +或者你也å¯ä»¥é€šè¿‡ç»å¯¹è·¯å¾„æ¥è¿è¡Œï¼Œæ¯”如: +\begin{alltt} +> \Ucom{D:\bs{}texlive\bs{}install-tl} +\end{alltt} +这是对 \TK\ \DVD 而言的,å‡å®š \dirname{D:} 是光驱。 + +è¦åœ¨æ–‡æœ¬æ¨¡å¼ä¸‹å®‰è£…,使用: +\begin{alltt} +> \Ucom{install-tl -no-gui} +\end{alltt} + +è¦åˆ—出所有å¯ç”¨çš„选项: +\begin{alltt} +> \Ucom{install-tl -help} +\end{alltt} + +\subsubsection{文本界é¢å®‰è£…程åº} + +图~\ref{fig:text-main} 展示了 Unix 下文本模å¼çš„主界é¢ã€‚ + +这是一个完全用命令行æ“作的安装程åºï¼Œå®Œå…¨ä¸æ”¯æŒå…‰æ ‡ç§»åŠ¨ã€‚所以你无法 +在多选框或者输入框之间用 Tab 上下切æ¢ï¼Œåªèƒ½åœ¨æ示符下输入特定的字符 +(大å°å†™æ•æ„Ÿçš„) 然åŽæŒ‰ä¸‹ Enter,整个终端窗å£å°±ä¼šæŠŠæ–°çš„内容刷新出æ¥ã€‚ + +文本安装程åºä¹‹æ‰€ä»¥è¿™ä¹ˆç®€é™‹æ˜¯å› ä¸ºå®ƒè¦å°½å¯èƒ½æ”¯æŒæœ€å¤šçš„å¹³å°ï¼Œå°±ç®— +åªæœ‰ä¸€ä¸ª Perl 的系统也能è¿è¡Œå®ƒ (对于 Windows 我们自带了一个 Perl +çš„è£å‰ªç‰ˆæœ¬)。 + +\subsubsection{图形界é¢å®‰è£…程åº} + +图~\ref{fig:gui-main} 展示了 Windows 下的的图形界é¢å®‰è£…程åºã€‚图中 +选项的差别主è¦æ˜¯å› ä¸ºè¿™å¼ å›¾æ˜¯ä»Ž Windows 下截å–的,而上é¢çš„æ–‡æœ¬æ¨¡å¼ +ç•Œé¢æ¥è‡ª \GNU/Linux。 + +\subsection{执行安装程åº} +\label{sec:runinstall} + +安装程åºåº”该ä¸éœ€è¦æ–‡æ¡£å°±è¶³å¤Ÿæ˜Žç¡®ã€‚ä¸è¿‡å¯¹è¿™äº›é€‰é¡¹å’Œå­èœå•è¿˜éœ€è¦ç‚¹å°è¯´æ˜Žã€‚ + +\subsubsection{二进制系统èœå• (åªå¯¹ Unix 适用)} +\label{sec:binary} + +\begin{figure}[tbh] +\begin{boxedverbatim} +Available sets of binaries: +=============================================================================== + + a [ ] alpha-linux DEC Alpha with GNU/Linux + b [ ] amd64-freebsd x86_64 with FreeBSD + c [ ] hppa-hpux HP-UX + d [ ] i386-freebsd Intel x86 with FreeBSD + e [X] i386-linux Intel x86 with GNU/Linux + f [ ] i386-openbsd Intel x86 with OpenBSD + g [ ] i386-solaris Intel x86 with Sun Solaris + h [ ] mips-irix SGI IRIX + i [ ] powerpc-aix PowerPC with AIX + j [ ] powerpc-linux PowerPC with GNU/Linux + k [ ] sparc-linux Sparc with GNU/Linux + l [ ] sparc-solaris Sparc with Solaris + m [ ] universal-darwin universal binaries for MacOSX/Darwin + o [ ] win32 Windows + p [ ] x86_64-linux x86_64 with GNU/Linux +\end{boxedverbatim} +\caption{Binaries (二进制程åº) èœå•}\label{fig:bin-text} +\end{figure} + +图~\ref{fig:bin-text} 展示了文本模å¼ä¸‹çš„ binaries (二进制程åº) +èœå•ã€‚默认情况下åªä¼šå®‰è£…你当å‰å¹³å°ä¸‹çš„二进制程åºã€‚在这个èœå•ä¸‹ï¼Œ +ä½ å¯ä»¥é€‰æ‹©å®‰è£…其他架构的二进制程åºã€‚这对你è¦å°† \TeX\ 树共享在 +异构网络上的情况比较有用,åˆæˆ–者用于åŒå¯åŠ¨çš„系统。 + +\subsubsection{选择è¦å®‰è£…的组件} +\label{sec:components} + +\begin{figure}[tbh] +\begin{boxedverbatim} +Select a scheme: +=============================================================================== + + a [ ] TeX Live basic scheme + b [ ] TeX Live scheme for ConTeXt + c [X] TeX Live full scheme + d [ ] GUST TeX Live scheme + e [ ] GUTenberg TeX Live scheme + f [ ] TeX Live medium scheme + g [ ] TeX Live minimal scheme + h [ ] TeX Live for Omega users + i [ ] teTeX scheme + j [ ] XML typesetting scheme +\end{boxedverbatim} +\caption{Scheme (安装方案) èœå•}\label{fig:scheme-text} +\end{figure} + +图~\ref{fig:scheme-text} 展示了 \TL\ 的安装方案èœå•ï¼›ä»Žè¿™é‡Œä½ é€‰æ‹©çš„是 +一套``安装方案'',也就是对软件包集åˆçš„一个统一划分。默认的 \optname{full} +方案会把所有å¯ç”¨çš„都装上,ä¸è¿‡ä½ ä¹Ÿå¯ä»¥ç»™å°ç‚¹çš„系统选择 \optname{basic} æ–¹ +案,为测试选用 \optname{minimal} 方案,åˆæˆ–者是 \optname{medium} 或 +\optname{teTeX} æ¥é€‰æ‹©ä»‹ä¹Žå…¶é—´çš„方案。还有许多特殊或者专门针对特定国家 +的方案。 + +\begin{figure}[tbh] +\tlpng{stdcoll}{.7\linewidth} +\caption{Collections (集åˆ) èœå• (Linux)}\label{fig:collections-gui} +\end{figure} + +ä½ å¯ä»¥ä½¿ç”¨ `standard collections' 与 `language collections' èœå•æ¥è¯¦ç»† +选择安装方案。(图~\ref{fig:collections-gui} 显示了 \GUI 模å¼ä¸‹ä¿®æ”¹çš„情 +况。) + +Collection (安装集åˆ) 是比 scheme (方案) è¦æ›´ç»†çš„一层 \Dash 实际上一个 +方案包å«äº†å¤šä¸ªé›†åˆï¼Œè€Œä¸€ä¸ªé›†åˆåˆåŒ…å«äº†ä¸€åˆ°å¤šä¸ªè½¯ä»¶åŒ…,然åŽæ¯ä¸ªè½¯ä»¶åŒ… +(\TL 中最å°çš„组织å•ä½) 则包å«äº†å®žé™…çš„ \TeX\ å®æ–‡ä»¶ï¼Œå­—体文件,等等。 + +如果你觉得 collection èœå•å¯¹å®‰è£…控制还ä¸å¤Ÿç»†ï¼Œå¯ä»¥åœ¨å®‰è£…åŽä½¿ç”¨ +\prog{tlmgr} ç¨‹åº (å‚è§ç¬¬~\ref{sec:tlmgr} 节),它能在软件包一层 +控制安装。 + +\subsubsection{目录} +\label{sec:directories} + +缺çœçš„目录布局在第~\ref{sec:texmftrees} 节有过å™è¿°ï¼Œè§ç¬¬ +\pageref{sec:texmftrees} 页。默认的 \dirname{TEXDIR} 路径 +则是 Windows 下的 |%PROGRAMFILES%\texlive\2008| å’Œ Unix +下的 \dirname{/usr/local/texlive/2008}。 + +更改默认值的主è¦åŽŸå› å¤§æ¦‚是你å¯èƒ½æ²¡æœ‰é»˜è®¤ä½ç½®çš„写æƒé™ã€‚虽然è¦å®‰è£… +\TL ä¸éœ€è¦æ˜¯ç®¡ç†å‘˜æˆ–者 root 用户,但你至少得对安装的目的目录有写 +æƒé™ã€‚ + +一个åˆç†çš„选择是你自己主目录下的一个å­ç›®å½•ï¼Œå°¤å…¶åœ¨åªæœ‰ä½ ä¸€ä¸ªäºº +使用的时候。使用 `|~|' æ¥è¡¨ç¤ºä¸»ç›®å½•ï¼Œæ¯”如 `|~/texlive/2008|'。 + +我们建议在目录å称中ä¿ç•™å¹´ä»½ï¼Œè¿™æ ·å¯ä»¥è®©ä½ ä¿ç•™å¤šä¸ªä¸åŒç‰ˆæœ¬çš„ +\TL{}。(ä½ å¯èƒ½å¸Œæœ›ç”¨ä¸€ä¸ªç±»ä¼¼ \dirname{/usr/local/texlive-cur} +这样的å字作为指å‘当å‰ç‰ˆæœ¬çš„符å·é“¾æŽ¥ï¼Œè¿™æ ·çš„目录å就和版本无 +关了,你åªè¦åœ¨æ–°ç‰ˆæœ¬å‡ºæ¥ç›´æŽ¥æ›´æ–°ç¬¦å·é“¾æŽ¥å³å¯ã€‚) + +在安装程åºä¸­ä¿®æ”¹ \dirname{TEXDIR} 之åŽè¿˜ä¼šåŒæ—¶ä¿®æ”¹ +\dirname{TEXMFLOCAL}, \dirname{TEXMFSYSVAR} å’Œ +\dirname{TEXMFSYSCONFIG}。 + +\dirname{TEXMFHOME} 是推è用æ¥å­˜æ”¾ä¸ªäººå®æ–‡ä»¶å’Œè½¯ä»¶åŒ…的目录。 +其缺çœå€¼æ˜¯ |~/texmf|。与 \dirname{TEXDIR} ä¸åŒï¼Œå…¶ä¸­åŒ…å«çš„ +|~| 会被ä¸åŠ è½¬æ¢åœ°å†™è¿›é…置文件,因为它能在 \TeX 系统è¿è¡Œæ—¶ +自动被替æ¢ä¸ºæ¯ä¸ªç”¨æˆ·è‡ªå·±çš„主目录。在 Unix 它会被展开为 +\dirname{$HOME},而 Windows 下展开为 \verb|%USERPROFILE%|。 + +\subsubsection{选项} +\label{sec:options} + +\begin{figure}[tbh] +\begin{boxedverbatim} +

use letter size instead of A4 by default: [ ] + create all format files: [X] + install font/macro doc tree: [X] + install font/macro source tree: [X] + create symlinks in standard directories: [ ] + binaries to: + manpages to: + info to: +\end{boxedverbatim} +\caption{Options èœå• (Unix)}\label{fig:options-text} +\end{figure} + +图~\ref{fig:options-text} 显示了文本模å¼çš„选项èœå•ã€‚其中有 +三个选项值得一æ: + +\begin{description} +\item[use letter size instead of A4 by default:] 常è§çš„缺çœçº¸å¼ å¤§å°é€‰æ‹©ã€‚ +当然如果需è¦ï¼Œæ¯ä»½æ–‡æ¡£éƒ½å¯ä»¥å•ç‹¬è®¾å®šä¸€ä¸ªçº¸å¼ å¤§å°ã€‚ + +\item[create all format files:] 虽然创建ä¸å¿…è¦çš„æ ¼å¼æ–‡ä»¶ä¼šæµªè´¹ä¸€ +点时间,也会多å ä¸€äº›ç£ç›˜ç©ºé—´ï¼Œä½† +我们还是建议现在ä¿æŒè¿™ä¸ªé€‰é¡¹çš„选定状æ€ï¼Œå› ä¸ºå¦‚果这次ä¸ç”Ÿæˆï¼Œä¸‹æ¬¡ +用到的时候格å¼æ–‡ä»¶å°±ä¼šåœ¨ç”¨æˆ·ä¸ªäººçš„ \dirname{TEXMFVAR} 目录树内生 +æˆã€‚这样æ¯æ¬¡äºŒè¿›åˆ¶æ–‡ä»¶æˆ–者断字模å¼æ›´æ–°çš„时候,这些格å¼æ–‡ä»¶ä¹Ÿå¾—ä¸ +到更新,所以å¯èƒ½ä¼šå¯¼è‡´å®ƒä»¬çš„ä¸å…¼å®¹ã€‚ + +\item[create symlinks in standard directories] (åªå¯¹ Unix 有效): +这个选项å¯ä»¥çœä¸‹è®¾å®šçŽ¯å¢ƒå˜é‡çš„步骤。如果没有选择它,就必须把 +\TL{} 的对应目录添加到 \envname{PATH}, \envname{MANPATH} å’Œ +\envname{INFOPATH} 中。如果è¦åˆ›å»ºç¬¦å·é“¾æŽ¥ï¼Œä½ éœ€è¦å¯¹è¿™äº›ç›®æ ‡ +目录的写æƒé™ã€‚我们ä¸å»ºè®®ä½ ç”¨è¿™ä¸ªå‘½ä»¤æ¥è¦†ç›–现有的 \TeX\ 系统, +它主è¦æ˜¯ä¸ºäº†åœ¨ç”¨æˆ·å·²çŸ¥çš„标准目录中创建符å·é“¾æŽ¥è®¾è®¡çš„,这些 +目录并ä¸åŒ…å«ä»»ä½• \TeX\ 文件。 +\end{description} + +如果所有的设置已ç»é½å¤‡ï¼Œä½ å°±å¯ä»¥æŒ‰ä¸‹ `I' æ¥å¼€å§‹å®‰è£…了。安装完æˆåŽï¼Œ +ä½ å¯ä»¥è·³è‡³ç¬¬ \ref{sec:postinstall} 节æ¥äº†è§£è¿˜éœ€è¦åšäº›ä»€ä¹ˆå·¥ä½œã€‚ + +\subsubsection{设置从 DVD{} è¿è¡Œ (åªå¯¹æ–‡æœ¬æ¨¡å¼é€‚用)} +\label{sec:fromdvd} + +按 `|V|' æ¥é€‰æ‹©è¿™ä¸ªé€‰é¡¹ã€‚它将主èœå•æ”¹å˜ä¸ºç±»ä¼¼å›¾~\ref{fig:main-fromdvd} +çš„ç•Œé¢ã€‚ +\begin{figure}[tbh] +\begin{boxedverbatim} +======================> TeX Live installation procedure <===================== + +=======> Note: Letters/digits in indicate menu items <======= +=======> for commands or configurable options <======= + + directories: + TEXDIRW (Writable root): + !! default location: /usr/local/texlive/2008 + !! is not writable, please select a different one! + TEXMFLOCAL (directory for site-wide local files): + /usr/local/texlive/texmf-local + TEXMFSYSVAR (directory for variable and automatically generated data): + /usr/local/texlive/2008/texmf-var + TEXMFSYSCONFIG (directory for local config): + /usr/local/texlive/2008/texmf-config + TEXMFHOME (directory for user-specific files): + ~/texmf + + options: + [ ] use letter size instead of A4 by default + [X] create all format files + + set up for installing to hard disk + +Other actions: + start installation for running from DVD + help + quit +\end{boxedverbatim} +\caption{å¯ç”¨ \optname{from DVD} 集åˆåŽçš„主èœå•}\label{fig:main-fromdvd} +\end{figure} + +注æ„å˜åŒ–之处:所有关于安装内容的选项都消失了,而目录这部分 +çš„è®¾ç½®çŽ°åœ¨æ˜¯æ ¹æ® \dirname{TEXDIRW} (或者一个å¯å†™çš„根目录) +æ¥è®¾ç½®çš„。创建符å·é“¾æŽ¥çš„选项也没有了。 + +这样安装程åºä»ç„¶ä¼šåˆ›å»ºä¸€äº›ç›®å½•å’Œé…置文件,但并ä¸ä¼šæŠŠ \dirname{texmf}, +\dirname{texmf-dist} 或 \dirname{texmf-doc} 目录å¤åˆ¶åˆ°æœ¬åœ°ç¡¬ç›˜ä¸Šã€‚ + +Unix 系统下的安装åŽé…置步骤è¦ç¨å¾®å¤æ‚一些,因为这样目录布局就和缺 +çœæƒ…况有所区别了,å‚è§ç¬¬ \ref{sec:postinstall} 节。 + +因为时间é™åˆ¶ï¼Œè¿™ä¸ªé€‰é¡¹è¿˜æ¥ä¸åŠé›†æˆè¿›å…¥ \GUI{} 安装程åºã€‚ä¸è¿‡å®ƒçš„ç¡® +是åŒæ—¶æ”¯æŒ Unix å’Œ Windows 的。Windows 用户需è¦ä»Žå‘½ä»¤è¡Œé€‰é¡¹æ¥å¯åŠ¨ +这个安装程åºï¼Œå‚è§ç¬¬ \ref{sec:cmdline} 节。 + +第 \ref{sec:portable-unix} 节æ述了一套更具å¯ç§»æ¤æ€§åœ°è¿è¡Œ \TL{} +的方法,它ä¸éœ€è¦å¯¹ç³»ç»Ÿé…ç½®åšä»»ä½•æ”¹åŠ¨ï¼Œä½†ä¹Ÿåšä¸äº†ä»»ä½•é…置。 + +\subsection{命令行安装选项} +\label{sec:cmdline} + +输入 +\begin{alltt} +> \Ucom{install-tl -help} +\end{alltt} +å¯ä»¥åˆ—出所有的命令行å‚数。你既å¯ä»¥ç”¨ |-| 也å¯ä»¥ç”¨ |--| æ¥æŒ‡å®šä¸€ä¸ª +å‚数。这里有些比较有趣的: + +\begin{ttdescription} +\item[-gui] å°½å¯èƒ½ç”¨ \GUI{} 模å¼çš„安装程åºã€‚它需è¦å®‰è£…了 + Perl/Tk æ¨¡å— (\url{http://tug.org/texlive/distro.html#perltk})ï¼› + 如果找ä¸åˆ° Perl/Tk,安装程åºå°±ä¼šåœ¨æ–‡æœ¬æ¨¡å¼ä¸‹å‡ºçŽ°ã€‚ +\item[-no-gui] 强制使用文本模å¼å®‰è£…程åºï¼Œå°±ç®—在 Windows 下也是如此。 +å¦‚æžœä½ éœ€è¦ `from \DVD' 安装方å¼å°±éœ€è¦ç”¨åˆ°è¿™ä¸ªé€‰é¡¹ï¼Œå› ä¸ºè¿™ä¸ªæ–¹å¼åœ¨ +\GUI{} 模å¼ä¸‹æ²¡æœ‰æ供。 +\item[-lang {\sl LL}] 指定安装程åºç•Œé¢çš„语言,使用两个字符的语言 +ä»£ç  \textsl{LL}。目å‰æ”¯æŒçš„语言有:英语 (\texttt{en}, 默认值), +德语 (\texttt{de}), 法语 (\texttt{fr}), è·å…°è¯­ (\texttt{nl}), 波兰语 +(\texttt{pl}), 斯洛文尼亚语 (\texttt{sl}) 和越å—语 (\texttt{vi})。 +安装程åºä¼šå°è¯•è‡ªå·±åˆ¤æ–­å‡ºåˆé€‚的语言,如果判断出的语言没有支æŒå°±ä¼š +使用英语替代。 +\item[-profile {\sl profile}] 安装程åºä¼šåœ¨ \dirname{2008/tlpkg} +目录或者安装到的å­ç›®å½• \dirname{tlpkg} ä¸­åˆ›å»ºä¸€ä¸ªå« +\filename{texlive.profile} 的文件。这个选项å¯ä»¥è®©å®‰è£…程åºé‡ç”¨ +现æˆçš„è¿™ç§æ–‡ä»¶ã€‚这里有个例å­ï¼š + \begin{fverbatim} +# texlive.profile written on Wed Jul 9 16:13:44 2008 UTC +# It will NOT be updated and reflects only the +# installation profile at installation time. +selected_scheme scheme-basic +TEXDIR /usr/local/texlive/2008 +TEXDIRW /usr/local/texlive/2008 +... +TEXMFSYSVAR /usr/local/texlive/2008/texmf-var +collection-basic 1 +... +option_symlinks 0 + \end{fverbatim} +这样一æ¥ï¼Œé€šè¿‡è¿™ä¸ªé€‰é¡¹ä½ å°±å¯ä»¥åœ¨åŽæ¥çš„系统里进行批é‡å®‰è£…了,å¯ä»¥ +ä¿è¯é€‰é¡¹å’Œç¬¬ä¸€æ¬¡å®‰è£…的完全一样。 +\item [-location {\sl url/path}] 为软件包指定一个éžå®˜æ–¹çš„æ¥æºï¼Œå‚è§ä¸‹æ–‡ã€‚ +\end{ttdescription} + +\subsubsection{\optname{location} å‚æ•°} +\label{sec:location} + +location 值å¯ä»¥æ˜¯ä¸€ä¸ªä»¥ \texttt{ftp:}, \texttt{http:}, 或 +\texttt{file:/} 起始的 URL,或者一个本地路径。如果给定的地 +å€åœ¨æœ¬åœ°ç£ç›˜ä¸Š (或者是路径或者是 \texttt{file:/} 开头的 URL), +我们å¯ä»¥ç«‹å³åˆ¤æ–­å‡ºå®‰è£…的类型 (压缩的 CD 还是 live DVD):如果 +èƒ½æ‰¾åˆ°ä¸€ä¸ªå« \dirname{archive} å­ç›®å½•è€Œä¸”它下é¢éƒ½æ˜¯ +\filename{.tar.lzma} æ ¼å¼çš„压缩文件,那就会用它进行安装,就算 +没压缩的文件也存在。 + +如果给定了一个 \texttt{http:} 或 \texttt{ftp:} 地å€ï¼Œå…¶æœ«å°¾çš„ +`\texttt{/}' 字符和末尾的 `\texttt{/tlpkg}' 这段都会被忽略。 +比如你å¯ä»¥é€‰æ‹©è¿™æ ·çš„一个 \CTAN é•œåƒï¼š +\url{http://ctan.example.org/tex-archive/texlive/tlnet/2008}, +当然你应该把 |ctan.example.org/tex-archive| 替æ¢ä¸ºå…·ä½“é•œåƒçš„ +域å和特定的顶层 \CTAN 路径 (\url{http://ctan.org/mirrors}) +维护了一个 \CTAN çš„é•œåƒåˆ—表)。缺çœå€¼æ˜¯ä½¿ç”¨ \url{http://mirror.ctan.org} +æ¥è‡ªåŠ¨åˆ¤æ–­çš„。ä¸ç®¡æ˜¯ä»€ä¹ˆæƒ…况,选定的镜åƒéƒ½ä¼šè¢«ç”¨æ¥ä¸‹è½½æ‰€æœ‰çš„ +内容。 + +\subsection{安装åŽçš„æ“作} +\label{sec:postinstall} + +安装åŽå¯èƒ½éœ€è¦ä¸€äº›é¢å¤–çš„æ“作。 + +\subsubsection{Windows} + +在 Windows 下安装程åºä¼šå®Œæˆæ‰€æœ‰çš„æ“作。 + +\subsubsection{如果创建了符å·é“¾æŽ¥} + +如果你选择了在标准路径下创建符å·è¿žæŽ¥ (在第~\ref{sec:options} 节æ到), +那就ä¸éœ€è¦è®¾ç½®çŽ¯å¢ƒå˜é‡äº†ã€‚ + +\subsubsection{Unix 下的环境å˜é‡} +\label{sec:env} + +你应该将自己使用的平å°ä¸‹äºŒè¿›åˆ¶ç¨‹åºçš„目录加入æœç´¢è·¯å¾„中。æ¯ä¸ªæ”¯ +æŒçš„å¹³å°éƒ½åœ¨ \dirname{TEXDIR/bin} 下有自己的å­ç›®å½•ã€‚å‚è§å›¾~\ref{fig:bin-text} +以了解所有的这些å­ç›®å½•å’Œå®ƒä»¬å¯¹åº”çš„å¹³å°ã€‚ + +如果希望 man å’Œ info 能够找到,你还å¯ä»¥æŠŠæ–‡æ¡£çš„ man å’Œ Info 目录加 +入其对应的æœç´¢è·¯å¾„中。 + +对于 \prog{bash} 这样的 Bourne 兼容 shell 而言,以 Intel x86 下的 +GNU/Linuxã€é»˜è®¤çš„目录设置为例,需è¦ä¿®æ”¹çš„文件是 \filename{$HOME/.profile} +(或者其他由 \filename{.profile} 载入的文件),应该添加的内容应该类似 +这样: + +\begin{sverbatim} +PATH=/usr/local/texlive/2008/bin/i386-linux:$PATH; export PATH +MANPATH=/usr/local/texlive/2008/texmf/doc/man:$MANPATH; export MANPATH +INFOPATH=/usr/local/texlive/2008/texmf/doc/info:$INFOPATH; export INFOPATH +\end{sverbatim} + +对于 csh 或者 tcsh,需è¦ä¿®æ”¹çš„文件通常是 \filename{$HOME/.cshrc},而 +应该添加的内容类似: + +\begin{sverbatim} +setenv PATH /usr/local/texlive/2008/bin/i386-linux:$PATH +setenv MANPATH /usr/local/texlive/2008/texmf/doc/man:$MANPATH +setenv INFOPATH /usr/local/texlive/2008/texmf/doc/info:$INFOPATH +\end{sverbatim} + +当然,你å¯èƒ½å·²ç»åœ¨ä½ çš„é…置文件里写过了这样的路径设置,那就åªéœ€è¦ +把 \TL\ 的这些目录加进去就行了。 + +\subsubsection{环境å˜é‡çš„全局é…ç½®} +\label{sec:envglobal} + +如果你希望在整个系统范围内修改这些å˜é‡ï¼Œæˆ–这样系统新增的用户自动 +继承这些å˜é‡ï¼Œå°±å¾—自寻方法了,因为ä¸åŒçš„系统之间这方é¢çš„é…置差异 +太大。 + +我们的建议是: 1)~ä½ å¯èƒ½åº”该看看 \filename{/etc/manpath.config} +这个文件是å¦å­˜åœ¨ï¼Œå¦‚果有的è¯ï¼Œæ·»åŠ ä¸‹é¢è¿™æ ·çš„内容: + +\begin{sverbatim} +MANPATH_MAP /usr/local/texlive/2008/bin/i386-linux \ + /usr/local/texlive/2008/texmf/doc/man +\end{sverbatim} + +ç„¶åŽ 2)~检查 \filename{/etc/environment} 是å¦å®šä¹‰äº†é»˜è®¤çš„æœç´¢è·¯å¾„ +和其他的默认环境å˜é‡ã€‚ + +\subsubsection{如果从 DVD è¿è¡Œ} + +通常æ¥è¯´ \TL{} 程åºéƒ½ä¼šå¯»æ‰¾ä¸€ä¸ªå«åš \filename{texmf.cnf} 的文件 +æ¥èŽ·çŸ¥æ‰€æœ‰çš„ \TeX æ ‘ä½ç½®ã€‚它会在一系列和其本身ä½ç½®ç›¸å…³çš„地方寻 +找这个文件。ä¸è¿‡å¦‚果直接在 \DVD 上è¿è¡Œï¼Œè¿™å¥—规则就ä¸é€‚用了:因为 +\DVD{} 是åªè¯»çš„,而æŸäº›è·¯å¾„åªèƒ½åœ¨å®‰è£…时确定下æ¥å¹¶å†™å…¥è¿™ä¸ªæ–‡ä»¶ï¼Œ +所以这个文件没法放在 \DVD{} 上,åªèƒ½å¦ç½®ä¸€å¤„。所以å¯èƒ½ä¼šéœ€è¦å®šä¹‰ +\envname{TEXMFCNF} æ¥å‘ŠçŸ¥ \TL{} 程åºè¯¥ä»Žå“ªå„¿æ‰¾åˆ°è¿™ä¸ª \filename{texmf.cnf} +文件。当然,如å‰æ‰€è¿° \envname{} 环境å˜é‡è¿˜æ˜¯è¦æ”¹çš„。 + +在安装结æŸæ—¶ï¼Œå®‰è£…程åºä¼šè¾“出一段告诉你如何设置 \envname{TEXMFCNF} +çš„ä¿¡æ¯ï¼Œå¦‚果你忽略了è¯ï¼Œå®ƒåº”该是 \dirname{$TEXMFSYSVAR/web2c},默认 +情况下就是 \dirname{/usr/local/texlive/2008/texmf-var/web2c}ï¼Œä½ éœ€è¦ +在 bash 下使用: +\begin{sverbatim} +TEXMFCNF=/usr/local/texlive/2008/texmf-var/web2c; export TEXMFCNF +\end{sverbatim} +或者 [t]csh 下使用: +\begin{sverbatim} +setenv TEXMFCNF /usr/local/texlive/2008/texmf-var/web2c +\end{sverbatim} + + +\subsubsection{\ConTeXt{} Mark IV} + +`è€ç‰ˆ'çš„ \ConTeXt{} 正常就应该能工作。新的 `Mark IV' \ConTeXt{} +则需è¦ä¸€äº›æ‰‹åŠ¨è®¾ç½®ã€‚å‚è§ +\url{http://wiki.contextgarden.net/Running_Mark_IV}。 + +\subsubsection{集æˆæœ¬åœ°ä¸Žä¸ªäººå®æ–‡ä»¶} +\label{sec:local-personal-macros} + +这在第~\ref{sec:texmftrees} 节已ç»é¡ºå¸¦æ到过了:\dirname{TEXMFLOCAL} +目录 (它的默认值是 \dirname{/usr/local/texlive/texmf-local} 或者 +\verb|C:\Program Files\texlive\texmf-local|) 这个目录就是为了存储 +é¢å‘整个系统的本地字体和å®æ–‡ä»¶çš„;而 \dirname{TEXMFHOME} 目录 (å…¶ +默认值是 \dirname{$HOME/texmf} 或者 \verb|%USERPROFILE%\texmf|), +则是用æ¥å­˜å‚¨ä¸ªäººçš„字体和å®æ–‡ä»¶çš„。这些目录应该在å„个 \TL{} +版本之间共享,æ¯ä¸ªç‰ˆæœ¬éƒ½èƒ½çœ‹åˆ°å…¶å†…容。因此ä¸åº”该把 +\dirname{TEXMFLOCAL} 改得和主 \TL{} 目录差别太大,å¦åˆ™æ–°çš„ç‰ˆæœ¬å‡ºæ¥ +ä½ åˆå¾—å†æ”¹ã€‚ + +对于这两个目录树而言,文件都应该放到åˆé€‚çš„å­ç›®å½•ä¸­ï¼Œå‚è§ +\url{http://tug.org/tds} 或者 \filename{texmf/web2c/texmf.cnf} +文件。比如一个 \LaTeX{} 文档类或者å®åŒ…应该放在 +\dirname{TEXMFLOCAL/tex/latex} 或者 \dirname{TEXMFHOME/tex/latex} +目录下,è¦ä¸ç„¶å°±æ˜¯å®ƒä»¬çš„一个å­ç›®å½•ä¸‹ã€‚ + +\dirname{TEXMFLOCAL} 目录需è¦ä¸€ä¸ªä¿æŒæ›´æ–°çš„文件åæ•°æ®åº“,å¦åˆ™æ–°å¢ž +的文件就无法找到。你å¯ä»¥ä½¿ç”¨ \cmdname{mktexlsr} 命令或者 +\prog{tlmgr} \GUI\ 模å¼ä¸‹ï¼Œconfiguration 选项å¡ä¸­çš„ +`Reinit file database' 按钮æ¥åˆ·æ–°å®ƒã€‚ + +\subsubsection{集æˆç¬¬ä¸‰æ–¹å­—体} + +ä¸å¹¸çš„是,这是一个éžå¸¸å¤æ‚而混乱的主题。除éžä½ å¯¹ \TeX{} 安装éžå¸¸ +熟悉,å¦åˆ™è¯·ä¸è¦æ¶‰è¶³è¿™ä¸ªé¢†åŸŸã€‚别忘了事先看看我们附带的字体,å‚è§ +第 \ref{sec:tl-fonts} 节。 + +\XeTeX 是一套å¯è¡Œçš„替代方案 (å‚è§ç¬¬ \ref{sec:tex-extensions} 节), +它能让你使用æ“作系统的字体而ä¸å¿…将它安装到 \TeX 中。 + +\subsection{测试安装是å¦æˆåŠŸ} +\label{sec:test-install} + +在完æˆä½ æ‰€éœ€è¦çš„ \TL{} 安装之åŽï¼Œè‡ªç„¶ä½ ä¼šå¸Œæœ›è¯•è¯•çœ‹å®ƒæ˜¯å¦æ­£å¸¸å·¥ä½œï¼Œå¥½è®©ä½ åœ¨ä»¥åŽèƒ½å¤Ÿ +创建优美的文档和字体。 + +这个å°èŠ‚给出了一些测试系统是å¦æ­£å¸¸å·¥ä½œçš„基本步骤。我们这里使用的是 Unix 命令,在 +\MacOSX{} å’Œ Windows 下你更å¯èƒ½æ˜¯ä½¿ç”¨å›¾å½¢ç•Œé¢è¿è¡Œè¿™äº›æµ‹è¯•çš„,ä¸è¿‡å…¶åŽŸç†å¹¶æ— ä¸åŒã€‚ + +\begin{enumerate} + +\item 首先确认你å¯ä»¥æ‰§è¡Œ \cmdname{tex} 程åºï¼š +\begin{alltt} +> \Ucom{tex -{}-version} +TeX 3.1415926 (Web2C 7.5.7) +kpathsea version 3.5.7 +... +\end{alltt} +如果返回的结果是 `command not found' 而éžç‰ˆæœ¬å’Œç‰ˆæƒä¿¡æ¯ï¼Œæˆ–者显示了 +旧版本的信æ¯ï¼Œå¾ˆæœ‰å¯èƒ½æ˜¯å› ä¸ºä½ æ²¡æœ‰æŠŠæ­£ç¡®çš„ \dirname{bin} å­ç›®å½•æ·»åŠ  +到 \envname{PATH} 中。å‚è§ç¬¬ \pageref{sec:env} 页关于设置环境å˜é‡ +的说明。 + +\item 处ç†ä¸€ä¸ªåŸºæœ¬çš„ \LaTeX{} 文件: +\begin{alltt} +> \Ucom{latex sample2e.tex} +This is pdfeTeXk, Version 3.141592... +... +Output written on sample2e.dvi (3 pages, 7484 bytes). +Transcript written on sample2e.log. +\end{alltt} +如果无法找到 \filename{sample2e.tex} 或其他什么文件,很å¯èƒ½æ˜¯å› ä¸ºæ—§çš„环境å˜é‡ +或é…置文件影å“了判断。我们建议你é‡ç½®æ‰€æœ‰ \TeX 相关的环境å˜é‡ç„¶åŽé‡è¯•ã€‚(ä½ å¯ä»¥ +让 \TeX{} 报告具体æœç´¢çš„路径,以便仔细分æžå‡ºé”™çš„原因。å‚è§ç¬¬ \pageref{sec:debugging} +页的``调试æ“作''一节以了解更多信æ¯ã€‚) + +\item å³æ—¶é¢„览结果: +\begin{alltt} +> \Ucom{xdvi sample2e.dvi} +\end{alltt} +(Windows ä¸‹ç±»ä¼¼çš„å‘½ä»¤å« \cmdname{dviout}。) 你应该å¯ä»¥çœ‹åˆ°åœ¨æ–°çª—å£ä¸­å‡ºçŽ°äº†ä¸€ç¯‡ +ä»‹ç» \LaTeX{} 基础的有趣文档。(如果你刚接触 \TeX\ 系统,还是值得一读的。) \cmdname{xdvi} +需è¦è¿è¡Œåœ¨ X 窗å£ç³»ç»Ÿä¸‹æ‰èƒ½å·¥ä½œï¼Œå¦‚果没有è¿è¡Œçª—å£çŽ¯å¢ƒæˆ– \envname{DISPLAY} 环境å˜é‡è®¾ç½® +错误,都会得到 \samp{Can't open display} è¿™å¥é”™è¯¯ä¿¡æ¯ã€‚ + +\item 创建用于打å°æˆ–显示的 \PS{} 文件: +\begin{alltt} +> \Ucom{dvips sample2e.dvi -o sample2e.ps} +\end{alltt} + +\item 创建 \acro{PDF} æ–‡ä»¶è€Œéž \dvi{}ï¼Œè¿™é‡Œé‡‡ç”¨ç›´æŽ¥å¤„ç† \filename{.tex} +文件输出 \acro{PDF} çš„æ–¹å¼ï¼š +\begin{alltt} +> \Ucom{pdflatex sample2e.tex} +\end{alltt} + +\item 预览 \acro{PDF} 文件: +\begin{alltt} +> \Ucom{gv sample2e.pdf} +\textrm{或:} +> \Ucom{xpdf sample2e.pdf} +\end{alltt} +ä¸å¹¸çš„是 \cmdname{gv} å’Œ \cmdname{xpdf} 现在都ä¸åŒ…å«åœ¨ \TL{} 中,你 +å¿…é¡»å•ç‹¬å®‰è£…它们。请分别å‚阅 \url{http://www.gnu.org/software/gv} å’Œ +\url{http://www.foolabs.com/xpdf}。(还有许多其他的 \acro{PDF} 查看器。) + +\item 除 \filename{sample2e.tex} 外å¯èƒ½ä¼šå¯¹ä½ æœ‰ç”¨çš„标准测试文件: + +\begin{ttdescription} +\item [small2e.tex] 比 \filename{sample2e} 更为简å•çš„文档,供你在é‡åˆ°é—®é¢˜ +æ—¶å°è¯•å‡å°‘输入的内容。 +\item [testpage.tex] 测试你的打å°æœºæ˜¯å¦å¸¦æœ‰é¢„设的å移é‡ã€‚ +\item [nfssfont.tex] 打å°ä¸€ä»½å­—体表格 (proofsheet) 以供测试。 +\item [testfont.tex] 用 plain \TeX{} 打å°å­—体表格。 +\item [story.tex] 最ç»å…¸çš„ (plain) \TeX{} 测试文件。在执行 +\samp{tex story.tex} 之åŽï¼Œä½ è¿˜è¦åœ¨ \code{*} æ示符下键入 \samp{\bs bye}。 +\end{ttdescription} +ä½ å¯ä»¥ç”¨ä¸Žæˆ‘ä»¬å¤„ç† \filename{sample2e.tex} 文件时相åŒçš„æ–¹å¼æ¥å¤„ç†è¿™äº›æ–‡ä»¶ã€‚ + +\end{enumerate} + +如果你还是个 \TeX{} 新手,或者在编辑 \TeX{} 或 \LaTeX{} 文档时需è¦å¸®åŠ©ï¼Œ +请访问 \url{http://tug.org/begin.html} 寻找引导性的资æºã€‚ + + +\section{网络安装} +\label{sec:netinstall} + +\TL{} 的设计å¯ä»¥ä½¿å®ƒåœ¨ä¸åŒçš„用户间共享,甚至å¯ä»¥åœ¨ç½‘络上ä¸åŒçš„系统间共 +享。在标准的目录结构下,ä¸éœ€è¦é…置固定的ç»å¯¹è·¯å¾„:\TL{} 程åºæ‰€éœ€è¦çš„æ–‡ +件都能通过都在这些程åºè‡ªèº«çš„相对路径找到。你å¯ä»¥åœ¨ +\filename{$TEXMFMAIN/web2c/texmf.cnf} é…置文件中看到实际的处ç†ï¼Œ +它包å«äº†ç±»ä¼¼ä¸‹é¢çš„内容: +\begin{verbatim} +TEXMFMAIN = $SELFAUTOPARENT/texmf +... +TEXMFLOCAL = $SELFAUTOPARENT/../texmf-local +\end{verbatim} +这就æ„味ç€ï¼Œå…¶å®ƒçš„系统或用户åªéœ€è¦æŠŠ \TL{} çš„å¯æ‰§è¡Œæ–‡ä»¶çš„ä½ç½®æ·»åŠ åˆ°å…¶ +系统的æœç´¢è·¯å¾„中å³å¯ã€‚ + +åŒç†ï¼Œä½ ä¹Ÿå¯ä»¥å…ˆæŠŠ \TL{} 安装在本地,然åŽå†æŠŠæ•´ä¸ªå®‰è£…目录转移到网络上。 + +当然,Windows 用户会有ä¸åŒçš„期望。\dirname{texmf-doc/source/texlive/texlive-common/w32client} +目录包å«äº†ä¸€ä¸ªæ ·ä¾‹è„šæœ¬ \filename{install-w32client},它å¯ä»¥ä¸ºå±€åŸŸç½‘上的 +\TL{} 安装产生é…置文件和èœå•å¿«æ·æ–¹å¼ã€‚它å¯ä»¥é€šè¿‡åœ¨ç›¸åŒç›®å½•çš„ +\filename{install-w32client.bat} 调用。 + +ä½ å¯ä»¥åœ¨ç¬¬~\ref{sec:kpathsea}~节中了解更多有关 \TL{} é…置和 +路径æœç´¢çš„内容。 + +\section{在 DVD 或 USB 上最具å¯ç§»æ¤æ€§åœ°è¿è¡Œ \protect\TL{}} +\label{sec:portable-unix} + +在第 \ref{sec:fromdvd} 节中介ç»çš„``从 \DVD{} è¿è¡Œ''选项å¯ä»¥ä½¿å‘行版在 +你的系统上很好地è¿è¡Œï¼Œä½†æ˜¯å¦‚果你在别人的机器上用éžç®¡ç†å‘˜å¸å·å·¥ä½œï¼Œ +那你就å¯èƒ½å¸Œæœ›ä½¿ç”¨å¯¹ç³»ç»Ÿæœ¬èº«çš„å½±å“最å°çš„è¿è¡Œæ–¹å¼ã€‚ + +在 \TL{} \DVD 的根目录,或者 \TK{} \DVD çš„ \dirname{texlive} å­ç›®å½•ä¸­ï¼Œ +有一个为 Unix 系统æ供的脚本 \filename{tl-portable} 和一个为 Windows +系统æ供的批处ç†æ–‡ä»¶ \filename{tl-portable.bat}。它们能开å¯ä¸€ä¸ªè®¾ç½®å¥½ +环境å˜é‡çš„终端或命令æ示符,在其中就能直接è¿è¡Œ \DVD 上的 \TL{}。 + +头一次执行时它会花点时间在 \dirname{~/.tlportable2008} 目录下生æˆä¸€äº› +文件,此åŽå°±å¯ä»¥åœ¨å¾ˆçŸ­çš„时间内å¯åŠ¨äº†ã€‚ + +而此时系统的其它程åºå¹¶ä¸çŸ¥é“ \TL{} 的存在,如果你需è¦è®©ä½ çš„文本编辑器 +使用这个 \TL,å¯ä»¥å†æ‰“开一个这样的 \filename{tl-portable} 会è¯æ¥ä½¿ç”¨ +该编辑器。 + +你还能通过 \filename{tl-portable} 在 \acro{USB} 驱动器上è¿è¡Œ \TL。 +在这ç§æƒ…况下,请 (至少) 把所有的顶层目录下的所有文件和 \dirname{bin}, +\dirname{texmf}, \dirname{texmf-dist} å’Œ \dirname{tlpkg} 下的所有内容 +å¤åˆ¶åˆ° USB 驱动器上。这会花一定的时间。如果你把它å¤åˆ¶åˆ°ä¸€ä¸ª \acro{FAT}32 +æ ¼å¼çš„ \acro{USB} 驱动上,请ä¿è¯å¤åˆ¶æ“作是跟踪 (dereference) 所有的 +符å·é“¾æŽ¥åˆ°å®žé™…æ•°æ®æ–‡ä»¶çš„ (\code{cp -L})。è¿è¡Œæ—¶éƒ½ä¼šæŸ¥æ‰¾å¹¶ä½¿ç”¨é©±åŠ¨å™¨ä¸Š +çš„ \dirname{texmf-local} 目录。 + +然åŽä½ å°±å¯ä»¥åœ¨é©±åŠ¨å™¨çš„根目录下åƒä¸Šé¢é‚£æ ·è¿è¡Œ \filename{tl-portable} +了。此时脚本能判断出这个驱动是å¯å†™çš„,并把产生的文件写到这里。 +ä¸ºäº†æ–¹ä¾¿èµ·è§ (比如你想把它æ供给别人),你也å¯ä»¥æŠŠé©±åŠ¨å™¨ä¸Šçš„最终内容 +刻录回到 \DVD{} 上。 + +\section{\cmdname{tlmgr}: 管ç†ä½ çš„安装} +\label{sec:tlmgr} + + +\begin{figure}[tb] +\tlpng{tlmgr-gui}{\linewidth} +\caption{图形界é¢æ¨¡å¼è¿è¡Œçš„ \prog{tlmgr} 程åºã€‚ +安装包/集åˆ/方案仅在按下 `Load' 按钮åŽæ˜¾ç¤ºã€‚}\label{fig:tlmgr-gui} +\end{figure} + +\begin{figure}[tb] +\tlpng{tlmgr-config}{\linewidth} +\caption{图形界é¢æ¨¡å¼çš„ \texttt{tlmgr}: Configuration 选项å¡}\label{fig:tlmgr-config} +\end{figure} + +安装程åºä¼šè£…ä¸Šä¸€ä¸ªå« \prog{tlmgr} 的程åºï¼Œå®ƒå¯ä»¥ç”¨æ¥ç®¡ç†å®‰è£…åŽçš„ +ç³»ç»Ÿã€‚åƒ \prog{updmap}, \prog{fmtutil} å’Œ \prog{texconfig} è¿™äº›ç¨‹åº +ä»ç„¶åŒ…å«åœ¨å‘行版中,而且在将æ¥ä¹Ÿä¸ä¼šå‰”除,但是 \prog{tlmgr} 是一个 +优选的界é¢ã€‚它的功能包括: + +\begin{itemize*} +\item 列出方案 (scheme),集åˆå’Œå®‰è£…包; +\item 安装ã€å‡çº§ã€å¤‡ä»½ã€æ¢å¤ã€å¸è½½è½¯ä»¶åŒ…,并且能自动计算ä¾èµ–关系; +\item 查找软件包; +\item 列出和添加å¯æ‰§è¡Œæ–‡ä»¶çš„架构; +\item 改å˜å®‰è£…选项,比如纸张大å°å’Œæºæ–‡ä»¶ä½ç½® (å‚è§ç¬¬~\ref{sec:location}~节)。 +\end{itemize*} +\textit{警告:} \prog{tlmgr} 并ä¸ä¸ºåœ¨ \DVD 中è¿è¡Œè®¾è®¡ï¼Œä¹Ÿä»Žæœªåšè¿‡ç›¸ +关的测试。 + +\subsection{图形界é¢æ¨¡å¼çš„ \cmdname{tlmgr}} +\prog{tlmgr} å¯ä»¥ç”¨ä»¥ä¸‹å‘½ä»¤ä»¥å›¾å½¢æ¨¡å¼å¯åŠ¨ï¼š +\begin{alltt} +> \Ucom{tlmgr -gui} +\end{alltt} +Windows 下å¯ä»¥é€šè¿‡å¼€å§‹èœå•ï¼š\texttt{开始},\texttt{程åº}, +\texttt{TeX Live 2008},\texttt{TeX Live Manager}。 +在å‡å®šå®‰è£…包æºæ˜¯æœ‰æ•ˆä¸”å¯åŠçš„情况下,在点击 `Load' 以åŽï¼Œå®ƒä¼šåˆ—出 +所有å¯èŽ·å–的或已安装 (å‰é¢ç”¨ `(i)' 表示) 的软件包。 + +图~\ref{fig:tlmgr-config} 展示了é…置选项å¡ã€‚ + +\subsection{\cmdname{tlmgr} 命令行使用示例} + +下é¢çš„例å­ä¼šä»Žä¸€ä¸ªéžé»˜è®¤çš„地å€å®‰è£…一些包,其中包括一个新的`引擎'。 + +\begin{alltt} +> \Ucom{tlmgr -location http://172.16.18.1/tldev install collection-xetex xkeyval} +\end{alltt} +它会产生下é¢çš„输出: +\begin{fverbatim} +install: collection-xetex +install: arabxetex +install: euenc +install: bidi +install: fontspec +install: fontwrap +install: ifxetex +install: philokalia +install: polyglossia +install: xecyr +install: xecyr.i386-linux +install: xepersian +install: xetex +install: xetexconfig +install: xetex.i386-linux +running post install action for xetex +install: xetex-def +install: xetex-pstricks +install: xetexfontinfo +install: xltxtra +install: xunicode +install: xkeyval +running mktexlsr +mktexlsr: Updating /usr/local/texlive/2008/texmf/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-config/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-dist/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-doc/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/../texmf-local/ls-R... +mktexlsr: Updating /usr/local/texlive/2008/texmf-var/ls-R... +mktexlsr: Done. +regenerating fmtutil.cnf +running fmtutil-sys --missing +... +Transcript written on xelatex.log. +fmtutil: /usr/local/texlive/2008/texmf-var/web2c/xetex/xelatex.fmt installed. +\end{fverbatim} +如你所è§ï¼Œ\prog{tlmgr} 会安装所有ä¾èµ–的包,也会处ç†æ‰€æœ‰åŒ…括刷新文件å +æ•°æ®åº“å’Œé‡æ–°ç”Ÿæˆæ ¼å¼æ–‡ä»¶åœ¨å†…的所有必è¦çš„安装åŽå·¥ä½œã€‚(åœ¨è¿™é‡Œï¼Œæˆ‘ä»¬ç”Ÿæˆ +了新的 \XeTeX\ æ ¼å¼æ–‡ä»¶)。 + +下é¢è¿™ä¸ªä¾‹å­å®‰è£…了一个新的语言支æŒï¼Œä¹Ÿä¼šè§¦å‘æ ¼å¼æ–‡ä»¶çš„é‡æ–°ç”Ÿæˆã€‚ +\begin{alltt} +> \Ucom{tlmgr install collection-langdutch} +\end{alltt} +如果想得到安装包的说明: +\begin{alltt} +> \Ucom{tlmgr show collection-wintools} +\end{alltt} +会产生 +\begin{fverbatim} +Package: collection-wintools +Category: Collection +ShortDesc: Windows support programs +LongDesc: Utilities for Windows, since they are not readily available there: + gzip, chktex, jpeg2ps, unzip, wget, xpdf. +Installed: Yes +\end{fverbatim} +把你的整个安装更新到最新版本: +\begin{alltt} +> \Ucom{tlmgr update -all} +\end{alltt} +如果你觉得这样太冒险了,å¯ä»¥å…ˆå°è¯• +\begin{alltt} +> \Ucom{tlmgr update -all -dry-run} +\end{alltt} +或 +\begin{alltt} +> \Ucom{tlmgr update -list} +\end{alltt} +程åºçš„完整文档: +\begin{alltt} +> \Ucom{tlmgr -help} +\end{alltt} + +\section{有关 Windows å¹³å°çš„说明} +\label{sec:windows} + +\TL{} 拥有å¯è¿è¡ŒäºŽ Windows å’Œ Unix å¹³å°çš„å•ä¸€å®‰è£…程åºã€‚当然,åªæœ‰åœ¨æ”¾å¼ƒå¯¹ +较è€ç‰ˆæœ¬ Windows 的支æŒçš„情况下,这æ‰æˆä¸ºå¯èƒ½ã€‚因此,现在 \TL{} åªèƒ½å®‰è£… +于 Windows 2000 或更新的版本。 + + +\subsection{针对 Windows 的特å¾} +\label{sec:winfeatures} + +在 Windows 下,安装程åºé¢å¤–地åšäº†ä»¥ä¸‹ä¸€äº›äº‹æƒ…: +\begin{description} +\item[èœå•ä¸Žå¿«æ·æ–¹å¼ã€‚] 在开始èœå•ä¸ŠåŠ å…¥äº†æ–°çš„`\TL{}'程åºèœå•ï¼Œä¸»è¦æ˜¯ä¸€äº› +\GUI{} ç¨‹åº (如 \prog{tlmgr}ã€\prog{texdoctk}ã€PS\_View PostScript 预览程 +åº) 和一些文档的èœå•ã€‚PS\_View 还有一个桌é¢å¿«æ·æ–¹å¼ï¼Œå¯ä»¥ä½œä¸ºæ‹–放 PostScript +文件的目标。 +\item[自动设置环境å˜é‡ã€‚] ä¸å†éœ€è¦æ‰‹åŠ¨çš„é…置步骤。 +\item[å安装程åºã€‚] 安装程åºä¸º \TL{} 创建了`添加/删除程åº'æ¡ç›®ã€‚这与 +\prog{tlmgr} 的删除按钮相对应。 +\end{description} + +\subsection{附加的软件} + +\begin{figure}[tb] +\tlpng{psview}{.6\linewidth} +\caption{PS\_View:å¯ä»¥èŽ·å¾—很高的放大å€æ•°ï¼}\label{fig:psview} +\end{figure} + +为了使安装更加完整,\TL{} 需è¦æ”¯æŒé‚£äº› Windows 机器上ä¸å¸¸è§çš„软件包。 +\TL{} æ供了以下缺失的部分: +\begin{description} +\item[Perl å’Œ Ghostscript。] 由于 Perl å’Œ Ghostscript çš„é‡è¦æ€§ï¼Œ\TL{} +æ供了这些程åºçš„`éšè—'æ‹·è´ã€‚需è¦è¿™äº›è½¯ä»¶æ”¯æŒçš„ \TL{} 程åºçŸ¥é“它们的ä½ç½®ï¼Œ +但它们ä¸ä¼šé€šè¿‡çŽ¯å¢ƒå˜é‡å’Œæ³¨å†Œè¡¨è®¾ç½®æ¥æš´éœ²æ‰€åœ¨çš„ä½ç½®ã€‚它们ä¸æ˜¯å®Œæ•´çš„å‘è¡Œ +版本,也ä¸ä¼šä¸Žä»»ä½• Perl 或 Ghostscript 系统安装程åºå†²çªã€‚ +\item[命令行工具。] 与常è§çš„ \TL{} 二进制文件一起,安装了一些常è§çš„ +Unix 命令行工具的 Windows 移æ¤ç‰ˆæœ¬ã€‚它们包括 \cmdname{gzip}〠+\cmdname{chktex}ã€\cmdname{jpeg2ps}ã€\cmdname{unzip}ã€\cmdname{wget} +å’Œæ¥è‡ªäºŽ \cmdname{xpdf} 套装中的一些命令行工具。(虽然 \cmdname{xpdf} +æµè§ˆå™¨æœ¬èº«æ²¡æœ‰ Windows 版本,但 Sumatra \acro{PDF} æµè§ˆå™¨æ˜¯åŸºäºŽå®ƒçš„: +\url{http://blog.kowalczyk.info/software/sumatrapdf}。) +\item[\texttt{fc-cache}。] 有助于 \XeTeX{} 更有效率地处ç†å­—体。 +\item[PS\_View。] åŒæ—¶å®‰è£…的还有 PS\_View,一个具有自由许å¯è¯çš„全新的 +PostScript æµè§ˆå™¨ï¼›è§å›¾~\ref{fig:psview}。 +\end{description} +\begin{description} + \item[\texttt{support} 目录。] 在 \ref{sec:tld} 节æ到过它。这个目录包括å„ç§åœ¨ + \TeX{} 使用过程中éžå¸¸æœ‰ç”¨çš„软件,主è¦æ˜¯ä¸€äº› \TeX{} 文件编辑器和 \TeX{} + å‰ç«¯ã€‚这具目录中的软件ä¸å—安装程åºå½±å“。åŒæ—¶ï¼Œè¿™ä¸ªç›®å½•ä¸­è¿˜åŒ…括 \dvi{} + 预览器 \cmdname{dviout}ï¼›å‚è§ä¸‹ä¸€èŠ‚的介ç»ã€‚ +\end{description} + +\subsection{Dviout 预览器} + +ä¸å¹¸çš„是,\TL{} å‘行版没有为 Windows 预装 \dvi{} 预览器。ä¸è¿‡ï¼Œä½ å¯ä»¥ä»Ž +\path{support/dviout/} 目录安装 Toshio Oshima æ供的 +\prog{dviout}。这个目录下包括了一份简短的 \filename{README},æ述了如何为 +\TL{} 安装和é…ç½® \prog{dviout}。请在安装å‰ä»”细阅读。 + +当你第一次使用 \cmdname{dviout} 预览文件时,因为没有安装å±å¹•æ˜¾ç¤ºå­—体,它 +将生æˆå­—体。一段时间åŽï¼Œä½ æ‰€ä½¿ç”¨çš„大部分字体都将生æˆï¼ŒéšåŽï¼Œä½ å°†å¾ˆå°‘å†çœ‹ +到生æˆå­—体的窗å£ã€‚ä½ å¯ä»¥ä»Ž (éžå¸¸æ£’çš„) 在线帮助中获得更加详细的信æ¯ã€‚ + +\subsection{å¯ä¸‹è½½çš„附加软件的链接} + +ä½ å¯èƒ½è€ƒè™‘安装的其它工具的下载链接: +\begin{description} +\item[Ghostscript] \url{http://www.cs.wisc.edu/~ghost/} +\item[Perl] \url{http://www.activestate.com/},辅助的包å¯ä»¥ä»Ž \acro{CPAN} +下载,\url{http://www.cpan.org/} +\item[ImageMagick] \url{http://www.imagemagick.com},用于图åƒå¤„ç†åŠè½¬æ¢ +\item[NetPBM] \url{http://netpbm.sourceforge.net/},åŒæ ·ç”¨äºŽå›¾åƒ + +\item[é¢å‘ \TeX 的编辑器] 有很大选择余地,通常是一个用户å好的问题。下 +é¢æ˜¯ä¸€äº›ç²¾é€‰çš„编辑器,当然,没有ä¾ç‰¹å®šé¡ºåºæŽ’列: + \begin{itemize*} + \item \cmdname{GNU Emacs} 有 Windows 下å¯ç”¨çš„原生版本,å‚è§ \url{http://www.gnu.org/software/emacs/windows/ntemacs.html}。 + \item 带 Auc\TeX{} 支æŒçš„ \cmdname{Emacs} çš„ Windows 版本å¯åœ¨ \TL{} 下的 \path{support} 目录下找到;它的主页是 \url{http://www.gnu.org/software/auctex}。 + \item \cmdname{WinShell} å¯ä»¥åœ¨ \TL{} çš„ \path{support} 目录下找到。它的主页在 \url{http://www.winshell.de}。 + \item \cmdname{WinEdt} 是一个共享软件,å¯ä»¥ä»Ž \url{http://www.winedt.com} 获得。 + \item \cmdname{Vim} 是自由软件,å¯ä»¥ä»Ž \url{http://www.vim.org} 获得。 + \item TeXnicCenter 是自由软件,å¯ä»¥ä»Ž \url{http://www.toolscenter.org} å’Œ pro\TeX{}t å‘行版中获得。 + \item \cmdname{LEd} å¯ä»¥ä»Ž \url{http://www.ctan.org/support/LEd} 获得。 + \item \cmdname{SciTE} å¯ä»¥ä»Ž \url{http://www.scintilla.org/SciTE.html} 获得。 + \end{itemize*} +\end{description} + + +\subsection{User Profile 目录相当于主目录} +\label{sec:winhome} + +Windows 下对应于 Unix 下的主目录的是 \verb|%USERPROFILE%|。在 Windows XP +å’Œ Windows 2000 下,它通常ä½äºŽ \verb|C:\Documents and Settings\|ï¼› +在 Windows Vista 下是 \verb|C:\Users\|。通常情况下,在 +\filename{texmf.cnf} 文件和 \KPS{} 中,\verb|~| 在 Windows å’Œ Unix 下å‡å¯ä»¥ +进行åˆé€‚的展开。 + + +\subsection{Windows 注册表} +\label{sec:registry} + +Windows 将几乎所有的é…置数æ®å­˜æ”¾åœ¨æ³¨å†Œè¡¨ä¸­ã€‚注册表是包å«å‡ ä¸ªä¸»æ”¯çš„一系 +列分层组织的分支。对于安装的程åºè€Œè¨€ï¼Œæœ€é‡è¦çš„主支是 \path{HKEY_CURRENT_USER} +å’Œ \path{HKEY_LOCAL_MACHINE},通常简写为 \path{HKCU} å’Œ \path{HKLM}。注册表的 +\path{HKCU} 部分ä½äºŽç”¨æˆ·çš„主目录 (å‚è§ \ref{sec:winhome} 节)。\path{HKLM} +通常ä½äºŽ Windows 目录的å­ç›®å½•ä¸­ã€‚ + +在æŸäº›æƒ…况下,系统信æ¯å¯ä»¥ä»ŽçŽ¯å¢ƒå˜é‡èŽ·å¾—,但对于其它信æ¯ï¼Œå¦‚å¿«æ·æ–¹å¼çš„ä½ç½®ï¼Œ +则需è¦è®¿é—®æ³¨å†Œè¡¨ã€‚设置永久环境å˜é‡ä¹Ÿéœ€è¦è®¿é—®æ³¨å†Œè¡¨ã€‚ + + +\subsection{Windows æƒé™} +\label{sec:winpermissions} + +在较新的 Windows 版本中,普通用户与管ç†å‘˜æ˜¯æœ‰åŒºåˆ«çš„。åªæœ‰ç®¡ç†å‘˜èƒ½è‡ªç”±è®¿é—® +整个æ“作系统。尽管如此,在实际中,作为å—é™ç”¨æˆ·ä¸Žæ™®é€šç”¨æˆ·ï¼Œä½ æœ€èƒ½å¥½èƒ½å¤Ÿæ +述所处的用户类别:作为一个管ç†å‘˜æ˜¯æƒ¯ä¾‹ï¼Œè€Œä¸æ˜¯ç‰¹ä¾‹ã€‚无论如何,我们努力使得 +\TL{} 的安装ä¸éœ€è¦ç®¡ç†å‘˜æƒé™ã€‚ + +如果用户是管ç†å‘˜èº«ä»½ï¼Œå®‰è£…程åºå°†ä¼šä¸ºæ‰€æœ‰ç”¨æˆ·å»ºç«‹å¿«æ·æ–¹å¼ï¼Œå¹¶ä¸”修改 +系统环境å˜é‡ã€‚å¦åˆ™ï¼Œå®‰è£…程åºåªä¸ºå½“å‰ç”¨æˆ·åˆ›å»ºå¿«æ·æ–¹å¼ï¼Œå¹¶æ”¹å˜ç”¨æˆ·çŽ¯å¢ƒå˜é‡ã€‚ +作为管ç†å‘˜ï¼Œå¦‚果倾å‘于使用用户级设置,å¯ä»¥ä½¿ç”¨ \prog{install-tl} çš„ +\optname{non-admin} 选项。 + +无论管ç†å‘˜çŠ¶æ€å¦‚何,\TL{} 预设的默认根目录总是ä½äºŽ \verb|%PROGRAMFILES%| +下。对于当å‰ç”¨æˆ·å®‰è£…程åºæ€»æ˜¯è¦æµ‹è¯•ï¼Œæ ¹ç›®å½•æ˜¯å¦å¯å†™ã€‚ + +如果用户ä¸æ˜¯ç®¡ç†å‘˜ï¼Œå¹¶ä¸” \TeX{} å·²ç»å­˜åœ¨æœç´¢è·¯å¾„中,则å¯èƒ½ä¼šå‡ºçŽ°é—®é¢˜ã€‚因为有效路径是由系统路径åŽæŽ¥ç”¨æˆ·è·¯å¾„组æˆï¼Œæ–°å®‰è£…çš„ \TL{} å¯èƒ½æ°¸è¿œä¸ä¼šä¼˜å…ˆè¿è¡Œã€‚在这ç§æƒ…况下,一个å˜é€šçš„方案是,安装程åºä¸ºå‘½ä»¤æ示符创建快æ·æ–¹å¼ã€‚在这个快æ·æ–¹å¼ä¸­ï¼Œæ–°å®‰è£…çš„ \TL{} çš„å¯æ‰§è¡Œç›®å½•è¢«é¢„设于本地的æœç´¢è·¯å¾„中。当从这个快æ·æ–¹å¼å¯åŠ¨å‘½ä»¤è¡Œä»»åŠ¡æ—¶ï¼Œä¾¿å¯ä»¥ä½¿ç”¨æ–°çš„ \TL{}。 + + +\section{Web2C 用户指å—} + +\Webc{} 是一整套 \TeX{} 相关程åºçš„集åˆï¼š\TeX{} 本身ã€\MF{}ã€\MP{}ã€\BibTeX{}, +等等。它是 \TL{} 的核心。\Webc{} 的主页åŠæœ€æ–°çš„手册等都在 +\url{http://tug.org/web2c}。 + +我们简å•çš„介ç»ä¸€ä¸‹å®ƒçš„历å²ï¼šæœ€æ—©å®ƒæ˜¯ç”± Tomas Rokicki 在 1987 年实现的,他开å‘了第一套 +å°† \TeX{} 系统的代ç è½¬æ¢ä¸º C 语言代ç çš„系统,基于的是 Unix 下 change files +的原ç†ï¼Œchange files çš„ +工作是 Howard Trickey å’Œ Pavel Curtis 完æˆçš„。Tim Morgan åŽæ¥æˆä¸ºäº†è¿™å¥—系统的维护 +者,在这期间,软件的å称改为了 Web-to-C\@。在许多其他贡献者的帮助下,1990 å¹´ Karl Berry +接手了这个工作,到 1997 年,他把这项工作交给了 Olaf Weber。Olaf Weber 在 2006 å¹´åˆ +把这项工作交还给了 Karl。 + +\Webc{} 系统å¯ä»¥åœ¨ Unixã€32 ä½ Windows 系统ã€\MacOSX{} 和其他的一些æ“作系统下è¿è¡Œã€‚ +它使用的是 Knuth 用 \web{} 文学编程语言编写的 \TeX{} 和其他基本程åºçš„原始代ç ï¼Œå°†å…¶è½¬æ¢ä¸º C +æºç ã€‚用这ç§æ–¹æ³•å¤„ç†çš„核心的 \TeX{} 程åºåŒ…括: + +\begin{cmddescription} +\item[bibtex] 维护å‚考文献。 +\item[dmp] 从 \cmdname{troff} æ ¼å¼è½¬æ¢ä¸º MPX (\MP{} 图片)。 +\item[dvicopy] 展开 \dvi{} 中的虚拟字体 (virtual font) 引用。 +\item[dvitomp] å°† \dvi{} 转æ¢ä¸º MPX (MetaPost 图片)。 +\item[dvitype] å°† \dvi{} 转æ¢ä¸ºå¯è¯»æ–‡æœ¬ã€‚ +\item[gftodvi] ç”Ÿæˆ Generic æ ¼å¼å­—体的 proofsheet。 +\item[gftopk] å°† Generic æ ¼å¼å­—体转æ¢ä¸º packed æ ¼å¼å­—体。 +\item[gftype] å°† Generic æ ¼å¼å­—体转æ¢ä¸ºå¯è¯»æ–‡æœ¬ã€‚ +\item[makempx] 排版 \MP{} label。 +\item[mf] 创建字体。 +\item[mft] 以漂亮的方å¼æŽ’版输出 \MF{} 的代ç ã€‚ +\item[mpost] 创建技术性æ’图。 +\item[mpto] 展开 \MP{} çš„ label。 +\item[newer] 比较文件的修改时间。 +\item[patgen] 创建断字规则文件。 +\item[pktogf] å°† Packed æ ¼å¼å­—体转æ¢ä¸º generic æ ¼å¼å­—体。 +\item[pktype] å°† PK æ ¼å¼è½¬æ¢ä¸ºå¯è¯»çš„文本。 +\item[pltotf] 将纯文本的 property list 转æ¢ä¸º TFM æ ¼å¼ã€‚ +\item[pooltype] 显示 \web{} çš„ pool 文件。 +\item[tangle] å°† \web{} 转æ¢ä¸º Pascal 代ç ã€‚ +\item[tex] 排版。 +\item[tftopl] å°† TFM æ ¼å¼è½¬æ¢ä¸ºçº¯æ–‡æœ¬çš„ property list æ ¼å¼ã€‚ +\item[vftovp] 将虚拟字体格å¼è½¬æ¢ä¸º virtual property list æ ¼å¼ã€‚ +\item[vptovf] å°† virtual property list æ ¼å¼è½¬æ¢ä¸ºè™šæ‹Ÿå­—体格å¼ã€‚ +\item[weave] å°† \web{} 转æ¢ä¸º \TeX。 +\end{cmddescription} + +\noindent 这些程åºçš„详细功能和调用语法都在其å„自软件包的文档中有说明,在 \Webc{} çš„æ–‡ +档中也有相关介ç»ã€‚ä¸è¿‡ï¼Œæœ‰äº›è§„则对所有这些程åºéƒ½æ˜¯é€šç”¨çš„,了解这些规则有助于你更好的使用 +\Webc{}。 + +所有的程åºéƒ½æŽ¥å—这些 \GNU 标准的选项: +\begin{ttdescription} +\item[-{}-help] 显示基本使用说明。 +\item[-{}-verbose] 显示详细的执行过程。 +\item[-{}-version] 显示版本信æ¯ï¼Œç„¶åŽé€€å‡ºã€‚ +\end{ttdescription} + +所有的 \Webc{} 程åºå‡ä½¿ç”¨ \KPS{} (\url{http://tug.org/kpathsea}) 路径æœç´¢åº“æ¥æŸ¥æ‰¾æ–‡ä»¶ï¼Œ +这套库结åˆçŽ¯å¢ƒå˜é‡å’Œé…置文件的 +使用æ¥ä¼˜åŒ–å¤§é‡ \TeX{} 文件的æœç´¢ã€‚\Webc{} å¯ä»¥åœ¨å¤šäºŽä¸€å¥—的目录树下执行查找,这å¯ä»¥æ–¹ +便维护类似 \TeX{} 标准å‘行版和本地版本的扩展这样两套目录树。为了优化æœç´¢çš„速度,æ¯ä¸ªç›® +录树的顶层目录下都有一个 \file{ls-R} 文件,这个文件里包å«äº†æ‰€æœ‰æ­¤ç›®å½•ä¸‹æ–‡ä»¶çš„å称和对 +应的相对路径。 + +\subsection{Kpathsea 路径æœç´¢} +\label{sec:kpathsea} + +我们首先介ç»ä¸€ä¸‹ \KPS{} 库的的通用路径æœç´¢æ–¹å¼ã€‚ + +我们将目录å称称作\emph{路径元素},而把用冒å·æˆ–者分å·åˆ†éš”的路径元素列表称 +作\emph{æœç´¢è·¯å¾„}。æœç´¢è·¯å¾„å¯èƒ½æ˜¯è®¸å¤šç§æ¥æºçš„组åˆï¼Œæ¯”如在 \samp{.:/dir} 路径下 +æœç´¢ \samp{my-file} 这个文件,\KPS{} å°†é€ä¸ªå°è¯•è·¯å¾„中的æ¯ä¸ªå…ƒç´ ï¼šé¦–先是 +\file{./my-file},然åŽæ˜¯ \file{/dir/my-file},并返回找到的第一个结果 (或者 +也å¯ä»¥è¿”回所有的结果)。 + +为了符åˆæ‰€æœ‰æ“作系统下的习惯,\KPS{} åœ¨éž Unix 系统下使用的路径分隔符å¯èƒ½ä¸æ˜¯å†’å· +(\samp{:}) å’Œæ–œæ  (\samp{/})。 + +在检查一个具体的路径元素 \var{p} 时,\KPS{} 首先检查是å¦æœ‰ç¬¦åˆ \var{p} 的文件å +æ•°æ®åº“ (è§ç¬¬ \pageref{sec:filename-database} 页的``文件åæ•°æ®åº“'') 存在,也就是说, +是å¦æœ‰æ•°æ®åº“æ­£å¥½å¯¹åº”ç€ \var{p} 的一个å‰ç¼€ã€‚如果存在,就在数æ®åº“中寻找符åˆçš„路径åŽç¼€ã€‚ + +è¦æ˜¯æ²¡æœ‰è¿™ç§æ•°æ®åº“存在ã€åˆæˆ–者所有的数æ®åº“都ä¸èƒ½å’ŒæŒ‡å®šçš„路径å‰ç¼€åŒ¹é…上ã€å†æˆ–者找到的数 +æ®åº“里没有进一步的匹é…,就è¦æœç´¢æ–‡ä»¶ç³»ç»Ÿäº† (å‰æ是我们没在路径å‰åŠ ä¸Š \samp{!!} ï¼Œåˆ +或者æœç´¢æ—¶å°±æŒ‡å®šäº†è¿™æ˜¯ä¸€æ¬¡``必定存在 (must exist)''åž‹çš„æœç´¢æ–¹å¼)。此时 \KPS{} å°† +æ ¹æ®è·¯å¾„元素构建一个需è¦æ£€æŸ¥çš„目录列表,é€ä¸ªå°è¯•è¿™äº›ç›®å½•ï¼Œè¯•å›¾æ‰¾åˆ°æŒ‡å®šçš„文件。 + +æœç´¢ \samp{.vf} 文件和 \TeX{} 用 \cs{openin} 命令读入的文件时,会指定``文件必 +定存在 (must exist)''这个选项。而有些文件 (比如 \file{cmr10.vf}) å¯èƒ½ä¸å­˜åœ¨ï¼Œ +花费时间在ç£ç›˜ä¸Šå¯¹å®ƒè¿›è¡Œæœç´¢æ˜¯ä¸å€¼å¾—的。因此,如果你安装了新的 \samp{.vf} 文件åŽæ²¡æœ‰ +æ›´æ–° \file{ls-R},那这个文件将永远找ä¸åˆ°ã€‚æœç´¢æ—¶ä¼šä¼˜å…ˆåœ¨æ•°æ®åº“寻找,然åŽå†åŽ»æœç´¢ç£ç›˜ã€‚ +一旦找到了就立å³åœæ­¢æœç´¢ï¼Œè¿”回结果。 + +尽管最简å•ä¹Ÿæœ€å¸¸è§çš„路径元素是目录å称,\KPS{} æœç´¢çš„路径里还是å¯ä»¥ä½¿ç”¨å…¶ä»–é¢å¤–功能的: +多层默认值,环境å˜é‡å称ã€é…置文件值ã€ç”¨æˆ·ä¸»ç›®å½•ï¼Œä»¥åŠé€’å½’å¼å­ç›®å½•æŸ¥æ‰¾ã€‚所以我们把 \KPS{} +å°†æœç´¢è·¯å¾„å˜æ¢ä¸ºä¸€ä¸ªæˆ–多个基本目录å的过程称为\emph{展开}è·¯å¾„å…ƒç´ çš„è¿‡ç¨‹ã€‚å±•å¼€çš„æ–¹å¼ +按执行的顺åºåœ¨åŽç»­å°èŠ‚里有å™è¿°ã€‚ + +注æ„,如果æœç´¢çš„文件给出了ç»å¯¹è·¯å¾„或者明确的相对路径,å³ä»¥ \samp{/} 或 \samp{./} 或 +\samp{../} 起始,\KPS{} å°†åªæ£€æŸ¥è¯¥æ–‡ä»¶æ˜¯å¦å­˜åœ¨ã€‚ + +\ifSingleColumn +\else +\begin{figure*} +\verbatiminput{examples/ex5.tex} +\setlength{\abovecaptionskip}{0pt} + \caption{一份示例性的é…置文件的例å­} + \label{fig:config-sample} +\end{figure*} +\fi + +\subsubsection{路径的æ¥æº} +\label{sec:path-sources} + +æœç´¢è·¯å¾„å¯èƒ½æ¥è‡ªè®¸å¤šåœ°æ–¹ï¼Œ\KPS{} 是按照下é¢çš„顺åºæŸ¥æ‰¾çš„: + +\begin{enumerate} +\item + 用户设置的环境å˜é‡ï¼Œä¾‹å¦‚ \envname{TEXINPUTS}\@。以 . 连接æŸä¸ªç¨‹åºå称的环境å˜é‡ +有更高的优先级,比如若正在è¿è¡Œçš„程åºæ˜¯ \samp{latex},那 \envname{TEXINPUTS.latex} +将比 \envname{TEXINPUTS} 优先级更高。 +\item + 专门针对æŸä¸ªç¨‹åºçš„é…置文件,比如 \cmdname{dvips} çš„ \file{config.ps} 里出现 +\samp{S /a:/b} 这样一行。 +\item \KPS{} é…置文件 \file{texmf.cnf},包å«ç±»ä¼¼ + \samp{TEXINPUTS=/c:/d} 这样的一行 (å‚è§ä¸‹é¢çš„解释)。 +\item 编译时的缺çœå€¼ã€‚ +\end{enumerate} +\noindent ä½ å¯ä»¥é€šè¿‡è°ƒè¯•é€‰é¡¹çœ‹åˆ°æ‰€æœ‰çš„这些值 (å‚è§ç¬¬ \pageref{sec:debugging} 页的 +``调试æ“作'')。 + +\subsubsection{é…置文件} + +\begingroup\tolerance=3500 +\KPS{} 读入\emph{è¿è¡Œæ—¶é…置文件} \file{texmf.cnf} æ¥èŽ·å¾—æœç´¢è·¯å¾„和其他定义。 +而这个 \file{texmf.cnf} 存放的路径则是在 \envname{TEXMFCNF} å˜é‡é‡Œå®šä¹‰çš„, +默认是在 \file{texmf/web2c} 目录下。æœç´¢è·¯å¾„里\emph{所有的} \file{texmf.cnf} +文件都会被读入,而先读入的优先级更高。所以,如果æœç´¢è·¯å¾„是 \verb|.:$TEXMF|,那么 +文件 \file{./texmf.cnf} 里é¢çš„值è¦æ¯” \verb|$TEXMF/texmf.cnf| 里边的优先。 +\endgroup + +\begin{itemize} +\item + 以 \code{\%} 表示å•è¡Œæ³¨é‡Šã€‚ +\item + 忽略空行。 +\item + 行末的 \bs{} 作为连接符,å³æŠŠä¸‹ä¸€è¡Œç›´æŽ¥æŽ¥ä¸Šã€‚但ä¿ç•™ä¸‹ä¸€è¡Œè¡Œé¦–的空白。 +\item + 所有剩余的行格å¼å¦‚下: +\begin{alltt} + \var{variable}[.\var{progname}] [=] \var{value} +\end{alltt}% + \samp{=} å·å’Œç©ºç™½éƒ½æ˜¯å¯é€‰çš„。 +\item + \ttvar{variable} (å˜é‡) å…许包å«ä»»ä½•å­—符,除空白ã€\samp{=}ã€\samp{.} + 之外。ä¸è¿‡åªç”¨ \samp{A-Za-z\_} 是最ä¿é™©çš„。 +\item + 如果 \samp{.\var{progname}} (程åºå) 存在,则该定义åªå¯¹æ­£åœ¨è¿è¡Œçš„åå« + \texttt{\var{progname}} 或 \texttt{\var{progname}.exe} + 的程åºèµ·ä½œç”¨ã€‚è¿™å¯ä»¥è®©ç»™ä¸åŒç§ç±»çš„ \TeX{} 程åºè®¾ç½®ä¸åŒçš„æœç´¢è·¯å¾„。 +\item \var{value} (值) å…许任何 \code{\%} 与 \samp{@} 之外的字符出现。 + ä¸æ”¯æŒåœ¨ç­‰å·å³ä¾§ä½¿ç”¨ \code{\$\var{var}.\var{prog}} 这样的写法。 + 如果在 Unix 下,\var{value} 中的 \samp{;}\ 字符会被转æ¢ä¸º + \samp{:}。如果你希望让 Unix, \acro{MS-DOS} å’Œ Windows 里都用åŒä¸€ä¸ª + \file{texmf.cnf},这会很有用。 +\item + 在读入所有定义åŽå†å¼€å§‹å±•å¼€ï¼Œæ‰€ä»¥ä½ å¯ä»¥å¼•ç”¨åŽè¾¹æ‰å®šä¹‰çš„å˜é‡ã€‚ +\end{itemize} +展示上é¢æ‰€æœ‰å†…容的一段é…置文件 +\ifSingleColumn +如下: + +\verbatiminput{examples/ex5.tex} +\else +è§å›¾~\ref{fig:config-sample}. +\fi + +\subsubsection{路径展开} +\label{sec:path-expansion} + +å’Œ Unix shell 类似,\KPS{} 能够识别æœç´¢è·¯å¾„中的特殊字符。比如一个å¤æ‚的路径 +\verb+~$USER/{foo,bar}//baz+,将展开为这样的å­ç›®å½•ï¼šåœ¨ \texttt{\$USER} +的主目录下的 \file{foo} 或 \file{bar} ç›®å½•ä¸­ï¼Œä¸”åŒ…å« \file{baz} +文件或目录。这ç§å±•å¼€å°†åœ¨ä¸‹é¢è§£é‡Šã€‚ +%$ +\subsubsection{默认展开} +\label{sec:default-expansion} + +\tolerance=2500 +如果最高优先级 (å‚è§ç¬¬ \pageref{sec:path-sources} 页的``路径æ¥æº'') +çš„æœç´¢è·¯å¾„中包å«ä¸€ä¸ª\emph{é¢å¤–的冒å·} (å³å‰ç½®ã€åŽç½®æˆ–连续的冒å·),\KPS{} 将在 +此处æ’入次高优先级的æœç´¢è·¯å¾„。如果æ’入的那个路径里也有é¢å¤–的冒å·ï¼ŒåŒæ ·çš„步骤将å‘生 +在更次以åŠä¼˜å…ˆçº§çš„路径上。å‡è®¾çŽ¯å¢ƒå˜é‡è®¾ç½®ä¸º + +\tolerance=1500 + +\begin{alltt} +> \Ucom{setenv TEXINPUTS /home/karl:} +\end{alltt} + +而 \file{texmf.cnf} 里的 \code{TEXINPUTS} 值为 + +\begin{alltt} + .:\$TEXMF//tex +\end{alltt} + +则用于æœç´¢çš„最终值为: + +\begin{alltt} + /home/karl:.:\$TEXMF//tex +\end{alltt} + +因为没必è¦æ’入多个相åŒçš„值,所以 \KPS{} åªä¼šä¿®æ”¹ä¸€ä¸ªé¢å¤–çš„ \samp{:},其他的ä¸å˜ã€‚ +它首先检查å‰ç½®çš„ \samp{:},然åŽæ˜¯æœ«å°¾çš„ \samp{:},最åŽæ˜¯è¿žç»­çš„ \samp{:}。 + +\subsubsection{大括å·å±•å¼€} + +大括å·å±•å¼€æ˜¯ä¸€é¡¹æœ‰ç”¨çš„特性,其作用是把 \verb+v{a,b}w+ 这样的转æ¢ä¸º +\verb+vaw:vbw+,å…许嵌套使用。通过把 \code{\$TEXMF} 赋值为一个括å·åˆ—表, +å¯ä»¥æž„造出多套 \TeX{} 层级结构。例如在 \file{texmf.cnf} 里有下é¢çš„定义 +(è¿™åªæ˜¯ä¸ªè¿‘似的例å­ï¼Œå®žé™…情况定义的目录树还è¦æ›´å¤š): +\begin{verbatim} + TEXMF = {$TEXMFHOME,$TEXMFLOCAL,!!$TEXMFVAR,!!$TEXMFMAIN} +\end{verbatim} +这样一æ¥ï¼Œå½“你设置 +\begin{verbatim} + TEXINPUTS = .;$TEXMF/tex// +\end{verbatim} +%$ +的时候,检查完当å‰ç›®å½•åŽï¼Œä¾æ¬¡æ£€æŸ¥çš„路径是 +\code{\$TEXMFHOME/tex}, \code{\$TEXMFLOCAL/tex}, \code{\$TEXMFVAR/tex} +å’Œ \code{\$TEXMFMAIN/tex} (åŽä¸¤ä¸ªåªåœ¨ \file{ls-R} æ•°æ®åº“中æœç´¢)。这样维护 +两套并行的 \TeX{} 结构就很方便的,一套是``固定 (frozen)''çš„ (比如放在 \CD\ 上) +而å¦ä¸€å¥—是在新版本出现时就更新的。因为所有的定义里都用到了 \code{\$TEXMF}, +所以你å¯ä»¥ç¡®ä¿¡æ—¶å¸¸æ›´æ–°çš„那个版本肯定是先被找到的。 + +\subsubsection{å­ç›®å½•å±•å¼€} +\label{sec:subdirectory-expansion} + +在路径元素里的目录å称 \var{d} åŽé¢æŽ¥è¿žä½¿ç”¨ä¸¤ä¸ªæˆ–更多连续的斜æ ï¼Œè¡¨ç¤º \var{d} çš„ +所有å­ç›®å½•ï¼šé¦–先是直接处于 \var{d} 下的那些,然åŽæ˜¯è¿™äº›å­ç›®å½•çš„å­ç›®å½•ï¼Œä¾æ­¤ç±»æŽ¨ã€‚ +æ¯å±‚的目录出现的顺åºæ˜¯\emph{ä¸ä¸€å®š}的。 + +如果你在 \samp{//} åŽé¢è¿˜æŒ‡å®šäº†æ–‡ä»¶å,匹é…çš„å°†åªæ˜¯é‚£äº›åŒ…å«äº†æŒ‡å®šæ–‡ä»¶çš„路径。 +比如 \samp{/a//b} 将展开为路径 \file{/a/1/b}, \file{/a/2/b}, +\file{/a/1/1/b} 等等,但ä¸ä¼šå±•å¼€ä¸º \file{/a/b/c} 或 \file{/a/1}。 + +å¯ä»¥åœ¨å•ä¸ªè·¯å¾„元素里使用多个 \samp{//},但出现在路径开头的 \samp{//} +将被忽略。 + +\subsubsection{特殊字符与其æ„义:简è¦è¯´æ˜Ž} + +下é¢çš„列表总结了 \KPS{} é…置文件中出现的特殊字符: + +% need a wider space for the item labels here. +\newcommand{\CODE}[1]{\makebox[3em][l]{\code{#1}}} +\begin{ttdescription} +\item[\CODE{:}] 路径分隔符,在路径的å‰è¾¹æˆ–者末尾时表示默认的展开方å¼ã€‚\par +\item[\CODE{;}] éž Unix 系统下的路径分隔符 (å’Œ \code{:} 功能一样)。 +\item[\CODE{\$}] å˜é‡å±•å¼€ã€‚ +\item[\CODE{\string~}] 表示用户的个人主目录。 +\item[\CODE{\char`\{...\char`\}}] Brace expansion. +\item[\CODE{//}] å­ç›®å½•å±•å¼€ (å¯ä»¥å‡ºçŽ°åœ¨é™¤è·¯å¾„开头外的任æ„ä½ç½®)。 +\item[\CODE{\%}] 注释的起始。 +\item[\CODE{\bs}] 连接下一行的字符 (以支æŒè·¨è¡Œçš„设置项)。 +\item[\CODE{!!}] \emph{åª}在数æ®åº“中æœç´¢æ–‡ä»¶ï¼Œ\emph{ä¸}æœå¯»ç£ç›˜ã€‚ +\end{ttdescription} + + +\subsection{文件åæ•°æ®åº“} +\label{sec:filename-database} + +\KPS{} 使用了一些方法æ¥å‡å°‘æœç´¢æ—¶çš„ç£ç›˜è®¿é—®æ¬¡æ•°ã€‚å°½ç®¡å¦‚æ­¤ï¼Œå¦‚æžœå®‰è£…çš„æ–‡ä»¶è¶³å¤Ÿå¤šï¼Œåœ¨å„ +个å¯èƒ½çš„目录下æœç´¢æŸä¸ªæ–‡ä»¶ä»ç„¶å¯èƒ½èŠ±ä¸Šå¾ˆé•¿æ—¶é—´ (尤其是在必须é历数百个字体目录的时候)。 +因此,\KPS{} 使用一个专门构建的纯文本``æ•°æ®åº“''文件,这个文件å«åš \file{ls-R},它将 +文件和目录进行映射,é¿å…对ç£ç›˜çš„大é‡æœç´¢ã€‚ + +第二个数æ®åº“ \file{aliases} å…许你给 \file{ls-R} 中的文件指定其他的å字。有助于 +帮助æºæ–‡ä»¶ç¬¦åˆ \acro{DOS} 8.3 命å规范。 + +\subsubsection{文件åæ•°æ®åº“} +\label{sec:ls-R} + +å‰è¾¹å·²ç»è§£é‡Šè¿‡ï¼Œä¸»æ–‡ä»¶åæ•°æ®åº“çš„å称必须是 \file{ls-R}。你å¯ä»¥åœ¨æ¯ä¸ªéœ€è¦æœç´¢çš„ +\TeX{} 目录树 (缺çœæ˜¯ \code{\$TEXMF}) 下放置一个这样的文件。\KPS{} 在 +\code{TEXMFDBS} 指定的路径中寻找这些 \file{ls-R} 文件。 + +推è使用å‘行版中包å«çš„ \code{mktexlsr} 脚本æ¥åˆ›å»ºå’Œç»´æŠ¤ \samp{ls-R} 文件。å„ç±» +\samp{mktex} 脚本也å¯èƒ½ä¼šé—´æŽ¥è°ƒç”¨è¿™ä¸ªè„šæœ¬ã€‚实际上,这个脚本åªæ˜¯æ‰§è¡Œä¸‹é¢çš„命令: + +\begin{alltt} +cd \var{/your/texmf/root} && \path|\|ls -1LAR ./ >ls-R +\end{alltt} + +æ„味ç€ä½ çš„系统的 \code{ls} 命令的输出格å¼å¿…须正确 (\GNU \code{ls} 是没 +问题的)。è¦ä¿è¯æ•°æ®åº“åŠæ—¶æ›´æ–°ï¼Œæœ€ç®€å•çš„方法是定期通过 \code{cron} æ¥é‡å»ºã€‚ + +如果文件在数æ®åº“中找ä¸åˆ°ï¼Œç¼ºçœæƒ…况下 \KPS{} 会在ç£ç›˜ä¸Šæœç´¢ã€‚如果æŸä¸ªç‰¹å®šçš„路径元素 +是以 \samp{!!} 起始的,就\emph{åªä¼š}在针对这一元素的数æ®åº“中查找而ä¸æœç´¢ç£ç›˜ã€‚ + + +\subsubsection{kpsewhich: 独立的路径æœç´¢} +\label{sec:invoking-kpsewhich} + +\texttt{kpsewhich} 程åºå°†è·¯å¾„æœç´¢ä»Žå…¶ä»–专用程åºä¸­ç‹¬ç«‹å‡ºæ¥ï¼Œå®ƒå¯ä»¥ä½œä¸ºç±»ä¼¼ \code{find} +一样的程åºï¼Œä¸“门在 \TeX{} 层级结构中定ä½æ–‡ä»¶ (这在å‘行版中的 \samp{mktex}\dots\ +脚本中使用得éžå¸¸å¤š)。 + +\begin{alltt} +> \Ucom{kpsewhich \var{option}\dots{} \var{filename}\dots{}} +\end{alltt} +\ttvar{option} 处的选项å¯ä»¥ç”¨ \samp{-} 也å¯ä»¥ç”¨ \samp{-{}-} æ¥èµ·å§‹ï¼Œå¹¶æŽ¥å— +任何ä¸é€ æˆç–‘义的缩写。 + +\KPS{} 将第一个éžé€‰é¡¹çš„å‚数作为文件åæ¥æŸ¥æ‰¾ï¼Œå¹¶è¿”回找到的第一个文件。它ä¸æä¾› +寻找所有相åŒå称文件的功能 (ä½ å¯ä»¥ä½¿ç”¨ Unix çš„ \samp{find} 程åºæ¥è¾¾åˆ°è¿™ä¸ªåŠŸèƒ½)。 + +下é¢ä»‹ç»äº†ä¸€äº›æ¯”较常è§çš„选项。 + +\begin{ttdescription} +\item[\texttt{-{}-dpi=\var{num}}]\mbox{} + 将解æžåº¦è®¾ç½®ä¸º \ttvar{num},这个选项åªå½±å“ \samp{gf} 文件和 \samp{pk} + 文件的查找。为了与 \cmdname{dvips} 兼容,æä¾› \samp{-D} + 这个åŒä¹‰çš„å‚数,默认值是 600。 + +\item[\texttt{-{}-format=\var{name}}]\mbox{}\\ + 将查找的文件格å¼è®¾ç½®ä¸º \ttvar{name}。默认情况下是通过文件åæ¥çŒœæµ‹æ ¼å¼çš„。对于扩展å +有二义性的格å¼ï¼Œæ¯”如 \MP{} 支æŒæ–‡ä»¶å’Œ \cmdname{dvips} é…置文件,必须以 \KPS{} 已知 +çš„å称指定格å¼ï¼Œæ¯”如 \texttt{tex} 或 \texttt{enc files}。è¿è¡Œ + \texttt{kpsewhich -{}-help} 会显示格å¼çš„列表。 + +\item[\texttt{-{}-mode=\var{string}}]\mbox{}\\ + 设置模å¼ä¸º \ttvar{string},åªå½±å“ \samp{gf} å’Œ \samp{pk} + 文件的查找。默认情况匹é…所有的模å¼ã€‚ +\item[\texttt{-{}-must-exist}]\mbox{}\\ + 尽一切å¯èƒ½æ‰¾åˆ°æ–‡ä»¶ï¼ŒåŒ…括直接在ç£ç›˜ä¸Šæœå¯»ã€‚默认情况下为了效率考虑,åªæ£€æŸ¥ + \file{ls-R} æ•°æ®åº“里的内容。 +\item[\texttt{-{}-path=\var{string}}]\mbox{}\\ + ä¸é€šè¿‡æ–‡ä»¶åæ¥çŒœæµ‹è·¯å¾„,沿 \ttvar{string} 指出的路径æœç´¢ + (也使用冒å·åˆ†éš”)ã€‚æ”¯æŒ \samp{//} 和所有常è§çš„展开方å¼ã€‚\samp{-{}-path} 选项 + å’Œ \samp{-{}-format} 选项是互斥的。 +\item[\texttt{-{}-progname=\var{name}}]\mbox{}\\ + 将执行查找的程åºå称设为 \texttt{\var{name}}。 + 这会通过 \texttt{.\var{progname}} 特性影å“æœç´¢è·¯å¾„。 + 缺çœå€¼æ˜¯ \cmdname{kpsewhich}。 +\item[\texttt{-{}-show-path=\var{name}}]\mbox{}\\ + 显示用于查找 \texttt{\var{name}} 类型文件的路径。和 \samp{-{}-format} + 选项一样,å¯ä»¥ä½¿ç”¨æ‰©å±•å (\code{.pk}, \code{.vf}, 等等) 也å¯ä»¥ä½¿ç”¨å…¨å。 +\item[\texttt{-{}-debug=\var{num}}]\mbox{}\\ + 将调试选项 (等级) 设置为 \texttt{\var{num}}。 +\end{ttdescription} + + +\subsubsection{使用举例} +\label{sec:examples-of-use} + +现在我们看看实际使用 \KPS{} 的例å­ã€‚这里是一个简å•çš„æœç´¢ï¼š + +\begin{alltt} +> \Ucom{kpsewhich article.cls} + /usr/local/texmf-dist/tex/latex/base/article.cls +\end{alltt} +我们寻找的是 \file{article.cls} 文件。因为 \samp{.cls} åŽç¼€å·²ç»è¯´æ˜Žäº†æ–‡ä»¶çš„类型,所以 +我们ä¸éœ€è¦ç‰¹åˆ«æŒ‡æ˜ŽæŸ¥æ‰¾çš„是 \optname{tex} 类型的文件 (也就是è¦åœ¨ (\TeX{} æºæ–‡ä»¶ç›®å½•ä¸‹æŸ¥æ‰¾)。 +我们在 \samp{texmf-dist} çš„ \file{tex/latex/base} å­ç›®å½•ä¸‹æ‰¾åˆ°äº†è¿™ä¸ªæ–‡ä»¶ã€‚与之类似, +下列所有文件都顺利找到,因为其扩展å没有二义。 +\begin{alltt} +> \Ucom{kpsewhich array.sty} + /usr/local/texmf-dist/tex/latex/tools/array.sty +> \Ucom{kpsewhich latin1.def} + /usr/local/texmf-dist/tex/latex/base/latin1.def +> \Ucom{kpsewhich size10.clo} + /usr/local/texmf-dist/tex/latex/base/size10.clo +> \Ucom{kpsewhich small2e.tex} + /usr/local/texmf-dist/tex/latex/base/small2e.tex +> \Ucom{kpsewhich tugboat.bib} + /usr/local/texmf-dist/bibtex/bib/beebe/tugboat.bib +\end{alltt} + +å¦å¤–,最åŽä¸€ä¸ªæ˜¯ \textsl{TUGBoat} 文章的 \BibTeX{} å‚考文献数æ®åº“。 + +\begin{alltt} +> \Ucom{kpsewhich cmr10.pk} +\end{alltt} + +\file{.pk} 类型的字体ä½å›¾æ–‡ä»¶æ˜¯ç»™ \cmdname{dvips} 或者 \cmdname{xdvi} +è¿™ç§æ˜¾ç¤ºç¨‹åºæ供的。因为 \TL{} 里没有预生æˆçš„ Computer Modern \samp{.pk} +字体,所以没有找到任何内容\Dash \TL{} 默认使用 Type~1 版本的。 + +\begin{alltt} +> \Ucom{kpsewhich wsuipa10.pk} +\ifSingleColumn /usr/local/texmf-var/fonts/pk/ljfour/public/wsuipa/wsuipa10.600pk +\else /usr/local/texmf-var/fonts/pk/ljfour/public/ +... wsuipa/wsuipa10.600pk +\fi\end{alltt} + +而这个字体 (Washington 大学的一套注音字æ¯è¡¨) 就需è¦ç”Ÿæˆ \samp{.pk} 文件了。我们默认的 +\MF{} 模å¼æ˜¯ \texttt{ljfour},基础解æžåº¦æ˜¯ 600\dpi{} (dots per inch),所以会得到这样一个文件。 +\begin{alltt} +> \Ucom{kpsewhich -dpi=300 wsuipa10.pk} +\end{alltt} + +一旦指明我们需è¦å¯»æ‰¾çš„åªæ˜¯ 300\dpi{} 的文件时 (\texttt{-dpi=300}),就会å‘现系统里 +没有符åˆè¦æ±‚的文件。这样 \cmdname{dvips} 或 \cmdname{xdvi} 会使用 \cmdname{mktexpk} +脚本去创建所需的 \texttt{.pk} 文件。 + +下é¢æˆ‘们将注æ„åŠ›è½¬å‘ \cmdname{dvips} 的头文件和é…置文件。首先看看最常用的一个,\file{tex.pro} +prologue 文件,然åŽæ£€æŸ¥é€šç”¨é…置文件 \file{config.ps} å’Œ \PS{} 字体映射文件 +\file{psfonts.map}\Dash 从 2004 年开始,映射文件和编ç æ–‡ä»¶éƒ½åœ¨ \dirname{texmf} +目录树下有其自己的æœç´¢è·¯å¾„了。因为 \samp{.ps} åŽç¼€å¯èƒ½ä¼šæœ‰äºŒä¹‰ï¼Œæˆ‘们必须指明æ„æ€æ˜¯ +\optname{dvips config}。 + +\begin{alltt} +> \Ucom{kpsewhich tex.pro} + /usr/local/texmf/dvips/base/tex.pro +> \Ucom{kpsewhich --format="dvips config" config.ps} + /usr/local/texmf/dvips/config/config.ps +> \Ucom{kpsewhich psfonts.map} + /usr/local/texmf/fonts/map/dvips/updmap/psfonts.map +\end{alltt} + +这样我们å¯ä»¥æ›´ä»”细地分æžä¸€ä¸‹ \acro{URW} Times çš„ \PS{} 支æŒæ–‡ä»¶ã€‚ä¾ç…§æ ‡å‡†çš„字体 +命å方案,这些文件的å‰ç¼€æ˜¯ \samp{utm}。首先查询的是é…置文件,其中包å«çš„是 map +文件的å称: + +\begin{alltt} +> \Ucom{kpsewhich --format="dvips config" config.utm} + /usr/local/texmf-dist/dvips/psnfss/config.utm +\end{alltt} + +这个文件的内容是 + +\begin{alltt} + p +utm.map +\end{alltt} + +å³æŒ‡å‘ \file{utm.map} 文件,也就是我们下一步è¦æ‰¾çš„。 + +\begin{alltt} +> \Ucom{kpsewhich utm.map} + /usr/local/texmf-dist/fonts/map/dvips/times/utm.map +\end{alltt} + +这个 map 文件定义了 URW 集åˆä¸­çš„ Type~1 \PS{} 字体文件å。内容差ä¸å¤šæ˜¯ä¸‹è¾¹è¿™æ · +(我们åªåˆ—出了其中一部分): + +\begin{alltt} +utmb8r NimbusRomNo9L-Medi ... \Ucom{kpsewhich utmr8a.pfb} +\ifSingleColumn /usr/local/texmf-dist/fonts/type1/urw/times/utmr8a.pfb +\else /usr/local/texmf-dist/fonts/type1/ +... urw/utm/utmr8a.pfb +\fi\end{alltt} + +现在你å¯ä»¥å‘现,追寻æŸä¸ªæ–‡ä»¶çš„下è½æ˜¯å¦‚此方便。尤其是在你怀疑找到的文件错了的时候,这些 +功能éžå¸¸é‡è¦ï¼Œå› ä¸º \cmdname{kpsewhich} åªèƒ½å‘Šè¯‰ä½ æ‰¾åˆ°çš„第一个文件。 + +\subsubsection{调试æ“作} +\label{sec:debugging} + +有时你å¯èƒ½ä¼šéœ€è¦åˆ†æžç¨‹åºæ˜¯å¦‚何解æžæ–‡ä»¶å¼•ç”¨çš„。\KPS{} æ供了多层调试输出æ¥å®žçŽ°è¿™ä¸ªåŠŸèƒ½ï¼š + +\begin{ttdescription} +\item[\texttt{\ 1}] \texttt{stat} 调用 (ç£ç›˜ä¸Šçš„查询)。在 \file{ls-R} + æ•°æ®åº“åŠæ—¶æ›´æ–°çš„情况下几乎ä¸ä¼šæœ‰ä»€ä¹ˆè¾“出。 +\item[\texttt{\ 2}] 对散列表的引用 (例如 \file{ls-R} æ•°æ®åº“,映射文件,é…置文件)。 +\item[\texttt{\ 4}] 文件的打开与关闭æ“作。 +\item[\texttt{\ 8}] \KPS{} æœç´¢çš„文件类型的通用路径信æ¯ã€‚有助于寻找针对æŸä¸€æ–‡ä»¶çš„ +特定路径。 +\item[\texttt{16}] æ¯ä¸ªè·¯å¾„元素的目录列表 (åªåœ¨æœ¬åœ°ç£ç›˜ä¸Šæœç´¢æ—¶æœ‰ç”¨)。 +\item[\texttt{32}] 文件æœç´¢ã€‚ +\item[\texttt{64}] å˜é‡çš„值。 +\end{ttdescription} +等级 \texttt{-1} å°†å¯ç”¨ä¸Šè¿°æ‰€æœ‰é€‰é¡¹ï¼Œå®žé™…上这是最方便的设置方法了。 + +类似地,在 \cmdname{dvips} 程åºä¸­è®¾ç½®ä¸Šè¿°è°ƒè¯•é€‰é¡¹çš„组åˆï¼Œä½ å°±å¯ä»¥å‡º \cmdname{dvips} +是从哪里找到它所需的文件的。å¦ä¸€æ–¹é¢ï¼Œå¦‚果找ä¸åˆ°æŸä¸ªæ–‡ä»¶ï¼Œè°ƒè¯•è¾“出也会显示程åºä»Žå“ªäº›ç›®å½•è¿›è¡Œ +了查找,你也å¯ä»¥æ®æ­¤åˆ¤æ–­å‡ºé—®é¢˜å‡ºåœ¨å“ªé‡Œã€‚ + +一般而言,因为所有的程åºéƒ½åœ¨å…¶å†…部调用 \KPS{} 库,你å¯ä»¥è®¾ç½® \envname{KPATHSEA\_DEBUG} +环境å˜é‡æ¥é€‰æ‹©è°ƒè¯•å‚数,将这个å˜é‡è®¾ç½®ä¸ºä¸Šè¿°å‚æ•°çš„ç»„åˆ (加法) 以获得对应的功能。 + +(Windows 用户请注æ„:因为在 Windows 下ä¸å®¹æ˜“把所有信æ¯éƒ½é‡å®šå‘到固定的文件中,为了方便诊断, +ä½ å¯ä»¥ä¸´æ—¶è®¾ç½® \texttt{SET KPATHSEA\_DEBUG\_OUTPUT=err.log})。 + +让我们以一个简å•çš„ \LaTeX{} æºæ–‡ä»¶ \file{hello-world.tex} 为例,其内容如下: +\begin{verbatim} + \documentclass{article} + \begin{document} + Hello World! + \end{document} +\end{verbatim} +这个å°æ–‡ä»¶åªä½¿ç”¨äº† \file{cmr10} 字体,我们å¯ä»¥çœ‹çœ‹ \cmdname{dvips} æ˜¯å¦‚ä½•ç”Ÿæˆ \PS{} +文件的 (我们希望使用 Type~1 版本的 Computer Modern 字体,所以使用了 \texttt{-Pcms} +å‚æ•°)。 +\begin{alltt} +> \Ucom{dvips -d4100 hello-world -Pcms -o} +\end{alltt} +此时我们将 \cmdname{dvips} 的调试等级 4 (表示字体路径) å’Œ \KPS\ 的路径元素展开组åˆåˆ° +一起 (å‚è§ \cmdname{dvips} å‚考手册,\OnCD{texmf/doc/html/dvips/dvips_toc.html})。 +(ç¨ä½œæ•´ç†çš„) 输出è§å›¾~\ref{fig:dvipsdbga}。 +\begin{figure*}[tp] +\centering +\input{examples/ex6a.tex} +\caption{寻找é…置文件}\label{fig:dvipsdbga} + +\bigskip + +\input{examples/ex6b.tex} +\caption{寻找 prolog 文件}\label{fig:dvipsdbgb} + +\bigskip + +\input{examples/ex6c.tex} +\caption{寻找字体文件}\label{fig:dvipsdbgc} +\end{figure*} + +\cmdname{dvips} å¯åŠ¨åŽå°±å¼€å§‹æœå¯»å…¶éœ€è¦ä½¿ç”¨çš„文件。首先找到的是 \file{texmf.cnf}, +它给出了用于进一步查询其他文件的路径,然åŽæ‰¾åˆ°çš„是 \file{ls-R} 文件åæ•°æ®åº“ (用于 +优化文件æœç´¢é€Ÿåº¦) å’Œ \file{aliases} 文件 (用于创建åŒä¸€æ–‡ä»¶çš„多个别å,比如为较自然 +的长文件å创建 \acro{DOS} 8.3 风格的短别å)ã€‚ç„¶åŽ \cmdname{dvips} 去寻找它的通用 +é…置文件 \file{config.ps},接下æ¥æŸ¥æ‰¾ä¸ªäººå®šåˆ¶æ–‡ä»¶ \file{.dvipsrc} (ä¸è¿‡ä¸Šè¿°ä¾‹å­ä¸­å¹¶ +未找到,显示 \emph{not found})ã€‚æœ€åŽ \cmdname{dvips} 找到了 Computer Modern +\PS{} 字体的é…置文件 \file{config.cms} (因为执行 \cmdname{dvips} 时使用了 +\texttt{-Pcms} 选项)。这个文件里包å«äº†å­—体的 \TeX{} å称, \PS{} å称和文件å的对 +应关系。 + +\begin{alltt} +> \Ucom{more /usr/local/texmf/dvips/cms/config.cms} + p +ams.map + p +cms.map + p +cmbkm.map + p +amsbkm.map +\end{alltt} +于是 \cmdname{dvips} 接下æ¥å¯»æ‰¾è¿™äº›æ–‡ä»¶ï¼Œå†åŠ ä¸Šå›ºå®šè½½å…¥çš„,通用映射文件 +\file{psfonts.map} (这个文件里包å«å¸¸ç”¨ \PS{} 字体的映射,å‚è§ç¬¬ +\ref{sec:examples-of-use} 节的最åŽä¸€éƒ¨åˆ†ï¼Œè®¨è®ºäº† \PS{} 映射文件的处ç†)。 + +这时候 \cmdname{dvips} å‘用户表示它的存在: +\begin{alltt} +This is dvips(k) 5.92b Copyright 2002 Radical Eye Software (www.radicaleye.com) +\end{alltt} +\ifSingleColumn +然åŽå¼€å§‹å¯»æ‰¾ prolog 文件 \file{texc.pro}: +\begin{alltt}\small +kdebug:start search(file=texc.pro, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(texc.pro) => /usr/local/texmf/dvips/base/texc.pro +\end{alltt} +\else +然åŽå¼€å§‹å¯»æ‰¾ prolog 文件 \file{texc.pro} (è§å›¾~\ref{fig:dvipsdbgb})。 +\fi + +找到所需文件åŽï¼Œ\cmdname{dvips} è¾“å‡ºæ—¥æœŸå’Œæ—¶é—´ï¼Œå¹¶å‘ŠçŸ¥æˆ‘ä»¬å®ƒå°†ç”Ÿæˆ +\file{hello-world.ps} 文件,需è¦ç”¨åˆ° \file{cmr10} 字体文件, +这个字体属于``常驻 (resident) çš„'',也就是ä¸éœ€è¦è½½å…¥ä½å›¾æ–‡ä»¶çš„字体: +\begin{alltt}\small +TeX output 1998.02.26:1204' -> hello-world.ps +Defining font () cmr10 at 10.0pt +Font cmr10 is resident. +\end{alltt} +寻找并找到了 \file{cmr10.tfm} 文件。然åŽå†æ¬¡å¼•ç”¨äº†ä¸€äº› prolog 文件 (此处略去), +最终找到了 \file{cmr10.pfb} 这个 Type~1 字体,并将它包å«åœ¨è¾“出文件中 (è§æœ€åŽ +一行)。 +\begin{alltt}\small +kdebug:start search(file=cmr10.tfm, must\_exist=1, find\_all=0, + path=.:~/tex/fonts/tfm//:!!/usr/local/texmf/fonts/tfm//: + /var/tex/fonts/tfm//). +kdebug:search(cmr10.tfm) => /usr/local/texmf/fonts/tfm/public/cm/cmr10.tfm +kdebug:start search(file=texps.pro, must\_exist=0, find\_all=0, + ... + +kdebug:start search(file=cmr10.pfb, must\_exist=0, find\_all=0, + path=.:~/tex/dvips//:!!/usr/local/texmf/dvips//: + ~/tex/fonts/type1//:!!/usr/local/texmf/fonts/type1//). +kdebug:search(cmr10.pfb) => /usr/local/texmf/fonts/type1/public/cm/cmr10.pfb +[1] +\end{alltt} + +\subsection{è¿è¡Œæ—¶é€‰é¡¹} + +\Webc{} å¦ä¸€é¡¹æœ‰ç”¨çš„特性是å¯ä»¥é€šè¿‡ \KPS{} 读入的è¿è¡Œæ—¶æ–‡ä»¶ \file{texmf.cnf} +æ¥æŽ§åˆ¶ä¸€ç³»åˆ—的内存å‚æ•° (具体而言是数组的大å°)。内存的设置å¯ä»¥åœ¨è¿™ä¸ªæ–‡ä»¶çš„第三部分找到。 +比较é‡è¦çš„几个设置是: + +\begin{ttdescription} +\item[\texttt{main\_memory}] + 总的å¯ç”¨å†…存数,以 word 为å•ä½ï¼Œ\TeX{}, \MF{} å’Œ \MP\ å—æ­¤é™åˆ¶ã€‚ + æ¯ä¿®æ”¹ä¸€æ¬¡éƒ½å¿…é¡»é‡æ–°ç”Ÿæˆä¸€ä¸ªæ–°çš„æ ¼å¼æ–‡ä»¶ã€‚比如你å¯ä»¥ç”Ÿæˆä¸€ä¸ª``巨型''版本的 + \TeX{},将其存为 \texttt{hugetex.fmt}。 +\item[\texttt{extra\_mem\_bot}] + 为``大型'' \TeX{} æ•°æ®ç»“构预留的é¢å¤–空间:boxes, glue, breakpoint 等。如果你使用 + \PiCTeX{} 时特别有用。 +\item[\texttt{font\_mem\_size}] + \TeX{} 用于存储字体数æ®çš„ word 数。大致等于载入的所有 \acro{TFM} 文件的总和。 +\item[\texttt{hash\_extra}] + 为存储控制åºåˆ—而设置的散列表的é¢å¤–空间。一般散列表足够存储将近 10,000 + 个控制åºåˆ—。如果你排版的是一本有大é‡äº¤å‰å¼•ç”¨çš„书ç±ï¼Œè¿™ä¸ªå€¼å¯èƒ½ä¸å¤Ÿç”¨ã€‚默认的 + \texttt{hash\_extra} 是 \texttt{50000}。 +\end{ttdescription} + +\noindent 当然,这项功能并éžçœŸæ­£çš„动æ€å†…存和数组分é…的替代,但考虑到动æ€åˆ†é…在现在的 \TeX{} +太难实现,æ‰é€šè¿‡è¿™äº›é€‰é¡¹æ供了一些çµæ´»æ€§ã€‚ + +\begin{comment} +\section{在 Unix å¹³å°ä¸‹ç¼–译} + +If you have a platform for which executables are not included, you will +need to compile \TeX{} and friends. This is not as hard as it +sounds. What you need is all in the directory \texttt{source} in the +distribution. + +\subsection{需求} + +You will need at least 100 megabytes of disk space to compile all of +\TeX{} and its support programs. You'll also need an \acro{ANSI} C +compiler, a \cmdname{make} utility, a lexical scanner, and a parser +generator. We recommend the \GNU version of these programs +(\cmdname{gcc}, \GNU \cmdname{make}, \cmdname{m4}, \cmdname{flex}, +\cmdname{bison}). You may be able to work with other C compilers and +\cmdname{make} programs, but you will need a good understanding of +building Unix programs to sort out problems. + +Also, the command \texttt{uname} must return a sensible value. + + +\subsection{é…ç½®} + +To begin, perform a normal installation of \TL{} to your disk (see +section~\ref{sec:install-disk} on +\p.\pageref{sec:install-disk}). You may wish to skip installing +all of the prebuilt binaries. + +Then, unpack the source from the compressed \texttt{tar} file in the +directory \dirname{source} to your disk and change directory to where +you placed it. + +Next, run \cmdname{configure} with a command line like this: +\begin{alltt} +> \Ucom{sh configure -prefix=/usr/local/TeX} +\end{alltt} + +The \optname{-prefix} directory is the one where you installed the +support tree; the directory layout will be as follows (where \$TEXDIR +stands for the directory you chose): + +\noindent +\begin{tabular}{>{\ttfamily}ll@{}} + \dirname{$TEXDIR/share/texmf} & main tree with fonts,\\ + & \qquad macros, etc\\ + \dirname{$TEXDIR/man} & Unix manual pages\\ + \dirname{$TEXDIR/info} & \GNU style Info manuals\\ + \dirname{$TEXDIR/bin/$PLATFORM} & binaries\\ +\end{tabular} +%$ + +If you want to leave out the \dirname{$PLATFORM} directory level, +i.e., put the binaries directly into \dirname{$TEXDIR/bin}, specify +the \verb|--disable-multiplatform| option to \cmdname{configure}. + +Have a look at the output of \verb|./configure --help| for more +options you can use. For example, you can skip building of \OMEGA{} and +\eTeX{}. + + +\subsection{è¿è¡Œ \cmdname{make}} + +Make sure the shell variable or option \texttt{noclobber} is not set. +Then, run the main \cmdname{make} like this: +\begin{alltt} +> \Ucom{make world} +\end{alltt} +and relax\ldots + +Alternatively, you want to log all the output, as in: +\begin{alltt} +> \Ucom{sh -c "make world >world.log 2>\&1" \&} +\end{alltt} + +Before you believe that everything went ok, please check the log file +for errors: \GNU \cmdname{make} always uses the string \samp{***} +whenever a command fails. Also, check if all the programs were built: + +\begin{alltt} +> \Ucom{cd \var{TEXDIR}/bin/\var{archname}} +> \Ucom{ls | wc} +\end{alltt} +The result should be over 200 (you can check the exact number with the +\dirname{bin} directory contents in the distribution). + +If you need special privileges for \texttt{make install}, you can +separate the \samp{make world} into two different runs, like this: +\begin{alltt} +> \Ucom{make all} +> \Ucom{su} +> \Ucom{make install strip} +\end{alltt} + +After you've installed your new binaries, you should follow the normal +post-installation procedures, given in section~\ref{sec:postinstall} +(\p.\pageref{sec:postinstall}). + +Also, if you'd like to make your binaries available to others, please +contact us. We'll be happy to put them on the \TL\ web pages. +\end{comment} + +\section{致谢} + +\TL{} 是在几乎所有 \TeX{} 用户组织的å力下完æˆçš„。这个版本由 Karl Berry +监制。下é¢åˆ—出了过去和现在主è¦çš„贡献者: + +\begin{itemize*} + +\item 英国ã€å¾·å›½ã€è·å…°å’Œæ³¢å…°çš„ \TeX{} 用户组织 +(分别为 \acro{TUG}, \acro{DANTE} e.V., \acro{NTG}, å’Œ \acro{GUST}),他们为所在 +地区的 \TeX{} 社群æ供了必备的技术和管ç†åŸºç¡€è®¾æ–½ã€‚请加入本地的 \TeX ç”¨æˆ·ç»„ç»‡ï¼ +(å‚è§ \url{http://tug.org/usergroups.html}。) + +\item \acro{CTAN} 团队,特别值得一æ的是 Robin Fairbairns, Jim Hef{}feron, +å’Œ Rainer Sch\"opfã€‚ä»–ä»¬è´Ÿè´£åˆ†å‘ \TL{} 光盘镜åƒï¼Œä¸ºè½¯ä»¶åŒ…æ›´æ–°æ供支撑,\TL{} +正是基于这些软件包构建的。 + +\item Peter Breitenlohner å’Œ \eTeX\ å›¢é˜Ÿï¼Œä»–ä»¬åˆ›é€ äº†æœªæ¥ \TeX\ 的稳定基础。 +åŒæ—¶ç‰¹åˆ«æ„Ÿè°¢ Peter,他为整个 \TL 中 GNU autotools 的使用æ供了主è¦çš„帮助。 + +\item Thomas Esser,如果没有他优秀的 \teTeX{} 套件,\TL{} 根本ä¸å¯èƒ½å­˜åœ¨ã€‚ + +\item Michel Goossens,他一起编写了原始的文档。 + +\item Eitan Gurari,他ä¸çŸ¥ç–²å€¦åœ°æ”¹è¿›ç€çš„ \TeX4ht 程åºç”¨äºŽåˆ›å»ºè¿™ä»½æ–‡æ¡£çš„ \HTML{} +版本。 + +\item \Thanh, Martin Schr\"oder,和 pdf\TeX\ 团队,他们æŒç»­ä¸æ–­åœ°æ”¹è¿› \TeX\ +的功能。 + +\item Hans Hagen,他对 \ConTeXt\ æ ¼å¼ (\url{http://pragma-ade.com}) åšäº† +许多测试和修改,使之能够包å«åœ¨ \TL{} 的框架下。 + +\item Hartmut Henkel,他对 pdf\TeX\, Lua\TeX 等程åºçš„å¼€å‘起到了é‡è¦çš„贡献。 + +\item Taco Hoekwater,他对 \MP{} å’Œ (Lua)\TeX\ (\url{http://luatex.org}) +çš„å¼€å‘使之焕å‘新的活力。他还å‚与了将 \ConTeXt\ èžå…¥ \TL 的工作。 + +\item Pawe{\l} Jackowski,他创建了 Windows ä¸‹çš„å®‰è£…ç¨‹åº \cmdname{tlpm}, +å’Œ Tomasz {\L}uczak,因为他的 \cmdname{tlpmgui} 被用在了以å‰çš„版本。 + +\item Akira Kakuto,以他的 \acro{W32TEX} å‘行版 +(\url{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/}) 为基础æ供了 +Windows 下的二进制文件,以åŠè®¸å¤šå…¶ä»–的贡献。 + +\item Jonathan Kew å’Œ \acro{SIL},因为 Xe\TeX{} 是如此新颖而é‡å¤§ +的改进。他还花了大é‡æ—¶é—´å’Œç²¾åŠ›æ¥å°†å…¶é›†æˆåˆ° \TL{} ä¸­ã€‚ä»¥åŠ Mac\TeX å®‰è£…ç¨‹åº +的早期版本。 + +\item Dick Koch 他维护了 Mac\TeX\ (\url{http://tug.org/mactex}) 这个和 +\TL{} è”ç³»éžå¸¸ç´§å¯†çš„å‘行版本。 + +\item Reinhard Kotucha,他对 \TL{} 2008 的基础架构和安装程åºèµ·åˆ°äº†é‡è¦è´¡çŒ®ï¼Œ +ä»¥åŠ Windows 下的研究性工作,\texttt{getnonfreefonts} 脚本,等等。 + +\item Siep Kroonenberg,也因为他对 \TL{} 2008 基础架构和安装程åºçš„é‡è¦è´¡çŒ®ï¼Œ +尤其是在 Windows 上。他还花了大é‡çš„时间更新手册,介ç»äº†è¿™äº›æ–°çš„特性。 + +\item Petr Ol\v{s}ak,他éžå¸¸è®¤çœŸåœ°å调和检查所有的æ·å…‹è¯­å’Œæ–¯æ´›ä¼å…‹è¯­èµ„料。 + +\item Toshio Oshima,他æ供了 Windows 下的 \cmdname{dviout} 预览工具。 + +\item Manuel P\'egouri\'e-Gonnard,他对å®åŒ…æ›´æ–°ã€æ–‡æ¡£æ”¹è¿›ä»¥åŠ +\cmdname{tldoc} å¼€å‘上的努力。 + +\item Fabrice Popineau,他创建了 \TL{} 最早的 Windows 支æŒã€‚ + +\item Norbert Preining,他是 \TL{} 2008 基础架构和安装程åºçš„总设计师,还 +è´Ÿè´£å调了 Debian 版本的 \TL{} 工作 (å’Œ Frank K\"uster 一起),并æ供了许 +多建议。 + +\item Sebastian Rahtz,他是 \TL{} 的创始者,并维护了它许多年。 + +\item Vladimir Volovich,他很大地帮助解决了许多移æ¤å’Œç»´æŠ¤çš„问题,尤其是令我们能够 +å°† \cmdname{xindy} 包å«è¿›æ¥ã€‚ + +\item Staszek Wawrykiewicz,\TL{} 主è¦çš„测试人员,åŒæ—¶è¿˜æ˜¯è®¸å¤šé‡è¦æ³¢å…°è¯­æ”¯æŒçš„åè°ƒ +人员:字体ã€Windows 安装,和其他许多工作。 + +\item Olaf Weber,他对 \Webc{} è€å¿ƒçš„维护。 + +\item Gerben Wierda,他创建和维护 \MacOSX\ 支æŒï¼Œå¹¶å‚与了大é‡é›†æˆå’Œæµ‹è¯•å·¥ä½œã€‚ + +\item Graham Williams,他整ç†äº†è½¯ä»¶åŒ…çš„ä¾èµ–情况的 \TeX\ Catalogue。 + +\end{itemize*} + +二进制版本的编译者: +Tigran Aivazian (\pkgname{x86\_64-linux}), +Tim Arnold (\pkgname{hppa-hpux}), +Randy Au (\pkgname{amd64-freebsd}), +Edd Barrett (\pkgname{i386-openbsd}), +Karl Berry (\pkgname{i386-linux}), +Akira Kakuto (\pkgname{win32}), +Dick Koch (\pkgname{universal-darwin}), +Manfred Lotz (\pkgname{i386-freebsd}), +Norbert Preining (\pkgname{alpha-linux}), +Arthur Reutenauer (\pkgname{sparc-linux}), +Thomas Schmitz (\pkgname{powerpc-linux}), +Apostolos Syropoulos (\pkgname{i386-solaris}), +Vladimir Volovich (\pkgname{powerpc-aix}, \pkgname{sparc-solaris}), +Olaf Weber (\pkgname{mips-irix})。 +关于 \TL{} 编译进程的信æ¯ï¼Œè¯·æŸ¥é˜… \url{http://tug.org/texlive/build.html}。 + +文档和翻译的更新: +Karl Berry (英语), +Daniel Flipo (法语), +Klaus H\"oppner (德语), +Petr Sojka \& Jan Busa (æ·å…‹\slash 斯洛ä¼å…‹è¯­), +Boris Veytsman (俄语), +Staszek Wawrykiewicz (波兰语)。\TL{} 文档的主页是 +\url{http://tug.org/texlive/doc.html}。 + +当然,最é‡è¦çš„感谢应该致予 Donald Knuth,感谢他å‘明了 \TeX,也感谢他将 +\TeX\ 赠与全世界。 + +\section{å‘行历å²} +\label{sec:history} + +\subsection{过去} + +1993 年末è·å…° \TeX{} 用户组开始为 \acro{MS-DOS} ç”¨æˆ·å¼€å‘ 4All\TeX{} \CD{} 时, +我们就开始了相关的讨论,并希望在此时为所有的æ“作系统æ供一个å•ä¸€çš„ã€åˆç†çš„ \CD{}。当时 +那是一个过于å®ä¼Ÿçš„目标,但的确滋生了éžå¸¸æˆåŠŸçš„ 4All\TeX{} \CD{},åŒæ—¶ \acro{TUG} +技术委员会工作组也开始设计 \emph{\TeX{} 目录结构} (\url{http://tug.org/tds}), +以指明如何创建一套一致而å¯æŽ§çš„集åˆï¼Œå›Šæ‹¬æ‰€æœ‰ \TeX{} 相关的文件。\TDS{} 的完整è‰æ¡ˆåœ¨ 1995 +å¹´ 12 月的 \textsl{TUGboat} 上出版,并åˆæ­¥ç¡®å®šæœŸæœ›çš„产å“将是在 \CD{} 上出现的范例 +结构。你现在使用的这个å‘行版正是工作组审议的直接结果。4All\TeX{} \CD{} çš„æˆåŠŸä¹Ÿè¯´æ˜Ž +如果有一个类似这样的易于使用的系统,对 Unix 用户肯定很有帮助,这是 \TL{} 最主è¦çš„出å‘点。 + +我们在 1995 年秋天开始å°è¯•æž„建一个新的 \CD{} (基于 \TDS{}),并很快å‘现 Thomas Esser +çš„ \teTeX{} å·²ç»æ˜¯æ¯”较ç†æƒ³çš„é…置,并因为在它构建时就已ç»è€ƒè™‘了跨文件系统的兼容性问题, +也已具有多平å°æ”¯æŒã€‚Thomas åŒæ„帮助我们,并在 1996 å¹´åˆå¼€å§‹äº†æ­£å¼çš„工作。第一版是在 +1996 年五月å‘行的。到 1997 å¹´åˆï¼ŒKarl Berry 完æˆäº† \Webc{} 的一个é‡å¤§çš„更新版本, +将几乎所有 Thomas Esser 加入 \teTeX{} 的特性囊括在内,这样我们决定在 \teTeX{} çš„ +\texttt{texconfig} 脚本的辅助下,基于标准的 \Webc{} æ¥åˆ¶ä½œç¬¬äºŒç‰ˆçš„ \CD{}。 +第 3 版的 \CD{} 基于 Olaf Weber 完æˆçš„ \Webc{} 的一个é‡å¤§ä¿®æ­£ç‰ˆæœ¬ï¼Œ7.2。与此åŒæ—¶ï¼Œ +\teTeX{} 的一个新版本出现了,\TL{} 也包å«äº†å…¶ä¸­ç»å¤§å¤šæ•°ç‰¹æ€§ã€‚第 4 版ä¾ç…§ä¸Šé¢çš„模å¼è¿› +行,使用了新版本的 \teTeX{} 和新版本的 \Webc{} (7.3)。系统此时也包括了完整的 Windows +下的é…置。 + +在第 5 版 (2000 å¹´ 3 月) 中检查并修正了 \CD{} 的许多部分,更新了数百个软件包。软件 +包的详细说明现在存放在 XML 文件中。ä¸è¿‡ \TeX\ Live 5 的首è¦å˜åŒ–还是移除了所有的éžè‡ªç”±è½¯ +件。\TL{} çš„æ‰€æœ‰éƒ¨åˆ†çŽ°åœ¨éƒ½åœ¨å‘ Debian Free Software Guidelines 兼容的方å‘改进, +我们尽最大努力检查了所有软件包的授æƒå议,欢迎为我们指出错误。 + +第 6 版 (2001 å¹´ 7 月) 更新了许多内容。最é‡å¤§çš„一项是新的安装形å¼ï¼Œç”¨æˆ·å¯ä»¥æ›´ç²¾ç¡® +地选择所需的软件集åˆã€‚与语言相关的集åˆä¹Ÿé‡æ–°ç»„织过了,这样一æ¥ï¼Œé€‰å®šæŸä¸ªè¯­è¨€é›†åˆæ—¶ä¼šè‡ª +动安装å®åŒ…ã€å­—体等文件,并自动设置好 \texttt{language.dat}。 + +2002 年出现的第 7 版里显著的更新是添加了 \MacOSX{} 的支æŒï¼Œè¿˜æœ‰å¤§é‡å„ç±»å®åŒ…å’Œç¨‹åº +的更新。这个版本的一个é‡è¦çš„目标是将æºä»£ç é‡æ–°ä¸Ž \teTeX{} 集æˆï¼Œå› ä¸ºåœ¨ç¬¬ 5 和第 6 +版中它们å离得太远了。 + +\subsubsection{2003} + +2003 年,在更新和增添æŒç»­ä¸æ–­åˆ°æ¥çš„情况下,我们å‘现 \TL{} å·²ç»è¿‡äºŽåºžå¤§ï¼Œæ— æ³•åœ¨ä¸€å¼  +\CD\ 中容纳,于是将其切分为三套ä¸åŒçš„å‘行版 (å‚è§ç¬¬~\ref{sec:tl-coll-dists} +节,\p.\pageref{sec:tl-coll-dists})。此外: + +\begin{itemize*} +\item 在 \LaTeX{} 团队的è¦æ±‚下,我们将 \cmdname{latex} å’Œ \cmdname{pdflatex} + 命令改为使用 \eTeX{} 引擎 (å‚è§ \p.\pageref{text:etex})。 +\item 包å«äº†æ–°çš„ Latin Modern 字体 (并推è使用)。 +\item 因为ä¸å†æœ‰äººæ‹¥æœ‰ (或主动æä¾›) 用于编译新的二进制程åºçš„硬件,去除了 + Alpha \acro{OSF} çš„æ”¯æŒ (å…ˆå‰å·²ç»åŽ»é™¤äº† \acro{HPUX} 的支æŒ)。 +\item Windows 下的安装有很大改å˜ï¼Œé¦–次æ供了基于 XEmacs 的集æˆçŽ¯å¢ƒã€‚ +\item Windows 下é‡è¦çš„è¾…åŠ©æ€§ç¨‹åº (Perl, Ghost\-script, Image\-Magick, Ispell) + 现在放在 \TL{} 的安装目录。 +\item \cmdname{dvips}, \cmdname{dvipdfm} å’Œ \cmdname{pdftex} + 使用的字体映射文件现在通过 \cmdname{updmap} 这套新程åºç”Ÿæˆï¼Œå¹¶å®‰è£…到 + \dirname{texmf/fonts/map} 目录下。 +\item \TeX{}, \MF{}, å’Œ \MP{} 现在缺çœç›´æŽ¥è¾“出大多数的输入字符 (ä½ç½® 32 åŠå…¶ä»¥ä¸Š) + (比如通过 \verb|\write|),包括输出到文件ã€æ—¥å¿—和终端上。也就是说,\emph{ä¸å†}使用 + \verb|^^| 标记æ¥è½¬æ¢ã€‚在 \TL{}~7 中是å¦è½¬æ¢æ ¹æ®ç³»ç»ŸåŒºåŸŸ (locale) + 设置而定,而这一版里 locale 设置ä¸å†å½±å“ \TeX{} 程åºçš„è¡Œä¸ºï¼Œæ‰€ä»¥å¦‚æžœä½ éœ€è¦ + \verb|^^| å½¢å¼çš„输出,请将 \verb|texmf/web2c/cp8bit.tcx| + 文件改å。(åŽç»­ç‰ˆæœ¬å°†æ供更简æ´çš„æ–¹å¼æ¥æŽ§åˆ¶ã€‚) +\item 对文档作了大é‡æ›´æ–°ã€‚ +\item 最åŽï¼Œå› ä¸ºç‰ˆæœ¬å·å¢žé•¿å¾—实在太快,现在简å•åœ°ä½¿ç”¨å¹´ä»½æ¥æ ‡è¯†ç‰ˆæœ¬ï¼š\TL{} 2003。 +\end{itemize*} + + +\subsubsection{2004} + +2004 年有许多改å˜ï¼š + +\begin{itemize} + +\item 如果你在本地安装的字体时涉åŠäº† \filename{.map} 或 \filename{.enc} +(附带这ç§æ–‡ä»¶çš„å¯èƒ½æ€§å¾ˆå°) 辅助文件,å¯èƒ½éœ€è¦è½¬ç§»è¿™äº›æ–‡ä»¶çš„ä½ç½®ã€‚ + +çŽ°åœ¨æ ¹æ® \envname{TEXFONTMAPS} å˜é‡ä¸­çš„路径设置,åªåœ¨ (所有 \filename{texmf} +目录树下的) \dirname{fonts/map} å­ç›®å½•ä¸‹æœç´¢ \filename{.map} +文件。与之类似,\filename{.enc} 文件现在åªåœ¨ \dirname{fonts/enc} +目录下æœç´¢ï¼Œæ ¹æ® \envname{ENCFONTS} å˜é‡ä¸­çš„路径设置。如果é‡åˆ°æœ‰é—®é¢˜çš„æ–‡ +件,\cmdname{updmap} 会æ出警告。 + +关于这ç§æœç´¢æ–¹å¼çš„其他信æ¯ï¼Œè¯·å‚è§ \url{http://tug.org/texlive/mapenc.html}。 + +\item 因为有人å¯èƒ½æ›´æ„¿æ„使用 \MIKTEX\ è€Œéž \Webc{} 系统,\TK\ +现在包å«äº†ä¸€å¥—基于 \MIKTEX\ çš„å¯å®‰è£… \CD,å‚è§ç¬¬~\ref{sec:overview-tl} 节 +(\p.\pageref{sec:overview-tl})。 + +\item 在原æ¥æ—§ç‰ˆæœ¬ \TL\ 中å•ä¸€çš„ \dirname{texmf} 目录树被分拆为三 +个:\dirname{texmf}, \dirname{texmf-dist}, å’Œ \dirname{texmf-doc}。å‚è§ +第~\ref{sec:tld} 节 (\p.\pageref{sec:tld}) åŠå„目录下的 \filename{README} +文件。 + +\item 所有 \TeX\ 输入文件现在统一收集到了 \dirname{texmf*} 下的 +\dirname{tex} å­ç›®å½•ä¸­ï¼Œä¸å†åˆ†æ•£åœ¨å„个 \dirname{tex}, \dirname{etex}, +\dirname{pdftex}, \dirname{pdfetex} 目录。è§~ +\CDref{texmf-doc/doc/english/tds/tds.html\#Extensions} +{\texttt{texmf-doc/doc/english/tds/tds.html\#Extensions}}。 + +\item 辅助性脚本 (并éžç›´æŽ¥æ供给用户调用的) 现在放在 \dirname{texmf*} 目录树下 +æ–°çš„ \dirname{scripts} å­ç›®å½•ä¸­ï¼Œå¹¶å¯ä»¥é€šè¿‡ \verb|kpsewhich -format=texmfscripts| +æ¥æœç´¢ã€‚如果你的程åºè°ƒç”¨äº†è¿™äº›è„šæœ¬ï¼Œå¿…须修改路径。å‚è§ +\CDref{texmf-doc/doc/english/tds/tds.html\#Scripts} +{\texttt{texmf-doc/doc/english/tds/tds.html\#Scripts}}。 + +\item 几乎所有格å¼ï¼Œéƒ½ç”¨ \filename{cp227.tcx} 这个转æ¢æ–‡ä»¶å°†å¤§å¤šæ•°çš„å¯è§ (printable) +字符ä¿ç•™ä¸‹æ¥ï¼Œè€Œä¸å†ä½¿ç”¨ \verb|^^| 标识æ¥è½¬æ¢è¿™äº›å­—符。具体而言,在ä½ç½® 32--256 çš„ +字符,加上 tab, vertical tab, å’Œ form feed 字符都作为å¯è§å­—符而ä¸å†è½¬æ¢ã€‚例外情况是 +plain \TeX\ (åªå°†ä½ç½® 32--126 的字符视为å¯è§), \ConTeXt\ (0--255 都视为å¯è§) 和与 +\OMEGA\ 相关的格å¼ã€‚缺çœçš„情况几乎与 \TL\,2003 完全一致,但通过更简æ´çš„æ–¹å¼å®žçŽ°ï¼Œå¹¶å…许 +更多定制。å‚è§ \CDref{texmf/doc/web2c/web2c.html\#TCX-files} +{\texttt{texmf/doc/web2c/web2c.html\#TCX-files}}。 +(å¦å¤–,如果é‡åˆ° Unicode 输入,\TeX\ å¯èƒ½ä¼šåœ¨æ˜¾ç¤ºé”™è¯¯ä¸Šä¸‹æ–‡æ—¶è¾“出åŠä¸ªå­—符,因为它是基于 +字节æµæ¥å¤„ç†è¾“入的。) + +\item \textsf{pdfetex} 现在是除 (plain) \textsf{tex} 外所有格å¼çš„默认引擎 (当然 +以 \textsf{latex} è¿™ç§æ–¹å¼è¿è¡Œæ—¶å®ƒè¿˜æ˜¯ç”Ÿæˆ \acro{DVI})。这样一æ¥ï¼Œè‡³å°‘ \textsf{pdftex} +的微调排版 (microtypographic) 技术å¯ä»¥åœ¨ \LaTeX, \ConTeXt 等格å¼ä¸­ä½¿ç”¨ï¼Œå¦å¤– \eTeX\ +的特性也包å«åœ¨å…¶ä¸­ (\OnCD{texmf-dist/doc/etex/base/})。 + +这还说明\emph{比以å‰ä»»ä½•æ—¶å€™éƒ½æ›´æœ‰å¿…è¦}使用 (对 plain å’Œ \LaTeX\ 都适用的) +\pkgname{ifpdf} å®åŒ…或其类似代ç ï¼Œå› ä¸ºåªæ£€æŸ¥ \cs{pdfoutput} 或其他原语是å¦å·²ç»å®šä¹‰ +ä¸å†æ˜¯åˆ¤æ–­æ˜¯å¦å¤„于 \acro{PDF} 输出状æ€çš„å¯é æ–¹æ³•ã€‚我们在这一年尽å¯èƒ½åœ°ä¿æŒå‘ä¸‹å…¼å®¹ï¼Œä½†ä»¥åŽ +å³ä½¿åœ¨è¾“出 \acro{DVI} æ—¶ \cs{pdfoutput} 也å¯èƒ½å·²ç»å®šä¹‰ã€‚ + +\item pdf\TeX\ (\url{http://pdftex.org}) 新增了许多特性: + + \begin{itemize*} + + \item å¯ä»¥ä½¿ç”¨ \cs{pdfmapfile} å’Œ \cs{pdfmapline} æ¥åœ¨å•ç‹¬æ–‡æ¡£å†…指定字体映射文件。 + + \item å¯ä»¥æ›´æ–¹ä¾¿åœ°ä½¿ç”¨æŽ’版微调 (Microtypographic) 和字体延展 (font expansion) + 技术了。\\ + \url{http://www.ntg.nl/pipermail/ntg-pdftex/2004-May/000504.html} + + \item 原æ¥ä½¿ç”¨ä¸“有格å¼çš„é…置文件 \filename{pdftex.cfg} 里的选项现在都必须改用 + \TeX{} 原语æ¥è®¾ç½®ï¼Œé€šå¸¸æ”¾åœ¨ \filename{pdftexconfig.tex} 里é¢ï¼Œä¸å†æ”¯æŒ + \filename{pdftex.cfg} çš„é…置方å¼ã€‚æ¯æ¬¡ä¿®æ”¹ \filename{pdftexconfig.tex} + 之åŽéƒ½å¿…é¡»é‡æ–°ç”Ÿæˆ \filename{.fmt} 文件。 + + \item å‚è§ pdf\TeX\ 手册以了解更多信æ¯ï¼š\OnCD{texmf/doc/pdftex/manual}。 + + \end{itemize*} + +\item \cmdname{tex} (ä»¥åŠ \cmdname{mf} å’Œ \cmdname{mpost}) 中的 \cs{input} +原语现在支æŒé€šè¿‡åŒå¼•å·æ¥å¼•ç”¨åŒ…å«ç©ºæ ¼å’Œç‰¹æ®Šå­—符的文件。一个典型的例å­å¦‚下: +\begin{verbatim} +\input "filename with spaces" % plain +\input{"filename with spaces"} % latex +\end{verbatim} +å‚阅 \Webc{} 文档以了解更多信æ¯ï¼š\OnCD{texmf/doc/web2c}。 + +\item enc\TeX\ 的支æŒçŽ°åœ¨å·²è¢«åŒ…å«åœ¨ \Webc{} 中,因而所有 \TeX\ 程åºéƒ½å¯ä»¥é€šè¿‡ +\optname{-enc} å‚æ•°å¯ç”¨è¿™ä¸€æ”¯æŒ \Dash \emph{å‰æ是构建好了格å¼æ–‡ä»¶}。enc\TeX\ +æ供了对输入输出通用的é‡æ–°ç¼–ç åŠŸèƒ½ï¼Œå®žçŽ°å¯¹ Unicode (以 \acro{UTF}-8 ç¼–ç çš„å½¢å¼) +的完整支æŒã€‚å‚è§ \OnCD{texmf-dist/doc/generic/enctex/} å’Œ +\url{http://www.olsak.net/enctex.html}。 + +\item æ供了 Aleph 这套新的 \TeX{} 引擎,它将 \eTeX\ å’Œ \OMEGA\ åˆå¹¶åˆ°äº†ä¸€èµ·ã€‚ +关于 Aleph 的部分信æ¯å¯ä»¥åœ¨ \OnCD{texmf-dist/doc/aleph/base} +å’Œ \url{http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph} 找到。Aleph +çš„ \LaTeX æ ¼å¼æ–‡ä»¶ç§°åš \textsf{lamed}。 + +\item 最新å‘布的 \LaTeX\ 包å«äº†æ˜¯æ–°ç‰ˆçš„ \acro{LPPL} 授æƒåè®®\Dash 这一å议已被 +Debian 首肯。\LaTeX\ å…¶ä»–çš„æ›´æ–°è¯·è§ \OnCD{texmf-dist/doc/latex/base} 下的 +\filename{ltnews} 文件。 + +\item 包å«äº†ä¸€ä¸ªå«åš \cmdname{dvipng} 的新程åºï¼Œç”¨äºŽå°† \acro{DVI} 转æ¢ä¸º +\acro{PNG} 图åƒæ–‡ä»¶ã€‚å‚è§ \OnCD{texmf/doc/man/man1/dvipng.1}。 + +\item 我们在作者 (Claudio Beccari) çš„åŒæ„下,将 \pkgname{cbgreek} 包å«çš„ +字体数é‡å‡å°‘到中等。去除了ä¸å¯è§ã€è½®å»“å’Œé€æ˜Žç‰ˆæœ¬çš„字体,这些字体几乎很少用到。而我们 +的光盘镜åƒéœ€è¦ç©ºé—´ã€‚完整版本当然还是在 \acro{CTAN} æä¾› +(\url{http://www.ctan.org/tex-archive/fonts/greek/cb})。 + +\item 去掉了 \cmdname{oxdvi},改为åªä½¿ç”¨ \cmdname{xdvi}。 + +\item ä¸å†ä¸º \cmdname{tex}, \cmdname{mf}, å’Œ \cmdname{mpost} 程åºåˆ›å»º +\cmdname{ini} å’Œ \cmdname{vir} 开头的命令链接,比如 +\cmdname{initex}。\cmdname{ini} 的功能早在几年å‰å°±é€šè¿‡ \optname{-ini} +命令行å‚æ•°æ供了。 + +\item 去掉了 \textsf{i386-openbsd} å¹³å°çš„支æŒã€‚因为在 \acro{BSD} Ports +系统中已ç»åŒ…å«äº† \pkgname{tetex} 软件包,而 \acro{GNU/}Linux å’Œ +Free\acro{BSD} 下的二进制版本都已存在,所以志愿者的时间å¯ä»¥èŠ±åœ¨å…¶ä»–的地方了。 + +\item 至少在 \textsf{sparc-solaris} å¹³å°ä¸‹ï¼Œä½ å¿…须设置好 +\envname{LD\_LIBRARY\_PATH} 环境å˜é‡æ‰èƒ½æ‰§è¡Œ \pkgname{t1utils} 包å«çš„程åºã€‚ +因为这些程åºæ˜¯ä½¿ç”¨ C++ 编写的,其è¿è¡Œæ—¶åº“没有固定的ä½ç½®ã€‚(这一情况并éžåœ¨ 2004 版 +中首次出现,但现在æ‰å†™å…¥æ–‡æ¡£) 与之类似,\textsf{mips-irix} å¹³å°ä¸‹éœ€è¦ç”¨åˆ° +\acro{MIPS}pro 7.4 è¿è¡Œæ—¶åº“。 + +\end{itemize} + +\subsubsection{2005} + +2005 年一如往常,å®åŒ…和程åºéƒ½æœ‰å¤§é‡çš„更新。底层结构和 2004 年相比ä¿æŒäº†ç¨³å®šï¼Œ +ä¸è¿‡ä»ç„¶å­˜åœ¨ä¸€äº›å˜åŒ–。 + +\begin{itemize} + +\item 引入了新的 \cmdname{texconfig-sys}, \cmdname{updmap-sys}, å’Œ + \cmdname{fmtutil-sys} 安装脚本,用于修改系统目录树下的é…置。而原有的 + \cmdname{texconfig}, \cmdname{updmap}, å’Œ \cmdname{fmtutil} + 则用于修改针对å•ä¸ªç”¨æˆ·çš„文件 (放在 \dirname{$HOME/.texlive2005} + 目录下的)。 + +\item 增加了对应的 \envname{TEXMFCONFIG} å’Œ \envname{TEXMFSYSCONFIG} + å˜é‡ï¼Œåˆ†åˆ«ç”¨äºŽè®¾ç½®é’ˆå¯¹ç”¨æˆ·å’Œç³»ç»Ÿçš„,专门存放é…置文件的目录树。所以你需è¦å°†ä¸ªäººä½¿ç”¨çš„ + \filename{fmtutil.cnf} å’Œ \filename{updmap.cfg} + 放到åˆé€‚ä½ç½®ã€‚ä¸è¿‡è¿˜æœ‰ä¸€ç§æ–¹æ³•æ˜¯åœ¨ \filename{texmf.cnf} 里边é‡æ–°å®šä¹‰ + \envname{TEXMFCONFIG} 或 \envname{TEXMFSYSCONFIG} + å˜é‡ã€‚无论如何,这两个值对应的实际目录都必须正确存在。å‚è§ç¬¬ + \pageref{sec:texmftrees} 页的第 \ref{sec:texmftrees} 节。 + +\item 虽然我们在上一年就已ç»ä½¿ç”¨äº† \cmdname{pdfetex} 作为输出程åºï¼Œä½†åœ¨å®ƒè¾“出 \dvi\ + æ ¼å¼æ—¶ä¼šç¦ç”¨ \verb|\pdfoutput| 等原语 + (primitive)。这一年,我们按照预期计划å–消了这一兼容性é™åˆ¶ã€‚所以,如果你的文档里使用了 + \verb|\ifx\pdfoutput\undefined| 这样的语å¥æ¥åˆ¤æ–­æ˜¯å¦æ­£åœ¨ PDF + 输出模å¼ä¸‹ï¼ŒçŽ°åœ¨å°±å¿…须修改了。你å¯ä»¥ä½¿ç”¨ \pkgname{ifpdf.sty} å®åŒ… (对 plain \TeX\ + å’Œ \LaTeX{} 都适用) æ¥åˆ¤æ–­ï¼Œæˆ–者仿照这个文件里的判断原ç†è‡ªå·±å†™ä¸€ä¸ªã€‚ + +\item 上一年,我们将格å¼æ–‡ä»¶çš„输出改æˆäº†å’Œè¿™äº›æ–‡ä»¶æœ¬èº«ä¸€æ ·çš„ 8 + ä½å­—符。在你需è¦çš„情况下,å¯ä»¥ä½¿ç”¨æ–°çš„ TCX 文件 \filename{empty.tcx} æ¥èŽ·å¾—原有的 + \verb|^^| 表示方å¼ã€‚例如: + +\begin{verbatim} +latex --translate-file=empty.tcx yourfile.tex +\end{verbatim} + +\item æ–°å¢žäº†ç”¨äºŽè½¬æ¢ DVI 为 PDF çš„ \cmdname{dvipdfmx} 程åºï¼Œè¿™æ˜¯ + \cmdname{dvipdfm} 的一个比较活跃更新的版本 (我们ä»ç„¶æä¾› + \cmdname{dvipdfm},但ä¸å»ºè®®ä½ ç»§ç»­ä½¿ç”¨)。 + +\item æ–°å¢žäº†å« \cmdname{pdfopen} å’Œ \cmdname{pdfclose} 的两个程åºï¼Œç”¨äºŽæŽ§åˆ¶ + Adobe Acrobat\slash Reader 在ä¸é‡å¯ç¨‹åºçš„情况下é‡æ–°è½½å…¥ pdf 文件。(其他的 + pdf 阅读器,如 \cmdname{xpdf}, \cmdname{gv}, å’Œ + \cmdname{gsview},都ä¸ä¼šé‡åˆ°è¿™ä¸ªé—®é¢˜ã€‚) + +\item 为了ä¿æŒä¸€è‡´æ€§ï¼Œå°† \envname{HOMETEXMF} å’Œ \envname{VARTEXMF} + 环境å˜é‡åˆ†åˆ«æ›´å为 \envname{TEXMFHOME} å’Œ + \envname{TEXMFSYSVAR}。还有一个针对å•ç‹¬ç”¨æˆ·çš„ \envname{TEXMFVAR} + 环境å˜é‡å¯ç”¨ã€‚å‚è§ä¸Šé¢çš„第一点。 + +\end{itemize} + + +\subsubsection{2006--2007} + +2006--2007 年,\TL{} 的一个é‡å¤§å˜åŒ–是增加了 \XeTeX{},以 \texttt{xetex} å’Œ +\texttt{xelatex} 程åºçš„å½¢å¼æ供。请å‚è§ \url{http://scripts.sil.org/xetex}。 + +\MP{} 也有å¯è§‚的更新,并计划在未æ¥å®žçŽ°æ›´å¤šçš„改进 +(\url{http://tug.org/metapost/articles}),pdf\TeX{} åŒæ ·å¦‚æ­¤ +(\url{http://tug.org/applications/pdftex})。 + +\TeX\ \filename{.fmt} (缓存格å¼) 文件和用于 MetaPost å’Œ \MF\ 的类似文件 +现在存储在 \dirname{texmf/web2c} çš„å­ç›®å½•ä¸­è€Œä¸ç›´æŽ¥æ”¾åœ¨ \dirname{texmf/web2c} +目录下 (ä¸è¿‡è€ƒè™‘到现有的 \filename{.fmt} 文件,直接放置在这个目录下的文件ä»ç„¶ +能被æœç´¢åˆ°)。å­ç›®å½•çš„å称是根æ®å½“å‰ä½¿ç”¨çš„``引擎''决定的,比如 \filename{tex} +或 \filename{pdftex} 或 \filename{xetex}。这个å˜åŒ–ä¸ä¼šå¯¹æ—¥å¸¸ä½¿ç”¨å¸¦æ¥ä»»ä½• +å½±å“。 + +(plain) \texttt{tex} 程åºä¸å†é€šè¿‡è¯»å– \texttt{\%\&} 开头的第一行æ¥å†³å®š +执行何ç§æ ¼å¼ï¼Œè€Œéµå¾ªçº¯ç²¹çš„ Knuth 风格 \TeX\ 的传统。(\LaTeX\ å’Œå…¶ä»–æ‰€æœ‰çš„ç¨‹åº +ä»ç„¶è¯»å– \texttt{\%\&} 开头的行。) + +当然,和往常一样,这一年里你能看到æˆç™¾ä¸Šåƒçš„å®åŒ…与程åºå¾—到更新。也和往常一样, +进一步的更新请使用 \acro{CTAN} (\url{http://www.ctan.org})。 + +从内部角度上看,æºä»£ç æ ‘现在改为使用 Subversion 管ç†ï¼Œå¹¶åœ¨æˆ‘们的主页上æ供了 +到 Web ç•Œé¢çš„链接,用于æµè§ˆä»£ç æ ‘。我们希望它能æˆä¸ºæœªæ¥å‡ å¹´ä¸­ç¨³å®šçš„å¼€å‘ +å¹³å°ã€‚ + +末了,2006 年五月 Thomas Esser 宣布他将åœæ­¢ te\TeX{} +(\url{http://tug.org/tetex}) 的更新。这样一æ¥ï¼Œå¤§å®¶å¯¹ \TL{} 的兴趣大增,尤其是在 +\GNU/Linux å‘行版中。(\TL{} æ供了一套新的 \texttt{tetex} 安装方案, +几乎和原有的 te\TeX{} 毫无二致。) 我们希望这些å˜åŒ–将最终转æ¢ä¸ºå¯¹æ•´ä¸ª \TeX\ +环境的改进,从而æ¯ä¸ªäººéƒ½ä¼šå—益。 + +\medskip \noindent +对过去历å²çš„最终一点æ示: 所有版本的 \TL{},包括 \CD\ 标签这些附属æ料,都在 +\url{ftp://tug.org/historic/systems/texlive} æ供。 + + +\subsection{现状} +\label{sec:tlcurrent} + +在 2008 年,整个 \TL{} 的基础架构都é‡æ–°è®¾è®¡è¿‡å¹¶é‡æ–°å®žçŽ°äº†ã€‚安装的完整 +ä¿¡æ¯è¢«å­˜æ”¾åœ¨ \filename{tlpkg/texlive.tlpdb} 这个纯文本文件中。 + +除了许多其他的功能外,我们终于å¯ä»¥é€šè¿‡ Internet 在安装åŽæ›´æ–° \TL{} +了,这是 MiK\TeX\ æ—©å·²æ供了许多年的特性。我们希望能定期更新 \CTAN 上 +æ–°å‘布的软件包。 + +包å«äº†ä¸€ä¸ªé‡è¦çš„新引擎 Lua\TeX\ (\url{http://luatex.org}),除了 +在排版上çµæ´»æ€§æ›´ä¸Šä¸€å±‚楼以外,它还æ供了一个优秀的脚本语言供 \TeX\ +文档内外使用。 + +对 Windows 和基于 Unix 系统的支æŒçŽ°åœ¨è¦ä¸€è‡´å¾—多了。尤其是大部分 Perl å’Œ +Lua 脚本都能在 Windows 下使用,通过 \TL 内部包å«çš„ Perl。 + +æ–°çš„ \cmdname{tlmgr} 脚本 (第 \ref{sec:tlmgr} 节) 是在åˆå§‹å®‰è£…åŽç®¡ç† +\TL{} 的通用界é¢ã€‚它处ç†äº†è½¯ä»¶åŒ…æ›´æ–°å’ŒåŽç»­çš„æ ¼å¼æ–‡ä»¶ã€map 文件和语言文件 +çš„é‡æ–°ç”Ÿæˆï¼Œå¹¶å¯é€‰åœ°åŒ…å«äº†æœ¬åœ°æ·»åŠ çš„内容。 + +éšç€ \cmdname{tlmgr} 到æ¥ï¼Œç¦ç”¨äº† \cmdname{texconfig} 中编辑格å¼å’Œ +æ–­å­—é…置文件的功能。 + +今年还æ供了大多数平å°çš„ \cmdname{xindy} 索引生æˆç¨‹åº +(\url{http://xindy.sourceforge.net})。 + +\cmdname{kpsewhich} 现在å¯ä»¥æŠ¥å‘Šç»™å®šæ–‡ä»¶çš„æ‰€æœ‰åŒ¹é… (\optname{--all} +å‚æ•°) 并é™åˆ¶åˆ—å‡ºç‰¹å®šç›®å½•ä¸‹çš„åŒ¹é… (\optname{--subdir} å‚æ•°)。 + +\cmdname{dvipdfmx} 程åºçŽ°åœ¨æ”¯æŒç”¨ \cmdname{extractbb} 命令æ¥è§£æž +bounding box ä¿¡æ¯ï¼Œè¿™æ˜¯ \cmdname{dvipdfm} 包å«ä½†æœªæ›¾å‡ºçŽ°åœ¨ +\cmdname{dvipdfmx} 中的最åŽä¸€ä¸ªåŠŸèƒ½ã€‚ + +去除了 \filename{Times-Roman}, \filename{Helvetica} 等字体别å。ä¸åŒçš„ +å®åŒ…对它们的ç†è§£ä¸åŒ (尤其是编ç çš„处ç†ä¸ä¸€æ ·),所以没有什么好的办法能解 +决。 + +去除了 \pkgname{platex} æ ¼å¼æ–‡ä»¶ï¼Œä»¥é¿å…与日文 \pkgname{platex} 的命å +冲çªï¼Œ\pkgname{polski} å®åŒ…现在被用作主è¦çš„波兰语支æŒã€‚ + +从内部而言 \web\ 字符串 pool 文件被编译进了二进制文件中,这样å¯ä»¥æ–¹ä¾¿ +å‡çº§ã€‚ + +最终 Donald Knuth 在他的 `\TeX\ tuneup of 2008' 中的更新也被包å«åœ¨è¿™æ¬¡ +å‘布中。å‚è§ \url{http://tug.org/TUGboat/Articles/tb29-2/tb92knut.pdf}。 + +\subsection{未æ¥} + +\emph{\TL{} 并ä¸å®Œç¾Žï¼} (也永远ä¸ä¼šè¾¾åˆ°å®Œç¾Žã€‚) 我们希望继续å‘行新的版本,也希望 +æ供更多的帮助文档ã€æ›´å¤šçš„实用程åºã€æ›´å¤šçš„安装程åºï¼Œå½“然还有更多更新的å®åŒ…与字体。这个 +工作是由压力巨大的志愿者在其空闲时间完æˆçš„,也有很多ä¸å¤Ÿå®Œå–„的地方。请å‚è§ +\url{http://tug.org/texlive/contribute.html}。 + +请把更正ã€å»ºè®®æˆ–者æ供帮助的æ„æ„¿å‘é€åˆ°ï¼š +\begin{quote} +\email{tex-live@tug.org} \\ +\url{http://tug.org/texlive} +\end{quote} + +\medskip +\noindent \textsl{ç¥ä½ ä½¿ç”¨ \TeX\ 愉快ï¼} + +\section{翻译说明} + +这里对简体中文版本《\TL{} 指å—》,å³æœ¬æ–‡æ¡£ä¸­éµå¾ªçš„翻译惯例作一简è¦è¯´æ˜Žï¼š + +\begin{itemize} + +\item package, 视上下文,有时翻译为软件包,有时翻译为å®åŒ…。 +\item format file, å³ \TeX{} 程åºä¸€èˆ¬éƒ½ä¼šé¢„载入的 \texttt{.fmt} +文件。本文档中翻译为格å¼æ–‡ä»¶ã€‚ +\item scheme, 本文档中译为 (安装) 方案。 +\item collection, 本文档中译为 (软件) 集åˆã€‚ +\item 本文档中有时对原文没有采用é€å­—é€å¥çš„对比翻译,而是总括其æ„æ€ï¼Œè½¬æ¢ä¸º +更易为中文 \TeX{} 用户习惯的表达方å¼ã€‚ +\item architecture/platform, 是æ„æ€æ¯”较相近的è¯ï¼ŒåŸºæœ¬ä¸Šæ˜¯åªæŸç§ CPU +和对应这个 CPU çš„æ“作系统。比如 i386-linux。本文里翻译为架构ã€å¹³å°ã€ä½“ç³» +结构等等。 +\item binary, 二进制文件,其实就是说å¯æ‰§è¡Œç¨‹åºæ–‡ä»¶å’Œåº“文件了。 + +\end{itemize} + +2007 年的简体中文版本由 Jiang Jiang, Jinsong Zhao, Yue Wang, +Helin Gai 翻译。其中 Jinsong Zhao è´Ÿè´£ Windows 部分的翻译,Yue Wang +å’Œ Helin Gai 进行了校对,Jiang Jiang 则负责其余的翻译和统稿。 + +2008 年的简体中文版本由 Jiang Jiang, Yue Wang å’Œ Jinsong Zhao 翻译。 + +\end{document} diff --git a/Master/tlpkg/tlpsrc/texlive-common.tlpsrc b/Master/tlpkg/tlpsrc/texlive-common.tlpsrc index ed08fb9d813..e69de29bb2d 100644 --- a/Master/tlpkg/tlpsrc/texlive-common.tlpsrc +++ b/Master/tlpkg/tlpsrc/texlive-common.tlpsrc @@ -1,2 +0,0 @@ -name texlive-common -category Documentation -- cgit v1.2.3